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 ProScan Group, lets you run all ProScan 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: Use ProScan / Change Management).
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 Open Manage 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, Open Manage 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 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.
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 the Java Client User Guide.
Event/Trap-Based Change Determination
The following steps to trigger Change Determination based on events received by Open Manage Network Manager. Your devices must transmit traps to the Open Manage Network Manager installation, and must emit traps when changes occur, or this does not work.
1. Back up the configuration file for a device you have discovered.
2. Make a change to that device with the Managed Resources editor, or from a Direct Access command line.
3. Such changes make the device emit an event that may have further consequences. For example, for Juniper devices, the Juniper JUNOS Configuration Changed event is a correlation event.
4. To provide a response (and to normalize the emitted event), create an automation rule that emits a redcellEquipmentConfigChangeNotification event when Open Manage Network Manager receives creates a event in response to events like the jnxCmCfgChange event that occurs when Juniper devices change.
5. Create a rule to respond to redcellEquipmentConfigChangeNotification by running the Change Determination process. You do not have to back up the configuration after the change. See How to: Create Event Processing Rules to Trigger Change Determination Process below.
6. To see the change itself, run the Change Determination Report (see Compliance and Change Reporting and How to: Report on Change Determination). The report displays the changes made.
Create Event Processing Rules to Trigger Change Determination Process
This exercise creates an Event Processing rule that has Change Determination respond to an event. The steps to configure such an event processing rule are as follows:
1. Create a new event processing rule by right-clicking in Event Processing Rules > New > Post Processing rule in the Event Processing Rule portlet.
2. Enter the name in the field labeled Name. (Example: Update Config Change Flag)
3. Click Next to go to the Filter tab.
4. For the Specify Events panel, click on the Add button to select the event to which this rule responds. A selector listing available events appears.
Notice you can limit the selector’s displayed events by entering text in the filter at the top of the selector screen.
5. In the selector, click the event definition (here: redcellEquipmentConfigChangeNotification), and confirm your selection.
6. Click Done to accept the Event(s) you have configured.
7. Notice you can further filter which events this rule responds to with the lowest panel in this screen’s Filter Conditions panel by clicking Add Filter. For example, you could create a rule that responds only to events from a particular IP address. For now, we will not configure additional filters.
8. Click Next to open the Actions tab.
9. Click Add Action, and click the Custom action alternative, then click Keyword Search and select Change Determination. That action appears in the drop-down combo box. Notice you can also select a target in the action selector. By not selecting one, we run change determination against all Managed Equipment.
10. Click Apply and view the Change Determination action listed in the Actions screen.
Notice that you can add more actions, and edit or delete existing ones with the icons to the right. Click Apply once you have selected Change Determination.
11. Click Save to preserve this event processing rule. The rule should now respond to the configured event, triggering the action you configured.
Backup and Change Determination automates backing
up target devices.
Also: Change Determination’s current default is to compare files even if the “Config Change” flag has not been modified. See the Open Manage Network Manager Java Client User Guide for instructions about how to change this default.