Is anyone aware of a feature which allows the EXP value on an STP frame to be
set when it is encapsulated by a xconnect on a 6500?
description Customer Port
xconnect 188.8.131.52 666 encapsulation mpls
service-policy input set-exp-3
set mpls experimental imposition 3
I would expect all traffic which ingresses on that customer port to be set to
EXP 3 when it is encapsulated. This is, unfortunately, not the case....
When the traffic egresses the 6500, it is 'mostly' set to EXP 3 - except - a
few special things, like the STP frames, LLDP and some other control-type
stuff. Basically, only the IP stuff gets set to EXP 3.
Control things get various values, STP for example goes to EXP 0 - and nothing
changes this as far as I can find. I have also noticed some other types of
traffic are set to other values (like EXP 5,6,7) so clearly there are more
exceptions than just STP, but I figure that they are probably controlled by the
same knob/feature, somewhere...
Platform is Cat6500 with S720-10G, X6748 cards and IOS 15.1(2)SY6
It's a specific customer requirement so changing platform isn't an option in
this case. I've also tried re-writing it (to EXP 3) on egress out of the box
towards the MPLS core, but this isn't supported on this platform. I also tried
setting it on the tunnel, but again that is only supported in ingress, not
So - any ideas anyone?
Custodian Data Centres
cisco-nsp mailing list firstname.lastname@example.org
archive at http://puck.nether.net/pipermail/cisco-nsp/