Animated CTA Banner
MapYourTech
MapYourTech has always been about YOUR tech journey, YOUR questions, YOUR thoughts, and most importantly, YOUR growth. It’s a space where we "Map YOUR Tech" experiences and empower YOUR ambitions.
To further enhance YOUR experience, we are working on delivering a professional, fully customized platform tailored to YOUR needs and expectations.
Thank you for the love and support over the years. It has always motivated us to write more, share practical industry insights, and bring content that empowers and inspires YOU to excel in YOUR career.
We truly believe in our tagline:
“Share, explore, and inspire with the tech inside YOU!”
Let us know what YOU would like to see next! Share YOUR thoughts and help us deliver content that matters most to YOU.
Share YOUR Feedback
Tag

Transaction Language 1

Browsing

TL1 (Transaction Language 1) is a command-line language used in telecommunication networks, particularly in managing optical networks. Developed in the 1980s, TL1 is one of the oldest network management protocols and remains a key protocol in legacy telecom systems. It is primarily used for managing telecommunication equipment like DWDM systems, SONET/SDH, and OTN devices, providing operators with the ability to configure, monitor, and control network elements via manual or automated commands.Lets explore the fundamentals of TL1, its command structure, how it is used in optical networks, advantages and disadvantages, and how it compares to modern network management protocols like NETCONF and gNMI. We will also provide examples of how TL1 can be used for managing optical devices.

What Is TL1?

TL1 (Transaction Language 1) is a standardized command-line interface designed to manage and control telecommunication network elements, especially those related to optical transport networks (OTNs), DWDM, SONET/SDH, and other carrier-grade telecommunication systems. Unlike modern protocols that are API-driven, TL1 is text-based and uses structured commands for device interaction, making it akin to traditional CLI (Command Line Interface).

Key Features:

  • Command-based: TL1 relies on a simple command-response model, where commands are entered manually or sent via scripts.
  • Human-readable: Commands and responses are structured as text, making it easy for operators to interpret.
  • Wide Adoption in Optical Networks: TL1 is still prevalent in older optical network equipment, including systems from vendors like Alcatel-Lucent, Nokia, Huawei, and Fujitsu.

TL1 commands can be used to:

  • Configure network elements (NEs), such as adding or removing circuits.
  • Retrieve the status of NEs, such as the power levels of optical channels.
  • Issue control commands, such as activating or deactivating ports.

TL1 Command Structure

The TL1 protocol is built around a structured command-response model, where each command has a specific format and triggers a predefined action on the network element.

Basic TL1 Command Syntax:

A standard TL1 command typically includes several parts:

<Verb>:[TID]:<AID>:<CTAG>::<Parameters>;
  • Verb: Specifies the action to be performed, such as SET, RTRV, ACT, DLT.
  • TID (Target Identifier): Identifies the network element to which the command is being sent.
  • AID (Access Identifier): Specifies the element or resource (e.g., port, channel) within the NE.
  • CTAG (Correlation Tag): A unique identifier for the command, used to track the request and response.
  • Parameters: Optional additional parameters for configuring the NE or specifying retrieval criteria.

Example of a TL1 Command:

Retrieve the status of an optical port:

RTRV-OPTPORT::OTN-1-3::ALL;

In this example:

  • RTRV-OPTPORT: The verb that requests the retrieval of optical port data.
  • OTN-1-3: The AID specifying the OTN element and port number.
  • ALL: Specifies that all relevant data for the optical port should be retrieved.

Common TL1 Commands for Optical Networks

TL1 commands are categorized by the type of action they perform, with the most common verbs being RTRV (retrieve), ACT (activate), SET (set parameters), and DLT (delete).

RTRV (Retrieve) Commands:

RTRV commands are used to gather status and performance information from optical devices. Examples include retrieving signal levels, operational states, and alarm statuses.

  • Retrieve the optical power level on a specific port:
     RTRV-OPTPORT::DWDM-1-2::ALL;
  • Retrieve alarm information for an optical channel:
    RTRV-ALM-OPTCHAN::DWDM-1-3::ALL;

ACT (Activate) Commands:

ACT commands are used to enable or bring a resource (e.g., port, channel) into an operational state.

  • Activate an optical channel:
    ACT-OPTCHAN::DWDM-1-2-CH-5;

    SET (Set Parameters) Commands:

    SET commands allow operators to modify the configuration of network elements, such as setting power levels, modulation formats, or wavelengths for optical channels.

    • Set the output power of a DWDM port:
      SET-OPTPORT::DWDM-1-3::POWER=-3.5;

      DLT (Delete) Commands:

      DLT commands are used to remove or deactivate network elements, such as deleting a circuit or channel.

      • Delete an optical channel:
        DLT-OPTCHAN::DWDM-1-2-CH-5;

        TL1 in Optical Networks

        In optical networks, TL1 is commonly used for managing DWDM systems, OTN devices, and SONET/SDH equipment. Operators use TL1 to perform critical network operations, including:

        Provisioning Optical Channels

        TL1 commands allow operators to provision optical channels by setting parameters such as frequency, power, and modulation format. For example, setting up a new optical channel on a DWDM system:

        ACT-OPTCHAN::DWDM-1-4-CH-7::FREQ=193.1GHz, POWER=-3.0dBm;

        This command provisions a new channel on DWDM port 1-4 at 193.1 GHz with a power output of -3 dBm.

        Monitoring Optical Power Levels

        Network operators can use TL1 to monitor the health of the optical network by retrieving real-time power levels from transponders and optical amplifiers:

        RTRV-OPTPORT::DWDM-1-2::ALL;

        This command retrieves the power levels, signal-to-noise ratios (SNR), and other key metrics for the specified port.

        Handling Alarms and Events

        TL1 provides a way to monitor and handle alarms in optical networks. Operators can retrieve current alarms, acknowledge them, or clear them once the issue is resolved:

        RTRV-ALM-OPTCHAN::DWDM-1-2::ALL;

        This command retrieves all active alarms on optical channel 1-2.

        TL1 Advantages

        Simplicity

        TL1 is simple and easy to learn, especially for telecom engineers familiar with CLI-based management. The human-readable command structure allows for straightforward device management without the need for complex protocols.

        Vendor Support

        TL1 is widely supported by legacy optical networking devices from various vendors, including  Ribbon, Cisco, Ciena, Alcatel-Lucent, Huawei, Nokia, and Fujitsu. This makes it a reliable tool for managing older telecom networks.

        Customizability

        Because TL1 is command-based, it can be easily scripted or automated using basic scripting languages. This makes it possible to automate repetitive tasks such as provisioning, monitoring, and troubleshooting in optical networks.

        Granular Control

        TL1 allows for granular control over individual network elements, making it ideal for configuring specific parameters, retrieving real-time status information, or responding to alarms.

        TL1 Disadvantages

        Limited Automation and Scalability

        Compared to modern protocols like NETCONF and gNMI, TL1 lacks built-in automation capabilities. It is not well-suited for large-scale network automation or dynamic environments requiring real-time telemetry.

        Proprietary Nature

        While TL1 is standardized to an extent, each vendor often implements vendor-specific command sets or extensions. This means TL1 commands may vary slightly across devices from different vendors, leading to compatibility issues.

        Lack of Real-Time Telemetry

        TL1 is primarily designed for manual or scripted command entry. It lacks native support for real-time telemetry or continuous streaming of data, which is increasingly important in modern networks for performance monitoring and fault detection.

        Obsolescence

        As networks evolve towards software-defined networking (SDN) and automation, TL1 is gradually being phased out in favor of more modern protocols like NETCONF, RESTCONF, and gNMI, which offer better scalability, programmability, and real-time capabilities.

        TL1 vs. Modern Protocols (NETCONF, gNMI, OpenConfig)

        TL1 examples in Optical Networks

        Provisioning an Optical Channel on a DWDM System

        To provision an optical channel with specific parameters, such as frequency and power level, a TL1 command could look like this:

        ACT-OPTCHAN::DWDM-1-2-CH-6::FREQ=193.3GHz, POWER=-2.5dBm;

        This command activates channel 6 on DWDM port 1-2 with a frequency of 193.3 GHz and an output power of -2.5 dBm.

        Retrieving Optical Port Power Levels

        Operators can retrieve the power levels for a specific optical port using the following command:

        RTRV-OPTPORT::DWDM-1-3::ALL;

        This retrieves the current signal levels, power output, and other metrics for DWDM port 1-3.

        Deactivating an Optical Channel

        If an optical channel needs to be deactivated or removed, the following command can be used:

        DLT-OPTCHAN::DWDM-1-2-CH-6;

        This deletes channel 6 on DWDM port 1-2, effectively taking it out of service.

        Summary

        TL1 remains a key protocol in the management of legacy optical networks, providing telecom operators with granular control over their network elements. Its command-based structure, simplicity, and vendor support have made it an enduring tool for managing DWDM, OTN, and SONET/SDH systems. However, with the advent of modern, programmable protocols like NETCONF, gNMI, and OpenConfig, TL1’s role is diminishing as networks evolve toward automation, real-time telemetry, and software-defined networking.

        Reference

        https://www.cisco.com/c/en/us/td/docs/optical/15000r10_0/tl1/sonet/command/guide/454a10_tl1command/45a10_overivew.html