On Sep 24, 2008, at 8:35 PM, T_R_J wrote:
I've come across another strange occurance with 2.2.3 that I didn't
seem to have before.
If I attempt to add a particular device with SNMP I'm getting this:
Code:
2008-09-24 20:34:29 INFO zen.Utils Executing command: /usr/local/
zenoss/zenoss/bin/zendisc run --now -d 192.168.7.64 --monitor
localhost --deviceclass /Network/BlueCoat --snmp-port 161 --snmp-
community xxxx --weblog
2008-09-24 20:34:34 WARNING zen.ZenDisc Reconnected to ZenHub
2008-09-24 20:34:34 INFO zen.ZenDisc connected to ZenHub
2008-09-24 20:34:34 INFO zen.ZenDisc Looking for 192.168.7.64
2008-09-24 20:34:58 INFO zen.ZenDisc IP '192.168.7.64' on no auto-
discover, skipping
2008-09-24 20:34:58 INFO zen.ZenDisc Result: Discovered device
192.168.7.64.
2008-09-24 20:34:58 INFO zen.ZenDisc scan time: 0.00 seconds
2008-09-24 20:34:59 INFO zen.ZenDisc Daemon ZenDisc shutting down
2008-09-24 20:35:00 INFO zen.ZenDisc zendisc shutting down
2008-09-24 20:35:00 INFO zen.DeviceLoader Device 192.168.7.64
loaded!
The key line in here is the "on no auto-discover, skipping". The
problem is that in 2.2.3 Zenoss required that the network the device
is on to be set to zAutoDiscover = True to add devices. This has been
corrected in 2.2.4 so that the zAutoDiscover property only relates to
auto-discover and not adding single devices.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
