7–RoCE Configuration
Configuring RoCE on the Adapter for Windows Server
142
BC0154501-00 P
Requestor
remote
operation
Remote side could not complete the
operation requested due to a local
issue.
Yes
Yes
A software issue at the
remote side (for exam-
ple, one that caused a
QP error or a mal-
formed WQE on the
RQ) prevented opera-
tion completion.
Requestor
retry
exceeded
Transport retries have exceeded the
maximum limit.
Yes
Yes
The remote peer may
have stopped respond-
ing, or a network issue
is preventing messages
acknowledgment.
Requestor
RNR
Retries
exceeded
Retry due to RNR NAK received
have been tried the maximum num-
ber of times without success.
Yes
No
The remote peer may
have stopped respond-
ing, or a network issue
is preventing messages
acknowledgment.
Responder
CQE
flushed
Posted work requests (receive buf-
fers on RQ) may be flushed by send-
ing completions with a flush status to
the CQ if the QP moves to an error
state for any reason, and pending
receive buffers exist on the RQ. If a
work request completed with an
error status, all other pending work
requests for that QP are flushed.
Yes
Yes
—
Responder
local
length
Invalid length in inbound messages.
Yes
Yes
Misbehaving remote
peer. For example, the
inbound send mes-
sages have lengths
greater than the receive
buffer size.
Responder
local
protection
The locally posted work request’s
data segment does not reference a
memory region that is valid for the
requested operation.
Yes
Yes
Indicates a software
issue with memory
management.
Table 7-3. Cavium FastLinQ RDMA Error Counters (Continued)
RDMA Error
Counter
Description
Applies
to
RoCE?
Applies
to
iWARP?
Troubleshooting