Hi Paul,
A couple of corrections:
1. The file name is "/usr/lnms/conf/FaultMan.conf"
2. Entries cannot be added to the file, therefore, you can't correlate
"everything and anything" - only those traps defined in the file. The file
itself is self-documented.
3. We do filter on "generic" MIB-II traps, you are correct. However, the
original question (and the Subject) is Cisco Traps. We don't filter on
Enterprise specific traps unless they are defined in
/usr/lnms/conf/FaultMan.conf.
4. Rather than edit each entry in the file, you can use the command I
posted earlier:
/usr/lnms/bin/fault_correlator_filter off
This will have the effect you are looking for.
Hope this clears up some confusion. Ralph's description of the process is
accurate, however. Optivity NMS moves trapd to port 412 and places a
process called "trap_server" on port 162. Traps received on port 162 are
processed by trap_server and passed on to trapd when and where appropriate
as I have explained.
-David J. Easter
Sr. Product Manager - Optivity NMS, Network Management Division
Bay Networks/Nortel Networks - How the world shares ideas.
-=-REgarding-=-
At 07:40 PM 12/19/98 -0000, Paul Anderson wrote:
>Cheers Ralph!
>That's worth knowing! Although I KNEW Optivity did it, I always wondered HOW
>Optivity did it....s'pose I should've guessed really....lol
>
>I achieve a similar effect by disabling the fault correlator i.e. I edit
>/usr/lnms/FaultCorr.conf so it doesn't correlate anything. By default the
>correlator will correlate traps from everything and anything. I can't
>remember the syntax but it's pretty obvious when you open the file....
>
>and further to the original query....although there are no specific rules
>for non-Bay devices, there are generic rules which filter out multiple traps
>of the same kind and only send 1 trap every hour or so. Although I'm sure
>this is done with the best intentions, if this is not configured correctly,
>it has the effect of 'blocking traps', which can be very confusing...
>
>regards Paul
>
>
>-----Original Message-----
>From: Schiffinger Ralph 0714 <Ralph.Schiffinger@ERSTEBANK.AT>
>To: NV-L@UCSBVM.ucsb.edu <NV-L@UCSBVM.ucsb.edu>
>Date: Friday, December 18, 1998 4:09 PM
>Subject: AW: cisco traps
>
>
>Check out your trapd settings via smitty!
>Default ports used to receive snmp traps are
>162 for both udp and tcp.
>Optivity changes port 162 for udp to port 412 for udp!
>And then every traps goes first through Optivity's own trap server,
>which then passes the stuff along to NetView's good old trapd daemon.
>Sorry everbody, but in my humble opinion Optivity's trap handling stinks!
>After changing both port settings back to 162 we (me and my NetView)
>are happy again.
>Regards, Ralph (a not-so-happy Optivity-user).
>
>-----Urspr|ngliche Nachricht-----
>Von: James Shanks [SMTP:James_Shanks@TIVOLI.COM]
>Gesendet am: Donnerstag, 17. Dezember 1998 21:24
>An: NV-L@UCSBVM.ucsb.edu; Schiffinger Ralph 0714
>Betreff: Re: cisco traps
>
>
>David -
>
>I understand what you are saying but in fact some customers do not set up
>Optivity in this way and many of those apparently don't know how it has
>been configured. I have been involved in many cases (passed from our Level
>2 folks) of "the traps don't show up in my event window and I have Optivity
>installed": and it has always turned out that they have some configuration
>thing in Optivity which causes it to hang onto the trap(s) from external
>agents.
>
>Is it possible that they could have set "correlate all traps" or perhaps
>"correlate all non-NetView traps" or some such nonsense? I don't know, but
>one of the first questions our Support people learn to ask when someone
>complains about not seeing traps is "Do you have Optivity installed?" .
>
>I am sorry to say that I have never seen the Optivity product set in
>operation, much less configured it. :-(
>
>James Shanks
>Tivoli (NetView for UNIX) L3 Support
>
>
>
>David Easter <David_Easter@BAYNETWORKS.COM> on 12/17/98 10:16:37 AM
>
>Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView <NV-L@UCSBVM.UCSB.EDU>
>
>To: NV-L@UCSBVM.UCSB.EDU
>cc: (bcc: James Shanks)
>Subject: Re: cisco traps
>
>
>
>
>
>Hi,
>
> Actually, Optivity NMS will forward any traps it isn't programmed
>specifically to correlate. It forwards these traps in raw format to the
>platform. We do correlate a couple of Cisco traps ("Protocol Entity
>Reinit" and "tty TCP Conn Closed") but otherwise we pass 'em on to NetView.
>
>Just FYI,
>
>-David J. Easter
>Sr. Product Manager - Optivity NMS, Network Management Division
>Bay Networks/Nortel Networks - How the world shares ideas.
>
>-=-REgarding-=-
>
>At 09:30 AM 12/17/98 -0500, James Shanks wrote:
>>Do you have any third party software on the system, such as Optivity?
>With
>>Optivity, you have to tell him which traps to forward to NetView or he
>will
>>just eat them.
>>
>>You can turn on the trapd tracing by issuing trapd -T from the command
>>line. Then in /usr/OV/log/trapd.trace you should see an entry of the sort
>>"trapd received over UDP from <some IP address>" so if you know that a
>>device sent a trap you can see here if it got to NetView. You can do an
>>iptrace to see if it made it to the box. You turn off trapd tracing by
>>issuing another trapd -T (it's a toggle).
>>
>>James Shanks
>>Tivoli (NetView for UNIX) L3 Support
>>
>>
>>
>>Oren Mamok <orenm@ns.tadiran.com> on 12/17/98 07:09:32 AM
>>
>>Please respond to Discussion of IBM NetView and POLYCENTER Manager on
>> NetView <NV-L@UCSBVM.UCSB.EDU>
>>
>>To: NV-L@UCSBVM.UCSB.EDU
>>cc: (bcc: James Shanks)
>>Subject: cisco traps
>>
>>
>>
>>
>>
>>Hello all,
>>I'm having problems getting cisco traps on my nv6k.
>>I uploaded the cisco mibs , i also configured the trap customization, i
>>configured the router to send f/r,config and snmp
>>traps to the nv6k ( snmp host...) but still all i can see are the nv
>>enterprise events.
>>Any ideas?
>>Greetings ,Oren.
>>
>>Attachment Converted: "c:\Eudora Temp\att-1.htm"
>>
>
|