Learn about the minimum network configuration requirements for setting up a local console on a network (LAN).
If you are not using the default embedded Ethernet port as the default console port, you need to install the LAN adapter for Operations Console according to your server model. 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.
You might want to treat 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. For example, consider configuring a local console on a network (LAN) in a network that is separate from the main network (or the company intranet) and strictly control access to the machine acting as the console.
You also might want to restrict LAN topologies for LAN-attached local Operations Consoles to a single, physical router environment. This might be as simple as connecting the PC and server using an inexpensive hub or router. Temporarily, you could also use an Ethernet crossover cable (when using a 2849) or any Ethernet cable if you are using the Host Ethernet Adapter 5767/5768, or 5706/5707 network adapter. 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. For example, use 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).
In the event that the local console on a network (LAN) is used in a larger network topology, or the devices go to the Internet, use DHCP packet filtering and consult a network administrator for addresses.
Although the system and PC can still perform a standard BOOTP operation as described here, i5/OS® Version 6 Release 1 enables the automatic discovery of a connection between the system and a PC. This function, called VSDISCOVER, is a mechanism used solely for Operations Console. Both the system and PC listen for a special broadcast frame from the network and when received, there is a negotiation using ports 67 and 68, and the system and PC can use the data exchanged to configure itself, if needed. In addition, the PC creates a configured connection that you can use to start a console session. This VSDISCOVER function is the default mechanism for configuring a connection. The BOOTP process is still used when VSDISCOVER is not necessary, such as when you already have a configured connection and the network data needs to be reset.
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.
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 a different 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 when your system is managed by a Hardware Management Console (HMC) because your network and network security are configured differently. When you set up your HMC, determine whether you want to configure a private or open network. If it is the first HMC in your network, configure that HMC as a DHCP server. For more information, see Types of HMC network connections and Preparing for HMC configuration.