Arthur Foster

Hillman House,  4, Madeira Road,

Parkstone,  Poole,  Dorset   BH14 9ET

UK

Description of GDMO
Notification Example

e-mail:

arthur@arthurfoster.com

tel: 

+44 (01202) 469468

fax:

+44 (01202) 469861

  

Home Site Map Search

Home Up Action Example Attribute Example Attribute Group Example Behaviour Example Managed Object Example Name Binding Example Notification Example Package Example Parameter Example

 

Notification Template
Event Report Operation

 

This example of a NOTIFICATION Template is taken from ITU-T Recommendation X.721.

The example is the communication alarm notification that is used in for communications alarms.

 

Notification Example

communicationsAlarm NOTIFICATION
	BEHAVIOUR   communicationsAlarmBehaviour;
	WITH INFORMATION SYNTAX Notification-ASN1Module.AlarmInfo
	AND ATTRIBUTE IDS
		probableCause		probableCause,
		specificProblems		specificProblems,
		perceivedSeverity		perceivedSeverity,
		backedUpStatus		backedUpStatus,
		backUpObject			backUpObject,
		trendIndication		trendIndication,
		thresholdInfo		thresholdInfo,
		notificationIdentifier	notificationIdentifier,
		correlatedNotifications	correlatedNotifications,
		stateChangeDefinition	stateChangeDefinition,
		monitoredAttributes		monitoredAttributes,
		proposedRepairActions	proposedRepairActions,
		additionalText		additionalText,
		additionalInformation	additionalInformation;
 
REGISTERED AS {joint-iso-ccitt ms(9) smi(3) part2(2) notification(10) 2};
 
communicationsAlarmBehaviour
	BEHAVIOUR
		DEFINED AS 
		"This notification type is used to report when the 
		object detects a communications error.";

 

The WITH INFORMATION SYNTAX field specifies an ASN.1 data structure that is carried in the arguments of the EVENT REPORT operation. This syntax includes the specification of the information that the agent system sends to the manager system. In this example the source of the ASN.1 data structure specification is identified as:

Notification-ASN1Module.AlarmInfo

This is known as a type reference. The type reference has two parts: 

  1. an ASN.1 module name, which identifies the ASN.1 containing the data structure to be employed; and,

  2. an ASN.1 type identifier which must be defined in that module (although it could be imported).

The ASN.1 module is named "Notification-ASN1Module" and the type identifier is "AlarmInfo" in this case.

The ASN.1 type used in notifications is always a sequence. Each of the components of the sequence identifies a component of the record that is used in the related EVENT REPORT and in the attributes of the related logRecord managed object class. The relationship of the components of the syntax to the attributes of the logRecord managed object class are specified in the AND ATTRIBUTES IDS clause. For example, the probableCause field of the AlarmInfo syntax is specified to be related to probableCause ATTRIBUTE of the related logRecord managed object class.

 

Author: Arthur Foster
28 May 2002

Arthur Foster is a

founder member of

 
 

Hosted by