RE: [nv-l] trapd.log

[James Shanks <jshanks@us.ibm.com>]

Brian -

mib2trap even on Windows will parse SNMP V2 traps into addtrap statements.  And you can load SNMP V2 MIBs with either loadmibv2 (and browse with browserv2) or the java MIB loader from the web client, mibloader.bat.  If you are getting traps showing as DEFAULT FMT then they are being sent ad SNMP V1 not SNMP V2 traps.  

I took a quick look at the MIBs from your link and they puzzle me greatly.  The names call them V1, yet they contain the MODULE IDENTITY statement, which is an SNMP V2 construct, so I don't quite know what to make of them.  But that may not be important.

In any case, I would try running addtrap on them and see what happens.  Since there are two MIBs, and one seems to be nothing but trap definitions, I would concatenate the two MIB files, the trap definitions second, into one big file, and run then mib2trap on that. If you cannot get that to work, I would call Support.  While I am forbidden to do anything more than give advice here, someone in Level 2 will be happy to download your MIBs and help you get the traps defined correctly.  That's what they do.

Alternatively, yes, you could just read the trap definitions MIB and manually add definitions to trapd.conf with Trap Settings.  That's always an option.  Alternatively, when the DEFAULT FMT message appears in the Event Browser, if you right click on that event and select "Event Details" you can see all the variables which were sent with that trap.  One way or the other, you can manually define the trap.   It is not hard.


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

Brian Kraftchick <Brian.Kraftchick@odfl.com> Sent by: owner-nv-l-digest@lists.us.ibm.com 10/20/2003 03:38 PM Please respond to nv-l

To:        "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>         cc:                 Subject:        RE: [nv-l] trapd.log

Below is the link to the MIB files that I have downloaded for the Nortel Contivity Extranet device.  In a previous thread I was told that these are V2 MIBS and they won't load in 7.1.2 on the Win2K platform.  I also found another suggestion to convert the MIB to a V1 MIB...but that was really an intricate procedure.  Is converting it the only option I have ?  Otherwise, I'd just need to manually define this particular trap, and other's that they might send to Netview, right ?
 
Thanks for you help James !!
-----Original Message-----
From: James Shanks [mailto:jshanks@us.ibm.com]
Sent: Monday, October 20, 2003 3:25 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] trapd.log


DEFAULT FMT means that the trap is NOT defined in trapd.conf, so it is getting the default FMT wrapper. 
Use Trap Settings to define it. 

And the ORIGIN slot on 7.1.2 is broken and will never fill in correctly.  You'll need to use another mapping.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

Brian Kraftchick <Brian.Kraftchick@odfl.com> Sent by: owner-nv-l-digest@lists.us.ibm.com 10/20/2003 03:00 PM Please respond to nv-l

To:        "NVList (E-mail)" <nv-l@lists.us.ibm.com>        cc:                Subject:        [nv-l] trapd.log

NV 7.1.2 on Win2K 
  
Has anybody seen the below in their trapd.log ?  I just wanted to know what the ? meant and why is states DEFAULT FMT.  We have the TEC adapter installed, and when the event gets to TEC, it is really generic.  Since the origin slot doesn't get filled correctly (our's always get filled with 211.36.147.10 for some reason, but that's another issue), I have no way of knowing from this event which interface went down from this event.  Any ideas ? 
  
Thanks ! 
  
Brian Kraftchick 
Network Administrator 
Old Dominion Freight Line 
Ph: (336) 822-5938 
Fax: (336) 822-5149 
E-mail: brian.kraftchick@odfl.com 
Web Site: www.odfl.com