![]() |
![]() |
![]() |
![]() |
![]() |
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.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.The procedure for setting up and starting the Oracle SNMP agent is described in “Setting Up Oracle SNMP Agent on a Managed Node” on page 3‑1.
1. Make sure the Tuxedo EventBroker server (TMSYSEVT) is running for the domain being managed. For more information, see “Setting Up Oracle SNMP Agent on a Managed Node” on page 3‑1.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.
2. Modify the 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” on page 3‑1.
3. If you have not already done so, load the Oracle SNMP Agent bea.asn1 MIB file into your management framework.
a. Select Options−>Load/Unload MIBs: SNMP.Figure 4‑1 Selecting Load/Unload MIBs in HP OpenView
b.
c. Specify the path to the Oracle SNMP Agent configuration file (bea.asn1). By default, this file is installed in:
d.
a. Select Options→Event Configuration.
b. Select the enterprise tuxedo.
c. Select an event type, such as networkFlowTrap in HP Open View.
d. Customize the management framework response to incoming events of that type. Select Edit→Modify Event in OpenView, which invokes the Event Configuration window shown in the following display.Figure 4‑2 HP OpenView Event Configuration WindowIn 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.A polling rule is defined by a RULE_ACTION entry in the Oracle SNMP Agent beamgr.conf configuration file.
b. Select beaSystemDescr..1.3.6.1.4.1.140.1.1.0.specific_trap_number