I am a new for Zenoss. I've installed Zenoss core on Centos 4 for. My question 
is: why no OS, Hardware route map  show up after add a cisco router 7206 into 
classe /Device/network/cisco/router?  My router use Snmp v3 for check and can 
be poll a lots of snmp information use snmpwalk. Has any one can help me how to 
monitor this device?   

And post the zenmodeler info as follow:
./zenmodeler run -d 136.139.96.249 -v10
DEBUG:zen.ZenModeler:Run in foreground, starting immediately.
DEBUG:zen.ZenModeler:run
DEBUG:zen.ZenModeler:Connecting to localhost:8789
DEBUG:zen.ZenModeler:Logging in as admin
INFO:zen.ZenModeler:Connected to ZenHub
DEBUG:zen.ZenModeler:setting up services EventService, ModelerService
DEBUG:zen.ZenModeler:chaining getInitialServices with d2
DEBUG:zen.ZenModeler:callback after getting service EventService
DEBUG:zen.ZenModeler:callback after getting service ModelerService
DEBUG:zen.ZenModeler:Calling connected.
DEBUG:zen.ZenModeler:connected
DEBUG:zen.ZenModeler:Sending event {'severity': 0, 'component': 'zenmodeler', 
'agent': 'zenmodeler', 'summary': 'started', 'manager': 'localhost', 'device': 
'localhost', 'eventClass': '/App/Start'}
DEBUG:zen.ZenModeler:fetching monitor properties
DEBUG:zen.ZenModeler:Getting threshold classes...
DEBUG:zen.ZenModeler:Loading classes ['Products.ZenModel.MinMaxThreshold']
DEBUG:zen.ZenModeler:Fetching default RRDCreateCommand...
DEBUG:zen.ZenModeler:Getting collector thresholds...
DEBUG:zen.thresholds:Updating threshold ('zeneventlog cycle time', 
('localhost', ''))
DEBUG:zen.thresholds:Updating threshold ('zenmodeler cycle time', ('localhost', 
''))
DEBUG:zen.thresholds:Updating threshold ('zenperfsnmp cycle time', 
('localhost', ''))
DEBUG:zen.thresholds:Updating threshold ('zenping cycle time', ('localhost', 
''))
DEBUG:zen.thresholds:Updating threshold ('zenprocess cycle time', ('localhost', 
''))
DEBUG:zen.thresholds:Updating threshold ('zenwin cycle time', ('localhost', ''))
DEBUG:zen.ZenModeler:Starting collector loop...
INFO:zen.ZenModeler:Collecting for device 136.139.96.249
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.DeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.InterfaceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.RouteMap
INFO:zen.ZenModeler:No WMI plugins found for 136.139.96.249
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.DeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.InterfaceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.RouteMap
INFO:zen.ZenModeler:No Python plugins found for 136.139.96.249
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.DeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.InterfaceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.RouteMap
INFO:zen.ZenModeler:No command plugins found for 136.139.96.249
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.DeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.InterfaceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.RouteMap
DEBUG:zen.ZenModeler:Using zenoss.snmp.NewDeviceMap on 136.139.96.249
DEBUG:zen.ZenModeler:Using zenoss.snmp.DeviceMap on 136.139.96.249
DEBUG:zen.ZenModeler:Using zenoss.snmp.InterfaceMap on 136.139.96.249
DEBUG:zen.ZenModeler:Using zenoss.snmp.RouteMap on 136.139.96.249
INFO:zen.ZenModeler:SNMP collection device 136.139.96.249
INFO:zen.ZenModeler:plugins: zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap, 
zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap
DEBUG:zen.SnmpClient:Starting SNMP info for 136.139.96.249 at 
136.139.96.249:161 timeout: 3.5 tries: 3 version: v3  securityName: Nagios 
authType:  privType: 
DEBUG:zen.SnmpClient:Testing SNMP configuration
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.DeviceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.InterfaceMap
DEBUG:zen.ZenModeler:Loaded plugin zenoss.snmp.RouteMap
INFO:zen.ZenModeler:No portscan plugins found for 136.139.96.249
DEBUG:zen.ZenModeler:Running 1 clients
DEBUG:zen.ZenModeler:Collection slots filled
DEBUG:zen.ZenModeler:Running 1 clients
DEBUG:zen.SnmpClient:running <zenoss.snmp.NewDeviceMap.NewDeviceMap instance at 
0xa6e366c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.NewDeviceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.DeviceMap.DeviceMap instance at 
0xa7ae20c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.DeviceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.InterfaceMap.InterfaceMap instance at 
0xa7ae22c>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.InterfaceMap
DEBUG:zen.SnmpClient:running <zenoss.snmp.RouteMap.RouteMap instance at 
0xa7ae1cc>
DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.RouteMap
INFO:zen.SnmpClient:snmp client finished collection for 136.139.96.249
DEBUG:zen.ZenModeler:Client for 136.139.96.249 finished collecting
DEBUG:zen.ZenModeler:Processing data for device 136.139.96.249
DEBUG:zen.ZenModeler:Processing plugin zenoss.snmp.InterfaceMap on device 
136.139.96.249 ...
INFO:zen.ZenModeler:processing zenoss.snmp.InterfaceMap for device 
136.139.96.249
DEBUG:zen.ZenModeler:Processing plugin zenoss.snmp.RouteMap on device 
136.139.96.249 ...
INFO:zen.ZenModeler:processing zenoss.snmp.RouteMap for device 136.139.96.249
INFO:zen.ZenModeler:No change in configuration detected
DEBUG:zen.ZenModeler:Client 136.139.96.249 finished
DEBUG:zen.ZenModeler:Running 0 clients
INFO:zen.ZenModeler:Scan time: 0.60 seconds
DEBUG:zen.thresholds:Checking value 0.601990938187 on 
Daemons/localhost/zenmodeler_cycleTime
DEBUG:zen.MinMaxCheck:Checking zenmodeler_cycleTime 0.601990938187 against min 
None and max 34560.0
DEBUG:zen.ZenModeler:Sending event {'manager': 'localhost', 'eventKey': 
'zenmodeler cycle time', 'device': 'localhost', 'eventClass': '/Perf', 
'summary': 'threshold of zenmodeler cycle time restored: current value: 0.60', 
'component': '', 'agent': 'zenmodeler', 'severity': 0}
DEBUG:zen.ZenModeler:Running 0 clients
INFO:zen.ZenModeler:Daemon ZenModeler shutting down
DEBUG:zen.ZenModeler:removing service EventService
DEBUG:zen.ZenModeler:removing service ModelerService
INFO:zen.ZenModeler:zenmodeler shutting down




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=31612#31612

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to