Smarts: How do I generate ConfigChange notifications
book
Article ID: 331839
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Customer may want to enable Configuration Change Alarms in their IP domains.
Config change alarms are not being generated in smarts. I can see the trap, of OID .1.3.6.1.4.1.9.9.43.2, being received from devices in smarts , but I do not see ConfigChange alarms/notifications being generated.
Environment
VMware Smart Assurance - SMARTS
Cause
The configChange alarm is suppressed by default in Smarts.
Resolution
To allow for the configChange alarms in smarts, follow these steps:
In your CLI, navigate to the base director of you smarts installation.
execute this command
<basedir> sm_edit tpmgr.conf
Find this section of the file, and change the EnableConfigChange FALSE as highlighted in the section below to TRUE.
# EnableConfigChange (Controls whether the IP Manager generates ConfigChange events: # A value of TRUE indicates that the IP Manager generates ConfigChange events. # A value of FALSE indicates that the IP Manager does not generate ConfigChange events.
# When the IP Manager generates a ConfigChange event, it adds the device that caused the event to the # Pending Devices list. # # Default Value = FALSE # EnableConfigChange FALSE
Restart the domain.
You should begin to see these alarms now.
NOTE: Devices that have these alarms will be put on the discovery pending list.