|
|
MIBs are specifications containing definitions of management information so that networked systems can be remotely monitored, configured and controlled. The rules for writing MIBs are defined in a collection of documents called the Structure of Management Information (SMI).
The MIB Editor is used to create and modify SNMP MIB definitions. The MIB definition and modification is most useful for enterprise MIB creation and prototyping. The MIB Editor has an easy-to-use wizard interface through which the various constructs conforming to SMIV1 and V2 specifications and ASN.1 rules can be created.
Starting MIB Editor
The MIB Editor can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/MibEditor.bat for windows OS (or) <Agent Toolkit Home>/bin/MibEditor.sh for other OS.
Yet another way to invoke the MIB Editor in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> SNMP Agent -> MIB Editor.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
The MIB Compiler is a tool, which provides an integrated environment to generate java source code for developing a standalone SNMP Agent. It takes the MIB file as input and based on the MIB generates the necessary java files. It also allows you to instrument the code and compile the Agent.
Starting MIB Compiler
The MIB Compiler can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/MibCompiler.bat for windows OS (or) <Agent Toolkit Home>/bin/MibCompiler.sh for other OS.
Yet another way to invoke the MIB Compiler in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> SNMP Agent -> MIB Compiler.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
The AdventNet MIB Browser is a complete SNMP MIB Browser that enables loading of MIB's, MIB Browsing, walking MIB tree, searching MIB's and performing all other SNMP related functions to users. Viewing and operating the data available through an SNMP agent on a managed device, e.g. a router, switch, hub etc., is made possible by using the MIB Browser.
Starting MIB Browser
The MIB Browser can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/MibBrowser.bat for windows OS (or) <Agent Toolkit Home>/MibBrowser.sh for other OS.
Yet another way to invoke the MIB Browser in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> SNMP Agent -> MIB Browser.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
SNMP V3Admin
The SNMP V3Admin is a tool which is used for configuring USM user tables and VACM tables for SNMPv3 agent at runtime.
Starting SNMP V3Admin
The SNMP V3Admin can be started in any of the following ways:
From the Agent Toolkit Launcher, by double clicking on SNMP V3Admin icon under SNMP agent.
From the bin directory, by running <Agent Toolkit Home>/bin/SnmpV3AdminTool.bat> for windows OS (or) <Agent Toolkit Home>/bin/SnmpV3AdminTool.sh> for other OS.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
The JMX Compiler is a tool, which provides an integrated environment to generate java source code for developing a Multi-Protocol agent. It takes the MIB file as input and based on the MIB generates the necessary java files. The generated code will be based on the Model MBeans specified by JMX specification.
Starting JMX Compiler
The JMX Compiler can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/JmxCompiler.bat for windows OS (or) <Agent Toolkit Home>/bin/JmxCompiler.sh for other OS.
Yet another way to invoke the JMX Compiler in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> Multi-Protocol Agent -> JMX Compiler.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
The AdventNet MBean Browser is a Manager application which enables the user to access a Multi-Protocol agent's MBeans and use the provided services through the RMI / CORBA/ HTTP protocol adaptor or connector . To accomplish this, the Multi-protocol agent must be started which instantiates the different adaptors/connectors at their specified port numbers.
The MBean Browser uses the client side API provided for accessing the MBeans through the connectors (RMI Adaptor, CORBA Adaptor, or HTTP Connector) at the server side.
Starting MBean Browser
The MIB Browser can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/MBeanBrowser.bat for windows OS (or) <Agent Toolkit Home>/MBeanBrowser.sh for other OS.
Yet another way to invoke the MIB Browser in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> Multi-Protocol Agent -> MBean Browser.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
TCS is a file containing definitions of management information so that a network element (NE) can be remotely monitored, configured and controlled. The rules for defining a TL1 message are defined in GR-831 standard. The TL1 Message Builder is an intuitive GUI tool that helps you create and modify TL1 Command Set and Data Set definitions in the XML format. The TL1 Data Set definition file will have possible values for each command defined in TCS.
Starting TL1 Message Builder
The TL1 Message Builder can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/TL1MessageBuilder.bat for windows OS (or) <Agent Toolkit Home>/bin/TL1MessageBuilder.sh for other OS.
Yet another way to invoke the TL1 Message Builder in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> TL1 Agent -> TL1 Message Builder.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
The TL1 Compiler is a tool, which provides an integrated environment to generate java source code for a standalone TL1 Agent. It takes the TL1 command set (TCS) file as input and generates code based on the commands defined in the TCS file.
Staring TL1 Compiler
The TL1 Compiler can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/TL1Compiler.bat for windows OS (or) <Agent Toolkit Home>/bin/TL1Compiler.sh for other OS.
Yet another way to invoke the TL1Compiler in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6 -> TL1 Agent -> TL1Compiler.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
AdventNet TL1 Browser is a full-fledged GUI application that can be used to query a TL1 device and get responses. It allows the user to view and operate on data available through a TL1 agent on a managed device thereby managing the device. Example: Telecom switch.
Starting TL1 Browser
The TL1 Browser can be started in any of the following ways:
From the Agent Toolkit launcher, by running the <Agent Toolkit Home>/AgentToolkit.bat for windows OS (or) <Agent Toolkit Home>/AgentToolkit.sh for other OS.
From the bin directory, by running <Agent Toolkit Home>/bin/TL1Browser.bat for windows OS (or) <Agent Toolkit Home>/bin/TL1Browser.sh for other OS.
Yet another way to invoke the MIB Editor in windows environment is by clicking Start menu -> Programs -> Agent Toolkit Java Edition 6-> TL1 Agent -> TL1 Browser.
Running the file, by default will take the JAVA_HOME path as set in the PATH variable. If the JAVA_HOME path is not set properly, it is essential that you set the path before proceeding further. You can do this by editing the setenv.bat/setenv.sh file in the bin directory.
|
|