You probably read this article because something went wrong with your configuration. You have several options, depending on what have happened, and what you like to do.
|Method||Authentication||Reboot||Deletes all data|
|Rollback using HTTPS||Password||No||No|
|Rollback using console||Password||No||No|
|Rollback during boot||Console access||Yes||No|
|Factory reset||Console access||Yes||Yes|
Rollback using HTTPS
- Go to the Configuration > Revision management
- Select a previous (known working) revision (so that the line highlights in blue)
- Press "Rollback"
Rollback using console
- Login to the console
- Navigate to the configuration menu, select the desired revision, and press "R"
Rollback during boot
- Connect to the console (video or serial)
- Reboot (possibly by powering off)
- Do not press any keys when the firmware prompt appears
- Wait for it to start booting (takes about a minute)
- When you see Press any key for recovery..., do so (press any key)
- Run default-config which will commit a new configuration revision
- Run boot to boot with the new, default configuration
- Once logged in with the default username and password (admin) you can rollback to a known working configuration as described previously
Stuck in recovery (update) partition
If the Halon system isn't rebooted properly after the recovery partition's update instruction is written, it gets stuck with the error
mount /cfg: Operation not permitted
because the recovery partition doesn't perform an fsck before mounting. It is fixed by rebooting (by typing reboot), pressing any key when it says "Hit [Enter] to boot..." and typing at the prompt
unload lsdev set currdev=disk0s3a include /boot/loader.rc boot
which will boot the normal system partiton, that will repair the configuration partition (with fsck). You can watch the procedure in this video.