devmon-support — General Devmon support

Re: [Devmon] Dell PE R710 and snmp

[psMz <ps...@gm...>]

I resolved this issue last week for vmware guests ,

You have to check the OID number for adpAdapterNumber,
logicalDriveNumber, physAdapterNumber
,
This OID number is store on your "oids" directory template.

And try to received the snmpwalk of this number , if you received the good
information from your SNMP trap so try to edit the "messages" from your
template or simply try to delete 1 of this variable to see whats happening.

Or may be there are a problem when you transform the variable in the
"transform" directory of your template.




Cordialement,
psMz

2015-07-09 9:06 GMT+02:00 Bruce Ferrell <bfe...@ba...>:

> snmpget to the numeric OID fails.
>
> the system is a dell R710 with a PERC 6i
>
> I may need a firmware update and have that in progress
>
>
>
> On 07/08/2015 02:14 PM, Josh Luthman wrote:
> > What happens if you snmpget the OID?
> >
> > Josh Luthman
> > Office: 937-552-2340
> > Direct: 937-552-2343
> > 1100 Wayne St
> > Suite 1337
> > Troy, OH 45373
> > On Jul 8, 2015 4:43 PM, "Bruce Ferrell" <bfe...@ba...> wrote:
> >
> >> I'm getting this this error with devmon.  Any ideas what might be
> missing?
> >>
> >>
> >> Missing repeater data for primary OID adpAdapterNumber
> >> Missing repeater data for primary OID logicalDriveNumber
> >> Missing repeater data for primary OID physAdapterNumber
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Don't Limit Your Business. Reach for the Cloud.
> >> GigeNET's Cloud Solutions provide you with the tools and support that
> >> you need to offload your IT needs and focus on growing your business.
> >> Configured For All Businesses. Start Your Cloud Today.
> >> https://www.gigenetcloud.com/
> >> _______________________________________________
> >> Devmon-support mailing list
> >> Dev...@li...
> >> https://lists.sourceforge.net/lists/listinfo/devmon-support
> >>
> >
> ------------------------------------------------------------------------------
> > Don't Limit Your Business. Reach for the Cloud.
> > GigeNET's Cloud Solutions provide you with the tools and support that
> > you need to offload your IT needs and focus on growing your business.
> > Configured For All Businesses. Start Your Cloud Today.
> > https://www.gigenetcloud.com/
> > _______________________________________________
> > Devmon-support mailing list
> > Dev...@li...
> > https://lists.sourceforge.net/lists/listinfo/devmon-support
> >
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

Re: [Devmon] Dell PE R710 and snmp

[Bruce F. <bfe...@ba...>]

snmpget to the numeric OID fails. 

the system is a dell R710 with a PERC 6i

I may need a firmware update and have that in progress



On 07/08/2015 02:14 PM, Josh Luthman wrote:
> What happens if you snmpget the OID?
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
> On Jul 8, 2015 4:43 PM, "Bruce Ferrell" <bfe...@ba...> wrote:
>
>> I'm getting this this error with devmon.  Any ideas what might be missing?
>>
>>
>> Missing repeater data for primary OID adpAdapterNumber
>> Missing repeater data for primary OID logicalDriveNumber
>> Missing repeater data for primary OID physAdapterNumber
>>
>>
>> ------------------------------------------------------------------------------
>> Don't Limit Your Business. Reach for the Cloud.
>> GigeNET's Cloud Solutions provide you with the tools and support that
>> you need to offload your IT needs and focus on growing your business.
>> Configured For All Businesses. Start Your Cloud Today.
>> https://www.gigenetcloud.com/
>> _______________________________________________
>> Devmon-support mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devmon-support
>>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

Re: [Devmon] Dell PE R710 and snmp

[Ken C. <kco...@ry...>]

Did you verify via cli with snmpwalk or snmget if the leaf or branch is
still valid ?
I've had issues where after upgrading hardware, oids change....



On Wed, Jul 8, 2015 at 4:18 PM, Bruce Ferrell <bfe...@ba...> wrote:

> I'm getting this this error with devmon.  Any ideas what might be missing?
>
>
> Missing repeater data for primary OID adpAdapterNumber
> Missing repeater data for primary OID logicalDriveNumber
> Missing repeater data for primary OID physAdapterNumber
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>



-- 


Ken Connell
Network Engineer
Computer & Communication Services
Ryerson University
350 Victoria St
RM AB50
Toronto, Ont
M5B 2K3
416-979-5000 x6709

Re: [Devmon] Dell PE R710 and snmp

[Josh L. <jo...@im...>]

What happens if you snmpget the OID?

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Jul 8, 2015 4:43 PM, "Bruce Ferrell" <bfe...@ba...> wrote:

> I'm getting this this error with devmon.  Any ideas what might be missing?
>
>
> Missing repeater data for primary OID adpAdapterNumber
> Missing repeater data for primary OID logicalDriveNumber
> Missing repeater data for primary OID physAdapterNumber
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

[Devmon] Dell PE R710 and snmp

[Bruce F. <bfe...@ba...>]

I'm getting this this error with devmon.  Any ideas what might be missing?


Missing repeater data for primary OID adpAdapterNumber
Missing repeater data for primary OID logicalDriveNumber
Missing repeater data for primary OID physAdapterNumber

[Devmon] Note about revision 246

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

In revision 246 transformation PACK is introduced. There is a small error 
in the documentation file TEMPLATES: the words "PACK" and 'UNPACK" are swapped.

Regards,
   Wim Nelis.

Re: [Devmon] APC PDU graph

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

>>> I'm trying to make a template for a PDU to graph power consumption, i have no problems to extract metrics from snmp but graphs doesn't show up and i'm a bit disappointed.
>>> rrd files aren't generated ...
>>>
>>> bin/xymon localhost 'hobbitdlog pdu-b07-02.power'
>>> pdu-b07-02|power|green||1428417135|1428484091|1428485891|0|0|127.0.0.1||||N|
>>> green Wed Apr  8 11:08:08 2015
>>>
>>> PDU status:
>>>
>>> Load A      : 2.70
>>> Load B      : 3.20
>>> Power       : 5.90
>>>
>>> Devmon version 0.3.1-beta1 running on xymon
>>>
>>> TEST2RRD is set with "power=devmon"
>>>
>>
>> If the devmon-format is selected, Xymon expects a header like the following:
>> <!--DEVMON RRD: PduStatus 0 0
>> DS:LoadA:GAUGE:600:0:U DS:LoadB:GAUGE:600:0:UDS:Power:GAUGE:600:0:U
>>
>> You probably mean "power=ncv" in variable TEST2RRD.
>>
>>
> If i follow this : http://sourceforge.net/p/devmon/code/HEAD/tree/trunk/docs/GRAPHING
>
> It talks about devmon-format, why should i use ncv instead is there a difference ?
>
As stated in the article referenced above, the devmon-format is used to 
create graphs of repeater-type OIDs, such as the throughput on all 
interfaces of a switch. The data to extract from the xymon status message 
is encapsulated in a specially formatted HTML comment section. This section 
is generated by Devmon if the "TABLE:rrd" directive is used in the message 
file.

The NCV format is meant to graph a few (non-repeater) values. It expects a 
number of lines in the xymon status message, using the format '<Variable> : 
<Value>' or '<Variable> = <Value>'. Those variables are extracted from the 
message and send to an RRD, assuming that the '<Test>=ncv' is specified in 
TEST2RRD and that a variable named NCV_<Test> is defined in config file 
xymonserver.cfg. As a precaution all the ":" and "=" signs in the status 
message, not belonging to the NCV lines, can be replaced by their HTML 
equivalent.

In your case, I see two options:
  A- you generate the Demon header explicitly in the message file of the 
template
  B- you instruct Xymon to use the NCV format

Case A:

Include in the message file the following 5 lines:

<!-- linecount=1 -->
<!--DEVMON RRD: power 0 0
DS:LoadA:GAUGE:600:0:U DS:LoadB:GAUGE:600:0:U DS:Power:GAUGE:600:0:U
X {LoadA}:{LoadB}:{Power}
-->

The {...} refer to the variables as defined in the transforms file.
This should generate an RRD named "power.X.rrd".

Case B:

Include in file xymonserver.cfg:

TEST2RRD=....,power=ncv
NCV_power="LoadA:GAUGE,LoadB:GAUGE,Power:GAUGE,*:NONE"

This should result in an RRD named "power.rrd".


HTH,
   Wim Nelis.

Re: [Devmon] APC PDU graph

[Thomas <tho...@fu...>]

April 8 2015 12:41 PM, "W.J.M. Nelis"  wrote:
> Hello  Thomas,
> 
> 
>> I'm trying to make a template for a PDU to graph power consumption, i have no problems to extract metrics from snmp but graphs doesn't show up and i'm a bit disappointed.
>> rrd files aren't generated ...
>> 
>> bin/xymon localhost 'hobbitdlog pdu-b07-02.power'
>> pdu-b07-02|power|green||1428417135|1428484091|1428485891|0|0|127.0.0.1||||N|
>> green Wed Apr  8 11:08:08 2015
>> 
>> PDU status:
>> 
>> Load A      : 2.70
>> Load B      : 3.20
>> Power       : 5.90
>> 
>> Devmon version 0.3.1-beta1 running on xymon
>> 
>> TEST2RRD is set with "power=devmon"
>> 
> 
> 
> If the devmon-format is selected, Xymon expects a header like the following:
> <!--DEVMON RRD: PduStatus 0 0
> DS:LoadA:GAUGE:600:0:U DS:LoadB:GAUGE:600:0:UDS:Power:GAUGE:600:0:U
> 
> You probably mean "power=ncv" in variable TEST2RRD.
> 
>

If i follow this : http://sourceforge.net/p/devmon/code/HEAD/tree/trunk/docs/GRAPHING

It talks about devmon-format, why should i use ncv instead is there a difference ?

Thomas

Re: [Devmon] APC PDU graph

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

Hello  Thomas,


> I'm trying to make a template for a PDU to graph power consumption, i have no problems to extract metrics from snmp but graphs doesn't show up and i'm a bit disappointed.
> rrd files aren't generated ...
>
> bin/xymon localhost 'hobbitdlog pdu-b07-02.power'
> pdu-b07-02|power|green||1428417135|1428484091|1428485891|0|0|127.0.0.1||||N|
> green Wed Apr  8 11:08:08 2015
>
> PDU status:
>
> Load A      : 2.70
> Load B      : 3.20
> Power       : 5.90
>
>
> Devmon version 0.3.1-beta1 running on xymon
>
>
>
> TEST2RRD is set with "power=devmon"
>
If the devmon-format is selected, Xymon expects a header like the following:

<!--DEVMON RRD: PduStatus 0 0
DS:LoadA:GAUGE:600:0:U DS:LoadB:GAUGE:600:0:UDS:Power:GAUGE:600:0:U

You probably mean "power=ncv" in variable TEST2RRD.

Regards,
   Wim Nelis.

[Devmon] APC PDU graph

[Thomas <tho...@fu...>]

Hi there,

I'm trying to make a template for a PDU to graph power consumption, i have no problems to extract metrics from snmp but graphs doesn't show up and i'm a bit disappointed.
rrd files aren't generated ...

bin/xymon localhost 'hobbitdlog pdu-b07-02.power'
pdu-b07-02|power|green||1428417135|1428484091|1428485891|0|0|127.0.0.1||||N|
green Wed Apr  8 11:08:08 2015

PDU status:

Load A      : 2.70
Load B      : 3.20
Power       : 5.90


Devmon version 0.3.1-beta1 running on xymon



TEST2RRD is set with "power=devmon"

and my rrd graph template for power is:

[power]
        TITLE Power
        YAXIS Amps
        DEF:LoadA=power.rrd:LoadA:AVERAGE
        DEF:LoadB=power.rrd:LoadB:AVERAGE
        DEF:Power=power.rrd:Power:AVERAGE
        LINE1:i#FF0000:LoadA
        GPRINT:i:LAST:\: %5.1lf (cur)
        GPRINT:i:MAX: \: %5.1lf (max)
        GPRINT:i:MIN: \: %5.1lf (min)
        GPRINT:i:AVERAGE: \: %5.1lf (avg)\n
        LINE1:o#0000FF:LoadB
        GPRINT:o:LAST:\: %5.1lf (cur)
        GPRINT:o:MAX: \: %5.1lf (max)
        GPRINT:o:MIN: \: %5.1lf (min)
        GPRINT:o:AVERAGE: \: %5.1lf (avg)\n
        LINE1:a#008F00:Power
        GPRINT:a:LAST:\: %5.1lf (cur)
        GPRINT:a:MAX: \: %5.1lf (max)
        GPRINT:a:MIN: \: %5.1lf (min)
        GPRINT:a:AVERAGE: \: %5.1lf (avg)\n
        -A

From oids:
rPDULoadStatusLoad1		: .1.3.6.1.4.1.318.1.1.12.2.3.1.1.2.1	: leaf
rPDULoadStatusLoad2		: .1.3.6.1.4.1.318.1.1.12.2.3.1.1.2.2	: leaf
rPDULoadStatusLoad3		: .1.3.6.1.4.1.318.1.1.12.2.3.1.1.2.3	: leaf

And Transforms:
pduLoad1	: MATH : {rPDULoadStatusLoad1} / 10
pduLoad2	: MATH : {rPDULoadStatusLoad2} / 10
pduLoad3	: MATH : {rPDULoadStatusLoad3} / 10


Any idea ?

Thomas

Re: [Devmon] Exclude pots with noalarm in ifAlias

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

Hello Stefan,

> I am looking for a solution where I can exclude interfaces from alerting
> based on the alias description.
>
> exceptions.cfg:
>
> ifName : ignore : Nu.+|Vl.+|VLA
> ifAlias : noalarm : noalarm.+
>
> But this does not seem to work.
> Any idea why this setup does not work?
>

I've solved a similar problem via the script which generates (a part of) 
the xymon hosts.cfg configuration file: it generates a device-specific 
DEVMON-directive, based on the configuration of the device to be tested. In 
your case something like "except(all;ifName;na:<interface-list>)" will be 
needed.

As far as I know, the entries in the exception file can only reference the 
primary OID, that is the OID you use in the leftmost column. If that is 
true, it is not possible to do what you want using the Devmon template only.

Regards,
   Wim Nelis.

Re: [Devmon] Exclude pots with noalarm in ifAlias

[Olivier A. <oli...@co...>]

hello

exceptions

ifAliasBox : ignore : .*nused..ort.*|.*o..onitor.*|.*UnMonitored.*|.*NoMonitor.*

transforms
ifAliasBox      : REGSUB        : {ifAlias} /(\S+.*)/ [$1]/


probably it's ifAliasBox and not ifAlias

oau

On Wed, Mar 04, 2015 at 11:48:01AM +0100, Stefan Coussens wrote:
> Hi,
> 
> I am looking for a solution where I can exclude interfaces from alerting
> based on the alias description.
> 
> exceptions.cfg:
> 
> ifName : ignore : Nu.+|Vl.+|VLA
> ifAlias : noalarm : noalarm.+
> 
> But this does not seem to work.
> Any idea why this setup does not work?
> 
> Kind regards,
> 
> Stefan
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support

[Devmon] Exclude pots with noalarm in ifAlias

[Stefan C. <ste...@gm...>]

Hi,

I am looking for a solution where I can exclude interfaces from alerting
based on the alias description.

exceptions.cfg:

ifName : ignore : Nu.+|Vl.+|VLA
ifAlias : noalarm : noalarm.+

But this does not seem to work.
Any idea why this setup does not work?

Kind regards,

Stefan

Re: [Devmon] Store OID output and associate that with particular devices (transforms)

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

Hello,


> I am very new to devmon, and trying to do bellow and need some help to
> understand
>
> Basically,
>
> Device-A
> snmpwalk -c xxxx-v 2c  Device-A .1.3.6.1.4.1.2620.1.5.6
> SNMPv2-SMI::enterprises.2620.
> 1.5.6.0 = STRING: "active"
>
> Device-B
> snmpwalk -c xxxxx -v 2c  Device-B .1.3.6.1.4.1.2620.1.5.6
> SNMPv2-SMI::enterprises.2620.1.5.6.0 = STRING: "standby"
>
> Template directory :-
>
> messages :
> THIS MEMBER IS {FailoverStatus}
>
> oids :-
> FailoverStatus          : .1.3.6.1.4.1.2620.1.5.6.0     : leaf
>
>
> What I want to do is :
>
> if Device-A become Standby , i want to make it RED ,
> same
> if Device-B become Active, i want to make it RED
>
> the issues, its its same oid for both devices and it string, it does
> not give any integer output.
> how can i transforms it to get my expected output ?
>

What you thus need is a device-dependent threshold. This can be done using 
the 'thresh' directive in the XYMON hosts.cfg file. If you look at the 
document 'using.html', you'll find that the desired result can be achieved 
with something like

     X.X.X.X Device-A  # DEVMON:thresh(YourTest;FailoverStatus;r:standby)
     X.X.X.X Device-B  # DEVMON:thresh(YourTest;FailoverStatus;r:active)

Regards,
   Wim Nelis.

Re: [Devmon] Store OID output and associate that with particular devices (transforms)

[Jeremy L. <jla...@re...>]

Perhaps you could use a transform to construct a string that contains the
device name (from sysName) and the active/standby status.  You'd end up
with something like "Device-A+Standby".  You might do this with a MATH
concatenate (period, ".") transform:

devstate : MATH : {sysName}."+".{FailoverStatus}

Then in your thresholds file, you set your colour accordingly:

devstate : green : Device-A+Active|Device-B+Standby
devstate : red : Device-A+Standby|Device-B+Active


On 21 November 2014 02:02, Fosiul alam <exp...@gm...> wrote:

> Hi
> I am very new to devmon, and trying to do bellow and need some help to
> understand
>
> Basically,
>
> Device-A
> snmpwalk -c xxxx-v 2c  Device-A .1.3.6.1.4.1.2620.1.5.6
> SNMPv2-SMI::enterprises.2620.
> 1.5.6.0 = STRING: "active"
>
> Device-B
> snmpwalk -c xxxxx -v 2c  Device-B .1.3.6.1.4.1.2620.1.5.6
> SNMPv2-SMI::enterprises.2620.1.5.6.0 = STRING: "standby"
>
> Template directory :-
>
> messages :
> THIS MEMBER IS {FailoverStatus}
>
> oids :-
> FailoverStatus          : .1.3.6.1.4.1.2620.1.5.6.0     : leaf
>
>
> What I want to do is :
>
> if Device-A become Standby , i want to make it RED ,
> same
> if Device-B become Active, i want to make it RED
>
> the issues, its its same oid for both devices and it string, it does
> not give any integer output.
> how can i transforms it to get my expected output ?
>
> Thanks for your help.
> Really appreciated
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

Re: [Devmon] Store OID output and associate that with particular devices (transforms)

[Ken C. <kco...@ry...>]

I too have run into this as well (poll result is not an integer), at which
point I end up writing and external script which I just cron and it updates
the xymon display.

I try to use devmon as much as possible for polling, but sometimes there
are special cases in your environment and snmp poll resutls and/or table
builds that don't always line up, so I just script it on the side and pump
the output into xymon.

I currently have over 200 "side scripts" that are special case or devmon
can't deal with.



On Thu, Nov 20, 2014 at 10:02 AM, Fosiul alam <exp...@gm...> wrote:

> Hi
> I am very new to devmon, and trying to do bellow and need some help to
> understand
>
> Basically,
>
> Device-A
> snmpwalk -c xxxx-v 2c  Device-A .1.3.6.1.4.1.2620.1.5.6
> SNMPv2-SMI::enterprises.2620.
> 1.5.6.0 = STRING: "active"
>
> Device-B
> snmpwalk -c xxxxx -v 2c  Device-B .1.3.6.1.4.1.2620.1.5.6
> SNMPv2-SMI::enterprises.2620.1.5.6.0 = STRING: "standby"
>
> Template directory :-
>
> messages :
> THIS MEMBER IS {FailoverStatus}
>
> oids :-
> FailoverStatus          : .1.3.6.1.4.1.2620.1.5.6.0     : leaf
>
>
> What I want to do is :
>
> if Device-A become Standby , i want to make it RED ,
> same
> if Device-B become Active, i want to make it RED
>
> the issues, its its same oid for both devices and it string, it does
> not give any integer output.
> how can i transforms it to get my expected output ?
>
> Thanks for your help.
> Really appreciated
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>



-- 


Ken Connell
Network Engineer
Computer & Communication Services
Ryerson University
350 Victoria St
RM AB50
Toronto, Ont
M5B 2K3
416-979-5000 x6709

[Devmon] Store OID output and associate that with particular devices (transforms)

[Fosiul a. <exp...@gm...>]

Hi
I am very new to devmon, and trying to do bellow and need some help to
understand

Basically,

Device-A
snmpwalk -c xxxx-v 2c  Device-A .1.3.6.1.4.1.2620.1.5.6
SNMPv2-SMI::enterprises.2620.
1.5.6.0 = STRING: "active"

Device-B
snmpwalk -c xxxxx -v 2c  Device-B .1.3.6.1.4.1.2620.1.5.6
SNMPv2-SMI::enterprises.2620.1.5.6.0 = STRING: "standby"

Template directory :-

messages :
THIS MEMBER IS {FailoverStatus}

oids :-
FailoverStatus          : .1.3.6.1.4.1.2620.1.5.6.0     : leaf


What I want to do is :

if Device-A become Standby , i want to make it RED ,
same
if Device-B become Active, i want to make it RED

the issues, its its same oid for both devices and it string, it does
not give any integer output.
how can i transforms it to get my expected output ?

Thanks for your help.
Really appreciated

Re: [Devmon] [Xymon] devmon mysterious behaviour

[Jeremy L. <jla...@re...>]

I seem to recall a problem on 64-bit platforms where 64-bit SNMP request
IDs were being rejected by libsnmp because it parsed them as 32-bit IDs,
but only if the values were large enough.  In this situation, I was able to
probe the OIDs just fine using snmpget, but devmon failed to get the
responses, but only sometimes.  Comparing packet captures of failures and
successes showed the problem.

A previously posted thread might be of some assistance:

http://sourceforge.net/p/devmon/mailman/message/30148661/

Re: [Devmon] devmon mysterious behaviour

[Becker C. <chr...@rh...>]

Hello Ryan,

hm, i should have thought about this by myself already.

Your description regarding the concurrent snmp polls sounds reasonable to me. I'll give this a try over the weekend and deactivate devmon in the "old" environment, so that I have devmon activated in the "new" environment only.
The issue with the lib paths and sym links is OK since devmon is running in general; further, the "old" environment is 64 Bit too.

Thank so far!

Regards

Christian Becker
IT-Services

Chr...@rh...
_________________________________
Mittelrhein-Verlag GmbH
August-Horch-Straße 28
D-56070 Koblenz
Verleger und Geschäftsführer: Walterpeter Twer
Reg.-Gericht Koblenz HRB 121
Finanzamt Koblenz Str.Nr. 22 65 10 285 2
www.rhein-zeitung.de

-----Ursprüngliche Nachricht-----
Von: Ryan Rush [mailto:rya...@gm...] 
Gesendet: Freitag, 31. Oktober 2014 09:16
An: dev...@li...
Cc: xy...@xy...
Betreff: Re: [Devmon] devmon mysterious behaviour

Are there any concurrent snmp polls running? I have noticed that when testing, older Cisco hardware will queue new walks when one is running. If the runtime if the current poll exceeds timeout on the new poll, one might experience the symptoms you are describing.

Verify no other polls are occurring, then check your lib paths. I have experienced issues when migrating older code to 64 bit Linux systems, and resolved the problems with sym links after reviewing debugs.
On Oct 31, 2014 1:05 AM, "Becker Christian" < chr...@rh...> wrote:

> Hello folks,
>
> we are running a Xymon 4.3.11 environment that persists of a server 
> running Red Hat Enterprise Linux 6.1 64 Bit. This setup also includes 
> devmon (0.3.1-beta1). In this environment, devmon works like a charm.
>
> Now we are in the situation to go away from Red Hat Enterprise Linux 
> and go ahead to Ubuntu 14.0.4.1 LTS 64 Bit. This is an internal decision.
> On this new environment I have set up Xymon 4.3.17, including devmon, 
> which is the same release as in our "old" environment.
>
> But here, I have mysterious problem, for which I cannot find an
> explanation:
> In the "old" environment, there is a Cisco 6506, that is "asked" by devmon.
> For any reason, in this environment devmon doesn't get any data out of 
> this Cisco device. It says "Missing repeater data for primary OID #######"
> (the "#######" is just an example....).
>
> The mysterious thing now is, that in the "new" environment, devmon 
> (some
> times...) extracts data out of this Cisco device, but -and this is the 
> most confusing thing- every now and then it is changing from "purple" to "clear"
> (again saying "Missing repeater data for primary OID ####### ".), and 
> on any time it changes back to "green" containing current data.
>
> The devmon logfile doesn't seem to contain any hint on this situation.
>
> I have really no idea why this could happen.
>
> Does anybody of you have an idea about this behavior?
>
> Greetings
> Christian
>
> Christian Becker
> IT-Services
>
> Chr...@rh...<mailto:
> Chr...@rh...>
> _________________________________
> Mittelrhein-Verlag GmbH
> August-Horch-Straße 28
> D-56070 Koblenz
> Verleger und Geschäftsführer: Walterpeter Twer Reg.-Gericht Koblenz 
> HRB 121 Finanzamt Koblenz Str.Nr. 22 65 10 285 2 
> www.rhein-zeitung.de<http://www.rhein-zeitung.de/>
>
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
------------------------------------------------------------------------------
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support

Re: [Devmon] devmon mysterious behaviour

[Ryan R. <rya...@gm...>]

Are there any concurrent snmp polls running? I have noticed that when
testing, older Cisco hardware will queue new walks when one is running. If
the runtime if the current poll exceeds timeout on the new poll, one might
experience the symptoms you are describing.

Verify no other polls are occurring, then check your lib paths. I have
experienced issues when migrating older code to 64 bit Linux systems, and
resolved the problems with sym links after reviewing debugs.
On Oct 31, 2014 1:05 AM, "Becker Christian" <
chr...@rh...> wrote:

> Hello folks,
>
> we are running a Xymon 4.3.11 environment that persists of a server
> running Red Hat Enterprise Linux 6.1 64 Bit. This setup also includes
> devmon (0.3.1-beta1). In this environment, devmon works like a charm.
>
> Now we are in the situation to go away from Red Hat Enterprise Linux and
> go ahead to Ubuntu 14.0.4.1 LTS 64 Bit. This is an internal decision.
> On this new environment I have set up Xymon 4.3.17, including devmon,
> which is the same release as in our "old" environment.
>
> But here, I have mysterious problem, for which I cannot find an
> explanation:
> In the "old" environment, there is a Cisco 6506, that is "asked" by devmon.
> For any reason, in this environment devmon doesn't get any data out of
> this Cisco device. It says "Missing repeater data for primary OID #######"
> (the "#######" is just an example....).
>
> The mysterious thing now is, that in the "new" environment, devmon (some
> times...) extracts data out of this Cisco device, but -and this is the most
> confusing thing- every now and then it is changing from "purple" to "clear"
> (again saying "Missing repeater data for primary OID ####### ".), and on
> any time it changes back to "green" containing current data.
>
> The devmon logfile doesn't seem to contain any hint on this situation.
>
> I have really no idea why this could happen.
>
> Does anybody of you have an idea about this behavior?
>
> Greetings
> Christian
>
> Christian Becker
> IT-Services
>
> Chr...@rh...<mailto:
> Chr...@rh...>
> _________________________________
> Mittelrhein-Verlag GmbH
> August-Horch-Straße 28
> D-56070 Koblenz
> Verleger und Geschäftsführer: Walterpeter Twer
> Reg.-Gericht Koblenz HRB 121
> Finanzamt Koblenz Str.Nr. 22 65 10 285 2
> www.rhein-zeitung.de<http://www.rhein-zeitung.de/>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

[Devmon] devmon mysterious behaviour

[Becker C. <chr...@rh...>]

Hello folks,

we are running a Xymon 4.3.11 environment that persists of a server running Red Hat Enterprise Linux 6.1 64 Bit. This setup also includes devmon (0.3.1-beta1). In this environment, devmon works like a charm.

Now we are in the situation to go away from Red Hat Enterprise Linux and go ahead to Ubuntu 14.0.4.1 LTS 64 Bit. This is an internal decision.
On this new environment I have set up Xymon 4.3.17, including devmon, which is the same release as in our "old" environment.

But here, I have mysterious problem, for which I cannot find an explanation:
In the "old" environment, there is a Cisco 6506, that is "asked" by devmon.
For any reason, in this environment devmon doesn't get any data out of this Cisco device. It says "Missing repeater data for primary OID #######" (the "#######" is just an example....).

The mysterious thing now is, that in the "new" environment, devmon (some times...) extracts data out of this Cisco device, but -and this is the most confusing thing- every now and then it is changing from "purple" to "clear" (again saying "Missing repeater data for primary OID ####### ".), and on any time it changes back to "green" containing current data.

The devmon logfile doesn't seem to contain any hint on this situation.

I have really no idea why this could happen.

Does anybody of you have an idea about this behavior?

Greetings
Christian

Christian Becker
IT-Services

Chr...@rh...<mailto:Chr...@rh...>
_________________________________
Mittelrhein-Verlag GmbH
August-Horch-Straße 28
D-56070 Koblenz
Verleger und Geschäftsführer: Walterpeter Twer
Reg.-Gericht Koblenz HRB 121
Finanzamt Koblenz Str.Nr. 22 65 10 285 2
www.rhein-zeitung.de<http://www.rhein-zeitung.de/>

Re: [Devmon] Due to PCI 3.0 requirements starting in 2015 we will not be able to use SNMP v1 or SNMP v2

[Jeremy L. <jla...@re...>]

What about tunneling through ssh?  Would that comply with PCI
requirements?  One way to do this would be to have devmon run on each
client, configured to probe 127.0.0.1, and report its results through the
tunnel.  Strictly speaking, you're not tunneling the SNMP probe, instead
you're tunneling the back-end BigBrother protocol that reports to Xymon.

You could either establish a persistent tunnel (a la xymon-tunnel.sh <
https://wiki.xymonton.org/doku.php/addons:ssh_tunnel>) or execute a
slightly modified devmon via an ssh command - modified to run once only (by
changing the "while(1)" into an "if(1)", for example).

This is a little bit messy, having to have devmon and its templates
installed everywhere, but probably a lot easier than trying to splice in
support for SNMPv3.

J


On 14 October 2014 00:03, Johan Sjöberg <Joh...@de...>
wrote:

> This is something that we will probably also need, as we are currently
> implementing PCI DSS in our environment.
> Is there anyone still working on devmon development?
>
> /Johan
>
> -----Original Message-----
> From: Mark Mulligan [mailto:MMu...@ll...]
> Sent: den 1 augusti 2014 19:37
> To: dev...@li...
> Subject: [Devmon] Due to PCI 3.0 requirements starting in 2015 we will not
> be able to use SNMP v1 or SNMP v2
>
> Are there any plans to upgrade devmon to snmp v3?
>
> Thanks,
>
> Mark Mulligan
> Associate Operations Engineer - Splunk and Xymon Admin P Please do not
> print this e-mail unless necessary
>
>
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck Code
> Sight - the same software that powers the world's largest code search on
> Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>

Re: [Devmon] Due to PCI 3.0 requirements starting in 2015 we will not be able to use SNMP v1 or SNMP v2

[Johan S. <Joh...@de...>]

This is something that we will probably also need, as we are currently implementing PCI DSS in our environment.
Is there anyone still working on devmon development?

/Johan

-----Original Message-----
From: Mark Mulligan [mailto:MMu...@ll...] 
Sent: den 1 augusti 2014 19:37
To: dev...@li...
Subject: [Devmon] Due to PCI 3.0 requirements starting in 2015 we will not be able to use SNMP v1 or SNMP v2

Are there any plans to upgrade devmon to snmp v3?

Thanks,

Mark Mulligan
Associate Operations Engineer - Splunk and Xymon Admin P Please do not print this e-mail unless necessary




------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support

Re: [Devmon] Changing the if_load graphs displayed on Xymon

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

Hello,

>> I am using a patch to Devmon to solve this problem. It changes the
>> name of the interfaced part of the RRD file name. This causes the
>> alphabetical order to be the same as the numerical order. There is a
>> drawback however. For some of the interfaces the RRD file name
>> changes, causing new files to be generated once the patch is
>> applied. If you do not want to loose the history, you need to save /
>> restore / move those files. Anyway, you need to remove the RRD files
>> with the unsed interface names in it, as they will mesh up the
>> graphs on the Xymon page.
>>
>> The patch itself is:
>>
>> Index: dm_tests.pm
>> ===================================================================
>> --- dm_tests.pm	(revision 13)
>> +++ dm_tests.pm	(revision 14)
>> @@ -2022,6 +2022,11 @@
>>              for my $leaf (@{$rrd{$name}{'leaves'}}) {
>>                my $pri_val = $oids->{$pri}{'val'}{$leaf};
>>                $pri_val =~ s/\s*//g;
>> +  #
>> +  # Map Cisco interface names like "Fa1/0/1" onto "Fa1/0/01". This
>> will cause a
>> +  # nicer order of the graphs in the trends column in Xymon.
>> +  #
>> +            if ( $pri_val =~
>> m/^(Fa\d\/|Fa\d\/\d\/|Gi\d\/\d\/|Gi\d\/|Po)(\d)$/ ) {
>> +              $pri_val = $1 . '0' . $2 ;
>> +            } elsif ( $pri_val =~ m/^(Vl)(\d{1,3})$/ ) {
>> +              $pri_val = $1 . substr( '000' . $2, -4, 4 ) ;
>> +            }  # of elsif
>
> If this is the approach everyone wants, this needs at least Te, and possibly longer prefixes that can be used (if the device is configured for long names) such as GigabitEthernet, TegGigE etc.
How about extending patch #27, "Add TABLE:sort option" to apply the same 
transformations to the RRD file names? That approach would make the code of 
Devmon independent of the devices being used. However, the line above using 
function substr is harder to catch in a s/// substitution.

Regards,
   Wim Nelis.

Re: [Devmon] Changing the if_load graphs displayed on Xymon

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

----- Original Message -----
> Hello Martin,
> 
> > Perhaps I'm just being lazy, but I'm looking for a way of changing
> > how the
> > default if_load graphs are displayed on Xymon/Devmon.
> >
> > Xymon version is 4.3.12
> > Devmon version is 0.3.1-beta1
> >
> > What I want is for the graphs to be displayed in interface or
> > numerical
> > order, but, out of the box, Devmon and Xymon display the graphs
> > sorted in
> > alphabetical order.
> >
> > Normally this is not an issue, but it is slightly tedious to have
> > to scroll
> > through the graph for interface Gi0/1 then through Gi0/10, Gi0/11,
> > Gi0/12,
> > Gi0/13, Gi0/14, Gi0/15, Gi0/16, Gi0/17, Gi0/18 and Gi0/19 graphs to
> > eventually get to Gi0/2.  is there not a way to either adjust the
> > interface
> > so it reads Gi0/01, Gi0/02 etc or a flag to 'sort numerically'?


But then you are introducing an inconsistency between the device and the graph name. I have for example considered putting the cdp test in a database and using it to make generation of a weathermap config (BTW., I use weathermap, among other things, to avoid having to scroll through lots of interface graphs to get to the one I want).

Wouldn't it be better to log a feature request for Xymon to split RRD names on character/numeric boundaries and sort within the boundary?

> I am using a patch to Devmon to solve this problem. It changes the
> name of the interfaced part of the RRD file name. This causes the
> alphabetical order to be the same as the numerical order. There is a
> drawback however. For some of the interfaces the RRD file name
> changes, causing new files to be generated once the patch is
> applied. If you do not want to loose the history, you need to save /
> restore / move those files. Anyway, you need to remove the RRD files
> with the unsed interface names in it, as they will mesh up the
> graphs on the Xymon page.
> 
> The patch itself is:
> 
> Index: dm_tests.pm
> ===================================================================
> --- dm_tests.pm	(revision 13)
> +++ dm_tests.pm	(revision 14)
> @@ -2022,6 +2022,11 @@
>             for my $leaf (@{$rrd{$name}{'leaves'}}) {
>               my $pri_val = $oids->{$pri}{'val'}{$leaf};
>               $pri_val =~ s/\s*//g;
> +  #
> +  # Map Cisco interface names like "Fa1/0/1" onto "Fa1/0/01". This
> will cause a
> +  # nicer order of the graphs in the trends column in Xymon.
> +  #
> +            if ( $pri_val =~
> m/^(Fa\d\/|Fa\d\/\d\/|Gi\d\/\d\/|Gi\d\/|Po)(\d)$/ ) {
> +              $pri_val = $1 . '0' . $2 ;
> +            } elsif ( $pri_val =~ m/^(Vl)(\d{1,3})$/ ) {
> +              $pri_val = $1 . substr( '000' . $2, -4, 4 ) ;
> +            }  # of elsif


If this is the approach everyone wants, this needs at least Te, and possibly longer prefixes that can be used (if the device is configured for long names) such as GigabitEthernet, TegGigE etc.

Regards,
Buchan