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+
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
Hi Victor,
the ES+ does not use pfc qos (mls qos commands). Qos in handled locally on
the lc. Per Default without marking configuration the ES+ should act in
trust dscp mode. The ingress ES+ should set dbus-cos to inform pfc about
cos values. Without ingress COS in case of routed interface you
It would be super useful if Cisco could just copy/paste whatever is in SXJ that
makes them ‘supported’ into SXI then. =)
-Drew
From: Phil Mayers [mailto:p.may...@imperial.ac.uk]
Sent: Tuesday, April 08, 2014 6:11 PM
To: Drew Weaver; 'cisco-nsp@puck.nether.net'
Subject: Re: [c-nsp] Quick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Multiple Vulnerabilities in Cisco ASA Software
Advisory ID: cisco-sa-20140409-asa
Revision 1.0
For Public Release 2014 April 9 16:00 UTC (GMT)
Summary
===
Cisco Adaptive Security Appliance (ASA) Software is affected by the following
