devmon-support — General Devmon support

Re: [Devmon] Template Request

[xbgmsharp <xbg...@gm...>]

Everything  is avalaible on the svn.

http://sourceforge.net/svn/?group_id=3D160720




Patrick Nixon <pn...@gm...> a =E9crit :

> I did try the 6500 as it was the one closest to the 4000 chassis in my
> mind, but it didn't see it.
>
> Kaya,  How would I get a copy of the templates you committed?  are
> they available on sf.net?
>
> Thanks for your help!
> --Pat
>
> On Jan 31, 2008 5:19 AM, xbgmsharp <xbg...@gm...> wrote:
>> Hello,
>>
>> I have commit today a lot of new template and some modification on other.
>> Add:
>>   * cisco-4500
>>   * cisco-msfc2
>>   * cisco-5500
>>   * cisco-6506
>>   * cisco-2811
>>   * cisco-3640
>>
>> Add memory and serial for:
>>   * cisco-2801
>>   * cisco-2960
>>   * cisco-2900
>>   * cisco-1700
>>   * cisco-2970
>>   * cisco-2950
>>   * cisco-3500
>>   * cisco-3550
>>   * cisco-3750
>>
>> Add serial for all cisco template.
>>
>> Regards,
>> KaYa
>>
>>
>> Buchan Milne <bg...@st...> a =E9crit :
>>
>>
>> > On Thursday 31 January 2008 05:19:28 Patrick Nixon wrote:
>> >> Hey all,
>> >>  Has anyone compiled a template for the Cisco 4000 series chassis?
>> >
>> > Have you tried any of the other cisco templates? If so, what did  =20
>> not work, or
>> > what additional OIDs need to be supported?
>> >
>> > I think we have a Cisco 4000 on order ... but it will take a  =20
>> month or two to
>> > get here.
>> >
>> > Regards,
>> > Buchan
>> >
>> > -----------------------------------------------------------------------=
--
>> > This SF.net email is sponsored by: Microsoft
>> > Defy all challenges. Microsoft(R) Visual Studio 2008.
>> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> > _______________________________________________
>> > Devmon-support mailing list
>> > Dev...@li...
>> > https://lists.sourceforge.net/lists/listinfo/devmon-support
>> >
>> >
>>
>> --
>> Thanks for using xbgm# / Devmon / BBwin.
>> http://xbgm.sourceforge.net/
>> http://devmon.sourceforge.net/
>> http://bbwin.sourceforge.net/
>> Please feedback.
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Devmon-support mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devmon-support
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
>

--=20
Thanks for using xbgm# / Devmon / BBwin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
http://bbwin.sourceforge.net/
Please feedback.

Re: [Devmon] Template Request

[Buchan M. <bg...@st...>]

On Thursday 31 January 2008 16:19:16 Patrick Nixon wrote:
> I did try the 6500 as it was the one closest to the 4000 chassis in my
> mind, but it didn't see it.
>
> Kaya,  How would I get a copy of the templates you committed?  are
> they available on sf.net?

You can use subversion to check them out, see 
http://sourceforge.net/svn/?group_id=160720 for more information.

Or, you can browse svn at 
http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/ and download files 
individually.

Regards,
Buchan

Re: [Devmon] Template Request

[Patrick N. <pn...@gm...>]

I did try the 6500 as it was the one closest to the 4000 chassis in my
mind, but it didn't see it.

Kaya,  How would I get a copy of the templates you committed?  are
they available on sf.net?

Thanks for your help!
--Pat

On Jan 31, 2008 5:19 AM, xbgmsharp <xbg...@gm...> wrote:
> Hello,
>
> I have commit today a lot of new template and some modification on other.
> Add:
>   * cisco-4500
>   * cisco-msfc2
>   * cisco-5500
>   * cisco-6506
>   * cisco-2811
>   * cisco-3640
>
> Add memory and serial for:
>   * cisco-2801
>   * cisco-2960
>   * cisco-2900
>   * cisco-1700
>   * cisco-2970
>   * cisco-2950
>   * cisco-3500
>   * cisco-3550
>   * cisco-3750
>
> Add serial for all cisco template.
>
> Regards,
> KaYa
>
>
> Buchan Milne <bg...@st...> a =E9crit :
>
>
> > On Thursday 31 January 2008 05:19:28 Patrick Nixon wrote:
> >> Hey all,
> >>  Has anyone compiled a template for the Cisco 4000 series chassis?
> >
> > Have you tried any of the other cisco templates? If so, what did not wo=
rk, or
> > what additional OIDs need to be supported?
> >
> > I think we have a Cisco 4000 on order ... but it will take a month or t=
wo to
> > get here.
> >
> > Regards,
> > Buchan
> >
> > -----------------------------------------------------------------------=
--
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Devmon-support mailing list
> > Dev...@li...
> > https://lists.sourceforge.net/lists/listinfo/devmon-support
> >
> >
>
> --
> Thanks for using xbgm# / Devmon / BBwin.
> http://xbgm.sourceforge.net/
> http://devmon.sourceforge.net/
> http://bbwin.sourceforge.net/
> Please feedback.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

[Devmon] Progressing towards release

[Buchan M. <bg...@st...>]

I managed to complete fixes for some of the last issues regarding generic 
graphing support for Devmon in hobbit (see 
http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/extras/hobbit-4.2.0-devmon.patch).

My current plan is to try and validate one of the changes to Hobbit in this 
patch, and then bump the version number to 0.3.0-rc1, and assuming there are 
no major issues anyone can report, tag and release it by tomorrow.

The last few things I can think of are maybe some documentation updates, and 
ChangeLog.

So ... if there is something that I have missed which you think need to be 
fixed by the rc ... I need to know now.

Regards,
Buchan

(P.S. Some of this urgency, and some of the work I've been doing is driven by 
timelines for implementing some of these features at work).

Re: [Devmon] Template Request

[xbgmsharp <xbg...@gm...>]

Hello,

I have commit today a lot of new template and some modification on other.
Add:
  * cisco-4500
  * cisco-msfc2
  * cisco-5500
  * cisco-6506
  * cisco-2811
  * cisco-3640

Add memory and serial for:
  * cisco-2801
  * cisco-2960
  * cisco-2900
  * cisco-1700
  * cisco-2970
  * cisco-2950
  * cisco-3500
  * cisco-3550
  * cisco-3750

Add serial for all cisco template.

Regards,
KaYa


Buchan Milne <bg...@st...> a =E9crit :

> On Thursday 31 January 2008 05:19:28 Patrick Nixon wrote:
>> Hey all,
>>  Has anyone compiled a template for the Cisco 4000 series chassis?
>
> Have you tried any of the other cisco templates? If so, what did not work,=
 or
> what additional OIDs need to be supported?
>
> I think we have a Cisco 4000 on order ... but it will take a month or two =
to
> get here.
>
> Regards,
> Buchan
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
>

--=20
Thanks for using xbgm# / Devmon / BBwin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
http://bbwin.sourceforge.net/
Please feedback.

Re: [Devmon] Template Request

[Buchan M. <bg...@st...>]

On Thursday 31 January 2008 05:19:28 Patrick Nixon wrote:
> Hey all,
>  Has anyone compiled a template for the Cisco 4000 series chassis?

Have you tried any of the other cisco templates? If so, what did not work, or 
what additional OIDs need to be supported?

I think we have a Cisco 4000 on order ... but it will take a month or two to 
get here.

Regards,
Buchan

Re: [Devmon] Template Help

[Buchan M. <bg...@st...>]

On Thursday 10 January 2008 23:12:01 Chuck Byam wrote:
> I'm working on a custom template, F5 specifically, and have a question for
> those  who have been through this before.  I'm attempting to generate an
> alert when the pool member node count drops to a certain point.
>
>
>
> Oid:
>
> PoolName : .1.3.6.1.4.1.3375.2.2.5.1.2.1.1 : branch
>
> PoolNodeCount : .1.3.6.1.4.1.3375.2.2.5.1.2.1.8 : branch
>
>
>
> Threshold:
>
> PoolNodeCount : yellow : <4 : {PoolName} Active Node Count {PoolNodeCount}
>
> PoolNodeCount : red : <2 : {PoolName} Active Node Count {PoolNodeCount}
>
>
>
> PoolNodeCount contains expected values as indicated in the message file,
> but alerts are never generated.  Running devmon in verbose mode doesn't
> yield any useful information.  What is the best way to troubleshoot this? 
> Any thoughts would be appreciated.

Did you use {PoolNodeCount.color} in your message file ? If you don't, no 
colors are applied ...

If you don't come right, please supply the message file. Unfortunately, it's 
not easy to add logging of matching of thresholds (the function is written in 
such a way that it returns when matching a threshold), but besides adding a 
{alias.color} tag, there's almost nothing to troubleshoot. When I did it 
myself, I wasted a lot of time before noticing that I needed to make this 
change:

http://devmon.svn.sourceforge.net/viewvc/devmon?view=rev&revision=40

Regards,
Buchan

[Devmon] Template Request

[Patrick N. <pn...@gm...>]

Hey all,
 Has anyone compiled a template for the Cisco 4000 series chassis?

Thanks!
--Pat

Re: [Devmon] extra-rrd.pl vs devmon RRD support

[Buchan M. <bg...@st...>]

On Thursday 10 January 2008 12:00:22 Buchan Milne wrote:
> The extra-rrd.pl in svn isn't using the RRD ds definitions that devmon
> sends (based on the template):
>
> <!--DEVMON RRD: if_load 0 0
> DS:ds0:COUNTER:600:0:U DS:ds1:COUNTER:600:0:U
> [....]
> -->
>
> So, according to most of the current templates for if_load, the ds names
> are "ds0" and "ds1", not "in" and "out". Also, the DS definitions are
> hardcoded in the current extra-rrd.pl, and the script needlessly limits
> itself to working on specific tests (while they are already limited by the
> hobbitd_channel command).
>
> I have attached the version I am currently using (which also works with the
> temp tests for compaq-server and dell-poweredge (which have:
> TABLE: noalarmsmsg,rrd(DS:ds0:cpqHeTemperatureCelsius:GAUGE;
> DS:ds1:cpqHeTemperatureThreshold:GAUGE)
> and
> TABLE: noalarmsmsg,rrd(DS:ds0:temperatureProbeReadingCelsius:GAUGE;
> DS:ds1:temperatureProbeLowerCriticalThresholdCelsius:GAUGE).
>
> So, I think it would be best to ship the final 0.3.0 with this being
> consistent (it wouldn't make sense to change it later). So, either we
> should change the templates, or people who have been using the current
> extra-rrd.pl should fix their data after upgrading, with something like:
>
>
> # for i in `find /var/lib/hobbit/rrd/ -name 'if_load.G*.rrd' `;do mv $i
> $i.old; rrdtool dump $i.old|sed -e 's/ in / ds0 /g;s/ out / ds1
> /g;'|rrdtool restore - $i;done
> # chown -R hobbit:hobbit /var/lib/hobbit/rrd/
>
>
> I am also looking at the possibility of shipping a patch for hobbit so that
> the extra-script is not necessary, and this would definitely have to use
> the RRD definitions devmon includes.


I added an initial stab at an rrd collector module for devmon in Hobbit, see 
http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/extras/do_devmon.c?view=log . 
I have one or two small things to clean up, but it currently works for me 
(with a one-line change required in do_rrd.c, and maybe an addition to 
TEST2RRD in hobbitserver.cfg).

I will look at whatever existing issues are still outstanding, and then look 
at releasing another tarball (rc1?).

Regards,
Buchan

Re: [Devmon] "devmon tests go purple" issue

[xbgmsharp <xbg...@gm...>]

...
> So, I have updated the text on the log page to indicate that the IML =20
>  should be
> cleared from the web interface. Note that if the IML log is empty and the =
log
> test is enabled on the server, most likely most of the other tests will be
> clear (in the case where I upped the limit for failed branches in the code=
,
> around line 560 in dm_snmp) or purple. I'm undoing the change on the "Fail=
ed
> too many queries" limit I had done. However, it would have been nicer if w=
e
> could just skip the test in question (rather than the whole device).
>
> Regards,
> Buchan
>

I think i could be a nice features to skip the test in question rather =20
than the whole device. In fact it has been done like this in order to =20
not block other devices. Because sometimes when a device is not weel =20
confiogured it will appear all clear instead of some test's color.
A limit of error for the device is usefull i think.
So maybe implement both a skip test error and a skip device error counter.


Regards,
Francois.


--=20
Thanks for using xbgm# / Devmon / BBwin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
http://bbwin.sourceforge.net/
Please feedback.

[Devmon] Anyone else using compaq-server test?

[Buchan M. <bg...@st...>]

I had problems with the compaq-server's raid test, in that it would give me 
errors about missing repeaters (may be due to the fact that most of our 
servers don't have hot spares in their arrays).

Eric reported that he didn't have problems, however, I required the attached 
patch to get it to work correctly.

If anyone else has the compaq-server raid test working correctly, I will 
consider adding a new device type (with some distinguishing detail, maybe my 
version of hpasm is too old, or too new) with just this change.

Regards,
Buchan

Index: templates/compaq-server/raid/thresholds
===================================================================
--- templates/compaq-server/raid/thresholds     (revision 30)
+++ templates/compaq-server/raid/thresholds     (working copy)
@@ -1,19 +1,7 @@
-cntrlCondTxt   : green         : OK
-cntrlCondTxt   : yellow        : Other|Degraded
-cntrlCondTxt   : red           : Failed
+logStatTxt     : green         : OK|Expanding|Queued for expansion : Normal
+logStatTxt     : yellow        : Unconfigured|Recovering|Read rebuild|
Rebuilding|Not available : Recovering
+logStatTxt     : red           : Failed|Wrong drive|Bad connect|Overheating|
Shutdown   : Logical drive has failed

-cntrlStatTxt   : green         : OK
-cntrlStatTxt   : yellow        : Other
-cntrlStatTxt   : red           : General failure|Cable problem|Powered off
-
-logStatTxt     : green         : OK|Expanding|Queued for expansion
-logStatTxt     : yellow        : Unconfigured|Recovering|Read rebuild|
Rebuilding|Not available
-logStatTxt     : red           : Failed|Wrong drive|Bad connect|Overheating|
Shutdown
-
-phyStatTxt     : green         : OK
-phyStatTxt     : yellow        : Other
-phyStatTxt     : red           : Failed|Predictive Failure
-
-sprStatTxt     : green         : Inactive
-sprStatTxt     : yellow        : Building|Active
-sprStatTxt     : red           : Failed
+phyStatTxt     : green         : OK    : Normal
+phyStatTxt     : yellow        : Other : Unknown failure
+phyStatTxt     : red           : Failed|Predictive Failure : Physical drive 
has failed
Index: templates/compaq-server/raid/message
===================================================================
--- templates/compaq-server/raid/message        (revision 30)
+++ templates/compaq-server/raid/message        (working copy)
@@ -1,9 +1,4 @@

-Controller status:
-TABLE: noalarmsmsg
-ID|Model|Firmware Rev|Condition|Status
-{cntrlIndex}|{cntrlModTxt}|{cntrlFwRev}|{cntrlCondTxt.color}{cntrlCondTxt}|
{cntrlStatTxt.color}{cntrlStatTxt}
-
 Logical drive status:
 TABLE: noalarmsmsg
 ID|Controller|Fault Tolerance|Size|OS name|Pysical IDs|Spare IDs|Status
@@ -11,10 +6,5 @@

 Physical drive status:
 TABLE: noalarmsmsg
-ID|Controller|Bay|Model|Firmware Rev|Speed|Size|Status
-{phyDrvIndex}|{phyDrvCntIndex}|{phyDrvBay}|{phyDrvModel}|{phyDrvFwRev}|
{phyDrvSpdTxt}|{phyDrvSize}mb|{phyStatTxt.color}{phyStatTxt}
-
-Spare drive status:
-TABLE: noalarmsmsg
-Physical Drive ID|Controller|Status
-{sprDrvIndex}|{sprDrvCntIndex}|{sprStatTxt.color}{sprStatTxt}
+ID|Controller|Bay|Model|Firmware Rev|Speed|Size|Serial|Status
+{phyDrvIndex}|{phyDrvCntIndex}|{phyDrvBay}|{phyDrvModel}|{phyDrvFwRev}|
{phyDrvSpdTxt}|{phyDrvSize}mb|{phyDrvSerial}|{phyStatTxt.color}{phyStatTxt}
Index: templates/compaq-server/raid/transforms
===================================================================
--- templates/compaq-server/raid/transforms     (revision 30)
+++ templates/compaq-server/raid/transforms     (working copy)
@@ -1,7 +1,3 @@
-cntrlModTxt    : SWITCH        : {cntrlModel} 1=Other,2=IDA,3=IDA 
Expansion,4=IDA-2,5=SMART,6=SMART-2/E,7=SMART-2/P,8=SMART-2SL,9=Smart 
3100ES,10=Smart 3200,11=SMART-2DH,12=Smart Array 221,13=Smart Array 
4250ES,14=Smart Array 4200,15=Integrated Smart Array,16=Smart Array 
431,17=Smart Array 5300,18=RAID LC2,19=Smart Array 5i,20=Smary Array 
532,21=Smart Array 5312,22=Smart Array 641,23=Smart Array 642,24=Smart Array 
6400,25=Smart Array 6400EM,26=Smart Array 6i,27=Generic Smart Array,29=Smart 
Array P600,30=Smart Array P400,31=Smart Array E200,32=Smart Array 
E200i,33=Smart Array P400i,34=Smart Array P800
-cntrlCondTxt   : SWITCH        : {cntrlCondition} 
1=Other,2=OK,3=Degraded,4=Failed
-cntrlStatTxt   : SWITCH        : {cntrlStatus} 1=Other,2=OK,3=General 
failure,4=Cable problem,5=Powered off
-
 logFaultTolTxt : SWITCH        : {logDrvFaultTol} 2=None,3=Mirroring,4=Data 
guard,5=Distributed data guard,6=Advanced data guard
 logStatTxt     : SWITCH        : {logDrvStatus} 
2=OK,3=Failed,4=Unconfigured,5=Recovering,6=Read rebuild,7=Rebuilding,8=Wrong 
drive,9=Bad connect,10=Overheating,11=Shutdown,12=Expanding,13=Not 
available,14=Queued for expansion
 logSprIdTxt    : UNPACK        : {logDrvSprIds} C* ","
@@ -9,5 +5,3 @@

 phyStatTxt     : SWITCH        : {phyDrvStatus} 
1=Other,2=OK,3=Failed,4=Predictive Failure
 phyDrvSpdTxt   : SWITCH        : {phyDrvSpeed} 1=Other,2=7200 rpm,3=10k 
rpm,4=15k rpm
-
-sprStatTxt     : SWITCH        : {sprDrvStatus} 
3=Failed,4=Inactive,5=Building,6=Active
Index: templates/compaq-server/raid/oids
===================================================================
--- templates/compaq-server/raid/oids   (revision 30)
+++ templates/compaq-server/raid/oids   (working copy)
@@ -1,9 +1,3 @@
-cntrlIndex     : 1.3.6.1.4.1.232.3.2.2.1.1.1   : branch
-cntrlModel     : 1.3.6.1.4.1.232.3.2.2.1.1.2   : branch
-cntrlFwRev     : 1.3.6.1.4.1.232.3.2.2.1.1.3   : branch
-cntrlCondition : 1.3.6.1.4.1.232.3.2.2.1.1.6   : branch
-cntrlStatus    : 1.3.6.1.4.1.232.3.2.2.1.1.12  : branch
-
 logDrvCntIndex : 1.3.6.1.4.1.232.3.2.3.1.1.1   : branch
 logDrvIndex    : 1.3.6.1.4.1.232.3.2.3.1.1.2   : branch
 logDrvFaultTol  : 1.3.6.1.4.1.232.3.2.3.1.1.3  : branch
@@ -21,8 +15,4 @@
 phyDrvStatus   : 1.3.6.1.4.1.232.3.2.5.1.1.6   : branch
 phyDrvSize     : 1.3.6.1.4.1.232.3.2.5.1.1.45  : branch
 phyDrvSpeed    : 1.3.6.1.4.1.232.3.2.5.1.1.59  : branch
-
-sprDrvCntIndex : 1.3.6.1.4.1.232.3.2.4.1.1.1   : branch
-sprDrvIndex    : 1.3.6.1.4.1.232.3.2.4.1.1.2   : branch
-sprDrvStatus   : 1.3.6.1.4.1.232.3.2.4.1.1.3   : branch
-
+phyDrvSerial   : 1.3.6.1.4.1.232.3.2.5.1.1.51  : branch
Index: templates/compaq-server/fans/thresholds
===================================================================
--- templates/compaq-server/fans/thresholds     (revision 30)
+++ templates/compaq-server/fans/thresholds     (working copy)
@@ -1,5 +1,4 @@
-cpqHeFltTolFanConditionTxt     : green         : OK                    : Fan 
OK
-cpqHeFltTolFanConditionTxt      : clear         : Other         : Fan state 
unkn
-own
+cpqHeFltTolFanConditionTxt     : green         : OK            : Fan OK
+cpqHeFltTolFanConditionTxt     : clear         : Other         : Fan state 
unknown
 cpqHeFltTolFanConditionTxt     : yellow        : Degraded      : Fan Degraded 
or other problem
-cpqHeFltTolFanConditionTxt     : red           : Failed                : Fan 
has failed
+cpqHeFltTolFanConditionTxt     : red           : Failed        : Fan has 
failed

Re: [Devmon] "devmon tests go purple" issue

[Buchan M. <bg...@st...>]

On Wednesday 19 December 2007 19:25:55 Buchan Milne wrote:
> On Wednesday 19 December 2007 17:19:34 xbgmsharp wrote:
> > Hi all,
> >
> > After a day of DEBUG. I works.
> > I modify the file dm_snmp.pm which do snmp pooling.
> > So now instead of pooling all leaf oid in one request, 1 oid equal 1
> > request. So now than i am pooling each oid separitly devmon should not go
> > purple. I try to make it per pakets like 5 or 10 but devmon get lost when
> > corresponding data with test done in dm_tests.pm
> >
> > I will let it working on some PIX and F5 devices and commit by the end of
> > the week.
> >
> > All of this, is for not getting SNMP Error: "error status: tooBig".
> > Because of this error all my leaf test was going clear.
> >
> > Comments?
>
> I have a number of servers using the compaq-server template, and on some,
> all the tests are always green. On the others, the are all clear, and I
> have error messages such as this:
>
> Missing repeater data for primary OID cpqHeFltTolFanIndex
>
> There is no apparent difference between the servers. One DL380 works, one
> does not. Two DL580s work, three don't.
>
> I'm wondering if there is a similar issue here. If I snmpwalk the whole
> Compaq OID, or each branch, I get the data I expect on the servers that
> aren't working.

I have resolved most of the issues here. In some cases it may have been that 
the Insight agent for the device type was not running (I have two servers 
that currently aren't showing any info on their raid controllers). In the 
other case, the IML log was empty, which results in a "No Such Object 
available on this agent at this OID" for the parent of all the branches in 
the log test.

When the IML log is emptied with the "hpasmcli -s 'clear iml'" command, the 
IML is empty, and this error occurs. When emptying the log from the iLO 
(integrated lights out) card's web interface, it puts one entry in the log, 
as follows:

Informational	Unknown	2008-1-14 13:14	2008-1-14 13:14	1	IML Cleared (iLO 
user:admin)

So, I have updated the text on the log page to indicate that the IML should be 
cleared from the web interface. Note that if the IML log is empty and the log 
test is enabled on the server, most likely most of the other tests will be 
clear (in the case where I upped the limit for failed branches in the code, 
around line 560 in dm_snmp) or purple. I'm undoing the change on the "Failed 
too many queries" limit I had done. However, it would have been nicer if we 
could just skip the test in question (rather than the whole device).

Regards,
Buchan

Re: [Devmon] =?iso-8859-1?q?Cisco_ATM_interfaces_and_ignoring_=22Unde?= =?iso-8859-1?q?fined=22_=09non-primary_aliases?=

[Buchan M. <bg...@st...>]

On Monday 14 January 2008 15:46:09 xbgmsharp wrote:
> I agree with the option 2.
> 2)Ignore rows from a repeater table where one of the repeaters is
> undefined:
>
> But you should write a message warning in the log file.

Done like this, see 
http://devmon.svn.sourceforge.net/viewvc/devmon?view=rev&revision=33

(commits are now on devmon-devel list, see 
http://sourceforge.net/mailarchive/forum.php?thread_name=E1JESgd-0001Ot-A9%40sc8-pr-svn3.sourceforge.net&forum_name=devmon-devel)

Regards,
Buchan

Re: [Devmon] Template Help

[Chuck B. <cb...@vi...>]

> > Oid:
> >
> > PoolName : .1.3.6.1.4.1.3375.2.2.5.1.2.1.1 : branch
> >
> > PoolNodeCount : .1.3.6.1.4.1.3375.2.2.5.1.2.1.8 : branch
> >
> >
> >
> > Threshold:
> >
> > PoolNodeCount : yellow : <4 : {PoolName} Active Node Count
> {PoolNodeCount}
> >
> > PoolNodeCount : red : <2 : {PoolName} Active Node Count
> {PoolNodeCount}
> >
> >
> >
> > PoolNodeCount contains expected values as indicated in the message
> file,
> > but alerts are never generated.  Running devmon in verbose mode
> doesn't
> > yield any useful information.  What is the best way to troubleshoot
> this?
> > Any thoughts would be appreciated.
>=20
> What version are you using ? 0.3.0-beta2 had a problem with numbeic
> thresholds, it is fixed in svn (I think this is the change that fixed
<< snip, snip >>
[Byam, Charles R]=20

Currently using beta4.  Snmpwalk returns a repeater type integer of =
expected values.

Regards,
--
Chuck Byam

Re: [Devmon] Cisco ATM interfaces and ignoring "Undefined" non-primary aliases

[xbgmsharp <xbg...@gm...>]

I agree with the option 2.
2)Ignore rows from a repeater table where one of the repeaters is undefined:

But you should write a message warning in the log file.

Regards,
Francois.

Buchan Milne <bg...@st...> a =E9crit :

> Our 7613s have ATM interfaces, but the ATM interfaces seem to generate a f=
ew
> entries in the if_* tables, e.g.:
>
>
> Ifc name  Ifc Speed  Rate in (load %)  Rate out (load %)
> AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   242.14 Kbps (2.36%)green
> 81.06 Kbps (0.79%)
>   AT2/0/0  0.00 bps &clear   Undefined (Undefined%) &clear   Undefined
> (Undefined%)
>   AT2/0/0 [---Link to XXX---]  10.24 Mbps &clear   Undefined  =20
> (Undefined%)clear
> Undefined (Undefined%)
>   AT2/0/0  0.00 bps &green   208.80 Kbps (0.00%)green   58.26 Kbps (0.00%)
>   AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   0.00 bps (0.00%)green
> 0.00 bps (0.00%)
> AT2/0/0.100  10.24 Mbps &clear   Undefined (Undefined%) &clear   Undefined
> (Undefined%)
>   AT2/0/0.100  10.24 Mbps &green   212.23 Kbps (2.07%) &green   58.26 Kbps
> (0.57%)
>
> Resulting in the page being clear (all other interfaces are green).
>
>
>
> The RRD lines looked like this:
>
> AT2_0_0 4213081072:2657713504
> AT2_0_0 U:U
> AT2_0_0 U:U
> AT2_0_0 1860389811:3500381518
> AT2_0_0 0:0
> AT2_0_0.100 U:U
> AT2_0_0.100 1860389811:3500381518
>
>
> The options in fixing this seem to be:
> 1)Extend the exceptions feature to address non-primary aliases  =20
> (since both the
> valid and invalid entries have the same primary alias), so we can except
> on "Undefined" or "0.00 bps" on a per-template-test basis
> 2)Ignore rows from a repeater table where one of the repeaters is undefine=
d:
>
> I've done (2) on the devmon instance in question:
>
> Index: modules/dm_tests.pm
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- modules/dm_tests.pm (revision 30)
> +++ modules/dm_tests.pm (working copy)
> @@ -1799,8 +1799,9 @@
>             # Get our oid vars
>              my $val   =3D $oid_h->{'val'}{$leaf};
>              my $color =3D $oid_h->{'color'}{$leaf};
> -            $val      =3D 'Undefined' if !defined $val;
> -            $color    =3D 'clear' if !defined $color;
> +           #$val      =3D 'Undefined' if !defined $val;
> +           #$color    =3D 'clear' if !defined $color;
> +           next T_LEAF if !defined $val;
>
>             # Check the exception types, if it is an 'ignore'
>             # dont include this leaf row if the data for this
>
>
> and now I get:
>
> AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   190.25 Kbps (1.86%) &gree=
n
> 52.06 Kbps (0.51%)
>   AT2/0/0  0.00 bps &green   8.13 Kbps (0.00%) &green   39.47 Kbps (0.00%)
>   AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   0.00 bps (0.00%) &green
> 0.00 bps (0.00%)
>
> The RRD lines still look the same:
>
> AT2_0_0 1766267040:3175078912
> AT2_0_0 U:U
> AT2_0_0 U:U
> AT2_0_0 3440140912:3883766474
> AT2_0_0 0:0
> AT2_0_0.100 U:U
> AT2_0_0.100 3440140912:3883766474
>
> So, I get a few graphs I don't need, however the page is green now.
>
> So, should rows with undefined non-primary aliases be ignored by default? =
Or,
> should it be possible to add them as exceptions per-template-test?
>
> Regards,
> Buchan
>

--=20
Thanks for using xbgm# / Devmon / BBwin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
http://bbwin.sourceforge.net/
Please feedback.

Re: [Devmon] Template Help

[xbgmsharp <xbg...@gm...>]

I would agree to release a new beta call 0.3.0-beta4 and see any bug =20
report in order to fix then.

Personally i have set the 0.3.0-beta4 in production.
It is polling all Firewalls (316) and Network (306) devices.

Note that the typical response to a bug report is a suggestion to try =20
the latest version first (svn). So please try doing that first, and =20
always include which versions you use of relevant software when =20
reporting bugs (minimum: devmon (devmon -V), devices type you are =20
trying to contact with the template.

Regards,
Francois

Buchan Milne <bg...@st...> a =E9crit :

> On Thursday 10 January 2008 23:12:01 Chuck Byam wrote:
>> I'm working on a custom template, F5 specifically, and have a question fo=
r
>> those  who have been through this before.  I'm attempting to generate an
>> alert when the pool member node count drops to a certain point.
>>
>>
>>
>> Oid:
>>
>> PoolName : .1.3.6.1.4.1.3375.2.2.5.1.2.1.1 : branch
>>
>> PoolNodeCount : .1.3.6.1.4.1.3375.2.2.5.1.2.1.8 : branch
>>
>>
>>
>> Threshold:
>>
>> PoolNodeCount : yellow : <4 : {PoolName} Active Node Count {PoolNodeCount=
}
>>
>> PoolNodeCount : red : <2 : {PoolName} Active Node Count {PoolNodeCount}
>>
>>
>>
>> PoolNodeCount contains expected values as indicated in the message file,
>> but alerts are never generated.  Running devmon in verbose mode doesn't
>> yield any useful information.  What is the best way to troubleshoot this?
>> Any thoughts would be appreciated.
>
> What version are you using ? 0.3.0-beta2 had a problem with numbeic
> thresholds, it is fixed in svn (I think this is the change that fixed it:
> http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/modules/dm_tests.pm?=
r1=3D3&r2=3D10)
>
> Could you test with current svn ? If not, I think we will try and release =
a
> new beta or rc this week.
>
> Regards,
> Buchan
>

--=20
Thanks for using xbgm# / Devmon / BBwin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
http://bbwin.sourceforge.net/
Please feedback.

Re: [Devmon] Ignored interfaces on cisco if_* tests

[xbgmsharp <xbg...@gm...>]

Hello all,

I was working on BBWin (http://bbwin.sourceforge.net/) central mode =20
for Hobbit 4.2 and the future 4.3.
Now that it is done i am back on devmon.

I agree with you, it is what i have been doing for cisco-asa template.

Regards,
Francois


Buchan Milne <bg...@st...> a =E9crit :

> On one of our 6509s, which has a few 100mb blades, I noticed I wasn't seei=
ng
> the Fa* devices in devmon output.
>
> I see that the exceptions file had this:
>
> ifName : alarm  : Gi.+
> ifName : ignore : Nu.+|Vl.+|VLAN.+
>
> This seems to effectively only alarm on Gi.+. Adding Fa.+ fixed the issue
> here.
>
> However, we have a 7613, which is detected by devmon as a 6509, and all th=
e
> tests work ... but the WAN interfaces (AT.+. Se.+) were ignored as well.
>
> More concerning is that the 7206 template has:
>
> ifName : alarm  : Gi.+
> ifName : ignore : Nu.+|Vl.+
>
> We can add regexes for all the valid interface names, but to me it would m=
ake
> more sense to do something like this (if it works):
>
> ifName : alarm : .+
> ifName : ignore : Nu.+|Vl.+|VLAN.+
>
> Regards,
> Buchan
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpla=
ce
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
>

--=20
Thanks for using xbgm# / Devmon / BBWin.
http://xbgm.sourceforge.net/
http://devmon.sourceforge.net/
Please feedback.

[Devmon] Cisco ATM interfaces and ignoring "Undefined" non-primary aliases

[Buchan M. <bg...@st...>]

Our 7613s have ATM interfaces, but the ATM interfaces seem to generate a few 
entries in the if_* tables, e.g.:


Ifc name  Ifc Speed  Rate in (load %)  Rate out (load %)
AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   242.14 Kbps (2.36%)green   
81.06 Kbps (0.79%)
  AT2/0/0  0.00 bps &clear   Undefined (Undefined%) &clear   Undefined 
(Undefined%)
  AT2/0/0 [---Link to XXX---]  10.24 Mbps &clear   Undefined (Undefined%)clear   
Undefined (Undefined%)
  AT2/0/0  0.00 bps &green   208.80 Kbps (0.00%)green   58.26 Kbps (0.00%)
  AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   0.00 bps (0.00%)green   
0.00 bps (0.00%)
AT2/0/0.100  10.24 Mbps &clear   Undefined (Undefined%) &clear   Undefined 
(Undefined%)
  AT2/0/0.100  10.24 Mbps &green   212.23 Kbps (2.07%) &green   58.26 Kbps 
(0.57%)

Resulting in the page being clear (all other interfaces are green).



The RRD lines looked like this:

AT2_0_0 4213081072:2657713504
AT2_0_0 U:U
AT2_0_0 U:U
AT2_0_0 1860389811:3500381518
AT2_0_0 0:0
AT2_0_0.100 U:U
AT2_0_0.100 1860389811:3500381518


The options in fixing this seem to be:
1)Extend the exceptions feature to address non-primary aliases (since both the 
valid and invalid entries have the same primary alias), so we can except 
on "Undefined" or "0.00 bps" on a per-template-test basis
2)Ignore rows from a repeater table where one of the repeaters is undefined:

I've done (2) on the devmon instance in question:

Index: modules/dm_tests.pm
===================================================================
--- modules/dm_tests.pm (revision 30)
+++ modules/dm_tests.pm (working copy)
@@ -1799,8 +1799,9 @@
            # Get our oid vars
             my $val   = $oid_h->{'val'}{$leaf};
             my $color = $oid_h->{'color'}{$leaf};
-            $val      = 'Undefined' if !defined $val;
-            $color    = 'clear' if !defined $color;
+           #$val      = 'Undefined' if !defined $val;
+           #$color    = 'clear' if !defined $color;
+           next T_LEAF if !defined $val;

            # Check the exception types, if it is an 'ignore'
            # dont include this leaf row if the data for this


and now I get:

AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   190.25 Kbps (1.86%) &green   
52.06 Kbps (0.51%)
  AT2/0/0  0.00 bps &green   8.13 Kbps (0.00%) &green   39.47 Kbps (0.00%)
  AT2/0/0 [---Link to XXX---]  10.24 Mbps &green   0.00 bps (0.00%) &green   
0.00 bps (0.00%)

The RRD lines still look the same:

AT2_0_0 1766267040:3175078912
AT2_0_0 U:U
AT2_0_0 U:U
AT2_0_0 3440140912:3883766474
AT2_0_0 0:0
AT2_0_0.100 U:U
AT2_0_0.100 3440140912:3883766474

So, I get a few graphs I don't need, however the page is green now.

So, should rows with undefined non-primary aliases be ignored by default? Or, 
should it be possible to add them as exceptions per-template-test?

Regards,
Buchan

Re: [Devmon] Devmon enhancement request

[Buchan M. <bg...@st...>]

On Monday 31 December 2007 13:33:01 Buchan Milne wrote:
> On Friday 14 December 2007 20:01:05 Stewart, Tom L. wrote:
> > Here are some additional details. If we can get a TABLE with nohtml and
> > no ":" then I can use the standard "disk" column in Hobbit to graph by
> > setting the message file to output and look like a normal disk column in
> > Hobbit.
>
> I tried it like this, by adding a "plain" option for TABLE (see attached
> patch against current svn), however this doesn't do what we need, as Hobbit
> expects exact spacing. I'll see if it is easy enough to run it through a
> printf instead (and, maybe change the option name, or add another one), so
> that we can easily format the output.
>
> (I'm currently testing against a WRT45GL running OpenWRT, which, until I
> get hobbit built for OpenWRT, would benefit from a template like this).

I got this working last week, I think the patch I sent previously was 
sufficient, I mostly needed changes in my template (which is now in svn with 
just the working disk test):

http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/templates/linux-openwrt/

Regards,
Buchan

Re: [Devmon] Template Help

[Buchan M. <bg...@st...>]

On Thursday 10 January 2008 23:12:01 Chuck Byam wrote:
> I'm working on a custom template, F5 specifically, and have a question for
> those  who have been through this before.  I'm attempting to generate an
> alert when the pool member node count drops to a certain point.
>
>
>
> Oid:
>
> PoolName : .1.3.6.1.4.1.3375.2.2.5.1.2.1.1 : branch
>
> PoolNodeCount : .1.3.6.1.4.1.3375.2.2.5.1.2.1.8 : branch
>
>
>
> Threshold:
>
> PoolNodeCount : yellow : <4 : {PoolName} Active Node Count {PoolNodeCount}
>
> PoolNodeCount : red : <2 : {PoolName} Active Node Count {PoolNodeCount}
>
>
>
> PoolNodeCount contains expected values as indicated in the message file,
> but alerts are never generated.  Running devmon in verbose mode doesn't
> yield any useful information.  What is the best way to troubleshoot this? 
> Any thoughts would be appreciated.

What version are you using ? 0.3.0-beta2 had a problem with numbeic 
thresholds, it is fixed in svn (I think this is the change that fixed it: 
http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/modules/dm_tests.pm?r1=3&r2=10)

Could you test with current svn ? If not, I think we will try and release a 
new beta or rc this week.

Regards,
Buchan

[Devmon] Ignored interfaces on cisco if_* tests

[Buchan M. <bg...@st...>]

On one of our 6509s, which has a few 100mb blades, I noticed I wasn't seeing 
the Fa* devices in devmon output.

I see that the exceptions file had this:

ifName : alarm  : Gi.+
ifName : ignore : Nu.+|Vl.+|VLAN.+

This seems to effectively only alarm on Gi.+. Adding Fa.+ fixed the issue 
here.

However, we have a 7613, which is detected by devmon as a 6509, and all the 
tests work ... but the WAN interfaces (AT.+. Se.+) were ignored as well.

More concerning is that the 7206 template has:

ifName : alarm  : Gi.+
ifName : ignore : Nu.+|Vl.+

We can add regexes for all the valid interface names, but to me it would make 
more sense to do something like this (if it works):

ifName : alarm : .+
ifName : ignore : Nu.+|Vl.+|VLAN.+

Regards,
Buchan

Re: [Devmon] (no subject)

[Buchan M. <bg...@st...>]

On Friday 11 January 2008 02:28:34 Alexander MacKinnon wrote:
> I have just installed devmon to get snmp information from some UPS's.
> Devmon is installed in a single hobbit server that has full snmp access to
> all those UPS's and has been confirmed with one snmpget to each of them. I
> have some problems getting devmon to obtain any information and there are a
> few questions that I need answered. In a single node system, does devmon
> get the list of hosts to be scanned from th bb-hosts file or from hosts.db
> file?

Devmon operates from the hosts.db file. If changes have been made to bb-hosts, 
devmon needs to be run with the --readbbhosts option to update the hosts.db 
file. It may be convenient to automate this. All of this is covered in the 
docs (INSTALLATION).

> In the devmon.cfg file there are several entries related to a 
> database. Are those entries required or useful in any way in a single node
> system?

No.

> Devmon is not writing to /var/log/devmon.log, actually the file 
> does not exists. Should I create it or did something fail during
> installation?

If the file does not exist, devmon would require write access to /var/log to 
create the file. I typically run devmon as the 'devmon' user, and configure 
it to log to /var/log/devmon/devmon.log, and create /var/log/devmon such that 
the 'devmon' user has write access to /var/log/devmon.

> Devmon is running each five minutes from a cron as adviced in 
> the doco and each time it runs, I get a message like this
> [08-01-11@11:20:42] Could not query device: myUPS_name_here

You mean you are running devmon with the --readbbhosts option according to 
item 5 in INSTALLATION ?

> I know is a lot, but if someone could show me the light would be
> appreciated. I have been going through the documentation with no luck :-(

You can run devmon with --readbbhosts --debug to get more information.

Regards,
Buchan

[Devmon] (no subject)

[Alexander M. <ale...@ya...>]

I have just installed devmon to get snmp information from some UPS's. Devmo=
n is installed in a single hobbit server that has full snmp access to all t=
hose UPS's and has been confirmed with one snmpget to each of them. I have =
some problems getting devmon to obtain any information and there are a few =
questions that I need answered.=0AIn a single node system, does devmon get =
the list of hosts to be scanned from th bb-hosts file or from hosts.db file=
?=0AIn the devmon.cfg file there are several entries related to a database.=
 Are those entries required or useful in any way in a single node system?=
=0ADevmon is not writing to /var/log/devmon.log, actually the file does not=
 exists. Should I create it or did something fail during installation?=0ADe=
vmon is running each five minutes from a cron as adviced in the doco and ea=
ch time it runs, I get a message like this=0A[08-01-11@11:20:42] Could not =
query device: myUPS_name_here=0A=0AI know is a lot, but if someone could sh=
ow me the light would be appreciated. I have been going through the documen=
tation with no luck :-(=0A=0AAlex=0A=0A=0A=0A=0A      Make the switch to th=
e world's best email. Get the new Yahoo!7 Mail now. www.yahoo7.com.au/world=
sbestemail=0A=0A

[Devmon] Template Help

[Chuck B. <cb...@vi...>]

I'm working on a custom template, F5 specifically, and have a question for
those  who have been through this before.  I'm attempting to generate an
alert when the pool member node count drops to a certain point.

 

Oid:

PoolName : .1.3.6.1.4.1.3375.2.2.5.1.2.1.1 : branch

PoolNodeCount : .1.3.6.1.4.1.3375.2.2.5.1.2.1.8 : branch

 

Threshold:

PoolNodeCount : yellow : <4 : {PoolName} Active Node Count {PoolNodeCount}

PoolNodeCount : red : <2 : {PoolName} Active Node Count {PoolNodeCount}

 

PoolNodeCount contains expected values as indicated in the message file, but
alerts are never generated.  Running devmon in verbose mode doesn't yield
any useful information.  What is the best way to troubleshoot this?  Any
thoughts would be appreciated.

 

Thanks,

--

Chuck Byam

[Devmon] extra-rrd.pl vs devmon RRD support

[Buchan M. <bg...@st...>]

The extra-rrd.pl in svn isn't using the RRD ds definitions that devmon sends 
(based on the template):

<!--DEVMON RRD: if_load 0 0
DS:ds0:COUNTER:600:0:U DS:ds1:COUNTER:600:0:U
[....]
-->

So, according to most of the current templates for if_load, the ds names 
are "ds0" and "ds1", not "in" and "out". Also, the DS definitions are 
hardcoded in the current extra-rrd.pl, and the script needlessly limits 
itself to working on specific tests (while they are already limited by the 
hobbitd_channel command).

I have attached the version I am currently using (which also works with the 
temp tests for compaq-server and dell-poweredge (which have:
TABLE: noalarmsmsg,rrd(DS:ds0:cpqHeTemperatureCelsius:GAUGE; 
DS:ds1:cpqHeTemperatureThreshold:GAUGE)
and
TABLE: noalarmsmsg,rrd(DS:ds0:temperatureProbeReadingCelsius:GAUGE; 
DS:ds1:temperatureProbeLowerCriticalThresholdCelsius:GAUGE).

So, I think it would be best to ship the final 0.3.0 with this being 
consistent (it wouldn't make sense to change it later). So, either we should 
change the templates, or people who have been using the current extra-rrd.pl 
should fix their data after upgrading, with something like:


# for i in `find /var/lib/hobbit/rrd/ -name 'if_load.G*.rrd' `;do mv $i 
$i.old; rrdtool dump $i.old|sed -e 's/ in / ds0 /g;s/ out / ds1 /g;'|rrdtool 
restore - $i;done
# chown -R hobbit:hobbit /var/lib/hobbit/rrd/


I am also looking at the possibility of shipping a patch for hobbit so that 
the extra-script is not necessary, and this would definitely have to use the 
RRD definitions devmon includes.

Regards,
Buchan