Preparing your console for software installation

Before you install a new software release, consider this information on consoles.

Although you can use twinaxial console on most servers, IBM recommends for V5R4 that you use either Operations Console or Hardware Management Console. For requirements on twinaxial console, Operations Console, and PCs, refer to the category, Connecting to iSeries . If you are moving from twinaxial console to Operations Console, use the iSeries Setup and Operations CD-ROM, SK3T-4098-02, to install Operations Console before you install the new release.

If you are using twinaxial console, the software installation process expects the system console device to be attached at port 0 and address 0 of the first workstation controller. In most cases, your hardware should be defined in this way. You should verify that the console is attached at port 0 address 0.

If you are planning on migrating your Operations Console, do so either before or after you upgrade. If you are planning on migrating your Hardware Management Console (HMC), do so only after you have completely installed your system. For more information about using the HMC as your i5/OS™ console, see Managing i5/OS consoles .

For all servers, verify that the console mode value is set correctly for your console. In addition, you can specify that an i5/OS LAN console or Hardware Management Console be taken over by another console in the event your console is disconnected. To verify the console mode value, follow these steps:

  1. Access Dedicated Service Tools (DST).
  2. Select Work with DST environment.
  3. Select System Devices.
  4. Select Console mode.

    The value of the current console mode is present in the input field. Verify that this is the correct setting. A value of zero means that the console mode has not been set and can interfere with the automatic installation process. The console mode value must be one of the following values.

    1 Twinaxial console
    2 Operations Console (directly attached)
    3 Operations Console (LAN attached)
    4 Hardware Management Console (HMC)

    During an installation or upgrade to V5R4, the console type specified by this value is used.

    The console mode display also includes the option to allow your 5250 console (does not include twinaxial console) to be taken over by another console. When this option is turned on, the system does not stop with a failure but continues to run uninterrupted. For more information, see the topic Console takeover and recovery .

If you use Operations Console, do the following before you install V5R4 on your server:
  • Review the Operations Console topic. To review the most recent information on the Operations Console client, go to the Operations Console Web site Link outside information center
  • IBM recommends that you update IBM® eServer™ iSeries™ Access for Windows® to V5R4 before you upgrade the i5/OS operating system. For more information, see iSeries Access for Windows: Installation and setup .
  • If you use the Operations Console configuration, Local console directly attached to the server, and the adapter used for the cable connection is 2771, the adapter must be in a specific position. For independent or primary partitions only, the position is based on the server model shown in the following table.
    Note: This applies only to iSeries 270 and 8xx models. This does not apply to IBM System i5, System p5, and IBM eServer i5 and p5 systems.
    Table 1. Card position
    Server model Operations Console asynchronous card position for the cable
    270 C07
    800 or 810 C07
    820 C06
    825 C06
    830 or SB2 C02
    840 or SB3 C02
    870 or 890 C02
  • When you receive the i5/OS release upgrade, the shipped service tools user IDs (except 11111111) are expired. For all upgrades and installations, you need to establish a connection between the server and Operations Console PC by using 11111111 (eight 1's) for both the service tools user ID and the default password. This ensures a successful authentication of the subsequent connection of the client to the server. This is especially important for automatic installations.

Failure to comply with the above actions can prevent the console from working correctly during the upgrade or installation.