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).
HQoS Troubleshooting

HQoS Troubleshooting

This chapter describes common causes of HQoS faults and provides troubleshooting flowcharts and procedures, alarms, and logs to help identify and rectify these faults.

Common Causes

This section describes the common causes of an HQoS fault.

Common causes are as follows:

  • Small traffic volume due to load balancing
  • Excess protocol packets
  • Excess duplicated broadcast packets
  • Invalid HQoS configuration on the public network side of the PW

Troubleshooting Flowchart

This section describes the HQoS troubleshooting flowchart.

Typical networking of HQoS is shown in Figure 4-120 and Figure 4-121. HQoS troubleshooting in this chapter is described based on these two networking figures.

  • HQoS on the User-Side Primary Interface of the PE

    Figure 4-120 Networking for HQoS configuration on the primary interface

    In general, HQoS is configured on the access-layer ME device to guarantee bandwidth and limit traffic of users or user groups.

    In this networking, the configuration roadmap of HQoS is as follows:

    • Configure the WRED parameters for each CoS.

    • Queue scheduling algorithm and parameters for each flow queue.

    • Configure mapping of the CoS for flow queues.

    • Configure the shaping value for user group queues.

    • Configure SQ on the interface.

    • Configure CQ on the interface.

  • HQoS on the User-Side Sub-interface of the PE

    Figure 4-121 Networking for HQoS configuration on the sub-interface

    In this networking, the client gateways connect to the sub-interface of the PE by means of VLL, VPLS or L3VPN. HQoS is configured on the access side of the PE to guarantee the bandwidth and limit traffic of users or user groups.

    The configuration roadmap is similar to that on the primary interface.

In the network shown in Figure 4-121, the traffic limit for the SQ is incorrect on one ME device. The troubleshooting flowchart is shown in Figure 4-122.

Figure 4-122 Flowchart for troubleshooting HQoS

Troubleshooting Procedure

This section describes the HQoS troubleshooting procedure.

Procedure

  1. Compare the actual traffic that passes through the ME device with the configuration.

    If they are inconsistent, do as follows:

    1. If the volume of traffic is smaller than the configuration, check that the interface where HQoS is configured is an Eth-Trunk interface.
    2. If the interface is an Eth-Trunk interface, check whether packet-based load balancing is configured on that Eth-Trunk interface.
      [~HUAWEI] interface eth-trunk 5
      [~HUAWEI-Eth-Trunk55] display this
      #
      interface Eth-Trunk55
       load-balance packet-all
      # 
    3. If packet-based load balancing is configured on the Eth-Trunk interface, disable the load balancing. Then the problem can be solved.
    4. If the volume of traffic is larger than the configuration and the interface is not an Eth-Trunk interface, go to Step 3.
    5. If the volume of traffic is too large, go to Step 2.

  2. Check that HQoS is configured on the inbound or outbound interface.

    • If HQoS is configured on the inbound interface, go to Step 3.

    • If HQoS is configured on the outbound interface, go to Step 4.

  3. Check that there are too many protocol packets.

    • When HQoS is configured on the inbound interface, SQ limits rate of all traffic including protocol packets. In this case, if too many protocol packets go into the ME device, the bandwidth allocated for protocol packets is wasted. Therefore, actual traffic volume is too small.

    • If too few protocol packets go into the ME device, go to Step 6.

  4. Check that there are multicast or unknown unicast packets.

    • If there are multicast or unknown unicast packets on the outbound interface, the volume of traffic that passes the ME device will be too large.

    • If there are no multicast or unknown unicast packets, go to Step 5.

  5. Check that the outbound interface is connected to the MPLS backbone network.

    • If the outbound interface is connected to the MPLS backbone network, the volume of traffic that passes the ME device will be too large because HQoS does not take effect on the backbone network side.

    • If the outbound interface is not connected to the MPLS backbone network, go to Step 6.

  6. Contact Huawei and provide the following information:

    • Results of this troubleshooting procedure

    • Configuration, log, and alarm files

Relevant Alarms and Logs

This section describes relevant HQoS alarms and logs.

Relevant Alarms

None.

Relevant Logs

None.

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 14288

Downloads: 257

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