Monitoring

NetApp E/EF-Series

To monitor your NetApp E/EF-Series devices with LogicMonitor, you will need to download, install, and configure SANtricity Web Services Proxy 1.3:

All of the OS options for running the Web Services Proxy are equally supported for monitoring E-Series via LogicMonitor. Steps 1-6 are NetApp-specific:

1. Once you have the Proxy installed, verify that you can reach the API by loading the built-in documentation page (change the IP for your environment):

http://10.0.0.1:8080/docs/rest/index.html

2. The NetApp E-Series datasources require a Basic Authentication username and password combination for the collector to access the API. The datasources only make GET requests and thus only need read privileges.

By default, users “rw” and “ro” are created with read-write and read-only privileges respectively. The password for each account is the same as the username. If you would like to make a new account, find the root of the SANtricity Web Services Proxy installation on your OS:

Default locations:

  • 
Linux: /opt/netapp/webservice

  • Windows: C:\Program Files\NetApp\SANtricity Web Services Proxy

From there, navigate to data/config and edit the file called users.properties.

Add a line for the username and password you want to add. You will add the password in plaintext initially. Here’s an example with our new entry for LogicMonitor at the bottom:

#
#Tue May 24 15:09:09 PDT 2016
admin=MD5\:21232f297a57a5a743894a0e4a801fc3,admin
ro=MD5\:3605c251087b88216c9bca890e07ad9c,storage.ro
rw=MD5\:038c0dc8a958ffea17af047244fb6960,storage.rw
lm=thisisyoursecretpassword,storage.ro

 

Now, navigate back to the Web Services Proxy installation files and run the securepasswds EXE or JAR (depending on your OS). It will modify the users.properties file so that your password is hashed like the existing users. You don’t have to pass any arguments to it, just run it, it will find the new entry and generate the hash, see below: 

#
#Tue May 24 15:22:50 PDT 2016
admin=MD5\:21232f297a57a5a743894a0e4a801fc3,admin
ro=MD5\:3605c251087b88216c9bca890e07ad9c,storage.ro
lm=MD5\:655bcb576646dbb0e1d7b63a880dfd66,storage.ro
rw=MD5\:038c0dc8a958ffea17af047244fb6960,storage.rw

 

3. Navigate back to the built-in web-based documentation page: http://10.0.0.1:8080/docs/rest/index.html

4. Scroll down to the line labelled Storage-Systems and click Show/Hide.

5. Now we’ll need to register your array(s) with the Web Services Proxy. You will need the IP addresses of your arrays (you only need one of the IPs for each). You can use the POST /storage-systems endpoint to do this conveniently from the built-in API documentation page, or with curl. You will need to pass a JSON object that looks like the following, of course, with the IP addresses changed to match your environment:

{
  "controllerAddresses": [
    "10.0.0.31"
  ]
}

 

If you have a lot of arrays and need to automate this, here’s a curl snippet to get you started:

URL="https://:/devmgr/v2/storage-systems"
curl --request POST --cookie "cookies.txt" \
     --header "Accept: application/json" --header "Content-Type: application/json" \
     --data '{"controllerAddresses":["10.0.0.31, "10.0.0.32]} \
     --insecure $URL

 

6. If the response comes back okay, you can confirm your arrays have been registered by using the GET /storage-systems endpoint. Click the Try it out! button and you should see your arrays in the JSON results window.

7. Now you just need to make sure to apply the following system properties to your array(s) in LogicMonitor. If you have more than one array, consider putting them into a group to make it easier to applies these properties:

  • netapp.rest.user // Username for the Web Services Proxy

  • netapp.rest.pass // Password for the Web Services Proxy user

  • netapp.rest.url // The base URL for the Web Services Proxy (https://hostname:8443)

system.categories should include SANtricityWebServices so that the datasources are properly applied. This will be done automatically via a PropertySource for models 2800 and newer, as long as the proper credentials are configured, or the default credentials are still valid.

You should now start seeing data for your NetApp E-Series devices.