POWER5 information.

Setting up the virtual control panel

You can set up the virtual control panel (VCP) through an Operations Console configuration.

To receive control panel functions by using a VCP, you must set up Operations Console and configure a VCP. The configuration path to create a VCP connection uses the Operations Console on a network path but does not require a network or network adapter.

You must also have a local console directly attached to the server that is being configured. To set up a local console directly attached to the server configuration, follow the setup instructions in Setting up Operations Console. The VCP functions have some limitations and restrictions.

Before you complete the following steps, ensure that you understand and meet the VCP requirements provided in Considerations for the virtual control panel.

To install the VCP, do the following:

  1. Install the latest service pack for iSeries® Access for Windows®. For more information, see the iSeries Access for Windows Service Packs Web site.
  2. Determine the value of the current console:
    1. Access service tools using dedicated service tools (DST) or system service tools (SST).
      • If you are using DST, select Work with DST environment > System devices.
      • If you are using SST, select Work with service tools user IDs and devices.
    2. Select Select console. The value of the current console is displayed. A value of 0 means that the console value is not set. The console value must be one of the following values:
      Console value Console
      1 Twinaxial console
      2 Operations Console (direct)
      3 Operations Console (LAN)
      4 HMC or Thin Console

      The HMC and Thin Console cannot be connected to the server at the same time.
  3. Complete one of the following steps only if the option Autocreate service tools device ID is 0:
    1. If the console value is Operations Console (LAN), create a service tools device ID and set user ID permissions.
    2. If the console value is not Operations Console (LAN), then you can use the existing service tools device ID of QCONSOLE for the VCP. You do not need to create a service tools device ID. If you are uncertain about whether the Operations Console (LAN) console option was ever used, reset the QCONSOLE service tools device ID before using the VCP. For instructions, see Creating a service tools device ID for the console VCP to access the service tools device ID and perform the reset password task for QCONSOLE.
  4. Create a new configuration for the VCP:
    1. From the Connection menu, click New Connection.
    2. Click Next. (If the window asking about prerequisites is displayed, click Yes.)
    3. Leave the option Local Area Network (LAN) selected, and click Next.
    4. Enter a name to refer to the VCP connection. If the PC that you are working with is connected to a network, do not use a name that can be found on that network or defined on the PC.
    5. Click Next.
    6. Enter 192.168.0.2 for the TCP/IP address when notified and click Next.
    7. Select the correct logical partition, and click Next.
      Important: IBM® System i® models start counting logical partitions with the number 1 (even if it is the only partition) instead of a 0. For the console to connect correctly, your logical partitions must also begin numbering at 1 instead of 0. This is especially true if you rely on the BOOTP process to configure the server with its network data.
    8. In the Service TCP/IP Address field, type 192.168.0.2.
      Note: In some cases, the address 192.168.0.n might have been previously used for something other than the Operations Console. In those cases, you might have had to use a different base address for the Operations Console, such as 192.168.1.n. If so, use the base address currently assigned to the Operations Console, but make the last value 2. For example, use 192.168.1.2.
      1. To check the current base address, use the regedit or another registry editing program. Navigate to the following: HKEY_LOCAL_MACHINE > Software > IBM > Client Access > CurrentVersion > AS400 Operations Console > LCS.
      2. Expand LCS, and select the appropriate configuration.
      3. Check the key IP Address. Use the IP address reported on your PC to validate the VCP address. You might also need to check the entries in the hosts file on your PC for a matching name or address.
    9. In the Service gateway address 1 field, enter 0.0.0.0.
    10. If requested, enter the service tools device ID you are going to use for the VCP connection, and click Next.
    11. In the serial number field, enter a serial number, and click Next. This number does not have to be the real system serial number.
    12. Enter the service tools device ID and password that you are going to use for the VCP connection authentication, and click Next. If you are using the default service tools device ID QCONSOLE, then enter its name and password. If you created a device ID, then enter its name and password. Beginning with iSeries Access for Windows, Version 5 Release 4 (V5R4), you are not prompted for the service tools device ID password. Instead, you are prompted for the service tools device ID name only.
    13. Enter the password that you want to use to connect this console configuration. This password is only used by the PC for the VCP connection and is not known at the server. For example, if you entered access as the password, then use access later to sign on.
    14. Enter the password for confirmation, and click Next.
    15. Click Finish.
    16. Select the configured connection you just created, and select Properties.
    17. Click the Configuration tab.
    18. Clear the Use console with this connection option, and click OK.
  5. You can now connect the console, if needed, and the VCP configuration to access the control panel functions. To determine how to make the connection, see Connecting a local console directly attached without remote access allowed.