SupportDocumentationSwitchesData Center SwitchCloudEngine 58&68&78&88&98Configuration & CommissioningConfiguration Guide

CloudEngine 9800, 8800, 6800, and 5800 V200R020C10 Configuration Guide - Virtualization

This document describes the configurations of virtualization, including Stack Configuration.

This document describes the configurations of virtualization, including Stack Configuration.

Example for Establishing a Stack of Three Switches in a Ring Topology

Example for Establishing a Stack of Three Switches in a Ring Topology

Networking Requirements

An enterprise network needs to provide sufficient ports for access devices, and the network structure should be simple to facilitate configuration and management.

As shown in Figure 1-30, SwitchA, SwitchB, and SwitchC need to set up a stack in a ring topology.

Figure 1-30 Stack in a ring topology

Configuration Roadmap

The configuration roadmap is as follows:

  1. Make a stack plan.

  2. Complete the stack configuration of each switch based on the stack plan, including the stack member ID, stack priority, stack domain ID, and stack port. After the configuration is completed, save the configuration and power off these switches.

  3. Connect the switches using stack cables, and then power on these switches.

  4. Check whether a stack has been set up successfully.

In this stack setup example, software is configured and then stack cables are connected. If you want to connect stack cables and then configure software, see Example for Establishing a Stack of Two Switches (Connecting Cables and Then Configuring Software).

Procedure

  1. Make a stack plan.

    • Set the stack member IDs of SwitchA, SwitchB, and SwitchC to 1, 2, and 3 respectively.
    • Specify SwitchA as the master switch and set a higher stack priority (150) for it. Set the stack priorities of SwitchB and SwitchC to 120 and 90 respectively.
    • Set the stack domain ID of SwitchA, SwitchB, and SwitchC to 10 and ensure that this stack domain ID is unique among all stack domain IDs on the network.
    • Set the stack connection topology to ring topology. Figure 1-31 shows the ports used for stack connections of member switches.
      Figure 1-31 Connections between stack ports

  2. Configure stack parameters.

    # On SwitchA, set the stack priority to 150 and stack domain ID to 10. By default, the stack member ID of a switch is 1. In this example, SwitchA retains the default stack member ID 1, and you do not configure this parameter.
    <HUAWEI> system-view
[~HUAWEI] sysname SwitchA
[*HUAWEI] commit
[~SwitchA] stack
[~SwitchA-stack] stack member 1 priority 150
Info: The operation will take effect after reboot.
[*SwitchA-stack] stack member 1 domain 10
Info: The operation takes effect only after the save command is executed. The device with a lower priority then will be reset in the stack merging scenario.
[*SwitchA-stack] quit
[*SwitchA] commit
    # On SwitchB, set the stack member ID to 2, stack priority to 120, and stack domain ID to 10.
    <HUAWEI> system-view
[~HUAWEI] sysname SwitchB
[*HUAWEI] commit
[~SwitchB] stack
[~SwitchB-stack] stack member 1 priority 120
Info: The operation will take effect after reboot.
[*SwitchB-stack] stack member 1 domain 10
Info: The operation takes effect only after the save command is executed. The device with a lower priority then will be reset in the stack merging scenario.
[*SwitchB-stack] stack member 1 renumber 2 inherit-config
Warning: The stack configuration of member ID 1 will be inherited to member ID 2 after the device resets. Continue? [Y/N]: y
[*SwitchB-stack] quit
[*SwitchB] commit

    SwitchB has not restarted and its stack member ID is still 1. Therefore, member 1 is specified in the stack configuration.

    The inherit-config parameter is specified when the stack member ID is changed, so SwitchB inherits the stack configuration of member 1 after restarting. If this parameter is not specified, SwitchB does not inherit the stack configuration of member 1 after restarting. You need to perform stack configuration on SwitchB based on member 2.

    # On SwitchC, set the stack member ID to 3, stack priority to 90, and stack domain ID to 10.

    <HUAWEI> system-view
[~HUAWEI] sysname SwitchC
[*HUAWEI] commit
[~SwitchC] stack
[~SwitchC-stack] stack member 1 priority 90
Info: The operation will take effect after reboot.
[*SwitchC-stack] stack member 1 domain 10
Info: The operation takes effect only after the save command is executed. The device with a lower priority then will be reset in the stack merging scenario.
[*SwitchC-stack] stack member 1 renumber 3 inherit-config
Warning: The stack configuration of member ID 1 will be inherited to member ID 3 after the device resets. Continue? [Y/N]: y
[*SwitchC-stack] quit
[*SwitchC] commit

  3. Configure stack ports.

    # On SwitchA, add 10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to stack port 1/2.

    [~SwitchA] interface stack-port 1/1
[*SwitchA-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2
Warning: After the configuration is complete,
1.The interface(s) (10GE1/0/1-1/0/2) will be converted to stack mode and be configured with the port crc-statistics trigger error-down command if the configuration does not exist. 
2.The interface(s) may go Error-Down (crc-statistics) because there is no shutdown configuration on the interfaces.Continue? [Y/N]: y
[*SwitchA-Stack-Port1/1] quit
[*SwitchA] interface stack-port 1/2
[*SwitchA-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4
Warning: After the configuration is complete,
1.The interface(s) (10GE1/0/3-1/0/4) will be converted to stack mode and be configured with the port crc-statistics trigger error-down command if the configuration does not exist. 
2.The interface(s) may go Error-Down (crc-statistics) because there is no shutdown configuration on the interfaces.Continue? [Y/N]: y
[*SwitchA-Stack-Port1/2] quit
[*SwitchA] commit
[~SwitchA] quit

    After service ports are configured as stack member ports, the port crc-statistics trigger error-down command is automatically configured on these member ports.

    # On SwitchB, add 10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to stack port 1/2.

    [~SwitchB] interface stack-port 1/1
[*SwitchB-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2
Warning: After the configuration is complete,
1.The interface(s) (10GE1/0/1-1/0/2) will be converted to stack mode and be configured with the port crc-statistics trigger error-down command if the configuration does not exist. 
2.The interface(s) may go Error-Down (crc-statistics) because there is no shutdown configuration on the interfaces.Continue? [Y/N]: y
[*SwitchB-Stack-Port1/1] quit
[*SwitchB] interface stack-port 1/2
[*SwitchB-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4
Warning: After the configuration is complete,
1.The interface(s) (10GE1/0/3-1/0/4) will be converted to stack mode and be configured with the port crc-statistics trigger error-down command if the configuration does not exist. 
2.The interface(s) may go Error-Down (crc-statistics) because there is no shutdown configuration on the interfaces.Continue? [Y/N]: y
[*SwitchB-Stack-Port1/2] quit
[*SwitchB] commit
[~SwitchB] quit

    # On SwitchC, add 10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to stack port 1/2.

    [~SwitchC] interface stack-port 1/1
[*SwitchC-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2
Warning: After the configuration is complete,
1.The interface(s) (10GE1/0/1-1/0/2) will be converted to stack mode and be configured with the port crc-statistics trigger error-down command if the configuration does not exist. 
2.The interface(s) may go Error-Down (crc-statistics) because there is no shutdown configuration on the interfaces.Continue? [Y/N]: y
[*SwitchC-Stack-Port1/1] quit
[*SwitchC] interface stack-port 1/2
[*SwitchC-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4
Warning: After the configuration is complete,
1.The interface(s) (10GE1/0/3-1/0/4) will be converted to stack mode and be configured with the port crc-statistics trigger error-down command if the configuration does not exist. 
2.The interface(s) may go Error-Down (crc-statistics) because there is no shutdown configuration on the interfaces.Continue? [Y/N]: y
[*SwitchC-Stack-Port1/2] quit
[*SwitchC] commit
[~SwitchC] quit

  4. Check the stack configuration.

    # After the preceding configuration is completed, run the display stack configuration command to check whether the configuration is consistent with the stack plan. If not, modify the configuration. The command output on SwitchA is used as an example.

    <SwitchA> display stack configuration
Oper          : Operation
Conf          : Configuration
*             : Offline configuration
Isolated Port : The port is in stack mode, but does not belong to any Stack-Port

Attribute Configuration:
-----------------------------------------
 MemberID      Domain         Priority 
Oper(Conf)   Oper(Conf)      Oper(Conf)
-----------------------------------------
1(1)         --(10)          100(150)    
-----------------------------------------

Stack-Port Configuration:
--------------------------------------------------------------------------------
Stack-Port      Member Ports
--------------------------------------------------------------------------------
Stack-Port1/1   10GE1/0/1           10GE1/0/2
Stack-Port1/2   10GE1/0/3           10GE1/0/4
--------------------------------------------------------------------------------

  5. Save the stack configuration and then power off the switches.

    # Save the configurations of SwitchA, SwitchB, and SwitchC and then power off them. The configurations of SwitchB and SwitchC are similar to that of SwitchA.

    <SwitchA> save
Warning: The current configuration will be written to the device. Continue? [Y/N]: y

  6. Connect the three switches using stack cables based on the stack plan. After the switches are connected, power on them.

    You are advised to first power on the high-priority switch so that it starts first and becomes the master switch.

  7. Verify the configuration.

    # Log in to the stack through the console interface or management interface of any switch and run the display stack command to check whether the stack is set up successfully. To log in through the management interface, specify the IP address of the master switch.

    <SwitchA> display stack
--------------------------------------------------------------------------------
MemberID Role     MAC              Priority   DeviceType         Description
--------------------------------------------------------------------------------
 1       Master   0004-9f31-d520   150        CE6881-48S6CQ 
 2       Standby  0004-9f62-1f40   120        CE6881-48S6CQ 
 3       Slave    0004-9f69-a391   90         CE6881-48S6CQ 
--------------------------------------------------------------------------------

    The preceding command output shows that a stack has been set up successfully and the master switch is the switch with the stack member ID 1, namely, SwitchA.

    # Display stack topology information.

    <SwitchA> display stack topology
Stack Topology:
----------------------------------------------
            Stack-Port 1      Stack-Port 2    
MemberID   Status Neighbor   Status Neighbor  
----------------------------------------------
1          up     2          up     3         
2          up     1          up     3         
3          up     2          up     1        
----------------------------------------------

Stack Link:
--------------------------------------------------------------------
Stack-Port       Port           Status     PeerPort       PeerStatus
--------------------------------------------------------------------
Stack-Port1/1    10GE1/0/1      up         10GE2/0/1      up
Stack-Port1/1    10GE1/0/2      up         10GE2/0/2      up
Stack-Port1/2    10GE1/0/3      up         10GE3/0/3      up
Stack-Port1/2    10GE1/0/4      up         10GE3/0/4      up
Stack-Port2/1    10GE2/0/1      up         10GE1/0/1      up
Stack-Port2/1    10GE2/0/2      up         10GE1/0/2      up
Stack-Port2/2    10GE2/0/3      up         10GE3/0/1      up
Stack-Port2/2    10GE2/0/4      up         10GE3/0/2      up
Stack-Port3/1    10GE3/0/1      up         10GE2/0/3      up
Stack-Port3/1    10GE3/0/2      up         10GE2/0/4      up
Stack-Port3/2    10GE3/0/3      up         10GE1/0/3      up
Stack-Port3/2    10GE3/0/4      up         10GE1/0/4      up
--------------------------------------------------------------------

  8. Save the stack configuration.

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

    <SwitchA> save
Warning: The current configuration will be written to the device. Continue? [Y/N]: y

Configuration Files

  • Stack configuration file

    #
sysname SwitchA
#
stack
 #
 stack member 1 domain 10
 stack member 1 priority 150
 #
 stack member 2 domain 10
 stack member 2 priority 120
 #
 stack member 3 domain 10
 stack member 3 priority 90
#
interface Stack-Port1/1
#
interface Stack-Port1/2
#
interface Stack-Port2/1
#
interface Stack-Port2/2
# 
interface Stack-Port3/1
# 
interface Stack-Port3/2
# 
interface 10GE1/0/1
 port mode stack
 stack-port 1/1
 port crc-statistics trigger error-down
#
interface 10GE1/0/2
 port mode stack
 stack-port 1/1
 port crc-statistics trigger error-down
#
interface 10GE1/0/3
 port mode stack
 stack-port 1/2
 port crc-statistics trigger error-down
#
interface 10GE1/0/4
 port mode stack
 stack-port 1/2
 port crc-statistics trigger error-down
#
interface 10GE2/0/1
 port mode stack
 stack-port 2/1
 port crc-statistics trigger error-down
#
interface 10GE2/0/2
 port mode stack
 stack-port 2/1
 port crc-statistics trigger error-down
#
interface 10GE2/0/3
 port mode stack
 stack-port 2/2
 port crc-statistics trigger error-down
#
interface 10GE2/0/4
 port mode stack
 stack-port 2/2
 port crc-statistics trigger error-down
#
interface 10GE3/0/1
 port mode stack
 stack-port 3/1
 port crc-statistics trigger error-down
#
interface 10GE3/0/2
 port mode stack
 stack-port 3/1
 port crc-statistics trigger error-down
#
interface 10GE3/0/3
 port mode stack
 stack-port 3/2
 port crc-statistics trigger error-down
#
interface 10GE3/0/4
 port mode stack
 stack-port 3/2
 port crc-statistics trigger error-down
#
return