Unsolved
2 Posts
0
3458
Isilon 8 SNMP ipAddrTable
Hi, I'm experiencing a problem where Isilon 8.1.2 is returning a bad ipAddrTable from SNMP. There are 7 interfaces. Only a single row is returned from ipAddrTable, and it has the address as 0.0.0.0 and netmask as 0.54.120.0. An Isilon 7 configured similarly returns a complete set of rows with expected addresses and netmasks.
Does anyone know if this is a known issue, or perhaps related to some kind of misconfiguration?
Thanks,
Jim
Examples:
An Isilon 8 node (all cluster nodes return the same kind of bad info)
snmpwalk -v 2c -c 10.200.60.133 ipAddrTable IP-MIB::ipAdEntAddr.0.0.0.0 = IpAddress: 0.0.0.0 IP-MIB::ipAdEntIfIndex.0.0.0.0 = INTEGER: 2 IP-MIB::ipAdEntNetMask.0.0.0.0 = IpAddress: 0.54.120.0 IP-MIB::ipAdEntBcastAddr.0.0.0.0 = INTEGER: 0 IP-MIB::ipAdEntReasmMaxSize.0.0.0.0 = INTEGER: 65535
An Isilon 7
snmpwalk -v 2c -c 10.200.60.161 ipAddrTable IP-MIB::ipAdEntAddr.10.20.60.161 = IpAddress: 10.20.60.161 IP-MIB::ipAdEntAddr.10.200.60.161 = IpAddress: 10.200.60.161 IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1 IP-MIB::ipAdEntAddr.172.29.104.111 = IpAddress: 172.29.104.111 IP-MIB::ipAdEntAddr.192.168.1.10 = IpAddress: 192.168.1.10 IP-MIB::ipAdEntIfIndex.10.20.60.161 = INTEGER: 3 IP-MIB::ipAdEntIfIndex.10.200.60.161 = INTEGER: 2 IP-MIB::ipAdEntIfIndex.127.0.0.1 = INTEGER: 5 IP-MIB::ipAdEntIfIndex.172.29.104.111 = INTEGER: 2 IP-MIB::ipAdEntIfIndex.192.168.1.10 = INTEGER: 7 IP-MIB::ipAdEntNetMask.10.20.60.161 = IpAddress: 255.255.252.0 IP-MIB::ipAdEntNetMask.10.200.60.161 = IpAddress: 255.255.252.0 IP-MIB::ipAdEntNetMask.127.0.0.1 = IpAddress: 255.0.0.0 IP-MIB::ipAdEntNetMask.172.29.104.111 = IpAddress: 255.255.252.0 IP-MIB::ipAdEntNetMask.192.168.1.10 = IpAddress: 255.255.255.0 IP-MIB::ipAdEntBcastAddr.10.20.60.161 = INTEGER: 1 IP-MIB::ipAdEntBcastAddr.10.200.60.161 = INTEGER: 1 IP-MIB::ipAdEntBcastAddr.127.0.0.1 = INTEGER: 1 IP-MIB::ipAdEntBcastAddr.172.29.104.111 = INTEGER: 1 IP-MIB::ipAdEntBcastAddr.192.168.1.10 = INTEGER: 1 IP-MIB::ipAdEntReasmMaxSize.10.20.60.161 = INTEGER: -1 IP-MIB::ipAdEntReasmMaxSize.10.200.60.161 = INTEGER: -1 IP-MIB::ipAdEntReasmMaxSize.127.0.0.1 = INTEGER: -1 IP-MIB::ipAdEntReasmMaxSize.172.29.104.111 = INTEGER: -1 IP-MIB::ipAdEntReasmMaxSize.192.168.1.10 = INTEGER: -1
JimSermersheim
2 Posts
0
March 8th, 2019 17:00
Follow-up:
I found a couple of bsnmpd bugs that match this same condition:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195445
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203264
Both are closed as fixed (seemingly in FreeBSD 10.2). Since the problem persists in FreeBSD 11.0-CURRENT, I logged a new one:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236408