102 lines
6.5 KiB
HTML
102 lines
6.5 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Limitations of the virtual control panel (VCP)" />
|
||
|
|
<meta name="abstract" content="You should consider the following features and limitations before installing and using virtual control panel." />
|
||
|
|
<meta name="description" content="You should consider the following features and limitations before installing and using virtual control panel." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrvirtualcontrolpanel.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrinstallvcp.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="limitationsvcp" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Limitations of the virtual control panel (VCP)</title>
|
||
|
|
</head>
|
||
|
|
<body id="limitationsvcp"><a name="limitationsvcp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Limitations of the virtual control panel (VCP)</h1>
|
||
|
|
<div><p>You should consider the following features and limitations before
|
||
|
|
installing and using virtual control panel.</p>
|
||
|
|
<div class="section"><ul><li>The VCP is only available while the console is connected.</li>
|
||
|
|
<li>You must remove the parallel remote control panel cable, if installed,
|
||
|
|
before configuring the VCP connection.</li>
|
||
|
|
<li>A unique service tools device ID must exist for each VCP configuration. <p>For
|
||
|
|
example, you have connected a PC named DIRECT to SERVER1 using a direct cable
|
||
|
|
and you want to configure a VCP. If no Operations Console (LAN) configuration
|
||
|
|
exists to this server then the service tools device ID QCONSOLE has not been
|
||
|
|
used. Therefore, you can specify QCONSOLE when you configure the
|
||
|
|
VCP.</p>
|
||
|
|
<p>Another example would involve a cabled console called DIRECT that
|
||
|
|
is a backup for LAN-connected Operations Console PCs named LAN1 and LAN2.
|
||
|
|
In this example LAN1 used the service tools device ID QCONSOLE during setup
|
||
|
|
and LAN2 used a user-created service tools device ID of QCONSOLE2 during its
|
||
|
|
setup. For the intended VCP configuration you must create another service
|
||
|
|
tools device ID, such as QCONSOLE3 to be specified when you configure the
|
||
|
|
VCP.</p>
|
||
|
|
</li>
|
||
|
|
<li>You cannot use or reuse an existing network name when you create the additional
|
||
|
|
VCP configuration. For example, if you have a configuration named SERVER1,
|
||
|
|
you cannot name the VCP SERVER1. Also, if the intended VCP-capable PC is
|
||
|
|
on a network, you cannot use any name that already exists on that network.</li>
|
||
|
|
<li>All VCP and remote control panels (RCPs) are active at the same time. <p>If
|
||
|
|
you have multiple PCs (LAN connected) that can become the console, one at
|
||
|
|
a time, and those configurations also use the remote control panel functions,
|
||
|
|
all active RCPs can control the server. Use care when working with control
|
||
|
|
panel functions when multiple PCs have access to the functions.</p>
|
||
|
|
</li>
|
||
|
|
<li>The use of a virtual control panel at a remote console is not supported.</li>
|
||
|
|
<li>An alternative for powering on the system at a later time, instead of
|
||
|
|
using a cabled remote control panel, can be provided using the IPL scheduling
|
||
|
|
function in Operational Assistant, available in <span class="keyword">i5/OS™</span>by
|
||
|
|
pressing the <span class="uicontrol">Attention</span> key. You can also use the <span class="keyword">i5/OS</span> command <span class="cmdname">go power</span> and
|
||
|
|
select the option <span class="uicontrol">Change power on and off schedule</span>.
|
||
|
|
Also, LAN connected configurations connecting directly to a primary partition
|
||
|
|
will provide the ability to power on a logical partition as long as the primary
|
||
|
|
partition remains active. </li>
|
||
|
|
<li>The hosts file on the PC may need manual cleanup. <p>Each time you create
|
||
|
|
a network configuration on the PC, data is saved in a file called hosts.
|
||
|
|
This file may be used each time the PC attempts to connect to the network.
|
||
|
|
Each entry is unique to any others by the connection name. Currently, if
|
||
|
|
you delete a VCP configuration the corresponding hosts entry is not deleted.
|
||
|
|
You must manually delete the appropriate line from this text-based file using
|
||
|
|
any text editor.</p>
|
||
|
|
</li>
|
||
|
|
<li>If you have a server model that uses the keystick, the mode button will
|
||
|
|
work with the same functions as the physical control panel when the keystick
|
||
|
|
is inserted.</li>
|
||
|
|
<li>The service tools user ID used to authenticate the connection must have
|
||
|
|
the <strong>partition remote panel key</strong> privilege to use the mode function provided
|
||
|
|
by the VCP. Service tools user IDs QSECOFR, QSRV, 22222222, or 11111111 already
|
||
|
|
have this permission by default. <div class="note"><span class="notetitle">Note:</span> Systems with a keystick require the keystick to be inserted before the user
|
||
|
|
is eligible to use the mode button. For example, the user has the remote
|
||
|
|
panel key privilege but will not have the mode function available until the
|
||
|
|
keystick is present. For systems without the keystick, the user ID being
|
||
|
|
used would only require the remote panel key privilege.</div>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrvirtualcontrolpanel.htm" title="The virtual control panel (VCP) is one way to get remote control panel (RCP) functions on the PC.">Virtual control panel (VCP)</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzajrinstallvcp.htm" title="Use the procedures below to install the virtual control panel.">Installing the virtual control panel</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|