IPv4 INTERFACE statement for HiperSockets and Static VIPAs

In z/OS® V2R1 Communications Server, you can use the INTERFACE statement in the TCP/IP profile to configure IPv4 interfaces for HiperSockets™ and static VIPAs. This enhancement has the following benefits:
Restrictions:
  • z/OS CS supports a maximum of eight VLANs per HiperSockets CHPID per z/OS image per IP version.
  • To designate a static VIPA as the source VIPA for an IPv4 interface that is configured using DEVICE and LINK statements, you must configure that static VIPA using DEVICE and LINK statements.

Using the IPv4 INTERFACE statement for HiperSockets and Static VIPAs

To use the IPv4 INTERFACE statement for HiperSockets and Static VIPAs, perform the appropriate tasks in Table 1.
Table 1. IPv4 INTERFACE statement for HiperSockets and Static VIPAs
Task Reference
To use the INTERFACE statement for an IPv4 HiperSockets interface, take the following steps:
  1. Configure the INTERFACE statement for IPAQIDIO in the TCPIP profile.
  2. Optionally, specify a source VIPA for this interface by using the SOURCEVIPAINTERFACE parameter.
  3. Activate the interface by using the START statement or VARY TCPIP,,START command, and by specifying the interface name.
 INTERFACE statement – IPAQIDIO in z/OS Communications Server: IP Configuration Reference
To convert existing IPv4 HiperSockets definitions to use the INTERFACE statement, take the following steps:
  1. Replace DEVICE and LINK statements for IPAQIDIO with the new IPv4 INTERFACE statement for IPAQIDIO.
  2. Remove the HOME entry and any BSDROUTINGPARMS entry for the interface.
  3. If you are currently using the order of your HOME list to designate the source VIPA to be associated with this interface, specify the name of the appropriate static VIPA on the SOURCEVIPAINTERFACE parameter of the IPAQIDIO INTERFACE statement.
  4. If you are currently configuring any static routes over this interface using the GATEWAY statement, convert the GATEWAY statement to a BEGINROUTES block.
To use the INTERFACE statements to define an IPv4 static VIPA interface, configure the IPv4 INTERFACE statement for VIRTUAL in the TCPIP profile. INTERFACE statement - VIRTUAL in z/OS Communications Server: IP Configuration Reference
To convert existing IPv4 static VIPA definitions to use the INTERFACE statement, take the following steps:
  • Replace the DEVICE and LINK statements for VIRTUAL with the new IPv4 INTERFACE statement for VIRTUAL.
  • Remove the HOME entry and any BSDROUTINGPARMS entry for the interface.
To configure multiple VLANs for a HiperSockets CHPID, take the following steps:
  • For IPv4, use the new IPv4 INTERFACE statement for IPAQIDIO. For IPv6, use the existing IPv6 INTERFACE statement for IPAQIDIO6. For each interface, specify the VLAN ID using the VLANID parameter.
  • For each IPv4 interface for this HiperSockets CHPID, configure a unique subnet using the subnet mask specification on the IPADDR parameter.
 See the following topics in z/OS Communications Server: IP Configuration Reference:
To configure a source VIPA for IPv4 dynamic XCF interfaces, configure the SOURCEVIPAINTERFACE parameter on the IPCONFIG DYNAMICXCF statement in the TCPIP profile. IPCONFIG statement in z/OS Communications Server: IP Configuration Reference
To display information about IPv4 HiperSockets and static VIPA interfaces that were configured using the INTERFACE statement, issue the Netstat DEvlinks/-d command. Netstat DEvlinks/-d in z/OS Communications Server: IP System Administrator's Commands
To limit a Netstat display to only show the interfaces that are associated with a specific HiperSockets TRLE, specify the TRLE name on the INTFName/-K filter when using either the Netstat DEvlinks/-d or HOme/-h command. See the following topics in z/OS Communications Server: IP System Administrator's Commands:
To display information about the dynamic HiperSockets TRLEs and the datapath devices, issue the D NET,ID=trle, or D NET,TRL,TRLE= command. See the following topics in z/OS Communications Server: SNA Operation:
Parent topic: Simplification