Upgrade Procedure - HP 10500 Series Configuration Manual

3. Upgrade all parent devices before upgrading any PEXs if both parent devices and PEXs require an
upgrade. For more information about upgrading parent devices, see
4. Use the dir command to verify that all PEXs and MPUs have sufficient storage space for the
upgrade images. If the storage space is not sufficient, delete unused files by using the delete
command. For a PEX to start up from its local storage medium, you must make sure its local storage
medium has sufficient space for the upgrade images. For more information, see "Managing the file
system."
5. Use FTP or TFTP to transfer the upgrade image file to the root directory of the default storage
medium on the global active MPU.
For more information about FTP and TFTP, see "Configuring FTP" and "Configuring TFTP."

Upgrade procedure

Perform this task in user view.
To upgrade PEXs:
Step
1. Specify main or backup
startup images for the PEX
to load from the local
medium.
2. Specify PEX startup images
for the PEX to load from the
parent device.
Command
•
Use an .ipe file for upgrade:
boot-loader file ipe-filename
chassis chassis-number slot
slot-number { backup |
main }
•
Use .bin files for upgrade:
boot-loader file boot
boot-package system
system-package [ feature
feature-package&<1-30> ]
chassis chassis-number slot
slot-number { backup |
main }
•
Use .bin files for upgrade:
boot-loader pex pex-model
file boot boot-package
system system-package
[ feature
feature-package&<1-30> ]
•
Use an .ipe file for upgrade:
boot-loader pex pex-model
file ipe ipe-filename
127
"IRF mode."
Remarks
This step is available only for 5700
PEXs. The boot-loader file command
copies the specified images from the
global active MPU to the local medium
of the PEX.
Specify the PEX virtual chassis number
for the chassis-number argument.
Specify the PEX virtual slot number for
the slot-number argument.
The boot-loader pex command copies
the specified PEX startup images
automatically to all MPUs on the parent
fabric. To prevent a PEX startup failure
after an active/standby or
master/subordinate switchover, HP
recommends that you execute this
command each time you add a new
member device or MPU to the parent
fabric.
For 5700 PEXs, you can use this
command to set startup software
images for backup.
To guarantee that the PEX loads the
correct software when a
master/subordinate switchover occurs,
make sure the PEX startup software
images are the same across the MPUs
in the IRF fabric.