Table of Contents
Advertisement
For this scenario, configure a local console on a network. See Set up Operations Console to complete an
interview that will produce a checklist specific to your configuration.
Advantages:
v You can configure a single PC to be the console for several different servers or partitions as long as
they are connected to the service connection network.
v The administrator will not need to be physically near the server to manage the console.
v Security features are available to protect your console connections.
v A local console on a network is the connectivity of choice for partitions in an LPAR environment. For
more information on consoles on partitioned servers, see Plan for logical partitions.
v Multiple PCs can be configured as the console to a server or partition, but only one can be active at a
time.
Disadvantages:
v No console is available in the event that a network failure takes place unless a backup console is in
place. Configure a local console directly attached to the server or a twinaxial console for backup. For
more information, see Plan for your backup console.
v Your server will need a separate LAN card to be used by the console or other service tools. For more
information, see Meet Operations Console hardware requirements.
Prepare for your network environment
|
|
This information assists you in identifying and complying with the minimum network configuration
required to set up an Operations Console local console on a network (LAN) configuration.
|
|
Important: You need to install the LAN adapter for Operations Console according to your iSeries model.
To do this, see Meet Operations Console hardware requirements. If your server is new and you ordered a
|
local console on a network configuration, the adapter should already be configured for use by the server.
|
|
The LAN adapter should be dedicated for service tools. It is recommended that you restrict LAN
topologies for LAN-attached local consoles to a single, physical ring, hub, switch, and router
|
environment. In the event that the local console on a network is used in a larger network topology,
|
|
broadcast (DHCP), packet filtering is always recommended. This might be as simple as connecting the PC
and server using a crossover cable or using an inexpensive hub with only the PC and server attached.
|
|
When you have only a single PC or small number of devices connected to the server using a hub and
|
these devices do not connect to another network or the internet, you can then use any numeric numbers
for addresses. An example would be 1.1.1.x or 10.220.215.x (where x can be 2 through 255 but avoid
|
|
x.x.x.1 which might cause problems in some hubs). If however, you have a network in which many users
|
share or the devices go to the internet then you should consult a network administrator for addresses.
11
Operations Console
Advertisement
Table of Contents
