[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3476.0. "LINK DOWN event fires LINK UP rule" by HLFS00::TIMMERMANS_A () Fri Jul 31 1992 04:19

Hi,

On receiving a PhaseV event link down event the alarm rule HDLC_LINK_DOWN and
rule HDLC_LINK_UP are fired. It seems to be a bug in DECmcc version 1.2.
 
!!!!!!!!!!!!!! Alarm, 30-JUL-1992 09:43:29 !!!!!!!!!!!!!! [1,25]
Domain: KA500_NS:.PILOTNETWERK                        Severity: Critical
Notification Entity: Node KA500_NS:.dcabis HDLC Link W618-3-2 
Event Source: Domain KA500_NS:.PILOTNETWERK Rule HDLC_LINK_DOWN 
Event: OSI Rule Fired

                             Event Type = QualityofServiceAlarm
                             Event Time = 30-JUL-1992 09:43:28.83
                         Probable Cause = Unknown
                        Additional Info = { (
                               significance = True,
                                information = "The last event detected: Node 
                                              KA500_NS:.dcabis HDLC Link 
                                              W618-3-2 Link Down  30-JUL-1992 
                                              09:43:28.47" ),
                                            (
                               significance = True,
DOWN  --------->                information = "Event: Link Down " ),
                                            (
                               significance = True,
                                information = "(OCCURS (NODE * HDLC Link * Link 
DOWN  --------->                              Down))" ) }
                         Managed Object = Node KA500_NS:.dcabis HDLC Link 
                                          W618-3-2 
                     Perceived Severity = Critical
                        Additional Text = " Link Down   
                                          "


!!!!!!!!!!!!!! Alarm, 30-JUL-1992 09:43:30 !!!!!!!!!!!!!! [1,26]
Domain: KA500_NS:.PILOTNETWERK                        Severity: Clear
Notification Entity: Node KA500_NS:.dcabis HDLC Link W618-3-2 
Event Source: Domain KA500_NS:.PILOTNETWERK Rule HDLC_LINK_UP 
Event: OSI Rule Fired

                             Event Type = QualityofServiceAlarm
                             Event Time = 30-JUL-1992 09:43:29.43
                         Probable Cause = Unknown
                        Additional Info = { (
                               significance = True,
                                information = "The last event detected: Node 
                                              KA500_NS:.dcabis HDLC Link 
                                              W618-3-2 Link Down  30-JUL-1992 
                                              09:43:28.47" ),
                                            (
                               significance = True,
DOWN  --------->                information = "Event: Link Down " ),
                                            (
                               significance = True,
                                information = "(OCCURS (NODE * HDLC Link * Link 
UP    --------->                              Up))" ) }
                         Managed Object = Node KA500_NS:.dcabis HDLC Link 
                                          W618-3-2 
                     Perceived Severity = Clear
                        Additional Text = " Link Up   
                                          "
Adrie Timmermans
Digital Holland

T.R	Title	User	Personal Name	Date	Lines
3476.1	is the node sending down, up together	HERON::PATEL_A	LoLo-AQIC-I82Q-B4IP, - LMF	`Fri Jul 31 1992 04:52`	11
	Haven't really started with Phase V yet. Something I have seen with Phase 4 eventing is as follows, If you sink events from a node X to a node Y, and the circuit goes down on X -- you do not see that event until the circuit is up again. As a result what you see on Y is a circuit down and circuit up one after the other. Note sure, but I think the node X q's the circuit down event until the circuit is actually up then relays it to node Y. This really shows up when you intentionally bounce the circuit on the node X
3476.2	No link up event	HLFS00::TIMMERMANS_A		`Fri Jul 31 1992 05:28`	9
	RE: .1 I have setup two event streams from the DECnis to the DECmcc station, one stream goes to the opcom message screen and the other one is going to the MCC_EVL_SINK. I am only receiving the Link Down event at that time. Within the screen output it's visible that the LINK_UP alarm rule is triggered by the Link Down event.
3476.3	Try the GETEVENT directive	MOLAR::ROBERTS	Keith Roberts - DECmcc Toolkit Team	`Fri Jul 31 1992 14:22`	12
	Could you try using the GETEVENT directive please. MCC> getevent NODE * HDLC Link * Link Down and cause the link to cycle. Then check the Link Up event: MCC> getevent NODE * HDLC Link * Link Up and post the output. btw - these are the directives which Alarms is using to collect your data. /keith
3476.4	getevent output	HLFS00::TIMMERMANS_A		`Mon Aug 03 1992 11:17`	40
	Hello, This is the output of the getevents for link up and link down. Hope this helps, Adrie $ manage/enter DECmcc (V1.2.0) MCC> getevent node * hdlc link * Link Down Node KA500_NS:.dcabis HDLC Link W618-3-0 AT 3-AUG-1992 15:02:17 CONFIGURATION EVENTS Successfully received events: Event: Link Down <------ forced link down event by NCL MCC> getevent node * hdlc link * Link Up Node KA500_NS:.dcabis HDLC Link W618-3-0 AT 3-AUG-1992 15:03:31 CONFIGURATION EVENTS Successfully received events: Event: Link Down <------ forced link down event by NCL MCC> getevent node * hdlc link * Link Up Node KA500_NS:.dcabis HDLC Link W618-3-0 AT 3-AUG-1992 15:03:49 CONFIGURATION EVENTS Successfully received events: Event: Link Up <------ forced link up event by NCL The getevent node * hdlc link * link down is not triggered by the link up event.
3476.5		MOLAR::ROBERTS	Keith Roberts - DECmcc Toolkit Team	`Mon Aug 03 1992 14:46`	15
	RE: .4 You asked for the Link Up event, and got a Link Down Event > MCC> getevent node * hdlc link * Link Up > > Node KA500_NS:.dcabis HDLC Link W618-3-0 > AT 3-AUG-1992 15:03:31 CONFIGURATION EVENTS > > Successfully received events: > Event: Link Down <------ forced link down event by NCL This is not an Alarms problem. Looks like something from DNA phase 5 /keith
3476.6	LINK DOWN event fires LINK UP rule revisited	GIDDAY::CHONG	Andrew Chong - Sydney CSC	`Wed Jul 14 1993 01:31`	188
	Hi, I am seeing exactly the same problem in note #3476. Is there any solution to the problem ? I am using mcc V1.3 Andrew/ ================================================================================ Note 3476.0 LINK DOWN event fires LINK UP rule 5 replies HLFS00::TIMMERMANS_A 65 lines 31-JUL-1992 03:19 -------------------------------------------------------------------------------- Hi, On receiving a PhaseV event link down event the alarm rule HDLC_LINK_DOWN and rule HDLC_LINK_UP are fired. It seems to be a bug in DECmcc version 1.2. !!!!!!!!!!!!!! Alarm, 30-JUL-1992 09:43:29 !!!!!!!!!!!!!! [1,25] Domain: KA500_NS:.PILOTNETWERK Severity: Critical Notification Entity: Node KA500_NS:.dcabis HDLC Link W618-3-2 Event Source: Domain KA500_NS:.PILOTNETWERK Rule HDLC_LINK_DOWN Event: OSI Rule Fired Event Type = QualityofServiceAlarm Event Time = 30-JUL-1992 09:43:28.83 Probable Cause = Unknown Additional Info = { ( significance = True, information = "The last event detected: Node KA500_NS:.dcabis HDLC Link W618-3-2 Link Down 30-JUL-1992 09:43:28.47" ), ( significance = True, DOWN ---------> information = "Event: Link Down " ), ( significance = True, information = "(OCCURS (NODE * HDLC Link * Link DOWN ---------> Down))" ) } Managed Object = Node KA500_NS:.dcabis HDLC Link W618-3-2 Perceived Severity = Critical Additional Text = " Link Down " !!!!!!!!!!!!!! Alarm, 30-JUL-1992 09:43:30 !!!!!!!!!!!!!! [1,26] Domain: KA500_NS:.PILOTNETWERK Severity: Clear Notification Entity: Node KA500_NS:.dcabis HDLC Link W618-3-2 Event Source: Domain KA500_NS:.PILOTNETWERK Rule HDLC_LINK_UP Event: OSI Rule Fired Event Type = QualityofServiceAlarm Event Time = 30-JUL-1992 09:43:29.43 Probable Cause = Unknown Additional Info = { ( significance = True, information = "The last event detected: Node KA500_NS:.dcabis HDLC Link W618-3-2 Link Down 30-JUL-1992 09:43:28.47" ), ( significance = True, DOWN ---------> information = "Event: Link Down " ), ( significance = True, information = "(OCCURS (NODE * HDLC Link * Link UP ---------> Up))" ) } Managed Object = Node KA500_NS:.dcabis HDLC Link W618-3-2 Perceived Severity = Clear Additional Text = " Link Up " Adrie Timmermans Digital Holland ================================================================================ Note 3476.1 LINK DOWN event fires LINK UP rule 1 of 5 HERON::PATEL_A "LoLo-AQIC-I82Q-B4IP, - LMF" 11 lines 31-JUL-1992 03:52 -< is the node sending down, up together >- -------------------------------------------------------------------------------- Haven't really started with Phase V yet. Something I have seen with Phase 4 eventing is as follows, If you sink events from a node X to a node Y, and the circuit goes down on X -- you do not see that event until the circuit is up again. As a result what you see on Y is a circuit down and circuit up one after the other. Note sure, but I think the node X q's the circuit down event until the circuit is actually up then relays it to node Y. This really shows up when you intentionally bounce the circuit on the node X ================================================================================ Note 3476.2 LINK DOWN event fires LINK UP rule 2 of 5 HLFS00::TIMMERMANS_A 9 lines 31-JUL-1992 04:28 -< No link up event >- -------------------------------------------------------------------------------- RE: .1 I have setup two event streams from the DECnis to the DECmcc station, one stream goes to the opcom message screen and the other one is going to the MCC_EVL_SINK. I am only receiving the Link Down event at that time. Within the screen output it's visible that the LINK_UP alarm rule is triggered by the Link Down event. ================================================================================ Note 3476.3 LINK DOWN event fires LINK UP rule 3 of 5 MOLAR::ROBERTS "Keith Roberts - DECmcc Toolkit Team" 12 lines 31-JUL-1992 13:22 -< Try the GETEVENT directive >- -------------------------------------------------------------------------------- Could you try using the GETEVENT directive please. MCC> getevent NODE * HDLC Link * Link Down and cause the link to cycle. Then check the Link Up event: MCC> getevent NODE * HDLC Link * Link Up and post the output. btw - these are the directives which Alarms is using to collect your data. /keith ================================================================================ Note 3476.4 LINK DOWN event fires LINK UP rule 4 of 5 HLFS00::TIMMERMANS_A 40 lines 3-AUG-1992 10:17 -< getevent output >- -------------------------------------------------------------------------------- Hello, This is the output of the getevents for link up and link down. Hope this helps, Adrie $ manage/enter DECmcc (V1.2.0) MCC> getevent node * hdlc link * Link Down Node KA500_NS:.dcabis HDLC Link W618-3-0 AT 3-AUG-1992 15:02:17 CONFIGURATION EVENTS Successfully received events: Event: Link Down <------ forced link down event by NCL MCC> getevent node * hdlc link * Link Up Node KA500_NS:.dcabis HDLC Link W618-3-0 AT 3-AUG-1992 15:03:31 CONFIGURATION EVENTS Successfully received events: Event: Link Down <------ forced link down event by NCL MCC> getevent node * hdlc link * Link Up Node KA500_NS:.dcabis HDLC Link W618-3-0 AT 3-AUG-1992 15:03:49 CONFIGURATION EVENTS Successfully received events: Event: Link Up <------ forced link up event by NCL The getevent node * hdlc link * link down is not triggered by the link up event. ================================================================================ Note 3476.5 LINK DOWN event fires LINK UP rule 5 of 5 MOLAR::ROBERTS "Keith Roberts - DECmcc Toolkit Team" 15 lines 3-AUG-1992 13:46 -------------------------------------------------------------------------------- RE: .4 You asked for the Link Up event, and got a Link Down Event > MCC> getevent node * hdlc link * Link Up > > Node KA500_NS:.dcabis HDLC Link W618-3-0 > AT 3-AUG-1992 15:03:31 CONFIGURATION EVENTS > > Successfully received events: > Event: Link Down <------ forced link down event by NCL This is not an Alarms problem. Looks like something from DNA phase 5 /keith