Planning Considerations For Your Control Panel; Remote Control Panel - IBM i Series Handbook

Planning considerations for your control panel

To make a connection to the control panel, you need to configure a remote control panel or a virtual
control panel. All IDs that want access need proper authority.
Both remote control panel and virtual control panel are graphical interfaces to the control panel. The
remote control panel allows you to perform most of the control panel functions from a local or a remote
location. The virtual control panel allows you to perform most of the control panel functions from a local
location only. By default, user-created user IDs will have these permissions.
The user must be granted access to a partition's remote control panel and functions to use the remote
control panel or virtual control panel. If a local console on a network is being used, then the service tools
device ID must also be granted access to that partition's remote control panel to use this feature.
| By default, users and service tools device IDs are no longer automatically granted access to the remote
| control panel for the partition. But access can be granted by an administrator for the user ID, device ID,
or both. The user that authenticates a connection must also have authority to the respective partition's
|
| keylock to change the mode.
Use these links to review your control panel options, see comparisons of the control panels, and find
setup instructions:
v To review your control panel options, see comparisons, and find setup instructions in the Control Panel
topic.
v To solve problems with the remote control panel or the virtual control panel, see the Troubleshoot
remote control panel and virtual control panel problems topic.
Related reference
"Scenario: A single console directly attached to the system without remote support" on page 20
This scenario discusses a situation in which you might want a single console attached to the system.
"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.

Remote control panel

A remote control panel connects to the system through a local area network (LAN). With remote control
panel, you can perform most of the control panel functions from a local or a remote location.
v The local console on a network no longer automatically selects the remote control panel function by
|
| default. Use Properties to select the function if you want to use the remote control panel. Also, the
remote control panel option might not be available for selection until after the first successful
|
connection is established and authorities are verified.
|
LAN configurations to the primary partition no longer configure remote control panels for each logical
| v
| partition to which the device ID is authorized. You have to enter Properties and select one or more
remote control panels.
|
– The remote control panels for the logical partitions have the same functions available as those
|
| provided by the LPAR menu. This includes the power-on function, as long as the primary partition
stays operational.
|
v A remote control panel that is directly connected, using parallel cable, is no longer supported.
v A virtual control panel requires the console to be directly connected by a serial cable. The console must
be connected to use the control panel functions. The virtual control panel cannot turn on the system
unless the connection is to a primary partition and the primary partition is active. The virtual control
panel also requires a service tools device ID on the system.
| v LAN configurations to logical partitions have less function than one that is directly connected to the
primary partition. For example, the remote control panel cannot turn on the logical partition.
|
– To obtain the same functions as those associated with the primary partition, create a separate
|
| configuration for the remote control panel and specify the primary partition's service host name
| (interface name). However, this might require another service tools device ID.
22
System i: Connecting to System i Operations Console