nv-l

RE: [nv-l] Several things - loading mibs and forwarding specifi c traps to a specific IP address in addition to TEC1

2003-05-01 18:03:48
Subject: RE: [nv-l] Several things - loading mibs and forwarding specifi c traps to a specific IP address in addition to TEC1
From: "Pearson, George" <GPearson AT bcbsm DOT com>
To: "'nv-l AT lists.tivoli DOT com'" <nv-l AT lists.tivoli DOT com>
Date: Thu, 1 May 2003 16:58:29 -0400

James,
For the mib2trap command, the third file in the command appears to be optional because of the brackets, is this true?
Also, can the file name be whatever I chose and where is this written?
I looked at the man mib2trap command and it indicates that the third file in the order string is used for Tec, will Tec not receive if no third file (baroc) coded?

I know that I am beating a dead horse to death (again), but I believe this will put a wrap on things.
George




-----Original Message-----
From: James Shanks [mailto:jshanks AT us.ibm DOT com]
Sent: Wednesday, April 30, 2003 5:23 PM
To: nv-l AT lists.tivoli DOT com
Subject: RE: [nv-l] Several things - loading mibs and forwarding
specific traps to a specific IP address in addition to TEC1


George -

I don't know whether you are aware that when you simply Reply to a note
from the nv-l list it only goes back to the original recipient.
I only respond on the list.  That's all I'm allowed to do.
But I did not request that you send me files.

I am not offering personal service on your problem, my management doesn't
allow that.  You have to call Support for that kind of service.
All I was doing was offering advice on how you could determine for
yourself where the source of your difficulties lay.

Ok, so, you are indeed running with the "-m" option.  That means you have
to configure each trap you want forwarded in trapd.conf.
So add 'em by running the mib2trap script.  Then alter them with xnmtrap.
Then when you see 'em in NetView, either in the window or in the
trapd.log,  they should also be sent to your destination.

If you still don't see them after all that, then I recommend an iptrace
and a call to Support.

Regards,

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group




"Pearson, George" <GPearson AT bcbsm DOT com>
04/30/2003 04:41 PM

 
        To:     James Shanks/Raleigh/IBM@IBMUS
        cc:
        Subject:        RE: [nv-l] Several things  -  loading mibs and forwarding specifi       c 
traps to a specific IP address in addition to TEC1





I have attached two documents,
1) showing that I selected option #2 (as indicated below) and
2) the results of the grep command you requested ( I believe I am using
the -m option).

George

-----Original Message-----
From: James Shanks [mailto:jshanks AT us.ibm DOT com]
Sent: Wednesday, April 30, 2003 3:55 PM
To: nv-l AT lists.tivoli DOT com
Subject: RE: [nv-l] Several things - loading mibs and forwarding
specific traps to a specific IP address in addition to TEC1

This is UNIX so you can use whatever file extension you like for the
mib2trap output.  It will be a script composed of addtrap commands,  as I
said.  Once the output file is created, you execute it.   See the man page

on mib2trap.   It will add the traps as "Log Only" so you will have to use

xnmtrap to alter that if you want to see them in the events window.

You didn't tell me which of the three different possible choices you used
in serversetup.
(1) Forward specific traps as events to (hosts) ___________
(2) Forward specific traps to (hosts)__________
(3) Forwad ALL traps to (hosts) --------------

Note that the serversetup panel does not number them.  I have done that
here to emphasize the difference

Each on of these will put a different option into the trapd.lrf file  for
trapd to use on restart.  The contents of the trapd.lrf file is then
copied to /usr/OV/conf/ovsuf  when the ovdelobj/ovaddobj is done, when you

hit the OK button in serversetup.   To see what that means in terms of the

actual options the daemon runs with you can do "ps -ef | grep trapd".  You

should see all the flags in the output.   The man page for trapd will
explain what all the flags mean.

I am guessing that you selected (2) above.  If so, then you must use
xnmtrap to edit the trap definitions for these traps in trapd.conf, after
you add them by running the mib2trap output script, and make sure the
Forward Trap button is set.  By default, it will not be.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group



"Pearson, George" <GPearson AT bcbsm DOT com>
04/30/2003 02:59 PM

 
        To:     James Shanks/Raleigh/IBM@IBMUS
        cc:
        Subject:        RE: [nv-l] Several things  -  loading mibs and
forwading specific traps to
a specific IP address in addition to TEC1


I found the mib2trap command  "mib2trap mib_file output_file".  My i/p
file is Mib70305.mib, so my command will be as follows:
mib2trap Mib70305.mib SeverIrons.???
What extension do I use for the o/p file?
Will I need to execute the above command from a specific directory?
Will I need to execute the o/p file from a specific directory?
In answer to your question as to who is handling the traps being
forwarded, it is BMC's Patrol Product (I believe PEM).
It will be monitoring traps from the server irons to continually check the

status of some critical application at this site.
As to your question about the option on trapd forwarding, here is what I
did.
1)I select Server Setup from the Admin pull down tab and selected the
following pull down options
2)Configure
3)Set options for daemons
4)Set options for events and trap processing daemons
5)Set options for trapd daemons
6)Click the OK button
7)Stopped and restarted the trapd daemon
I did not recall an "-m" or "-M" option in the above scenario.
George Pearson (gpearson AT bcbsm DOT com)
(313) 225-8306

-----Original Message-----
From: James Shanks [mailto:jshanks AT us.ibm DOT com]
Sent: Tuesday, April 29, 2003 4:44 PM
To: nv-l AT lists.tivoli DOT com
Subject: Re: [nv-l] Several things - loading mibs and forwading specific
traps to a specific IP address in addition to TEC1

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 AT bcbsm DOT com>
04/29/2003 03:40 PM
 
        To:     nv-l AT lists.tivoli DOT 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 AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT 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)


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT 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)

 



#### Forward Traps.doc has been removed from this note on April 30, 2003
by James Shanks
#### grep command.doc has been removed from this note on April 30, 2003 by
James Shanks



---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT 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)

<Prev in Thread] Current Thread [Next in Thread>