Huawei-Troubleshooting - QoS

HUAWEI NetEngine5000E Core Router
V800R002C01
Troubleshooting - QoS
Issue 01
Date 2011-10-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2011-10-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Troubleshooting - QoS About This Document
About This Document
Intended Audience
This document describes the troubleshooting workflow and methods for HUAWEI
NetEngine5000E. This document describes the troubleshooting of HUAWEI
NetEngine5000E with various services, including information collection methods, common
processing flows, common troubleshooting methods, and troubleshooting cases.
This document is intended for:
l System maintenance engineers

l Commissioning engineers
l Network monitoring engineers
Related Versions (Optional)

The following table lists the product versions related to this document.
Product Name Version
HUAWEI NetEngine5000E V800R002C01

Core Router
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Alerts you to a high risk hazard that could, if not avoided,

result in serious injury or death.
Alerts you to a medium or low risk hazard that could, if

not avoided, result in moderate or minor injury.
Issue 01 (2011-10-15) Huawei Proprietary and Confidential ii

Troubleshooting - QoS About This Document
Symbol Description
Alerts you to a potentially hazardous situation that could,

if not avoided, result in equipment damage, data loss,
performance deterioration, or unanticipated results.
Provides a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or

supplement important points in the main text.
Command Conventions (Optional)

The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 01 (2011-10-15)

The initial commercial release.
Issue 01 (2011-10-15) Huawei Proprietary and Confidential iii

Troubleshooting - QoS Contents
Contents
About This Document.....................................................................................................................ii

1 Troubleshooting for 802.1p-Based Simple Traffic Classification........................................1
1.1 Common Causes.................................................................................................................................................2
1.2 Troubleshooting Flowchart.................................................................................................................................2
1.3 Troubleshooting Procedure.................................................................................................................................3
1.4 Relevant Alarms and Logs.................................................................................................................................4
2 Troubleshooting for Complex Traffic Classification.............................................................5

2.1 Common Causes.................................................................................................................................................6
2.2 Troubleshooting Flowchart.................................................................................................................................6
2.3 Troubleshooting Procedure.................................................................................................................................7
2.4 Relevant Alarms and Logs.................................................................................................................................8
3 Troubleshooting for Traffic Classification-Based Queue Scheduling.............................10

3.1 Common Causes...............................................................................................................................................11
3.2 Troubleshooting Flowchart...............................................................................................................................11
3.3 Troubleshooting Procedure...............................................................................................................................12
3.4 Relevant Alarms and Logs...............................................................................................................................13
4 QPPB Troubleshooting...............................................................................................................14
4.1 Common Causes...............................................................................................................................................15
4.2 Troubleshooting Flowchart...............................................................................................................................15
4.3 Troubleshooting Procedure...............................................................................................................................16
4.4 Relevant Alarms and Logs...............................................................................................................................17
Issue 01 (2011-10-15) Huawei Proprietary and Confidential iv

HUAWEI NetEngine5000E Core Router 1 Troubleshooting for 802.1p-Based Simple Traffic
Troubleshooting - QoS Classification
1 Troubleshooting for 802.1p-Based Simple

Traffic Classification
About This Chapter
This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting
procedure for the fault that the 802.1p value of received packets is incorrect.
1.1 Common Causes
1.2 Troubleshooting Flowchart
1.3 Troubleshooting Procedure
1.4 Relevant Alarms and Logs
Issue 01 (2011-10-15) Huawei Proprietary and Confidential 1

1.1 Common Causes

This fault is commonly caused by one of the following:
l The priority mapping in the domain of the inbound interface is incorrect.
l The priority mapping in the domain of the outbound interface is incorrect.
l The inbound or outbound interface is not a sub-interface.
l The inbound or outbound interface is not enabled to trust 802.1p values of packets.

Figure 1-1 shows the typical networking of simple traffic classification.
Figure 1-1 Networking of 802.1p-based simple traffic classification
Vlan-type dotlq 1
GE1/0/1 GE1/0/1.1 GE1/0/1
GE8/0/1 GE3/0/1.1
RouterA RouterB Vlan-type dotlq 1 RouterC RouterD
On the network shown in Figure 1-1, Router A sends an IP packet with the DSCP value of 10.
The IP packet reaches GE 3/0/1.1 on Router C through Router B, with the DSCP value being
mapped to an incorrect 802.1p value.
Figure 1-2 shows the troubleshooting flowchart.

Figure 1-2 Troubleshooting flowchart for 802.1p-based simple traffic classification
The 8021P value of

the packet received by
RouterC is incorrect
Is the
Modify the configuration
mapping used No on the inbound
on the inbound interface and adopt
interface
correct? correct mapping
YES
Is the Modify the configuration

mapping used No on the outbound
on the outbound
interface interface and adopt
correct? correct mapping
YES
Is the
inbound/outbound No Configure the sub-
interface the sub- interface
interface?
YES
Is 8021P
enabled on the No Configure trust 8021P
inbound/outbound on the sub-interface
interface?
YES
No
Seek Huawei Is the fault
technical support removed?
YES
End

NOTE
After commands are configured to troubleshoot faults, pay attention to the configuration validation mode
to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the
immediate validation mode.
l In immediate validation mode, configurations take effect after commands are input and the Enter key
is pressed.
l In two-phase validation mode, after commands are configured, the commit command needs to be run
to commit the configurations.
Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct
the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure
Step 1 Check that priority mapping on the interface sending the packet, GE 8/0/1 on Router B, is correct.
Run the display this command on GE 8/0/1 of Router B to check the configuration of the trust
upstream ds-domain-name command.
l If non-default domain is not configured in the trust upstream ds-domain-name command,
run the display diffserv domain ds-domain-name command in any view to check whether
the priority mapping in the domain is correct.
l If the trust upstream default command is configured, run the display diffserv domain
default command in any view to check whether the priority mapping in the default domain
is correct. If not, re-configure priority mapping in the domain.
Step 2 Check that priority mapping on the interface receiving the packet, GE 3/0/1.1 on Router C, is
correct.
Run the display this command on GE 3/0/1.1 of Router C to check the configuration of the
trust upstream ds-domain-name.
l If non-default domain is not configured in the trust upstream ds-domain-name command,
run the display diffserv domain ds-domain-name command in any view to check whether
the priority mapping in the domain is correct.
l If the trust upstream default command is configured, run the display diffserv domain
default command in any view to check whether the priority mapping in the default domain
is correct. If not, re-configure priority mapping in the domain.
Step 3 Check that the interface receiving the packet, GE 3/0/1.1 on Router C, is enabled to trust 802.1p
values of packets.
Run the display this command on GE 3/0/1.1 of Router C to check whether the trust 8021p
command is configured. If not, configure this command.
----End

None.

Troubleshooting - QoS 2 Troubleshooting for Complex Traffic Classification
2 Troubleshooting for Complex Traffic

Classification
About This Chapter
procedure for the fault that a traffic policy is incorrectly applied for complex traffic classification.
2.1 Common Causes

2.1 Common Causes

l No packet is received on the inbound interface.
l Traffic classification is incorrectly implemented on the inbound interface.
l The traffic behavior is incorrect.
l The traffic policy is incorrect.
l The traffic policy is incorrectly applied.

Figure 2-1 shows the typical networking of complex traffic classification.
Figure 2-1 Networking of complex traffic classification
mac address
1-1-1
GE1/0/1.1 GE8/0/1.1
RouterA RouterB
On the network shown in Figure 2-1, a traffic policy is configured on Router B to discard VLAN
packets with the 802.1p value of 3 or MAC address of 1-1-1. After Router B receives this type
of VLAN packet, Router B does not discard the VLAN packet, not following the traffic policy.

Figure 2-2 Troubleshooting flowchart for complex traffic classification
A fault occurs in
traffic policy
Check Check the status of

whether the No the interface and
inbound interface
isolate the fault on
receives the the link layer
packet
Yes
Check
whether the Re-configure the
traffic lassification No
rule of the inbound traffic classification
interface is rule
correct
Yes
Check
whether the traffic No Re-configure the
behavior is traffic behavior
correct
Yes
Check
whether the traffic No Re-configure the
policy is traffic policy
correct
Yes
Check
whether the traffic No Apply the traffic
policy is applied policy correctly
correctly
Yes
No
Seek Huawei Is the fault
Yes
End

NOTE
is pressed.
Procedure
Step 1 Check that the devices are connected.
Run the display interface interface-type interface- number command in any view to check
whether the packet is received on the inbound interface. If the packet is not received on the
inbound interface, run the display ip interface brief command to check the status of interfaces.
Up indicates that the interface is available, whereas Down indicates that the interface is
unavailable. If the interface is Down, check whether the link is connected properly or whether
the shutdown command is used on the interface.
Step 2 Check that traffic classification is correctly implemented.

1. Run the display acl command in any view to check whether the rule deny source-mac
command is configured to define a matching rule to filter out packets with specific source
MAC addresses.
2. Run the display traffic classifier user-defined command in any view to check whether a
traffic classifier has been defined and whether the following if-match clauses have been
configured in the traffic classifier view.
l if-match 8021p 3
l if-match acl acl-number. acl-number specifies the number of the ACL that is used to
filter out packets with specific source MAC addresses.
Step 3 Check that the traffic behavior is correct.
Run the display traffic behavior user-defined command in any view to check whether a traffic
behavior has been defined and whether the action deny is configured in the traffic behavior view.
Step 4 Check that the traffic policy is correct.
Run the display traffic policy user-defined command in any view to check whether a traffic
policy has been defined and whether a correct traffic behavior has been defined in the traffic
policy.
Step 5 Check that the traffic policy is correctly applied to GE 8/0/1.1.
Run the display this command on GE 8/0/1.1 of Router B to check whether the vlan-type dot1q
3 and traffic-policy inbound link-layer commands have been configured.
----End

None.

HUAWEI NetEngine5000E Core Router 3 Troubleshooting for Traffic Classification-Based Queue
Troubleshooting - QoS Scheduling
3 Troubleshooting for Traffic Classification-

Based Queue Scheduling
About This Chapter
procedure for the fault that queue scheduling is incorrectly implemented.
3.1 Common Causes

3.1 Common Causes

l The devices are not connected.
l Simple traffic classification is not configured on the inbound interface.
l Simple traffic classification is not configured on the outbound interface.
l Queue scheduling is incorrectly configured.

Figure 3-1 shows the typical networking of traffic classification-based queue scheduling.
Figure 3-1 Networking of traffic classification-based queue scheduling
GE1/0/0 GE1/0/1
GE8/0/1 GE8/0/1
RouterA RouterB RouterC
On the network shown in Figure 3-1, Router A sends the EF traffic at 700 Mbit/s, AF1 traffic
at 100 Mbit/s, AF2 traffic at 200 Mbit/s, and BE traffic at 300 Mbit/s. The bandwidth of GE
1/0/1 on Router B is 1000 Mbit/s. Queue scheduling is configured to prevent traffic congestion
by allowing all EF traffic to be sent from GE 1/0/1 on Router B and AF1, AF2, and BE traffic
to be transmitted at 50 Mbit/s, 100 Mbit/s, and 150 Mbit/s respectively. On Router B, however,
traffic is not transmitted as defined in queue scheduling.

Figure 3-2 Troubleshooting flowchart for traffic classification-based queue scheduling
A fault occurs
Check
No Isolate the
the network
network fault
connectivity
Yes
Check
whether simple No Configure simple traffic
traffic classification is classification on the
configured on the
inbound inbound interface
interface
Yes
Check
whether simple Configure simple traffic
traffic classification is No
configured on the classification on the
outbound outbound interface
interface
Yes
Check
whether queue No Configure queue
scheduling is
configured scheduling correctly
correctly
Yes
Seek Huawei No Is the fault

Yes
End

NOTE
is pressed.

Procedure
Run the display ip interface brief command to check the status of each interface. Up indicates
that the interface is available, whereas Down indicates that the interface is unavailable. If the
interface is Down, check whether the link is connected properly or whether the shutdown
command is used on the interface.
Step 2 Check that simple traffic classification is configured on the inbound interface.
Run the display this command on GE 8/0/1 of Router B to check whether the trust upstream
command is run to configure simple traffic classification.
Step 3 Check that simple traffic classification is configured on the outbound interface.
Run the display this command on GE 1/0/1 of Router B to check whether the trust upstream
command is run to configure simple traffic classification.
Step 4 Check that priority mapping in the DS domain is correct.
Run the display diffserv domain command in any view on Router B to check whether priority
mapping in the DS domain is correct.
Step 5 Check that queue scheduling is correctly configured.
Run the display this command on GE 1/0/1 of Router B to check whether queue scheduling is
correctly configured or whether the qos queue ef, qos queue af1, qos queue af2, and qos queue
be commands are configured, and whether traffic shaping parameters are correctly configured
for traffic with different CoSs.
----End

None.

Troubleshooting - QoS 4 QPPB Troubleshooting
4 QPPB Troubleshooting
About This Chapter
procedure for the QPPB fault.
4.1 Common Causes

4.1 Common Causes

l The devices are not connected.
l The route receiver does not receive BGP routes.
l No QoS parameters are delivered in the routing table.
l No QPPB policies are applied to the interface.
l The QPPB policy is incorrectly configured.

Figure 4-1 shows the typical networking of QPPB.
Figure 4-1 Networking of QPPB

GE1/0/0 GE1/0/0
Router A Router B
On the network shown in Figure 4-1, the BGP peer relationship is established between
Router A and Router B. Router B functions as the BGP route sender, and Router A functions as
the BGP route receiver. Router B sends BGP routes carrying the community attributes to
Router A. After receiving the BGP routes, Router A matches the routes with the community list
and associates QoS policy IDs with QoS behaviors for the routes. The QPPB policy configured
on Router A, however, is invalid.

Figure 4-2 Troubleshooting flowchart for QPPB
A QPPB fault occurs
Check that devices No Check the status of

are connected interfaces and links
Yes
Check that BGP No Check the BGP

routes are received configuration
Yes
Check that QoS No Check the routing

parameters are recorded policy configuration
in the routing table
Yes
Check that the No

Apply the QPPB
QPPB policy is policy to the interface
correctly applied
Yes
No
Seek Huawei Is the fault rectified?
technical support
Yes
End

NOTE
is pressed.
Procedure
Run the display interface interface-type interface- number command in any view to check
whether the packet is received on the inbound interface. If the packet is not received on the
inbound interface, run the display ip interface brief command to check the status of interfaces.
Up indicates that the interface is available, whereas Down indicates that the interface is
unavailable. If the interface is Down, check whether the link is connected properly or whether
the shutdown command is used on the interface.
Step 2 Check that BGP routes are received.
Run the display ip routing-table or display ip routing-table statistics command in any view
to check whether BGP routes are received. If no BGP routes are received, run the display bgp
peer command to check whether the State field value is Established. If the State field value is
Established, the BGP peer relationship is established.
Step 3 Check that QoS parameters are correctly recorded in the routing table.
Run the display ip routing-table verbose command in any view to check whether the QoSInfo
field value is 0. The value 0 indicates that no QoS parameters are delivered.
Step 4 Check that the QPPB policy is applied to the interface.
Run the display this command on the interface to check whether a QPPB policy is applied. The
following QPPB policies can be applied to an interface:
qppb local-policy-name destination inbound
qppb local-policy-name source inbound
qppb local-policy-name outbound
qppb ip-precedence destination
qppb ip-precedence source
qppb qos-local-id destination inbound
qppb qos-local-id source inbound
Step 5 Check that the QPPB policy is correctly configured.

For detailed configuration of QPPB, refer to the HUAWEI NetEngine5000E Core Router
Configuration Guide - QoS.
----End

None.


Huawei-Troubleshooting - QoS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei-Troubleshooting - QoS

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine5000E Core Router

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2011-10-15) Huawei Proprietary and Confidential i

About This Document

This document is intended for:

l System maintenance engineers

Related Versions (Optional)

Product Name Version

HUAWEI NetEngine5000E V800R002C01

Alerts you to a high risk hazard that could, if not avoided,

Alerts you to a medium or low risk hazard that could, if

Issue 01 (2011-10-15) Huawei Proprietary and Confidential ii

Alerts you to a potentially hazardous situation that could,

Provides a tip that may help you solve a problem or save

Provides additional information to emphasize or

Command Conventions (Optional)

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

# A line starting with the # sign is comments.

Changes in Issue 01 (2011-10-15)

Issue 01 (2011-10-15) Huawei Proprietary and Confidential iii

About This Document.....................................................................................................................ii

2 Troubleshooting for Complex Traffic Classification.............................................................5

3 Troubleshooting for Traffic Classification-Based Queue Scheduling.............................10

Issue 01 (2011-10-15) Huawei Proprietary and Confidential iv

1 Troubleshooting for 802.1p-Based Simple

About This Chapter

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 1

1.1 Common Causes

1.2 Troubleshooting Flowchart

Figure 1-1 Networking of 802.1p-based simple traffic classification

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 2

Figure 1-2 Troubleshooting flowchart for 802.1p-based simple traffic classification

The 8021P value of

Is the Modify the configuration

1.3 Troubleshooting Procedure

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 3

1.4 Relevant Alarms and Logs

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 4

2 Troubleshooting for Complex Traffic

About This Chapter

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 5

2.1 Common Causes

2.2 Troubleshooting Flowchart

Figure 2-1 Networking of complex traffic classification

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 6

Figure 2-2 Troubleshooting flowchart for complex traffic classification

Check Check the status of

2.3 Troubleshooting Procedure

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 7

Step 2 Check that traffic classification is correctly implemented.

Step 3 Check that the traffic behavior is correct.

Step 4 Check that the traffic policy is correct.

Step 5 Check that the traffic policy is correctly applied to GE 8/0/1.1.

2.4 Relevant Alarms and Logs

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 8

Issue 01 (2011-10-15) Huawei Proprietary and Confidential 9