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).
Example for Establishing a Stack of Two Switches (Connecting Cables and Then Configuring Software)

Example for Establishing a Stack of Two Switches (Connecting Cables and Then Configuring Software)

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.

In Figure 1-31, SwitchA and SwitchB (two access switches) set up a stack.

Figure 1-31 Configuring a stack of two switches

Configuration Roadmap

The configuration roadmap is as follows:
  1. Make a stack plan.

  2. Connect SwitchA and SwitchB using stack cables based on the stack plan.

  3. Complete the stack configuration of the high-priority switch, including the stack member ID, stack priority, stack domain ID, and stack port. After the configuration is completed, save the configuration and restart the switch.

  4. Disable stack ports of the high-priority switch. This operation prevents a failure to save the configuration and set up a stack because it prevents the low-priority switch from automatically restarting due to a stack merge during the configuration.

  5. Complete the stack configuration of the low-priority switch. After the configuration is completed, save the configuration and restart the switch.

  6. Enable disabled stack ports on the high-priority switch to set up a stack.

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

Procedure

  1. Make a stack plan.

    • Set the stack member IDs of SwitchA and SwitchB to 1 and 2 respectively.
    • Specify SwitchA as the master switch and set a higher stack priority (150) for it. Set the stack priority of SwitchB to 120.
    • Set the stack domain ID of SwitchA and SwitchB to 10 and ensure that this stack domain ID is unique among all stack domain IDs on the network.
    • Configure SwitchA and SwitchB to use ports 10GE1/0/1 through 10GE1/0/4 for stack connections.

  2. Connect SwitchA and SwitchB using stack cables based on the stack plan.
  3. Complete the stack configuration of SwitchA first because SwitchA is specified as the high-priority switch.

    # 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
    [*SwitchA-stack] stack member 1 domain 10
    [*SwitchA-stack] quit
    [*SwitchA] commit
    
    # On SwitchA, add 10GE1/0/1 to 10GE1/0/4 to stack port 1/1.
    [~SwitchA] interface stack-port 1/1
    [*SwitchA-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/4
    Warning: After the configuration is complete,
    1.The interface(s) (10GE1/0/1-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/1] commit
    [~SwitchA-Stack-Port1/1] return
    

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

  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.

    <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       Switch Mode     Uplink Port
    Oper(Conf)   Oper(Conf)      Oper(Conf)      Oper(Conf)      Oper(Conf)
    ----------------------------------------------------------------------------
    1(1)         --(10)          100(150)        Auto(Auto)      4*40GE(4*40GE)
    ----------------------------------------------------------------------------
    
    Stack-Port Configuration:
    --------------------------------------------------------------------------------
    Stack-Port      Member Ports
    --------------------------------------------------------------------------------
    Stack-Port1/1   10GE1/0/1           10GE1/0/2           10GE1/0/3
                    10GE1/0/4
    --------------------------------------------------------------------------------
    

  5. Save the configuration of SwitchA and then restart it.

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

  6. Disable stack ports of SwitchA.

    # After SwitchA restarts, log in to it and disable its stack ports.

    <SwitchA> system-view
    [~SwitchA] interface stack-port 1/1
    [~SwitchA-Stack-Port1/1] shutdown
    [*SwitchA-Stack-Port1/1] commit
    [~SwitchA-Stack-Port1/1] quit
    

    Disabling stack ports can prevent a stack merge between SwitchA and SwitchB. If stack ports of SwitchA are not disabled, SwitchB and SwitchA may merge into one stack in advance because the stack merge conditions have been met. In this situation, SwitchB will automatically restart without saving its configuration. As a result, SwitchA and SwitchB cannot set up a stack because their configurations are lost after their startup.

  7. Complete the stack configuration of SwitchB.

    # 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
    [*SwitchB-stack] stack member 1 domain 10
    [*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
    
    NOTE:

    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 SwitchB, add 10GE1/0/1 to 10GE1/0/4 to stack port 1/1.
    [~SwitchB] interface stack-port 1/1
    [*SwitchB-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/4
    Warning: After the configuration is complete,
    1.The interface(s) (10GE1/0/1-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/1] commit
    [~SwitchB-Stack-Port1/1] return
    

  8. Save the configuration of SwitchB and then restart it.

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

  9. Enable stack ports of SwitchA.

    # During the restart of SwitchB, enable disabled stack ports of SwitchA to enable SwitchA and SwitchB to set up a stack.

    [~SwitchA] interface stack-port 1/1
    [~SwitchA-Stack-Port1/1] undo shutdown
    [*SwitchA-Stack-Port1/1] commit
    [~SwitchA-Stack-Port1/1] return
    

    You are advised to enable disabled stack ports of SwitchA during the restart of SwitchB. If you enable these ports after the restart of SwitchB, SwitchB automatically restarts again due to a stack merge.

  10. Verify the configuration.

    # Wait for several minutes, and run the display stack command on the master switch SwitchA to check whether a stack has been set up successfully.

    <SwitchA> display stack
    --------------------------------------------------------------------------------
    MemberID Role     MAC              Priority   DeviceType         Description
    --------------------------------------------------------------------------------
    +1       Master   0004-9f31-d520   150        CE6850-48T4Q-EI 
     2       Standby  0004-9f62-1f40   120        CE6850-48T4Q-EI 
    --------------------------------------------------------------------------------
    + indicates the device where the activated management interface resides.
    

    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.

    # Check stack topology information.

    <SwitchA> display stack topology
    Stack Topology:
    ----------------------------------------------
                Stack-Port 1      Stack-Port 2
    MemberID   Status Neighbor   Status Neighbor
    ----------------------------------------------
    1          up     2          --     --
    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/1    10GE1/0/3          up         10GE2/0/3          up
    Stack-Port1/1    10GE1/0/4          up         10GE2/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/1    10GE2/0/3          up         10GE1/0/3          up
    Stack-Port2/1    10GE2/0/4          up         10GE1/0/4          up
    ----------------------------------------------------------------------------
    

  11. Save the stack configuration.

    NOTE:

    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
    #
    interface Stack-Port1/1
    #
    interface Stack-Port2/1
    #
    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/1
     port crc-statistics trigger error-down
    #
    interface 10GE1/0/4
     port mode stack
     stack-port 1/1
     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/1
     port crc-statistics trigger error-down
    #
    interface 10GE2/0/4
     port mode stack
     stack-port 2/1
     port crc-statistics trigger error-down
    #
    return
    
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1000166645

Views: 38467

Downloads: 298

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