Actions such as resolving events and forwarding events are not supported
in ESE.automation. Ue these in rulesets that you apply to user's
workspaces. Rules in ESE.automation are for background tasks -
generally running scripts via the Action template.
Cheers,
Jane
nraaman AT chennai.tcs.co DOT in wrote:
Hi,
I need to correlate
the events at
NetView level. So i
created a ruleset
for whenever a link
goes down, this
evetn as to await
for 10 min. If Up
event recived within
10 mins, Netview
should drop both Up
and down events, if
not down events
should take action.
Ruleset file -
correvent.rs. The
content of the files
is shown below:
RuleSet2 RuleSet
TrapID3 TrapID6
"" 1
TrapID3 TrapID
AttrJoin4
netView6000
1.3.6.1.4.1.2.6.3 6
58916867 0
"netView6000
1.3.6.1.4.1.2.6.
3" "IBM_NVIDWN_EV
Specific 58916867
" ""
AttrJoin4 AttrJoin
ResolvedCorr5
2 0 2 600 0 0 ""
ResolvedCorr5
ResolvedCorr
""
TrapID6 TrapID
AttrJoin4.2
netView6000
1.3.6.1.4.1.2.6.3 6
58916866 0
"netView6000
1.3.6.1.4.1.2.6.
3" "IBM_NVIUP_EV
Specific 58916866
" ""
This ruleset file
name is mentioned in
the ESE.automation
and restarted the
ovactiond daemon and
running fine.
bash-2.05a#
/usr/OV/bin/ovstatus
ovactiond
object manager
name: ovactiond
behavior:
OVs_WELL_BEHAVED
state:
RUNNING
PID:
48194
last message:
Initialization
complete.
exit status:
-
Please help me to
solve this
Regards
N.Raaman
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry <jane.curry AT skills-1st.co DOT uk>. All rights
reserved.
|
