Verifying Whether a Stack Is Set Up Successfully

Through a display Command

Through Indicators

Follow-up Procedure

• Ports of some member switches are in Error-Down state.

  During the setup of a stack, if the number of member switches exceeds the upper threshold because of incorrect configuration or connection, excess devices cannot join the stack and ports of these devices enter the Error-Down state (The device records the status of an interface as Error-Down when it detects that a fault occurs. The interface in Error-Down state cannot receive or send packets and the interface indicator is off.). In the following example, a service port is in Error-Down state.

  <HUAWEI> display interface 10ge 1/1/0/1
  10GE1/1/0/1 current state : ERROR DOWN(stack-member-exceed-limit) (ifindex: 12)
  Line protocol current state : DOWN     
  ......
  

  After ports of excess devices enter the Error-Down state, modify the configuration or connection to remove excess devices and then check whether the ports recover from the Error-Down state.
  You can recover ports from the Error-Down state using either of the following methods:

  • Manually recover ports from the Error-Down state (after the ports become Error-Down).

    • Run the shutdown and then undo shutdown commands or run the restart command on each port to restart the port.

    • Run the reboot command to restart member switches one by one to recover all the ports from the Error-Down state.

  • Enable ports to automatically recover from the Error-Down state (before the ports become Error-Down).

    To enable service ports to automatically recover from the Error-Down state, run the error-down auto-recovery cause stack-member-exceed-limit interval interval-value command in the system view to enable ports in Error-Down state to become Up automatically and set the delay after which ports become Up automatically.

    This method takes effect only for the ports that become Error-Down after this command is executed but not for those that have been in Error-Down state before this command is executed.

• Ports of a member switch are in Error-Down state.

  If there is no forwarding link between two member devices, 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.

  In the following example, a service port is in Error-Down state.

  <HUAWEI> display interface 10ge 1/1/0/1
  10GE1/1/0/1 current state : ERROR DOWN(no-stack-link) (ifindex: 12)
  Line protocol current state : DOWN     
  ......
  

  After the link fault is rectified and the forwarding link becomes Up, the Error-Down fault is automatically rectified.

• The stack fails to be set up, and service ports of some member switches are in Error-Down state.

  During the setup of a stack, if the standby switch has the stack configuration that conflicts with the master switch, the stack may fail to be set up, and service ports of the standby switch will enter the Error-Down state (The device records the status of an interface as Error-Down when it detects that a fault occurs. The interface in Error-Down state cannot receive or send packets and the interface indicator is off.). In the following example, a port is in Error-Down state.

  <HUAWEI> display interface 10ge 1/1/0/1
  10GE1/1/0/1 current state : ERROR DOWN(stack-config-conflict) (ifindex: 12)
  Line protocol current state : DOWN     
  ......
  

  After service ports of a member switch enter the Error-Down state, you can run the display stack troubleshooting current command to check the conflicting configuration and then modify the configuration to meet service requirements. Subsequently, restart the switch to enable the stack to be set up again and recover the service ports from the Error-Down state.

• Stack member ports are in Error-Down state.

  If a stack member port receives a large number of stack protocol packets or stack error packets within a short period, the port will enter the Error-Down state (The device records the status of an interface as Error-Down when it detects that a fault occurs. The interface in Error-Down state cannot receive or send packets and the interface indicator is off.). In the following example, a port is in Error-Down state.

  <HUAWEI> display interface 10ge 1/1/0/1
  10GE1/1/0/1 current state : ERROR DOWN(stack-packet-defensive) (ifindex: 12)
  Line protocol current state : DOWN     
  ......
  

  After a stack member port enters the Error-Down state, you are advised to find out the cause of the Error-Down event first. For example, check whether network connection errors cause a broadcast storm.
  You can recover ports from the Error-Down state using either of the following methods:

  • Manually recover ports from the Error-Down state (after the ports become Error-Down).

    Run the shutdown and then undo shutdown commands or run the restart command on each port to restart the port.

  • Enable ports to automatically recover from the Error-Down state (before the ports become Error-Down).

    To enable service ports to automatically recover from the Error-Down state, run the error-down auto-recovery cause stack-packet-defensive interval interval-value command in the system view to enable ports in Error-Down state to become Up automatically and set the delay after which ports become Up automatically.

    This method takes effect only for the ports that become Error-Down after this command is executed but not for those that have been in Error-Down state before this command is executed.