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

Cisco Cisco Prime Optical 10.6 Technical References

Download
Page of 115
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  
2.18  MTNM Version Module 
2.18.1  Data Types  
This module has no data types that represent second level objects. 
2.18.2 Interfaces 
Table Error! No text of specified style in document.-44. Version 
Operation Status 
Support 
Exception/ 
Error Reason  
Comments 
getVersion M 
 
 
 
2.18.3 Notifications 
There are no specific notifications associated with the data types in this module.  
2.19 MultiLayerSubnetwork Module 
2.19.1  Data Types  
Table Error! No text of specified style in document.-45. MultiLayerSubnetwork 
Attribute Name 
Set 
By 
Set When and How 
Format 
Clarification Needed 
name EMS 
C 
FREE 
 
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. 
subnetworkType EMS 
C 
FIXED 
(e.g., 
TOPO_SINGLETON) 
 
supportedRates 
EMS 
A 
VALUE LIST (e.g., 
LR_Low_Order_TU3_VC3, 
LR_STS1_and_AU3_High_
Order_VC3, 
LR_STS3c_and_AU4_VC4) 
 
additionalInfo 
- 
- 
- 
Name/Value list defined by 
the EMS vendor. 
Also, extensions are included 
in additionalInfo.  
For v3.5 the following 
elements are specified: 
RoutingAreaLevel, 
SuperiorMLRA, 
LayeredRoutingAreaIdList, 
SupportingMEName, 
SRGNode 
Version 3.0 Additions  
NetworkAccess 
Domain 
E 
EMS (C) or NMS via 
setAdditionalInfo (L) 
FREE  
TMF814Av3.1 
TeleManagement Forum 2007 
Page  49 of 115