Технические ссылки для Cisco Cisco Transport Manager 9.1
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
TMF 814Av3.0
TeleManagement Forum 2003
100
Identifiers
The “official” MTNM identifiers are used, such as “OT_PHYSICAL_TERMINATION_POINT”
instead of abbreviations, e.g., “PTP”. The latter would make for a more legible table of course, but
a set of abbreviations is not currently available. The worst problem is with the layer rates: if one
just gives the value (e.g., "22") it will not be understood. Unfortunately, the complete strings are
fairly long, e.g., "22 = LR_Section_OC48_STS48_and_RS_STM16".
instead of abbreviations, e.g., “PTP”. The latter would make for a more legible table of course, but
a set of abbreviations is not currently available. The worst problem is with the layer rates: if one
just gives the value (e.g., "22") it will not be understood. Unfortunately, the complete strings are
fairly long, e.g., "22 = LR_Section_OC48_STS48_and_RS_STM16".
Different kinds of Probable Causes:
The example shows the kind of relationships that can exist between (MTNM) Probable Cause,
Native Probable Cause, and Probable Cause Qualifier:
Native Probable Cause, and Probable Cause Qualifier:
One (MTNM) Probable Cause value may correspond to several Native Probable Cause
values
One Native Probable Cause Value may correspond to several Probable Cause Qualifier
values - or to none at all.
Additional Text:
The strings shown in Probable Cause Qualifier (which is not displayed to NMS operator) can also
used as Additional Text (which is displayed). This is not a general rule, but it is allowed by the
MTNM model. The example itself does not include Additional Text.
used as Additional Text (which is displayed). This is not a general rule, but it is allowed by the
MTNM model. The example itself does not include Additional Text.
Additional Info and ITU alarm coding:
The X.733 Event Type is used an example of Additional Info.
The rules for doing this are set out in the "Notification Service Usage" supporting
document to the IDL.
Note that this is optional both for EMS to produce and for NMS to take into account. This
only makes sense if both EMS and NMS actually use X.733 alarm format internally.
The table gives examples of the four X.733 Event Type values applicable for MTNM
Alarms (Communications Alarm, Equipment Alarm, Environmental Alarm and Processing
Error Alarm). The last Event Type value is Quality Of Service Alarm, which is the same
thing in practice as a TCA, even if they are defined differently.
Error Alarm). The last Event Type value is Quality Of Service Alarm, which is the same
thing in practice as a TCA, even if they are defined differently.
One difference between MTNM and ITU alarm management principles is in "software" or
"processing error" faults:
"processing error" faults:
ITU "Processing Error Alarm" Event Type corresponds to software problems in general,
wherever they occur.
The assumption here is "software" type problems in NEs are given a (MTNM) Probable
Cause value "EQPT". Such problems can occur, since NEs perform information
processing. However, the same kind of error in the EMS is given a (MTNM) Probable
Cause value "EMS".
processing. However, the same kind of error in the EMS is given a (MTNM) Probable
Cause value "EMS".