8.2 Running a Simulation Agent
To run a simulation agent only a set of supported MIB modules need to be configured by setting up a code generation project using the “Accessing the Project Wizard” on page 13. Then simply press the button on the tab and the simulation agent is started to listen on all local IP addresses on port 161, the default SNMP port for command responder applications.
To bind all local addresses, the special IP address 0.0.0.0 is used.
If the simulation agent start fails, a popup is displayed with an error message and the root cause is displayed in the tab. In most cases, startup failures are caused by address or port conflicts or because on UNIX systems AgenPro does not have enough privileges to bind a port below 1024.
The running agent can be configured using standard SNMP means. The Table 6 on page 57 lists the MIB modules that are supported at minimum, that is, if no MIB modules for code generation have been configured for the current project. To initially access the agent you will need the security settings listed in the next section
|
MIB Module Name |
Description |
|---|---|
|
SNMPv2-MIB |
Contains general information about the agent. |
|
SNMP-VIEW-BASED-ACM-MIB |
Controls the view access control model (VACM) of the agent. The VACM controls which user/community has access to which contexts and MIB tree subsets. |
|
SNMP-USER-BASED-SM-MIB |
Controls the (SNMPv3) users and their authentication and privacy settings. SNMPv1/v2c communities are mapped to users. See also SNMP-COMMUNITY-MIB. |
|
SNMP-COMMUNITY-MIB |
The SNMP-COMMUNITY-MIB maps communities (v1 or v2c) to SNMPv3 security names (users). With that mapping, the VACM can be applied to community based SNMP version too. |
|
SNMP4J-LOG-MIB |
Controls the log levels for the simulation agent. |
|
SNMP-TLS-TM-MIB |
Maps certificates to SNMPv3 security names. To enable TLS support, you need to add a row to the snmpTlstmCertToTSNTable which maps a certificate to the TLSPRIV user name. Certificates can provided to the Java runtime with the -Djavax.net.ssl.trustStore and the |
|
SNMP4J-CONFIG-MIB |
Manages the persistent storage of the agent‘s MIB data. By default, AgenPro uses the AgenProSim.cfg and the AgenProSim.bc to store its MIB data and boot counter respectively. Both files are stored in the user‘s home directory who is running AgenPro. |
|
AGENTPP-SIMULATION-MIB |
With the simulation MIB all simulated MIB objects can be modified through SNMP. The agentppSimMode MIB object can be used to put the agent from the default mode operation into the config mode. In config mode, all MIB objects, regardless of their MAX-ACCESS limit, can be modified with a SNMP SET operation (as long as VACM provides access to the object itself). For more details, see “Simulation Agent Configuration with SNMP” on page 55 |
Security Credentials for SNMP Access
To be able to access the agent through SNMP, use one of the protocol version and community or security name, protocol, and passphrases combinations list by Table 7 on page 58: