Common Stack Fault Location Guide

Publication Date:  2015-06-17 Views:  719 Downloads:  0
Issue Description
1.  A Stack Fails to Be Established.

2.  All Service Ports of a CE12800 in a Stack Enter the Error-Down State.
Handling Process
1.  A Stack Fails to Be Established.

Troubleshooting procedure:

Check the physical cables, stack configuration, and logs in sequence to locate the fault.

Step 1 Check whether physical cables between stack member devices are correctly connected.

CE12800 stack connection restrictions:

The following figure shows the recommended connections on CE12800s.



You are advised to fully cross-connect SIP ports according to the preceding diagram. Few connections cannot ensure reliability.

LPUs must be connected in 2+2 mode according to the preceding diagram.Cross-connections are not supported in V100R003C00 and earlier versions but supported in V100R003C10 and later versions.

GE interfaces cannot be used for forwarding connections.

10GE optical interfaces can be used as physical member interfaces only when they have 10GE optical modules installed. They cannot be used to set up a stack when being equipped with GE optical modules or GE copper modules.

Physical member ports in a stack port must be the same type. For example, 10GE and 40GE ports cannot be added to the same stack port.

Starting from V100R003C00, 10GE optical interfaces derived from 40GE optical interfaces can be used for stack connections. In V100R002C00 and earlier versions, these 10GE optical interfaces cannot be used for stack connections.

In V100R003C00 and V100R003C10, 10GE optical ports derived from 100GE optical ports cannot be used for stack connection. In V100R005C00 and later versions, 10GE or 40GE optical ports derived from 100GE optical ports can be used for stack connection.

CE7800&6800&5800 switch stack connection restrictions:

Switches of different series cannot set up a stack. For example, CE6850EI and CE5850EI switches cannot set up a stack; CE5850EI and CE5850HI switches cannot set up a stack.

GE interfaces cannot be used for stack connections.

10GE optical interfaces can be used as physical member interfaces only when they have 10GE optical modules installed. They cannot be used to set up a stack when being equipped with GE optical modules or GE copper modules.

Physical member ports in a stack port must be the same type. For example, 10GE and 40GE ports cannot be added to the same stack port.

From V100R003C00 (except the CE7850-EI), 10GE optical interfaces derived from 40GE optical interfaces can be used for stack connections. In V100R002C00 and earlier versions, these 10GE optical interfaces cannot be used for stack connections.

On the CE6850EI, CE6810EI, CE6810LI, and CE5850EI, if a 10GE interface with port number in the range 4N+1 to 4N+4 (N = 0, 1, 2, 3...) is configured as a physical member interface in a stack, all the interfaces with port numbers 4N+1 to 4N+4 are configured as physical member interfaces. This restriction does not apply to switches of other models.

The CE5810-48T4S-EI provides four 10GE optical interfaces. Only 10GE1/0/1 and 10GE1/0/2 can be added to the same stack interface, and 10GE1/0/3 and 10GE1/0/4 can be added to the same stack interface. This restriction does not apply to switches of other models.

Step 2 Check whether the stack configuration is correct.

Run the display stack configuration / display stack topology command to check the stack configuration:

Check whether the stacking function is enabled (applicable only to the CE12800).
By default, the stacking function is disabled on the CE12800. You need to run the stack enable command to enable the stacking function before setting up a stack.
By default, the stacking function is enabled on the CE7800&6800&5800.

Check whether member switches in the stack have the same stack domain ID.
All member switches of the same stack must have the same stack domain ID configured. By default, no stack domain ID is configured. If member switches have different stack domain IDs, run the stack member { member-id | all } domain domain-id command to change these domain IDs to the same.

Check whether member switches use the same stack connection mode (applicable only to the CE12800).
When CE12800s need to set up a stack, all member switches in the stack must have the same stack connection mode configured. If member switches use different stack connection modes, run the stack member { member-id | all } link-type { mainboard-direct | linecard-direct } command to change these stack connection modes to the same.

Check whether the stack port configuration is correct.
Check whether physical ports have been added to specified logical stack ports as required. If the configuration is correct, check whether physical ports used for stack connections are Up. If a port is Down, check whether the stack cable is securely connected to the port. If the stack cable is securely connected, the cable or optical module on the port may be faulty. Replace the cable or optical module.

Check whether conflicting offline configuration exists.
Run the display current-configuration all command to check whether the master switch has the offline stack configuration of the standby or slave switch and the configuration conflicts with the stack configuration of the standby or slave switch. For example, the master switch has the logical stack port configuration of the offline standby switch, and logical stack ports have the shutdown configuration. If the master switch has the conflicting offline configuration, modify the conflicting configuration and then restart the standby or slave switch.

Step 3 Save the modified stack configuration to the configuration file.

The domain ID configuration takes effect immediately after being saved. However, you must restart the stack to make the configurations of other stack attributes take effect. Therefore, ensure that all the modified configurations are saved to the configuration file before the restart.

Step 4 Run the display stack troubleshooting command to check fault information about the stack.

Fault information is recorded during stack establishment. You can use this command to view the cause of the stack establishment failure, such as inconsistent domain IDs and stack interface configuration conflict.

Step 5 If stack connections and configuration are correct, collect log information and contact Huawei technical support personnel.

<HUAWEI> save logfile  //Collect common user log file log.log.
<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] save logfile diagnose-log     //Collect diagnostic log file diag.log generated when the device is running.
----End

2.  All Service Ports of a CE12800 in a Stack Enter the Error-Down State

Troubleshooting procedure:

You can determine the fault using the following methods:

Check interface indicators on LPUs.
When a service port enters the Error-Down state, the service port becomes Down and the interface indicator is off.

Run the display alarm active command to view Error-Down alarm information.

<HUAWEI> display alarm active
-------------------------------------------------------------------------------- 
Sequence   AlarmId    Severity Date Time  Description 
-------------------------------------------------------------------------------- 
135        0x8520006  Warning  2013-12-17 Error-down occurred. (Ifindex=71, Ifna 
                                 15:54:08  me=10GE1/4/0/0, Cause=no-stack-link) 
134        0x8520006  Warning  2013-12-17 Error-down occurred. (Ifindex=72, Ifna 
                                 15:54:08  me=10GE1/4/0/1, Cause=no-stack-link) 
133        0x8520006  Warning  2013-12-17 Error-down occurred. (Ifindex=73, Ifna 
                                 15:54:08  me=10GE1/4/0/2, Cause=no-stack-link) 
132        0x8520006  Warning  2013-12-17 Error-down occurred. (Ifindex=74, Ifna 
                                 15:54:08  me=10GE1/4/0/3, Cause=no-stack-link) 
--------------------------------------------------------------------------------
The command output displays the no-stack-link Error-Down alarm.

Run the display error-down recovery command to check the interface Error-Down cause.

<HUAWEI> display error-down recovery
interface                    error-down cause           recovery   remainder
                                                        time(sec)  time(sec)
----------------------------------------------------------------------------
10GE1/4/0/0                  no-stack-link              --         --
10GE1/4/0/1                  no-stack-link              --         --
10GE1/4/0/2                  no-stack-link              --         --
10GE1/4/0/3                  no-stack-link              --         --
The command output displays that the interface Error-Down cause is no stack link.

View logs.

View the log.log file to check the interface Error-down cause.
To rectify the fault, ensure that physical member interfaces are correctly connected and service ports are correctly added to logical stack ports.

Root Cause

1.A Stack Fails to Be Established
Common causes:
Cables are incorrectly connected or faulty.
The stack configuration is incorrect.

2.  All Service Ports of a CE12800 in a Stack Enter the Error-Down State
Common causes:
In V100R003C00 and earlier versions and MPU connection mode, if all forwarding links fail and the master switch has working LPUs, all service ports on the standby switch enter the Error-Down state.
In V100R003C10 and later versions and MPU connection mode, if there is no forwarding link between two member devices, all service ports of one member device enter the Error-Down state.
 If two member devices are not connected through the forwarding link when setting up a stack or the forwarding link has not been Up after a stack is set up, service ports on the standby switch enter the error-down state.
 If the forwarding link changes from Up to Down, service ports on the member device with fewer LPUs enter the error-down state. If the two member devices have the same number of LPUs, service ports on the standby switch enter the error-down state.
 

END