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).
PBB VPLS Troubleshooting

PBB VPLS Troubleshooting

This section describes how to locate and troubleshoot common PBB VPLS faults.

A PBB VPLS VSI Cannot Go Up

This section describes how to troubleshoot the fault that a PBB VPLS I-VSI or B-VSI cannot go Up.

Common Causes

Common causes are as follows:

  • PBB-related parameters are incorrectly configured for the I-VSI on the UPE or NPE.
  • The AC interface bound to the I-VSI on the UPE or NPE is Down.
  • The PWs between B-VSIs on the UPE, SPE, and NPE are Down.
Troubleshooting Flowchart

Figure 4-106 shows the troubleshooting flowchart.

Figure 4-106 Flowchart for troubleshooting the fault that a PBB I-VSI cannot go Up

Troubleshooting Procedure

Context

NOTE:

Save the results of each troubleshooting step. If the fault persists after following this procedure, Huawei will need these results for further troubleshooting.

Procedure

  1. Check that PBB-related parameters, including the I-Tag, service type, B-SMAC address, and B-DMAC address, are set correctly for the I-VSI.

    Run the display this command in the I-VSI view to check PBB-related parameter settings.
    • If PBB-related parameter settings are correct, go to Step 2.

    • If some PBB-related parameters on one end mismatch those on the other end, re-set these parameters.

  2. Check that the AC interface bound to the I-VSI is Up.

    Run the display vsi vsi-name verbose command to check whether the interface identified by the Interface Name field is Up.
    • If the AC interfaces on both ends are Down, refer to Ping Failure to locate the fault and configure the interfaces to go Up.

    • If the AC interfaces on both ends are Up, go to Step 3.

  3. Check that the encapsulation types are the same on both ends.

    • If the PW encapsulation types are different, run the encapsulation { ethernet | vlan } command in the VSI view to change the encapsulation type on one end to be the same as that on the other end.

    • If the encapsulation types are the same, go to Step 4.

  4. Check that MTUs are the same on both ends.

    • If the MTUs are different, run the mtu mtu-value command in the VSI view to change the MTU on one end to be the same as that on the other end.

    • If the MTUs are the same, go to Step 5.

  5. Check that the VSI IDs or negotiation VC IDs are the same on both ends.

    • If the VSI IDs or negotiation VC IDs are different, run the vsi-id vsi-id or peer peer-address negotiation-vc-id vc-id command in the VSI-LDP view to change the VSI ID or negotiation VC ID on one end to be the same as that on the other end.

    • If the VSI IDs or negotiation VC IDs are the same, go to Step 6.

  6. Check that the LDP session between both ends is Up.

    Run the display vsi vsi-name verbose command to check whether the LDP session between both ends is Up.
    • If the LDP session is Down, refer to section "LDP Session Goes Down" to locate the fault and configure the LDP session to go Up.

    • If the LDP session is Up, go to Step 7.

  7. Check that the VSI has selected a tunnel.

    Run the display vsi vsi-name verbose command.

    • Check whether the Tunnel ID field is displayed as 0x0. If the Tunnel ID field is displayed as 0x0, the VSI does not select any tunnel.

    • Check the Tunnel Policy Name field. If this field is not displayed, the VSI selects an LDP LSP or no tunnel policy is configured for the VSI. If the VSI selects an MPLS TE tunnel, the tunnel policy must be configured. The Tunnel Policy Name field indicates the tunnel policy of the VSI. To check tunnel policy details, run the display this command in the corresponding tunnel policy view.

      [HUAWEI-tunnel-policy-p1] display this
      #
      tunnel-policy p1
       tunnel select-seq cr-lsp load-balance-number 1
      #
      
    NOTE:

    If the tunnel binding destination dest-ip-address te { tunnel interface-number } command has been configured for a tunnel policy, be sure to run the mplste reserved-for-binding command on the corresponding interface.

    If the tunnel between both ends is Down, refer to section LDP LSP Down or TE Tunnel Goes Down to locate the fault and configure the tunnel to go Up. If the tunnel between both ends is Up and the TE interface is configured correctly, go to Step 8.

  8. contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.1 hwVplsVcDown
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.2 hwVplsVcUp
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.3 hwVplsVsiDown
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.4 hwVplsVsiUp
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.8 hwVplsVcStatusChange
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.11 hwVplsVcNumberMaxExceed
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.12 hwVplsVcNumberMaxClear
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.13 hwVplsPwRedundancyDegraded
  • L2VPN_1.3.6.1.4.1.2011.5.25.119.1.2.14 hwVplsPwRedundancyDegradedClear
Relevant Logs
  • L2VPN/3/hwVplsVcDown_active
  • L2VPN/3/hwVplsVcDown_clear
  • L2VPN/3/hwVplsVsiDown_active
  • L2VPN/3/hwVplsVsiDown_clear
  • L2VPN/4/hwVplsVcStatusChangeNotrap
  • L2VPN/3/hwVplsVcNumberMaxExceed
  • L2VPN/3/hwVplsVcNumberMaxClear
  • L2VPN/2/hwVplsPwRedundancyDegraded_active
  • L2VPN/2/hwVplsPwRedundancyDegraded_clear
Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 14592

Downloads: 258

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