![]() |
![]() |
e-docs > Tuxedo > SNMP Agent Administration Guide > BEA SNMP Agent Integrator Commands |
SNMP Agent Administration Guide
|
BEA SNMP Agent Integrator Commands
The following sections explain the commands and utilities used for the BEA SNMP Agent Integrator:
Commands
reinit_agent
Syntax
reinit_agent all | logical_agent_name [logical_agent_name]
Description
Causes the specified agents to re-read their configuration file. This utility must be run with root permissions. Using the all argument causes all SNMP agents to re-initialize. For all SNMP agents other than tux_snmpd, logical_agent_name is the name of the executable.
For example, the command:
reinit_agent snmp_integrator
causes the BEA SNMP Agent Integrator to re-read its configuration file.
snmp_integrator
Syntax
[-b ipaddr_list | hostname_list ]
Arguments
130.86.33.13
130.86.23.1
Description
The snmp_integrator file is the SNMP BEA SNMP Agent Integrator executable. It allows multiple SNMP agents and SMUX subagents from any vendor to coexist on the same node and to appear as a single SNMP agent to any SNMP manager.
The BEA SNMP Agent Integrator can simultaneously support any number of:
Also, the BEA SNMP Agent Integrator can coexist on the standard SNMP port (161/udp) with any other SNMP agent. It directly supports the SMUX MIB (RFC 1227) in addition to the MIB-II system(1) and snmp(3) groups.
When the program is running as an SNMP agent, it generates a coldStart trap to the host specified by the TRAP_HOST entry in the beamgr.conf file at startup. If there is no TRAP_HOST entry, the trap is sent to UDP port 162 on the host where the utility is running, with a community defined as public.
Read-write and read-only communities supported by the BEA SNMP Agent Integrator can be specified in the beamgr_snmpd.conf file. By default, read-only community is public and read-write community is iview.
Using the beamgr_snmpd.conf file, you can configure the BEA SNMP Agent Integrator to expect a password from SMUX subagents that register with it.
On Windows Systems
Messages displayed with the -d argument are sent to the Event Log.
The -n argument has no effect.
On UNIX Systems
The -d argument is usually used for debugging purposes when the program is executed on the command line. Messages displayed are sent to the standard output of the program. If the program is started by init(1M), the destination of these messages is determined by the UNIX platform and version. These messages are most frequently sent to the console.
The -n argument is usually used when the program is started by init(1M) with the respawn option.
stop_agent
Syntax
Arguments
show_agent
Syntax
Description
BEA SNMP Agent Utilities
The BEA SNMP Agent software provides the following utilities to help you install and test an agent or subagent:
instsrv Purpose
Synopsis
Arguments
snmpget
Purpose
Synopsis
[variable_name ...]
Arguments
Description
Environment Variables
Examples
.beaSysHasDisk.0
INTEGER: yes(2)
mgmt.mib.system.sysUpTime.0
OCTET STRING- (ascii): Kinetics FastPath2
Timeticks: (2270351) 6:18:23
snmpgetnext
Purpose
Synopsis
[variable_name ...]
Arguments
Description
Environment Variables
Examples
.ifOutOctets.0
COUNTER: 85655250
.ifOutOctets.1
snmptest
Purpose
Synopsis
Arguments:
Description
Environment Variables
Examples
requestid 0x775efba0 errstat 0x0 errindex 0x0
Name: private.enterprises.bea.beaEm.beaEmMonitorTimer.0
INTEGER: 5000
snmptrap
Purpose
Synopsis
trap_type specific_trap variable_binding_value
Arguments
Description
beaTrapDescr.0
sysDescr
Examples
snmptrapd
Purpose
Synopsis
Arguments
Environment Variables
Description
Examples
Name: private.enterprises.bea. beaSystem.beaTrapDescr.0
OCTET STRING- (ascii): host xyz is booting
snmpwalk
Purpose
Synopsis
Arguments
Description
Environment Variables
Diagnostics
Examples
OCTET STRING- (ascii): SunOS
OCTET STRING- (ascii): blueberry
SNMP Request Format
BEA SNMP Agent utilities use SNMP requests to query SNMP agents for information about managed objects. Refer to RFC 1157 (SNMP) for more information about the format of SNMP requests. For information about locating RFCs on the Internet, see SNMP Information.
MIB Variable Definition Files
When a MIB variable is used with a BEA SNMP Agent utility, the utility attempts to convert the variable to a numeric OID by searching first in a file named mib.txt in the current directory, then in a file specified in the environment variable BEA_SM_SNMP_MIBFILE, and finally in the tux_prod_dir\udataobj\snmp\etc\mib.txt file on a Windows system, or tux_prod_dir/udataobj/snmp/etc/mib.txt file on a UNIX system. These files should use ASN.1 notation and use the OBJECT TYPE macro defined in RFC 1155 (Structure of Management Information).
The mib.txt file describes the RFC 1213 (MIB-II) and the BEA private MIB objects.
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |