Skip to main content
The snctl power command group controls and monitors DC power for SN40L nodes. Power operations live in their own top-level command group, separate from snctl node.
Power operations affect actual hardware. They perform DC cycle operations through management interfaces (IPMI, Redfish, or SSH), and do not control AC power (PDUs), network switches, serial console servers, or other infrastructure components.

Key concepts

Read this section once. Everything after it depends on these five things.

Prerequisites

Every power command authenticates to the target devices, so device credentials must be registered first. If they are missing or wrong, the command fails to authenticate.
See Device credentials for details.

What each --type targets

snctl power cycle does not accept --type — it always targets the whole node.

Choosing a target

Either --node or --group must be specified. They are mutually exclusive.

The SambaNova Daemon check

snctl power on and snctl power cycle wait for snd.service (the SambaNova Daemon) to become active before returning, so a successful exit means the node is ready for work rather than merely powered. Pass --skip-snd-check to return as soon as power is applied, without waiting for the daemon. Use it when powering on hardware that is not expected to boot into a working SambaStack environment — for example, immediately before a firmware upgrade.
snctl power off and snctl power state do not wait for the daemon and have no --skip-snd-check flag.

Flags

Concurrency defaults

--parallelism-racks caps how many racks are processed at once, and its default differs per subcommand:
--parallelism-devices is a separate, global cap on nodes in-flight across all racks at once, regardless of how many racks are being processed. Use it to limit the total number of simultaneous IPMI, Redfish, and SSH sessions against your management network:

Check power state

Query the current power state of a node or its components. This is read-only and safe to run at any time.
Each cell reports On, Off, or Unknown. A component that could not be reached shows Error, with the reason listed as a note below the table. Single node:
Every node in a group:
Host only:
Including the protocol that answered each query:
With -o wide, the protocol is appended inline to each state rather than added as a separate column, because the table is pivoted with one column per component:

Power on

Turn on a node, its host, or its XRDUs.

Power off

Turn off a node, its host, or its XRDUs.

Power cycle

Power-cycle the entire node. Unlike the other subcommands, power cycle always targets the whole node — it does not accept a component --type.

Next step

To check or upgrade firmware on these nodes, see Firmware Updates.