Overview
This article describes the deployment communication model for Crosswork Assurance with emphasis on Sensor Management. In this model, the local management and control remain on-prem, while hybrid deployments forward measurement data to Cloud Crosswork Assurance for ingestion and analytics.
The objective of this model is to keep customer control local, move measurement processing to cloud analytics where applicable, and preserve a clear separation between control, telemetry, and planned alert-return traffic.
Deployment Summary
| Mode | Control Plane | Worker Model | Cloud Role | Notable Behavior |
|---|---|---|---|---|
| Hybrid | On-prem Crosswork Assurance cluster | Dedicated H/W SM worker node in non-HA, active/passive workers in HA | Measurement ingestion, analytics, and alerting | Sensor Controller connects directly to active H/W SM over SSH |
| Non-hybrid | On-prem Crosswork Assurance only | No dedicated H/W SM worker nodes | No Cloud Crosswork Assurance | H/W SM runs on controller node |
Diagram
Basic Components
Tip: For better viewing, click here to view the diagram in a new window.
Detailed Communications and Ports
Tip: For better viewing, click here to view the diagram in a new window.
Key Architectural Flows
Control flows
- PCA API gateway passes requests through Identity & Authorization to YANG Gateway.
- YANG Gateway drives local software sensor lifecycle and control actions.
- In hybrid mode, monitored-object and metadata requests can extend to Cloud Crosswork Assurance APIs.
- Users access H/W SM UI and API through nginx.
Telemetry flows
- CSV Collector sends sensor data to H/W / S/W Integration on the on-prem controller node.
- Gateway Collector communicates with Sensor Agent.
- Gateway Collector also forwards collected data to H/W / S/W Integration.
- Cloud Crosswork Assurance processes ingested measurements for analytics and alerting in hybrid deployments.
Planned flow
- Alert sync from Cloud Crosswork Assurance back to Local RabbitMQ is marked as planned.
- The described return path uses an outbound WSS connection from on-prem.
- Selected alerts are republished to the local event bus for YANG Gateway consumption.
Traffic classification
- CONTROL: API, orchestration, SSH, and UI/API proxying
- TELEMETRY: collector and measurement data movement
- PLANNED: alert return path
© 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