Bug or not?

EdTheLad

I sending qnq traffic through a network where the top tag gets reclassified at ingress and stripped at egress as it leaves third party, i want to ensure my original markings are correct on egress of the core. I put this policy map on ingress of my downstream switch.Anyway i would have expected one of my classes to be hit. most prob a bug but possible theres a rule about not being able to match cos on ingress blah blah what u think?


TenGigabitEthernet8/1 is up, line protocol is up (connected)
Hardware is C6k 10000Mb 802.3, address is 0013.7fcb.ccdc (bia 0013.7fcb.ccdc)
MTU 9216 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 24/255
Encapsulation ARPA, loopback not set
Full-duplex, 10Gb/s
input flow-control is desired, output flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 2d16h, output 1w0d, output hang never
Last clearing of "show interface" counters 00:04:32
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fair queuing
Output queue: 0/40 (size/max)
5 minute input rate 942206000 bits/sec, 230113 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
63724546 packets input, 32626960031 bytes, 0 no buffer
Received 17 broadcasts (9 multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
9 packets output, 576 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out



test#show policy-map inter ten 8/1
TenGigabitEthernet8/1

Service-policy input: CheckCos

Class-map: Priority0 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 0
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority1 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 1
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority2 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 2
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority3 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 3
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority4 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 4
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority5 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 5
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority6 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 6
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: Priority7 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: cos 7
queue size 0, queue limit 250000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0
bandwidth 10.00%, kbps 1000000

Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
queue size 0, queue limit 500000
packets input 0, packet drops 0
tail/random drops 0, no buffer drops 0, other drops 0



test#show policy-map
Policy Map CheckCos
Class Priority0
bandwidth percent 10
Class Priority1
bandwidth percent 10
Class Priority2
bandwidth percent 10
Class Priority3
bandwidth percent 10
Class Priority4
bandwidth percent 10
Class Priority5
bandwidth percent 10
Class Priority6
bandwidth percent 10
Class Priority7
bandwidth percent 10

Oh and traffic is definitely arriving tagged on my trunk with vlan 100.

d07-6500-1#show vlan id 100 counters
* Multicast counters include broadcast packets

Vlan Id : 100
L2 Unicast Packets : 5010489
L2 Unicast Octets : 2545328412
L3 Input Unicast Packets : 0
L3 Input Unicast Octets : 0
L3 Output Unicast Packets : 0
L3 Output Unicast Octets : 0
L3 Output Multicast Packets : 0
L3 Output Multicast Octets : 0
L3 Input Multicast Packets : 0
L3 Input Multicast Octets : 0
L2 Multicast Packets : 0
L2 Multicast Octets : 0

dtlokee

Is the port set to trust the incomming CoS? I seem to remember that the CoS classes will be bypassed on ingress then head to the IP tos processing (precedence) if the port is untrusted.

EdTheLad

dtlokee wrote:

Is the port set to trust the incomming CoS? I seem to remember that the CoS classes will be bypassed on ingress then head to the IP tos processing (precedence) if the port is untrusted.

I put the policy map on the egress port of an es20 and it worked.I've since found out that policy-maps cannot match cos on a 6500 6704 blade when its in switch mode.