Skip to main content
Version: 2.12.1

Auto-discovery Reporter (10701)

The Auto-discovery Reporter publishes the network inventory and topology that NFO builds through SNMP discovery: a list of discovered devices and the physical and logical connections between them. Use it to feed an up-to-date network map into your SIEM or analytics platform without maintaining the topology by hand.

Functionality​

This module emits two kinds of events: discovered devices (nfc_id=20701) and the connections between them (nfc_id=20702). Connections are derived from multiple discovery sources (neighbor protocols such as LLDP and CDP, Layer 2 bridge tables, Layer 3 IP forwarding, and routing-protocol adjacencies such as BGP and OSPF), and reported with a con_source field identifying where each connection came from.

Parameters​

Reporting Frequency​

Parameter NameDescriptionDefault
Report devicesFrequency of reporting devices3600 sec
Report device connectionsFrequency of reporting device connections3600 sec

Reported Data​

Parameter NameDescriptionNotes
DevicesList of devices sent as eventsClick SNMP auto-discovery to configure; view last updated timestamp and perform other actions
Device connectionsList of device connections sent as eventsClick SNMP auto-discovery to configure; view last updated timestamp and perform other actions

Syslog/JSON Message Fields​

Devices (nfc_id=20701)​

Field NameDescriptionTypeExample / Notes
nfc_idMessage type identifierstringnfc_id=20701
nfo_hostnameHostname of the reporting NFO instancestringe.g. NFO-Beta
siteSite identifier of the reporting NFO instancestringe.g. SFO1
mgmt_ipSNMP management IP addressIPv4 address or IPv6 addressPrimary device identifier. e.g. 172.31.31.73
device_groupDevice groupstringSemicolon-separated. e.g. Cisco Router;Cisco;Router
device_typeDevice typestringe.g. router, firewall, switch
sysObjectIDSNMP sysObjectIDstringe.g. 1.3.6.1.4.1.9.1.619
sysNameSNMP sysNamestringe.g. Cisco2801
sysLocationSNMP sysLocationstringe.g. NetFlow Logic AWS Demo
capabilitiesDevice capabilitiesstringComma-separated. e.g. wlanAccessPoint,router,telephone
statusDevice statusstringe.g. Up
error_msgError message from SNMP pollingstringPresent when polling fails
idUnique device IDnumber

Device Connections (nfc_id=20702)​

Field NameDescriptionTypeExample / Notes
nfc_idMessage type identifierstringnfc_id=20702
nfo_hostnameHostname of the reporting NFO instancestringe.g. NFO-Beta
siteSite identifier of the reporting NFO instancestringe.g. SFO1
mgmt_ipSource device main IP addressIPv4 addressPrimary join key to 20701 device list. e.g. 172.31.24.19
device_typeSource device typestringAvoids join to 20701 when present. e.g. switch
sysNameSource device sysNamestringAvoids join to 20701 when present. e.g. EX4100
src_ip / src_ip6Source interface IP addressIPv4 address or IPv6 addressMay differ from mgmt_ip on multi-interface devices. e.g. 172.31.24.19
ifIndexSource interface SNMP indexnumbere.g. 2
ifNameSource interface namestringOptional, may be missing. e.g. ens5
dest_mgmt_ipDestination device main IP addressIPv4 addressOptional, may be missing or equal to dest_ip (e.g. some LLDP sources or IP_FORWARDING). e.g. 172.31.16.1
dest_ip / dest_ip6Destination interface IP addressIPv4 address or IPv6 addresse.g. 172.31.16.1
dest_ifIndexDestination interface SNMP indexnumberOptional, destination index may not be known. e.g. 0
con_sourceConnection discovery sourcestringLLDP, CDP, BRIDGE, IP_FORWARDING, NEXT_HOP, BGP, OSPF
note

con_source identifies how each connection was discovered. LLDP, CDP, and BRIDGE are Layer 2 sources; IP_FORWARDING, NEXT_HOP, BGP, and OSPF are Layer 3. BGP and OSPF connections are discovered only on Layer 3 devices and are disabled by default; enable them with the Enable BGP peer discovery and Enable OSPFv3 neighbor discovery options on the SNMP Management Settings tab.