Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > IP Address Manager (IPAM) > Indirect Discovery (Neighbor Scanning) in IPAM

Indirect Discovery (Neighbor Scanning) in IPAM

Table of contents
No headers

The IPAM feature Neighbor Scanning attempts to retrieve the status of a device that may not be responding to ICMP by scanning the ARP table of a neighbor router to see which IP addresses are active.

 

IPAM first checks if the device is capable of SNMP and supports ARP table:

 

To check whether SNMP is available, IPAM uses these OIDs:

  • OidSysContact                 "1.3.6.1.2.1.1.4.0" iso.org.dod.internet.mgmt.mib-2.system.sysContact.0

 

To check whether the ARP table is available:

  • OidIPNetToMediaTable          "1.3.6.1.2.1.4.22" iso.org.dod.internet.mgmt.mib-2.ip.ipNetToMediaTable

 

The IPNetToMediaTable is pulled for client information. If the device supports this table, then IPAM can work with it.

 

Under the 1.3.6.1.2.1.4.22 oid IPAM will poll the following subsidary oid's:

  • 1.3.6.1.2.1.4.22.1.1- ipNetToMediaIfIndex
  • 1.3.6.1.2.1.4.22.1.2 - ipNetToMediaPhysAddress
  • 1.3.6.1.2.1.4.22.1.3 - ipNetToMediaNetAddress
  • 1.3.6.1.2.1.4.22.1.4 - ipNetToMediaType

 

A null return indicates the device does not support that MIB. 

Last modified
04:18, 4 Mar 2016

Tags

Classifications

Public