pm_snmpd
unix_snmpd
beaSystem, beaUnix, beaSmgr, and beaSysPerf MIB groups.
nt_snmpd
beaNTSysPerf and beaSystem MIB groups. Also supports the following subgroups within the beaUnix group: the host process table (beaPsTable), the host file system table (beaDfTable), the system statistics group, and the local file system table (beaLclDfTable). Does not support the message queue (beaMqTable) and semaphore (ipcs -sa) (beaSemTable) tables. Also, the beaShmTable (UNIX shared memory table) and beaSmgrTable are not supported.
Refer to Chapter 8, "BEA SNMP Agent MIB," for more information about the supported MIB objects.
A SMUX subagent which supports the BEA Log Central Process Monitor.
pm_snmpd [-d] [-n] [-s] [-pport| -rsmux_port]
-d
-n
-s
-p port
-r smux_port
The pm_snmpd program is the BEA Manager SMUX subagent that supports the BEA Manager Log Central Process Monitor MIB groups (beaPm and beaPmProcTable). This subagent is capable of running as an SNMP agent as well as a SMUX subagent.
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. If there is no TRAP_HOST entry, the trap is sent to port 162 on the host where the utility is running, with a community defined as public.
If the program is running as an SNMP agent:
beamgr_snmpd.conf file. By default, the read-only community is public and the read-write community is beamgr.
If the program is running as a SMUX subagent:
beaPm, beaPmProcTable, and beaSmgr. You may limit the advertised MIB groups by specifying an OID_CLASS entry in the beamgr.conf file. For more information, refer to "BEA Manager Configuration File (beamgr.conf)."
The The Messages displayed with the The UNIX
-d argument is usually used when the program is executed on the command line for debugging purposes. Displayed messages are sent to the standard output of the program. If the program is started by init, the destination of these messages is determined by the UNIX platform and version. These messages are most frequently sent to the console.
-n argument is usually used when the program is started by init with the respawn option.
Windows NT
-d argument are sent to the Windows NT Event Log.
-n argument has no effect.
nt_snmpd
Syntax
nt_snmpd [-d] [-s] [-p port] [-r smux_port]
Arguments
This subagent is capable of running as an SNMP agent as well as a SMUX subagent. In either case, it runs as a Windows NT service.
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 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 nt_snmpd (community) can be specified in the beamgr_snmpd.conf file. (Community is meaningful only when running as an SNMP agent.) By default, the read-only community is public and the read-write community is beamgr.
When the program is running as a SMUX subagent, it can (if desired) specify a password to the SMUX master when it establishes communication. The password used is the value of the environment variable BEA_SMUX_PASSWD.
This utility supports the MIB-II snmp group when running as an SNMP agent.
By default, when running as a SMUX subagent, nt_snmpd advertises all the MIBs it knows about. The nt_snmpd subagent supports the following MIB groups: beaSystem, beaNTSysPerf, beaSysPerf, and some objects under the beaUnix group.
You may limit the MIBs to be advertised by nt_snmpd by specifying an OID_CLASS entry in the beamgr.conf file. For more information, refer to "BEA Manager Configuration File (beamgr.conf)."
Messages displayed with the -d argument are sent to the NT Event Log.
unix_snmpd [-d] [-n] [-s] [-p port] [-r smux_port]
This option dumps the SNMP/SMUX packets received and sent by the agent to stdout.
The program is not run as a daemon.
This subagent is capable of running as an SNMP agent as well as a SMUX subagent.
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 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 unix_snmpd (community) can be specified in the beamgr_snmpd.conf file. (Community is meaningful only when running as an SNMP agent.) By default, the read-only community is public and the read-write community is beamgr.
When the program is running as a SMUX subagent, it can (if desired) specify a password to the SMUX master when it establishes communication. The password used is the value of the environment variable BEA_SMUX_PASSWD.
This utility supports the MIB-II snmp group when running as an SNMP agent.
By default, when running as a SMUX subagent, unix_snmpd advertises all the MIBs it knows about. The unix_snmpd subagent supports the following MIB groups on UNIX platforms: beaSystem, beaUnix, beaSmgr and beaSysPerf groups.
You may limit the MIBs to be advertised by unix_snmpd by specifying an OID_CLASS entry in the beamgr.conf file. For more information, refer to "BEA Manager Configuration File (beamgr.conf)."
The -d argument is usually used when the program is executed on the command line for debugging purposes. Messages displayed are sent to the standard output of the program. If the program is started by init, the destination of these messages is determined by the UNIX platform and version.
The -n argument is usually used when the program is started by init(1M) with the respawn option.