Chet, I can reliably reproduce a bug where, even after verifying that the "ccmHistoryRunningLastChanged" OID has been updated, the device isn't fully remodeled:
[EMAIL PROTECTED]:~$ zenmodeler run --debug --device uspdxvg01.vestas.net INFO:zen.ZenModeler:starting collector loop INFO:zen.ZenModeler:collecting for device uspdxvg01.vestas.net INFO:zen.ZenModeler:no cmd plugins found for uspdxvg01.vestas.net INFO:zen.ZenModeler:snmp collection device uspdxvg01.vestas.net INFO:zen.ZenModeler:plugins: zenoss.snmp.CiscoHSRP, zenoss.snmp.CiscoMap, zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap INFO:zen.ZenModeler:no portscan plugins found for uspdxvg01.vestas.net lastpolluptime = 134937116 lastchange = 134965132 INFO:zen.SnmpClient:snmp client finished collection for uspdxvg01.vestas.net INFO:zen.ApplyDataMap:no change detected INFO:zen.ZenModeler:scan time: 0.42 seconds INFO:zen.ZenModeler:stopping... note "lastpolluptime" and "lastchange" are different, yet I have to use the -F flag in order for the modeler to update the device. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chet Luther > Sent: Wednesday, 28 November, 2007 13:59 > To: [email protected] > Subject: Re: [zenoss-users] Modeling devices automagically? > > > We are monitoring a few cisco switches and routers. > > The thing is that we get graphs on the if that were up when the > > discovery runned, But when things changes in like if description, > > interfaces goes up and so on... The device don't update unless we > > run a model device manually. > > > > Is that the correct way or do I have to do anything in a > cron job or > > such? > > This is actually due to a Cisco specific feature of Zenoss. Cisco > devices have an OID that you can query to determine the last time > anything about the device was changed. If we have modeled the device > since this time, we skip modeling. Unfortunately it appears > as though > Cisco devices don't reliably update this value so changes are > missed. > The reason that manually modeling the devices works is that > it sets a > "--force" flag on the modeling that skips the Cisco check. > > You can make this the default behavior of zenmodeler by stopping it > and running "zenmodeler start --force" from the command line as the > zenoss user. > > Ticket: > http://dev.zenoss.org/trac/ticket/2004 > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users > _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
