Upgrading the vSEC Controller

Upgrading from R80 to R80.10

To upgrade the vSEC Controller v1 and v2 from R80 to R80.10, see sk111841 for upgrade instructions.

Important Information

1. When you upgrade the vSEC Controller to R80.10 the following files are overwritten with default values:
   • vSEC Controller v1
     • $VSECDIR/conf/vsec.conf
   • vSEC Controller v2
     • $VSECDIR/conf/vsec.conf
     • $MDS_FWDIR/conf/tagger_db.C

   Before you begin the upgrade, back up any files that you have changed.

2. A Multi-Domain Server that contains imported Data Center objects in the Global Domain is not supported in the upgrade to R80.10. You must remove objects from the Global Domain before you install the upgrade.
3. Before you perform the upgrade on the Management server, if you have a Cisco APIC server, keep only one URL. After the upgrade, add the other URLs.
4. For upgrades from the vSEC Controller v1, manually connect again to each Data Center Server. For those servers that communicate with HTTPS, in SmartConsole double-click the Data Center object and trust the certificate again.

Note - During the upgrade, the vSEC Controller does not communicate with the Data Center. Therefore, Data Center objects are not updated on the Security Management Server or the Security Gateways.

Upgrading from R77.30 to R80.10

For information on upgrading from R77.30 to R80.10, contact Check Point Support.

vSEC Controller and Supported Security Gateways

The vSEC Controller works with:

• R77.20 gateways
• R77.30 gateways
• R80.10 gateways
• 60000/40000 Scalable Platforms R76SP.50 (starting with Jumbo Hotfix Accumulator, Take 20)

Important - To use the vSEC Controller with R77.20 and R77.30 gateways (R77.30 gateways with Jumbo Hotfix Accumulator below Take 309) install the R80.10 vSEC Controller v1 Enforcer Hotfix. See sk120464.