|
|
Open view log location
|
|
cmsnmpd(1m) cmsnmpd(1m) NAME
cmsnmpd - SNMP subAgent that services the High Availability cluster MIB objects SYNOPSIS
cmsnmpd DESCRIPTION
cmsnmpd is a subAgent that together with the SNMP Master Agent (snmpdm), form the SNMP Agent for a particular system. The cmsnmpd provides the instrumentation for the High Availability cluster MIB objects. The cmsnmpd is a separate process, yet registers with the SNMP Master Agent, and the two share a procedural interface. Traps The cmsnmpd sends asynchronous event notifications called "traps". By default, SNMP traps are not sent to any destination. To configure the agent to send traps to one or more specific destinations, add the trap destinations to /etc/SnmpAgent.d/snmpd.conf. The SNMP Master Agent and the cmsnmpd collaborate to send High Availability cluster-related traps and information. For example, a trap is sent when the cluster configuration changes, or when a Highly Available package has failed. A complete list of all the cluster-related traps can be found on systems with OpenView installed. On an OpenView management station, the trap descriptions can be found in /etc/opt/OV/share/conf/$LANG/trapd.conf. Supported MIB Objects The Management Information Base (MIB) is a conceptual database of values on the agent system. The cmsnmpd implements the hp-cluster and hp-sgcluster MIB objects. Included in these MIBs are descriptions of the cluster configuration, as well as the current status of each cluster component. A complete list of all the High Availability MIB objects can be found on systems with OpenView installed. On an Open- View management station, the MIB object descriptors can be found in /etc/opt/OV/share/conf/snmpmib. cmsnmpd Startup Startup is controlled by the setting of the AUTOSTART_CMSNMPD variable in the /etc/rc.config.d/cmsnmpagt file. If AUTOSTART_CMSNMPD is set to 1, the cmsnmpd is started automatically each time the system boots. The variable should be set to 1 if you will be using ClusterView to monitor your Highly Available clusters through OpenView. If AUTOSTART_CMSNMPD is set to 0, the cmsnmpd is not started automatically when the system boots. If configured for autostart, the cmsnmpd should startup automatically, after the SNMP Master Agent starts, each time the system reboots, or any time the system transitions from run level 1 to run level 2. When the system enters run level 2, the system will execute /sbin/init.d/SnmpMaster which will start the Master Agent. Similarly, /sbin/init.d/cmsnmpagt will start the cmsnmpd immediately after the Master Agent is started. Prior to executing these startup scripts the system will examine all scripts in /etc/rc.config.d for environment variables which could potentially influence the startup of the Master Agent and the cmsnmpd. See the specific startup script or configuration file for details on supported environment variables. The user should never modify scripts in /sbin/init.d. Instead, the startup behavior should be con- trolled by adjusting values in the configuration script /etc/rc.config.d/cmsnmpd. There are two ways to start the SNMP Master Agent and the cmsnmpd manually. The first way is to execute snmpdm and then start cmsnmpd by invoking the cmsnmpd executable (/usr/lbin/cmsnmpd). The second and simplest way to start the SNMP Agent manually is to execute the snmpd startup script which will invoke the Master Agent and all subAgents who have been installed and designed to operate in this paradigm. The snmpd startup script is layered upon the V.4 startup paradigm and so makes use of the component startup scripts in /sbin/init.d and configuration scripts in /etc/rc.config.d. When snmpd is invoked it passes all its command line arguments to snmpdm and then executes each script found in /sbin/SnmpAgtStart.d. DEPENDENCIES
None. AUTHOR
cmsnmpd was developed by Hewlett-Packard. FILES
/usr/lbin/cmsnmpd /sbin/init.d/cmsnmpagt /etc/rc.config.d/cmsnmpagt /var/adm/SGsnmpsuba.log SEE ALSO
snmpd(1m), snmpd.conf(4). Requires Optional Serviceguard Software cmsnmpd(1m)
