|
|
The Recording wizard allows to easily create simulations of actual devices. Once data is captured from a device, any variation on this basic simulation can be created for use with the SNMP Agent Simulator and Network Designer. The wizard is easy-to-use and user-friendly.
You can save the recorded configuration and create multiple copies of the same to simulate a network in the Network Designer. The recorded configuration can also be suitably modified to re-create problems or test configuration variations.
Select Configure -> Record from
a Real Agent option from the menu bar or click on the record icon
from the toolbar. The Recording Wizard is displayed,
wherein you have to specify the following details.
Agent Name/IP : You can specify either the machine name or IP address of the machine. For example, agent-test or 192.168.215.1
Port Number : The port on which the real agent is running. The default port is set to 161.
Community : Specify community if defined or else the default community is taken to be public.
SNMP Version : Specify the SNMP agent version. The support versions are V1, V2c and V3.
If the real agent version is SNMP v3, specify the v3 user details like user name, context name, security level, auth / priv protocol values and password in the v3recording.conf file available in <SimulatorHome>/conf directory.
Time out ( in secs ) : If the real agent is not reachable, how long should it try to maintain the connection.
Retries : If the real agent takes time to respond,how many times should the simulator try again.
Record all data: Select this option to record all the OIDs in the real agent. If this option is not selected, the starting oid and ending oid option will be enabled.
Starting OID : Browse to specify where you want to start recording from by specifying the starting OID. For example : 1.3.6
Ending OID : You can browse to specify the Ending OID. However, it is optional. Learning from the real agent happens until end of MIB when the ending OID is not specified.
Generate Debug message while recording : You can also generate debug messages to trace the proceeding of the recording from the real agents. The log file will be generated in the name of the host specified in the ./logs directory.
Click Record to record from the real agent. The progress bar shows the rate at which information is read from the real agent and is updated in the simulator. When the recording is successfully completed, the following message is displayed. Click OK to exit from the dialog.
If the simulator encounters any errors while updating the recorded data, the following message is displayed after the recording process is completed. Click Yes to view the log messages.
If the real agent is not running at the specified port, the message Recording Terminated because of Errors will be displayed in the Error dialog as shown in the screen-shot below:
In case you want to stop the recording of the real agent, click Stop to abort process.
|
|
On recording the real agent configuration, the configuration must be saved. |
The errors encountered by the simulator, while updating the recorded values are captured in a recordError.log file, in <Simulator Home>/logs directory. The following messages are captured in the log file as shown in the screen shot below:
The log file captures the details about the real agent being recorded, such as Agent Name, Agent Port, Agent Community, Agent Version, Timeout value and number of retries.
The log file displays the OID of the nodes which contain empty values in the real agent being recorded.
For example, if RFC1213 MIB is recorded and the value of the node sysLocation in System group does not contain any value, the following error message is displayed: Empty value obtained for :.1.3.6.1.2.1.1.6.0
If there is a data type mismatch between the real agent and the MIB loaded in the simulator, the simulator will record it as empty value. The log file captures any data type mismatches between the real agent and the MIB loaded in the simulator.
For example : The syntax of the scalar node sysObjectID with OID .1.3.6.1.2.1.1.2.0, in the real agent is "Object Identifier". In the MIB loaded in the simulator, the same OID has the syntax as "Integer". This error is captured and displayed in the log file.
If the simulator is not able to resolve the index in a particular table while updating the recorded value, an error message will be logged in the log file. The corresponding table will not be updated with the recorded data.
Example : Could not get simulated objects for the instance .6.1.192.168.1.224 in the table with oid .1.3.6.1.2.1.3.1.1
Scalar and Table Groups Recorded
The real agent may or may not have all the scalar and table groups available in the MIB. Similarly, the MIB, may or may not have all the scalar and table groups available in the real agent. The log file captures this information and displays the scalar and table groups actually recorded from the real agent.
|
|
