Well, I think you may have a misunderstanding of the mechanisms involved.
Are you expecting these devices to send you traps? If so, what did you do
on those boxes themselves to enable that?
Nothing you did in NetView will cause these boxes to send traps to
NetView; they have to b configured to do that.
If you think these devices are properly configured, do you see traps from
them in the trapd.log? If no, then the problem is on their end.
The option you set on trapd forwards traps from trapd to the destination
address (assuming that you did it correctly) but it does not guarantee
that there is anything to send. If you use the "-m" option rather than
the "-M" option, then you must explicitly configure each trap you want
forwarded in the trapd.conf file. You do that with xnmtrap by modifying
the trap and toggling the button which says "Do Not Forward Trap" to
"Forward Trap".
So if these traps you are expecting to see are vendor specific, they must
be defined in trapd.conf to begin with. If they aren't, then you have to
add them. Merely loading the MIBs which define them is not enough. If
the traps are defined in that MIB, then you could use mib2trap to create a
script to add them (the script contains a series of addtrap commands), but
you would still need to use xnmtrap after running the script to adjust the
forwarding for each trap, unless you are forwarding all traps. I hope
this is clear. If not, ask more questions.
Finally, the destination IP address must be for another trap receiver,
either listening on udp port 162 by default , or else on some other port
you specified. The traps will arrive there as raw hex data and will need
to be received by some programmed receiver who can display them. So what
facility on the destination box are you using for that? Another NetView?
And forwarding traps this way has almost nothing to do with sending them
to TEC, though some of the same facilities are involved. Generally
speaking, traps sent to TEC via the internal adapter should be defined in
trapd.conf so that you can control the slot values.
If all this sounds foreign to you, then perhaps you should start with a
more complete description of what you are trying to accomplish.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
"Pearson, George" <GPearson@bcbsm.com>
04/29/2003 03:40 PM
To: nv-l@lists.tivoli.com
cc:
Subject: [nv-l] Several things - loading mibs and forwading
specific traps to a
specific IP address in addition to TEC1
I have loaded mibs MIB70305.MB for five Server Irons.
I have added the IP addresses for the Server Irons to netmon.seed file and
issued a netmon -y command to discover new addresses.
I have added a destination IP address to forward these specific traps from
the Server Irons, using "Set options for Trapd daemon".
I have stopped and restarted the Trapd daemon.
I can ping the Server Irons as well as the destination IP address where
the traps are to be forwarded.
I do not see any traps from the Server Irons, what am I missing???
George Pearson
(313) 225-8306
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|