IBM System i Manual page 20

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 a crossover cable or using an inexpensive hub with only the PC and system attached.
|
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.
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 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.
The BOOTP request carries the system serial number and partition ID. The system serial number and
partition ID are used to assign the IP configuration information. If you are having problems configuring
the service IP communications stack, verify that the Operations Console PC is on the same physical
network, and that the system serial number and partition ID are correct in the configuration.
A local console on a network (LAN) uses ports 2323, 3001, and 3002. To use Operations Console in a
different physical network the router and firewall must allow IP traffic on these ports.
| The success of BOOTP is dependent on the network hardware used to connect the system and the PC. In
some cases, you might need a different device to configure a console connection using system service
|
tools (SST). To use BOOTP, the network hardware used must be capable of autonegotiation of speed and
|
| duplex when using the 2838 Ethernet Adapter for the Operations Console connection.
Related reference
"Planning considerations for your backup console" on page 6
Most system plans include a level of redundancy to allow for the event of hardware failures; however,
many people do not consider the console in their plans. To recover quickly from an unexpected loss of
your console, you need to plan for a backup console.
"Operations Console hardware requirements" on page 18
You need to meet the PC and System i hardware requirements for an Operations Console
configuration.
12
System i: Connecting to System i Operations Console