|
|
Asynchronous message processing: The run time agent supports processing of more than one request at a time.
Generates powerful debug messages: The agent generates powerful debug messages during agent run time which makes debugging easier. It also provides different debug levels ERRMSG, DEBUGMSG, TRACEMSG, and user-specific debug message. The debug level can be selected based on the available memory.
Agent source code is very modular: Provides option to include/exclude the necessary modules during compilation. For example, the macro SNMPV3 is used to either include or exclude SNMPv3 module.
Support for Timer Service and Monitor Service: The Timer service enables to send notifications at specific dates and times. The Monitoring service allows you to observe the variation over time of attribute values in an observed module.
Support to generate API documents: The Agent Toolkit C Edition supports API documents, which is a set of C source files and methods for creating C-based agent applications.
Persistence storage (text file , database) for SNMP table is supported: The SNMP Agent supports storage of data in text files or databases based on the options provided in the Agent Compiler UI.
Database access for tables: The C Agent supports storage of data in database and accessing this database table from the handler files by using a set of APIs for any incoming request.
Low memory footprint: This is required to run the agent.
Support for Device and embedded systems management: The C Agent has been ported and tested in the following Real Time Operating Systems (RTOS) : VxWorks, QNX Nutrino, Windows CE , OSE.
Support for System Management: The C Agent has been ported and tested in other operating systems, such as Windows 2000, XP and Vista, Solaris, Linux , Unix, Free BSD, Net BSD, HP-Unix, OS-2.
Very modular code with clean separation of platform-dependent and platform-independent and instrument (stub) files.
The Multi-Protocol Agent is designed based on the JMX model of Common instrumentation with Multi-Protocol access to the agent.
The following are the features supported by the SNMP Agent. The functionality of each feature is covered in detail as separate topics in the book Building SNMP Agents.
Supports SNMP v1, v2c, and v3 agents : The run-time agent supports all the three versions of the SNMP Protocol. Hence the SNMP Agent can be developed either as SNMPv1, v2c, v3 agent.
Support for master and Sub-agent architecture, i.e., Extensible agent : The run-time agent supports to generate code for the SNMP agent either as Master agent with the Proxy Feature or as Sub-agent ( Standalone agent without the proxy feature).
Supports atomic set in the case of Multiple variable set : The run time agent supports atomic set implementation. When a set request is made for more than one MIB variable from the manager, then the final result in the agent should be either all the MIB variable values modified with new value (given from manager) or none of the values is modified.
Support for Access Control List: This is to authenticate read and read-write access to managers. The run time agent supports to provide authentication in the case of SNMPv1 and SNMPv2c request.
Good code generation for v1, v2 and v3 traps , notifications, and informs: The run-time agent supports to generate Traps in the case of SNMPv1, Notifications, and Informs in the case of SNMPv2.
Support for authenticated manager's list in the case of traps generation: The run-time agent implements the v1v2Manager Table and v3Manager Table to maintain the list of Managers to which traps should be sent.
Support for SNMP group counters: The run-time agent has implemented the SNMP group counters as per the RFC1907 MIB specification. This implementation is optional.
RFC2574 (USM MIB) and RFC2575 (VACM) MIBs: These are implemented in SNMPv3. The run-time agent has implemented the USM as default security model and VACM as default access control model as defined by SNMPv3 Framework.
Row Status support in v2c: The run-time agent provides Row Status support in SNMP V2. It is used for the creation and deletion of conceptual rows.
External index is handled: The WebNMS Agent Toolkit supports code generation for external index handling. Through external index handling, we can derive some of the features of an already existing table in another MIB. It also avoids duplication.
Persistence storage (text file , database) for SNMP table is supported: The run-time agent supports to provide storage in text files or databases based on the options provided in the Agent Compiler UI.
The following are the features supported by the TL1 Agent:
Delayed Activation: Delay Activation is a function whereby an input message may be stored in a Message Pending buffer at the NE for final execution at some later time, either automatically or by a subsequent message from the OS.
Built in Commands: The TL1 Agent of the WebNMS Agent Toolkit C Edition supports twelve built in commands. Using these commands you can control the TL1 Agent with much ease.
Built in Commands for Delayed Activation: Using the built in commands for Delayed Activation, you can activate, deactivate, or retrieve Delay Activation input messages.
Self Monitoring: This Feature enables the TL1 Agent to monitor the Agent details, such as the number of requests received, number of responses, and autonomous messages sent, etc.
Asynchronous Message Processing : Asynchronous Message Processing enables the client to send many requests simultaneously without having to wait for the previous message to be processed.
Session API: In Standalone TL1 and Multi-Protocol TL1 Agents, you can plug in any transport protocol using the Session API feature. TCP/IP is the default transport protocol used by the TL1 Agent. You can implement any other transport protocol and plug in or register it with the Transport Provider of the Session API.
Security: To prevent the possibility of deliberate or accidental attack on TL1 NE, SECURITY is provided in the TL1 Agent. Security in the TL1 Agent has been implemented as per the specifications in GR 815 and TR 835.
Gateway NE Feature: Gateway NE (GNE) will route the input message from a manager to the NEs connected to it. In other words, the GNE will act as a proxy TL1Agent.
Logging Framework: Using the Logging framework you can log any details of the TL1 Agent during run time. This framework permits you to easily create, configure, and customize the logs and also allows you to extend the capabilities of the framework specific to your needs.
Persistence Storage Support: This feature supports to provide persistent storage for non-volatile information in the form of text files. During run time the changes in the agent information for which persistent storage is available, will be updated in the text file. Any other external storage mechanism can also be used for keeping non-volatile information.
TR 835, GR 815 Compliance: The TL1 Agent complies to the Telcordia standards GR 815, TR835 and the provisioning messages from GR199.
MIB to TCS Customization: Allows you to modify the command code at the group level or node level.
The following features are supported by the Multi-Protocol HTTP Agent:
Authentication is supported by the Multi-Protocol HTTP Agent.
SSI tags are supported by the Multi-Protocol HTTP Agents.
Notification generation support is also available for the Multi-Protocol HTTP Agent. There are options to generate customized log messages.
Customization of HTML pages.
Log Messages option provides customized debug messages.
Implementation of WWW-MIB
Supports SSL (Secured Socket Layer)
HTTP 1.1 is supported
Self-Monitoring support
IP Filtering support
Request Control Mechanism
Other features, such as managing the SNMP parameters (USM, VACM, AGENT-CONFIG-MIB, etc) using the Multi-Protocol HTTP Agent are also available.
The following features are supported by the Multi-Protocol CLI Agent:
Supports String Mode Agent.
Browsing the agent: You can browse the MIB attributes through command line interface.
Notification Handling: RTRVNOTIF command enables the retrieval of the notifications generated by the agent.
Role-Based security: Each command is assigned a privilege level. Only users having the privilege can execute the command.
Telnet Server.
Supports Telnet, TCP, Craft, and Serial Interfaces.
Session API Framework to plug in user protocol for communication.
Self-Monitoring helps to monitor the Agent details, such as the number of requests received and number of responses sent.
Complete Help (cisco-like help).
Supports Built-in Commands which can help users configure the CLI Agent with much ease.
Command Usage: When you enter a wrong command, the agent shows the correct usage of the command.
Command Line Editing.
Command History.
Command Completion: Press Tab key to complete a command by command completion.
"?" Support: Press '?' key the agent to list the matching commands.
Handles more than one request at a time in multi-threaded platform.
|
|