devmon-support — General Devmon support

Re: [Devmon] Any way to set thresholds based on previous values?

[W.J.M. N. <Wim...@nl...>]

Hhello,

> Is there any way to configure the threshold file such that a red alert will be sent based on a comparison between a test's previous value and its current value?  For example, I'm monitoring interface errors on a network device.  I'd like to send a red alert if the current number of interface errors is greater than the previous number of errors by X amount.
>   
A standard feature in Devmon: use the DELTA transform. It is used in 
many of the templates available in the Demon distribution.

Regards,
  Wim Nelis.



*******************************************************************************************************
The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages.
*******************************************************************************************************

Re: [Devmon] How to handle a sparse repeater?

[Dan S. <rrd...@gm...>]

I have exactly the same issue with one twist.
I have a sparse repeater that contains all alarms on a system.
When there were no alarms, all subsequent SNMP polls seemed to fail.

I have four test directories, A, B, C, D
The sparse repeater lives under B and has 10 OIDs associated with the sparse
repeater table (things like alarm name, alarm severity, alarm trigger
timestamp, etc.).

If I add up to 3 of the sparse repeater OIDs, I see the "No SNMP data found
for <oid alias> on <host>" error in the log for that OID.
If I add 4 or more of the sparse repeater OIDs, the first test in C fails
and throw errors in the logs of "No SNMP data found for <oid alias> on
<host>".  C just happens to have a branch index as the first entry, so the
table in test C fails to draw.

I assume that this is being caused by timeouts on the SNMP request or
something along those lines.
Has anyone else run into this?  Maybe adding a way to mark sparse repeaters
so devmon could short cycle them instead of going through error handling and
logging.

-dan

> -----Original Message-----
> From: W.J.M. Nelis [mailto:Wim...@nl...] 
> Sent: Wednesday, January 26, 2011 8:09 AM
> To: dev...@li...
> Subject: [Devmon] How to handle a sparse repeater?
> 
> Hello,
> 
> access ports on a Cisco switch may get into the status 
> 'err-disabled'.  
> I would like that to monitor using Devmon, and add this 
> status information to test 'if_stat'. However, the table 
> which does show this status only shows the interfaces which 
> are in teh 'err-disabled' state. 
> For example:
> 
> Using the switch CLI:
> nlrlnx93>sho int status | i err-dis
> Fa1/0/5                      err-disabled 174          auto   auto 
> 10/100BaseTX
> 
> Using SNMP:
> -bash-3.00$ snmpwalk -v 2c -c public nlrlnx93 
> .1.3.6.1.4.1.9.9.548.1.3 
> SNMPv2-SMI::enterprises.9.9.548.1.3.1.1.2.10005.0 = INTEGER: 
> 17 SNMPv2-SMI::enterprises.9.9.548.1.3.1.1.3.10005.0 = Gauge32: 0
> 
> Note that '10005' is the ifIndex of interface Fa1/0/5. The 
> interfaces which are *not* in state 'err-disabled' are thus 
> not mentioned in table
> (repeater) enterprises.9.9.548.1.3.1.1.2. Normally, this 
> table will be empty. Is there a way to handle this kind of 
> sparsely populated tables in Devmon?
> 
> An alternative is to write a script to retrieve this 
> information, but it implies that the results cannot be shown 
> in test if_stat.
> 
> Regards,
>   Wim Nelis.
> 
> 
> 
> **************************************************************
> *****************************************
> The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is 
> valid for NLR e-mail messages.
> **************************************************************
> *****************************************
> 
> 
> --------------------------------------------------------------
> ----------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even 
> better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer 
> expires February 28th, so secure your free ArcSight Logger TODAY! 
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
> 

[Devmon] Any way to set thresholds based on previous values?

[Lee, R. <Ray...@qw...>]

Hi,

Is there any way to configure the threshold file such that a red alert will be sent based on a comparison between a test's previous value and its current value?  For example, I'm monitoring interface errors on a network device.  I'd like to send a red alert if the current number of interface errors is greater than the previous number of errors by X amount.


Thanks,
Ray

Raymond Lee
Lead Internet Systems Engineer
Network Services
Qwest Corporation
4250 N. Fairfax Dr., 4E193
Arlington VA 22203
(703) 363-8889 (Office)
leeraym at vtext dot com (pager)

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.

Re: [Devmon] Regex issue with thresholds

[Dan S. <rrd...@gm...>]

The table suggestion sounds good.  I upgraded to 0.3.1-beta1 last night so I
could take advantage of the INDEX transform.  With that, I can pull off the
OID name and put that in as the index for the table.

Thanks!

-dan 

> -----Original Message-----
> From: Buchan Milne [mailto:bg...@st...] 
> Sent: Friday, February 04, 2011 12:17 AM
> To: dev...@li...
> Cc: Dan Smith
> Subject: Re: [Devmon] Regex issue with thresholds
> 
> On Thursday, 3 February 2011 21:01:20 Dan Smith wrote:
> > Are regular expressions supported in the OID name in the 
> thresholds file?
> 
> No.
> 
> > I guess I was trying to be lazy, but I've got data aliases defined 
> > like
> > this:
> > # Power down=0 up=1
> > AbcPEM48VoltAPowerSupply :  .x.x.x.x.x.x.x.x.x.x.x.1.0  : leaf 
> > AbcPEM48VoltBPowerSupply :  .x.x.x.x.x.x.x.x.x.x.x.2.0  : leaf
> > AbcPEM5VoltAPowerSupply :   .x.x.x.x.x.x.x.x.x.x.x.3.0  : leaf
> > AbcPEM5VoltBPowerSupply :   .x.x.x.x.x.x.x.x.x.x.x.4.0  : leaf
> > AbcPEMHot5VoltPowerSupply : .x.x.x.x.x.x.x.x.x.x.x.5.0  : leaf
> 
> This data would have better been supplied in a table IMHO, in 
> which case you would have only needed one set of thresholds.
> 
> > And I would like to apply the same up/down green/red threshold to 
> > all...something like this:
> > AbcPEM.*                    : red           : =0            : PSU is
> > currently DOWN
> > AbcPEM.*                    : green         : =1            : PSU is
> > currently UP
> > 
> > When I do that, devmon throws this error:
> > [11-02-03@13:54:06] Undefined oid 'AbcPEM.*' referenced in 
> > /usr/share/devmon/templates/System-Abc/chassis/thresholds at line 8 
> > [11-02-03@13:54:06] Undefined oid 'AbcPEM.*' referenced in 
> > /usr/share/devmon/templates/System-Abc/chassis/thresholds at line 8
> > 
> > I can't imagine a more simple regular expression than ".*", so am I 
> > correct that the regular expression support does not apply 
> to the data alias.
> > The TEMPLATES file talks about regular expressions in 
> thresholds, but 
> > I think it is saying that they can be used only in the 
> VALUE portion.
> 
> Correct.
> 
> Regards,
> Buchan
> 

Re: [Devmon] Regex issue with thresholds

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

On Thursday, 3 February 2011 21:01:20 Dan Smith wrote:
> Are regular expressions supported in the OID name in the thresholds file?

No.

> I guess I was trying to be lazy, but I've got data aliases defined like
> this:
> # Power down=0 up=1
> AbcPEM48VoltAPowerSupply :  .x.x.x.x.x.x.x.x.x.x.x.1.0  : leaf
> AbcPEM48VoltBPowerSupply :  .x.x.x.x.x.x.x.x.x.x.x.2.0  : leaf
> AbcPEM5VoltAPowerSupply :   .x.x.x.x.x.x.x.x.x.x.x.3.0  : leaf
> AbcPEM5VoltBPowerSupply :   .x.x.x.x.x.x.x.x.x.x.x.4.0  : leaf
> AbcPEMHot5VoltPowerSupply : .x.x.x.x.x.x.x.x.x.x.x.5.0  : leaf

This data would have better been supplied in a table IMHO, in which case you 
would have only needed one set of thresholds.

> And I would like to apply the same up/down green/red threshold to
> all...something like this:
> AbcPEM.*                    : red           : =0            : PSU is
> currently DOWN
> AbcPEM.*                    : green         : =1            : PSU is
> currently UP
> 
> When I do that, devmon throws this error:
> [11-02-03@13:54:06] Undefined oid 'AbcPEM.*' referenced in
> /usr/share/devmon/templates/System-Abc/chassis/thresholds at line 8
> [11-02-03@13:54:06] Undefined oid 'AbcPEM.*' referenced in
> /usr/share/devmon/templates/System-Abc/chassis/thresholds at line 8
> 
> I can't imagine a more simple regular expression than ".*", so am I correct
> that the regular expression support does not apply to the data alias.
> The TEMPLATES file talks about regular expressions in thresholds, but I
> think it is saying that they can be used only in the VALUE portion.

Correct.

Regards,
Buchan

[Devmon] Regex issue with thresholds

[Dan S. <rrd...@gm...>]

Are regular expressions supported in the OID name in the thresholds file?
I guess I was trying to be lazy, but I've got data aliases defined like
this:
# Power down=0 up=1
AbcPEM48VoltAPowerSupply :  .x.x.x.x.x.x.x.x.x.x.x.1.0  : leaf
AbcPEM48VoltBPowerSupply :  .x.x.x.x.x.x.x.x.x.x.x.2.0  : leaf
AbcPEM5VoltAPowerSupply :   .x.x.x.x.x.x.x.x.x.x.x.3.0  : leaf
AbcPEM5VoltBPowerSupply :   .x.x.x.x.x.x.x.x.x.x.x.4.0  : leaf
AbcPEMHot5VoltPowerSupply : .x.x.x.x.x.x.x.x.x.x.x.5.0  : leaf

And I would like to apply the same up/down green/red threshold to
all...something like this:
AbcPEM.*                    : red           : =0            : PSU is
currently DOWN
AbcPEM.*                    : green         : =1            : PSU is
currently UP

When I do that, devmon throws this error:
[11-02-03@13:54:06] Undefined oid 'AbcPEM.*' referenced in
/usr/share/devmon/templates/System-Abc/chassis/thresholds at line 8
[11-02-03@13:54:06] Undefined oid 'AbcPEM.*' referenced in
/usr/share/devmon/templates/System-Abc/chassis/thresholds at line 8

I can't imagine a more simple regular expression than ".*", so am I correct
that the regular expression support does not apply to the data alias.
The TEMPLATES file talks about regular expressions in thresholds, but I
think it is saying that they can be used only in the VALUE portion.
 
Thanks!
 
-dan

Re: [Devmon] devmon 0.3.1-beta1 goes purple, error message

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

On Monday, 29 November 2010 11:55:19 Buchan Milne wrote:
> On Friday, 26 November 2010 15:14:50 Taylor Lewick wrote:
> > We upgraded xymon to run 4.3.0-0.beta2 from hobbit 4.2.3
> > In so doing, we also upgraded devmon to devmon 0.3.1-beta1.  So far
> > everything with xymon works great, and devmon works as expected, except
> > it goes purple quite often.
> 
> I can't reproduce this reliably myself.

Well, I'm back in an environment I was in before, and one of the devmon 
installations (on RHEL5) still gives the purple problem, even after upgrading 
to svn (but, for another installation, on RHEL4, the upgrade seems to have 
solved all problems).

In the case of the problematic installation, it reports to a remote hobbitd, 
and with -vvv --debug, it logs this:
[11-02-02@09:56:56] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:56] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:56] DEBUG: Printing single combo message size 26428
[11-02-02@09:56:56] DEBUG: Finished printing single combo message
[11-02-02@09:56:56] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:56] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:56] DEBUG: Printing single combo message size 26412
[11-02-02@09:56:56] DEBUG: Finished printing single combo message
[11-02-02@09:56:56] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:56] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:56] DEBUG: Printing single combo message size 41414
[11-02-02@09:56:56] DEBUG: Finished printing single combo message
[11-02-02@09:56:56] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:56] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:56] DEBUG: Printing combo message with multiple messages
[11-02-02@09:56:56] DEBUG: Finished printing combo message with multiple 
messages
[11-02-02@09:56:56] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:56] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:56] DEBUG: Printing single combo message size 8338
[11-02-02@09:56:56] DEBUG: Finished printing single combo message
[11-02-02@09:56:56] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:56] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:56] DEBUG: Printing combo message with multiple messages

[...]

[11-02-02@09:56:57] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:57] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:57] DEBUG: Printing combo message with multiple messages
[11-02-02@09:56:57] DEBUG: Finished printing combo message with multiple 
messages
[11-02-02@09:56:57] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:57] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:57] DEBUG: Printing combo message with multiple messages
[11-02-02@09:56:57] DEBUG: Finished printing combo message with multiple 
messages
[11-02-02@09:56:57] DEBUG: Printing combo message with multiple messages
[11-02-02@09:56:57] DEBUG: Finished printing combo message with multiple 
messages
[11-02-02@09:56:57] DEBUG: Printing combo message with multiple messages
[11-02-02@09:56:57] DEBUG: Finished printing combo message with multiple 
messages
[11-02-02@09:56:57] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:56:57] DEBUG: Looping through messages to build a combo
[11-02-02@09:56:57] DEBUG: Printing combo message with multiple messages
[11-02-02@09:56:57] DEBUG: Finished printing combo message with multiple 
messages
[11-02-02@09:56:57] DEBUG: Opening socket to xxx.xxx.xxx.xxx:1984
[11-02-02@09:57:00] DEBUG: Looping through messages to build a combo
[11-02-02@09:57:00] DEBUG: Printing single combo message size 102907
[11-02-02@10:49:11] Forking to background process 11517
[11-02-02@10:49:11] Re-opened log file /var/log/devmon/devmon.log
[11-02-02@10:49:11] Nodename autodetected as yyy.yyy.yyy
[11-02-02@10:49:11] Option 'bbdateformat' defaulting to: %a %b %d %H:%M:%S %Z 
%Y.
[11-02-02@10:49:11] Option 'snmptimeout' defaulting to: 2.
[11-02-02@10:49:11] ---Initilizing devmon...
[11-02-02@10:49:11] Verbosity level: 3
[11-02-02@10:49:11] Logging to /var/log/devmon/devmon.log

[...]


I have seen it fail a number of times, and every time it fails, it fails on:

[11-02-02@09:57:00] DEBUG: Printing single combo message size 102907

But, we see above that one the same polling cycle, it managed to do this a 
number of times without a problem. I don't think it's specifically the size, 
as I have seen it fail with "message size" of less (around 30 000).

When it fails like this, the devmon[master] process is missing, and the rest 
of the devmon forks are eating CPU (which I will look at fixing).


I have moved some logging around locally, the code running currently looks 
like this:


       # Make sure the message itself isnt too big
        if(length $msg > $g{'msgsize'}) {

         # Nuts, this is a huge message, bigger than our msg size. Well want
         # to send it by itself to minimize how much it gets truncated
          if($msg_size == 0) {
            my $thismsgsize = length $msg;
           # Okay, we are clear, send the message 
            eval {
              local $SIG{ALRM} = sub {do_log("Dying in alarm",0); die 
"Printing message timed out\n" };
              alarm 10;
              do_log("DEBUG: Printing single combo message size 
$thismsgsize",3) if $g{'debug'};
              print SOCK "$msg\n";
              do_log("DEBUG: Finished printing single combo message",3) if 
$g{'debug'};
              alarm 0;
            };
            if ($@) {
              do_log("Timed out printing to display server: $!",0);
              close SOCK;
              return;
            }
          }

         # Not an empty combo msg, wait till our new socket is open
          else {
            unshift @{$g{'test_results'}}, $msg;
          }

         # Either way, open a new socket
          close SOCK;
          next SOCKLOOP;
        }

(very similar to what is in svn)

Now, I don't see how the current behaviour is possible. After printing "DEBIG: 
Printing single combo message ...", it should print to the socket. If the 
print call takes more than 10s, we should at *least* see "Dying in alarm", or 
"Timed out printing to display server: Printing message timed out" in the log. 
If it succeeds, we should of course see "Finished printing single combo 
message" as we do in the other examples.

So, I wonder if anyone else can shed some light on this?

I was really hoping to try and solve all the purple issues I could reproduce 
soon, and release 0.3.1 ...

Regards,
Buchan

Re: [Devmon] SNMP: no responce received

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

On Wednesday, 22 December 2010 11:26:11 Stef Coene wrote:
> Hi,
> 
> One of our SAN switches I'm monitoring has problems with the snmp daemon.
> 
> This is the devmon output:
> 
> SNMP Error:
> no response received
> SNMPv2c_Session (remote host: "x.x.x.x" [x.x.x.x].161)
>                    community: "public"
>                   request ID: -2068369166
>                  PDU bufsize: 16384 bytes
>                      timeout: 2s
>                      retries: 4
>                      backoff: 1)
>  at /data/users/hobbit/server/devmon/modules/dm_snmp.pm line 645
> [10-12-22@09:23:03] Performing test logic
> [10-12-22@09:23:03] No SNMP data found for swOperStatus on xxx
> 
> Can I trap this in devmon and generate an error status?

What happens at present? Does the test go clear?

I'll see if we can expose the SNMP error message somewhere.

Regards,
Buchan

Re: [Devmon] HP Proliant DL380 G6

[Colin C. <col...@gm...>]

Hmm, that was a little light on detail...

OK, these are a mix of RHEL5 and RHEL6, all x86_64.  They're running
the supplied net-snmp SNMP daemon.  Also installed are hp-health,
hp-snmp-agents and hpacucli from the Proliant Support Packs.

snmpwalk works fine.

Looking at templates/compaq-server/raid/transforms, I see
"cntrlModTxt" only goes up to 34 whereas the DL380 G6 is reporting
"39"
---
snmpwalk -v2c -c CENSOR 192.168.10.56 1.3.6.1.4.1.232.3.2.2.1.1.2
SNMPv2-SMI::enterprises.232.3.2.2.1.1.2.0 = INTEGER: 39
---

I've configured SNMP and pointed devmon at a couple more G6s and found
that only the initial two G6s are reporting the badness (see attached
.png file).  The other G6s are reporting OK for condition and status.

I've run hpacucli:
---
HP Array Configuration Utility CLI 8.60-8.0
Detecting Controllers...Done.
Type "help" for a list of supported commands.
Type "exit" to close the console.

=> controller slot=0 show

Smart Array P410i in Slot 0 (Embedded)
   Bus Interface: PCI
   Slot: 0
   Serial Number: .censored.
   Cache Serial Number: .censored.
   RAID 6 (ADG) Status: Disabled
   Controller Status: OK
   Chassis Slot:
   Hardware Revision: Rev C
   Firmware Version: 3.00
   Rebuild Priority: Medium
   Expand Priority: Medium
   Surface Scan Delay: 15 secs
   Surface Scan Mode: Idle
   Queue Depth: Automatic
   Monitor and Performance Delay: 60 min
   Elevator Sort: Enabled
   Degraded Performance Optimization: Disabled
   Inconsistency Repair Policy: Disabled
   Wait for Cache Room: Disabled
   Surface Analysis Inconsistency Notification: Disabled
   Post Prompt Timeout: 0 secs
   Cache Board Present: True
   Cache Status: Permanently Disabled
   Accelerator Ratio: 25% Read / 75% Write
   Drive Write Cache: Disabled
   Total Cache Size: 512 MB
   No-Battery Write Cache: Disabled
   Cache Backup Power Source: Batteries
   Battery/Capacitor Count: 1
   Battery/Capacitor Status: OK
   SATA NCQ Supported: True

=>
---

The only thing that I can that is different between the systems
reporting OK and those not reporting OK is on the cache status line.
Thos reporting OK have a cache status of OK, the others have a cache
status of "permanently disabled".

Thanks

CC

On Thu, Jan 27, 2011 at 10:08 PM, Root, Paul <Pau...@qw...> wrote:
> So what's running your snmpd? Are you trying to look at the Lom, or are you going into the OS?
>
> How is it configured. What do you get when you do an snmpwalk (just system) of the machine?
>
>
> Paul Root
> Lead Internet Systems Eng
> Qwest Network Services
>
>
> -----Original Message-----
> From: Colin Coe [mailto:col...@gm...]
> Sent: Thursday, January 27, 2011 12:54 AM
> To: dev...@li...
> Subject: [Devmon] HP Proliant DL380 G6
>
> Hi all
>
> I'm getting 'unknown' as the model number for the DL380 G6's that I'm
> monitoring as well as condition of degraded and status of general
> failure.
>
> Is anyone else seeing this?
>
> Thanks
>
> CC
>
> --
> RHCE#805007969328369
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

-- 
RHCE#805007969328369

Re: [Devmon] HP Proliant DL380 G6

[Root, P. <Pau...@qw...>]

So what's running your snmpd? Are you trying to look at the Lom, or are you going into the OS?

How is it configured. What do you get when you do an snmpwalk (just system) of the machine?


Paul Root
Lead Internet Systems Eng
Qwest Network Services


-----Original Message-----
From: Colin Coe [mailto:col...@gm...]
Sent: Thursday, January 27, 2011 12:54 AM
To: dev...@li...
Subject: [Devmon] HP Proliant DL380 G6

Hi all

I'm getting 'unknown' as the model number for the DL380 G6's that I'm
monitoring as well as condition of degraded and status of general
failure.

Is anyone else seeing this?

Thanks

CC

--
RHCE#805007969328369

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support

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.

Re: [Devmon] HP Proliant DL380 G6

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

On Thursday, 27 January 2011 08:54:01 Colin Coe wrote:
> Hi all
> 
> I'm getting 'unknown' as the model number for the DL380 G6's that I'm
> monitoring as well as condition of degraded and status of general
> failure.

Can you re-phrase your question, it is a bit difficult to give a useful answer 
with a question without much in the way of details.

Regards,
Buchan

[Devmon] HP Proliant DL380 G6

[Colin C. <col...@gm...>]

Hi all

I'm getting 'unknown' as the model number for the DL380 G6's that I'm
monitoring as well as condition of degraded and status of general
failure.

Is anyone else seeing this?

Thanks

CC

-- 
RHCE#805007969328369

[Devmon] How to handle a sparse repeater?

[W.J.M. N. <Wim...@nl...>]

Hello,

access ports on a Cisco switch may get into the status 'err-disabled'.  
I would like that to monitor using Devmon, and add this status 
information to test 'if_stat'. However, the table which does show this 
status only shows the interfaces which are in teh 'err-disabled' state. 
For example:

Using the switch CLI:
nlrlnx93>sho int status | i err-dis
Fa1/0/5                      err-disabled 174          auto   auto 
10/100BaseTX

Using SNMP:
-bash-3.00$ snmpwalk -v 2c -c public nlrlnx93 .1.3.6.1.4.1.9.9.548.1.3
SNMPv2-SMI::enterprises.9.9.548.1.3.1.1.2.10005.0 = INTEGER: 17
SNMPv2-SMI::enterprises.9.9.548.1.3.1.1.3.10005.0 = Gauge32: 0

Note that '10005' is the ifIndex of interface Fa1/0/5. The interfaces 
which are *not* in state 'err-disabled' are thus not mentioned in table 
(repeater) enterprises.9.9.548.1.3.1.1.2. Normally, this table will be 
empty. Is there a way to handle this kind of sparsely populated tables 
in Devmon?

An alternative is to write a script to retrieve this information, but it 
implies that the results cannot be shown in test if_stat.

Regards,
  Wim Nelis.



*******************************************************************************************************
The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages.
*******************************************************************************************************

Re: [Devmon] Don't use 'x' in OID names used in MATH

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

On Tuesday, 4 January 2011 13:56:07 W.J.M. Nelis wrote:
> Hello,
> 
> for a test (of a Cisco switch) the following OID is defined in file 'oids':
>   ifDuplexNum : .1.3.6.1.2.1.10.7.2.1.19      : branch
> 
> In order to make a combined test, this variable was used in a MATH
> transform:
> 
>   ifStSpDu : MATH : {ifBps} + {ifOperStatNum} - 1 + ({ifDuplexNum}-1)x7
> 
> This resulted in the following error to be logged:
> [11-01-04@10:30:29] Failed eval for TRANS_MATH on ifStSpDu.10101:
> $dep_val[0] + $dep_val[1] - 1 + ({ifDuple*Num}-1)*7 (Bareword "ifDuple"
> not allowed while "strict subs" in use at (eval 2127005512) line 1,
> <$__ANONIO__> line 16594987. Bareword "Num" not allowed while "strict
> subs" in use at (eval 2127005512) line 1, <$__ANONIO__> line 16594987.
> 
> The 'x' in 'ifDuplexNum' has been changed to a '*' as well. This happens in
> module dm_tests.pm, function trans_math near line 442:
> 
>    # Convert our math symbols to their perl equivalents
>     $expr =~ s/x/\*/g;  # Multiplication
>     $expr =~ s/\^/**/g; # Exponentiation
> 
> The RE sgould be replaced by one which replaces any 'x' outside '{' and
> '}'. Lacking the knowledge to write such an RE, I've changed the name of
> the variable, such that is does not contain an 'x' in it any more.

I have changed it instead to only honour ' x ':

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

It might be better to allow '*' as multiplication operator instead, and phase 
'x' or ' x ' out.

There was only one template in svn using {oid}xINT, you'll see the commit 
fixed it.

Regards,
Buchan

[Devmon] Don't use 'x' in OID names used in MATH

[W.J.M. N. <Wim...@nl...>]

Hello,

for a test (of a Cisco switch) the following OID is defined in file 'oids':
  ifDuplexNum : .1.3.6.1.2.1.10.7.2.1.19      : branch

In order to make a combined test, this variable was used in a MATH 
transform:

  ifStSpDu : MATH : {ifBps} + {ifOperStatNum} - 1 + ({ifDuplexNum}-1)x7

This resulted in the following error to be logged:
[11-01-04@10:30:29] Failed eval for TRANS_MATH on ifStSpDu.10101: $dep_val[0] + $dep_val[1] - 1 + ({ifDuple*Num}-1)*7 (Bareword "ifDuple" not allowed while "strict subs" in use at (eval 2127005512) line 1, <$__ANONIO__> line 16594987.
Bareword "Num" not allowed while "strict subs" in use at (eval 2127005512) line 1, <$__ANONIO__> line 16594987.

The 'x' in 'ifDuplexNum' has been changed to a '*' as well. This happens in module dm_tests.pm, function trans_math near line 442:

   # Convert our math symbols to their perl equivalents
    $expr =~ s/x/\*/g;  # Multiplication
    $expr =~ s/\^/**/g; # Exponentiation

The RE sgould be replaced by one which replaces any 'x' outside '{' and '}'. Lacking the knowledge to write such an RE, I've changed the name of the variable, such that is does not contain an 'x' in it any more.

Regards,
  Wim Nelis.



*******************************************************************************************************
The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages.
*******************************************************************************************************

[Devmon] SNMP: no responce received

[Stef C. <ste...@do...>]

Hi,

One of our SAN switches I'm monitoring has problems with the snmp daemon.

This is the devmon output:

SNMP Error:
no response received
SNMPv2c_Session (remote host: "x.x.x.x" [x.x.x.x].161)
                   community: "public"
                  request ID: -2068369166
                 PDU bufsize: 16384 bytes
                     timeout: 2s
                     retries: 4
                     backoff: 1)
 at /data/users/hobbit/server/devmon/modules/dm_snmp.pm line 645
[10-12-22@09:23:03] Performing test logic
[10-12-22@09:23:03] No SNMP data found for swOperStatus on xxx

Can I trap this in devmon and generate an error status?


Stef

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

[Devmon] Ignore power warning

[Colin C. <col...@gm...>]

Hi all

I've been asked to start monitoring a few Proliant ML370 G3s.  All of
these machines are single power supply only although they are capable
of having two in a redundant setup.  As a result, all of these
machines are warning about only having a single power suppply.

I've read through the USING file but haven't grasped how to make
devmon ignore this.  I've tried:

0.0.0.0 server  #
DEVMON:model(compaq;servernohspare),except(power;cpqHeFltTolPowerSupplyPresentTxt;i)

and

0.0.0.0 server  #
DEVMON:model(compaq;servernohspare),except(power;Power Supply
Present;i)

Any ideas?

Thanks

CC

-- 
RHCE#805007969328369

Re: [Devmon] HP Proliant DL380

[Colin C. <col...@gm...>]

On Thu, Dec 9, 2010 at 8:31 PM, Buchan Milne <bg...@st...> wrote:
> On Thursday, 9 December 2010 02:02:53 Colin Coe wrote:
>
>> I grabbed the code out of the SVN on SF and rebuilt.  It looked a lot
>> better but what I found was on one of the Proliants with a failed
>> drive but no spare,
>
> What template were you using? This probably indicates you should be using (for
> now) compaq-servernohspare, until the questions below are resolved ...
>
>> the test came back clear not red.  I made this
>> change:
>> # diff -u dm_tests.pm.orig dm_tests.pm
>> ----
>> --- dm_tests.pm.orig    2010-12-09 08:07:04.000000000 +0800
>> +++ dm_tests.pm 2010-12-09 08:18:14.000000000 +0800
>> @@ -1820,9 +1820,9 @@
>>
>>         # Make sure we have leaf data for our primary oid
>>          if(!defined $oids->{$pri}{'val'}) {
>> -          do_log("Missing repeater data for $pri for $test msg", 0);
>> -          $msg .= "&clear Missing repeater data for primary OID $pri\n";
>> -          $worst_color = 'clear';
>> +          do_log("Warning: missing repeater data for $pri for $test msg",
>> 0); +#          $msg .= "&clear Missing repeater data for primary OID
>> $pri\n"; +#          $worst_color = 'clear';
>>            next;
>>          }
>>
>> ----
>> and it now comes back red although I don't know what the potential
>> badness of this change is (not knowing the code).
>
> This isn't the right fix, but it is difficult to know what the correct fix is.
> What should occur when a table is totally empty? If there has been one
> complete table on the test, do we ignore failures on the rest? Do we report
> that the tables are empty? Do we try and allow customisation of what happens
> based on the template (e.g., in this case, warn that there are no hot spares
> or not, including allowing the admin to change a threshold)?
>
> Maybe for now the best option is to keep the $msg line?
>
> Regards,
> Buchan
>

Hi Buchan

Many thanks for the pointers.  Using 'servernohspare' does look like
it has fixed my problems.

Another question though, it appears that the 'servernohspare' test
does not show the controller status where plain 'server' does.  Is
this intentional?

Thanks again

CC

-- 
RHCE#805007969328369

Re: [Devmon] HP Proliant DL380

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

On Thursday, 9 December 2010 02:02:53 Colin Coe wrote:

> I grabbed the code out of the SVN on SF and rebuilt.  It looked a lot
> better but what I found was on one of the Proliants with a failed
> drive but no spare,

What template were you using? This probably indicates you should be using (for 
now) compaq-servernohspare, until the questions below are resolved ...

> the test came back clear not red.  I made this
> change:
> # diff -u dm_tests.pm.orig dm_tests.pm
> ----
> --- dm_tests.pm.orig    2010-12-09 08:07:04.000000000 +0800
> +++ dm_tests.pm 2010-12-09 08:18:14.000000000 +0800
> @@ -1820,9 +1820,9 @@
> 
>         # Make sure we have leaf data for our primary oid
>          if(!defined $oids->{$pri}{'val'}) {
> -          do_log("Missing repeater data for $pri for $test msg", 0);
> -          $msg .= "&clear Missing repeater data for primary OID $pri\n";
> -          $worst_color = 'clear';
> +          do_log("Warning: missing repeater data for $pri for $test msg",
> 0); +#          $msg .= "&clear Missing repeater data for primary OID
> $pri\n"; +#          $worst_color = 'clear';
>            next;
>          }
> 
> ----
> and it now comes back red although I don't know what the potential
> badness of this change is (not knowing the code).

This isn't the right fix, but it is difficult to know what the correct fix is. 
What should occur when a table is totally empty? If there has been one 
complete table on the test, do we ignore failures on the rest? Do we report 
that the tables are empty? Do we try and allow customisation of what happens 
based on the template (e.g., in this case, warn that there are no hot spares 
or not, including allowing the admin to change a threshold)?

Maybe for now the best option is to keep the $msg line?

Regards,
Buchan

Re: [Devmon] HP Proliant DL380

[Colin C. <col...@gm...>]

On Tue, Dec 7, 2010 at 10:26 PM, Buchan Milne
<bg...@st...> wrote:
> On Tuesday, 7 December 2010 07:01:03 Colin Coe wrote:
>> Hi all
>>
>> I'm having a problem with devmon and some HP Proliant DL380's.  The
>> problem is simply that devmon is able to extract info (raid, power,
>> temp, etc) from some but not others.
>
> This can occur when a test has some oids that may not be populated at all
> (e.g. using compaq-server on HP ProLiants with no hot spare configured end up
> with a failure polling sprDrvCntIndex, devmon gives up and doesn't poll - say
> - fans).
>
> I think I fixed this in svn with this commit:
>
> http://devmon.svn.sf.net/viewvc/devmon?view=revision&revision=156
>
> (see the explanation there)
>
> If this is not the issue, can you give more information (which tests are
> clear, details from verbose or debug logging indicating what occurs)?
>
>> To make matters less clear, on a
>> couple of the hosts where devmon works, I *cannot* snmpwalk from the
>> devmon/xymon server and on hosts where devmon doesn't work I *can*
>> snmpwalk.
>
> This makes no sense ... please confirm you are using the correct details
> devmon uses (e.g. 'cat -v hosts.db' will show records separated by '^['
> sequences). You may also want to do some packet tracing (with tcpdump or
> wireshark) if you really can't sort this out.
>
>> I've looked at the oids file and snmpwalked (for example "snmpwalk -v
>> 2c -c COMMUNITY_STR server 1.3.6.1.4.1.232.6.2.6.8.1.1") on all the
>> hosts where the "compaq;server" tests are clear, and found that I
>> could "proper" responses from most of them.
>
> Check all the oids from all tests, or apply the patch from svn, or test with
> svn trunk.
>
>> The mix of working machines includes Linux (RHEL4 & 5) and Windows.
>> The non-working machines are all Linux (RHEL4 & 5).
>>
>> All Linux nodes have the HP PSP RPMs installed (specifically
>> hp-snmp-agents) and include "dlmod cmaX /usr/lib64/libcmaX64.so" at
>> the top of /etc/snmp/snmpd.conf.
>>
>> /etc/snmp/snmpd.conf on all Linux hosts has the line: "rocommunity
>> COMMUNITY_STR monhost.company.com" where monhost.company.com is the
>> devmon/xymon server.
>>
>> The SNMP service has been restarted.
>>
>> This has me stumped.
>
>
> Regards,
> Buchan
>

Hi

I grabbed the code out of the SVN on SF and rebuilt.  It looked a lot
better but what I found was on one of the Proliants with a failed
drive but no spare, the test came back clear not red.  I made this
change:
# diff -u dm_tests.pm.orig dm_tests.pm
----
--- dm_tests.pm.orig    2010-12-09 08:07:04.000000000 +0800
+++ dm_tests.pm 2010-12-09 08:18:14.000000000 +0800
@@ -1820,9 +1820,9 @@

        # Make sure we have leaf data for our primary oid
         if(!defined $oids->{$pri}{'val'}) {
-          do_log("Missing repeater data for $pri for $test msg", 0);
-          $msg .= "&clear Missing repeater data for primary OID $pri\n";
-          $worst_color = 'clear';
+          do_log("Warning: missing repeater data for $pri for $test msg", 0);
+#          $msg .= "&clear Missing repeater data for primary OID $pri\n";
+#          $worst_color = 'clear';
           next;
         }

----
and it now comes back red although I don't know what the potential
badness of this change is (not knowing the code).

As for what I can snmpwalk and what I can't, I'm going to have to
plead insanity.  After some sleep and looking at it again I see where
I went wrong on those hosts

Thanks

CC


-- 
RHCE#805007969328369

Re: [Devmon] HP Proliant DL380

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

On Tuesday, 7 December 2010 07:01:03 Colin Coe wrote:
> Hi all
> 
> I'm having a problem with devmon and some HP Proliant DL380's.  The
> problem is simply that devmon is able to extract info (raid, power,
> temp, etc) from some but not others.

This can occur when a test has some oids that may not be populated at all 
(e.g. using compaq-server on HP ProLiants with no hot spare configured end up 
with a failure polling sprDrvCntIndex, devmon gives up and doesn't poll - say 
- fans).

I think I fixed this in svn with this commit:

http://devmon.svn.sf.net/viewvc/devmon?view=revision&revision=156

(see the explanation there)

If this is not the issue, can you give more information (which tests are 
clear, details from verbose or debug logging indicating what occurs)?

> To make matters less clear, on a
> couple of the hosts where devmon works, I *cannot* snmpwalk from the
> devmon/xymon server and on hosts where devmon doesn't work I *can*
> snmpwalk.

This makes no sense ... please confirm you are using the correct details 
devmon uses (e.g. 'cat -v hosts.db' will show records separated by '^[' 
sequences). You may also want to do some packet tracing (with tcpdump or 
wireshark) if you really can't sort this out.

> I've looked at the oids file and snmpwalked (for example "snmpwalk -v
> 2c -c COMMUNITY_STR server 1.3.6.1.4.1.232.6.2.6.8.1.1") on all the
> hosts where the "compaq;server" tests are clear, and found that I
> could "proper" responses from most of them.

Check all the oids from all tests, or apply the patch from svn, or test with 
svn trunk.

> The mix of working machines includes Linux (RHEL4 & 5) and Windows.
> The non-working machines are all Linux (RHEL4 & 5).
> 
> All Linux nodes have the HP PSP RPMs installed (specifically
> hp-snmp-agents) and include "dlmod cmaX /usr/lib64/libcmaX64.so" at
> the top of /etc/snmp/snmpd.conf.
> 
> /etc/snmp/snmpd.conf on all Linux hosts has the line: "rocommunity
> COMMUNITY_STR monhost.company.com" where monhost.company.com is the
> devmon/xymon server.
> 
> The SNMP service has been restarted.
> 
> This has me stumped.


Regards,
Buchan

[Devmon] HP Proliant DL380

[Colin C. <col...@gm...>]

Hi all

I'm having a problem with devmon and some HP Proliant DL380's.  The
problem is simply that devmon is able to extract info (raid, power,
temp, etc) from some but not others.  To make matters less clear, on a
couple of the hosts where devmon works, I *cannot* snmpwalk from the
devmon/xymon server and on hosts where devmon doesn't work I *can*
snmpwalk.

I've looked at the oids file and snmpwalked (for example "snmpwalk -v
2c -c COMMUNITY_STR server 1.3.6.1.4.1.232.6.2.6.8.1.1") on all the
hosts where the "compaq;server" tests are clear, and found that I
could "proper" responses from most of them.

The mix of working machines includes Linux (RHEL4 & 5) and Windows.
The non-working machines are all Linux (RHEL4 & 5).

All Linux nodes have the HP PSP RPMs installed (specifically
hp-snmp-agents) and include "dlmod cmaX /usr/lib64/libcmaX64.so" at
the top of /etc/snmp/snmpd.conf.

/etc/snmp/snmpd.conf on all Linux hosts has the line: "rocommunity
COMMUNITY_STR monhost.company.com" where monhost.company.com is the
devmon/xymon server.

The SNMP service has been restarted.

This has me stumped.

Any ideas on this?

CC

-- 
RHCE#805007969328369

Re: [Devmon] Graphing Interface Errors / Other tests

[Mario V. <mar...@gm...>]

Thanks for the reply.

I re-checked the config after receiving your mail and realised I hadn't
added the "*TABLE:rrd... " *section correctly in the message files.  The *.rrd
*files are now updating happily....

Yes, I get an RRD table in the html of the test, but the graphs are
still not showing - I think this must be due to my graph definitions which
I'll look at next week.


Thanks also for explaining my last question below, much appreciated.


Best regards,
Mario




On 3 December 2010 16:44, Buchan Milne <bg...@st...> wrote:

> On Friday, 3 December 2010 14:34:22 Mario Valetti wrote:
> > Hi,
> >
> > I realise my question has previously been posted, but I cannot find an
> > answer or guide that gets this working on my installation.
> >
> > Basically, I want to graph interface errors (if_err), or discards
> > (if_dsc) or something that is monitored in devmon which is not already
> > graphed by default (like the if_load, for example).  I've followed the
> > documentation on
> > http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/docs/GRAPHING,
> which
> > I believe is the latest how-to, but at the moment I don't get .rrd files
> > created after completing steps 1 & 2 and restarting  Xymon (adding
> > "if_err=devmon" to TEST2RRD in hobbitserver.cfg).
> >
> > I'm running XYMON 4.3.0.0-beta2, and DEVMON v0.3.1-beta1.
>
> I believe the devmon collector module crashes in xymon-4.3.0-beta2, please
> use
> beta3. However ... if you are getting graphs for if_load, then there must
> be a
> different problem.
>
> > As I'm testing this against a 3750 switch, I have also added
> > "TABLE:rrd(DS:ds0:ifInErrors:COUNTER; DS:ds1:ifOutErrors:COUNTER)" to the
> > message file of the standard cisco-3750/if_err template as explained in
> the
> > docs.
> >
>
> Do you get an RRD table in the html of the test (e.g. View->Source from
> your
> browser when viewing the test page for if_err on this device)?
>
> If so, what you have done should be sufficient to generate rrd files. You
> may
> want to check your rrd-status.log file for any errors.
>
> > I've added graph definitions to the hobbitgraph.cfg file; but even if
> there
> > is an error there it shouldn't prevent the .rrd files been written, as
> far
> > as I understand.
> >
> >
> > Last thing...
> > I'm not fully understanding the steps (and probably where I'm going
> wrong:
> > * "In order for Hobbit to collect the values and update the RRD files,
> you
> >   need to either use a script with the --extra-script option to
> >   hobbitd_rrd (such as extras/devmon-rrd.pl) or use the supplied devmon
> >   rrd collector module (extras/do_devmon.c) and the patch (
> >   extras/hobbit-4.2.0-devmon.patch) which adds the collector to
> do_rrd.c."*
> >
> > How do I use the supplied devmon rrd collector module to make Hobbit
> > collect the data?
>
> Xymon now includes this collector module by default. You do not need a
> script,
> and setting if_err=devmon in TEST2RRD is all that is required to "use the
> devmon rrd collector module".
>
> > Do I need to schedule a script which runs this
> > periodically?
>
> No.
>
> Regards,
> Buchan
>

Re: [Devmon] Graphing Interface Errors / Other tests

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

On Friday, 3 December 2010 14:34:22 Mario Valetti wrote:
> Hi,
> 
> I realise my question has previously been posted, but I cannot find an
> answer or guide that gets this working on my installation.
> 
> Basically, I want to graph interface errors (if_err), or discards
> (if_dsc) or something that is monitored in devmon which is not already
> graphed by default (like the if_load, for example).  I've followed the
> documentation on
> http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/docs/GRAPHING, which
> I believe is the latest how-to, but at the moment I don't get .rrd files
> created after completing steps 1 & 2 and restarting  Xymon (adding
> "if_err=devmon" to TEST2RRD in hobbitserver.cfg).
> 
> I'm running XYMON 4.3.0.0-beta2, and DEVMON v0.3.1-beta1.

I believe the devmon collector module crashes in xymon-4.3.0-beta2, please use 
beta3. However ... if you are getting graphs for if_load, then there must be a 
different problem.

> As I'm testing this against a 3750 switch, I have also added
> "TABLE:rrd(DS:ds0:ifInErrors:COUNTER; DS:ds1:ifOutErrors:COUNTER)" to the
> message file of the standard cisco-3750/if_err template as explained in the
> docs.
> 

Do you get an RRD table in the html of the test (e.g. View->Source from your 
browser when viewing the test page for if_err on this device)?

If so, what you have done should be sufficient to generate rrd files. You may 
want to check your rrd-status.log file for any errors.

> I've added graph definitions to the hobbitgraph.cfg file; but even if there
> is an error there it shouldn't prevent the .rrd files been written, as far
> as I understand.
> 
> 
> Last thing...
> I'm not fully understanding the steps (and probably where I'm going wrong:
> * "In order for Hobbit to collect the values and update the RRD files, you
>   need to either use a script with the --extra-script option to
>   hobbitd_rrd (such as extras/devmon-rrd.pl) or use the supplied devmon
>   rrd collector module (extras/do_devmon.c) and the patch (
>   extras/hobbit-4.2.0-devmon.patch) which adds the collector to do_rrd.c."*
> 
> How do I use the supplied devmon rrd collector module to make Hobbit
> collect the data?

Xymon now includes this collector module by default. You do not need a script, 
and setting if_err=devmon in TEST2RRD is all that is required to "use the 
devmon rrd collector module".

> Do I need to schedule a script which runs this
> periodically?

No.

Regards,
Buchan

[Devmon] Graphing Interface Errors / Other tests

[Mario V. <mar...@gm...>]

Hi,

I realise my question has previously been posted, but I cannot find an
answer or guide that gets this working on my installation.

Basically, I want to graph interface errors (if_err), or discards
(if_dsc) or something that is monitored in devmon which is not already
graphed by default (like the if_load, for example).  I've followed the
documentation on
http://devmon.svn.sourceforge.net/viewvc/devmon/trunk/docs/GRAPHING, which I
believe is the latest how-to, but at the moment I don't get .rrd files
created after completing steps 1 & 2 and restarting  Xymon (adding
"if_err=devmon" to TEST2RRD in hobbitserver.cfg).

I'm running XYMON 4.3.0.0-beta2, and DEVMON v0.3.1-beta1.


As I'm testing this against a 3750 switch, I have also added
"TABLE:rrd(DS:ds0:ifInErrors:COUNTER; DS:ds1:ifOutErrors:COUNTER)" to the
message file of the standard cisco-3750/if_err template as explained in the
docs.

I've added graph definitions to the hobbitgraph.cfg file; but even if there
is an error there it shouldn't prevent the .rrd files been written, as far
as I understand.


Last thing...
I'm not fully understanding the steps (and probably where I'm going wrong:
* "In order for Hobbit to collect the values and update the RRD files, you
  need to either use a script with the --extra-script option to
  hobbitd_rrd (such as extras/devmon-rrd.pl) or use the supplied devmon
  rrd collector module (extras/do_devmon.c) and the patch (
  extras/hobbit-4.2.0-devmon.patch) which adds the collector to do_rrd.c."*

How do I use the supplied devmon rrd collector module to make Hobbit collect
the data?  Do I need to schedule a script which runs this periodically?


Mario