IBM E Server i Series Manual page 15

v 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.
v For secondary partitions consider:
– In an LPAR environment, the term alternate console is referring to a 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 gives you another level of protection. Tagging a single IOP
as both the primary console and the alternate console does not give you this
protection from an IOP-type failure. 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.
– The current implementation for tagging a console type is only at the IOP
level. Placing two network adapters for the same IOP can sometimes make it
difficult to determine, in advance, which network adapter will be used for the
console. IBM recommends only one network adapter for the IOP tagged as
the primary console to support Operations Console local console on a
network.
– 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.
– 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 additional backup consoles:
Note: If you plan to use Operations Console local console on a network (LAN) as
a backup to another console type, you must have the console type set to
Operations Console (LAN) and have the associated network adapter
configured prior to needing this device. Setting the console to Operations
Console (LAN) does not prevent an Operations Console (direct) or twinaxial
from becoming the console during an IPL. Just make certain only one
console type is available during the IPL.
Backup console configuration types:
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
Chapter 3. Plan for Operations Console
9