System information

Introduction
25
Services Console log. As an alternative, Display Station Passthru can be
used to sign on to the remote AS/400 system and then a native AS/400
Telnet session can be used to
view the Network Station User Services
Console.
An example of a remote boot server environment is shown in Figure 5. In this
scenario, the TCP/IP network is comprised of a central site AS/400 in
Chicago, two remote sites with AS/400s and a mixture of PCs and IBM
Network Stations. The central site in Chicago and the remote site in Boston
are connected through routers across a wide area network. However, a PPP
(point-point protocol) is used to connect the Seattle AS/400 system to the
central site AS/400 system and network in Chicago. (PPP requires OS/400
V4R3 and V4R2 or later allows the AS/400 system to provide routing
functions.) For the Seattle AS/400 system to provide routing functions for the
other devices on its network, its TCP attributes had to be changed using the
Change TCP/IP Attributes (CHGTCPA) command and specifying *YES for the
IP Datagram Forwarding parameter.
Figure 5. Remote Boot Servers Example
Please refer to Chapter 4, “Remote Servers and Split Boot Servers” on page
107 for additional information on the remote boot server option.
10.1.1.2
10.2.1.2
Router
Router
......
......
......
(PPP)
10.3.1.2
10.1.1.6
10.1.1.3
10.1.1.7
10.1.1.35
10.1.1.36
10.1.1.40
10.3.1.4
10.3.1.24
10.2.1.6
10.2.1.18
10.2.1.19
10.2.1.3
Chicago
Seattle
Boston
AS4CHI
AS4BOS
AS4SEA
......