|
|
This chapter explains the Standalone TL1 Agent architecture in the Agent Toolkit C Edition. The various modules of the architecture are as follows:
The following architecture image explains the various modules in the Standalone TL1 Agent:
This module is responsible for establishing contact between the Client and the Server and for listening to client requests. The Session Module comprises the following components.
a. Session
This is responsible for establishing contact between the Client and the Server. This module listens for client request (TL1 Manager) and accepts client request if it comes for the TL1 Agent. The connection is maintained until client closes connection.
b. 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.
c. Craft
Craft interface is a local interface to TL1 agent. It receives input message from user on console and passes it to TL1 engine.
d. TCP/IP
TCP/IP is the default transport protocol for the TL1 Agent for managing remotely.
TL1 Engine is the core of TL1 Agent. It receives the parsed TL1 input message object from the TL1 parser and then identifies the listener (generated command code stub file) from the incoming input message, for which it should do the processing. The generated stub file forms TL1 output message which will be formatted and sent to OSS or CTI. It also does the dequeuing of the autonomous message and sends it to OSS or CTI.
The TL1 Engine module consists of three components: Message Processing, Agent provisioning and Monitoring, and Security.
a. 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, such as Input, Response, Autonomous, and Acknowledgment. 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.
Acknowledgment Message Originator: TL1 acknowledgment messages will be sent to the managers , for instance, when the request processing takes time (In Progress acknowledgment. message). This component in the TL1 adapter facilitates to send all type of acknowledgment 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 sending autonomous messages efficiently. This component in TL1 adapter 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.
b. Agent Provisioning and Monitoring
This module contains some provisioning input commands that are built-in into the TL1 Agent and commands that facilitate the monitoring of the TL1 Agent
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
Self-Monitoring: This module monitors the TL1 Agent. Agent details, such as the number of requests received, number of responses, and autonomous messages sent, etc. are monitored here.
c. 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.
This registry maintains the reference of all the generated command code listeners with respect to their command code/verb/modifiers as key. This registry will be looked after by the TL1 Adapter when any input message reaches it. The appropriate listeners will process the incoming TL1 input messages.
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.
|
|