[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

2576.0. "Circuit AM Event alarming" by SEDSWS::MALLOY () Mon Mar 16 1992 18:49

	Alarm Circuit Events
	=====================


I have created a circuit called FI_BR.
And associated a node4 circuit with it.


mcc> set circuit FI_BR aendpointname=(instance=node4 .titan circuit sva-0,
objectid=%x7777,objectname=.titan_sva0)

Setup several alarm rules  for the circuit FI_BR.
char
----
expression=occurs(circuit mcc_ns:.FI_BR aendpointcheanged) 
severity major
probable cause unknown
target oject Not returned

expression=occurs(circuit mcc_ns:.FI_BR componentcheanged) 
severity critical
probable cause unknown
target oject Not returned

expression=occurs(circuit mcc_ns:.FI_BR NMFadminstrativestatechanged) 
severity minor
probable cause unknown
target oject Not returned

expression=occurs(circuit mcc_ns:.FI_BR NMFoperationalstatecheanged) 
severity major
probable cause unknown
target oject Not returned

In the documentation page 3.29 is really critical page for setting up
alarm of course is to be supplied "nuts".

TESTING TIME
-----------
I then switch off/on the line sva-0. The node TITAN iconic changed colour as
per  event alarm rules on node4 titan circuit sva-0.

But the circuit FI_BR remain green.
 I thought the circuit rule aendpointchanged when of fired, not a hope.	
 Or maybe componentchanged .Sorry NOT a dicky bird

I then changed the the circuit adminstration state to unlock and
then to locked. Decnet event circuit sva-0 unsync.
 Check NCP>show circuit sva-0 sta      "off"

The alarm rule counter for adminstrativestatechanged incremented.
But circuit iconic remain green.
 "error message exception occured"


AM I going crazy or have I made a complete mess?

Or is BL15 not working correctly......

PS
	I would be great if circuittype could also include "Ethernet"

	set circuit br_fi circuittype=(mode=dedicated,type=dna4 ddcmp circuit)
								/\
								|
						ethernet--------!

	I know only few people use ethernet

		
		Time for BED
		`	GARY
T.RTitleUserPersonal
Name		DateLines
2576.1NANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamTue Mar 17 1992 08:0221
RE: .0

  Gary,

  Could you enable Notification Services so you will get a list when each
  Alarms Rule Fires?

  You can do this from the Iconic Map (under the applications pull-down)
  run the FCL interface in another window (on the same system) and use the
  notify directive:

	notify domain <domain-name>

  Where <domain-name> is the where your circuit and alarms rules are stored.

  ---------

  Each Alarms Rule Fired (or exception) event which Alarms detects will be
  listed by Notification Services.

  /keith
2576.2set notification "Recieved error message"SEDSWS::MALLOYThu Mar 19 1992 13:0438
	Keith


	I enable notification as requested.


Switch line SVA-0 off/on

	The node iconic changed colour as per Node4 circuit SVA-0 alarm
rule.
	These alarm events were display on the notification window.

Again
	The circuit rule failed to fire. (No notification)

Next
====

	I then changed the state of the circuit administrative state to unlocked
to locked. The circuit SVA-0 when down

	The alarm rule of adminstrativechange fired as counter
evaluation true increased to 1.
	There was no notification just two error messages

ONE message on a error message window

"notify request 1 from domain Gary encounter an error
%MCC-E-ILVINE , specified not found within current constructor"

One  error message on decterm which activated the Iconic Map

"MCC_NS_OCC_CREATE
Unexpected error 52875178 decoding response from request 1" 

		Gary Malloy
		dtn 7844 3308
2576.3This may be the problem with Alarms and Event Id codesNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamFri Mar 20 1992 10:548
  This may be the same seen elsewhere in this conference.

  Alarms has a problem with the occurs function, in the way it
  passes the event id code to the target MM (in this case the Circuit AM).

  Try using 'any event' inplace of the event name.

  /keith
2576.4Crircuit Am is total mess when it comes to alarming SEDSWS::MALLOYFri Mar 20 1992 13:2124
Keith
	I appreciate what you are saying but there were four alarm rule
setup for this CIRCUIT.
	
	But only one fired and it caused an exception. 

Event Names

	aendpointcheange
	componentcheanged
	NMFadminstrativestatechanged----->fired--->exception
	NMFoperationalstatecheange



I will try the other events for CIRCUIT AM



	
			Gary Malloy
			(DTN 7744 3308)
2576.5NANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamFri Mar 20 1992 13:2811
> I appreciate what you are saying but there were four alarm rule
> setup for this CIRCUIT.

  Because the Event code that Alarms passes to the Circuit AM is not
  being processed correctly (by Alarms), anything is possible.

	Garbage In ==> Garbage Out

  This problem is on the list of things to fix for 1.2 

  /keith