How can I prevent the creation of Next Hop Routing rules (dscy_route_next_hop)

[SandySeegers]

Does anybody know how to prevent the creation of these records.   We have 1 million + of these records.

I have a note from a long time ago that says to disable the 'ports' field in the SNMP - Switching probe.   And there is something in the Wiki about doing this very thing.   But I'm not sure the Wiki is addressing the same problem.

Thanx in advance

Sandy

[doug_schulze · Accepted solution]

Take a look at the SNMP Routing Probe.. You can remove the entire probe from the classifier or you can have a go at just removing the next hop routing table query..

But before you do, remember we are mapping L2/3 relationships now and this may be important to have.. so you might just choose to hide the table from views so not have to deal with the records but have them for support of other functionality!

[SandySeegers]

Thanx Doug!   Proving, once again you are the Disco King.

And I can't emphasis enough how amazed I am that you and other gurus like you are so accessible.   It is one of the things I love the most about ServiceNow.

[doug_schulze]

Glad to be of Service Sandra! And its me who's grateful, keep doing amazing things with the tool, and telling us how you are making it your own... I learn so much from the community each day!

[cyked]

I've notice this issue (long running discovery due to the SNMP - Routing probe) on some routers.   Can you help me get a better understanding what we could be potentially missing by disabling this probe from the the Standard Router classifier?   The network management team has a management tool so we have little need to (currently) collect this information in CMDB.   Would disabling this impact anything related to App Dep Mapping during discovery, or relationship mapping between classes of items?

Thanks.