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

VPLS Troubleshooting

This chapter describes common causes of VPLS faults and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

VSI of Martini VPLS Cannot Go Up

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the VSI of Martini VPLS cannot go Up.

Common Causes

This fault is commonly caused by one of the following:

  • Encapsulation types of both ends are different.
  • MTUs of both ends are different.
  • VSI IDs of both ends are different.
  • LDP sessions are not in the Up state.
  • The tunnel policy for selecting a TE tunnel as the public network tunnel is incorrectly configured.
  • The local or remote end of the tunnel does not go Up.
  • The local or remote AC interface does not go Up.
Troubleshooting Flowchart

After Martini VPLS is configured, the VSI cannot go Up.

Figure 4-102 shows the troubleshooting flowchart.

Figure 4-102 Troubleshooting flowchart for the fault that the VSI of Martini VPLS cannot go Up

Troubleshooting Procedure

Context

NOTE:

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

  1. Check that the encapsulation types of both ends are the same.

    <HUAWEI> display vsi name tt
    Vsi                         Mem    PW   Mac      Encap     Mtu   Vsi
    Name                        Disc   Type Learn    Type      Value State
    --------------------------------------------------------------------------
    tt                          static ldp  unqualify vlan     1500   up
    
    • If the encapsulation types of both ends are different, run the encapsulation { ethernet | vlan } command in the VSI view to change the encapsulation type of either end, ensuring that the encapsulation types of both ends are the same.

    • If the encapsulation types of both ends are the same, go to Step 2.

    NOTE:

    The same encapsulation type on both ends is one of the prerequisites for the VSI to go Up.

  2. Check that MTUs of both ends are the same.

    <HUAWEI> display vsi name tt
    Vsi                         Mem    PW   Mac      Encap     Mtu   Vsi
    Name                        Disc   Type Learn    Type      Value State
    --------------------------------------------------------------------------
    tt                          static ldp  unqualify vlan     1500   up
    
    • If the MTUs of both ends are different, run the mtu mtu-value command in the VSI view to change the MTU of either end, ensuring that the MTUs of both ends are the same.

    • If the MTUs of both ends are the same, go to Step 3.

    NOTE:

    The same MTU on both ends is one of the prerequisites for the VSI to go Up.

  3. Check that the VSI IDs or negotiation-VC-IDs of both ends are the same.

    <HUAWEI> display vsi name tt verbose
     ***VSI Name               : tt
        Administrator VSI      : no
        Isolate Spoken         : disable
        VSI Index              : 3
        PW Signaling           : ldp
        Member Discovery Style : static
        Bridge-domain Mode     : disable
        PW MAC Learn Style     : unqualify
        Encapsulation Type     : vlan
        MTU                    : 1500
        Diffserv Mode          : uniform
        Service Class          : --
        Color                  : --
        DomainId               : 255
        Domain Name            :
        Tunnel Policy Name     : p1
        Ignore AcState         : disable
        P2P VSI                : disable
        Multicast Fast Swicth  : disable
        Create Time            : 2 days, 2 hours, 47 minutes, 40 seconds
        VSI State              : up
        Resource Status        : --
    
        VSI ID                 : 101
       *Peer Router ID         : 1.1.1.15
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 187393
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              : 0x0000000001004c4d62
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 6
        NKey                   : 5
        StpEnable              : 0
        PwIndex                : 0
        Control Word           : disable
    
        Interface Name         : GigabitEthernet1/0/0.1
        State                  : up
        Access Port            : false
        Last Up Time           : 2013/08/13 19:25:37
        Total Up Time          : 0 days, 14 hours, 45 minutes, 27 seconds
    
     **PW Information:
    
       *Peer Ip Address        : 1.1.1.15
        PW State               : up
        Local VC Label         : 43128
        Remote VC Label        : 37927
        Remote Control Word    : disable
        PW Type                : label
        Tunnel ID              : 0x0000000001004c4d62
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 6
        NKey                   : 5
        Main PW Token          : 0x0
        Slave PW Token         : 0x0
        Tnl Type               : ldp
        OutInterface           : GigabitEthernet3/0/0
        Backup OutInterface    : --
        Stp Enable             : 0
        Mac Flapping           : 0
        PW Last Up Time        : 2013/08/13 19:26:37
        PW Total Up Time       : 0 days, 14 hours, 44 minutes, 27 seconds
    • If the VSI IDs or negotiation-VC-IDs are different for both ends, run the vsi-id command in the VSI-LDP view to modify the VSI ID of either end, or run the peer peer-address negotiation-VC-ID vc-id command in the VSI-LDP view to modify the negotiation-VC-ID of either end, ensuring that the VSI IDs or negotiation-VC-IDs of both ends are the same.

    • If the VSI IDs or negotiation-VC-IDs of both ends are the same, go to Step 4.

    NOTE:

    The same VSI ID or negotiation-VC-ID on both ends is one of the prerequisites for the VSI to go Up.

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

    Run the display vsi name vsi-name verbose command to check whether the Sessionfield is displayed as Up.

    <HUAWEI> display vsi name tt verbose
     ***VSI Name               : tt
        Administrator VSI      : no
        Isolate Spoken         : disable
        VSI Index              : 3
        PW Signaling           : ldp
        Member Discovery Style : static
        Bridge-domain Mode     : disable
        PW MAC Learn Style     : unqualify
        Encapsulation Type     : vlan
        MTU                    : 1500
        Diffserv Mode          : uniform
        Service Class          : --
        Color                  : --
        DomainId               : 255
        Domain Name            :
        Tunnel Policy Name     : p1
        Ignore AcState         : disable
        P2P VSI                : disable
        Multicast Fast Swicth  : disable
        Create Time            : 2 days, 2 hours, 47 minutes, 40 seconds
        VSI State              : up
        Resource Status        : --
    
        VSI ID                 : 101
       *Peer Router ID         : 1.1.1.15
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 187393
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              : 0x0000000001004c4d62
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 6
        NKey                   : 5
        StpEnable              : 0
        PwIndex                : 0
    
        Interface Name         : GigabitEthernet1/0/0.1
        State                  : up
        Access Port            : false
        Last Up Time           : 2013/08/13 19:25:37
        Total Up Time          : 0 days, 14 hours, 45 minutes, 27 seconds
    
     **PW Information:
    
       *Peer Ip Address        : 1.1.1.15
        PW State               : up
        Local VC Label         : 43128
        Remote VC Label        : 37927
        PW Type                : label
        Tunnel ID              : 0x0000000001004c4d62
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 6
        NKey                   : 5
        Main PW Token          : 0x0
        Slave PW Token         : 0x0
        Tnl Type               : ldp
        OutInterface           : GigabitEthernet3/0/0
        Backup OutInterface    : --
        Stp Enable             : 0
        Mac Flapping           : 0
        PW Last Up Time        : 2013/08/13 19:26:37
        PW Total Up Time       : 0 days, 14 hours, 44 minutes, 27 seconds
    • If the LDP session between both ends does not go Up, refer to the section "LDP Session Goes Down" to locate the fault and ensure that the LDP session goes Up.

    • If the LDP session between both ends is Up, go to Step 5.

    NOTE:

    The Up status of the LDP session is one of the prerequisites for both ends to perform the L2VPN negotiation.

  5. Check whether the VSI has selected a tunnel.

    Run the display vsi name vsi-name verbose command to check the following:

    • Check whether the Tunnel ID field is displayed as null. If so, the VSI does not select a 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, a tunnel policy must be configured. The value of the Tunnel Policy Name field indicates the tunnel policy of the VSI. You can view details of the tunnel policy by running 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 is configured in the tunnel policy view, you also need to configure the mpls te reserved-for-binding command in the tunnel interface view.

    If the tunnel between both ends is not Up, refer to the session "LSP Goes Down" or "TE Tunnel Goes Down" to locate the fault and ensure that the tunnel goes Up. If the tunnel between both ends is Up and the TE interfaces are correctly configured, go to Step 6.

    NOTE:

    The Up status of the tunnel is one of the prerequisites for the VSI to go Up.

  6. Check that the AC interfaces of both ends are in the Up state.

    Run the display vsi name vsi-name verbose command on both ends to check whether the interfaces corresponding to the Interface Name field are in the Up state.

    • If not, refer to the section "Physical Interconnection & Interface Type" to locate the fault and ensure that the AC interfaces go Up.
    • If the AC interfaces on both ends are Up, go to Step 7.
    NOTE:

    The Up status of AC interfaces on both ends is one of the prerequisites for the VSI to go Up.

  7. Collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

Relevant Alarms and Logs

Relevant Alarms

None

Relevant Logs

None

VSI Goes Up Only on One End

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the VSI goes Up only on one end.

Common Causes

The common cause of this fault is that multiple AC interfaces in the Up state are bound to the VSI on the local end but no tunnel is selected.

Troubleshooting Flowchart

After VPLS is configured, the VSI goes Up only on one end.

Figure 4-103 shows the troubleshooting flowchart.

Figure 4-103 Troubleshooting flowchart for the fault that the VSI goes Up only on one end

Troubleshooting Procedure

Context

NOTE:

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

  1. Check that multiple AC interfaces on the local end are bound to the VSI.

    <HUAWEI> display vsi name tt verbose
     ***VSI Name               : tt
        Administrator VSI      : no
        Isolate Spoken         : disable
        VSI Index              : 3
        PW Signaling           : ldp
        Member Discovery Style : static
        Bridge-domain Mode     : disable
        PW MAC Learn Style     : unqualify
        Encapsulation Type     : vlan
        MTU                    : 1500
        Diffserv Mode          : uniform
        Service Class          : --
        Color                  : --
        DomainId               : 255
        Domain Name            :
        Tunnel Policy Name     : p1
        Ignore AcState         : disable
        P2P VSI                : disable
        Multicast Fast Swicth  : disable
        Create Time            : 2 days, 6 hours, 3 minutes, 55 seconds
        VSI State              : up
        Resource Status        : --
    
        VSI ID                 : 101
       *Peer Router ID         : 1.1.1.15
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 187393
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              : 0x0000000001004c4d62
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 6
        NKey                   : 5
        StpEnable              : 0
        PwIndex                : 0
        Control Word           : disable
    
        Interface Name         : GigabitEthernet1/0/0.1
        State                  : up
        Last Up Time           : 2010/02/05 06:36:57
        Total Up Time          : 2 days, 5 hours, 56 minutes, 34 seconds
        Interface Name         : GigabitEthernet1/0/1.1
        State                  : up
        Last Up Time           : 2010/02/07 12:33:13
        Total Up Time          : 0 days, 0 hours, 0 minutes, 18 seconds
    

    If two or more AC interfaces are bound to the VSI, this is a normal situation that the VSI status is Up.

  2. Collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

Relevant Alarms and Logs

Relevant Alarms

None.

Relevant Logs

None.

Trouble Cases

VPLS Services Fail
Fault Symptom

As shown in Figure 4-104, after a Huawei device replaces another vendor's device and functions as PE1, only VPLS services fail.

Figure 4-104 Networking diagram of Martini VPLS

Fault Analysis
NOTE:

After a Huawei device replaces another vendor's device, only VPLS services fail. You can exclude the possibility of a link failure or the failure of another device.

  1. Run the display current-configuration command on PE1 to check whether the configurations are correct and consistent with those of PE2, You can find that configurations of PE1 are correct and consistent with those of PE2.
  2. Run the display vpls connection command on PE1 to check the VCState field. You can find that VCState is Up, indicating that a Layer 2 tunnel is established.
  3. When CE1 pings Server, you can obtain VPLS packet headers in the inbound and outbound directions of PE1 on another device of the MAN.

    A obtained VPLS packet header in the inbound direction of PE1 is shown as follows:

      0018 821D 2010 0014 1CD2 FC06 8847 22C0
      01FE 0019 E019 0D9E 0019 21D5 5FD6 0806
      0001 0800 0604 0002 0019 21D5 5FD6 0303
      0301 0019 E019 0D9E 0303 0302 0000 0000
    

    As indicated by the 0806 field, the obtained VPLS packet header sent from PE2 carries no VLAN tag and is just a common ARP packet. PE1 and PE2, however, are configured with the encapsulation mode of VLAN, causing PE1 to add a VLAN tag to the VPLS packet. After adding a VLAN tag to the VPLS packet, PE1 forwards the packet in the outbound direction.

    A obtained VPLS packet header in the outbound direction of PE1 is shown as follows:

      0019 E019 0D9E 0019 21D5 5FD6 8100 019b
      0800 0604 0002 0019 21D5 5FD6 0303 0301
      0019 E019 0D9E 0303 0302 0000 0000 0000
    

    You can find that PE1 replaces the 0806 field (ARP packet identifier) with the 8100 field (VLAN packet identifier). As a result, VPLS services fail. If the VLAN encapsulation mode of PE2 (another vendor's device) is modified to send VLAN tags, or PE1 and PE2 are configured with the encapsulation mode of Ethernet, the fault can be rectified.

Procedure

  • Solution 1: Modify the VLAN encapsulation mode of another vendor's device to send VLAN tags.
  • Solution 2: Change the encapsulation mode on PE1 and PE2 to Ethernet. The Huawei device (PE1) can be configured as follows:
    1. Run the system-view command to enter the system view.
    2. Run the vsi vsi-name command to enter the VSI view.
    3. Run the encapsulation ethernet command to set the VSI encapsulation mode as Ethernet.

      After the preceding configurations, CEs can ping each other successfully, and VPLS services become normal.

Summary

Why can the Layer 2 tunnel be Up when PE1 has incorrectly parsed packets?

To answer this question, check the configurations of PE2. You can find that the VPLS sending and receiving on PE2 is in hybrid mode. That is, PE2 can process any types of packets; when receiving a VPLS packet carrying a VLAN tag, PE2 removes the VLAN tag and then forwards the VPLS packet. This is the cause for the problem.

As defined by relevant standards, if a packet transmitted on a PW is encapsulated in tagged mode, the packet must carry a VLAN tag.

VSIs Cannot Be Up in LDP Signaling Mode
Fault Symptom
Figure 4-105 Networking diagram of VPLS
NOTE:

In this example, interface 1 and interface 2 are 1/0/0 and GE2/0/0, respectively.



VPLS in LDP signaling mode is configured on both PE1 and PE2. After the configuration, the VSI on both PEs cannot be Up.

Then PE1 initiates CE-Ping to detect the IP address of CE2, but the detection fails. The reason is that the VSIs on PE1 and PE2 cannot go Up.

Fault Analysis
  1. Check the VSI status on PE1 and PE2.

    Run the display vsi verbose command.

    The display on PE1 is as follows.

     ***VSI Name                : v1
        VSI Index               : 0
        PW Signaling            : ldp
        Member Discovery Style  : static
        Bridge-domain Mode      : disable
        PW MAC Learn Style      : unqualify
        Encapsulation Type      : vlan
        MTU                     : 1500
        VSI State               : down
        Resource Status         : --
        VSI ID                  : 1
       *Peer Router ID          : 3.3.3.9
        VC Label                : 17409
        Session                 : up
        Tunnel ID               : 0x0000000001004c4d62
        Interface Name          : GigabitEthernet1/0/0
        State                   : up

    The display on PE2 is as follows.

     ***VSI Name                : v1
        VSI Index               : 0
        PW Signaling            : ldp
        Member Discovery Style  : static
        Bridge-domain Mode      : disable
        PW MAC Learn Style      : unqualify
        Encapsulation Type      : vlan
        MTU                     : 1500
        VSI State               : down
        Resource Status         : Valid
        VSI ID                  : 1
       *peer Router ID          : 2.2.2.9
        VC Label                : 17408
        Session                  : up
        Tunnel ID               : 0x0000000001004c4d61
        Interface Name          : GigabitEthernet2/0/0
        State                    : up

    ACs on both ends are Up. The tunnel on both ends of a PW is in existence, and the tunnel ID is not null.

  2. According to the displayed PW information, you can find that the designated remote LDP peer of the PE2 is not correct. It should be 1.1.1.9 rather than 2.2.2.9. Then modify the peer.

Procedure

  1. Run the display vsi verbose command on PEs.
  2. Check the status of VSI and AC. Find that the VSI is Down, but AC is Up.
  3. Check the status of the PW. Find that the PW cannot be set up.
  4. Check whether the tunnel is available. Find that the tunnel is ready.
  5. Find that the designated remote LDP peer of the PE2 is not correct according to the displayed PW information. The incorrectness makes the PW establishment failed. It should be designated as 1.1.1.9 rather than 2.2.2.9. Modify the peer.
  6. Reconfigure the remote LDP peer of the PE2, which means to designate it as 1.1.1.9. Then the PW is established successfully.
Summary

If the signaling protocol is LDP and the VSI cannot be Up, the errors related to the peer are as follows:

  • The peer is specified incorrectly.

  • The address of the peer is not the peer LSR-ID. The LDP remote session then cannot be established.

  • The LSR-ID of the peer is re-defined. Then the LDP remote session cannot be set up.

If a VSI is Up, there must be at least two ACs are Up, or at least one AC is Up and one PW is Up.

To locate the fault, you can check the status of the AC and PW first.

  • It is simple to let an AC go Up. You must bind the AC with a physical interface, and the line protocol state of the interface must be Up.

  • There are many conditions for a PW to go Up, such as the correct configurations of MTU, encapsulation type, VSI ID, and remote peer. The key is that the local and the remote ends can receive labels from each other.

You can run the display vsi remote ldp command to find which device is faulty according to the label receiving.

Packets Cannot Be Forwarded Successfully Between Two PEs Though VSIs Are Up
Fault Symptom

After configuring VPLS, check the VSI status on PEs. You find that both VSIs are Up, but the packets cannot be forwarded successfully between two PEs.

Fault Analysis
  1. Check whether the PW is available.

    Run the display vsi verbose command to check whether the PW is available.

    If the PW is not available, check whether the delivering status of the PW is up, as shown below:

    • If the status is not up, it shows that the forwarding information is not delivered to the interface board, which leads to the failure of the forwarding.

    • If the status is up but the forwarding still fails, check the operating status of the interface board.

  2. Check the MAC limit.

    If the PW is available, but packets cannot be forwarded between PEs, run the display current-configuration | begin vsi vsi-name command to check the MAC limit. If the number of MAC address entries exceeds the MAC limit, re-configure the MAC limit.

  3. Check the encapsulation types of PEs on both ends.

    If the BGP peer is set up, run the display current-configuration | begin vsi vsi-name command to check the encapsulation types of PEs on both ends. If the types are different, re-configure them to be the same.

    If the fault persists, contact technical support personnel.

Procedure

  1. Run the display vsi command to check whether the status of the PW is up.
  2. Run the display vpls connection command to check whether the PW is available.
  3. If the status is up, check whether the operating status of the interface board is normal.
Summary

The fault occurs when one of the following conditions is met:

  • The PW information is not delivered to the forwarding chip.

  • The number of MAC address entries exceeds the MAC limit.

  • The encapsulation types on PEs of both ends are different.

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13791

Downloads: 257

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