✨ New: Try our AI‑powered Search (Ctrl + K) — Read more

Compatibility Matrix

Prev Next

cureThis article provides a comprehensive compatibility matrix for Cisco Provider Connectivity Assurance, showing how platform components, collectors, sensors, and software versions work together across the entire solution.

Solution Overview

The Provider Connectivity Assurance solution consists of multiple interconnected components. Use this matrix to understand compatibility requirements when deploying or upgrading.

Browser Compatibility

For supported browsers and display requirements, see Browser and Connectivity Requirements.

Sensor Control Release Compatibility

The following table shows minimum compatible release versions for Provider Connectivity Assurance components when using Sensor Control (VCX).

Sensor Control

Skylight Orchestrator (VM)

Legacy Orchestrator (Docker)

Provider Connectivity Assurance (Kubernetes)

25.07.2

23.12.3

24.09.1

25.07

25.07.1

23.12.3

24.09.1

25.07

25.07

23.12.3

24.09.1

25.07

24.11.1

23.12

23.12

N/A

24.11

23.12

23.12

N/A

24.09

23.12

23.12

N/A

23.12

23.12

23.12

N/A

Notes:

  • Sensor Management and Analytics are capabilities included in Provider Connectivity Assurance 25.7. In later releases, an option to deploy Provider Connectivity Assurance with only the Sensor Management capability (without Analytics) will be available.

  • If you roll back to an earlier release, roll back all software components to compatible versions.

Module Dock Remote Device Compatibility

The following table shows the remote device firmware suite versions that each Module Dock release can configure.

Module Dock Release

Supported Firmware Suite Versions

25.07

20.05, 20.11, 20.11.2, 21.12, 22.06, 22.12, 22.12.1, 23.12, 24.09, 24.11, 24.11.1, 25.07

24.11.1

20.05, 20.11, 20.11.2, 21.12, 22.06, 22.12, 22.12.1, 23.12, 24.09, 24.11, 24.11.1

24.11

20.05, 20.11, 20.11.2, 21.12, 22.06, 22.12, 22.12.1, 23.12, 24.09, 24.11

24.09

2.4, 2.5, 2.5.0.2, 2.6, 2.6.0.1, 2.7, 19.07, 19.12, 20.05, 20.11, 20.11.2, 21.12, 22.06, 22.12, 22.12.1, 23.12, 24.09

Sensor Management Device Compatibility

The following table details the device firmware releases that are known to interoperate with Sensor Management.

For release-specific details, see the Sensor Management Release Notes.

Software Release

Sensor Control

Sensor GT

Sensor LT

Sensor LX

Sensor F100

Sensor F25

25.7

19.12 → 25.07.2

7.1.2 → 25.07

7.1.2 → 25.07

7.9 → 25.07

22.01.1 → 24.08

23.09 → 24.08

24.09.1

19.12 → 25.07.2

7.1.2 → 25.07

7.1.2 → 25.07

7.9 → 25.07

22.01.1 → 24.08

23.09 → 24.08

24.09

19.12 → 24.09

7.1.2 → 24.07

7.1.2 → 24.07

7.9 → 24.07

22.01.1 → 24.08

23.09 → 24.08

23.12.4

19.12 → 25.07.2

7.1.2 → 25.07

7.1.2 → 25.07

7.9 → 25.07

22.01.1 → 24.08

23.09 → 24.08

23.12.3

19.12 → 25.07.2

7.1.2 → 25.07

7.1.2 → 25.07

7.9 → 25.07

22.01.1 → 24.08

23.09 → 24.08

23.12.2

19.12 → 22.12.2

7.1.2 → 7.9.6

7.1.2 → 7.9.6

7.9 → 7.9.6

22.01.1 → 23.09.1

23.09 → 23.09.1

23.12.1

19.12 → 22.12.2

7.1.2 → 7.9.6

7.1.2 → 7.9.6

7.9 → 7.9.6

22.01.1 → 23.09.1

23.09 → 23.09.1

23.12

19.12 → 22.12.2

7.1.2 → 7.9.6

7.1.2 → 7.9.6

7.9 → 7.9.6

22.01.1 → 23.09.1

22.01.1 → 23.09.1

Notes:

  • Releases prior to 23.04 cannot provide RTT values for TWAMP and ETH-DM using Sensor Control releases 22.12 or later.

  • If you intend to deploy Sensor Control 22.06 - 24.11.1 to your network, please ensure you have first upgraded to release 24.09 or later.

  • If you intend to deploy Sensor Control 25.07 or 25.07.1 to your network, please ensure you have first upgraded to release 24.09.1 or later.

Sensor Agent Deployment Compatibility

Assurance Sensor Agents deploy as containers. The following table shows the deployment requirements by release. For installation details, see Sensor Agent Installation Guidelines.

Agent Release

Architecture

Container Runtime

Base Image

25.07.1

x86_64, ARM64

Docker 23.0.6+

Alpine 3.22

25.07

x86_64, ARM64

Docker 23.0.6+

Alpine 3.21

24.09

x86_64, ARM64

Docker 23.0.6+

Alpine 3.20.1

24.05

x86_64, ARM64

Docker 23.0.6+

—

23.11

x86_64, ARM64

Docker 20.10.0+

—

Notes:

  • Sensor Agents use a container-based deployment model. The host OS must support the required Docker version.

  • Agents use a destroy-redeploy upgrade model—configuration is stored in the orchestration system, not the agent container.

  • Docker-compose configurations are backwards compatible to release 21.12.

Sensor Capture Hypervisor Compatibility

Assurance Sensor Capture can be deployed in virtualized environments. For deployment instructions, see How to Deploy Assurance Sensor Capture Virtual Appliance in VMware and How to Deploy Sensor Capture Virtual Appliance in Hyper-V.

Hypervisor

License Requirement

Traffic Capture Methods

VMware vSphere

Standard or Enterprise

Virtual Standard Switch (VSS)

VMware vSphere

Enterprise+

VSS, Distributed Virtual Switch (DVS), ERSPAN

Microsoft Hyper-V

Windows Server 2019, 2022

Port Mirroring

Notes:

  • DVS and ERSPAN require VMware vSphere Enterprise+ license.

  • VSS requires the Sensor Capture VA to be on the same ESX host as the VMs being monitored.

  • DVS allows the Sensor Capture VA to be on a different ESX host but on the same L2 network.

  • ERSPAN allows the Sensor Capture VA to be on a different L3 network.

Telemetry Collector Router Compatibility

The Telemetry Collector ingests Model Driven Telemetry (MDT) from Cisco IOS XR and IOS XE routers. For complete setup instructions, see Telemetry Ingestion Solution Guide.

Platform

Connectivity Options

Default Metrics

Cisco IOS XR

gNMI Dial-In, MDT Dial-Out

Y.1731 delay/jitter, IPSLA, interface bandwidth, CPU/memory utilization, QoS policy metrics

Cisco IOS XE

gNMI Dial-In, MDT Dial-Out

Interface bandwidth, CPU/memory utilization

Note: If your use case requires MDT telemetry data not covered by the default metrics, contact Sales for a customization quote.

For questions or feedback on this documentation, contact the Technical Publications team at techpubs_skylight@cisco.com.

© 2026 Cisco and/or its affiliates. All rights reserved.

For more information about trademarks, please visit:
Cisco trademarks 
For more information about legal terms, please visit:
Cisco legal terms