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 AT TIVOLI DOT COM]
Gesendet am: Donnerstag, 17. Dezember 1998 21:24
An: NV-L AT UCSBVM.ucsb DOT 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 AT BAYNETWORKS DOT COM> on 12/17/98 10:16:37 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L AT UCSBVM.UCSB DOT EDU>
To: NV-L AT UCSBVM.UCSB DOT 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 AT ns.tadiran DOT com> on 12/17/98 07:09:32 AM
>
>Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView <NV-L AT UCSBVM.UCSB DOT EDU>
>
>To: NV-L AT UCSBVM.UCSB DOT 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"
>
|
