Cisco Cisco Transport Manager 9.1 テクニカルリファレンス
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
TMF 814Av3.0
TeleManagement Forum 2003
11
It allows several alarms to be sent from the same object, with the same probable cause, while still
remaining identifiably different. (The alternative would be to manage unique values of the
notification identifier, but some EMS vendors have problems with that.)
remaining identifiably different. (The alternative would be to manage unique values of the
notification identifier, but some EMS vendors have problems with that.)
Note that probableCause qualifier is not necessarily human readable, as its real purpose is to
satisfy the second point. For instance, if the EMS works internally with a GDMO model, then it
might use a GDMO probableCause and specificProblems attribute values (which are sequences
of integers, not very exciting to read). The additionalText parameter is there to tell the human
operator what is going on.
satisfy the second point. For instance, if the EMS works internally with a GDMO model, then it
might use a GDMO probableCause and specificProblems attribute values (which are sequences
of integers, not very exciting to read). The additionalText parameter is there to tell the human
operator what is going on.
Example 1:
Consider a vendor that has a line terminal NE that issues the following native alarms from the
same termination point and layer rate:
same termination point and layer rate:
DegradedSignal
fecUncorrectedBlocks
(meaning that our Reed-Solomon Forward Error Correcting algorithm
has rejected some frames)
Both these alarms are mapped to the generic probable cause BER_SD (i.e., "signal degraded").
The probableCauseQualifier, nativeEMSProbableCause and possibly the additionalText
parameters distinguish between the two. Note that this saves one the trouble of going to TM
Forum MTNM standards group and asking for a new probableCause value, and even better, it
saves the NMS vendor the trouble of managing a new fault condition which from their point of
view is equivalent to the other one ("a difference that makes no difference is no difference").
The probableCauseQualifier, nativeEMSProbableCause and possibly the additionalText
parameters distinguish between the two. Note that this saves one the trouble of going to TM
Forum MTNM standards group and asking for a new probableCause value, and even better, it
saves the NMS vendor the trouble of managing a new fault condition which from their point of
view is equivalent to the other one ("a difference that makes no difference is no difference").
Example 2:
Just consider all the equipment alarms that can be generated by all the equipment vendors. The
MTNM interface designers intentionally use a single probableCause value “EQPT” for all of them.
The implication is that it is not expected for the NMS to discriminate between hundreds of
equipment conditions.
MTNM interface designers intentionally use a single probableCause value “EQPT” for all of them.
The implication is that it is not expected for the NMS to discriminate between hundreds of
equipment conditions.
2.1.6.2 Threshold Crossing Alerts (TCAs)
One TCA template should be provided for each supported (or required) PM parameter for which
the vendor supports thresholding or the service provider requires thresholding. As was the case
for the probable cause template, a single Threshold template can cover several types of TCA
(one TCA for each layer rate associated with a PM parameter). It should be noted that for a given
PM parameter some parameters in the template may vary based on the layer rate.
the vendor supports thresholding or the service provider requires thresholding. As was the case
for the probable cause template, a single Threshold template can cover several types of TCA
(one TCA for each layer rate associated with a PM parameter). It should be noted that for a given
PM parameter some parameters in the template may vary based on the layer rate.
Table 2-7. Threshold Template
Parameter Format
Comments/
Clarifications
notificationId
FREE
The notificationId is not guaranteed to be
unique. However, if a vendor does
support unique Ids, this should be noted.
unique. However, if a vendor does
support unique Ids, this should be noted.
objectName FIXED
nativeEMSName FREE