Hello all, When attempting to view a policy on a nexus 7k interface I cannot see the offered rates as you would normally see. Any ideas? Here is how mine shows up: 7k01# sh policy-map interface e1/1 Global statistics status :   enabled Ethernet1/1   Service-policy (queuing) input:   default-in-policy     SNMP Policy Index:  301989921     Class-map (queuing):   in-q1 (match-any)       queue-limit percent 50       bandwidth percent 80       queue dropped pkts : 0     Class-map (queuing):   in-q-default (match-any)       queue-limit percent 50       bandwidth percent 20       queue dropped pkts : 0   Service-policy (queuing) output:   Nexus-QoS-10G     SNMP Policy Index:  301992049     Class-map (queuing):   1p7q4t-out-pq1 (match-any)       priority level 1       queue-limit percent 20       queue dropped pkts : 0     Class-map (queuing):   1p7q4t-out-q2 (match-any)       random-detect cos-based       random-detect cos 7 minimum-threshold percent 80 maximum-threshold percent 100       queue-limit percent 5       bandwidth remaining percent 5       queue dropped pkts : 0     Class-map (queuing):   1p7q4t-out-q3 (match-any)       random-detect cos-based       random-detect cos 6 minimum-threshold percent 80 maximum-threshold percent 100       queue-limit percent 5       bandwidth remaining percent 5       queue dropped pkts : 0     Class-map (queuing):   1p7q4t-out-q4 (match-any)       random-detect cos-based       random-detect cos 4 minimum-threshold percent 80 maximum-threshold percent 100       queue-limit percent 20       bandwidth remaining percent 15       queue dropped pkts : 0   From the cisco white paper: Configuration Examples For Monitoring QoS Statistics The following example shows how to display the QoS statistics: switch(config)# show policy-map interface ethernet 8/1 Global statistics status: enabled Ethernet8/1 Service-policy (qos) input: pmap policy statistics status: enabled Class-map (qos): map (match-all) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: cos 0 police cir 10 mbps bc 200 ms conformed 0 bytes, 0 bps action: transmit violated 0 bytes, 0 bps action: drop Class-map (qos): map1 (match-all) 0 packets, 0 bytes ... View more

Hello all, When attempting to view a policy on a nexus 7k interface I cannot see the offered rates as you would normally see. Any ideas? Here is how mine shows up: 7k01# sh policy-map interface e1/1 Global statistics status :   enabled Ethernet1/1   Service-policy (queuing) input:   default-in-policy     SNMP Policy Index:  301989921     Class-map (queuing):   in-q1 (match-any)       queue-limit percent 50       bandwidth percent 80       queue dropped pkts : 0     Class-map (queuing):   in-q-default (match-any)       queue-limit percent 50       bandwidth percent 20       queue dropped pkts : 0   Service-policy (queuing) output:   Nexus-QoS-10G     SNMP Policy Index:  301992049     Class-map (queuing):   1p7q4t-out-pq1 (match-any)       priority level 1       queue-limit percent 20       queue dropped pkts : 0     Class-map (queuing):   1p7q4t-out-q2 (match-any)       random-detect cos-based       random-detect cos 7 minimum-threshold percent 80 maximum-threshold percent 100       queue-limit percent 5       bandwidth remaining percent 5       queue dropped pkts : 0     Class-map (queuing):   1p7q4t-out-q3 (match-any)       random-detect cos-based       random-detect cos 6 minimum-threshold percent 80 maximum-threshold percent 100       queue-limit percent 5       bandwidth remaining percent 5       queue dropped pkts : 0     Class-map (queuing):   1p7q4t-out-q4 (match-any)       random-detect cos-based       random-detect cos 4 minimum-threshold percent 80 maximum-threshold percent 100       queue-limit percent 20       bandwidth remaining percent 15       queue dropped pkts : 0   From the cisco white paper: Configuration Examples For Monitoring QoS Statistics The following example shows how to display the QoS statistics: switch(config)# show policy-map interface ethernet 8/1 Global statistics status: enabled Ethernet8/1 Service-policy (qos) input: pmap policy statistics status: enabled Class-map (qos): map (match-all) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: cos 0 police cir 10 mbps bc 200 ms conformed 0 bytes, 0 bps action: transmit violated 0 bytes, 0 bps action: drop Class-map (qos): map1 (match-all) 0 packets, 0 bytes ... View more

Hi everyone, My network team has been having a discussion lately on where 'random-detect' should be placed.  For a long time we had it in the scavenger class and the default class.  I've personally never heard of it being in more than one class.  I think it should be in the default-class only.  So this raised more questions: 1. can it be in both classes? If yes, Are there any problems with this?' 2. Should it only be in one class? 3. should it be in the Parent policy TEST_ETH10000 under class-default so it applies random-detect to all classes in the child policy TEST-MPLS-QoS ?? How are other enterprises implementing random-detect? ! Configure child policy policy-map TEST-MPLS-QoS class Voice priority 1000 class Video bandwidth remaining percent 40 class VVSignaling bandwidth remaining percent 24 set ip dscp cs3 class NetworkSupport bandwidth remaining percent 5 class Scavenger bandwidth remaining percent 1 set ip dscp cs1 police rate percent 40 random-detect ?????? class class-default bandwidth remaining percent 30 set ip dscp default random-detect ?????? ! Configure Parent policy policy-map TEST_ETH10000 class class-default   random-detect ??????   shape average 9500000    service-policy TEST-MPLS-QoS ! Apply to WAN interface interface Gig1/1 description connection to MPLS ISP service-policy output TEST_ETH100000 ! Class-maps class-map match-any Voice match ip dscp ef class-map match-any Video match ip dscp af41 af42 class-map match-any VVSignaling match ip dscp cs3 match ip dscp af31 class-map match-any NetworkSupport match ip dscp cs6 match ip dscp cs2 match access-group name NetworkControl class-map match-any Scavenger match ip dscp cs1 match access-group name Scavenger-Protocols thanks, Dan CCIE RS 34827        ... View more

Does anyone have any information on when the 6k will support layer 3 ISSU? what code release and time frame etc? I'm looking to deploy a small/medium 10g solution and we need L3 to the WAN edge. Basically a collapsed DC core/aggregation with 2k's on the access. thanks, Dan CCIE RS 34827        ... View more

Hi Everyone, I've been searching high and low for specific information on my question but I can't seem to find just what I need... Other than testing on real equipment, I'm wondering of the performance impact a long ACL inside a class-map used for classification inside of a QOS policy would be... For example. A class-map is marking traffic with an ACL that has 5 entires, vs. a class-map that is marking traffic with 50 entries? 100 entries? 1000 entries?  I would assume there is some impact, depending on traffic throughput, load of other services, etc.  Has anyone experienced a similar design in production environment where they had very long ACL's within class maps nested in a QOS Policy-map? ======================================== class-map match-any Scavenger match access-group name Scav_ACL_Short ip access-list extended Scav_ACL_Short permit ip any 192.168.1.1 permit ip any 192.168.1.2 permit ip any 192.168.1.3 permit ip any 192.168.1.4 permit ip any 192.168.1.5 ========================================== Compared to... ========================================= class-map match-any Scavenger match access-group name Scav_ACL_Long ip access-list extended Scav_ACL_Long permit ip any 192.168.1.1 permit ip any 192.168.1.2 permit ip any 192.168.1.3 permit ip any 192.168.1.4 permit ip any 192.168.1.5 <output omitted> (entries all the way from 1 through 102) permit ip any 192.168.1.99 permit ip any 192.168.1.100 permit ip any 192.168.1.101 permit ip any 192.168.1.102 ... View more