06-20-2014 09:35 AM
Since my partner finished commit of a PA-500, I have found the versioned configuration files locked on No.11, show as below. I have no idea about why it happened. This problem make this device stop to increase versioned configuration files after committed. How can I fix it ?
PS: It's OK to delete all configuration if necessary.
06-21-2014 05:13 AM
I think someone has accidentally locked the configuration.
How to Remove Configuration Lock
06-21-2014 10:46 AM
Thanks for your reply. There is no body locked as below:
06-21-2014 12:07 PM
Could you try running the cli delete locks command using the root login.
> request config-lock remove
06-21-2014 01:25 PM
Yes, I had tried. The device responded:
Server error : Config is not currently locked for scope shared
I think it means that no one lock configuration.
Finally, I have cleared all versioned configuration files by this command
admin@PA-500> delete config-audit-history
that make all versioned configuration files --- and my problem---- disappear, even though I don't know why/how it happens.
However, thank you very much to talk with me.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!