The following sections provide information about the Oracle SNMP Agent Integrator and describe the procedure to install the Oracle SNMP Agent Integrator:
The Oracle SNMP Agent Integrator enables multiple agents and subagents from any vendor to cooperate in managing diverse hardware and software components on a single host. It makes possible the extended SNMP manager/agent model shown in Figure 5-1.
The Oracle SNMP Agent Integrator enables you to:
User-defined rules enable the Oracle SNMP Agent Integrator to check for the occurrence of significant system events and send alarms or execute programs when the events are detected. Communication over the network occurs only when an event is detected or when polling activity from the manager is started or stopped.
The Oracle SNMP Agent Integrator uses the SMUX protocol defined in RFC 1227 to respond to the SMUX subagents and fans out requests from an SNMP-compliant system or network management station to the appropriate subagent.
The DPI master agent uses SNMP to respond to requests from network managers. The DPI master agent can, therefore, be configured to communicate through the Oracle SNMP Agent Integrator in the same manner as other peer SNMP agents.
This feature is particularly useful for off-loading polling to the Oracle SNMP Agent Integrator to manage a distributed system whose components are spread over a number of computers. To the Oracle SNMP Agent Integrator, the managed resources appear as if they are on a single computer. For more information, see Using the Oracle SNMP Agent Integrator for Polling.
SNMP requests received by the Oracle SNMP Agent Integrator are fanned out to the appropriate peer SNMP agent or SMUX subagent, and the responses from the agents or subagents are passed on to the SNMP manager by the Oracle SNMP Agent Integrator.
Figure 5-2 summarizes how the Oracle SNMP Agent Integrator master agent can control an assortment of master agents, SNMP agents, and SMUX subagents.
The various agents and subagents all appear to the SNMP manager as a single SNMP agent. The Oracle SNMP Agent Integrator acts as a proxy for the SNMP manager.
The Oracle SNMP Agent Integrator can run on the same node with any master agent/subagent architecture as long as the master agent uses SNMP to respond to management requests.
The Oracle SNMP Agent Integrator uses the following environment variables:
BEA_PEER_MAX_WAITentry to the Oracle SNMP Agent configuration file.
BEA_PEER_MAX_WAITentry in the configuration file, the default is three seconds. For peer SNMP agents, the default timeout value can be overridden for individual SNMP agents using the timeout parameter in
NON_SMUX_PEERentries in the Oracle SNMP Agent
beamgr.confconfiguration file. (Note that “peer SNMP agent” and “non-SMUX peer agent” are identical terms. A peer SNMP agent, or a non-SMUX peer agent, is an SNMP agent running under the Oracle SNMP Agent Integrator.)
beamgr.confconfiguration file, ending with the filename
Once you have set up Oracle SNMP Agent according to the instructions in Setting Up Oracle SNMP Agent on a Managed Node, perform the following step to set up and use the Oracle SNMP Agent Integrators:
The peer SNMP agents can be on the same managed node (IP address) as the Oracle SNMP Agent Integrator, or they can be on remote nodes. Access to the objects managed by the peer SNMP agents is defined through
NON_SMUX_PEER entries in the
beamgr.conf configuration file. Each entry defines or moves a branch of the OID tree that is accessible via that agent. This task is described in Using Multiple SNMP Agents.
Because a DPI master agent speaks SNMP, it appears to the Oracle SNMP Agent Integrator as just another peer SNMP agent. Setting up access to DPI subagents is thus done the same way as setting up access to peer SNMP agents, as described in Step 1.
You can modify a SMUX subagent’s management scope—for example, to avoid conflicts with other agents—by specifying
OID_CLASS entries in the
beamgr.conf configuration file. By default, a SMUX subagent automatically indicates the section of the OID tree for which it is responsible when it registers with the Oracle SNMP Agent Integrator master agent. The syntax for
OID_CLASS entries is defined in Configuration Files.
This step is necessary only if you want to use the Oracle SNMP Agent Integrator to off-load polling from the management station. Polling rules are defined through
RULE_ACTION entries in the
beamgr.conf configuration file. Polling is automatically active when the Oracle SNMP Agent Integrator starts. Oracle SNMP Agent Integrator local polling can be de-activated or re-activated from a management station using SNMP Set commands. Oracle SNMP Agent Integrator polling rules, and how to start and stop polling, are described in Using the Oracle SNMP Agent Integrator for Polling.
Configure the management system for Oracle SNMP Agent Integrator traps. Some configuration is required on your SNMP-compliant management framework to make use of SNMP trap notifications that are generated by the Oracle SNMP Agent Integrator.
The exact set of steps you need to perform vary depending upon which management system you are using. Typically, some configuration or mapping is required to get the management system to perform a desired action (such as turning an icon red) when a trap is received. Consult your management system documentation for specific instructions.
These entries are supported by the Oracle SNMP Agent Integrator in the MIB-II
If you are using an Oracle SNMP agent as a SMUX subagent to manage Oracle Tuxedo applications, configure the Oracle SNMP Agent Integrator timeout to at least 30 seconds. To do this, add a
BEA_PEER_MAX_WAIT entry to the Oracle SNMP Agent
beamgr.conf configuration file as follows:
Another way you can set the timeout value is to set the environment variable
BEA_PEER_MAX_WAIT to 30. For C shell on UNIX systems, for example, use this command:
setenv BEA_PEER_MAX_WAIT 30
To start the Oracle SNMP Agent Integrator and SMUX subagents on a Windows system, follow these steps:
snmp_integrator. It should be started before the SMUX subagents.
To start the Oracle SNMP Agent Integrator and SMUX subagents on a UNIX system, log in as
root and start the following programs in the specified order:
To stop the Oracle SNMP Agent Integrator or one or more subagents on a Windows system, follow these steps:
To stop the Oracle SNMP Agent Integrator or one or more subagents on a UNIX system, issue the following command:
| all [
For all SNMP agents other than
logical_agent_name is always the name of the executable. If you specify
all, all SNMP agents are stopped.