126
Step
Command
Remarks
1.
Specify main or
backup startup
images for the
global active MPU.
•
Use an .ipe file for
upgrade:
boot-loader file
ipe-filename
{
all
|
chassis
chassis-number
slot
slot-number
}
{
backup
|
main
}
•
Use .bin files for upgrade:
boot-loader file boot
filename system
filename
[
feature
filename
&<1-30> ] {
all
|
chassis
chassis-number
slot
slot-number
}
{
backup
|
main
}
Upgrade files must be saved in the root
directory of a file system on the global active
MPU.
If the storage medium is partitioned, save the
file to the root directory of the first file system
on the storage medium.
2.
Specify the main
startup images for
each standby MPU
in the IRF fabric.
•
Method 1:
Use an .ipe file for
upgrade:
boot-loader file
ipe-filename
{
all
|
chassis
chassis-number
slot
slot-number
}
{
backup
|
main
}
Use .bin files for
upgrade:
boot-loader file boot
filename system
filename
[
feature
filename
&<1-30> ]
{
all
|
chassis
chassis-number
slot
slot-number
}
{
backup
|
main
}
•
Method 2:
boot-loader update
{
all
|
chassis
chassis-number
slot
slot-number
}
Skip this step if you have only one single-MPU
device.
When you use the
boot-loader update
command, make sure you understand the
following requirements and upgrade results:
•
If an ISSU upgrade has been performed,
use the
install commit
command to
update the main startup images on the
active MPU before software
synchronization. The command ensures
startup image consistency between the
active MPU and the standby MPU.
•
The
boot-loader update
command uses
the main or backup startup image list for
synchronization, instead of the current
software images list.
The main images list is used if the
global active MPU started up with the
main startup images.
The backup image list is used if the
global active MPU started up with the
backup startup images.
Startup image synchronization will fail if any
software image being synchronized is
corrupted or is not available.
3.
Save the running
configuration.
save
This step ensures that any configuration you
have made can survive a reboot.
4.
Reboot the IRF
fabric.
reboot
At startup, the MPUs read the preloaded
BootWare image to RAM, and load the startup
images.
5.
(Optional.) Verify
the software image
settings.
display boot-loader
[
chassis
chassis-number
[
slot
slot-number
] ]
Verify that the current software images are the
same as the startup software images.
Enabling software synchronization from the active
MPU to the standby MPU at startup
This feature is available only when the device is operating in standalone mode. To synchronize
software from the global active MPU to other MPUs on an IRF fabric, use the
irf auto-update enable
Содержание FlexNetwork 10500 Series
Страница 139: ...130 Sysname display version ...