I'm sorry everyone that I keep beating on this ruleset thing, but here's
where I am today.
I have received a copy of a ruleset from one of the nice group members
(thanks Mark) that I have modified slightly for our use. The rule set
basically looks for the IBM_NVNDWN_EV or IBM_NVIUP_EV events. At that point
I have it setup to echo a response out to a log file for now just to watch
it work. If I create a Dynamic Workspace with the ruleset, I get responses
in my log file, but when I place the ruleset (actually rulesets, I need our
different OSPF areas broke down) in the /usr/OV/conf/ESE.automation file, I
get no longer receive responses. After I placed the entries in the
ESE.automation file, I did a 'ovstop actionsvr' and then a 'ovstart
actionsvr' and I'm still not getting any results.
Is there something else I need to do to get these working?
Thanks
--
Dean Sullinger
Arizona Deptartment of Transportation
Technical Information Resources Phone: (602)712-8673
Network Architecture Group
Email : dean@dot.state.az.us
SMail : 206 S. 17th Ave #110G Phx Az 85007-3212
Internet: http://www.dot.state.az.us
-----Original Message-----
From: Dean Sullinger [mailto:DSullinger@dot.state.az.us]
Sent: Thursday, July 20, 2000 2:11 PM
To: 'IBM NetView Discussion'
Subject: RE: [NV-L] Ruleset for Downed Nortel Rtr
Thanks James... I'll give this a shot next week.
Dean Sullinger
-----Original Message-----
From: James_Shanks@tivoli.com [mailto:James_Shanks@tivoli.com]
Sent: Tuesday, July 18, 2000 2:18 PM
To: IBM NetView Discussion
Subject: Re: [NV-L] Ruleset for Downed Nortel Rtr
There is nothing simple about the ruleset you have included below, at least
in
my opinion.
It includes many FieldCompares, each of which means that nvcorrd will have
to
pause his processing and query ovwdb for object information before
continuing.
That may be why it appears to stop. It also has correlation and user exits.
Looks pretty complex to me. The only way to know for sure what is going
on
would be to trace it while it runs. Issue "nvcdebug -d all" from the
command
line after you have it loaded and look at the nvcorrd.alog/blog. I also
suggest that you open a problem to Support and get some help reading the
traces.
It is very difficult for anyone to evaluate a ruleset without loading it in
the
editor to get a graphical picture of it and then looking at the traces to
see
how it runs.
As for other publications on using rulesets, you may find the redbook,
"Examples
Using NetView for AIX Version 4", SG24-4515-00, which you can get from IBM
at
http://www.redbooks.ibm.com/ .
The Admin Guide details most of the variables -- they are the contents of
the
trap -- enterprise id, origin, community name, generic id, specific id, and
all
the trap variables. The only things that are also passed to an action are
the
category and severity of the trap in trapd.conf. If you look at the
nvaction.alog/blog, you can actually see what is passed in a tilde "~"
separated
stream.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Dean Sullinger <DSullinger@dot.state.az.us> on 07/18/2000 04:16:04 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'nv-l@tkg.com'" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Ruleset for Downed Nortel Rtr
We need to create a simple ruleset that will page us when one of our Nortel
routers go down. I have tried the examples in the documentation and
continue to get information for other devices along with the routers. We
don't need to be informed when there are minor events happening with the
routers, we just need to know when they go red and when they come back to
green (up or down). I put together a ruleset (below), but it seams to work
for awhile and then stop. Also, I would like it to page us only once when
the router goes down and once when the router comes back up.
Please excuse my simplicity... I have little experience messing with the
rulesets. BTW - Is there anyplace where you can find all the different
variables that are or can be passed to an external app using the "Action"
function?
Any suggestion's where I could get any examples or ideas would be great.
Thanks
==== ruleset starts here ====
RuleSet72 RuleSet TrapID73 TrapID91
"" 0
TrapID73 TrapID NVFldCmp74 AttrJoin82
netView6000 1.3.6.1.4.1.2.6.3 "6 " "58916865 " 0 "netView6000
1.3.6.1.4.
1.2.6.3" "IBM_NVNDWN_EV Specific 58916865 " "" 0
NVFldCmp74 NVFldCmp NVFldCmp75
isPC "" "" 0 1 1 13566272 Origin 0 ""
NVFldCmp75 NVFldCmp NVFldCmp76 NVFldCmp79
"IP Status" Critical "" 0 1 1 0 Origin 0 ""
NVFldCmp76 NVFldCmp UserExit77
isIPRouter TRUE "" 0 1 1 0 Origin 0 ""
UserExit77 UserExit ForwardCorr78
"/usr/local/bin/nv_logfileDN $NVA" 0 0 0 ""
ForwardCorr78 ForwardCorr
""
NVFldCmp79 NVFldCmp UserExit80
isBayNetworksWellfleetRouter TRUE "" 0 1 1 0 Origin 0 ""
UserExit80 UserExit ForwardCorr81
"/usr/local/bin/nv_logfileDN $NVA" 0 0 0 ""
ForwardCorr81 ForwardCorr
""
AttrJoin82 AttrJoin NVFldCmp83
"" 0 "" 600 "" 0 ""
NVFldCmp83 NVFldCmp NVFldCmp84
isPC "" "" 0 1 1 0 Origin 0 ""
NVFldCmp84 NVFldCmp NVFldCmp85 NVFldCmp88
"IP Status" Normal "" 0 1 1 0 Origin 0 ""
NVFldCmp85 NVFldCmp UserExit86
isIPRouter TRUE "" 0 1 1 0 Origin 0 ""
UserExit86 UserExit ResolvedCorr87
"/usr/local/bin/nv_logfileUP $NVA" 0 0 0 ""
ResolvedCorr87 ResolvedCorr
""
NVFldCmp88 NVFldCmp UserExit89
isBayNetworksWellfleetRouter TRUE "" 0 1 1 0 Origin 0 ""
UserExit89 UserExit ResolvedCorr90
"/usr/local/bin/nv_logfileUP $NVA" 0 0 0 ""
ResolvedCorr90 ResolvedCorr
""
TrapID91 TrapID AttrJoin82.2
netView6000 1.3.6.1.4.1.2.6.3 "6 " "58916864 " 0 "netView6000
1.3.6.1.4.
1.2.6.3" "IBM_NVNUP_EV Specific 58916864 " "" 0
==== ruleset ends here ====
--
Dean Sullinger
Arizona Deptartment of Transportation
Technical Information Resources Phone: (602)712-8673
Network Architecture Group
Email : dean@dot.state.az.us
SMail : 206 S. 17th Ave #110G Phx Az 85007-3212
Internet: http://www.dot.state.az.us
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|