The following information may help you determine which remote control
panel configuration is best for you.
The local console on a network will select the remote control panel by
default. Use Properties to deselect the function if you do not want to use
the remote control panel.
A remote control panel that is directly connected, using parallel cable,
has all available remote control panel functions.
A virtual control panel requires the console to be directly connected
via serial cable and the console must be connected to use the control panel
functions. The VPC cannot power on the server 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 server.
LAN configurations to the primary will, by default, configure remote control
panels for each logical partition to which the device ID is authorized.
The remote control panels for the logical partitions have the same functions
available as those provided by the LPAR menu. This includes power-on, as long
as the primary stays operational.
LAN configurations to logical partitions will initially have a remote
control panel but it has less function than one directly connected to the
primary. For example, it would not be able to power on the logical partition.
To obtain the same functions as those associated to the primary, create
a separate configuration for the remote control panel and specify the primary's
service host name (interface name). However, this might require another service
tools device ID.
Any configuration where the device ID is not authorized will be greyed
out or missing.
Greyed out after the first connection if it was selected but not authorized.
Missing after the first connection if it was not selected and was not
authorized.
Once authorized it will reappear in Properties, on the next connect.