Each object in the MIB has an object identifier (OID), which the management station uses to request the object’s value from the agent. An OID is a sequence of integers that uniquely identifies a managed object by defining a path to that object through a tree-like structure called the
OID tree or registration tree. When an SNMP agent needs to access a specific managed object, it traverses the OID tree to find the object. The MIB object identifier hierarchy and format is shown in
Figure 1‑2.
Absolute OIDs specify a path to an attribute from the root of the OID tree. Absolute OID names always begin with a dot and must specify every node of the OID tree from the top-most node to the specific managed object. For example:
Relative OIDs specify a path to the attribute relative to some node in the OID tree. For example,
2.1.1.1 specifies the
sysDescr object in the
system group, relative to the Internet node in the OID tree.
Note that 2.1.1.7 in this example is a relative OID.
Oracle SNMP Agent provides a file named bea.asn1 for defining the SNMP MIB. For an Oracle Tuxedo 10.0 installation, the
bea.asn1 file resides in the
tux_prod_dir/udataobj/snmp/etc directory, where
tux_prod_dir represents the directory in which the Oracle Tuxedo 10.0 distribution is installed.
The bea.asn1 file for Oracle Tuxedo 10.0 makes the features of the following components recognizable and thus manageable within an SNMP network management framework:
The SNMP MIB defined by the bea.asn1 file for Oracle Tuxedo 10.0 refers to the entire database of management information at the management station or agent. The SNMP MIB, itself, consists of distinct component MIBs, each of which refers to a specific defined collection of management information that is part of the overall SNMP MIB. The management station uses the component MIBs to administer the particular components of the Oracle Tuxedo system, to administer the agents themselves, and to collect information about the managed resources.
|
•
|
Core MIB—OID prefix: .1.3.6.1.4.1.140.300 (or tuxedo)—Contains the MIB objects for controlling the operation and configuration of a Tuxedo application. This MIB contains the main information groups for Tuxedo applications, including domains, machines, queues, servers, routing, clients, and services. For a detailed description, see “Core MIB” on page 2‑1.
|
|
•
|
Domains MIB—OID prefix: .1.3.6.1.4.1.140.300 (or tuxedo)—Contains the MIB objects for describing the interaction between Tuxedo domains (Tuxedo business applications). For a detailed description, see “Domains MIB” on page 3‑1.
|
|
•
|
Workstation MIB—OID prefix: .1.3.6.1.4.1.140.300 (or tuxedo)—Contains the MIB objects for specifying information about Tuxedo client workstations including workstation listeners and handlers. For a detailed description, see “Workstation MIB” on page 7‑1.
|
|
•
|
Application Queue MIB—OID prefix: .1.3.6.1.4.1.140.300 (or tuxedo)—Contains the MIB objects for managing access to Tuxedo application queues. The groups include objects for managing queue spaces, queues, messages, and transactions. For a detailed description, see “Application Queue MIB” on page 8‑1.
|
|
•
|
EventBroker MIB—OID prefix: .1.3.6.1.4.1.140.300 (or tuxedo)—Contains the MIB objects for describing current event subscriptions, defining new subscriptions, or invalidating subscriptions. For a detailed description, see “EventBroker MIB” on page 9‑1.
|
|
•
|
Traps MIB—OID prefix: .1.3.6.1.4.1.140.300 (or tuxedo)—Contains the MIB objects for specifying the trap notifications generated by the SNMP agent for Oracle SNMP Agent, and for specifying the objects passed in the variable bindings for the traps. For a detailed description, see “Traps MIB” on page 10‑1.
|
|
•
|
Oracle System MIB—OID prefix: .1.3.6.1.4.1.140.1 (or beaSystem)—Contains the MIB objects for passing the trap notifications generated by the Oracle SNMP Agent Integrator polling rules. As an example, a rule-action might specify that when the value of the polled object at OID .1.3.6.1.4.1.140.1.0 is greater than 20, send a trap with a specific trap ID of 200; when the object’s value becomes less than 20, send a trap with a specific Trap ID of 300. For a description of the Oracle SNMP Agent Integrator polling feature, see “Using the Oracle SNMP Agent Integrator for Polling” in the Oracle Tuxedo SNMP Agent Administration Guide.
|
|
•
|
Oracle Agent Integrator MIB—OID prefix: .1.3.6.1.4.1.140.200 (or beaIntAgt)—Contains the MIB objects for creating user-defined traps that are generated by the Oracle SNMP Agent Integrator according to user-defined polling rules. You can configure the Oracle SNMP Agent Integrator running on the managed node to perform local polling and generate SNMP trap notifications, or execute a system command when certain conditions are met. Individual rules, stored as MIB objects, can be activated and deactivated by the management station. For a description of polling rules, see “Configuration Files” in the Oracle Tuxedo SNMP Agent Administration Guide.
|
The bea.asn1 file defines a full range of Oracle Tuxedo system and application events in accordance with RFC 1215, Trap definitions. These system and application events are transmitted as enterprise-specific traps to the management station. For a list of these traps, see
“Traps MIB” on page 10‑1.
The SNMP agent for Oracle SNMP Agent uses a file named mib.txt to set up its local SNMP MIB on the managed node (machine). The
mib.txt file, similar to the
bea.asn1 file, provides a textual description of the content of the SNMP MIB. By default, the
mib.txt file resides in the
tux_prod_dir/udataobj/snmp/etc directory, where
tux_prod_dir represents the directory in which the Oracle Tuxedo 10.0 distribution is installed. For more information about using the
mib.txt file to create the local SNMP MIB on a managed node, see
“Oracle SNMP Agent Integrator Commands” in
Oracle SNMP Tuxedo Agent Administration Guide.
|
•
|
-1 if the object is numeric
|
|
•
|
A dash (-) if the object data type is DisplayString
|
Instead of referring to groups and
managed objects, as is common in SNMP terminology, the TMIB defines application resources as
classes and
attributes. Classes
are the administrative class definitions that make up the TMIB. Each class has a set of attributes that identifies individual items in the class. Examples of TMIB classes are:
