VIO官方升级步骤及其注意事项

Installing
Use one of the following methods to install the latest VIOS Fix Pack.
Applying updates from a local hard disk
To apply the updates from a directory on your local hard disk, follow these steps.
The current level of the VIOS must be 2.1.0 or higher
Log in to the VIOS as the user padmin.
If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here..
Create a directory on the Virtual I/O Server.
$ mkdir
Using ftp, transfer the update file(s) to the directory you created.
Commit previous updates by running the updateios command
$ updateios -commit
Apply the update by running the updateios command
$ updateios -accept -install -dev
If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 8 if you are upgrading from a prior level of the VIOS):
$ swrole - PAdmin
To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart
After the VIOS has rebooted, you are required to accept the license.
$ license -accept
Verify that the update was successful by checking the results of the updateios command and by running the isolevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.
$ioslevel

Applying updates from a remotely mounted file system
If the remote file system is to be mounted read-only, follow one of these steps.
The current level of the VIOS must be 2.1.0 or higher
Log in to the VIOS as the user padmin.
If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here..
Mount the remote directory onto the Virtual I/O Server.
$ mount remote_machine_name:directory /mnt
Commit previous updates, by running the updateios command
$ updateios -commit
Apply the update by running the updateios command
$ updateios -accept -install -dev /mnt
If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 7 if you are upgrading from a prior level of the VIOS):
$ swrole - PAdmin
To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart
After the VIOS has rebooted, you are required to accept the license.
$ license -accept
Verify that the update was successful by checking the results of the updateios command and by running the isolevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.
$ioslevel

Applying updates from the CD/DVD drive
This fix pack can be burned onto a CD by using the ISO image file(s). After the CD has been created, follow these steps.
The current level of the VIOS must be 2.1.0 or higher
Log in to the VIOS as the user padmin
If you use one or more File Backed Optical Media Repositories, you need to unload media images before you apply the Fix Pack. See details here..
Place the CD-ROM into the drive assigned to VIOS
Commit previous updates, by running the updateios command
$ updateios -com

mit
Apply the update by running the following updateios command:
$ updateios -accept -install -dev /dev/cdX
where X is the device number 0-N assigned to VIOS
If you are upgrading to Fix Pack 24 from VIOS level 2.1.3, run the following command (skip to step 7 if you are upgrading from a prior level of the VIOS):
$ swrole - PAdmin
To load all changes, reboot the VIOS as user padmin .
$ shutdown -restart
After the VIOS has rebooted, you are required to accept the license.
$ license -accept
Verify that the update was successful by checking the results of the updateios command and by running the isolevel command, which should indicate that the ioslevel is now 2.2.0.10-FP-24.
$ioslevel
Before installing the Fix Pack
How to check for a loaded media repository, and then unload it
To check for loaded images, run the following command:
& lsvopt
The Media column lists any loaded media.
To unload media images. run the following commands on all VTDs that have loaded images.
& unloadopt -vtd
To verify that all media are unloaded, run the following command again.
& lsvopt
The command output should show No Media for all VTDs.
After installing the Fix Pack
How to check for an incomplete installation caused by a loaded media repository
After installing a fix pack, you can use either one of the following two methods to determine if you have encountered the problem of a loaded media library.
Method 1
Check the Media Repository by running this command:
$ lsrep
If the command reports: "Unable to retrieve repository date due to incomplete repository structure," then you have likely encountered this problem during the installation. The media images have not been lost and are still present in the file system of the virtual media library. Running the lsvopt command should show the media images.
Method 2
Check the install.log and look for a failure message like this one:
ios.cli.rte 6.1.4.1 USR APPLY SUCCESS
ios.cli.rte 6.1.4.1 ROOT APPLY FAILED
ios.cli.rte 6.1.4.1 ROOT CLEANUP SUCCESS

Renaming Media Repository Logical Volume:
VMLibrary_LV --> VMLibrary
umount: error unmounting /dev/VMLibrary_LV: Device busy

Media Repository failed to unmount. We cannot continue
until it can be successfully unmounted. Please address
and retry.
update: Failed while executing the ios.cli.rte.post_u script.

installp: The installation has FAILED for the "root" part
of the following filesets:
ios.cli.rte 6.1.4.1

installp: Cleaning up software for:
ios.cli.rte 6.1.4.1
How to recover from an incomplete installation caused by a loaded media repository
To recover from this type of installation failure, unload any media repository images, and then reinstall the ios.cli.rte package. Follow these steps:
Unload any media images
$ unloadopt -vtd

ptical_device>
If you have not yet restarted the VIOS, restart it now. You must restart before you can run the installp command in the next step.
$ shutdown -restart
Reinstall the ios.cli.rte fileset by running the following commands.
To escape the restricted shell:
$ em_setup_env
To install the failed fileset:
# installp -Or -agX ios.cli.rte
To return to the restricted shell:
# exit
Verify that the Media Repository is operational by running this command:
$ lsrep