CISCO-PROCESS-MIB does indeed contain process-related oids but 
it also contains the new CPU stuff:

    ciscoProcessMIBObjects OBJECT IDENTIFIER ::= { ciscoProcessMIB 1 }
    cpmCPU          OBJECT IDENTIFIER ::= { ciscoProcessMIBObjects 1 }
    cpmProcess      OBJECT IDENTIFIER ::= { ciscoProcessMIBObjects 2 }
    cpmCPUHistory   OBJECT IDENTIFIER ::= { cpmProcess 5 }

    ... etc...

Stuff I want to watch under ciscoEnvMon is also indexed.

Thanks.



On Wed, Dec 20, 2006 at 09:14:14PM -0500, Erik A. Dahl wrote:
> David,
> 
> To monitor oids that have indexes we currently need to extend the  
> model... What we need to do is make it easy to extend the model in  
> arbitrary ways.  That said we do have CPU in the model and I think  
> the "modern" way to monitor cisco cpus is to basically use a cpu  
> index correct?   I haven't looked at the PROCESS-MIB but it sounds  
> like its more of a process list then a CPU list...
> 
> -EAD
> 
> On Dec 20, 2006, at 4:24 PM, David Carmean wrote:
> 
> >
> > So I've managed to create an RRDTemplate that monitors the deprecated
> > Cisco avgBusy1, etc, CPU load objects; since this this is a non- 
> > indexed OID,
> > I can place it in the .../Device RRDTemplate.
> >
> > However, the more modern CISCO-PROCESS-MIB has a set of indexed  
> > objects such
> > as cpmCPUTotal1Min.  I think I've just learned that the .../Device  
> > RRDTemplates
> > can't deal with indexed objects; is that correct?  And I also want  
> > to add
> > Cisco environment monitoring, which will also be indexed.
> >
> > What needs to be done to extend the system to handle (model?) the  
> > additional
> > Meta Types (?) required to monitor arbitrary indexed objects?
> >
> > Thanks.
> >
> > _______________________________________________
> > 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
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to