No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Traffic-Classification-Based Queue Scheduling Troubleshooting

Traffic-Classification-Based Queue Scheduling Troubleshooting

This chapter describes common causes of traffic-classification-based queue scheduling faults and provides troubleshooting flowcharts and procedures, alarms, and logs to help identify and rectify these faults.

Common Causes

This section describes common causes and logs for a traffic classification-based queue scheduling fault.

Common causes are as follows:

  • The devices are not connected.

  • Simple traffic classification is not configured on the inbound interface.

  • Simple traffic classification is not configured on the outbound interface.

  • Queue scheduling is incorrectly configured.

Troubleshooting Flowchart

This section describes the troubleshooting flowchart for traffic-classification-based queue scheduling.

Figure 4-116 shows a typical networking scheme for traffic-classification-based queue scheduling.

Figure 4-116 Networking of traffic-classification-based queue scheduling

NOTE:

Interfaces 1 through 3 are GE 1/0/0, GE 6/0/2, GE 1/0/1, respectively.

On the network shown in Figure 4-116, Device 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 Device 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 Device B and AF1, AF2, and BE traffic to be transmitted at 50 Mbit/s, 100 Mbit/s, and 150 Mbit/s, respectively. However, on Device B, traffic is not transmitted as defined in queue scheduling.

Figure 4-117 shows the troubleshooting flowchart.

Figure 4-117 Flowchart for troubleshooting a traffic-classification-based queue scheduling fault

Troubleshooting Procedure

This section describes the troubleshooting procedure for traffic classification-based queue scheduling.

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that the devices are connected.

    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 the shutdown command is used on the interface.

  2. Check that BA classification is configured on the inbound interface.

    Run the display this command on GE 6/0/2 of ME device B to check whether the trust upstream command has been run to configure BA classification.

  3. Check that BA classification is configured on the outbound interface.

    Run the display this command on GE 1/0/1 of ME device B to check whether the trust upstream command has been run to configure BA classification.

  4. Check that the priority mapping in the DS domain is correct.

    Run the display diffserv domain command in any view on ME device B to check whether the priority mapping in the DS domain is correct.

Relevant Alarms and Logs

This section describes relevant alarms and logs for traffic-classification-based queue scheduling.

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 14121

Downloads: 257

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next