NetApp Storage Cluster Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2024 11:51 AM
While discovering NetApp Storage devices (using Basic and SNMP credentials), we have come across a scenario where some of the Storage clusters are having the same serial number. This is causing the same cluster record to be updated whenever Discovery runs (OOB IRE rules matching on Serial Number) and different Storage servers are getting related to the same cluster record.
Our storage SME has updated that this seems to be expected in some scenarios (KB Article: "The cluster serial is set based on the cluster base license key entered. It sometimes happens with conversions, rushed installs etc, that the cluster base license key is unavailable, and a well known temporary key is used which corresponds to serial 180000099, so you will sometimes see customers with multiple clusters with the serial 180000099. The cluster serial number can be changed if necessary.")
Would like to know if anyone has come across this scenario and what options can be used within ServiceNow. One of the option that I could think of is to create a new Identification rule with a lower priority matching on Cluster Name, any other thoughts/suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2024 10:24 AM
Yes we encountered this issue
We have modified the Identifier entry for Storage cluster from Serial number to (IP, Serial Number), then unique records got created
