Daniel Rich
2013-07-19 21:07:36 UTC
Daniel Rich [http://community.zenoss.org/people/sjthespian] created the discussion
"Auto discovery duplicating hosts if they have multiple NICs"
To view the discussion, visit: http://community.zenoss.org/message/74061#74061
--------------------------------------------------------------
I have been fighting a problem with duplicate devices and devices with IP addresses for the device id, and I finally tracked it down to auto-discovery. We have quite a few machines with multiple interfaces and interface aliases. It looks like any time auto-discovery finds a machine like this it creates multiple devices. If I do the discovery through the web inerface it does the right thing and detects the second box as a duplicate and refuses to add it.
I'm wondering if it is something as simple as auto-discovery doing a commit() after each device but not a sync() before so it doesn't have a current copy of the device tree?
As an example, let's say I have a device "newhost" with the following interfaces:
* eth0: 192.168.38.54
* eth0:1: 192.168.38.154
Adding these two IPs via. the web interface will start two jobs, the second one run will show the message "Found IP '192.168.38.154' on device '192.168.38.54'; skipping discovery".
Running the following command:
* /opt/zenoss/bin/zendisc run --now --prefer-snmp-naming --range 192.168.38.54-54,192.168.38.154-154
will create two devices, one with a device id of "newhost" and one with a device id of "192.168.38.154". Both will have the device title of "newhost".
Any thoughts from anyone of how to fix this? Should I open a JIRA on this?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74061#74061]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Auto discovery duplicating hosts if they have multiple NICs"
To view the discussion, visit: http://community.zenoss.org/message/74061#74061
--------------------------------------------------------------
I have been fighting a problem with duplicate devices and devices with IP addresses for the device id, and I finally tracked it down to auto-discovery. We have quite a few machines with multiple interfaces and interface aliases. It looks like any time auto-discovery finds a machine like this it creates multiple devices. If I do the discovery through the web inerface it does the right thing and detects the second box as a duplicate and refuses to add it.
I'm wondering if it is something as simple as auto-discovery doing a commit() after each device but not a sync() before so it doesn't have a current copy of the device tree?
As an example, let's say I have a device "newhost" with the following interfaces:
* eth0: 192.168.38.54
* eth0:1: 192.168.38.154
Adding these two IPs via. the web interface will start two jobs, the second one run will show the message "Found IP '192.168.38.154' on device '192.168.38.54'; skipping discovery".
Running the following command:
* /opt/zenoss/bin/zendisc run --now --prefer-snmp-naming --range 192.168.38.54-54,192.168.38.154-154
will create two devices, one with a device id of "newhost" and one with a device id of "192.168.38.154". Both will have the device title of "newhost".
Any thoughts from anyone of how to fix this? Should I open a JIRA on this?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74061#74061]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]