Netstat VCRT/-V report

Displays the dynamic VIPA Connection Routing Table used for sysplex distributor and moveable dynamic VIPA support. On a sysplex distributor routing stack, it displays all connections being routed through the distributor. On a stack taking over a dynamic VIPA, it displays every connection to the dynamic VIPA. On a sysplex distributor target stack or a stack that is in the process of giving up a dynamic VIPA, the report displays every connection for which the stack is an endpoint.

TSO syntax


>>---NETSTAT VCRT--| Modifier |--| Target |--| Output |--| (Filter |---><

Modifier


>>-DETAIL------------------------------------------------------><

DETAIL

Displays the general dynamic VIPA Connection Routing Table information plus the following additional information for each connection:

Policy rule and policy action.
Timed affinity-related information.
Indicates whether the connection is eligible for acceleration. This information is not displayed if the stack is not enabled for acceleration. For details about how to enable a stack for acceleration, see the IPCONFIG profile statement information in the z/OS Communications Server: IP Configuration Reference.
Information about the route used by the stack which owns a dynamic VIPA to send packets to the target stack. This information is not displayed on a target stack or if no VIPAROUTE profile statements have been configured to the stack. The routing information provided describes the route used in forwarding the last packet received for this connection to the target stack.
The routing information might describe the best available route to reach the IP address, which was defined in the VIPAROUTE statement for that target stack, or it might describe the dynamic XCF route for that target stack. See VIPADYNAMIC information in the z/OS Communications Server: IP Configuration Reference for details about the VIPAROUTE statement. For more information about the use of the routing information, see route selection for distributing packets details in the z/OS Communications Server: IP Configuration Guide.

Target

Provides the report for a specific TCP/IP address space by using TCp tcpname. See The Netstat command target for more information about the TCp parameter.

Output

The default output option displays the output on the user's terminal. For other options, see The TSO NETSTAT command syntax or Netstat command output.

Filter


>>-+-HOSTName--hostname----------------+-----------------------><
   |         .-----------------------. |   
   |         V                       | |   
   +-IPAddr----+-ipaddr------------+-+-+   
   |           +-ipaddr/prefixLen--+   |   
   |           '-ipaddr/subnetmask-'   |   
   |         .----------------.        |   
   |         V                |        |   
   +-IPPort----ipaddr+portnum-+--------+   
   |       .-------------.             |   
   |       V             |             |   
   '-POrt------portnum---+-------------'

z/OS UNIX syntax


>>---netstat -V--| Modifier |--| Target |--| Output |--| Filter |---><

Modifier


>>-DETAIL------------------------------------------------------><

DETAIL

Displays the general dynamic VIPA Connection Routing Table information plus the following additional information for each connection:

Policy rule and policy action.
Timed affinity-related information.
Indicates whether the connection is eligible for acceleration. This information is not displayed if the stack is not enabled for acceleration. For details about how to enable a stack for acceleration, see the IPCONFIG profile statement information in the z/OS Communications Server: IP Configuration Reference.
Information about the route used by the stack which owns a dynamic VIPA to send packets to the target stack. This information is not displayed on a target stack or if no VIPAROUTE profile statements have been configured to the stack. The routing information provided describes the route used in forwarding the last packet received for this connection to the target stack.
The routing information might describe the best available route to reach the IP address, which was defined in the VIPAROUTE statement for that target stack, or it might describe the dynamic XCF route for that target stack. See VIPADYNAMIC details in the z/OS Communications Server: IP Configuration Reference for information about the VIPAROUTE statement. For more details about the use of the routing information, see information about route selection for distributing packets in the z/OS Communications Server: IP Configuration Guide.

Target

Provide the report for a specific TCP/IP address space by using -p tcpname. See The Netstat command target for more information about the TCp parameter.

Output

The default output option displays the output to z/OS UNIX shell stdout. For other options, see The z/OS UNIX netstat command syntax or Netstat command output.

Filter


          .----------------.            
          V                |            
>>-+- -B----ipaddr+portnum-+--------+--------------------------><
   +- -H--hostname------------------+   
   |      .-----------------------. |   
   |      V                       | |   
   +- -I----+-ipaddr------------+-+-+   
   |        +-ipaddr/prefixLen--+   |   
   |        '-ipaddr/subnetmask-'   |   
   |      .-------------.           |   
   |      V             |           |   
   '- -P------portnum---+-----------'

Filter description

HOSTName/-H hostname

Filter the output of the VCRT/-V report using the specified host name hostname. You can enter one filter value at a time and the specified value can be up to 255 characters long.

Result: At the end of the report, Netstat displays the host name that the resolver used for the resolution and the list of IP addresses returned from the resolver that it used as filters.

Restrictions:

The HOSTName/-H filter does not support wildcard characters.
Using the HOSTName/-H filter might cause delays in the output due to resolution of the hostname value, depending upon resolver and DNS configuration.

IPAddr/-I ipaddrIPAddr/-I ipaddr/prefixlengthIPAddr/-I ipaddr/subnetmask

Filter the report output using the specified IP address ipaddr, ipaddr/prefixlength, or ipaddr/subnetmask. You can enter up to six filter values. Each specified IPv4 ipaddr value can be up to 15 characters in length and each selected IPv6 ipaddr value can be up to 45 characters in length.

ipaddr: Filter the output of the VCRT/-V report using the specified IP address ipaddr. For IPv4 addresses, the default subnet mask of 255.255.255.255 is used. For IPv6 addresses, the default prefixlength of 128 is used.

ipaddr/prefixlength: Filter the output of the VCRT/-V report using the specified IP address and prefix length ipaddr/prefixlength. For an IPv4 address, the prefix length range is 1 – 32. For an IPv6 address, the prefix length range is 1 – 128.

ipaddr/subnetmask

Filter the output of the VCRT/-V report using the specified IP address and subnet mask ipaddr/subnetmask. The IP address ipaddr in this format must be an IPv4 IP address.

Guidelines:

The filter value ipaddr can be a source IP address, a destination IP address, or a destination XCF IP address.
For an IPv6-enabled stack:
- Both IPv4 and IPv6 ipaddr values are accepted and can be mixed on the IPAddr/-I option.
- An IPv4-mapped IPv6 address is accepted as a valid ipaddr value and will usually provide the same result as its IPv4 address.

Restrictions:

The IPAddr/-I option for VCRT/-V report does not support wildcard characters.
For an IPv4-only stack, only IPv4 ipaddr values are accepted.
For a UDP endpoint socket, the filter value applies only to the local or source IP address.

IPPort/-B ipaddr+portnum

Filter the report output of the VCRT/-V report using the specified IP address and port number. You can enter up to six filter values. Each specified IPv4 ipaddr value can be up to 15 characters in length, denoting a single IPv4 IP address; each specified IPv6 ipaddr value can be up to 45 characters in length, denoting a single IPv6 IP address. Valid portnum values are in the range 0–65535. The filter values ipaddr and portnum matches any combination of the local and remote IP address and local and remote port.

Guidelines:

The filter value ipaddr can be a source IP address, a destination IP address, or a destination XCF IP address.
For an IPv6-enabled stack, the following apply:
- Both IPv4 and IPv6 ipaddr values are accepted and can be mixed on the IPPort/-B option.
- An IPv4-mapped IPv6 address is accepted as a valid ipaddr value and usually provides the same result as the IPv4 address.

Restrictions:

The ipaddr value in the IPPort/-B filter does not support wildcard characters.
For an IPv4-only stack, only IPv4 ipaddr values are accepted.
An entry is returned only when both the ipaddr and portnum values match.
For a UDP endpoint socket, the filter value applies only to the local or source IP address and port.

POrt/-P portnum: Filter the output of the VCRT/-V report using the specified port number portnum. You can enter up to six filter values.

Guideline: The port number can be either a local or remote port.

Restriction: For a UDP endpoint socket, the filter value applies only to the local or source port.

Command syntax examples

From TSO environment

NETSTAT VCRT
   Displays the dynamic VIPA Connection Routing Table information in the default 
   TCP/IP stack. 
NETSTAT VCRT TCP TCPCS6
   Displays the dynamic VIPA Connection Routing Table information in the TCPCS6 
   stack.

From UNIX shell environment

   netstat -V
   netstat -V -p tcpcs6

Report examples

The following examples are generated by using TSO NETSTAT command. Using the z/OS UNIX netstat command displays the data in the same format as the TSO NETSTAT command.

Not IPv6 enabled (SHORT format)

NETSTAT VCRT

MVS TCP/IP NETSTAT CS V2R1       TCPIP Name: TCPCS           18:17:26
Dynamic VIPA Connection Routing Table:                               
Dest IPaddr      DPort  Src IPaddr       SPort  DestXCF Addr         
-----------      -----  ----------       -----  ------------   
201.2.10.11      00021  193.9.200.1      00000  193.1.1.18     
201.2.10.11      00021  193.9.200.1      01025  193.1.1.18 
201.2.10.11      00021  201.1.10.85      01026  201.1.10.10    
203.1.10.18      08000  193.10.1.1.118   01080  193.1.1.108

NETSTAT VCRT DETAIL

MVS TCP/IP NETSTAT CS V2R1       TCPIP Name: TCPCS           14:16:16
Dynamic VIPA Connection Routing Table:                               
Dest IPaddr      DPort  Src IPaddr       SPort  DestXCF Addr         
-----------      -----  ----------       -----  ------------         
201.2.10.11      00021  201.1.10.85      00000  201.1.10.10           
  CfgTimAff: 0200  TimAffCnt: 0000000002  TimAffLft: 0000       
201.2.10.11      00021  201.1.10.85      01026  201.1.10.10 
  PolicyRule:    *NONE*                                              
  PolicyAction:  *NONE*  
  Intf:  CTC1            
    VipaRoute: Yes      Gw: 0.0.0.0
  Accelerator: No
201.2.10.11      00021  201.1.10.85      01027  201.1.10.10 
  PolicyRule:    *NONE*                                              
  PolicyAction:  *NONE*  
  Intf:   OSAQDIOLINK 
    VipaRoute: Yes      Gw: 199.100.1.1 
  Accelerator: yes
203.1.10.18      08000  193.10.1.118     01080  193.1.1.108
  PolicyRule:    PRule-TCP-High                                      
  PolicyAction:  PAction-TCP-High  
  Intf:   EZAXCFC7
    VipaRoute: No       Gw: 0.0.0.0   
  Accelerator: No
203.1.10.19      09000  193.10.1.119     01081  193.1.1.109
  PolicyRule:    PRule-TCP-High                                      
  PolicyAction:  PAction-TCP-High  
  Intf:   EZAXCFC6         
    VipaRoute: Unavail  Gw: 0.0.0.0  
  Accelerator: No

IPv6 enabled or request for LONG format

NETSTAT VCRT

MVS TCP/IP NETSTAT CS V2R1       TCPIP Name: TCPCS           20:04:04
Dynamic VIPA Connection Routing Table:                               
Dest:      201.2.10.11..21                                           
  Source:  193.9.200.1..0       
  DestXCF: 193.1.1.18          
Dest:      201.2.10.11..21                                           
  Source:  193.9.200.1..1025       
  DestXCF: 193.1.1.18
Dest:      201.2.10.11..21      
  Source:  201.1.10.85..1026    
  DestXCF: 201.1.10.10          
Dest:      203.1.10.18..8000      
  Source:  193.9.200.1..1080    
  DestXCF: 193.1.1.108   

Dest:      2001:0db8::0522:f103..21  
  Source:  2001:0db8::0524:f104..1026
  DestXCF: 2001:0db8::0943:f003

NETSTAT VCRT DETAIL

MVS TCP/IP NETSTAT CS V2R1       TCPIP Name: TCPCS           20:04:04
Dynamic VIPA Connection Routing Table:                               
Dest:      201.2.10.11..21                                           
  Source:  201.1.10.85..0       
  DestXCF: 201.1.10.10          
    CfgTimAff: 0200  TimAffCnt: 0000000002  TimAffLft: 0000  
Dest:      201.2.10.11..21      
  Source:  201.1.10.85..1026    
  DestXCF: 201.1.10.10 
    PolicyRule:    *NONE*                                             
    PolicyAction:  *NONE* 
    Intf:   CTC1            
      VipaRoute: Yes      Gw: 0.0.0.0                       
  Accelerator: No
Dest:      201.2.10.11..21      
  Source:  201.1.10.85..1027    
  DestXCF: 201.1.10.10 
    PolicyRule:    *NONE*                                             
    PolicyAction:  *NONE* 
    Intf:   OSAQDIOLINK 
      VipaRoute: Yes      Gw: 199.100.1.1         
  Accelerator: No
Dest:      203.1.10.18..8000      
  Source:  193.9.200.1..1080    
  DestXCF: 193.1.1.108 
    PolicyRule:    PRule-TCP-High                                      
    PolicyAction:  PAction-TCP-High     
    Intf:   EZAXCFC7
      VipaRoute: No       Gw: 0.0.0.0 
  Accelerator: No
Dest:      203.1.10.19..9000      
  Source:  193.9.10.119..1081    
  DestXCF: 193.1.1.109 
    PolicyRule:    PRule-TCP-High                                      
    PolicyAction:  PAction-TCP-High     
    Intf:   EZAXCFC6
      VipaRoute: Unavail  Gw: 0.0.0.0 
  Accelerator: No
 Dest:     2ec0::0522:f103..21  
  Source:  2ec0::0524:f104..1026
  DestXCF: 2ec0::0943:f003 
    PolicyRule:    PRule-TCP-High                                      
    PolicyAction:  PAction-TCP-High
    Intf:   OSAQDIO46 
      VipaRoute: Yes      Gw:  2ec0::206:2aff:fe71:4400

Report field descriptions

For a SHORT format report

Dest IPaddr: The destination IP address for this connection.

DPort: The destination port for this connection.

Src IPaddr: The source IP address for this connection. If the source IP address value is 0 for an entry, then the entry does not represent an established connection. Entries with a source IP address value 0 represent an affinity between a client IP address and a dynamic VIPA destination IP address and port. Such an affinity arises from passive-mode FTP. Each affinity entry is immediately followed by all the established connection entries that are associated with the affinity.

SPort: The source port for this connection. If the source port value is 0 for an entry, then the entry does not represent an established connection. Entries with a source port value 0 represent an affinity between a client IP address and a dynamic VIPA destination IP address and port. Such an affinity might arise from passive-mode FTP or from a distributed DVIPA with a nonzero value for the TIMEDAFFINITY parameter on the VIPADISTRIBUTE profile statement. Each affinity entry is immediately followed by all the established connection entries that are associated with the affinity.

DestXCF Addr: The dynamic XCF address of the stack that is processing this connection. For connections to and from non-z/OS tier 1targets, this value is the IP address of the tier 1 target.

For a LONG format report

Dest: The destination IP address and port for this connection.

Source: The source IP address and port for this connection. If the source IP address value is 0 for an entry, then the entry does not represent an established connection. Entries with a source IP address value of zero represent an affinity between a client IP address and a dynamic VIPA destination IP address and port. Such an affinity arises from passive-mode FTP. Each affinity entry is immediately followed by all the established connection entries that are associated with the affinity.
If the source port value is zero for an entry, then the entry does not represent an established connection. Entries with a source port value of zero represent an affinity between a client IP address and a dynamic VIPA destination IP address and port. Such an affinity might arise from passive-mode FTP or from a distributed DVIPA with a nonzero value for the TIMEDAFFINITY parameter on the VIPADISTRIBUTE profile statement. Each affinity entry is immediately followed by all the established connection entries that are associated with the affinity.

DestXCF: The dynamic XCF address of the stack that is processing this connection. For connections to and from non-z/OS tier 1targets, this value is the IP address of the tier 1 target.

For a SHORT or LONG format report

DETAIL

For each entry that represents an established dynamic VIPA connection or an affinity created by the passive-mode FTP, displays the preceding information plus the following policy rule and action.

PolicyRule: The policy rule name configured to the Policy Agent. The PolicyRule value *NONE* indicates that the connection was not mapped to a policy rule.

PolicyAction: The policy action name configured to the Policy Agent. A PolicyAction value *NONE* indicates that the connection was not mapped to a policy action.

For each entry that represents an established dynamic VIPA connection on the stack which owns the dynamic VIPA (when VIPAROUTE profile statements have been configured to the stack), displays the preceding information plus the following additional routing information.

Intf: The name of the interface for the route being used to distribute packets to the target stack. The value *NONE* indicates that there is no route associated with this connection.

VipaRoute

Indicates whether the VIPAROUTE parameter is being used to route packets to the target stack for this connection:

No: Indicates that the dynamic XCF interface is being used to distribute packets to the target stack.

Yes: Indicates that the best available route, based on the VIPAROUTE parameters, is being used to distribute packets to the target stack.

Unavail: Indicates that the TCP/IP stack attempted to use the route based on the VIPAROUTE parameters, but an error was detected during the verification of the VIPAROUTE statement. Because of this, the dynamic XCF interface is being used to distribute packets to that target stack. See VIPADYNAMIC statement information in the z/OS Communications Server: IP Configuration Reference for details about the VIPAROUTE statement.

Gw

The gateway used to send packets to the target stack. If the value is equal to 0.0.0.0 for an IPv4 entry or :: for an IPv6 entry, then the destination is directly reachable without needing to go through a gateway.

Accelerator

Indicates whether this connection is eligible for the QDIO Accelerator function. To be eligible, the QDIO accelerator function must be enabled by specifying the QDIOACCELERATOR parameter on the IPCONFIG statement. The accelerator field is displayed only if QDIOACCELERATOR is specified on the IPCONFIG statement. For more information about the IPCONFIG statement, see the IPCONFIG profile statement information in z/OS Communications Server: IP Configuration Reference

The packets that are eligible for acceleration are those that are received by the Sysplex Distributor and that are forwarded to a target stack in any of the following inbound and outbound DLC combinations:

Inbound HiperSockets™, forwarded outbound over OSA-Express QDIO connections
Inbound OSA-Express QDIO, forwarded outbound over the dynamic XCF HiperSockets connection
Inbound OSA-Express QDIO, forwarded outbound over OSA-Express QDIO connections
Inbound HiperSockets, forwarded outbound over the dynamic XCF HiperSockets connection

No: Indicates that this connection is not eligible for the QDIOACCELERATOR function.
Yes: Indicates that this connection is eligible for the QDIOACCELERATOR function.

For each entry that represents an affinity created by the TIMEDAFFINITY parameter on the VIPADISTRIBUTE profile statement, displays the preceding information plus the following affinity-related information.

CfgTimAff: The affinity value that was defined in the TIMEDAFFINITY parameter on the VIPADISTRIBUTE profile statement.

TimeAffCnt: The count of currently established connections associated with this affinity.

TimAffLft: The number of seconds left before the affinity between the client IP address and the dynamic VIPA destination IP address and port is removed. After the last established connection is closed, the affinity will remain for the number of seconds indicated in the CfgTimAff field.