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 12

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).
Configuration Examples

Configuration Examples

This section provides stack configuration examples, including networking requirements, configuration roadmap, and configuration procedure.

Example for Establishing a Stack in a Chain Topology

Networking Requirements

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

As shown in Figure 2-28, SwitchA, SwitchB, and SwitchC need to set up a stack in a chain topology. For stack connections, add 10GE1/17/1 and 10GE1/17/2 of SwitchA to stack port 1/1, 10GE2/17/1 and 10GE2/17/2 of SwitchB to stack port 2/1, 10GE2/17/3 and 10GE2/17/4 of SwitchB to stack port 2/2, and 10GE3/17/1 and 10GE3/17/2 of SwitchC to stack port 3/1.

Figure 2-28 Stack in a chain topology
Configuration Roadmap
The configuration roadmap is as follows:
  1. To enable the switches to set up a stack and distinguish the stack from other stacks on the network, configure stack parameters for the switches, including the stack member ID, priority, and stack domain ID.

  2. To enable data packets to be forwarded between stack member switches, configure stack ports on the switches. Multiple physical member ports can be added to a stack port to improve stack link bandwidth and reliability.

  3. To make the configuration effective and ensure that the stack can be set up successfully, save the stack configuration, restart the switches, connect the switches using stack cables.

Procedure

  1. Configure stack parameters on SwitchA, SwitchB, and SwitchC.

    # On SwitchA, set the stack member ID to 1, stack priority to 150, and stack domain ID to 10.

    <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 SwitchB, set the stack member ID to 2 and stack domain ID to 10.

    <HUAWEI> system-view
    [~HUAWEI] sysname SwitchB
    [*HUAWEI] commit
    [~SwitchB] stack
    [*SwitchB-stack] stack member 2 domain 10
    [*SwitchB-stack] quit
    [*SwitchB] commit

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

    <HUAWEI> system-view
    [~HUAWEI] sysname SwitchC
    [*HUAWEI] commit
    [~SwitchC] stack
    [*SwitchC-stack] stack member 3 domain 10
    [*SwitchC-stack] quit
    [*SwitchC] commit
    NOTE:
    When you run the stack member member-id renumber new-member-id [ inherit-config ] command to change the stack member ID:
    • 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.

  2. Configure stack ports.

    # On SwitchA, add 10GE1/17/1 and 10GE1/17/2 to stack port 1/1.

    [~SwitchA] interface stack-port 1/1
    [*SwitchA-Stack-Port1/1] port member-group interface 10ge 1/17/1 to 1/17/2
    Warning: The interface(s) (10GE1/17/1-1/17/4) will be converted to stack mode. [Y/N]: y
    [*SwitchA-Stack-Port1/1] quit
    [*SwitchA] commit
    [~SwitchA] quit

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

    [~SwitchB] interface stack-port 2/1
    [*SwitchB-Stack-Port2/1] port member-group interface 10ge 2/17/1 to 2/17/2
    Warning: The interface(s) (10GE2/17/1-2/17/4) will be converted to stack mode. [Y/N]: y
    [*SwitchB-Stack-Port2/1] quit
    [*SwitchB] interface stack-port 2/2
    [*SwitchB-Stack-Port2/2] port member-group interface 10ge 2/17/3 to 2/17/4
    [*SwitchB-Stack-Port2/2] quit
    [*SwitchB] commit
    [~SwitchB] quit

    # On SwitchC, add 10GE3/17/1 and 10GE3/17/2 to stack port 3/1.

    [~SwitchC] interface stack-port 3/1
    [*SwitchC-Stack-Port3/1] port member-group interface 10ge 3/17/1 to 3/17/2
    Warning: The interface(s) (10GE3/17/1-3/17/4) will be converted to stack mode. [Y/N]: y
    [*SwitchC-Stack-Port3/1] quit
    [*SwitchC] commit
    [~SwitchC] quit

  3. Check the stack configuration.

    # After completing the stack configuration, run the display stack configuration command on the switches to check whether the configuration is the same as expected. 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/17/1     10GE1/17/2
    --------------------------------------------------------------------------------
    
    Isolated Port Configuration:                    
    10GE1/17/3      10GE1/17/4
    

  4. Save the configuration and restart the switch.

    # Save the configurations of SwitchA, SwitchB, and SwitchC, and restart the switches.

    <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

    # The configurations of SwitchB and SwitchC are similar to the configuration of SwitchA, and are not mentioned here.

  5. Connect the switches using stack cables to set up a stack.
  6. Verify the configuration.

    # Check information about the stack member switches.

    <SwitchA> display stack
    ----------------------------------------------------------------------------------
    MemberID Role     MAC              Priority   Device Type     Bay/Chassis         
    ----------------------------------------------------------------------------------
    1        Master   0004-9f31-d520   150        CX310           1/120               
    2        Standby  0004-9f62-1f40   100        CX310           2/120               
    3        Slave    0004-9f69-a391   100        CX310           3/120               
    ----------------------------------------------------------------------------------
    

    # Display 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          up     3         
    3          up     2          --     --        
    ----------------------------------------------
    
    Stack Link:
    --------------------------------------------------------------------
    Stack-Port       Port           Status     PeerPort       PeerStatus
    --------------------------------------------------------------------
    Stack-Port1/1    10GE1/17/1      up         10GE2/17/1      up
    Stack-Port1/1    10GE1/17/2      up         10GE2/17/2      up
    Stack-Port2/1    10GE2/17/1      up         10GE1/17/1      up
    Stack-Port2/1    10GE2/17/2      up         10GE1/17/2      up
    Stack-Port2/2    10GE2/17/3      up         10GE3/17/1      up
    Stack-Port2/2    10GE2/17/4      up         10GE3/17/2      up
    Stack-Port3/1    10GE3/17/1      up         10GE2/17/3      up
    Stack-Port3/1    10GE3/17/2      up         10GE2/17/4      up
    --------------------------------------------------------------------
    

  7. Save the configuration.

    NOTE:

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

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

Configuration Files
  • Configuration file of the stack

    #
    sysname SwitchA
    #
    stack
     #
     stack member 1 domain 10
     stack member 1 priority 150
     #
     stack member 2 domain 10
     #
     stack member 3 domain 10
    #
    interface Stack-Port1/1
    #
    interface Stack-Port2/1
    #
    interface Stack-Port2/2
    # 
    interface Stack-Port3/1
    # 
    interface 10GE1/17/1
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/2
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/3
     port mode stack
    #
    interface 10GE1/17/4
     port mode stack
    #
    interface 10GE2/17/1
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/2
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/3
     port mode stack
     stack-port 2/2
    #
    interface 10GE2/17/4
     port mode stack
     stack-port 2/2
    #
    interface 10GE3/17/1
     port mode stack
     stack-port 3/1
    #
    interface 10GE3/17/2
     port mode stack
     stack-port 3/1
    #
    interface 10GE3/17/3
     port mode stack
    #
    interface 10GE3/17/4
     port mode stack
    #
    return
    

Example for Establishing a Stack in a Ring Topology

Networking Requirements

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

As shown in Figure 2-29, SwitchA, SwitchB, and SwitchC need to set up a stack in a ring topology. For stack connections, add 10GE1/17/1 and 10GE1/17/2 of SwitchA to stack port 1/1, 10GE1/17/3 and 10GE1/17/4 of SwitchA to stack port 1/2, 10GE2/17/1 and 10GE2/17/2 of SwitchB to stack port 2/1, 10GE2/17/3 and 10GE2/17/4 of SwitchB to stack port 2/2, and 10GE3/17/1 and 10GE3/17/2 of SwitchC to stack port 3/1, 10GE3/17/3 and 10GE3/17/4 of SwitchC to stack port 3/2.

Figure 2-29 Stack in a ring topology
Configuration Roadmap
The configuration roadmap is as follows:
  1. To enable the switches to set up a stack and distinguish the stack from other stacks on the network, configure stack parameters for the switches, including the stack member ID, priority, and stack domain ID.

  2. To enable data packets to be forwarded between stack member switches, configure stack ports on the switches. Multiple physical member ports can be added to a stack port to improve stack link bandwidth and reliability.

  3. To make the configuration effective and ensure that the stack can be set up successfully, save the stack configuration, restart the switches, connect the switches using stack cables.

Procedure

  1. Configure stack parameters on SwitchA, SwitchB, and SwitchC.

    # On SwitchA, set the stack member ID to 1, stack priority to 150, and stack domain ID to 10.

    <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 SwitchB, set the stack member ID to 2 and stack domain ID to 10.

    <HUAWEI> system-view
    [~HUAWEI] sysname SwitchB
    [*HUAWEI] commit
    [~SwitchB] stack
    [*SwitchB-stack] stack member 2 domain 10
    [*SwitchB-stack] quit
    [*SwitchB] commit

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

    <HUAWEI> system-view
    [~HUAWEI] sysname SwitchC
    [*HUAWEI] commit
    [~SwitchC] stack
    [*SwitchC-stack] stack member 3 domain 10
    [*SwitchC-stack] quit
    [*SwitchC] commit
    NOTE:
    When you run the stack member member-id renumber new-member-id [ inherit-config ] command to change the stack member ID:
    • 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.

  2. Configure stack ports.

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

    [~SwitchA] interface stack-port 1/1
    [*SwitchA-Stack-Port1/1] port member-group interface 10ge 1/17/1 to 1/17/2
    Warning: The interface(s) (10GE1/17/1-1/17/4) will be converted to stack mode. [Y/N]: y
    [*SwitchA-Stack-Port1/1] quit
    [*SwitchA] interface stack-port 1/2
    [*SwitchA-Stack-Port1/2] port member-group interface 10ge 1/17/3 to 1/17/4
    [*SwitchA-Stack-Port1/2] quit
    [*SwitchA] commit
    [~SwitchA] quit

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

    [~SwitchB] interface stack-port 2/1
    [*SwitchB-Stack-Port2/1] port member-group interface 10ge 2/17/1 to 2/17/2
    Warning: The interface(s) (10GE2/17/1-2/17/4) will be converted to stack mode. [Y/N]: y
    [*SwitchB-Stack-Port2/1] quit
    [*SwitchB] interface stack-port 2/2
    [*SwitchB-Stack-Port2/2] port member-group interface 10ge 2/17/3 to 2/17/4
    [*SwitchB-Stack-Port2/2] quit
    [*SwitchB] commit
    [~SwitchB] quit

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

    [~SwitchC] interface stack-port 3/1
    [*SwitchC-Stack-Port3/1] port member-group interface 10ge 3/17/1 to 3/17/2
    Warning: The interface(s) (10GE3/17/1-3/17/4) will be converted to stack mode. [Y/N]: y
    [*SwitchC-Stack-Port3/1] quit
    [*SwitchC] interface stack-port 3/2
    [*SwitchC-Stack-Port3/2] port member-group interface 10ge 3/17/3 to 3/17/4
    [*SwitchC-Stack-Port3/2] quit
    [*SwitchC] commit
    [~SwitchC] quit

  3. Check the stack configuration.

    # After completing the stack configuration, run the display stack configuration command on the switches to check whether the configuration is the same as expected. 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/17/1     10GE1/17/2
    Stack-Port1/2        10GE1/17/3     10GE1/17/4
    --------------------------------------------------------------------------------
    

  4. Save the configuration and restart the switch.

    # Save the configurations of SwitchA, SwitchB, and SwitchC, and restart the switches.

    <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

    # The configurations of SwitchB and SwitchC are similar to the configuration of SwitchA, and are not mentioned here.

  5. Connect the switches using stack cables to set up a stack.
  6. Verify the configuration.

    # Check information about the stack member switches.

    <SwitchA> display stack
    ----------------------------------------------------------------------------------
    MemberID Role     MAC              Priority   Device Type     Bay/Chassis         
    ----------------------------------------------------------------------------------
    1        Master   0004-9f31-d520   150        CX310           1/120               
    2        Standby  0004-9f62-1f40   100        CX310           2/120               
    3        Slave    0004-9f69-a391   100        CX310           3/120               
    ----------------------------------------------------------------------------------
    

    # 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/17/1      up         10GE2/17/1      up
    Stack-Port1/1    10GE1/17/2      up         10GE2/17/2      up
    Stack-Port1/2    10GE1/17/3      up         10GE3/17/3      up
    Stack-Port1/2    10GE1/17/4      up         10GE3/17/4      up
    Stack-Port2/1    10GE2/17/1      up         10GE1/17/1      up
    Stack-Port2/1    10GE2/17/2      up         10GE1/17/2      up
    Stack-Port2/2    10GE2/17/3      up         10GE3/17/1      up
    Stack-Port2/2    10GE2/17/4      up         10GE3/17/2      up
    Stack-Port3/1    10GE3/17/1      up         10GE2/17/3      up
    Stack-Port3/1    10GE3/17/2      up         10GE2/17/4      up
    Stack-Port3/2    10GE3/17/3      up         10GE1/17/3      up
    Stack-Port3/2    10GE3/17/4      up         10GE1/17/4      up
    --------------------------------------------------------------------
    

  7. Save the configuration.

    NOTE:

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

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

Configuration Files
  • Configuration file of the stack

    #
    sysname SwitchA
    #
    stack
     #
     stack member 1 domain 10
     stack member 1 priority 150
     #
     stack member 2 domain 10
     #
     stack member 3 domain 10
    #
    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/17/1
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/2
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/3
     port mode stack
     stack-port 1/2
    #
    interface 10GE1/17/4
     port mode stack
     stack-port 1/2
    #
    interface 10GE2/17/1
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/2
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/3
     port mode stack
     stack-port 2/2
    #
    interface 10GE2/17/4
     port mode stack
     stack-port 2/2
    #
    interface 10GE3/17/1
     port mode stack
     stack-port 3/1
    #
    interface 10GE3/17/2
     port mode stack
     stack-port 3/1
    #
    interface 10GE3/17/3
     port mode stack
     stack-port 3/2
    #
    interface 10GE3/17/4
     port mode stack
     stack-port 3/2
    #
    return
    

Example for Configuring DAD in Direct Mode

Networking Requirements

As shown in Figure 2-30, SwitchA and SwitchB set up a stack, and SwitchA is the master switch. The stack member ID of SwitchA is 1, and the stack member ID of SwitchB is 2.

If the stack splits due to a stack link failure, the network has two stacks with conflicting configurations. To avoid this dual-active condition, configure the DAD function in the stack. This function minimizes the impact of a stack split on the network.

Figure 2-30 DAD in direct mode
Configuration Roadmap
The configuration roadmap is as follows:
  1. Configure DAD in direct mode on ports of the stack member switches.

NOTE:

In Smart Channel mode, VLANs of the port with DAD must be different from those of the Smart Channels. If a Smart Channel fails, the ports in the VLANs of the Smart Channel are disabled (error-down), and therefore the ports cannot provide the DAD function. It is recommended that you use the operations described in Configuring DAD Through Management Interfaces.

Procedure

  1. Configure DAD in direct mode on ports of the stack member switches.

    # Configure DAD in direct mode on 10GE 1/17/5.

    <HUAWEI> system-view
    [~HUAWEI] interface 10ge 1/17/5
    [~HUAWEI-10GE1/17/5] dual-active detect mode direct
    Warning: The interface will block common data packets, except BPDU packets. Continue? [Y/N]: y
    [*HUAWEI-10GE1/17/5] commit
    [~HUAWEI-10GE1/17/5] quit
    

    # Configure DAD in direct mode on 10GE 2/17/5.

    [~HUAWEI] interface 10ge 2/17/5
    [~HUAWEI-10GE2/17/5] dual-active detect mode direct
    Warning: The interface will block common data packets, except BPDU packets. Continue? [Y/N]: y
    [*HUAWEI-10GE2/17/5] commit
    [~HUAWEI-10GE2/17/5] return
    

  2. Configure port VLANs.

    # Configure a VLAN.

    <HUAWEI> system-view
    [~HUAWEI] vlan 1020
    [*HUAWEI-vlan1020] commit
    [~HUAWEI-vlan1020] quit
    

    # Configure the VLAN for port 10GE 1/17/5.

    <HUAWEI> system-view
    [~HUAWEI] interface 10ge 1/17/5
    [~HUAWEI-10GE1/17/5] port default vlan 1020
    [*HUAWEI-10GE1/17/5] commit
    [~HUAWEI-10GE1/17/5] quit
    

    # Configure the VLAN for port 10GE 2/17/5.

    [~HUAWEI] interface 10ge 2/17/5
    [~HUAWEI-10GE2/17/5] port default vlan 1020
    [*HUAWEI-10GE2/17/5] commit
    [~HUAWEI-10GE2/17/5] return
    

  3. Verify the configuration.

    # Check the detailed DAD configuration on the stack.

    <HUAWEI> display dual-active
    Dual-active status: Normal                     
    Dual-active detect mode: Direct                  
    Dual-active detect configuration of MEth: Disable
    Dual-active direct detect interfaces configured:   
     10GE1/17/5    up                                  
     10GE2/17/5    up                                   
    Dual-active relay detect interfaces configured:      
     - 
    Excluded ports(configurable):                   
     -                                              
    Excluded ports(can not be configured):           
     10GE1/17/1
     10GE1/17/2
     10GE1/17/3
     10GE1/17/4
     10GE2/17/1
     10GE2/17/2
     10GE2/17/3
     10GE2/17/4
    

  4. Verify the DAD function.

    # When no service is configured on the stack after the DAD configuration is complete, trigger a stack split to verify whether the DAD function takes effect.
    NOTE:

    Do not trigger a stack split when services are running on the stack. Otherwise, services are affected when the stack splits.

    1. Trigger a stack split by shutting down all the ports with stack cable connected or removing all the stack cables.

    2. Log in to each member switch to check the stack status. You can see that the stack has split into two single-chassis stacks.

      <HUAWEI> display stack
      ----------------------------------------------------------------------------------
      MemberID Role     MAC              Priority   Device Type     Bay/Chassis         
      ----------------------------------------------------------------------------------
      1        Master   0004-9f31-d520   150        CX310           1/120               
      ----------------------------------------------------------------------------------
      
    3. Run the display trapbuffer command. A dual-active alarm is displayed.

      <HUAWEI> display trapbuffer
      Trapping buffer configuration and contents : enabled                            
      Allowed max buffer size : 1024                                                  
      Actual buffer size : 256                                                        
      Channel number : 3, Channel name : trapbuffer                                   
      Dropped messages : 0                                                            
      Overwritten messages : 0                                                        
      Current messages : 190                                                          
                                                                                      
      Aug 15 2013 14:32:35 HUAWEI %%01DAD/1/hwDadConflictDetect(t):CID=0x807f0419-OID=
      1.3.6.1.4.1.2011.5.25.246.1.1;Dual-active scenario is detected.
      
    4. The preceding operations verify that the DAD function is configured successfully.

    5. Restore the physical member ports to Up state or connect stack cables. The two switches set up a stack again.

Configuration Files
  • Configuration file of the stack

    #
    vlan 1020
    #
    stack
     #
     stack member 1 domain 10
     stack member 1 priority 150
     #
     stack member 2 domain 10
    #
    interface Stack-Port1/1
    #
    interface Stack-Port2/1
    #
    interface 10GE1/17/1
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/2
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/3
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/4
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/5
     port default vlan 1020
     dual-active detect mode direct
    #
    interface 10GE2/17/1
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/2
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/3
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/4
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/5
     port default vlan 1020
     dual-active detect mode direct
    #
    return

Example for Configuring DAD in Relay Mode

Networking Requirements

As shown in Figure 2-31, SwitchA, SwitchB, and SwitchC set up a stack and connect to SwitchD through Eth-Trunk10.

If the stack splits due to a stack link failure, the network has two stacks with conflicting configurations. To avoid this dual-active condition, configure the DAD function in the stack. This function minimizes the impact of a stack split on the network.

Figure 2-31 DAD in relay mode
Configuration Roadmap
The configuration roadmap is as follows:
  1. Use SwitchD as a DAD relay agent. On the stack, configure DAD in relay mode on Eth-Trunk10 connected to SwitchD.

  2. On SwitchD, enable the DAD proxy function on Eth-Trunk10 so that DAD packets can be forwarded through Eth-Trunk10.

NOTE:

In Smart Channel mode, VLANs of the port with DAD must be different from those of the Smart Channels. If a Smart Channel fails, the ports in the VLANs of the Smart Channel are disabled (error-down), and therefore the ports cannot provide the DAD function. It is recommended that you use the operations described in Configuring DAD Through Management Interfaces.

Procedure

  1. On the stack, configure DAD in relay mode on Eth-Trunk10.

    <HUAWEI> system-view
    [~HUAWEI] interface eth-trunk 10
    [*HUAWEI-Eth-Trunk10] trunkport 10ge 1/17/5
    [*HUAWEI-Eth-Trunk10] trunkport 10ge 2/17/5
    [*HUAWEI-Eth-Trunk10] trunkport 10ge 3/17/5
    [*HUAWEI-Eth-Trunk10] dual-active detect mode relay
    [*HUAWEI-Eth-Trunk10] commit
    [~HUAWEI-Eth-Trunk10] return
    

  2. On SwitchD, enable the DAD proxy function on Eth-Trunk10.

    # Log in to SwitchD and configure the DAD proxy function.

    <HUAWEI> system-view
    [~HUAWEI] sysname SwitchD
    [*HUAWEI] commit
    [~SwitchD] interface eth-trunk 10
    [*SwitchD-Eth-Trunk10] trunkport 10ge 1/17/1
    [*SwitchD-Eth-Trunk10] trunkport 10ge 1/17/2
    [*SwitchD-Eth-Trunk10] trunkport 10ge 1/17/3
    [*SwitchD-Eth-Trunk10] dual-active proxy
    [*SwitchD-Eth-Trunk10] commit
    [~SwitchD-Eth-Trunk10] return
    

  3. Verify the configuration.

    # Check the detailed DAD configuration on the stack.

    <HUAWEI> display dual-active
    Dual-active status: Normal
    Dual-active detect mode: Relay
    Dual-active detect configuration of MEth: Disable
    Dual-active direct detect interfaces configured:
     -                -
    Dual-active relay detect interfaces configured:
     Eth-Trunk10
          10GE1/17/5    up
          10GE2/17/5    up
          10GE3/17/5    up
    Excluded ports(configurable):
     -
    Excluded ports(can not be configured):
     10GE1/17/1
     10GE1/17/2
     10GE1/17/3
     10GE1/17/4
     10GE2/17/1
     10GE2/17/2
     10GE2/17/3
     10GE2/17/4
     10GE3/17/1
     10GE3/17/2
     10GE3/17/3
     10GE3/17/4
    

    # Check the DAD proxy configuration on SwitchD.

    <SwitchD> display dual-active proxy
    Dual-active proxy interfaces configured:
     Eth-Trunk10
          10GE1/17/1    up
          10GE1/17/2    up
          10GE1/17/3    up
    

  4. Verify the DAD function.

    # When no service is configured on the stack after the DAD configuration is complete, trigger a stack split to verify whether the DAD function takes effect.
    NOTE:

    Do not trigger a stack split when services are running on the stack. Otherwise, services are affected when the stack splits.

    1. Trigger a stack split by shutting down all the ports with stack cable connected or removing all the stack cables.

    2. Log in to each member switch to check the stack status. You can see that the stack has split into two single-chassis stacks.

      <HUAWEI> display stack
      ----------------------------------------------------------------------------------
      MemberID Role     MAC              Priority   Device Type     Bay/Chassis         
      ----------------------------------------------------------------------------------
      1        Master   0004-9f31-d520   150        CX310           1/120               
      ----------------------------------------------------------------------------------
      
    3. Run the display trapbuffer command. A dual-active alarm is displayed.

      <HUAWEI> display trapbuffer
      Trapping buffer configuration and contents : enabled                            
      Allowed max buffer size : 1024                                                  
      Actual buffer size : 256                                                        
      Channel number : 3, Channel name : trapbuffer                                   
      Dropped messages : 0                                                            
      Overwritten messages : 0                                                        
      Current messages : 190                                                          
                                                                                      
      Aug 15 2013 14:32:35 HUAWEI %%01DAD/1/hwDadConflictDetect(t):CID=0x807f0419-OID=
      1.3.6.1.4.1.2011.5.25.246.1.1;Dual-active scenario is detected.
      
    4. The preceding operations verify that the DAD function is configured successfully.

    5. Restore the physical member ports to Up state or connect stack cables. The two switches set up a stack again.

Configuration Files
  • Configuration file of the stack

    #
    stack
     #
     stack member 1 domain 10
     stack member 1 priority 150
     #
     stack member 2 domain 10
     #
     stack member 3 domain 10
    #
    interface Eth-Trunk10
     dual-active detect mode relay
    #
    interface Stack-Port1/1
    #
    interface Stack-Port2/1
    #
    interface Stack-Port2/2
    #
    interface Stack-Port3/1
    #
    interface 10GE1/17/1
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/2
     port mode stack
     stack-port 1/1
    #
    interface 10GE1/17/3
     port mode stack
    #
    interface 10GE1/17/4
     port mode stack
    #
    interface 10GE1/17/5
     eth-trunk 10
    #
    interface 10GE2/17/1
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/2
     port mode stack
     stack-port 2/1
    #
    interface 10GE2/17/3
     port mode stack
     stack-port 2/2
    #
    interface 10GE2/17/4
     port mode stack
     stack-port 2/2
    #
    interface 10GE2/17/5
     eth-trunk 10
    #
    interface 10GE3/17/1
     port mode stack
     stack-port 3/1
    #
    interface 10GE3/17/2
     port mode stack
     stack-port 3/1
    #
    interface 10GE3/17/3
     port mode stack
    #
    interface 10GE3/17/4
     port mode stack
    #
    interface 10GE3/17/5
     eth-trunk 10
    #
    return
    
  • Configuration file of SwitchD

    #
    sysname SwitchD
    #
    interface Eth-Trunk10
     dual-active proxy
    #
    interface 10GE1/17/1
     eth-trunk 10
    #
    interface 10GE1/17/2
     eth-trunk 10
    #
    interface 10GE1/17/3
     eth-trunk 10
    #
    return
    

Example for Configuring Inter-Device Eth-Trunks

Networking Requirements

A network often uses link redundancy designs to improve link reliability, but link redundancy may cause loops on the network. Stacks can increase link bandwidth and improve link reliability while preventing loops on a network.

As shown in Figure 2-32, aggregation switches SwitchA and SwitchB set up a stack. SwitchA is the master switch, and SwitchB is the standby switch. The stack connects to the upstream and downstream devices through Eth-Trunks.
Figure 2-32 Inter-device Eth-Trunk networking
Configuration Roadmap
The configuration roadmap is as follows:
  1. Add the links that connect the stack to the upstream and downstream devices to inter-device Eth-Trunks. This configuration improves link bandwidth and reliability, while preventing loops on the network.

  2. Enable local preferential forwarding on the Eth-Trunks to improve forwarding efficiency and reduce loads on the stack links between stack member switches.

NOTE:

In Smart Channel mode, VLANs of the port with DAD must be different from those of the Smart Channels. If a Smart Channel fails, the ports in the VLANs of the Smart Channel are disabled (error-down), and therefore the ports cannot provide the DAD function. It is recommended that you use the operations described in Configuring DAD Through Management Interfaces.

Procedure

  1. Configure inter-device Eth-Trunks.

    # On the stack, create Eth-Trunk10, Eth-Trunk20, and Eth-Trunk30, and add the interfaces connected to the upstream and downstream devices to the Eth-Trunks.

    <HUAWEI> system-view
    [~HUAWEI] sysname iStack
    [*HUAWEI] commit
    [~iStack] interface eth-trunk 10
    [*iStack-Eth-Trunk10] trunkport 10ge 1/17/5
    [*iStack-Eth-Trunk10] trunkport 10ge 2/17/5
    [*iStack-Eth-Trunk10] quit
    [*iStack] interface eth-trunk 20
    [*iStack-Eth-Trunk20] trunkport 10ge 1/17/6
    [*iStack-Eth-Trunk20] trunkport 10ge 2/17/6
    [*iStack-Eth-Trunk20] quit
    [*iStack] interface eth-trunk 30
    [*iStack-Eth-Trunk30] trunkport 10ge 1/17/7
    [*iStack-Eth-Trunk30] trunkport 10ge 2/17/7
    [*iStack-Eth-Trunk30] quit
    [*iStack] commit

    # On SwitchC, create Eth-Trunk10 and add 10GE1/17/1 and 10GE1/17/2 connected to the stack to Eth-Trunk10.

    <HUAWEI> system-view
    [~HUAWEI] sysname SwitchC
    [*HUAWEI] commit
    [~SwitchC] interface eth-trunk 10
    [*SwitchC-Eth-Trunk10] trunkport 10ge 1/17/1
    [*SwitchC-Eth-Trunk10] trunkport 10ge 1/17/2
    [*SwitchC-Eth-Trunk10] quit
    [*SwitchC] commit

    # The configurations on SwitchD and SwitchE are similar to the configuration on SwitchC, and are not mentioned here.

  2. Enable local preferential forwarding on the stack.

    [~iStack] interface eth-trunk 10
    [~iStack-Eth-Trunk10] undo local-preference disable
    [*iStack-Eth-Trunk10] quit
    [*iStack] interface eth-trunk 20
    [*iStack-Eth-Trunk20] undo local-preference disable
    [*iStack-Eth-Trunk20] quit
    [*iStack] interface eth-trunk 30
    [*iStack-Eth-Trunk30] undo local-preference disable
    [*iStack-Eth-Trunk30] quit
    [*iStack] commit
    [~iStack] quit
    NOTE:

    By default, local preferential forwarding is enabled on an Eth-Trunk.

  3. Verify the configuration.

    After the configuration is complete, run the display eth-trunk membership trunk-id command in any view to view information about member interfaces of the Eth-Trunks. Information about member interfaces of Eth-Trunk10 on the stack is used as an example.

    <iStack> display eth-trunk membership 10
    Trunk ID: 10
    Used Status: Valid
    Type: Ethernet
    Working Mode: Normal
    Number Of Ports in Trunk: 2
    Number Of Up Ports in Trunk: 2
    Operating Status: up
    
    Interface 10GE1/17/5, valid, operate up, weight=1
    Interface 10GE2/17/5, valid, operate up, weight=1
    

Configuration Files
  • Configuration file of the stack

    #
    sysname iStack
    # 
    interface Eth-Trunk10
    #  
    interface Eth-Trunk20
    #  
    interface Eth-Trunk30
    #  
    interface 10GE1/17/5 
     eth-trunk 10
    # 
    interface 10GE1/17/6 
     eth-trunk 20
    # 
    interface 10GE1/17/7 
     eth-trunk 30
    # 
    interface 10GE2/17/5 
     eth-trunk 10
    #
    interface 10GE2/17/6 
     eth-trunk 20
    #
    interface 10GE2/17/7 
     eth-trunk 30
    # 
    return
    
  • Configuration file of SwitchC

    #
    sysname SwitchC
    # 
    interface Eth-Trunk10
    #  
    interface 10GE1/17/1 
     eth-trunk 10
    # 
    interface 10GE1/17/2 
     eth-trunk 10
    #
    return
    
  • Configuration file of SwitchD

    #
    sysname SwitchD
    # 
    interface Eth-Trunk20
    #  
    interface 10GE1/17/1 
     eth-trunk 20
    # 
    interface 10GE1/17/2 
     eth-trunk 20
    #
    return
    
  • Configuration file of SwitchE

    #
    sysname SwitchE
    # 
    interface Eth-Trunk30
    #  
    interface 10GE1/17/1 
     eth-trunk 30
    # 
    interface 10GE1/17/2 
     eth-trunk 30
    #
    return
    
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59266

Downloads: 3623

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