メインコンテンツへスキップ

NVMe/TCPでサブシステムを作成できません

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.

     

    • この記事は役に立ちましたか?