![]() |
![]() |
![]() |
![]() |
![]() |
Starting from Oracle Tuxedo 12c Release 2 (12.2.2), Oracle Tuxedo SNMP can compile with SNMPv3. For more information, see Using SNMPv3.As shown in Figure 1‑1, Oracle SNMP Agent provides the SNMP links from Tuxedo applications to SNMP-capable management stations (consoles). Also shown in the figure is that Oracle SNMP Agent allows multiple SNMP agents and subagents—from any vendor—to operate on the same machine.Figure 1‑1 Oracle SNMP Agent for Oracle Tuxedo
• In the model, shown in Figure 1‑2, a network manager exchanges monitoring and control information about network and system resources with distributed software processes called agents.Figure 1‑2 Manager/Agent ModelAny network or system resource that is manageable through this exchange of information is a managed resource. A managed resource could be a software resource, such as a message queue or an Oracle Tuxedo application, or a hardware resource, such as a router or NFS file server.The manageable features of resources, as defined in an SNMP-compliant MIB, are called managed objects (also termed management variables or variables). Examples of managed (or MIB) objects include the state of an Oracle Tuxedo domain, the number of users currently logged on to an Oracle Tuxedo system, Tuxedo processes, and Tuxedo application variables. When the heterogeneous components of an enterprise’s distributed systems are defined within a common MIB on the management framework, a unified perspective and single access point is provided for managing system and network resources.Figure 1‑3 shows an example SNMP installation that provides system administrator access to management information from a management console. Management commands are issued to SNMP agents to collect the values of various management variables (as defined in the platform’s MIB).The Oracle SNMP MIB supports a full range of Oracle Tuxedo system and application events. These system and application events are transmitted as enterprise-specific traps. See the Oracle Tuxedo SNMP Agent MIB Reference for more information about the Oracle SNMP MIB.
• Figure 1‑4 shows how the Tuxedo SNMP agent, the Oracle SNMP Agent Integrator, and the Oracle SNMP MIB work together to incorporate Tuxedo information within an SNMP management framework.Figure 1‑4 Oracle SNMP Agent Components
Note: The Oracle SNMP Agent component files reside in the tux_prod_dir/bin directory and 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 Tuxedo SNMP agent, named tux_snmpd, responds to requests from SNMP managers and generates SNMP trap notifications for Tuxedo system and application events. The tux_snmpd executable translates management information for Tuxedo applications into a form compatible with SNMP, and stores the information in a local SNMP MIB for later access by the SNMP manager (a front-end process running in the SNMP network management framework).The tux_snmpd executable can be started as an SNMP agent or an SNMP multiplexing (SMUX) subagent. The SMUX protocol is defined in RFC 1227.The Oracle SNMP Agent Integrator, named snmp_integrator, provides both SNMP master agent and SMUX master agent capabilities. As such, the snmp_integrator executable enables multiple SNMP agents and SMUX subagents from any vendor to coexist on the same managed node (machine) and appear as a single SNMP agent to the SNMP manager.
Provides a textual description of the content of the SNMP MIB similar to the bea.asn1 file—in fact, mib.txt is created from the bea.asn1 file.Used by tux_snmpd at startup to set up its local SNMP MIB on the managed node.The SNMP MIB, created from the bea.asn1 and mib.txt files, makes the features of the following components manageable within an SNMP network management framework:
Also known as the “Oracle SNMP Agent configuration file.” Contains the user-defined operational configurations read by tux_snmpd and snmp_integrator at startup. Also known as the “Oracle SNMP Agent passwords configuration file.” Contains the user-defined password configurations (SNMP community names, SMUX password) read by tux_snmpd and snmp_integrator at startup.The default read-only community name is public, and the default read-write community name is iview. The default SMUX password is no password.For more information about the Oracle SNMP Agent configuration files, see “Configuration Files” on page 8‑1.The Oracle SNMP Agent software provides the following commands to control tux_snmpd and snmp_integrator processes.
Windows and UNIX: Causes the specified tux_snmpd and/or snmp_integrator processes to re-read the local Oracle Tuxedo configuration files. On UNIX systems, this command must be run with root permissions. Windows and UNIX: Lists the names and process IDs (PIDs) of the specified tux_snmpd and/or snmp_integrator processes. * On a Windows system, an Oracle SNMP agent (tux_snmpd, snmp_integrator) process can only be stopped as a Windows service; command-line shutdown is not supported.The Oracle SNMP Agent software provides the following utilities to install and test tux_snmpd and snmp_integrator processes:
Sends an SNMP TrapRequest message to a host. Receives and logs SNMP TrapRequest messages sent on a local machine to the SNMP trap port. Traverses the object identifier (OID) tree using the SNMP GetNextRequest message to query managed objects.