4-2
z
To execute the
boot-loader
command successfully, you must save the file for the next device
boot under the root directory of the storage media on a member device.
z
If the storage medium is on the master, you can specify the storage medium by giving its name,
such as
flash
; if the storage medium is on a slave, you can specify the storage medium by giving
its name and the member ID of the device, that is, in the format of slot
slot-number#
StorageMediumName
(
slot-number
represents the member ID of the salve), such as
slot2#flash
.
z
When you specify the boot file of the master, the
file
-
url
argument cannot contain the member ID
of the device, and
slot-number
should be specified as the member ID of the master; when you
specify the boot file of the slave, the
file
-
url
argument must contain the member ID (such as
slot2#flash:/test.bin
), and
slot-number
should be specified as the member ID of the slave.
z
If you provide the keyword
all
, the
file
-
url
argument cannot contain a member ID, otherwise, the
execution of this command will fail; you must save the specified boot file on the storage media of
all member devices in the same filename, otherwise, member devices without this file will fail to be
reconfigured during the reboot.
z
The names of the files for the next boot of the master and slaves may be different, but the versions
of the files must be the same; otherwise, a slave will reboot by using the master's boot file and join
the stack again.
Related commands:
display boot-loader
.
Examples
# Specify the main boot file for the master (the member ID is 1) for the next device boot as
test.bin
(Make sure that the file
test.bin
is already saved on the storage medium of the master; otherwise, the
system prompts error and the execution of the commend fails).
<Sysname> boot-loader file test.bin slot 1 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 1!
# Specify the main boot file for the slave (the member ID is 2) for the next device boot as
test.bin
(Make sure that the file
test.bin
is already saved on the storage medium of the slave; otherwise, the
system prompts error and the execution of the commend fails).
<Sysname> boot-loader file slot2#flash:/test.bin slot 2 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 2!
# Specify the main boot file for all member devices for the next device boot as
test.bin
(Make sure that
the file
test.bin
is already saved on the storage media of all the member devices; otherwise, the
system prompts error and the execution of the commend fails).
<Sysname> boot-loader file test.bin slot all 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 1!
The specified file will be used as the main boot file at the next reboot on slot 2!
bootrom
Syntax
bootrom
update
file
file-url slot slot-number-list
Summary of Contents for E4510-48G
Page 109: ...2 18 Sysname interface bridge aggregation 1 Sysname Bridge Aggregation1 shutdown ...
Page 309: ...6 4 Sysname interface vlan interface 1 Sysname Vlan interface1 ip address dhcp alloc ...
Page 324: ...8 3 Sysname interface vlan interface 1 Sysname Vlan interface1 ip address bootp alloc ...
Page 530: ...2 5 Sysname mvlan 100 subvlan 10 to 15 ...
Page 739: ...8 15 Sysname system view Sysname port security trap addresslearned ...
Page 819: ...13 11 Sysname system view Sysname public key peer key2 import sshkey key pub ...
Page 914: ...5 17 Sysname reset oam ...
Page 1064: ...5 30 Slot 2 Set next configuration file successfully ...
Page 1325: ...21 13 Examples Redirect to member 2 Sysname irf switch to 2 Sysname Slave 2 ...