9.3.2 Interface-based Traffic Policing Results Are Incorrect
This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting
procedure to use when interface-based traffic policing results are incorrect.
Common Causes
Interface-based traffic policing results are incorrect in the following scenarios:
l
Traffic policing fails to take effect.
l
The CAR parameter values are incorrect.
This fault is commonly caused by one of the following:
l
The
qos car
command is not used on the interface.
l
Traffic policing is applied to an incorrect direction or CAR parameter values are incorrect.
l
Flow-based traffic policing and the
qos car
command are used in the same direction and
the CIR value for flow-based traffic policing is smaller than that for interface-based traffic
policing.
Troubleshooting Flowchart
If interface-based traffic policing fails to take effect, see
. If the CAR parameter values
for interface-based traffic policing are incorrect, see
Figure 9-7
Troubleshooting flowchart for ineffective interface-based traffic policing
Interface-based
traffic policing rate is
incorrect
Correctly configure
interface-based
traffic policing
Is fault rectified?
No
Yes
No
Seek technical
support
Is interface-based
traffic policing set?
Do statistics
exist on interface?
No
End
Yes
Huawei AR2200-S Series Enterprise Routers
Troubleshooting
9 QoS
Issue 01 (2012-01-06)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
248