System information

191
TCP/IP interface. It was then necessary to manually change the TCP/IP
interface to include the As1 LAN address as the Associated Local Interface.
The As1 system was then configured as a BOOTP/DHCP Relay Agent. This
relay agent was configured and started through Operations Navigator. The
configuration was set to forward DHCP messages from the locally attached
twinax subnet to the remote DHCP server, As2.
The address pool, 10.1.1.x, was split within the DHCP configuration on the
As2 system. The two configured pools were then re-grouped to form a single
pool within DHCP.
An IP address pool for the remote twinax subnet was configured, within
DHCP, on the As2 system. The DHCP server was then started on the As2
system.
After the configuration was complete the IBM Network Station was again
started. However, this time the DHCP messages were forwarded by the local
DHCP/BOOTP Relay Agent (As1) to the remote DHCP server, As2. The IBM
Network Station then obtained the necessary network start up information
that it required to boot up successfully.
5.9 Twinax IBM Network Station with Remote Boot Server
It is possible to have the IBM Network Station send a request to a DHCP
server, for network information, and have that information returned. The
returned information contains the name or IP address of another host that
serves the IBM Network Station with its kernel and user configuration.
You can also configure the AS/400 DHCP server to provide the options that
are necessary to instruct the IBM Network Station to load its kernel from a
server other than the DHCP server host. Up to two systems can be specified
from which the user configuration data can be loaded.
Figure 100 on page 192 shows a twinax Network Station attached to an
AS/400 system, As1. In this scenario, the twinax Network Station goes to As1
system for its network configuration. The As1 system then replies to the
Network Station that it should go to address 10.1.1.50, system As2, for the
kernel and configuration data. The Network Station then accesses As2, using
the workstation controller and the LAN for its base code and configuration
data.