Технические ссылки для Cisco Cisco Transport Manager 9.1

MTNM IMPLEMENTATION STATEMENT TEMPLATES AND GUIDELINES  

TMF 814Av3.0 

  TeleManagement Forum 2003 

9 

 

 

 

 

AlarmReporting, 
PotentialFuture 
SetupIndicator, 
TrailTraceActualTx, 
TrailTraceExpectedRx, 
TrailTraceMonitor, 
FrameFormat, LineCode, 
Mapping, SignalLabel 
ExpectedRx  

 

 Not 

supported 

 Not 

supported 

theSNC  

 

errorReason  

 

 

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.  

 

Table 2-5. Exception Table Example - getRoute 

EXCPT_NOT_IMPLEMENTED 

 

getRoute is supported in this hypothetical example. 
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.  

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.  

2. 

The EMS is undergoing scheduled system 
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