ONTAP Discussions

OEM13c returns SVM as DOWN

steven_doan

We have a Clustered Data ONTAP envionment with several SVM.

 

We were able to add OEM to the Cluster level and to four SVMs.  THe Cluster and 3 of the 4 SVMs report to be UP and are reporting. 

One however reports as DOWN

 

In doing some digging into the OEM logs we see these errors:

[2018-08-16 14:28:48,079] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System 192.168.10.100: Connection refused
[2018-08-16 14:30:15,314] [main] [ERROR] Failed to get network interface error rate : Metric [CsNetworkInterfaceError]::com.netapp.autozapi.ApiExecutionException: Object "ifnet" was not found.
[2018-08-16 14:30:20,616] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System 192.168.10.100: Connection refused
[2018-08-16 14:30:36,089] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System 192.168.10.100: Connection refused
[2018-08-16 14:34:08,453] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System 192.168.10.100: Connection refused
[2018-08-16 14:39:17,957] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System : Connection refused
[2018-08-16 14:40:48,355] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System : Connection refused

 

We used the same method to add the user credentials for the Cluster and all four (4) SVMs so there shouldnt be any difference there, but for some reason this one SVM is refusing connection and returning these errors.

 

The error from OEM is:

The error message reported is that filer1 is unreachable over the network or is down.

 

Any suggestions?

2 REPLIES 2

Re: OEM13c returns SVM as DOWN

steven_doan

As a follow up of the four (4) SVMs we are monitoring in addition to the NetApp Cluster the only one SVM that has an issue was the one which was migrated from a 7-Mode platform using 7MTT.

 

Could there have been something inherited from 7-Mode that is preventing communication?  Is there a way to output all the configuration settings of an SVM so that we can compare the differences and potentially see if that is the cause of the communication failure?

Re: OEM13c returns SVM as DOWN

steven_doan

More details.....

 

I tried removing & re-adding the SVM using a different account, but the system still reports a connection refused message & interestingly it still references the account 'oemplugin' rather than the new one selected.

 

It also points to an issue with snapmirror details

 

[2018-09-10 10:55:07,414] [main] [ERROR] Failed to get snapmirror details for vserver: Metric[VsSnapMirror]::com.netapp.autozapi.ApiExecutionException: Insufficient privileges: user 'oemplugin' does not have read access to this resource
[2018-09-10 10:56:57,160] [main] [ERROR] Failed to get snapmirror details for vserver: Metric[VsSnapMirror]::com.netapp.autozapi.ApiExecutionException: Insufficient privileges: user 'oemplugin' does not have read access to this resource

2021 NetApp Partner Experience Survey
PES Banner
All Community Forums
Public