System information

171
A test of Proxy ARP is to ping the twinax attached IBM Network Station from a
remote host. From
As2.mycompany.com , a ping is sent to address
10.1.1.194. The attempt was successful.
5.7.11 Summary
This scenario installed a twinax subnet on a DHCP server. The twinax
address range, that was used, is a subset of the address space 10.1.1.x. A
range of 64 IP addresses was allocated for the twinax subnet.
A DHCP server configuration was built for the twinax subnet. When the twinax
IBM Network Stations were powered on, the AS/400 system automatically
built the necessary TDLC configurations and a TCP/IP interface for the
workstation controller. A manual change was required on this TCP/IP
interface and the IBM Network Stations required a reboot.
After the IBM Network Station was restarted, connectivity was tested to the
rest of the network by starting a 5250 TELNET session to a remote host. This
same remote host successfully sent a ping request to the IBM Network
Station.
5.8 Twinax IBM Network Station with a Remote DHCP Server Scenario
This scenario shows how to configure and use a remote DHCP server to
supply network information to twinax connected IBM Network Stations.
It is not necessary to use the same system, to which the twinax attached IBM
Network Stations are connected, as your DHCP server. You can utilize
another DHCP server in your network.
5.8.1 Scenario Overview
In this scenario, there are twinax attached IBM Network Stations connected
to a local AS/400 system. Although this AS/400 system is not acting as a
DHCP server, it is serving as a BOOTP/DHCP Relay Agent.
Locally attached IP over twinax devices have their DHCPDISCOVER
messages forwarded to a DHCP server that is running on a different AS/400
system. This is done to obtain a network address and start-up information
that is required for boot up.
Figure 80 on page 172 shows the logical network topology that is used in this
scenario. The twinax IBM Network Stations are attached to the