1 Reply Latest reply on Sep 10, 2018 6:58 PM by mrdoan

    Latest OEM13c Plug-in for NetApp Storage Systems

    mrdoan

      We have an OEM 13c environment running and we are trying to monitor our NetApp storage Systems.  It appears that the plug-in and support are only 'supported' by the NetApp community itself and I can only find reference to a plug-in agent for 12.1.0.4.0 for the NetApp system.

       

      I can say one thing, it works, EXCEPT we have component of the NetApp system which does not and we need to see if there is a newer version of the plug-in or if others have used the plug-in to monitor their NetApp Storage systems.

      The issue we have is that we CAN monitor the NetApp Cluster mode environment and 4 SVMs present on that cluster.  However there is one more SVM on the same Cluster which reports as being 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?

        • 1. Re: Latest OEM13c Plug-in for NetApp Storage Systems
          mrdoan

          Here is a bit more to the issue.

           

          I removed the SVMs from OEM and then removed the 'oemplugin' account from the SVMs as well.

          I then proceeded to add one of the working SVMs back without the account.  It showed the SVM as DOWN and returned the following error:

           

          [2018-09-10 13:27:28,795] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiAuthenticationException: Authentication to Storage System 192.168.10.101 as user oemplugin failed.  Response code: 401

           

          After adding back the 'oemplugin' account it showed the SVM as UP.

           

          When I repeated the same process on the SVM that is failing it too reported DOWN, but with a different error:

           

          [2018-09-10 13:35:43,244] [main] [ERROR] Failed to initialize Zapi runner. :com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System 192.160.10.100: Connection refused