Cisco Cisco Transport Manager 9.1 Technical References
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
TMF 814Av3.0
TeleManagement Forum 2003
6
attribute2
…
Conventions:
Set By – an indication of who can set the attribute. “NMS” means only the NMS can set the value,
“EMS” means only the EMS can set the value, and “E” means either the NMS or EMS can set the
value
“EMS” means only the EMS can set the value, and “E” means either the NMS or EMS can set the
value
Set When – an indication of when the attribute can be set. “C” (creation) means the attribute can
only be set when the managed object is created, “L” (lifespan) means the attribute is only set after
the managed object is created, and “A” (anytime) means the value can be set at birth or anytime
thereafter.
only be set when the managed object is created, “L” (lifespan) means the attribute is only set after
the managed object is created, and “A” (anytime) means the value can be set at birth or anytime
thereafter.
Format – the format of the attribute. Possible values are
“FREE” for Free Format (in this case the vendor or service provide may want provide their
supported/required format(s), e.g., CLLI™ codes for the nativeEMSName)
“FIXED” for Fixed Format (the format is defined in the IDL and must be used without
variance, and no additional clarification is needed by the vendor or service provider)
“VALUE LIST” for List (the attribute takes values from a typically long set of possible values
defined in the IDL, e.g., layerRate, pmParameterName). In this case, the vendor or service
provider may want to provide their supported/required set of values. VALUE LIST is used in
only a few places in the following tables. Basically, a VALUE LIST is a data type with a set of
supported values.
provider may want to provide their supported/required set of values. VALUE LIST is used in
only a few places in the following tables. Basically, a VALUE LIST is a data type with a set of
supported values.
These three categories are meant to be mutually exclusive.
Clarification Needed – in cases where an attribute may allow for various implementation options,
the EMS vendor should state how they are handling the option.
the EMS vendor should state how they are handling the option.
Remarks:
All parameters for second-level objects are readable by the NMS. Consequently, there is not a
column to indicate whether or not an attribute is readable.
column to indicate whether or not an attribute is readable.
2.1.3 Interfaces
There is one table for each interface.
Table 2-2. Interface Name, e.g., EquipmentInventoryMgr
Operation Status
Support Exception/
Error Reason
Comments
operation1
M or O
Y, N or C
Exception_Name <error reason
string>
operation2
…
CLLI and CLEI are trademarks of Telcordia Technologies.