Valid-stack-port Sets
RUCKUS stacking systems support flexible stacking ports. Most platforms allow users to select stacking ports from a list of ports. The ports that are not used as stacking ports can be used as data ports. The stacking port selection cannot be arbitrary. It must follow rules that respect the defined valid-stack-port set (a/b/c, a/b/d, n), where a/b/c and a/b/d are the starting ports of two directions, and n is the maximum number of ports in a stacking trunk. Some platforms support multiple valid-stack-port sets.
RUCKUS supports linear or ring topologies. A unit has one direction (in a typical linear
topology) or two directions (in a ring). Each direction contains one or multiple stacking
ports. The command
stack-port
unit/slot/port contains one port, and the command
stack-trunk
unit/slot/port
to
unit/slot/port uses multiple contiguous ports.
In FastIron 08.0.90 or later, you must observe the following rules to configure the
stack-port or
stack-trunk command related to the valid-stack-port set.
- A stack-port must be a port in the valid-stack-port set. For example, the configuration
stack-port 1/2/4is allowed, butstack-port 1/2/2is not allowed. - A stack-trunk must contain contiguous ports starting from one port in the valid-stack-port
set. For example, the configuration
stack-trunk1/3/1 to 1/3/5 satisfies the valid-stack-port set (x/2/1, x/3/1, 6), but the configurationstack-trunk1/3/2 to 1/3/4 is invalid. - The number of ports in a
stack-trunkconfiguration cannot exceed the number defined in the valid-stack-port set. - The
stack-portand thestack-trunkconfiguration for a unit must originate from the same valid-stack-port set. For example, the configurationstack-port1/2/1 andstack-trunk1/3/1 to 1/3/6 satisfies the valid-stack-port set (1/2/1, 1/3/1, 6). The configurationstack-port1/2/1 andstack-port1/3/4 is invalid because the two stacking ports originate in different valid-stack-port sets. - Adding
stack-portorstack-trunkconfiguration may cause the removal of existingstack-portorstack-trunkconfiguration if the new configuration is not contained in the same valid-stack-port set. For example, suppose a unit configuration containsstack-port1/2/1 andstack-port1/2/4. If you configurestack-port1/3/1, the system removes stack-port 1/2/4 and keeps 1/2/1 because port 1/2/1 and port 1/3/1 satisfy the valid-stack-port set (1/2/1, 1/3/1, 6). If you configurestack-port1/3/4, the system removes both old stack-ports because no valid-stack-port set contains both the ports in the new configuration, 1/2/x and 1/3/4. - If adding
stack-portorstack-trunkconfiguration would cause the removal of a live stacking port or stacking trunk, the command entry is denied. For example, suppose a unit has a live link 1/3/1 to another unit. If you were to configurestack-port1/2/4, it would cause the removal of 1/3/1 because the port combination (1/2/4, 1/3/1) is not contained in any valid-stack-port set. In this case, the system prints an error message and denies the configuration as shown in the following example.ICX7750-26Q Router# configure terminal ICX7750-26Q Router(config)# stack unit 1 ICX7750-26Q Router(config-unit-1)# stack-port 1/2/4 Error! It may break the link 1/3/1 -- 2/3/1. If the link is not needed, please unplug cables and remove the configuration of both ends. stack-port 1/2/4 would remove stack-port 1/3/1 to satisfy (1/2/1, 1/2/4, 3).