SMC-Rv2

SMC-Rv2 defines the updates to the SMC-R protocol allowing SMC-Rv2 enabled hosts to connect and communicate over multiple IP subnets. SMC-Rv2 uses the RoCEv2 protocol also known as "routable RoCE". SMC-Rv2 connection eligibility is defined by the Enterprise ID. SMC-Rv2 peer hosts must define a common EID. SMC-Rv2 preserves many of the architectural concepts of SMC-R, such as supporting TCP sockets, dynamically creating SMC-Rv2 connections from the TCP/IP connection and preserving many of the related TCP quality of services such as the network administrative model, TCP connection load balancer compatibility, and TCP connection (TLS) security.

Some of the key differences of SMC-Rv2 are related to IP connectivity, such as provisioning an IP address to the RoCE interface and the reliance on your IP routing definitions (static or dynamic) and your IP topology (IP routes, routers, firewalls, etc.). In most cases your existing IP routing definitions will be sufficient. For high availability, it is strongly recommended that users define multiple equal cost routes between hosts exploiting SMC-Rv2.

Your RoCEv2 network high availability reuses your existing IP network high availability methodology. SMC-Rv2 continues to provide high availability through the SMC-Rv2 link group architecture using multiple links for load balancing and high availability.

SMC-R does not support IPSec. TCP connections that require IPSec are not eligible for SMC-Rv2 or SMC-Rv1. SMC-R network traffic supports connection level security such as TLS or AT-TLS.