Setting Up the Oracle SNMP Agent Integrator

The following sections provide information about the Oracle SNMP Agent Integrator and describe the procedure to install the Oracle SNMP Agent Integrator:

•	About the Oracle SNMP Agent Integrator

•	Configuring the Oracle SNMP Agent Integrator

•	Starting the Oracle SNMP Agent Integrator and Subagents on a Windows System

•	Starting the Oracle SNMP Agent Integrator and Subagents on a UNIX System

•	Stopping the Oracle SNMP Agent Integrator and Subagents on a Windows System

•	Stopping the Oracle SNMP Agent Integrator and Subagents on a UNIX System

About 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.

Figure 5‑1 SNMP Manager/Agent Model

The Oracle SNMP Agent Integrator enables you to:

•	Run multiple peer SNMP agents on a single managed node.

All communication between the agents and the SNMP manager is handled through the Oracle SNMP Agent Integrator master agent.

•	Off-load polling from the management station to reduce network traffic and reduce load on the network manager.

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.

•	Manage system resources using multiple SNMP multiplexing (SMUX) subagents.

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.

•	Manage system resources using any other master agent/subagent protocol, such as Distributed Program Interface (DPI), where the master agent responds to SNMP management requests.

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.

•	Coordinate communication between an SNMP manager and multiple SNMP agents on multiple network nodes.

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.

•	Listen on UDP port 161 and handle all communications with the SNMP manager.

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.

Figure 5‑2 Oracle SNMP Agent Integrator Master/Subagent Architecture

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.

Configuring the Oracle SNMP Agent Integrator

The Oracle SNMP Agent Integrator uses the following environment variables:

BEA_SMUX_PASSWD

Indicates the password that a SMUX subagent must use when re-establishing communication with the Oracle SNMP Agent Integrator.

BEA_PEER_MAX_TRIES

Indicates the number of times the Oracle SNMP Agent Integrator retries sending an SNMP request to peer SNMP agents when no response is received within the established timeout interval.

BEA_PEER_MAX_WAIT

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.

(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.)

BEA_SM_BEAMGR_CONF

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:

1.	Indicate the managed objects (if any) that are available from peer SNMP agents.

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.

2.	Indicate the managed objects that are available (if any) through Distributed Program Interface (DPI) master 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.

3.	Modify the management scope of SMUX subagents, if desired.

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 9‑1.

4.	Define local polling rules and the actions to be taken by the Oracle SNMP Agent Integrator if user-defined thresholds are crossed.

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.	Configure your SNMP management framework for the Oracle SNMP Agent Integrator. For more information, see “Integrating Oracle SNMP Agent with a Management Framework” on page 4‑1.

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.

6.	Modify other entries in the configuration file (if desired)

You may want to modify the following fields in the Oracle SNMP Agent beamgr.conf configuration file:

•

SYS_DESCR

•	SYS_CONTACT

•	SYS_LOCATION

•	SYS_SERVICES

These entries are supported by the Oracle SNMP Agent Integrator in the MIB-II snmp group.

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:

BEA_PEER_MAX_WAIT 30

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

Starting the Oracle SNMP Agent Integrator and Subagents on a Windows System

To start the Oracle SNMP Agent Integrator and SMUX subagents on a Windows system, follow these steps:

1.	Start the Oracle SNMP Agent Integrator and SMUX subagents from the Services window.

On the Windows taskbar, choose Start->Settings->Control Panel->Services (or Start->Programs->Administrative Tools->Services on a Windows 2003 system) to display the Services window.

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.

3.	Click Start. There may be a short delay as each service is initiated.

4.	Start any other SMUX subagents.

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.

Starting the Oracle SNMP Agent Integrator and Subagents on a UNIX System

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:

•	snmp_integrator

•

tux_snmpd

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.

Stopping the Oracle SNMP Agent Integrator and Subagents on a Windows System

To stop the Oracle SNMP Agent Integrator or one or more subagents on a Windows system, follow these steps:

1.	On the Windows taskbar, choose Start->Settings->Control Panel->Services (or Start->Programs->Administrative Tools->Services on a Windows 2003 system) to display the Services window.

2.	In the list of Services, locate and select the installed service and click Stop to stop it.

Stopping the Oracle SNMP Agent Integrator and Subagents on a UNIX System

To stop the Oracle SNMP Agent Integrator or one or more subagents on a UNIX system, issue the following command:

prompt> stop_agent logical_agent_name | all [logical_agent_name]

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.