Copying The Flash Image To A Stack Unit From The Active Controller; Configuring Stacking Trunks In A Live Environment - Arris Ruckus ICX 7850 Series Configuration Manual

Copying the flash image to a stack unit from the active controller

You can replace a bad image on a stack unit or an image that does not match the active controller's image by copying the correct
flash image from the active controller.
NOTE
In most cases, you do not have to manually copy the flash image to a mismatched stack unit. For more information,
refer to Auto Image Copy for stack units
To copy the flash image to the primary flash memory of a stack unit from the active controller primary flash, enter the copy flash
flash command followed by the keyword unit-id-pri and the stack unit number as shown in the following example.
device# copy flash flash unit-id-pri 2
The example copies active controller primary flash to the primary flash for stack unit 2.
You can also copy flash to more than one stack unit at the same time as shown in the following example.
device# copy flash flash unit-id-pri 2,3,5-8
The example copies active controller primary flash to stack units 2 and 3 and 5 through 8.
Use the keyword unit-id-sec to copy from active controller primary flash as shown in the following example.
copy flash flash unit-id-sec 2-4
The example copies active controller secondary flash to stack units 2 through 4.
For additional information on copy flash commands, refer to the Ruckus FastIron Command Reference.
Configuring stacking trunks in a live
environment
To create or modify a trunk in a production environment, use the multi-stack-trunk command. The multi-stack-trunk
command is used to ensure that a stack trunk is formed on two directly connected stack units at the same time. The multi-
stack-trunk command can only be enabled on the active controller unit.
By configuring a multi-stack-trunk on two sets of connected stack ports, a trunk-to-port connection is avoided. A trunk-to-port
connection is formed when one side of the ports forms a trunk, and the other side of the ports does not. A trunk-to-port
connection can result in dropped packets and can potentially break a stacking link.
The following example shows a trunk being formed between stack units 1 and 2 and another trunk being formed between stack
units 2 and 3.
device(config)# stack unit 1
device(config-unit-1)# multi-stack-trunk 1/2/3 to 1/2/4 and 2/2/1 to 2/2/2
device(config-unit-1)# stack unit 2
device(config-unit-2)# multi-stack-trunk 2/2/3 to 2/2/4 and 3/2/1 to 3/2/2
Use the no form of the multi-stack-trunk command to remove the stacking trunk configuration.
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01
on page 206.

Configuring stacking trunks in a live environment

Stack Management
207