|
|
Before starting the simulated agent, you can configure the run time Agent Settings such as port, version, community, etc. If the settings are not configured, the simulated agent will start with the default settings. To configure the agent settings, Select Settings -> Agent Settings option in the menu bar or click on the Agent Settings icon in the toolbar.
The simulated SNMP agent, starts at default port number 8001. You can specify any alternative port. If you are unable to start the agent at port 161, refer to the topic, TroubleShooting - General.
Engine ID is used in SNMPv3. It is the unique identifier of the SNMP Engine in the domain. You can specify Engine ID or by default it will take the combination of the port and IPAddress.
The SNMP Version can be specified as either V1, V2c, or V3 . By default, the SNMP version is V2c.
The following Logging options are available in SNMP Agent Simulator. The logs will be generated in the agent.log file inside the <Simulator_Home>/logs directory , based on the selected logging level.
Disabled (0) : This level indicates that the debugging mode is disabled. Hence, log messages do not get stored in the text file.
Fatal (1) : This level indicates that the application has encountered a severe error. These errors need to be attended with care. When this level is chosen, critical messages such as details on Agent crash, Authentication errors, Agent already open in another session, etc., get stored in the log file.
Error (2) : This level indicates that an error has occurred and the application cannot handle the request as designed. This may be automatically corrected during execution or the application should be capable of handling those situations when a similar request comes again. Selecting this level stores all the Error and Exception messages in the log file along with the fatal messages.
Warning (3) : This level indicates that the application has met with an expected error. All Warning messages get stored in the log file when debug level is WARN.
Info (4) : This level does not signify the occurrence of any error but logs all important events. Any information that might be required for reference gets stored in the log file under this info level.
Debug (5) : This level indicates that the application moves into the debug mode. It will be used for generating debugging information and should not be used in general cases.
Trace (6) : This level indicates that the application logs every activity from entering a method to exiting it. Hence, selecting this level may affect performance. The Trace level should be used only to solve any complex problem.
The agent simulator supports English, Japanese and Chinese encoding types. The default encoding type is "English". The Encoding option enables you to select the encoding type to be supported by the simulator. When the agent simulator is started, any string will be encoded as per the encoding format selected.
The SNMP Agent Simulator provides option to manage the SNMP agent from the remote, using Remote Method Invocation (RMI). Selecting the option ' Manage using RMI ' will register the simulator with the RMI registry.
Refer to the topic Managing Agents via RMI, to learn more.
When a Inform is sent from the SNMP Agent, an SNMP Manager that receives the Inform request acknowledges the message with an SNMP response PDU. Selecting this option will capture all the inform response received from the manager, in a log file. The log file informresponse will be created under <Simulator_Home>/logs directory.
Reverse Order Of Script Execution
A script may be configured at the table instance level, table column level and table entry level . By default, the instance level script will be executed first, the column level script will be executed next and the table entry level script will be executed last.
If the option Reverse Order of Script execution is selected , the script will be executed in the reverse order. (i.e) the script configured at the table entry level will be executed first, the column level script will be executed next, and then the instance level script will be executed.
The community to be used while processing the GET request . The default Read Community is public. You can define more than one community name. Click Add to add your own read community string.
The community to be used while processing the SET request. The default Write Community is public. You can define more than one community name. Click Add to add your own write community string.
|
|