Configuration changed but not saved for Cisco Nexus

Vendor

Cisco

Description

Indeni will alert if the configuration was changed on a device, but not saved.

Remediation Steps

Log into the device and save the configuration.
1. Check that there are not unsaved configuration changes by running the "show running-config diff" NX-OS command
2. Log into the device and save the configuration with the "copy running-config startup-config" NX-OS command
3. Consider creating snapshots of the configuration by utilizing the Checkpoint and Rollback NX-OS features. The NX-OS checkpoint and rollback feature are extremely useful, and a life saver in some cases, when a new configuration change to a production system has caused unwanted effects or was incorrectly made/planned and we need to immediately return to an original/stable configuration.
4. For more information about checkpoint and rollback NX-OS features please review the following article:
http://www.firewall.cx/cisco-technical-knowledgebase/cisco-data-center/1202-cisco-nexus-checkpoint-rollback-feature.html

How does this work?

This script logs into the Cisco Nexus switch using SSH and uses the "show running-config diff | count" command to check if there is a diff between the saved and running configuration. The output includes the number of unsaved lines.

Why is this important?

Check if the latest config changes were saved. If the config has not been saved and the device reloads, any unsaved config changes will be lost.

Without Indeni how would you find this?

It is not possible to poll this data through SNMP. Configuration changes are reported in Syslog, but the saved/unsaved state is not reported.

View Source Code
single