Setting this write-only object to bootCold (0) triggers a full cold boot that reruns diagnostics, reloads operational software (downloading it fresh if needed), and reloads configuration before restarting the node; setting it to bootWarm (1) skips diagnostics and software reload, just reloading configuration and restarting. An admin picks cold boot to recover from a suspected software or hardware fault, and warm boot for a faster restart when only configuration needs refreshing, since cold boot takes considerably longer and disrupts traffic longer. For example, after pushing a corrected node configuration, an admin would use bootWarm to apply it quickly without the multi-minute diagnostics cycle of a cold boot.