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

Configuration Guide - Virtualization

CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of virtualization, including stack and VS.

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.

    • If multiple management interfaces are available in a stack, only one management interface takes effect.

  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   006d-8835-2b00   150        CE12804
    2        Standby  006d-8835-2c00   100        CE12804
    --------------------------------------------------------------------------------
    
    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

If a stack is set up successfully, indicator states on the member switches are as follows:
  • On one switch, the STACK indicator on an MPU is steady green. This switch is the master switch. On the other switch, the STACK indicators on both MPUs are blinking green. This switch is the standby switch.

    If both switches have a STACK indicator in steady green state, the two switches are running the stacking function but they fail to set up a stack.

  • The LINK indicators of the SIP ports on the MPUs or service ports used for stack connection are steady green.

Table 1-6 describes the indicator states and meanings.
Table 1-6 Indicator description

Indicator Location

Indicator

Color

Description

MPU

ACT: active/standby status indicator

Green

  • Steady on: The MPU is the active MPU of the local switch.

  • Off: The MPU is the standby MPU of the local switch.

STACK: stack status indicator

Green

  • Steady on: The stacking function is enabled, and the MPU is the system master MPU of the stack.

  • Blinking: The stacking function is enabled, and the MPU is not the system master MPU of the stack.

  • Off: The stacking function is not enabled.

SIP port status indicator

Green

  • Steady on: The link status of the SIP port is Up.

  • Off: The link status of the SIP port is Down.

LPU

Port status indicator

Green

  • Steady on: The link status of the SIP port is Up.

  • Off: The link status of the port is Down.

Follow-up Procedure

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

    In MPU connection mode, 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.

      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.

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

    In MPU connection mode, 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.
  • Service ports on a stack card are in Error-Down state.

    In LPU connection mode, if a stack card has different resource modes than the configured resource modes during startup, or the port split configurations are inconsistent, all service ports except stack member ports on the stack card 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 extended TCAM resource mode, ARP resource allocation mode, Eth-Trunk quantity, TCAM ACL resource mode, extended Layer 3 forwarding resource mode, tunnel mode, NVO3 ACL extension mode, card interoperability mode, card enhance mode (sFlow), card enhance mode (NetStream), 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/1/0/1
    10GE1/1/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 card 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 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 service 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 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/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.

      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-03-21

Document ID: EDOC1000166610

Views: 44273

Downloads: 131

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next