Prepare for your network environment

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.

Network security

IBM^® recommends treating the console over a LAN connection with the same physical security considerations and controls as a local console directly attached to the server or a twinaxial console. For instance, consider configuring a local console on a network in a network separate from the main network (or the company intranet) and strictly control access to the machine acting as the console.

BOOTstrap Protocol

A local Operations Console on a network uses the BOOTstrap Protocol (BOOTP) to configure the server service IP communications stack. The IP stack configuration plus server serial number and partition ID is requested in the Operations Console configuration wizard. The server broadcasts a BOOTP request. The Operations Console PC replies with the information submitted during the configuration wizard. The server then stores and uses the configuration information for the service IP communications stack.

The Operations Console PC must be placed on a network that is accessible by the server. 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. IBM recommends that this setup occur on the same physical network.

The BOOTP request carries the server serial number and partition ID. The server serial number is used to assign the IP configuration information. If you are having problems configuring the service IP communications stack, check that the Operations Console PC is on the same physical network and the server serial number and partition ID is 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 server and the PC. In some cases you may need an alternate console device to configure the connection in DST. To use BOOTP the network hardware used must be capable of AutoNegotiation of Speed and Duplex if using the 2838 Ethernet Adapter for the Operations Console connection.