Cisco Cisco Prime Optical 9.5 Technical References
TM FORUM Implementation Statement (IS) Template and Guidelines
isClearable FIXED
perceivedSeverity
VALUE LIST
The EMS vendor (SP or NMS vendor)
should describe the criteria that are used
(required) when assigning a perceived
severity to a particular alarm.
should describe the criteria that are used
(required) when assigning a perceived
severity to a particular alarm.
layerRate VALUE
LIST
Service provider (vendor) should indicate the
required (supported) layerRates to which this
alarm type applies
required (supported) layerRates to which this
alarm type applies
granularity FIXED
pmParameterName
VALUE LIST
The EMS vendor (SP or NMS vendor)
should indicate the set support (required)
PM parameters.
should indicate the set support (required)
PM parameters.
pmLocation FIXED
thresholdType FIXED
value
FREE
unit
FREE
Version 3.0 Additions
acknowledge
Indication
Indication
2.1.6.3 AVCs, Object Creation/Deletion and Other Notifications
The second-level objects in the MTNM model are expected to emit Attribute Value Change (AVC), Object
Creation, Object Deletion, and State Change notifications. Table Error! No text of specified style in
document.-8 summarizes the notifications that are to be supported for the second-level objects. The table is
based on Section 6 of the MTNM Information Agreement. A party (vendor or service provider) using this
implementation statement should indicate any variances from the required MTNM notifications. A notification
compliance statement is to be included for each module (see, for example, Sections 2.5.3, 2.6.3, 2.8.3). The
notification formats are provided in a supporting document to the MTNM IDL Solution Set (the supporting
document is called Using the Notification and Log Services).
Creation, Object Deletion, and State Change notifications. Table Error! No text of specified style in
document.-8 summarizes the notifications that are to be supported for the second-level objects. The table is
based on Section 6 of the MTNM Information Agreement. A party (vendor or service provider) using this
implementation statement should indicate any variances from the required MTNM notifications. A notification
compliance statement is to be included for each module (see, for example, Sections 2.5.3, 2.6.3, 2.8.3). The
notification formats are provided in a supporting document to the MTNM IDL Solution Set (the supporting
document is called Using the Notification and Log Services).
Table Error! No text of specified style in document.-8. Notifications for Second-Level Objects
Notification
Type
Type
Notification Producers
Variations from the MTNM Interface
Specification
Specification
Object
Creation
Creation
Topological Link, Equipment, Equipment Holder,
Subnetwork, Traffic Descriptor, PTP, TP Pool,
Subnetwork Connection, Managed Element,
Protection Group
Subnetwork, Traffic Descriptor, PTP, TP Pool,
Subnetwork Connection, Managed Element,
Protection Group
(v3.0) ASAP, Equipment Protection Group, Group
Termination Point, Log, Transmission Descriptor
Termination Point, Log, Transmission Descriptor
Page 22 of 115
TeleManagement Forum 2007
TMF814Av3.1