For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
GitHub
DocumentationREST API Reference
DocumentationREST API Reference
    • Home
  • Overview
    • What is NICo?
    • Key Capabilities
    • Operational Principles
    • Day 0 / Day 1 / Day 2 Lifecycle
    • Scope and Boundaries
  • Getting Started
    • Building NICo Containers
    • Quick Start Guide
  • Architecture
    • Overview and Components
    • Reliable State Handling
    • Networking Integrations
    • Key Group Synchronization
  • Provisioning (Day 0)
    • Ingesting Hosts
    • Ingesting Hosts (REST API)
    • Machine Validation
    • SKU Validation
    • Measured Boot Attestation
  • Configuration (Day 1)
    • Network Isolation
    • Tenant Management
    • Organization & Permissions
  • Operations (Day 2)
    • Tenant Lifecycle Cleanup
    • Network Isolation
    • Network Security Groups
    • InfiniBand Partitioning
    • NVLink Partitioning
    • Rack-Level Administration (RLA)
    • IP Resource Pools
    • BGP Peering
    • nicocli Reference
      • Azure OIDC for Infra Controller Web UI
      • Force Deleting and Rebuilding Hosts
      • Rebooting a Machine
      • InfiniBand Setup
  • Reference
    • Hardware Compatibility List
    • Release Notes
    • FAQs
    • Glossary
GitHub
NVIDIANVIDIA
Developer-friendly docs for your API
Privacy Policy | Your Privacy Choices | Terms of Service | Accessibility | Corporate Policies | Product Security | Contact

Copyright © 2026, NVIDIA Corporation.

LogoLogo
On this page
  • Important note
  • Reboot Steps
  • 1. Obtain access to nico-admin-cli
  • 2. Execute the nico-admin-cli machine reboot command
Operations (Day 2)Playbooks

Rebooting a machine

||View as Markdown|
Previous

Force Deleting and Rebuilding Hosts

Next

InfiniBand Setup

This page describes how to reboot a machine managed by NVIDIA Infra Controller (NICo) (i.e. a managed host or DPU) in any potential state of its lifecycle.

Important note

This is not a site-provider or tenant facing workflow. Rebooting a machine while it is in-use for a tenant can have unexpected side effects. If a tenant requires a reboot, they should use the InvokeInstancePower request - which is properly integrated into the instance lifecycle.*

Reboot Steps

The following steps can be used to reboot a machine:

1. Obtain access to nico-admin-cli

See nico-admin-cli access on a NICo deployment.

2. Execute the nico-admin-cli machine reboot command

nico-admin-cli machine reboot can be used to restart a machine. It always will require the machine’s BMC IP and port to be specified.

BMC credentials can either be explicitly passed, or the --machine-id parameter can be used to let the NICo site controller read the last known credentials for the machine.

Rebooting a machine will also always reset its boot order. The machine will PXE boot, and thereby will be able to retrieve new boot instructions from the NICo site controller.

Example:

/opt/nico/nico-admin-cli -c https://127.0.0.1:1079 machine reboot --address 123.123.123.123 --port 9999 --machine-id="60cef902-9779-4666-8362-c9bb4b37184f"

or using username and password:

/opt/nico/nico-admin-cli -c https://127.0.0.1:1079 machine reboot --address 123.123.123.123 --port 9999 --username myhost --password mypassword