ISR Computing -

CSM - Firewall deploy error. Failed to create snapshot: Internal error

To fix "CSM - Firewall deploy error. Failed to create snapshot: Internal error":

1. Stop the daemon manager

2. Reset the password for the "vms" database
To do this, open a command prompt in CSCOpx/bin directory and issue the following command:

perl dbpasswd.pl dsn=vms npwd=admin

This will reset the DB password to "admin"

3. Connect to the DB using dbisqlc program

Invoke "dbisqlc" from command prompt
After the "dbisqlc" gui comes up fill in the following fields:
At Login tab -> User ID : DBA ; Password : admin
At Database tab -> Database name: vms
click ok

4. Execute the following query to find the devices that we removed but still present in the VPN-

select * from vpndevice where deviceid not in (select device_id from device)

NOTE: IF THE ABOVE QUERY RETURNS SOME RESULT, THE CUSTOMER IS FACING THE PROBLEM OF THE DANGLING DEVICE. IF IT IS THE CASE PROCEED WITH THE FOLLOWING STEPS. ELSE STOP HERE AND WE NEED TO INVESTIGATE FURTHER!

5. Note down the results of the above query. This will have a deviceId and ref_id columns. Note down the device_id and ref_id for each entry

device_id=X
ref_id=Y

For each of these deviceIds use the following steps

6. Execute the following query to find the corresponding "node_id"

select * from policy_main  where  ref_id=Y

In the above query, replace Y with the ref_id found in step#5
From the query results, note down the value for "node_id".

node_id=Z 

7. Clean up the database using the following commands

delete from vpndevice where deviceid=X
delete from policy_main where ref_id=Y
delete from hierarchy_nodes where node_id=Z
delete from history_devices where device_id=X

In the above, replace X with the deviceId found in step 5, replace Y with the ref_id found in step 5, and replace Z with the node_id found in step#6.

8. Commit the changes

Type "commit" in dbisqlc and press "execute"

9. Close the dbisqlc tool and restart the daemon manager