content_image/1002757.jpg
Only minor changes are required for z/VM guests. An OS can be enabled for SMC-R and SMC-D. SMC-D is used when both peers are within the same CPC (and ISM PNet and VLAN). After the ISM HCD configuration is complete, SMC-D can be enabled in z/OS with a single TCP/IP parameter (GLOBALCONFIG SMCD). ISM FIDs must be associated with an IP network. The association is accomplished by matching PNet IDs (for example, HiperSockets and ISM). 

Note:  ISM FIDs must be associated with HiperSockets or with an OSA adapter by using a PNet ID. It cannot be associated to both. 

## D.3.10 SMC-D over ISM prerequisites 

SMC-D over ISM features the following prerequisites: 

GLYPH<SM590000> IBM z14, z13s, or z13 (Driver 27): HMC/SE for ISM vPCI Functions. 

GLYPH<SM590000> At least two z/OS V2.2 systems (or later) in two LPARs on the same CPC with required service installed: 

– SMC-D can communicate with another z/OS V2.2 instance only and peer hosts must be on the same CPC and ISM PNet. 

– SMC-D requires an IP Network with access through OSA or HiperSockets that includes a defined PNet ID that matches the ISM PNet ID. 

GLYPH<SM590000> If running as a z/OS guest under z/VM, z/VM 6.3 with APAR VM65716, including APARs is required for guest access to RoCE (Guest Exploitation only). 

GLYPH<SM590000> Linux support is planned for a future deliverable. 

The required APARs per z/OS subsystem are listed in Table D-1. 

<img src='content_image/1002757.jpg'>

