Setting Up the BEA SNMP Agent on a Managed Node


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Search \| PDF Files \| Contact

BEA SNMP Agent Doc Home \| Administrator's Guide \| Previous Topic \| Next Topic \| Contents \| Index

To integrate the 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. This chapter describes the procedure for setting up the BEA SNMP Agent on the managed node. Integration into the management framework is described in Integrating the BEA SNMP Agent with a Management Framework.

This chapter includes the following sections:

Directory Structure

The BEA SNMP Agent files can be found in the directories shown in Figure 2-1.

Figure 2-1 Directory Structure

Note: The items that appear in the gray boxes are descriptions only; they are not actual file names.

Configuring the BEA SNMP Agent

Configure the BEA SNMP Agent for Tuxedo or WLE by performing these steps::

Make sure Tuxedo or WLE is installed.
Install the BEA SNMP Agent on the managed nodes.
The tux_snmpd Tuxedo SNMP Agent and the wle_snmpd SNMP Agent are installed one at a time. On a Windows NT system, if you do not install Tuxedo or WLE first, you do not get the option to install corresponding tux_snmpd or wle_snmpd. For detailed information about how to install the BEA SNMP Agent, refer to the BEA SNMP Agent Installation Guide for BEA Tuxedo and BEA WebLogic Enterprise.

Some attributes of Tuxedo resources are accessible globally (that is, no matter which Tuxedo node they are on) while others are accessible only by an SNMP agent local to the same machine. To access managed objects that are only accessible locally, you must install Tuxedo SNMP agents on each machine where these resources reside, or install Tuxedo SNMP agents 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.
Set up access to WLE or Tuxedo shared binaries.
- On a UNIX system:
  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.
- On a Windows NT system:
  If the BEA SNMP Agent is not installed in the same directory as the Tuxedo or WLE application, make sure that the bin directory of the appropriate Tuxedo or WLE installation precedes any other Tuxedo or WLE installations in the PATH system environment variable. This directory order in PATH enables the BEA SNMP Agent to have access to the correct Tuxedo or WLE dynamic link libraries (DLLs).
Install the BEA SNMP Agent configuration file.
- On a UNIX system:
  Log in as root and copy the BEA SNMP Agent configuration file beamgr.conf from installation_directory/etc to the /etc directory.
```
%su
Password:
# cp installation_directory/etc/beamgr.conf /etc
```
- On a Windows NT system:
  Copy the BEA SNMP Agent configuration file (beamgr.conf):
```
md c:\etc
copy installation-directory\etc\beamgr.conf c:\etc
```
Set your PATH to include the location of the BEA SNMP Agent executables. This applies to both UNIX and Windows NT.
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:
```
% set path = ( $PATH installation_directory/bin )
```
Set your master agent timeout if you are running the agent as a subagent.
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, this can be done by adding a INTEGRATOR_TIMEOUT entry to the BEA SNMP Agent configuration file (beamgr.conf) as follows:

INTEGRATOR_TIMEOUT 30
When the BEA SNMP Agent is installed on a Windows NT system, ensure that a match exists between the TCP/IP host name and the computer name.
To do this, 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.
Specify the destination for traps.
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 refer to Configuration Files.
Identify the domain to be managed.
The identity of the Tuxedo application to be managed can be specified in two ways. The BEA SNMP Agent uses the following sources in the indicated order of precedence:
1. The 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 refer to Configuration Files.
2. TUXCONFIG and TUXDIR environment variables
Ensure that the Tuxedo Event Broker is configured.
The BEA SNMP Agent cannot receive Tuxedo event notifications unless the Tuxedo Event Broker server (TMSYSEVT) is running. To enable forwarding of Tuxedo events as SNMP traps, ensure that the Tuxedo Event Broker servers are running. Information on the Tuxedo Event Broker can be found in the "Programmed Administration" chapter of the BEA Tuxedo Administrator's Guide and in Section 5 of the BEA Tuxedo Reference Manual.
If you are only using SNMP agents, start the Tuxedo or WLE SNMP agents on the managed nodes where your Tuxedo or WLE resources reside. See the Starting the BEA SNMP Agent section for more information.
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 Agent and then the BEA SNMP Agent Integrator.
Integrate the BEA SNMP Agent with your SNMP management framework. Refer to Integrating the BEA SNMP Agent with a Management Framework.

Advanced Configuration

There are additional steps that you may want to perform to customize the BEA SNMP Agent to your needs for tasks such as monitoring multiple Tuxedo domains concurrently or using nondefault ports for communication with the system manager. The following configuration steps are optional:

Define logical agent names if you want to monitor multiple Tuxedo domains concurrently.
To monitor multiple Tuxedo domains 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 monitor multiple domains, run a separate Tuxedo or WLE agent for each domain being monitored. These agents must be run as subagents under the BEA SNMP Agent Integrator.

When multiple agents are running on the same node, then SNMP manager SET or GET requests to an agent must be addressed using a community of the form:

community@logical_agent_name

logical_agent_name identifies the agent to which the SNMP request is forwarded. For example:
```
public@simpapp_agent
```
If only one agent is running on a node, logical_agent_name is optional in specifying the community in GET or SET requests.
Define Tuxedo event filters to be used.
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 "Tuxedo Core MIB" in the BEA SNMP Agent Reference.
Specify non-default SNMP communities and SMUX password.
By default, SNMP agents (such as the BEA SNMP Agent Integrator or tux_snmpd or wle_snmpd when running as SNMP agents) use 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.
1. To set up the passwords file:
  On a UNIX system:
  
  Copy the BEA SNMP Agent beamgr_snmpd.conf passwords file from the installation_directory/etc to the /etc directory and make the copy readable and writable only by root. For example:
```
# cp installation_directory/etc/beamgr_snmpd.conf /etc
# chmod 600 /etc/beamgr_snmpd.conf
```
  On a Windows NT system:
  
  Copy the BEA SNMP Agent beamgr_snmpd.conf passwords file to c:\etc. For example:
```
copy installation-directory\etc\beamgr_snmpd.conf c:\etc
```
2. Modify the SNMP communities in this file. The keywords used in this file are:
  SMUX_PASSWD
  
  COMMUNITY_RO
  
  COMMUNITY_RW
  
  DISABLE_SET
3. If you want to set the agent to be read-only, specify a DISABLE_SET entry in the passwords file as follows:
  DISABLE_SET YES
  
  If there is no DISABLE_SET entry in the passwords file, the agent has both SET and GET capability.
  
  For more information refer to Configuration Files.
Specify a SMUX password when using the BEA SNMP Agent as a subagent under a SMUX master agent, such as the BEA SNMP Agent Integrator.
The environment variable BEA_SMUX_PASSWD specifies the password that the BEA 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 or wle_snmpd when registering.
Define different port numbers.
By default, 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.
- On a UNIX system:
  To modify or define the services, perform these steps:
1. Determine if the NIS server is running. Use the ypwhich command to determine if an NIS server or map master is available. For example:
```
% ypwhich
zort.kremvax.com
```
2. If an NIS server is available, use the ypcat command to determine if the services are available.
```
% ypcat services | grep snmp
snmp-trap    162/udp    snmptrap
snmp         161/udp
```
3. If an NIS server is not available and services are provided on the local host, examine the /etc/services file.
```
% 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.
- On a Windows NT system:
  To modify or define the services, add the appropriate lines in the NT-root-directory\system32\drivers\etc\services file. For example:
  
  snmp 161/udp snmp
  
  snmp-trap 162/udp snmp
  
  Consult your NT system administrator for the default settings used for your SNMP-related services.

Starting the BEA SNMP Agent

To monitor multiple Tuxedo or WLE domains, you can run multiple SNMP agents on the same node. Each agent can monitor only one domain. To monitor multiple domains, you must have the BEA SNMP Agent Integrator running and the agents must be started as subagents.

On startup, a Tuxedo or WLE 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 or WLE 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 refer to Configuration Files.

Starting the BEA SNMP Agent on a UNIX System

To start the BEA SNMP Agent on a UNIX system, enter the Tuxedo or WLE SNMP startup command at the command-line prompt.

For the Tuxedo SNMP Agent, the syntax of the startup command is:

tux_snmpd  [-l logical_agent_name] [-d]  [-n]  [-s]  [-p  snmp_port]
[-r  smux_port] [-m  hostname] [-h] [-c]

For the WLE SNMP Agent, the syntax of the startup command is:

wle_snmpd  [-l logical_agent_name] [-d]  [-n]  [-s]  [-p  snmp_port]
[-r  smux_port]  [-m  hostname] [-h] [-c]

UNIX Startup Options

The command line options are:

-l logical_agent_name

The logical_agent_name string associates an agent with a 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. See the Advanced Configuration section for format information.

Assign separate logical agent names to run multiple instances of the agent on the same node. If you do not specify the -l option, the BEA SNMP Agent uses the name of the executable as the logical agent name.

-d

Dumps the SNMP or SMUX packets received and sent by the agent to standard output.

-n

If the agent/subagent is run with this option, it does not become a daemon. Use this option to start the BEA SNMP Agent with the init command.

-s

Specifies the BEA SNMP Agent to run as an SNMP agent. If you do not specify this option, the BEA SNMP Agent runs as a SMUX subagent.

-c

Enables you to run the agent only on the master node but to still gather information from all machines. This results in a more manageable solution because it requires you to run one agent process per domain instead of one per node. In addition, it enables you to gather SNMP information from nodes with operating systems not supporting the current SNMP Agent.

When using this option, you must ensure that only one agent is started on the domain; otherwise, the results are unpredictable.

-p snmp_port

The 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

Specifies the TCP port to connect to a SMUX master agent. The default is port 199. This option is meaningful only when the BEA SNMP Agent is running as a SMUX subagent.

-m hostname

The name of the machine where the SMUX master agent, such as the BEA SNMP Agent Integrator, is running. This option is used only when you want the BEA SNMP Agent to register with a SMUX master agent on a remote machine.

-h

Displays the syntax for the tux_snmpd or wle_snmpd command.

BEA SNMP Agent Processes

The tux_snmpd binary is the Tuxedo SNMP agent which supports the Tuxedo MIB. For a description of the supported MIB groups and objects, please refer to the BEA SNMP Agent Reference.

The wle_snmpd binary is the WLE SNMP agent which supports the Tuxedo MIB with WLE extensions. For a description of the supported WLE-specific MIB groups and objects, refer to "WLE MIB Groups" in the BEA SNMP Agent MIB Reference for BEA Tuxedo and BEA WebLogic Enterprise.

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 . See the Configuring the BEA SNMP Agent section for more information.

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.

Both tux_snmpd and wle_snmpd support the MIB-II snmp group when running as the SNMP agent.

Starting the BEA SNMP Agent on a Windows NT System

To start the BEA SNMP Agent on a Windoes NT system:

Install additional Windows NT services if you want to run multiple agents on a single node.
The installation program for Windows NT installs the SNMP agent as a single Windows NT service. If you want to run multiple instances of the agent to monitor multiple Tuxedo or WLE domains, you need to install additional Windows NT services for the additional agents.

Run the following commands for each additional BEA SNMP Agent for Tuxedo:
```
instsrv logical_agent_name
install_directory\bin\tux_snmpd.exe
```
Alternatively, run the following commands for each additional BEA SNMP Agent for WLE:
```
instsrv logical_agent_name
install_directory\bin\wle_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 or WLE 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. See the Advanced Configuration section for more information.

This entry assigns the agent started with logical_agent_name to the indicated Tuxedo or WLE domain. Refer to Configuration Files.
Start the BEA SNMP Agent for Tuxedo or WLE from the Services window.
1. On the Windows taskbar, click Start->Settings->Control Panel.
2. In the Control Panel window, double-click the Services icon. The Services window is displayed. (See Figure 2-2.)
In the list of Services, locate and select the installed service (logical_agent_name) and click Start to start it, as shown in Figure 2-2. There may be a short delay as the service is initiated.
Figure 2-2 Starting a Service

Windows NT Startup Options

Enter the desired startup options in the Startup Parameters field in the Services window.

-d

Dumps the SNMP or SMUX packets received and sent by the agent to the Windows NT Event Log.

-s

Specifies the BEA SNMP Agent to run as an SNMP agent. If you do not specify this option, the BEA SNMP Agent runs as a SMUX subagent. If a SMUX master agent (for example, snmp_integrator) is not running, you must provide -s as a start-up parameter before selecting Start.

-p snmp_port

-r smux_port

Specifies the TCP port to connect to a SMUX master agent. (The default is port 199.) This option is meaningful only when tux_snmpd or wle_snmpd is running as a SMUX subagent.

-m hostname

The name of the machine where the SMUX master agent, such as the BEA SNMP Agent Integrator, is running. This option is used only when you want tux_snmpd or wle_snmpd to register with a SMUX master agent on a remote machine.

-c

When using this option, you must ensure that only one agent is started on the domain; otherwise, the results are unpredictable.

Stopping the BEA SNMP Agent

Use this command to stop one or more SNMP agents:

stop_agent logical_agent_name | all [logical_agent_name]

For example,

stop_agent tux_snmpd

If you specify all, all SNMP agents are stopped. The name of the executable is the default logical agent name.

Tuxedo and WLE Master and Non-Master Nodes

The Tuxedo SNMP agent can be installed on both Tuxedo or WLE master and non-master nodes. If the Tuxedo or WLE application is down on the non-master node, SNMP GET requests addressed to the 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 Tuxedo or WLE application is down on the local node.

Some MIB groups in the Tuxedo MIB return values for all Tuxedo nodes whereas other MIB groups return data only for the local node, as shown in Table 2-1. Thus, if you want to manage objects whose values are local to a particular machine, you must install a copy of the SNMP Agent on that machine or start the SNMP Agent with the -c option on the master machine.

Table 2-1 MIB Tables/Groups Returning Only Local Values

MIB Table/Group
Description

tuxTwshTbl

Run time attributes of workstation handler (WSH) client processes.

tuxTulog Table

Run time attributes of userlog files within an application.

tuxTmsgTable

Run time attributes of the Tuxedo System/T UNIX system message tables.

tuxTqueueTable

Run time attributes of queues in an application.

tuxTAppQTbl

Attributes of application queues.

tuxTAppQmsgTbl

Attributes of messages stored in application queues.

tuxTQspaceTbl

Attributes of application queue spaces.

tuxTQtransTbl

Run time attributes of transactions associated with application queue spaces.

tuxTBridgeTbl

Status and statistics pertaining to connections between machines making up an application.

tuxTclientTbl

Run time attributes of active clients within an application.

tuxTconnTable

Run time attributes of active conversations within an application.

tuxTdeviceTbl

Configuration and run time attributes of raw disk slices or UNIX system files being used to store Tuxedo System/T device lists.

tuxTsrvrTblExt

Attributes of servers within an application. It is an extension of tuxTsrvrTbl.

tuxTranTbl

Run time attributes of active transactions within the application.

tuxTsvcGrp

Configuration attributes of services within an application.

wleLclIfQueueTable

Local run time attributes of an interface for a particular server queue.

wleLclInterfaceTable

Configuration and run time attributes of CORBA interfaces for the local host on which the BEA SNMP Agent is running.

tuxTAppQctrl

A control MIB that enables controlled access to all application queue-related MIB groups.

MIB Table/Group	Description
tuxTwshTbl	Run time attributes of workstation handler (WSH) client processes.
tuxTulog Table	Run time attributes of userlog files within an application.
tuxTmsgTable	Run time attributes of the Tuxedo System/T UNIX system message tables.
tuxTqueueTable	Run time attributes of queues in an application.
tuxTAppQTbl	Attributes of application queues.
tuxTAppQmsgTbl	Attributes of messages stored in application queues.
tuxTQspaceTbl	Attributes of application queue spaces.
tuxTQtransTbl	Run time attributes of transactions associated with application queue spaces.
tuxTBridgeTbl	Status and statistics pertaining to connections between machines making up an application.
tuxTclientTbl	Run time attributes of active clients within an application.
tuxTconnTable	Run time attributes of active conversations within an application.
tuxTdeviceTbl	Configuration and run time attributes of raw disk slices or UNIX system files being used to store Tuxedo System/T device lists.
tuxTsrvrTblExt	Attributes of servers within an application. It is an extension of tuxTsrvrTbl.
tuxTranTbl	Run time attributes of active transactions within the application.
tuxTsvcGrp	Configuration attributes of services within an application.
wleLclIfQueueTable	Local run time attributes of an interface for a particular server queue.
wleLclInterfaceTable	Configuration and run time attributes of CORBA interfaces for the local host on which the BEA SNMP Agent is running.
tuxTAppQctrl	A control MIB that enables controlled access to all application queue-related MIB groups.