Owners Manual

Change Management (Example) | Change Management and Compliance
498 OMNM 6.5.2 User Guide
Change Management (Example)
The following describes an example use of Change Manager. This backs up a configuration file,
modifies it, then scans the file for the modified text, and acts according to the result. The following
steps describe how to do this:
1 Back up a device configuration. Select a device and click the File Management > Backup
right-click menu in Managed Resources portlet.
2 Right-click, and Export this backup to a file in the Configuration Files portlet.
3 Edit this config file, adding the word “MyTestContact” somewhere in its text that has no
impact. For example, the snmp-server contact, or in comments. Some devices let you create
descriptions within their configurations so you can enter a word without impact there.
4 Now import this edited file from the Managed Resources portlet after you have right-clicked
on the same device from which you exported it. Renaming it something distinctive is helpful.
5 Right-click this file and Restore to the device. Since the name is a comment or description, it
should not interfere with the device’s operations.
6 Right-click the device and select File Management > Backup . This makes the
MyTestContact file label Current.
To confirm MyTestContact is labeled Current, you can use an Advanced filter in the
expanded Configuration Files portlet to view only Current labels.
7 Now, create a compliance policy by right-clicking in the Compliance Policies/ProScan portlet,
selecting
New > Policy.
8 In the General tab, name this policy MyTestContactScan, and as an input, select the
Configuration Label > Current label as the Input Source.
9 In the Targets tab, select the equipment from which you exported the config file.
10 In the Criteria tab, click Add Criteria enter contains MyTestContact as the Match All of the
following criteria
.
11 Click Save.
12 Right-click the new policy and select Execute Compliance .
13 The audit screen that appears should indicate Success.
14 Right-click and Open the MyTestContactScan policy, and change the Criteria to “does not
contain” MyTestContact.
15 Save
16 Re-execute the policy.
17 The audit screen that appears should indicate Failure.
Alarms/Events
Once you have a compliance policy that has failed, the redcellProScanFailureNotification alarm
appears in the Alarms portlet. Success produces an event, not an alarm (visible in the Event History
portlet) called redcellProScanClearNotification.
To create a response, create processing rules for the event/alarm (see
Creating Event Processing
Rules
on page 300). For example, you could restore the Compliant-labeled configuration file if
redcellProScanFailureNotification occurs, or send an e-mail to a technician, among many other
responses.