Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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

Indirect Discovery (Neighbor Scanning) in IPAM

Table of contents
No headers
Created by Interspire Import, last modified by Nigel on Jul 05, 2018

Views: 1,861 Votes: 1 Revisions: 9

Last modified: March 4, 2016

 

Neighbor Scanning in IPAM 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 OIDs:

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

Tags

Classifications

Public