Can't resolve Ascend traps. Who's wrong Ascend or tkined?

Marc MERLIN (marc.merlin@magic.metawire.com)
Thu, 22 May 1997 17:19:27 -0700 (PDT)

> There are plenty of people using Scotty successfully under
> Linux. I'm not among them ... Installation can be a bit
> delicate the first time. What's your situation (how far
> along in installation are you), and what symptoms do you
> see?

sorry, I waited a little bit before answering as I wanted to gather more
info.

Tkined seems to be working.
According to someone else, I can ignore the following message:
straps: unable to bind multicast trap socket: Address already in use

(I'm still curious to know what I'm missing, and why configure didn't
disable the use of multicast sockets if linux is not supposed to support
them)

I am receiving traps, but I have problems with their contents.
I receive traps from two kinds of devices: Retix routers and an Ascend Max
4000 (ISDN/modem dialin box).

>From the Retixes, I receive two kinds of traps:

Thu May 22 12:26:39 PDT 1997 SNMPv1 trap from [204.80.112.65]:
sysUpTime.0 = 0d 2:11:35.48
snmpTrapOID.0 = 1.3.6.1.4.1.72.0.11
portLgclPortID.13 = 13
snmpTrapEnterprise.0 = retix

Here, the 0.11 trap wasn't converted into useful text, because I can't seem
to get the MIB contain the 72.0 branch (traps if I'm not mistaken). That's a
problem I'll have to solve with Retix.

The other messages seem to work fine:

Thu May 22 12:26:46 PDT 1997 SNMPv1 trap from [204.80.112.65]:
sysUpTime.0 = 0d 2:11:35.59
snmpTrapOID.0 = BRIDGE-MIB!newRoot
snmpTrapEnterprise.0 = dot1dBridge

My much bigger problem is with Ascend (and it's far from being the first
time I have "fun" with them).

The box sends me traps of this form:

Thu May 22 12:27:17 PDT 1997 SNMPv1 trap from [198.147.96.77]:
sysUpTime.0 = 67d 10:32:16.00
snmpTrapOID.0 = 1.3.6.1.4.1.529.1.2.4.0.12
consoleIndex.2 = 2
snmpTrapEnterprise.0 = max4000

Descriptor: max4000
MIB Module: ASCEND-MIB
Identifier: 1.3.6.1.4.1.529.1.2.4
Max. Access: not-accessible
File: /usr/local/lib/tnm2.1.5/mibs/ascend.mib

So, a trap like 1.3.6.1.4.1.529.1.2.4 would make sense and would be resolved
as ascend.products.max.max4000, and the resulting string is max4000

Another one is:
Descriptor: consoleStateChange
MIB Module: ASCEND-TRAP
Identifier: 1.3.6.1.4.1.529.0.12
SMI Macro: TRAP-TYPE
Max. Access: not-accessible
File: /usr/local/lib/tnm2.1.5/mibs/ascendtrp.mib

529.0 is the ascend traps file.
Here, again, 1.3.6.1.4.1.529.0.12 would make sense.

However, I get 1.3.6.1.4.1.529.1.2.4.0.12
(the trap type is attached after full description of my hardware).

I haven't read the SNMP RFCs (a bit numerous), but this looks wrong to me,
yet ascend tells me it's the way it's supposed to be and that their HP
openview deals fine with it.

Here's the question:
Who messes up: Tkined or Ascend?

Thanks,
Marc

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.