We don't actually collect addresses in the VRF discovery code at all.
If they IPs aren't there already, they won't be there if VRF stuff works, either.
I don't think there's much that can be done if Cisco haven't bothered to support MPLS-VPN-MIB...
adam.
On 2014-06-24 12:17, Rob VanHooren wrote:
it seems vrfs aren't discovered, since the OIDs are not found.
this leads to all sorts of unhappiness, since with no ipaddr (mgmt vrf) winds up with no syslog, no routing, no nothing except L2 info.
who can I send the walk to?
(would rather not post it to the list or jira)
thanks,
R.
[me@host ~] ./discovery.php -h theN7k -m cisco-vrf -d DEBUG!
theN7k 135 nxos (cisco) VRFs : DEBUG: SNMP Auth options = -v2c -c 'secretSNMPro' /usr/bin/snmpbulkwalk -v2c -c 'secretSNMPro' -Osqn -m MPLS-L3VPN-STD-MIB -M /opt/observium/mibs 'udp':'theN7k':'161' mplsL3VpnVrfRD .1.3.6.1.2.1.10.166.11.1.2.2.1.4 No Such Object available on this agent at this OID
DEBUG: SNMP Auth options = -v2c -c 'secretSNMPro' /usr/bin/snmpbulkwalk -v2c -c 'secretSNMPro' -Osqn -m MPLS-VPN-MIB -M /opt/observium/mibs 'udp':'theN7k':'161' mplsVpnVrfRouteDistinguisher .1.3.6.1.3.118.1.2.2.1.3 No Such Object available on this agent at this OID
DEBUG: SNMP Auth options = -v2c -c 'secretSNMPro' /usr/bin/snmpbulkwalk -v2c -c 'secretSNMPro' -Osqn -m MPLS-VPN-MIB -M /opt/observium/mibs 'udp':'theN7k':'161' .1.3.6.1.3.118.1.2.2.1.2 .1.3.6.1.3.118.1.2.2.1.2 No Such Object available on this agent at this OID
DEBUG: SNMP Auth options = -v2c -c 'secretSNMPro' /usr/bin/snmpbulkwalk -v2c -c 'secretSNMPro' -Osqn -m MPLS-VPN-MIB -M /opt/observium/mibs 'udp':'theN7k':'161' .1.3.6.1.3.118.1.2.1.1.2 .1.3.6.1.3.118.1.2.1.1.2 No Such Object available on this agent at this OID
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium