|Subject:||Re: [nv-l] Mib2trap alcatel AOS devices|
|From:||James Shanks <firstname.lastname@example.org>|
|Date:||Tue, 13 Jan 2004 15:37:40 -0500|
|Delivery-date:||Tue, 13 Jan 2004 20:49:09 +0000|
If you see nothing in trapd.log, then odds are you aren't getting them, though you could use serversetup to cause trapd to run with the -x option (hex dump all packets) and then start the trapd trace. You can toggle it on and off at the command line with "trapd -T". If we got it, it'll be logged there, even if you had configured trapd to ignore it.
Other than that, an iptrace of port 162 on the AIX NetView box would tell you definitively if they ever arrive. I think this should do it:
startsrc -s iptrace -a "-a -s <netview_server_name> -b -p 162 /tmp/iptrace.bin"
then when you are sure they should have arrived format the iptrace via
ipreport -srn /tmp/iptrace.bin > iptrace.txt
and see whether they are there.
Bet they aren't.
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
Our biggest issue right now is working with Alcatel devices both the previously known xylan devices and there new ones. we have enabled all traps on the devices to be sent to the AIX netview box though I have received none from it, no FMT ones or anything. going to use a sniffer to try and trap all the data and see if it is spitting out the information right. I have checked the trapd logs as well
thanks for the help
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||RE: [nv-l] Cannot identify OID, Binder, Karin|
|Next by Date:||RE: [nv-l] Cannot identify OID, CMazon|
|Previous by Thread:||Re: [nv-l] Mib2trap alcatel AOS devices, Christopher J Petrina|
|Next by Thread:||[nv-l] A plea for anyone who used the old Tivoli Manager for Network Connectivity product, Van Order, Drew \(US - Hermitage\)|
|Indexes:||[Date] [Thread] [Top] [All Lists]|
Archive operated by Skills 1st Ltd
See also: The NetView Web