On-Site Enrollment and Restoration Overview

StarlingX supports on-site enrollment and restore operations for AIO-SX subclouds in environments where the System Controller does not have BMC access and cannot communicate with the subcloud over the network until site configuration is complete. This scenario typically applies when connectivity is established only after deployment, such as through an IPsec tunnel provided by a vCSR.

Note

StarlingX supports on-site operations for AIO-SX subclouds only.

Important

Before starting any on-site operation, remove or eject any previously inserted media that contains a cloud-init seed ISO, such as an enrollment seed ISO left attached from an earlier operation. If you leave a seed ISO attached, cloud-init can detect it as a valid data source and reapply its configuration, overwriting the settings for the current operation.

For Subclouds Without BMC Access

The following topics cover on-site enrollment and restore procedures for subclouds that do not have BMC access:

• Enroll an AIO-SX Subcloud On-Site — Enroll a factory-installed subcloud using a seed ISO when the System Controller has no remote access.

• Restore an AIO-SX Subcloud On-Site — Restore a subcloud from local backup, remote backup, or factory defaults using a seed ISO or the GRUB boot menu.

• Troubleshoot On-Site Enroll and Restore Issues — Diagnose and resolve common issues that may occur during on-site enrollment and restore procedures.

For Subclouds With BMC Access

Use the standard remote enrollment and restore procedures for subclouds where the System Controller has direct BMC access. For more information, see:

• Enroll a Factory Installed Non Distributed Standalone System as a Subcloud

• Restore a Subcloud/Group of Subclouds from Backup Data Using DCManager CLI