You can subscribe to this list here.
2006 |
Jan
|
Feb
(38) |
Mar
(131) |
Apr
(5) |
May
(23) |
Jun
(9) |
Jul
(9) |
Aug
(9) |
Sep
(24) |
Oct
(28) |
Nov
(33) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(45) |
Feb
(22) |
Mar
(52) |
Apr
(17) |
May
(4) |
Jun
(68) |
Jul
(12) |
Aug
(25) |
Sep
(63) |
Oct
(45) |
Nov
(25) |
Dec
(76) |
2008 |
Jan
(34) |
Feb
(53) |
Mar
(30) |
Apr
(42) |
May
(50) |
Jun
(45) |
Jul
(21) |
Aug
(36) |
Sep
(33) |
Oct
(28) |
Nov
(32) |
Dec
(16) |
2009 |
Jan
(35) |
Feb
(36) |
Mar
(32) |
Apr
(24) |
May
(26) |
Jun
(15) |
Jul
(17) |
Aug
(30) |
Sep
(14) |
Oct
(18) |
Nov
(26) |
Dec
(22) |
2010 |
Jan
(11) |
Feb
(33) |
Mar
(35) |
Apr
(16) |
May
(11) |
Jun
(4) |
Jul
(36) |
Aug
(3) |
Sep
(14) |
Oct
(5) |
Nov
(10) |
Dec
(12) |
2011 |
Jan
(7) |
Feb
(31) |
Mar
(13) |
Apr
(14) |
May
(18) |
Jun
(25) |
Jul
(6) |
Aug
(23) |
Sep
(20) |
Oct
(18) |
Nov
(4) |
Dec
(9) |
2012 |
Jan
(32) |
Feb
(4) |
Mar
(15) |
Apr
(3) |
May
(8) |
Jun
(9) |
Jul
(6) |
Aug
(6) |
Sep
|
Oct
(14) |
Nov
(22) |
Dec
(4) |
2013 |
Jan
(16) |
Feb
(11) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(6) |
Jul
|
Aug
(5) |
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(5) |
Nov
(5) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
(3) |
Apr
(4) |
May
|
Jun
(1) |
Jul
(19) |
Aug
(4) |
Sep
(13) |
Oct
(3) |
Nov
(8) |
Dec
(4) |
2016 |
Jan
(18) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(7) |
2017 |
Jan
(5) |
Feb
|
Mar
(3) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(5) |
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Root, P. <Pau...@qw...> - 2011-06-06 20:00:06
|
Anybody have a Cisco ACS that they are monitoring with Devmon? Paul Root Lead Internet Systems Eng CenturyLink This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. |
From: Josh L. <jo...@im...> - 2011-06-02 19:23:11
|
Sorry about that, I didn't recognize that format. I made the changes, deleting power.rrd and the file is no longer being generated. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Thu, Jun 2, 2011 at 4:12 AM, Buchan Milne <bg...@st...>wrote: > I supplied a diff you should have been able to apply to the original > messages > file. > > Here is the complete modified messages file: > > > {upsStatus.errors} > {upsBattStat.errors} > {upsLoadOut.errors} > {upsBattRep.errors} > {upsVoltageIn.errors} > > UPS status: > > Vendor: apc > Model: {upsModel} > > UPS Status: {upsOutStat} > Battery Status: {upsBattStat} > > Runtime Remaining: {upsMinsRunTime} > - minutes (red={upsMinsRunTime.thresh:red}m) > Battery Capacity: {upsBattCap}% > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > red={upsLoadOut.thresh:red}%) > > Voltage in: {upsVoltageIn} > (yellow={upsVoltageIn.thresh:yellow}v > red={upsVoltageIn.thresh:red}v) > Voltage out: {upsVoltageOut} > > Last failure due to: {upsFailCause} > Time on battery: {upsSecsOnBatt} > - seconds > > > Regards, > Buchan > > On Wednesday, 1 June 2011 18:00:33 Josh Luthman wrote: > > I put that information in the message file and now it is putting that on > > the Xymon page ( > > http://172.16.0.114/xymon-cgi/svcstatus.sh?HOST=stouderapc&SERVICE=power) > > > > Looks like this: http://i.imgur.com/dGAzY.png > > > > It doesn't look like it's reading it correctly or I told it to do > something > > wrong. > > > > Josh Luthman > > Office: 937-552-2340 > > Direct: 937-552-2343 > > 1100 Wayne St > > Suite 1337 > > Troy, OH 45373 > > > > On Wed, Jun 1, 2011 at 10:46 AM, Buchan Milne > <bg...@st...>wrote: > > > On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > > > > >No version of this template has had RRD support for the power test > > > > > > (yet). > > > > > > > If > > > > > > > > >you have a temperature sensor, the 'temp' test should though. > > > > > > > > I don't have a temp column, should I? I get an answer for the first > > > > OID but the humidity is -1. > > > > > > > > >This should not be necessary in 4.2.3 or later. > > > > > > > > I'll remove it once everything is working, thanks for the tip. I am > > > > running 4.3.2 > > > > > > > > > bb localhost 'hobbitdlog ups.power' > > > > > > > > http://pastebin.com/DaySRCTe > > > > > > No RRD "header" for the devmon collector. > > > > > > > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > > > > > > > http://pastebin.com/2hjKyrXZ > > > > > > Looks like this was collected by NCV, but the values following the "C" > > > are not > > > pure numeric. I would suggest you play with the formatting in the > > > messages file to ensure that lines with a colon are strictly: > > > > > > Name : value > > > > > > Something like this: > > > > > > Index: templates/apc-9619/power/message > > > =================================================================== > > > --- templates/apc-9619/power/message (revision 225) > > > +++ templates/apc-9619/power/message (working copy) > > > @@ -12,12 +12,15 @@ > > > > > > UPS Status: {upsOutStat} > > > Battery Status: {upsBattStat} > > > > > > -Runtime Remaining: {upsMinsRunTime} minutes > > > (red={upsMinsRunTime.thresh:red}m) > > > +Runtime Remaining: {upsMinsRunTime} > > > + - minutes (red={upsMinsRunTime.thresh:red}m) > > > > > > Battery Capacity: {upsBattCap}% > > > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > > > > > > red={upsLoadOut.thresh:red}%) > > > > > > -Voltage in: {upsVoltageIn}v > > > (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) > > > -Voltage out: {upsVoltageOut}v > > > +Voltage in: {upsVoltageIn} > > > + (yellow={upsVoltageIn.thresh:yellow}v > > > red={upsVoltageIn.thresh:red}v) > > > +Voltage out: {upsVoltageOut} > > > > > > Last failure due to: {upsFailCause} > > > > > > -Time on battery: {upsSecsOnBatt} secs > > > +Time on battery: {upsSecsOnBatt} > > > + - seconds > > > > > > > > > Regards, > > > Buchan > |
From: Buchan M. <bg...@st...> - 2011-06-02 08:12:25
|
I supplied a diff you should have been able to apply to the original messages file. Here is the complete modified messages file: {upsStatus.errors} {upsBattStat.errors} {upsLoadOut.errors} {upsBattRep.errors} {upsVoltageIn.errors} UPS status: Vendor: apc Model: {upsModel} UPS Status: {upsOutStat} Battery Status: {upsBattStat} Runtime Remaining: {upsMinsRunTime} - minutes (red={upsMinsRunTime.thresh:red}m) Battery Capacity: {upsBattCap}% UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% red={upsLoadOut.thresh:red}%) Voltage in: {upsVoltageIn} (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) Voltage out: {upsVoltageOut} Last failure due to: {upsFailCause} Time on battery: {upsSecsOnBatt} - seconds Regards, Buchan On Wednesday, 1 June 2011 18:00:33 Josh Luthman wrote: > I put that information in the message file and now it is putting that on > the Xymon page ( > http://172.16.0.114/xymon-cgi/svcstatus.sh?HOST=stouderapc&SERVICE=power ) > > Looks like this: http://i.imgur.com/dGAzY.png > > It doesn't look like it's reading it correctly or I told it to do something > wrong. > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Wed, Jun 1, 2011 at 10:46 AM, Buchan Milne <bg...@st...>wrote: > > On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > > > >No version of this template has had RRD support for the power test > > > > (yet). > > > > > If > > > > > > >you have a temperature sensor, the 'temp' test should though. > > > > > > I don't have a temp column, should I? I get an answer for the first > > > OID but the humidity is -1. > > > > > > >This should not be necessary in 4.2.3 or later. > > > > > > I'll remove it once everything is working, thanks for the tip. I am > > > running 4.3.2 > > > > > > > bb localhost 'hobbitdlog ups.power' > > > > > > http://pastebin.com/DaySRCTe > > > > No RRD "header" for the devmon collector. > > > > > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > > > > > http://pastebin.com/2hjKyrXZ > > > > Looks like this was collected by NCV, but the values following the "C" > > are not > > pure numeric. I would suggest you play with the formatting in the > > messages file to ensure that lines with a colon are strictly: > > > > Name : value > > > > Something like this: > > > > Index: templates/apc-9619/power/message > > =================================================================== > > --- templates/apc-9619/power/message (revision 225) > > +++ templates/apc-9619/power/message (working copy) > > @@ -12,12 +12,15 @@ > > > > UPS Status: {upsOutStat} > > Battery Status: {upsBattStat} > > > > -Runtime Remaining: {upsMinsRunTime} minutes > > (red={upsMinsRunTime.thresh:red}m) > > +Runtime Remaining: {upsMinsRunTime} > > + - minutes (red={upsMinsRunTime.thresh:red}m) > > > > Battery Capacity: {upsBattCap}% > > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > > > > red={upsLoadOut.thresh:red}%) > > > > -Voltage in: {upsVoltageIn}v > > (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) > > -Voltage out: {upsVoltageOut}v > > +Voltage in: {upsVoltageIn} > > + (yellow={upsVoltageIn.thresh:yellow}v > > red={upsVoltageIn.thresh:red}v) > > +Voltage out: {upsVoltageOut} > > > > Last failure due to: {upsFailCause} > > > > -Time on battery: {upsSecsOnBatt} secs > > +Time on battery: {upsSecsOnBatt} > > + - seconds > > > > > > Regards, > > Buchan |
From: Josh L. <jo...@im...> - 2011-06-01 16:01:00
|
I put that information in the message file and now it is putting that on the Xymon page ( http://172.16.0.114/xymon-cgi/svcstatus.sh?HOST=stouderapc&SERVICE=power ) Looks like this: http://i.imgur.com/dGAzY.png It doesn't look like it's reading it correctly or I told it to do something wrong. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Wed, Jun 1, 2011 at 10:46 AM, Buchan Milne <bg...@st...>wrote: > On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > > >No version of this template has had RRD support for the power test > (yet). > > > > If > > > > >you have a temperature sensor, the 'temp' test should though. > > > > I don't have a temp column, should I? I get an answer for the first OID > > but the humidity is -1. > > > > >This should not be necessary in 4.2.3 or later. > > > > I'll remove it once everything is working, thanks for the tip. I am > > running 4.3.2 > > > > > bb localhost 'hobbitdlog ups.power' > > > > http://pastebin.com/DaySRCTe > > No RRD "header" for the devmon collector. > > > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > > > http://pastebin.com/2hjKyrXZ > > Looks like this was collected by NCV, but the values following the "C" are > not > pure numeric. I would suggest you play with the formatting in the messages > file to ensure that lines with a colon are strictly: > > Name : value > > Something like this: > > Index: templates/apc-9619/power/message > =================================================================== > --- templates/apc-9619/power/message (revision 225) > +++ templates/apc-9619/power/message (working copy) > @@ -12,12 +12,15 @@ > UPS Status: {upsOutStat} > Battery Status: {upsBattStat} > > -Runtime Remaining: {upsMinsRunTime} minutes > (red={upsMinsRunTime.thresh:red}m) > +Runtime Remaining: {upsMinsRunTime} > + - minutes (red={upsMinsRunTime.thresh:red}m) > Battery Capacity: {upsBattCap}% > UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% > red={upsLoadOut.thresh:red}%) > > -Voltage in: {upsVoltageIn}v (yellow={upsVoltageIn.thresh:yellow}v > red={upsVoltageIn.thresh:red}v) > -Voltage out: {upsVoltageOut}v > +Voltage in: {upsVoltageIn} > + (yellow={upsVoltageIn.thresh:yellow}v > red={upsVoltageIn.thresh:red}v) > +Voltage out: {upsVoltageOut} > > Last failure due to: {upsFailCause} > -Time on battery: {upsSecsOnBatt} secs > +Time on battery: {upsSecsOnBatt} > + - seconds > > > Regards, > Buchan > |
From: Buchan M. <bg...@st...> - 2011-06-01 14:47:02
|
On Wednesday, 1 June 2011 16:30:44 Josh Luthman wrote: > >No version of this template has had RRD support for the power test (yet). > > If > > >you have a temperature sensor, the 'temp' test should though. > > I don't have a temp column, should I? I get an answer for the first OID > but the humidity is -1. > > >This should not be necessary in 4.2.3 or later. > > I'll remove it once everything is working, thanks for the tip. I am > running 4.3.2 > > > bb localhost 'hobbitdlog ups.power' > > http://pastebin.com/DaySRCTe No RRD "header" for the devmon collector. > >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd > > http://pastebin.com/2hjKyrXZ Looks like this was collected by NCV, but the values following the "C" are not pure numeric. I would suggest you play with the formatting in the messages file to ensure that lines with a colon are strictly: Name : value Something like this: Index: templates/apc-9619/power/message =================================================================== --- templates/apc-9619/power/message (revision 225) +++ templates/apc-9619/power/message (working copy) @@ -12,12 +12,15 @@ UPS Status: {upsOutStat} Battery Status: {upsBattStat} -Runtime Remaining: {upsMinsRunTime} minutes (red={upsMinsRunTime.thresh:red}m) +Runtime Remaining: {upsMinsRunTime} + - minutes (red={upsMinsRunTime.thresh:red}m) Battery Capacity: {upsBattCap}% UPS Load: {upsLoadOut}% (yellow={upsLoadOut.thresh:yellow}% red={upsLoadOut.thresh:red}%) -Voltage in: {upsVoltageIn}v (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) -Voltage out: {upsVoltageOut}v +Voltage in: {upsVoltageIn} + (yellow={upsVoltageIn.thresh:yellow}v red={upsVoltageIn.thresh:red}v) +Voltage out: {upsVoltageOut} Last failure due to: {upsFailCause} -Time on battery: {upsSecsOnBatt} secs +Time on battery: {upsSecsOnBatt} + - seconds Regards, Buchan |
From: Josh L. <jo...@im...> - 2011-06-01 14:31:13
|
>No version of this template has had RRD support for the power test (yet). If >you have a temperature sensor, the 'temp' test should though. I don't have a temp column, should I? I get an answer for the first OID but the humidity is -1. >This should not be necessary in 4.2.3 or later. I'll remove it once everything is working, thanks for the tip. I am running 4.3.2 > bb localhost 'hobbitdlog ups.power' http://pastebin.com/DaySRCTe >rrdtool info /home/xymon/data/rrd/stouderapc/power.rrd http://pastebin.com/2hjKyrXZ Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Wed, Jun 1, 2011 at 9:32 AM, Buchan Milne <bg...@st...>wrote: > On Tuesday, 31 May 2011 21:58:08 Josh Luthman wrote: > > I am trying to set up graphs for an APC 9619 (I am using the template > from > > the SF files directory). > > No version of this template has had RRD support for the power test (yet). > If > you have a temperature sensor, the 'temp' test should though. > > > The dm column appears on the bbdisp host. I am > > getting the power message on this host on Xymon and I can see the graph > > reference, but the image is blank/broken. > > > > I only have docs/GRAPHING to go by and I followed this by: > > > > * --extra-script /usr/share/devmon/extras/devmon-rrd.pl to both > rrdstatus > > and rrddata in tasks.cfg > > This should not be necessary in 4.2.3 or later. > > > * power=devmon to the end of TEST2RRD in xymonserver.cfg > > The devmon collector is intended for devmon's TABLE:rrd operator in message > files, however the power test doesn't operate on any repeater OIDs. The ncv > module may be more appropriate, but it may choke on some of the non-numeric > values that follow colons in the message file ... > > > * I'm at a complete loss in what would be accurate in Xymon's graphs.cfg, > > but I took an example from extras/devmon-graph.cfg and changed a few > > things. I was hoping to look at the RRD file for examples to help me > > complete this > > > > [power] > > FNPATTERN power.(.*).rrd > > TITLE Power > > YAXIS Volts > > DEF:in@RRDIDX@=@RRDFN@:ds0:AVERAGE > > CDEF:inbytes@RRDIDX@=in@RRDIDX@,8,* > > DEF:out@RRDIDX@=@RRDFN@:ds1:AVERAGE > > CDEF:outbytes@RRDIDX@=out@RRDIDX@,8,* > > LINE1:inbytes@RRDIDX@#@COLOR@:@RRDPARAM@ In > > GPRINT:inbytes@RRDIDX@:LAST: %8.2lf %s (cur) > > GPRINT:inbytes@RRDIDX@:MAX: %8.2lf %s (max) > > GPRINT:inbytes@RRDIDX@:MIN: %8.2lf %s (min) > > GPRINT:inbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > > LINE1:outbytes@RRDIDX@#@COLOR@:@RRDPARAM@ Out > > GPRINT:outbytes@RRDIDX@:LAST: %8.2lf %s (cur) > > GPRINT:outbytes@RRDIDX@:MAX: %8.2lf %s (max) > > GPRINT:outbytes@RRDIDX@:MIN: %8.2lf %s (avg) > > GPRINT:outbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > > -l 0 > > > > > > I am looking at the RRD file and the values (min, max, value, etc) are > all > > NaN or 0.0000000000e+00 > > > > Can anyone point me in the right direction? > > Please supply the output of: > bb localhost 'hobbitdlog ups.power' > > or equivalent, where 'ups' is the host name of your APC 9619 in the > bb-hosts > file. > > The 'rrdtool info /path/to/file.rrd' would also help shed some light here. > > Regards, > Buchan > |
From: Buchan M. <bg...@st...> - 2011-06-01 13:32:11
|
On Tuesday, 31 May 2011 21:58:08 Josh Luthman wrote: > I am trying to set up graphs for an APC 9619 (I am using the template from > the SF files directory). No version of this template has had RRD support for the power test (yet). If you have a temperature sensor, the 'temp' test should though. > The dm column appears on the bbdisp host. I am > getting the power message on this host on Xymon and I can see the graph > reference, but the image is blank/broken. > > I only have docs/GRAPHING to go by and I followed this by: > > * --extra-script /usr/share/devmon/extras/devmon-rrd.pl to both rrdstatus > and rrddata in tasks.cfg This should not be necessary in 4.2.3 or later. > * power=devmon to the end of TEST2RRD in xymonserver.cfg The devmon collector is intended for devmon's TABLE:rrd operator in message files, however the power test doesn't operate on any repeater OIDs. The ncv module may be more appropriate, but it may choke on some of the non-numeric values that follow colons in the message file ... > * I'm at a complete loss in what would be accurate in Xymon's graphs.cfg, > but I took an example from extras/devmon-graph.cfg and changed a few > things. I was hoping to look at the RRD file for examples to help me > complete this > > [power] > FNPATTERN power.(.*).rrd > TITLE Power > YAXIS Volts > DEF:in@RRDIDX@=@RRDFN@:ds0:AVERAGE > CDEF:inbytes@RRDIDX@=in@RRDIDX@,8,* > DEF:out@RRDIDX@=@RRDFN@:ds1:AVERAGE > CDEF:outbytes@RRDIDX@=out@RRDIDX@,8,* > LINE1:inbytes@RRDIDX@#@COLOR@:@RRDPARAM@ In > GPRINT:inbytes@RRDIDX@:LAST: %8.2lf %s (cur) > GPRINT:inbytes@RRDIDX@:MAX: %8.2lf %s (max) > GPRINT:inbytes@RRDIDX@:MIN: %8.2lf %s (min) > GPRINT:inbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > LINE1:outbytes@RRDIDX@#@COLOR@:@RRDPARAM@ Out > GPRINT:outbytes@RRDIDX@:LAST: %8.2lf %s (cur) > GPRINT:outbytes@RRDIDX@:MAX: %8.2lf %s (max) > GPRINT:outbytes@RRDIDX@:MIN: %8.2lf %s (avg) > GPRINT:outbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n > -l 0 > > > I am looking at the RRD file and the values (min, max, value, etc) are all > NaN or 0.0000000000e+00 > > Can anyone point me in the right direction? Please supply the output of: bb localhost 'hobbitdlog ups.power' or equivalent, where 'ups' is the host name of your APC 9619 in the bb-hosts file. The 'rrdtool info /path/to/file.rrd' would also help shed some light here. Regards, Buchan |
From: Josh L. <jo...@im...> - 2011-05-31 20:28:51
|
I am trying to set up graphs for an APC 9619 (I am using the template from the SF files directory). The dm column appears on the bbdisp host. I am getting the power message on this host on Xymon and I can see the graph reference, but the image is blank/broken. I only have docs/GRAPHING to go by and I followed this by: * --extra-script /usr/share/devmon/extras/devmon-rrd.pl to both rrdstatus and rrddata in tasks.cfg * power=devmon to the end of TEST2RRD in xymonserver.cfg * I'm at a complete loss in what would be accurate in Xymon's graphs.cfg, but I took an example from extras/devmon-graph.cfg and changed a few things. I was hoping to look at the RRD file for examples to help me complete this [power] FNPATTERN power.(.*).rrd TITLE Power YAXIS Volts DEF:in@RRDIDX@=@RRDFN@:ds0:AVERAGE CDEF:inbytes@RRDIDX@=in@RRDIDX@,8,* DEF:out@RRDIDX@=@RRDFN@:ds1:AVERAGE CDEF:outbytes@RRDIDX@=out@RRDIDX@,8,* LINE1:inbytes@RRDIDX@#@COLOR@:@RRDPARAM@ In GPRINT:inbytes@RRDIDX@:LAST: %8.2lf %s (cur) GPRINT:inbytes@RRDIDX@:MAX: %8.2lf %s (max) GPRINT:inbytes@RRDIDX@:MIN: %8.2lf %s (min) GPRINT:inbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n LINE1:outbytes@RRDIDX@#@COLOR@:@RRDPARAM@ Out GPRINT:outbytes@RRDIDX@:LAST: %8.2lf %s (cur) GPRINT:outbytes@RRDIDX@:MAX: %8.2lf %s (max) GPRINT:outbytes@RRDIDX@:MIN: %8.2lf %s (avg) GPRINT:outbytes@RRDIDX@:AVERAGE: %8.2lf %s (avg)\n -l 0 I am looking at the RRD file and the values (min, max, value, etc) are all NaN or 0.0000000000e+00 Can anyone point me in the right direction? Thank you for this much needed addition to Xymon! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 |
From: Colin C. <col...@gm...> - 2011-05-29 05:54:21
|
I've made some progress on these but I'm out of the office for the next week or so, so I'll revisit this then. I'll post the resulting templates to the list when I'm done. CC On Sat, May 28, 2011 at 6:41 PM, Richard Finegold <gol...@gm...> wrote: > On Tue, May 17, 2011 at 00:05, Buchan Milne <bg...@st...> wrote: >> On Tuesday, 17 May 2011 08:16:22 Colin Coe wrote: > [snip] >>> >> I can get data up for the Smart UPS but it is not being automatically >>> >> detected. I have the following as the spec file >>> >> cat /usr/share/devmon/templates/apc-sups-1000rm/specs >>> >> vendor : apc >>> >> model : Smart-UPS 1000 RM >>> >> snmpver : 1 >>> >> sysdesc : Smart-UPS 1000 RM >> >> Note that the template name ('apc-sups-1000rm') must be composed of <vendor>- >> <model>. So, your model should be 'sups-1000rm', otherwise your template won't >> be recognised. Please run devmon with some verbosity, it will list all the >> templates it loads, and log errors about your template ... > [snip] >>> SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card >>> (MB:v3.8.6 PF:v5.1.3 PN:apc_hw05_aos_513.bin AF1:v5.1.3 >>> AN1:apc_hw05_sumx_513.bin MN:AP9630 HR:05 SN: ZA1031030798 >>> MD:07/31/2010) (Embedded PowerNet SNMP Agent SW v2.2 compatible) > > Actually, following the pattern of the other APC templates, this > should be stored as "apc-9630", with a sysdesc of "MN:AP9630". As one > can see at http://en.wikipedia.org/wiki/APC_Smart-UPS#SmartSlot_card_models > there are a variety of cards that can fit in the Smart Slot that can > provide different capabilities (e.g. external temperature) regardless > of the model of UPS they fit into (bread loaf or rack mount). > > Speaking personally, some of our SU1400s have a 9617 and some a 9619, > and some of our 3000RM XLs have a 9617 and some a 9619, but each with > a 9619 has an "snmpwalk enterprises | wc -l" linecount of 717, and > with a 9617, 568 or 570. > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > Devmon-support mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devmon-support > -- RHCE#805007969328369 |
From: Richard F. <gol...@gm...> - 2011-05-28 10:42:09
|
On Tue, May 17, 2011 at 00:05, Buchan Milne <bg...@st...> wrote: > On Tuesday, 17 May 2011 08:16:22 Colin Coe wrote: [snip] >> >> I can get data up for the Smart UPS but it is not being automatically >> >> detected. I have the following as the spec file >> >> cat /usr/share/devmon/templates/apc-sups-1000rm/specs >> >> vendor : apc >> >> model : Smart-UPS 1000 RM >> >> snmpver : 1 >> >> sysdesc : Smart-UPS 1000 RM > > Note that the template name ('apc-sups-1000rm') must be composed of <vendor>- > <model>. So, your model should be 'sups-1000rm', otherwise your template won't > be recognised. Please run devmon with some verbosity, it will list all the > templates it loads, and log errors about your template ... [snip] >> SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card >> (MB:v3.8.6 PF:v5.1.3 PN:apc_hw05_aos_513.bin AF1:v5.1.3 >> AN1:apc_hw05_sumx_513.bin MN:AP9630 HR:05 SN: ZA1031030798 >> MD:07/31/2010) (Embedded PowerNet SNMP Agent SW v2.2 compatible) Actually, following the pattern of the other APC templates, this should be stored as "apc-9630", with a sysdesc of "MN:AP9630". As one can see at http://en.wikipedia.org/wiki/APC_Smart-UPS#SmartSlot_card_models there are a variety of cards that can fit in the Smart Slot that can provide different capabilities (e.g. external temperature) regardless of the model of UPS they fit into (bread loaf or rack mount). Speaking personally, some of our SU1400s have a 9617 and some a 9619, and some of our 3000RM XLs have a 9617 and some a 9619, but each with a 9619 has an "snmpwalk enterprises | wc -l" linecount of 717, and with a 9617, 568 or 570. |
From: Buchan M. <bg...@st...> - 2011-05-20 10:53:49
|
On Monday, 16 May 2011 21:17:42 Mark Jones wrote: > Let me respond for Steve here as he is doing this for me. > > As you know devmon builds the table of interfaces with the values etc. it > also sends the ncv data to Xymon so Xymon can build the rrd files etc. > > When the page is viewed in the browser it is created on the fly by the > servicestatus cgi. So as you said it takes what devmon has sent it and > wraps it in headers and footers etc. it also adds the graphs to the bottom > of the page based on the rrd files it finds. > > What we are trying to do is add another column to the table to have a link > to the page that clicking on the graph gives. The problem being is that > there is no way to identify the graphs as Xymon uses an id starting at 1 or > 0 for the first graph based on some kind of ordering of the rrd files. You can use a URL that uses the interface name (with some minor changes). For example, a URL taken from the weathermap example I gave (the graph popups are empty for you, but on the live versions you would see an 'overlib' interface graph) in my previous reply uses: http://seaknight.area51.telkomsa.net/hobbit- cgi/hobbitgraph.sh?host=phi&service=if_load:Gi5_2.&graph_height=120&graph_width=576&color=green&action=menu for interface Gi5/2 (the . is added to ensure it doesn't match Gi5/20 etc.). So, you would need a regex transform to get the interface name right, and some means to pull out the host and service names (dynamically), and then decide how to construct the rest of the URL (e.g. using some of the Xymon environment variables). So, some of this might be messy to have in the template, but devmon has most of them available. Since this is generally useful, the real question becomes, how do we want to present the graph. In many cases, going back and forward in the browser is not convenient. Would the overlib method (as used in the weathermap) be better. For example, displaying the graph in a "popup" when mousing over the interface name? > So Steve has tried to duplicate this ordering of the ifnames so that he can > match to the graph id. But the method of sort is not as one would expect > so we have issues where things don't match up. I don't think relying on the sorting matching is reliable. Regards, Buchan |
From: KING, K. (ATTSI) <KK...@at...> - 2011-05-18 20:15:02
|
I have added 1 test to the Cisco template for OSPF. I am getting this in the log: [11-05-18@15:10:24] ERROR: Error walking 1.3.6.1.2.1.14.10.1.10 for ScbhIlIfSs7R01A () [11-05-18@15:10:24] ERROR: Error walking 1.3.6.1.2.1.14.10.1.1 for ScbhIlIfSs7R01A () [11-05-18@15:10:24] ERROR: Failed too many queries on ScbhIlIfSs7R01A, aborting query [11-05-18@15:10:24] ERROR: Error walking 1.3.6.1.2.1.14.10.1.6 for ScbhIlIfSs7R01A () [11-05-18@15:10:25] ERROR: Error walking 1.3.6.1.2.1.14.10.1.10 for AllnTxDwSS7R01A () [11-05-18@15:10:25] ERROR: Failed too many queries on AllnTxDwSS7R01A, aborting query [11-05-18@15:10:25] ERROR: Error walking 1.3.6.1.2.1.14.10.1.6 for AllnTxDwSS7R01A () [11-05-18@15:10:25] ERROR: Error walking 1.3.6.1.2.1.14.10.1.1 for AllnTxDwSS7R01A () These are the OIDs I added. ospfAreaBdrRtrStatus : .1.3.6.1.2.1.14.1.4.0 : leaf ospfASBdrRtrStatus : .1.3.6.1.2.1.14.1.5.0 : leaf ospfAreaId : .1.3.6.1.2.1.14.2.1.1 : branch ospfAreaBdrRtrCount : .1.3.6.1.2.1.14.2.1.5 : branch ospfASBdrRtrCount : .1.3.6.1.2.1.14.2.1.6 : branch ospfAreaLSACount : .1.3.6.1.2.1.14.2.1.7 : branch ospfAreaStatus : .1.3.6.1.2.1.14.2.1.10: branch ospfNbrIpAddr : .1.3.6.1.2.1.14.10.1.1: branch ospfNbrRtrId : .1.3.6.1.2.1.14.10.1.3: branch ospfNbrState : .1.3.6.1.2.1.14.10.1.6: branch ospfNbrEvents : .1.3.6.1.2.1.14.10.1.7: branch ospfNbrLsRetransQLen : .1.3.6.1.2.1.14.10.1.8: branch ospfNbmaNbrPermanence : .1.3.6.1.2.1.14.10.1.10: branch ospfNbrHelloSuppressed : .1.3.6.1.2.1.14.10.1.11: branch What is the limit for the number of queries in Devmon? Kevin H. King Engineer V Implementations "You can not please everyone everyday, But everyday please everyone you can" -me |
From: W.J.M. N. <Wim...@nl...> - 2011-05-17 07:23:54
|
Hi Colin, >>> I'm attempting to monitor a few UPS. The UPS models I need to monitor include: >>> - APC Smart-UPS 1000 RM >>> - Powerware 9390 >>> - Powerware 9130 >>> - Powerware 9135 >>> - Powerware 9125 >>> - PowerShield PSCE10000 >>> >>> I can get data up for the Smart UPS but it is not being automatically >>> detected. I have the following as the spec file >>> cat /usr/share/devmon/templates/apc-sups-1000rm/specs >>> vendor : apc >>> model : Smart-UPS 1000 RM >>> snmpver : 1 >>> sysdesc : Smart-UPS 1000 RM >>> >>> I get this from >>> snmpwalk -v1 -c public ups 1.3.6.1.4.1.318.1.1.1.1.1.1.0 >>> PowerNet-MIB::upsBasicIdentModel.0 = STRING: "Smart-UPS 1000 RM" >>> >>> >> What does `snmpget -v1 -c public ups sysDescr.0` returns? The result of >> this snmpget is used by Devmon to select the template to use: it >> searches the templates for a matching 'sysdesc' in file 'specs'. >> >> > > SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card > (MB:v3.8.6 PF:v5.1.3 PN:apc_hw05_aos_513.bin AF1:v5.1.3 > AN1:apc_hw05_sumx_513.bin MN:AP9630 HR:05 SN: ZA1031030798 > MD:07/31/2010) (Embedded PowerNet SNMP Agent SW v2.2 compatible) > > It had only just clicked that the sysdesc == sysDescr.0 from snmpwalk. > > >> Alternatively, you could specify the model in the Xymon hosts.cfg >> (Hobbit: bb-hosts) the model, thus bypassing the automatic model detection. >> >> > The APC template for the Smart-UPS 1000 RM works OK. > > What I now see is the Powerware 9390 and 9130 getting matched against > ups/standard because of the string 'UPS' in sydDesc.0. These nodes > report: > SNMPv2-MIB::sysDescr.0 = STRING: ConnectUPS Web/SNMP Card V4.30 > This is a rather general, non-descriptive sysDescr. We've seen that too with some UPS devices, which contain a network interface manufactured by another party, and thus containing a standard sysDescr. In those cases we specify the model in the DEVMON directive in hosts.cfg file. Regards, Wim Nelis. ******************************************************************************************************* The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages. ******************************************************************************************************* |
From: Buchan M. <bg...@st...> - 2011-05-17 07:06:51
|
On Tuesday, 17 May 2011 08:16:22 Colin Coe wrote: > Hi Wim > > On Tue, May 17, 2011 at 2:02 PM, W.J.M. Nelis <Wim...@nl...> wrote: > > Hello Colin, > > > >> Hi all > >> > >> I'm attempting to monitor a few UPS. The UPS models I need to monitor > >> include: - APC Smart-UPS 1000 RM > >> - Powerware 9390 > >> - Powerware 9130 > >> - Powerware 9135 > >> - Powerware 9125 > >> - PowerShield PSCE10000 > >> > >> I can get data up for the Smart UPS but it is not being automatically > >> detected. I have the following as the spec file > >> cat /usr/share/devmon/templates/apc-sups-1000rm/specs > >> vendor : apc > >> model : Smart-UPS 1000 RM > >> snmpver : 1 > >> sysdesc : Smart-UPS 1000 RM Note that the template name ('apc-sups-1000rm') must be composed of <vendor>- <model>. So, your model should be 'sups-1000rm', otherwise your template won't be recognised. Please run devmon with some verbosity, it will list all the templates it loads, and log errors about your template ... > >> > >> I get this from > >> snmpwalk -v1 -c public ups 1.3.6.1.4.1.318.1.1.1.1.1.1.0 > >> PowerNet-MIB::upsBasicIdentModel.0 = STRING: "Smart-UPS 1000 RM" > > > > What does `snmpget -v1 -c public ups sysDescr.0` returns? The result of > > this snmpget is used by Devmon to select the template to use: it > > searches the templates for a matching 'sysdesc' in file 'specs'. > > SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card > (MB:v3.8.6 PF:v5.1.3 PN:apc_hw05_aos_513.bin AF1:v5.1.3 > AN1:apc_hw05_sumx_513.bin MN:AP9630 HR:05 SN: ZA1031030798 > MD:07/31/2010) (Embedded PowerNet SNMP Agent SW v2.2 compatible) > > It had only just clicked that the sysdesc == sysDescr.0 from snmpwalk. > > > Alternatively, you could specify the model in the Xymon hosts.cfg > > (Hobbit: bb-hosts) the model, thus bypassing the automatic model > > detection. > > > > Regards, > > Wim Nelis. > > The APC template for the Smart-UPS 1000 RM works OK. > > What I now see is the Powerware 9390 and 9130 getting matched against > ups/standard because of the string 'UPS' in sydDesc.0. These nodes > report: > SNMPv2-MIB::sysDescr.0 = STRING: ConnectUPS Web/SNMP Card V4.30 > > I see that there is a pware-xups template with a sysdesc of > 'ConnectUPS'. How do I make Xymon use pware-xups instead of > ups/standard? Using the model(vendor;model) option, as described in the USING file. Regards, Buchan |
From: Colin C. <col...@gm...> - 2011-05-17 06:16:28
|
Hi Wim On Tue, May 17, 2011 at 2:02 PM, W.J.M. Nelis <Wim...@nl...> wrote: > Hello Colin, > >> Hi all >> >> I'm attempting to monitor a few UPS. The UPS models I need to monitor include: >> - APC Smart-UPS 1000 RM >> - Powerware 9390 >> - Powerware 9130 >> - Powerware 9135 >> - Powerware 9125 >> - PowerShield PSCE10000 >> >> I can get data up for the Smart UPS but it is not being automatically >> detected. I have the following as the spec file >> cat /usr/share/devmon/templates/apc-sups-1000rm/specs >> vendor : apc >> model : Smart-UPS 1000 RM >> snmpver : 1 >> sysdesc : Smart-UPS 1000 RM >> >> I get this from >> snmpwalk -v1 -c public ups 1.3.6.1.4.1.318.1.1.1.1.1.1.0 >> PowerNet-MIB::upsBasicIdentModel.0 = STRING: "Smart-UPS 1000 RM" >> > What does `snmpget -v1 -c public ups sysDescr.0` returns? The result of > this snmpget is used by Devmon to select the template to use: it > searches the templates for a matching 'sysdesc' in file 'specs'. > SNMPv2-MIB::sysDescr.0 = STRING: APC Web/SNMP Management Card (MB:v3.8.6 PF:v5.1.3 PN:apc_hw05_aos_513.bin AF1:v5.1.3 AN1:apc_hw05_sumx_513.bin MN:AP9630 HR:05 SN: ZA1031030798 MD:07/31/2010) (Embedded PowerNet SNMP Agent SW v2.2 compatible) It had only just clicked that the sysdesc == sysDescr.0 from snmpwalk. > Alternatively, you could specify the model in the Xymon hosts.cfg > (Hobbit: bb-hosts) the model, thus bypassing the automatic model detection. > > Regards, > Wim Nelis. > The APC template for the Smart-UPS 1000 RM works OK. What I now see is the Powerware 9390 and 9130 getting matched against ups/standard because of the string 'UPS' in sydDesc.0. These nodes report: SNMPv2-MIB::sysDescr.0 = STRING: ConnectUPS Web/SNMP Card V4.30 I see that there is a pware-xups template with a sysdesc of 'ConnectUPS'. How do I make Xymon use pware-xups instead of ups/standard? Thanks CC -- RHCE#805007969328369 |
From: W.J.M. N. <Wim...@nl...> - 2011-05-17 06:02:21
|
Hello Colin, > Hi all > > I'm attempting to monitor a few UPS. The UPS models I need to monitor include: > - APC Smart-UPS 1000 RM > - Powerware 9390 > - Powerware 9130 > - Powerware 9135 > - Powerware 9125 > - PowerShield PSCE10000 > > I can get data up for the Smart UPS but it is not being automatically > detected. I have the following as the spec file > cat /usr/share/devmon/templates/apc-sups-1000rm/specs > vendor : apc > model : Smart-UPS 1000 RM > snmpver : 1 > sysdesc : Smart-UPS 1000 RM > > I get this from > snmpwalk -v1 -c public ups 1.3.6.1.4.1.318.1.1.1.1.1.1.0 > PowerNet-MIB::upsBasicIdentModel.0 = STRING: "Smart-UPS 1000 RM" > What does `snmpget -v1 -c public ups sysDescr.0` returns? The result of this snmpget is used by Devmon to select the template to use: it searches the templates for a matching 'sysdesc' in file 'specs'. Alternatively, you could specify the model in the Xymon hosts.cfg (Hobbit: bb-hosts) the model, thus bypassing the automatic model detection. Regards, Wim Nelis. ******************************************************************************************************* The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages. ******************************************************************************************************* |
From: Colin C. <col...@gm...> - 2011-05-16 23:50:23
|
Hi all I'm attempting to monitor a few UPS. The UPS models I need to monitor include: - APC Smart-UPS 1000 RM - Powerware 9390 - Powerware 9130 - Powerware 9135 - Powerware 9125 - PowerShield PSCE10000 The Powerware 9390 and 9130 both look reasonable out of the box but report that they have no battery packs attached. I've checked both of these and can confirm that they have multiple battery packs. I'm guessing this is a result of being detected as "ups/standard" rather the correct Powerware model. I figure I'll have to proper templates for these models to get the battery info. The Smart-UPS 1000 and Powerware 9135 return "No matching templates for device" so I've started writing templates for these. If I manually edit /var/lib/devmon/hosts.db and edit the make model fields I can get data up for the Smart UPS but it is not being automatically detected. I have the following as the spec file cat /usr/share/devmon/templates/apc-sups-1000rm/specs vendor : apc model : Smart-UPS 1000 RM snmpver : 1 sysdesc : Smart-UPS 1000 RM I get this from snmpwalk -v1 -c public ups 1.3.6.1.4.1.318.1.1.1.1.1.1.0 PowerNet-MIB::upsBasicIdentModel.0 = STRING: "Smart-UPS 1000 RM" Could someone point me in the right direction? Thanks CC -- RHCE#805007969328369 |
From: Mark J. <mj...@mn...> - 2011-05-16 19:15:36
|
Let me respond for Steve here as he is doing this for me. As you know devmon builds the table of interfaces with the values etc. it also sends the ncv data to Xymon so Xymon can build the rrd files etc. When the page is viewed in the browser it is created on the fly by the servicestatus cgi. So as you said it takes what devmon has sent it and wraps it in headers and footers etc. it also adds the graphs to the bottom of the page based on the rrd files it finds. What we are trying to do is add another column to the table to have a link to the page that clicking on the graph gives. The problem being is that there is no way to identify the graphs as Xymon uses an id starting at 1 or 0 for the first graph based on some kind of ordering of the rrd files. So Steve has tried to duplicate this ordering of the ifnames so that he can match to the graph id. But the method of sort is not as one would expect so we have issues where things don't match up. Hope this makes sense. Mark Jones Operations Managed Network Systems London Desk 519-679-5207 Windsor Desk 519-258-2333 x8417 Cell 519-521-8222 -----Original Message----- From: Buchan Milne [mailto:bg...@st...] Sent: Friday, May 13, 2011 7:50 AM To: dev...@li...; sst...@mn... Subject: Re: [Devmon] xymonrrd.c changes... (i think) On Wednesday, 11 May 2011 15:27:27 Steve Staples wrote: > Hi, I originally sent this to the XYMON list, but a reply was suggested > i send it here... so here is what I wrote, and maybe hopefully someone > has a suggestion on how I can do this :) > Well, I had intended you reply to my reply, but on this list. As in my other reply, you shouldn't need to touch either of: 1)RRD collector code - the collector code in Xymon doesn't modify the contents of the 'test' that is stored by Xymon. 2)The page generation code. The Xymon page generation code more or less just wraps whatever was sent by the "client" (devmon) in headers and footers, plus adds in the graphs at the end of the page. Now, if you don't want the graphs at the bottom of the page at all, then you may need to touch some of the bbgen code. However, if you want the graphs to appear in the table, you should be able to do that by inserting some js in the table, by modifying the 'messages' file of the devmon template. If this is seen as something that devmon users would like for most devmon tests that have graphs, I could possibly add a new TABLE option for it. However, it would probably be best first to prototype it by changing a 'messages' file. However, the real question is, what are you trying to achieve. If you are trying to make it easier to present/see the utilisation of important network links, the weathermap (e.g. http://staff.telkomsa.net/~bgmilne/xymon/weathermap/nbsc.html) may be a better solution. That said, in some cases, you would just like to be able to associate the graph to the interface description, without scrolling up and down a lot. In that case, I have a short perl script (just commited to svn[1]) that uses an unreleased perl module for Xymon, to get the interface description out of the if_load test and put it in the graph[3]. You need to put the Xymon::Client (Client.pm file[2]) somewhere perl can find it (e.g. you can add PERL5LIB to hobbitserver.cfg, and in the directory it points to, create a Xymon directory, and drop the attached file there). I will find a place to host this project (either in Xymon itself, devmon, or a separate project) later, hopefully soon. 1. http://devmon.svn.sf.net/viewvc/devmon/trunk/extras/devmongraphtitle.pl 2. http://staff.telkomsa.net/~bgmilne/xymon/Client.pm 3. http://staff.telkomsa.net/~bgmilne/xymon/if_load_graph_with_int_descr.png Now, the question is whether the page load time on a device with > 200 interfaces, due to the graphs, warrants taking the code out of the bbgen pieces, and instead rely on JS generated by devmon, to show the graphs on demand. Regards, Buchan > -- ORIGINAL MESSAGE TO XY...@XY... -- > Hi! > > This is my first post here... I am just trying to make some small > changes to our xymon system, and I am having some weird issues... > > we are using the 4.3.0 branch, and the issues i am running into, are > with the devmon if_load pages. > > The thing that I am doing, is in this page there is the table at the > top, and a bunch of graphs on the bottom (i didn't set this up, and i am > assuming that this is the "default"). I am trying to create a link from > the table, that will open the corresponding graph url (as if i had > scrolled down to the graph and click on it). > > I had it sort of working with some creative javascripting, but after > looking into it, it wasn't 100%. > > the "table" is not sorted at all, but the "graphs" section is sorted > based on the rrd name. > > > is there anyway (i am sure that there is) to put the same value from the > transforms file {ifLoad} into the ./lib/xymonrrd.c file? does that > make sense? doesn't have to be that {ifLoad} perse, but something that > i can make match from teh table to the graphs... > > i was thinking in this area, to add the 'id=\"ifload_%s\"': > static const char *xymonlinkfmt = "<table summary=\"%s Graph > \"><tr><td><A HREF=\"%s&action=menu\" id=\"ifload_%s\"><IMG BORDER=0 > SRC=\"%s&graph=hourly&action=view\" ALT=\"xymongraph %s > \"></A></td><td>..... > > If you could point me in the right direction, I would be greatful :) > > Steve. ---------------------------------------------------------------------------- -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Devmon-support mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devmon-support |
From: Buchan M. <bg...@st...> - 2011-05-13 13:01:25
|
On Wednesday, 11 May 2011 15:27:27 Steve Staples wrote: > Hi, I originally sent this to the XYMON list, but a reply was suggested > i send it here... so here is what I wrote, and maybe hopefully someone > has a suggestion on how I can do this :) > Well, I had intended you reply to my reply, but on this list. As in my other reply, you shouldn't need to touch either of: 1)RRD collector code - the collector code in Xymon doesn't modify the contents of the 'test' that is stored by Xymon. 2)The page generation code. The Xymon page generation code more or less just wraps whatever was sent by the "client" (devmon) in headers and footers, plus adds in the graphs at the end of the page. Now, if you don't want the graphs at the bottom of the page at all, then you may need to touch some of the bbgen code. However, if you want the graphs to appear in the table, you should be able to do that by inserting some js in the table, by modifying the 'messages' file of the devmon template. If this is seen as something that devmon users would like for most devmon tests that have graphs, I could possibly add a new TABLE option for it. However, it would probably be best first to prototype it by changing a 'messages' file. However, the real question is, what are you trying to achieve. If you are trying to make it easier to present/see the utilisation of important network links, the weathermap (e.g. http://staff.telkomsa.net/~bgmilne/xymon/weathermap/nbsc.html) may be a better solution. That said, in some cases, you would just like to be able to associate the graph to the interface description, without scrolling up and down a lot. In that case, I have a short perl script (just commited to svn[1]) that uses an unreleased perl module for Xymon, to get the interface description out of the if_load test and put it in the graph[3]. You need to put the Xymon::Client (Client.pm file[2]) somewhere perl can find it (e.g. you can add PERL5LIB to hobbitserver.cfg, and in the directory it points to, create a Xymon directory, and drop the attached file there). I will find a place to host this project (either in Xymon itself, devmon, or a separate project) later, hopefully soon. 1. http://devmon.svn.sf.net/viewvc/devmon/trunk/extras/devmongraphtitle.pl 2. http://staff.telkomsa.net/~bgmilne/xymon/Client.pm 3. http://staff.telkomsa.net/~bgmilne/xymon/if_load_graph_with_int_descr.png Now, the question is whether the page load time on a device with > 200 interfaces, due to the graphs, warrants taking the code out of the bbgen pieces, and instead rely on JS generated by devmon, to show the graphs on demand. Regards, Buchan > -- ORIGINAL MESSAGE TO XY...@XY... -- > Hi! > > This is my first post here... I am just trying to make some small > changes to our xymon system, and I am having some weird issues... > > we are using the 4.3.0 branch, and the issues i am running into, are > with the devmon if_load pages. > > The thing that I am doing, is in this page there is the table at the > top, and a bunch of graphs on the bottom (i didn't set this up, and i am > assuming that this is the "default"). I am trying to create a link from > the table, that will open the corresponding graph url (as if i had > scrolled down to the graph and click on it). > > I had it sort of working with some creative javascripting, but after > looking into it, it wasn't 100%. > > the "table" is not sorted at all, but the "graphs" section is sorted > based on the rrd name. > > > is there anyway (i am sure that there is) to put the same value from the > transforms file {ifLoad} into the ./lib/xymonrrd.c file? does that > make sense? doesn't have to be that {ifLoad} perse, but something that > i can make match from teh table to the graphs... > > i was thinking in this area, to add the 'id=\"ifload_%s\"': > static const char *xymonlinkfmt = "<table summary=\"%s Graph > \"><tr><td><A HREF=\"%s&action=menu\" id=\"ifload_%s\"><IMG BORDER=0 > SRC=\"%s&graph=hourly&action=view\" ALT=\"xymongraph %s > \"></A></td><td>..... > > If you could point me in the right direction, I would be greatful :) > > Steve. |
From: Steve S. <sst...@mn...> - 2011-05-11 13:43:40
|
Hi, I originally sent this to the XYMON list, but a reply was suggested i send it here... so here is what I wrote, and maybe hopefully someone has a suggestion on how I can do this :) Thanks in advance! Steve. -- ORIGINAL MESSAGE TO XY...@XY... -- Hi! This is my first post here... I am just trying to make some small changes to our xymon system, and I am having some weird issues... we are using the 4.3.0 branch, and the issues i am running into, are with the devmon if_load pages. The thing that I am doing, is in this page there is the table at the top, and a bunch of graphs on the bottom (i didn't set this up, and i am assuming that this is the "default"). I am trying to create a link from the table, that will open the corresponding graph url (as if i had scrolled down to the graph and click on it). I had it sort of working with some creative javascripting, but after looking into it, it wasn't 100%. the "table" is not sorted at all, but the "graphs" section is sorted based on the rrd name. is there anyway (i am sure that there is) to put the same value from the transforms file {ifLoad} into the ./lib/xymonrrd.c file? does that make sense? doesn't have to be that {ifLoad} perse, but something that i can make match from teh table to the graphs... i was thinking in this area, to add the 'id=\"ifload_%s\"': static const char *xymonlinkfmt = "<table summary=\"%s Graph \"><tr><td><A HREF=\"%s&action=menu\" id=\"ifload_%s\"><IMG BORDER=0 SRC=\"%s&graph=hourly&action=view\" ALT=\"xymongraph %s \"></A></td><td>..... If you could point me in the right direction, I would be greatful :) Steve. -- END MESSAGE -- |
From: W.J.M. N. <Wim...@nl...> - 2011-05-10 13:19:07
|
Hello, > Is there a way to ignore an interface based on text in the alias? The > docs show: > > The exceptions file is contains rules which are only applied > against repeater type data aliases. > > An example of a exceptions file is as follows: > > -<start file>----------------------------- > > ifName : alarm : Gi.+ > ifName : ignore : Nu.+|Vl.+ > > -<end file>------------------------------- > > You can see that each entry is on its on line, with three > fields separated by colons. The first field is the primary > data alias that the exception should be applied against. The > second field is the exception type, and the third field is > the regular expression that the primary alias is matched > against. Exception regular expressions (unlike non-numeric > thresholds) ARE anchored, and thus need to match the primary > oid EXACTLY. > > > What I would like to do is have the interface ignored if the text of the > alias (description) has something like "NEW TURNUP","NOT LIVE" or > "DECOM" . > > The folks that do the port provisioning load the configs and the port > will be left in a down state. This keeps the Xymon display red for the > router. How are other folks handling this? Or is it as simple as an > exception using the "ifAlias" oid in the exceptions file? > We achieve something like that by using a script which generates amongst others the Devmon configuration. That script periodically checks the status of all network equipment and also the status of all networkports. The interfaces to be skipped are put into the Devmon configuration in the Xymon hosts.cfg configuration file: 0.0.0.0 SomeSwitch # DEVMON:except(all;ifName;i:Gi0/1|Gi0/2) Moreover, in the templates, the exceptions file we do not use the keyword 'ignore', only the keyword 'only'. In this way both selections will be applied. ( An 'except' in the Xymon hosts-file overrules an 'ignore' in the template.) Regards, Wim Nelis. ******************************************************************************************************* The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages. ******************************************************************************************************* |
From: KING, K. (ATTSI) <KK...@at...> - 2011-05-10 12:54:42
|
Is there a way to ignore an interface based on text in the alias? The docs show: The exceptions file is contains rules which are only applied against repeater type data aliases. An example of a exceptions file is as follows: -<start file>----------------------------- ifName : alarm : Gi.+ ifName : ignore : Nu.+|Vl.+ -<end file>------------------------------- You can see that each entry is on its on line, with three fields separated by colons. The first field is the primary data alias that the exception should be applied against. The second field is the exception type, and the third field is the regular expression that the primary alias is matched against. Exception regular expressions (unlike non-numeric thresholds) ARE anchored, and thus need to match the primary oid EXACTLY. What I would like to do is have the interface ignored if the text of the alias (description) has something like "NEW TURNUP","NOT LIVE" or "DECOM" . The folks that do the port provisioning load the configs and the port will be left in a down state. This keeps the Xymon display red for the router. How are other folks handling this? Or is it as simple as an exception using the "ifAlias" oid in the exceptions file? Kevin H. King Engineer V Implementations AT&T 404-444-0410 "You can not please everyone everyday, But everyday please everyone you can" -me |
From: Johan S. <Joh...@de...> - 2011-05-09 12:27:11
|
Hi. I have been trying to take a new grip on this problem. I can't understand why it is not working. According to Buchan, 64-bit counters should not be a problem, but Devmon fails get get any data from the 64-bit OIDs on our Netapp filer. I did a debug run against this device only, I have attached the log file. I have also attached the oids file for the "volumes" test, which is the one with problems. I want to be able to replace the dfTotalKBytes and dfUsedBytes OIDs with their 64-bit counterpaths, but for now I have just added the 64-bit OIDs as separate variables printing them in separate column. When I poll these OID:s manually from the shell, it works fine. mon01 # snmpwalk -v 2c -c public filer02 .1.3.6.1.4.1.789.1.5.4.1.29 iso.3.6.1.4.1.789.1.5.4.1.29.1 = Counter64: 7810884864 iso.3.6.1.4.1.789.1.5.4.1.29.2 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.3 = Counter64: 16777216 iso.3.6.1.4.1.789.1.5.4.1.29.4 = Counter64: 4194304 iso.3.6.1.4.1.789.1.5.4.1.29.5 = Counter64: 524288000 iso.3.6.1.4.1.789.1.5.4.1.29.6 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.7 = Counter64: 1048576000 iso.3.6.1.4.1.789.1.5.4.1.29.8 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.9 = Counter64: 104857600 iso.3.6.1.4.1.789.1.5.4.1.29.10 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.11 = Counter64: 52428800 iso.3.6.1.4.1.789.1.5.4.1.29.12 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.13 = Counter64: 524288000 iso.3.6.1.4.1.789.1.5.4.1.29.14 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.15 = Counter64: 4237309008 iso.3.6.1.4.1.789.1.5.4.1.29.16 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.17 = Counter64: 524288000 iso.3.6.1.4.1.789.1.5.4.1.29.18 = Counter64: 0 iso.3.6.1.4.1.789.1.5.4.1.29.19 = Counter64: 524288000 iso.3.6.1.4.1.789.1.5.4.1.29.20 = Counter64: 0 Does anyone have any clue why this isn't working in devmon? Could there be some problem with perl and SNMP? Can I create a simple perl script and try to poll the OIDs using the perl modules that devmon uses? /Johan > -----Original Message----- > From: Buchan Milne [mailto:bg...@st...] > Sent: den 11 mars 2011 12:00 > To: Johan Sjöberg > Subject: Re: [Devmon] 64-bit counters > > > ----- "Johan Sjöberg" <joh...@de...> wrote: > > > Hi. > > > > Thanks for your reply. I couldn't see any reasons it shouldn't support > > 64-bit counters, but I wanted to check just to make sure. I will start > > digging through the debug logs and try to find the cause of this. Is > > it possible to poll just one device with debug, so that I don't get > > all unnecessary logging for unaffected devices? Maybe I can create a > > special hosts file and run devmon in the foreground or something? > > The OIDs look correct. Here is the output of the index OID, 32-bit > > volume size and 64-bit volume size, and nothing is missing. > > > > mon01:/var/log# snmpwalk -v 2c -c public filer01 > > .1.3.6.1.4.1.789.1.5.4.1.1 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.1 = INTEGER: 1 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.2 = INTEGER: 2 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.3 = INTEGER: 3 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.4 = INTEGER: 4 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.5 = INTEGER: 5 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.6 = INTEGER: 6 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.7 = INTEGER: 7 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.8 = INTEGER: 8 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.9 = INTEGER: 9 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.10 = INTEGER: 10 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.11 = INTEGER: 11 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.12 = INTEGER: 12 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.13 = INTEGER: 13 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.14 = INTEGER: 14 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.15 = INTEGER: 15 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.16 = INTEGER: 16 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.17 = INTEGER: 17 > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.18 = INTEGER: 18 mon01:/var/log# > > snmpwalk -v 2c -c public filer01 > > .1.3.6.1.4.1.789.1.5.4.1.3 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.1 = INTEGER: -2039060528 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.2 = INTEGER: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.3 = INTEGER: 16777216 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.4 = INTEGER: 4194304 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.5 = INTEGER: 524288000 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.6 = INTEGER: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.7 = INTEGER: 524288000 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.8 = INTEGER: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.9 = INTEGER: 524288000 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.10 = INTEGER: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.11 = INTEGER: 408944640 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.12 = INTEGER: 136314880 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.13 = INTEGER: 41943040 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.14 = INTEGER: 10485760 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.15 = INTEGER: 25165824 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.16 = INTEGER: 6291456 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.17 = INTEGER: 367001600 > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.18 = INTEGER: 0 mon01:/var/log# > > snmpwalk -v 2c -c public filer01 > > .1.3.6.1.4.1.789.1.5.4.1.29 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.1 = Counter64: 2255906768 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.2 = Counter64: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.3 = Counter64: 16777216 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.4 = Counter64: 4194304 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.5 = Counter64: 524288000 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.6 = Counter64: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.7 = Counter64: 524288000 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.8 = Counter64: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.9 = Counter64: 524288000 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.10 = Counter64: 0 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.11 = Counter64: 408944640 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.12 = Counter64: 136314880 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.13 = Counter64: 41943040 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.14 = Counter64: 10485760 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.15 = Counter64: 25165824 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.16 = Counter64: 6291456 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.17 = Counter64: 367001600 > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.18 = Counter64: 0 > > Provide the oids files for all the tests for the template you are using .. > > Regards, > Buchan |
From: Johan S. <Joh...@de...> - 2011-05-09 12:26:40
|
Forgot to attach the files, as usual. /Johan > -----Original Message----- > From: Johan Sjöberg > Sent: den 9 maj 2011 14:14 > To: 'Buchan Milne'; dev...@li... > Subject: RE: [Devmon] 64-bit counters > > Hi. > > I have been trying to take a new grip on this problem. I can't understand why > it is not working. According to Buchan, 64-bit counters should not be a > problem, but Devmon fails get get any data from the 64-bit OIDs on our > Netapp filer. > I did a debug run against this device only, I have attached the log file. I have > also attached the oids file for the "volumes" test, which is the one with > problems. I want to be able to replace the dfTotalKBytes and dfUsedBytes > OIDs with their 64-bit counterpaths, but for now I have just added the 64-bit > OIDs as separate variables printing them in separate column. > > When I poll these OID:s manually from the shell, it works fine. > > mon01 # snmpwalk -v 2c -c public filer02 .1.3.6.1.4.1.789.1.5.4.1.29 > iso.3.6.1.4.1.789.1.5.4.1.29.1 = Counter64: 7810884864 > iso.3.6.1.4.1.789.1.5.4.1.29.2 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.3 = Counter64: 16777216 > iso.3.6.1.4.1.789.1.5.4.1.29.4 = Counter64: 4194304 > iso.3.6.1.4.1.789.1.5.4.1.29.5 = Counter64: 524288000 > iso.3.6.1.4.1.789.1.5.4.1.29.6 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.7 = Counter64: 1048576000 > iso.3.6.1.4.1.789.1.5.4.1.29.8 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.9 = Counter64: 104857600 > iso.3.6.1.4.1.789.1.5.4.1.29.10 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.11 = Counter64: 52428800 > iso.3.6.1.4.1.789.1.5.4.1.29.12 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.13 = Counter64: 524288000 > iso.3.6.1.4.1.789.1.5.4.1.29.14 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.15 = Counter64: 4237309008 > iso.3.6.1.4.1.789.1.5.4.1.29.16 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.17 = Counter64: 524288000 > iso.3.6.1.4.1.789.1.5.4.1.29.18 = Counter64: 0 > iso.3.6.1.4.1.789.1.5.4.1.29.19 = Counter64: 524288000 > iso.3.6.1.4.1.789.1.5.4.1.29.20 = Counter64: 0 > > Does anyone have any clue why this isn't working in devmon? Could there be > some problem with perl and SNMP? Can I create a simple perl script and try > to poll the OIDs using the perl modules that devmon uses? > > /Johan > > > -----Original Message----- > > From: Buchan Milne [mailto:bg...@st...] > > Sent: den 11 mars 2011 12:00 > > To: Johan Sjöberg > > Subject: Re: [Devmon] 64-bit counters > > > > > > ----- "Johan Sjöberg" <joh...@de...> wrote: > > > > > Hi. > > > > > > Thanks for your reply. I couldn't see any reasons it shouldn't > > > support 64-bit counters, but I wanted to check just to make sure. I > > > will start digging through the debug logs and try to find the cause > > > of this. Is it possible to poll just one device with debug, so that > > > I don't get all unnecessary logging for unaffected devices? Maybe I > > > can create a special hosts file and run devmon in the foreground or > something? > > > The OIDs look correct. Here is the output of the index OID, 32-bit > > > volume size and 64-bit volume size, and nothing is missing. > > > > > > mon01:/var/log# snmpwalk -v 2c -c public filer01 > > > .1.3.6.1.4.1.789.1.5.4.1.1 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.1 = INTEGER: 1 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.2 = INTEGER: 2 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.3 = INTEGER: 3 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.4 = INTEGER: 4 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.5 = INTEGER: 5 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.6 = INTEGER: 6 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.7 = INTEGER: 7 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.8 = INTEGER: 8 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.9 = INTEGER: 9 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.10 = INTEGER: 10 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.11 = INTEGER: 11 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.12 = INTEGER: 12 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.13 = INTEGER: 13 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.14 = INTEGER: 14 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.15 = INTEGER: 15 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.16 = INTEGER: 16 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.17 = INTEGER: 17 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.1.18 = INTEGER: 18 > > > mon01:/var/log# snmpwalk -v 2c -c public filer01 > > > .1.3.6.1.4.1.789.1.5.4.1.3 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.1 = INTEGER: -2039060528 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.2 = INTEGER: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.3 = INTEGER: 16777216 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.4 = INTEGER: 4194304 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.5 = INTEGER: 524288000 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.6 = INTEGER: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.7 = INTEGER: 524288000 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.8 = INTEGER: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.9 = INTEGER: 524288000 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.10 = INTEGER: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.11 = INTEGER: 408944640 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.12 = INTEGER: 136314880 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.13 = INTEGER: 41943040 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.14 = INTEGER: 10485760 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.15 = INTEGER: 25165824 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.16 = INTEGER: 6291456 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.17 = INTEGER: 367001600 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.3.18 = INTEGER: 0 > > > mon01:/var/log# snmpwalk -v 2c -c public filer01 > > > .1.3.6.1.4.1.789.1.5.4.1.29 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.1 = Counter64: 2255906768 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.2 = Counter64: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.3 = Counter64: 16777216 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.4 = Counter64: 4194304 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.5 = Counter64: 524288000 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.6 = Counter64: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.7 = Counter64: 524288000 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.8 = Counter64: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.9 = Counter64: 524288000 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.10 = Counter64: 0 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.11 = Counter64: 408944640 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.12 = Counter64: 136314880 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.13 = Counter64: 41943040 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.14 = Counter64: 10485760 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.15 = Counter64: 25165824 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.16 = Counter64: 6291456 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.17 = Counter64: 367001600 > > > SNMPv2-SMI::enterprises.789.1.5.4.1.29.18 = Counter64: 0 > > > > Provide the oids files for all the tests for the template you are using .. > > > > Regards, > > Buchan |
From: Jeremy L. <jla...@re...> - 2011-05-06 03:30:12
|
Hi The file dm_config.pm has "umask 0" in there. The effect of this is that all log files and the pid file get created as world-writeable, which isn't very good IMHO. In my installation, I commented out that line. Please let me know if this was the wrong thing to do, and otherwise, I suggest this be put into the code. The perldoc page on umask seems to suggest NOT using umask, and instead using creation modes in sysopen, and leaving policy decisions (umask) to the user (which would be the start-up/init script in this case). Cheers Jeremy |