[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

2207.0. "can#t receive event 4.18" by COL01::LUNT () Tue Jan 28 1992 08:26

Hi,

	I'm trying to set up the event logger. I have chosen
two NODE4 entities to try out. One is a workstation, the other a
Router. I followed the following procedure:

1. Create node4 bylu08 outbound stream bylv21 remote sink monitor class =0, 
   event type = (9)
2. Create node4 bylr01 outbound stream bylv21 remote sink monitor class =0,
   event type = (9)
3. Create node4 bylr01 outbound stream bylv21 remote sink monitor class =4,
   event type = (18)
4. enable opcom messages on a decterm, I can recieve all three events.
5. disable node4 bylv21 local sink monitor
6. set node4 bylv21 local sink monitor name mcc_dna4_evl
7. enable node4 bylv21 local sink monitor
8. notify domain <domain1> events=(counters zeroed), entity list =(node4 bylu08)
9. notify domain <domain2> events=(counters zeroed), entitz list =(node4 bylr01)
10. Both notifications fire when I zero the counters.
11. notify domain <domain2> events=(adjaceny down), entity list =(node4 bylr01
   circuit ethernet)
	Terminates with the following error message: No entities in this
	 domain support the requested events.
12. getevent node4 bylr01 circuit ethernet adjacent node * adjaceny down
	MCC then waits for an event to occur, I see the event occur on
	my decterm, but mcc doesn't recieve it.
13. getevent node4 bylr01 
	I get the an event id missing error although the documenation
	says this should prompt me with a EVENTS:?

Note 1720 talks about event 4.18 causing the MCC_dna4_evl logging
process to stop in V1.1. Are there known bugs in t1.2.4 about event
4.18?

	Thanks in advance, Julie Ann
T.RTitleUserPersonal
Name
DateLines
2207.1try these entity specifiersTOOK::JEAN_LEETue Jan 28 1992 17:3453
Hi,

>>8. notify domain <domain1> events=(counters zeroed), entity list =(node4 bylu08)
>>9. notify domain <domain2> events=(counters zeroed), entitz list =(node4 bylr01)
						       ^^^^^^
	is this a typo?  you meant entity, right?

	If you failed to receive Event counter zeroed or Event automatic 
	counters under a "node4" entity, try this entity specifier:

		node4 bylu08 remote node bylu08

	This is because Node4 sees itself as both the Executor node, and as 
	a Remote Node.  Once a node4 has had a connection to itself during 
	the current network session, the counter information is retuned as 
	the Executor Node's view of itself as a remote node.  These 
	events are now returned by DECmcc under a remote node entity.

>>11. notify domain <domain2> events=(adjaceny down), entity list =(node4 bylr01
>>	circuit ethernet)
>>	Terminates with the following error message: No entities in this
	 domain support the requested events.

	This is because (adjacency down) is an event under this entity:

		node4 bylr01 circuit ethernet adjacent node <>

>> 12. getevent node4 bylr01 circuit ethernet adjacent node * adjaceny down
>>	MCC then waits for an event to occur, I see the event occur on
>>	my decterm, but mcc doesn't recieve it.

	Yes, a bug related to 4.18 event (adjacency down) is found in 
	V1.2 FT kit.  It is already fixed.

>> 13. getevent node4 bylr01 
>>	I get the an event id missing error although the documenation
>>	says this should prompt me with a EVENTS:?

	Yes, it should prompt you with this message:

		Type ? for a list of valid event IDs
		Event:

	But if you type CR at this point (maybe, by accident), you will
	get "event ID is missing" message.  

	Can you try it again, make sure you type ? instead of CR.

	Hope it helps.

	Jean


2207.2use config eventsTOOK::CALLANDERMCC = My Constant CompanionFri Jan 31 1992 13:367
    PLEASE NOTE: NOTIFY is having a problem with parsing 
    adjacency down, I am working on the fix. For now please
    use "any configuration events" to get that one.
    
    (thanks to the people in this conference for finding the
    bug!)