z/OS 2.3 HiperSockets Converged Interface (HSCI) support

IBM – Enterprise Networking Solutions
Page 1 IBM Confidential Until Availability Announce © Copyright International Business Machines Corporation 2018
z/OS 2.3 HiperSockets Converged Interface (HSCI)
03-8-18 Update
Jerry Stevens – sjerry@us.ibm.com
Randall Kunkel – kunkel@us.ibm.com
z/OS® V2R3 Communications Server – Enterprise Networking Solutions

Contributions
The content of this presentation was a collaborative team effort resulting
in a comprehensive presentation covering a new z/OS HiperSockets
solution that overlaps with broader System z networking concepts.
Thanks to the z/OS CS development team for the review, input and
many contributions!
Ø Greg Callis
Ø Charles Cruse
Ø Jeff Haggar
Ø Randall Kunkel
Ø Benjamin Rau

Agenda Topics
1. Review / Background topics:
A. OSA / HiperSockets (HS) “Transport Modes” (Layer 2 vs. Layer 3)
B. z/VM VSwitch Bridge Environment
C. Multi-homed hosts
2. Problem Descriptions (two issues) and solution
1. Issue #1 Overview: z/OS and Linux HS incompatibility
2. Solution: HSCI Introduction
3. Issue #1 Solution Overview
4. Issue #2 Overview: z/OS relocation and HS usability
5. Issue #2 Solution Overview
3. z/OS HSCI: Product Overview
4. Backup

Topic 1A. OSA and HS System Architecture “Transport Modes”
(Layer 2 vs. Layer 3 mode)
1. OSA/HS (QDIO) architecture defines two “transport” modes of adapter connectivity:
1. Layer 2 (Ethernet) mode (frames forwarded based on MAC address (VMAC))
2. Layer 3 (IP) mode (IP packets forwarded based on IP address)
2. The QDIO L2/L3 transport mode is System z internal architecture that affects how
OSA/HS virtualizes (shares) the adapter and how packets are “forwarded” internally within
the system (by MAC vs. IP address). In this context “Layer 3” does not mean IP routing.
3. The mode is defined in software (i.e. in the OS configuration, when the network interface
is activated).
4. OSA Layer 3 mode provides various Layer 3 “IP assist” functions (e.g. ARP, CHKSUM,
Segmentation etc.). IP assists are not supported when in L2 mode and not supported by
HS (N/A for either mode).
5. Mixing L2 and L3 modes on the same:
• OSA (card/port):
LPARs (hosts) that share the same OSA (port) can communicate internally (“loop back”). Hosts
sharing the same OSA can communicate internally even when using mixed modes (i.e. L2 hosts
can communicate internally with L3 hosts).
• HS (IQD CHPID):
L2 hosts using the same HS (IQD) CHPID (“internal LAN”) can not communicate with L3 hosts.
Hosts can connect to the same IQD CHPID while using either mode, but they can only
communicate with other hosts (on the same CHPID) using the same transport mode.1
Note 1. An IQD Channel configured with “External Bridge” supports Layer 2 mode only.

Topic 1A. QDIO OSA and HS Transport Modes Concepts (part 2)
VLAN ID tag
Ethernet 802.3 header, if VLAN ID is in use, the 4
additional bytes (802.1Q VLAN tag) are inserted here.

System z QDIO Architecture: OSA Mixing Layer 2 and Layer 3 Modes
. . .
LP 1 LP 3LP 2 LP 5LP 4 LP N
PR/SM
LP 6
OSD
OSDOSDOSD OSD OSD
OSD
1
OSD
2
IP 1 IP2 IP3 IP4 IP5 IP X IP Y IP Z
CPC
LPARs sharing OSA in Layer 2 mode can communicate (internally through OSA)
with LPARs in Layer 3 mode. The QDIO L2/L3 transport mode is transparent to the
external LAN.
OSA QDIO connections using L2 and
L3 modes sharing the same OSA
PCHID (card/port) can communicate
internally through OSA.
OSD
IP interfaces can
be defined in
either L2 or L3
transport modes.
Not all Operating
Systems support
both modes.
L2 L2
L2
L2L2 L3 L3
L3
External LAN
OSA PCHID
üok

System z IQD Architecture: HS Mixing Layer 2 and Layer 3 Modes
. . .
LP 1 LP 3LP 2 LP 5LP 4 LP N
PR/SM
LP 6
IQD CHPID (Internal Network)
IQD IQDIQDIQD IQD IQD
IQD
1
IQD
2
IP 1 IP2 IP3 IP4 IP5 IP X IP Y IP Z
CPC
IQD Layer 2
Connections
IQD Layer 3
Connections
LPARs using HS in Layer 2 mode can not communicate with LPARs in Layer 3 mode.
On the same IQD CHPID, the green
IQD connections using L2 mode are
isolated from the yellow connections
using L3. L2 and L3 IQD connections
can NOT communicate over the
same IQD CHPID!
IP interfaces can
be defined in
either L2 or L3
transport modes.
Not all Operating
Systems support
both modes.
L2 L2 L2 L2L2 L3 L3
L3
X

Topic 1A. z/OS OSA and HS Transport Modes (part 3)
1. z/OS supports Layer 3 mode only for both OSA and HS1.
2. Although z/OS only supports L3 mode, z/OS also supports an OSA “hybrid” L3 mode
(L3 mode that also uses a VMAC). Using an OSA-generated VMAC (INTERFACE
statement with VMAC) is the recommended mode for all z/OS OSA connectivity.2
3. Layer 2 mode is more beneficial / applicable to z/VM (Linux guests) environments.
For additional planning considerations and implementation details, reference:
1. z/VM Connectivity SC24-6174-09
http://publibz.boulder.ibm.com/epubs/pdf/hcsc9c33.pdf
2. Linux:
Device Drivers, Features, and Commands:
http://public.dhe.ibm.com/software/dw/linux390/docu/l412dd32.pdf
When combining z/OS (L3) and Linux guests (L2 or L3) on the same HS network (IQD
CHPID), issues with connectivity / complexity could occur.
Notes:
1. Exceptions: IQDX (IEDN HS) and OSA OSM CHPIDs are L2. HSCI (introduced here) will also support L2.
2. Refer to the OSA INTERFACE statement VMAC parameter in the TCP/IP Configuration Reference. Best
practice is to use VMAC (OSA generated).

Topic 1B. Broadcast Domain (network Bridge vs. Router)
A broadcast domain is a logical division of a computer network, in which all
nodes can reach each other by broadcast at the data link layer. A broadcast
domain can be within the same LAN segment or it can be bridged to other
LAN segments.
switch
nodes nodes nodes
LAN segment 1 LAN segment 2 LAN segment 3
L2 Bridge
Broadcast Domain 1 Broadcast Domain 2
L3
IP Router
Broadcast Domain = “Physical Network” (can be defined with a “PNetID”)
switch switch

§ The z/VM VSwitch and HS must be
operating in the L2 transport mode
(i.e. the Bridge requires L2)
§ No transport mode conversions
§ Guests QA1,QA2, QA3 and QA4 have real
(dedicated) QEBSM connections to HS
PCHID.
– Optimum performance configuration requiring almost
no z/VM involvement
– Bridged by default when using QDIO Assist
(QEBSM, which provides connectivity to both HS and
the external LAN segments)
§ Guests VA1 and VA2 have virtual (NIC)
connections through VSwitch A
– Optimum performance config for guests that are not
deployed with QEBSM on z/VM. Eliminates “shadow”
queue overhead
– Connectivity to HS and external LAN segments
§ OSA uplink port BAU no changes in current
support
OSA
External LAN
HiperSockets (IQD)
PR/SM
z/VM LPAR A
VSwitch A
zLinuxQA3
zLinuxQA4
OSAUplinkPort
zLinuxVA1
z/OSVA2
QEBSM
zLinuxQA2
zLinuxQA1
OSA
VSwitch HS
Bridge Port
HS Uplink
Port
HS Bridge Capable
NIC Port
CEC X
Topic 1B. z/VM VSwitch HS Bridge Overview

LAN/VLAN
Single Subnet
10.1.1.0/24
Host A
Network
Interface
IP Address: 10.1.1.5
Single Default Route
LAN/VLAN
Single Subnet
10.1.1.0/24
Host A
Network
Interface
IF1
IP Address:
10.1.2.5
Network
Interface
IF2
LAN/VLAN
Single Subnet
10.1.2.0/24
IP Address:
10.1.1.5
Which Interface do we use for outbound traffic?
Which interface is used for inbound traffic?
What network route entries are needed?
What if an interface fails?
Can I transparently fall over to the alternate interface?
Which
Interface
do we
use?
Single-Homed Host
Multi-Homed Host
Complexity Level (drives up cost)
Topic 1C. Single vs. Multi-Homed Hosts

Topic 2. Problem statement(s) and Solution
There are two main issues:
1. z/VM Bridge and Linux (Layer 2) Incompatibility:
The z/VM Bridge support provides a very competitive and seamless solution for the overall System
z networking landscape for Linux on z clients. There are many advantages (e.g. allows single IP
interface per Linux guest) to the z/VM bridge model.
However, z/OS does not support (L2) connectivity to Linux in this configuration.
The missing z/OS support creates a gap in the overall value of the z System solution (Layer 2 Linux
compatibility, HS, z/VM Bridge, VSwitch etc.), rendering the overall z solution as “partial/unfinished”.
2. z/OS HiperSockets usability:
When moving a z/OS instance to another CPC, it requires manual administrative actions to
reconfigure the HS interfaces to match the new IP subnet(s) on the new CPC. This applies to all
z/OS environments (even in z/OS only environments). Some customers regularly / frequently move
their z/OS instances. Customers have expressed concerns about this issue (i.e. how this manual
step impacts their day to day operations causing some customers to rethink or stop using HS).

z/VM VSwitch Bridge: Issue #1 z/OS and Linux HS L2
OSD NIC
CPC X
z/VM
LPAR
OSA NIC OSA NIC
Linux Guest Linux Guest
VSwitch
z/OS LPAR
OSD NIC
Linux LPAR
OSD
OSA Uplink
Port
VS HS
Bridge
Port
Guest Port Guest Port
OSD
Primary Backup
HS Uplink Port
Server B
(native)
Server A
(native)
HiperSockets (IQD)
Server E
(simulated)
Server C
(real)
z/OS Guest
Server F
(simulated)
OSD NIC
Server D
(real)
Linux Guest
IQD NIC
PR/SM
If 1 If 1
If 1
If A
If A
If A
LAN
OSD
Problem: This Linux guest is
configured to use HS (bridged
to the external LAN, which
requires L2 mode). This
guest can’t communicate with
z/OS (over this HS L2
interface).
With the Linux on z environment, the
user could deploy many (e.g. dozens or
100s) of Linux guests, multiple z/VM
LPARs all similar to Server D
(all having the same issue)
Layer 2 Mode
Focus on Server D!

z/VM VSwitch Bridge: Workaround
OSD NIC
CPC X
z/VM
LPAR
OSA NIC OSA NIC
Linux Guest Linux Guest
VSwitch
z/OS LPAR
OSD NIC
Linux LPAR
OSD
OSA Uplink
Port
VS HS
Bridge
Port
OSD
Primary Backup
HS Uplink Port
Server B
(native)
Server A
(native)
HiperSockets (IQD-A)
Server E
(simulated)
Server C
(real)
z/OS Guest
Server F
(simulated)
OSD NIC
Server D
(real)
Linux Guest
IQD NIC
PR/SM
If 1 If 1
If 1
If A
If A
If A
LAN
OSD
If B
IQD NIC
HiperSockets (IQD-B)
IQD NIC
If 2
workaround: configure a
2nd HS CHPID and IP
interface in every Linux
guest and all z/OS images
This Linux guest (Server D) is now
multi-homed driving up complexity
and cost (when deploying many
guests).
Layer 3 Mode Layer 2 Mode
Focus on Server D!

Solution: HiperSockets Converged Interface Concepts
LPAR 1 LPAR 2 LPAR 3
z/OS 1 z/OS 2 z/OS 3
PR/SM
OSA
External LAN
OSA Interface OSA Interface OSA Interface
IQD
OSA OSA OSA
CPC
HiperSockets (IQD) is
transparently “converged”
(provided) with your OSA
interface
192.168.1.100 192.168.1.102 192.168.1.104
The IQD internal network is
“joined” with your external network,
forming a single network…
(single “broadcast domain” or a
single “PNetID”)
1 2

Solution: z/OS HSCI (Available 1Q/2018)
z/OS HiperSockets Converged Interface (HSCI)
Single OSA IP Address
(single Network Interface)
OSD IQD
External LAN
PNet “A”
z/OS
The OSA link provides access to the
“External LAN fabric”
… and provides access to all servers on
both the Internal and External Network
The IQD link provides access to the CPC
“Internal LAN / HS fabric” (optimal path)
… and provides access to just the subset of servers
on the same CPC Internal portion of the LAN
HS Internal LAN
The z/OS administrator
only configures / manages
the OSA interface
VLANs are optional and when
used are configured and
supported withoutchange
Converged
Interface
With AUTOIQDC…
(TCP/IP profile Globalconfig)
the IQD interface is
dynamically / transparently
added when matching
PNet IDs are found
OSA PNet ID must be
configured in HCD
All IP traffic to / from
this IP subnet
Communications Server transparently
splits and converges
network traffic to this IP interface
IQD PNet ID must be configured in HCD and
must match OSA PNet ID
Layer 2Layer 3
IQD (HS)OSA
ARP
Cache
ARP Cache

z/OS 2.3 HSCI (AUTOIQDC) Highlights
1. The upper layers of the TCP/IP software stack only see an OSA Interface (i.e. the IP route(s), IP
address/subnet, MTU, etc. all reflect the attributes of the OSA interface, IQDC is not visible)
2. The HSCI (L2) path is used by the lower layers of the stack when the peer host is found on the IQD network
(i.e. when the next hop IP address is in the sending host’s ARP/ND cache).
3. IPv4 and IPv6 are both supported.
4. The HSCI inherits the associated OSA INTERFACE attributes (IP address, VMAC, VLAN ID, MTU etc.)
5. All HSCI related artifacts are dynamically created with the following naming conventions:
1. IQDC IPv4:
1. Interface name = EZAIQCnn (where EZAIQC indicates IPv4 IQDC and nn = CHPID, e.g. EZAIQCE0).
2. TRLE name = IUTIQCnn (where IUTIQC indicates IPv4 IQDC and nn = CHPID, e.g. IUTIQCEO).
2. IQDC IPv6:
1. Interface name = EZ6IQCnn (where EZ6IQC indicates IPv6 IQDC and nn = CHPID, e.g. EZ6IQCE0
2. TRLE name = IUTIC6nn (where IUTIC6 indicates IPv6 IQDC and nn = CHPID, e.g. IUTIC6EO).
6. Layer 2 architecture requires that software:
1. transmits and receives “Ethernet frames”.
2. handles all ARP (IPv4) and Neighbor Discovery (IPv6) processing in software
7. z/OS QDIO Accelerator is supported (see backup for details)
8. AUTOIQDC can be changed with Vary Obey. The change does not impact current usage, but will impact any
future attempts to use it.

z/OS 2.3 HSCI Enablement
APARs:
1. OA53198 (VTAM, FMID HVT6230)
2. PI83372 (TCP/IP, FMID HIP6230)
Notes.
1. z/OS 2.3 Announcement Letter (see HSCI on networking page 18):
IBM z/OS 2.3 RFA URL
2. The VTAM and TCP/IP PTFs are co-reqs (HSCI requires both)
3. HSCI is off by default, enabled with AUTOIQDC parameter
4. Terminology: HSCI (solution) is controlled by AUTOIQDC (parameter); HSCI = IQDC
5. There are no other software or System z hardware requirements
(no other product dependencies or co-reqs)1
Note 1. When Linux is executing as a z/VM guest virtual machine, then exploiting the z/VM VSwitch bridge is required.
The IQD CHPID must be configured with External Bridge and the z/VM VSwitch Bridge support must be enabled for
the same IQD CHPID that is being used by the Linux guest. Also refer to VM66135 for maintenance.

z/OS HSCI and z/VM VSwitch Bridge L2 Compatibility
OSA NIC
CPC X
z/VM
LPAR
OSA NIC OSA NIC
Linux
Guest
Linux Guest
L2 VSwitch
z/OS LPAR
OSA NIC
Linux LPAR
OSA
OSA Uplink
PortVS HS
Port
HS Uplink Port
Server B
(native)
Server A
(native)
Server E
(simulated)
IQD NIC
Server C
(real)
z/OS Guest
Server F
(simulated)
OSA NIC IQD NIC
Server D
(real)
Linux Guest
IQD NIC
PR/SM
If 1 If 1
If A
If A
If A
If A
External LAN
OSA
Focus on Server D!
z/OS HSCI Solution: Linux (Server D) is using a single IP
interface (HS L2) and can now communicate internally with z/OS
(HSCI) and externally (transparently) over the LAN using the
z/VM VSwitch Bridge (using OSA). There are no changes to
Linux, z/VM or HS.
Layer 2 Mode IQD Bridged HiperSockets
Very Important HSCI Concept!
z/OS HSCI is bridge compatible but is
not bridge eligible (network traffic does
not go thru (use) the IQD bridge)!
z/OS communicates internally with hosts
that are directly connected to IQD (L2 HS)
and communicates externally using OSA.

z/OS Only Configurations and HSCI (Issue #2)
Switching topics… the next set of charts examine:
Ø z/OS only configurations (i.e. z/OS configurations without Linux or the
z/VM VSwitch Bridge) and ...
Ø how HSCI can resolve the z/OS relocation usability issue (issue #2)
while also significantly improving / simplifying the overall z/OS HS
usage model.

If A If B
OSA NIC HS NIC
If C If E If G If I If KIf D If F If H If J If L
HS NIC HS NICHS NIC HS NIC HS NICOSA NIC OSA NIC OSA NIC OSA NIC OSA NIC
OSD
Server A
z/OS 1
Server B
z/OS 2
Server C
z/OS 3
Server D
z/OS 4
Server E
z/OS 5
Server F
z/OS 6
IP A.1 IP X.1
VLAN A VLAN X
LAN (Net A)
PR/SM
CPC Y
IQD CHPID A Network ‘X’
IP Route A
IP Route B
IP Route C
IP Route D
IP Route E
IP Route F
IP Route G
IP Route H
IP Route I
IP Route J
IP Route K
IP Route L
User must provision and manage
three independent networks
Net A, Net X and Net Y
IQD CHPID B Network ‘Y’
VLAN A
Each z/OS image has
multiple (2) networks
(the 2 systems use
3 networks)
z/OS traditional HS (without HSCI): Each host sees multiple IP networks (subnets)
IP A.2 IP X.2
VLAN A VLAN X
IP A.3 IP X.3
VLAN A VLAN X
IP A.4 IP Y.1
VLAN A VLAN Y
IP A.5 IP Y.2
VLAN A VLAN Y
IP A.6 IP Y.3
VLAN A VLAN Y
Sysplex A Sysplex ACPC X
PR/SM
OSD
1
2
3
Net Y
Net A
Net X

Without HSCI: Moving a z/OS instance to another CPC requires reconfiguring HS
If A If B
OSA NIC HS NIC
If C If E If G If I If KIf D If F If H If J If L
OSD
Server A
z/OS 1
Server B
z/OS 2
Server C
z/OS 3
Server D
z/OS 4
Server E
z/OS 5
Server F
z/OS 6
IP A.1 IP X.1
VLAN A VLAN X
LAN
PR/SM
CPC Y
IQD CHPID A Network ‘X’
IP Route A
IP Route B
IP Route C
IP Route D
IP Route E
IP Route F
IP Route G
IP Route H
IP Route I
IP Route J
IP Route K
IP Route L
User must provision and manage
three independent networks
IQD CHPID B Network ‘Y’
VLAN A
IP A.2 IP X.2
VLAN A VLAN X
IP A.3 IP Y.4
VLAN A VLAN Y
IP A.4 IP Y.1
VLAN A VLAN Y
IP A.5 IP Y.2
VLAN A VLAN Y
IP A.6 IP Y.3
VLAN A VLAN Y
PR/SM
OSD
1
2
3
Net Y
Net A
Net XWhen z/OS 3 is moved from
CPC X to CPC Y the HS
interface must be
reconfigured for a different
HS network in CPC Y

If A
OSA NIC HS NIC
If B If C If D If E If F
OSD
Server A
z/OS 1
Server B
z/OS 2
Server C
z/OS 3
Server D
z/OS 4
Server E
z/OS 5
Server F
z/OS 6
IP A.1
VLAN A
LAN
PR/SM
CPC Y
IQD CHPID A Network ‘A’
IP Route A IP Route B IP Route C IP Route D IP Route E IP Route F
User provisions and manages
a single network, Net A !
IQD CHPID B Network ‘A’
VLAN A
Now each z/OS image
has access to 1 network
(network A), via “OSA”
HS is not visible to the
TCP/IP stack!
Solution, With HSCI: Each host now sees a single IP network (subnet A)
IP A.2
VLAN A
IP A.3
VLAN A
IP A.4
VLAN A
IP A.5
VLAN A
IP A.6
VLAN A
PR/SM
OSD
1
1
1
Net A
Net A
Net A

With HSCI: Moving a z/OS instance requires no HS configuration changes!
If A
OSA NIC HS NIC
If B If C If D If E If F
OSD
Server A
z/OS 1
Server B
z/OS 2
Server C
z/OS 3
Server D
z/OS 4
Server E
z/OS 5
Server F
z/OS 6
IP A.1
VLAN A
LAN
PR/SM
CPC Y
IQD CHPID A Network ‘A’
IP Route A IP Route B IP Route C IP Route D IP Route E IP Route F
User provisions and manages
a single network !
IQD CHPID B Network ‘A’
VLAN A
IP A.2
VLAN A
IP A.3
VLAN A
IP A.4
VLAN A
IP A.5
VLAN A
IP A.6
VLAN A
PR/SM
OSD
1
1
1
Net A
Net A
Net A
When z/OS 3 is moved to CPC Y
there are no z/OS HS changes
required! (HS is not configured
and is not visible to the stack)

OSA IP Address A.y
OSD-2
IQD
HSCI
External LAN
PNet “A”
z/OS
Single logical network
All associated OSA VMACs are reused
(duplicated) on the HSCI.
HS Internal LAN
Converged
Interface
One IQD data device is used for
all OSAs with access to the same PNetID
(Note. One IQD device per stack, per IP version per PNetID.
The HSCI device terminates when the last associated OSA
interface terminates)
Layer 2Layer 3
IQD (HS)OSA-2
ARP
Cache
ARP Cache
OSD-1
ARP Cache
OSA-1
OSA IP Address A.x
Converged
Interface
Layer 3
VMAC A VMAC B VMAC A’
VMAC B’
IQD
TRLE
z/OS HSCI: Multiple OSAs single IP subnet (single IQD device)
IF layer
Device layer
hardware layer
A separate logical association
is created for each
associated OSA interface
with the same IQD device
i.e. each OSA has a HSCI (IQDC)
provided by the same IQD device

OSA IP Address B.x
IP subnet B / VLAN B
OSD-2
IQD
HSCI
PNet “A”
z/OS
All associated OSA VMACs and VLAN IDs are
reused (duplicated) on the HSCI
Subnet HS Internal LAN
Converged
Interface
One IQD data device is used for
all OSAs with access to the same PNetID
(Note. One IQD device per stack, per IP version Per PNetID.
The HSCI device terminates when the last associated OSA
interface terminates)
Layer 2Layer 3 / VMAC B
IQD (HS)OSA-2
ARP
Cache
ARP Cache
OSA-1
OSA IP Address A.x
IP subnet A /VLAN A
Converged
Interface
Layer 3 / VMAC A
VMAC A VMAC B VMAC A’ VMAC B’
IQD
TRLE
IF layer
Device layer
hardware layer
IP Subnet A / VLAN A IP Subnet B / VLAN B
z/OS HSCI: Multiple OSAs and Multiple IP subnets (single IQD device)
OSD-1
HS Subnet / VLAN A HS Subnet / VLAN B
A separate logical association
is created for each
associated OSA interface
with the same IQD device
i.e. each OSA has a HSCI (IQDC)
provided by the same IQD device
ARP Cache

PNetIDs and HSCI (refresher / background)...
Ø PNetIDs are configured on a port basis in HCD and represent a user defined
“Physical Network ID” for the physical network that this port will be connected
Ø PNetIDs are dynamically learned by z/OS and are used to associate adapters by
their physical network connectivity, for example:
1. SMC-R: Associate OSA with RoCE ports
2. SMC-D:
1. Associate OSA with ISM1 ports … (or alternatively)
2. Associate HiperSockets with ISM1 ports
3. HSCI: Associate OSA with HiperSockets (new with HSCI)
Important Note!
Without (prior to) HSCI (e.g. see chart 21):
OSA and HS can NOT have the same PNetID.
(i.e. it is architecturally impossible for HS and OSA to represent the same “physical
network”)2
With HSCI (e.g. see chart 23):
Now OSA and HS can (must) have the same PNetID (with HSCI, OSA and HS
become a single logical network). For z/OS this is only valid with HSCI.
Note 1. HS and ISM are logical adapters that do not have physical ports but implement a single “logical port” per “PCHID”.
Note 2. To understand why it’s invalid for OSA and HS to be the same network research “Discontiguous Network”

PNetIDs and HSCI with SMC (SMC-R or SMC-D)
Ø Without HSCI (e.g. chart 21):
ISM can be used (associated) with OSA or HS (but not both for the same
ISM CHID)! OSA and HS can’t have the same PNetID.
Ø With HSCI (e.g. chart 23):
› HSCI “logically combines” the OSA LAN with the HS internal LAN forming a
single network. Therefore…
ISM can be used (associated) with both OSA and HS. Now ISM, OSA and HS all
(must) have the same PNetID.
› If SMC-R / RoCE is also used for this same OSA port, then the RoCE port will
also need to have the same PNetID.
In this case, OSA, RoCE, ISM and HS all have the same PNetID.
This means the TCP/IP connection can now:
– setup over OSA or HS and
– can then (when eligible) switch to use either:
• SMC-D (when peer hosts are within the same CPC) or
• SMC-R (peer hosts are on different CPCs).
Note 1. HS and ISM CHIDs don’t have physical ports but implement a single logical port.

Topic 3. z/OS CommServer HSCI Product Externals
1. HSCI is enabled with a single TCP/IP GLOBALCONFIG parameter “AUTOIQDC”
Notes
1. AUTOIQDC is the single parameter that enables the HSCI function (automatically create and converge
IQD devices with OSD devices)
2. NOAUTOIQDC is the default
3. AUTOIQDC has one sub-parameter (ALLTRAFFIC | NOLARGEDATA)
defaults to ALLTRAFFIC
4. HCD1 configuration for HS (IQD) is required with parameters:
1. External Bridge (L2 only) and
2. PNetID that matches the associated OSA(s) PNetID(s) in HCD
2. The IQDC interface is dynamically built, automatically:
1. started (when the first associated OSA is started) and
2. stopped (when the last associated OSA interface becomes inactive).
3. The VTAM HSCI TRLE is dynamically built and can be displayed
4. NetStat displays the HSCI with the associated OSA interface(s) and by the HSCI interface name
5. The operator can (alternatively) stop the IQDC interface and restart (if at least one associated OSA is already
active).
6. The IQDC interface supports UNICAST only. It is not used for MCAST or BCAST (other than ARP/ND). OSA
provides the necessary MCAST/BCAST support.
7. NMI, SMF, SNMP and TCPIPCS are all updated to add the HSCI reporting with the OSA interface(s)
Note 1. The HCD configuration requirements for IQDC are existing System HCD functions (now used by IQDC).

HSCI Configuration Requirements / Considerations
TCP/IP profile:
1. Your GLOBALCONFIG statement must specify AUTOIQDC
(default is NOAUTOIQDC)
2. The configuration for OSA (OSD) requires:
› INTERFACE statement (dev/link is not supported for HSCI)
› VMAC (OSA generated, a user defined VMAC is not supported)
Note. VLAN ID is optional. If configured it will be duplicated on the HSCI.
HCD:
1. IQD CHPID:
1. Must have a PNetID1 and External Bridge configured
2. The number of required IQD channel devices per TRLE: Two devices (read/write) are required for control
+ one additional device per TCP/IP stack, up to 8 stacks for a total of 10 devices per TRLE. A TRLE is
created for each IP version (up to 2 TRLEs). TRLEs are created for each unique IQD CHPID (PNetID)2.
3. IQD Max Frame Size Recommendation:
Use (at least) 24k (16k MTU)2
Note.
IQD default MFS = 16k (8k MTU). An 8k MTU is not large enough for a full Ethernet jumbo frame 8992)
(i.e. can force the OSA path to be used when streaming)
2. OSD CHPID(s) must have a PNetID1 configured that matches your IQD (External Bridge) CHPID PNetID
Notes
1. When using SMC-R or SMC-D, both OSA and IQD might already have PNetID configured. See chart 29.
2. See notes page for additional details.

Defining the IQD Parameters for HSCI in HCD (“Bridged HS”)
Specify IQD Channel Parameters
Specify or revise the values below.
Maximum frame size in KB . . . . . . 24 +
IQD function . . . . . . . . . . . . 3 1. Basic HiperSockets
2. IEDN Access (IQDX)
3. External Bridge
Physical network ID . . . . . . . . NETA____________
Note 1.
In order to enable HSCI the IQD CHPID must be configured as External (option 3
indicates this HS channel has external connectivity). This External setting is required
even when the z/VM VSwitch bridge function (environment) is not used or present (e.g. in
z/OS only configurations). OSA’s HCD configuration must also specify the same PNetID.
2. Must specify
External Bridge1
1. Recommend
24k MFS
3. Must configure
an IQD PNetID
that matches your
OSA PNetID

Coding AUTOIQDC in Configuration Assistant
TCP/IP stack configuration tasks
Define Network Interfaces
Global Interface Properties
Radio buttons control ALLTRAFFIC
vs. NOLARGEDATA
Checkbox codes AUTOIQDC
Requires Configuration Assistant APAR PI94208

Netstat Config (IQDC state)
D TCPIP,TCPCS3,N,CONFIG
EZD0101I NETSTAT CS V2R4 TCPCS3 709
TCP CONFIGURATION TABLE:
DEFAULTRCVBUFSIZE: 00065536 DEFAULTSNDBUFSIZE: 00065536
DEFLTMAXRCVBUFSIZE: 00262144 SOMAXCONN: 0000001024
MAXRETRANSMITTIME: 120.000 MINRETRANSMITTIME: 0.500
ROUNDTRIPGAIN: 0.125 VARIANCEGAIN: 0.250
VARIANCEMULTIPLIER: 2.000 MAXSEGLIFETIME: 30.000
DEFAULTKEEPALIVE: 00000120 DELAYACK: YES
RESTRICTLOWPORT: YES SENDGARBAGE: NO
.
.
.
SYSPLEXWLMPOLL: 060 MAXRECS: 100
EXPLICITBINDPORTRANGE: 00000-00000 IQDMULTIWRITE: NO
AUTOIQDC: ALLTRAFFIC
AUTOIQDX: ALLTRAFFIC ADJUSTDVIPAMSS: AUTO
WLMPRIORITYQ: NO .
.
.
.
SMFSRV: NO
ZERTSRV: NO
END OF THE REPORT

Netstat devlinks OSA Interface with IQDC (part 1)
D TCPIP,TCPCS3,N,DEVLINKS,INTFNAME=QDIO4103L
INTFNAME: QDIO4103L INTFTYPE: IPAQENET INTFSTATUS: READY
PORTNAME: QDIO4103 DATAPATH: 0E36 DATAPATHSTATUS: READY
CHPIDTYPE: OSD SMCR: DISABLED (GLOBALCONFIG NOSMCR)
PNETID: ZOSNET SMCD: DISABLED (GLOBALCONFIG NOSMCD)
TRLE: QDIO103
SPEED: 0000001000
IPBROADCASTCAPABILITY: NO
VMACADDR: 420001AA0E36 VMACORIGIN: OSA VMACROUTER: ALL
SRCVIPAINTF: VIPA4813L
ARPOFFLOAD: YES ARPOFFLOADINFO: NO
CFGMTU: NONE ACTMTU: 8992
IPADDR: 172.16.1.3/16
VLANID: 401 VLANPRIORITY: DISABLED
DYNVLANREGCFG: NO DYNVLANREGCAP: YES
READSTORAGE: GLOBAL (4096K)
INBPERF: DYNAMIC
WORKLOADQUEUEING: YES
CHECKSUMOFFLOAD: YES SEGMENTATIONOFFLOAD: NO
SECCLASS: 255 MONSYSPLEX: NO
ISOLATE: NO OPTLATENCYMODE: NO
… netstat output continues…

Netstat devlinks OSA Interface with IQDC (part 2)
…. Continued…
MULTICAST SPECIFIC:
MULTICAST CAPABILITY: YES
GROUP REFCNT SRCFLTMD
----- ------ --------
224.0.0.1 0000000001 EXCLUDE
SRCADDR: NONE
INTERFACE STATISTICS:
BYTESIN = 0
INBOUND PACKETS = 0
INBOUND PACKETS IN ERROR = 0
INBOUND PACKETS DISCARDED = 0
INBOUND PACKETS WITH NO PROTOCOL = 0
BYTESOUT = 316
OUTBOUND PACKETS = 1
OUTBOUND PACKETS IN ERROR = 0
OUTBOUND PACKETS DISCARDED = 0
ASSOCIATED IQD CONVERGED INTERFACE: EZAIQCE0 IQC STATUS: READY
BYTESIN = 1002
INBOUND PACKETS = 3
BYTESOUT = 668
IPV4 LAN GROUP SUMMARY
LANGROUP: 00001
NAME STATUS ARPOWNER VIPAOWNER
---- ------ -------- ---------
QDIO4103L ACTIVE QDIO4103L YES
1 OF 1 RECORDS DISPLAYED
END OF THE REPORT

D TCPIP,TCPCS1,N,DEVL,INTFNAME=EZAIQCE0
INTFNAME: EZAIQCE0 INTFTYPE: IPAQIQDC
INTFSTATUS: READY
DATAPATH: 0E0E DATAPATHSTATUS: READY
CHPIDTYPE: IQD CHPID: E0
PNETID: ZOSNET
TRLE: IUTIQCE0
READSTORAGE: MAX (2048K)
IQDMULTIWRITE: DISABLED
MULTICAST SPECIFIC:
MULTICAST CAPABILITY: NO
BYTESIN = 725955474
INBOUND PACKETS = 124553
BYTESOUT = 9674459
END OF THE REPORT
Netstat Devlinks IQDC Interface

D TCPIP,TCPCS1,N,ARP
QUERYING ARP CACHE FOR ADDRESS 172.16.1.5
INTERFACE: EZAIQCE0 IPAQIQDC: 420001AA0E3A
INTERFACE: EZAIQCE0 IPAQIQDC: 420001AA0E3A
INTERFACE: EZAIQCE0 IPAQIQDC: 420001AA0E36
END OF THE REPORT
Netstat ARP
Local (home) IP
address and source
MAC for this interface
(IQDC interface).
Remote IP addresses
and destination MAC
addresses for peer
hosts that are
reachable over IQDC

Netstat ND
d tcpip,tcpcs2,n,nd
QUERY NEIGHBOR CACHE FOR 2001:DB8:10::81:1:1
INTFNAME: QDIO6105 INTFTYPE: IPAQENET6 IQC: EZ6IQCE0
LINKLAYERADDR: 620002AA0E36 STATE: REACHABLE
TYPE: HOST ADVDFLTRTR: NO
QUERY NEIGHBOR CACHE FOR FE80::16:1:3
INTFNAME: QDIO6105 INTFTYPE: IPAQENET6 IQC: EZ6IQCE0
INTFNAME: EZ6IQCE0 INTFTYPE: IPAQIQDC6
QUERY NEIGHBOR CACHE FOR FE80::16:1:3
INTFNAME: EZ6IQCE0 INTFTYPE: IPAQIQDC6
LINKLAYERADDR: 620002AA0E36 STATE: STALE
INTFNAME: EZ6SAMEMVS INTFTYPE: MPCPTP6
LINKLAYERADDR: 000000000000 STATE: REACHABLE
END OF THE REPORT
Link local (home) IP
address and source
MAC for this interface
(IQDC IPv6 interface).
Remote IPv6 address
and destination MAC
address for peer host
that is reachable over
IQDC

D NET,ID=IUTIQCE0,E
IST097I DISPLAY ACCEPTED
IST075I NAME = IUTIQCE0, TYPE = TRLE 171
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = LEASED , CONTROL = MPC , HPDT = YES
IST1954I TRL MAJOR NODE = ISTTRL
IST1715I MPCLEVEL = QDIO MPCUSAGE = SHARE
IST2263I PORTNAME = ***NA*** PORTNUM = N/A OSA CODE LEVEL = *NA*
IST2337I CHPID TYPE = IQD CHPID = E0 PNETID = ZOSNET
IST2319I PHYSICAL CHANNEL ID = 00E0
IST1577I HEADER SIZE = 4096 DATA SIZE = 16384 STORAGE = ***NA***
IST1221I WRITE DEV = 0E0D STATUS = ACTIVE STATE = ONLINE
IST1577I HEADER SIZE = 4092 DATA SIZE = 0 STORAGE = ***NA***
IST1221I READ DEV = 0E0C STATUS = ACTIVE STATE = ONLINE
IST924I -------------------------------------------------------------
IST1221I DATA DEV = 0E0E STATUS = ACTIVE STATE = N/A
IST1724I I/O TRACE = OFF TRACE LENGTH = *NA*
IST1717I ULPID = TCPCS1 ULP INTERFACE = EZAIQCE0
IST2310I ACCELERATED ROUTING DISABLED
IST2331I QUEUE QUEUE READ QUEUE
IST2332I ID TYPE STORAGE STATUS
IST2205I ------ -------- --------------- ----------------------
IST2333I RD/1 PRIMARY 2.0M(126 SBALS) ACTIVE
IST2305I NUMBER OF DISCARDED INBOUND READ BUFFERS = 0
IST2386I NUMBER OF DISCARDED OUTBOUND WRITE BUFFERS = 0
.
.
.
VTAM; Display the TRLE (IQDC Device)

D TCPIP,TCPCS1,N,DEVL,PNETID=ZOSNET
IEF196I IEF237I 054B ALLOCATED TO SYS00076
INTFNAME: QDIO4103L INTFTYPE: IPAQENET
TRLE: QDIO103 CHPID: C4 PCHID: 01C4 CHPIDTYPE: OSD
PORTNAME: QDIO4103 SMCR: DISABLED (GLOBALCONFIG NOSMCR)
DATAPATH: 0E36 VLANID: 401 SMCD: DISABLED (GLOBALCONFIG NOSMCD)
VMACADDR: 420001AA0E36
INTFNAME: EZAIQCE0 INTFTYPE: IPAQIQDC ASSOCIATED: YES
TRLE: IUTIQCE0 CHPID: E0 VCHID: 010C
DATAPATH: 0E0E
END OF THE REPORT
NetStat; Display all devices with a specific PNetID
Note that the HSCI (IQDC)
display does not include the
IQDC VMAC or VLAN ID since
they are the same as the
associated OSA.

HSCI Product Externals (NMI/SMF)
NMI updates:
Ø Get Profile (show the new AUTOIQDC parameter).
Ø GetIfs (indicate if there is an associated IQDC interface and what its name is. The dynamic IQDC interface is
also displayed as a record.
Ø GetIfStats (show byte/packet counts for the interface that actually use the IQDC interface. The dynamic IQDC
interface is also displayed as one of the interfaces.
Ø GetIfStatsExtended (shows the IQDC interface and the associated data device).
SMF updates:
Ø TCP/IP Profile Event Record (subtype 4):
reflect the new GLOBALCONFIG statement parameters.
Ø Interface statistics record (subtype 6):
› return information about the IQDC interfaces (i.e. similar to what is provided for layer 3
HiperSockets interfaces).
› OSD interfaces:
– will also contain the associated IQDC interface if being used.
– inbound and outbound byte and unicast packet counts that went over the associated IQDC
interface.
TCPIPCS and SNMP updates:
Ø See speaker notes page for TCPIPCS subcommand and SNMP updates

Diagnosis: IQDC Interface Does not Activate
Ø Verify your HCD IQD configuration:
› IQD CHPID is defined with External Bridged and
› PNetID that matches your OSA(s) PNetID (see backup charts)
› Verify you have defined enough channel devices (recommend 101) and
the devices are online to this z/OS
› Verify the VTAM TRLE (IQDC) was built (D NET,TRL)
Ø Verify your OSA config (for each applicable OSA CHPID):
› HCD: OSA PNetID matches your IQD PNetID (see backup charts)
› TCP/IP profile: AUTOIQDC setting, OSA is defined with INTERFACE
and VMAC (OSA-generated)
Ø Tip: Activation Sequence:
OSA interface must be started after your IQD (HCD) configuration
is activated (eligible IQD devices are active and online)
1. The number of required IQD channel devices per TRLE: Two devices (read/write are required for control + one
additional devicr per TCP/IP stack, up to 8 stacks for a total of 10 devices per TRLE. A TRLE is created for each IP
version (up to 2 TRLEs). TRLEs are created for each unique IQD CHPID (PNetID). Also see the notes page.

Diagnosis: IQDC Interface is active but it is not being used
Ø Verify the peer (same CPC) host is:
› active and using the same IQD CHPID (CHID) and this IQD CHID is configured (in
HCD) with External Bridge
› When Linux is the peer host then verify that Linux is Bridge Eligible
Note, in order for Linux to be Bridge Eligible:
– When Linux is executing in a native LPAR it is Bridge Eligible by default (z14 only).
– When Linux is executing as a z/VM guest, the guest must be configured with QDIO Assist
(in order to be Bridge Eligible).
› When z/OS is the peer host:
z/OS peer is configured with IQDC
› configured to use the same IP subnet and VLAN
› Displayed in your IQDC ARP or ND cache (netstat ARP / ND)
› Reachable via Ping
Ø Tip: some “large” outbound transmissions will flow over OSA if the frame is too large (e.g.
OSA is using jumbo frames and IQD is using 8k MTU which is a 16k IQD MFS).
Recommend using 24k (or larger) for the IQD Maximum Frame size (MFS) in HCD.
Also check your setting of AUTOIQDC ALLTRAFFIC (vs. NOLARGEDATA)

Things to think about
1. PNetID “rules” for OSA and HS with and without HSCI (AUTOIQDC) and how this might impact
SMC usage
(Note. See PNetID topic on charts 28, 29 and backup PNetID display charts)
2. A single IQDC interface (channel device) is used per PNetID (for all associated OSAs) per stack
per IP version.
3. Recommend reviewing the TCP/IP Configuration Guide (HSCI Topic)
4. The IQDC interface uses each associated OSA’s VMAC (and optional VLAN ID when configured
in TCP/IP) on the IQD “internal LAN”.
Understanding this will help the administrator understand each association when multiple OSAs
are in use.
5. The upper software layers of TCP/IP only see an OSA interface, the IP route(s), IP
address/subnet, MTU, etc. is OSA (IQDC is not visible).
6. Migration, when using IQDC for z/OS to z/OS, then both (all) z/OS instances must be 2.3.
7. For SYSPLEX, the HSCI function is N/A to DYNXCF HS (i.e. XCF HS is not affected or changed
by HSCI). See DYNXCF usage considerations on the notes page.
8. Enterprise Extender traffic also (transparently) exploits HSCI.
9. Packet Trace: Packets are traced as if flowing over the associated OSA. Inbound packets will
have an IQDC flag. Outbound packets will not have flag (traced before the IQDC decision).

Backup
Topics:
Ø z/OS and Netstat PNetID displays
Ø QDIO Accelerator and HSCI

D PCIE (PFIDs that are in use)
D PCIE
IQP022I 12.14.22 DISPLAY PCIE 691
PCIE 0010 ACTIVE
PFID DEVICE TYPE NAME STATUS ASID JOBNAME PCHID VFN
00000005 10GbE RoCE Express ALLC 0038 VTAMCS 0100 0005
00000001 10GbE RoCE Express ALLC 0038 VTAMCS 0184 0001
00000500 ISM ALLC 0038 VTAMCS 07E0 0001
00000501 ISM ALLC 0038 VTAMCS 07E0 0002
00000502 ISM CNFG 07E0 0003
00000503 ISM CNFG 07E0 0004
00000504 ISM CNFG 07E0 0005
00000600 ISM ALLC 0038 VTAMCS 07E1 0001
00000601 ISM ALLC 0038 VTAMCS 07E1 0002
00000602 ISM CNFG 07E1 0003
00000603 ISM CNFG 07E1 0004
00000604 ISM CNFG 07E1 0005
Display PCIE shows the ISM PFIDs that are now allocated to VTAM (ALLC):
Note. If you display a specific FID additional detail is provided including the configured PNetID value.

Displaying the Configured PNetIDs for Channel Devices
OSD CHPID:
d m=chp(16)
IEE174I 11.20.44 DISPLAY M 612
CHPID 16: TYPE=11, DESC=OSA DIRECT EXPRESS, ONLINE
DEVICE STATUS FOR CHANNEL PATH 16
0 1 2 3 4 5 6 7 8 9 A B C D E F
0096 + + + + + + + + + + + + . . . +
SWITCH DEVICE NUMBER = NONE
PHYSICAL CHANNEL ID = 01C0
PNETID 1 = P1
************************ SYMBOL EXPLANATIONS ************************
+ ONLINE @ PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST
* PHYSICALLY ONLINE $ PATH NOT OPERATIONAL
IQD CHPID:
d m=chp(21)
IEE174I 11.21.19 DISPLAY M 615
CHPID 21: TYPE=24, DESC=INTERNAL QUEUED DIRECT COMM, ONLINE
DEVICE STATUS FOR CHANNEL PATH 21
0 1 2 3 4 5 6 7 8 9 A B C D E F
0FD1 + + + + + + + + + + + + + + + +
SWITCH DEVICE NUMBER = NONE
ATTRIBUTES = MFS(24KB)
PNETID = P2
************************ SYMBOL EXPLANATIONS ************************
+ ONLINE @ PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST
* PHYSICALLY ONLINE $ PATH NOT OPERATIONAL

Displaying the Configured PNetIDs for PCI Devices
RoCE PFID:
d pcie,pfid=5
PCIE 0010 ACTIVE
PFID DEVICE TYPE NAME STATUS ASID JOBNAME CHID VFN
00000005 10GbE RoCE Express CNFG 0100 0005
CLIENT ASIDS: NONE
PNetID 1: P1
PNetID 2: P1
ISM PFID:
d pcie,pfid=500
PCIE 0010 ACTIVE
PFID DEVICE TYPE NAME STATUS ASID JOBNAME CHID VFN
00000500 ISM CNFG 07E0 0001
CLIENT ASIDS: NONE
PNetID 1: P1

Netstat Devlinks all PNetIDs
Netstat DEvlinks/-d PNETID * shows a summary of all the active interfaces that have a PNetID
configured organized by PNetID value:
D TCPIP,TCPIP2,NETSTAT,DEVLINKS,PNETID=*
EZD0101I NETSTAT CS V2R3 TCPIP2 881
PNETID: P2
INTFNAME: IQDIOINTF6 INTFTYPE: IPAQIDIO6
INTFNAME: IQDIOLNK0A0F0217 INTFTYPE: IPAQIDIO
INTFNAME: EZAISM01 INTFTYPE: ISM ASSOCIATED: YES
PNETID: P1
INTFNAME: V6OSD1 INTFTYPE: IPAQENET6
INTFNAME: OSD1 INTFTYPE: IPAQENET
INTFNAME: EZARIUT10003 INTFTYPE: RNIC ASSOCIATED: YES
END OF THE REPORT

Netstat Devlinks specific PNetID
Netstat DEvlinks/-d PNETID <pnetid> shows details of the all active interfaces that have a PNetID
configured for a specific PNetID value:
D TCPIP,TCPIP2,NETSTAT,DEVLINKS,PNETID=P2
INTFNAME: IQDIOINTF6 INTFTYPE: IPAQIDIO6
TRLE: IUTIQDIO CHPID: 21 VCHID: 07E3
DATAPATH: FD12 VLANID: NONE SMCD: YES
INTFNAME: IQDIOLNK0A0F0217 INTFTYPE: IPAQIDIO
TRLE: IUTIQDIO CHPID: 21 VCHID: 07E3
DATAPATH: FD12 VLANID: NONE SMCD: YES
TRLE: IUT00605 PFID: 0605 VCHID: 07E1
GIDADDR: 09008586C9172964
END OF THE REPORT

Netstat DEvlinks/-d for a SMCD-enabled OSD interface
D TCPIP,TCPIP2,NETSTAT,DEVLINKS,INTFNAME=OSD1
INTFNAME: OSD1 INTFTYPE: IPAQENET INTFSTATUS: READY
PORTNAME: HYDRA960 DATAPATH: 0962 DATAPATHSTATUS: READY
CHPIDTYPE: OSD SMCR: YES
PNETID: P1 SMCD: YES
SPEED: 0000001000
VMACADDR: 0200014860B0 VMACORIGIN: OSA VMACROUTER: ALL
ARPOFFLOAD: YES ARPOFFLOADINFO: YES
IPADDR: 10.15.1.21/24
.
.
.
ASSOCIATED RNIC INTERFACE: EZARIUT10001
ASSOCIATED ISM INTERFACE: EZAISM02
LANGROUP: 00002
---- ------ -------- ---------
OSD1 ACTIVE OSD1 YES
END OF THE REPORT
Shows the PNETID and the associated RNIC and ISM interfaces:

Netstat DEvlinks/-d for a SMCD-enabled IQD interface
D TCPIP,TCPIP2,NETSTAT,DEVLINKS,INTFNAME=IQD1
INTFNAME: IQD1 INTFTYPE: IPAQIDIO INTFSTATUS: READY
TRLE: IUTIQ421 DATAPATH: FD12 DATAPATHSTATUS: READY
CHPID: 21
IPADDR: 10.15.2.21/24
VLANID: 200
READSTORAGE: GLOBAL (3008K)
SECCLASS: 255 MONSYSPLEX: NO
IQDMULTIWRITE: DISABLED
MULTICAST SPECIFIC:
MULTICAST CAPABILITY: YES
GROUP REFCNT SRCFLTMD
----- ------ --------
224.0.0.1 0000000001 EXCLUDE
SRCADDR: NONE
BYTESIN = 0
INBOUND PACKETS = 0
BYTESOUT = 0
END OF THE REPORT
Shows the PNETID and the associated ISM interface:

Netstat DEvlinks/-d for a SMCD-enabled OSD interface
D TCPIP,TCPIP2,NETSTAT,DEVLINKS,INTFNAME=OSD1
INTFNAME: OSD1 INTFTYPE: IPAQENET INTFSTATUS: READY
PORTNAME: HYDRA960 DATAPATH: 0962 DATAPATHSTATUS: READY
CHPIDTYPE: OSD SMCR: YES
SPEED: 0000001000
VMACADDR: 0200014860B0 VMACORIGIN: OSA VMACROUTER: ALL
IPADDR: 10.15.1.21/24
.
.
.
ASSOCIATED RNIC INTERFACE: EZARIUT10001
LANGROUP: 00002
---- ------ -------- ---------
OSD1 ACTIVE OSD1 YES
END OF THE REPORT
Shows the PNETID and the associated RNIC and ISM interfaces:

Background information: QDIO Accelerator
§ Provides fast path IP forwarding for these
DLC combinations
Inbound QDIO, outbound QDIO or HiperSockets
Inbound HiperSockets, outbound QDIO or
HiperSockets
§ Sysplex Distributor (SD) acceleration
Inbound packets over HiperSockets or OSA-E
QDIO
When SD gets to the target stack using either
• Dynamic XCF connectivity over HiperSockets
• VIPAROUTE over OSA-E QDIO
§ Improves performance and reduces processor
usage for such workloads
DLC
IP
TCP/UDP
Application
DLC
IP
TCP/UDP
Application
IP-layer
routing table
Connection
routing table
DLC
IP
TCP/UDP
Application
DLC
IP
TCP/UDP
Application
OSAOSA OSA
DLC
IP
TCP/UDP
Application
DLC
IP
TCP/UDP
ApplicationShadow copies
of selected
entries in
Connection
routing table
and IP-layer
routing table
DLC
IP
TCP/UDP
Application
DLC
IP
TCP/UDP
Application
OSAOSA OSA
QDIO Accelerator with HSCI now supports inbound layer 2 traffic over IQDC,
but only transmits outbound using layer 3 (i.e. over OSA rather than IQDC)!

Diagnostic Information (Packet trace and IPCS samples)

Inbound IQDC Packet Trace
19 MVS161 PACKET 00000004 10:45:48.203750 Packet Trace
From Interface : QDIO6103 Device: QDIO Ethernet6 Full=80
Tod Clock : 2018/02/05 10:45:48.203750 Intfx: 137
Segment # : 0 Flags: In IQDC
Source : 2001:db8:172::16:1:5
Destination : 2001:db8:172::16:1:3
Source Port : 21 Dest Port: 1024 Asid: 0036 TCB: 0000000
QID : 1
IpHeader: Version : 6 Header Length: 40
Class: : 00 Flow: 000000
Payload Length : 40
Hops : 255 Protocol: TCP
Source : 2001:db8:172::16:1:5
Destination : 2001:db8:172::16:1:3
TCP
Source Port : 21 (ftp) Destination Port: 1024 ()
Sequence Number : 736146897 Ack Number: 2473635293
Header Length : 40 Flags: Ack Syn
Window Size : 65535 CheckSum: 45C4 FFFF Urgent Data Pointer:
Option : Max Seg Size Len: 4 MSS: 1432
Option : NOP
Note. There is no IQDC flag set for outbound flows for IP packets as packet trace occurs before low level decision
is made to use IQDC. Outbound flags are added to ARP and ND outbound packets.

Outbound ND (Neighbor Solicitation) Packet trace
To Interface : QDIO6103 Device: QDIO Ethernet6 Full=72
Tod Clock : 2018/02/05 10:45:48.200578 Intfx: 137
Segment # : 0 Flags: Out IQDCND
Source : 2001:db8:172::16:1:3
Destination : ff02::1:ff01:5
Asid: 0038 TCB: 007AD040
Next Hop : ff02::1:ff01:5
Class: : 00 Flow: 000000
Payload Length : 32
Hops : 255 Protocol: ICMPv6
Source : 2001:db8:172::16:1:3
Destination : ff02::1:ff01:5
ICMPv6
Type/Code : 87/0 Neighbor Solicitation
CheckSum : A82C FFFF
Target : 2001:db8:172::16:1:5
Option : Source LinkAddr Length: 8
Link-Layer Addr : 620002AA0E36

Inbound ND (Neighbor Advertisement) Packet trace
From Interface : QDIO6103 Device: QDIO Ethernet6 Full=72
Tod Clock : 2018/02/05 10:45:48.202624 Intfx: 137
Segment # : 0 Flags: In IQDCND
Source : fe80::16:1:5
Destination : 2001:db8:172::16:1:3
Asid: 0036 TCB: 00000000
QID : 1
Class: : 00 Flow: 000000
Payload Length : 32
Hops : 255 Protocol: ICMPv6
Source : fe80::16:1:5
Destination : 2001:db8:172::16:1:3
ICMPv6
Type/Code : 88/0 Neighbor Advertisement
CheckSum : 4696 FFFF
Flags : S O
Target : 2001:db8:172::16:1:5
Option : Target LinkAddr Length: 8
Link-Layer Addr : 620001AA0E3A

ip tcpipcs config tcp(tcpcs5)
IPv4 Pif@ LinkName
0000_7F7B8910 LOOPBACK
.
.
0000_7F1F9910 O6ETHN0
0000_7F1F5910 EZARIUT10001
0000_7F1F3910 EZARIUT10061
0000_7F1F1910 EZARIUT10040
0000_7F1EF910 EZARIUT1009F
0000_7F1D4910 EZAISM01
0000_7F1D2910 EZAISM02
0000_7F1D0910 EZAISM03
0000_7F1CE910 EZAISM04
0000_7F1CC910 EZAISM05
0000_7F195910 O6ETHN0V80
0000_7F193910 O6ETHN0V112
0000_7F191910 O6ETHC0
0000_7F18F910 O6ETHC1
0000_7F18D910 O6ETHD0
0000_7F18B910 EZAIQC29

EZAIQC29 (IQDC) PIF@
7F18B910 D7C9C640 00000000 00000000 7F18D910 | PIF ........".R. |
7F18B920 00000000 7F18A910 00000000 7F18D910 | ....".z.....".R. |
7F18B930 00000000 7F18A910 00000000 00000000 | ....".z......... |
7F18B940.:7F18B95F. LENGTH(X'20')--All bytes contain X'00'
7F18B960 00000000 00000000 00000000 7F18C010 | ............".{. |
7F18B970 00000000 00000000 D5020802 00000000 | ........N....... |
7F18B980 00000000 00000000 C9C6C3C9 D6C3E3D3 | ........IFCIOCTL |
7F18B990 D70000D0 00000000 00000306 00000005 | P..}............ |
7F18B9A0 D3EC84E9 0CAFBAA0 C5E9C1C9 D8C3F2F9 | L.dZ....EZAIQC29 |
7F18B9B0 40404040 40404040 C5E9C1C9 D8C3F2F9 | EZAIQC29 |
7F18B9C0 40404040 40404040 00002320 00000000 | ........ |
7F18B9D0 80088000 00000099 00000000 00000000 | .......r........ |
7F18B9E0 D3EC84E7 B2D85AA4 00000000 0022000C | L.dX.Q!u........ |
7F18B9F0 00000020 00000000 00000000 00000100 | ................ |
7F18BA00 00000000 00000000 01000000 00000000 | ................ |
7F18BA10.:7F18BA3F. LENGTH(X'30')--All bytes contain X'00’
.
.
7F18BEF0 00000000 00000000 00000000 7F18D910 | ............".R. |
7F18BF00 00000000 7F193910 00000000 00000000 | ...."........... |
7F18BF10.:7F18BF1F. LENGTH(X'10')--All bytes contain X'00'
Head @ of associated OSDs (phy_osxs)
Tail @ of associated OSDs

ARP Tree for PIF EZAIQC29 at 00000000_7F18B910
Tree root Header at 0000_7F18B530
Instance : 61
Total elements : 31
Deleted elements : 20
Rebuild count : 0
Maximum key length : 5 bytes
Rebuild threshold : 20
Rebuild time : 1900/01/01
00:00:00.000000
Node@ Bit Parent LChild RChild Key Element Status KeyValue
0000_7AD836E0 31 0000_7EFC81E0 0000_7EFBE220 0000_7AD836E0 0000_7EB5F170 0000_7D946B10 Active 100B2069 00
0000_7EFC6720 29 0000_7EFC81A0 0000_7EFC81A0 0000_7EFC6720 0000_7EB5EE50 0000_7D947C10 Active 100B216D 00
0000_7AD854E0 24 0000_7EFC81A0 0000_7EFC4EE0 0000_7AD854E0 0000_7EB5EE30 0000_7D946110 Active 100B2085 00
0000_7EFC81E0 30 0000_7EFC4EE0 0000_7AD836E0 0000_7EFC81E0 0000_7EB5EC98 0000_7D945B10 Active 100B206A 00
0000_7EFC81A0 23 0000_7EFBE220 0000_7AD854E0 0000_7EFC6720 0000_7EB5EE08 0000_7D947210 Active 100B2169 00
0000_7EFC5A60 31 0000_7EFC5A20 0000_7EFC5A20 0000_7EFC5A60 0000_7EB5ED50 0000_7AD7F830 Active 100B206D 00
0000_7EFC5A20 30 0000_7EFC4EE0 0000_7EFC5A60 0000_7EFC4EE0 0000_7EB5ED88 0000_7D946610 Active 100B206C 00
0000_7EFC59E0 29 0000_7EFBE260 0000_7EFC8160 0000_7EFC59E0 0000_7EB5EC68 0000_7D946F10 Active 100B706C 00
0000_7EFC4EE0 29 0000_7AD854E0 0000_7EFC81E0 0000_7EFC5A20 0000_7EB5ED80 0000_7D947510 Active 100B206E 00
0000_7EFBE260 17 0000_7EFBE1E0 0000_7EFBE220 0000_7EFC59E0 0000_7EB5EC50 0000_7EA152F0 Active 100B7068 00
0000_7EFBE220 18 0000_7EFBE260 0000_7EFBF1A0 0000_7EFC81A0 0000_7EB5EC48 0000_7EA153F0 Active 100B2068 00

z/OS 2.3 HiperSockets Converged Interface (HSCI) support

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to z/OS 2.3 HiperSockets Converged Interface (HSCI) support

Similar to z/OS 2.3 HiperSockets Converged Interface (HSCI) support (20)

More from zOSCommserver

More from zOSCommserver (9)

Recently uploaded

Recently uploaded (20)

z/OS 2.3 HiperSockets Converged Interface (HSCI) support