|
|
|
|
|
|
| | | |
Integrating BEA SNMP Agent with a Management Framework
The following sections explain how to integrate the BEA SNMP Agent into your management framework:
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 Tuxedo and WLE resources.
By default, the SNMP MIB file, named bea.asn1, is installed in the installation_directory/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 SNMP Agent Release Notes for BEA Tuxedo and BEA WebLogic Enterprise or the BEA SNMP Agent Release Notes for BEA Tuxedo 8.0.
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 Tuxedo or WLE system events occur?
For details, see Integrating Tuxedo and WLE 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 BEA SNMP agent as a SMUX subagent with the BEA SNMP Agent Integrator, you might want to off-load some threshold checking to the BEA SNMP Agent Integrator. The BEA SNMP Agent Integrator generates enterprise-specific traps when the user-defined threshold is crossed. Off-loading checking of selective thresholds to the BEA SNMP Agent Integrator reduces the network bandwidth consumed by the management framework's polling activities.
The procedure for setting up and starting the BEA SNMP agent is described in Setting Up BEA SNMP Agent on a Managed Node.
Integrating Tuxedo and WLE Event Notifications
To integrate the Tuxedo and WLE system event traps with your management framework, follow these steps:
BEA SNMP Agent will not receive event notifications unless the EventBroker server (TMSYSEVT) is running. For information on the Tuxedo EventBroker server, see the reference page TMSYSEVT(5) in the BEA Tuxedo File Formats and Data Descriptions Reference.
For example, on HP OpenView Network Node Manager, see the following display and do the following:
Figure 3-1 Selecting Load/Unload MIBs in HP OpenView
installation_directory\etc\bea.asn1 (Windows)
installation_directory/etc/bea.asn1 (UNIX)
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:
Figure 3-2 HP OpenView Event Configuration Window
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.
Retrieving or Modifying Object Values When Managing Multiple Domains
Monitoring of multiple domains is done by running a separate Tuxedo or WLE 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 or WLE 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.
Integrating Events Generated by BEA SNMP Agent Integrator Polling
The BEA SNMP Agent Integrator can be used to poll Tuxedo or WLE objects, or other managed resources. To integrate the BEA 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 BEA SNMP Agent beamgr.conf configuration file.
For example, in HP OpenView, you can add a new event type by doing the following:
In the window that is invoked you would use the following as the event number:
.1.3.6.1.4.1.140.1.1.0.specific_trap_number
For more information, see Using the BEA SNMP Agent Integrator for Polling.
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|