Virtual Control Panel; Limitations Of The Virtual Control Panel - IBM i Series Handbook

Connecting to operations console
Hide thumbs Also See for i Series:
Table of Contents

Advertisement

v Any configuration where the device ID is not authorized is disabled or missing.
– The device ID is disabled after the first connection if it was selected but not authorized.
– The device ID is missing after the first connection if it was not selected and was not authorized.
After the device ID is authorized, it reappears in Properties, on the next connection.

Virtual control panel

A virtual control panel connects to the system through a serial cable. With virtual control panel, you can
perform most of the control panel functions from a local location only.
The virtual control panel uses the serial cable and the connection of a directly cabled console. There is no
requirement for network adapters on the PC or system with virtual control panel. You must, however,
create a configuration that uses the network path. You must also have an unused service tools device ID
available for the virtual control panel connection. If your console uses the network connectivity already,
you need to use the remote control panel option available for that configuration rather than virtual
control panel.
In this section you will see references to a unique service tools device ID. If you are using V6R1 for both
|
the Operations Console code and i5/OS on the system, by default the option Autocreate service tools
|
|
device IDs supplies the connection with this unique device ID. See Operations Console simplification for
more information.
|
The virtual control panel allows nearly all the same functions as the remote control panel. The graphical
interface is the same for the virtual control panel as it is for the remote control panel. Only the
connectivity is different. Because of the connectivity differences, the virtual control panel cannot, for
example, be used to turn on a system or a partition. The virtual control panel function can work with the
System i Access for Windows V6R1, or later, IBM eServer iSeries Access for Windows V5R4 or V5R3, or
iSeries Access for Windows V5R2 that communicates with a System i product running i5/OS V5R3, or
®
later, or OS/400
V5R2.
The virtual control panel uses a TCP/IP connection on the Operations Console cable. You have to have a
directly-cabled console configured and connected in order to use the virtual control panel. The virtual
control panel cannot be used to replace a parallel-connected remote control panel-only configuration. The
virtual control panel will require an additional configuration.
Important: It is recommended that you install the latest service pack for the client. The latest service
pack can be found at the System i Access Service Packs Web site.
Related concepts
"Operations Console simplification" on page 67
Operations Console can automatically create service tools device IDs, manage access passwords, and
discover systems.
Related reference
"Troubleshooting remote control panel and virtual control panel problems" on page 99
When setting up your initial connection, you might encounter problems accessing your control panels.
Related information
System i Access Service Packs Web site

Limitations of the virtual control panel:

Before you install and use a virtual control panel, consider these features and limitations.
v The VCP is only available while the console is connected.
v You must remove the parallel remote control panel cable, if installed, before configuring the VCP
connection.
v A unique service tools device ID must exist for each VCP configuration.
23
Operations Console

Advertisement

Table of Contents
loading

Table of Contents