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

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50 Configuration Guide - Virtualization

This document describes the configurations of virtualization, including stack and SVF.
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).
Verifying Whether a Stack Is Set Up Successfully

Verifying Whether a Stack Is Set Up Successfully

After the stack configuration is complete, to check whether a stack has been set up successfully, log in to a member switch and run a display command; alternatively, view indicators on member switches.

NOTE:

After a stack is set up successfully, you are advised to run the save command immediately to save the configuration.

Through a display Command

  1. Log in to the stack.

    • Local login: Log in through the console interface of any member switch.
    • Remote login: Log in through the management interface or another Layer 3 interface of any member switch. You can use remote login modes, such as Telnet and STelnet, if there are reachable routes between the switch and your operation terminal.
    NOTE:
    • After a stack is set up, the configuration file of the master switch takes effect in the stack. Therefore, you must specify the IP address of the master switch when logging in to the stack remotely.

    • After a stack is set up, the management interfaces of all stack members share the same IP address (IP address of the management interface on the master switch). When the management interfaces of multiple stack members are connected to the management network, only the management interface of one stack member is working. By default, the management interface on the master switch is working. If this interface becomes faulty or unavailable, the management interface on another stack member is working.

  2. Check whether the stack is set up successfully.

    Run the display stack command to check information about the stack member switches. If all member switches are displayed, the stack is set up successfully.
    <HUAWEI> display stack
    --------------------------------------------------------------------------------
    MemberID Role     MAC              Priority   DeviceType         Description
    --------------------------------------------------------------------------------
    +1       Master   0004-9f31-d520   150        CE6850-48T4Q-EI 
     2       Standby  0004-9f62-1f40   100        CE6850-48T4Q-EI 
     3       Slave    0004-9f69-a391   100        CE6850-48T4Q-EI 
    --------------------------------------------------------------------------------
    + indicates the device through which the user logs in.
    
    If only some member switch is displayed, the stack fails to be established. See Troubleshooting a Stack Setup Failure to handle the problem.

Through Indicators

View the MST indicators on all the member switches.
  • If the MST indicator of one switch is steady green and MST indicators of the other switches are off, the stack is set up successfully. The master switch is the one where the MST indicator is steady green.
  • If MST indicators on multiple switches are steady green or yellow, the stack fails to be set up.
Table 1-6 Description of stack-related indicators on switch panels

Indicator/Button

Color

Description

MST: stack master/slave indicator

-

Off: The switch is not the stack master switch.

Green

Steady on: The switch is the stack master switch or a standalone switch.

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/0/1
    10GE1/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.

      NOTE:

      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.

  • Service ports on a stack member switch are in Error-Down state.

    If a stack member switch that is starting uses a different resource mode than the master switch, or the port split configurations are inconsistent, all service ports except stack member ports 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.). Resource modes include ARP resource allocation mode, Eth-Trunk quantity, tunnel mode, layer 3 resource allocation mode, large Layer 3 interface mode, and EEDB resource mode. In the following example, a service port is in Error-Down state.
    <HUAWEI> display interface 10ge 1/0/1
    10GE1/0/1 current state : ERROR DOWN(resource-mismatch) (ifindex: 12)
    Line protocol current state : DOWN     
    ......
    

    After service ports enter the Error-Down state, you can save the configuration and then restart the faulty device to recover the service ports.

  • 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 or slave 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 or slave 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 service port is in Error-Down state.
    <HUAWEI> display interface 10ge 1/0/1
    10GE1/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 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 service port is in Error-Down state.
    <HUAWEI> display interface 10ge 1/0/1
    10GE1/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.

      NOTE:

      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.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1000166645

Views: 55421

Downloads: 344

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