Troubleshooting Image Copy Issues; Configuration, Startup Configuration Files, And Stacking Flash - Arris Ruckus ICX 7850 Series Configuration Manual

4. To reset hardware and memory, enter the powercycle command at the boot prompt. This causes the system to execute
a cold boot as shown in the following example.
ICX77xx-Boot> powercycle
Bootloader Version: 10.1.01T205 (Jun 11 2014 - 16:29:55)
SVR: 0x82180111, PVR: 0x80230022
Sidewinder:48C,A1
SYS CPLD VER: 0xe, Released Ver: 0
Enter 'b' to stop at boot monitor:
bootdelay: ===
Booting image from Secondary
## Booting kernel from Legacy Image at 0300a200 ...
Created:
Data Size:
Load Address: 00000000
Entry Point:
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
setup_arch: bootmem

Troubleshooting image copy issues

The copy tftp flash command copies the image to all stack units including the active controller. The copy flash flash command
copies the image from the primary or secondary flash on the active controller to the primary or secondary flash image of a stack
member. If you are unable to copy an image to one or more stack units, check the following:
• Make sure the unit is actually part of the stack. Use the show stack command.
• If a unit joins a stack after the image copy command was issued, you will need to copy the image to this unit separately.
Configuration, startup configuration files, and
stacking flash
Stacking system behavior is defined by the runtime configuration, which can be displayed using the show running-config
command. The write memory command stores the runtime configuration in a flash file called startup-config.txt. During bootup,
the system reads and applies the startup-config.txt file to the runtime configuration. The startup-config.txt file can be shown
using the show config command.
The stacking system installs a stacking.boot file on each unit that tells the unit what its role is during the boot process. The
stacking.boot file is generated whenever there is an election that defines the roles for all units.
When an active controller is booted or a write memory command is issued, the active controller synchronizes its startup-
config.txt file to every stack unit. The original startup-config.txt files in the standby controller and other stack members are
renamed to startup-config.old. If you issue the stack unconfigure me command on the standby controller or stack member
directly, these units recover their original startup-config.txt files and reboot as standalone devices. If you enter the stack
unconfigure all command from the active controller, all devices recover their old startup-config.txt files and become standalone
devices. When this happens, the startup-config.old file is renamed to startup-config.txt, and the stacking.boot file is removed.
Whenever a stack unit configuration parameter, such as the priority setting, is changed, an election is held to determine the
active controller, and the result is written into the stacking.boot file. A prompt message appears on the console that
recommends you use the write memory command. For an active controller role change to take effect, you must reset the entire
stack.
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01
0
2015-02-19 6:23:46 UTC
17787567 Bytes = 17 MiB
00000000

Configuration, startup configuration files, and stacking flash

ICX Stack Troubleshooting
243