> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sambanova.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# SambaRack Manager release notes

Release notes for SambaRack Manager, including new features, enhancements, and fixes.

***

## SambaRack Manager v2.2.3 release

**Release Date:** October 12, 2026

This release introduces hardware monitoring for SambaRack. Rack power, thermal, and RDU telemetry are published as Prometheus metrics and consumed by your existing monitoring stack.

### New features and enhancements

**Hardware monitoring**

This release adds three Prometheus exporters. The `sambanova-hardware-monitoring` Helm chart deploys the PDU and XRDU exporters. The SambaNova exporter ships with SambaNova Runtime and runs on each host module, and the chart adds the Service and ServiceMonitor that make it scrapeable.

| Component | Version |
| :- | :- |
| `sambanova-hardware-monitoring` chart | 1.0.0 |
| `pdu-exporter` | 1.0.0 |
| `xrdu-exporter` | 1.0.0 |

The PDU and XRDU exporters are enabled by default. The SambaNova exporter service is disabled by default: enable it on each host module, and set `sambanova-exporter.serviceMonitor.enabled=true` so Prometheus scrapes it.

| Exporter and scrape interval | Metrics enabled and what they report |
| :- | :- |
| **SambaNova exporter**<br />Ships with SambaNova Runtime<br />Scrape: 15s | **RDU utilization:** tile activity per RDU, as the percentage of each window spent in execute, argument load, program load, and idle<br />**RDU memory and I/O:** HBM, DDR, and PCIe statistics<br />**Faults:** platform fault and error counts per host<br />**Platform identity:** runtime and component versions, boot and service timestamps |
| **XRDU exporter**<br />Scrape: 30s | **Thermal and fans:** XRDU temperature (°C) and fan speed (RPM) per sensor<br />**Reachability:** BMC up/down |
| **PDU exporter**<br />Scrape: 30s | **Rack power:** real power draw (W) per PDU, rolled up to rack level<br />**Reachability:** PDU up/down |

RDU metrics are labeled by `node`. All metrics carry a `rack` label once you declare rack topology.

Hardware monitoring is documented as separate guides:

* [Monitoring overview](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/monitoring-overview)
* [Install monitoring](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/monitoring-install)
* [SambaNova exporter](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/exporter-sambanova)
* [PDU exporter](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/exporter-pdu)
* [XRDU exporter](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/exporter-xrdu)
* [Reference dashboards](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/monitoring-reference-dashboards)
* [Troubleshooting](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/monitoring-troubleshooting)

***

**Required configuration**

`targets` is empty by default, so the chart declines to render until you configure it. Before you install, set the PDU and XRDU targets, the XRDU BMC credentials, and, for per-rack grouping, the `rack` label. [Install monitoring](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/monitoring-install) covers each step and the cluster requirements.

***

**Dashboards and alerts**

These are standard Prometheus exporters. They work with any Prometheus-compatible tooling, so you can build dashboards, queries, and alerts in the stack you already run. Grafana is not required.

The chart installs three sample Grafana dashboards by default, covering rack power, fan and temperature, and RDU utilization. Use them as provided, or adapt them to your environment. See [Reference dashboards](/docs/en/sambastack/hardware-admin/sambarack-manager/monitoring/monitoring-reference-dashboards).

Alert rules are not included. The chart ships no `PrometheusRule` objects. Define thresholds for your environment against the metrics listed above.

***

### Known issues

* **RDU metrics report `-1.0` for absent components** – `-1.0` is a sentinel value, not a reading. It appears when a component is absent or not responding. Guard queries with `!= -1`, as the shipped dashboards do, so averages and sums exclude it.

***

## SambaRack Manager v2.1.1 release

**Release Date:** August 31, 2026

This release rewrites `snctl` as a Go binary, moves several commands into new groups, and adds bulk rack and group provisioning from an inventory file, all found under **1.0.0 version** for SambaRack Manager.

<Warning>
  **This release renames commands and flags.** Work through **Upgrade notes** before you upgrade, and update any script that calls `snctl`.
</Warning>

### Upgrade notes

**Renamed and relocated commands**

The `node power*` family has moved to a new top-level `power` group, and `device firmware-*` has become `firmware`.

| Previous | Current |
| :- | :- |
| `snctl doctor` | `snctl diag doctor` |
| `snctl node powerstate` | `snctl power state` |
| `snctl node poweron` | `snctl power on` |
| `snctl node poweroff` | `snctl power off` |
| `snctl node powercycle` | `snctl power cycle` |
| `snctl device firmware-check` | `snctl firmware version` |
| `snctl device firmware-update` | `snctl firmware upgrade` |

**Renamed flags and values**

| Change | Action |
| :- | :- |
| `snctl` rewritten in Go | Reinstall `snctl`. Existing scripts that pass the flags below need updating. |
| `rack add --type` renamed to `--partnumber` | Update scripts. The flag is now required. |
| Firmware `--type` renamed to `--device-type` | Update scripts. |
| Firmware `--file` renamed to `--image` | Update scripts. The flag is now optional — omit it to download the plan-of-record image automatically. |
| Device type `scs` renamed to `serial_terminal` | Update any script or inventory file using the previous name. |
| `--log-level` values changed from `DEBUG…CRITICAL` to `debug\|info\|warn\|error` | Lowercase the value and map `CRITICAL` to `error`. |
| `--version` / `-v` removed | Use `snctl version`. |

<Note>
  `--index` is accepted for the slotted device types `xrdu` and `card` only. It is rejected for `bios`, `bmc`, and `all`, which have no per-device slot.

  Firmware updates are supported for THOR card, BIOS, BMC, and XRDU devices.
</Note>

### New features and enhancements

**SambaRack Manager Go CLI**

`snctl` has been rewritten as a Go binary. Reinstall it before you upgrade, and update any script that passes the flags listed under **Upgrade notes** above.

Command output can now be controlled by a global `-o, --output` flag accepting `text` (the default), `wide` (additional detail), and `json` (a new JSON output format).

<Note>
  **`-o wide` is not universally supported.** `power on`, `power off`, `power cycle`, `firmware upgrade`, `group create`, `group add-rack`, `group remove-rack`, and `group delete` accept `text` or `json` only. `rack export` uses `-o` differently — it selects the output file format, `json` or `yaml`, inferred from the `--file` extension and defaulting to `json` on stdout.
</Note>

Two setup options are worth calling out:

* **Non-interactive initialization** – `snctl config init --defaults` accepts every default without prompting, for provisioning scripts and image builds.

  ```bash theme={}
  snctl config init --defaults --service-account /path/service-account.json
  ```

* **Per-device credential overrides** – Alongside the per-device-type default, a single device can carry its own credential, addressed by canonical path. `snctl secret get --device <path>` reports which tier the value resolved from. This is not part of standard setup; it is available for deployments that need it.

  ```bash theme={}
  snctl secret set --device Rack/001/Node/0/bmc
  ```

Device, power, and firmware administration are now documented as separate guides:

* [Command reference](/docs/en/sambastack/hardware-admin/sambarack-manager/srm-command-reference)
* [Power administration](/docs/en/sambastack/hardware-admin/sambarack-manager/srm-power-admin)
* [Firmware updates](/docs/en/sambastack/hardware-admin/sambarack-manager/srm-firmware-updates)
* [Inventory file schema](/docs/en/sambastack/hardware-admin/sambarack-manager/srm-inventory-file-schema)

***

**Bulk rack provisioning**

Racks and groups can now be provisioned from a file instead of one device at a time. A single SN40L-16 rack scaffolds around 17 devices, each otherwise needing its own `rack add-device` call.

```bash theme={}
snctl rack import <file> [flags]
```

The file is a native `snctl` inventory in JSON or YAML, and may contain a subset of racks, groups, or both — including a file produced by `rack export`. Pass `-` to read from stdin.

| Flag | Description |
| :- | :- |
| `--dry-run` | Preview the changes without modifying the inventory |
| `--overwrite` | Replace existing racks and groups. Without it, existing entries are skipped and reported. |

<Note>
  **Run with `--dry-run` first.** It reports exactly which racks would be added, updated, or skipped, and how many credentials would be imported, without writing anything.
</Note>

`snctl rack export` writes the inventory back out, exporting all racks when no rack ID is given. Passwords are always replaced with placeholders such as `${BMC_SECRET}`, so an export file is safe to share. If an import file does contain real passwords, they are loaded into the encrypted credential store and do not need setting separately.

`snctl rack show` now reports node names under `-o wide`, and always includes the `node_name` field under `-o json`.

For the file format and the full procedure, see [Rack administration](/docs/en/sambastack/hardware-admin/sambarack-manager/srm-rack-admin) and the [Inventory file schema](/docs/en/sambastack/hardware-admin/sambarack-manager/srm-inventory-file-schema).

***

## SambaRack Manager v1.2.0 release

**Release Date:** July 14, 2026

This release improves firmware update reliability across device types, 2-PDU SambaRack SN40L-16 configurations, and includes general performance and usability improvements, all found under **0.0.5 version** for SambaRack Manager.

#### Improvements and fixes

**Firmware update reliability**

* Improved reliability of firmware image downloads for `snctl device firmware-update` across a broader range of network environments.
* Resolved an issue affecting firmware upgrades for XRDU devices and updated steps for BIOS update
* `snctl device firmware-update` now validates `--type` against the set of supported device types.
* Cleaned up `firmware-check` output to remove unnecessary log noise on version-mismatch results.

**General improvements**

* Improved performance of commands that read inventory data

## SambaRack Manager v1.0.57 release

**Release Date:** April 30, 2026

This release introduces 2-PDU configuration support for SambaRack SN40L-16 and a new firmware update command for BIOS, BMC, card, and XRDU device types.

### New features and enhancements

**SambaRack SN40L-16: 2-PDU configuration support**

SambaRack Manager now supports the 2-PDU SambaRack SN40L-16 configuration (part number `P-1002331`) alongside the existing 4-PDU configuration (part number `1001934`).

* `snctl rack add` accepts part number `P-1002331`; the component list reflects the actual PDU count.
* `snctl rack list` shows `Type: P-1002331` and `PDUs: 2` for 2-PDU racks.
* `snctl rack show` shows only `PDU/1` and `PDU/2` for 2-PDU racks.
* The device index table is updated to reflect 1–4 (4-PDU config) or 1–2 (2-PDU config).

**Firmware update command**

The `snctl device firmware-update` command is now available for BIOS, BMC, card, and XRDU device types.

* Use `--rack-id` or `--group` to select the target; use `--index` to target a specific XRDU (single, comma-separated list, or all).
* Use `--file` for a custom firmware file; use `--force` to skip pre-condition checks.
* When upgrading multiple components in the same maintenance window, follow this order: THOR CARD → BIOS → BMC → XRDU.
* XRDUs within a rack are upgraded in parallel; racks within a group are processed sequentially.

***