VIOS 1.5.2.1 FixPack 11.

1 Virtual I/O Server

1.0.0.0 VIOS 1.5.2.1 FixPack 11.1 Readme

Readme file for: VIOS 1.5.2.1 FixPack 11.1

Product/Component Release: 1.0.0.0
Update Name: VIOS 1.5.2.1 FixPack 11.1
Fix ID: VIOS_1.5.2.1-FP-11.1
Publication Date: 10 October 2009
Last modified date: 10 October 2009

Contents
Download location
Known issues

Installation information
Prior to installation
Installing

Additional information
List of fixes
Document change history

Download location
Below is a list of components, platforms, and file names that apply to this Readme file.

Fix Download for Others

Product/Component Name: Platform: Fix:
Virtual I/O Server VIOS 1.5.2.0 VIOS_1.5.2.1-FP-11.1

Known issues
VIOS ITM
The following issues exist for the VIOS Premium agent:
• When defining the partition profile for VIOS or IVM, if the Virtual SCSI Server adapter has
been created with remote partition set to "Any Partition" for a particular server slot, instead
of specifying a partition name, the Storage Mapping for this slot will not be displayed in the
ITM workspace.
• Data from the "Storage Mapping" attribute group is misaligned. Use one of the following
workarounds
1. Remove the hostname alias from the /etc/hosts file in the VIOS partition.
 OR
2. If the alias is not defined, then change the NSORDER environment variable to
"NSORDER=local" or change the /etc/netsvc.conf file to use the local /etc/hosts file.

OR
3. Make the following changes to aixDataProvider.pl for the function "Storage_Mappings" and
"Network_Mappings":
From:
chomp(my $output = `host $vio_hostname`);
my ($trash, $trash2, $ip) = split(/\s+/, $output);
my $vio_ip = $ip;

To:
chomp(my $output = `host $vio_hostname`);
my ($trash, $trash2, $ip) = split(/\s+/, $output);
my $vio_ip = $ip;
$vio_ip =~ s/\,$//;

• On reboot of VIOS, users will receive the error message listed below. This error message
should be ignored. Restarting the ITM agents on reboot is handled by the 'cfgsvc' command.
sh: /etc/rc.itm1: 0403-006 Execute permission denied
• During install/update of VIOS, user may receive the following message, which should be
ignored:
Use of silent install mode implies license agreement acceptance. You can view
the license file details in the /opt/IBM/ITM/LAP/license directory
Preparing to install the IBM Global Security Kit (GSkit)
installp: There are incomplete installation operations
on the following filesets. Run installp -C to clean up
the previously failed installations before continuing.

itm.vios_premium.agent
install.sh warning: The root user must run installGSkit after the install to
complete the setup, continuing ...

Use of silent install mode implies license agreement acceptance. You can view
the license file details in the /opt/IBM/ITM/LAP/license directory
Preparing to install the IBM Global Security Kit (GSkit)
installp: There are incomplete installation operations
on the following filesets. Run installp -C to clean up
the previously failed installations before continuing.

itm.vios.agent
install.sh warning: The root user must run installGSkit after the install to
complete the setup, continuing ...

Use of silent install mode implies license agreement acceptance. You can view
the license file details in the /opt/IBM/ITM/LAP/license directory
Preparing to install the IBM Global Security Kit (GSkit)
installp: There are incomplete installation operations
on the following filesets. Run installp -C to clean up
the previously failed installations before continuing.

itm.cec.agent
install.sh warning: The root user must run installGSkit after the install to
complete the setup, continuing ...

VIOS ITM Base agent

The ITM VIOS base agent has not changed from the previous release, so please read the
ITM_README.doc document before configuring ITM VIOS base agent.
You can download the ITM_README.doc document from the following location:
IBM Tivoli Monitoring System Edition for System p
To access or download the Readme document, you must sign in with your IBM ID and password,
and then accept license terms.
Installation information

Prior to installation
Removing interim fixes
All Interim Fixes applied to the VIOS must be manually removed before applying Fix Pack 11.1.
VIOS customers that applied interim fixes to the VIOS should use the following procedure to
remove them prior to applying Fix Pack 11.1.
# oem_setup_env /*from the VIOS command line
# emgr -P /*list installed efix's (by label)
# emgr -r -L /* for each additional efix listed, run to remove
# exit
Fix Pack 11.1 updates your VIOS partition to ioslevel V1.5.2.1-FP-11.1. To determine if Fix Pack
11.1 is already installed, run the ioslevel command per the following procedure to determine if the
VIOS ioslevel is V1.5.2.1-FP-11.1:
# ioslevel /* from the VIOS command line
If the above procedure shows that the VIOS Fix Pack 11.1 is not installed, use the installation
instructions included in this Readme.
Note : After you install the Fix Pack, you must reboot the VIOS Server.

Installing
Notes:
1. The installation and upgrade instructions for installing a Fix Pack have been changed. Please
read the instructions under "Installing the Fix Pack".
2. The size of the FixPack has increased due to the enablement of Tivoli products.
If you are updating from an ioslevel prior to 1.3.0.1, the updateios command may indicate several
failures (i.e. missing requisites) during fix pack installation. These messages are expected. Proceed
with the update if you are prompted to "Continue with the installation [y/n]".

Applying updates from a local hard disk

To apply the updates from a directory on your local hard disk, follow one of these two procedures,
depending on your currently installed level of VIOS.
A. If the current level of the VIOS is earlier than V1.2.0.0 (V1.0 or V1.1):
NOTE:
If you are updating from VIOS level 1.1, you must update to the 10.1 level of the Fix Pack before
updating to the 11.1 level of Fix Pack. In other words, if you are at level 1.1, updating to the 11.1
Fix Pack is a two-step process: First, update to version 10.1 Fix Pack, and then update to the 11.1
Fix Pack.
Contact your IBM Service Representative to obtain the VIOS 10.1 Fix Pack.
After you install the 10.1 Fix Pack, follow these steps to install the 11.1 Fix Pack.
1. Login to the VIOS as the user padmin.
2. Create a directory on the Virtual I/O Server.
$ mkdir
 3. Using ftp, transfer the update file(s) to the directory you created.
4. Commit previous updates, by running the updateios command
$ updateios -commit
5. Apply the update by running the updateios command
$ updateios -accept -dev
6. Verify that update was successful by checking results of the updateios command and
running the ioslevel command. It should indicate the ioslevel is now V1.5.2.1-FP-11.1.
$ ioslevel
7. To load all changes, reboot the VIOS as User padmin
$ shutdown -restart
B. If the current level of the VIOS is V1.2 through V1.5:
1. Login to the VIOS as the user padmin.
2. Create a directory on the Virtual I/O Server.
$ mkdir
3. Using ftp, transfer the update file(s) to the directory you created.
4. Commit previous updates, by running the updateios command
$ updateios -commit
5. Apply the update by running the updateios command
$ updateios -accept -install -dev
6. Verify that update was successful by checking results of the updateios command and
running the ioslevel command. It should indicate the ioslevel is now V1.5.2.1-FP-11.1.
$ ioslevel
7. To load all changes, reboot the VIOS as User padmin
$ shutdown -restart
Back to top

Applying updates from a remotely mounted file system

If the remote file system is to be mounted read-only, follow one of these two procedures, depending
on your currently installed level of VIOS.
A. If the current level of the VIOS is earlier than V1.2.0.0 (V1.0 or V1.1):
NOTE:
If you are updating from VIOS level 1.1, you must update to the 10.1 level of the Fix Pack before
updating to the 11.1 level of Fix Pack. In other words, if you are at level 1.1, updating to the 11.1
Fix Pack is a two-step process: First, update to version 10.1 Fix Pack, and then update to the 11.1
Fix Pack.
Contact your IBM Service Representative to obtain the VIOS 10.1 Fix Pack.
After you install the 10.1 Fix Pack, follow these steps to install the 11.1 Fix Pack.
1. Login to the VIOS as the user padmin.
2. Mount the remote directory onto the Virtual I/O Server.
$ mount remote_machine_name:directory /mnt
3. Commit previous updates, by running the updateios command
$ updateios -commit
4. Apply the update by running the updateios command.
$ updateios -accept -dev /mnt
5. Verify that update was successful by checking results of the updateios command and
running the ioslevel command. It should indicate the ioslevel is now V1.5.2.1-FP-11.1.
$ ioslevel
6. To load all changes, reboot the VIOS as User padmin
 $ shutdown -restart
B. If the current level of the VIOS is V1.2 through V1.5:
1. Login to the VIOS as the user padmin.
2. Mount the remote directory onto the Virtual I/O Server.
$ mount remote_machine_name:directory /mnt
3. Commit previous updates, by running the updateios command
$ updateios -commit
4. Apply the update by running the updateios command
$ updateios -accept -install -dev /mnt
5. Verify that update was successful by checking results of the updateios command and
running the ioslevel command. It should indicate the ioslevel is now V1.5.2.1-FP-11.1.
$ ioslevel
6. To load all changes, reboot the VIOS as User padmin
$ shutdown -restart
Back to top

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 one of these two procedures, depending on your currently installed level of VIOS.
A. If the current level of the VIOS is earlier than V1.2.0.0 (V1.0 or V1.1):
NOTE:
If you are updating from VIOS level 1.1, you must update to the 10.1 level of the Fix Pack before
updating to the 11.1 level of Fix Pack. In other words, if you are at level 1.1, updating to the 11.1
Fix Pack is a two-step process: First, update to version 10.1 Fix Pack, and then update to the 11.1
Fix Pack.
Contact your IBM Service Representative to obtain the VIOS 10.1 Fix Pack.
After you install the 10.1 Fix Pack, follow these steps to install the 11.1 Fix Pack.
1. Login to the VIOS as the user padmin.
2. Place the CD-ROM into the drive assigned to VIOS.
3. Commit previous updates, by running the updateios command
$ updateios -commit
4. Apply the update by running the updateios command
$ updateios -accept -dev /dev/cdX
where X is the device number 0-N assigned to VIOS
5. Verify that update was successful by checking results of the updateios command and
running the ioslevel command. It should indicate the ioslevel is now V1.5.2.1-FP-11.1.
$ ioslevel
6. To load all changes, reboot the VIOS as User padmin
$ shutdown -restart
B. If the current level of the VIOS is V1.2 through V1.5:
1. Login to the VIOS as the user padmin
2. Place the CD-ROM into the drive assigned to VIOS
3. Commit previous updates, by running the updateios command
$ updateios -commit
4. 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
 5. Verify that update was successful by checking results of the updateios command and
running the ioslevel command. It should indicate the ioslevel is now V1.5.2.1-FP-11.1.
$ ioslevel
6. To load all changes, reboot the VIOS as User padmin
$ shutdown -restart

Additional information
Fix Pack 11.1 provides a migration path for existing Virtual I/O Server (VIOS) installations.
Applying this package will upgrade the VIOS to the latest level, V1.5.2.1.
Review the list of fixes included in Fix Pack 11.1.
Users of IBM Tivoli Monitoring (ITM) should read about known issues and limitations.
VIOSs installed with the previous VIOS install media (LCD4-7462-07, LCD4-7462-08 or LCD8-
0819-00), or running with a Fix Pack prior to Fix Pack 11.1, should be updated by applying Fix
Pack 11.1.
In order to take full advantage of all the function available in the VIOS (including SEA bandwidth
apportioning.), it is necessary to be at system firmware level SF235 or later. SF230_120 is the
minimum level of SF230 firmware supported by the Virtual I/O Server. If a system firmware update
is necessary, it is recommended that the firmware be updated before upgrading the VIOS to
V1.5.2.1.
For recommended or supported combinations of HMC and system firmware levels, refer to the
POWER Code Matrix
There is no migration path from an HMC-managed VIOS to an IVM-managed VIOS. Fix Pack 11.1
includes the IVM code, but it will not be enabled on HMC-managed systems. Fix Pack 11.1, like all
VIOS fix packs, can be applied to either HMC-managed or IVM-managed VIOS.

List of fixes
Fixes in Fix Pack 11.1 (VIOS V1.5.2.1) include:
• Added support for Bandwidth apportioning for Shared Ethernet Adapter.
• Added support for a Shared Ethernet Adapter accounting tool (new CLI command "seastat").
• Added virtual switch support to Partition Mobility commands.
• Added MPIO Support for Raided SAS Switch.
• Added CLI command for new SEA command "seastat"
• Improved topas reporting for SEA, EtherChannel, and VLAN.
• Added new VLAN attribute called vlan_priority to VLAN pseudo device.
• Added LoopBack Device Support.
• Added minimal-delay-mode support for fcparray.
• Added Support for CLI Image Management commands.
• Added support for IPv6.
• Added updates to the Systems Planning and Deployment Tool.
• Fixed problems with EtherChannel not available on boot and problems with gratuitous
ARPs.
• Fixed a potential security vulnerability in the entstat command.
• Fixed a problem changing an attribute in fibre channel set up.
• Fixed a problem with extending the # of Fibre Channel adapters supported on the VIOS.
• Fixed a problem of slow failback of I/O in dual failure conditions.
 • Fixed a problem with Linux installation using file-backed optical media.
• Fixed a problem with file-backed optical-does not report media change to client.
• Fixed a problem where VIOS can hang during live partition migration.
• Fixed a problem with a VIO Client I/O hang if disk is not presented to the VIO servers.
• Fixed a problem when VIOS client does not recover on SAN error.
• Fixed a problem with DS3K_DE-hung I/O's during controller reboot.
• Fixed a problem with backupios fails to CD due to ?L flag not being processed.
• Fixed a problem where unable to update microcode through web GUI on IVM partition.
• Fixed a problem where mksysplan from HMC fails due to large number of devices on the
VIOS.
• Fixed problem with unexpected file-backed volume after power failure.
• Fixed problem with "raso" command on the VIOS.
• Fixes for possible security vulnerability in the optimiznet cli command.
• Fixed problem with the mkvopt command with the ?size option.
• Fixed problem with partition mobility when moving to a VIOS level that is more recent and
if there is a version mismatch.
• Fixed IVM problem with uploading a media file.
• Fixed problem with displaying of physical location codes.
• Fixed a reliability issue in the disk subsystem.
• Fixed the shutdown command, problems when used with invalid flags.
• Fixed multiple problems for MPIO.
• Fixed several problems with disk storage.
• Fixed problem for the release of the CD drive.

Document change history

Date Description of change