Automatic Subnet Discovery modification

donrobert5

- Currently, the supported OIDs we poll to get information for subnet discovery is below.

1.3.6.1.2.1.4.1

1.3.6.1.2.1.4.21.1.1

1.3.6.1.2.1.4.21.1.11.

1.3.6.1.2.1.4.24.4.1.1.

1.3.6.1.2.1.4.24.4.1.2

1.3.6.1.2.1.4.21.1.8

1.3.6.1.2.1.4.21.1.7

It is written below.

https://documentation.solarwinds.com/en/Success_Center/IPAM/Content/IPAM-Import-IPv4-subnets-and-IP-addresses.htm

-The problem with this method is it only gets the results for the default routing table. If you somehow rename the routing table, it will not be returned via SNMP. You will need to edit the SNMP community string of the SNMPwalk part to get those values which does not exists on the IPAM module.

- Submitting this as a feature request so that IPAM will be able discover not only default route tables but all of the routing tables.  This would discover more Subnets and IPs.

adrianf

It would be a nice thing to have this feature implemented.

If we do the pooling with the above OIDs they will only return the data from the default routing instance (I have tried this on the Juniper devices where we have multiple routing instances) and we need all the subnets being pulled from all the routing instances.

In my opinion this feature is a great plus to have as the majority of network equipments are using multiple routing instances.