Preparation For Your Network Environment - IBM i Series Handbook

Connecting to operations console
Hide thumbs Also See for i Series:
Table of Contents

Advertisement

need to deallocate the LAN card if you are not planning on using an Operations Console local console
on a network configuration or the service tools server.
Related reference
"Installing an Operations Console cable" on page 32
You need to install an Operations Console cable when your configurations have a local console that is
directly attached to the system.
Related information
Installing, upgrading, or deleting i5/OS and related software

Preparation for your network environment

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.
Important: You need to install the LAN adapter for Operations Console according to your model.
|
If your system is new and you chose a local console on a network configuration, the adapter is already
allocated for use by the system. The LAN adapter is dedicated for service tools. It is suggested that you
|
restrict LAN topologies for LAN-attached local consoles to a single, physical ring, hub, switch, or router
|
|
environment. In the event that the local console on a network is used in a larger network topology, it is
suggested that you use broadcast (DHCP) packet filtering. This might be as simple as connecting the PC
|
and system using an inexpensive hub or router. Temporarily, you could also use an Ethernet crossover
|
|
cable (when using a 2849 adapter). When you have only a single PC or a small number of devices
connected to the system using a hub, and these devices do not connect to another network or the
|
Internet, you can then use any numeric numbers for addresses, for example, 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). However, if you
have a network that many users share, or in which the devices are connected to the Internet, then you
|
should consult a network administrator for addresses.
|
A crossover cable is a standard network cable that has the transmit and receive signal wires reversed. This
|
|
virtually allows each end to act as if a hub, switch, or router were between them. The use of a crossover
|
cable might also require a nonstandard network configuration at the system and PC.
Network security
It is suggested that you treat the console over a LAN connection with the same physical security
considerations and controls as a local console directly attached to the system or a twinaxial console. For
instance, consider configuring a local console on a network separate from the main network (or the
company intranet) and strictly controlling access to the PC that acts as the console.
BOOTstrap Protocol
A local Operations Console on a network uses the BOOTstrap Protocol (BOOTP) to configure the system
service IP communications stack. The IP stack configuration plus the system serial number and the
partition ID are requested in the Operations Console configuration wizard. The system broadcasts a
BOOTP request. The Operations Console PC replies with the information submitted during the
configuration wizard. The system then stores and uses the configuration information for the service IP
communications stack.
The system will perform a BOOTP when the console type is set to Operations Console (LAN) and the
|
system does not contain a valid IP address for the service host name (service interface).
|
The Operations Console PC must be placed on a network that can be accessed by the system. This can be
the same physical network or a network that permits broadcast packets to flow. This is an initial setup
requirement. Normal Operations Console operation does not require this. It is suggested that this setup
occur on the same physical network.
13
Operations Console

Advertisement

Table of Contents
loading

Table of Contents