Manualsbrain.com
  1. Manuals
  2. Brands
  3. Cisco
  4. Cisco Prime Optical 9.6
  5. Technical References

Cisco Cisco Prime Optical 9.6 Technical References

Download
Page of 115
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  
setAdditionalInfo O 
 
 
 
2.4.3 Notifications 
There are no specific notifications associated with the data types in this module.  
2.5 EmsMgr 
Module 
2.5.1 Data 
Types 
 
Table Error! No text of specified style in document.-14. EMS 
Attribute Name 
Set 
By 
Set When and How 
Format 
Clarification Needed 
name 
EMS 
C 
FREE 
The Value string that 
applies to the 
"ManagedElement", for 
example, can contain any 
string as long as it uniquely 
identifies the Managed 
Element within the EMS. 
The EMS supplier should 
indicate the maximum 
length of the attribute 
(same comments holds 
true for all attributes). 
userLabel 
E 
A – set by the EMS (C), 
or by the NMS via 
setUserLabel (L) 
FREE 
nativeEMSName 
E 
A – set by the EMS (C), 
or by the NMS via 
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. 
emsVersion 
EMS 
A – set at time of EMS 
initialization and is not 
expected to change very 
often 
FREE  
type 
EMS 
A – set at time of EMS 
initialization and is not 
expected to change very 
often 
FREE  
additionalInfo 
- 
- 
- 
Name/Value list defined by 
the EMS vendor. 
Also, extensions are 
included in additionalInfo.  
Version 3.0 Additions 
ASAPpointer 
E 
EMS (C), or by the NMS 
via assignASAP (L) 
FIXED  
TMF814Av3.1 
TeleManagement Forum 2007 
Page  27 of 115