Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Referencia técnica

Descargar
Página de 23
3
a.
Set information—The simplest type of messages are those that set information or instruct the 
NE to perform an action and return only a result with no data in the response:
Example: ENT-CRS-<STS_PATH> to create an STS cross-connection
b.
Get information—Some TL1 commands get information or request information be returned 
from the NE.
Example: RTRV-ALM-ALL to show the current status of all active alarm conditions
c.
Response message—The response portion of a command message correlates to a particular 
request message. If a command is successful, the NE sends a response message containing the 
COMPLD code.
Example:    
   SV192-DATA-461 2003-08-05 10:35:17
M  123 COMPLD
;
If a command fails, the NE sends an error response which includes the DENY code and may 
or may not contain an error message.
Example:    
   SV192-DATA-461 2003-08-05 10:35:17
M  123 DENY
;
The following list shows standard responses:
COMPLD—Completed
DENY—TL1 command failed
PRTL—Partially successful response. The requested action can be completed for some of the 
specified AIDs but not for all of them.
RTRV—The response is successful but is lengthy and is being returned in multiple parts. Each 
part has a RTRV response code, but the final response has a COMPLD response code.
d.
Response acknowledgment—Responses may also include intermediate acknowledgment 
messages. Brief messages that update the user as to the status of a given command are called 
acknowledgments. When a command has been sent to the NE and the NE takes longer than 
two seconds to respond, the NE sends an acknowledgment message to be followed later by 
the full response. This class of responses, however, is yet to be supported by Cisco ONS 
platforms.
2.
Autonomous messages—These messages are used to report alarms, configuration changes or 
condition changes. Many of these messages, such as those relating to alarm conditions, are 
spontaneously triggered by the NE itself without intervention. Other messages, such as those 
relating to the reporting of periodic condition states or performance data values are scheduled by 
the NE user via other commands. Autonomous messages are not issued to the NE and hence they 
do not include input formats or input examples.