![]() |
![]() |
![]() |
![]() |
![]() |
The following sections explain the commands and utilities used for the Oracle SNMP Agent Integrator:
• 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.-p port-r smux_portIf the machine where the Oracle SNMP Agent Integrator is running has multiple IP addresses, by default the Oracle SNMP Agent Integrator listens on all IP addresses. The -b option can be used to specify a subset of IP addresses to monitor for incoming SNMP requests.you can configure the Oracle SNMP Agent Integrator to only service requests addressed to 130.86.23.1 by starting it with the following command:The snmp_integrator file is the SNMP Oracle 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.Also, the Oracle 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 Oracle 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 Oracle 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.For all SNMP agents other than tux_snmpd, the logical agent name is always the name of the executable.
-p portThe 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.Must be set to specify the path to mib.txt, which provides an ASCII text description of the contents of your private MIB.The following command sends a query to the SNMP agent running on the host named topaz, using public as the community for authorization. The agent retrieves the value of the managed object beaSysHasDisk in the Oracle 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.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.-p portYou 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.Must be set to specify the path to mib.txt, which provides an ASCII text description of your private MIB.This example contacts the host named 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:Note that the instance index .0 must be appended to the end of the OID to refer to the value of the object.-p portWhen this program is executed, it prompts you to enter an OID. The snmptest utility returns information about request and reply packets as well as the name and type of the object.
Must be set to specify the path to mib.txt, which provides an ASCII text description of your private MIB.After displaying the result, you can enter another variable name, or $Q to quit the program.If you enter $Q, a quit message appears:snmptrap [‑a agent_addr] [‑d] [-p port] host community
trap_type specific_trap variable_binding_value‑a agent_addrSpecifies an originating address, if it is different from that of the host, where snmptrap is executed. This argument enables you to send a trap on behalf of another host.-p portAn integer that identifies the enterprise-specific trap that occurs when trap_type is set to generic trap type 6.
The sending agent is reporting that an enterprise-specific event has occurred. The value of the specific-trap field indicates the nature of the event.The value of this object can be specified in the variable-binding-value argument.The following command sends a 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).-l portMust be used to specify the path to mib.txt, which provides an ASCII text description of your private MIB.This utility receives SNMP traps sent on the UDP port specified by the -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.On UNIX platforms, if the -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.-p portThe unique object identifier, expressed symbolically, decimally, or as a combination of both. If you do not specify a variable name, snmpwalk searches the entire MIB.This utility traverses the OID tree from the object specified on the command line. 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. If no objects are specified, snmpwalk searches the entire MIB tree supported by the SNMP agent.Must be used to specify the path to mib.txt, which provides an ASCII text description of your private MIB objects.This is an example of an snmpwalk command:Oracle 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” on page A‑1.When a MIB variable is used with an Oracle 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 Oracle private MIB objects.