Table of Contents
Advertisement
– If the load source storage device fails and the system recovery will include the use of the IBM
|
|
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.
|
Planning configuration types for backup consoles:
|
|
Note: Recovering from the loss of the console depends on many factors. Some of which would be the
model, the hardware resources available, the previous console type, and the new 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.
|
|
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. See
Prepare for your network environment.
|
Backup console configuration considerations:
|
v If your server is accessed 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.
v 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.
|
v 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.
|
|
v 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.
|
|
Note: 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.
In summary, consider as much redundancy as possible for your console needs. If you consider "what if
|
|
this fails" and you have another method to provide a console, and also make compromises for the
hardware requirements necessary to overcome the various levels where a failure might occur, you will be
|
reducing your exposure to a catastrophic console failure condition.
|
See Managing your multiple consoles for information on the ability to switch between console devices.
|
8
iSeries: iSeries Access for Windows Operations Console
Advertisement
Table of Contents
