AUTO-ARCHIVED:Why are FCPNodeName and iSCSINodeName errors generated by NetApp SMI-S Provider against my non-SAN ONTAP clusters?

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 53

Visibility:: Internal

Votes:: 0

Category:: netapp-smi-s-provider

Specialty:: legacy

Last Updated:

Applies to

NetApp SMI-S Provider 5.2.4+

Answer

If you see messages such as the following reported in the SMI-S Provider cimserver logs against non-SAN ONTAP clusters:

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

It is because even though you are not using SAN on those clusters, they have been licensed for iSCSI and FCP protocols.

The presence of a license has SMI-S Provider check for the relevant configurations, and throw an error if it cannot obtain them. So this is expected and can be safely ignored if the licenses are installed but not being used.

Additional Information

additionalInformation_text