7 Steps - NetAPP Storage discovery Using SNMP

Here is a quick guide on how to discover netapp storage in servicenow using SNMP. I have detailed 7 step guide which will help you kick start your netapp storage discovery in servicenow. The below content is based on my implementation experince your free to comment down any corrections and quries and i would act on it accordingly...

To get started, You would need the below pre-req to be fullfilled inorder to get started with netapp storage discovery... You can also check for my complete guide on servicenow discovery Implementation pre-requisities:Servicenow Discovery Implementaion Requirement Gathering & Pre-requisites.

More Contents On Discovery :

Servicenow vCenter Discovery | Step by step Discovering VMware using vCenter Discovery.

Set Discovery Schedule name to CMDB Record (via Discovery)

Netapp Storage Discovery Pre - Requirements :

1. Source IPs or Subnets to be discovered
2. Basic Auth Creds.
3. SNMP Creds (Can be v2 or v3)
4. Port 161 UDP needs to be opened from Servicenow MIDSERVER to TARGET.
5. Make sure mibs are up-to-date in servicenow instace.
6. MID server with good configurations.

Step1 : You would needs a basic auth creds from netapp storage team which needs to be configured in servicenow as below.

Step 2 : You would also primarly need a SNMP Credentails (it can be v2 or v3) to be configured as below. The below highlited fields needs to be updated as per need.

Once saved, Test the snmp creds against the Netapp storage server IP for which you want to perform Netapp storage discovery in servicenow.

Step 3: Now ! You are ready with your connection and credentials to launch netapp discovery, before that you have to make sure that you have the device OID already defined in your servicenow instace for netapp storage discovery.

To do so, Navigate to > SNMP System OIDs

Search for 'manufacturer' as '*netapp' , see if you already have snmp oids defined for your netapp storage devices. If no entry found click on 'new' button and create a new SNMP OIDs for Netapp storage discovery.

The OIDs can be obtained from the OUTPUT of the ecc queue named as , or this can also be obtained from responsible team. (netApp storage team).

As you see below on 3rd row , you can see 'SNMP - Classify: 0 OIDs' > This means you are unable to get any info from the target.

If your able to get the OIDs lets say '535 OIDs' and still unable to create a CI (This is when you need to chekc if the received sysObjectID is added to the OID module in servicenow as shown above....)

Step 4 : Once your done with the OID checks, Move to Discovery Schedules > New

Create a new schedule for Netapp storage discovery as below, all the below highlited fields needs to be updated as per need...

Step 5 : Save the record , click on the 'Quick Ranges' > from the related links which will throw a pop-up asking for IPs to be discovered.

You can update the IPs or Subnets in a comma seprated string and click on > Make Ranges

Based on the number of IPs given 'Discovery IP Ranges' Records will be created. This is how you define a IP for discovering Netapp storage discovery in servicenow.

Step 6 : Before you Kickstart the discovery make sure all your previous configuration as well configured, Click on 'Discovery Now' From the schedules realted links.

Step 7 : You can check the progress by clicking on refresh and wait untill the state changes to 'Completed'.

If all the configuration as configured properly and the if the connectivity with netapp devices is perfect it must not trun out any errors in the discovery logs...

If you find the article to be useful or effective for your knowledge Kindly Consider Marking the article HELPFUL and BOOKMARK if for your future use...

< Previous Post Next Post >

<<< Top Articles >>>

MF Sohail Khilji | Servicenow Developer / Consultant.

Connect On LinkedIn >https://www.linkedin.com/in/mf-sohail-khilji/

netapp #storagediscovery #netappdiscovery