Bob Nicksic
2012-03-06 15:49:05 UTC
Bob Nicksic [http://community.zenoss.org/people/bnicksic] created the discussion
"Modeling server with multiple IP addresses"
To view the discussion, visit: http://community.zenoss.org/message/64969#64969
--------------------------------------------------------------
I am running Zenoss 3.1.0 on Centos 5. I have a CentOS 5 server with 3 IP addresses on a bonded vlan interface. This particular server doesn't get the primary address assigned to it via modeling, but other servers with multiple addresses do. Here is the snmpwalk for the interfaces:
snmpwalk -v 1 -c private-ro localhost .1.3.6.1.2.1.4.20.1.1
IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1
IP-MIB::ipAdEntAddr.172.29.22.162 = IpAddress: 172.29.22.162
IP-MIB::ipAdEntAddr.172.29.22.168 = IpAddress: 172.29.22.168
IP-MIB::ipAdEntAddr.172.29.22.170 = IpAddress: 172.29.22.170
Modeling debug returns this:
<Products.DataCollector.plugins.CollectorPlugin.GetTableMap object at 0x1442d4d0>: {'.1.3.6.1.2.1.4.20.1.1': {'.1.3.6.1.2.1.4.20.1.1.172.29.22.170': '172.29.22.170', '.1.3.6.1.2.1.4.20.1.1.172.29.22.162': '172.29.22.162', '.1.3.6.1.2.1.4.20.1.1.127.0.0.1': '127.0.0.1', '.1.3.6.1.2.1.4.20.1.1.172.29.22.168': '172.29.22.168'}, '.1.3.6.1.2.1.4.20.1.2': {'.1.3.6.1.2.1.4.20.1.2.172.29.22.168': 8, '.1.3.6.1.2.1.4.20.1.2.172.29.22.162': 8, '.1.3.6.1.2.1.4.20.1.2.172.29.22.170': 8, '.1.3.6.1.2.1.4.20.1.2.127.0.0.1': 1}, '.1.3.6.1.2.1.4.20.1.3': {'.1.3.6.1.2.1.4.20.1.3.127.0.0.1': '255.0.0.0', '.1.3.6.1.2.1.4.20.1.3.172.29.22.168': '255.255.255.255', '.1.3.6.1.2.1.4.20.1.3.172.29.22.162': '255.255.255.0', '.1.3.6.1.2.1.4.20.1.3.172.29.22.170': '255.255.255.255'}}
And for a server that gets correct results:
snmpwalk -v 1 -c private-ro localhost .1.3.6.1.2.1.4.20.1.1
IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1
IP-MIB::ipAdEntAddr.172.29.22.163 = IpAddress: 172.29.22.163
IP-MIB::ipAdEntAddr.172.29.22.169 = IpAddress: 172.29.22.169
<Products.DataCollector.plugins.CollectorPlugin.GetTableMap object at 0x67214d0>: {'.1.3.6.1.2.1.4.20.1.1': {'.1.3.6.1.2.1.4.20.1.1.172.29.22.163': '172.29.22.163', '.1.3.6.1.2.1.4.20.1.1.127.0.0.1': '127.0.0.1', '.1.3.6.1.2.1.4.20.1.1.172.29.22.169': '172.29.22.169'}, '.1.3.6.1.2.1.4.20.1.2': {'.1.3.6.1.2.1.4.20.1.2.172.29.22.169': 8, '.1.3.6.1.2.1.4.20.1.2.172.29.22.163': 8, '.1.3.6.1.2.1.4.20.1.2.127.0.0.1': 1}, '.1.3.6.1.2.1.4.20.1.3': {'.1.3.6.1.2.1.4.20.1.3.127.0.0.1': '255.0.0.0', '.1.3.6.1.2.1.4.20.1.3.172.29.22.169': '255.255.255.255', '.1.3.6.1.2.1.4.20.1.3.172.29.22.163': '255.255.255.0'}}
Why does the first server model the interfaces out of order and return a secondary address?
Thanks in advance. I've been troubleshooting this for a couple of days now, and it doesn't make any sense.
Thanks,
Bob
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/64969#64969]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Modeling server with multiple IP addresses"
To view the discussion, visit: http://community.zenoss.org/message/64969#64969
--------------------------------------------------------------
I am running Zenoss 3.1.0 on Centos 5. I have a CentOS 5 server with 3 IP addresses on a bonded vlan interface. This particular server doesn't get the primary address assigned to it via modeling, but other servers with multiple addresses do. Here is the snmpwalk for the interfaces:
snmpwalk -v 1 -c private-ro localhost .1.3.6.1.2.1.4.20.1.1
IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1
IP-MIB::ipAdEntAddr.172.29.22.162 = IpAddress: 172.29.22.162
IP-MIB::ipAdEntAddr.172.29.22.168 = IpAddress: 172.29.22.168
IP-MIB::ipAdEntAddr.172.29.22.170 = IpAddress: 172.29.22.170
Modeling debug returns this:
<Products.DataCollector.plugins.CollectorPlugin.GetTableMap object at 0x1442d4d0>: {'.1.3.6.1.2.1.4.20.1.1': {'.1.3.6.1.2.1.4.20.1.1.172.29.22.170': '172.29.22.170', '.1.3.6.1.2.1.4.20.1.1.172.29.22.162': '172.29.22.162', '.1.3.6.1.2.1.4.20.1.1.127.0.0.1': '127.0.0.1', '.1.3.6.1.2.1.4.20.1.1.172.29.22.168': '172.29.22.168'}, '.1.3.6.1.2.1.4.20.1.2': {'.1.3.6.1.2.1.4.20.1.2.172.29.22.168': 8, '.1.3.6.1.2.1.4.20.1.2.172.29.22.162': 8, '.1.3.6.1.2.1.4.20.1.2.172.29.22.170': 8, '.1.3.6.1.2.1.4.20.1.2.127.0.0.1': 1}, '.1.3.6.1.2.1.4.20.1.3': {'.1.3.6.1.2.1.4.20.1.3.127.0.0.1': '255.0.0.0', '.1.3.6.1.2.1.4.20.1.3.172.29.22.168': '255.255.255.255', '.1.3.6.1.2.1.4.20.1.3.172.29.22.162': '255.255.255.0', '.1.3.6.1.2.1.4.20.1.3.172.29.22.170': '255.255.255.255'}}
And for a server that gets correct results:
snmpwalk -v 1 -c private-ro localhost .1.3.6.1.2.1.4.20.1.1
IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1
IP-MIB::ipAdEntAddr.172.29.22.163 = IpAddress: 172.29.22.163
IP-MIB::ipAdEntAddr.172.29.22.169 = IpAddress: 172.29.22.169
<Products.DataCollector.plugins.CollectorPlugin.GetTableMap object at 0x67214d0>: {'.1.3.6.1.2.1.4.20.1.1': {'.1.3.6.1.2.1.4.20.1.1.172.29.22.163': '172.29.22.163', '.1.3.6.1.2.1.4.20.1.1.127.0.0.1': '127.0.0.1', '.1.3.6.1.2.1.4.20.1.1.172.29.22.169': '172.29.22.169'}, '.1.3.6.1.2.1.4.20.1.2': {'.1.3.6.1.2.1.4.20.1.2.172.29.22.169': 8, '.1.3.6.1.2.1.4.20.1.2.172.29.22.163': 8, '.1.3.6.1.2.1.4.20.1.2.127.0.0.1': 1}, '.1.3.6.1.2.1.4.20.1.3': {'.1.3.6.1.2.1.4.20.1.3.127.0.0.1': '255.0.0.0', '.1.3.6.1.2.1.4.20.1.3.172.29.22.169': '255.255.255.255', '.1.3.6.1.2.1.4.20.1.3.172.29.22.163': '255.255.255.0'}}
Why does the first server model the interfaces out of order and return a secondary address?
Thanks in advance. I've been troubleshooting this for a couple of days now, and it doesn't make any sense.
Thanks,
Bob
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/64969#64969]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]