Upgrading Legacy Orchestrator and Sensor Control Together

This guide provides a consolidated, step-by-step path for upgrading Legacy Orchestrator from a virtual machine (VM) deployment to Docker, and upgrading Crosswork Assurance Sensor Control to the latest supported version. Use this guide when you must perform both upgrades together.

Critical Dependencies

Before starting any upgrade, understand the following critical dependencies:

Upgrade Path Overview

See below for the common scenario of upgrading from Legacy Orchestrator 23.04 VM to 24.09.1 Docker while also upgrading Sensor Control 23.12 to 25.07.2:

Prerequisites Checklist

Before starting, confirm the following:

• Deployment profile identified: 5K, 15K, 30K, or 60K (must match source and target)
• Redundancy configuration identified: Non-Hot Standby or Hot Standby
• Network information documented: Hostname, IP addresses, NTP server, timezone
• Docker host prepared: Meets CPU, memory, and disk requirements for your profile
• Firewall rules configured: Application can connect to network; users can access interfaces
• Required software files downloaded:
  • upgradeAppliance-SO_v23.12_11_package-prod.tar
  • SO_v23.12_11.fsa
  • Skylight_orchestrator_24.09.1_GA_8_docker-dist-cisco-24.09.1-GA-8.sh
  • VCX_25.07.2_121759.afl (Sensor Control firmware)

For deployment profile requirements, see Docker Deployment Profile Configuration.

Phase 1: Legacy Orchestrator Migration and Upgrade

Step 1: Upgrade VM 23.04 to VM 23.12 Release

Procedure: Upgrading Skylight orchestrator 23.12

Step 2: Prepare the Target Docker Environment (Docker 24.09.1)

Deploy a new Legacy Orchestrator Docker instance to version 24.09.1.

Procedure: Docker Deployment

Ensure:

• Same deployment profile as source (5K/15K/30K/60K)
• Hostname, IP address, NTP server, and timezone match source
• Firewall rules are in place

Step 3: Migrate 23.12 VM to 24.09.1 Docker

This step transfers your configuration and data from the VM to Docker.

Choose the procedure for your configuration:

• Non-Hot Standby: Migrating from a Non-Hot Standby Virtual Machine to Docker
• Hot Standby: Migrating from Hot Standby Virtual Machine to Docker

Phase 2: Sensor Control Upgrade

Prerequisite

• Legacy Orchestrator must be at either version 23.12.3, 24.09, or 24.09.1 before upgrading Sensor Control to 25.07.x.

Step 1: Review Sensor Control Release Notes

Before upgrading, review the Assurance Sensor Control release notes for important cautions.

Key cautions:

• Sensor Control upgrade does not automatically upgrade remote device firmware suites
• Remote device upgrades from firmware versions before FWSUITE_VCX_2.2_10190 are blocked
• If you have remote devices on older firmware, you must first upgrade them to FWSUITE_VCX_2.2_10190 using an older Sensor Control version

Reference: Assurance Sensor Control Release Notes 25.07.2

Step 2: Stage Firmware in Legacy Orchestrator

Procedure: Managing Device Firmware

1. Navigate to Devices > Firmware.
2. Click Add firmware.
3. Select the .afl file (VCX_25.07.2_121759.afl).
4. Click Import FW Load > Import.
5. Click Refresh to verify the firmware appears in the list.

Step 3: Create and Run Firmware Upgrade Job

Procedure: Setting Up a Firmware Upgrade Configuration Job

1. Navigate to Commission > Jobs.
2. Configure common job settings.
3. Select FW upgrade in the left pane.
4. Configure the upgrade:
   • Firmware from EMS: True (to use staged firmware) or False (to specify SFTP URL).
   • Type: Standard Upgrade (recommended) or Download and Activate for two-step process.
5. Click Apply, then Close.

Caution: Firmware upgrade requires a reboot. This momentarily interrupts traffic and operations.

Step 4: Verify Sensor Control Upgrade

1. Navigate to Devices ▶ Firmware.
2. Verify that the Sensor Control shows current firmware as 25.07.2.
3. Check device connectivity and that operations have resumed normally.

Post-Upgrade Verification Checklist

After completing all upgrades, verify that:

• Legacy Orchestrator version shows 24.09.1 in the UI
• All services are healthy (services status)
• Hot Standby redundancy is operational (if applicable)
• Device inventory is complete and accurate
• Alarms are functioning correctly
• Configuration jobs execute successfully
• Reporting and sessions work as expected
• Sensor Control firmware shows 25.07.2
• Remote devices are communicating normally

Troubleshooting

Upgrade Fails or Application Does Not Function After Upgrade

If the upgrade terminates unexpectedly or the application doesn't function correctly:

1. Roll back the upgrade.
   • Procedure: Upgrading Skylight orchestrator 23.12
2. Roll back the migration.
   • Non-Hot Standby: Migrating from a Non-Hot Standby Virtual Machine to Docker
   • Hot Standby: Migrating from Hot Standby Virtual Machine to Docker
3. Contact Cisco Technical Support with:
   • Current and target versions
   • Error messages or logs
   • Steps completed before failure

Sensor Control Upgrade Blocked for Remote Devices

If remote device upgrades are blocked due to old firmware:

1. Use an older Sensor Control version to upgrade remote devices to FWSUITE_VCX_2.2_10190 first.
2. Proceed with Sensor Control 25.07.2 upgrade.

Related Documentation

Legacy Orchestrator

• Upgrade Matrix
• Upgrade and Migration Navigator
• Docker Deployment Profile Configuration
• Docker Disk Configuration
• Managing Device Firmware
• Upgrading Firmware of Devices

Assurance Sensor Control

• Assurance Sensor Control Release Notes 25.07.2