Hi Victor,
Is it possible to use an ingress policy on the ES card to match the DSCP
values and explicitly set the 802.1p value based on matching the
corresponding DSCP ? This way you will know that it is set and not
expecting it happen by the PFC/DFC as part of the egress qos on the line
card.
It is also possible that having a port-channel as the logical egress
interface is causing some problem, have you tried it without the
port-channel ? Port-channels do strange things with QoS in general.
regards,
Tony.
On Mon, 07 Apr 2014 07:08:11 +1000, Victor Lyapunov
<[email protected]> wrote:
Have not correcty described the setup:
(egress) Physical : Portchannel Switch port belonging to a WS_6724 card
(egress) Logical : SVI interface (802.1q encapsulation) for L3
termination
(ingress) Physical / Logical: Routed interface belonging to a ES+ card
(no
802.1q encapsulation)
We see that traffic that is forwarded through the WS card has 802.1p = 0
regardless of dscp value
But If theout going interface is also in a ES+ card then the output
802.1p
corresponds to the packets DSCP value
In ES+ a L3 interface is Dscp tust, was mistaken earlier. Indeed this
value
is retained (we see it in the corresponding
output packets of the WS card) but the derived 802.p =0. Need to find a
way
to make this derived 802.1p value to
correspond to the packet's DSCP when the egress interface belongs to a
WS_67xx card
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
