***** is an HSRP VIP. Aborting discovery

[Adiseshu Borra]

Hi All,

For some of network device discovery we are getting "  *****   is an HSRP VIP. Aborting discovery  " error. Any inputs to fix the issue.

Thanks In Advance 

[DaveHertel]

Hi -- had to put in exclusions to blacklist the IPs. .... never found a better approach 😞

[Adiseshu Borra]

Hi Dave,

if we added the IPs in exclusion list, in future if same IP is reassign to some other device or server, it will be a problem ?

[DaveHertel]

Hi -- potentially yes.   The SN platform won't know automatically when your business decides to repurpose the IP for some other use.  In short, a business process would need to intervene to 'audit' or monitor excluded IPs on some routine basis.   This isn't great... but it is what it is...  fragile.

If anyone has a better approach to reclaim excluded IP's that would be helpful info to know 🙂  Please share...

[Insomaniac]

Instead of excluding the IP.

I created a BR on the table Discovery Active error & put the filter on short description.

& in the script setAbortAction(true).

I think this will help us in not getting those records in the Table.

[chuckm · Accepted solution]

A workaround for the X.X.X.X is an HSRP VIP. Aborting discovery error is detailed in KB article KB0746795 - Discovery of Cisco switches using HSRP VIP logs an error (https://hi.service-now.com/kb_view.do?sysparm_article=KB0746795).  The workaround displays a warning instead of an error.  The error message is being generated in the SNMP – Classify sensor.

Fixed in
London Patch 9 (London Patch 9)
Madrid Patch 4 (Madrid Patch 4)

A permanent fix is intended for New York.

Workaround
1) Open the SNMP – Classify Sensor (Discovery Definition->Sensors).
2) Locate the DiscoveryLogger.error(errorMessage) as shown.
3) Change DiscoveryLogger.error(errorMessage) to DiscoveryLogger.warn(errorMessage).
4) The change will now display a warning instead of an error.