About viewing network changes
This topic contains the following sections that describe how to view network changes in BMC Network Automation:
You can view network changes by navigating to Home > Home > Dashboard. The Dashboard is displayed.
The Dashboard identifies what has changed when responding to unplanned, problematic, and non-compliant changes.
The Dashboard lists all devices with known configuration discrepancies and compliance violations. A user can also launch Quick Reports to view change discrepancies and compliance violations. The report is generated for the current view.
Viewing configuration discrepancies
For each device listed on the Dashboard, information is provided about various types of discrepancies. These discrepancies appear in the following columns in the displayed table.
- Running versus Startup: Differences that were detected between the active Running configuration and the boot Startup configuration and need to be reconciled (that is, Commit).
- Running versus Trusted Running and Startup versus Trusted Startup: Differences that were detected between your administratively assigned Trusted configuration and the current device configuration. For recommendations for managing the trusted configuration see About device configuration management.
- OS image discrepancy: This type of discrepancy is detected if the current Running and Trusted Running configuration files are tagged with different OS versions.
Viewing changes by device
To further analyze, accept, or remediate the discrepancy or violation displayed on the Dashboard, click the device name. For recommendations on how to resolve Dashboard discrepancies and violations see Fixing compliance violations.
Through the displayed device properties, you can perform the following actions and generate the following reports:
- View Device Details: Access the device record to view device details, inventory, configuration history, and the status of the last configuration action (for example Snapshot, Deploy to Active, Deploy to Stored, Deploy OS image).
- View Discrepancy Details: View details of the discrepancies (that is, differences) between the current and the trusted configuration.
- View Running/Startup Change Summary: View the events and configuration changes since the earliest discrepancy or compliance violation.
- View OS Image History: View the history of OS image versions installed on the device since detecting an OS image discrepancy. An OS image discrepancy is detected when the current Running and Trusted Running configuration files are tagged with different OS versions.
- View Running/Startup Compliance Summary: View the pass or fail status for all Rules assigned to the device.
- View Events: Displays the number of events reported on the device or group since the earliest discrepancy or violation was detected. This enables you to determine if a configuration change can be the cause of a network problem.
- Reboot: Restart the device. Clears the discrepancy between the Startup and Running configurations.
- Snapshot: Back up the Running and Startup configurations. This action causes the BMC Network Automation system to capture the current Running and Startup configurations for discrepancy and violation analysis.
- Refresh Device Status: Refresh the compliance status, discrepancy status and/or configuration profiled dynamic fields (CAP). For information about when to use this span action for refreshing compliance status, see Viewing compliance violations.
- Telnet/SSH Session: Launch a Telnet/SSH session with the device to interrogate the device or change the configuration.
- Mark As Trusted: Mark the current Running or Startup configurations as trusted.
The Running versus Trusted Running or Startup versus Trusted Startup discrepancies are cleared. Perform this operation when you are ready to baseline (that is, mark as trusted) the current Running or Startup configurations.
- Deploy to Active: Use this option to resolve discrepancies (that is, rollback to Trusted Running) or violations (that is, Remediate With Rule Set(s)) in the current Running configuration.
- Commit: Copy the current Running configuration to the Startup Configuration on the device. The Running versus Startup discrepancy is cleared. This operation ensures that when the device restarts, the Startup is the same as the current Running configuration.
- Deploy to Stored: Use this option to resolve discrepancies (that is, Deploy to Stored the Trusted Startup) or violations (that is, Remediate With Rule Set(s)) in the current Startup configuration. You can reconcile all issues with the Running configuration first (using Deploy to Active), and then perform a Commit operation.
Viewing changes by group
To further analyze, accept, or remediate the discrepancy or violation listed on the Dashboard, select the By > Groups option, and then click the group name.
The reports and span actions are now applied to all the devices in the group. If a span action is not applicable to a device in a group, it is skipped.