Refreshing the status of a device
A job with the Refresh Device Status action refreshes the compliance violations, discrepancies, configuration attribute profiles, and device attributes configurations for a network span without performing a snapshot. The refresh is performed using the current configurations and settings. If new discrepancies or violations are found during the refresh, events are logged and change policies are triggered (for example, send SNMP trap).
Understanding when to refresh
The following table presents the recommendations for when to perform the various refresh actions:
When to perform
Refresh Compliance Violation Status
The most common reason for refreshing compliance violations is when changing or adding rules. First, use the Compliance Summary report to verify that the rule grammar is functioning correctly, as outlined in the Best Practices. After the rule is verified, perform a refresh for the appropriate network spans. The refresh can tax system performance for large network spans, so use it sparingly. Avoid starting multiple refresh operations.
Another reason for refreshing violation status is when the configuration trails for a device have changed such that there are violations present on trails the device no longer supports. For example, if you change the device type for a device and the new device type has fewer trails, or if you import or revert a device type adapter such that <supportedTrail> elements are removed, you might need to clear away stale violations.
Do not perform a refresh when:
Refresh Discrepancy Status
Perform a refresh after BMC has updated your XML device adapter to ignore certain configuration changes when monitoring discrepancies (for example, if new comment lines have been added).
As stated in the Refresh Compliance Violation Status row, perform this refresh if you have reduced the supported configuration trails of a device or a device type, such that the Running or Startup trails were eliminated. This action will clear discrepancies on the dashboard for the unsupported trails.
Refresh Configuration Attribute Profiles
Perform a refresh when a Configuration Profiled dynamic field is added or modified, or a dynamic field with auto-grouping enabled is modified.
As stated in the Refresh Compliance Violation Status row, perform this refresh if you have reduced the supported configuration trails of a device or a device type, to eliminate captured values that were derived from the unsupported trails.
|Device Attributes Configuration||Perform a refresh when you first upgrade to version 8.9.00 (to generate these configurations). Perform a refresh if system errors occur that cause the configurations to be out of sync with device settings.|
Take a Device Offline
When a device has not been successfully backed up for a period of time, you might want to automatically place the device in offline status. The assumption is that the device has been removed from the network, so you want BMC Network Automation to skip the device when referenced in jobs, reports, and policies. At a later time, you might decide to delete offline devices by using the multiple Delete option on the Device List filtered by Online=No.
Tips on when to force a compliance check
Submit a Refresh Device Status span action under the following conditions:
- Initially, when creating a set of rules, do not enable the rule set until rules have been tested.
- Always test new rules and grammar changes before submitting a Refresh Device Status span action.
- Use the View Trace link in the Compliance Summary report to test rules. The View Trace shows exactly how BMC Network Automation applies the rule to the configuration.
- When the rules are functioning correctly, submit a Refresh Device Status span action to force a compliance check where discovered violations are logged, policies are triggered and the Dashboard is updated.
To run the Refresh Device Status action
- On the Add Job page, select Add Action > Span Actions > Refresh Device Status.
Enter information in the following fields:
(Optional) Annotation assigned to the action.
Select a realm, group, multiple devices, or a single device for the Refresh Device Status action. When the Network Span is Realm or Group, you can use Filter Devices to select which devices to include in the action.
When the action is triggered in an event-based Policy, additional options include: Same as Triggering Realm, Same as Triggering Group, Same as Triggering Device.
- Select the items that you want to refresh, any combination of the following:
- Compliance Violation Status: To re-evaluate the applicable enabled rule sets and rules against the current configurations.
- Discrepancy Status: To re-compute discrepancies based on current running and startup configurations and current device adapter contents.
- Configuration Attribute Profiles: To re-extract values from the current configurations based on the applicable enabled dynamic fields.
- Device Attributes Configuration: To re-generate the current device attributes configuration.
- Take offline if no successful snapshot within the past number days: To set devices offline that are malfunctioning.
- To execute the Refresh Device Status action for multiple devices in the network span concurrently, select the Run in Parallel option.
This option improves the efficiency of the refresh. By default, BMC Network Automation runs up to 20 span actions concurrently. See your system administrator if you want to change this default.
- Click OK to add the action to the job.