Configuration Management
This chapter contains steps to resolve device configuration and management issues.
Symptom/Cause | Solution |
CLI running configuration output does not match the output of NetConf ‘get-config’ output, and this conflict is leading to an inability to alter device configuration. This situation can arise when the device running-config or start-up configuration is not synced with the device configuration store. | You can use this command to recover the device from this state: • reload flush-db: This command removes the current start-up database. The board reboots after you give this command. |
Replacing the Start-up Configuration File
To replace a start-up configuration file, you must update the configuration database as well. To do this, follow these steps:
1. Copy the configuration file to the startup configuration (copy file command)
2. Reboot and apply the configuration to the device and the configuration database (reload flush-db command)
If the start-up configuration file and the configuration database are not synchronized, then the system does not allow configurations to be done and will result in an unstable state. Therefore, you must keep the configuration file and the configuration database synchronized.
This example shows replacing a start-up configuration file and then synchronizing it to the configuration database:
#copy file /home/ZebOS-TEST.conf startup-config
Copy Success
#
#reload flush-db
The system has unsaved changes.
Would you like to save them now? (y/n): n
Configuration Not Saved!
Are you sure you would like to reset the system? (y/n): y
For both of these prompts, you must specify whether to save or discard the changes. Abnormal termination of the session without these inputs can impact the system behavior.
For the unsaved changes prompt:
Would you like to save them now?
Always say “no” to this prompt because otherwise the command takes the current running configuration and applies it to the current start-up configuration.
OcNOS Datastores
Table 13-1 describes the datastores used by OcNOS.
Table 13-1: OcNOS datastores
Name | Location | Description |
|---|
Candidate configuration datastore | volatile memory | A configuration datastore that can be manipulated without impacting the device's current configuration and that can be committed to the running configuration datastore and stored in volatile memory. |
Running configuration datastore | CML_RD.db | A configuration datastore holding the complete configuration currently active on the device. The running configuration data store always exists. |
Startup configuration datastore | CML_DB.db | The configuration datastore holding the configuration loaded by the device when it boots. This separates the startup configuration datastore from the running configuration datastore. |
ZebOS.conf | /cfg/usr/local/etc/ZebOS.conf | The show running-config command queries protocol module data structures to get the running configuration and display it. A write given at the command line writes the running configuration to the ZebOS.conf file. The ZebOS.conf file contains device startup configuration in human-readable format (same as show running-config output). |
Note: Do not alter these datastores manually. Always use OcNOS/NetConf commands to read and update these files.