Management | 69
Recovering from a Failed Start
A system that does not start correctly might be attempting to boot from a corrupted FTOS image or from a
mis-specified location. In that case, you can restart the system and interrupt the boot process to point the
system to another boot location.
For more information about the
setenv command, its supporting commands, and other commands that can
help recover from a failed start, refer to the Boot User chapter in the FTOS Command Line Reference for
the MXL 10/40GbE Switch IO Module.
To recover from a failed start using the
setenv command, follow these steps:
2 Power-cycle the chassis by switching off all of the power modules and then switching them back on.
3 Hit any key to abort the boot process.
You enter uBoot immediately, as
indicated by the => prompt.
hit any key (during bootup)
4 Set the system parameters to ignore
the enable password when the system
reloads.
setenv enablepwdignore true
uBoot
5 Reload the system.
reset
uBoot
6 Configure a new enable password. enable {secret | password} CONFIGURATION
7 Save the running-config to the
startup-config.
copy running-config startup-config
EXEC Privilege
Step Task Command Syntax Command Mode
1 Power-cycle the chassis (pull the power cord and reinsert it).
2 Hit any key to abort the boot process.
You enter uBoot immediately, as
indicated by the => prompt.
hit any key (during bootup)
3 Assign the new location to the FTOS
image to be used when the system
reloads.
setenv [primary_image f10boot location |
secondary_image f10boot location |
default_image f10boot location]
uBoot
4 Assign an IP address to the
Management Ethernet interface.
setenv ipaddre address uBoot
5 Assign an IP address as the default
gateway for the system.
setenv gatewayip address
uBoot
6 Reload the system.
reset
uBoot
Step Task Command Syntax Command Mode
To Next Page
Loading...
Need help?
General
