-
Título
How to Test & Diagnose problems with SNMP Alerts -
Descripción
This document provides additional steps for testing and diagnosing problems with SNMP alerts
This work in conjunction with the test available Administration | Configuration | Coordinator
-
Causa
Change Auditor does need to be installed before the SNMP ServiceIf this is not the case, Registry Keys need to be created to point to the proper DLLs -
Resolución
Prerequisite
- SNMP Services must be installed on the Server hosting the Coordinator
- SNMP Services can be added via Server Manager | Features
- Reboot of the Server will be mandatory after installation
- Open Services.msc to configure the SNMP Service
- In Security, setup a Community name as READ CREATE
- In Trap, select the Community created previously then set a Trap Destination
ie. the server which will host the Trap Receiver tool
Testing:
- Install a SNMP Trap Receiver tool of your choice on the host whose IP is setup in step 6 above
- Open the Trap Receiver tool to configure and load the MIB pointing to CAAD.MIB
- by default C:\Program Files\Quest\ChangeAuditor\Service
- Let the Trap Receiver tool run
- Make sure that the SNMP Service is running in Services.msc and restart it
- A Trap should be generated after restart
- Go to CA Client | Administration | Configuration
- Click Test SNMP
- A confirmation window should appear and SNMP Trap should be received
Troubleshooting:
If an error message is displayed during the step above or no Trap is being received, please follow the steps below:
Open the Coordinator Logs and check for error
- If the following message is showing:
Could not probe for kernel event, SNMP service might not be running, or agent not loaded
or
Cannot continue processing SNMP alerts on this repository, SNMP is handled by: *************
In this case, you would also see AlertTypeID in the Alert.Queue in SQL Management
- Confirm the SNMP Service is running
- Check if the Coordinator is pointing to the proper SNMP Service hosting Server
- For that, open the SQL Management Studio on the SQL Server
- Go to the Change Auditor database, click New Query, and run the following
Select * from dbo.SystemProperty
- Look for SNMPServer and confirm this is the proper name for the server
- Otherwise, update the Server name as per KB 4233536
If the SNMP Service was installed or reinstalled after Change Auditor was installed
Check the following:
- Confirm that CAADSnmp.dll exists in the Change Auditor Coordinator Directory
- By default C:\Program Files\Quest\ChangeAuditor\Service\
- Open the Registry
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Quest\ChangeAuditor\Coordinator\SNMP
- Confirm that the Key is pointing to the CAADSnmp.dll folder
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SNMP\Parameters\ExtensionAgents
-
If missing, create a STRING value as per below
-
Value Name: CAAD
-
Value Data: Software\Quest\ChangeAuditor\Coordinator\SNMP
-
Información adicional
Quest Software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.The information in the script(s) provided is known to work successfully; however, they have not been officially tested by Quest Software Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by Quest Software Support and Development.Quest Software Support and Development recommend always making a backup of the current database prior to execution of any script(s) that may modify it.For customization of the <insert product name>, please contact our Professional Services Organization.