
204 MergePoint 5224/5240 Service Processor Manager Installer and Administrator Guide
The single-user prompt appears, as shown in the following example.
U-Boot network boot options and caveats
When a network boot is performed with the U-boot net_boot command, the SP manager boots
from the specified image on the TFTP server. The image uses the RAM as the root file system.
Network boots are useful for troubleshooting because the net
-booted image can run even if the SP
manager’s Flash memory is not usable.
Network boots are recommended only for troubleshooting and must not be used for normal
operation of the SP manager. For example, if you want to test a new release of the software to make
sure a problem is fixed, or if the removable Flash memory becomes corrupted, you could download
the software to a tftpboot server and then save it to the removable Flash after testing, using the
create_cf command with the appropriate options (see Options for the create_cf command on
page 205).
When a network boot is performed, the system uses one of the two following sources of
configuration data:
• If the net_boot command is entered with the configsource=factory_default option, the
factory_default configuration files are loaded.
• Otherwise, the backed up configuration files from the /dev/hda3 backup partition are copied to
the RAMDISK and used.
Any configuration changes made after the last backup copy was made are lost unless the
configuration files were backed up before the network boot and then restored afterwards (see
Backing Up Configuration Files on page 129 and Restoring Backed Up Configuration Files on
page 129).
To upgrade to a boot image from a network boot:
Before performing this procedure, make sure that a copy of the latest boot image has been
downloaded from the Avocent ftp site to a TFTP server that is accessible to the SP manager.
1. Boot in U
-boot monitor mode. If needed, see To boot in U-Boot monitor mode: on page 203.
2. Use the
setenv command to set the ipaddr, serverip and bootfile environment variables.
The format of the boot filename is:
fl<seven_digit_version_number>.bin. In the following
example, the filename
fl2222222.bin is used,
[root@(none) /]#
=> setenv ipaddr SPmanager_IPaddress
=> setenv serverip boot_server_IPaddress
=> setenv bootfile boot_filename
=> setenv ipaddr 192.168.45.29
=> setenv serverip 192.168.45.127
=> setenv bootfile fl2222222.bin
Commentaires sur ces manuels