Concepts for console networking
Consider configuring a local console on a network (LAN) in a network that is separate from the main network or the company intranet. Also consider strictly controlling access to the console.
You also might want to restrict LAN topologies for LAN-attached
local consoles to a single, physical router environment. This could
be accomplished in several ways, including connecting the PC and server
using an inexpensive hub or router, using an Ethernet crossover cable
(when using a 2849) or any Ethernet cable if you are using the Host Ethernet Adapter or the external network adapters (http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajr/rzajrhardwarereq.htm).
If you only have 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.
Note: Avoid x.x.x.1,
which might cause problems in some networks.
If 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.
