|
|
The following sections explain the commands and utilities used for the BEA SNMP Agent Integrator:
reinit_agent all | logical_agent_name [logical_agent_name]
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.
causes the BEA SNMP Agent Integrator to re-read its configuration file.
-d
-n
-p port
-r smux_port
-b ipaddr_list | hostname_list
-b option can be used to specify a subset of IP addresses to monitor for incoming SNMP requests.
ipaddr_list
Can consist of a single IP address or a blank-separated list of IP addresses.
hostname_list
Can consist of one host name or a blank-separated list of host names.
For example, if the machine on which the BEA SNMP Agent Integrator is running has the following IP addresses:
130.86.34.3
130.86.33.13
130.86.23.1
you can configure the BEA SNMP Agent Integrator to only service requests addressed to 130.86.23.1 by starting it with the following command:
snmp_integrator -b 130.86.23.1
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.
Messages displayed with the -d argument are sent to the Event Log.
The -n argument has no effect.
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.
all
logical_agent_name
tux_snmpd, the logical agent name is always the name of the executable.
The BEA SNMP Agent software provides the following utilities to help you install and test an agent or subagent:
executable_file to create a service. Enter remove to remove a service.
For example:
instrsrv snmp_integrator c:\tux81\bin\snmp_integrator.exe
service_name
executable_file
-d
-p port
host
community
variable_name
snmpget utility uses SNMP Get requests to retrieve information about managed objects. You can enter one or more object identifiers as arguments on the command line. These names can be absolute, starting from the root of the tree, or relative to .iso.org.dod.internet.
mib.txt, which provides an ASCII text description of the contents of your private MIB.
topaz, using public as the community for authorization. The agent retrieves the value of the managed object beaSysHasDisk in the BEA private MIB. Note that in this example, a relative OID (private.enterprises.bea.beaSystem) is specified. .iso.org.dod.internet. is prepended to generate an absolute path.
snmpget topaz public private.enterprises.bea.beaSystem
.beaSysHasDisk.0
This command returns the following information about the object:
Name: private.enterprises.bea.beaSystem.beaSysHasDisk.0
INTEGER: yes(2)
The following command sends a query to the SNMP agent running on the host named ruby, using public as the community for authorization. The agent retrieves the value of the managed objects sysDescr and sysUptime in the MIB.
snmpget ruby public mgmt.mib.system.sysDescr.0
mgmt.mib.system.sysUpTime.0
This command returns the following information:
Name: mgmt.mib.system.sysDescr.0
OCTET STRING- (ascii): Kinetics FastPath2
Name: mgmt.mib.system.sysUpTime.0
Timeticks: (2270351) 6:18:23
-d
-p port
host
community
variable_name
.iso.org.dod.internet.
mib.txt, which provides an ASCII text description of your private MIB.
blueberry using the community name public and retrieves the value of the instance immediately following mgmt.mib.interfaces.ifTable.ifEntry.ifOutOctets.0 from the MIB:
snmpgetnext blueberry public mgmt.mib.interfaces.ifTable.ifEntry
.ifOutOctets.0
Note that the instance index .0 must be appended to the end of the OID to refer to the value of the object.
The output of the previous command might look like this:
Name: mgmt.mib.interfaces.ifTable.ifEntry.ifOutOctets.1
COUNTER: 85655250
You could then enter a command that retrieves information about the next variable:
snmpgetnext blueberry public mgmt.mib.interfaces.ifTable.ifEntry
.ifOutOctets.1
-d
-p port
host
community
snmptest utility returns information about request and reply packets as well as the name and type of the object.
$Q
mib.txt, which provides an ASCII text description of your private MIB.
snmptest topaz public
The program responds with:
Please enter the variable name:
Enter a variable name and press Enter:
private.enterprises.bea.beaEm.beaEmMonitorTimer.0
The program requests another variable name:
Please enter the variable name:
You can either enter another variable name, or press Enter to see the result. When you press Enter, the program displays the result of the test:
Received GET RESPONSE from 192.84.232.47
requestid 0x775efba0 errstat 0x0 errindex 0x0
Name: private.enterprises.bea.beaEm.beaEmMonitorTimer.0
INTEGER: 5000
After displaying the result, you can enter another variable name, or $Q to quit the program.
Please enter the variable name: $Q
If you enter $Q, a quit message appears:
Quitting, Good-bye
snmptrap [-a agent_addr] [-d] [-p port] host community
trap_type specific_trap variable_binding_value
-a agent_addr
snmptrap is executed. This argument enables you to send a trap on behalf of another host.
-d
-p port
host
community
trap_type
specific_trap
trap_type is set to generic trap type 6.
variable_binding_value
.iso.org.dod.internet.private.enterprises.bea.beaSystem.
beaTrapDescr.0
The value of this object can be specified in the variable-binding-value argument.
The enterprise field, which is part of the SNMP trap PDU header, is always:
.1.3.6.1.4.1.140.1.1
which is equivalent to:
.iso.org.dod.internet.private.enterprises.bea.beaSystem.
sysDescr
coldStart trap to the host named topaz, using public as the community for authorization. Note that a value for the specific-trap argument must be present, even though it is ignored when the value of the trap-type argument is not 6 (enterpriseSpecific).
-d
-l port
-p
mib.txt, which provides an ASCII text description of your private MIB.
-l argument. If no port is specified, it uses port number 162. This utility must be able to open the snmp-trap port, which usually requires root permissions.
-p argument is not specified, snmptrapd uses the UNIX syslog utility to log messages with a status of WARNING. If the LOG_LOCAL0 facility is available, it is used instead of syslog or snmptrapd.
On Windows systems, if the -p argument is not specified, the Event Log is used to log WARNING messages.
snmptrapd -p
When the host receives the trap, it displays the following information:
192.84.232.47: Cold Start Trap (0) Uptime: 0:00:00
Name: private.enterprises.bea. beaSystem.beaTrapDescr.0
OCTET STRING- (ascii): host xyz is booting
-d
-p port
host
community
variable_name
snmpwalk searches the entire MIB.
.iso.org.dod.internet. If no objects are specified, snmpwalk searches the entire MIB tree supported by the SNMP agent.
mib.txt, which provides an ASCII text description of your private MIB objects.
snmpwalk blueberry public private.enterprises.bea.beaSystem
This is some of the output generated from the command:
Name: private.enterprises.bea.beaSystem.beaSysSysname.0
OCTET STRING- (ascii): SunOS
Name: private.enterprises.bea.beaSystem.beaSysNodename.0
OCTET STRING- (ascii): blueberry
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.
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.
|