Verifying connections with Netstat, Ping, and Traceroute

The interfaces were verified with the instructions in IP configuration overview. The first thing to verify is that the devices and interfaces are started. In the case of point-to-point links like the CTCs in TCPCS4, the following message is written to the z/OS® console when the device starts:

EZZ4313I INITIALIZATION COMPLETE FOR DEVICE CTCE02

In the case of IPv6 interfaces like OSAQDIO46 in TCPCS4, the following message is written to the z/OS console when the interface starts:

EZZ4340I INITIALIZATION COMPLETE FOR INTERFACE OSAQDIO46

The same information can be determined by using the Netstat DEvlinks/-d command. The following example is a portion of the output of the Netstat DEvlinks/-d command with the CTCE02 device shown as ready. The Netstat DEvlinks/-d command can be issued on TCPCS4 and TCPCS7 to verify that the devices on both systems are ready.

DevName: CTCE02            DevType: CTC       DevNum: 0E00             
  DevStatus: Ready                                                
  LnkName: CTC4TO7           LnkType: CTC         LnkStatus: Ready
    NetNum: 0    QueSize: n/a                                          
    ActMtu: 32760                                                    
  Routing Parameters:                                              
    MTU Size: 01500             Metric: 01                             
    DestAddr: 0.0.0.0           SubnetMask: 255.255.255.0              
  Multicast Specific:                                                  
    Multicast Capability: Yes                                          
  GROUP             REFCNT
  -----             ------
  224.0.0.5         0000000001
  224.0.0.1         0000000001
  Link Statistics:                                                     
    BytesIn                           = 488                            
    Inbound Packets                   = 0                              
    Inbound Packets In Error          = 0                              
    Inbound Packets Discarded         = 0                              
    Inbound Packets With No Protocol  = 0                              
    BytesOut                          = 1092                          
    Outbound Packets                  = 0                              
    Outbound Packets In Error         = 0                              
    Outbound Packets Discarded        = 0

The following example is a portion of the output of the Netstat DEvlinks/-d command with an IPv6 interface (OSAQDIO46) shown as ready.

IntfName: OSAQDIO46        IntfType: IPAQENET6 IntfStatus: Ready
    NetNum: n/a  QueSize: 0   Speed: 0000001000                       
   MacAddress: 0002559A3F65
    DupAddrDet: 1                                                      
    CfgRouter: Non                   ActRouter: Non                
    CfgMtu: None                     ActMtu: 8992                   
  Multicast Specific:                                                  
    Multicast Capability: Yes                                      
    RefCnt      Group                                                  
    ------      -----                                                  
    0000000001  ff02::1:ff03:1                                      
    0000000002  ff02::1                                        
  Interface Statistics:                                                
    BytesIn                           = 592                           
    Inbound Packets                   = 0                              
    Inbound Packets In Error          = 0                              
    Inbound Packets Discarded         = 0                              
    Inbound Packets With No Protocol  = 0                              
    BytesOut                          = 1008                           
    Outbound Packets                  = 0                              
    Outbound Packets In Error         = 0                              
    Outbound Packets Discarded        = 0

If the devices do not have a LnkStatus or IntfStatus of Ready, this must be resolved before continuing. There are several things that might cause the LnkStatus or IntfStatus to not be ready. For example, the device might not be defined to z/OS correctly, the device might not be defined in PROFILE.TCPIP correctly, and so on.

You can use the PING command to verify indirect routes exist to others hosts within the network .

ping 9.67.107.7                                   
 CS V1R6: Pinging host 9.67.107.7
 Ping #1 response took 0.048 seconds.
 READY
ping 2001:0db8:0:a1b:2:559a:3f65:3                  
 CS V1R6: Pinging host 2001:0db8:0:a1b:2:559a:3f65:3
 Ping #1 response took 0.051 seconds.             
 READY

Use the Traceroute command to verify that the correct route is being taken for each indirectly attached host:

tracerte 9.67.107.5                                    
 CS V1R6: Traceroute to 9.67.107.5 (9.67.107.5)       
 1 9.67.106.7 (9.67.106.7)  40 ms  7 ms  6 ms
 2 9.67.107.5 (9.67.107.5)  9 ms  8 ms  9 ms
 READY

The following example shows IPv6 for indirectly attached hosts:

tracerte 2001:0db8:0:a1c:2:36a4:b39a:7 
 CS V1R6: Traceroute to 2001:0db8:0:a1c:2:36a4:b39a:7
 at IPv6 address: 2001:0db8:0:a1c:2:36a4:b39a:7
 1 fe80::1:2:3:4
 (fe80::1:2:3:4) 13 ms 25 ms 40 ms
 2 2001:0db8:0:a1c:2:36a4:b39a:7
 (2001:0db8:0:a1c:2:36a4:b39a:7) 29 ms 263 ms 196 ms