This article provides guidance about upgrade duration and service impact during a Corero platform upgrade across SWA (SmartWall Analytics), CMS (Central Management Server), and NTD (Network Threat Defense) components. It also outlines the recommended approach to minimize disruption during the upgrade.

Planned upgrade path

SWA: v10.3.0 → v10.3.4 → v11.7.2

CMS: v10.3.3 → v10.3.4 → v11.7.2

NTD: v10.3.0 → v11.7.2

Expected downtime - Each upgrade requires approximately 10–15 minutes per component for reboot and application startup. SWA may take slightly longer than CMS in some cases.

Service impacts are as follows

SWA: no traffic impact; temporary loss of data reporting

CMS: no traffic impact; temporary loss of configuration control and reporting

NTD: traffic impact expected; mitigation unavailable during upgrade

Recommended upgrade sequence

Upgrade SWA

Upgrade CMS

Upgrade NTDs

For NTD devices, upgrade one device at a time to reduce overall traffic impact, provided the remaining devices can handle the traffic.

Plan for a total maintenance window of approximately 2 to 2.5 hours, including operational overhead (execution, validation, and post-checks).

Follow the recommended sequence, and upgrade NTDs sequentially to minimize service disruption.NTD upgrades only affect live traffic; SWA and CMS upgrades temporarily affect management.