Administration: Stack Management
Stack Ports
127
Cisco 350, 350X and 550X Series Managed Switches, Firmware Release 2.4, ver 0.4
8
Reconnecting the Original Master Unit After Failover
After failover, if the original master is connected again, the master selection process is
performed. If the original master (unit 1) is reselected to be the master, the current master (unit
2, which was the original backup unit) is rebooted and becomes the backup once again.
NOTE
During master failover, the uptime of the backup unit is retained.
Stack Ports
All ports on the device are network ports by default. To connect units, you must change the
types of the ports to be used to connect the devices as stack ports. These ports are used to
transfer data and protocol packets among the units
You must indicate to the system (reserve) which ports you plan to use as stack ports (in the
page).
The following ports can be stack ports:
•
XG Devices
(all ports support the 10Gigabit speed)—All ports can be stack ports.
•
X Devices
(Only uplink ports support the 10Gigabit speed)—Only the four XG uplink
ports can be stack ports.
Stack Port Link Aggregation
When two neighboring units are connected with multiple stack links, the stack ports
connecting them are automatically assigned to a stack LAG. This feature enables increasing
the stack bandwidth of the stack port beyond that of a single port.
There can be up to two stack LAGs per unit.
The stack LAG can be composed of between two and up to the maximum number of stack
ports depending on the unit type.
On the Sx550X/SG350 devices, up to two interfaces can compose a stacking LAG between 2
units. The allowed interface combination for the same stacking LAG is either interfaces XG1
and XG2 or interfaces XG3 and XG4. Other combination of interlaces in the same stack LAG
is not supported.
