|
|
To integrate BEA SNMP Agent into your management framework, you need to set up the BEA SNMP Agent software on the managed node and on the management framework. The following sections describe the procedure for setting up the BEA SNMP Agent on the managed node:
The BEA SNMP Agent files reside in the directories shown in the following figure.
| Note: | tux_prod_dir represents the directory in which the BEA Tuxedo 10.0 distribution is installed. |
BEA SNMP Agent provides the following two configuration files: beamgr.conf and beamgr_snmpd.conf. The beamgr.conf file, also known as the "BEA SNMP Agent configuration file," contains the user-defined operational configurations read by the Tuxedo SNMP agent (tux_snmpd) and the BEA SNMP Agent Integrator (snmp_integrator) at startup.
The beamgr_snmpd.conf file, also known as the "BEA 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 BEA SNMP Agent configuration files, see Configuration Files.
To configure BEA SNMP Agent, follow these steps:
The Tuxedo SNMP agent tux_snmpd is installed one at a time. On a Windows system, if you do not install BEA Tuxedo first, you do not get the option to install tux_snmpd. For detailed information about how to install BEA SNMP Agent, see Installing the BEA Tuxedo System.
Some attributes of Tuxedo resources are accessible globally (that is, no matter which Tuxedo node they are on) while others are accessible only by a BEA SNMP agent local to the same machine. To access managed objects that are only accessible locally, you must install BEA SNMP agents on each machine where these resources reside, or install a BEA SNMP agent on the master node and execute it with the -c option, which enables you to run the agent only on the master node but to still gather information from all machines.
If BEA SNMP Agent is not installed in the same directory as the BEA Tuxedo application, make sure that the bin directory of the appropriate Tuxedo installation precedes any other Tuxedo installations in the PATH system environment variable. This directory order in PATH enables BEA SNMP Agent to have access to the correct Tuxedo dynamic link libraries (DLLs).
Make sure the search path for shared libraries includes $TUXDIR/lib. The search path for shared libraries is:
SHLIB_PATH on HP-UX, LIBPATH on AIX, and LIBRARY_PATH on all other UNIX systems.
Open a command-line shell and copy the BEA SNMP Agent configuration file beamgr.conf to the C:\etc directory:
prompt> md c:\etcprompt> copy tux_prod_dir\udataobj\snmp\etc\beamgr.conf
c:\etc
Log in as root and copy the BEA SNMP Agent configuration file beamgr.conf to the /etc directory:
prompt> suprompt> Password:prompt> cp tux_prod_dir/udataobj/snmp/etc/beamgr.conf /etc
PATH to include the location of the BEA SNMP Agent executables. This step applies to both Windows and UNIX systems.
All users of the installed BEA SNMP Agent products need to update their PATH environment variable to include the location of the BEA SNMP Agent executable files. The following is a UNIX example in C shell:
prompt> set path = ( $PATH tux_prod_dir/bin )
Configure the timeout of your SMUX master, if any (such as snmp_integrator), and of your SNMP manager, to at least 30 seconds. For snmp_integrator, you can set this timeout by adding an INTEGRATOR_TIMEOUT entry to the BEA SNMP Agent beamgr.conf configuration file as follows:
Check that the host name specified in Start->Settings->Control Panel->Network->Identification is all UPPERCASE and matches the host name specified in Start->Settings->Control Panel->Network->Protocols->TCP/IP-> Properties->DNS, which should also be all UPPERCASE.
The default destination for SNMP trap notifications is localhost. To send traps to other destinations, use a text editor to modify the TRAP_HOST entry in the BEA SNMP Agent beamgr.conf configuration file to specify the host name of the target destination machine for SNMP trap notifications, and the port number and community name to use in sending traps.
Typically, the destination is the host machine where the SNMP management framework is located. Some management frameworks use distributed trap daemons that "collect" SNMP trap notifications for forwarding to management stations. In that case, the machine with the trap daemon should be the destination.
For more information, see Configuration Files.
The identity of the BEA Tuxedo application to be managed can be specified in two ways. BEA SNMP Agent uses the following sources in the indicated order of precedence:
TMAGENT entry in the BEA SNMP Agent configuration file. This entry is of the form:
TMAGENT logical_agent_name tuxdir tuxconfig_path
For more information, see Configuration Files.
TUXCONFIG and TUXDIR environment variables
BEA SNMP Agent cannot receive Tuxedo event notifications unless the Tuxedo EventBroker server (TMSYSEVT) is running. To enable forwarding of Tuxedo events as SNMP traps, ensure that the Tuxedo EventBroker servers are running. For information on the Tuxedo EventBroker, see
About the EventBroker in Administering a BEA Tuxedo Application at Run Time and reference page TMSYSEVT(5) in BEA Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference.
If you are using the BEA SNMP Agent Integrator, follow the instructions in Setting Up the BEA SNMP Agent Integrator and set up the BEA SNMP agents and then the BEA SNMP Agent Integrator.
If you want to customize BEA SNMP Agent for tasks such as managing multiple BEA Tuxedo domains concurrently or using nondefault ports for communication with the system manager, perform the following additional steps:
To manage multiple Tuxedo domains on a managed node at the same time, add a TMAGENT entry to the BEA SNMP Agent configuration file for each agent. The TMAGENT entry is of the following form:
TMAGENT logical_agent_name tuxdir tuxconfig_path
To manage multiple domains on a managed node, run a separate Tuxedo agent for each domain being monitored. These agents must be run as SMUX subagents under the BEA SNMP Agent Integrator.
When multiple agents running as SMUX subagents are running on the same node, SNMP manager Set or Get requests to a particular agent must be addressed using a community of the form:
where logical_agent_name identifies the agent to which the SNMP request is forwarded. For example:
If only one agent is running on a node, logical_agent_name is optional in specifying the community in Set or Get requests.
Tuxedo event filters can define a subset of Tuxedo events to be received by the agent for each domain being monitored. You can use TMEVENT_FILTER entries in the BEA SNMP Agent configuration file to define a subset of Tuxedo event notifications that are to be forwarded as SNMP trap notifications. For more information, see Configuration Files. MIB objects corresponding to Tuxedo event filters are described in
Core MIB in BEA Tuxedo SNMP Agent MIB Reference.
By default, an SNMP agent (such as the BEA SNMP Agent Integrator or tux_snmpd when running as an SNMP agent) uses public as the read-only community and iview as the read-write community when communicating with SNMP managers. To define additional community names, specify them in the BEA SNMP Agent passwords file. You can also use the passwords file to specify a password for the BEA SNMP Agent Integrator to use for authenticating connection requests from SMUX subagents.
Open a command-line shell and copy the BEA SNMP Agent beamgr_snmpd.conf passwords file to c:\etc. For example:
prompt> copy tux_prod_dir\udataobj\snmp\etc\beamgr_snmpd.conf
c:\etc
Copy the BEA SNMP Agent beamgr_snmpd.conf passwords file to the /etc directory and make the copy readable and writable only by root. For example:
prompt> cp tux_prod_dir/udataobj/snmp/etc/beamgr_snmpd.conf prompt>
/etc chmod 600 /etc/beamgr_snmpd.conf
DISABLE_SET entry in the passwords file as follows:
If there is no DISABLE_SET entry in the passwords file, the agent has both Set and Get capability.
For more information, see Configuration Files.
The environment variable BEA_SMUX_PASSWD specifies the password that the SNMP agent uses when registering with a SMUX master agent, such as the BEA SNMP Agent Integrator. This environment variable is required only if the SMUX master agent expects a password. If this environment variable is not set, a password is not specified by tux_snmpd when registering.
By default, BEA SNMP agents assume the following port numbers as specified by SNMP and SMUX standards:
snmp 161/udp
snmp-trap 162/udp
smux 199/tcp
If the default port assignments are not sufficient for your needs, you can define these services on other ports, or use the appropriate command-line options when starting SNMP agents to assign them to nondefault ports.
To modify or define the services, add the appropriate lines in the root_directory\system32\drivers\etc\services file. For example:
snmp 161/udp snmp
snmp-trap 162/udp snmp
Consult your Windows system administrator for the default settings used for your SNMP-related services.
ypwhich command to determine if an NIS server or map master is available. For example:
prompt> ypwhich
zort.kremvax.com
ypcat command to determine if the services are available.
prompt> ypcat services | grep snmp
snmp-trap 162/udp snmptrap
snmp 161/udp
/etc/services file.
prompt> cat /etc/services | grep snmp
snmp-trap 162/udp snmptrap
snmp 161/udp
To establish the SNMP services, refer to your UNIX system documentation as needed for instructions specific to your UNIX platform.
To manage multiple BEA Tuxedo domains, you can run multiple BEA SNMP agents on the same node. Each agent can manage only one domain. To manage multiple domains, you must have the BEA SNMP Agent Integrator running and the agents must be started as SMUX subagents.
On startup, a Tuxedo SNMP agent checks for a TMAGENT entry in the BEA SNMP Agent configuration file that matches its logical agent name. A TMAGENT entry provides a path to the Tuxedo domain to be monitored. If no matching TMAGENT entry is found, the agent connects to the Tuxedo domain specified in the TUXCONFIG
and TUXDIR environment variables. The agent exits if the TUXCONFIG or TUXDIR environment variable is not defined and no appropriate TMAGENT entry is found in the BEA SNMP Agent configuration file. For more information, see Configuration Files.
The tux_snmpd binary is the Tuxedo SNMP agent that supports the Tuxedo SNMP MIB. For a description of the supported MIB groups and objects, see BEA Tuxedo SNMP Agent MIB Reference.
The BEA SNMP agent can run as an SNMP agent or as a SMUX subagent.
When the BEA SNMP agent starts up as an SNMP agent, it generates a coldStart trap. The destination host, port, and community used when sending traps are as specified in the TRAP_HOST entry in the BEA SNMP Agent beamgr.conf configuration file. For more information, see BEA SNMP Agent Configuration.
When running as a SMUX subagent, the BEA SNMP agent specifies a password to the SMUX master agent at the time of registration if the environment variable BEA_SMUX_PASSWD has been defined. In that case, the BEA SNMP agent uses the value of BEA_SMUX_PASSWD as the password; if BEA_SMUX_PASSWD has not been defined, the BEA SNMP agent does not specify a password to the master agent when registering.
The tux_snmpd supports the MIB-II snmp group when running as the SNMP agent.
To start BEA SNMP agents on a Windows system, follow these steps:
tux81_snmpd and click Start to start it, as shown in the following figure. There may be a short delay as the service is initiated.The installation program for Windows installs the SNMP agent as a single Windows service. If you want to run multiple instances of the agent to monitor multiple Tuxedo domains, you need to install additional Windows services for the additional agents.
To install additional Windows services for Tuxedo SNMP agents, open a command-line shell and run the following command for each additional Tuxedo SNMP agent:
prompt> instsrv logical_agent_name tux_prod_dir\bin\tux_snmpd.exe
Assign separate logical agent names to run multiple instances of the agent on the same node. To use multiple agents to monitor multiple Tuxedo domains, logical_agent_name is a string that associates an agent with a Tuxedo domain as defined by a TMAGENT entry in the BEA SNMP Agent beamgr.conf configuration file. For format information, see BEA SNMP Agent Advanced Configuration.
This entry assigns the agent started with logical_agent_name to the indicated Tuxedo domain. See Configuration Files.
Enter the desired startup options in the Startup Parameters field in the Services window.
-d
-s
snmp_integrator) is not running, you must provide -s as a startup parameter before selecting Start.
-p snmp_port
snmp_port option specifies the UDP port on which the BEA SNMP agent listens for incoming SNMP packets. The -p option enables you to run the BEA SNMP agent on a port other than the standard SNMP port 161. This option is meaningful only when the BEA SNMP agent is running as an SNMP agent.
-r smux_port
tux_snmpd is running as a SMUX subagent.
-m hostname
tux_snmpd to register with a SMUX master agent on a remote machine.
-c
To start BEA SNMP agents on a UNIX system, enter the Tuxedo SNMP agent startup command at the command-line prompt:
tux_snmpd [-l logical_agent_name] [-d] [-n] [-s] [-p snmp_port]
[-r smux_port] [-m hostname] [-h] [-c]
-l logical_agent_name
logical_agent_name string associates an agent with a BEA Tuxedo domain as defined by a TMAGENT entry in the BEA SNMP Agent beamgr.conf configuration file. The logical agent name can be a maximum of 32 characters long. For format information, see BEA SNMP Agent Advanced Configuration.
-l option, the BEA SNMP agent uses the name of the executable as the logical agent name.
-d
-n
init command.
-s
-c
-p snmp_port
snmp_port option specifies the UDP port on which the BEA SNMP agent listens for incoming SNMP packets. The -p option enables you to run the BEA SNMP agent on a port other than the standard SNMP port 161. This option is meaningful only when the BEA SNMP agent is running as an SNMP agent.
-r smux_port
-m hostname
-h
On a Windows system, you stop BEA SNMP agents and the optional BEA SNMP Agent Integrator via the Services window. On a UNIX system, you stop BEA SNMP agents and the optional BEA SNMP Agent Integrator by entering the stop_agent command at the command-line prompt.
To stop one or more BEA SNMP agents on a Windows system, follow these steps:
To stop one or more BEA SNMP agents on a UNIX system, issue the following command:
prompt> stop_agent logical_agent_name | all [logical_agent_name]
If you specify all, all SNMP agents are stopped. The name of the executable is the default logical agent name.
The Tuxedo SNMP agent can be installed on both Tuxedo master and non-master nodes. If the BEA Tuxedo application is down on the non-master node, SNMP Get requests addressed to the BEA SNMP agent on the non-master node may not have the latest information. For example, this would be true if the requested information was updated on a master node after the application on the non-master node went down. Set requests to a non-master node are not permitted if the BEA Tuxedo application is down on the local node.
Some MIB groups in the Tuxedo SNMP MIB return values for all Tuxedo nodes, whereas other MIB groups return data only for the local node, as shown in the following table. Thus, if you want to manage objects whose values are local to a particular machine, you must install a copy of the BEA SNMP agent on that machine or start the BEA SNMP agent with the -c option on the master machine.
|
