AS/400 IBM Network Station: Techniques for Deployment in a WAN Fant Steele, Nick Harris, Joan Barrett, Hernan Coronel, Andy Grant, Yudhi Haryadi, Gerri Passe International Technical Support Organization http://www.redbooks.ibm.
SG24-5187-00 International Technical Support Organization AS/400 IBM Network Station: Techniques for Deployment in a WAN March 1999
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 285. First Edition (March 1999) This edition applies to IBM Network Station Manager Program Version 1 Release 3, Program Number 5648-C05, and OS/400 Version 4 Release 3. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept.
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv The Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Comments Welcome . . . . . . . . . . . . . . . . . . . . . .
2.7 Problem and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . 55 2.8 Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 2.9 Roaming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 2.10 Slow Link Boot versus Flash Card Peer Boot . . . . . . . . . . . . . . . . . . 56 2.11 CISC and RISC Co-existence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 2.
3.5.3 3.5.4 3.5.5 3.5.6 Creating a Peer Boot Configuration File . . . . . . . . . . . . . . . . . . 101 Configuring the Peer Boot Network Station . . . . . . . . . . . . . . . . 102 Verifying Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Peer Boot Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Chapter 4. Remote Servers and Split Boot Servers . . . . . . . 4.1 Terminology for this Chapter . . . . . . . . . . . . . . . . . . . . . . . 4.
5.6.8 Configuring and Starting the IBM Network Station . . . . . . . . . . 147 5.6.9 Configuring an AS/400 IP Interface. . . . . . . . . . . . . . . . . . . . . . 147 5.6.10 Testing Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 5.6.11 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 5.7 Twinax IBM Network Station with Local DHCP Server Scenario . . . . 154 5.7.1 Scenario Overview . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Accessing the System Log Using TELNET . . . . . . . . . . . . . . . . 209 6.1.2 Accessing the System Log Using the Console Manager . . . . . . 211 Chapter 7. Replicating a Remote Boot Server Environment . . . . . . . 213 7.1 Centralized Authentication Server . . . . . . . . . . . . . . . . . . . . . . . . . . 213 7.1.1 IBM Network Station Manager Replication to Remote Server . . 214 7.2 Decentralized Authentication Server. . . . . . . . . . . . . . . . . . . . . . . . . 217 7.2.
C.2.1 WAN Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 C.2.2 ISDN Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 C.3 5500 Control Unit and TCP/IP LAN Concepts . . . . . . . . . . . . . . . . . . . . 278 C.3.1 Installing the IBM 5500 into an Existing Network . . . . . . . . . . . . . . 279 C.4 Optimizing Twinax Performance for the Client Workstation . . . . . . . . . . 282 C.
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. Roaming User Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Separation of Servers - Load Balancing Example . . . . . . . . . . . . . . . . . . . . 9 Changing TFTP Attributes for Subnet Broadcast Boot . . . . . . . . . . . . . . . 11 Enabling Subnet Broadcast Boot for IBM Network Stations . . . . . . . . . . .
40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. x QTDL824300 Line Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Automatically Created Device Type 5150 under CTL01 . . . . . . . . . . . . . 135 Adding IP Interface for QTDLC824300 Line Description . . . . . . . . . . . . . 136 Starting the Interface for the QTDLC824300 Line Description . . . . . . . .
82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99. AS/400 Operations Navigator - TCP/IP Server Status. . . . . . . . . . . . . . . 175 Automatically Created QTDL Descriptors . . . . . . . . . . . . . . . . . . . . . . . . 176 CFGTCP Option 1 Display Showing the TDLC Interface. . . . . . . . . . . . . 176 TCP/IP Interface Updated with an Associated Local Interface Value . . . 177 AS/400 Operations Navigator - Configuring BOOTP/DHCP Relay Agent 178 BOOTP/DHCP Relay Agent Configuration .
124.Console Log Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 125.Replicating Remote Boot Servers - Centralized Authentication Server . 214 126.Replicating Remote Boot Servers - Decentralized Authentication . . . . . 218 127.Customize System Default Menu Bar Buttons . . . . . . . . . . . . . . . . . . . . 220 128.Add Custom NC Navigator Button to System Default Menu Bar. . . . . . . 220 129.Add 3270 Menu Bar Button to Group Grp3270’s Preference Settings . .
Tables 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. Applications and Printer Data Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Elements Loaded to a Network Station (MB) . . . . . . . . . . . . . . . . . . . . . 39 Time (Seconds) to Perform Hardware Test . . . . . . . . . . . . . . . . . . . . . . 43 Kernel/Configuration Initialization Time . . . . . . . . . . . . . . . . . . . . . . . . . 45 Kernel/Configuration Initialization Time . . . . . . . . . . . . .
xiv AS/400 IBM Network Station: Techniques for Deployment in a WAN
Preface Gain an edge implementing an IBM Network Station solution in a Wide Area Network (WAN). This redbook offers a number of alternative implementation techniques that demonstrate the IBM Network Station’s flexibility and rapid deployment capabilities. As you read this book, you find valuable information about running IBM Network Station with Network Station Manager Program Release 3 (NSM).
Specialist in the United Kingdom AS/400 Business. Prior to joining IBM, he worked for the Ministry of Defense as a Mechanical and Electrical Design Engineer. Joan Barrett is an Advisory I/T Availability Professional in the AS/400 Software Support Center in Canada. She has worked for IBM for 10 years. Over the past five years, she worked in the communications group within the AS/400 platform. In the previous five years, she worked as a Customer Service Representative in the Mid-range systems field.
Thanks to the following people for their invaluable contributions to this project: Ray Romon, Network Station Development Manager Chuck Carmack, Network Station Development Dave Limpert, Network Station Software Architect AJ Meyer, Network Station Development Ron Stevenson, Network Station Performance IBM Rochester Marc Pamely, Product Engineer Buz Stepanek, 5500 Product Management IBM Charlotte Comments Welcome Your comments are important to us! We want our redbooks to be as helpful as possible.
xviii AS/400 IBM Network Station: Techniques for Deployment in a WAN
Chapter 1. Introduction Although IBM Network Stations can be locally attached to your AS/400 using twinax, Ethernet, or Token Ring using TCP/IP. This redbook focuses on implementing IBM Network Stations at your remote sites. In addition, this redbook assumes that you have some familiarity with IBM Network Stations.
The IBM Network Station Series 300, the Internet network computer, is an ideal solution when your users spend a lot of time on your corporate intranet or the Internet, as well as access server based applications. In addition to providing the same Series 100 capabilities listed above, the Series 300 can run simple or entry level Java applets and applications.
Manager from any location on their TCP/IP network using an appropriate browser. In June of 1998, a new release with significant enhancements to IBM Network Station Manager for AS/400 became available.
finger directly on the display and dragging or clicking objects as if you were using a mouse. With this free enhancement and a touch-sensitive display, the IBM Network Station can be the client for a broad range of applications requiring read-only access to data, from kiosks in shopping malls to hospitals, museums, and libraries. PCMCIA on Series 1000 Enables the use of a Type II PCMCIA card slot on the IBM Network Station Series 1000 after it has been installed.
For additional information about National Language Support, refer to the manual IBM Network Station Manager Installation and Use, SC41-0664, and in the online help text of the IBM Network Station Manager program. 1.2.2 Network Station Manager Group Support Previous releases of IBM Network Station Manager for AS/400 provided default system, user and workstation level settings.
1.2.3 Separation of Servers Several IBM Network Station Manager for AS/400 server functions that were previously bundled can now be split and installed on multiple servers. This allows you to balance network traffic, if desired. Balancing network traffic enables IBM Network Station end users to access their normal desktop when they are away from their regular server.
Terminal Configuration Server The IBM Network Station Manager program on this server provides terminal-based configuration settings. The IBM Network Station Manager program manages these settings. Examples of terminal configuration settings are a printer that is attached to the network station, or the network station's keyboard language. The address of the terminal configuration server is the same as the address of the base code server by default. The inventory server (AS/400 only) runs on this server.
Figure 1. Roaming User Example • Figure 2 on page 9 shows how the separation of servers function might be used to reduce network congestion if all IBM Network Stations are powered on at 8:00 on Monday morning. In this case, separation of servers is used to split the server functions across multiple systems. For example, one AS/400 (10.1.1.2) provides both the authentication and terminal configuration server functions and the PC server (10.2.1.2) is the DHCP server. In addition, there are two AS/400s (10.3.
Authentication Server Base Code Server Base Code Server DHCP Server Terminal Configuration Server 10.4.1.2 10.3.1.2 10.2.1.2 10.1.1.2 IBM Network Station Figure 2. Separation of Servers - Load Balancing Example For additional information on how to use the separation of servers function to enable user roaming and provide load balancing, refer to the manual IBM Network Station Manager Installation and Use, SC41-0664. This manual and others are available on-line at the Web site: www.ibm.
1.2.4 Broadcast Boot for AS/400 The broadcast boot support in IBM Network Station Manager for AS/400 Release 3 provides the capability to boot multiple Network Stations on the same subnet. This broadcast boot is performed in parallel through a single transmission. In situations where large numbers of IBM Network Stations start up at the same time, heavy network usage or boot storms can result.
Change TFTP Attributes (CHGTFTPA) Type choices, press Enter. Autostart server . . . . . . . . Enable subnet broadcast . . *YES Number of server jobs: Minimum . . . . . . . . . . . Maximum . . . . . . . . . . . Server inactivity timer . . . . ASCII single byte CCSID: Coded character set identifier Maximum block size . . . . . . . Connection response timeout . . Allow file writes . . . . . . . Alternate source directory . . .
Important Before you use TFTP Subnet Broadcast, you must ensure that certain PTFS are installed on every AS/400 in your network. Please refer to the manual IBM Network Station Manager Installation and Use, SC41-0664, for the most current list of PTFs. These PTFs prevent unpredictable results, including possible data loss. This manual can be found online at the Web site: www.ibm.com/nc/pubs 1.2.
Network Station Manager program and selecting the LANG parameter pull-down list). • Emulator menu bar or pull downs, dialogue boxes, online help, keyboard remapping, color mapping, record/playback, and so on, are now translated into many languages (a list of available languages can be seen by selecting the Language Setup Task in the IBM Network Station Manager program and then clicking on the pull down list for the LC_MESSAGES parameter).
record and playback function. However, hand editing of VTxxx keyboard mapping files is available. After hand editing a VTxxx mapping file, you can use the new group support (see Section 1.2.2, “Network Station Manager Group Support” on page 5) by putting the file into the group’s proper file path/directory on the authentication server and then using the Network Station Manager program to associate the desired users with that group.
with OS/400 V4R2, a special type of TCP/IP can run over a twinax network. In addition, you must create a relationship between the workstation controller and a TCP/IP interface. A TCP/IP interface is needed to identify your workstation controller to your AS/400 server and IBM Network Stations. Each TCP/IP interface must have a unique IP address. The IP addresses for twinax IBM Network Station models are assigned by the TDLC (Twinax Data Link Control) component on the AS/400 system.
stream into another. If you are using IBM Network Station applications that generate PostScript data, but you only have a PCL type printer attached to your IBM Network Station, the print request can be sent to the AS/400 system, transformed from PostScript to PCL, and routed back to the IBM Network Station attached PCL printer.
Important Transforming print jobs requires OS/400 Version 4 Release 2 or later. Because the host print transform takes place on the server, the AS/400 system resources are utilized. 1.2.9 ICA Client Protocol In addition to the previously available X11 protocol support, Release 3 also allows you to use the ICA protocol to access Microsoft Windows based applications running on a server.
set of Java applets that provide a basic set of functions such as email, calendar, word processing, spreadsheet, address book and presentation graphics in a single product. IBM Network Station Manager for AS/400 Release 3 allows you (the system administrator) to easily set the eSuite Workplace product as the default desktop.
Release 3 also provides a number of other enhancements to the NC Navigator browser such as: • Mail client function enables a user to send and receive e-mail using a POP3 (Post Office Protocol V3) server. • News Reader function enables a user to read news items on an NNTP (Network News Transfer Protocol) server. • The Navigator enables printing to remote printers on the network. • Localized versions enable French, German, and Korean (in addition to English) languages.
from the database, you must have IBM DB2 Query Manager and SQL Development Kit for AS/400 installed. Note If you decide to use the new separation of servers function, the hardware inventory server must run on the server providing the Terminal Configuration server function. 1.2.
Details on implementing full-screen solutions are found online at the Web site: www.ibm.com/nc/pubs in the Advanced User Information section. 1.2.15 DHCP Support An AS/400 with TCP/IP and OS/400 Version 4 Release 2 or later installed can be configured to act as a DHCP server. DHCP (Dynamic Host Configuration Protocol) allows a server to automatically provide IP addresses and configuration information to clients without needing to manually keep track of client MAC addresses.
headquarters building one block away are actually remote since that Token Ring LAN is connected to the AS/400 LAN through a remote bridge. As you can see, it is very important to understand your existing network. If a current network diagram does not already exist, it is very important to create one before implementing network computers. Sample network diagrams are found throughout other chapters in this redbook.
you may have already installed or plan to install distributed AS/400 systems in some or all of your remote sites for various reasons. These remote AS/400 systems can provide users with local access to applications like Domino and also act as a boot server. A remote AS/400 boot server option is one which provides a high degree of flexibility and function for the current andl future needs of your remote users .
the general recommendation is to leave the IBM Network Stations powered on. Therefore, the AS/400 CPU required for Network Station boot up will most likely be needed only occasionally. On the other hand, your site may have different policies or habits regarding the powering off of desktop workstations on a daily or weekly basis. In these cases, it is more critical to have adequate CPU to handle the more frequent IBM Network Station initialization. Refer to Section 2.
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.
1.4.2 IBM 2212 Nways Access Utility The new IBM 2212 Access Utility which was announced on September 22, 1998, is a multi-services networking device that provides more versatility, integrated functions and performance than a fixed function router or remote access server. This product offers the combined functions of a router, remote access server, Virtual Private Network Server and boot server in a cost effective, single box solution.
A major advantage of this remote site solution is that there is minimal setup and maintenance required in comparison to the remote boot server option. In addition, unlike the Flash boot option, the boot files located on the IBM 2212 are automatically updated when necessary. Also, keep in mind that this device provides router and remote access functions, as well as the boot server function. However, we recommend that no more than thirty IBM Network Stations be active at one time.
For additional information about planning for, and implementing the IBM 2212 and the Thin Server Feature, refer to the manuals: IBM 2212 Access Utility Introduction and Planning Guide, GA27-4215, and IBM 2212 Access Utility Installation and Initial Configuration Guide, GA27-4216. These manuals are available online at the Web site: www.networking.ibm.com/did/2212bks.html In addition, as mentioned previously, a future IBM redbook discussing the IBM 2212 Access Utility is planned for availability in 1999. 1.
cards because there is currently no automated way of keeping the files on the Flash card and the server synchronized. For ordering and other information about obtaining Flash memory cards, software, and documentation necessary to use this functional enhancement, please contact your IBM representative or an IBM Business Partner and refer to PRPQ P97000, 5799-GEB, Feature Number 4002.
Central AS/400 Flash Card Enabled IBM Network Station Central S/390 Code sourced from flash card enabled Network Station Remote Location Central Location WAN Link Central RS/6000 Peer Boot IBM Network Station Figure 7. Remote Site - Flash Memory Card Peer Boot Example 1.4.4 Network Station Terminology The following are definitions of terms that are used throughout this redbook.
Split boot Refers to the use of the Release 3 separation of servers function to split or separate functions that occur during the boot up or initialization of the IBM Network Station. For example, an IBM Network Station could obtain its operating system kernel from a base code server and obtain other files, preferences and applications from another boot server.
32 AS/400 IBM Network Station: Techniques for Deployment in a WAN
Chapter 2. Planning Considerations In this chapter, we discusss the planning considerations for implementing Network Stations in the AS/400 environment. Implementing Network Stations can vary from very simple transitions from non-programmable terminals (NPTs) to network stations with emulation only, to very complex installations where combinations of NPTs and PCs are migrated to a full function browser and collaborative environment. Some of the topics we discuss must be considered for both implementations.
• • • • • Security Capacity Operations Problem Change Management Communications Network How much capacity do you have within your network? Do you need to increase the capacity to support current and future requirements of your end-uses ? These items require some detailed investigation to accurately size the network. Resource Availability Are there resources available to support this project? There is a requirement for skills in networking, host systems, PCs, project management, system and network sizing.
2.2 What You Are Likely to Have Now Figure 8 shows examples of network components that may exist in your organization. We detailed as many example connections as possible (hopefully not all these examples exist at one time). AS/400 Router Local LAN Local Twinax Router Modem Remote LAN Modem Modem Modem Local ASCii 5x94 5208/5209 Remote PCs Remote Host AS/400, S/390, RS/6000 Remote Twinax Remote ASCii Figure 8.
AS/400 DHCP Authentication Server AS/400 10 users AS/400 100 Users 50 Users Flash Card Figure 9. Network Station Implementation The best place to start the discussion on these options is at the bottom of Figure 9. In this scenario, there are 50 users in a stand-alone organization, which has it’s own I/T function. This is the simplest setup and easiest to compare with an existing NPT network. All information is stored on the local AS/400 system.
boot server. A small AS/400 system is a very cost effective solution in comparison with a local PC server. This system can be managed very effectively from the central site. If you look at the 100 users group, there is a local server that can provide boot information. You do not want to impact its work load. In this scenario, you can use Broadcast boot. This provides faster bootup, and central management, or again, you can could implement a small AS/400 system to act as the boot server.
section. The following Network Station functions are included in the discussion: • Time to initialize the Network Station (prior to login) for Ethernet, Token-Ring and twinax • Time to load the applications (5250 emulation, browser, and so on) • 5250 application performance • Browser performance • Java Virtual Machine (JVM) applet or application performance • Times for the Network Station Series 100, 300 and 1000 The computer industry has a generic name for the IBM Network Station - the thin client.
Table 2. Elements Loaded to a Network Station (MB) Release Series Release 1-2.5 Rel 3 Rel 3 DBCS* 100/300 1000 All All Kernel+Configuration +other 4.0 4.8 3.0 3.9 5250 Emulation 0.9 0.9 1.6 3.8 3270 Emulation 0.3 0.3 0.9 3.2 IBM Network Station Browser 2.2 2.2 NA NA Navio NC Navigator 3.7 3.7 5.0 10.00 Java Virtual Machine 1.5 - 5.0 1.5 - 5.0 1.5 - 5.0 1.5 - 5.
Release 3 contains an option, TFTP subnet broadcast, that can significantly decrease the amount of data transmitted during the boot process, as well as saving significant CPU cycles in the AS/400 system. This option is described in more detail in the following sections. 2.5.1.1 IBM Network Station Initialization Initialization, at this time, is non-trivial and can be a performance concern for some customers.
Releases 1 though 2.5. All methods are suitable in Release 3. For Releases 1 though 2.5, NVRAM uses TFTP to load the kernel/configuration files and, after login, uses RFS. For Release 3, NVRAM uses TFTP to load the kernel and RFS for all subsequent files. BOOTP and DHCP use TFTP to load the kernel and then use RFS to load all subsequent files. For Releases 1 though 2.5, the Network Station tries 10 times, with a five second timeout, to locate and read the kernel using TFTP.
Some customers who have Series 1000s have experienced performance problems. The Series 1000 supports both full duplex and half duplex. In general, the performance problem is caused by a configuration error. As a result, the Series 1000 tries to operate in full duplex mode, but a router or something else in the network supports only half duplex. The Series 1000 almost continuously runs into collisions on the Ethernet, which results in extremely slow performance.
The hardware test is just that, a memory test and other hardware tests to insure that the Network Station hardware is operational. For the most part, the length of this test is determined by the amount of memory in the IBM Network Station. Table 3. Time (Seconds) to Perform Hardware Test Memory (MB) Series 100 Series 300 Series 1000 8 15 14 - 16 18 18 - 32 24 22 10 48 30 26 - 64 36 31 13 2.
block size equal to the MTU or frame size. Users must be aware that some routers, switches and gateways do not support this fragmentation capability. Twinax MTU or frame size are fixed. Therefore, fragmentation does not apply to twinax attached Network Stations. The number of TFTP jobs on the AS/400 server is also a performance factor. The optimal number, for a system with a single LAN IOP, is about six (the default). The TFTP jobs are a pool of AS/400 jobs that download the kernel to Network Stations.
Table 4. Kernel/Configuration Initialization Time AS/400 Model F97 (V3R2) IBM Network Station Series 300 Release 1-2.5 16Mb token-ring Vary TFTP Block Size #NS 512 1024 2048 4096 8192 1 109 (5.0) 46 (5.5) 34 (4.2) 29 (2.9) 26 (2.6) 10 225 (27.0 105 (31.0) 77 (26.0) 63 (22.6) 57 (12.2) 50 992 (32.8) 470 (41.7) 327 (30.8) 257 (24.0) 209 (20.1) 100 1885 (35.2) 890 (46.3) 624 (33.6) 503 (25.5) 395 (22.3) Note: Time in seconds (Average CPU in %) Table 5.
Table 6. Kernel/Configuration Initialization Time AS/400 Model 510-2144 (V3R7) IBM Network Station Series 300 Release 1-2.5 2619 16Mb token-ring IOP Vary TFTP Block Size #NS 512 1024 2048 4096 8192 1 71 (9.8) 59 (7.4) 52 (6.4) 46 (5.8) 43 (5.2) 10 169 (39.3) 117 (30.3) 81 (26.1) 65 (21.2) 62 (17.3) 50 790 (44.5) 451 (42.5) 361(32.6) 265 (28.7) 209 (27.0) 100 1526 (47.3) 875 (45.2) 667 (35.7) 498 (31.7) 384 (30.5) Note: Time in seconds (Average CPU in %) Table 7.
Table 8. Kernel/Configuration Initialization Time AS/400 Model 400-2132 IBM Network Station Series 300 Release 1-2.5 2629 10MB Ethernet LAN IOP Vary TFTP Block Size #NS 512 1024 2048 4096 8192 1 76 (35.6) 53 (26.3) 45 (19.8) 39 (17.7) 34 (15.5) 10 280 (90.2) 167 (82.0) 110 (72.6) 83 (63.7) 67 (55.7) 50 1311 (97.5) 745 (93.8) 467 (88.6) 321 (82.1) 277 (69.3) 100 2691 (97.82) 1466 (96.9) 895 (93.4) 623 (86.7) 540 (73.1) Note: Time in seconds (Average CPU in %) Table 9.
Note Notice that subnet broadcast uses less AS/400 CPU. However, as discussed previously, each twinax device on the subnet gets their own copy of the broadcast data, even if they did not request it, which would mean unwanted data on the twinax cable. In general, you should not use twinax subnet broadcast. Subnet broadcast should be used on LANs. In Table 9, the Network Stations are all chained to a single cable port.
b. Enter the desired host name to get to the 5250 sign-on window. Most administrators use the Network Station Manager to configure for direct menu bar to 5250 sign-on. 5. Getting to the browser is a single step. From the menu bar, select the Browse button to get to the NC Navigator browser. Examples of load times can be found in the following tables. Table 10. Load Times (Seconds) AS/400 Models 150-2270 and S10-2144 (V3R7) IBM Network Station Series 100 and 300 Releases 1-2.
segment. Assume the electricity on all 100 Networks Stations goes out and some time later it comes back on. Assume the Network Stations all have the same memory size (for example, 32MB) and identical monitors attached. It is possible for all 100 to be at the Login window in 280 seconds (less than five minutes). The 280 seconds comes from: 21 seconds for hardware test, 30 seconds to load the kernel, and 229 seconds to load configuration files. 2.5.1.
2.5.1.7 The AS/400 as a Router The AS/400 is a router (data passes though it) when twinax attached Network Stations send or receive data from the Internet or other servers. At this time, limited performance data is available. The following two tables show results when data is read from an NT server through an AS/400 system to a Network Station. Table 12.
Table 13. LAN to Twinax Throughput AS/400 Model 400-2132 (V4R2) IBM Network Station Series 300 Release 3, using Twinax to AS/400 300Mhz PC NT server using 16MB TR to AS/400 2629 LAN IOP, 6180 Twinax Adapter, 2MB of data. 8K TFTP block #NS Time (sec) AS/400 Util (%) AS/400 Throughput (KB/s) 1 33 9.9 70.1 2 48 9.9 96.4 3 109 10.3 63.7 4 127 10.5 72.9 5 150 11.1 77.1 6 213 11.0 65.2 2.6 Performance Conclusions The Network Station provides for an excellent working environment.
Network Stations, LAN utilization, CPU utilization, and so on. I/T Technical Support Staff must evaluate each project to produce the optimum network design. We recommend that, when you are building Network Station solutions, you phase the customer projects to ensure the design meets expectations with no surprises. • Initialization time varies from AS/400 model to AS/400 model. In general, the larger the model, the better the performance.
• Release 3 boots about as fast as previous releases, even though more data and function are sent. Much of the data sent is compressed. • Switches, routers and gateways can cause problems. Ensure your Network Administrator is involved in the implementation. • For 6180 twinax attached Network Stations, best performance is obtained if all Express Datastream enabled devices are on the same cable, excluding older, non-Express capable devices.
AS/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 about 75Kb/s from a LAN to twinax. 2.7 Problem and Change Management At times, the Network Station operating system may stop unexpectedly with a PANIC error. One of two symptoms may appear: • PANIC appears on your Network Station and a > cursor is shown. • The display turns reverse video (mostly black) and a > cursor is presented.
• Configuration Information and User Data: Information that has been entered through the IBM Network Station Manager is migrated. If the configuration files have been manually edited, you can obtain additional information on how to migrate your configuration by referring to the Advanced User Information at: http://www.ibm.com/nc/pubs 2.9 Roaming With the availability of Release 3 of the IBM Network Station Manager, you can take advantage of Multiple Server Environments.
Peer boot is a new function that allows multiple IBM Network Stations to boot from a single Flash card located in a local Network Station. The performance of Network Stations utilizing peer boot is very acceptable. Up to ten Network Stations peer booting simultaneously from a single Flash card were tested with very good results. Because of the current size limitations of the Flash cards, it is not possible to store all of the code required to start and operate the Network Station on a single card.
5648-C05 (R3.0) products. It is important to remember that Network Stations booted from an R3.0 NSM server can assess a V3R2 CISC AS/400 through 5250 Emulation. However, any Network Stations booting from a V3R2 system does not have the R3.0 enhancements available (for example, roaming capability, DCHP support, separation of servers, and so on.) because NSM R2.5 (not R3.0) is supported on V3R2. Customers running R2.5 should migrate to R3.0 for: • Support • Year 2000 certification • New functions R2.5 to R3.
Figure 10. Possible Network Station Printing Scenarios For server-based applications, such as a 5250 application, you must configure a printer on the server where the application is running. In this case, think of the Network Station as only a window to the server, in that server still performs the work. In Figure 10, if Network Station A runs a 5250 session on the AS/400 server and you want to print to Printer 4, you must create a printer device description on the AS/400 server.
2.12.2 Configuring Basic Printer Scenarios Using Figure 10 as an example, Table 14 explains the basic steps to configure printers for your Network Stations. Identify the scenario that best meets your needs and follow the steps to configure your printers. Table 14.
Desired Print Scenario Print Job Flow Configuration Instructions Network Station to another Network Station with an attached printer Network Station B to Network Station A to Printer 6 In the Network Manager program, configure an entry in the Remote Printer Server field with the IP address of the Network Station to which the printer is attached. In the Queue name field, type PARALLEL1 or SERIAL1, depending on how the printer connects to the Network Station.
One technique is to have a server control the printers for your Network Stations. In Figure 10 on page 59, the AS/400 server can control a LAN printer, such as Printer 4. If Network Station A and B always sent their print jobs to the AS/400 server, the AS/400 server can control the flow of print jobs to the printer. This scenario reduces the work load on the Network Stations when the printer’s buffer is full because the AS/400 server can negotiate print jobs with the printer.
Chapter 3. Using Flash Cards with the Network Station This chapter outlines the Flash card support for the IBM Network Station, describes how they work with the IBM Network Station, when they should be used and what the limitations are. Release 3.0 of the IBM Network Station Manager has been enhanced to provide Flash memory card support. This function is available in U.S. English for IBM Network Stations connected to any of the IBM servers supported by Release 3.0.
3.1 Flash Card Support The IBM Network Station products only work with linear C series and linear D series PCMCIA type II Flash memory cards. The maximum size of C series technology is limited to 10MB. However, D series cards are currently available in various sizes with up to 32MB of capacity and in the near future will support as much as 40Mbytes of storage capacity. Flash cards can be purchased from several manufacturers. IBM does not manufacture or resell these cards.
3.1.1 Flash Card Sizing Table 16 provides an estimate of the card size required for each IBM Network Station native application. The Series 1000 IBM Network Stations have a different boot kernel. There are also separate executable modules required for supporting the Series 1000. If you intend to peer boot a mixture of Series 1000 and the Series 100 and 300, you need both sets of files and the required card size approximately doubles. Table 16.
The linear Flash memory supported by the Network Station has the characteristic that space is allocated in contiguous blocks at the end of existing used memory. If a file is added or replaced it goes at the end of currently allocated memory and the memory allocated to the previous version of the file is effectively lost.
the Flash card similar to CDROM from the administrator's and user's perspective. This arrangement works well as long as the environment is rather static and frequent updates are not required. 3.1.3 Separation of Servers, Authentication Login, and the Flash Card Beginning in Release 3, the Network Station's NVRAM can be configured so that the kernel is booted from one system, the configuration files are loaded from another system, and user authentication is performed by a third system.
By default, ACTLogin attempts to authenticate to the boot server. This obviously will not work correctly when booting from the Flash because there is no default boot server. A specific authentication server must therefore be provided to ACTLogin, as shown in the flash.nsm file Figure 13 on page 77. In some cases, it is desirable to not have the ACTLogin display (for example, login display) show.
PCMCIA Adapter on the Series 1000 is 07L8336 and can be ordered in the GEMS ordering system in the US and Canada, and the UPOS ordering system in EMEA. Contact your IBM Network Station Sales Representative or Business Partner to order these adapters. IBM has tested Flash cards from Centennial Technologies (http://www.cent-tech.com) and cards from Simple Technology (http://www.simpletech.com) the latter of which offers a full line of D series cards.
C entral S/390 C entral AS/400 Flash Card Enabled IBM Network Station C entral RS/6000 W AN Link R em ote Location C entral Location Figure 11. Flash Card Support for Emulators from a Remote Location 3.2.2 Scenario Advantages The scenario has the following advantages: • Users at the remote location experience quick boot up times as the required code to start the IBM Network Station is contained on the local Flash card or file system.
In the event of a Flash card failure, an identical secondary card should be distributed to the user, along with the first. • The NVRAM settings cannot be easily changed from local Flash boot to server boot. To enable the IBM Network Station to use the Flash card and boot locally, the settings in NVRAM must be modified. It may not be a simple task for the end user to change these settings back in the event of a Flash card failure.
S/390 AS/400 Flash Card Enabled IBM Network Station .2 .3 RS/6000 .10 Network Address: .4 10.1.1.x Subnet mask: 255.255.255.0 WAN Link Central Location Remote Location Figure 12. Remote Flash Card Enabled IBM Network Station Topology Diagram 3.3 Creating A Flash Card To enable an IBM Network Station to boot from the local Flash card, complete the following steps: 1. 2. 3. 4. 5. 6. 7. Verify prerequisite tasks. Create a Flash card boot image. Create a separate configuration file.
3.3.1 Verifying Prerequisites You must ensure that your system is running IBM Network Station Manager program Release 3.0 and has the latest PTFs have been installed. To support Flash cards, you must also have the latest OS/400 and NSM PTF code. The latest PTF for NFS must also be installed if you intend to transfer the data to the Flash card using NFS/400. 3.3.
3.3.3.1 Creating a Test Directory Structure By default, the only path in the AS/400 IFS that allows TFTP read access is the default IBM Network Station path, /QIBM/ProdData/NetworkStation. To avoid changing or altering the production directory structure, create an nsflash directory in the root of the IFS using the following command, which allows user QTFTP access to this directory: CHGTFTPA ALTSRCDIR('/nsflash') Note: TFTP has no built-in security mechanisms.
Note In this scenario, we use a Flash card that is only 8MB in size. We only have enough room to place the compressed kernel on this card (denoted by the .Z extension), and not the uncompressed kernel which is about 4MB in size. Consequently, in this scenario, we do not intend to boot any IBM Network Station Series 1000s from this Flash card. The files specific to the Series 1000 are denoted by the .63 in the extension. The number 63 relates to the processor found in the Series 1000, the 603e RISC chip.
• term.nws • nsterm.nws 3.3.4 Creating a Separate Configuration File To enable the Flash card boot function, make the appropriate changes to redirect the loading of specific files from the AS/400 IFS to the local Flash memory card. Note We recommended that you create a new file called flash.nsm , rather than edit the supplied system configuration files. The supplied system configuration files can change or be overwritten with each new release of the IBM Network Station Manager program. The flash.
# flash.nsm - This file resides in the /QIBM/ProdData/NetworkStation/configs directory # # AS/400 File Service Table # set file-service-table = { {"/netstation/prodbase" nil 10.1.1.2 tftp "/QIBM/ProdData/NetworkStation/" unix 3 30 4096 4096} {"/QIBM/ProdData" nil 10.1.1.2 tftp "/QIBM/ProdData/" unix 3 30 4096 4096 } } # Read the configuration files from the server # read standard.
2. Power on the IBM Network Station. The IBM logo is shown, followed by a memory and keyboard check. 3. After the message NS0500 Search for Host System is shown, press ESC to stop the start-up sequence. Note If prompted for an administrator password, enter it now. This is the password an administrator sets using the IBM Network Station Manager program. 4.
16.Enter the correct IP address information for the fields, Gateway IP Address and Subnet Mask according to your network. The Broadcast IP address should default to the correct setting environment. 17.Press Enter. 18.Press PF4 (Set Boot Parameters). 19.Type kernel.Z in the Boot File field. 20.In the TFTP Boot Directory field, enter the following: /QIBM/ProdData/NetworkStation/nsflash/ This forces the Network Station to load the kernel from the Flash card test image. Be sure to include the final slash (/).
Network Station at start up to obtain this information. It can be read from the display after the POST (Power On Self Tests) are complete. After the Network Station has started up and presented you with the login (ACTLogin) display, sign on with the user profile that you have already configured to show the different emulator choices on the menu bar and start each emulator by pressing the appropriate menu bar buttons.
Special Command Check, command = ns5250 NSK8202: loading libprapi from /QIBM/ProdData/NetworkStation/nsflash/mods/libprapi.nws + 0:00:08:27 NSK8203: loaded 'IBM Network Station model 8361 V1.3.0 libprapi 07/14/1998, PTF fix1998290' NSK8202: loading libprxapi from /QIBM/ProdData/NetworkStation/nsflash/mods/libprxapi.nws NSK8203: loaded 'IBM Network Station model 8361 V1.3.0 libprxapi 05/06/1998, PTF DRV190' NSK8202: loading ns5250 from /QIBM/ProdData/NetworkStation/nsflash/mods/ns5250.
1. Open the file flash.nsm in /QIBM/ProdData/NetworkStation/configs using a PC editor (or FTP to copy to your PC or AS/400 system and edit locally). 2. Add the following lines to flash.nsm after the read standard.nsm statement set xserver-initial-x-resources = "ncdconsole.disable.TerminalMenu: false" set file-manager-password = password set file-manager-access-control-enabled = true Replace password with the password of your choice. 3. Save the file into /QIBM/ProdData/NetworkStation/configs and exit. 3.3.
1. Power off the IBM Network Station. 2. Ensure that the write protect switch on the Flash card is in the enable write position. 3. Insert the PCMCIA Flash card into the IBM Network Station as recommended by the manufacturer. 4. Power on the IBM Network Station. 5. When the messageNS0500 Search for Host System appears, press ESC to stop the start-up sequence. If prompted for an administrator password, enter it now (this is the password an administrator can set using the IBM Network Station Manager program).
3.3.9 Loading the Image onto the Flash Card If you completed the steps in Section 3.3.8, “Formatting the Flash Card” on page 82 to build a Flash card from start to finish, the Local File Manager display should be active on your Flash Card enabled IBM Network Station. If the local file manager is not active, follow the previous instructions on how to start it. There are several tools that you can use to load the image onto the Flash card.
3. The boot.nsl file, which resides in the path /QIBM/ProdData/NetworkStation/nsflash, must be edited before copying it to the Flash card. a. Open the file boot.nsl from the directory /QIBM/ProdData/NetworkStation/nsflash using a PC editor. b. Change the following line in boot.nsl to read: Login.bootConfigType: MOUNT_LOCAL c. Close and save the file to the same directory, /QIBM/ProdData/NetworkStation/nsflash. 4. Enter the following command on any AS/400 command line to copy the kernel and boot.
7. After the copy operation is complete, look for the message on the AS/400 that informs you that all objects were copied and no (or zero) objects failed. You can also use the IBM Network Station local file manager to check that all the files have been copied using the dir command. 8. From the Network Station local file manager, type verify on the /local file system. This verifies the file structure and reports back any errors. 9.
6. Copy the kernel to the Flash card file system by entering the following command in the local file manager: cp kernel.Z /local/ This copy operation should take approximately four minutes to complete. 7. Edit the boot.nsl file in /QIBM/ProdData/NetworkStation/nsflash before copying it to the Flash card. a. Open the file boot.nsl from the directory /QIBM/ProdData/NetworkStation/nsflash with a PC editor. b. Change the line to read: Login.bootConfigType: MOUNT_LOCAL c.
• • • • • • • • • • mwm.nws nfsd.nws ns3270.nws ns5250.nws ns5250xx.nws sbcs_im.nws seriald.nws setup.nws term.nws nsterm.nws 12.Type verify to check the local Flash card file system once the copy operation is complete. 13.Type df to display the file system size in bytes. 14.Type exit to end the local file manager program. 15.Click on logout to end the session. 16.Proceed to Section 3.3.10, “Booting the IBM Network Station Using the Flash Card” on page 89. Table 17.
Command Description help Displays a list of Local File Manager commands. info or df [/local] Lists the total size in bytes of the local file system and the total number of free bytes available. list or ls or dir [-R] [directory] Displays a list of the files stored in the local file system. This command can be used with a -R option to list subdirectory content recursively. mkdir dir_name Makes a directory named dir_name in the local file system. quit Disconnects from the Local File Manager.
1. Open the file flash.nsm in /QIBM/ProdData/NetworkStation/configs using a PC editor. 2. Change the following line from: set boot-desired-source = tftp to: set boot-desired-source = local and set modules-directory = /QIBM/ProdData/NetworkStation/nsflash/mods to: set modules-directory = /local/mods 3. Ensure the file is saved to the directory /QIBM/ProdData/NetworkStation/config . Refer to Figure 15 on page 91 for an updated example of the flash.nsm file with all changes and additions made so far.
# flash.nsm - This file resides in the /QIBM/ProdData/NetworkStation/configs directory # # AS/400 File Service Table # set file-service-table = { {"/netstation/prodbase" nil 10.1.1.30 tftp "/QIBM/ProdData/NetworkStation/" unix 3 30 4096 4096 } {"/QIBM/ProdData" nil 10.1.1.30 tftp "/QIBM/ProdData/" unix 3 30 4096 4096 } } # Read the configuration files from the server # read standard.
We highly recommend that you reset NVRAM to the factory defaults prior to any major change to the configuration of the IBM Network Station. a. Power on the IBM Network Station. The IBM logo is shown, followed by a memory and keyboard check. b. After the message, NS0500 Search for Host System appears, press ESC to stop the start-up sequence. If prompted for an administrator password, enter it now. (This is the password an administrator can set using the IBM Network Station Manager program.) c.
10.Press PF4 (Set Boot Parameters). 11.Type kernel.Z in the Boot File field. 12.Leave the TFTP Boot Directory blank. 13.In the NFS Boot Directory field, enter /local/. This forces the Network Station to load the kernel from the Flash card image. 14.In the Boot Host Protocol section, disable TFTP order and NFS order by typing a D next to the corresponding field. 15.Enter 1 next to the local order field. 16.Press Enter. 17.Press PF5 (Set Configuration Parameters). 18.Enter flash.
Provided that you entered the correct system information when configuring the three emulators using the IBM Network Station Manager program, each one starts and the appropriate system sign on display is shown. Now, you must verify that the modules were loaded from the /local/mods directory on the Flash card by reviewing the console log of the Network Station. Use the following steps to view the console log and verify that the modules were loaded from the correct directory: 1.
chosen to use the local file manager to copy files from the AS/400 IFS, instead of using the NFS support. Use the following steps to change the lines in the file flash.nsm to disable access to the local file manager: 1. Open the file using a simple text editor. 2. Delete the following lines from the flash.nsm file: set xserver-initial-x-resources = "ncdconsole.disable.TerminalMenu: false" set file-manager-password = password 3.
standard.nsm file and then overrides the values necessary to enable Flash booting. The image was tested by reading the flash.nsm file and directing the Network Station, using NVRAM, to load the files and executable modules from the test image. After the Network Station started and functioned correctly from the test image, the Flash card was formatted and the test image was copied to the Flash card, using either NFS or the local file manager on the Network Station.
3.4.1 Scenario Objectives In this scenario, we want to accomplish the following objectives: • Configure a Network Station to boot from another Network Station containing a Flash card. • Load the executable modules required for 5250, 3270 and VTxxx emulators from the Flash card. • Use ACTLogin and server separation to authenticate the user at the central site. • Load the user configuration, fonts and other volatile data from the central site, allowing the data to be maintained centrally.
• Only one Flash card is required at each remote location in this case. • Multiple Network Stations peer boot from the serving Network Station without performance degradation. 3.4.3 Scenario Disadvantages This scenario has the following disadvantages: • There is no automated central management of the Flash Cards. The system administrator must ensure that the Flash Cards are updated when any new applicable releases and/or Network Station PTFs are applied to the host system.
The peer Network Station authenticates and load volatile data from the central AS/400 system in the same manner as the Flash-card enabled Network Station. AS/400 Flash Card Enabled IBM Network Station S/390 .2 .10 WAN Link .3 Code sourced from flash card enabled Network Station Network Address: 10.1.1.x Subnet mask: 255.255.255.0 RS/6000 .4 Aunthentication, user preferences & fonts sourced from the Central AS/400. .11 Peer Boot IBM Network Station Figure 18.
If each user using different functions, for example one person requires the Netscape browser, while another requires 5250 and 3270 emulation, then these modules should reside on the Flash card to reduce network traffic and load time. • Is there a mixture of Series 100/300 and Series 1000 Network stations peer booting from the serving Network Station? If there is a mixture of Series 100/300 and Series 1000 Network Stations, should more than one serving Network Station be deployed.
3.5.3 Creating a Peer Boot Configuration File A new file must be created in /QIBM/ProdData/NetworkStation/configs, called peer.nsm , to distinguish it from the flash.nsm file. This file overrides the normal settings with those required to redirect the Network Station to load executable modules from the Flash card Network Station. An example of the peer.nsm file is shown in Figure 19. # peer.
3.5.4 Configuring the Peer Boot Network Station The NVRAM settings on the peer Network Station must be modified to direct it to load the kernel and other configuration data from the Network Station containing the Flash card. Use the following steps to modify the NVRAM settings on the peer Network Station: 1. Reset NVRAM on the IBM Network Station. We highly recommend that you reset NVRAM to the factory defaults before making any major change to the configuration of the IBM Network Station. 2.
If prompted for an administrator password, enter it now (this is the password an administrator can set using the IBM Network Station Manager program). 6. Press PF3 (Set Network Parameters). 7. The Network parameters should default to NVRAM after the reset. To change the IP Addressed from field from Network to NVRAM, use the right arrow key. 8. Enter the Network Station IP address, in this scenario the IP address of the Network Station is 10.1.1.11. 9. Enter The First Boot Host IP address of 10.1.1.10.
26.Press Enter. 27.Press Enter again to reboot the IBM Network Station. The IBM Network Station starts and loads the kernel from the Flash card located in the predefined IBM Network Station. The file peer.nsm points the Network Station to the /local/mods directory from which the emulators and ACTLogin code are loaded. Please proceed to the next section to verify that the peer Network Station has sourced the executable modules from the Flash card enabled Network Station. 3.5.
2. Click on the Messages button to view the log. 3. Use the vertical scroll bar to move up and down the log file. 4. Please refer to the example in Figure 20, which shows in bold text the 5250 emulation executable modules being sourced from the /peerboot/mods directory on the Flash card. Special Command Check, command = ns5250 NSK8202: loading libprapi from /peerboot/mods/libprapi.nws + 0:00:08:27 NSK8203: loaded 'IBM Network Station model 8361 V1.3.
We started the peer boot Network Station and checked the system logs to ensure there were no errors and the Network Station was obtaining the executable modules from the serving Network Station’s Flash card.
Chapter 4. Remote Servers and Split Boot Servers This chapter describes how the split boot feature can be used in different scenarios. These scenarios range from basic to advanced configurations. Please notice that not all of the configurations may apply to your own organization. A mixture of scenarios may better suite your needs. 4.
1. Acquire IP address: It may be already configured into NVRAM or it may be acquired from a DHCP or BOOTP server. 2. Get the kernel: The IBM Network Station gets the kernel using several available protocols (tftp, nfs, or local) from the base code server 3. Get the configuration files: Usually the standard.nsm file from the base code server. However, it can be configured to get this file from another server. 4. Get the support files: This loads the needed support files to initialize the Network Station. 5.
These functions are: • Base code server • Terminal-based configuration server • Authentication and configuration server The separation of server function in Release 3 allows you to use the split boot feature if you have multiple servers in your organization. The reasons for separating these functions can vary from site to site.
3. Migrate the user-based configuration and data of the users to the new server. 4.4.2 Scenario Overview In Figure 22, site A, which is the central location (perhaps, headquarters) is connected to the other sites starting from site B, C and so on. In our example, we assume that the initial implementation involved remote boot servers, because the sites were autonomous. 10.1.2.3 10.1.1.2 10.1.2.4 Base code server Terminal-based configs server Authentication and configuration server Site A 10.1.x.
10.1.2.3 10.1.2.4 10.1.1.2 Base code server Terminal-based configs server Authentication and configuration server Site A 10.1.x.x Site B 10.2.x.x 10.3.2.2 10.3.2.3 Site D Site C Base code server 10.3.x.x 10.4.x.x 10.3.1.2 Figure 23. Consolidated Server Topology 4.4.3 Consolidating Servers To consolidate our authentication and configuration servers, perform the following steps: 1.
In this example, 10.1.1.2 is used in the previous parameter because it is our centralized server’s IP address. After the above steps are completed, users authentication and configuration files come from the centralized server at site A. Migrate the group or users configuration and data from site C to site A. Site C has the users shown in Figure 24: • ITSCIDGRPA • ITSCIDGRPB • Both belong to group ITSCIDGRP Figure 24. Users and User Group 5.
Figure 25. User ITSCIDGRPA Now create the group profile on site A by completing the following steps: 8. Sign on to the site A AS/400 system using an administrator user ID. 9. At the command line enter the following command and press F4: CRTUSRPRF 10.Type ITSCIDGRP in the user profile field. 11.The password field should be *NONE, because this is a group profile. 12.Type in a text description for this group. This should result in a display similar to Figure 26 on page 114.
Figure 26. Group Creation Now create the users profile: 13.Type the following command on a command line and press F4. CRTUSRPRF 14.Type ITSCIDGRPA in the user profile field. 15.Type the password in the password field. Ensure that it is the same password on the old system. If it is not, inform the user of the new password. 16.Type the description in the User class field. 17.Press F10 for more options. 18.Page down to scroll down. 19.Type in a user description in the text description field. 20.
Figure 27. User’s Attributes (Part 1 of 2) Figure 28. User’s Attribute (Part 2 of 2) Now we need to migrate configurations and data.
We are going to use a PC with Windows 95 and CA/400 connected to an AS/400 in this example. To continue, we need to have the AS/400 connections folder from CA/400 already configured. 21.Select Tools from the Explorer menu. 22.Select the Map Network Drive menu option. 23.Map any available drive letter to the site C host name preceded by two backslashes. In our example, it is drive F: to \\MYSERVER. 24.Map any available drive letter to the site A host name preceded by two backslashes.
Figure 29. Paste Group’s Configuration Files The group configuration files should be copied, as shown in Figure 30 on page 118.
Figure 30. Resulting Group’s Configuration Files In the next steps, the user configuration files are copied. 27.Select the F:—> QIBM —> UserData —> NetworkStation —> Users —> TSCIDGRPA folder on the left pane. Press the right mouse button over the folder and select Copy. 28.Select the G:—> QIBM —> UserData —> NetworkStation —> Users folder on the left pane. On the right pane right-click over a white area and select Paste. 29.Repeat the above two steps using ITSCIDGRPB.
folder on the left pane. Press the right mouse button over the folder and select Copy. 30.Select the G:—> QIBM —> UserData —> NetworkStation —> Users folder on the left pane. On the right pane, right-click over a white area and select Paste. 31.Finally you have to copy both user data folders, which are in F:—> QIBM —> UserData —> NetworkStation —> Home —> ITSCIDGRPA and F:—> QIBM—> UserData —> NetworkStation —> Home —> TSCIDGRPB. These subdirectories may not exist.
4.5 Roaming Feature The roaming feature allows mobile users (for example, users that are not at their home systems) to use the facilities of a remote system to access their local user-based terminal setup. At the Network Station login dialog screen or display there is a Roam button that allows you to locate your home configuration files.
After the Network Station has booted up, the visiting user selects the Roam button on the login dialog. The user then enters the name or address of the Chicago authentication server (such as nsm1chicago.mycompany.com or 10.2.1.2). As a result, the Chicago authentication server validate or authenticates the user ID and password entered, and downloads any user based configuration information.
Distributed Configuration Central Site Remote Sites NSM Boot Code ConfigurationFiles Authentication High Speed Connection (T1 or better) Networkstations Figure 32.
4.5.1.2 Remote Boot with Centralized Configurations This example, is perhaps the most common configuration (see Figure 33). Distributed Configuration Central Site Remote Sites Boot Code Boot Code NSM ConfigurationFiles Authentication High Speed Connection (T1 or better) Networkstations Boot Code Figure 33. Remote Reboot with Centralized Configurations By deploying a boot server at each remote site, we get better usage of the remote and local bandwidth available.
4.5.1.3 Remote Boot Servers Provide All Functions Remote boot servers are used to provide all functions (such as boot, authentication, and so on) to the Network Station. The advantages for this strategy are: • Independent from central authentication servers (for example, if the link goes down) • Smaller bandwidth required • Faster bootup • Remote servers can be used to deploy other applications The disadvantages for this strategy are: • More hardware required • More servers to deploy and manage 4.5.
If you are using a centralized model, it can appear as shown in the Figure 35. Centralized Model Site A Site B Site C Site D Figure 35. Centralized Model In Figure 35, every site is connected to site A and every remote site has a local server. For example, a bank or insurance company may keep their branch office data local (for example, in the remote servers), but may transfer updated statistics or prices from the central location.
advantages and disadvantages. In general, the distributed model is the opposite. The advantages of the centralized model are: • • • • Less management overhead Reduced hardware costs Reduced hardware deployment costs Reduced application deployment costs The disadvantages of the centralized model are: • Some data or applications may not be accessible if the link goes down . • Increased communication costs (for example, higher bandwidth). • Increased cost in communication hardware.
Chapter 5. Twinax Attachment of Network Stations The non-programmable terminal (NPT) has, traditionally, been one of the user interfaces to an AS/400 system. The NPT’s limited capabilities however, has prevented it from connecting to an intranet or Internet. For such connectivity, a personal computer (PC) would be considered but with an associated cost for PC hardware, software, on-going maintenance, support costs and possibly additional wiring.
For further information regarding the IBM Network Station Twinax model, visit the Web site: http://www.pc.ibm.com/networkstation. Clicking on the Support and Services tab will present a link to the IBM Network Station Release 3.0, which contains detailed information on the Model 341. 5.2 AS/400 Software Requirements The AS/400 software must meet the following requirements: • OS/400 level must be V4R2 or higher • Cumulative PTF package C8140420 or later 5.
5.4.1 Scenario Overview This scenario shows an example of a twinaxial Network Station subnet attached to an AS/400 system. This same AS/400 server has connectivity to a LAN. There is a minimum configuration needed on the Network Stations and some TCP/IP configuration required on the AS/400 system. A private set of IP addresses is used for the twinax subnet. 5.4.2 Scenario Objectives The objectives of this scenario are to: • Configure the twinax attached IBM Network Stations.
.2 Intranet LAN 10.1.1.0 As2.mycompany.com .1 *WSC Twinax Subnet Subnet ID: 10.10.10.0 Mask: 255.255.255.0 Figure 36. TCP/IP Network Topology for Basic IP over Twinax Scenario 5.4.6 Task Summary The following tasks are required to implement this scenario: 1. Define a TCP/IP address range to use on the twinax subnet. 2. Configure and start the IBM Network Station. 3. Configure an AS/400 IP interface as determined by messages logged in the QSYSOPR message queue. 5.4.
Network Stations can be on port 1 or any other available port that does not have NPT’s connected. This type of configuration is not mandatory but is suggested for performance reasons. When a twinax IBM Network Station is powered on for the first time, it prompts you to specify the address to use for the port to which it is connected. This is not the TCP/IP address. It is an address, from 0 through 6, to use on the workstation controller port to which the IBM Network Station is connected.
e. f. g. h. i. Enter L to reset the NVRAM. Enter S save the defaults into NVRAM. Enter Y to the question: Are you sure? Enter Q to quit. Power the IBM Network Station off and then on again. It starts with the factory settings and prompts you to input a station address. If you only want to change the address, wait until the message NS0500 Search for Host System appears on the Network Station. Press Esc and select option 8 (Set Twinax Station Address), from the IBM Network Station Setup Utility menu. 3.
Note If the message NS0500 is logged on the Network Station and there are no messages logged in QSYSOPR message queue, check the System Value QAUTOCFG using the AS/400 command DSPSYSVAL QAUTOCFG. If this value is set to OFF, change it to ON to connect and configure twinax IBM Network Stations to your AS/400 system. The QHST log on the AS/400 system has additional messages logged, as shown in Figure 38.
Work with Configuration Status AS1 08/31/98 13:28:21 Position to . . . . . Starting characters Type options, press Enter. 1=Vary on 2=Vary off 5=Work with job 8=Work with description 9=Display mode status 13=Work with APPN status... Opt Description Status -------------Job-------------QTDL824300 ACTIVE QTDL8NET VARIED ON QTDL8TCP VARIED OFF Figure 39. Configuration Status Display of Automatically Created QTDL Descriptors Figure 40 shows the detail of the twinaxial data link control line description.
Display Device 5769SS1 V4R3M0 980729 Device description . . . . . . . Option . . . . . . . . . . . . . Category of device . . . . . . . Device class . . . . . . . . . . Device type . . . . . . . . . . Device model . . . . . . . . . . Port number . . . . . . . . . . Switch setting . . . . . . . . . Online at IPL . . . . . . . . . Attached controller . . . . . . Keyboard language type . . . . . Print device . . . . . . . . . . Output queue . . . . . . . . . . Printer file . . . . . . . . . . Library . . . . .
Add TCP/IP Interface (ADDTCPIFC) Type choices, press Enter. Internet address . . . . . . . . Line description . . . . . . . . Subnet mask . . . . . . . . . . Associated local interface . . . Type of service . . . . . . . . Maximum transmission unit . . . Autostart . . . . . . . . . . . PVC logical channel identifier + for more values X.25 idle circuit timeout . . . X.25 maximum virtual circuits . X.25 DDN interface . . . . . . . TRLAN bit sequencing . . . . . . 10.10.10.
• The TCP/IP address (in this scenario 10.10.10.2) assigned to the Network Station. • The IP address (in this scenario 10.10.10.1) for the Twinax interface. • The Configuration Directory (in this scenario /QIBM/ProdData/NetworkStation/configs/) The IBM Network Station updates its own NVRAM settings with the Boot Host IP Address and Configuration Directory. On the AS/400 system, the QTDLC line, controller and device are ACTIVE . The configuration display is shown in Figure 44.
Display Device Description 5769SS1 V4R3M0 980729 Device description . . . . . . . . : DEVD Option . . . . . . . . . . . . . . : OPTION Category of device . . . . . . . . : Device class . . . . . . . . . . . : DEVCLS Device type . . . . . . . . . . . : TYPE Device model . . . . . . . . . . . : MODEL Port number . . . . . . . . . . . : PORT Switch setting . . . . . . . . . . : SWTSET Internet address. . . . . . . : Online at IPL . . . . . . . . . . : ONLINE Attached controller . . . . . . .
Display BOOTP Table Entry System: Network device: Client host name . . : MAC address . . . . . : IP address . . . . . : Hardware type . . . . : Network routing: Gateway IP address . : Subnet mask . . . . . : Boot: Type . . . . . . . . : File name . . . . . . : File path . . . . . . : Press Enter to continue. AS1 DSP02_AS1.MYCOMPANY.COM 00.00.a7.02.38.d1 10.10.10.2 26 IBMNSM kernel /QIBM/ProdData/NetworkStation Figure 47. Display of BOOTP Table Entry 5.4.
5.5 Transparent Subnet Masking In this scenario, we allow the twinax subnet access to the local LAN and beyond. With the introduction of transparent subnet masking , introduced in V4R2 of OS/400, an addressing scheme for the twinax subnet can be configured on the AS/400. This implementation allows IP over twinax devices to appear as though they were on the local network. Transparent subnet masking uses different masks over the same network ID.
T r a n s p a r e n t S u b n e ttin g 1 0 .1 .x .x 2 5 5 .2 5 5 .0 .0 1 0 .1 .1 .x 2 5 5 .2 5 5 .2 5 5 .0 1 0 .1 .3 .x 2 5 5 .2 5 5 .2 5 5 .0 1 0 .1 .2 .x 2 5 5 .2 5 5 .2 5 5 .0 Figure 48. Transparent Subnetting Example 5.5.1 Twinax Transparent Subnetting Example The twinax subnet requires a contiguous range of TCP/IP addresses defined and allocated. Figure 49 helps determine which mask to apply and what range of addresses you can use.
Looking at the Figure 49 on page 141, a mask of 128 in the last octet provides two address groups: • .1 to .126 • .129 to .254 The subnet boundaries in both groups cannot be used. In this case, the addresses .0, .127, .128 and .255 cannot be used. The same applies for a mask of 240. This mask gives you 16 groups of (16-2) contiguous addresses, remembering that the boundary addresses in each group, cannot be used.
T ra n s p a re n t S u b n e ttin g T w in a x S c e n a rio .1 9 0 1 9 2 .1 6 8 .1 .x 2 5 5 .2 5 5 .2 5 5 .0 .1 8 9 .2 .3 25 5 h os ts a v a ila b le .5 .1 9 3 1 9 2 .1 6 8 .1 .1 9 2 2 5 5 .2 5 5 .2 5 5 .2 2 4 .1 9 4 30 h o s ts a v a ila ble .2 2 5 .2 4 1 1 9 2 .1 6 8 .1 .2 4 0 2 5 5 .2 5 5 .2 5 5 .2 4 0 1 9 2 .1 6 8 .1 .2 2 4 2 5 5 .2 5 5 .2 5 5 .2 4 0 .2 2 2 T w in a x 1 .4 .2 2 6 .2 3 2 .2 3 8 .2 4 2 T w in ax 2 .2 4 8 .
boundary addresses within a group cannot be used, the group of addresses for subnet Twx1 is from 192.168.1.193 to 192.168.1.222. The third group, Twx2, has a subnet address of 192.168.1.224 and a mask of 255.255.255.240. This mask gives you 16 groups of 16 contiguous IP addresses. The group of addresses that is defined, within DHCP, is from 192.168.1.225 to 192.168.1.238. The last group, Twx3, has a subnet address of 192.168.1.240 and a mask of 255.255.255.240.
5.6.3 Scenario Advantages The advantages of this scenario are: • It is easy to connect twinax attached IBM Network Stations to an existing network. • Minimal configuration required on the IBM Network Stations. • The IBM Network Stations have access to hosts beyond the immediate AS/400 server. 5.6.4 Scenario Disadvantages The disadvantage of this scenario is that an understanding of concepts, such as subnetting and Proxy ARP, may be required if the network has a somewhat restricted addressing scheme. 5.6.
5.6.6 Task Summary Note Depending on the TCP/IP addressing scheme of your network, you must ensure that the address pool, which your are configuring for your twinax subnet, is not duplicated in another pool within the entire network. If you have the ability in your network to allocate 64 IP addresses to the twinax subnet, you should do so and realize that some of the IP addresses will not be used.
address of 10.1.1.193 is designated for the workstation controller (interface address). Figure 53 provides a visual representation of the address space that is allocated to the twinax subnet. Mapping Subnet Mask Settings to Host Address Ranges Mask Settings: Number of contiguous 24 bits: .0 .128 25 .192 Twinax Subnet range 26 .224 27 .240 28 .
Display Messages Queue . . . . . : Library . . . : Severity . . . : QSYSOPR QSYS 90 System: Program . . . . : Library . . . : Delivery . . . : AS1 *DSPMSG *HOLD Type reply (if required), press Enter. Automatic configuration created device description DSP02. Line QTDL827500 varied on successfully. DSP02 cannot connect. TCP/IP interface not added for line QTDL827500. Controller QTDL8NET contacted on line QTDL827500. Figure 54.
The display device created underneath the workstation controller (CTL01 in this case) is shown in Figure 56. This figure also shows the console, DSP01, for the AS/400 system. Work with Configuration Status Position to . . . . . AS1 10/02/98 10:06:17 Starting characters Type options, press Enter. 1=Vary on 2=Vary off 5=Work with job 8=Work with description 9=Display mode status 13=Work with APPN status...
Add TCP/IP Interface (ADDTCPIFC) Type choices, press Enter. Internet address . . . . . . Line description . . . . . . Subnet mask . . . . . . . . Associated local interface Type of service . . . . . . . . Maximum transmission unit . . . Autostart . . . . . . . . . . . PVC logical channel identifier + for more values 10.1.1.193 QTDL827500 Name, *LOOPBACK, *VIRTUALIP 255.255.255.192 10.1.1.2 *NORMAL *MINDELAY, *MAXTHRPUT... *LIND 576-16388, *LIND *YES *YES, *NO 001-FFF Figure 57.
Work with TCP/IP Interfaces System: Type options, press Enter. 1=Add 2=Change 4=Remove Internet Opt Address 10.1.1.2 10.1.1.193 127.0.0.1 5=Display Subnet Mask 9=Start AS1 10=End Interface Status 255.255.255.0 Active 255.255.255.192 Active 255.0.0.0 Active Figure 59. TCP/IP Interface Status Display If you return to the Network Station, the boot process should be continuing. The TDLC component, on the AS/400 system, sends an initiation link to the IBM Network Station.
The display device, DSP02, is also updated to include the assigned IP address of 10.1.1.194. This is shown in Figure 61. Display Device Description Device description . . . . . . . . : Option . . . . . . . . . . . . . . : Category of device . . . . . . . . : DSP02 *BASIC *DSP Device class . . . . . Device type . . . . . Device model . . . . . Port number . . . . . Switch setting . . . . Internet address . Online at IPL . . . . Attached controller . Keyboard language type *LCL 5150 3 1 0 10.1.1.
Display BOOTP Table Entry System: Network device: Client host name . . : MAC address . . . . IP address . . . . Hardware type . . . Network routing: Gateway IP address Subnet mask . . . . Boot: Type . . . . . . . File name . . . . . . : . : . : AS1 DSP02_AS1.MYCOMPANY.COM 00.00.a7.02.38.d1 10.1.1.194 26 . : . : . : . : File path . . . . . . : IBMNSM kernel /QIBM/ProdData/NetworkStation Figure 63.
5.7 Twinax IBM Network Station with Local DHCP Server Scenario This scenario attaches the twinax IBM Network Stations to a local workstation controller on the AS/400 system. The local workstation controller is CTL01, which also supports the system console. DHCP is used to configure the workstation controller with an IP address and to provide the twinax IBM Network Stations with network start-up information. A network addressing scheme, that enables Proxy ARP, is implemented.
5.7.5 Scenario Network Configuration Figure 64 shows the network topology used for this scenario. The twinax attached IBM Network Stations are connected to the DHCP server, As1. The IBM Network Stations receive their start-up information from the As1 system. The IBM Network Stations are on their own subnet which is taken out of the address space 10.1.1.0. 1 0 .1 .1 .0 m ask 2 5 5 .2 5 5 .2 5 5 . 0 .2 .5 0 A s 1 .m y c o m p a n y .c o m A s 2 .m y c o m p a n y .c o m D H C P S e rv e r * W S C .
5.7.6 Task Summary Note Depending on the TCP/IP addressing scheme of your network, you must ensure that the address pool, that you use for your twinax subnet, is not duplicated in a pool on another DHCP server within the same network. Operations Navigator DHCP server configuration does not allow you to create duplicate IP addresses in two subnets on the same DHCP server. If you have the ability, in your network, to allocate 64 IP addresses to the twinax subnet, you should do so.
Mapping Subnet Mask Settings to Host Address Ranges Mask Settings: Number of contiguous 24 bits: .0 .128 25 .192 Twinax Subnet range 26 .224 27 .240 28 .248 0 4 8 16 24 32 40 48 56 64 72 80 88 96 104 112 120 128 136 144 152 160 168 176 184 192 200 208 216 224 232 240 248 255 29 12 20 28 36 44 52 60 68 76 84 92 100 108 116 124 132 140 148 156 164 172 180 188 196 204 212 220 228 236 244 252 Figure 65. Applying Subnet Mask to Carve a Contiguous Range for Twinax Subnet 5.7.
Figure 66. AS/400 Operations Navigator - Configure DHCP Server 3. Double-click Network. This display in Figure 67 is shown. Figure 67.
4. Double-click Servers. The display Figure 68 is shown. Figure 68. AS/400 Operations Navigator - Selecting Network Servers 5. Double click TCP/IP. The display Figure 69 is shown. Figure 69. AS/400 Operations Navigator - Selecting TCP/IP Servers 6. Double-click DHCP. This shows the DHCP Server Configuration display (see Figure 70 on page 160). Ensure that Global is highlighted.
Figure 70. AS/400 Operations Navigator - DHCP Configuration 7. Right-click the mouse on Global. Select New-Subnet Advanced. Figure 71.
8. As shown in Figure 71 on page 160, select the General tab. Specify Twinax Subnet 10.1.1.192 in the Name field. Specify a network ID to make it easier to distinguish the twinax subnet from the other subnets. 9. Check Twinax subnet to enable it. 10.Specify the IP address of the workstation controller in the field Controller’s IP address. The first usable address of the allocated subnet is used. In this scenario the address is 10.1.1.193. 11.
Figure 72. DHCP Twinax Address Pool Range Tip You do not need to exclude the workstation controller IP address from the range as seen in Figure 72. The configuration excludes this address automatically. 13.Click the Leases tab. 14.Set the lease time to Never expire.
15.Click the Options tab, as shown Figure 73 on page 163. 16.Add the options for the DHCP server-to-server shown in Table 18 to the twinax IBM Network Stations. Table 18. Options for DCHP Server-to-Server Option Value 1 Subnet Mask 255.255.255.192 3 Router 10.1.1.193 (the WSC is the first hop attached device) 66 Server name 10.1.1.193 67 Boot file name QIBM/ProdData/NetworkStation/kernel Note: You should not need to add option 67; it is included in the twinax IBM Network Station class, IBMNSM3.4.
17.Click OK. 18.Close the DHCP configuration window. If the DHCP server is running, you are asked to save the changes you made. Click YES. If the DHCP server is not running, the configuration GUI closes and returns you back to the TCP/IP server display. 19.Start the DHCP server by right clicking on DHCP and select Start. If the DHCP server starts successfully, the status is updated as shown in Figure 74 on page 164. Figure 74.
using. In most cases, you should be able to use the same port and address for the replacement IBM Network Station. When a twinax IBM Network Station is powered on for the first time, it prompts you to specify the address to use for the port to which it is connected. This is not the TCP/IP address. It is an address, from 0 through 6, to use on the workstation controller port to which the IBM Network Station is connected. Use the following steps to configure the IBM Network Station to use over twinax: 1.
e. f. g. h. i. Enter L to reset the NVRAM. Enter S save the defaults into NVRAM. Enter Y to the question: Are you sure? Enter Q to quit. Power the IBM Network Station off and then on again. It starts with the factory settings and prompts you to input a station address. If you only want to change the address, wait until message NS0500 Search for Host System appears on the Network Station. Press ESC and select option 8 (Set Twinax Station Address), from the IBM Network Station Setup Utility menu. 3.
Work with Configuration Status Position to . . . . . AS1 09/16/98 16:06:25 Starting characters Type options, press Enter. 1=Vary on 2=Vary off 5=Work with job 8=Work with description 9=Display mode status 13=Work with APPN status... Opt Description QTDL825900 QTDL8NET QTDL8TCP Status ACTIVE ACTIVE ACTIVE -------------Job-------------- QTCPIP QTCP 006736 Figure 75. QTDLxxxxxx Line, Controller, and Device Configuration Status Figure 76 shows the twinaxial data link control line description.
Display Device Description Device description . . . . . . . . : Option . . . . . . . . . . . . . . : Category of device . . . . . . . . : DSP02 *BASIC *DSP Device class . . . . . Device type . . . . . Device model . . . . . Port number . . . . . Switch setting . . . . Internet address . . . Online at IPL . . . . Attached controller . Keyboard language type Print device . . . . . Output queue . . . . . *LCL 5150 3 1 0 10.1.1.194 *YES CTL01 USB *SYSVAL *DEV . . . . . . . . . . . . . . . . . . . . . . .
Figure 78 shows the interface descriptor when it is first created by the system. Notice the LCLIFC parameter defaults to *NONE. Display TCP/IP Interface Internet address . . Subnet mask . . . . Line description . . Line type . . . . . Associated local Interface status . . Type of service . . Maximum transmission Automatic start . . . .. . .. . .. .. . .: . .. . .. . .. .. . .: . .. . .. . .. .. . .: . .. . .. . .. .. . .: interface. . . . . . . : . .. . .. . .. .. . .: . .. . .. . .. .. . .: unit . . . .
Display TCP/IP Interface Internet address . . Subnet mask . . . . Line description . . Line type . . . . . Associated local Interface status . . Type of service . . Maximum transmission Automatic start . . . .. . .. . .. .. . .: . .. . .. . .. .. . .: . .. . .. . .. .. . .: . .. . .. . .. .. . .: interface. . . . . . . : . .. . .. . .. .. . .: . .. . .. . .. .. . .: unit . . . . . . . . . . : . .. . .. . .. .. . .: System: 10.1.1.193 255.255.255.192 QTDL825900 *TDLC 10.1.1.
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.
BOOTP/DHCP Relay Agent server which forwards all DHCP broadcasts, originating from the twinax subnet to the primary DHCP server, system As2. 10.1.1.0 m ask 255.25 5.255. 0 .2 .50 As1.m ycom pany.com BO O TP/D H C P relay agent *W S C .193 As2.m ycom pany.com prim ary D H C P S erver Twinax subnet Subnet address: 10.1.1.192 M ask: 255.255.255.192 Figure 80. Using Remote DHCP Server to Configure Twinax IBM Network Stations 5.8.1.
Network 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 first IBM Network Station is ready to be powered on: 1. Configure the local AS/400 DHCP configuration file on As1.mycompany.com. 2. Power on the IBM Network Station. This automatically builds the TCP/IP interface on the local AS/400 system for the workstation controller. After this completes, the IBM Network Station can be powered off. 3.
disable the subnet on the As1 system by right-clicking on the subnet and clicking on Disable. Figure 81 shows the Operations Navigator display that shows the configured subnet. The current status of this subnet is Disabled. Figure 81. AS/400 Operations Navigator DHCP Configuration for Twinax Subnet on As1 System Figure 82 on page 175 shows the TCP/IP servers display within Operations Navigator. From this figure, we see that the DHCP server on the As1 system is in a stopped state.
Figure 82. AS/400 Operations Navigator - TCP/IP Server Status 5.8.4 Power on the IBM Network Station Start the twinax IBM Network Station to allow the AS/400 system to build the necessary TCP/IP interface and line description for the workstation controller.
Work with Configuration Status Position to . . . . . AS1 09/21/98 12:10:15 Starting characters Type options, press Enter. 1=Vary on 2=Vary off 5=Work with job 8=Work with description 9=Display mode status 13=Work with APPN status... Opt Description QTDL826400 QTDL8NET QTDL8TCP Status ACTIVE ACTIVE ACTIVE -------------Job-------------- QTCPIP QTCP 006736 Figure 83. Automatically Created QTDL Descriptors A TCP/IP interface has also been automatically created.
5.8.5 Manually Changing the Auto Created TCP/IP Interface For the twinax IBM Network Station to see and be seen across the network, the LAN interface of the As1 system must be manually added in the TCP/IP TDLC interface. To add the LAN interface, complete the following steps: 1. From an AS/400 session, type CFGTCP on any command line. 2. Select option 1 (Work with interfaces). 3. To end the TDLC interface, select option 10. In this scenario, the 10.1.1.193 interface is ended. 4.
2. From a command line, enter CHGDHCPA MODE(*RELAY),and press Enter. This changes the mode of the DHCP server to be a BOOTP/DHCP Relay Agent. 3. From Operations Navigator, select As1—> Network —>Servers —>TCP/IP and right-click on BOOTP/DHCP relay agent as shown in Figure 86. Click on Configuration to select it. Figure 86. AS/400 Operations Navigator - Configuring BOOTP/DHCP Relay Agent 4. The BOOTP/DHCP Relay Agent properties window appears.
10.Click OK. The resulting display is shown in Figure 87. Figure 87. BOOTP/DHCP Relay Agent Configuration 11.From Operations Navigator, right-click BOOTP/DHCP relay agent. Select Start to start the server. The resulting status display is shown in Figure 88 on page 180.
Figure 88. AS/400 Operations Navigator - TCP/IP Server Status The BOOTP/DHCP Relay Agent now forwards DHCP messages from the workstation controller interface to the DHCP server, As2. 5.8.7 Changing the DHCP Server Configuration The twinax subnet addresses that you use must be a subset of the address space 10.1.1.x. Because of this, the pool of addresses from 10.1.1.1 through 10.1.1.254 must be divided into two ranges. The pool must also be further reduced so that it does not include the addresses from 10.
Mapping Subnet Mask Settings to Host Address Ranges Number of contiguous 24 bits: Mask Settings: .0 .128 25 .192 26 .224 27 .240 28 29 .248 0 4 8 16 24 32 40 12 20 28 36 48 44 56 52 60 64 72 80 88 68 76 84 96 104 112 120 128 136 144 152 160 168 176 184 192 200 208 216 224 232 240 248 255 92 100 108 116 124 132 140 148 156 164 172 180 188 196 204 212 220 228 236 244 252 Figure 89. Applying Subnet Masks These pools must be defined in the DHCP configuration. Complete these steps: 1.
Figure 90. AS/400 Operations Navigator - Creating New Subnet in DHCP 5. Click on the Address Pool tab and fill in the Subnet address and the Subnet mask as shown in Figure 91 on page 183. 6. When you click on Range to Assign, the values are filled in automatically. Ensure that addresses 10.1.1.2 and 10.1.1.50 are excluded from the pool because these are the LAN IP interfaces for the AS/400 systems in this scenario.
Figure 91. DHCP Configuration The second group display is shown in Figure 92 on page 184.
Figure 92. DHCP Configuration Attention For both of these groups, select the Options tab and configure DHCP option 1 to pass the real mask to use on this network, which is 255.255.255.0. You also must configure any other relevant options that clients on the main network require. The next step is to group the two address ranges together again to form one pool in the DHCP server configuration. To form a subnet group within the DHCP configuration, perform the following steps: 1.
Figure 93. DHCP Configuration - Forming a New Subnet Group 3. Specify a valid description in the Name field. Blanks or special characters are not valid in this field. Refer to Figure 94 on page 186.
Figure 94. DHCP configuration - New Subnet Group Properties 4. Highlight the first address group, under the Available subnets, and click Add. Repeat this step for the second group. The resulting display is shown in Figure 95 on page 187. 5. Click the Address Order tab. Click either In order or Balanced to select the appropriate option. In order is the default. 6. Click OK. The resulting DHCP display is shown in Figure 96 on page 187.
Figure 95. DHCP Configuration - Selection of Subnets for New Subnet Group Figure 96. DHCP Configuration - Showing Contents of Subnet Group 5.8.8 Configuring the Twinax Subnet Address Pool A TCP/IP address pool must be added on the primary DHCP server, As2. This provides network start-up information to the remote twinax client. To accomplish this, a normal IP address pool must be configured because the twinax IBM Network Stations are not locally attached.
not configured as discussed in Section 5.7.8, “Configuring the DHCP Server As1 for Twinax Support” on page 157. To configure the twinax subnet pool, complete the following steps: 1. Open the DHCP configuration, from Operations Navigator, on As2. 2. Right click Global and select New Subnet - Advanced. 3. Click General and enter the values as shown in Figure 97 on page 188. Figure 97. DHCP Configuration - New Subnet Group Note: Ensure that the Twinax subnet box is left unchecked. 4.
Figure 98. DHCP Configuration - Remote Twinax IP Address Pool 8. Click the Options tab and add the options shown in Table 19. Table 19. Options and Values Option Value 1 Subnet Mask 255.255.255.192 3 Router 10.1.1.193 (the WSC is the first hop for the devices) 66 Server name 10.1.1.193 67 Boot file name /QIBM/ProdData/NetworkStation/kernel 9. Click OK. The resulting display is shown in Figure 99 on page 190.
Figure 99. Operations Navigator - DHCP Configuration Display Showing Subnet Groups 10.Update or start the DHCP server on the As2 system. 5.8.9 Starting the IBM Network Station When the DHCP configuration has completed correctly, the twinax IBM Network Station can be powered on. The Network Station should now boot to completion. 5.8.10 Testing Connectivity In this scenario a 5250 TELNET session was started to both the As1.mycompany.com and As2.mycompany.com systems. Both attempts were successful. 5.8.
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.
TFTP S e rv e r DHCP S e rv e r As1 As2 .5 0 1 0 .1 .1 .0 2 5 5 .2 5 5 .2 5 5 .0 .2 WSC AS1 3 ) 1 0 .1 .1 .5 0 , B o o t m e up 1 ) M y n e tw o rk C o n fig u ra tio n ? 2 )G o to 1 0 .1 .1 .5 0 fo r yo u r k e rn e l a n d c o n fig u ratio n d a ta Figure 100. Twinax Attached Network Station Obtaining Network Configuration 5.9.1 Scenario Overview This scenario shows an example of a twinaxial Network Station attached to a local workstation controller on an AS/400 system.
5.9.3 Scenario Advantages The advantages of this scenario include: • Easier to connect twinax-attached IBM Network Stations to an existing network • Multiple servers do not need to exist on one system but can be configured on different systems • Routing of datagrams, from the twinax subnet to the attached LAN and vice versa, occurs automatically 5.9.4 Scenario Disadvantages There is a requirement for an extensive understanding of DHCP.
5.9.6 Task Summary Note It is assumed, in this scenario, that the DHCP server on the As1 system already functions correctly and supports the attached twinax Network Stations. If this is not the case, refer to Section 5.7, “Twinax IBM Network Station with Local DHCP Server Scenario” on page 154. This section outlines the necessary steps needed to configure the DHCP server for twinax support. The following tasks are required to complete this scenario: 1.
Figure 102. Operations Navigator - DHCP Twinax Subnet Properties 2. Click the Options tab. 3. From the previous DHCP configuration, options 1, 3, 66 and 67 were defined. They are shown in the Selected options. For this scenario, however, option 66 must be modified to show the address of the TFTP server: 10.1.1.50. See Figure 103 on page 196 for the resulting display.
Figure 103. DHCP Configuration - Defining TFTP Server 4. Click Templates. 5. Click New. To add user option 211 (protocol to use for loading the user configuration data), specify the data as shown in Figure 104 on page 197.
Figure 104. DHCP Configuration - Option 211 Configuration Protocol Template 6. Click OK. 7. Repeat the steps 4 and 5 to add the user options 212, 213 and 214 as shown in Figure 105, Figure 106 on page 198, and Figure 107 on page 198. Figure 105.
Figure 106. DHCP Configuration - Option 213 Configuration File Path Template Figure 107. DHCP Configuration - Option 214 Protocol to Use Template 8. You are returned to the main Options display. Under the Available options scroll down to the end of the list to see that options 211 through 214 have been added. The resulting display is shown in Figure 108 on page 199.
Figure 108. DHCP Configuration - Viewing Available Options 9. The newly defined tags must now have the corresponding values added. For each of the tags from 211 to 214, click the TAG number in the Available options window and then click Add to add the value into the Selected options. Figure 109 on page 200, Figure 110 on page 201 through Figure 112 on page 203 shows the addition of these tags.
Figure 109.
Figure 110.
Figure 111.
Figure 112. DHCP Configuration - Adding Tag 214 Protocol 10.After the tags are added, click OK. You are returned to the main DHCP server display. With the twinax subnet still highlighted, the options are shown with their corresponding Hexadecimal data. The resulting display is shown in Figure 113 on page 204.
Figure 113. Operations Navigator - Modified DHCP Configuration Display 11.Close the DHCP window. You are prompted to update the server. Click Yes on this window. If the server is already running, stop and restart the server from Operations Navigator. 5.9.8 Ensuring the Proper TCP/IP Servers are Started on As2 The TFTP Server and the Network Station Login Daemon Server must both be started on the As2 system for this scenario.
Work with TCP/IP Connection Status System: Local internet address . . . . . . . . . . . : As2 *ALL Type options, press Enter. 4=End 5=Display details Remote Opt Address * * * * * * * * * Remote Port * * * * * * * * * Local Port ftp-con > telnet smtp tftp www-http pop3 snmp 256 as-svrmap Idle Time 014:37:50 000:00:05 183:47:21 013:53:47 018:21:35 183:47:11 141:49:43 013:49:59 000:00:22 State Listen Listen Listen *UDP Listen Listen *UDP Listen Listen Figure 114.
adapter of the system. In this case, this parameter has the value of 10.1.1.2. A display device also exists for each of the attached Network Stations. Note If your system currently does not have DHCP configured and running, refer to Section 5.7, “Twinax IBM Network Station with Local DHCP Server Scenario” on page 154 for instructions on how to set up the DHCP server. Figure 116 and Figure 117 show the information that can be viewed within the Network Station’s Setup Utility.
IBM Network Station Set Configuration Parameters Configuration File .......................... Configuration Directory: First ..................................... /QIBM/ProdData/NetworkStation/con figs/ Second .................................... Configuration Host Protocol: First ..................................... Default Second .................................... Default Figure 117. Set Configuration Parameters Display (Before Bootup) The Network Station is now ready to be powered up.
IBM Network Station Set Network Parameters IP Addressed from ................................ NVRAM Boot Host IP Address: First Host ..................................... 10.1.1.193 Second Host .................................... 0.0.0.0 Third Host ..................................... 0.0.0.0 Configuration Host IP Address: First Host ..................................... 10.1.1.50 Second Host .................................... 0.0.0.0 Figure 119.
Chapter 6. Problem Determination This section outlines some of the more commonly used tools that can help you in diagnosing some common IBM Network Station errors. 6.1 Viewing the IBM Network Station Console Log The IBM Network Station maintains a system log of almost every event that has occurred on the Network Station. This system log can be very useful in helping to diagnose configuration problems with your Network Station. There are two methods to view the system log of the IBM Network Station.
3. From the file pulldown menu select Terminal. 4. Select Preferences 5. Change the Buffer size to 9999, as shown in to Figure 122. This enables you to scroll back through the entire console log file. Figure 122. TELNET Terminal Preferences 6. Click on OK. 7. Select Connect from the file pull down menu. 8. Click on Remote System. 9. Enter the TCP/IP address of the desired Network Station and the console log port ID of 5998. Please refer to Figure 123. Figure 123.
6.1.2 Accessing the System Log Using the Console Manager You can also view the system log directly on the Network Station by accessing the User Services Console. The following steps assume you were able to start the Network Station and have the Login display on the display, or you have signed on and authenticated against a host server. Use the follow steps to view the console log (see Figure 124): 1. Press Alt + Shift + Home to start the Network Station User Service console. 2.
212 AS/400 IBM Network Station: Techniques for Deployment in a WAN
Chapter 7. Replicating a Remote Boot Server Environment If you determine that remote boot servers are the best option for your planned remote IBM Network Station users, one of your next tasks is to develop an implementation plan. In addition, you must make a key decision about whether you will use the separation of servers function or if your remote boot servers will also act as authentication servers.
In developing the implementation plan, the company decided to use the central AS/400 system at headquarters to authenticate the IBM Network Station users at the remote sites. In this case, the Release 3 IBM Network Station Manager for AS/400 is used for the separation of servers function. The AS1 AS/400 system in New York acts as a base code server for the IBM Network Stations in New York and also provide the DHCP, Authentication and Terminal Configuration server functions to all IBM Network Stations.
Because our central and remote system are both at the same OS/400 V4R3 level, the document referenced at the end of this paragraph was used to verify that there were no prerequisite PTFs required before installing IBM Network Station Manager for AS/400 on AS2. However, if the remote server had been at an earlier release level, we would need to verify that the prerequisite PTFs were installed before doing the following steps.
Object moved. Object moved. Object QAYTCSNC1P in QUSRSYS type *FILE created. 1 objects duplicated. Ownership of object QAYTCSNC1P in QUSRSYS type *FILE changed. Object STRNSSA in QSYS type *CMD deleted. Object STRNSSA in QSYS type *CMD created. 1 objects duplicated. Ownership of object STRNSSA in QSYS type *CMD changed. Object QAYTCSNC1 in QUSRSYS type *FILE created. 1 objects duplicated. Ownership of object QAYTCSNC1 in QUSRSYS type *FILE changed. File QAYTCSNC1P started journaling to journal QYTCSJRN.
8. In this case, since DHCP is being used, ensure that the DHCP server options are set up correctly on AS1 server so that the IBM Network Stations in St. Louis have AS2 server as their base code server. For example, option 66 would point to different TFTP servers to allow IBM Network Stations in different locations to get their base code from the appropriate server.
was made to copy the base IBM Network Station Manager environment to the remote sites from the AS/400 system, SYSAS3 at the central site. In addition, common system-wide and group-level preferences were determined. Because they applied to all remote servers, the changes were made on the master SYSAS3 system before replication.
verify that there were no prerequisite PTFs required prior to installing IBM Network Station Manager for AS/400 Release 3. However, if the remote server had been at an earlier release level, then we would need to ensure that the prerequisite PTFs were installed before doing the following steps. The prerequisite PTFs are listed for each OS/400 version/release/modification level in the AS/400 Software Knowledge Database on the Web site: as400service.ibm.
Figure 127. Customize System Default Menu Bar Buttons Figure 128.
2. The group profile must already exist to set group preferences. Therefore, create the group profile grp3270 and a dummy user ID (which references grp3270 in its profile) on the master copy system, SYSAS3. Note: The grp3270 profile is a normal AS/400 group profile. Use the IBM Network Station Manager to add a 3270 button to the Menu Setup Task for the group grp3270 as shown in Figure 129. Figure 129. Add 3270 Menu Bar Button to Group Grp3270’s Preference Settings 3.
From the central SYSAS3, use the following commands to FTP the C05SAVF containing the 5648-C05 product to the existing as4work library on the remote server SYSAS4: ftp sysas4 (Enter user ID and password when prompted.) bin cd /QSYS.LIB/as4work.lib/ lcd worklib put c05savf 5.
STRTCPSVR SERVER(*HTTP) HTTPSVR(DEFAULT) 7. Because the central AS/400 SYSAS3 system was used to create the master system wide default preferences and the grp3270 group preferences, these configuration files must be transferred to the remote boot server from the master SYSAS3. 8.
In addition, the AS/400 TCP/IP Autoconfiguration: DNS and DHCP, SG24-5147, is available online at: www.redbooks.ibm.com As a result of the previous steps, the IBM Network Station users at the Rochester remote site boot from their local SYSAS4 AS/400 system which was replicated from the master copy SYSAS3 AS/400 system at the central site.
Chapter 8. Using a Network Station to Access Mail Electronic mail, called e-mail, is information that is sent electronically to and from users on an interconnected network by using a computer with special application software. In this chapter, we describe how the IBM Network Station can access e-mail from POP3 Server and Domino Server. 8.1 POP3 Mail Configuration The Post Office Protocol (POP) is the AS/400 implementation of the Post Office Protocol Version 3 mail interface.
b. Verify that there is an IP address associated with the host name for the system, either in the DNS server configuration or local host table. For the DNS server, add an A record in the DNS server configuration for the SMTP mail server host as shown in the following example: DNS as1.mycompany.com IN A 10.1.1.1 Figure 131.
Add Directory Entry Type choices, press Enter. Mail service level . . 2 1=User index 2=System message store 4=Lotus Domino 9=Other mail service For choice 9=Other mail service: Field name . . . . Preferred address . . . F4 for list 3 1=User ID/Address 2=O/R name 3=SMTP name 9=Other preferred address F4 for list Address type . . . . For choice 9=Other preferred address: Field name . . . . F4 for list Figure 134.
b. To start the POP3 server, run the following command: STRTCPSVR SERVER(*POP) c. To start the Mail server Framework, run the following command: STRMSF For more detail information about how to configure the POP3 Server on an AS/400 System, refer to the redbook AS/400 Electronic-Mail Capabilities, SG24-4703. This manual is available at the Web site: www.redbooks.ibm.com The term POP or POP3 is used throughout this chapter and should be considered synonymous. 8.
Figure 136 on page 229 shows the main Lotus eSuite Workplace desktop. Figure 136. eSuite Workplace Desktop 8.2.1 Starting eSuite on the Network Station To enable users to start eSuite, perform the following tasks: 1. Enable users or groups to access eSuite. 2. Start RMI and eSuite registry server on the AS/400. 8.2.1.1 Enabling Users or Groups to Access eSuite Before users or groups can access eSuite, the system administrator must enable these users or groups to use eSuite.
Figure 137. Menu Content Defaults Display 2. Click Group defaults or User defaults depending on which group or user you want to enable and then click Browse. 3. Select the group or user you want to enable, then click Select and return. 4. Click Next at the bottom of Menu Content Defaults, this shows you the Menu Content for the group or user you wish to enable. 5. The next display is the Desktop and Menu Bar options.
Note If the user or group does not receive the main Lotus eSuite Workspace desktop, after logging on to the Network Station, ensure that both the RMI and eSuite servers are active on the AS/400. These jobs, QESRRMI and QESRSVR, run in the QSYSWRK subsystem. Details on starting these servers are included in the following section. 8.2.1.
Figure 139. eSuite Mail Configuration 2. The first time you start eSuite mail, you are prompted to enter some information. Ask your system administrator for the following login information: • Login name. For example, if you are John Doe, your login name to your eSuite mail account might be jdoe • Mail account password. For example, your password is: lotus. Note: The asterisk (*) character is shown when you type in your password. • Name.
• Mail server path. This is the path to the mail server where your messages are stored, for example: sysnam.mycompany.com • Mail server type (IMAP4 or POP3). This identifies the mail server type to which you are going to login. In this case, click POP3 instead of IMAP4. • SMTP server path. This is path to the SMTP server that sends your messages over the Internet. For example: sysnam.mycompany.com. In this example, we use the same AS/400 system as both our POP3 and SMTP server.
Tip You can set eSuite mail to automatically log the user into the mail account using the user name and password from the initial login. Follow these steps to accomplish this: 1. 2. 3. 4. In the action bar at the bottom of the display, click Mail. In the pop-up menu, click Preferences. In the pop-up-display, click Management. Click one or more options: • Move deleted messages intothe Trash folder. • Always save a copy of a message when sending mail.
3. Click Next at the bottom of the display. The Network Setting display appears as shown in Figure 141. Figure 141. Network Settings - System Defaults Display 4. Enter the HTTP Proxy address and Port number. 5. Click Finish to end and save configuration. 8.3.1.2 Loading NC Navigator from Network Station Use the following steps to load the NC Navigator on the IBM Network Station: 1. Logon to the Network Station. 2. After the login is complete, clicks NC Navigator on the menu bar.
Figure 142. Main Dsplay of the NC Navigator Browser 8.3.2 Configuring NC Navigator to Access e-mail Before you can access e-mail using the NC Navigator, you must first setup the e-mail configuration. Use the following steps to configure e-mail: 1. Select the Mail options. 2. Set up server information. 3. Set up your identity.
8.3.2.1 Selecting Mail Options The first time you start NC Navigator mail, you may need to enter some information. 1. From NC Navigator display, click Options Preferences. —> Mail and News 2. Click the Servers tab. The display in Figure 143 is shown. Figure 143. NC Navigator: Mail & News Preferences Display 3. To access e-mail on POP3 server, you must provide the server information. As shown in Figure 143, enter the following information: • SMTP Server—For example: sysnam.mycompany.com.
• Name—This is the name that your mail recipient will see when they receive your message.For example: John Doe, • Email Address—For example: jdoe@sysnam.mycompany.com. In this example, jdoe is the AS/400 profile name for the user on the AS/400 system. The AS/400 host name is sysnam and the domain name is mycompany.com . An example of the NC Navigator mailbox is shown in Figure 144. Figure 144.
8.4 Domino Access Domino for AS/400 is the implementation of a Lotus Domino server on the AS/400 platform. Lotus Domino, on any of the supported platforms, can provide users with a range of server functions. Some of these server functions are: • • • • Mail server for Notes, POP3, or IMAP4 clients Database server Database replication server HTTP server In providing these server functions, Domino supports many protocols.
Before you run the Configure Domino Server (CFGDOMSVR) command, decide what to use for these key characteristics. These characteristics are discussed here briefly. For more information, see Planning the Domino System. 8.4.1.1 Server Name To avoid additional TCP/IP configuration, use the TCP/IP host name of your AS/400, as the Domino server name. Each Domino server has a unique name that is maintained in its own ID file. Domino creates the server ID automatically during the server setup processing. 8.4.1.
8.4.1.3 Organization Typically, the organization name is the name of your company or a major division within your company. Each organization has a Certifier ID that is stored in a file named CERT.ID. During the server setup processing, Domino creates the organization Certifier ID automatically using the organization name you specify and an optional country code. When you register new users or servers, Domino uses the Certifier ID to certify each user or server.
8.4.2 Avoiding Conflicts between AS/400 HTTP Server and Domino The AS/400 operating system (OS/400) includes several TCP/IP application servers, including an HTTP server, that is known as the Internet Connection Secure Server (ICS). This HTTP server processes HTML documents, CGI scripts, and Java scripts for home pages. Domino for AS/400 also provides an HTTP server capability which enables Notes databases to be seen as HTML documents on the Web. You can have both HTTP servers installed and running.
Note If you set a port number other than 80, the client must include a specific port number on requests to the Domino server. The port number is preceded by a colon and follows the host name in the URL. In this example we use port 8080 for Domino HTTP server, the URL, http://as1.mycompany.com:8080/, requests the default page from a host named as1.mycompany.com that is listening on port 8080. The AS/400 system on which the Domino server is installed and running is as1.
3. In the Public Address Book, open the Server document for the Web server. In the Agent manage r section, enter the name of a person or server in the Run restricted LotusSript agents field. This person or server is anyone you want to have this access on the server, and whose ID to which you have access. It is not necessarily the name of the Web use because the user does not have a Notes ID. 4. Start the Notes workstation and switch to the ID specified in step 2. 5.
Figure 145. User ID and Password Prompt 8.4.3.2 Views User are presented with a full variety of Mail File views when accessing their WebMail templates. When using a browser to access the Mail file on the Domino Server, the user sees the views as shown in Figure 146 on page 246.
Figure 146. Views Display These views are presented as icons on the left side of the window. Figure 147 on page 247 shows a sample Inbox view with a message visible on the right and other Views and Folders on the left.
Figure 147.
• • • • Send broadcast meeting invitations Confirm, cancel, or reschedule meetings Review invitee responses Create and view bookmarks, phone messages, and tasks Because of browser limitation, the following features are not yet available for Web mail users: • • • • • • • • • • • • • • • • Convert a mail message to a task Reply with history or forward documents Sign messages Schedule repeating appointments Reserve resources or rooms for a meeting Set and receive alarm notices Accept counter proposal for an
The IBM Network Station can use either the protocol called Independent Computing Architecture (ICA) or X11 to connect into WTSE. These protocols are not provided by WTSE. The ICA functionality provided by Citrix’s ICA protocol is still available but requires the installation of Citrix’s MetaFrame product in addition to WTSE. If the X11 functionality is also desired, then NCD’s Unix Integration Services are required, in addition to MetaFrame.
Figure 148. Configuring an ICA Client The client, ICACLNT, must be entered in the Program to run box. The term e -host is required in the Parameter i box. This is needed to indicate the target host. In our, example (Figure 148) we also used the term -colors 16 to ensure no color blinking. The syntax and usage of the ICACLNT client name is shown in the following example: ICACLNT [-host hostname or ip address] [-options ...
5. Select the File Server Install option on the next Notes Install display. 6. The next display asks if you want to change the defaults option in the Typical vs. Custom Setup display. It is recommended that the Custom Setup option be chosen and that all features that are not needed are deselected. One very obvious feature is the Notes Modem definitions. The only options left selected are Notes Workstation and Attachment viewer. 7.
16.Create a text file called nclogin.bat in the c:\wtsrv\system32\repl\import\scripts\ directory that contains the same lines as this sample file lotusnotesinstall.txt shown in the following example. Be sure to replace SERVERNAME with your server’s name.
CHANGE USER /EXECUTE When a user logs on the next time, their user directory is automatically created, mapped to h:\, and the Lotus Notes Workstation set up as an application as shown in Figure 149. Figure 149.
254 AS/400 IBM Network Station: Techniques for Deployment in a WAN
Appendix A. Flash Card Scenarios This appendix contains examples of the flash.nsm and peer.nsm files and a list of the files and directory structure that must be loaded onto the Flash card for the relevant application support. In all cases the source directory structure is /QIBM/ProdData/NetworkStation. For example, the file ACTLogin is sourced from /QIBM/ProdData/NetworkStation/mods/ and must be placed in the directory /local/mods/ on the Flash card.
miscpr32.nws mwm.nws nfsd.nws ns3270.nws ns5250.nws ns5250xx.nws nsterm.nws sbcs_im.nws seriald.nws term.nws The flash.nsm file and peer.nsm files are also shown as an example. Please note that the flash.nsm file contains lines that are optional depending on whether you intend to use the peer boot functionality.
Flash.nsm File Example # flash.nsm - This file resides in the /QIBM/ProdData/NetworkStation/configs directory # # AS/400 File Service Table # set file-service-table = { {"/netstation/prodbase" nil 10.1.1.30 tftp "/QIBM/ProdData/NetworkStation/" unix 3 30 4096 4096 } {"/QIBM/ProdData" nil 10.1.1.30 tftp "/QIBM/ProdData/" unix 3 30 4096 4096 } } # Read the configuration files from the server # read standard.
Peer.nsm File Example # # peer.nsm - place onto the flash card in /local/configs and into # /QIBM/ProdData/NetworkStation/configs # #Set up the file service table to access the server set file-service-table = { {"/netstation/prodbase/configs/" nil 10.1.1.2 tftp "/QIBM/ProdData/NetworkStation/configs/" unix 3 30 4096 4096 } { "/QIBM/ProdData/NetworkStation/configs/" nil 10.1.1.2 tftp "/QIBM/ProdData/NetworkStation/configs/" unix 3 30 4096 4096 } { "/netstation/prodbase/" nil 10.1.1.
Attention Please be aware that when the fonts directories are stripped down, the fonts.dir file (this file contains a directory of available fonts) must be updated to reflect that not all of the original fonts are located on the Flash card. The utility required to do this, mkfontdir, is generally only available on UNIX systems. This limits your ability to scale down the font directories unless you have access to a UNIX system. This section was added for your reference.
/local/X11/app-defaults/ mcuis Mwm system.mwmrc /local/X11/fonts/pcf/i18n/ Block11.iso1_UCS.pcf.Z Block17.iso1.UCS.pcf.Z Ergo15.iso1_UCS.pcf.Z Ergo17.iso1_UCS.pcf.Z fonts.dir /local/X11/locale/ locale.alias locale.dir /local/X11/locale/UTF-8_BASE-0/XLC_LOCALE /local/X11/locale/UTF-8_C/XLC_LOCALE /local/X11/locale/UTF-8_iso8859-1/XLC_LOCALE /local/mods/ actlogin.nws colormap.nws export.63a export.nws filed.nws libconf.nws libmlc.nws libprapi.nws libprxapi.nws lpd.nws lprd.nws mcuis.nws miscpr32.nws mwm.
seriald.nws term.nws A.2.1 The Flash.nsm File Additions to Support Local Font Storage To support local font storage, the following lines must be added to your flash.nsm file. Flash.nsm File Additions # Add these lines to flash.nsm # # Get the background screen and screensaver from the flash card filesystem set set set set set pref-screen-background-bitmap-file = "/local/SysDef/ibmwall.xbm" pref-screensaver-bitmap-file = "/local/SysDef/ibmwall.
A.3 Support for NC Navigator with Java Virtual Machine The files required to start the Network Station and run the NC Navigator Browser and the Java Virtual Machine from the Flash card is found in this section. There is no change to the flash.nsm and peer.nsm files because all of the configuration for NC Navigator is done on the server using IBM Network Station Manager program. The only difference is the files which are required on the Flash card.
/local/java/lib/ appletviewer.properties awt.properties content-types.properties font.properties font.properties.en javac.properties rmic.properties serialver.properties /local/java/lib/security/ java.security /local/mods/ actlogin.nws desktop.nws export.63a export.nws filed.nws java.63a java.nws jawt.63a jawt.nws jcomm.nws jjpeg.63a jjpeg.nws jmath.63a jmath.nws jmmedia.63a jmmedia.nws jnet.63a jnet.nws jsysresource.nws jzip.63a jzip.nws libconf.nws libmlc.nws libprapi.nws libprxapi.nws loaddb.nws lpd.
lprd.nws mcuis.nws miscpref.nws mwm.nws navio.nws nfsd.nws sbcs_im.nws seriald.nws A.4 Support for ICA Client In this scenario, the Network Station is started and the ICA client is loaded from the Flash card. The ICA client enables the Network Station to connect to a multi-user NT server running WinCenter or Citrix MetaFrame. There is no change required to the flash.nsm and peer.nsm files.
nfsd.nws sbcs_im.nws seriald.nws A.5 Java Application Support In this example, the Network Station is started from the Flash card with the intent to run a Java application from the Flash card. Using compressed kernels requires approximately 16 megabytes of space on the Flash card plus the java application you want to run. This example has not been tested. The list is intended as a starting point to identify which files are required by the Network Station to support a Java application.
export.63a export.nws filed.nws java.63a java.nws jawt.63a jawt.nws jcomm.nws jjitc.63a jjpeg.63a jjpeg.nws jmath.63a jmath.nws jmmedia.63a jmmedia.nws jnet.63a jnet.nws jsysresource.nws jzip.63a jzip.nws libconf.nws libmlc.nws libprapi.nws libprxapi.nws libprdbcs.nws mcuis.nws mwm.nws nfsd.nws sbcs_im.nws seriald.nws setup.
Appendix B. Executable Module Descriptions The appendix attempts to outline each module, found in release 3.0, with a brief description of the modules function. This is not a definitive listing. However, it provides some information on what each module is used for. B.1 Module Information Table 20. Module Information Module Name Module file ID Type Description ACTLogin actlogin.nws client Login Authentication Manager audio audio.nws extension Network Audio color map colormap.
Module Name 268 Module file ID Type Description Java system information jsysresource.nws extension Java System Resource Info. Java Zip jzip.nws extension Uncompress Java ZIP files keymap52 keymap52.nws extension 5250 Keyboard map editor local client. libconf libconf.nws library Configuration Library libmlc libmlc.nws library Used by Console => Setup libppp libppp.nws library PPP Protocol library libprapi libprapi.nws library AIX printer library libprxapi libprxapi.
Module Name Module file ID Type Description pref pref.nws utility Change user preferences (from the console) qsetup qsetup.nws utility Change Quick Setup (from the console) Serial Daemon seriald.nws extension Serial/Parallel port daemon Setup setup.nws utility Change setup parameters (from the console) show show.nws utility Show Memory usage (from the console) SIE sie.nws extension SImple Image Extension (not used) Statistics stats.
270 AS/400 IBM Network Station: Techniques for Deployment in a WAN
Appendix C. 5500 Express IP Control Unit This appendix, which presents an overview of the IBM 5500 Express IP control unit, includes some technical details and example configurations. This product was not available at the time of writing. However, we provide this information to give you a more complete view of WAN connection capabilities. C.
The 5500 control unit provides connection to: • Express twinax clients attached to AS/400 systems running V4R1 or earlier. This connection is established either though LAN or WAN and SLIP. • For AS/400 systems running V4R2 or later release, the connection is still through LAN or WAN, but the PPP and SLIP are available. The 5500 supports the latest IP/Twinax devices. IBM 5250 Express Adapters and IBM 5250 Adapters (ISA) PCs with IBM 5250 adapters require no new hardware Twinax Network Stations (8361-341).
– One of the following operating systems: • MS Windows NT 4.x with Service Pack 3 • MS Windows 95 with Service Pack 1 • MS Windows 98 • Twinax IBM Network Station 8361-341 with 24 megabytes RAM minimum memory and Network Station Manager program Release 3.0 or higher. Note The 5500 Control Unit is not a router or a DHCP relay agent.
Figure 151 shows an example of an IBM 5500 used in a 5250 Express environment with a fiber optic link to a multiplexer. Figure 151.
Figure 152 shows an example of an IBM 5500 in a complex combination of network media types. Figure 152.
Figure 153 shows an example of the synchronous modem for the WAN connection between an AS/400 system and IBM 5500. Figure 153.
Figure 154 shows an example of a frame relay WAN connection to the IBM 5500 providing connectivity for remote terminals. Figure 154. Frame Relay Connectivity C.2.
C.2.1.1 Understanding IP Address Requirements Obtaining contiguous IP addresses may be difficult. Be prepared by obtaining extra addresses for future use. Valid Internet protocol (IP) addresses must meet the following criteria: • Four decimal numbers separated by periods. • Number one must be greater than or equal to 1 and less than or equal to 223. • Numbers two, three, and four must be greater than or equal to zero (0) and less than or equal to 255. • All IP addresses must be unique.
• The AS/400 system is connected through the WAN interface of the 2210 router. LAN is connected to the 2210 router and existing 5494 with twinax workstations initially connected to the 5494 migrating to the IBM 5500 control unit. C.3.0.1 Gateways and IP Addresses As part of planning the installation of your 5500 control unit, determine the range of addresses to be used by each network port of the 5500 control unit.
subnet the IBM 5500 control unit or to obtain an additional set of addresses for the twinax workstations attached to the control unit. Should you decide to obtain a new address space, the routing tables in routers that are upstream from the IBM 5500 control unit must be manually updated to include the new address space.
• Original network uses subnet mask 255.255.255.0 and is assigned addresses 100.100.100.0 through 100.100.100.255 (See Figure 155) • Desire to split this address space so that 64 addresses are reserved for use by the twinax workstations attached to the IBM 5500 control unit and 192 addresses are left for other LAN devices. • Twinax workstation use subnet mask 255.255.255.192 and can take any contiguous 64 addresses between 100.100.100.0 and 100.100.100.255.
a different address to any device on the LAN that is using one of the addresses in the range of addresses subnetted to the twinax workstations. LAN Subnet mask: 255.255.255.0 Address range: 100.100.100.0 through 100.100.100.191 Subnet Subnet mask: 255.255.255.192. Address range: 100.100.100.192 through 100.100.100.255 Figure 157. Example of a Network after Installing the IBM 5500 C.
ports to time slice. However, the 5500 control unit’s WSC is actually two mini-controllers, each responsible for servicing 4 ports. Setting the 5500 control unit’s dual mode operation to Enable allows each device to obtain quicker service. To maximize performance, balance the load between the two mini-controllers, dividing your devices equally between ports 0 through 3 and ports 4 through 7. Using Twinax Multiplexers The use of twinax multiplexers can prevent and increase in performance.
This file also prevents the NSM configuration server from changing the NVRAM settings. The 5500 control unit uses TFTP protocol to transfer the operating system kernel files but changes to NFS by default. The NC user should avoid selecting the ROAM function. By default, the authentication login display points to the TCP/IP address of the 5500 control unit (when using the 5500 control unit to boot from).
Appendix D. Special Notices This publication is intended to help System Specialists and Business Partners who are assisting customers to implement an IBM Network Station solution for their network user needs. The information in this publication is not intended as the specification of any programming interfaces that are provided by the IBM Network Station and the Network Station Manager Program.
Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites. Any performance data contained in this document was determined in a controlled environment, and therefore, the results that may be obtained in other operating environments may vary significantly.
PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. Pentium, MMX, ProShare, LANDesk, and ActionMedia are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names may be trademarks or service marks of others.
288 AS/400 IBM Network Station: Techniques for Deployment in a WAN
Appendix E. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. E.1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 291.
E.
How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change. The latest information may be found at http://www.redbooks.ibm.com/.
How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: • Online Orders – send orders to: In United States In Canada Outside North America IBMMAIL usib6fpl at ibmmail caibmbkz at ibmmail dkibmbsh at ibmmail Internet usib6fpl@ibmmail.com lmannix@vnet.ibm.com bookshop@dk.ibm.
IBM Redbook Order Form Please send me the following: Title First name Order Number Quantity Last name Company Address City Postal code Country Telephone number Telefax number VAT number Card issued to Signature Invoice to customer number Credit card number Credit card expiration date We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment.
294 AS/400 IBM Network Station: Techniques for Deployment in a WAN
Index Symbols . 207 A Access Integration Services (AIS) 26 AIS (Access Integration Services) 26 applet viewer 5 ASCII 16 authentication server, decentralized 217 B boot broadcast 3, 10 flash memory 28 peer (buddy) 3 sequence 107 storms 10 boot image creation 73 loading 82 testing 73 booting peer 96 browser NC Navigator 3 web access 243 C centralized authentication server 213 defaults.
part numbers 63 PCMCIA 63 simple technology 63 flash memory card 28 FLASH.
adapter 4 memory card 28 slot 4 peer boot configuration file 101 network topology 97 PEER.
twinax 3 advanced IP 144 attached network stations 127 basic IP 128 DHCP 154 remote boot 191 remote DHCP 171 Twinax Data Link Control (TDLC) 15 twinax subnet address pool 187 U user configuration management 121 users local 21 remote 21 V Views 245 W WinCenter 14 298 AS/400 IBM Network Station: Techniques for Deployment in a WAN
ITSO Redbook Evaluation AS/400 IBM Network Station: Techniques for Deployment in a WAN SG24-5187-00 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and return it using one of the following methods: • Use the online evaluation form found at http://www.redbooks.ibm.com • Fax this form to: USA International Access Code + 1 914 432 8264 • Send your comments in an Internet note to redbook@us.ibm.
AS/400 IBM Network Station: Techniques for Deployment in a WAN SG24-5187-00 Printed in the U.S.A.
