Neighbor Scanning

There's a configuration for Neighbor Scanning on the subnet. In the admin guide, it defines this as:

Neighbor Scanning will attempt to retrieve the status of a device that may not be responding to ICMP by scanning the ARP table of a neighbor router to determine what IP addresses are active. It is disabled by default.

This feature sounds like there is no down side assuming that IPAM pings the IP first and resolves the neighbor second if the ping times out. The only potential problem we see with enabling this is potential load on the Orion application server?

Can SolarWinds tell us why the default setting is disabled?

Neighbor Scanning.PNG

Thanks,

Jason Henson

Loop1 Systems

Find more posts tagged with

neighbor

neighbor scanning

Accepted answers

All comments

donrobert5

I believe this is disabled as that feature acts as a backup in case the IP address is not reachable via ICMP. usually if the IP address is on a different segment, it is not pingable, and therefore this feature can somewhat help the users to still get the status of the IP with the SNMP gathered data.

swf5002

I know this is super late but in case this is helpful - it can dramatically increase CPU usage on a router if you have many subnets that it's the gateway for.

agusst

Better late than never....I was actually researching this same question to try and determine if this feature would cause an extra burden on the router or not.