Users Guide

Change Determination Process | Change Management and Compliance
OMNM 6.5.3 User Guide 521
After running the Change Determination Process, you can run the Configuration Change report to
display what changed for a defined period. The contents of that report depends on the report filter,
and the specified period. This report lists changed attributes in the configurations.
Triggering Change Management and ProScan
To trigger the Change Management for a device, right-click it in the Managed Resources portlet
and select
Change Management > Change Determination . You can also schedule Change
Determination to run repeatedly, on regular intervals in the Schedules portlet.
You can similarly trigger ProScan by right-clicking a device, and selecting
Change Management >
Execute ProScan
or Execute ProScan Policy . The former execute all policies connected with the
selected device, while the latter allows you to select policy (or policies) to run. Creating a
Compliance Policy Group, lets you run all compliance policies for each device within the selected
group, scanning groups even if they consist of devices from different vendors. In ProScan, you can
scan device configurations (of specified labels) or Adaptive CLI command output. (See How to:
Using Change Management and Compliance on page 496).
How To:
Run the Change Determination Process
The following describes an exercise for the Change Determination process based on manually
running it. To run the process as a response to events devices must transmit traps to OpenManage
Network Manager. The next sections describe using Change Determination in the following ways:
•
Change Determination Confirmation
• Event/Trap-Based Change Determination
Change Determination Confirmation
The following steps confirm change determination is working.
1 Initialize the Change Determination Report and let it do a configuration backup. The first
time this runs, OpenManage Network Manager creates no diffs. It just initializes the Change
Determination label.
2 Edit a configuration to make a change. For example, make a change in a device you have
discovered. One benign change is to add a contact or a description to an interface.
3 Restore it to the device.
4 Execute the Change Determination process on the device by right-clicking it in the Managed
Resources Portlet, and selecting
Change Management > Change Determination .
This then backs up the device, compares the original and altered configurations, and writes
the difference to report later (see How to:
Report on Change Determination on page 525 for
the steps to run the report to see such changes).
Since we have initialized the report in step 1, the updated report shows the changes made to
the config file.
5 Repeat step 2 through 5 if you like after you have made further changes.
NOTE:
Best practice in production is to schedule a recurring run for Change Determination in the Schedules
portlet. Notice that you can also disseminate the report by e-mail, or view previous reports in the web
client, as described in the Reports portion of this guide.