|
Hello again,
I did not realize that the rule set editor was for editing
the .rs file(s). I don't know why I could not make that connection. I will
open a PMR as I have added the trap settings node and a forward node and
connected the two nodes. I do not have TEC forwarding setup yet as I am using a
the control desk dynamic workspace with TEC-ITS.rs
How do I know if the tecits_upgrade program was run or how
do I know if the TEC_ITS event class structure has been
upgraded?
Thank you,
Kevin Sperry
From: nv-l-bounces@lists.ca.ibm.com
[mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of James
Shanks
Sent: Thursday, March 26, 2009 11:16 AM
To: Tivoli
NetView Discussions
Subject: RE: [NV-L] Events to
TEC
DO NOT manually edit the file!!! The chances of messing it up are enormous.
It was never meant to be edited with vi.
It looks confusing because it is
meant to be edited with the ruleset editor, nvrsEdit, and half of what you see
is used by the GUI display for that tool.
The Admin Guide has a whole
section on creating rulesets. I suggest you read it over before attempting to
modify the ruleset in the editor. BTW, the editor makes a backup copy of the
file when you open it.
Basically what you are going to do is add a new
trap settings node for your vendor events. You can add many of them in a single
trap settings node. If you need help, your best bet is to open a PMR. Support
has been helping people do this for a decade.
James Shanks
Tivoli
Network Availability Management Level Three
Network Availability
Management
Tivoli Software, IBM Corp
1-919-224-1642 | T/L 687-1642 | ITN
26871642
 "Sperry, Kevin"
<Kevin.Sperry@us.ngrid.com>
"Sperry, Kevin"
<Kevin.Sperry@us.ngrid.com>
Sent by:
nv-l-bounces@lists.ca.ibm.com
03/26/2009 09:52 AM
|
Please respond to
Tivoli
NetView Discussions
<nv-l@lists.ca.ibm.com> | |
|
Hello,
using the scripts method seems straight forward but we
want to poses the central control of what is sent to TEC. We are running UNIX
and like the idea of using the adapter, however, adding vendor events to
TEC_ITS.rs is confusing me. When I look at the file, this is what I see for
example.
EventAttr35 EventAttr ForwardCorr36
Specific 0 50790442
50790442 0
ForwardCorr36 ForwardCorr
""
EventAttr37 EventAttr
ForwardCorr38
Specific 0 50790419 50790419 0
ForwardCorr38
ForwardCorr
""
I looked in the manuals and cannot find information about the
format of this file or field descriptions. How do I enter vendor specific events
into this file? Any insight would be greatly appreciated as
always.
Thank
you,
Kevin Sperry
From:
nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com]
On Behalf Of James
Shanks
Sent:
Wednesday, March 04, 2009 2:53 PM
To: Tivoli NetView
Discussions
Subject:
Re: [NV-L] Events to TEC
Well, that depends on how the scripts are implemented. And on
what platform, UNIX and Linux or Windows. And on whether you want to forward
NetView events or include vendor events too. I think you are on Linux as I
recall.
In general we favor the adapter approach over scripts. All our
documentation is written that way. And using an adapter daemon gives you a
single point of control for starting, stopping, or modifying what you send. Plus
you can log or trace what the daemon does, whereas with postemsg scripts that's
not so easy.
In UNIX and Linux the adapter is implemented as part of the
nvserverd daemon. You configure the event forwarding from serversetup. That
creates a /usr/OV/conf/tecint/conf file. The standard ruleset for TEC forwarding
is TEC_ITS.rs and it is designed to work with the netview.rls rulebase shipped
in TEC 3.9. That rulebase will automatically close matching Critical and Normal
events for the same host, escalate the severity of the critical events based on
time open, and that sort of thing. The TEC_ITS.rs will send only NetView events
that the rulebase is expecting to keep the traffic low, but you can edit it to
add vendor events if you wish.
The formatting for the event sent to TEC
that nvserverd will use is stored in trapd.conf for the event. There's a base
set of information that will be used if none is provided. And mib2trap can be
used to format vendor MIBs which describe traps into addtrap statements which
will include TEC formatting if you specify that you want a baroc file created
when you run mib2trap. We've tried to make this easier than writing scripts
yourself.
If you want to log the events being sent to TEC, you edit the
tecint.conf file and uncomment the line #NvserverdTraceTECEvents=YES, and then
you can get nvserverd to reload that conf file by issuing
nvtecia
-reload
This will cause nvserverd to write each event to
/usr/OV/log/nvserverd.log before he gives it to the TEC library code for
sending. You will have to manage that log file yourself as it will just grow and
grow.
Hope this helps,
James Shanks
Tivoli Network Availability
Management Level Three
Network Availability Management
Tivoli Software,
IBM Corp
1-919-224-1642 | T/L 687-1642 | ITN 26871642
 "Sperry, Kevin"
<Kevin.Sperry@us.ngrid.com>
"Sperry, Kevin"
<Kevin.Sperry@us.ngrid.com>
Sent by:
nv-l-bounces@lists.ca.ibm.com
03/04/2009 02:22 PM
|
Please respond to
Tivoli NetView Discussions
<nv-l@lists.ca.ibm.com> | |
|
Hello,
Using NV 7.15 w/ FP1. We now have a need for NV
integration w/ TEC. Another part of our company uses OpenView and TEC. They use
scripts to forward events to TEC. I have done some research and have identified
two ways to accomplish this task. Scripts and using the "serversetup" gui. Could
you give insight to pros and cons of either method?
Thank you,
Kevin Sperry
IT Analyst, Data Center Monitoring Control
nationalgrid
7437 Henry
Clay Blvd. Bldg#3
Liverpool, NY
13088
Phone: (315) 460-2688
Internal: 829-2688
Kevin.Sperry@us.ngrid.com
********************************************************************************
This
e-mail and any files transmitted with it, are confidential to National Grid and
are intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error, please reply to this
message and let the sender know._______________________________________________
NV-L mailing
list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)
********************************************************************************
This
e-mail and any files transmitted with it, are confidential to National Grid and
are intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error, please reply to this
message and let the sender
know._______________________________________________
NV-L mailing
list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser
access limited to internal IBM'ers only)
********************************************************************************
This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please reply to this message and let the sender know.
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
