<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>  <style>  </style> </head> <body lang=EN-AU link=blue vlink=purple> <div class=Section1> I recall an issue getting the correct syntax when I transitioned from cli snmp MIB gets, however I need time to go back through my commissioning notes to find out what the roo issue was.<o:p></o:p> In the meantime this below is a sample of what I'm currently using:<o:p></o:p> <o:p> </o:p> cmmands.cfg:<o:p></o:p> define command{<o:p></o:p> command_name check_snmp<o:p></o:p> command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$<o:p></o:p> }<o:p></o:p> <o:p> </o:p> ACE-snmp-check.cfg extract:<o:p></o:p> define service{<o:p></o:p> use generic-service-t5<o:p></o:p> host_name DC1 ACE sub-system - ACE module - acedc01c6504<o:p></o:p> service_description Context-PACSTEST throughput [through the ACE Bytes per second] - Denied <o:p></o:p> check_command check_snmp!-C ROpassword@SpecificContext -P 2c -o .1.3.6.1.4.1.9.9.480.1.1.4.1.8.8.80.65.67.83.84.69.83.84.11 -w 1 -c 2 ; <o:p></o:p> servicegroups ACE-DC1-SpecificContext<o:p></o:p> }<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> -----Original Message----- From: Jonathan Aquilina [mailto:eagles051387@gmail.com] Sent: Monday, 8 August 2011 2:47 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Monitoring throughput for compression and SSL oncisco ace 4710 <o:p> </o:p> Stuart my output is as follows<o:p></o:p> <o:p> </o:p> -o .1.3.6.1.4.1.9.9.254.1.1.1.1.3.1 -C $HOSTSNMP_COMMUNITY$ -w @40:44 -c <o:p></o:p> ~:45 -t 60<o:p></o:p> <o:p> </o:p> it works on command line but times out when the check runs normally <o:p></o:p> after setting it up in nagios ql.<o:p></o:p> <o:p> </o:p> On 08/08/2011 01:02, Jones, Stuart wrote:<o:p></o:p> > Can you provide details of your check_snmp command please?<o:p></o:p> ><o:p> </o:p> > -----Original Message-----<o:p></o:p> > From: Jonathan Aquilina [mailto:eagles051387@gmail.com]<o:p></o:p> > Sent: Friday, 5 August 2011 3:28 PM<o:p></o:p> > To: Nagios Users List<o:p></o:p> > Subject: Re: [Nagios-users] Monitoring throughput for compression and<o:p></o:p> > SSL oncisco ace 4710<o:p></o:p> ><o:p> </o:p> > ok. i got that sorted more or less but what im not getting is this.<o:p></o:p> ><o:p> </o:p> > I run the check snmp via commandline it runs fine, but in regards to ssl<o:p></o:p> > when i run the check via nagios and not command line it times out. i<o:p></o:p> > added the -t switch to increase the time out but its not working. it<o:p></o:p> > still times out. any ideas?<o:p></o:p> ><o:p> </o:p> > On 05/08/2011 09:17, Jones, Stuart wrote:<o:p></o:p> >> If you load the MIB file: CISCO-L4L7MODULE-RESOURCE-LIMIT-MIB into<o:p></o:p> >> your snmp directory then use a snmpwalk referencing that MIB, or use a<o:p></o:p> >> MIB browser, you should get something like:<o:p></o:p> >><o:p> </o:p> >> crlResourceSummaryCurrentUsage.26 0 Gauge<o:p></o:p> >> crlResourceSummaryCurrentUsage.27 6094 Gauge<o:p></o:p> >> crlResourceSummaryCurrentUsage.28 16652203 Gauge<o:p></o:p> >> crlResourceSummaryCurrentUsage.29 0 Gauge<o:p></o:p> >> crlResourceSummaryPeakUsage.2 9113 Gauge<o:p></o:p> >> crlResourceSummaryPeakUsage.3 410 Gauge<o:p></o:p> >> crlResourceSummaryPeakUsage.4 389 Gauge<o:p></o:p> >> crlResourceSummaryPeakUsage.6 2771 Gauge<o:p></o:p> >><o:p> </o:p> >><o:p> </o:p> >> You can then use Nagios, check_snmp, to query& alert based on a<o:p></o:p> >> threshold you define subject to your licence and setting.<o:p></o:p> >><o:p> </o:p> >><o:p> </o:p> >> -----Original Message-----<o:p></o:p> >> From: Jonathan Aquilina [mailto:eagles051387@gmail.com]<o:p></o:p> >> Sent: Thursday, 4 August 2011 2:43 PM<o:p></o:p> >> To: nagios-users@lists.sourceforge.net<o:p></o:p> >> Subject: Re: [Nagios-users] Monitoring throughput for compression and<o:p></o:p> >> SSL oncisco ace 4710<o:p></o:p> >><o:p> </o:p> >> Does the OID work for both compression and SSL?<o:p></o:p> >><o:p> </o:p> >> On 04/08/2011 01:49, Jones, Stuart wrote:<o:p></o:p> >>> I'm using the subset from:<o:p></o:p> >>><o:p> </o:p> >>> 1.3.6.1.4.1.9.9.480<o:p></o:p> >>><o:p> </o:p> >>> Try it and let me know if you need further assistance.<o:p></o:p> >>><o:p> </o:p> >>> -----Original Message-----<o:p></o:p> >>> From: Jonathan Aquilina [mailto:eagles051387@gmail.com]<o:p></o:p> >>> Sent: Wednesday, 3 August 2011 3:07 PM<o:p></o:p> >>> To: Nagios Users List<o:p></o:p> >>> Subject: [Nagios-users] Monitoring throughput for compression and SSL<o:p></o:p> >>> oncisco ace 4710<o:p></o:p> >>><o:p> </o:p> >>> Hey guys I am trying to monitor through put for the above services<o:p></o:p> >>> and device.<o:p></o:p> >>><o:p> </o:p> >>> I was told to use the check_snmp check, but I have no idea what OID I<o:p></o:p> >>> am<o:p></o:p> >>><o:p> </o:p> >>> looking for can anyone point me in the right direction for the OID i<o:p></o:p> >>> should be using?<o:p></o:p> >>><o:p> </o:p> >>> ---------------------------------------------------------------------<o:p></o:p> >>> -<o:p></o:p> >>> --<o:p></o:p> >>> ------<o:p></o:p> >>> BlackBerry® DevCon Americas, Oct. 18-20, <st1:place w:st="on"><st1:City w:st="on">San Francisco</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place> The<o:p></o:p> >>> must-attend event for mobile developers. Connect with experts.<o:p></o:p> >>> Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> >>> Sessions, hands-on labs, demos& much more. Register early& save!<o:p></o:p> >>> http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> >>> _______________________________________________<o:p></o:p> >>> Nagios-users mailing list<o:p></o:p> >>> Nagios-users@lists.sourceforge.net<o:p></o:p> >>> https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> >>> ::: Please include Nagios version, plugin version (-v) and OS when<o:p></o:p> >>> reporting any issue.<o:p></o:p> >>> ::: Messages without supporting info will risk being sent to<o:p></o:p> >>> /dev/null<o:p></o:p> >>><o:p> </o:p> >>> ---------------------------------------------------------------------<o:p></o:p> >>> -<o:p></o:p> >>> -------- BlackBerry® DevCon Americas, Oct. 18-20, <st1:City w:st="on"><st1:place w:st="on">San Francisco</st1:place></st1:City>,<o:p></o:p> >>> CA The must-attend event for mobile developers. Connect with experts.<o:p></o:p> >>> Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> >>> Sessions, hands-on labs, demos& much more. Register early& save!<o:p></o:p> >>> http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> >>> _______________________________________________<o:p></o:p> >>> Nagios-users mailing list<o:p></o:p> >>> Nagios-users@lists.sourceforge.net<o:p></o:p> >>> https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> >>> ::: Please include Nagios version, plugin version (-v) and OS when<o:p></o:p> >> reporting any issue.<o:p></o:p> >>> ::: Messages without supporting info will risk being sent to<o:p></o:p> >>> /dev/null<o:p></o:p> >> ----------------------------------------------------------------------<o:p></o:p> >> --<o:p></o:p> >> ------<o:p></o:p> >> BlackBerry® DevCon Americas, Oct. 18-20, <st1:place w:st="on"><st1:City w:st="on">San Francisco</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place> The<o:p></o:p> >> must-attend event for mobile developers. Connect with experts.<o:p></o:p> >> Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> >> Sessions, hands-on labs, demos& much more. Register early& save!<o:p></o:p> >> http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> >> _______________________________________________<o:p></o:p> >> Nagios-users mailing list<o:p></o:p> >> Nagios-users@lists.sourceforge.net<o:p></o:p> >> https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> >> ::: Please include Nagios version, plugin version (-v) and OS when<o:p></o:p> >> reporting any issue.<o:p></o:p> >> ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> >><o:p> </o:p> >> ----------------------------------------------------------------------<o:p></o:p> >> -------- BlackBerry® DevCon Americas, Oct. 18-20, <st1:City w:st="on"><st1:place w:st="on">San Francisco</st1:place></st1:City>,<o:p></o:p> >> CA The must-attend event for mobile developers. Connect with experts.<o:p></o:p> >> Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> >> Sessions, hands-on labs, demos& much more. Register early& save!<o:p></o:p> >> http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> >> _______________________________________________<o:p></o:p> >> Nagios-users mailing list<o:p></o:p> >> Nagios-users@lists.sourceforge.net<o:p></o:p> >> https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> >> ::: Please include Nagios version, plugin version (-v) and OS when<o:p></o:p> > reporting any issue.<o:p></o:p> >> ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> ><o:p> </o:p> > ------------------------------------------------------------------------<o:p></o:p> > ------<o:p></o:p> > BlackBerry® DevCon Americas, Oct. 18-20, <st1:place w:st="on"><st1:City w:st="on">San Francisco</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place> The<o:p></o:p> > must-attend event for mobile developers. Connect with experts.<o:p></o:p> > Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> > Sessions, hands-on labs, demos& much more. Register early& save!<o:p></o:p> > http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> > _______________________________________________<o:p></o:p> > Nagios-users mailing list<o:p></o:p> > Nagios-users@lists.sourceforge.net<o:p></o:p> > https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> > ::: Please include Nagios version, plugin version (-v) and OS when<o:p></o:p> > reporting any issue.<o:p></o:p> > ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> ><o:p> </o:p> > ------------------------------------------------------------------------------<o:p></o:p> > BlackBerry® DevCon Americas, Oct. 18-20, <st1:place w:st="on"><st1:City w:st="on">San Francisco</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place><o:p></o:p> > The must-attend event for mobile developers. Connect with experts.<o:p></o:p> > Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> > Sessions, hands-on labs, demos& much more. Register early& save!<o:p></o:p> > http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> > _______________________________________________<o:p></o:p> > Nagios-users mailing list<o:p></o:p> > Nagios-users@lists.sourceforge.net<o:p></o:p> > https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> > ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<o:p></o:p> > ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> <o:p> </o:p> <o:p> </o:p> ------------------------------------------------------------------------------<o:p></o:p> BlackBerry® DevCon Americas, Oct. 18-20, <st1:place w:st="on"><st1:City w:st="on">San Francisco</st1:City>, <st1:State w:st="on">CA</st1:State></st1:place><o:p></o:p> The must-attend event for mobile developers. Connect with experts. <o:p></o:p> Get tools for creating Super Apps. See the latest technologies.<o:p></o:p> Sessions, hands-on labs, demos & much more. Register early & save!<o:p></o:p> http://p.sf.net/sfu/rim-blackberry-1<o:p></o:p> _______________________________________________<o:p></o:p> Nagios-users mailing list<o:p></o:p> Nagios-users@lists.sourceforge.net<o:p></o:p> https://lists.sourceforge.net/lists/listinfo/nagios-users<o:p></o:p> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. <o:p></o:p> ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> </div> </body> </html>