Discovered secondary IP, Instead of Primary IP (loopback IPs)

Anurudh Kumar
Mega Expert

Hello Everyone,

I tried to do a quick discovery  of CI with IP = 10.12.1345 (loopback IPs) and found Device Discovered successfully but with secondary IP = 10.12.23

What could be the reason for this?

Also How can the loopback IPs can only be added in discovery schedule and make sure that is populated in CIs.

3 REPLIES 3

David A2
Giga Guru

I worked through a similar issue with HI support a few years ago. Hope this helps: https://community.servicenow.com/community?id=community_question&sys_id=18e5c2d8db757380feb1a851ca961972

 

As to not trigger unnecessary probes on the same device and on the same discovery, discovery checks if the CI has already been discovered on such discovery attempt. If the CI is found in the same discovery, discovery stops triggering "repeated" probes on the same device and sets the status to "extra IP". This saves both the MID server and instance from duplicating work. It is only needed to discover a device via one IP address to collect the necessary information.

Thus, it would not be necessary to discover the device via x.x.x.x. All you would need to do is manually set the IP address to x.x.x.x, if this were not a loopback address. The next discovery should keep it, when using probes (I checked and this discovery is using probes), so long this IP address is one of the ip addresses returned on the payload. However, because x.x.x.x is a loopback interface, discovery automatically removes this IP address from the payload. This is done on script include SnmpIdentityInfoParser.

You can see in SnmpIdentityInfoParser that interfaces of type 24 are removed, see line 296.

Therefore, to use a loopback address for network switches you would need to:

01) Customize the script include SnmpIdentityInfoParser to not remove interfaces of type 24.

02) Manually set the IP of the device to the desired ip.

03) Ensure "Enforce syncing of IP addresses" is false (it is currently set to true) under "Discovery Definition > Properties".

04) Next discoveries should not modify the ip address

Rahul Priyadars
Tera Sage

See if this KB helps you.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0727893

Regards

RP

pratik0306
Tera Guru

Hi Anurudh,

to which IP is the gateway configured? You will have to check this on the device whether its server/network etc..

And is this happening for all types of devices or just few