![]() |
![]() |
![]() |
![]() |
![]() |
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.Figure 5‑1 SNMP Manager/Agent Model
• 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” on page 7‑1.Figure 5‑2 summarizes how the Oracle SNMP Agent Integrator master agent can control an assortment of master agents, SNMP agents, and SMUX subagents.Modifies the default time interval that the Oracle SNMP Agent Integrator waits for a reply to a request sent to a SMUX subagent or an SNMP peer agent. This value can also be set by adding a BEA_PEER_MAX_WAIT entry to the Oracle SNMP Agent configuration file.If this environment variable is not set, and there is no BEA_PEER_MAX_WAIT entry 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_PEER entries in the Oracle SNMP Agent beamgr.conf configuration file.Specifies the absolute path to the Oracle SNMP Agent beamgr.conf configuration file, ending with the filename beamgr.conf.Once you have set up Oracle SNMP Agent according to the instructions in “Setting Up Oracle SNMP Agent on a Managed Node” on page 3‑1, 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” on page 6‑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” on page 8‑1.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” on page 7‑1.
5. You may want to modify the following fields in the Oracle SNMP Agent beamgr.conf configuration file: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:prompt> setenv BEA_PEER_MAX_WAIT 30
2. Locate each of the installed services. The Oracle SNMP Agent Integrator is installed as a Windows Service named snmp_integrator. It should be started before the SMUX subagents.An Oracle SNMP agent (tux_snmpd) is installed as a Windows service named tux81_snmpd or some other logical agent name if additional Oracle SNMP agents were installed.
Note: For any tux_snmpd process started as a non-SMUX peer agent (-s option specified at startup), you must start that process before starting the Oracle SNMP Agent Integrator. The starting order for Oracle SNMP Agent is as follows: start all non-SMUX peer agents, then the Oracle SNMP Agent Integrator, and then all 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:
Note: For any tux_snmpd process started as a non-SMUX peer agent (-s option specified at startup), you must start that process before starting the Oracle SNMP Agent Integrator. The starting order for Oracle SNMP Agent is as follows: start all non-SMUX peer agents, then the Oracle SNMP Agent Integrator, and then all SMUX subagents.For all SNMP agents other than tux_snmpd, the logical_agent_name is always the name of the executable. If you specify all, all SNMP agents are stopped.