Scenarios: Select Your Configuration - IBM E Server i Series Manual

v When using mostly networked consoles, consider setting up a local console
Note: If more than one local console on a network is planned, be certain to create
In summary, consider as much redundancy as possible for your console needs. If
you consider "what if this fails" and you have another route 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.

Scenarios: Select your configuration

The following scenarios assists you in choosing your Operations Console
configuration.
The table provides an overview of the advantages and disadvantages of each
scenario.
10
iSeries: iSeries Access for Windows Operations Console
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 is not using it until necessary.
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 activating the line, you have a console to replace the currently
failed console. This same concept can be implemented for twinaxial workstations
just as easily.
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.
Scenario: A single console directly attached to the server without remote
support
A scenario that discusses a situation in which you may want a single console
attached to the server.
Scenario: A single console directly attached to the server with remote
support
A scenario that discusses the ability to dial-in to the console from a remote
location.
Scenario: Consoles for multiple servers or partitions
A scenario that discusses a situation in which you want to manage multiple
servers or partitions.
Scenario: Directly dial-up a server from a remote location
A scenario that discusses a situation in which you might need to access the
server without a console from a console at a remote location.