Configuring H/W Sensor Management - Non-High-Availability System

Introduction

This article provides the configuration values and verification steps for deploying Hardware Sensor Management (H/W SM) in a non-high-availability environment with a worker VM instance. 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.

Details for Configuring H/W Sensor Management on the Crosswork Assurance Admin Console Web GUI

Host Information

Field	Value
Enable H/W Sensor Management	Enabled
Host Information	Enabled
Show the prerequisites	Select to display the Docker host requirements.
Host IP Address(es)	IP address of the H/W SM worker
SSH Private Key	Upload the `skylight` private key file
Skylight User Password	Password for the skylight user (required for sudo access).
Enable Dual-Stack	Check: Sensor Management connects to devices on both IPv4 and IPv6 networks. Uncheck: Sensor Management connects to devices on IPv4 networks only.

High Availability

Field	Value
High Availability	Disabled

Application Configuration

Field	Default / Lab Value
Application Configuration	Enabled
Application Version	`25.07.1-LTS-HYBRID`
Deployment Selection	Install
Device profile (max devices)	5K
Session profile (max sessions)	125K
User profile (max users)	250
FIPS mode	Enabled: Sensor Management manages FIPS devices. Disabled: Sensor Management manages non-FIPS devices. Default: Enabled

Leave ⚠ Reset Worker Node(s) (Destructive) off.

Sensor Collector

Field	Default / Lab Value
Sensor Collector	Disabled unless required (a personal access token is required when enabled)

Refer to Configuring the Sensor Collector for H/W and S/W Sensor Management for details.

Deploy and Verify H/W SM Worker

Crosswork Assurance deploys the H/W SM worker automatically. Pre-flight checks include the H/W SM worker checks (SSH as skylight, sudo, firewalld/SELinux, disk, and other prerequisites); resolve any failures before deploying.

Follow the progress on the Controller node:

Access the root user or run sudo su - if the account has sudo privileges.
Configure to use kubectl command, enter:

export KUBECONFIG="/var/lib/embedded-cluster/k0s/pki/admin.conf"
export PATH="$PATH:/var/lib/embedded-cluster/bin"

Check pods and job log, enter:

kubectl -n pca get jobs,pods | grep hw-sm
kubectl -n pca logs job/<hw-sm-app-deploy-job-name>

When the installation succeeds, the hw-sm-app-deploy log ends with:

The installation of Cisco Crosswork Assurance Sensor Management <version> ... is complete

Then verify:

Check	Command	Expected Result
Worker joined	`kubectl get nodes`	The SM worker is `Ready` alongside the Kubernetes node(s)
H/W SM containers	On the worker: `docker ps`	`so-core`, `so-med`, `so-nbi`, `so-mysql`, `so-syslog` all `healthy`
H/W SM CLI	On the worker, as `skylight`: `/usr/bin/smcli.sh`	SM management menu
Admin Console	Dashboard	Ready, Cluster State Up to date

The H/W SM files are under /home/skylight/so/ on the worker.

© 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