Troubleshooting
Problem
This document provides a thorough explanation of how TCP/IP should be configured on your IBM iSeries family of servers system.
Resolving The Problem
What is TCP/IP and do I need it?
It is nearly impossible to pick up a newspaper, technical journal, or magazine without reading something about the Internet. References to the Internet and to the information superhighway have become part of our daily lives. What does all this have to do with TCP/IP? Simply stated, the communications backbone for the Internet is TCP/IP.
In slightly more technical terms, TCP/IP stands for Transmission Control Protocol/Internet Protocol. TCP/IP is a set of rules that allow computers with different hardware and software to communicate across a network (see Note below). As computer networks become more and more popular, it becomes critical to be able to freely exchange information between computers of all types. Users of UNIX workstations want to share files with their peers who use an OS/2 workstation. Teams separated by thousands of miles want to exchange e-mail to coordinate their projects. Information System administrators want to provide efficient means of printing files for users connected to a LAN. At the same time, they want to ensure that their business assets are protected, and that their transactions across the Internet are secure. All these tasks can be accomplished using TCP/IP.
Note: For a more detailed discussion of TCP/IP, see the book TCP/IP Configuration and Reference, SC41-5420.
What can I do with TCP/IP?
After you have installed and set up TCP/IP on your IBM OS/400 or IBM i5/OS system, here are some of the applications you can run:
The following is a list of TCP/IP functions provided with the OS/400 operating system:
What do I need to know before I can set up TCP/IP?
Before you start setting up TCP/IP, you need to be aware of the software requirements, have a basic understanding of TCP/IP addressing, be familiar with the configuration and administration tasks, and gather some information about your system.
What needs to be installed before I can use TCP/IP?
The basic TCP/IP communications function is included with the OS/400 operating system. However, if you are interested in using any of the applications mentioned in the previous chapter (TELNET, FTP, and so forth), you must ensure that the TCP/IP Connectivity Utilities for iSeries family system licensed program (LP) is installed on your system. This LP is included without charge with the OS/400 operating system; however, it must be installed separately.
To see if the TCP/IP LP is already installed, enter the Go Licensed Program (GO LICPGM) command and then select Option 10 to display the installed licensed programs. Here is an example of how the LP you are looking for is displayed in Version 7 Release 2 Modification 0 (V7R2M0).
Note: If your system is not running V7R2, the LP may have a different program number. However, the program number for this LP will always end with TC1.
If the TCP/IP Connectivity Utilities LP is not installed on your system, use Option 11 on the Work with Licensed Programs (GO LICPGM) menu to install it.
What do I need to know about TCP/IP addressing?
One of the keys to success in a TCP/IP network is that each system in the network must have its own unique address. This address is known as the Internet Protocol address (or IP address) of your system. An IP address consists of four numbers (0-255) separated by periods. For example, 128.1.15.95 is a valid format for an IP address.
An additional part of TCP/IP addressing is the subnet mask. The subnet mask allows you to divide a single network into smaller networks called subnetworks.
For the configuration steps in the next chapter, we assume that the IP address and subnet mask for your system have been assigned by your network administrator. If you are the network administrator and you need help defining the addressing scheme for your network, this book is only a starting point. A complete discussion of TCP/IP addressing and subnet masks is beyond the scope of this book. An introduction to TCP/IP addressing and subnet masks is provided in the TCP/IP Configuration and Reference manual, SC41-5420. You can also contact your IBM representative for information on classes or workshops that may be available.
How do I administer and configure TCP/IP?
Two menus of tasks are useful in administering and configuring TCP/IP. These menus are used extensively throughout "How do I set up TCP/IP?". It is not necessary to understand the details of each menu option, but it is helpful to become familiar with them now. See the online help for additional information about each menu option. These menus are:
The TCP/IP Administration Menu
The TCP/IP Administration (TCPADM) menu (Figure 1 ) provides easy access to common functions associated with administering TCP/IP. This menu is a starting point for the configuration tasks. To reach this menu, enter the GO TCPADM (Go TCP/IP Administration) command.
Figure 1. TCP/IP Administration Menu
The Configure TCP/IP Menu
All the tasks necessary to set up your OS/400 or i5/OS to communicate with other systems in a TCP/IP network can be performed from the Configure TCP/IP (CFGTCP) menu (Figure 2). To get to this menu, either select option 1 on the TCPADM menu or enter the CFGTCP (Configure TCP/IP) command.
Usually only five of the options on the Configure TCP/IP menu are used. A common method is to use options 1, 2, 10, 12 and 13 as the steps to configure TCP/IP on OS/400 or i5/OS. We cover each of these steps in more detail in the next section.
Figure 2. Configure TCP/IP Menu
What information is needed about my system and network?
Some information is needed about your OS/400 or i5/OS and the TCP/IP network you are attaching to before you can set up TCP/IP. Table 1 is provided to help you collect and organize this information.
If you are new to TCP/IP or to the OS/400 or i5/OS system, you may not know all of the items in the table. There may also be terms used in the table that you are not familiar with. In these cases, read "How do I set up TCP/IP?" to become familiar with the concepts and return to this table after you have collected the necessary information.
How do I set up TCP/IP?
This chapter walks you through the steps that are necessary to set up TCP/IP for the first time. The steps in the following list may use terms that you are not familiar with. The terms and how they relate to TCP/IP are described in the associated step. Important information about how each step is used in the overall operation of TCP/IP is discussed in each step. For these reasons, it is suggested that you read the entire document before actually performing the steps.
Step 1. Identify your iSeries® family system to the local network.
In this step we will:
First, some background information.
The communications objects for iSeries family system TCP/IP are the line descriptions, the network controller descriptions, and the network device descriptions. In this context, the line is the physical line that is used to transfer data in a network. Of these three communications objects, the only one discussed here is the line description. We will let the system automatically create the network controller description and the network device description.
TCP/IP can communicate over a variety of physical line types. The command used to define the characteristics of the physical line connection depends on the type of communications adapter installed in your system as shown in Table 2.
Table 2 lists just two of the communications adapters that are supported. For more information, see the topic on "Configuring a Physical Line for TCP/IP Communication" in the book TCP/IP Configuration and Reference, SC41-5420. For more information on creating line descriptions, see LAN and Frame-Relay Support, SC41-5404, and Communications Configuration, SC41-5401.
Use the steps that follow to connect any of the communications adapters listed in Table 2 to the network. This example shows the steps for an Ethernet adapter. The steps for a token-ring adapter are similar.
Step 1a. Determine if a line description already exists.
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. TCP/IP does not need a separate physical line.
To determine if a line description already exists, follow these steps:
Figure 3. Work with Communication Resources display
Figure 4. Work with Communication Descriptions display
If a line description already exists, the name of the line description is displayed as shown in Figure 4. This is the information you need to continue with TCP/IP configuration. Continue with "Step 1c. Define a TCP/IP interface".
If a line description does not exist, you must create one by continuing with step 1b.
Step 1b. If a line description does not already exist, create one.
Enter 1 on the Opt field on the Work with Configuration Descriptions display (Figure 4) or use the appropriate command from Table 2 to create a line description for your communications adapter. The example in Figure 5 illustrates the steps for an Ethernet adapter.
In this example we simply gave the new line description the name ETHTCP. From Figure 3 in topic 3.1.1 we know that the Ethernet adapter has a resource name of LIN031. This is the name that the system needs to associate the line description with the communications adapter.
Figure 5. Creating an Ethernet line description. Display 1 of 3
Figure 6. Creating an Ethernet line description. Display 2 of 3
You can accept the default values for the items in Figure 5 and Figure 6. However, on the third display (Figure 7 ) change the default setting for Autocreate controller from *NO to *YES. Although this is not essential for TCP/IP, it is a good practice when creating line descriptions because it allows the system to handle some of the configuration tasks.
Figure 7. Creating an Ethernet line description. Display 3 of 3
After you have filled in the information, press Enter. Watch for the information message at the bottom of the display that indicates that the line description was created.
Step 1c. Define a TCP/IP interface
An interface identifies a direct connection of your iSeries family system to a network using TCP/IP. The network is identified by providing the name of the line description which we determined in the preceding steps. Because the interface is internal to your system and cannot be touched or held in your hands, it is known as a logical interface. It is the logical interface that defines an IP address associated with a line description on your iSeries family system.
Each line description associated with a physical communications line can have several interfaces with different IP addresses. These addresses are the addresses you are assigning to this iSeries family system. They are not the addresses for any other systems in the network. In most cases, you only need one IP address for your system. For information about assigning multiple IP addresses to your system, see the topic on the "Multihoming Function" in the book TCP/IP Configuration and Reference, SC41-5420.
Figure 8. Work with TCP/IP Interfaces display
Figure 9. Add TCP/IP Interface display
Step 2. Define a default TCP/IP route
A route provides the connection between your system and the external network. It is the route that allows your system to communicate with other systems on other networks.
If you will be using an IP router to access resources beyond your local LAN, you will need to set at least one route entry for a default route. The display in Figure 10 shows what this route entry might look like. We do not need an entry pointing to our local network. But, we 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 the chore of getting the packets to their destination after that.
Figure 10. Work with TCP/IP Routes display
Step 3. Define a host name and domain name
A domain name identifies your system within a group of systems. The group of systems is called a domain. The domain name is used by remote servers to identify the local host to other systems. The domain name is essential for SMTP operation and optional for LPR. 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 4.) You can choose any values for these names, but we suggest that you use the iSeries family system system name for the local host name (for example, GENSYS00). Your local domain name should be descriptive of your organization. The last portion of the local domain name should follow Internet conventions; that is, use COM for commercial enterprises, GOV for government organizations, and EDU for educational institutions. ACME.COM is our primary domain name.
Figure 11. Change TCP/IP Domain Display
For additional information, see the topic on "Domain Naming Conventions" in the book TCP/IP Configuration and Reference, SC41-5420.
Step 4. Identify the names of the systems in your network.
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 network is called a host. The association between host name and the IP address of that system is stored in a host table. Your iSeries family system can be configured to use a host table that is kept in its own storage or on another system in your network. When the table is on your iSeries family system, 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.
You can set up your iSeries family system 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 iSeries family system 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 iSeries family system should be able to find out that the host name GENSYS00.DOMAINXYZ.ACME.COM (defined in "Step 3. Define a local domain name and host name") is for the IP address 199.5.83.158 (defined in step "Step 1c. Define a TCP/IP interface"). Also remember that both the host names and IP addresses must be unique in the network for the network to function correctly.
Step 4a. Build a local host table
A local host table is typically used to associate symbolic names of systems with IP addresses for small networks that have only a few hosts on them. The main advantage of a local host table is that, as the name implies, it is stored on your iSeries family system. Therefore, it is always accessible and can be quickly searched. The main disadvantage is that whenever an entry in the table is changed, the change must be copied to all the other host tables on the systems in your network.
Each IP address in an iSeries family system local host table can be associated with from one to four host names. We refer to this association of an IP address with a set of names as a host table entry.
Figure 12. Work with Host Table Entries - Before Adding Names
Note: Just as iSeries family system TCP/IP automatically creates a LOOPBACK interface, it also automatically adds an entry to your local host table to associate the IP address 127.0.0.1 with the host names LOOPBACK and LOCALHOST.
Figure 13. Work with Host Table Entries (Add Option)
If you define a domain name (see "Step 3. Define a local domain name and host name"), it is recommended that you also have an entry in your host table with both the long and short names for your iSeries family system. If the system name is GENSYS00 and the domain name is DOMAINXYZ.ACME.COM, the short name is GENSYS00 and the long name is GENSYS00.DOMAINXYZ.ACME.COM as shown in Figure 13.
Note: Type a plus sign (+) in the appropriate field to get additional space for adding the short name.
Once the long and short host names are added , the Work with Host Table Entries display should appear like Figure 14.
Figure 14. Work with Host Table Entries - After Adding Names
Each address entry can have multiple names assigned to it.
Step 4b. Identify a remote name server
Note: Option 13 from the CFGTCP menu does not exist at V4R3 and later; it is incorporated into CFGTCP, Option 12.
A domain name server, 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 contain a system that can provide this function (your iSeries family system 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 will use one or more domain name servers. You can also configure your iSeries family system 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 iSeries family system to use a remote name server and to search it first, the iSeries family system system sends a request to the remote name server each time that it wants to know the Internet address associated with a host name.
If a host name is specified without a domain, the iSeries family system system adds the local domain name portion of the domain name (that you provided in "Step 3. Define a local domain name and host name") to the host name before sending the request. If the remote name server does not respond or does not find an Internet address for a name, your iSeries family system looks at its own local host table to resolve the Internet address.
Note: The default value of *REMOTE for the Searched first parameter should work in the majority of cases. If you are using a name server and you experience problems because a TCP/IP application is not able to resolve the host name of your iSeries family system, check to make sure the name server is correctly configured to return the fully qualified domain name for your iSeries family system.
If, for some reason, you cannot change the configuration of your name server, you can also change the value for the Searched first parameter in Figure 15 to *LOCAL and create a local host table entry for the fully qualified domain name of your iSeries family system. 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.
Figure 15. Change Remote Name Server Display
You can configure up to three remote name servers. However, most installations have only one name server.
Step 5. Start TCP/IP
Before any TCP/IP services are available, TCP/IP processing must be started.
Step 6. Verify that TCP/IP works
To verify the TCP/IP connection from your iSeries family system to the network, select option 8 from the TCP/IP Administration menu (GO TCPADM) or use the PING (or VFYTCPCNN) command.
Figure 16. Verifying TCP/IP Connection - LOOPBACK
Figure 17. Verifying TCP/IP Connection - Internet Address
Figure 18. Verifying TCP/IP Connection - Host Name
TCP/IP sends data to the Ethernet adapter, instructing the adapter to send the data to its own Ethernet address. The data should then be returned to TCP/IP.
Figure 19. Verifying TCP/IP Connection - Remote System
If the PING operation is successful, the job log should contain messages similar to the ones shown in Figure 20. (To view the messages, use the Display Job Log (DSPJOBLOG) command, press F10 to display detailed messages, and then Page Up.)
Figure 20. Successful PING Messages
If the PING operation is unsuccessful, you should see messages similar to the ones shown in Figure 21.
Figure 21. Unsuccessful PING Messages
If this occurs, check your configuration steps. In addition, verify that the configuration at the remote system is correct and that the remote system is powered up.
For more details about PING (VFYTCPCNN), see the topic on "Verifying TCP/IP Connections" in the TCP/IP Configuration and Reference manual, SC41-5420.
You have just completed the iSeries family system TCP/IP configuration for a single-network example. The system is ready to run applications like FTP, LPR, TELNET, or SMTP and other user-written applications.
It is nearly impossible to pick up a newspaper, technical journal, or magazine without reading something about the Internet. References to the Internet and to the information superhighway have become part of our daily lives. What does all this have to do with TCP/IP? Simply stated, the communications backbone for the Internet is TCP/IP.
In slightly more technical terms, TCP/IP stands for Transmission Control Protocol/Internet Protocol. TCP/IP is a set of rules that allow computers with different hardware and software to communicate across a network (see Note below). As computer networks become more and more popular, it becomes critical to be able to freely exchange information between computers of all types. Users of UNIX workstations want to share files with their peers who use an OS/2 workstation. Teams separated by thousands of miles want to exchange e-mail to coordinate their projects. Information System administrators want to provide efficient means of printing files for users connected to a LAN. At the same time, they want to ensure that their business assets are protected, and that their transactions across the Internet are secure. All these tasks can be accomplished using TCP/IP.
Note: For a more detailed discussion of TCP/IP, see the book TCP/IP Configuration and Reference, SC41-5420.
What can I do with TCP/IP?
After you have installed and set up TCP/IP on your IBM OS/400 or IBM i5/OS system, here are some of the applications you can run:
o | Telnet (TELetypewriter NETwork) - Allows you to log on to another computer system from your system. |
o | FTP (File Transfer Protocol) - Allows you to exchange files with other computers. |
o | SMTP (Simple Mail Transfer Protocol) - Allows you to send e-mail. |
o | POP (Post Office Protocol) mail server - Allows you to exchange mail (including video, image, audio, or binary files) with any clients that support the POP Version 3 mail interface. |
o | REXEC (Remote EXECution) - Allows you to submit system commands to a remote OS/400 or i5/OS system. |
o | LPR (Line Printer Requester) - Allows you to print files on a remote system or a network-attached printer. |
o | LPD (Line Printer Daemon) - Allows remote systems to print files on your OS/400 or i5/OS system. |
o | SNMP (Simple Network Management Protocol) - Allows you to manage an Internet environment. |
o | WSG (Workstation Gateway) - Allows you to sign on to the OS/400 or i5/OS system over an Internet, using a Web browser at your workstation. |
o | Internet Connection Server for iSeries family system (also known as HTTP server) - Allows you to use the OS/400 or i5/OS system to serve hypertext information to standard Web browsers across both the Internet and intranets. |
o | BOOTP (Bootstrap Protocol) - Allows a client workstation to request the file containing initial code from a server on the network. |
o | RouteD (Route Daemon) - Provides support for Routing Information Protocol (RIP). RIP improves performance and reliability in the routing of IP data packets. |
o | SLIP (Serial Line Internet Protocol) - Allows remote systems to dial into the OS/400 or i5/OS system or OS/400 or i5/OS system to dial into remote systems over a telephone line using a modem. |
o | TFTP (Trivial File Transfer Protocol) - Provides basic file transfers to and from a remote server. |
Before you start setting up TCP/IP, you need to be aware of the software requirements, have a basic understanding of TCP/IP addressing, be familiar with the configuration and administration tasks, and gather some information about your system.
What needs to be installed before I can use TCP/IP?
The basic TCP/IP communications function is included with the OS/400 operating system. However, if you are interested in using any of the applications mentioned in the previous chapter (TELNET, FTP, and so forth), you must ensure that the TCP/IP Connectivity Utilities for iSeries family system licensed program (LP) is installed on your system. This LP is included without charge with the OS/400 operating system; however, it must be installed separately.
To see if the TCP/IP LP is already installed, enter the Go Licensed Program (GO LICPGM) command and then select Option 10 to display the installed licensed programs. Here is an example of how the LP you are looking for is displayed in Version 7 Release 2 Modification 0 (V7R2M0).
Display Installed Licensed Programs System: SYSNAM01 Licensed Installed Program Description Release 5770TC1 TCP/IP Connectivity Utilities/400 V7R2M0 |
Note: If your system is not running V7R2, the LP may have a different program number. However, the program number for this LP will always end with TC1.
If the TCP/IP Connectivity Utilities LP is not installed on your system, use Option 11 on the Work with Licensed Programs (GO LICPGM) menu to install it.
What do I need to know about TCP/IP addressing?
One of the keys to success in a TCP/IP network is that each system in the network must have its own unique address. This address is known as the Internet Protocol address (or IP address) of your system. An IP address consists of four numbers (0-255) separated by periods. For example, 128.1.15.95 is a valid format for an IP address.
An additional part of TCP/IP addressing is the subnet mask. The subnet mask allows you to divide a single network into smaller networks called subnetworks.
For the configuration steps in the next chapter, we assume that the IP address and subnet mask for your system have been assigned by your network administrator. If you are the network administrator and you need help defining the addressing scheme for your network, this book is only a starting point. A complete discussion of TCP/IP addressing and subnet masks is beyond the scope of this book. An introduction to TCP/IP addressing and subnet masks is provided in the TCP/IP Configuration and Reference manual, SC41-5420. You can also contact your IBM representative for information on classes or workshops that may be available.
How do I administer and configure TCP/IP?
Two menus of tasks are useful in administering and configuring TCP/IP. These menus are used extensively throughout "How do I set up TCP/IP?". It is not necessary to understand the details of each menu option, but it is helpful to become familiar with them now. See the online help for additional information about each menu option. These menus are:
o | TCP/IP Administration |
o | Configure TCP/IP |
The TCP/IP Administration (TCPADM) menu (Figure 1 ) provides easy access to common functions associated with administering TCP/IP. This menu is a starting point for the configuration tasks. To reach this menu, enter the GO TCPADM (Go TCP/IP Administration) command.
TCPADM TCP/IP Administration System: SYSNAM01 Select one of the following: 1. Configure TCP/IP 2. Configure TCP/IP applications 3. Start TCP/IP 4. End TCP/IP 5. Start TCP/IP servers 6. End TCP/IP servers 7. Work with TCP/IP network status 8. Verify TCP/IP connection 9. Start TCP/IP FTP session 10. Start TCP/IP TELNET session 11. Send TCP/IP spooled file 20. Work with TCP/IP jobs in QSYSWRK subsystem Selection or command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel |
The Configure TCP/IP Menu
All the tasks necessary to set up your OS/400 or i5/OS to communicate with other systems in a TCP/IP network can be performed from the Configure TCP/IP (CFGTCP) menu (Figure 2). To get to this menu, either select option 1 on the TCPADM menu or enter the CFGTCP (Configure TCP/IP) command.
Usually only five of the options on the Configure TCP/IP menu are used. A common method is to use options 1, 2, 10, 12 and 13 as the steps to configure TCP/IP on OS/400 or i5/OS. We cover each of these steps in more detail in the next section.
CFGTCP Configure TCP/IP System: SYSNAM01 Select one of the following: 1. Work with TCP/IP interfaces 2. Work with TCP/IP routes 3. Change TCP/IP attributes 4. Work with TCP/IP port restrictions 5. Work with TCP/IP remote system information 10. Work with TCP/IP host table entries 11. Merge TCP/IP host table 12. Change TCP/IP domain information 13. Change remote name server 20. Configure TCP/IP applications 21. Configure related tables 22. Configure point-to-point TCP/IP Selection or command ===> F3=Exit F4=Prompt F9=Retrieve F12=Cancel |
What information is needed about my system and network?
Some information is needed about your OS/400 or i5/OS and the TCP/IP network you are attaching to before you can set up TCP/IP. Table 1 is provided to help you collect and organize this information.
If you are new to TCP/IP or to the OS/400 or i5/OS system, you may not know all of the items in the table. There may also be terms used in the table that you are not familiar with. In these cases, read "How do I set up TCP/IP?" to become familiar with the concepts and return to this table after you have collected the necessary information.
Important: To perform any communications configuration tasks on your OS/400 or i5/OS, you must have the special authority of *IOSYSCFG (I/O System Configuration) defined in your user profile. Verify the characteristics of your user profile using the Display User Profile (DSPUSRPRF) command. Contact your system administrator or security administrator if you do not have *IOSYSCFG special authority. |
________________________________________________________________________
| Table 1. Information required to set up TCP/IP |
|_________________ __________________ ___________________________________|
| Required | | |
| information | For your system | Notes |
|_________________|__________________|___________________________________|
| Resource name | ______________ | Example: CMN04 |
| of your | | It is assumed that a communications|
| communications | | adapter has already been installed |
| adapter | | in your system. |
| | | . |
|_________________|__________________|___________________________________|
| Line | ______________ | Example: ETHTCP |
| description for | | |
| your | | If you don't know, see "Step 1. |
| communications | | Identify your iSeries to the local |
| line | | network". |
|_________________|__________________|___________________________________|
| IP address for | _______________ | Example: 199.5.83.158 |
| your iSeries | | |
|_________________|__________________|___________________________________|
| Subnet mask for | ______________ | Example: 255.255.255.0 |
| your iSeries | | |
|_________________|__________________|___________________________________|
| Next hop | ______________ | Example: 199.5.83.129 |
| address | | |
| | | The next hop address is the |
| | | address of the IP router (if any) |
| | | that routes network traffic from |
| | | your local LAN to other networks |
| | | within and outside of your |
| | | organization. For more |
| | | information, see "Step 2. Define |
| | | a default TCP/IP route". |
|_________________|__________________|___________________________________|
| Host name and | ______________ | Example: |
| domain name for | | GENSYS00.DOMAINXYZ.ACME.COM |
| your system | | |
| | | For more information, see "Step |
| | | 3. Define a local domain name and |
| | | host name". |
|_________________|__________________|___________________________________|
| IP address for | ______________ | Example: 199.4.191.76 |
| domain name | | |
| server | | The domain name server maintains |
| | | the host table for an entire |
| | | TCP/IP domain. For additional |
| | | information, see "Step 4b. |
| | | Identify a remote name server". |
|_________________|__________________|___________________________________|
How do I set up TCP/IP?
This chapter walks you through the steps that are necessary to set up TCP/IP for the first time. The steps in the following list may use terms that you are not familiar with. The terms and how they relate to TCP/IP are described in the associated step. Important information about how each step is used in the overall operation of TCP/IP is discussed in each step. For these reasons, it is suggested that you read the entire document before actually performing the steps.
1 | Identify your OS/400 or i5/OS to the local network (the network that your OS/400 is directly connected to). a. Determine if a line description already exists. b. If a line description does not already exist, create one. c. Define a TCP/IP interface to give your OS/400 or i5/OS an IP address. |
2 | Define a TCP/IP route. This allows your OS/400 or i5/OS to communicate with systems on remote TCP/IP networks (networks that your OS/400 or i5/OS is not directly connected to). |
3 | Define a local domain name and host name. This assigns a name to your system. |
4 | Identify the names of the systems in your network. a. Build a local host table. b. Identify a remote name server. |
5 | Start TCP/IP. |
6 | Verify that TCP/IP works. |
In this step we will:
1 | Determine if a line description that can be used by TCP/IP has already been created. |
2 | If not, create a line description. |
3 | Define a TCP/IP interface to give your iSeries family system an IP address. |
The communications objects for iSeries family system TCP/IP are the line descriptions, the network controller descriptions, and the network device descriptions. In this context, the line is the physical line that is used to transfer data in a network. Of these three communications objects, the only one discussed here is the line description. We will let the system automatically create the network controller description and the network device description.
TCP/IP can communicate over a variety of physical line types. The command used to define the characteristics of the physical line connection depends on the type of communications adapter installed in your system as shown in Table 2.
________________________________________________________________________
| Table 2. Sample of Communications Adapters Supported by TCP/IP |
|_________________ ______________________________________________________|
| Communications | Line description configuration command |
| adapter | |
|_________________|______________________________________________________|
| Ethernet | Create Line Description (Ethernet) (CRTLINETH) |
|_________________|______________________________________________________|
Table 2 lists just two of the communications adapters that are supported. For more information, see the topic on "Configuring a Physical Line for TCP/IP Communication" in the book TCP/IP Configuration and Reference, SC41-5420. For more information on creating line descriptions, see LAN and Frame-Relay Support, SC41-5404, and Communications Configuration, SC41-5401.
Use the steps that follow to connect any of the communications adapters listed in Table 2 to the network. This example shows the steps for an Ethernet adapter. The steps for a token-ring adapter are similar.
Step 1a. Determine if a line description already exists.
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. TCP/IP does not need a separate physical line.
To determine if a line description already exists, follow these steps:
1 | Enter GO HARDWARE to get the Hardware Resources menu. |
2 | Select Option 1, Work with communication resources to show a display similar to Figure 3. |
Work with Communication Resources System: GENSYS00 Type options, press Enter. 2=Edit 4=Remove 5=Work with configuration descriptions Opt Resource Type Text _ CC01 2625 Comm Processor _ LIN03 2625 LAN Adapter 5 CMN04 2625 Ethernet Port |
Figure 3. Work with Communication Resources display
In this example, there is already one Ethernet adapter installed with the resource name of LIN031. To determine if a line description exists for this adapter, use Option 5, Work with configuration descriptions, as shown in Figure 3 to show a display similar to Figure 4. |
Work with Configuration Descriptions System: GENSYS00 Resource name . . . . . . . : CMN04 Text . . . . . . . . . . . . : Ethernet Port Type options, press Enter. 1=Create 5=Work with description 8=Work with configuration status Opt Description _ __________ _ ETHTCP |
Figure 4. Work with Communication Descriptions display
If a line description already exists, the name of the line description is displayed as shown in Figure 4. This is the information you need to continue with TCP/IP configuration. Continue with "Step 1c. Define a TCP/IP interface".
If a line description does not exist, you must create one by continuing with step 1b.
Step 1b. If a line description does not already exist, create one.
Enter 1 on the Opt field on the Work with Configuration Descriptions display (Figure 4) or use the appropriate command from Table 2 to create a line description for your communications adapter. The example in Figure 5 illustrates the steps for an Ethernet adapter.
In this example we simply gave the new line description the name ETHTCP. From Figure 3 in topic 3.1.1 we know that the Ethernet adapter has a resource name of LIN031. This is the name that the system needs to associate the line description with the communications adapter.
Create Line Desc (Ethernet) (CRTLINETH) Type choices, press Enter. Line description . . . . . . . . > ETHTCP Name Resource name . . . . . . . . . > CMN04 Name, *NWID, *NWSD Online at IPL . . . . . . . . . *YES *YES, *NO Vary on wait . . . . . . . . . . *NOWAIT *NOWAIT, 15-180 (1 second) Local adapter address . . . . . *ADPT 020000000000-7EFFFFFFFFFF... Exchange identifier . . . . . . *SYSGEN 05600000-056FFFFF, *SYSGEN Ethernet standard . . . . . . . *ALL *ETHV2, *IEEE8023, *ALL SSAP list: Source service access point . *SYSGEN 02-FE, *SYSGEN SSAP maximum frame . . . . . . *MAXFRAME, 265-1496, 265... SSAP type . . . . . . . . . . *CALC, *NONSNA, *SNA, *HPR + for more values Text 'description' . . . . . . . *BLANK |
Figure 5. Creating an Ethernet line description. Display 1 of 3
Create Line Desc (Ethernet) (CRTLINETH) Type choices, press Enter. Additional Parameters Network controller . . . . . . . Name Group address . . . . . . . . . *NONE 010000000000-FDFFFFFFFFFF... + for more values Maximum controllers . . . . . . 40 1-256 Error threshold level . . . . . *OFF *OFF, *MIN, *MED, *MAX Link speed . . . . . . . . . . . 10M *MIN, 1200, 2400, 4800... Cost/connect time . . . . . . . 0 0-255 Cost/byte . . . . . . . . . . . 0 0-255 Security for line . . . . . . . *NONSECURE *NONSECURE, *PKTSWTNET... Propagation delay . . . . . . . *LAN *LAN, *MIN, *TELEPHONE... User-defined 1 . . . . . . . . . 128 0-255 User-defined 2 . . . . . . . . . 128 0-255 User-defined 3 . . . . . . . . . 128 0-255 |
Figure 6. Creating an Ethernet line description. Display 2 of 3
You can accept the default values for the items in Figure 5 and Figure 6. However, on the third display (Figure 7 ) change the default setting for Autocreate controller from *NO to *YES. Although this is not essential for TCP/IP, it is a good practice when creating line descriptions because it allows the system to handle some of the configuration tasks.
Create Line Desc (Ethernet) (CRTLINETH) Type choices, press Enter. Autocreate controller . . . . . *YES *YES, *NO Autodelete controller . . . . . 1440 1-10000 (minutes), *NONE Recovery limits: Count limit . . . . . . . . . 2 0-99, *SYSVAL Time interval . . . . . . . . 5 0-120 (minutes) Authority . . . . . . . . . . . *LIBCRTAUT Name, *LIBCRTAUT, *CHANGE... |
Figure 7. Creating an Ethernet line description. Display 3 of 3
After you have filled in the information, press Enter. Watch for the information message at the bottom of the display that indicates that the line description was created.
Step 1c. Define a TCP/IP interface
An interface identifies a direct connection of your iSeries family system to a network using TCP/IP. The network is identified by providing the name of the line description which we determined in the preceding steps. Because the interface is internal to your system and cannot be touched or held in your hands, it is known as a logical interface. It is the logical interface that defines an IP address associated with a line description on your iSeries family system.
Each line description associated with a physical communications line can have several interfaces with different IP addresses. These addresses are the addresses you are assigning to this iSeries family system. They are not the addresses for any other systems in the network. In most cases, you only need one IP address for your system. For information about assigning multiple IP addresses to your system, see the topic on the "Multihoming Function" in the book TCP/IP Configuration and Reference, SC41-5420.
1 | To define an interface, select Option 1, Work with TCP/IP interfaces, on the Configure TCP/IP menu (see Figure 2) to get the display in Figure 8. Note: The interface with a line type of *LOOPBACK is automatically created by TCP/IP. The LOOPBACK interface is provided to test TCP/IP or a TCP/IP application. Any data written to the LOOPBACK interface is echoed back to the same interface. LOOPBACK can never be used to reach a remote system. |
Work with TCP/IP Interfaces System: GENSYS00 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 8. Work with TCP/IP Interfaces display
2 | Type 1 under the Opt field to add an interface. See Figure 9. |
Add TCP/IP Interface (ADDTCPIFC) Type choices, press Enter. Internet address . . . . . . . . > '199.5.83.158' Line description . . . . . . . . ETHTCP Name, *LOOPBACK Subnet mask . . . . . . . . . . 255.255.255.0 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 9. Add TCP/IP Interface display
Reminder: A very common mistake is to define not only the IP address for your iSeries family system, but also the addresses of all the other systems you want your iSeries family system to communicate with. Do not do this! It will not work. An address that is defined as an interface is an IP address for this iSeries family system only. An interface should never be the address of another system in your network. In most cases, only one interface must be defined: the IP address that identifies your iSeries family system in your TCP/IP network. The steps to allow your iSeries family system to communicate with the other systems in your network are covered in "Step 2. Define a default TCP/IP route". |
3 | Type the Internet address, Line description, and Subnet mask with the information from Table 1. Accept the default values for the remaining items on this display. Press the Enter key, and check for messages to ensure that the interface was added. |
A route provides the connection between your system and the external network. It is the route that allows your system to communicate with other systems on other networks.
Are all the systems you want your iSeries family system to communicate with attached to the same local network that your iSeries family system is directly attached to? For example, are all of your systems on the same Ethernet local area network (LAN)? If they are, you can skip this section. Do not add any routing entries here. iSeries family system TCP/IP uses routing entries to determine how to communicate with systems that are not on the same local network as your iSeries family system. If you have only one network and you do not need to communicate outside that network, you do not need to define any routes. |
If you will be using an IP router to access resources beyond your local LAN, you will need to set at least one route entry for a default route. The display in Figure 10 shows what this route entry might look like. We do not need an entry pointing to our local network. But, we 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 the chore of getting the packets to their destination after that.
1 | To define a default route, return to the Configure TCP/IP menu and select Option 2. Work with TCP/IP Routes. A display similar to Figure 10 is shown. (If a route has not yet been added, the list will be empty.) |
Work with TCP/IP Routes System: GENSYS00 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 10. Work with TCP/IP Routes display
2 | Enter a 1 on the Opt field to add a route. o The Route Destination is *DFTROUTE o The Subnet Mask is *NONE o The Type of Service is *NORMAL o The Next Hop is the address of the first IP router your traffic must go through to get to the outside world (from Table 1). |
3 | 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. TCP/IP does not have selection processes to choose between these multiple defaults -- results may be unpredictable. |
Step 3. Define a host name and domain name
A domain name identifies your system within a group of systems. The group of systems is called a domain. The domain name is used by remote servers to identify the local host to other systems. The domain name is essential for SMTP operation and optional for LPR. 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 4.) You can choose any values for these names, but we suggest that you use the iSeries family system system name for the local host name (for example, GENSYS00). Your local domain name should be descriptive of your organization. The last portion of the local domain name should follow Internet conventions; that is, use COM for commercial enterprises, GOV for government organizations, and EDU for educational institutions. ACME.COM is our primary domain name.
1 | To define the local domain name and the local host name for your iSeries family system, select Option 12, Change TCP/IP domain information, from the Configure TCP/IP menu. An example of the display is shown in Figure 11. Changes that you make take effect immediately. |
Change TCP/IP Domain (CHGTCPDMN) Host name . . . GENSYS00 Domain name . . . . GENSYS00.DOMAINXYZ.ACME.COM |
Figure 11. Change TCP/IP Domain Display
For additional information, see the topic on "Domain Naming Conventions" in the book TCP/IP Configuration and Reference, SC41-5420.
Step 4. Identify the names of the systems in your network.
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 network is called a host. The association between host name and the IP address of that system is stored in a host table. Your iSeries family system can be configured to use a host table that is kept in its own storage or on another system in your network. When the table is on your iSeries family system, 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.
You can set up your iSeries family system 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 iSeries family system 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 iSeries family system should be able to find out that the host name GENSYS00.DOMAINXYZ.ACME.COM (defined in "Step 3. Define a local domain name and host name") is for the IP address 199.5.83.158 (defined in step "Step 1c. Define a TCP/IP interface"). Also remember that both the host names and IP addresses must be unique in the network for the network to function correctly.
Step 4a. Build a local host table
A local host table is typically used to associate symbolic names of systems with IP addresses for small networks that have only a few hosts on them. The main advantage of a local host table is that, as the name implies, it is stored on your iSeries family system. Therefore, it is always accessible and can be quickly searched. The main disadvantage is that whenever an entry in the table is changed, the change must be copied to all the other host tables on the systems in your network.
Each IP address in an iSeries family system local host table can be associated with from one to four host names. We refer to this association of an IP address with a set of names as a host table entry.
1 | To add a host table entry to the local host table on your iSeries family system, return to the Configure TCP/IP menu and select Option 10, Work with TCP/IP host table entries. The display in Figure 12 is shown. |
Work with TCP/IP Host Table Entries System: GENSYS00 Type options, press Enter. 1=Add 2=Change 4=Remove 5=Display 7=Rename Internet Host Opt Address Name 1 _ 127.0.0.1 LOOPBACK LOCALHOST |
Figure 12. Work with Host Table Entries - Before Adding Names
Note: Just as iSeries family system TCP/IP automatically creates a LOOPBACK interface, it also automatically adds an entry to your local host table to associate the IP address 127.0.0.1 with the host names LOOPBACK and LOCALHOST.
2 | Enter a 1 in the Opt field to show the Add TCP/IP Host Table Entry display, as shown in Figure 13. |
Add TCP/IP Host Table Entry (ADDTCPHTE) Type choices, press Enter. Internet address . . . . . . . . > '199.5.83.158 ' Host names: Name . . . . . . . . . . . . . > GENSYS00.DOMAINXYZ.ACME.COM Name . . . . . . . . . . . . . > GENSYS00 + for more values _ Text 'description' . . . . . . . > 'Fastpath Test System' |
Figure 13. Work with Host Table Entries (Add Option)
If you define a domain name (see "Step 3. Define a local domain name and host name"), it is recommended that you also have an entry in your host table with both the long and short names for your iSeries family system. If the system name is GENSYS00 and the domain name is DOMAINXYZ.ACME.COM, the short name is GENSYS00 and the long name is GENSYS00.DOMAINXYZ.ACME.COM as shown in Figure 13.
Note: Type a plus sign (+) in the appropriate field to get additional space for adding the short name.
Once the long and short host names are added , the Work with Host Table Entries display should appear like Figure 14.
Work with TCP/IP Host Table Entries System: GENSYS00 Type options, press Enter. 1=Add 2=Change 4=Remove 5=Display 7=Rename Internet Host Opt Address Name _ _ 199.5.83.158 GENSYS00.DOMAINXYZ.ACME.COM GENSYS00 _ 127.0.0.1 LOOPBACK |
Figure 14. Work with Host Table Entries - After Adding Names
Each address entry can have multiple names assigned to it.
Step 4b. Identify a remote name server
Note: Option 13 from the CFGTCP menu does not exist at V4R3 and later; it is incorporated into CFGTCP, Option 12.
A domain name server, 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 contain a system that can provide this function (your iSeries family system 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 will use one or more domain name servers. You can also configure your iSeries family system 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 iSeries family system to use a remote name server and to search it first, the iSeries family system system sends a request to the remote name server each time that it wants to know the Internet address associated with a host name.
If a host name is specified without a domain, the iSeries family system system adds the local domain name portion of the domain name (that you provided in "Step 3. Define a local domain name and host name") to the host name before sending the request. If the remote name server does not respond or does not find an Internet address for a name, your iSeries family system looks at its own local host table to resolve the Internet address.
Note: The default value of *REMOTE for the Searched first parameter should work in the majority of cases. If you are using a name server and you experience problems because a TCP/IP application is not able to resolve the host name of your iSeries family system, check to make sure the name server is correctly configured to return the fully qualified domain name for your iSeries family system.
If, for some reason, you cannot change the configuration of your name server, you can also change the value for the Searched first parameter in Figure 15 to *LOCAL and create a local host table entry for the fully qualified domain name of your iSeries family system. 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.
1 | To set or change the remote name server, select option 13 on the Configure TCP/IP menu. The Change Remote Name Server display is shown as in Figure 15. Changes that you make to the remote name server take effect immediately. |
Change Remote Name Server Type choices, press Enter. System: GENSYS00 Server address . . . . 199.4.191.76 Internet address + for more values . . Server protocol . . . . *UDP *UDP, *TCP Retries . . . . . . . . 2 1-99 Retry interval . . . . 2 1-99 (seconds) Searched first . . . . *REMOTE *REMOTE, *LOCAL |
Figure 15. Change Remote Name Server Display
You can configure up to three remote name servers. However, most installations have only one name server.
Step 5. Start TCP/IP
Before any TCP/IP services are available, TCP/IP processing must be started.
1 | To start TCP/IP, select option 3 from the TCP/IP Administration menu (GO TCPADM). 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 associated with Option 2, Configure TCP/IP applications. The goal of this document is to get you up and running with a minimum of configuration fuss. The default values for the TCP/IP applications are enough to get you started. |
2 | 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 (QTCPCTL and QTCPWRK at R610) should be in the list (along with other TCP/IP application server jobs such as FTP, TELNET, HTTP, SMTP). After the QTCPIP job is started, proceed with "Step 6. Verify that TCP/IP works". 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 one of the following Display Message (DSPMSG) commands: DSPMSG QSYSOPR DSPMSG QTCP |
Note: TCP/IP must be started whenever all subsystems are ended or you IPL your system. To have TCP/IP start automatically after an IPL, 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 Work Management guide, SC41-5306. KB doc N1014291 can be reviewed for the recommended method of starting TCP automatically. |
Step 6. Verify that TCP/IP works
To verify the TCP/IP connection from your iSeries family system to the network, select option 8 from the TCP/IP Administration menu (GO TCPADM) or use the PING (or VFYTCPCNN) command.
1 | To test your TCP/IP configuration without sending anything out of the Ethernet adapter, specify the special host name LOOPBACK (Figure 16). |
Verify TCP/IP Connection (VFYTCPCNN) Type choices, press Enter. Remote system . . . . . . . . . loopback |
Figure 16. Verifying TCP/IP Connection - LOOPBACK
2 | To test that the line description and TCP/IP interface are working correctly, specify the IP address or host name for your system as defined in the host table ( Figure 17 or Figure 18). Note: This step is valid only for LAN interfaces like token-ring, Ethernet, FDDI, or wireless. Skip this step if you are using a frame relay or X.25 interface. |
Verify TCP/IP Connection (VFYTCPCNN) Type choices, press Enter. Remote system . . . . . . . . . 199.5.83.158 |
Figure 17. Verifying TCP/IP Connection - Internet Address
Verify TCP/IP Connection (VFYTCPCNN) Type choices, press Enter. Remote system . . . . . . . . . gensys00 |
Figure 18. Verifying TCP/IP Connection - Host Name
TCP/IP sends data to the Ethernet adapter, instructing the adapter to send the data to its own Ethernet address. The data should then be returned to TCP/IP.
3 | To test your connection to the network, specify the IP address or host name of another system in your network, see Figure 19. |
Verify TCP/IP Connection (VFYTCPCNN) Type choices, press Enter. Remote system . . . . . . . . . gensys00 |
Figure 19. Verifying TCP/IP Connection - Remote System
If the PING operation is successful, the job log should contain messages similar to the ones shown in Figure 20. (To view the messages, use the Display Job Log (DSPJOBLOG) command, press F10 to display detailed messages, and then Page Up.)
ping '199.5.83.158' Verifying connection to host system 199.5.83.158. Connection verification 1 took .003 seconds. 1 successful connection verifications. Connection verification 2 took .002 seconds. 2 successful connection verifications. Connection verification 3 took .003 seconds. 3 successful connection verifications. Connection verification 4 took .002 seconds. 4 successful connection verifications. Connection verification 5 took .002 seconds. 5 successful connection verifications. Connection verification statistics: 5 of 5 successful (100 %). Round-trip (in milliseconds) min/avg/max = 2/2/3 |
Figure 20. Successful PING Messages
If the PING operation is unsuccessful, you should see messages similar to the ones shown in Figure 21.
ping gensys01 Verifying connection to host system GENSYS01.domainxyz.acme.com at address 199.5.83.1. No response from host within 1 seconds for connection verification 1. No response from host within 1 seconds for connection verification 2. No response from host within 1 seconds for connection verification 3. No response from host within 1 seconds for connection verification 4. No response from host within 1 seconds for connection verification 5. Connection verification statistics: 0 of 5 successful (0 %). Bottom |
Figure 21. Unsuccessful PING Messages
If this occurs, check your configuration steps. In addition, verify that the configuration at the remote system is correct and that the remote system is powered up.
For more details about PING (VFYTCPCNN), see the topic on "Verifying TCP/IP Connections" in the TCP/IP Configuration and Reference manual, SC41-5420.
You have just completed the iSeries family system TCP/IP configuration for a single-network example. The system is ready to run applications like FTP, LPR, TELNET, or SMTP and other user-written applications.
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
18300213
Was this topic helpful?
Document Information
Modified date:
12 October 2022
UID
nas8N1019592
Manage My Notification Subscriptions