Cisco Systems OL-14253-01 appendix Object Creation

Appendix A Notifications, Fault Management, and Probable Cause Mapping

Supported Events

To improve throughput, you should receive the event and forward it to another thread for processing. For example:

void push_structured_event(StructuredEvent notification) { try {

some_other_thread_queue.addNotification(notification);

}catch (Exception ex) {

//catch all exception and ignore

ex.printStackTrace();

}

}

Caution As shown in the example, you must catch all exceptions, or you will stop receiving notifications.

A.4 Supported Events

The following sections list the attributes of each event.

A.4.1 Object Creation

The following table lists the object creation types and attributes.

Table A-3		Object Creation
	Attribute Name		Type		Supported by CTM?
	notificatId		string		Yes. The uniqueness and sequence of the notification ID are not
					guaranteed.
	objectName		globaldefs::NamingAttributes_T		Yes.
	objectType		notifications::ObjectType_T		Yes.
	emsTime		globaldefs::Time_T		Yes.
	neTime		globaldefs::Time_T		No.
	edgePoint		boolean		No.
		Object creation notifications are sent to the NMS for the objects in the following table.
Table A-4		Object Creation Notifications
	Object Type			Type Sent in remainder_of_body for Object Creation Event
	OT_MANAGED_ELEMENT			managedElement::ManagedElement_T
	OT_MULTILAYER_SUBNETWORK			multiLayerSubnetwork::MultiLayerSubnetwork_T
	OT_TOPOLOGICAL_LINK			topologicalLink::TopologicalLink_T
	OT_SUBNETWORK_CONNECTION			subnetworkConnection::SubnetworkConnection_T
	OT_EQUIPMENT			equipment::Equipment_T
	OT_PROTECTION_GROUP			protection::ProtectionGroup_T
			Cisco Transport Manager Release 8.5 GateWay/CORBA User Guide and Programmer Manual
	OL-14253-01					A-3