IBM z13s, Техническое руководство

Страница: 523 / 588

Appendix D. Shared Memory Communications
495
Figure D-16 shows an SMC-D configuration in which HiperSockets provide the connectivity.
Figure D-16 SMC-D configuration that uses HiperSockets to provide connectivity
D.3.5 Planning considerations
In the z/OS SMC-D implementation, z/OS uses a single Virtual Function (VF) per ISM PNet.
This is true for a single VLAN or for multiple VLANs per PNet (that is, the number of VLANs
that are defined for a PNet does not affect the number of VFs required).
z/OS Communications Server requires one ISM FID per ISM PNet ID per TCP/IP stack. This
requirement is not affected by the version of the IP (that is, it is true even if both IPv4 and IPv6
are used).
The following are reasons why z/OS might use extra ISM FIDs:
򐂰 IBM supports up to 8 TCP/IP stacks per z/OS LPAR. SMC-D can use up to 8 FIDs or VFs
(one per TCP/IP stack).
򐂰 IBM supports up to 32 ISM PNet IDs per CEC. Each TCP/IP stack can have access to a
PNet ID that consumes up to 32 FIDs (one VF per PNet ID).
D.3.6 Hardware configuration definitions
Complete these steps to create HCDs:
1. Configure ISM vPCI Functions (HCD/HCM).
2. Define PNet IDs (OSA, HiperSockets (IQD) and ISM) in HCD/HCM.
3. Activate the definition using HCD.
IP Subnet ‘A’
z/OS A (LP 1) z/OS B (LP 2)
System z 13 GA2 or z13s
ISM Network (PNet X)
IQD IQD
IQD IQD
PR/SM
IQD VCHID (PNet X)
ISM ISM
ISM ISM
IP Interface A.1
IP Interface A.2
VCHID X
ISM Network ‘X’
becomes a “logical
extension” of the
internal Layer 2
Network ‘X’ (IQD
Network ‘X’)
Each host has an IP
network interface /
connection to a Layer 2
Network (with a defined
PNet ID) associated with
IP subnet ‘A’
PNet X could be an
external LAN or an internal
HS Network (IQD VCHID
with PNet X)
PNet X PNet X
Both hosts use the same IP subnet
ISM Network (PNet X)