Maggie -
Perhaps it is just me but I am having a very hard time following what you are
trying to tell me. Perhaps the problem is that you are expecting to get
something out of the ruleset action that is not there. But without seeing your
action command for sure, I cannot tell.
You keep jumping back and forth between how the trap can be displayed in
trapd.log or in the event window and what you get out of the action node of a
ruleset. These are two entirely different things. You are correct that loading
a MIB and adding traps to trapd.conf has no effect whatsoever on what you get
out of the ruleset. Did you expect that it would?
In a ruleset action, you must do all the formatting. In trapd, for the most
part, you need only tell trapd what you want, by configuring trapd.conf. I hope
the difference is clear. All that gets passed to the ruleset is the raw trap.
It is not formatted.
Now we are back to the beginning. You MUST make the effort to figure out what
the trap variables in the 8260 mean. I cannot do it for you. Once you know,
then you can fix your action node script to send a meaningful mail message.
Perhaps you can use the trap formats in trapd.log and the event window to help.
If you make the event log message read "$*" it will show you all the variables
with what whatever MIB definitions you have loaded. Then you can use that
information to add your own formatting to mail message. But if all you do is
echo the variables, $NVATTR_1 to $NVATTR_50, then all you will get is whatever
was in that position in the trap, and there will be no formatting done. What
you are seeing is not only normal but expected.
There are NO APIs to read trapd.conf and extract the message formatting but you
can do that in a script if you like. I am afraid you are on your own here.
All NetView APIs you may use for whatever purpose are documented in the NetView
Programmer's Reference. Hints on how to design programs are discussed in the
NetView Programmer's Guide.
Hope this helps.
James Shanks
Tivoli (NetView for UNIX) L3 Support
|