Cisco Cisco Prime Optical 10.3 Technical References

Page of 115
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  
Object 
Deletion 
Topological Link, Equipment, Equipment Holder, 
Subnetwork, Traffic Descriptor, PTP, TP Pool, 
Subnetwork Connection, Managed Element, 
Protection Group  
(v3.0) ASAP, Equipment Protection Group, Group 
Termination Point, Log, Transmission Descriptor 
 
Attribute Value 
Change (AVC)  
Topological Link, Equipment, Equipment Holder, 
Subnetwork, Traffic Descriptor, PTP, CTP, TP 
Pool, Subnetwork Connection, Managed Element, 
Protection Group, EMS 
(v3.0) ASAP, Equipment Protection Group, Group 
Termination Point, Log, Transmission Descriptor 
 
State Change 
Equipment Holder, Equipment, PTP, CTP, 
Subnetwork Connection, Managed Element, 
Protection Group 
(v3.0) Equipment Protection Group, Group 
Termination Point, Log 
 
 
2.2  Alarm Severity Assignment Profile (v3.0) 
2.2.1  Data Types  
Table Error! No text of specified style in document.-9. ASAP 
Attribute Name 
Set 
By 
Set When and How 
Format 
Clarification Needed 
name EMS 
FREE 
 
userLabel 
A – set by the EMS (C), 
or by the NMS via 
createASAP (C) or 
setUserLabel (L) 
FREE 
nativeEMSName 
A – set by the EMS (C), 
or by the NMS via 
createASAP (C) or 
setNativeEMSName (L) 
FREE (e.g. CLEI 
code) 
owner 
NMS 
L – setOwner  
FREE 
As noted in Section 
4.3, userLabel, owner, 
nativeEMSName can 
be used in a variety of 
ways. The EMS 
vendor (SP) should 
describe their 
particular usage of 
these attributes. 
notModifiable EMS 
C FIXED 
 
alarmSeverityAssignmentList 
A – set by the EMS (C), 
or by the NMS via 
createASAP (C) or 
modifyASAP (L) 
FREE 
EMS supplier should 
indicate range of 
possible value 
additionalInfo - 
- - 
Name/Value 
list 
defined by the EMS 
vendor. 
Also, extensions are 
included in 
additionalInfo.  
 
2.2.2 Interfaces 
There is the ASAPIterator interface which is used to retrieve a large number of ASAPs (one batch at a time). 
TMF814Av3.1 
TeleManagement Forum 2007 
Page  23 of 115