- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 02:12 AM
Hello,
A Question from my Network Discovery issue. Let's say on an IP 10.0.0.1, I had a Cisco 2950 48P Switch configured. Now this is spare and I am configuring a new Cisco 9200 48 P with same IP and same name. Why discovery does not create a new CI and also doesn't updates the old one completely. I often see that , discovery updates the model ID of the older entry and does not creates a new entry for new serial Number. However , i see the new serial number created by discovery in the Serial Number table. So now both serial numbers are available in the Serial Number table and related to the same IP.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 12:27 PM - edited 01-23-2023 12:29 PM
I ran into similar issues. ServiceNow OOB doesn't support Cisco HSRP or other high availability protocols very well where the name and IP are shared. That is because the Identification rules for Computers and Network Gear both inherit from Hardware (you can see this via CI Class Manager.) To fix this, we created an independent Identification Rules at the Network level that looks for 1) Serial Number and Serial Number Type on the Serial Number Table, 2) Serial Number on the Netgear Table, 3) Name and Serial Number on the Netgear Table and 4) MAC Address and Name on the Networks Adapter table. This effectively added "Serial Number" for the third Identification rule in Hardware and enabled ServiceNow to distinguish between the two HSRP enabled Netgear devices (aka routers, switches, and firewalls.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 02:24 AM
Hi @Vishal42
You need to understand that discovery uses CI Identifiers for identifcation and reconciliation. As I see the switch CI has OOB serial number and name as identifiers with serial number with higher priority.
Make sure you are using OOB identification rules only and observe the behavior.
So when you rediscovered the switch with same name and IP, it updated the same CI as name was also an identifier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 02:47 AM - edited 01-23-2023 02:53 AM
Hello @SiD2 ,
Thank you for your response.
We are using the following in IRE. So below have happened in the discovery run:
1st priority = Serial Number search in Serial Number table - not found because the SN is new
2nd Priority = Serial Number search in Hardware Table - same as above.
3rd Priority = Name Search in Hardware Table - existing name was caught and CI updated.
However , the run did not updated all discoverable details. It just updated the Model ID from 2950 48P to Cisco 9200 48 P and didn't update Serial number or any other info. Also the dis. completed saying (PFA) screenshot for ref.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 03:10 AM
Hi @Vishal42
Ok, ideally it should have updated the serial no as once the CI is identified rest all other info will be overridden and says Updated CI.
For that one needs to debug the implementation, but seems here only probes were being used. Is that right, have you not migrated to use patterns yet?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-25-2023 06:46 AM
Hello @SiD2 Thank you for your response again. Yes, maybe i can check this with the technical team on the Pattern thing.
