---
title: "xNode2 Takes Longer to Boot After Software Update"
slug: "xnode2-takes-longer-to-boot-after-software-update"
updated: 2026-05-01T16:34:32Z
published: 2026-05-01T16:34:32Z
canonical: "docs.telosalliance.com/xnode2-takes-longer-to-boot-after-software-update"
---

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

# xNode2 Takes Longer to Boot After Software Update

## Overview

There are occasions when an **xNode2** may take longer than expected to boot — particularly after a software update. This behavior is normal and does not generally indicate a problem.

## Why This Happens

After a software update, the system performs an integrity check between:

- The stored **configuration database**
- The active **system configuration**

If the unit determines that the running configuration does not match the database, it will:

1. Update the internal system configuration to match the database
2. Automatically reboot to apply those changes

This results in what appears to be a longer boot cycle because the unit is effectively booting twice.

## What You May Observe

- The unit boots normally after the update.
- It remains online briefly.
- It then reboots again automatically.
- The second boot completes normally.

This is expected behavior when configuration reconciliation is required.

## When to Be Concerned

You should investigate further only if:

- The unit enters a continuous reboot loop.
- The unit never completes the second boot.
- The unit becomes unreachable after multiple boot attempts.

In normal circumstances, allowing the xNode2 sufficient time (several minutes) to complete this process will resolve the issue.

## Summary

A longer boot time after a software update is typically caused by the xNode2 detecting a configuration mismatch, updating its system configuration, and performing an automatic second reboot. This is part of the normal update process.