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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 13

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Establishing a Stack

Establishing a Stack

This section describes how to establish a stack.

Before establishing a stack, make a proper network plan, confirm software and hardware requirements, and determine roles and functions of member switches. Then connect the switches using stack cables and complete software configuration.

Stack cable connection and software configuration can be performed in either sequence. The stack setup procedure varies depending on which task is performed first.

Setting Up a Stack by Configuring Software and Then Connecting Stack Cables

You can complete software configuration before connecting stack cables if you are at the device deployment site. This stack setup procedure is simple, as shown in Figure 2-23.
Figure 2-23 Setting up a stack by configuring software and then connecting stack cables

Configuring Software

(Optional) Configuring a Stack Member ID

Context

Stack member IDs are used to identify and manage member switches in a stack. Each member switch has a unique stack member ID. If member switches have the same stack ID, the slave switches restart repeatedly.

  • After the CX11x&CX31x&CX91x series switch modules are configured with stacking IDs, if the software is rolled back from V100R001C03SPC310 to V100R001C03SPC301 or earlier, ensure that the stack ID is the default ID (slot number of the device) and run the reset offline-config command to delete offline configuration data. Otherwise, an error message is displayed and the upgrade fails if you use the upgrade package again after the version rollback.
  • Modify the CX311 stack ID with caution. If the stack ID is modified, ports of the new ID do not have FCoE configurations because the ports cannot inherit configurations from ports of the old ID. In this case, add FCoE configurations for ports (*/1-16/1-2) connected to compute nodes and ports (*/20/1 - */20/8) connected to the MX510 by referring to Configuring the CX311 to Connect to the FCoE Gateway, disable STP for ports (*/1-16/1-2) connected to compute nodes, and decide whether to disable the 40GE ports used for cascading based on the switch module relation (stack or cascade).

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the stack command to enter the stack management view.
  3. Run the stack member member-id renumber new-member-id [ inherit-config ] command to configure a stack member ID for the local switch.

    By default, the stack member ID of each device is its slot number. After changing the stack member ID, restart the switch for the configuration to take effect.

    • If you specify inherit-config in the command, the switch inherits the original stack configuration after it restarts.

    • If you do not specify inherit-config, the current stack configuration is lost after the switch restarts, and the configuration related to the new stack member ID in the configuration file takes effect.

    • If the configuration file contains offline configuration for the new stack member ID, do not specify inherit-config in the command.

  4. Run the commit command to commit the configuration.

(Optional) Configuring a Stack Priority

Context

The stack priority of a member switch determines its role in the stack. A larger value indicates a higher priority and higher probability that the member switch is elected as the master switch.

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the stack command to enter the stack management view.
  3. Run the stack member { member-id | all } priority priority-value command to configure a stack priority for the switch.

    By default, the stack priority of a switch is 100. After changing the stack priority, restart the switch for the configuration to take effect.

  4. Run the commit command to commit the configuration.

Configuring a Stack Domain ID

Context

After switches are connected using stack links and set up a stack, they form a stack domain. Multiple stacks can be deployed on a network to support various applications. These stacks are identified by their domain IDs.

Member switches in a stack must be configured with the same domain ID. Otherwise, they cannot set up a stack.

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the stack command to enter the stack management view.
  3. Run the stack member { member-id | all } domain domain-id command to configure a stack domain ID.

    By default, a switch has no stack domain ID. If the switch has no stack domain ID, the configuration takes effect after you save the configuration. If you change the existing stack domain ID, the new ID takes effect after the switch restarts.

  4. Run the commit command to commit the configuration.

Configuring a Stack Port

Context

Multiple physical member ports can be added to a stack port to improve stack link bandwidth and reliability. You can add physical member ports to a stack port using either of the following methods:
  • Method 1: Configure service ports as physical member ports and then add them to a stack port.

  • Method 2: Add service ports to a stack port. Then the service ports can be automatically configured as physical member ports.

  • V100R001 supports only method 1.

  • No configuration is set to physical ports.

  • You are advised to configure the same number of physical member ports on member switches. If a smaller number of physical member ports are configured on a low-priority switch, this switch may be initialized earlier than the other member switch after it restarts and becomes the master switch.

Procedure

  1. Create a stack port.
    1. Run the system-view command to enter the system view.
    2. Run the interface stack-port member-id/port-id command to create a stack port.

      By default, no stack port exists in the system.

    3. Run the commit command to commit the configuration.
  2. Configure service ports as physical member ports.

    Configurations in the stack management view and the interface view are the same. You can choose either one.

    • Configuration in the stack management view:
      1. Run the system-view command to enter the system view.

      2. Run the stack command to enter the stack management view.

      3. Run the port mode stack interface interface-type { interface-number1 [ to interface-number2 ] } &<1-16> command to configure service ports as physical member ports.

      4. Run the commit command to commit the configuration.

    • Configuration in the interface view:
      1. Run the system-view command to enter the system view.

      2. Run the interface interface-type interface-number command to enter the interface view.

      3. Run the port mode stack command to configure the service port as a physical member port.

      4. Run the commit command to commit the configuration.

  3. Add service ports or physical member ports to the stack port.

    Configurations in the stack management view and the interface view are the same. You can choose either one.

    • Configuration in the stack port view:
      1. Run the system-view command to enter the system view.

      2. Run the interface stack-port member-id/port-id command to enter the stack port view.

      3. Run the port member-group interface interface-type { interface-number1 [ to interface-number2 ] } &<1-16> command to add physical member ports to the stack port.

      4. Run the commit command to commit the configuration.

    • Configuration in the interface view:
      1. Run the system-view command to enter the system view.

      2. Run the interface interface-type interface-number command to enter the interface view.

      3. Run the stack-port member-id/port-id command to add the physical port to the stack port.

      4. Run the commit command to commit the configuration.

  4. (Optional) Configure a load balancing mode for the stack port.
    1. Run the system-view command to enter the system view.
    2. Run the interface stack-port member-id/port-id command to enter the stack port view.
    3. Run the load-balance { dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac } command to configure a load balancing mode for the stack port.

      By default, the load balancing mode used in a stack port is src-dst-ip.

    4. Run the commit command to commit the configuration.
  5. (Optional) Set an alarm threshold for the number of stack member links.
    1. Run the system-view command to enter the system view.
    2. Run the stack command to enter the stack management view.
    3. Run the stack port-link threshold alarm-threshold command to set an alarm threshold for the number of stack links.

      By default, the alarm threshold for the number of stack links is 1.

      If some stack links fail and the number of available stack links falls below the alarm threshold, the system generates an alarm. When the number of available stack links is larger than or equal to the alarm value, the system generates a clear alarm.

      • V100R001 does not support alarm threshold configuration.

      • A single-chassis stack does not generate alarms on the number of stack links.

    4. Run the commit command to commit the configuration.

Restarting the Switch After Saving the Configuration

Context

To prevent loss of stack configuration caused by power failure or restart of member switches, you are advised to save the configuration immediately after you complete the software configuration. Save the configuration such as the stack member ID and priority, and restart the switch to make the configuration take effect.

Procedure

  1. Run the save command in the user view to save the configuration.
  2. Run the reboot command in the user view to reboot the switch.

Connecting Stack Cables

Preparations

  • Required components: high-speed cables or optical modules and matching optical fibers
  • Required tools: cable ties, fiber binding tapes, labels, and ESD wrist strap or ESD gloves

Precautions

When installing or removing optical fibers, do not look into optical ports or connectors without eye protection.

  • Wear an ESD wrist strap or ESD gloves when connecting stack cables.
  • Ensure that the stack cables are not tangled with other cables.
  • Install or remove optical fibers carefully to avoid damages to fiber connectors.
  • The bend radius of optical fibers or high-speed cables must be larger than the minimum bend radius.
  • If a fiber connector is dirty, use an alcohol swab or a piece of air-laid paper to gently wipe the fiber connector in one direction.
  • To remove a high-speed cable, gently push the cable connector and then pull out the cable by the pull ring.

Procedure

  1. Wear an ESD wrist strap and connect the ground terminal to the ESD jack on the rack.
  2. Attach labels to both ends of each stack cable and number these labels starting with 1, as shown in Figure 2-24.
    Figure 2-24 Attaching labels
  3. Connect the stack cables according to the connection rules.

    Stack member switches are connected using physical member ports, which are bound to logical stack ports. A stack port can have one or more physical member ports. You can bind multiple physical member ports to one stack port to implement link redundancy and increase link bandwidth.
    Figure 2-25 Stack connection
    Each switch supports two stack ports, named Stack-Portn/1 and Stack-Portn/2, where n is the stack member ID of the switch.
    A stack can be connected in a chain or ring topology, as shown in Figure 2-26.
    Figure 2-26 Stack topologies

Checking Whether a Stack Is Set Up Successfully

After completing the stack configuration, observe the indicators on the member switches to check whether the stack is set up successfully. If the stack is set up successfully, log in to the stack and run commands to check the stack running state and configure enhanced stack functions. If the stack fails to be set up, analyze the cause of the failure according to indicator states, or log in to any member switch and run commands to analyze the cause.

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

Observing Indicators to Check Whether a Stack Is Set Up

Background

After you complete stack connection and configuration, you can view indicators on the switch panels to check whether a stack is set up successfully.

Procedure
  • Press the mode switch button on any member switch until the STACK indicator is steady green.

    This method applies to V100R002 and later versions.

    • If STACK indicators on all the member switches are steady green, the stack is set up successfully. Then, you can check the MST indicators on the member switches to identify the master switch. The MST indicator on the master switch is steady green, and the MST indicators on the other member switches are off.
    • If some member switches have their STACK indicators off, the stack fails to be set up.
  • 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.
Stack-related Indicators
Table 2-5 Description of stack-related indicators on switch panels

Indicator/Button

Color

Description

STAT: stacking status indicator

Green

  • Off: The switch module is not powered on.
  • Blinking green for 10 times: The switch module is being powered on.
  • Blinking green: The switch module is standby in stacking mode and is operating properly.
  • Steady green: The switch module is active in stacking mode or is not stacked, and is working properly.

Logging In and Checking Whether a Stack Is Set Up Successfully

Context

You can observe indicators on member switches or log in to the system and use commands to check whether a stack is set up successfully. If the stack fails to be established, you can locate the fault according to the command output.

Procedure

  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.
    • 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.

    • If indicators on member switches show that the switches fail to set up a stack, log in to each switch to analyze the cause.

  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   Device Type     Bay/Chassis         
    ----------------------------------------------------------------------------------
    1        Master   0004-9f31-d520   150        CX310           1E/120               
    2        Standby  0004-9f62-1f40   100        CX310           2X/120               
    3        Slave    0004-9f69-a391   100        CX310           3X/120               
    ----------------------------------------------------------------------------------
    

    If only some of member switches are displayed, the stack fails to be established. See Handling a Stack Setup Failure to handle the problem.

    After the stacking is complete, run the stp disable to disable the STP function from the stack standby or slave interface that connects to the compute node.

Handling a Stack Setup Failure
  1. Run the display device command to check the device model. Switches of different series cannot set up a stack.

  2. Run the display interface brief command to check whether physical ports with stack cable connected are Up. If a port is Down, check whether configurations for stack devices are complete. If the configurations are complete, check whether the stack cable is securely connected to the port. If the stack cable is securely connected, the cable or the optical module on the port may be faulty. Replace the cable or optical module.

  3. Run the display stack configuration command to check whether stack domain IDs on the member switches are the same. If the member switches use different stack domain IDs, modify the configuration and restart the switches.

  4. Run the display stack troubleshooting command to check stack fault events. The command displays some causes of stack setup failures.

Setting Up a Stack by Connecting Stack Cables and Then Configuring Software

Context

Figure 2-27 shows the procedure for setting up a stack by connecting stack cables and then configuring software. You can use this method in for remote configuration of a stack.
Figure 2-27 Setting up a stack by connecting stack cables and then configuring software

You must disable the stack port on the high-priority switch, and then enable the stack port after configuring the low-priority switch. Otherwise, the low-priority switch will restart due to stack merging, and its configuration will be lost. As a result, the stack cannot be set up.

Procedure

  1. Connect the member switches using stack cables according to the connection rules described in Connecting Stack Cables.
  2. According to the network plan, log in the high-priority switch first and complete software configuration on the switch. For the configuration procedure, see Configuring Software.

    After completing the software configuration, run the save command in the user view to save the configuration. If some settings take effect after a restart, run the reboot command in the user view to restart the switch.

  3. Disable the stack port of the high-priority switch connected to the low-priority switch. On the high-priority switch, run the interface stack-port member-id/port-id command in the system view to enter the stack port view, and then run the shutdown command to disable the stack port.
  4. Log in to the low-priority switch and complete the software configuration according to Configuring Software.

    After completing the software configuration, run the save command in the user view to save the configuration. If some settings take effect after a restart, run the reboot command in the user view to restart the switch.

  5. Enable the stack port on the high-priority switch. On the high-priority switch, run the interface stack-port member-id/port-id command in the system view to enter the stack port view, and then run the undo shutdown command to enable the stack port.

    Then the two single-chassis stacks merge into one. The low-priority switch restarts and joins the stack.

  6. Check whether the stack is set up successfully according to Checking Whether a Stack Is Set Up Successfully.

    If the stack is set up successfully, run the save command in the user view to save the configuration of the stack.

Translation
Download
Updated: 2019-12-13

Document ID: EDOC1000041694

Views: 61611

Downloads: 3623

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