Nexus 7000/5000

[Ortner, Gerald]

Hi,

The only working CPU OIDs (CISCO-PROCESS-MIB) I found for Nexus 7000 are.
.1.3.6.1.4.1.9.9.109.1.1.1.1.6  The overall CPU busy percentage in the last 5 second period
.1.3.6.1.4.1.9.9.109.1.1.1.1.7  The overall CPU busy percentage in the last 1 minute period
.1.3.6.1.4.1.9.9.109.1.1.1.1.8  The overall CPU busy percentage in the last 5 minute period

And ( CISCO-SYSTEM-EXT-MIB)
.1.3.6.1.4.1.9.9.305.1.1.2.0    The average utilization of CPU on the active supervisor.


Gerald


-----Ursprüngliche Nachricht-----
Von: Nagios User [mailto:john.nagios at gmail.com]
Gesendet: Donnerstag, 09. September 2010 20:50
An: Nagios Users List
Betreff: Re: [Nagios-users] Nexus 7000/5000

Kyle,
Thanks! I was at the same the site checking for an OID. Also tried fiddling with some OIDs with no luck. Will keep messing with different OIDs untill I find a solution.

Thanks,
--john

On Thu, Sep 9, 2010 at 1:55 PM, Kyle O'Donnell <nagios at isprime.org> wrote:
> the nexus 5k and 7k dont run IOS.  I suspect there's an entirely
> different set of OIDs to query.
>
> ftp://ftp-sj.cisco.com/pub/mibs/supportlists/nexus5000/Nexus5000MIBSup
> portList.html
>
>
>
> On Thu, 9 Sep 2010 13:17:52 -0400, Nagios User <john.nagios at gmail.com>
> wrote:
>> Anyone monitoring Cisco's Nexus 7000/5000 for load average? The
>> existing plugin (check_snmp_cisco_loadavg) gives an OID error. Please
>> help me with this.
>>
>> root at nagios:/usr/local/nagios/libexec# ./check_snmp_cisco_loadavg -H
>> 10.31.101.134 -C blabla
>> Status is a WARNING level - SNMP OID does not exist
>>
>>
>> --john
>>
>> ---------------------------------------------------------------------
>> --------- This SF.net Dev2Dev email is sponsored by:
>>
>> Show off your parallel programming skills.
>> Enter the Intel(R) Threading Challenge 2010.
>> http://p.sf.net/sfu/intel-thread-sfd
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when
>> reporting any issue.
>> ::: Messages without supporting info will risk being sent to
>> /dev/null
>
>
> ----------------------------------------------------------------------
> -------- This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null

OOe. Gesundheits- und Spitals-AG
Techcenter, Hafenstrasse 47-51, 4020 Linz DVR 2107870, ATU 51928204, Firmenbuchgericht: Landesgericht Linz, FN 210146 p

------------------------------------------------------------------------------
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful, 
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance. 
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null