Stacking support of S series fixed switch

3

The S7706/S7712, S9706/S9712, S12704/S12708/S12712, and S9306/S9312 support CSS, but S7703, S9703, and S9303 do not support CSS. Only the switches of the same series can set up a CSS. For example, an S7706 can set up a CSS with S7706 or S7712, but cannot set up a CSS with S9706.
A CSS can contain a maximum of two switches.
The S7706/S7712, S9706/S9712, and S9306/S9312 support both cluster card CSS and service port CSS. The S12700 supports only cluster card CSS. The S7706/S7712 have supported cluster card CSS since V1R6 and service port CSS since V2R2. The S9706/S9712 have supported cluster card CSS since V2R3 and service port CSS since V2R1C01. The S9306/S9312 have supported cluster card CSS since V1R3 and service port CSS since V2R2. The S12708/S12712 have supported cluster card CSS since V2R5 and S12704 has supported cluster card CSS since V2R8.
To set up a CSS through cluster cards, the customer needs to buy the cluster cards. To set up a CSS through service ports on S9306/S9312, the customer needs to apply for the license (the other models do not need license).
The CSS support, clustering modes, software and hardware requirements, typical networking, and configuration procedures on all models are provided in Typical CSS Configuration of Typical Configuration Examples.
For the CSS support on S7700&S9700, see Software and Hardware Requirements for the CSS Card Connection Mode and Software and Hardware Requirements on the Service Port Connection Mode in Typical Configuration Examples-Typical CSS Configuration.
For the CSS support on S12700, see Software and Hardware Requirements for the CSS Card Connection Mode and Software and Hardware Requirements on the Service Port Connection Mode in Typical Configuration Examples-Typical CSS Configuration.
For the CSS support on S9300, see Software and Hardware Requirements for the CSS Card Connection Mode and Software and Hardware Requirements on the Service Port Connection Mode in Typical Configuration Examples-Typical CSS Configuration.

Other related questions:
Advantages of stacks of S series fixed switches
Stacking technology provides high network reliability and forwarding performance while simplifying network management. It has the following advantages: 1. High reliability: Member switches in a stack work in redundancy mode. Link redundancy can also be implemented between member switches through inter-device link aggregation. 2. High scalability: You can increase ports, bandwidth, and processing capacity of a stack by simply adding member switches to the stack. Member switches can join or leave the stack without affecting other member switches. New switches automatically synchronize the configuration file and system software version with the master switch. 3. Simpler configuration and management: You can log in to a stack from any member switch to manage and configure all the member switches in the stack. In addition, complicated Layer 2 ring protection protocols or Layer 3 protection switching protocols are not required after switches set up a stack; therefore, the network configuration is much simpler.

Upgrade stacks of S series fixed switches
You can upgrade a stack of S series fixed switches using either of the following methods: Traditional upgrade: All member switches in the stack need to restart. This upgrade method causes service interruption in a relatively long time and can be used in scenarios insensitive to the service interruption time. Upgrade procedure 1. Upload system software to the master switch in the stack. 2. Run the startup system-software system-file all command to set the next startup software for all member switches in the stack. 3. Run the reboot command to upgrade the stack by restarting the entire system. Smooth upgrade: Member switches in a stack can be divided into an active area and a backup area that back up each other. Member switches in the two areas are upgraded in turn. During the upgrade of an area, traffic is transmitted through the other area, minimizing the impact of the upgrade on services. This upgrade method applies to scenarios sensitive to the service interruption time. The stack and networking must meet the following requirements: The uplinks and downlinks work in redundancy mode. The system software for next startup supports the smooth upgrade function. Member switches in the stack are running the same system software with the same software package name, version, and path. Member switches in the stack have the same system software for next startup with the same software package name, version, and path. Upgrade procedure 1. Upload system software to all the member switches in the stack. Ensure that member switches have the same system software with the same software package name, version, and path. 2. Run the system-view command to enter the system view. 3. Run the upgrade backup-area slot slot-id to slot-id command to define the active and backup areas for a smooth upgrade. The member switches with stack IDs in the specified range join the backup area, and the other member switches automatically join the active area. Note: Follow these rules to define the active and backup areas in a stack: The active and backup areas cannot contain the same member switch, and both areas must have at least one member switch. The backup area cannot contain the master switch. Member switches in each area must be directly connected. Member switches in the active and backup areas form the entire stack. 4. (Optional) Run the display upgrade area command to check whether the configured areas meet the requirements of the current stack topology. If the stack topology changes after the areas are configured, the smooth upgrade will fail. To avoid this problem, check the area configuration before starting a smooth upgrade. If the areas fail the check, redefine the active and backup areas correctly according to the current stack topology. 5. Run the upgrade start command to enable a smooth upgrade. 6. (Optional) Run the display upgrade state [ slot slot-id ] command to check the smooth upgrade status.

Service ports on S series fixed switches that support stacking
For details about service ports on S series fixed switches that support stacking, click Typical Configuration Examples and choose Typical Stack Configuration of Fixed Switches- Determining the Stack Connection Mode and Hardware and Software Requirements. This section describes whether each model and version of S series fixed switches supports stacking as well as stack modes, hardware and software requirements, typical networking, and configuration steps to set up stacks.

Change stack IDs of S series fixed switches of a stack
To change the stack ID of an S series fixed switch (except the S1700 switch) of a stack, run the stack slot slot-id renumber new-slot-id command. Ensure that the new stack ID is unique in the stack. After changing the stack ID, restart the switch to make the setting take effect.

Split stacks of S series fixed switches
Split a stack of S series fixed switches that is established in stack card connection mode as follows: 1. Run the save command to save the configuration. 2. Run the copy source-filename destination-filename all command to back up the configuration file to all the member switches. 3. Remove stack cables between the member switches. After the stack cables are disconnected, the stack splits. Part of the member switches restart. Remote login may fail because configurations such as the IP address of the stack member switches are the same. Log in to a switch through the console port and perform the following operations. 4. Run the system-view command to enter the system view. 5. Run the stack slot slot-id renumber 0 command to restore the stack ID of the member switch to the default value 0. 6. Power off all the member switches. 7. Remove the stack card. Split a stack of S series fixed switches that is established in service port connection mode as follows: 1. Run the save command to save the configuration. 2. Run the copy source-filename destination-filename all command to back up the configuration file to all the member switches. 3. Remove stack cables between the member switches. After the stack cables are disconnected, the stack splits. Part of the member switches restart. Remote login may fail because configurations such as the IP address of the stack member switches are the same. Log in to a switch through the console port and perform the following operations. 4. Run the system-view command to enter the system view. 5. Run the interface stack-port member-id/port-id command to enter the logical stack port view. 6. Run the shutdown interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> command to disable the physical member port. 7. Run the undo port interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> enable command to restore the physical member port to a service port. 8. Run the quit command to exit from the logical stack port. 9. Run the stack slot slot-id renumber 0 command to restore the stack ID of the member switch to the default value 0. 10. Power off all the member switches. Note: Steps 5 to 7 are performed to restore a stack port to a service port, and the operations are performed based on versions later than V200R002. For details about configuration in V200R002 and earlier versions

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top