[Solved] Problems performing native discovery of the NetApp server without the need to traverse an SMI-S server

[DennisFoster1]

Hi experts -

I am trying to discover a NetApp device without the SMI-S server requirement. I am following the guidance provided here:

https://docs.servicenow.com/bundle/kingston-it-operations-management/page/product/discovery/concept/netapp-discovery.html

The NetApp is configured in 7-Mode and ONTAP version 8.1.4 P5. I've configured the SNMP communitity string and Basic Auth user credentials. The Basic Auth user has permissions as prescribed in the docs article. I've ensured that glide.discovery.sensors.netapp_native_7mode property is true.

When I run discovery on this device it starts classifying with SNMP and finds the name but then starts the UNIX classify and returns "SSH authentication or connection failure".

Am I missing a step to have it run the NetApp Storage 7-Mode discovery pattern?

Thanks for reading,

Dennis

[DennisFoster1]

The issue was that the SNMP payload returned system OID : .1.3.6.1.4.1.789.2.3 . ServiceNow was expecting either 1.3.6.1.4.1.789.2.1 or  1.3.6.1.4.1.789.2.5

So I added a classification record (insert on the existing .1 record)  for OID 1.3.6.1.4.1.789.2.3 and now scan.

[daniel_badyan]

Hi Dennis,

i'm from the pattern dev team. thanks for your input on this matter, i'll be adding this OID to the out-of-the-box classification process so that others may benefit from your struggle 🙂 thanks.

[Ashutosh Munot1]

Hi Daniel,

I am getting one wired error. I am getting whole data from NetApp IP which i am giving.

Now the issue is, the last step of pattern is failing as shown below. 

"Found duplicate Lookup items (0 and 1) in the payload index 0 using fields serial_number,serial_number_type,Found duplicate Lookup items (0 and 1) in the payload index 1 using fields serial_number,serial_number_type,Found duplicate Lookup items (0 and 1) in the payload index 2 using fields serial_number,serial_number_type,Found duplicate Lookup items (0 and 1) in the payload index 3 using fields serial_number,serial_number_type,Abandoned due to too many errors,Abandoned due to too many errors,Abandoned due to too many errors,Abandoned due to too many errors,Abandoned due to too many errors,Abandoned due to too many errors".

Now if you see above logs, it says create CI, But when i see it is not creating any CI, No relationships nothing.

Can you explain why?

Thanks,
Ashutosh Munot

[daniel_badyan]

hi,

yes, this seems to be an issue with the pattern, and it should be easily resolved by adding a step to remove those duplicate items. could you please open an incident so support personnel can access your instance and fix the issue?