Xymon Mailing List Archive search

Devmon causing core dumps

list Robert Holden
Fri, 31 Oct 2008 10:55:35 -0700
Message-Id: <user-43a3d88e9ac7@xymon.invalid>

When I run snmpwalk on my interfaces I get the following:
(I believe that the devmon template is using this ... notice that they are
all the same.  A transform won't help)
IF-MIB::ifName.70 = STRING: AT5/0/0
IF-MIB::ifName.71 = STRING: AT5/0/0
IF-MIB::ifName.72 = STRING: AT5/0/0
IF-MIB::ifName.73 = STRING: AT5/0/0
IF-MIB::ifName.74 = STRING: AT5/0/0

(This could be used, but you would end up w/ very long names.  G0/0 would
become GigabitEthernet0/0)
IF-MIB::ifDescr.70 = STRING: ATM5/0/0
IF-MIB::ifDescr.71 = STRING: ATM5/0/0-atm layer
IF-MIB::ifDescr.72 = STRING: ATM5/0/0.0-atm subif
IF-MIB::ifDescr.73 = STRING: ATM5/0/0-aal5 layer
IF-MIB::ifDescr.74 = STRING: ATM5/0/0.0-aal5 layer

(This may be helpful ... somehow ignore all type 37 and type 49, and sub
interface 0 ??)
IF-MIB::ifType.70 = INTEGER: sonet(39)
IF-MIB::ifType.71 = INTEGER: atm(37)
IF-MIB::ifType.72 = INTEGER: atmSubInterface(134)
IF-MIB::ifType.73 = INTEGER: aal5(49)
IF-MIB::ifType.74 = INTEGER: aal5(49)

I will open a bug if you like.  Is the issue that originated this thread the
same as the one I am experiencing?

Robert

On Fri, Oct 31, 2008 at 9:19 AM, Buchan Milne <user-9b139aff4dec@xymon.invalid>wrote:
On Friday 31 October 2008 17:35:44 Robert Holden wrote:
I have seen this as well.  I finally determined it was caused by ATM
interfaces.  Devmon does not give different components of an ATM circuit
(the physical interface, the -atm layer, .0 sub interface, -aal5 layer)
unique names.  So rrd was receiving data for 5 interfaces all with the
same
name.  As a temporary interface, I stopped monitoring the atm interfaces,
but this is a bug.

Interface names:
ATM5/0/0
ATM5/0/0-atm layer
ATM5/0/0.0-atm subif
ATM5/0/0-aal5 layer
ATM5/0/0.0-aal5 layer
It's the spaces in the interface names.
Devmon sees these all as: ATM5/0/0  because devmon templates (atleast for
6509's) are looking at ifName as the main identifier, which is not always
unique.
No, on earlier IOSs, there will still many interface names for ATM
interfaces,
but there were no spaces in the names. I have adjusted my template in this
case as follows to avoid the problem with spaces:

in transforms:

ifNameFixed     : REGSUB        : {ifName} /(\S+)(\s*)?(\S+)$/$1$3/

then replace ifName with ifNameFixed in the message file.
Not sure on a solution yet.  MRTG uses ifIndex as it's unique key.
Well, this is not the issue, but using ifIndex is not a solution either.

(BTW, there isn't a bug filed on this issue, so so far I've just been
wanting
to fix this for my own setup ...)

Regards,
Buchan