NOTE
The image-file-name-on-device variable is case-insensitive and converts any uppercase characters
in the image file name to lowercase characters.
For example:
C:\> scp FCXR08000.bin terry@10.168.1.50:flash:primary
or
C:\> scp FCXR08000.bin terry@10.168.1.50:flash:pri:FCXR08000.bin
or
C:\> scp FCXR08000.bin terry@10.168.1.50:flash:secondary
or
C:\> scp FCXR08000.bin terry@10.168.1.50:flash:sec:FCXR08000.bin
NOTE
On ICX 6430 and ICX 6450 devices, you can use the same syntax as for FCX devices. However,
after the copy operation is completed at the host, you do not get the command prompt back because
the device is synchronizing the image to flash. To ensure that you have successfully copied the file,
enter the show flash command. If the copy operation is not complete, the show flash command
output shows the partition (primary or secondary) as EMPTY.
4. Verify that the flash code has been successfully copied onto the device by using the show flash
command at any level of the CLI.
5. Reboot the device using the reload or boot system command.
6. Verify that the new flash image is running on the device by using the show version command.
Software recovery
If the software upgrade or downgrade fails, the device may reboot continuously as shown in the
following CLI ouput:
bootdelay: ===
Booting image from Primary
Bad Magic Number
could not boot from primary, no valid image; trying to boot from secondary
Booting image from Secondary
Bad Magic Number
## Booting image at 01ffffc0 ...
Bad Magic Number
## Booting image at 01ffffc0 ...
Bad Magic Number
could not boot from secondary, no valid image; trying to boot from primary
Booting image from Primary
Bad Magic Number
## Booting image at 01ffffc0 ...
Bad Magic Number
This section explains how to recover devices from image installation failure or deleted or corrupted flash
images.
Software recovery
FastIron Ethernet Switch Software Upgrade Guide 33
53-1003632-02
To Next Page
Loading...
Need help?
General
