![]() |
![]() |
e-docs > Tuxedo > SNMP Agent Administration Guide > Integrating BEA SNMP Agent with a Management Framework |
SNMP Agent Administration Guide
|
Integrating BEA SNMP Agent with a Management Framework
The following sections explain how to integrate the BEA SNMP Agent into your management framework:
Understanding the BEA SNMP Agent MIB Files
BEA 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.
Using BEA SNMP Agent with a Management Framework
To use BEA 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 BEA SNMP Agent. It also defines the event notifications that can be generated by BEA SNMP Agent. The MIB thus provides the management framework with information it requires to manage BEA 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 BEA SNMP Agent, refer to the BEA Tuxedo Release Notes.
Integrating BEA Tuxedo Event Notifications
To integrate the BEA Tuxedo system event traps with your management framework, follow these steps:
Figure 4-2 HP OpenView Event Configuration Window
Retrieving or Modifying Object Values When Managing Multiple Domains
Monitoring of multiple BEA 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 BEA 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:
community@logical_agent_name
For example:
public@payrollagent
In this example payrollagent is a logical agent name that identifies the agent to which the request is to be forwarded by the BEA SNMP Agent Integrator.
Integrating Events Generated by BEA SNMP Agent Integrator Polling
The BEA SNMP Agent Integrator can be used to poll BEA Tuxedo objects, or other managed resources. To integrate the BEA SNMP Agent Integrator threshold-checking activity with the management framework, perform the following steps:
For more information, see Using the BEA SNMP Agent Integrator for Polling.
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |