Hipersockets - IBM z13s Technical Manual

Intranode management network
The INMN is a private and physically isolated 1000BASE-T Ethernet internal management
network that operates at 1 Gbps. It connects all resources (z13s and zBX Model 004
components) of an ensemble node for management purposes. It is pre-wired, internally
switched, configured, and managed with full redundancy for high availability.
The INMN requires two ports (CHPID port 0 from two OSA-Express5S 1000BASE-T features,
or OSA-Express4S 1000BASE-T features; CHPID port 1 is not used at all in this case) that
are configured as CHPID type OSM. The connection is through a System Control Hub (SCH)
in the z13s server. Because it is a stand-alone node, the INMN ToR switches on
zBX Model 004 are not connected to the SCHs.
Ensemble HMC management functions
An HMC can manage multiple z Systems servers and can be at a local or a remote site. If the
z13s server is defined as a member of an ensemble, a pair of HMCs (a primary and an
alternate) is required, and certain restrictions apply. The primary HMC is required to manage
ensemble network connectivity, the INMN, and the IEDN network.
For more information, see 11.6, "HMC in an ensemble" on page 428 and 9.5, "RAS capability
for the HMC and SE" on page 362.

4.8.6 HiperSockets

The HiperSockets function of z13s servers provides up to 32 high-speed virtual LAN
attachments, just like the IBM zEnterprise zEC12, IBM zEnterprise BC12, IBM zEnterprise
196, and IBM zEnterprise 114 servers. Previous servers provided 16 attachments.
HiperSockets IOCP definitions on z13 and z13s servers: There is a new parameter for
HiperSockes IOCP definitions on z13 and z13s servers. As such, the z13 and z13s IOCP
definitions need to be migrated to support the HiperSockets definitions (CHPID type IQD).
On z13 and z13s servers, the CHPID statement of HiperSockets devices requires the
keyword VCHID. VCHID specifies the virtual channel identification number associated with
the channel path. Valid range is 7E0 - 7FF.
VCHID is not valid on z Systems before the z13 and z13s servers.
For more information, see the z Systems Input/Output Configuration Program User's Guide
for ICP IOCP, SB10-7163.
HiperSockets can be customized to accommodate varying traffic sizes. Because
HiperSockets does not use an external network, it can free up system and network resources.
This advantage can help eliminate attachment costs, and improve availability and
performance.
HiperSockets eliminates having to use I/O subsystem operations and having to traverse an
external network connection to communicate between LPARs in the same z13s server.
HiperSockets offers significant value in server consolidation when connecting many virtual
servers. It can be used instead of certain coupling link configurations in a Parallel Sysplex.
HiperSockets internal networks support two transport modes:
Layer 2 (link layer)
Layer 3 (network or IP layer)
172
IBM z13s Technical Guide