Passive end-user experience monitoring provides an SNMP MIB that enables your SNMP manager to get SNMP traps and to query SNMP data.
This page gives detailed information about correcting SNMP service failures, enabling Real User Analyzer and Collector components installed on the same machine, and disabling the SNMP service validation.
The SNMP service in BMC Real End User Experience Monitoring is made up of the following components:
|snmp-master-agent||The primary SNMP service that starts and stops the snmpd SNMP agent daemon.|
|snmpconfig.sh||The controlling script that updates the snmpd deamon config.|
|snmp-sub-agent||A service responsible for the host SNMP properties (CPU, memory, etc.)|
If the system requirements are met but an error message appears when you try to enable the SNMP service, you must login to the server as a root user and check the following issues:
service snmp-master-agent.sh start
snmpconfig.sh -e 2c
If the Real User Analyzer and Collector components were installed on the same machine, the SNMP service must be synchronized between both components to operate correctly.
The Real User Analyzer and Collector components must have identical SNMP configuration details for the local agent, SNMP MIB, and SNMP trap for both components. For more information, see:
If you see an error message when the SNMP service is enabled, it means that the service validation check failed and the SNMP service has not started.
When the SNMP service has started, but the service validation is incorrect, the service validation check can be disabled when the SNMP service is enabled with the user interface.
Open the import-controller.properties file and set the
controller.cmd.snmp.verifysnmp command to false.