Cisco Cisco Prime Optical 10.3 Technical References
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
4 Guidelines
This section covers guidelines concerning usage of the MTNM specifications. The intent is to describe, in
further detail, the more complicated and/or less constrained aspects of the MTNM specifications. For example,
the MTNM specifications state that subnetwork configuration is the responsibility of the EMS. Without further
information, the NMS vendor needs to design their NMS to anticipate any of a number of possible subnetwork
configuration schemes employed by various EMS vendors.
further detail, the more complicated and/or less constrained aspects of the MTNM specifications. For example,
the MTNM specifications state that subnetwork configuration is the responsibility of the EMS. Without further
information, the NMS vendor needs to design their NMS to anticipate any of a number of possible subnetwork
configuration schemes employed by various EMS vendors.
4.1 Implementation-specific Use Cases
The MTNM Business Agreement document provides use cases for many management activities, e.g., NMS
Provisions Alarm Monitoring Off, The NMS Creates a Subnetwork Connection, and Retrieval of Protection
Group by the NMS. These use cases are not prescriptive and allow for many options. For a particular
implementation of the NMS-EMS interface, it is recommended that the use cases be specialized and detailed in
order to ensure greater interoperability between the NMS and EMS. The use cases in the MTNM BA could
server as a basis for any product-specific use cases.
Provisions Alarm Monitoring Off, The NMS Creates a Subnetwork Connection, and Retrieval of Protection
Group by the NMS. These use cases are not prescriptive and allow for many options. For a particular
implementation of the NMS-EMS interface, it is recommended that the use cases be specialized and detailed in
order to ensure greater interoperability between the NMS and EMS. The use cases in the MTNM BA could
server as a basis for any product-specific use cases.
•
o In this case, the EMS (or the EMS GUI users) handles
4.2 EMS Subnetwork Configuration
In the MTNM model, the EMS decides how to package MEs into subnetworks. An understanding of how an
EMS packages MEs into subnetwork will facilitate inventory discovery on the part of an NMS. Some examples
concerning the packaging of the MEs within rings are as follows:
EMS packages MEs into subnetwork will facilitate inventory discovery on the part of an NMS. Some examples
concerning the packaging of the MEs within rings are as follows:
• The EMS packages each ring (SONET, SDH, or DWDM) into a separate subnetwork. Open rings are
packaged into separate subnetworks.
o In this case, the NMS will need to configure ring interconnection.
The EMS packages interconnected rings (having protected interconnection) into separate subnetworks
(this could lead large mesh subnetworks), and all other rings into individual subnetworks. Open rings
are packaged into separate subnetworks.
(this could lead large mesh subnetworks), and all other rings into individual subnetworks. Open rings
are packaged into separate subnetworks.
most of the configuration concerning ring
interconnection.
In the first case above, each ring (or open ring) is in a separate subnetwork. For example, consider the case
where a DSC is used to interconnect rings (say ring 1 and ring 2). The DSC is managed by one EMS and the
rest of each ring is managed by another EMS. In this case, the NMS needs to setup three SNCs to get an end-
to-end connection between a CTP in ring 1 and a CTP in ring 2. The SNCs in ring 1 and 2 would be of type
ST_SIMPLE and the SNC in the DSC would be of type ST_DOUBLE_INTERCONNECT.
where a DSC is used to interconnect rings (say ring 1 and ring 2). The DSC is managed by one EMS and the
rest of each ring is managed by another EMS. In this case, the NMS needs to setup three SNCs to get an end-
to-end connection between a CTP in ring 1 and a CTP in ring 2. The SNCs in ring 1 and 2 would be of type
ST_SIMPLE and the SNC in the DSC would be of type ST_DOUBLE_INTERCONNECT.
In the second case, the NMS only needs to request one SNC. In this case, the SNC type would be
ST_DOUBLE_INTERCONNECT. This case is easier for the NMS since it does not need to know much about
the internal structure of the mesh subnetwork (only needs to know that the mesh support DRI).
ST_DOUBLE_INTERCONNECT. This case is easier for the NMS since it does not need to know much about
the internal structure of the mesh subnetwork (only needs to know that the mesh support DRI).
In the event subnetwork configuration is done via the EMS GUI, the EMS vendor may simply provide guidelines,
suggestions and constraints concerning the configuration of subnetworks. In the event subnetwork configuration
is performed via fixed logic in the EMS, the EMS vendor would an explanation of how the EMS decides on
subnetwork packaging.
suggestions and constraints concerning the configuration of subnetworks. In the event subnetwork configuration
is performed via fixed logic in the EMS, the EMS vendor would an explanation of how the EMS decides on
subnetwork packaging.
TMF814Av3.1
TeleManagement Forum 2007
Page 87 of 115