SSL Visibility Appliance: Difference between .nsu , .nru, and .patch file updates

Products

• SSL Visibility Appliance Software

Issue/Introduction

The SSL Visibility appliance supports three different update methods:

 

.patch

Updates the main partition; includes only the changes from one version to the next, all data and configurations are retained, applied through the WebUI.

 .nru

Replaces the existing rescue image with the new image; all data and configurations are retained, applied through the WebUI.
 

.nsu

System update file; replaces the active image, re-images the rescue partition, triggers restore factory defaults, retains management IP address; all existing data and configurations are wiped, applied through the WebUI.

Note: Configurations are wiped, so you need to back-up the appliance before installing the .nsu. After you install the .nsu, you can restore the back-up files, starting with the PKI file, and then the Policy file.
IMPORTANT: Restore the PKI file before you restore the Policy file. If the Policy file is restored before the PKI file, then the Policy will be unable to find the PKI objects referenced in the ruleset and the SSL Visibility appliance will go into Fail-to-Wire (FTW) mode.

The following illustrations show how each update process appears in the SSL Visibility WebUI:

Update using the .patch file

[Before update]

[Select the patch file]

[confirm to update]

[After update only the active image was updated ]

 

Update using the .nru file

[Before update]

[Select the .nru file]

[confirm to update]

[After update only the rescue image was updated ]

 

Update using the .nsu file

[Before update]

[Select the .nsu file]

[confirm to update]

[After update active and rescue image were updated ]