|
|
An Autonomous message is a message that is sent from the NE to the appropriate OS without having an explicit input message associated with it. Typical scenarios where Autonomous messages are used include
Reporting of alarmed or non-alarmed trouble events.
Reporting of scheduled diagnostic tests in the NE.
Reporting of Performance Monitoring data.
Reporting of a change in the NE's database.
Periodic reporting of selected NE conditions.
This topic explains the different blocks which form the Autonomous Message and the steps involved in configuring the autonomous message in TL1 Agent Simulator.
The general structure of a TL1 Autonomous message is given below. Here the text block is the optional field and all other fields are essential.
|
<header> <auto id> [ <text block> ] <terminator> |
The Header represents the information common to all output responses and autonomous messages. It contains System identifier <sid>,date, and time stamps.
|
<cr><lf><lf>^^^<sid>^<year>-<month>-<day>^<hour>:<minute>:<second> |
It contains System identifier <sid>, date, and time stamps.<sid> is restricted to 20 characters maximum and identifies the NE generating the message. The syntax of <sid> is any TL1 identifier or text string. The <year><month><day>
construct represents the day in which the output response is generated. The <hour><minute> <second> construct represents the time at which the output response is generated.
The AutoID indicates the severity and the nature of the Autonomous message. The <Auto id> entry for an autonomous message is of the form:
|
<cr><lf> <almcde>^<atag>^<verb>[^<modifier>[^<modifier>]] |
<almcde> is the alarm code. It can be any of the following based on the severity of the autonomous message. Valid values in decreasing order of severity are
*C - Critical Alarm
** - Major Alarm
* - Minor Alarm
A - Non-Alarm Message
<atag> is the Autonomously Generated Correlation Tag. It is assigned by the NE. Must be sequential and must be included in all autonomously generated messages. It allows an OS to correlate spontaneous outputs triggered by a common problem and also to identify whether the OS has failed to receive any output.
<verb>[^<modifier>[^<modifier>]] entry identifies the nature of the spontaneous output . The first identifier is a required entry and indicates the message verb. The autonomous message can have two optional modifiers separated by space character.
The optional [<text block>] is used to represent information specific to the particular autonomous message. The format of the text block is as follows:
|
(<cr><lf>^^^<unquoted line>)|(<cr><lf>^^^<quoted line>)|(<cr><lf>^^^<comment>) |
It consists of three components, namely unquoted line, quoted line, and comment. Both quoted and unquoted lines consists of text that is parsable, while comment is not.
The semi-colon character (;) terminates a TL1 Autonomous message. The terminator block has the form <cr><lf> ( ; | >) . This is required for all TL1 message types.
Enable/Disable TL1 Autonomous Message Service
The TL1 Agent Simulator/ Network Simulator provides option to enable/disable the execution of autonomous messages configured in the TL1 agent, at agent runtime. If autonomous message service is disabled, the agent will not check for autonomous message configurations before sending the response. Hence , you can use this option to improve the performance of the TL1 agent, if autonomous messages are not required to be executed.
By default, the service is enabled and the autonomous messages configured (if any), will be executed. To disable the service,
Select Operations -> Initialize Services in TL1 Agent Simulator or select Run-> Initialize Service in Network Designer.
The Initialize Service dialog is displayed.
Deselect "Enable TL1 Autonomous Message Service".
Start the Agent. Now, the autonomous messages configured in the simulator will not be executed.
|
|
Note: The options in the Initialize Services dialog will be disabled when the TL1 agent is started. |
Configuring Values for Autonomous Code
The Autonomous message comprises of the Alarm code and Text Block combination. The TL1 Agent Simulator supports to configure any number of Alarm code and Text block combination for a single Autonomous code .
To configure the TextBlock for the Autocode,
Select the required Autonomous code from the loaded TCS file (as .tcs file or .prp configuration file format). The dialog on the right side provides options to select the required Alarm Code and configure Text Blocks for the selected Autonomous command.
|
|
Note: You can configure any number of Alarm code and Text block combination for a single command. The Alarm Description list box is used to identify the Alarm code and Text block combination. |
Click the Add button of the Alarm Description list box. Enter the value for Alarm Description and click OK, to add to the list. You can add any number of alarm description to the list.
Select a Alarm Description from the list, for which the Alarm Code, Text Block combination must be defined.
Select the Alarm Code from the values listed in the combo box.
To configure Text block, click Add button of the Configure Text Block. The ConfigureParamValues dialog is displayed. The Response Line type displays the textblock type, as defined in the tcs file. The text block type may be quoted, unquoted or commented. The Parameter name and Parameter type defined for the Autonomous message is listed with default values. Enter the required parameter values and click OK, to add the text to the list. You can configure any number of text blocks.
Example
Select the Autonomous code, REPT ALM EQPT defined in Acme-MSU.tcs file.
Click the Add button of the Alarm Description list box. Enter the value for Alarm Description as A1 and click OK, to add to the list. You can add any number of Alarm descriptors to the list.
Select the Alarm Description A1 from the list, for which the Alarm Code, Text Block combination must be defined.
Select the Alarm Code as Major from the values listed in the combo box.
To configure Text block, click Add button of the Configure Text Block. The ConfigureParamValues dialog is displayed. Enter the following parameter values :
i. aid : SLOT-7
ii. ntfcncde : MJ
iii. conditiontype :HITEMP
6. Click OK to add the above values to the text block. Now, the screen will look like this :
Configuring Request-Based Autonomous Messages
The TL1 Agent Simulator supports to generate Request Based Autonomous Messages, by configuring Autonomous code and Alarm Descriptor for the selected Input Command Code , Command Code - AID or Command Code - AID - MPB combinations. When a request is made for the Command , Command Code - AID or Command Code - AID - MPB, on which the message is configured, the NE sends the configured Autonomous message to the OS concerned.
To configure Request based Autonomous messages,
Select Configure -> Request Based Autonomous Message from the menu bar or the icon from the toolbar. The Request Based Autonomous Message dialog is displayed.
Click Add button to configure a new Request Based Autonomous Message.
You have the option to configure Request Based Autonomous Message at the following levels.
To configure request based autonomous message for a command code, select the required command code.
To configure request based autonomous message for a Command code - AccessID combination,
Select the required command code. The Access ID configured for the selected command is displayed on the right-frame.
Select the required Access Id.
To configure request based autonomous message for a Command code - Access ID - Message Pay load combination,
Select the required command code. The Access ID configured for the selected command is displayed on the right-frame.
Select the required Access Id. Selecting the AccessID, will display the Message Payload configured.
Select the required Message Payload.
Browse and select the required Autonomous Code from the Autonomous Code dialog. Selecting the autonomous code will display the Alarm Descriptors configured for the code. Select the required Alarm Descriptor and click OK.
Click OK to add the selection to the list.
Click Close to exit from the dialog.
Example
Configure a Request based autonomous message for the Input Command RTRV-EQPT with autonomous code REPT ALM EQPT and Alarm Descriptor A1, as shown in the screen-shot below and click OK to add the entry to the list.
Perform a Retrieve operation from TL1 Craft Interface or from any other TL1 manager applications for Command Code RTRV-EQPT defined in Acme-MSU.tcs . The NE responds to the request and sends the configured Autonomous message, as shown in the screen shot below:
Configuring Timer-Based Autonomous Messages
The TL1 Agent Simulator supports to generate Timer-Based Autonomous Messages by configuring Autonomous code and Alarm descriptor for a specific date and time. These messages are generated at the configured time.
Select Configure -> Timer Based Autonomous Message from the menu bar or the icon from the toolbar. The Timer Based Autonomous Message dialog is displayed.
Click Add button to configure Autonomous code, alarm descriptor, and timer details.
The Configure Timer Based Autonomous Message dialog opens with the Autonomous Code defined in the TCS file, displayed on the top portion of the dialog. Selecting an Autonomous code, will display the Alarm descriptors configured for the selected Autonomous code.
Select the Alarm Descriptor for the Autonomous code.
Enter the Timer Details.
Timer Details
Staring Time : Configure the date and time at which the simulator will start sending Autonomous messages..
Periodically send : Check this option to send Autonomous message on a periodical basis. Specify the duration of the message to be sent as once in number of hour(s) / day(s).
Total Messages : Specify the total number of messages that you want to send. Eg: 100.
Time Interval : You can also specify the time interval between the messages that are to be sent. The time interval option is available in Milliseconds. Example: 1000 Milliseconds.
Click Ok to add the configuration to the list.
Click Close to exit from the dialog.
Example
The Autonomous code, REPT ALM EQPT is defined in Acme-MSU.tcs file. In the TL1 Simulator, the Autonomous code REPT ALM EQPT is selected and the following configuration is made: Alarm Code : Critical, TextBlock : Default Text Block
The above autonomous message with Autonomous code REPT ALM EQPT , Alarm Code Critical, and the Text Block must be sent at a specified time. This is defined using Configure -> Timer Based Autonomous Message option, as shown in the screen shot below.
You have configured Total messages as 3 with a timer interval of 5000 milliseconds and choose to periodically send it once in 5 days.
The above configuration will generate 3 messages with a time interval of 5 seconds each, once in 5 days, starting from the Date and Time specified. The timer based autonomous message can be viewed from the TL1 craft interface as shown in the screen shot below:
Deleting Request/Timer Autonomous Messages
The TL1 agent simulator provides option to delete the configured Request-based/Timer-based Autonomous messages.
To delete Request-based Autonomous messages,
Select the configuration to be deleted from the Request Based Autonomous Messages dialog.
Click Delete, to delete the configuration .
To delete Timer-based Autonomous messages,
The TL1 agent simulator provides option to delete the configured timer based autonomous messages. To delete request based autonomous messages,
Select the configuration to be deleted from the Timer Based Autonomous Messages dialog.
Click Delete, to delete the configuration
|
|
