跳转到主内容

无法使用 NVMe/TCP 创建子系统

  1. 最后更新
  2. 另存为PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

适用于

  • Ontap 9
  • Trident
  • Openshift

问题

  • 无法使用 NVMe/TCP 创建子系统。
  • 来自 Openshift 集群（RedHat）在多个 POD 上报告的日志片段：
MapVolume.SetUpDevice failed for volume "pvc-b50447d9-c91b-4be1-ac87-b4ee005e5xxx" : rpc error: code = Internal desc = failed to stage volume: failed to connect subsystem nqn.1992-08.com.netapp:sn.a4e4eee357d911efa9ebd039ea5bxxxx:subsystem.s_trident_pvc_b50447d9_c91b_4be1_ac87_b4ee005e59xx to 10.216.2.5: exit status 1; failed to connect subsystem
 
  • ONTAP 上报告的日志事件：
DEBUG  nvmf.spdk.err: NVMe/TCP controller limits reached on this node. Queue slots provisioned 69568, additional queue slots requested:128, currently supported queue slots:69632.
No more NVMe connects via NVMe/TCP LIFs on this node are allowed.
 
  •  遇到大量 RWX（Read Write Many，可安装在多个节点上）卷的规模限制
  • 无法扩展到所需的 RWX 卷数量
  • 由于使用了每个节点的子系统，因此对 RWO 卷没有影响

    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.