ADTRAN 4200659L2 User Manual
1.66 Mb

Chapter 9 Transaction Language 1 (TL1)


Transaction Language 1 (TL1) is a BELLCORE standard used in the input and output messages that pass between Operations Systems (OS) and Network Elements (NE) in telecommunication networks. It was developed to standardize equipment surveillance and memory administration, and to test with a common format.

This release of TL1 primarily supports the interactive and autonomous retrieval of system events as part of a valid TL1 session.


TL1 is an ASCII-basedlanguage that supports both commandresponse and autonomous (NE) message generation. Commonly, TL1 is used over a X.25 packet network but is completely independent of any physical layer protocols. For the

MX2800 STS-1,TL1 is implemented as a Telnet session running over either Ethernet or PPP.

Currently, up to eight simultaneous TL1 Telnet connections can be active. To manually bring up a TL1 Telnet connection, a Telnet client is used to request a connection on (TCP) port 3116. A successful connection will require that the MX2800 STS-1be properly configured to operate via the LAN or modem. For example, in the LAN case, the MX2800STS-1must have the LAN


MX2800 STS-1User Manual


Chapter 9. Transaction Language 1 (TL1)

management port enabled, a valid IP and gateway address, and a valid subnet mask.

Once the Telnet connection is established, it is necessary to initiate a TL1 session. Establishing a TL1 session involves successful user authentication. Until a TL1 session is established, all commands other than those used to initiate or terminate a session will be denied (autonomous messaging is also disabled). Authentication involves the successful entry of a username/password pair. A table of usernames and associated passwords and privileges is kept for TL1 authentication. This table is maintained by an administrator through theVT-100menus or through a TL1 session. For information on using theAct-Usercommand to initiate a TL1 session, see the sectionTL1 Commands on page 9-5.


As stated earlier, TL1 messages are either part of a commandresponse exchange or are generated autonomously.

The general format for a TL1 command is as follows:


Refer to TL1 Commands on page 9-5 for a list of TL1 commands supported by the MX2800STS-1.

TL1 Responses

There are three types of TL1 responses:

Acknowledgment messages

Output Response messages

Autonomous messages

Acknowledgment Messages

Acknowledgment messages are brief output messages generated in response to received TL1 commands. The MX2800 STS-1


MX2800 STS-1User Manual


Chapter 9. Transaction Language 1 (TL1)

currently supports two types of acknowledgment messages: In Progress (IP) and All Right (OK).

In Progress

The IP acknowledgment message is usually generated as an interim response message to indicate that a message has been received and that the command is being executed. IP messages have the following general format:



All Right

The OK acknowledgment message indicates that a command has been received and that the required action was initiated and completed. This message has the following general format:



Output Response Messages

Output Response messages are generated in response to received commands and have the following general format:


<SID> <YR>-<MO>-<DAY><HR>:<MIN>:<SEC><CR><LF>




For the MX2800 STS-1,theCOMPLETION CODE field will contain one of the following values:

COMPLD - Successful execution of the received command

DENY - Denial of the received command

When the received command is denied, the line in the message following the COMPLETION CODE line will contain a4-lettererror code. See the sectionTL1 Error Codes on page 9-13 for a description of possible MX2800STS-1error codes.


MX2800 STS-1User Manual


Chapter 9. Transaction Language 1 (TL1)

The MX2800 STS-1specifically uses “quoted line(s)” in the response message of successfully executedRTRV-ALM commands. The quoted line format is as follows:


The NTFCNCDE field will contain one of the following values:

MN - Minor

MJ - Major

CR - Critical

Refer to the condition types listed in Table 9-2 on page 9-10 (MX2800 STS-1 Alarm Events) for possible MX2800STS-1


Autonomous Messages

The Autonomous message is sent from the NE to the OS and is not associated with any explicit input message. The MX2800 STS-1uses this message to exclusively report alarmed andnon-alarmedevents. An autonomous message has the following general format:



Possible values for the ALARM CODE field include:

*C - Critical Alarm

** - Major Alarm

* - Minor Alarm

A - Non-alarm

NULL - (blank)


MX2800 STS-1User Manual