Using Operations Navigator to start, stop, configure, and verify a TCP/IP connection
6. Click on Properties
While this chapter uses a token-ring example, the steps are the same for Ethernet with a few differences that are noted.
You may not need to create a new line description. If a physical line is already configured, this existing line can be shared between TCP/IP and other protocols like Systems Network Architecture (SNA) at the same time.
To determine if a line description already exists:
__ 1. EnterGO HARDWAREat the command line to get the Hardware Resources menu.
You see a display similar to Figure 7.
__ 2. Select Option 1, Work with communication resources to show a display that is similar to Figure 8 on page 36.
===>
HARDWARE Hardware Resources
System: SYS1 Select one of the following:
1. Work with communication resources 2. Work with local workstation resources 3. Work with storage resources
4. Work with processor resources
5. Work with token-ring LAN adapter resources 6. Work with DDI LAN adapter resources 7. Work with all LAN adapter resources 8. Work with coupled system adapter 70. Related commands
Figure 7. Hardware Resources Menu
Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System 35
__ 3. In this example, there is already one token-ring adapter(LIN05)installed with the resource name ofLIN051. To determine if a line description exists for this adapter, use Option 5, Work with configuration descriptions, as shown in Figure 8
to show a display that is similar to Figure 9.
__ 4. If a line description already exists, the name of the line description is displayed similar to what is shown in Figure 9.
Token-Ring Only:
If you seeTRNLINEhere, do NOT use this line. Create a new one. Note the system name and the resource name as you continue with TCP/IP configuration. You need this information later. If you want to use the line description shown, go to step 2 on page 38.
If a line description does not exist, you must create one by going to step 1.
__ 1. Create a line description:
Type CRTLINTRN (CRTLINETH for Ethernet) on the command line.
In this example we gave the new line description the nameTKNTCP. From Figure 8, we know that the token-ring adapter has a resource name ofLIN051.
This is the name that the system needs to associate the line description with the communications adapter.
Work with Communication Resources
System: SYS1 Type options, press Enter.
2=Edit 4=Remove 5=Work with configuration descriptions
Opt Resource Type Text
CC02 2626 Comm Processor LIN05 2626 LAN Adapter
LIN051 2626 Token-Ring Port
Figure 8. Work with Communication Resources
Work with Configuration Descriptions
System: SYS1 Resource name . . . : LIN051
Text . . . : Token-Ring Port Type options, press Enter.
1=Create 5=Work with description 8=Work with configuration status Opt Description
_ __________
_ TKNTCP
Figure 9. Work with Configuration Descriptions display
Accept the default values for the items in Figure 10 but change the line speed
to match your line speed (usually 16M) in Figure 11. On the third display ( Figure 12 on page 38), press F10 for additional parameters. Change the default setting for Autocreate controller from *NO to *YES in Figure 13 on page 38.
Create Line Desc (Token-Ring) (CRTLINTRN) Type choices, press Enter.
Line description . . . TKNTCP Name
Resource name . . . LIN051 Name, *NWID, *NWSD
Figure 10. Creating a token-ring line description. Display 1 of 4
===>
Create Line Desc (Token-Ring) (CRTLINTRN) Type choices, press Enter.
Line description . . . > TKNTCP Name
Resource name . . . > NWSD Name, *NWID, *NWSD Online at IPL . . . . *YES *YES, *NO
Vary on wait . . . . *NOWAIT *NOWAIT, 15-180 (1 seco Maximum controllers . . . . 40 1-256
Line speed . . . . 16M 4M, 16M, *NWI
Maximum frame size . . . . 1994 265-16393, 265, 521, 10 Local adapter address . . . . . *ADPT 400000000000-7FFFFFFFFF Exchange identifier . . . . *SYSGEN 05600000-056FFFFF, *SYS SSAP list:
Source service access point . *SYSGEN 02-FE, *SYSGEN SSAP maximum frame . . . . *MAXFRAME, 265-16393 SSAP type . . . . *CALC, *NONSNA, *SNA, *
+ for more values Text 'description' . . . . *BLANK
Figure 11. Creating a token-ring line description. Display 2 of 4
Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System 37
After you have filled in the information, press Enter.
To see if the line description was created, typeGO HARDWARE, select Option 1 – Work with communication resources. Check to see if the line shows up in the listing. If it does not show in the list, repeat the steps you just completed.
__ 2. Define a TCP/IP interface.
__ a. TypeCFGTCPat the AS/400 command prompt, then select Option 1, Work with TCP/IP interfaces, on the Configure TCP/IP menu (CFGTCP) to get the display in Figure 14 on page 39.
Create Line Desc (Token-Ring) (CRTLINTRN) Type choices, press Enter.
Text 'description' . . . . *BLANK
Additional Parameters Network controller . . . . Name
TRLAN manager logging level . . *OFF *OFF, *MIN, *MED, *MAX TRLAN manager mode . . . . *OBSERVING *OBSERVING, *CONTROLLIN Log configuration changes . . . *LOG *LOG, *NOLOG
Token-ring inform of beacon . . *YES *YES, *NO
Functional address . . . . *NONE *NONE, C00000000001...
+ for more values
Early token release . . . . *LINESPEED *YES, *NO, *LINESPEED Error threshold level . . . . . *OFF *OFF, *MIN, *MED, *MAX Link speed . . . . 4M *MIN, 1200, 2400, 4800.
Cost/connect time . . . . 0 0-255
Figure 12. Creating a token-ring line description. Display 3 of 4
Create Line Desc (Token-Ring) (CRTLINTRN) Type choices, press Enter.
Cost/byte . . . . 0 0-255
Security for line . . . . *NONSECURE *NONSECURE, *PKTSWTNET.
Propagation delay . . . . *LAN *MIN, *LAN, *TELEPHONE.
User-defined 1 . . . . 128 0-255 User-defined 2 . . . . 128 0-255 User-defined 3 . . . . 128 0-255 Autocreate controller . . . . . *YES *YES, *NO
Autodelete controller . . . . . 1440 1-10000 (minutes), *NON Recovery limits:
Count limit . . . . 2 0-99, *SYSVAL Time interval . . . . 5 0-120 (minutes) Authority . . . . *LIBCRTAUT Name, *LIBCRTAUT, *CHAN
Figure 13. Creating a token-ring Line Description. Display 4 of 4
Note: TCP/IP automatically creates the interface with a line type of
*loopback. The LOOPBACK interface is provided as a local IP address to test TCP/IP or a TCP/IP application. Any data that is written to the LOOPBACK interface is echoed back to the same interface. LOOPBACK can not be used to reach a remote system.
__ b. Enter a1in the Opt field to add an interface. A display similar to Figure 15 is shown.
Work with TCP/IP Interfaces
System: SYS1 Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 9=Start 10=End
Internet Subnet Line Line
Opt Address Mask Description Type
1 _______________
_ 127.0.0.1 255.0.0.0 *LOOPBACK *NONE
Figure 14. Work with TCP/IP Interfaces display
Add TCP/IP Interface (ADDTCPIFC) Type choices, press Enter.
Internet address . . . > 9.5.5.3
Line description . . . . TKNTCP Name, *LOOPBACK Subnet mask . . . . 255.000.000.000
Type of service . . . . *NORMAL *MINDELAY, *MAXTHRPUT..
Maximum transmission unit . . . *LIND 576-16388, *LIND Autostart . . . . *YES *YES, *NO PVC logical channel identifier 001-FFF
+ for more values
X.25 idle circuit timeout . . . 60 1-600 X.25 maximum virtual circuits . 64 0-64 X.25 DDN interface . . . . *NO *YES, *NO TRLAN bit sequencing . . . . *MSB *MSB, *LSB
Figure 15. Add TCP/IP Interface display
Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System 39
Don’t Make This Mistake
A common mistake is to define not only the IP address for your AS/400, but also the addresses of all the other systems you want your AS/400 to communicate with.
Do not do this.
An address that is defined as an interface is an IP address for this AS/400 system only. An interface should never be the address of another system in your network. In most cases, only one interface needs to be defined: the IP address that identifies your AS/400 in your TCP/IP network.
The steps to follow to have your AS/400 system communicate with the other systems in your network are covered in step 3.a on page 41 .
__ c. A display similar to Figure 15 on page 39 is shown. Fill in the Internet address, Line description, and Subnet mask information. Write this information down. You need it later. See step 2 on page 33.
__ d. Accept the default values for the rest of the items on this display. Press Enter and check for messages to ensure that the interface was added.
__ 3. Default route
A route provides the connection between your system and the external network.
A route allows your system to communicate with other systems on other TCP/IP networks.
Should you skip this step?
Are all the systems you want your AS/400 to communicate with attached to the same local TCP/IP network that your AS/400 is directly attached to?
For example, are all of your systems on the same Local Area Network (LAN)? If they are, you can skip this step. Do not add any routing entries here.
AS/400 TCP/IP uses routing entries to determine how to communicate with systems that are not on the same local network as your AS/400.
If you will be using an IP router to access resources beyond your local LAN, you will need to configure at least one route entry. This route entry is a default route.
The display in Figure 16 on page 41 shows what this route entry might look like.
You do not need an entry pointing to your local network. You do need a default entry pointing to the IP router. The default route tells the system to route any traffic for locations that are not on your local LAN to the IP router. The router handles getting the packets to their destination.
__ a. Define a default route
Return to the Configure TCP/IP menu and select Option 2 – Work with TCP/IP Routes. A display that is similar to Figure 16 is shown. (If a route has not yet been added, the list is empty.)
__ b. Enter a1on the Opt field to add a route.
v The Route Destination is*DFTROUTE v The Subnet Mask is*NONE
v The Type of Service is*NORMAL
v The Next Hop is the address of the first IP router your traffic must go through to get to the other TCP/IP networks.
__ c. For the vast majority of installations, this is all that is needed. If, however, you have defined multiple interfaces, you may need to add explicit entries for certain networks that you want to reach. It is possible to have multiple default routes, but it is not recommended.
__ 4. Define a local domain name and host name.
__ a. Select Option 12, Change TCP/IP domain information, from the Configure TCP/IP menu. An example of the display is shown in Figure 17 on page 42 . Changes that you make take effect immediately.
Work with TCP/IP Routes
System: SYS1 Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display
Type
Route Subnet of Next
Opt Destination Mask Service Hop
1 ______________ ______________ __________ _________
_ *DFTROUTE *NONE *NORMAL 199.5.83.29
Figure 16. Work with TCP/IP Routes display
Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System 41
A domain name identifies a group of systems to which your system belongs.
The group of systems is called a domain. Remote servers use the domain name to identify the local host to other systems. Domain names consist of labels that are separated by periods (for example,DOMAINXYZ.ACME.COM).
The domain name has two parts, the local domain name and the local host name. The combination of the local domain name and the local host name becomes the fully qualified domain name by which your host is known to the network. (The fully qualified domain name is often referred to as the host name.
Host names are discussed in more detail in step 5 on page 43). You can choose any values for these names, but we suggest that you use the AS/400 system name for the local host name (for example,SYS1). Your local domain name should be descriptive of your organization. The last portion of the local domain name should follow Internet conventions; that is, useCOMfor commercial enterprises,GOVfor government organizations, andEDUfor educational institutions.
For additional information, see the topic on″Domain Naming Conventions″in the bookTCP/IP Configuration and Reference, SC41-5420-02.
To communicate with another system in a TCP/IP network, you need to know the IP address of that system within your network. Although it is certainly possible to work directly with the IP address of a system, in practice this is seldom done.
Remembering and working with IP addresses is both tedious and error-prone.
Therefore, most network administrators assign each system a host name that is easier for people to remember and work with.
Each computer system in a TCP/IP network is called a host. The association between host name and the IP address of that system is stored in a host table.
You can configure your AS/400 to use a host table that is kept either in its own storage or on another system in your network. When the table is on your AS/400, it is referred to as a local host table, for obvious reasons. If a host table is located on a remote system, that system is referred to as a remote name server.
Change TCP/IP Domain (CHGTCPDMN) Type choices, press Enter.
Host name . . . . *SAME Domain name . . . . *SAME
Host name search priority . . . *SAME *REMOTE, *LOCAL, *SAME Internet address . . . . *SAME
*SAME
*SAME
Figure 17. Change Local Domain and Host Names Display
You can set up AS/400 to use both a local host table and one to three remote name servers. They are not mutually exclusive. However, most TCP/IP networks will use only one approach or the other to look up symbolic names. The
advantages and disadvantages of each approach will be mentioned when we discuss how to set up each in the steps below.
However you choose to organize the information in the host tables in your network, you should ensure that your AS/400 can always find an entry for the name you gave it when you defined the local domain and host name. Using our example data, our AS/400 should be able to find out that the host name SYS1.DOMAINXYZ.ACME.COM (defined in step 4 on page 41) is for the IP address 199.5.83.158 (defined in step 2 on page 38). Also remember that both the host names and IP addresses must be unique in the network for the network to function correctly.
__ 5. Build a Local Host Table
__ a. From the Configure TCP/IP menu, select option 10.
__ b. Enter a10in the Opt field to show the Add TCP/IP Host Table Entries display, as shown in Figure 18.
If you define a domain name (see step 4 on page 41), it is recommended that you also have an entry in your host table with both the long and short names for your host. If the system name isMOLLYand the domain name is DOMAINXYZ.ACME.COM, the short name would beMOLLYand the long name would beMOLLY.DOMAINXYZ.ACME.COMas shown in Figure 18.
Note: You need to Enter a plus sign (+) in the appropriate field to get additional space for adding the short name.
Once you have added your long and short host names, the Work with Host Table Entries display should appear like Figure 19 on page 44.
Add TCP/IP Host Table Entry (ADDTCPHTE) Type choices, press Enter.
Internet address . . . > '199.5.83.205 ' Host names:
Name . . . > MOLLY.DOMAINXYZ.ACME.COM
Name . . . > MOLLY
+ for more values _
Text 'description' . . . > 'Molly's PC'
Figure 18. Work with Host Table Entries (Add Option)
Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System 43
Each address entry can have multiple names assigned to it.
__ 6. Identify a remote name server
A domain name server that is also called a remote name server, maintains the host table for an entire TCP/IP domain. The advantage of using a domain name server in your TCP/IP network is that it frees each individual host from having to maintain its own local host table. When a system is added or removed from your network, only the host table on the domain name server system needs to be updated.
The disadvantage of a name server is that it requires more effort and experience to define and administer than a local host table. It also requires that your network contains a system that can provide this function (Your AS/400 cannot function as a domain name server).
In general, small networks with only a few systems will use local host tables.
Larger networks with many hosts use one or more domain name servers. You can also configure your AS/400 to use both a remote name server and your local host table. They are not mutually exclusive.
You can specify whether a remote name server or your local host table is searched first. If you configure TCP/IP on your AS/400 to use a remote name server and to search it first, the AS/400 system sends a request to the remote name server each time that it wants to know the IP address associated with a host name.
If a host name is specified without a domain, the AS/400 system adds the local domain name portion of the domain name (that you provided in step 4 on page 41 ) to the host name before sending a request to the remote name server.
If the remote name server does not respond or does not find an IP address for a name, your AS/400 looks at its own local host table to resolve the IP address.
If you cannot change the configuration of your name server, you can also change the value for the Searched first parameter to *LOCAL and create a local host table entry for the fully qualified domain name of your AS/400. Doing this causes the value in the local host table to be used first. The remote name server is only searched if the local host table does not return a value when searched first.
Work with TCP/IP Host Table Entries
System: SYS1 Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 7=Rename Internet Host
Figure 19. Work with Host Table Entries - After Adding Names
__ 7. Start TCP/IP.
Check to see if the line controllers are varied on.
__ a. TypeWRKCFGSTS *LINon the command line __ b. Check your line to see if it isVaried On.
__ c. If it is not, vary it off and vary it on.
Before any TCP/IP services are available, TCP/IP processing must be started.
__ a. TypeGO TCPADMand select Option 3. Option 3 starts TCP/IP processing, starts the interfaces (that have been configured to start automatically), and starts the TCP/IP server jobs.
Note: You may wonder why we did not discuss any of the steps that are associated with Option 2, Configure TCP/IP applications. The goal of this book is to get you set up with a minimum of configuration fuss. The default values for the TCP/IP applications are enough to get you started.
__ b. Allow a few moments for TCP/IP to start, then select Option 20, Work with TCP/IP jobs in QSYSWRK subsystem from the TCP/IP Administration menu.
The job QTCPIP should be in the list (along with jobs for FTP, POP, TELNET, LPD, and SMTP). After the QTCPIP job is started, you can proceed with step 8 on page 46.
Messages indicating that TCP/IP has been started are sent to the TCP (QTCP) and system operator (QSYSOPR) message queues. To check for the successful start of TCP/IP, enter either of these Display Message (DSPMSG) commands:
DSPMSG QSYSOPR DSPMSG QTCP
Note:
You must start TCP/IP whenever you end all subsystems or you IPL your system. To have TCP/IP start automatically after an IPL, you need to change the IPL start-up program. For information on how to do this, see the topic on″Changing the IPL Start-Up Program″in the bookWork Management, SC41-5306-02 .
If you change configurations (TCP or IPX)
You need to end host servers with (ENDHOSTSVR *ALL) and restart them if you change your configuration.
Host server jobs that provide TCP/IP socket communications support must be started before you can connect a PC using the Client Access connections
Host server jobs that provide TCP/IP socket communications support must be started before you can connect a PC using the Client Access connections