I'm running Zen 2.2.3 on SuSE 10.3 (that's kernel 2.6.18)
I was trying to discover an SNMP enabled printer (a Konica BizHub) that had
been successfully discovered and modeled in prior versions of Zen.
However, in 2.2.3, discovery was failing with an "Empty or Invalid ID" error in
the GUI and the device wasn't seen in the device list.
So, I ran zendisc in debug mode and got the following:
Code:
$> zendisc run --now -d 192.168.1.200 --monitor localhost --deviceclass
/Printer/Laser --snmp-port 161 --snmp-community public -v10
DEBUG:zen.ZenDisc:Run in foreground, starting immediately.
DEBUG:zen.ZenDisc:Run in foreground, starting immediately.
DEBUG:zen.ZenDisc:run
DEBUG:zen.ZenDisc:Connecting to localhost
DEBUG:zen.ZenDisc:Logging in as admin
WARNING:zen.ZenDisc:Reconnected to ZenHub
DEBUG:zen.ZenDisc:setting up services EventService, DiscoverService
DEBUG:zen.ZenDisc:chaining getInitialServices with d2
DEBUG:zen.ZenDisc:callback after getting service EventService
DEBUG:zen.ZenDisc:callback after getting service DiscoverService
DEBUG:zen.ZenDisc:Calling connected.
DEBUG:zen.ZenDisc:connected
DEBUG:zen.ZenDisc:Sending event {'severity': 0, 'component': 'zendisc',
'agent': 'zendisc', 'summary': 'started', 'manager': 'localhost', 'device':
'crkmon.crklaw.local', 'eventClass': '/App/Start'}
INFO:zen.ZenDisc:connected to ZenHub
INFO:zen.ZenDisc:Looking for 192.168.1.200
DEBUG:zen.ZenDisc:Found IP 192.168.1.200 for device 192.168.1.200
DEBUG:zen.ZenDisc:Scanning device with address 192.168.1.200
DEBUG:zen.ZenDisc:Doing SNMP lookup on device 192.168.1.200
DEBUG:zen.ZenDisc:Finished SNMP lookup on device 192.168.1.200
DEBUG:zen.ZenDisc:Failed to lookup 192.168.1.200 ((0, 'Resolver Error 0 (no
error)'))
ERROR:zen.ZenDisc:('Empty or invalid id specified', '')
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/DataCollector/zendisc.py", line 269,
in inner
raise ZentinelException(result.value)
ZentinelException: ('Empty or invalid id specified', '')
DEBUG:zen.ZenDisc:Finished scanning device with address 192.168.1.200
INFO:zen.ZenDisc:Result: Discovered device 192.168.1.200.
DEBUG:zen.ZenDisc:starting collector loop
DEBUG:zen.ZenDisc:Running 0 clients
INFO:zen.ZenDisc:scan time: 0.00 seconds
DEBUG:zen.ZenDisc:Collection slots filled
DEBUG:zen.ZenDisc:Running 0 clients
INFO:zen.ZenDisc:Daemon ZenDisc shutting down
DEBUG:zen.ZenDisc:Running 0 clients
DEBUG:zen.ZenDisc:removing service EventService
DEBUG:zen.ZenDisc:removing service DiscoverService
INFO:zen.ZenDisc:zendisc shutting down
The "resolver error" in the trace got me thinking, so I checked and found that
the device wasn't in DNS. I added it and discovery worked fine, as can be seen
in the output below:
Code:
$> zendisc run --now -d 192.168.1.200 --monitor localhost --deviceclass
/Printer/Laser --snmp-port 161 --snmp-community public -v10
DEBUG:zen.ZenDisc:Run in foreground, starting immediately.
DEBUG:zen.ZenDisc:Run in foreground, starting immediately.
DEBUG:zen.ZenDisc:run
DEBUG:zen.ZenDisc:Connecting to localhost
DEBUG:zen.ZenDisc:Logging in as admin
WARNING:zen.ZenDisc:Reconnected to ZenHub
DEBUG:zen.ZenDisc:setting up services EventService, DiscoverService
DEBUG:zen.ZenDisc:chaining getInitialServices with d2
DEBUG:zen.ZenDisc:callback after getting service EventService
DEBUG:zen.ZenDisc:callback after getting service DiscoverService
DEBUG:zen.ZenDisc:Calling connected.
DEBUG:zen.ZenDisc:connected
DEBUG:zen.ZenDisc:Sending event {'severity': 0, 'component': 'zendisc',
'agent': 'zendisc', 'summary': 'started', 'manager': 'localhost', 'device':
'crkmon.crklaw.local', 'eventClass': '/App/Start'}
INFO:zen.ZenDisc:connected to ZenHub
INFO:zen.ZenDisc:Looking for 192.168.1.200
DEBUG:zen.ZenDisc:Found IP 192.168.1.200 for device 192.168.1.200
DEBUG:zen.ZenDisc:Scanning device with address 192.168.1.200
DEBUG:zen.ZenDisc:Doing SNMP lookup on device 192.168.1.200
DEBUG:zen.ZenDisc:Finished SNMP lookup on device 192.168.1.200
DEBUG:zen.ZenDisc:Sending event {'severity': 2, 'component': '192.168.1.200',
'agent': 'zendisc', 'summary': "'Discovered device name 'KonicaBizhub' for ip
'192.168.1.200'", 'manager': 'localhost', 'eventKey': '192.168.1.200',
'device': 'KonicaBizhub', 'eventClass': '/Status/Snmp', 'ipAddress':
'192.168.1.200'}
DEBUG:zen.ZenDisc:trying to auto-allocate device KonicaBizhub
DEBUG:zen.ZenDisc:no auto-allocation script found
DEBUG:zen.ZenDisc:Finished scanning device with address 192.168.1.200
INFO:zen.ZenDisc:Result: Discovered device 192.168.1.200.
DEBUG:zen.ZenDisc:starting collector loop
INFO:zen.ZenDisc:no wmi plugins found for KonicaBizhub
INFO:zen.ZenDisc:no python plugins found for KonicaBizhub
INFO:zen.ZenDisc:no cmd plugins found for KonicaBizhub
DEBUG:zen.ZenDisc:using zenoss.snmp.NewDeviceMap on KonicaBizhub
DEBUG:zen.ZenDisc:using zenoss.snmp.DeviceMap on KonicaBizhub
DEBUG:zen.ZenDisc:using zenoss.snmp.InterfaceMap on KonicaBizhub
DEBUG:zen.ZenDisc:using zenoss.snmp.RouteMap on KonicaBizhub
INFO:zen.ZenDisc:snmp collection device KonicaBizhub
INFO:zen.ZenDisc:plugins: zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap,
zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap
DEBUG:zen.SnmpClient:Starting SNMP info for KonicaBizhub at 192.168.1.200:161
timeout: 2.5 tries: 2 version: v1 community: public
DEBUG:zen.SnmpClient:Testing SNMP configuration
INFO:zen.ZenDisc:no portscan plugins found for KonicaBizhub
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Collection slots filled
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.SnmpClient:running <zenoss.snmp.NewDeviceMap.NewDeviceMap instance at
0x8b7906c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.DeviceMap.DeviceMap instance at
0x8b790cc>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.DeviceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.InterfaceMap.InterfaceMap instance at
0x8b7922c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.InterfaceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.RouteMap.RouteMap instance at
0x8c12a8c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.RouteMap
INFO:zen.SnmpClient:snmp client finished collection for KonicaBizhub
DEBUG:zen.ZenDisc:client for KonicaBizhub finished collecting
DEBUG:zen.ZenDisc:processing data for device KonicaBizhub
DEBUG:zen.ZenDisc:processing plugin zenoss.snmp.NewDeviceMap on device
KonicaBizhub
INFO:zen.ZenDisc:processing zenoss.snmp.NewDeviceMap for device KonicaBizhub
DEBUG:zen.ZenDisc:HWProductKey=.1.3.6.1.4.1.18334.1.1.1.2.1.17.2.1
DEBUG:zen.ZenDisc:OSProductKey=KONICA bizhub
DEBUG:zen.ZenDisc:processing plugin zenoss.snmp.DeviceMap on device KonicaBizhub
INFO:zen.ZenDisc:processing zenoss.snmp.DeviceMap for device KonicaBizhub
DEBUG:zen.ZenDisc:processing plugin zenoss.snmp.InterfaceMap on device
KonicaBizhub
INFO:zen.ZenDisc:processing zenoss.snmp.InterfaceMap for device KonicaBizhub
DEBUG:zen.ZenDisc:processing plugin zenoss.snmp.RouteMap on device KonicaBizhub
INFO:zen.ZenDisc:processing zenoss.snmp.RouteMap for device KonicaBizhub
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Running 1 clients
INFO:zen.ZenDisc:changes applied
DEBUG:zen.ZenDisc:Running 1 clients
DEBUG:zen.ZenDisc:Client KonicaBizhub finished
DEBUG:zen.ZenDisc:Running 0 clients
INFO:zen.ZenDisc:scan time: 12.54 seconds
DEBUG:zen.ZenDisc:Running 0 clients
INFO:zen.ZenDisc:Daemon ZenDisc shutting down
DEBUG:zen.ZenDisc:removing service EventService
DEBUG:zen.ZenDisc:removing service DiscoverService
INFO:zen.ZenDisc:zendisc shutting down
So, my question - Why does Zen require that a host be known to DNS and have a
resolvable name before it can successfully discover it? Can this be disabled
to force it to discover and manage by IP address (or MIB-II hostname)?
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23687#23687
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
