Use this information to assist you with identifying and complying with the minimum network configuration required to set up a local console on a network (LAN).
You need to install the LAN adapter for Operations Console according to your server model if you are not using the default embedded Ethernet port. To do this, see Operations Console hardware requirements. If your server is new and you ordered a local console on a network (LAN), the adapter should already be configured with the server. The LAN adapter should be dedicated for service tools.
Treating the console over a LAN connection with the same physical security considerations and controls as a local console that is directly attached or a twinaxial console is recommended. For example, consider configuring a local console on a network (LAN) in a network separate from the main network (or the company intranet) and strictly control access to the machine acting as the console.
Restricting LAN topologies for LAN-attached local Operations Consoles to a single, physical router environment is recommended. In the event that the local console on a network (LAN) is used in a larger network topology, 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 router 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 router, switch, or 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 networks). If, however, you have a network that many users share, or the devices go to the internet, then you should consult a network administrator for addresses.
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; typical Operations Console operation does not require this. This setup should occur on the same physical network.
The BOOTP request carries the server serial number and partition ID. The server serial number and partition ID are 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 are correct in the configuration. IBM System i5™ and eServer™ i5 models identify the first partition as 1 and not 0 as in the case of the older model 270 and 8xx servers.
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. BOOTP uses UDP ports 67 and 68 per RFC 951. For more information, see http://www.faqs.org/rfcs/rfc951.html
The success of BOOTP is dependent on the network hardware used to connect the server and the PC. In some cases, you might 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.
Networking security considerations are different depending on if your system is managed by a Hardware Management Console (HMC). Your network and network security is configured differently when your system is managed by an HMC. When you set up your HMC, you must decide if you want to configure a private or open network. If it is the first HMC in your network, you should configure that HMC as a DHCP server. For more information, see Types of HMC network connections and Gathering required configuration settings.