Table of Contents
Advertisement
• QoS feature is enabled but packets are classified into interface default class as shown in
Scenario 2. possible cause for this is the packet may not reach the leaf node. Follow the
steps given below.
- the MF tree configured. you can use 'show qos chassis policy-map
[policy-map name] detail' to get the details about the policy-map.
- Ensure that packets are getting classified at the parent node. Then only it will reach
the leaf node. For this check care fully the key values assigned the parents are
appropriate.
- If problem still persist then capture the packet by using "tcp dump" or Ethereal or
any of the available packet capturing tools. Capture the packet and analyze it with
the MF tree configured.
Not all the packets are classified
Symptom: The user can perceive less number of packets are getting classified than what he
sent/incoming/outgoing packets.
Problem description: Sometimes the user may perceive not all packets are getting classified.
He may find some of the packets which he sent/incoming/outgoing is classified under interface
default class.
Prerequisite: Policy-map should be created and attached to an interface successfully.
Troubleshooting tips: Create a class-default class for each classification type. Then all the
packets which aren't classified under the given classes won't go to interface default rather it
goes to class-default.
Troubleshooting
Chassis QoS troubleshooting
August 2013
243
Advertisement
Table of Contents
Troubleshooting
