Cisco Cisco Prime Optical 9.8 Technical References
MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES
tpMappingMode
transmissionParams
AlarmReporting,
PotentialFuture
SetupIndicator,
TrailTraceActualTx,
TrailTraceExpectedRx,
TrailTraceMonitor,
FrameFormat, LineCode,
Mapping, SignalLabel
ExpectedRx
PotentialFuture
SetupIndicator,
TrailTraceActualTx,
TrailTraceExpectedRx,
TrailTraceMonitor,
FrameFormat, LineCode,
Mapping, SignalLabel
ExpectedRx
ingressTraffic
DescriptorName
Not
supported
egressTraffic
DescriptorName
Not
supported
theSNC
errorReason
2.1.5 Exceptions
The EMS may raise an exception in response to an MTNM operation request. The allowable exceptions are
defined in the IDL. The EMS may also provide an error reason in conjunction with an exception. The allowable
error reasons are not defined in the MTNM interface. It is proposed that the following table be used in cases
where the EMS supplier wishes to provide further information about their error reasons.
defined in the IDL. The EMS may also provide an error reason in conjunction with an exception. The allowable
error reasons are not defined in the MTNM interface. It is proposed that the following table be used in cases
where the EMS supplier wishes to provide further information about their error reasons.
Table Error! No text of specified style in document.-5. Exception Table Example - getRoute
Exception Error
Reason
Explanation
EXCPT_NOT_IMPLEMENTED
getRoute is supported in this hypothetical example.
So, this exception would never by used.
So, this exception would never by used.
EXCPT_INTERNAL_ERROR
1.
EMS is processing
other (higher priority
requests) and cannot
respond to getRoute
at this time.
other (higher priority
requests) and cannot
respond to getRoute
at this time.
2. EMS
undergoing
system maintenance
1.
In some cases, the EMS will reject requests if it
is processing higher-priority activities. The
NMS should try the request at a later point in
time.
is processing higher-priority activities. The
NMS should try the request at a later point in
time.
2.
The EMS is undergoing scheduled system
maintenance and cannot presently respond to
the request.
maintenance and cannot presently respond to
the request.
EXCPT_INVALID_INPUT
No error reasons are provided with this exception
EXCPT_ENTITY_NOT_FOUND
No error reasons are provided with this exception
2.1.6 Notifications
2.1.6.1 Alarms and Probable Causes
The MTNM team has not specified a set of alarms. The team has, however, defined a set of probable causes
and does allow for the definition of native probable causes (basically non-MTNM defined probable causes). An
alarm type may be uniquely identified by the combination of a probable cause, object type, and layer rate. In
and does allow for the definition of native probable causes (basically non-MTNM defined probable causes). An
alarm type may be uniquely identified by the combination of a probable cause, object type, and layer rate. In
TMF814Av3.1
TeleManagement Forum 2007
Page 19 of 115