The following sections explain how to integrate the Oracle SNMP Agent into your management framework:
Oracle SNMP Agent provides the following two SNMP MIB files. bea.asn1
and mib.txt
. The bea.asn1
file is used by the SNMP network management framework to set up that portion of its local MIB (on the management station) required to manage Tuxedo applications. The mib.txt
file, which is created from the bea.asn1
file, is used by the Tuxedo SNMP agent (tux_snmpd
) at startup to set up its local SNMP MIB on the managed node.
Note: | Only the bea.asn1 file is of interest in the discussions that follow. |
To use Oracle SNMP Agent with your management framework, follow these steps:
The SNMP MIB defines the data types and access permissions for the various managed objects that can be accessed through Oracle SNMP Agent. It also defines the event notifications that can be generated by Oracle SNMP Agent. The MIB thus provides the management framework with information it requires to manage Oracle Tuxedo resources.
By default, the SNMP MIB file, bea.asn1
, is installed in the tux_prod_dir
/udataobj/snmp/etc
directory. The MIB file must be imported into the management database of your management framework. Some management frameworks refer to this process as loading a MIB. For a list of management frameworks tested with Oracle SNMP Agent, refer to the Oracle Tuxedo Release Notes.
For example, are there particular attributes of the resources you are managing that you want to monitor? Do you want to be notified when certain Oracle Tuxedo system events occur?
For details, see Integrating Oracle Tuxedo Event Notifications.
Periodic collection of values of pertinent objects is valuable for analysis of trends. This analysis is valuable for capacity planning and load-balancing. You can also use polling to generate alarms, which is useful for fault management.
If you are using the Oracle SNMP agent as a SMUX subagent with the Oracle SNMP Agent Integrator, you might want to off-load some threshold checking to the Oracle SNMP Agent Integrator. The Oracle SNMP Agent Integrator generates enterprise-specific traps when the user-defined threshold is crossed. Off-loading checking of selective thresholds to the Oracle SNMP Agent Integrator reduces the network bandwidth consumed by the management framework’s polling activities.
The procedure for setting up and starting the Oracle SNMP agent is described in Setting Up Oracle SNMP Agent on a Managed Node.
To integrate the Oracle Tuxedo system event traps with your management framework, follow these steps:
TMSYSEVT
) is running for the domain being managed. For more information, see Setting Up Oracle SNMP Agent on a Managed Node.
Oracle SNMP Agent will not receive event notifications unless the EventBroker server (TMSYSEVT
) is running. For information on the Tuxedo EventBroker server, see reference page TMSYSEVT(5) in Oracle Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference.
TRAP_HOST
entry in the Oracle SNMP Agent beamgr.conf
configuration file to specify the location of the management machine that is to be the destination for traps generated by the agent. For more information, see Setting Up Oracle SNMP Agent on a Managed Node.bea.asn1
MIB file into your management framework.For example, on HP OpenView Network Node Manager, see the following display and do the following:
You might want to change the way in which Tuxedo SNMP traps are displayed on your management console, or the actions that the management framework takes in response to specified events. For example, you might choose to ignore some routine informational notifications. For example, to view the event configuration on HP OpenView, do the following:
tuxedo
.networkFlowTrap
in HP Open View.You can modify the event configuration to ignore an event, or generate a pop-up notification or run a program or script when the event is received. You might also want to create a separate category for Tuxedo events, as shown in the preceding display.
Monitoring of multiple Oracle Tuxedo domains is done by running a separate Tuxedo SNMP agent for each domain being monitored. These agents must be run as SMUX subagents under the Oracle SNMP Agent Integrator.
When more than one Tuxedo SNMP agent is running as a SMUX subagent on a node, then SNMP manager Set or Get requests to an agent must be addressed using a community of the form:
In this example payrollagent
is a logical agent name that identifies the agent to which the request is to be forwarded by the Oracle SNMP Agent Integrator.
The Oracle SNMP Agent Integrator can be used to poll Oracle Tuxedo objects, or other managed resources. To integrate the Oracle SNMP Agent Integrator threshold-checking activity with the management framework, perform the following steps:
A polling rule is defined by a RULE_ACTION
entry in the Oracle SNMP Agent beamgr.conf
configuration file.
For example, in HP OpenView, you can add a new event type by doing the following:
For more information, see Using the Oracle SNMP Agent Integrator for Polling.