Xymon Mailing List Archive search

Plan for XYMON and SNMP

list Jeremy Laidman
Sun, 23 Jun 2019 01:54:53 +1000
Message-Id: <CACO=user-df8516be58b3@xymon.invalid>

Great news.

Do you think the typo in the snmpmibs.cfg was causing no RRD files to be
generated?


On Sun, 23 Jun 2019 at 01:47, Bruce Ferrell <user-24fbf1912cfe@xymon.invalid> wrote:

Hi Jeremy,

Yes, you're correct, the snmpmibs.cfg is an excerpt. It does have the
[systemmib] section and that part executes correctly (or seems to) so I
left that out.  The debug output does have the opening snmpmibs part.  That
shows all of the sections and it's rather lengthy,  I did not note errors
there.

I've now corrected the error you noted and commented out everything I'm
not using in snmpmibs.cfg (should have done that before)...

And I'm now getting columns in the display and RRDs!

I. AM. STOKED!

Now to get the charts working.  Once I get that working (some year) I'll
write my notes up and submit them as semi-documentation for the feature.

Thanks for the help!


On 6/22/19 7:01 AM, Jeremy Laidman wrote:

Bruce

Firstly, just to make sure the snmpmibs.cfg you showed is only an excerpt,
right? Your snmphosts.cfg file references systemmib and so snmpmibs.cfg
must have a [systemmib] section. Your debug output should be saying
"Opening file /home/xymon/server/etc/snmpmibs.cfg" but it's not, so I'm
hoping you're providing an abridged version of the output.

Secondly, I believe there's an error in the snmpmibs.cfg file in the
[hrstorage] section. I don't know if this will affect your situation given
that your snmphosts.cfg does not reference hrstorage, and your manual run
of xymon-snmpcollect does not show any errors along these lines.

Anyhow, for the record, I believe this line:

        keyidx [(HOST-RESOURCES-MIB::hrStorageType]

is supposed to be:

        keyidx [HOST-RESOURCES-MIB::hrStorageType]

In the first form, the opening parenthesis has no matching closing
parenthesis and I believe it's an extra character that should be removed.

Having said all this, your debug output seems to be sending something into
Xymon without any problem reported, so the problem may be further down the
chain.

The xymon-snmpcollect process creates a supplemental client data message
to report its findings to Xymon, so have a look at the client data for your
host and see if there's an [ifmib] section and that it looks reasonable.

The SNMP client data is parsed by xymond - so check xymond.log for errors.

From the parsed client data, xymond creates a status message of the form
"status hostname.mibname color timestamp <summary>" such as "status
hostname.org.ifmib green Sat Jun 22 21:20:19 2019 bla bla". You could use
xymond_channel to tap into the status message stream and confirm that
there's a status message being generated. You should also see an "ifmib"
test appear on the Xymon page containing the hostname.

If a status message is generated, it gets picked up by xymond_rrd. If the
message is malformed, you might find a message explaining why in the
rrd_status.log file. The status message has a particular format so that the
RRD parser can turn the text and numbers into RRD data. It should have
"Interval=N" (N is likely 300), and "ActiveIP=<IP address>". Then it will
have a series of VAR=VAL lines, possibly in sections denoted by square
brackets. In the case of the ifmib, the sections are the interface names,
and the VAR=VAL lines contain things like ifOctets=NNNNN and
ifOperStatus=up (and all the things in the [ifmib] section of the
snmpmibs.cfg file.

Cheers
Jeremy

On Sat, 22 Jun 2019 at 14:38, Bruce Ferrell <user-24fbf1912cfe@xymon.invalid> wrote:

As a follow on...

using tcpdump and snmpget against the data in the dump shows the counters
ARE being retrieved, just not registering.

snmpget -v 2c -c community666name 127.0.0.1 .1.3.6.1.2.1.31.1.1.1.3.4 -Oa

IF-MIB::ifInBroadcastPkts.4 = Counter32: 0

tcpdump was run while hand running xymoln-snmpcollect


On 6/21/19 9:24 PM, Bruce Ferrell wrote:
OK, I have bug on this now... I have had off an on for a while now

I have one host in my network NOT being monitored by devmon and I'm
trying to use the built in snmp of xymon

snmphosts.cfg:

[hostname.org]
  version=2
  community=community666name
  ip=127.0.0.1
  systemmib
  ifmib=(*)

snmpmibs.cfg is the file from 4.2.28

[ifmib]
        keyidx (IF-MIB::ifDescr)
        keyidx [IF-MIB::ifPhysAddress]
        keyidx <IF-MIB::ifName>
        validx {IP-MIB::ipAdEntIfIndex}
        ifDescr = IF-MIB::ifDescr
        ifType = IF-MIB::ifType
        ifMtu = IF-MIB::ifMtu
        ifSpeed = IF-MIB::ifSpeed
        ifPhysAddress = IF-MIB::ifPhysAddress
        ifAdminStatus = IF-MIB::ifAdminStatus
        ifOperStatus = IF-MIB::ifOperStatus
        ifLastChange = IF-MIB::ifLastChange
        ifInOctets = IF-MIB::ifInOctets
/rrd:COUNTER
        ifInUcastPkts = IF-MIB::ifInUcastPkts
/rrd:COUNTER
        ifInNUcastPkts = IF-MIB::ifInNUcastPkts
/rrd:COUNTER
        ifInDiscards = IF-MIB::ifInDiscards
/rrd:COUNTER
        ifInErrors = IF-MIB::ifInErrors
/rrd:COUNTER
        ifInUnknownProtos = IF-MIB::ifInUnknownProtos
/rrd:COUNTER
        ifOutOctets = IF-MIB::ifOutOctets
/rrd:COUNTER
        ifOutUcastPkts = IF-MIB::ifOutUcastPkts
/rrd:COUNTER
        ifOutNUcastPkts = IF-MIB::ifOutNUcastPkts
/rrd:COUNTER
        ifOutDiscards = IF-MIB::ifOutDiscards
/rrd:COUNTER
        ifOutErrors = IF-MIB::ifOutErrors
/rrd:COUNTER
        ifOutQLen = IF-MIB::ifOutQLen
/rrd:GAUGE
Run by hand as follows:

 ./server/bin/xymon-snmpcollect --debug

26951 2019-06-21 21:12:36.952110 Opening file
/home/xymon/server/etc/snmphosts.cfg
26951 2019-06-21 21:12:36.953150 Got key-oid '.1.3.6.1.2.1.2.2.1.2.1' =
'"lo"'
26951 2019-06-21 21:12:36.953381 Got key-oid '.1.3.6.1.2.1.2.2.1.2.2' =
'"em1"'
26951 2019-06-21 21:12:36.953629 Got key-oid '.1.3.6.1.2.1.2.2.1.2.3' =
'"em2"'
26951 2019-06-21 21:12:36.953844 Got key-oid '.1.3.6.1.2.1.2.2.1.2.4' =
'"em3"'
26951 2019-06-21 21:12:36.954081 Got key-oid '.1.3.6.1.2.1.2.2.1.2.5' =
'"em4"'
26951 2019-06-21 21:12:36.954303 Got key-oid '.1.3.6.1.2.1.2.2.1.2.6' =
'"br0"'
26951 2019-06-21 21:12:36.954519 Got key-oid '.1.3.6.1.2.1.2.2.1.2.7' =
'"docker0"'
26951 2019-06-21 21:12:36.954737 Finished host hostname.org
26951 2019-06-21 21:12:36.966129 No more oids left
26951 2019-06-21 21:12:36.966137 Finished host hostname.org
26951 2019-06-21 21:12:36.966258 Transport setup is:
26951 2019-06-21 21:12:36.966269 xymondportnumber = 1984
26951 2019-06-21 21:12:36.966274 xymonproxyhost = NONE
26951 2019-06-21 21:12:36.966278 xymonproxyport = 0
26951 2019-06-21 21:12:36.966282 Recipient listed as 'XYMON_HOST'
26951 2019-06-21 21:12:36.966287 Standard protocol on port 1984
26951 2019-06-21 21:12:36.966292 Will connect to address XYMON_HOST
port 1984
26951 2019-06-21 21:12:36.966463 Connect status is 0
26951 2019-06-21 21:12:36.966551 Sent 7650 bytes
26951 2019-06-21 21:12:36.966588 Closing connection

I get the interface names, but no counters and as a result no RRD
entries,and of course, no charting.

What I want it to do is collect the stats for all of the interfaces and
then chart them.  I'm suspecting the ifmib definition isn't right if not
that, the maybe I need to do
something different with snmphosts.cfg

Thoughts?


On 5/17/19 2:04 PM, Jeremy Laidman wrote:
For me, yes.


On Fri, 17 May 2019, 17:59 Japheth Cleaver, <user-87556346d4af@xymon.invalid
<mailto:user-87556346d4af@xymon.invalid>> wrote:
     Other than documentation (obviously), would that be the primary
feature
     set that helps makes this a reasonable thing to integrate in
officially?

     -jc

     On 5/16/2019 11:08 PM, Bruce Ferrell wrote:
I just figured out there has to be a task... At first I
wondered how
xymonnet launched xymon-snmpcollector, then I started running
it by
hand and running tcpdump to see what was being polled

What it looks like what we don't get is mib variable
manipulation ala
devmon... calculated load percentages etc.

Still I think a move in the right direction and it directly
supports
snmp v3


On 5/16/19 10:45 PM, Jeremy Laidman wrote:
Not sure what that will give you. The OIDs are extracted from
the
file snmpmibs.conf, and I expect you'll have to populate that
with
anything you want to monitor.

One thing I forgot to mention is that you need to create a
task to
run the xymon-snmpcollect program every 5 minutes. I created a
tasks.d/xymon-snmpcollect.cfg file containing the following:

[snmpcollect]
        ENVFILE $XYMONHOME/etc/xymonserver.cfg
        CMD $XYMONHOME/ext/xymon-snmpcollect --debug
        LOGFILE $XYMONSERVERLOGS/xymon-snmpcollect.log
        INTERVAL 5m

Obviously the --debug flag can be removed.

On Fri, 17 May 2019 at 15:26, Bruce Ferrell <
user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid>
wrote:

    Just thinking aloud... Since the build uses net-snmp, it
should
use the same mibs net-snmp uses... So xymon will know about my
SmartUPS and poweredge.

    I'm gonna have to study the code some more


      On 5/16/19 10:08 PM, Jeremy Laidman wrote:
Right you are. DOSNMP is set to "yes" as a result of
SNMP being
set to 1 (and the Net-SNMP tools being found).

On Fri, 17 May 2019 at 14:42, Bruce Ferrell
<user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid> <mailto:
user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid>>
<mailto:user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid>>>> wrote:
    On 5/16/19 9:10 PM, Jeremy Laidman wrote:
On Fri, 17 May 2019 at 13:36, Bruce Ferrell
<user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid> <mailto:
user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid>>
user-24fbf1912cfe@xymon.invalid> <mailto:user-24fbf1912cfe@xymon.invalid <mailto:
user-24fbf1912cfe@xymon.invalid>>
<mailto:user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid>>>>> wrote:
    Yes, I did Jeremy.  My apologies.


No problem.

    I did figure out I have to export SNMP=1 then
configure and rebuild


Ah, I didn't know that. Or I forgot that.

Just looking at the code now - are you sure this
isn't
"DOSNMP=1"?

    The Makefile tests for if  $SNMP=1... At least in
4.3.28
    What is the tag in the hosts file (if any)?


Nothing. The hostnames are found by
xymon-snmpcollect in
the snmphosts.cfg. You still need the hosts to be in
hosts.cfg, but
not tags are required.
Jeremy
    Thanks again!


    On 5/16/19 6:41 PM, Jeremy Laidman wrote:
If you meant to say, "Hey Jeremy" then the
answer
is, that it's all stuff for Xymon.

On Fri, 17 May 2019 at 11:15, Bruce Ferrell
<user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid> <mailto:
user-24fbf1912cfe@xymon.invalid <mailto:user-24fbf1912cfe@xymon.invalid>>
user-24fbf1912cfe@xymon.invalid> <mailto:user-24fbf1912cfe@xymon.invalid <mailto:
user-24fbf1912cfe@xymon.invalid>>
user-24fbf1912cfe@xymon.invalid>
user-24fbf1912cfe@xymon.invalid>> <mailto:user-24fbf1912cfe@xymon.invalid <mailto:
user-24fbf1912cfe@xymon.invalid>
wrote:
    Hey Josh, I saw that before.  Is that
stuff
that devmon looks at or stuff for xymon.

    I'm not at all clear

    Thanks in advance

    On 5/16/19 6:00 PM, Jeremy Laidman wrote:
    Xymon already has code for SNMP that
works,
but isn't documented. I have it working for me, but it
required a
fair bit or digging to find the right
    configuration. I've
    posted on this previously; might help:
https://lists.xymon.com/archive/2019-March/046191.html
    J

    On Thu, 16 May 2019 at 19:26, Bruno
Manzoni
<user-81df5df13c04@xymon.invalid <mailto:
user-81df5df13c04@xymon.invalid> <mailto:user-81df5df13c04@xymon.invalid
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>>>> wrote:
        Thanks you Josh,

        Yes I know about devmon (I put my
own
devmon version which is a try to be a consolidate version)

        In fact, I just would like to know
if
there was another SNMP development (but it seems not as you
say it
will be merged) inside Xymon . (I am thinking
    a way to
    integrate
        SNMP v3, but it do not uses the
current
SNMP_session perl lib as it is not supported within this lib)?
        Regards

        Bruno Manzoni
        (Bonomani)


        Le 14.05.2019 à 15:20, Josh Luthman
a écrit :
        You can just use Devmon these days.

        I've seen nothing to suggest the
projects
will be merged.

        Josh Luthman
        Office: XXX-XXX-XXXX
        Direct: XXX-XXX-XXXX
        XXXX Wayne St
        Suite XXXX
        Troy, OH XXXXX


        On Fri, May 10, 2019 at 12:33 PM
Bruno
Manzoni <user-81df5df13c04@xymon.invalid <mailto:
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>
user-81df5df13c04@xymon.invalid>
user-81df5df13c04@xymon.invalid>>>>>> wrote:
 Hello,

            Is there any plan to have SNMP
include with a new version of xymon? If
 yes, what is the current state?