|
|
|
|
|
|
At startup, the Oracle SNMP Agent Integrator (snmp_integrator) and the Oracle SNMP agent (tux_snmpd) read the absolute pathname specified by the BEA_SM_BEAMGR_CONF environment variable to locate the beamgr.conf configuration file on the host system. The Oracle SNMP Agent Integrator and agents read certain configurations in the beamgr.conf file.
1 (default): Only accepts and sends messages in SNMPv1.
3: Only accepts and sends messages in SNMPv3.
If you do not specify SYS_VERSION, SNMPv1 is used.Specifies that the engineID should be built from the given text STRING. The length of STRING must be less than 26.
Tuxedo SNMP's engineID includes two parts: the header and the given text STRING. The header's hexadecimal digits are 8000008C04.
In addition, snmp_integrator's engineID is built from the given text STRING directly, but tux_snmpd's engineID is built from the give text STRING and its logical name.
For example:
ENGINE_ID tux_snmpd
TMAGENT Dom1_SnmpAgt …
snmp_integrator's engineID is built from string tux_snmpd; its value is 8000008C047475785F736E6D7064.tux_snmpd's engineID is built from string tux_snmpdDom1_SnmpAgt; its value is 8000008C047475785F736E6D7064446F6D315F536E6D70416774.Because these options are put in the configuration file, the keys of authentication and privacy are put in the configuration file rather than the passwords of them. -v option in SNMP utilities is ignored, because only 3 is valid. For more information about command line options, see Oracle SNMP Agent Utilities.
In SNMPv3, trap_community indicates a CMD_PARAMETERS paraName value that indicates which security and message processing is to be used in sending messages to a particular target.Indicates the engineID of the authoritative side of the message. The authoritative side is the SNMP agent. Valid values are:
- An octet string of 1 to 32 octets (2 to 64 hex digits).
- A '-' (dash) indicates the default value.
The default value is the local SNMP agent's engineID.Indicates whether the keys defined by authKey and privKey are localized or non-localized. Localized indicates that they have been generated with the appropriate engineID making the key usable only at one snmpEngine. Non-localized indicates the key may be used at different snmpEngines. The authKey and privKey, if both are specified, must both be localized or both be non-localized.
- L indicates keys are localized.
- M indicates keys are non-localized.
- '-' (dash) indicates default value is non-localized key.Authentication protocol to be used on authenticated messages on behalf of this user. It indicates the authentication protocol to be used on authenticated messages on behalf of this user. Valid values are:
- MD5 indicates HMAC-MD5.
- SHA indicates HMAC-SHA.
- '-' (dash) indicates the default value.
The default value is MD5 if an authentication key is specified; if no authentication key is specified, no authentication can be done for messages to/from this user.Authentication key to be used in authenticating messages on behalf of this user. The keyType field will indicate whether the key is localized or non-localized. Valid values are:
- An octet string of 16 bytes (32 hex digits) when authProto is MD5.
- An octet string of 20 bytes (40 hex digits) when authProto is SHA.
Default value is no key, indicating no encryption.Privacy protocol to be used on encrypted messages on behalf of this user. If authentication is not requested, this field is ignored. Valid values are:
- DES indicates CBC-DES (only with the additional encryption product).
- AES indicates CFB128-AES-128 (only with the additional encryption product).
- '-' (dash) indicates default value.
The default value is no privacy, meaning no encryption will be done on messages to/from this user.The privacy key to be used in authenticating message to and from this user. This field will be ignored when privProto is specified or defaulted as '-'. The keyType field will indicate whether the key is localized or non-localized. Privacy can be requested only if authentication is also requested. If authentication is not requested, this field is ignored. The privacy key and the authentication key are assumed to have been generated using the same authentication protocol (HMAC-MD5 or HMAC-SHA). Valid values are:
- An octet string of 16 bytes (32 hex digits) if the key is localized or if the key is non-localized and the authProto is HMAC-MD5.
- An octet string of 20 bytes (40 hex digits) if the key is localized or if the key is non-localized and the authProto is HMAC-SHA.
- '-' (dash) indicates default value.
The default value is no key, indicating no encryption.Maps a security name into a named group. Several group directives can specify the same group name, allowing a single access setting to apply to several users.
- groupName: Group name for the view-based access control model and must be unique to the SNMP agent.
- securityModel: Security model for this entry. The valid value is usm.
- securityName: User name defined by USM_USER.Defines a named view - a subset of the overall OID tree. This is most commonly a single subtree, but several view directives can be given with the same view name (VNAME), to build up a more complex collection of OIDs.Is either included or excluded, which can again define a more complex view. Valid values are: included or excluded.Must be null ("").Indicates the securityLevel for this entry. Valid values are:
- none: Indicates there is no authentication or privacy protocol.
- auth: Indicates authentication protocols are applied but no privacy protocol is applied.
- priv: Indicates both authentication and privacy protocols are applied.Specifies how CONTEXT should be matched against the context of the incoming request. Valid values are:
- exact indicates entire contextName must match.
- prefix indicates only the prefix of the contextName must match.Indicates the name of the view to be applied when read options are performed under control of this entryIndicates the name of the view to be applied when write operations are performed under control of this entry.Sets the Oracle SNMP Agent Integrator timeout in waiting for responses to requests. The default timeout is 30 seconds.You can set the Oracle SNMP Agent Integrator timeout by adding an INTEGRATOR_TIMEOUT entry as follows:Specifies the OIDs supported by an SNMP agent when it is running as a peer of the Oracle SNMP Agent Integrator. For more information, see “NON_SMUX_PEER Entry” on page 8‑9.Specifies an Oracle SNMP Agent Integrator polling rule. This allows threshold-checking to be offloaded from the network management system to the distributed integrator agents on managed nodes. For more information, see “RULE_ACTION Entry” on page 8‑15.Defines the Oracle Tuxedo domain that an agent is to monitor. There must be one TMAGENT entry for each Tuxedo SNMP agent on a managed node. The format of the entry is as follows:TMAGENT logical_agent_name tuxdir tuxconfig_pathA string that must be unique among all TMEVENT_FILTER entries in the Oracle SNMP Agent configuration file. The maximum length of the string is 16 characters.Maps the event filter to a particular agent on that node. A logical agent name is a string up to 32 characters long. The logical agent name is the name given to the Windows service on a Windows system that starts the agent, or the name specified in the -l option when starting the agent from the command line on a UNIX system.A Tuxedo event name expression. This string can be a maximum of 255 characters long. For information about event name expressions, which are regular expressions, see reference page tpsubscribe(3c) in Oracle Tuxedo ATMI C Function Reference.This name must match a Tuxedo event name for that event to be forwarded as an SNMP trap. For a list of event names, see reference page EVENTS(5) in Oracle Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference.The default is all events. If NONE is used, no events are forwarded and the other parameters in the TMEVENT_FILTER entry can be omitted. An entry of NONE overrides all other event filter entries for the same logical agent name. For example:An event filter expression. This string can be a maximum of 255 characters long. Each Tuxedo event is accompanied by an FML buffer that contains pertinent information about the event. The buffer is evaluated with respect to this filter if the filter is present. If the buffer content is evaluated to TRUE, the event is forwarded; otherwise the event is not forwarded. Oracle SNMP Agent uses this filter as an argument for a call to tpsubscribe(). For more information, see reference page tpsubscribe(3c) in Oracle Tuxedo ATMI C Function Reference.Can be either active or inactive. If the status is active, the filter is being used; otherwise the filter is not being used.There is a MIB table that corresponds to the TMEVENT_FILTER entries in the Oracle SNMP Agent configuration file. These entries can be updated dynamically using an SNMP Set request. For more information, see the beaEvtFilterTable object in “Core MIB” in Oracle Tuxedo SNMP Agent MIB Reference.To configure the Oracle SNMP Agent Integrator to access MIB objects through a peer SNMP agent (for example, a non-SMUX master agent or a non-SMUX peer agent), add the NON_SMUX_PEER entry to the beamgr.conf file in the following format:when the SNMP agent is remote from the Oracle SNMP Agent Integrator. If ip_address or hostname is not specified, the Oracle SNMP Agent Integrator assumes that the peer SNMP agent is on the same managed node as the Oracle SNMP Agent Integrator.In SNMPv1, it specifies the community to be used by the Oracle SNMP Agent Integrator when the SNMP agent is polled. The special value * is used to specify that the Oracle SNMP Agent Integrator should use the community supplied by the SNMP manager.
In SNMPv3, it indicates a CMD_PARAMETERS paraName value that indicates which security and message processing is to be used in sending messages to a particular target.If an SNMP agent tries to register a subtree at a priority that is already taken, the Oracle SNMP Agent Integrator repeatedly increments the integer value (lowering the priority) until an unused priority is found. A special priority -1, causes the selection of the highest available priority. When a request is made to register with priority -1, registration is made at the highest available number below 20. If the priority field is missing, the MIB tree is exported at a -1 priority.Specifies the time interval in seconds for which the Oracle SNMP Agent Integrator waits for the replies from this SNMP agent for the particular MIB group. The default value is three seconds. This default can be changed by setting the BEA_PEER_MAX_WAIT environment variable to a different value.The access (ro or rw), priority, and timeout fields are optional. However, you must specify access and priority if you need to specify timeout, and you must specify access if you need to specify priority for a MIB tree.Note that a subtree registration hides the registrations by other SNMP agents/subagents of objects within the subtree. So, if an agent A registers subtree .1.3.6.1.4.1.140 and another agent/subagent, B, registers subtree .1.3.6.1.4.1.140.1, agent/subagent A is consulted for all the objects under the .1.3.6.1.4.1.140.1 subtree.At any point, the command reinit_agent snmp_integrator can be invoked to force the Oracle SNMP Agent Integrator to re-read its configuration file.The Oracle SNMP Agent Integrator disallows/disregards any attempt to register above, at, or below the SNMP (mib2.snmp) and SMUX subtrees of the MIB.The following examples are provided to illustrate the use of the NON_SMUX_PEER entry:
if (VAL(oid) rel_operator value) logical_op ( cond_2 ) ...
{ TRAPID_ERR=enterprise_specific_trapid
TRAPID_OK=enterprise_specific_trapid
COMMAND_ERR=executable COMMAND_OK=executable }