Node status and health

Use node status and health information to decide whether a node is ready for Applications, needs attention, or is still moving through a lifecycle operation. Status is the first signal, but it is not the whole picture. A healthy node also needs the expected project assignment, EVE-OS version, adapter configuration, storage, configuration state, and security posture.

Start from the Nodes list

Open Infrastructure > Fleet > Nodes. Use this page for fleet-level triage before opening an individual node. The table shows the node name, current Status, associated Applications, EVE-OS Version, location, and project. Search and filters help narrow the list when you are looking for a specific node, project, version, or status.

Nodes list showing Updating, Online, and Suspect statuses with EVE-OS version, location, and project columns.

The Nodes list supports status filters for Online, Registered, Suspect, Maintenance Mode, Updating, Rebooting, Init, Halted, Offline, and Error.

The floating + action is contextual. On the Nodes list, it starts node onboarding. On other resource pages, the same + creates that page’s resource.

Separate the signals

Status, admin state, configuration state, and health signals answer different questions.

Signal	What it tells you	Where to check
Status	What the node is reporting now, such as online, suspect, updating, or offline.	Nodes list and the node detail status ribbon.
Admin state	Whether the node is intended to be active, inactive, or registered.	Sub-label under Status in the status ribbon; full value in the Details tab under State & Timeline.
Uptime and last seen	Whether the node is actively reporting runtime data.	Node detail status ribbon.
Resource utilization	Whether CPU, memory, storage, or network usage may affect Applications.	Node detail Overview.
Configuration status	Whether the node has fetched the latest generated configuration.	Configuration Status action.
System and security	Whether attestation, HSM, PCR, virtualization, ECC, Configuration Lock, and Edge Sync signals look expected.	Node detail Overview.
Recent activity and events	What changed recently and whether lifecycle or configuration actions produced errors.	Node detail Overview and View events.

Use status for live readiness. Use the other signals to understand why the node is in that state and whether it is safe to act.

Interpret common statuses

Status	Meaning	Usual next check
Online	The node is connected and available for normal operation.	Confirm utilization, configuration status, and Application readiness.
Provisioned	The node identity is known to the platform, but the node may not yet be fully active. The Nodes list filter labels this state Registered.	Confirm assignment, admin state, and onboarding completion.
Init	The node is initializing or has not reported enough runtime state yet.	Wait briefly, then check last seen and recent events.
Updating	The node is preparing or applying an EVE-OS update.	Check recent activity and avoid interrupting the update.
Rebooting	A reboot has been requested or is in progress.	Wait for the node to return to Online, then review uptime and events.
Halted	The node has halted or is prepared for shutdown.	Confirm the shutdown was intentional before taking further action.
Offline	The cloud controller is not receiving expected communication from the node.	Check power, network reachability, EVE-OS boot state, and last seen.
Suspect	The node is reporting a condition that needs review.	Open the node, review configuration status, system/security signals, and events.
Error	The node has reported or entered an error state.	Open events, review recent activity, and inspect configuration differences.
Maintenance Mode	The node is in a maintenance-oriented state.	Confirm maintenance was intentional and avoid normal workload assumptions.

Review the node overview

Open a node from the list to review the detailed health view. Below the header action icons, the status ribbon shows a six-cell snapshot of Status, Uptime, Last seen, Reboot reason, EVE version, and Workload count. The page tabs below the ribbon organize health by area: Overview, Details, Workloads, Adapters, and Storage.

Node detail Overview showing status, live resource utilization, identity, workloads, recent activity, and system and security signals.

Start on Overview and check these areas:

Area	What to inspect
Status ribbon	Status (with admin state sub-label), uptime, last seen, reboot reason, EVE-OS version, and workload count. See Status ribbon for the full field reference.
Live status	CPU, network, storage, and memory utilization. Use this to spot resource pressure before deploying or troubleshooting Applications.
Identity	Name, title, serial number, project, location, and hardware model.
Workloads	Application count and current Application health at a glance.
Recent activity	Recent lifecycle, configuration, and operational changes.
System and Security	Attestation, HSM, PCR, virtualization, ECC memory, Configuration Lock, and Edge Sync signals when available. Hover the PCR signal to review reported PCR values and, if needed, configure a PCR template for the hardware model. See Manage PCR Templates and the System and Security panel.

Move to the other tabs when the symptom points to a specific area:

Tab	Use it when
Details	You need ownership, lifecycle, software, hardware, or admin-state context.
Workloads	Applications are not starting, running, or connecting as expected.
Adapters	Networking, VLAN, LAG, IO Adapter, or topology behavior needs review.
Storage	Volume placement, available storage, or disk health needs review.

Inspect configuration status

Select Configuration Status from the node detail header when a recent change has not appeared on the node, the node is Suspect or Error, or Configuration Lock may be affecting propagation.

Configuration Status dialog showing Last Fetched, Last Generated, and no configuration difference.

Use the dialog to compare:

Field	How to use it
Last Fetched	The latest configuration the node has fetched from the cloud controller.
Last Generated	The latest configuration the cloud controller generated for the node.
Difference state	Whether the node and cloud configuration are aligned.
Show Details	Opens the detailed configuration comparison when a difference exists.

If Last Generated is newer than Last Fetched, the node has not yet consumed the newest configuration. Check connectivity, Configuration Lock, node status, and recent events before making additional changes.

Readiness checklist

A node is generally ready for Applications when:

Status is Online or otherwise shows that the node has completed registration and is reporting.
The node is assigned to the expected project.
The EVE-OS version is known and appropriate for the workload.
Required adapters are configured for management and Application traffic.
Required Virtual Networks exist for the Applications you plan to deploy.
Storage is available for the expected workload.
Configuration status shows no unexpected difference.
System and security signals match your operational requirements.

Troubleshoot by symptom

Symptom	What to check first
Node is Offline	Confirm power, EVE-OS boot state, cloud reachability, last seen time, and recent events.
Node is Suspect or Error	Open the node, inspect Configuration Status, recent activity, system/security signals, and View events.
Node remains Updating or Rebooting	Wait for the lifecycle operation to finish, then review uptime and events if the status does not recover.
Applications do not start	Check Workloads, resource utilization, storage, and whether required Virtual Networks are present.
Applications cannot connect	Check Adapters, topology, VLAN or LAG settings, and Virtual Networks used by the Applications.
Recent configuration did not apply	Check Configuration Status, Configuration Lock, last fetched time, and connectivity.
Security posture looks wrong	Review System and Security, hardware model expectations, attestation state, and Configuration Lock state.

Verify the result

After investigating node health:

Confirm the node status matches the expected operation.
Confirm the admin state matches your intent.
Check recent activity and events if the status changed unexpectedly.
Review configuration status if the node did not apply a recent change.
Review adapters and storage if Applications cannot start or connect.

Next steps

Use Node details to understand each tab.
Use Configure node adapters to review NICs, VLANs, LAGs, IO Adapters, and topology.
Use Manage node lifecycle for operations such as reboot, deactivate, off-board, or delete.
Use Configuration locking if configuration changes are intentionally paused.

Start Here

Infrastructure Services Overview

Core infrastructure

Build

Applications and delivery

Edge Kubernetes

Operations

Monitor

Administration and Security

Troubleshooting

Partnerships

Start from the Nodes list

Separate the signals

Interpret common statuses

Review the node overview

Inspect configuration status

Readiness checklist

Troubleshoot by symptom

Verify the result

Next steps

​Start from the Nodes list

​Separate the signals

​Interpret common statuses

​Review the node overview

​Inspect configuration status

​Readiness checklist

​Troubleshoot by symptom

​Verify the result

​Next steps

Start from the Nodes list

Separate the signals

Interpret common statuses

Review the node overview

Inspect configuration status

Readiness checklist

Troubleshoot by symptom

Verify the result

Next steps