Combining Standalone Switches into a CSS

Created: Feb 28, 2019 15:48:13 27 0 0 0

Networking Requirements

Two modular switches at the aggregation layer use VRRP and STP to implement gateway backup. To simplify the configuration, the two modular switches need to be combined into a logical CSS.

In Figure 4-25, S1 and S2 at the aggregation layer are two standalone switches and need to be combined into a CSS to simplify configuration and facilitate maintenance and management.

Figure 4-25  Networking diagram of combining standalone switches into a CSS 
imgDownload?uuid=9d6928f07b34484ebea7c8d
When two standalone devices are combined into a CSS, major configuration changes include:
  • The VRRP gateway backup protocol deployed at the aggregation layer is not required and its configuration needs to be deleted.
  • The STP loop prevention protocol deployed at the access layer is not required and its configuration needs to be deleted.
  • The links at the access, aggregation, and core layers are changed to Eth-Trunks, and related interface configurations need to be changed, including basic VLAN configuration, QoS configuration, and ACL configuration.

Guidelines

  • After the CSS function is enabled on a standalone switch, configurations on the interfaces of the switch will be lost. Therefore, back up the configuration file before enabling the CSS function.
  • The following procedure provides only the related configurations. Whether other configurations need to be changed depends on the actual networking.

Procedure

  1. In the original networking, traffic at the access layer is load-balanced among multiple links through STP and VRRP. In Figure 4-26, some traffic is forwarded through S1 and some traffic is forwarded through S2.

    Figure 4-26  Existing traffic forwarding 
    imgDownload?uuid=6f816418a987476f91c066c

  2. Manually shut down the uplink and downlink ports of S2 to change the STP and VRRP status so that S2 is isolated from the network and all traffic is forwarded through S1, as shown in Figure 4-27.

    Figure 4-27  Traffic forwarding after an STP and VRRP status switchover 
    imgDownload?uuid=7eb5ddeaa91c40589e8938b

  3. Back up the configuration file of S2. After the CSS function is enabled on a standalone switch, the interface number format on the switch is changed from slot ID/subcard ID/port number to stack member ID/slot ID/subcard ID/port number, and the configurations on the interfaces of the switch are lost.
  4. Change S2 to the CSS state.

  5. Change the configuration of S2, which has been changed to a single-chassis cluster CSS-1. Alternatively, change the configuration after S1 and S2 are combined into a CSS. Changing the configuration of S2 before S1 and S2 are combined into a CSS can reduce the traffic loss.

    Figure 4-28  Single-chassis CSS 
    imgDownload?uuid=4fcc7dfdbcd54a7abb1d1f9
    1. Bind uplink ports XGE1/4/0/1 and XGE1/4/0/2 of CSS-1 to Eth-Trunks and move the configurations of these ports to the Eth-Trunks.

      For example: The configurations on the original ports (connecting CSS-1 to devices at the core layer) are as follows:
      #
      interface XGigabitEthernet4/0/1
       undo portswitch                                                                                                                    
       ip address 192.168.4.2 255.255.255.0 
      #
      interface XGigabitEthernet4/0/2
       port link-type trunk                                                                                                               
       port trunk allow-pass vlan 100 200
      #
      Change the configurations.
      <S2> system-view[S2] sysname CSS  // Change the device name to facilitate maintenance.[CSS] interface eth-trunk 20  // Add the port connecting the CSS to a core device to Eth-Trunk 20.[CSS-Eth-Trunk20] trunkport xgigabitethernet1/4/0/1[CSS-Eth-Trunk20] ip address 192.168.4.2 255.255.255.0[CSS-Eth-Trunk20] quit[CSS] interface eth-trunk 10  // Add the port connecting the CSS to another core device to Eth-Trunk 10.[CSS-Eth-Trunk10] trunkport xgigabitethernet1/4/0/2[CSS-Eth-Trunk10] port link-type trunk[CSS-Eth-Trunk10] port trunk allow-pass vlan 100 200[CSS-Eth-Trunk10] quit
    2. Change the configurations of devices at the core layer and access layer and bind physical ports to Eth-Trunks. The procedure is similar to the preceding procedure.

    3. Delete the VRRP configuration on CSS-1.

      For example, the configurations of VLANIF interfaces are as follows:
      #
      interface Vlanif100
       ip address 10.1.10.1 255.255.255.0
       vrrp vrid 1 virtual-ip 10.1.10.111
       vrrp vrid 1 priority 120
      #
      interface Vlanif200
       ip address 10.1.20.1 255.255.255.0
       vrrp vrid 2 virtual-ip 10.1.20.111
      #
      Delete the configurations of VLANIF interfaces.
      [CSS] interface vlanif 100[CSS-Vlanif100] undo vrrp vrid 1[CSS-Vlanif100] undo ip address[CSS-Vlanif100] quit[CSS] interface vlanif 200[CSS-Vlanif200] undo vrrp vrid 2[CSS-Vlanif200] undo ip address[CSS-Vlanif200] quit
    4. Delete unnecessary network segments from the OSPF routing domain.
    5. Change the configurations of the interfaces on which QoS and ACLs are configured to bind these interfaces to Eth-Trunks.
    6. Change the STP priority of CSS-1 so that CSS-1 becomes the root switch of all VLANs.

  6. Run the undo shutdown command to disable the interfaces on CSS-1 to check whether Layer 2 and Layer 3 forwarding between CSS-1 and devices at the access layer and core layer is normal.
  7. After confirming that Layer 2 and Layer 3 forwarding between CSS-1 and devices at the access layer and core layer is normal, shut down interfaces on S1 so that S1 is isolated from the network and all traffic is forwarded through CSS-1.

    Figure 4-29  Traffic switched to CSS-1 
    imgDownload?uuid=ee70b61d50e04cadae7ad4c

  8. Change S1 to the CSS state. After S1 is added to CSS-1, S1 uses the configuration file of CSS-1.

  9. S1 is changed to CSS-2 and becomes the stack standby.

    Figure 4-30  Two CSS systems merging into one 
    imgDownload?uuid=c44c104a014f4e018fc7fdb

  10. Change the configurations of CSS-2 and add interfaces of CSS-2 to Eth-Trunks.

    1. Add uplink ports XGE2/4/0/1 and XGE2/4/0/2 of CSS-2 to Eth-Trunks.

      [CSS] interface eth-trunk 20[CSS-Eth-Trunk20] trunkport xgigabitethernet2/4/0/1[CSS-Eth-Trunk20] quit[CSS] interface eth-trunk 10[CSS-Eth-Trunk10] trunkport xgigabitethernet2/4/0/2[CSS-Eth-Trunk10] quit
    2. Change the configurations of devices at the core layer and access layer and bind physical ports to Eth-Trunks. The procedure is similar to the preceding procedure.

  11. Run the undo shutdown command to disable the interfaces of CSS-2 and check whether Layer 2 and Layer 3 forwarding between CSS-2 and devices at the core layer and access layer is normal. In this case, S1 and S2 have been combined into a CSS, as shown in Figure 4-31.

    Figure 4-31  Traffic forwarding after a CSS merge 
    imgDownload?uuid=e0b5295b50c6456b8f5bb46

See more please click 

https://support.huawei.com/enterprise/en/doc/EDOC1000069520/9aadccc0/comprehensive-configuration-examples


  • x
  • convention:

Reply

Reply
You need to log in to reply to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Fast reply Scroll to top