Sysplex Distributor After Roce; D.2.11 Enabling Smc-R Support In Z/Os Communications Server - IBM z13s Technical Manual

Sysplex Distributor after RoCE

Figure D-10 shows a RoCE Sysplex Distributor:
The initial connection request goes through the Sysplex Distributor stack.
The session then flows directly between the client and the target over the RoCE cards.
Figure D-10 Sysplex Distributor after RoCE
Note: As with all RoCE communications, the session end also flows over OSAs.

D.2.11 Enabling SMC-R support in z/OS Communications Server

The following checklist provides a task summary for enabling SMC-R support in z/OS
Communications Server. This list assumes that you start with an existing IP configuration for
LAN access using OSD:
HCD definitions (install and configure RNICs in the HCD):
– Add the PNet ID for the current OSD.
– Define PFIDs for RoCE (with the same PNet ID).
Specify the GLOBALCONFIG SMCR parameter (TCP/IP Profile):
– Must specify at least one PCIe Function ID (PFID):
• A PFID represents a specific RNIC adapter.
• A maximum of 16 PFID values can be coded.
– Up to eight TCP/IP stacks can share a RoCE PCHID (RoCE feature) in a specific LPAR
(each stack must define a unique FID value).
Start the IPAQENET or IPAQENET6 INTERFACE with CHPIDTYPE OSD:
– SMC-R is enabled, by default, for these interface types.
– SMC-R is not supported on any other interface types.
Note: The IPv4 INTERFACE statement (IPAQENET) must also specify an IP subnet mask
Repeat in each host (at least two hosts).
Start the TCP/IP traffic and monitor it with Netstat and IBM VTAM displays.
488
IBM z13s Technical Guide