Steps for diagnosing sysplex routing problems

Determine why packets are not distributed properly in your sysplex.

Procedure

Perform the following steps:

Run the Netstat VIPADyn VIPAROUTE/-v VIPAROUTE command on the distributing stack to see what type of route is used for distributing packets to target stacks.
Figure 1. Netstat VIPADyn example
```
D TCPIP,TCPCS,NET,VIPADYN,VIPAROUTE               
EZD0101I NETSTAT CS V1R7 TCPCS                  
VIPA ROUTE:                                       
  DESTXCF: 193.1.3.94                             
    TARGETIP: 213.5.1.1                           
    RTSTATUS: ACTIVE                              
  DESTXCF: 193.1.4.94                             
    TARGETIP: 213.6.2.2                           
    RTSTATUS: INACTIVE                            
  DESTXCF: 2EC0::943:F003                         
    TARGETIP: 1EC0::5:1:1                         
    RTSTATUS: ACTIVE                              
  DESTXCF: 2EC0::943:F004                         
    TARGETIP: 1EC0::6:2:2                         
    RTSTATUS: INACTIVE                            
4 OF 4 RECORDS DISPLAYED
```
- If there is no VIPA ROUTE entry, IP packets that are distributed by Sysplex Distributor to target stacks use dynamic XCF interfaces. Use the Netstat ROUTe/-r command on the distributing stack to see other routing failure problems.
- If there is a VIPA ROUTE entry defined for a target stack and the RtStatus field shows Active, IP packets that are distributed by Sysplex Distributor to that target stack use the normal IP routing tables to determine the best available route.
- If there is a VIPA ROUTE entry defined for that target stack and the RtStatus field shows Unavail, the defined target IP address in the route entry is not available yet. This could be because the target stack is currently active, but the target IP address is not defined in that target stack. All packets to that target stack use dynamic XCF interfaces. This is likely to be a configuration error that should be investigated. EZD1173I is issued when the stack detects this problem.
- If there is a VIPA ROUTE entry defined for a target stack and the RtStatus field shows Inactive, no route exists to that target stack. See z/OS Communications Server: IP System Administrator's Commands for more information about the RtStatus field.

Run the Netstat ROUTe/-r command on the distributing stack to see details of the routing information. The following shows an example of this information.

D TCPIP,TCPCS,NET,ROUTE                                         
EZD0101I NETSTAT CS V1R7 TCPCS                            
IPV4 DESTINATIONS                                               
DESTINATION         GATEWAY          FLAGS     REFCNT  INTERFACE
193.1.1.94/32       0.0.0.0          H         000000  EZASAMEMVS  
193.1.1.94/32       0.0.0.0          UH        000000  EZAXCFC6    
193.1.1.94/32       0.0.0.0          UH        000000  EZAXCFC7    
193.1.3.94/32       0.0.0.0          UHS       000000  EZAXCFC6    
193.1.4.94/32       0.0.0.0          UHS       000000  EZAXCFC7    
203.1.1.94/32       0.0.0.0          UH        000000  VIPLCB01015E
213.4.1.1/32        0.0.0.0          UH        000000  LTRLE1A     
213.4.2.2/32        0.0.0.0          H         000000  LTRLE2A     
213.5.1.1/32        0.0.0.0          UHZ       000001  LTRLE1A     
213.6.2.2/32        0.0.0.0          HZ        000001  LTRLE2A     
IPV6 DESTINATIONS                             
DESTIP:   ::1/128                             
  GW:     ::                                  
  INTF:   LOOPBACK6         REFCNT:  000000   
  FLGS:   UH                MTU: 65535        
DESTIP:   1EC0::4:1:1/128                     
  GW:     ::                                  
  INTF:   V6TRLE1A          REFCNT:  000000   
  FLGS:   UH                MTU: 14336        
DESTIP:   1EC0::4:2:2/128                     
  GW:     ::                                  
  INTF:   V6TRLE2A          REFCNT:  000000   
  FLGS:   H                 MTU: 0            
DESTIP:   1EC0::5:1:1/128                     
  GW:     ::                                  
  INTF:   V6TRLE1A          REFCNT:  000001   
  FLGS:   UHZ               MTU: 14336    
DESTIP:   1EC0::6:2:2/128                      
  GW:     ::                                   
  INTF:   V6TRLE2A          REFCNT:  000001    
  FLGS:   HZ                MTU: 32000             
.
.
32 OF 32 RECORDS DISPLAYED   
END OF THE REPORT

Run the Netstat VCRT/-V DETAIL command on the distributing stack to see the routing information for each connection. The following shows an example of this information.

Figure 2. Netstat VCRT/-V detail example

D TCPIP,TCPCS,NET,VCRT,DETAIL                   
EZD0101I NETSTAT CS V1R7 TCPCS        
DYNAMIC VIPA CONNECTION ROUTING TABLE:
Dest:      203.38.1.1..801              
  Source:  192.168.2.76..1029           
  DestXCF: 193.1.3.94                   
    PolicyRule:    *NONE*               
    PolicyAction:  *NONE*               
    Intf:  LTRLE1A                      
      VipaRoute:  Yes       Gw:  0.0.0.0
Dest:      203.38.1.1..801              
  Source:  192.168.2.76..1028           
  DestXCF: 193.1.7.94                   
    PolicyRule:    *NONE*               
    PolicyAction:  *NONE*               
    Intf:  EZASAMEMVS                   
      VipaRoute:  No        Gw:  0.0.0.0
Dest:      203.38.1.2..9001             
  Source:  192.168.2.76..1031           
  DestXCF: 193.1.4.94                   
    PolicyRule:    *NONE*               
    PolicyAction:  *NONE*               
    Intf:  LTRLE2A                      
      VipaRoute:  Yes       Gw:  0.0.0.0
Dest:      203.38.1.2..9001             
  Source:  192.168.2.76..1030           
  DestXCF: 193.1.6.94                   
    PolicyRule:    *NONE*               
    PolicyAction:  *NONE*               
    Intf:  EZASAMEMVS                   
      VipaRoute:  No        Gw:  0.0.0.0
4 OF 4 RECORDS DISPLAYED

Results

See Routing failures for additional information about routing failures.