Chris,
A less painful solution, IMHO, would be to upgrade to NMS 8.1.1 which
does have support for the BayStack 450 switches. This would load the trap
defintions into trapd.conf automatically for you.
-David J. Easter
Sr. Product Manager - Optivity NMS, Network & IP Services Management Division
Bay Networks/Nortel Networks - How the world shares ideas.
-=-Regarding-=-
At 08:37 AM 4/1/99 -0500, OGrant wrote:
>Don't know about netview/unix, but on NT, I had little success with mib2trap
>and some cisco mibs - eventually, I created the traps by hand through
>netview's event browser. That is, I had to correlate the oid to a more
>descriptive event in order to bring those never-ending "DEFAULT FMT"
>messages to an end.
>
>> -----Original Message-----
>> From: Chris McBride [SMTP:ChrisM@RIGROUP.COM]
>> Sent: Wednesday, March 31, 1999 6:21 PM
>> To: NV-L@UCSBVM.ucsb.edu
>> Subject: adding traps to trapd.conf for Bay 450 switches
>>
>> I'm running Netview 5 w/ Optivity 8.1. I currently have the
>> faultcorrelator
>> set to pass the traps on to netview.
>>
>> I'm trying to find an addtrap script or a mib which I can actually compile
>> an addtrap script using mib2trap for the Bay 450 switches. I've
>> downloaded
>> the MIB's from Bay's website, but none of them create anything when run
>> through mib2trap. I'm not sure why this doesn't work but it appears to be
>> because not all of the information needed to create the addtrap commands
>> is
>> in the mib file.
>>
>> Has anyone had any success in this?
>>
>> Here is an example of what I'm currently seeing in the trapd.log:
>>
>> 922885932 3 Wed Mar 31 07:12:12 1999 172-16-145-75.rigroup.com ? Agent
>> Interface Up (linkUp Trap) enterprise:synoptics (1.3.6.1.4.1.45.3.35.1)
>> args(1):
>> 922885932 3 Wed Mar 31 07:12:12 1999 172-16-145-75.rigroup.com ? [1]
>> mgmt.mib-2.interfaces.ifTable.ifEntry.ifIndex.17 (Integer): 17
>> 922885932 5 Wed Mar 31 07:12:12 1999 172-16-145-75.rigroup.com A
>> SynOptics
>> FaultCorrelator Meta-Trap: Device 172.16.145.75, fault report: Link Down,
>> Description: The communications link on interface 17 is down. This fault
>> was
>> first reported on Thu Mar 18 16:41:09 1999. The fault status has changed
>> 37
>> times., Severity: 7, Traps correlated: 48
>>
>> I currently get entries from both faultcorrelator and trapd. Orginally I
>> thought I would disable faultcorrelator completely, but the it's ability
>> to
>> display the number of traps correlated is good to know.
>>
>> thanks.
>> --
>> Chris McBride
>> The Rock Island Group
>> chrism@rigroup.com
>
|