Redeploy Existing Configurations to a Device
You can force-deploy existing (unchanged) configurations to a single managed device. We strongly recommend you deploy in a maintenance window or at a time when any interruptions to traffic flow and inspection will have the least impact.
|
When you deploy, resource demands may result in a small number of packets dropping without inspection. Additionally, deploying some configurations restarts the Snort process, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without further inspection depends on how the target device handles traffic. See Snort Restart Traffic Behavior and Configurations that Restart the Snort Process When Deployed or Activated.
|
Before you begin
Review the guidelines described in Best Practices for Deploying Configuration Changes.
Procedure
| 1 |
Choose . |
||
| 2 |
Click Edit ( |
||
| 3 |
Click Device. |
||
| 4 |
Click Edit ( |
||
| 5 |
Click Force Deploy (
|
||
| 6 |
Click Deploy. The system identifies any errors or warnings with the configurations you are deploying. You can click Proceed to continue without resolving warning conditions. However, you cannot proceed if the system identifies an error. |
) next to the device where you want to force deployment.
). 
What to do next
-
(Optional) Monitor deployment status; see View Deployment Messages.
-
If deploy fails, see Best Practices for Deploying Configuration Changes.