Cisco Cisco Transport Manager 9.1 Technical References
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
TMF 814Av3.0
TeleManagement Forum 2003
5
2 FUNCTIONAL INTEROPERABILITY STATEMENTS (FIS)
2.1 Overview
This section provides Functional Interface Statement (FIS) templates for the data structures
(those that represent objects in the information model), operations and notifications in the MTNM
Phase II IDL. These templates related to the functional aspects of the operations, notifications
and data structures, i.e., whether or not particular capabilities are supported. The non-functional
aspects of the operations, notifications and data structures are discussed in Section 2. Functional
aspects relate to what an entity does, and non-functional aspects related to how an entity
provides its functionality, e.g., how fast an operation request is fulfilled on average.
(those that represent objects in the information model), operations and notifications in the MTNM
Phase II IDL. These templates related to the functional aspects of the operations, notifications
and data structures, i.e., whether or not particular capabilities are supported. The non-functional
aspects of the operations, notifications and data structures are discussed in Section 2. Functional
aspects relate to what an entity does, and non-functional aspects related to how an entity
provides its functionality, e.g., how fast an operation request is fulfilled on average.
2.1.1 FIS Template
The following FIS templates are used for each module:
Module Name, e.g., Equipment
Data Types
A template (in the form of a table) needs to be provided for each second-level object
associated with the module. The data type template has one row for each attribute of the
second-level object.
associated with the module. The data type template has one row for each attribute of the
second-level object.
Interfaces
A template (in the form of a table) needs to be provided for each interface associated with
the module. The interface template has one row for each operation comprising the
interface.
the module. The interface template has one row for each operation comprising the
interface.
Notifications
A template (in the form of a table) needs to be provided for each notification associated
with the module. The notification template has one row for each parameter of the
notification.
with the module. The notification template has one row for each parameter of the
notification.
The individual components of the FIS template are explained in the following subsection.
2.1.2 Data Types
There is one table for each second-level object defined in the module.
Table 2-1. <Name of Data Type, e.g., Managed Element>
Attribute Name
Set By
Set When and How
Format
Clarification Needed
attribute1, e.g.,
userLabel
userLabel
EMS,
NMS or E
to indicate
either
Set When: C, L, A (see the note
below for definition of these
abbreviations)
below for definition of these
abbreviations)
Set How: List operations that can
be used to set the attribute’s
value. Typically, this field would
only be included if the attribute is
settable by the NMS.
be used to set the attribute’s
value. Typically, this field would
only be included if the attribute is
settable by the NMS.
FREE, FIXED, or
VALUE LIST (see the
note below for
definition of these
abbreviations)
The EMS supplier
should state the
maximum length for
the attribute. The
NMS supplier should
also mention any
length requirements.
should state the
maximum length for
the attribute. The
NMS supplier should
also mention any
length requirements.