Planning considerations for your Operations Console installation or upgrade
To plan for your Operations Console installation or upgrade, know this information.
If you are upgrading to V5R4 and you want to replace an existing console with Operations Console, upgrade the system before migrating the console. This will prevent any conflict between the existing console and the Operations Console.
Prerequisite information for Operations Console users upgrading to or installing V5R4
You must comply with the following before upgrading or installing your software (i5/OS®, Licensed Internal Code) to V5R4:
- If your system has a 2771 adapter card in the processing unit and you plan to use Operations Console as either your primary console or as a backup console, it must be installed in the location designated by model for cable connections based on the following table, prior to the upgrade or installation. Each model has a different preferred location:
Model Operations Console asynchronous card location for the cable 270 C07 800, 810 C07 820 C06 825 C06 830, SB2 C02 840, SB3 C02 870, 890 C02
- When you receive the i5/OS release upgrade, all of the user IDs included with the operating system are expired, except for 11111111 (eight 1's). For all upgrades and installations, establish a connection between the System i™ platform and Operations Console using the service tools user ID of 11111111. This prevents any failed re-authentication of the client connection to the system caused by expired user IDs. This is especially important for automated installations and upgrades.
- IBM recommends that you update iSeries™ Access for Windows® to V5R4 before you upgrade the i5/OS operating system. For more information about installing iSeries Access for Windows, refer to the Install iSeries Access for Windows topic.
Failure to comply with the above actions may prevent the console from working correctly during the upgrade or installation.
During a manual IPL of the system and if no console has been specified before, you receive two additional displays to confirm the setting of the console type. The first requires that you accept your current console type, and the second shows that a value did not previously exist (a zero is present for the old value) and the new value is shown. Press Enter to exit and set the console type automatically. The IPL then continues to the IPL or Install the System display. This condition is most likely to occur during the installation of a new partition, but it can happen on your first manual IPL, for example, during the A-mode IPL following the restore of Licensed Internal Code, or during the upgrade or installation when a console value of zero is found.
Migration to Operations Console before your system upgrade
If you are migrating from a different console type to Operations Console on your new system, it is important that you configure your new Operations Console PC before beginning the upgrade. The Operations Console features that match the connectivity you plan to use should be specified as part of the order for your new system. In this way, at the point in the upgrade instructions where console functions are required on the new system, you can perform them on your new Operations Console device.
Also, when migrating a former load source device that was used with Operations Console local console on a network configuration, and this load source device is to become a load source device in a new partition, the LAN adapter must be deallocated before removing the device from the old partition and installing it in the new partition.
Parent topic:
Planning considerations for Operations Console
Related tasks
Installing iSeries Access for Windows
Deallocating or moving the LAN adapter card from use by Operations Console
Related reference
Installing an Operations Console cable
Related information
Upgrade your iSeries
Install, upgrade, or delete i5/OS and related software