os value
is not overwritten by earl or derived from dscp."
Hope this helps
Thomas
-Ursprüngliche Nachricht-
Von: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] Im Auftrag von
Victor Lyapunov
Gesendet: Mittwoch, 9. April 2014 09:03
An: cisco-nsp
Betreff: Re: [c-nsp] 7609 ES+, WS mark
Hello.
Is it possible, that the device connected to your WS card interfaces is not
trusting the CoS, but only the DSCP ?
So in fact your 7609 is correctly marking the CoS, but the next device unmark
it. Consider applying mls qos trust cos on it.
Also where exactly do you sniff the packets to
Hello Tony and thank you for the input
Unfortunately I can not get rid of the Port-Channel in my setup, byt still
performed the test with:
physical-interface: GigE interface / switchport
Logical-interface: SVI
And got the same results though. I can not though understand the
behaviour of ES+ rega
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
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 t
Hello
Have a question about 7609/RSP720 platform marking operation with mixed
linecard types. In the setup we are testing uplinks are
implemented in ES+ while customer facing interfaces in WS cards.
The egress traffic is forwarded out of the WS cards through a Port-channel
interface switchport wi
