RoCEv2 (server)
The server receives the RoCEv2 flow and can generate congestion notifications. Compared with the client, the server does not have Targets, Rate settings (PPS), or Payload settings; the client defines the load. The RDMA command, InfiniBand MTU, and DCQCN settings are also client-side only.
- Receiver — same as for the HTTP server plugin.
- IP header (L3) — same as for the HTTP server plugin.
- Server-side RoCEv2 settings:
Table 198 — RoCEv2 server settings
| Name | Description | Value |
|---|---|---|
| Queue Pair count | Number of queues that receive RDMA traffic. If the server's QP Count is lower than the client's, packets addressed to unavailable QPs receive an NACK (Invalid Request). | Number (default: 1000) |
| CNP | Congestion Notification Packet: the server generates a CNP when incoming packets carry ECN-CE | On/off |
| CNP interval | Minimum interval between CNPs for one QP | Microseconds; available when CNP is enabled |
| PFC | Priority Flow Control (IEEE 802.1Qbb) on the NIC | On/off |
| PFC class | PFC priority class | 0–7; available when PFC is enabled |
- Reception duration — same as for the HTTP server plugin.
- Network tunnels (optional).