Migrating the Virtual I/O Server from the HMC
Find instructions for migrating the Virtual I/O Server (VIOS) to Version 2.1.0.0, or later, from the Hardware Management Console (HMC) by using the installios command.
Before you start, verify you meet the following requirements:
- HMC is attached to the managed system.
- The Virtual I/O Server logical partition has at least one Ethernet adapter and a 16 GB disk assigned to it.
- You have hmcsuperadmin authority.
- You have the Virtual I/O Server migration media. Note: The migration media is separate from the installation media.
- The Virtual I/O Server is currently at Version 1.3 or later.
- The disk name (PV_name) of your root volume
group (rootvg) is hdisk0. You can verify the
disk name by running the following command from the Virtual I/O Server command line
interface: lsvg -pv rootvgNote: If the disk name is anything other than hdisk0, you cannot use the migration DVD to perform the migration. Instead, see Migrating the Virtual I/O Server from a downloaded migration image to ensure that you can migrate the Virtual I/O Server successfully.
- The rootvg volume group has been assigned to the Virtual I/O Server
- Use the startnetsvc command to note what services you have started for the Virtual I/O Server.
- Determine the services and agents that are configured (by using
the cfgsvc command) for use with the Virtual I/O Server. Use the lssvc command
to display a list of all agents. Use the lssvc with
the agent name parameter (lssvc <agent_name> to
display information for a specified agent. Note: If any parameters have been set for an agent or service, you will need to reconfigure the parameters after you complete the migration process.
- Back up the mksysb image before migrating Virtual I/O Server. Run the backupios command and save the mksysb image to a safe location.
To migrate the Virtual I/O Server, follow these steps:
After the migration is complete, the Virtual I/O Server logical
partition is restarted to its preserved configuration prior to the
migration installation. It is recommended to perform the following
tasks:
- Verify that migration was successful by checking the results of the installp command and by running the ioslevel command. The results of the ioslevel command indicate the ioslevel is now $ ioslevel 2.1.0.0.
- Restart previously running daemons and agents:
- Log on to the Virtual I/O Server as padmin user.
- Complete the following command: $ motd -overwrite "<enter previous banner message>"
- Start up any previously running daemons, such as FTP and Telnet.
- Start up any previously running agents, such as ituam.
- Check for updates to the Virtual I/O Server. For instructions,
see the Fix Central website. Remember: The Virtual I/O Server migration media is separate from the Virtual I/O Server installation media. Do not use the installation media for updates after you perform a migration. It does not contain updates and you will lose your current configuration. Only apply updates using the instructions from the Virtual I/O Server Support for Power Systems™ Web site.