If the managed object you want to monitor is supported by a SMUX subagent that has been installed on the managed node, the subagent automatically registers its section of the OID tree with the Oracle SNMP Agent Integrator when the subagent is started. This can be modified using OID_CLASS entries in the Oracle SNMP Agent configuration file, as described in “Configuration Files” on page 9‑1.For peer SNMP agents (or DPI or SMUX master agents), you must define the segments of the OID tree supported by those agents in NON_SMUX_PEER entries in the Oracle SNMP Agent configuration file. This is described in “Configuring the Oracle SNMP Agent Integrator for Use with Multiple SNMP Agents” on page 6‑1.The Oracle SNMP Agent Integrator directly supports the following MIB groups: MIB-II system and snmp groups, the SMUX MIB, and the Oracle SNMP Agent beaintAgtTable in the SNMP agent MIB.Each polling instruction for the SNMP Integrator is called a rule. Rules are defined under the RULE_ACTION entry in the Oracle SNMP Agent beamgr.conf configuration file. You can use your favorite text editor to modify this file. (For information on how to create rules, see “Creating New Polling Rules” on page 7‑15.) Rules are explained in “Oracle SNMP Agent Integrator Rules” on page 7‑3, while “Configuration Files” on page 9‑1 provides the complete syntax for the RULE_ACTION entries.When a polling threshold is crossed, the Oracle SNMP Agent Integrator sends an enterprise-specific SNMP trap notification to the destinations specified by the TRAP_HOST entries in the Oracle SNMP Agent configuration file. Some configuration is required on your SNMP-compliant management system to make use of the traps that are thus generated. The exact set of steps you need to perform varies, depending upon which management system you are using. Typically, some configuration or mapping is required to get the management system to perform a desired action when a trap is received. For example, you might want the management system to turn an icon red when a trap is received. Consult your management system documentation for specific instructions.The Oracle SNMP Agent Integrator begins executing all valid polling rules when it is started. For more information, see “Starting Oracle SNMP Agent Integrator Polling Activity” on page 7‑14.Polling rules are available as MIB objects; thus you can de-activate or re-activate polling from the management station by means of an SNMP Set request. This topic is described in “Starting Oracle SNMP Agent Integrator Polling Activity” on page 7‑14.
• A condition (or threshold) for which the integrator is to check. (This is described further in “Conditions” on page 7‑4.)
• An action to take if the specified threshold is crossed. (This is described in “States and Transitions” on page 7‑11.)
• A polling frequency (specified in seconds), that is, the time delay between each access of the specified object valueWhen the Oracle SNMP Agent Integrator polls, it checks to determine if a specified condition holds. A condition is defined as a relationship between an object (specified by its object identifier) and a value.
For example, suppose that you want the Oracle SNMP Agent Integrator to check if any server group is inactive. The state of the server group is represented by the tuxTgroupState object in the beaSysPerf group. The Oracle SNMP Agent component uses SNMP multiplexing (SMUX) protocol to talk to the Oracle SNMP Agent Integrator, and to supply the value of the object to the Oracle SNMP Agent Integrator on the same machine.object in the beaSysPerf group. This subagent uses SMUX protocol to talk to the Oracle SNMP Agent Integrator.The expression VAL() is used to obtain the value of the tuxTgroupState object. The specified condition is obtained if any server group is not active (!=1). In this example, the initial dot indicates that this is an absolute OID; that is, the path to the tuxTgroupState object is .1.3.6.1.4.1.140.300.4.1.1.4. The asterisk (*) wildcard for the instance index indicates that the condition is satisfied if any tuxTgroupState is not equal to 1. Use 0 as the instance index for scalar objects. For more information, see “Instance Indexes” on page 7‑10.In this example, grpState is the name of the rule. The Oracle SNMP Agent Integrator checks the server group state every 1 minute (60). If any value of tuxTgroupState is not equal to 1, TRAPID_ERR=300 instructs the Oracle SNMP Agent Integrator to generate an enterprise-specific trap with a specific-trap type number of 300.
Note: (The MIB objects whose values the Oracle SNMP Agent Integrator can obtain depend on the MIB objects supported by the agents or subagents that the Oracle SNMP Agent Integrator is managing. In the previous example, the Oracle SNMP Agent Integrator can poll for the tuxTgroupState object value only if the tux_snmpd subagent is running on the managed node. The MIB objects that the Oracle SNMP Agent Integrator can access through a peer SNMP agent depend on the NON_SMUX_PEER entries in the Oracle SNMP Agent configuration file, as explained in “Using Multiple SNMP Agents” on page 6‑1.The Oracle SNMP Agent Integrator can also obtain MIB object values from SNMP peer (non-SMUX peer) agents on either the same machine or other machines in the network. For example, suppose that a peer SNMP agent supports the MIB-II interfaces group. If so, you might want the Oracle SNMP Agent Integrator to check if a physical interface is not operational. This feature of the interface is represented by the ifOperStatus object in the ifTable in the MIB-II interfaces group. In this case, you want to know whether the value of ifOperStatus is not equal to 1. (An interface is operational if its ifOperStatus value is 1.) If you want to check the ifOperStatus value for the first interface on the machine, you could use the following condition:This condition holds if, and only if, the first interface in the ifTable is operational. The last numeral, 1, specifies the instance index—the first interface entry in the table.If the condition is satisfied, you want the Oracle SNMP Agent Integrator to take some action. For example, if the ifOperStatus value for an interface is not 1 (that is, the interface is not up), you might want the Oracle SNMP Agent Integrator to notify the management station. To do this, you can specify that the Oracle SNMP Agent Integrator send an enterprise-specific SNMP trap to the management station with a special specific-trap value that identifies the cause of the trap to you (the system administrator).Instead of requesting this notification if a specific interface (such as the first one in the ifTable) is down, you might want to be notified if any of the interfaces is down.In this example, checkIf is the name given to this particular rule. The value 120 indicates that the Oracle SNMP Agent Integrator should check the interface every two minutes. By using the asterisk wildcard for the instance index, the condition is satisfied if any interface in the ifTable has an ifOperStatus not equal to 1; that is, all instances are checked. If the value of the OID is not equal to 1 (the interface is not up) for any instance, an enterprise-specific trap is sent with a specific trap ID of 300.Conditions are of two types, simple and complex. A simple condition consists of a relation between a managed object and a value. All of the examples in the previous sections have been simple conditions.You can use the logical operators AND, OR, and NOT to define complex conditions. For example, if A and B are two simple conditions, you can specify a complex condition where both A and B occur.
Logical negation. The threshold is crossed if and only if condition_A does not hold. Logical disjunction. The threshold is crossed if and only if either condition_A or condition_B obtain. Logical conjunction. The threshold is crossed if and only if both condition_A and condition_B obtain.For example, you might not want the Oracle SNMP Agent Integrator to send an alarm when ifOperStatus is not up for an interface if you have taken that interface down for repair. In that case, you could define a rule that asks the Oracle SNMP Agent Integrator to determine if two conditions hold: ifOperStatus is not up AND ifAdminStatus is up. That is, you want to be notified if the interface should be up but is not.To do this, you might modify your checkIf rule as follows:In this example, the Oracle SNMP Agent Integrator checks the interfaces every minute (60) and generates an enterprise-specific trap, with a specific trap value of 301, if any of the interfaces is not up (ifOperStatus not equal to 1) but has an ifAdminStatus value of up (that is, the interface should be up but it is not).Is one of the relations described in the table titled “Relations for Defining Conditions” on page 7‑4.Is specified in one of the formats described in “Specifying Object Identifiers in Conditions” on page 7‑9.
•
•
• IP address (in the form number1.number2.number3.number4)In defining polling conditions, the object identifier (OID) must be specified numerically, not using textual symbols (other than MIB II [mib-2] or enterprises as indicated in the following list). One of the following formats can be used to specify the object identifier:
• An absolute object identifier, that is, the full path to the object is specified from the root of the OID tree. An initial dot is used to indicate that the path starts at root, (for example, .1.3.6.1.2.1.1.1.0). Note that the trailing zero in this example is the instance index.When the reserved word mib-2 appears as the leading sub-oid, .1.3.6.1.2.1 is assumed to be prefixed to the rest of OID. For example:When the reserved word enterprises appears as the leading sub-oid, .1.3.6.1.4.1 is assumed to be prefixed to the rest of OID. For example:If there is no leading “.” and the OID starts with a number, .1.3.6.1.4.1 is assumed to be prefixed to the rest of OID. For example:Columnar objects are used to represent a column of a tabular MIB group. Columnar objects, accordingly, can have multiple instances. To specify an instance, the index is appended to the rest of the OID. If the index is a single attribute, the last number in an OID is used to specify the particular instance. If the more than one attribute is required to uniquely identify an instance, an instance number for each attribute is appended to the OID, separated by a dot, in the order specified by the INDEX definition in the ASN.1 file.For example, suppose that you want to check for the condition in which the state of a particular server is anything but active. To uniquely specify a server instance, you require both the group number and the server ID. The INDEX entry for tuxTsrvrTbl in the ASN.1 file specifies the following as an INDEX to particular instances.The relative OID for tuxTsrverState is the following:Note that the order of the two attribute instances added to the tuxTsrvrState OID is indicated by the INDEX definition above: tuxTsrvrGrpNo followed by tuxTsrvrId.You can use a specific number to specify a particular instance or the asterisk wildcard to specify all instances. Use zero as the instance index in the case of scalar objects (objects that can have only one instance). Use the asterisk wildcard only to represent all instances of a columnar object. For example:specifies all of the instances of a columnar object. When a wildcard is used to define a condition, the condition is satisfied if any instance satisfies the condition.
• When you use a wildcard to define a condition, the condition is satisfied if any instance satisfies the condition. For example, VAL(.1.3.6.1.2.1.2.1.2.2.1.8.*) == 1 is satisfied if 1 is the value of any instance. Once the condition is satisfied, the rule is in the ERR state. The rule remains in the ERR state as long as any instance satisfies the condition. The rule transitions to the OK state only when no instance satisfies the rule.Associated with each active polling rule is a state. There are two possible states for an active rule:
•
Note: The Oracle SNMP Agent Integrator carries out an action only when a transition occurs. Continued polling does not result in duplicate actions as long as the rule remains in the same state. This restriction prevents duplicate traps from being generated in response to detection of a single event.The program specified by command is executed if the state of the rule transitions from OK to ERR.The program specified by command is executed if the state of the rule transitions from ERR to OK.
Note: The string specifying the command to be executed must be in quotes. For example: COMMAND_ERR = “usr/mybin/test.ksh”.The statements specifying actions must be placed within curly braces. When multiple commands are specified in a rule, the commands must be separated by spaces and command must be enclosed in quotes.A string containing the name of the rule and the direction of the state transition (OK to ERR or ERR to OK) is passed as an argument to the script or program called by the COMMAND_ERR or COMMAND_OK actions.A TRAPID_ERR action passes a string in the variable bindings of the trap that takes the following form:A TRAPID_OK action passes a string in the variable bindings of the trap that takes the following form:what is bea?the last word in “Oracle SNMP Agent Integrator polling alarms use bea“
Note: as an enterprise identifier, whereas the Oracle Tuxedo SNMP Agent system traps use tuxedo as the enterprise identifier.In the following example, the Oracle SNMP Agent Integrator polls every ten minutes (600) to determine if disk capacity in use is greater than 90 percent. If any file system has more than 90 percent capacity in use, an enterprise-specific trap with number 102 is generated. If subsequently all the file systems have less than or equal to 90 percent of capacity in use, an enterprise-specific trap with trap number 202 is generated.In the next example, a Tuxedo application is checked to determine if the transaction triptime exceeds 36 msec. If the threshold is crossed, an enterprise-specific trap is generated and a user script, logtime, is invoked to log the time of the event. If the triptime is subsequently less than 36 msec after having crossed that threshold on the previous poll, an enterprise-specific trap with a number of 302 is generated.In the next example, the Oracle SNMP Agent Integrator polls every five seconds to check whether the number of requests completed by the Tuxedo server Server1 is greater than six. If it is, an enterprise-specific trap is generated with a specific trap number of 210 and the command C:/etc/srv_reqs.cmd is executed.Polling rules are defined as RULE_ACTION entries in the Oracle SNMP Agent beamgr.conf configuration file. The default location of this file is C:\etc on Windows systems and /etc on UNIX systems. Individual rules are MIB objects, stored as an entry (row) in the beaIntAgtTable.The status of each rule entry determines whether the Oracle SNMP Agent Integrator executes that rule (that is, whether the Oracle SNMP Agent Integrator actively checks the condition specified in the rule). The status of each rule entry is stored in the beaIntAgtStatus object. Polling is active for a rule if the status of that rule is valid (integer value of 1). Polling is inactive for a rule if its status has been set to inactive (integer value of 3). The specific rule can be Set from a management station (such as OpenView or SunNet Manager) by using the unique name of the rule as the key field used to specify the entry instance (row).
Note: The Oracle SNMP Agent Integrator begins to execute all polling rules defined in RULE_ACTION entries in the Oracle SNMP Agent beamgr.conf configuration file when it first starts up. The status of each rule object in the beaIntAgtTable is valid at startup.
• Use a text editor, such as vi, to add a RULE_ACTION entry to file, making sure that you conform to the syntax of the rule, as described in “Configuration Files” on page 9‑1. However, if the Oracle SNMP Agent Integrator is already running, the new rule does not take effect until you execute the following command:
• Since individual rules are MIB objects, stored as an entry (row) in the beaIntAgtTable, you can use an SNMP manager (or the snmptest utility) to create a new entry (row) in the beaIntMgtTable. (The SNMP manager must have the ability to issue SNMP Set requests that contain multiple objects in a single Set request.) To create the new row, issue a Set request after you specify an index value that does not already exist in the table. This Set request causes a new RULE_ACTION entry to be created in the configuration file.Oracle SNMP Agent Integrator polling rules can be modified in the same two ways they can be created:
• Use a text editor to delete (or comment out) or modify a RULE_ACTION entry in the beamgr.conf file. This change does not take effect unless you issue the following command to force the Oracle SNMP Agent Integrator to re-read its configuration file:
• Remove the RULE_ACTION entry from the configuration file.You can turn off a polling rule by commenting out or deleting that RULE_ACTION entry in the Oracle SNMP Agent beamgr.conf configuration file. However, for this to take effect, you need to execute reinit_agent snmp_integrator. This execution, in turn, causes the Oracle SNMP Agent Integrator to re-read its configuration file.
• Polling for that rule can be de-activated from the management station (or by using the snmptest utility packaged with the Oracle SNMP Agent Integrator) by setting the value of that object to inactive (an integer value of 3). Setting the value to 2 (invalid) causes the RULE_ACTION entry to be deleted from the configuration file. The following figure shows the rule diskchk, discussed earlier, being set to inactive. Note that the read/write community string (in this example, iview) is required for set permission.Figure 7‑1 Setting a Polling Rule to InactiveWhen a polling rule has been de-activated using a Set request from a management station, the rule can be re-activated using a Set request to set the value of the corresponding beaIntAgtStatus object to valid (integer value of 1).