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

QPPB Troubleshooting

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

Common Causes

This section describes common causes for QPPB.

Common causes are as follows:

  • The devices are not connected.

  • The route receiver does not receive BGP routes.

  • No QoS parameters are delivered in the routing table.

  • No QPPB policies are applied to the interface.

  • The QPPB policy is incorrectly configured.

Troubleshooting Flowchart

This section describes the troubleshooting flowchart for QPPB.

Figure 4-118 shows a typical networking scheme for QPPB.

Figure 4-118 Networking for QPPB

NOTE:

Interface 1 in this example is GE 1/0/0.

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

Figure 4-119 shows the troubleshooting flowchart.

Figure 4-119 Flowchart for troubleshooting QPPB

Troubleshooting Procedure

This section describes the troubleshooting procedure for QPPB.

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 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, run the display ip interface brief command to check the status of the 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 the shutdown command is used on the interface.

  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 it is, the BGP peer relationship is established.

  3. Check that the 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.

  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
    

  5. Check that the QPPB policy is correctly configured.

    For detailed configuration of QPPB, see the HUAWEI ME60 Multiservice Control Gateway Configuration Guide - QoS.

Relevant Alarms and Logs

This section describes relevant alarms and logs for QPPB.

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13881

Downloads: 257

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