217 lines
14 KiB
HTML
217 lines
14 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="Using the console service functions (65+21)" />
|
|||
|
|
<meta name="abstract" content="The emergency console recovery functions and their uses" />
|
|||
|
|
<meta name="description" content="The emergency console recovery functions and their uses" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrcommonservertasks.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrswitchconsolenotoperational.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrrecoverydetails.htm" />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajra600500a.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="functions6521" />
|
|||
|
|
<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>Using the console service functions (65+21)</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="functions6521"><a name="functions6521"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Using the console service functions (65+21)</h1>
|
|||
|
|
<div><p>The emergency console recovery functions and their uses</p>
|
|||
|
|
<div class="section"><p>This function-set should be used only in circumstances where an
|
|||
|
|
unexpected console failure has occurred and there are no other workstations
|
|||
|
|
available for recovery or debugging. Improper use may result in the inability
|
|||
|
|
to use the intended console. Any hardware allocations or configurations will
|
|||
|
|
have to be accomplished before using the console service functions (65+21).
|
|||
|
|
For example, if you are using a shared IOP in an LPAR environment you can
|
|||
|
|
deallocate and allocate the resource from one partition to another, if your
|
|||
|
|
hardware supports this method.</p>
|
|||
|
|
<p>The console service functions (65+21)
|
|||
|
|
are standard control panel functions. They can be entered at the physical
|
|||
|
|
control panel, any of the remote control panel connectivity types providing
|
|||
|
|
a graphical user interface in Operations Console or using the LPAR menus on
|
|||
|
|
a primary partition. Since the first function is a 65, which is the deactivation
|
|||
|
|
of the communications line used by the local console directly attached, you
|
|||
|
|
may see the status of a connection using a serial cable go to <samp class="codeph">Connecting
|
|||
|
|
console</samp>. </p>
|
|||
|
|
<div class="important"><span class="importanttitle">Important:</span> In order to use these functions,
|
|||
|
|
the server must be far enough through the IPL for the code to run properly.
|
|||
|
|
If a console device is available, you should use that console to perform
|
|||
|
|
any console service functions, if possible. If a console device is not available,
|
|||
|
|
then perform these functions only after a failing System Reference Code (SRC)
|
|||
|
|
has been displayed. This SRC usually is an A6005008.</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><p>The following functions are available using the console service
|
|||
|
|
functions (65+21): </p>
|
|||
|
|
<ul><li>Change the console mode value (01-03)<p>You can use the console service
|
|||
|
|
functions (65+21) to change the console mode from its current value to another.
|
|||
|
|
For example, you ordered your server with Operations Console LAN but you
|
|||
|
|
are having trouble getting it to work. Since you should have received the
|
|||
|
|
console cable for a direct attached console you would like to change the value
|
|||
|
|
from a 3 (LAN) to a 2 (direct).</p>
|
|||
|
|
</li>
|
|||
|
|
<li>Clear the resource and configuration for the LAN adapter used by Operations
|
|||
|
|
Console (C3)<p>This option allows you to disassociate the current LAN adapter
|
|||
|
|
used for Operations Console. You might use this option to overcome a mistake
|
|||
|
|
in the configuration. For example, you didn't see a keying error and you
|
|||
|
|
entered in another device's IP address. At connect time the client configured
|
|||
|
|
the server's LAN adapter for use by the console but the console fails to connect
|
|||
|
|
because the other device is active. This option would clear the server's
|
|||
|
|
network data for the console and allow you to delete the client's configuration
|
|||
|
|
and start over, allowing BOOTP to work again. See <a href="rzajrminnetwork.htm#minnetwork">Prepare
|
|||
|
|
for your network environment</a> for more information about BOOTP.</p>
|
|||
|
|
<p>Depending
|
|||
|
|
on your intent to clear the LAN adapter configuration you might also want
|
|||
|
|
to stop and restart the LAN adapter. The example here would benefit from
|
|||
|
|
following the clear function with a deactivate and activate (A3) function
|
|||
|
|
to save time from having to do an IPL.</p>
|
|||
|
|
</li>
|
|||
|
|
<li>Deactivate followed by an activate of the LAN adapter used by Operations
|
|||
|
|
Console (A3)<p>This option will allow you to reset the LAN adapter used by
|
|||
|
|
Operations Console in the event some network issue caused the server to get
|
|||
|
|
into a bad state and the console won't become active. This will force the
|
|||
|
|
LAN adapter to deactivate, and then start back up again. This may clear up
|
|||
|
|
the problem providing the original problem that caused the connection failure
|
|||
|
|
has been corrected.</p>
|
|||
|
|
<p>This option may be used in place of an IPL for some
|
|||
|
|
circumstances, such as after a clear of the LAN adapter configuration.</p>
|
|||
|
|
</li>
|
|||
|
|
<li>Dump Operations Console flight recorders to vlogs (DD)<div class="note"><span class="notetitle">Note:</span> This option
|
|||
|
|
will not work if the system is IPLed in D-mode.</div>
|
|||
|
|
<p>This option will
|
|||
|
|
allow you to capture valuable debug information regarding a console connection
|
|||
|
|
failure for support personnel. This method is less intrusive than performing
|
|||
|
|
a main storage dump which would force an IPL. By using the console service
|
|||
|
|
functions (65+21) an attempt is made to gather all the flight recorder logs
|
|||
|
|
from the many parts of the code used by Operations Console. A set of vlogs
|
|||
|
|
is created for major code 4A00 and minor code 0500. These vlogs can then
|
|||
|
|
be sent to your service provider for analysis. </p>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> When possible, perform
|
|||
|
|
an IPL on the system to guarantee all vlogs get created even if the IPL will
|
|||
|
|
fail. The intent is that LIC has started the vlog tasks prior to performing
|
|||
|
|
the dump of flight recorders.</div>
|
|||
|
|
</li>
|
|||
|
|
</ul>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><p>The following is an overview of how this function works:</p>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> If
|
|||
|
|
your system is not in manual mode, and the extended functions are not activated,
|
|||
|
|
or both, follow these steps: <ol><li>First, if your server uses a keystick, insert it in the key slot.</li>
|
|||
|
|
<li>Place the server into <samp class="codeph">manual</samp> mode by using the system's
|
|||
|
|
control panel.</li>
|
|||
|
|
<li>Using <span class="uicontrol">Up</span> and <span class="uicontrol">Down</span>, select
|
|||
|
|
function <span class="uicontrol">25</span>. Press <span class="uicontrol">Enter</span>.</li>
|
|||
|
|
<li>Use <span class="uicontrol">Up</span> to select function <strong>26</strong>. Press <span class="uicontrol">Enter</span>.</li>
|
|||
|
|
</ol>
|
|||
|
|
</div>
|
|||
|
|
<p>A function 65 is performed from one of the input methods.
|
|||
|
|
You have approximately 45 seconds to enter a function 21 for the system to
|
|||
|
|
pair the two functions together. If not, the function 21 is a force of DST
|
|||
|
|
to the console. Depending on the state of the current IPL you may or may
|
|||
|
|
not see a change at the console, assuming the console is still present after
|
|||
|
|
the 65. If the 65 and 21 are entered in less than 45 seconds a System Reference
|
|||
|
|
Code (SRC) of A6nn500A should appear on the control panel. The value of nn
|
|||
|
|
is dependent upon the console type currently being used, 01 thru 03. Repeating
|
|||
|
|
the 65 and 21 puts the system into an edit mode in which you can make a change
|
|||
|
|
or cause an action to be performed. After the second 65+21 pair is entered,
|
|||
|
|
the control panel will respond with the SRC of A6nn500B to indicate you are
|
|||
|
|
in edit mode. Each repeated 65+21 within edit mode will increment nn of the
|
|||
|
|
SRC until you reach the value representing what action you intend to perform.
|
|||
|
|
At this time you enter just a single 21 which will cause the selected function
|
|||
|
|
to be performed. The SRC should then become A6nn500C to indicate the function
|
|||
|
|
was successfully submitted. If at any time you exceed 45 seconds between
|
|||
|
|
the 65 and 21 or between succeeding 21s, SRC A6nn500D may be presented indicating
|
|||
|
|
a timeout condition and the system is no longer in edit mode. If you were
|
|||
|
|
intending to make a change you will need to restart the operations. This
|
|||
|
|
SRC will be reset in approximately 3 minutes. You can cancel out of edit
|
|||
|
|
mode by doing a function 66. The function 66 does not have to complete successfully.</p>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><p>The following codes will allow you to track your progress: </p>
|
|||
|
|
<p>A6nn 500x</p>
|
|||
|
|
<p><strong>Where nn means:</strong></p>
|
|||
|
|
<p>00 = No console defined <br />
|
|||
|
|
01 = Twinax console<br />
|
|||
|
|
02 = Direct attached Operations Console<br />
|
|||
|
|
03 = LAN Operations Console<br />
|
|||
|
|
C3 = Clear LAN configuration <br />
|
|||
|
|
A3 = Deactivate followed by an activate of the LAN Operations Console adapter<br />
|
|||
|
|
DD = Dump all console related flight recorder into a set of vlogs</p>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> <ol><li>Selecting 02 will automatically activate the asynchronous communications
|
|||
|
|
adapter used for Operations Console direct attached.</li>
|
|||
|
|
<li>Selecting 03 may also require a function A3 to activate the LAN adapter
|
|||
|
|
in rare cases. Also, if a LAN connected console is connected, the emulator
|
|||
|
|
may go to a <span class="cmdname">Disconnected</span> state. If so, you can start it
|
|||
|
|
again by clicking <span class="uicontrol">Communication</span> and selecting <span class="uicontrol">Connect</span>.</li>
|
|||
|
|
</ol>
|
|||
|
|
</div>
|
|||
|
|
<p><strong>Where x means:</strong></p>
|
|||
|
|
<dl><dt class="dlterm">A6nn 500A</dt>
|
|||
|
|
<dd>You are displaying the current console mode setting.</dd>
|
|||
|
|
<dt class="dlterm">A6nn 500B</dt>
|
|||
|
|
<dd>You did a second 65+21 pair so you are in edit mode.</dd>
|
|||
|
|
<dt class="dlterm">A6nn 500C </dt>
|
|||
|
|
<dd>You executed a second 21 to cause an action, such as setting the console
|
|||
|
|
to another value.</dd>
|
|||
|
|
<dt class="dlterm">A6nn 500D </dt>
|
|||
|
|
<dd>You waited too long after entering edit mode to cause an action so you
|
|||
|
|
will have to enter edit mode again if you intended to make a change. A 21
|
|||
|
|
at this time will force the console to DST, not cause an action.</dd>
|
|||
|
|
</dl>
|
|||
|
|
</div>
|
|||
|
|
<div class="section"><div class="p">If you do not want to make a change after entering edit mode you
|
|||
|
|
can wait 3 minutes and this completion code should show up indicating a change
|
|||
|
|
is no longer pending or you do a function 66 to cancel any pending changes
|
|||
|
|
and exit. <div class="note"><span class="notetitle">Note:</span> You have 45 seconds between a 65 and the 21 to start display
|
|||
|
|
mode or edit mode changes. If the time between these codes exceeds this limit
|
|||
|
|
the 21 will become a <kbd class="userinput">force DST console</kbd> request.</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div class="example"><p>An example of a console change would be:</p>
|
|||
|
|
<div class="p">The console type
|
|||
|
|
is 01 (twinaxial) and you want to use LAN (03). <p>65 - 21 = A601 500A You are in display mode and the console mode is 01<br />
|
|||
|
|
65 - 21 = A602 500B You entered edit mode and incremented the counter<br />
|
|||
|
|
65 - 21 = A603 500B You incremented the counter again<br />
|
|||
|
|
21 = A603 500C You invoked the action (set the console mode to 03)</p>
|
|||
|
|
</div>
|
|||
|
|
<p>If
|
|||
|
|
the LAN adapter already had a valid configuration, for example you previously
|
|||
|
|
configured the LAN adapter for use with the service tool server, then you
|
|||
|
|
would be ready to create a local console on a network configuration on the
|
|||
|
|
client, if one didn't already exist. You could then power off the twinaxial
|
|||
|
|
device and connect the Operations Console LAN configuration. </p>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> To
|
|||
|
|
reset the console without changing the console mode value you can do a 65
|
|||
|
|
- 21 - 21. The server should respond with A6nn500A after the first 21 and
|
|||
|
|
a A6nn500C after the second 21. This will cause the connection to the console
|
|||
|
|
to be dropped during the reset process. It is recommended that this function
|
|||
|
|
not be used when you already have a working console. This function will not
|
|||
|
|
correct all errors associated with a console failure, but rather resets the
|
|||
|
|
hardware associated with the configured console connection.</div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
<div>
|
|||
|
|
<div class="familylinks">
|
|||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrcommonservertasks.htm" title="Management tasks that are not dependant on a specific connectivity.">Common tasks</a></div>
|
|||
|
|
</div>
|
|||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|||
|
|
<div><a href="rzajrswitchconsolenotoperational.htm" title="If you develop a problem with the current console, you may be able to use one of the following methods to change the console mode.">Switching from one console type to another when the current console is not operational</a></div>
|
|||
|
|
<div><a href="rzajrrecoverydetails.htm" title="These are some details you should refer to concerning the console recovery action.">Recovery details</a></div>
|
|||
|
|
<div><a href="rzajra600500a.htm" title="System Reference Codes used to access console modes and console tasks">SRCs A6nn500x</a></div>
|
|||
|
|
</div>
|
|||
|
|
</div>
|
|||
|
|
</body>
|
|||
|
|
</html>
|