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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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

Troubleshooting Procedure

Context

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the two-phase validation mode.

  • In immediate validation mode, the configuration takes effect immediately after you run a command and press Enter.
  • In two-phase validation mode, you must run the commit command after commands are configured to commit the configuration.

Save the results of each troubleshooting step, so you can provide related information to Huawei technical support if your troubleshooting fails.

Procedure

  1. Check the status of interfaces on MSTP devices.

    Check the role of each MSTP-enabled port in each instance.

    On the network shown in Figure 13-4, there is only one MSTP ring, which means that each instance can have only one blocked interface. Run the display stp brief command on each device to check whether the status of each port is normal.

    Run the display stp brief command in any view to check the MSTP status on Switch1. As shown in Figure 13-4, in instances 0 and 1, Switch1 functions as a root bridge, and all ports on Switch1 are designated ports. In instance 2, one port on Switch1 is a designated port, and the other port is a root port. Both ports are in the Forwarding state.

    [Switch1] display stp brief
     MSTID  Port                        Role  STP State     Protection  Cost       Edged                                                
         0  10GE1/0/1                   DESI  forwarding    none        2          disable                                              
         0  10GE1/0/2                   DESI  forwarding    none        2          disable                                              
         1  10GE1/0/1                   DESI  forwarding    none        2          disable                                              
         1  10GE1/0/2                   DESI  forwarding    none        2          disable                                              
         2  10GE1/0/1                   ROOT  forwarding    none        2          disable                                               
         2  10GE1/0/2                   DESI  forwarding    none        2          disable                                               
    

    Run the display stp brief command in any view to check the MSTP status on Switch2. As shown in Figure 13-4, in instances 2, Switch2 functions as a root bridge, and all ports on Switch2 are designated ports. In other instances, one port on Switch2 is a designated port, and the other port is a root port. Both of them are in the Forwarding state.

    [Switch2] display stp brief
     MSTID  Port                        Role  STP State     Protection  Cost       Edged                                                
         0  10GE1/0/1                   ROOT  forwarding    none        2          disable                                              
         0  10GE1/0/2                   DESI  forwarding    none        2          disable                                              
         1  10GE1/0/1                   ROOT  forwarding    none        2          disable                                              
         1  10GE1/0/2                   DESI  forwarding    none        2          disable                                              
         2  10GE1/0/1                   DESI  forwarding    none        2          disable                                               
         2  10GE1/0/2                   DESI  forwarding    none        2          disable                                               
    

    Run the display stp brief command in any view to check the MSTP status on Switch3. As shown in Figure 13-4, in instance 2, one port on Switch3 is an Alternate port and the other port is a root port. The Alternate port is blocked and in the Discarding state. In other instances, one port on Swicth3 is a designated port and the other port is a root port. Both of them are in the Forwarding state.

    [Switch3] display stp brief
     MSTID  Port                        Role  STP State     Protection  Cost       Edged                                                
         0  10GE1/0/1                   DEST  forwarding    none        2          disable                                              
         0  10GE1/0/2                   ROOT  forwarding    none        2          disable                                              
         1  10GE1/0/1                   DEST  forwarding    none        2          disable                                              
         1  10GE1/0/2                   ROOT  forwarding    none        2          disable                                              
         2  10GE1/0/1                   ALTE  discarding    none        2          disable                                               
         2  10GE1/0/2                   ROOT  forwarding    none        2          disable                                               
    

    Run the display stp brief command in any view to check the MSTP status on Switch4. As shown in Figure 13-4, in instance 0, one port on Switch4 is an Alternate port, and the other port is a root port. The Alternate port is blocked and in the Discarding state. In instance 2, one port on Switch4 is a designated port, and the other port is a root port. Both of them are in the Forwarding state.

    [Switch4] display stp brief
     MSTID  Port                        Role  STP State     Protection  Cost       Edged
       0    10GE1/0/1                   ALTE  discarding    none        2          disable
       0    10GE1/0/2                   ROOT  forwarding    none        2          disable
       1    10GE1/0/1                   ALTE  discarding    none        2          disable
       1    10GE1/0/2                   ROOT  forwarding    none        2          disable
       2    10GE1/0/1                   DESI  forwarding    none        2          disable
       2    10GE1/0/2                   ROOT  forwarding    none        2          disable
    

    • On the network shown in Figure 13-4, each instance has only one port in the Discarding state and the other port is in the Forwarding state. If several ports are in the Discarding state, an MSTP calculation error occurs. To solve this problem, go to Step 5.

    • If the MSTP status is correct, go to Step 2.

  2. Check that the MSTP configuration is correct.

    Run the display stp region-configuration command to view mappings between VLANs and instances. The following uses Switch1 as an example.

    [Switch1] display stp region-configuration
    Oper configuration
       Format selector    :0
       Region name        :306b20792201
       Revision level     :0
    
       Instance   VLANs Mapped
          0       21 to 4094
          1       1 to 10
          2       11 to 20

    • Check whether mappings between VLANs and instances are correct. If a mapping is incorrect, run the instance command to map the VLAN to a specified spanning tree instance.

    Run the display current-configuration command to view the MSTP configuration in the configuration file of the device.

    • Check whether MSTP is disabled on the interfaces that connect to user terminals or the interfaces are configured as edge interfaces.
    • Check whether interfaces are added to VLANs correctly. For VLAN configurations, see "VLAN Configuration" in the Configuration Guide - LAN.
    • If the MSTP configuration is correct, go to Step 3.
  3. Check that no MSTP recalculation was performed.

    Run the display stp command in any view to check whether the device received TC messages. The following uses Switch1 as an example.

    [Switch1]display stp
    -------[CIST Global Info][Mode MSTP]-------
    Config Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
    CIST Bridge         :32768.00e0-fc0e-a421
    Active Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
    CIST Root/ERPC      :32768.00e0-fc0e-a421 / 0 (This bridge is the root)
    CIST RegRoot/IRPC   :32768.00e0-fc0e-a421 / 0 (This bridge is the root)
    CIST RootPortId     :0.0
    BPDU-Protection     :Disabled
    STP Converge Mode   :Normal
    Share region-configuration :Enabled
    Time since last TC  :0 days 23h:9m:30s
    Number of TC        :1
    Last TC occurred    :10GE1/0/1

    • If the values of TC or TCN received and TC count per hello in the command output increase, the device has received TC messages, and the network topology has changed, go to Step 4.

      If a multi-process has been created on the device, and TC notification was configured in the multi-process, when the topology of the multi-process changes, a TC message is sent to process 0 to instruct devices in process 0 to refresh their MAC and ARP address tables. Then, devices on the network can re-select links to forward traffic, ensuring non-stop traffic.

    • If the values of the TC or TCN received and TC count per hello in the command output are 0s, the device does not receive any TC message. Contact technical support personnel.

  4. Check that no interface on the device alternates between Up and Down.

    View the log message STANDARD/2/linkdown_active to check whether an MSTP-enabled port alternates between Up and Down.

    • If an MSTP-enabled interface alternates between Up and Down, the interface flaps. If a physical interface frequently alternates between Up and Down, the MSTP status of the device on the network becomes unsteady. As a result, a large number of TC messages are generated, ARP entries and MAC entries are frequently deleted, and services are interrupted. Run the shutdown command on the flapping interface. If services are not restored after the interface is shut down, go to Step 5.

    • If no interface flaps, go to Step 5.

  5. Check that the MSTP convergence mode is Normal.

    Run the display stp command in any view to check the MSTP convergence mode of the device.

    [Switch1] display stp
    
    -------[CIST Global Info][Mode MSTP]-------
    CIST Bridge         :32768.00e0-fc0e-a421
    Config Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
    Active Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
    CIST Root/ERPC      :32768.00e0-fc0e-a421 / 0 (This bridge is the root)
    CIST RegRoot/IRPC   :32768.00e0-fc0e-a421 / 0 (This bridge is the root)
    CIST RootPortId     :0.0
    BPDU-Protection     :Disabled
    TC or TCN received  :0
    TC count per hello  :0
    
    
    Share region-configuration :Enabled
    Time since last TC  :0 days 23h:9m:30s
    Number of TC        :1
    Last TC occurred    :10GE1/0/1
    Topo Change Flag    :0

    • If the convergence mode is Normal, go to Step 6.

    • If the convergence mode is Fast, run the stp converge normal command to change the convergence mode to Normal. If services are not restored after the convergence mode is changed, go to Step 6.

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

    • Results of the preceding troubleshooting procedure

    • Configuration files, log files, and alarm files of the device

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 608341

Downloads: 2951

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next