[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. | 
| Notice: | Use IPMT for problems. Newsletter location in note 6187 | 
| Moderator: | TAEC::BEROUD | 
|  | 
| Created: | Mon Aug 21 1989 | 
| Last Modified: | Wed Jun 04 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 6497 | 
| Total number of notes: | 27359 | 
6014.0. "Notification ordering problem with events via rules" by BACHUS::FOLENS () Thu Jun 09 1994 06:36
I'm currently using DECmcc v1.3.
I have created 3 occurs alarm rules:
Domain QUAKER:.backbone Rule router_circuit_down
AT  9-JUN-1994 12:27:25 Characteristics
Examination of attributes shows:
                  Alarm Fired Procedure = DISK$DATA_1:[FOLENS]MCC_ROUTER_CIRCUIT
                                          _STATE.COM;4
                             Expression = (OCCURS (Node4 * circ * circuit down))
                               Severity = Critical
                         Probable Cause = Unknown
Domain QUAKER:.backbone Rule router_circuit_down_fault
AT  9-JUN-1994 12:27:35 Characteristics
Examination of attributes shows:
                  Alarm Fired Procedure = DISK$DATA_1:[FOLENS]MCC_ROUTER_CIRCUIT
                                          _STATE.COM;4
                             Expression = (OCCURS (Node4 * circ * circuit down
                                          circuit fault))
                               Severity = Critical
                         Probable Cause = Unknown
Examination of attributes shows:
                  Alarm Fired Procedure = DISK$DATA_1:[FOLENS]MCC_ROUTER_CIRCUIT
                                          _STATE.COM;4
                             Expression = (OCCURS (Node4 * circ * circuit up))
                               Severity = Warning
                         Probable Cause = Unknown
The purpoose is to detect failure of WAN links and to get a procedure executed
to log the problem to DCM.
Now it happens that a link goes down for a very short period of time. 
Thus I receive first an 'circuit down' event and right after a 'circuit up' 
event. 
Now notification seems to have a problem to report these event in the right 
order although that the time reported is right:
The last event detected: Node4 QUAKER:.routers.qbr900 Circuit SYN-0 Circuit Up
 9-JUN-1994 05:25:48.81
The last event detected: Node4 QUAKER:.routers.qbr900 Circuit SYN-0 Circuit Down
 Circuit Fault   9-JUN-1994 05:25:48.39
If I don't use rules but notify requests the order is correct. What can I do 
about it?
-Geert-