VIOS 2.1.0.0 Migration DVD Virtual I/O Server 1.0.0.0 VIOS 2.1.0.0 Migration DVD Readme

Readme file for:VIOS 2.1.0.0 Migration DVD
Product/Component Release:1.0.0.0
Update Name:VIOS 2.1.0.0 Migration DVD
Fix ID:VIOS_2.1.0.0
Publication Date:10 September 2009
Last modified date:10 September 2009

Online version of the readme file:http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400000002
Important: The most current version of the readme file can always be found online.

Contents

Download location
Known issues

Installation information
   Installing

Additional information
List of fixes
Copyright and trademark information
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 ServerVIOS 2.1.0.0
VIOS_2.1.0.0





Known issues



Installation information

Installing

Migrating the VIOS from Version 1.3 or later to Version 2.1

Use the VIOS Migration DVD to migrate from VIOS Version 1.3 or later to VIOS Version 2.1.

Before you begin a migration, backup your current VIOS and then follow the steps for the method of migration that you choose.

Warning

Do not use the HMC DVD drive to migrate your VIOS to Version 2.1. Use the DVD drive assigned to your VIOS logical partition.

Migrating the VIOS from a migration DVD

To migrate the VIOS from a migration DVD, follow these steps:

Step 1. Pre-migration tasks

Follow these steps:

  1. Note what services you have started using the startnetsvc command.
  2. Note what other services/agents you have configured, using cfgsvc,
    1. lssvc displays a list of all agents
    2. lssvc displays information for the specified agent. Note if any parameters have been set for this agent. These parameters will have to be reconfigured after the migration.

Step 2. Activate the VIOS logical partition using the HMC (version 7 or later)

Follow these steps:

  1. Insert the VIOS migration DVD into the DVD drive assigned to the VIOS logical partition.
  2. In the HMC navigation area, expand Systems Management Servers.
  3. Select the VIOS logical partition server.
  4. In the contents area, select the VIOS logical partition.
  5. Shutdown VIOS by doing the following
    1. Select Tasks>Operations>Shutdown.
    2. On the Shutdown menu, select delayed, and then select OK.
  6. Select Tasks>Operations>Activate.
    The Activate Partition menu opens with a selection of logical partition profiles. Ensure that the correct profile is highlighted.
  7. Select Open a terminal window or console session to open a virtual terminal (vterm) window.
  8. Select (Advanced) to open the advanced options menu.
  9. Select SMS for the boot mode.
  10. Click OK to close the advanced options menu.
  11. Click OK. A virtual terminal window opens for the logical partition.

Step 3. Select a boot device

Follow these steps:

  1. Select Select Boot Options and press Enter.
  2. Select Select Install/Boot Device and press Enter.
  3. Select CD/DVD and press Enter.
  4. Select the device number that corresponds to the DVD and press Enter. You can also select List all devices, select the device number from the list, and then press Enter.
  5. Select Normal mode boot.
  6. Select Yes to exit SMS.

Step 4. Install the VIOS

Follow these steps:

  1. Select a console and press Enter.
  2. Select a language for the BOS menus and press Enter.
  3. Select Change/Show Installation Settings and Install.
    If the title displayed is not VIOS Migration Installation and Settings, then replace the DVD that is in the drive with the correct DVD before continuing to the next step.

  4. Select Install with the setting listed above.
  5. Select Continue with Install.
  6. Select Continue with migration

Step 5. Post-migration tasks

Follow these steps:

  1. Verify that the migration was successful by doing the following
    1. Check the results of the installp command.
    2. Run the ioslevel command. The results should indicate that the ioslevel is $ ioslevel 2.1.0.0.
    3. Update the inittab file by executing the following commands:
      $ oem_setup_env
      # /usr/sbin/rmitab install_assist > /dev/null 2>&1
      # exit
  2. Restart the daemons and agents that were previously running by doing the following:
    1. Log on to the VIOS as a padmin user.
    2. Enter the following command:
      $ motd -overwrite ""
    3. Run the cfgsvc command to reconfigure all the agents by using the configuration data that you saved in Pre-migration step 1, and then run the startsvc command to start the agents.
    4. Use the startnetsvc command to restart any services that were running before the migration: those that you noted in Pre-migration step 1.

Migrating the Virtual I/O Server from DVD - IVM

If you use the Integrated Virtualization Manager (IVM) to manager your Virtual I/O Server and client logical partitions, then follow these instructions for migrating the Virtual I/O server from a DVD device.

Before migration

Before you begin the migration, verify that the following statements are true:

Migration tasks

To migrate the Virtual I/O Server from a DVD, follow these steps:

Step 1. Pre-migration tasks

Follow these steps:

  1. Note what services you have started using the startnetsvc command.
  2. Note what other services/agents you have configured, using cfgsvc,
    1. lssvc displays a list of all agents
    2. lssvc displays information for the specified agent. Note if any parameters have been set for this agent. These parameters will have to be reconfigured after the migration.

Step 2. Access the Virtual I/O Server logical partition

Do ONE of the following:

Blade server environment only

  1. Access the Virtual I/O Server logical partition using the management module of the blade server.
  2. Verify that all logical partitions except the Virtual I/O Server logical partition are shut down.
  3. Insert the Virtual I/O Server migration DVD into the Virtual I/O Server logical partition.
  4. Use telnet to connect to the management module of the blade server on which the Virtual I/O Server logical partition is located.
  5. Enter the following command: env -T system:blade[x] where x is the specific number of the blade to be migrated.
  6. Enter the following command: console
  7. Sign on to the Virtual I/O Server using the appropriate user ID and password.
  8. Enter the following command: shutdown -restart
  9. When you see the system management services (SMS) logo appear, select 1 to enter the SMS menu.

OR

Non-Blade server environment only

  1. Access the Virtual I/O Server logical partition using the Advanced System Management Interface (ASMI) with a Power Systems server that is not managed by an HMC.
  2. Verify that all logical partitions except the Virtual I/O Server logical partition are shut down.
  3. Insert the Virtual I/O Server migration DVD into the Virtual I/O Server logical partition.
  4. Log in to the ASCII terminal to communicate with the Virtual I/O Server. See Access the ASMI without an HMC if you need assistance.
  5. Sign on to the Virtual I/O Server using the appropriate user ID and password.
  6. Enter the following command: shutdown -restart
  7. When you see the SMS logo appear, select 1 to enter the SMS menu.

Step 3. Select the boot device

  1. Select Select Boot Options and press Enter.
  2. Select Select Install/Boot Device and press Enter.
  3. Select CD/DVD and press Enter.
  4. Select the device number that corresponds to the DVD and press Enter. You can also select List all devices and select the device number from a list and press Enter.
  5. Select Normal mode boot.
  6. Select Yes to exit SMS.

Step 4. Install the Virtual I/O Server

  1. Select the desired console and press Enter.
  2. Select a language for the Base Operating System (BOS) menus and press Enter.
  3. Select Start Install Now with Default Settings and press Enter. You can also verify the installation and system settings by typing 2 to select Change/Show Installation Settings and Install.
    Note: You should not have to change installation settings simply to select the migration installation method. If a previous version of the operating system exists, the installation method defaults to migration.
  4. Select Continue with Install. The system will reboot after the installation is complete.

Step 5. Post-migration tasks

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 that you perform the following tasks:

Follow these steps:

  1. Verify that the migration was successful by doing the following
    1. Check the results of the installp command.
    2. Run the ioslevel command. The results should indicate that the ioslevel is $ ioslevel 2.1.0.0.
    3. Update the inittab file by executing the following commands:
      $ oem_setup_env
      # /usr/sbin/rmitab install_assist > /dev/null 2>&1
      # exit
  2. Restart the daemons and agents that were previously running by doing the following:
    1. Log on to the VIOS as a padmin user.
    2. Enter the following command:
      $ motd -overwrite ""
    3. Run the cfgsvc command to reconfigure all the agents by using the configuration data that you saved in Pre-migration step 1, and then run the startsvc command to start the agents.
    4. Use the startnetsvc command to restart any services that were running before the migration: those that you noted in Pre-migration step 1.


Additional information

Notices

Minimum software levels required for N_Port ID Virtualization

N_Port ID Virtualization (NPIV) was made available with VIOS Fix Pack 20.1. NPIV required the following minimum software levels.

ProductMinimum required level
8 Gigabit Dual Port Fibre Channel adapter, feature code 5735 110305
System firmware 340_039
HMC V7 R3.4.0
VIOS 2.1.0.10-FP20.1
AIX 6.1 6100-02-02-0849
AIX 5.3 5300-09-02-0849


List of fixes

Fixes in Version 2.1.0



Copyright and trademark information


http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:



Document change history


Date Description of change