IBM SC41-5420-04 manual Verifying Additional TCP/IP Connections, Successful Ping Messages

Page 41

> ping '9.4.73.212'

Verifying connection to host system 9.4.73.212.

PING request 1 from 9.4.73.212 took 24 ms. 256 bytes. TTL 64. PING request 2 from 9.4.73.212 took 11 ms. 256 bytes. TTL 64. PING request 3 from 9.4.73.212 took 31 ms. 256 bytes. TTL 64. PING request 4 from 9.4.73.212 took 11 ms. 256 bytes. TTL 64 PING request 5 from 9.4.73.212 took 12 ms. 256 bytes. TTL 64. Round-trip (in milliseconds) min/avg/max = 11/17/31 Connection verification statistics: 5 of 5 successful (100 %).

Figure 18. Successful PING Messages

3.If the PING operation is successful, you should see messages similar to those in Figure 18.

If the PING operation is unsuccessful, you should see messages similar to those in Figure 19.

If you receive an unsuccessful PING message, check your configuration steps. Also check that the configuration at the remote system is correct and that the remote system is not powered down. For additional information about identifying the cause for an unsuccessful connection verification, see TCP/IP Troubleshooting (http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/info/rzaku/ rzakuoverview.htm) in the Information Center. If you are using the Supplemental Manuals CD, then switch to the iSeries Information Center CD to access this information.

>ping '9.4.73.198'

Verifying connection to host system 9.4.73.198.

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 19. Unsuccessful PING Messages

Note: A datagram sent by TCP or UDP to a system with the name LOOPBACK does not actually leave the system. The IP layer, instead, returns the datagram to the TCP or UDP layer from which it came. The other layers then treat the datagram as a normal incoming datagram. The LOOPBACK host name can be used with any TCP/IP command requiring a system name, such as PING or FTP (or any TCP or UDP application including user-written applications). Using the LOOPBACK default host name provides an ability to test TCP/IP applications without actually connecting to a physical network.

The server defines LOOPBACK as the default host name by automatically creating an entry in the local host table.

Verifying Additional TCP/IP Connections

Once TCP/IP is configured on the iSeries, and the initial connection is verified, you will probably want to add more systems to your network. When you connect

Chapter 1. Configuring TCP/IP 27

Image 41
Contents TCP/IP Configuration and Reference Page TCP/IP Configuration and Reference Fifth Edition May Contents Index About TCP/IP Configuration and Reference SC41-5420 Vi OS/400 TCP/IP Configuration and Reference V5R1 Operations Navigator Prerequisite and related informationViii OS/400 TCP/IP Configuration and Reference V5R1 Page OS/400 TCP/IP Configuration and Reference V5R1 Summary of changes Xii OS/400 TCP/IP Configuration and Reference V5R1 What you need to know before you can configure TCP/IP Configuring TCP/IPGathering Information About your Network Planning for TCP/IP Installation and ConfigurationLine Description Parameters Checklist TCP/IP Planning ChecklistsInterfaces to Local TCP/IP Networks Local TCP/IP Host Information Checklist25 / Remote System Information Installing the TCP/IP Application ProgramsTcpadm Using the TCP/IP Administration MenuUsing the Configure TCP/IP Menu Cfgtcp Configure TCP/IP MenuConfiguring TCP/IP using the Command Line Interface Configuring TCP/IP using the EZ-Setup WizardServices table Protocol tableConfiguring a TCP/IP Interface Configuring a Line DescriptionImportant Note Internet addressLine description Subnet maskAssociated local interface Automatic startDo you need to add routes at all? Configuring TCP/IP RoutesMaximum Transmission Unit MTU size Route destinationDftroute None Preferred binding interfaceAdding TCP/IP routes NO, *YES Multiple Default RoutesNormal Configuring TCP/IP Remote System Information Configuring TCP/IP attributesIP Datagram Forwarding Adding Remote System InformationLind 15, *LIND, *TRANSMIT PVCNone NONE, *REQUEST, *ACCEPT Adding an Entry to the Host Table Configuring TCP/IP Host Table EntriesWork with TCP/IP Host Table Display DNS BernMacian Localhost SYSNAM890Loopback AnyNet/400 Appc over TCP/IP Configuring the Local Domain and Host NameLocal Domain Name System DNS ServerDspmsg Qsysopr Dspmsg Qtcp Starting TCP/IP and TCP/IP ServersJob Name Description TCP/IP JobsEnd TCP/IP Endtcp Verifying the TCP/IP ConnectionSuccessful Ping Messages Verifying Additional TCP/IP ConnectionsVerify TCP/IP Connection Vfytcpcnn Verify TCP/IP ConnectionVerify TCP/IP Connection Ping Verifying TCP/IP Connections with Host Name-ExampleVERBOSE, *QUIET COMP, *ESCAPEVerifying TCP/IP Connections with Internet Address-Example Saving Your TCP/IP ConfigurationConfiguring TCP/IP 32 OS/400 TCP/IP Configuration and Reference V5R1 Work with TCP/IP Network Status Menu Network StatusWork with TCP/IP Network Status Work with TCP/IP Interface StatusWork with TCP/IP Interface Status Internet Network LineStarting TCP/IP Interfaces Opt Address Mask ServiceInternet Subnet Type MaxthrputEnding TCP/IP Interfaces Route Subnet Next Opt Destination Mask Hop Available Display TCP/IP Route InformationDisplay TCP/IP Route Information Work with TCP/IP Connection Status Route Type Opt Destination ServiceType Source BottomRemote Local Opt Address Port User Bytes Out Work with TCP/IP Connection StatusRemote Local Opt Address Port Idle Time State ALL Ending TCP/IP ConnectionsRemote Local Opt Address Port Type TCPConfirm End of TCP/IP Connections Working with Configuration StatusDisplay Multicast Groups Displaying TCP/IP Network Status InformationOpt Description Status Job Trnline Active Trnlinet Trnlitcp QtcpipHost Group Hardware Address Displaying TCP/IP InterfacesDisplay Multicast Host Groups Display TCP/IP Interface Status Displaying Associated RoutesTrlan MSBRoute Subnet Next Opt Destination Mask Hop Displaying Route Details OptionDisplay Associated Routes Direct Displaying TCP/IP Route InformationDisplay TCP/IP Route Details Display TCP/IP Route Information, Display 1 Display TCP Connection Status Displaying TCP/IP ConnectionsDisplay TCP/IP Connection Status, Display 2 Displaying Connection TotalsDisplay TCP/IP Connection Totals TCP/IP Host TablesHost File Formats Managing TCP/IP Host TablesHost Table Information with *AIX Files Host Table Information with *NIC FilesHost Table Information with *AS400 Files Tips for Merging Host TablesMerging TCP/IP Host Tables Managing the Host Table from a Central Site Merge the File Dead Gateway Processing Negative Advice from TCP or the Data Link LayerMultihoming Function How IP Responds to Negative AdviceMultihoming Single Host, Single Network, Single Line Per physical LAN only Multihoming TCP/IP Network Example The Multihoming functionLoopback None Type of Service TOSX25LINE TOS Example Multiple RoutesTCP/IP Port Restriction Paolo Configuring TCP/IP Port RestrictionsGerry UDP, *TCPOnly Related Tables and the Host Table Configure Related Tables MenuWork with Service Table Entry Display IBM Using X.25 PVC instead of SVCMulticast Restrictions Chglintrn Lindtrnline FCNADRC00000040000 70 OS/400 TCP/IP Configuration and Reference V5R1 TCP/IP Protocol Support Provided by IOP Base Pool SizeTCP/IP Jobs Outbound batching of TCP and UDP datagrams Running TCP/IP Only Performance Considerations Merge Host Table Performance74 OS/400 TCP/IP Configuration and Reference V5R1 Line type Configuration command Source Service Access Point Configuration StepsCreating the Line Description Line Description NameDetermining the Maximum Size of Datagrams Setting the Maximum Transmission Unit78 OS/400 TCP/IP Configuration and Reference V5R1 TCP/IP Exit Points and Exit Programs Appendix B. TCP/IP Application Exit Points and ProgramsTCP/IP Application Exit Points OS/400 Registration FacilityAdding Your Exit Program to the Registration Facility Creating Exit ProgramsQAPP0100 Select your exit pointAdd your exit program Select the Add Exit Program optionYourlib Removing Exit ProgramsTCP/IP Application Request Validation Exit Point Interface Exit Point Interfaces for TCP/IP Application Exit PointsRequired Parameter Group Application identifierUser profile Operation identifierRemote IP address Length of remote IP addressAllow operation Usage NotesLength of operation-specific information QSYS.LIB file system pathnames are always in uppercase Point Command stringLength of command string Character conversion option Command processor identifierQshell interpreter not installed 92 OS/400 TCP/IP Configuration and Reference V5R1 Copyright IBM Corp Trademarks Programming Interface InformationDB2 96 OS/400 TCP/IP Configuration and Reference V5R1 Index Special Characters Interface Qtgtelnets Qtsmtpsrvr Page SC41-5420-04