HP A7500 Series Command Reference Manual page 126

To execute the boot-loader command successfully, save the file for the next device boot in the root
•
directory of the storage media on the active MPU.
• If the storage media is on the active MPU, specify the storage media by giving its name, such as
flash.
If the storage media is on the standby MPU, specify the storage media by giving its name and the
•
slot-number of the standby MPU, in the format of slotslot-number#StorageMediumName, where
slot-number represents the number of the slot in which the card resides, such as slot1#flash.
When you specify the system software image for the active MPU, the file-url argument cannot
•
contain a slot number, and slot-number should be specified as the slot number of the active MPU.
• When you specify the system software image for the standby MPU, the file-url argument must
contain a slot number (such as slot1#flash:/test.app), and slot-number should be specified as the
slot number of the standby MPU.
The names of the files for the next boot of the active MPU and the standby MPU may be different,
•
but the versions of the files must be the same. Otherwise, the device may not boot normally.
Related commands: display boot-loader.
In IRF mode
2.
Use the boot-loader command to specify a system software image for the next boot of an MPU on a
member switch.
To execute the boot-loader command successfully, save the file for the next device boot under an
•
MPU's root directory of the storage media on a specified member switch.
• If the storage media is on the active MPU of the IRF fabric (the active MPU of the master), specify the
storage media by giving its name, such as flash.
If the storage media is on the standby MPU of the IRF fabric (any MPUs except the active MPU of the
•
IRF fabric), specify the storage media by giving its device ID and the slot-number of the card, in the
format of chassischassis-number#slotslot-number#, such as chassis2#slot1#flash.
When you specify the system software image for the next boot of the active MPU of the IRF fabric,
•
the file-url argument cannot contain a member ID or a slot ID, chassis-number should be specified
as the member ID of the master, and slot-number should be specified as the slot number of the active
MPU of the IRF fabric.
When you specify the system software image for the next boot of a standby MPU of the IRF fabric,
•
the file-url argument must contain the slot number of the card and the member ID of the member
switch where the MPU resides, such as chassis3#slot1#flash:/test.app, chassis-number should be
specified as the member ID of the IRF member switch, and slot-number should be specified as the
slot number of the card.
The names of the files for the next boot of the active MPU and standby MPU of the IRF fabric may
•
be different, but the versions of the files must be the same. Otherwise, the standby MPU cannot join
the IRF fabric again.
Related commands: display boot-loader.
Examples
# Specify the main system software image for the active MPU (the slot number is 0) for the next device
boot as test.app (Make sure that the file test.app is already saved on the storage media of the active MPU.
Otherwise, the system prompts error and the execution of the command fails). (In standalone mode)
<Sysname> boot-loader file test.app slot 0 main
This command will set the boot file of the specified board. Continue? [Y/N]:y
The specified file will be used as the main boot file at the next reboot on slot 0!
119