Skip to main content
NetApp Knowledge Base

NVMe RDMA path stays connecting after rebooting E-Series controller

Views:
4
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

  • E-Series EF80
  • SANtricity OS 12.10R or earlier
  • RoCE (RDMA over Converged Ethernet)
  • NVMe over RoCE

Issue

  • Some NVMe/RDMA paths stay in connecting after a controller reboot while other paths on the same subsystem stay live
  • nvme list-subsys command shows some NVMe/RDMA paths as connecting

Example:

+- nvme6 rdma traddr=<TARGET_ADDRESS>,trsvcid=4420,host_traddr=<HOST_ADDRESS> live
+- nvme7 rdma traddr=<TARGET_ADDRESS>,trsvcid=4420,host_traddr=<HOST_ADDRESS> live
+- nvme8 rdma traddr=<TARGET_ADDRESS>,trsvcid=4420,host_traddr=<HOST_ADDRESS> connecting
+- nvme9 rdma traddr=<TARGET_ADDRESS>,trsvcid=4420,host_traddr=<HOST_ADDRESS> live

  • Linux host log repeats messages showing I/O queue creation is rejected:

Example:

nvme nvme8: creating 4 I/O queues.
nvme nvme8: Connect rejected: status 10 (stale conn).
nvme nvme8: rdma connection establishment failed (-104)

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.