Jordi,
The 'node up' event does not close the ov_node_down event exactly. The way it
flows is when a down event occurs, the TEC receives an ov_node_down event and
opens a TEC event. When the status changes in NetView from down to up, another
ov_node_down event is sent to the TEC, with a status of up. This second
ov_node_down is what closes the first event.
The same logic will apply to threshold events.
HTH
Dean Grant
Ahold Information Services
Jordi Pons <jordi.pons@eltec.es> on 03/29/2000 11:48:16 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: Dean Grant/AIS/US/Ahold)
Subject: [NV-L] NView TEC events cancellation
Hello,
when NetView is configured to send events to the TEC (using any created
ruleset) while a 'node up' event closes in the TEC the previous 'node
down' event, a 'threshold rearm' event in data collecting does not close
a 'threshold' event. I've been trying to correlate them in the ruleset,
but the event stream is configured for convenience as 'block' instead as
'pass' (i saw it in the rs examples). Another thing i did was to modify
the 'TEC slot mapping' ,in the event configuration, to emulate the
fields 'OV_status' and 'status' that seem to be used in the cancellation
of NodeUp/NodeDown IfaceUp/IfaceDown events but with no results...
does anyone know how should i have to do it?
thanks in advance,
--------------------------------------------
Jordi Pons Orteu
debis IT Services - Eltec S.A.
Rbla Marina 478-480
08907 L'Hospitalet del Llobregat (Barcelona)
Tel. 935082000 ext4015
E-mail:jordi.pons@eltec.es
---------------------------------------------
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|