Loopback interfaces are not discovered on SNMP devicesDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview Loopback interfaces are intentionally not recorded for SNMP devices out of box due to the SNMPIdentityInfoParser Script Include. The code states that if an SNMP - Identity probe payload returns a device interface with an ifType value of 24, then it will not be recorded. Example Below is an example of an SNMP - Identity probe input payload for SNMP device 10.0.0.1: This interface returned with an ifType value of 24, so it will not be recorded. Notice the identifying ifIndex value in this case is set to 8, but will vary by device. <ifEntry instance=".8"><ifIndex type="SnmpInt32">8</ifIndex> <ifDescr type="SnmpOctetString">Loopback0</ifDescr><ifType type="SnmpInt32">24</ifType> <ifPhysAddress type="SnmpOctetString"/><ifAdminStatus type="SnmpInt32">1</ifAdminStatus><ifOperStatus type="SnmpInt32">1</ifOperStatus> Using the ifIndex value, look further down the payload for the ipAdEntIfIndex with the same value. This will be the IP address that is not recorded.<ipAddrEntry instance=".10.0.0.1"><ipAdEntAddr type="SnmpIPAddress">10.0.0.1</ipAdEntAddr><ipAdEntIfIndex type="SnmpInt32">8</ipAdEntIfIndex> <ipAdEntNetMask type="SnmpIPAddress">255.255.255.255</ipAdEntNetMask></ipAddrEntry>