to assign this high priority queue for user traffic, you encounter this warning message
suggesting that the user traffic assigned to this queue will cause drop of the critical traffic.
Warning!! This setting will make critical and data traffic treated with same priority. This will
cause drops in critical traffic Please not that the configuration will still be successful after this
warning.
Troubleshooting Module QoS - Error conditions
1.
Packets are not getting classified to a class-map
Symptom: Forwarded or dropped byte counters are not incrementing.
Description: When a policy-map is configured and attached to an interface, user
may see that the packets are not getting classified to the specified class-map in the
“show qos module policy-map” command output.
Troubleshooting tips: Some of the reasons that could result in the above behavior
are described below:
• Wrong rules are configured for the class-map. Traffic sent won’t be classified
to a class-map unless the packets match the rules configured in that class-
map. Make sure the rules configured for the class-map are proper. The
classification field and the value assigned should be correct. Use the show
qos module policy-map command to see the rules configured.
• Wrong
rule types are used. There are 3 types of classification rules supported
in Module QoS 1. IPv4 rules - The ipv4 rules should be used only for IPv4
packets i.e. packets with IPv4 payload (any packets having ether-type value
0x0800). 2. IPv6 rules - The ipv6 rules should be used only for IPv6 packets
i.e. packets with IPv6 payload (any packets having ether-type value 0x86dd)
3. Non IP rules - The non-ip rules should be used for non-ipv4 and non-ipv6
Troubleshooting Module QoS - Error conditions
Troubleshooting August 2013 281
To Next Page
Loading...
