subscribe iconSubscribe to this 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 with the VCP, you must install the Operations Console and configure a virtual control panel. The configuration path to create the VCP connection uses the Operations Console on a network path but does not require a network or network adapter.

You must have a local console directly attached to the server configured in order for the virtual control panel to function. To set up a local console directly attached to the server configuration, follow the setup instructions in the Operations Console. The virtual control panel functions have some limitations and restrictions.

To install the virtual control panel (VCP), do the following:

  1. Ensure that you understand and meet the VCP requirements.
  2. Install the latest service pack for System i® Access for Windows®.
  3. Review Changing the console mode in i5/OS, and then complete one of the following steps, depending on the current console value:
    1. If the console value is Operations Console (LAN), then 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, perform a reset of the QCONSOLE service tools device ID before using the VCP. See the create a service tools device ID topic 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. Select the correct logical partition, and click Next. POWER5™ server models 5xx begin counting logical partitions at 1, while all other server models start counting at 0.
    6. 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.
    7. In the Service gateway address 1 field, enter 0.0.0.0.
    8. In the serial number field, enter a serial number, and click Next. This number does not have to be the real system serial number.
    9. 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 System i 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.
    10. 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.
    11. Enter the password for confirmation and, click Next.
    12. Click Finish.
    13. Select the configured connection you just created, and then select Properties.
    14. Click the Configuration tab.
    15. Unselect 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 find out how to make the connection, see Connecting a local console directly attached without remote access allowed.

Send feedback | Rate this page

Last updated: Fri, Oct 30, 2009