Introduction
This article provides configuration details for the Sensor Collector in Hardware (H/W) and Software (S/W) Sensor Management deployments. Use this article alongside the Replicated Cluster with H/W Sensor Management Worker Deployment article, which contains the broader Crosswork Assurance deployment workflow and additional background details.
H/W Sensor Collector
The Sensor Collector collects CSV files exported by H/W Sensor Management and sends the data to Crosswork Assurance. Enabling this option provisions the collector and configures H/W Sensor Management's Northbound API to publish CSV files over SFTP.
The collector is optional and independent of the main installation. It can be configured or changed after H/W Sensor Management is running.
Host Requirements
The collector deployment host must meet the following requirements:
| Requirement | Details |
|---|---|
| Docker | Docker must be installed. |
| Local user | A local skylight user must exist with a home directory and a login shell. Example: useradd -m -s /bin/bash skylight |
| Sudo group membership | The skylight user must belong to the sudo group on Ubuntu or the wheel group on RHEL. |
| Docker group membership | The skylight user must belong to the docker group. |
| Sudo configuration | Sudo must require a password. Example sudoers entry: skylight ALL=(ALL) ALL. Do not use NOPASSWD. Use the Skylight User Password configured under Host Information. |
| SSH authentication | The public key corresponding to the SSH private key uploaded under Host Information must be installed in /home/skylight/.ssh/authorized_keys. |
Configuration
| Field | Value |
|---|---|
| Sensor Collector | Enabled: Provision the CSV collector and configure H/W Sensor Management to publish CSV files to it over SFTP. Disabled: Leave unchecked when the collector is not required. |
| Show the prerequisites | Select to display the collector host requirements. |
| Uninstall Sensor Collector (delete) | Select to remove the collector containers, volumes, installation files, and Crosswork Assurance configuration, and disable H/W CSV exports. Exported CSV data is preserved. Increment the uninstall trigger and deploy to perform the uninstall. Collector provisioning is skipped while this option is selected. |
| Collector Name | Used as both the connector configuration name and zone. Default value: hw-sm-collector |
| CSV Path | Directory from which the Sensor Collector FileWatcher reads CSV files. The directory must be writable or able to be created on the collector deployment host. Default value: /opt/data/hw-sm-collector |
| Local PCA Access Token (PAT) | Personal access token used for local Crosswork Assurance collector API calls, package downloads, and configuring the connection between H/W Sensor Management's Northbound API and the collector. |
| Collector Deploy Target IP | IP address of the host running the collector container. This can be the Sensor Management host, the local Crosswork Assurance host, or another reachable host. H/W Sensor Management reuses the uploaded SSH key to publish CSV files directly to CSV Path; no separate SFTP configuration is required. |
S/W Sensor Management
The S/W Sensor Collector installs an OpenMetrics collector (RoadRunner) from local Crosswork Assurance on the configured host. This feature is independent of H/W Sensor Management and Hybrid mode.
Host Requirements
The collector deployment host must meet the following requirements:
| Requirement | Details |
|---|---|
| Docker | Docker must be installed and running. |
| Required utilities | Bash, curl, jq, OpenSSL, GNU tar, and iproute2 (ss) must be installed. |
| Local user | A local skylight user must exist with a home directory. |
| SSH authentication | The SSH public key installed for skylight must match the configured private key. |
| Docker group membership | The skylight user must belong to the docker group. |
| Sudo configuration | Sudo must require a password, using an entry such as skylight ALL=(ALL) ALL. Do not use NOPASSWD. The configured Skylight User Password is used for privilege escalation when needed. |
| SSH access | SSH connectivity must be available from the cluster to the collector host. |
| Crosswork Assurance connectivity | HTTPS connectivity must be available from the collector host to local Crosswork Assurance. |
| Collector ports | Inbound TCP ports 55777 and 55888 must be accessible from S/W sensors. Both ports must be unused before installation. |
| Sensor certificate trust | S/W sensors must trust the generated self-signed CA certificate, .tls_custom/ca.pem. Certificate distribution to sensors is not automated. |
Configuration
| Field | Value |
|---|---|
| Sensor Collector | Enabled: Install RoadRunner from local Crosswork Assurance on the configured host. Existing collectors automatically apply Hybrid tenant changes. Container recreation briefly interrupts collection. |
| Show the prerequisites | Select to display the collector host requirements. |
| Uninstall Sensor Collector (delete) | Select to remove the collector containers, volumes, installation files, and Crosswork Assurance configuration. Increment the uninstall trigger and deploy to perform the uninstall. Collector provisioning is skipped while this option is selected. |
| Reuse H/W Sensor Management SSH and Sensor Collector Settings | Checked: Deploy the S/W Sensor Collector on the same server as the H/W Sensor Collector, using the same connection settings. Unchecked: Configure a different server or connection settings. |
| Collector Name | Used as both the collector name and zone. Default value: sw-sm-collector. Warning: Uninstall the collector using its existing name and target before changing either value. A different collector name still requires available collector ports on the target host. |
| Certificate Generation | Self-signed CA and signed server certificate: Generate a private self-signed CA valid for 3,650 days and a CA-signed server certificate valid for 365 days, using the collector zone as their common name. Enables RR_INSECURE for gateway connections to Crosswork Assurance. Import .tls_custom/ca.pem from the collector installation directory into each sensor's trust store. Certificates are preserved during subsequent deployments. Certificate renewal must be performed manually. Upload certificate: Unavailable in this version. |
© 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