SimpleTech STI-FAX/33.6 Technical Information

SG24-5187-00International Technical Support Organizationhttp://www.redbooks.ibm.comAS/400 IBM Network Station:Techniques for Deployment in a WAN Fant

viii AS/400 IBM Network Station: Techniques for Deployment in a WANC.2.1 WAN Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . .

80 AS/400 IBM Network Station: Techniques for Deployment in a WANNetwork Station at start up to obtain this information. It can be read from the displ

Using Flash Cards with the Network Station 81Figure 14. Console Log Example: Loading the 5250 Emulator from the Test Image DirectoryAfter you confirm

82 AS/400 IBM Network Station: Techniques for Deployment in a WAN1. Open the file flash.nsm in /QIBM/ProdData/NetworkStation/configs using a PC editor

Using Flash Cards with the Network Station 831. Power off the IBM Network Station.2. Ensure that the write protect switch on the Flash card is in the

84 AS/400 IBM Network Station: Techniques for Deployment in a WAN3.3.9 Loading the Image onto the Flash CardIf you completed the steps in Section 3.3

Using Flash Cards with the Network Station 853. The boot.nsl file, which resides in the path /QIBM/ProdData/NetworkStation/nsflash, must be edited bef

86 AS/400 IBM Network Station: Techniques for Deployment in a WAN7. After the copy operation is complete, look for the message on the AS/400 that info

Using Flash Cards with the Network Station 876. Copy the kernel to the Flash card file system by entering the following command in the local file mana

88 AS/400 IBM Network Station: Techniques for Deployment in a WAN • mwm.nws • nfsd.nws • ns3270.nws • ns5250.nws • ns5250xx.nws • sbcs_im.nws •

Using Flash Cards with the Network Station 89Before copying files from the local file system to a remote file system, consider the following points:

© Copyright IBM Corp. 1999ixFigures1. Roaming User Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82. Separati

90 AS/400 IBM Network Station: Techniques for Deployment in a WAN1. Open the file flash.nsm in /QIBM/ProdData/NetworkStation/configs using a PC editor

Using Flash Cards with the Network Station 91Figure 15. Updated Example of the Flash.nsm File3.3.10.2 Modifying the NVRAM Configuration for Local Bo

92 AS/400 IBM Network Station: Techniques for Deployment in a WANWe highly recommend that you reset NVRAM to the factory defaults prior to any major c

Using Flash Cards with the Network Station 9310.Press PF4 (Set Boot Parameters).11.Type kernel.Z in the Boot File field.12.Leave the TFTP Boot Directo

94 AS/400 IBM Network Station: Techniques for Deployment in a WANProvided that you entered the correct system information when configuring the three e

Using Flash Cards with the Network Station 95chosen to use the local file manager to copy files from the AS/400 IFS, instead of using the NFS support.

96 AS/400 IBM Network Station: Techniques for Deployment in a WANstandard.nsm file and then overrides the values necessary to enable Flash booting. Th

Using Flash Cards with the Network Station 973.4.1 Scenario ObjectivesIn this scenario, we want to accomplish the following objectives: • Configure

98 AS/400 IBM Network Station: Techniques for Deployment in a WAN • Only one Flash card is required at each remote location in this case. • Multiple

Using Flash Cards with the Network Station 99The peer Network Station authenticates and load volatile data from the central AS/400 system in the same

x AS/400 IBM Network Station: Techniques for Deployment in a WAN40. QTDL824300 Line Description. . . . . . . . . . . . . . . . . . . . . . . . . . . .

100 AS/400 IBM Network Station: Techniques for Deployment in a WANIf each user using different functions, for example one person requires the Netscape

Using Flash Cards with the Network Station 1013.5.3 Creating a Peer Boot Configuration FileA new file must be created in /QIBM/ProdData/NetworkStatio

102 AS/400 IBM Network Station: Techniques for Deployment in a WAN3.5.4 Configuring the Peer Boot Network StationThe NVRAM settings on the peer Netwo

Using Flash Cards with the Network Station 103If prompted for an administrator password, enter it now (this is the password an administrator can set u

104 AS/400 IBM Network Station: Techniques for Deployment in a WAN26.Press Enter.27.Press Enter again to reboot the IBM Network Station.The IBM Networ

Using Flash Cards with the Network Station 1052. Click on the Messages button to view the log.3. Use the vertical scroll bar to move up and down the l

106 AS/400 IBM Network Station: Techniques for Deployment in a WANWe started the peer boot Network Station and checked the system logs to ensure there

© Copyright IBM Corp. 1999107Chapter 4. Remote Servers and Split Boot ServersThis chapter describes how the split boot feature can be used in differe

108 AS/400 IBM Network Station: Techniques for Deployment in a WAN1.Acquire IP address: It may be already configured into NVRAM or it may be acquired

Remote Servers and Split Boot Servers 109These functions are: • Base code server • Terminal-based configuration server • Authentication and configu

xi82. AS/400 Operations Navigator - TCP/IP Server Status. . . . . . . . . . . . . . . 17583. Automatically Created QTDL Descriptors . . . . . . . .

110 AS/400 IBM Network Station: Techniques for Deployment in a WAN3. Migrate the user-based configuration and data of the users to the new server.4.4.

Remote Servers and Split Boot Servers 111Figure 23. Consolidated Server Topology4.4.3 Consolidating ServersTo consolidate our authentication and con

112 AS/400 IBM Network Station: Techniques for Deployment in a WANIn this example, 10.1.1.2 is used in the previous parameter because it is our centra

Remote Servers and Split Boot Servers 113Figure 25. User ITSCIDGRPANow create the group profile on site A by completing the following steps:8. Sign o

114 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 26. Group CreationNow create the users profile:13.Type the following command

Remote Servers and Split Boot Servers 115Figure 27. User’s Attributes (Part 1 of 2) Figure 28. User’s Attribute (Part 2 of 2)Now we need to migrate

116 AS/400 IBM Network Station: Techniques for Deployment in a WANWe are going to use a PC with Windows 95 and CA/400 connected to an AS/400 in this e

Remote Servers and Split Boot Servers 117Figure 29. Paste Group’s Configuration FilesThe group configuration files should be copied, as shown in Figu

118 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 30. Resulting Group’s Configuration FilesIn the next steps, the user configu

Remote Servers and Split Boot Servers 119folder on the left pane. Press the right mouse button over the folder and select Copy.30.Select the G:—> Q

xii AS/400 IBM Network Station: Techniques for Deployment in a WAN124.Console Log Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

120 AS/400 IBM Network Station: Techniques for Deployment in a WAN4.5 Roaming FeatureThe roaming feature allows mobile users (for example, users that

Remote Servers and Split Boot Servers 121After the Network Station has booted up, the visiting user selects the Roam button on the login dialog. The u

122 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 32. Fully Centralized ConfigurationThe advantages for this strategy are: •

Remote Servers and Split Boot Servers 1234.5.1.2 Remote Boot with Centralized ConfigurationsThis example, is perhaps the most common configuration (s

124 AS/400 IBM Network Station: Techniques for Deployment in a WAN4.5.1.3 Remote Boot Servers Provide All FunctionsRemote boot servers are used to pr

Remote Servers and Split Boot Servers 125If you are using a centralized model, it can appear as shown in the Figure 35.Figure 35. Centralized ModelIn

126 AS/400 IBM Network Station: Techniques for Deployment in a WANadvantages and disadvantages. In general, the distributed model is the opposite.The

© Copyright IBM Corp. 1999127Chapter 5. Twinax Attachment of Network StationsThe non-programmable terminal (NPT) has, traditionally, been one of the

128 AS/400 IBM Network Station: Techniques for Deployment in a WANFor further information regarding the IBM Network Station Twinax model, visit the We

Twinax Attachment of Network Stations 1295.4.1 Scenario OverviewThis scenario shows an example of a twinaxial Network Station subnet attached to an A

© Copyright IBM Corp. 1999xiiiTables1. Applications and Printer Data Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . 162. Elements Loade

130 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 36. TCP/IP Network Topology for Basic IP over Twinax Scenario5.4.6 Task Sum

Twinax Attachment of Network Stations 131Network Stations can be on port 1 or any other available port that does not have NPT’s connected. This type o

132 AS/400 IBM Network Station: Techniques for Deployment in a WANe. Enter L to reset the NVRAM.f. Enter S save the defaults into NVRAM.g. Enter Y to

Twinax Attachment of Network Stations 133The QHST log on the AS/400 system has additional messages logged, as shown in Figure 38.Figure 38. Display o

134 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 39. Configuration Status Display of Automatically Created QTDL DescriptorsFi

Twinax Attachment of Network Stations 135Figure 41. Automatically Created Device Type 5150 under CTL01 The next step is to create an IP interface for

136 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 42. Adding IP Interface for QTDLC824300 Line Description3. Start the interfa

Twinax Attachment of Network Stations 137 • The TCP/IP address (in this scenario 10.10.10.2) assigned to the Network Station. • The IP address (in t

138 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 45. Updated 5150 Device Description5. When the IBM Network Station was initi

Twinax Attachment of Network Stations 139Figure 47. Display of BOOTP Table Entry5.4.10 Testing ConnectivityIn this scenario, the IBM Network Station

xiv AS/400 IBM Network Station: Techniques for Deployment in a WAN

140 AS/400 IBM Network Station: Techniques for Deployment in a WAN5.5 Transparent Subnet MaskingIn this scenario, we allow the twinax subnet access t

Twinax Attachment of Network Stations 141Figure 48. Transparent Subnetting Example5.5.1 Twinax Transparent Subnetting ExampleThe twinax subnet requi

142 AS/400 IBM Network Station: Techniques for Deployment in a WANLooking at the Figure 49 on page 141, a mask of 128 in the last octet provides two a

Twinax Attachment of Network Stations 143Figure 50. Transparent Subnetting Twinax Scenario with Class C TCP/IP AddressFigure 51. Transparent Subnett

144 AS/400 IBM Network Station: Techniques for Deployment in a WANboundary addresses within a group cannot be used, the group of addresses for subnet

Twinax Attachment of Network Stations 1455.6.3 Scenario AdvantagesThe advantages of this scenario are: • It is easy to connect twinax attached IBM N

146 AS/400 IBM Network Station: Techniques for Deployment in a WAN5.6.6 Task SummaryThe following tasks are required to complete this scenario:1. Pla

Twinax Attachment of Network Stations 147address of 10.1.1.193 is designated for the workstation controller (interface address).Figure 53 provides a v

148 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 54. Display of QSYSOPR Message Queue on AS/400 SystemThe QHST log, on the AS

Twinax Attachment of Network Stations 149The display device created underneath the workstation controller (CTL01 in this case) is shown in Figure 56.

© Copyright IBM Corp. 1999xvPrefaceGain an edge implementing an IBM Network Station solution in a Wide Area Network (WAN). This redbook offers a numbe

150 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 57. Adding IP Interface for QTDLC827500 Line Description3. To start the inte

Twinax Attachment of Network Stations 151Figure 59. TCP/IP Interface Status DisplayIf you return to the Network Station, the boot process should be c

152 AS/400 IBM Network Station: Techniques for Deployment in a WANThe display device, DSP02, is also updated to include the assigned IP address of 10.

Twinax Attachment of Network Stations 153Figure 63. Display of BOOTP Table EntryIf NVRAM was chosen in the IBM Network Station Setup Utility when the

154 AS/400 IBM Network Station: Techniques for Deployment in a WAN5.7 Twinax IBM Network Station with Local DHCP Server ScenarioThis scenario attache

Twinax Attachment of Network Stations 1555.7.5 Scenario Network ConfigurationFigure 64 shows the network topology used for this scenario. The twinax

156 AS/400 IBM Network Station: Techniques for Deployment in a WAN5.7.6 Task SummaryThe following tasks are required to complete this scenario:1. Pla

Twinax Attachment of Network Stations 157Figure 65. Applying Subnet Mask to Carve a Contiguous Range for Twinax Subnet5.7.8 Configuring the DHCP Ser

158 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 66. AS/400 Operations Navigator - Configure DHCP Server3. Double-click Netwo

Twinax Attachment of Network Stations 1594. Double-click Servers. The display Figure 68 is shown.Figure 68. AS/400 Operations Navigator - Selecting N

xvi AS/400 IBM Network Station: Techniques for Deployment in a WANSpecialist in the United Kingdom AS/400 Business. Prior to joining IBM, he worked fo

160 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 70. AS/400 Operations Navigator - DHCP Configuration7. Right-click the mouse

Twinax Attachment of Network Stations 1618. As shown in Figure 71 on page 160, select the General tab. Specify Twinax Subnet 10.1.1.192 in the Name fi

162 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 72. DHCP Twinax Address Pool Range13.Click the Leases tab.14.Set the lease t

Twinax Attachment of Network Stations 16315.Click the Options tab, as shown Figure 73 on page 163.16.Add the options for the DHCP server-to-server sho

164 AS/400 IBM Network Station: Techniques for Deployment in a WAN17.Click OK.18.Close the DHCP configuration window. If the DHCP server is running, y

Twinax Attachment of Network Stations 165using. In most cases, you should be able to use the same port and address for the replacement IBM Network Sta

166 AS/400 IBM Network Station: Techniques for Deployment in a WANe. Enter L to reset the NVRAM.f. Enter S save the defaults into NVRAM.g. Enter Y to

Twinax Attachment of Network Stations 167Figure 75. QTDLxxxxxx Line, Controller, and Device Configuration StatusFigure 76 shows the twinaxial data li

168 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 77. Device Type 5150 under CTL01The system automatically creates a TCP/IP in

169Figure 78 shows the interface descriptor when it is first created by the system. Notice the LCLIFC parameter defaults to *NONE.Figure 78. TCP/IP

xviiThanks to the following people for their invaluable contributions to this project:Ray Romon, Network Station Development ManagerChuck Carmack, Ne

170 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 79. TCP/IP Interface Updated with an Associated Local Interface ValueA check

171A 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.

172 AS/400 IBM Network Station: Techniques for Deployment in a WANBOOTP/DHCP Relay Agent server which forwards all DHCP broadcasts, originating from t

173Network Station. It is also assumed that the IBM Network Station can start as a DHCP client. The following tasks start from the point when the fir

174 AS/400 IBM Network Station: Techniques for Deployment in a WANdisable the subnet on the As1 system by right-clicking on the subnet and clicking on

175Figure 82. AS/400 Operations Navigator - TCP/IP Server Status5.8.4 Power on the IBM Network StationStart the twinax IBM Network Station to allow

176 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 83. Automatically Created QTDL DescriptorsA TCP/IP interface has also been a

1775.8.5 Manually Changing the Auto Created TCP/IP InterfaceFor the twinax IBM Network Station to see and be seen across the network, the LAN interf

178 AS/400 IBM Network Station: Techniques for Deployment in a WAN2. From a command line, enter CHGDHCPA MODE(*RELAY),and press Enter. This changes th

17910.Click OK. The resulting display is shown in Figure 87.Figure 87. BOOTP/DHCP Relay Agent Configuration11.From Operations Navigator, right-click

xviii AS/400 IBM Network Station: Techniques for Deployment in a WAN

180 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 88. AS/400 Operations Navigator - TCP/IP Server StatusThe BOOTP/DHCP Relay A

181Figure 89. Applying Subnet MasksThese pools must be defined in the DHCP configuration. Complete these steps:1. From Operations Navigator, select

182 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 90. AS/400 Operations Navigator - Creating New Subnet in DHCP5. Click on the

183Figure 91. DHCP ConfigurationThe second group display is shown in Figure 92 on page 184.

184 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 92. DHCP ConfigurationThe next step is to group the two address ranges toget

185Figure 93. DHCP Configuration - Forming a New Subnet Group3. Specify a valid description in the Name field. Blanks or special characters are not

186 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 94. DHCP configuration - New Subnet Group Properties4. Highlight the first a

187Figure 95. DHCP Configuration - Selection of Subnets for New Subnet GroupFigure 96. DHCP Configuration - Showing Contents of Subnet Group5.8.8

188 AS/400 IBM Network Station: Techniques for Deployment in a WANnot configured as discussed in Section 5.7.8, “Configuring the DHCP Server As1 for T

189Figure 98. DHCP Configuration - Remote Twinax IP Address Pool8. Click the Options tab and add the options shown in Table 19.Table 19. Options an

© Copyright IBM Corp. 19991Chapter 1. Introduction Although IBM Network Stations can be locally attached to your AS/400 using twinax, Ethernet, or To

190 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 99. Operations Navigator - DHCP Configuration Display Showing Subnet Groups1

191TCP/IP interface. It was then necessary to manually change the TCP/IP interface to include the As1 LAN address as the Associated Local Interface.T

192 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 100. Twinax Attached Network Station Obtaining Network Configuration5.9.1 S

1935.9.3 Scenario AdvantagesThe advantages of this scenario include: • Easier to connect twinax-attached IBM Network Stations to an existing networ

194 AS/400 IBM Network Station: Techniques for Deployment in a WAN5.9.6 Task SummaryThe following tasks are required to complete this scenario:1. Con

195Figure 102. Operations Navigator - DHCP Twinax Subnet Properties2. Click the Options tab.3. From the previous DHCP configuration, options 1, 3, 6

196 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 103. DHCP Configuration - Defining TFTP Server4. Click Templates.5. Click Ne

197Figure 104. DHCP Configuration - Option 211 Configuration Protocol Template6. Click OK.7. Repeat the steps 4 and 5 to add the user options 212, 2

198 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 106. DHCP Configuration - Option 213 Configuration File Path TemplateFigure

199Figure 108. DHCP Configuration - Viewing Available Options9. The newly defined tags must now have the corresponding values added. For each of the

2 AS/400 IBM Network Station: Techniques for Deployment in a WANThe IBM Network Station Series 300, the Internet network computer, is an ideal solutio

200 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 109. DHCP Configuration - Adding Tag 211 Configuration Protocol

201Figure 110. DHCP Configuration - Adding Tag 212 Terminal Server

202 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 111. DHCP Configuration - Adding Tag 213 Configuration File Path

203Figure 112. DHCP Configuration - Adding Tag 214 Protocol 10.After the tags are added, click OK. You are returned to the main DHCP server display.

204 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 113. Operations Navigator - Modified DHCP Configuration Display11.Close the

205Figure 114. Netstat *CNN Display Showing Active TCP/IP ServersFigure 115. Operations Navigator - TCP/IP Server Status Display5.9.9 Configuring

206 AS/400 IBM Network Station: Techniques for Deployment in a WANadapter of the system. In this case, this parameter has the value of 10.1.1.2. A dis

207Figure 117. Set Configuration Parameters Display (Before Bootup)The Network Station is now ready to be powered up. The messages seen on the initi

208 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 119. Set Network Parameters Display (After Bootup)Figure 120. Set Configura

© Copyright IBM Corp. 1999209Chapter 6. Problem DeterminationThis section outlines some of the more commonly used tools that can help you in diagnosi

Introduction 3Manager from any location on their TCP/IP network using an appropriate browser. In June of 1998, a new release with significant enhancem

210 AS/400 IBM Network Station: Techniques for Deployment in a WAN3. From the file pulldown menu select Terminal.4. Select Preferences5. Change the Bu

Problem Determination 2116.1.2 Accessing the System Log Using the Console ManagerYou can also view the system log directly on the Network Station by

212 AS/400 IBM Network Station: Techniques for Deployment in a WAN

© Copyright IBM Corp. 1999213Chapter 7. Replicating a Remote Boot Server EnvironmentIf you determine that remote boot servers are the best option for

214 AS/400 IBM Network Station: Techniques for Deployment in a WANIn developing the implementation plan, the company decided to use the central AS/400

Replicating a Remote Boot Server Environment 215Because our central and remote system are both at the same OS/400 V4R3 level, the document referenced

216 AS/400 IBM Network Station: Techniques for Deployment in a WANObject moved. Object mov

Replicating a Remote Boot Server Environment 2178. In this case, since DHCP is being used, ensure that the DHCP server options are set up correctly on

218 AS/400 IBM Network Station: Techniques for Deployment in a WANwas made to copy the base IBM Network Station Manager environment to the remote site

Replicating a Remote Boot Server Environment 219verify that there were no prerequisite PTFs required prior to installing IBM Network Station Manager f

4 AS/400 IBM Network Station: Techniques for Deployment in a WANfinger directly on the display and dragging or clicking objects as if you were using a

220 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 127. Customize System Default Menu Bar ButtonsFigure 128. Add Custom NC Nav

Replicating a Remote Boot Server Environment 2212. The group profile must already exist to set group preferences. Therefore, create the group profile

222 AS/400 IBM Network Station: Techniques for Deployment in a WANFrom the central SYSAS3, use the following commands to FTP the C05SAVF containing th

Replicating a Remote Boot Server Environment 223STRTCPSVR SERVER(*HTTP) HTTPSVR(DEFAULT)7. Because the central AS/400 SYSAS3 system was used to create

224 AS/400 IBM Network Station: Techniques for Deployment in a WANIn addition, the AS/400 TCP/IP Autoconfiguration: DNS and DHCP, SG24-5147, is availa

© Copyright IBM Corp. 1999225Chapter 8. Using a Network Station to Access MailElectronic mail, called e-mail, is information that is sent electronica

226 AS/400 IBM Network Station: Techniques for Deployment in a WANb. Verify that there is an IP address associated with the host name for the system,

Using a Network Station to Access Mail 227Figure 134. Mail Service Level - System Message Storage (Preferred Address)On the display, as shown in Figu

228 AS/400 IBM Network Station: Techniques for Deployment in a WANb. To start the POP3 server, run the following command:STRTCPSVR SERVER(*POP)c. To s

Using a Network Station to Access Mail 229Figure 136 on page 229 shows the main Lotus eSuite Workplace desktop.Figure 136. eSuite Workplace Desktop8.

Introduction 5For additional information about National Language Support, refer to the manual IBM Network Station Manager Installation and Use, SC41-0

230 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 137. Menu Content Defaults Display2. Click Group defaults or User defaults d

Using a Network Station to Access Mail 2318.2.1.2 Starting RMI and eSuite Registry Server from AS/400 SystemThe RMI and eSuite Registry servers run o

232 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 139. eSuite Mail Configuration2. The first time you start eSuite mail, you a

Using a Network Station to Access Mail 233 •Mail server path. This is the path to the mail server where your messages are stored, for example: sysnam

234 AS/400 IBM Network Station: Techniques for Deployment in a WAN8.3 NC Navigator AccessNC Navigator mail has many capabilities to help you read and

Using a Network Station to Access Mail 2353. Click Next at the bottom of the display. The Network Setting display appears as shown in Figure 141.Figur

236 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 142. Main Dsplay of the NC Navigator Browser8.3.2 Configuring NC Navigator

Using a Network Station to Access Mail 2378.3.2.1 Selecting Mail OptionsThe first time you start NC Navigator mail, you may need to enter some inform

238 AS/400 IBM Network Station: Techniques for Deployment in a WAN •Name—This is the name that your mail recipient will see when they receive your me

Using a Network Station to Access Mail 2398.4 Domino AccessDomino for AS/400 is the implementation of a Lotus Domino server on the AS/400 platform. L

6 AS/400 IBM Network Station: Techniques for Deployment in a WAN1.2.3 Separation of ServersSeveral IBM Network Station Manager for AS/400 server func

240 AS/400 IBM Network Station: Techniques for Deployment in a WANBefore you run the Configure Domino Server (CFGDOMSVR) command, decide what to use f

Using a Network Station to Access Mail 2418.4.1.3 OrganizationTypically, the organization name is the name of your company or a major division within

242 AS/400 IBM Network Station: Techniques for Deployment in a WAN8.4.2 Avoiding Conflicts between AS/400 HTTP Server and DominoThe AS/400 operating

Using a Network Station to Access Mail 243For more information, refer to the manual Internet Connection Services and Internet Connection Secure Server

244 AS/400 IBM Network Station: Techniques for Deployment in a WAN3. In the Public Address Book, open the Server document for the Web server. In the A

Using a Network Station to Access Mail 245Figure 145. User ID and Password Prompt8.4.3.2 ViewsUser are presented with a full variety of Mail File vi

246 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 146. Views DisplayThese views are presented as icons on the left side of the

Using a Network Station to Access Mail 247Figure 147. Web Mail Inbox The Web mail template uses the familiar Notes mail interface and contains many o

248 AS/400 IBM Network Station: Techniques for Deployment in a WAN • Send broadcast meeting invitations • Confirm, cancel, or reschedule meetings •

Using a Network Station to Access Mail 249The IBM Network Station can use either the protocol called Independent Computing Architecture (ICA) or X11 t

Introduction 7Terminal Configuration Server The IBM Network Station Manager program on this server provides terminal-based configuration settings. The

250 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 148. Configuring an ICA ClientThe client, ICACLNT, must be entered in the Pr

Using a Network Station to Access Mail 2515. Select the File Server Install option on the next Notes Install display.6. The next display asks if you w

252 AS/400 IBM Network Station: Techniques for Deployment in a WAN16.Create a text file called nclogin.bat in the c:\wtsrv\system32\repl\import\script

Using a Network Station to Access Mail 253CHANGE USER /EXECUTEWhen a user logs on the next time, their user directory is automatically created, mapped

254 AS/400 IBM Network Station: Techniques for Deployment in a WAN

© Copyright IBM Corp. 1999255Appendix A. Flash Card ScenariosThis appendix contains examples of the flash.nsm and peer.nsm files and a list of the fi

256 AS/400 IBM Network Station: Techniques for Deployment in a WAN miscpr32.nws mwm.nws nfsd.nws ns3270.nws ns5250.nws ns5250xx.nws nsterm.nws

Flash Card Scenarios 257# flash.nsm - This file resides in the /QIBM/ProdData/NetworkStation/configs directory## AS/400 File Service Table#set file-se

258 AS/400 IBM Network Station: Techniques for Deployment in a WANA.2 Support for 5250, 3270, and VTxxx with FontsNetwork traffic can be reduced by a

Flash Card Scenarios 259If the uncompressed kernel for the Series 100 and 300 Network Stations is used, the number of bytes required is 7,966,842 byte

8 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 1. Roaming User Example • Figure 2 on page 9 shows how the separation of serv

260 AS/400 IBM Network Station: Techniques for Deployment in a WAN/local/X11/app-defaults/ mcuis Mwm system.mwmrc/local/X11/fonts/pcf/i18n/ Block1

Flash Card Scenarios 261 seriald.nws term.nwsA.2.1 The Flash.nsm File Additions to Support Local Font StorageTo support local font storage, the fol

262 AS/400 IBM Network Station: Techniques for Deployment in a WANA.3 Support for NC Navigator with Java Virtual MachineThe files required to start t

Flash Card Scenarios 263/local/java/lib/ appletviewer.properties awt.properties content-types.properties font.properties font.properties.en java

264 AS/400 IBM Network Station: Techniques for Deployment in a WAN lprd.nws mcuis.nws miscpref.nws mwm.nws navio.nws nfsd.nws sbcs_im.nws seri

Flash Card Scenarios 265 nfsd.nws sbcs_im.nws seriald.nwsA.5 Java Application SupportIn this example, the Network Station is started from the Flas

266 AS/400 IBM Network Station: Techniques for Deployment in a WAN export.63a export.nws filed.nws java.63a java.nws jawt.63a jawt.nws jcomm.n

Executable Module Descriptions 267Appendix B. Executable Module DescriptionsThe appendix attempts to outline each module, found in release 3.0, with

268 AS/400 IBM Network Station: Techniques for Deployment in a WANJava system informationjsysresource.nws extension Java System Resource Info.Java Zip

Executable Module Descriptions 269pref pref.nws utility Change user preferences (from the console)qsetup qsetup.nws utility Change Quick Setup (from t

Introduction 9Figure 2. Separation of Servers - Load Balancing ExampleFor additional information on how to use the separation of servers function to

270 AS/400 IBM Network Station: Techniques for Deployment in a WAN

© Copyright IBM Corp. 1999271Appendix C. 5500 Express IP Control UnitThis appendix, which presents an overview of the IBM 5500 Express IP control uni

272 AS/400 IBM Network Station: Techniques for Deployment in a WANThe 5500 control unit provides connection to: • Express twinax clients attached to

5500 Express IP Control Unit 273 – One of the following operating systems: • MS Windows NT 4.x with Service Pack 3 • MS Windows 95 with Service Pac

274 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 151 shows an example of an IBM 5500 used in a 5250 Express environment with a

5500 Express IP Control Unit 275Figure 152 shows an example of an IBM 5500 in a complex combination of network media types.Figure 152. IBM 5500 with

276 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 153 shows an example of the synchronous modem for the WAN connection between

5500 Express IP Control Unit 277Figure 154 shows an example of a frame relay WAN connection to the IBM 5500 providing connectivity for remote terminal

278 AS/400 IBM Network Station: Techniques for Deployment in a WANC.2.1.1 Understanding IP Address RequirementsObtaining contiguous IP addresses may

5500 Express IP Control Unit 279 • The AS/400 system is connected through the WAN interface of the 2210 router. LAN is connected to the 2210 router a

AS/400 IBM Network Station:Techniques for Deployment in a WAN March 1999SG24-5187-00International Technical Support Organization

10 AS/400 IBM Network Station: Techniques for Deployment in a WAN1.2.4 Broadcast Boot for AS/400The broadcast boot support in IBM Network Station Man

280 AS/400 IBM Network Station: Techniques for Deployment in a WANsubnet the IBM 5500 control unit or to obtain an additional set of addresses for the

5500 Express IP Control Unit 281 • Original network uses subnet mask 255.255.255.0 and is assigned addresses 100.100.100.0 through 100.100.100.255 (S

282 AS/400 IBM Network Station: Techniques for Deployment in a WANa different address to any device on the LAN that is using one of the addresses in t

5500 Express IP Control Unit 283ports to time slice. However, the 5500 control unit’s WSC is actually two mini-controllers, each responsible for servi

284 AS/400 IBM Network Station: Techniques for Deployment in a WANThis file also prevents the NSM configuration server from changing the NVRAM setting

© Copyright IBM Corp. 1999285Appendix D. Special NoticesThis publication is intended to help System Specialists and Business Partners who are assisti

286 AS/400 IBM Network Station: Techniques for Deployment in a WANCustomers attempting to adapt these techniques to their own environments do so at th

Special Notices 287PC Direct is a trademark of Ziff Communications Company and is usedby IBM Corporation under license.Pentium, MMX, ProShare, LANDesk

288 AS/400 IBM Network Station: Techniques for Deployment in a WAN

© Copyright IBM Corp. 1999289Appendix E. Related PublicationsThe publications listed in this section are considered particularly suitable for a more

Introduction 11Figure 3. Changing TFTP Attributes for Subnet Broadcast BootFigure 4. Enabling Subnet Broadcast Boot for IBM Network Stations

290 AS/400 IBM Network Station: Techniques for Deployment in a WANE.3 Other PublicationsThese publications are also relevant as further information s

© Copyright IBM Corp. 1999291How to Get ITSO RedbooksThis section explains how both customers and IBM employees can find out about ITSO redbooks, CD-R

292 AS/400 IBM Network Station: Techniques for Deployment in a WANHow Customers Can Get ITSO RedbooksCustomers may request ITSO deliverables (redbooks

293IBM Redbook Order FormPlease send me the following:We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not

294 AS/400 IBM Network Station: Techniques for Deployment in a WAN

© Copyright IBM Corp. 1999295IndexSymbols. 207AAccess Integration Services (AIS) 26AIS (Access Integration Services) 26applet viewer 5ASCII

296 AS/400 IBM Network Station: Techniques for Deployment in a WANpart numbers 63PCMCIA 63simple technology 63flash memory card 28FLASH.NSM

297adapter 4memory card 28slot 4peer bootconfiguration file 101network topology 97PEER.NSM 261performance5250 applications 44AS/400 rou

298 AS/400 IBM Network Station: Techniques for Deployment in a WANtwinax 3advanced IP 144attached network stations 127basic IP 128DHCP 154re

© Copyright IBM Corp. 1999299ITSO Redbook EvaluationAS/400 IBM Network Station: Techniques for Deployment in a WAN SG24-5187-00Your feedback is very

12 AS/400 IBM Network Station: Techniques for Deployment in a WAN1.2.5 Converged 5250/3270 EmulatorsThe 5250 and 3270 emulators have been enhanced to

Printed in the U.S.A.SG24-5187-00AS/400 IBM Network Station: Techniques for Deployment in a WAN SG24-5187-00

Introduction 13Network Station Manager program and selecting the LANG parameter pull-down list). • Emulator menu bar or pull downs, dialogue boxes, o

14 AS/400 IBM Network Station: Techniques for Deployment in a WANrecord and playback function. However, hand editing of VTxxx keyboard mapping files i

Introduction 15with OS/400 V4R2, a special type of TCP/IP can run over a twinax network. In addition, you must create a relationship between the works

16 AS/400 IBM Network Station: Techniques for Deployment in a WANstream into another. If you are using IBM Network Station applications that generate

Introduction 171.2.9 ICA Client ProtocolIn addition to the previously available X11 protocol support, Release 3 also allows you to use the ICA protoc

18 AS/400 IBM Network Station: Techniques for Deployment in a WANset of Java applets that provide a basic set of functions such as email, calendar, wo

Introduction 19Release 3 also provides a number of other enhancements to the NC Navigator browser such as: • Mail client function enables a user to s

© Copyright International Business Machines Corporation 1999. All rights reservedNote to U.S Government Users – Documentation related to restricted r

20 AS/400 IBM Network Station: Techniques for Deployment in a WANfrom the database, you must have IBM DB2 Query Manager and SQL Development Kit for AS

Introduction 21Details on implementing full-screen solutions are found online at the Web site: www.ibm.com/nc/pubs in the Advanced User Information se

22 AS/400 IBM Network Station: Techniques for Deployment in a WANheadquarters building one block away are actually remote since that Token Ring LAN is

Introduction 23you may have already installed or plan to install distributed AS/400 systems in some or all of your remote sites for various reasons. T

24 AS/400 IBM Network Station: Techniques for Deployment in a WANthe general recommendation is to leave the IBM Network Stations powered on. Therefore

Introduction 25Services Console log. As an alternative, Display Station Passthru can be used to sign on to the remote AS/400 system and then a native

26 AS/400 IBM Network Station: Techniques for Deployment in a WAN1.4.2 IBM 2212 Nways Access UtilityThe new IBM 2212 Access Utility which was announc

Introduction 27A major advantage of this remote site solution is that there is minimal setup and maintenance required in comparison to the remote boot

28 AS/400 IBM Network Station: Techniques for Deployment in a WANFor additional information about planning for, and implementing the IBM 2212 and the

Introduction 29cards because there is currently no automated way of keeping the files on the Flash card and the server synchronized. For ordering and

© Copyright IBM Corp. 1999iiiContentsFigures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixT

30 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 7. Remote Site - Flash Memory Card Peer Boot Example1.4.4 Network Station Te

Introduction 31Split bootRefers to the use of the Release 3 separation of servers function to split or separate functions that occur during the boot u

32 AS/400 IBM Network Station: Techniques for Deployment in a WAN

© Copyright IBM Corp. 199933Chapter 2. Planning ConsiderationsIn this chapter, we discusss the planning considerations for implementing Network Stati

34 AS/400 IBM Network Station: Techniques for Deployment in a WAN • Security • Capacity • Operations • Problem • Change ManagementCommunication

Planning Considerations 352.2 What You Are Likely to Have NowFigure 8 shows examples of network components that may exist in your organization. We de

36 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 9. Network Station ImplementationThe best place to start the discussion on th

Planning Considerations 37boot server. A small AS/400 system is a very cost effective solution in comparison with a local PC server. This system can b

38 AS/400 IBM Network Station: Techniques for Deployment in a WANsection. The following Network Station functions are included in the discussion: • T

Planning Considerations 39Table 2. Elements Loaded to a Network Station (MB) The kernel or configuration data is downloaded when the Network Station

iv AS/400 IBM Network Station: Techniques for Deployment in a WAN2.7 Problem and Change Management . . . . . . . . . . . . . . . . . . . . . . . . .

40 AS/400 IBM Network Station: Techniques for Deployment in a WANRelease 3 contains an option, TFTP subnet broadcast, that can significantly decrease

Planning Considerations 41Releases 1 though 2.5. All methods are suitable in Release 3. For Releases 1 though 2.5, NVRAM uses TFTP to load the kernel/

42 AS/400 IBM Network Station: Techniques for Deployment in a WANSome customers who have Series 1000s have experienced performance problems. The Serie

Planning Considerations 43The hardware test is just that, a memory test and other hardware tests to insure that the Network Station hardware is operat

44 AS/400 IBM Network Station: Techniques for Deployment in a WANblock size equal to the MTU or frame size. Users must be aware that some routers, swi

Planning Considerations 45Table 4. Kernel/Configuration Initialization TimeTable 5. Kernel/Configuration Initialization TimeAS/400 Model F97 (V3R2)

46 AS/400 IBM Network Station: Techniques for Deployment in a WANTable 6. Kernel/Configuration Initialization TimeTable 7. Kernel/Configuration Init

Planning Considerations 47Table 8. Kernel/Configuration Initialization TimeTable 9. Kernel/Configuration Initialization TimeAS/400 Model 400-2132IBM

48 AS/400 IBM Network Station: Techniques for Deployment in a WANIn Table 9, the Network Stations are all chained to a single cable port. For the 6180

Planning Considerations 49b. Enter the desired host name to get to the 5250 sign-on window. Most administrators use the Network Station Manager to con

v3.5.3 Creating a Peer Boot Configuration File . . . . . . . . . . . . . . . . . . 1013.5.4 Configuring the Peer Boot Network Station. . . . . . .

50 AS/400 IBM Network Station: Techniques for Deployment in a WANsegment. Assume the electricity on all 100 Networks Stations goes out and some time l

Planning Considerations 512.5.1.7 The AS/400 as a RouterThe AS/400 is a router (data passes though it) when twinax attached Network Stations send or

52 AS/400 IBM Network Station: Techniques for Deployment in a WANTable 13. LAN to Twinax Throughput2.6 Performance ConclusionsThe Network Station pr

Planning Considerations 53Network Stations, LAN utilization, CPU utilization, and so on. I/T Technical Support Staff must evaluate each project to pro

54 AS/400 IBM Network Station: Techniques for Deployment in a WAN • Release 3 boots about as fast as previous releases, even though more data and fun

Planning Considerations 55AS/400 as a Router Limited data is available. A model 400-2132 is able to route about 970kb/s from one LAN to another and ab

56 AS/400 IBM Network Station: Techniques for Deployment in a WAN • Configuration Information and User Data:Information that has been entered through

Planning Considerations 57Peer boot is a new function that allows multiple IBM Network Stations to boot from a single Flash card located in a local Ne

58 AS/400 IBM Network Station: Techniques for Deployment in a WAN5648-C05 (R3.0) products. It is important to remember that Network Stations booted fr

Planning Considerations 59Figure 10. Possible Network Station Printing ScenariosFor server-based applications, such as a 5250 application, you must c

vi AS/400 IBM Network Station: Techniques for Deployment in a WAN5.6.8 Configuring and Starting the IBM Network Station . . . . . . . . . . 1475.6.9

60 AS/400 IBM Network Station: Techniques for Deployment in a WAN2.12.2 Configuring Basic Printer ScenariosUsing Figure 10 as an example, Table 14 ex

Planning Considerations 612.12.3 Printer Administration TechniquesAdministrating a printer environment can be a difficult task. You should create a p

62 AS/400 IBM Network Station: Techniques for Deployment in a WANOne technique is to have a server control the printers for your Network Stations. In

© Copyright IBM Corp. 199963Chapter 3. Using Flash Cards with the Network StationThis chapter outlines the Flash card support for the IBM Network Sta

64 AS/400 IBM Network Station: Techniques for Deployment in a WAN3.1 Flash Card SupportThe IBM Network Station products only work with linear C serie

Using Flash Cards with the Network Station 653.1.1 Flash Card SizingTable 16 provides an estimate of the card size required for each IBM Network Stat

66 AS/400 IBM Network Station: Techniques for Deployment in a WANThe linear Flash memory supported by the Network Station has the characteristic that

Using Flash Cards with the Network Station 67the Flash card similar to CDROM from the administrator's and user's perspective. This arrangeme

68 AS/400 IBM Network Station: Techniques for Deployment in a WANBy default, ACTLogin attempts to authenticate to the boot server. This obviously will

Using Flash Cards with the Network Station 69PCMCIA Adapter on the Series 1000 is 07L8336 and can be ordered in the GEMS ordering system in the US and

vii6.1.1 Accessing the System Log Using TELNET . . . . . . . . . . . . . . . . 2096.1.2 Accessing the System Log Using the Console Manager . . . .

70 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 11. Flash Card Support for Emulators from a Remote Location3.2.2 Scenario Ad

Using Flash Cards with the Network Station 71In the event of a Flash card failure, an identical secondary card should be distributed to the user, alon

72 AS/400 IBM Network Station: Techniques for Deployment in a WANFigure 12. Remote Flash Card Enabled IBM Network Station Topology Diagram3.3 Creati

Using Flash Cards with the Network Station 733.3.1 Verifying PrerequisitesYou must ensure that your system is running IBM Network Station Manager pro

74 AS/400 IBM Network Station: Techniques for Deployment in a WAN3.3.3.1 Creating a Test Directory StructureBy default, the only path in the AS/400 I

Using Flash Cards with the Network Station 75Appendix A, “Flash Card Scenarios” on page 255 has more information about the files required to support t

76 AS/400 IBM Network Station: Techniques for Deployment in a WAN • term.nws • nsterm.nws3.3.4 Creating a Separate Configuration FileTo enable the

Using Flash Cards with the Network Station 77Figure 13. Example Flash.nsm File3.3.5 Testing the Boot Image from the AS/400 SystemTo set NVRAM on the

78 AS/400 IBM Network Station: Techniques for Deployment in a WAN2. Power on the IBM Network Station. The IBM logo is shown, followed by a memory and

Using Flash Cards with the Network Station 7916.Enter the correct IP address information for the fields, Gateway IP Address and Subnet Mask according