TL1 Agent Architecture

This chapter explains the Standalone TL1 Agent architecture in the Agent Toolkit Java Edition.

The following architecture image explains the various modules in the Standalone TL1 agent.

Transport Provider Interface: Transport Provider is responsible for all communications between the Agent and the Manager. It uses the configured protocol for this purpose. It acts as a bridge between the Session layer and the underlying transport protocol. The advantage of using this approach is that the Session layer need not be aware of the underlying protocol used. For using a particular protocol, the user has to implement that protocol and plug in (or register) the protocol with the Transport Provider.

TCP/IP : TCP/IP is the default transport protocol for the TL1 Agent  for managing remotely.

Message Processing: This module is responsible for processing the input message received from the client. This module is responsible for parsing and processing the input message received by the TL1 Engine. This module is also responsible for sending the output response messages and autonomous messages back to the NEs.

• TL1 Parser: TL1 Parser package is the default parser provided by this WebNMS TL1 Agent Toolkit. The parser is built as per the Bellcore standards. It can parse all TL1 messages like Input, Response, Autonomous, and Acknowledgement. Some options are also provided to set the parsing levels for each session. These methods can be called from the TL1Session. Apart from this, you can write your own parser and plug it into the TL1Session.

• Acknowledgement Message Originator: TL1 acknowledgement messages will be sent to the managers , for instance, when the request processing takes time (In Progress acknowledgment. message). This component in the TL1 adaptor facilitates to send all type of acknowledgement messages.

• Output Formatter: It takes care of formatting and sending the response message to the TL1 Manager.

• Autonomous Message Originator: TL1 agents are most preferred for fault management. And it becomes utmost important for efficiently sending autonomous messages. This component in TL1 adaptor is used to create and send the autonomous message to the TL1 Manager. The stub files can invoke methods in this component to send  autonomous messages.

Built-in Commands: This module contains all the Built-in Commands that are implemented in the TL1 Agent. Built-in Commands are provisioning input commands common to all OS/NE interfaces. They are commonly used input commands that have already been implemented in the WebNMS TL1 Agent. Some general Built-in Commands as well as Built-in Commands for Delayed Activation have already been implemented in the TL1 Agent.

Security: This module contains the various Security Views associated with the Security implemented in the TL1 Agent. Security Validation such as User Authentication, Channel Authentication, Command Authentication, etc., takes place in the Security Module.
 

Instrumentation (TL1 Stubs Instrumentation )

The instrumentation files are the generated stub files for a given TL1 Command Set (.tcs) file. User or application/device-specific instrumentation can be done on these files.