09-05-2018 10:34 AM - edited 02-21-2020 08:12 AM
Created a new vpn policy the other day and pushed it to a pair of appliances, but when i did the deploy failed and as a result faced an outage briefly on the network. Modified the configuration, redeployed but same results (failed plus an outage). Looking online, found this:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc56570
Which seems to suggest that this is a bug. Anyone else experienced this and have some possible work-arounds, other than maintenance windows for what should be benign changes?
Solved! Go to Solution.
09-05-2018 06:13 PM
Hi,
The defect that you have mentioned is applicable only when we make changes pertaining to device parameters/flex config or VPN.
For instance, if the change is in an access control policy or intrusion policy and then the policy deploy fails the defect is not applicable. No temporary drop in connection would be seen.
09-05-2018 06:13 PM
Hi,
The defect that you have mentioned is applicable only when we make changes pertaining to device parameters/flex config or VPN.
For instance, if the change is in an access control policy or intrusion policy and then the policy deploy fails the defect is not applicable. No temporary drop in connection would be seen.
09-12-2018 08:02 AM
Thanks for the information. The change I made was indeed adding what seemed like a simple vpn configuration. NAT and Access Policy were already previously deployed, was just the vpn that failed and caused the outage.
05-17-2022 06:44 AM
How did you solve the problem, did you return the changes made?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide