HiperSockets Converged Interface support
z/OS® V2R3 Communications Server, with APARs PI83372 and OA53198, provides HiperSockets Converged Interface (HSCI) solution to support the z/VM® bridge environment. With this solution, a Linux guest can connect to z/OS via Layer 2 HiperSockets and to the external network by using a single IP interface.
This support also significantly improves HiperSockets usability by dynamically provisioning and activating a HiperSockets interface when an OSD interface is activated for the same physical network ID (PNetID). With this support, the TCP/IP stack only sees the OSD interface. This design approach greatly reduces the network administration costs as HiperSockets interfaces no longer are required to be configured, operated, or managed in z/OS Communications Server. This solution allows a single IP interface (OSD) to provide access to the external Ethernet LAN and transparent access to HiperSockets for LPAR to LPAR communications within the central processor complex (CPC). This solution also eliminates the need to reconfigure z/OS HiperSockets interfaces when moving a z/OS instance from one CPC to another. The HSCI is also referred to as an IQDC interface.
- This function does not support IPAQENET interfaces that are defined by using the DEVICE, LINK, and HOME statements. Convert your IPAQENET definitions to use the INTERFACE statement to enable this support.
- This function also requires the virtual MAC (VMAC) operand be specified on your IPAQENET interfaces to request OSA-generated VMACs.
- This function minimally requires a zEnterprise® EC12 (zEC12).
- This function requires an Internal Queued Direct I/O (IQD) channel path ID (CHPID) configured with the external bridge function.
|If you use IPv4 Queued Direct I/O (QDIO) interfaces that are defined with the DEVICE, LINK, and HOME statements, convert those definitions to use the IPAQENET INTERFACE statement.||Steps for converting from IPv4 IPAQENET DEVICE, LINK, and HOME definitions to the IPv4 IPAQENET INTERFACE statement in z/OS Communications Server: IP Configuration Guide|
|Configure at least one IQD CHPID with the external bridge function in hardware
configuration definition (HCD). For each bridged IQD CHPID, configure at least 10 channel unit
addresses (CUAs) for each protocol (IPv4 and IPv6) that your network supports.
If you use jumbo frames for your OSD interfaces that are associated with a converged HiperSockets CHPID, specify an IQD frame size larger than 16 K when you configure your converged HiperSockets CHPID. This avoids fragmentation, which allows more traffic to flow over the converged HiperSockets interface.
|z/OS HCD User's Guide|
|Select a unique physical network ID (PNetID) for each of your networks. Configure the appropriate PNetID in HCD for each OSD CHPID on a network and configure the same PNetID on each bridged IQD CHPID to be used on that network. If you already have a PNetID configured on your OSD CHPID for Shared Memory Communications, configure the same PNetID on your bridged IQD CHPID.||z/OS HCD User's Guide|
|Configure AUTOIQDC on the GLOBALCONFIG statement in the TCP/IP profile.||GLOBALCONFIG statement in z/OS Communications Server: IP Configuration Reference|
|Display whether the stack is enabled for dynamic IQDC interfaces and whether large outbound TCP socket sends should use these interfaces.||Netstat CONFIG/-f report in z/OS Communications Server: IP System Administrator's Commands|
|Display information about the dynamic IQDC TRLEs and datapath devices by issuing the D NET,ID=trle, or D NET,TRL,TRLE= command.||z/OS Communications Server: SNA Operation|
|Display the dynamically generated name of an IQDC interface by issuing the Netstat DEvlinks/-d command against the associated OSD interface. Extract the name from the "Associated IQD Converged Interface" output line.||Netstat DEvlinks/-d report in z/OS Communications Server: IP System Administrator's Commands|
|Display information about the number of packets and bytes which went over the dynamic IQDC interface by issuing the Netstat DEvlinks/-d command against the IQDC interface.||Netstat DEvlinks/-d report in z/OS Communications Server: IP System Administrator's Commands|
|Display the ARP cache entries that are associated with an IPv4 IQDC interface by issuing the Netstat ARp/-R command.||Netstat ARp/-R report in z/OS Communications Server: IP System Administrator's Commands|
|Display the neighbor cache entries that are associated with an IPv6 IQDC interface by issuing the Netstat ND/-n command.||Netstat ND/-n report in z/OS Communications Server: IP System Administrator's Commands|
To find all new and updated topics about HiperSockets Converged Interface support, see Table 2.