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

Adiseshu Borra · ‎05-21-2019

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

chuckm · ‎07-06-2019

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.

View solution in original post

sethivarun · ‎05-21-2019

Hi,

Please have a look at "https://community.servicenow.com/community?id=community_question&sys_id=35070be5db1cdbc01dcaf3231f9619ac"

DaveHertel · ‎05-22-2019

I'm also facing same issue with HSRP VIP's being hit by Discovery and causing errors. Reading this thread, the other community thread doesn't seem help with a viable / realistic solution to avoid the errors.

Anyone have more input on how to implement a solution/work around?

manoj_s · ‎05-31-2019

Did anyone find any solution on this ?

Is the HSRP VIP even need to be discovered ?

stevenfroggattk · ‎06-04-2019

Hi,

We have the same requirement. It's spamming our discovery logs with errors which would indicate it should be classified and stored in the CMDB?

Let me know if you find a solution for this.

Thanks

Steve