Cisco Cisco Transport Manager 9.1 Technical References

Page of 151
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  
TMF 814Av3.0 
  TeleManagement Forum 2003 
75 
gtpConnectionState EMS  A 
FIXED 
 
additionalInfo 
Name/Value list defined by 
the EMS vendor. 
Also, extensions are 
included in additionalInfo.  
Version 3.0 Additions  
ASAPpointer 
EMS (C), or by the NMS 
via assignASAP (L) 
FIXED  
NetworkAccessDomain 
EMS (C), or NMS via 
createGTP(C) or 
setAdditionalInfo (L) 
FREE  
 
2.22.2  Interfaces 
There are no interfaces in the subnetwork connection module other than Termination Point 
iterator and the GTP iterator. The TP iterator is used to retrieve a large number of TPs, a batch at 
a time. The GTP iterator is used to retrieve a large number of GTPs, a batch at a time. 
2.22.3  Notifications 
To be provided by the organization preparing an interoperability statement 
2.23  Topological Link Module 
2.23.1  Data Types  
Table 2-51. Topological Link  
Attribute Name 
Set By 
Set When and How  
Format 
Clarification Needed 
name 
EMS 
FREE 
This field has two tuples. 
The first tuple is for the 
EMS. The second is for the 
topological link. The value 
in the second tuple is the 
same as the 
nativeEMSName field 
except for Y-cable links, 
which will have “::1” and 
“::2” appended to the 
nativeEMSName to identify 
the two legs of the Y-cable 
link. 
 
userLabel E 
C  FREE 
nativeEMSName E 
FREE 
(e.g. 
CLEI 
code) 
nativeEMSName is a string 
and the naming convention 
is described in the CORBA