admin@ctrl01:~$ cli
admin connected from 10.1.10.2 using ssh on ctrl01 --- WARNING ------------------------------------------------------Running db may be inconsistent. Enter configuration mode and load a saved configuration.------------------------------------------------------------------

To fix the “Running db may be inconsistent.

Enter configuration mode and load a saved configuration”,
please do the following [Note there will be some downtime as services need to be stopped]

Please enter configuration mode on CLI and save the configuration
e.g.

[edit]
admin@Branch1-cli(config)% save /var/tmp/config.txt

Exit out of CLI onto the shell
vsh stop
cd /opt/versa/confd/var/confd/cdb
rm the 3 cdb files A.cdb, 0.cdb and C.cdb
vsh start
Enter configuration mode on CLI once the device is UP and do “load merge <config.txt>” [the file saved in step 1]

admin@Branch1-cli(config)% load merge ?
Possible completions:
  <filename/terminal>

admin@Branch1-cli(config)% load merge /var/tmp/config.txt 
admin@Branch1-cli(config)% commit and-quit

From Shell
admin@Branch1$ vsh restart

Check the branch configuration and stability post applying this resolution. In case of any error encountered during the commit, which leads to an error caused by any syntax. Follow the second method to recover VOS from this error.

Second Method:

Before continuing with the recovery action. Make sure we collect the necessary files backup as part of the pre-requisite to help this method.

- Backup configuration (save /var/tmp/config.txt )

- Backup A.cdb, C.cdb, and O.cdb

- Backup ckey file

- Backup all certificates, and key files loaded on this VOS

- Take snapshot of this VOS from Versa Director

Once all the prerequisites are completed for this second method. Continue with the below actions:

admin@VGW-01-cli> request erase running-config

Restored A.cdb, C.cdb, and O.cdb backup files - Copy these three cdb files from any other external system to the impacted VOS. These three CDB files were taken as a backup in our pre-requisite.

[admin@VGW-01: cdb] $ vsh restart

Check the presence of the original configuration in VOS, and verify all certificates are still intact as before.