跳转到主内容

为什么 NetApp SMI-S Provider 会针对非 SAN ONTAP 集群生成 FCPNodeName 和 iSCSINodeName 错误?

Views:
11
Visibility:
Public
Votes:
0
Category:
netapp-smi-s-provider
Specialty:
om
Last Updated:

适用场景

  • NetApp SMI-S Provider 5.2.4 及更高版本

问题解答

  • 如果在针对非 SAN ONTAP 集群的 SMI-S Provider cimserver 日志中看到如下消息:

06-Nov-2020 15:47:14.484 SEVERE  cimserver: ONTAPStatus:At ..\..\wbemontapi\utils2.c:1225 in getFCPNodeNameZAPI(): entry doesn't exist - With storage system 10.1.1.10.

06-Nov-2020 17:23:20.23 WARNING cimserver: Unable to get iSCSINodeName. Check to see if iSCSI is enabled on 10.1.1.10

     这是因为,即使您不在这些集群上使用 SAN ,它们也已获得 iSCSI 和 FCP 协议的许可。

  • 如果存在许可证, SMI-S Provider 会检查相关配置,如果无法获取这些配置,则会引发错误。因此,这是意料之中的,如果安装了许可证但未使用许可证,则可以安全地忽略此问题。

追加信息

附加信息 _text

 

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.