Cisco Firepower 1010 Getting Started page 36

Deploying Your Changes
Caution
The FTD device drops traffic when the inspection engines are busy because of a software resource issue, or
down because a configuration requires the engines to restart during configuration deployment. For detailed
information on changes that require a restart, see
page
Procedure
Step 1 Click the Deploy Changes icon in the upper right of the web page.
The icon is highlighted with a dot when there are undeployed changes.
The Pending Changes window shows a comparison of the deployed version of the configuration with the
pending changes. These changes are color-coded to indicate removed, added, or edited elements. See the
legend in the window for an explanation of the colors.
If the deployment requires that inspection engines be restarted, the page includes a message that provides
detail on what changed that requires a restart. If momentary traffic loss at this time would be unacceptable,
close the dialog box and wait until a better time to deploy changes.
If the icon is not highlighted, you can still click it to see the date and time of the last successful deployment
job. There is also a link to show you the deployment history, which takes you to the audit page filtered to
show deployment jobs only.
Step 2 If you are satisfied with the changes, you can click Deploy Now to start the job immediately.
The window will show that the deployment is in progress. You can close the window, or wait for deployment
to complete. If you close the window while deployment is in progress, the job does not stop. You can see
results in the task list or audit log. If you leave the window open, click the Deployment History link to view
the results.
Optionally, you can do the following:
• Name the Job—To name the deployment job, click the drop-down arrow on the Deploy Now button
and select Name the Deployment Job. Enter a name, then click Deploy. The name will appear in the
audit and deployment history as part of the job, which might make it easier for you to find the job.
For example, if you name a job "DMZ Interface Configuration," a successful deployment will be named
"Deployment Completed: DMZ Interface Configuration." In addition, the name is used as the Event
Name in Task Started and Task Completed events related to the deployment job.
• Discard Changes—To discard all pending changes, click More Options > Discard All. You are prompted
for confirmation.
• Copy Changes—To copy the list of changes to the clipboard, click More Options > Copy to Clipboard.
This option works only if there are fewer than 500 changes.
Getting Started
36
37.
Configuration Changes that Restart Inspection Engines, on
Getting Started