160 lines
12 KiB
HTML
160 lines
12 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="Plan for your backup console" />
|
||
|
|
<meta name="abstract" content="Here are some suggestions if you would like to plan for a backup for your console:" />
|
||
|
|
<meta name="description" content="Here are some suggestions if you would like to plan for a backup for your console:" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrplanconfig.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrconsoleplanningconsiderations.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrconsoletakeoverandrecover.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrminnetwork.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrmanageshared.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrscenariothree.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="backupconsole" />
|
||
|
|
<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>Plan for your backup console</title>
|
||
|
|
</head>
|
||
|
|
<body id="backupconsole"><a name="backupconsole"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan for your backup console</h1>
|
||
|
|
<div><p>Here are some suggestions if you would like to plan for a backup
|
||
|
|
for your console:</p>
|
||
|
|
<div class="section"><p>Most system plans include a level of redundancy to allow for the
|
||
|
|
event of hardware failures, however many people do not consider the console
|
||
|
|
in their plans. You should plan to back up your console information to recover
|
||
|
|
quickly from an unexpected loss of the console.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Considerations for a backup console:</h4><ul><li>The adapter location is fixed or at least limited for independent servers
|
||
|
|
or primary partitions. Based on your server's hardware requirements you may
|
||
|
|
have limited choices of console types. Try to accommodate at least one additional
|
||
|
|
console type, if possible.</li>
|
||
|
|
<li>Consider using the take over and recovery option as part of your backup
|
||
|
|
console strategy. However, the hardware used for the new console mode must
|
||
|
|
exist and be available at the time of recovery. For more information about
|
||
|
|
take over and recovery see the section: <a href="rzajrconsoletakeoverandrecover.htm#consoletakeoverandrecover">Take
|
||
|
|
over or recover an Operations Console connection</a>.</li>
|
||
|
|
<li>If you are working in a partitioned environment, consider: <ul><li>In an LPAR environment, the term "alternate console" is referring to the
|
||
|
|
twinaxial console type located in another IOP tagged as the alternate console.
|
||
|
|
If a failure of the primary console is detected, the system will automatically
|
||
|
|
try the alternate console's IOP. This function gives you another level of
|
||
|
|
protection. Tagging a single IOP as both the primary console and the alternate
|
||
|
|
console can result in the inability to select a console. Further isolation
|
||
|
|
can be planned by placing the alternate console IOP on a different bus so
|
||
|
|
that failures of the primary console's bus will not prevent a console from
|
||
|
|
being available.</li>
|
||
|
|
<li>Models 270 and 8xx are tagged for a console type only at the IOP level.
|
||
|
|
Placing two like console adapters, for example two 2849s or two 2771s, for
|
||
|
|
the same IOP can sometimes make it difficult to determine, in advance, which
|
||
|
|
adapter will be used for the console. IBM recommends only one console adapter
|
||
|
|
for the IOP tagged as the primary console to support Operations Console. The
|
||
|
|
lowest addressed adapter on the bus will be attempted first but if that adapter
|
||
|
|
is slow reporting to the system another adapter might get selected instead. </li>
|
||
|
|
<li>Consider a shared resource environment in which you can allocate and deallocate
|
||
|
|
a console supporting IOP to a partition on a part-time basis. Many work environments
|
||
|
|
rarely need a console device on a full-time basis and you can reduce your
|
||
|
|
initial cost of dedicated hardware by implementing this concept.</li>
|
||
|
|
<li>If the load source storage device fails and the system recovery will include
|
||
|
|
the use of the IBM<sup>®</sup> distribution
|
||
|
|
Licensed Internal Code media instead of a customer backup, and the system
|
||
|
|
is using Operations Console (LAN), you may have to use another console type
|
||
|
|
for the initial portion of the system recovery.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Planning configuration types for backup consoles:</h4><div class="p">When
|
||
|
|
planning the configuration of the backup console or consoles remember that
|
||
|
|
recovering from the loss of the console depends on many factors. Some of
|
||
|
|
these factors include, the model and series, the hardware resources available,
|
||
|
|
the previous console type, and the intended console type. Recovery might
|
||
|
|
consist of repairing the currently failed console or temporarily replacing
|
||
|
|
it with another console type. Most changes of a console type can be performed
|
||
|
|
without the need for an IPL but there may be circumstances in which an IPL
|
||
|
|
will still be necessary. When using the console service functions (65+21),
|
||
|
|
console-supporting hardware must be installed and available prior to performing
|
||
|
|
the function. Any partition tagging of resources must also have been done
|
||
|
|
already. <div class="important"><span class="importanttitle">Important:</span> If you plan to use Operations Console local
|
||
|
|
console on a network (LAN) as a backup to another console type, the network
|
||
|
|
adapter must be located in a console designated slot or properly tagged IOP.
|
||
|
|
If not previously configured, the BOOTP process will be used to configure
|
||
|
|
the server. For more information about setting up Operations Console on a
|
||
|
|
network (LAN), see: <a href="rzajrminnetwork.htm#minnetwork">Prepare for
|
||
|
|
your network environment</a>.</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Backup console configuration considerations:</h4><ul><li>If you access your server remotely, consider off-site console capability
|
||
|
|
or another connectivity for the console. A local console on a network can
|
||
|
|
be backed up with additional local console on a network PC. If the network
|
||
|
|
adapter were to fail, consider a local console directly attached to the server
|
||
|
|
as a backup. By changing the console type to a local console directly attached
|
||
|
|
to the server with remote access, you can add the ability for a remote PC
|
||
|
|
to become the console.</li>
|
||
|
|
<li>In an LPAR or multiple server environment you will most likely be using
|
||
|
|
multiple local console on a network configurations on a single PC as your
|
||
|
|
primary consoles. Consider additional PCs using this same type configuration.
|
||
|
|
Avoid supporting too many consoles on the same PC if possible. The PC resources
|
||
|
|
can be easily overwhelmed when supporting multiple consoles and remote control
|
||
|
|
panels. </li>
|
||
|
|
<li>Consider multiple local console on a network configurations in large environments
|
||
|
|
so that each PC has a core set of console responsibilities and the overlap
|
||
|
|
coverage of backup configurations with each other. For example, if you have
|
||
|
|
a PC that supports 10 local consoles on a network configuration and another
|
||
|
|
PC with the same number of primary consoles for another 10 partitions, instead
|
||
|
|
of backing up each PC with the other's configuration, you add a third PC and
|
||
|
|
spread the 20 consoles out so that two PCs back up a portion of each PC's
|
||
|
|
primary console configurations. Another consideration is a dedicated PC to
|
||
|
|
be the backup of a certain number of consoles, but not connected until necessary.</li>
|
||
|
|
<li>When using mostly networked consoles, consider setting up a local console
|
||
|
|
directly attached to the server on a PC and place it on a rollaway cart with
|
||
|
|
a console cable. If you have supporting adapters, you can quickly roll the
|
||
|
|
cart with the PC near the server or partition in need of the console. After
|
||
|
|
connecting the cable and changing the console mode value, you have a console
|
||
|
|
to replace the currently failed console. This same concept can be implemented
|
||
|
|
for twinaxial workstations just as easily.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If more than one local console on a network is planned, be certain
|
||
|
|
to create additional service tools device IDs on the server before you start
|
||
|
|
configuring the Operations Console PC. Each PC connecting to the same target
|
||
|
|
server or logical partition must have a unique service tools device ID.</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>In summary, consider incorporating as much redundancy as possible
|
||
|
|
into your console configuration. If you consider the question, "What happens
|
||
|
|
if this fails?" and you have another method to provide a console in place,
|
||
|
|
and if you make compromises and adjustments for the various hardware requirements
|
||
|
|
necessary to overcome the various levels where a failure might occur, you
|
||
|
|
will reduce your exposure to a catastrophic console failure situation.</p>
|
||
|
|
<p>For
|
||
|
|
more information on switching between console devices, see: <a href="rzajrmanageshared.htm#manageshared">Managing
|
||
|
|
your multiple consoles</a>.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrplanconfig.htm" title="In order to plan for your configuration, you should find out the specific connectivity types allowed by the various Operations Console configurations. The scenarios included offer specific configurations examples to help you select a console configuration most suited to your needs. If you plan ahead, you can include additional features in your configuration.">Plan for your configuration</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzajrconsoleplanningconsiderations.htm" title="There are several important items to consider when planning for Operations Console for one or more of your servers.">Console planning considerations</a></div>
|
||
|
|
<div><a href="rzajrconsoletakeoverandrecover.htm" title="Use these functions to take control of another console device.">Take over or recover an Operations Console connection</a></div>
|
||
|
|
<div><a href="rzajrminnetwork.htm" title="To prepare for your network environment, you need to identify and comply with the minimum network configuration required to set up an Operations Console local console on a network (LAN) configuration.">Prepare for your network environment</a></div>
|
||
|
|
<div><a href="rzajrmanageshared.htm" title="Manage multiple devices that can become consoles">Manage your multiple consoles</a></div>
|
||
|
|
<div><a href="rzajrscenariothree.htm" title="A scenario that discusses a situation in which you want to manage multiple servers or partitions.">Scenario: Consoles for multiple servers or partitions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|