Nodes Not Showing Under Manage Nodes but Visible Under Manage Agents in the SolarWinds Platform

2/19/2026 5:02 PM

2/19/2026 5:02 PM

• When searching for specific servers under Settings → Manage Nodes, only some of the expected nodes appear (or none at all).

• The same servers are present under Settings → Manage Agents, with:

  • Agent Status = Agent is running or Update available

  • Connection Status = Connected

• You can still Unmanage / Mute from Manage Agents, but do not see the related node rows under Manage Nodes.

Example:

1. Manage Nodes shows only a single node matching the search:

 

2. Manage Agents shows multiple agent entries for the same servers:

    

Server Application Monitor

Node objects were likely removed or changed while agents remained registered, leaving “agent‑only” entries.

1. Agents and Nodes are separate objects

In the SolarWinds Platform:

• Agent records (on the Manage Agents page) and Node records (on the Manage Nodes page) are distinct objects.

• By default, when a new agent registers and no node exists yet, the platform automatically creates a managed node for that machine, unless Automatically create node has been disabled in Agent Settings.

• If a node already exists, the agent is added but the polling method is not automatically switched to agent.

2. Node objects were deleted or renamed, leaving “agent‑only” entries

If someone:

• Deleted the node from Manage Nodes, or

• Renamed/modified the node record while leaving the agent in place

then the platform is left with:

• A valid agent object under Manage Agents, but

• No active managed node tied to that agent (or a node with a different name/IP).

This explains why:

• The servers still appear as agents (and can be unmanaged/muted from that view).

• The same servers do not appear under Manage Nodes when searching by their current hostname.

3. “Update available” is unrelated to node visibility

The “Update available” agent status only indicates the agent software version is behind the SolarWinds Platform version and needs an upgrade; it does not control whether a node exists or appears in Manage Nodes.

Remove the agents and nodes from SolarWinds and re‑add them, which recreates the node records and restores normal behavior.

Step 1 – Confirm the orphaned agent

1. In the web console, navigate to
   Settings → All Settings → Manage Agents.

2. Search for one of the affected servers by hostname or IP.

3. Confirm:

   • Agent Status is Agent is running (or Update available).

   • Connection Status is Connected.

If the agent is disconnected or unhealthy, fix connectivity first; otherwise proceed.

---

Step 2 – Recreate/attach the node from Manage Agents

For each affected server:

1. On Manage Agents, select the agent row.

2. Click Manage as Node.

3. The Add Node page opens pre-populated with the agent details.

4. Complete the Add Node wizard (credentials, polling method, etc.) and click Submit.

Result:

• A new node object is created (or the existing one is correctly tied to the agent).

• The server now appears under Settings → Manage Nodes and behaves normally (including Unmanage/Remanage and Mute/Unmute options).

If this works for one test server, repeat the same procedure for the remaining agents.

---

Step 3 – Clean rebuild (if needed)

If the Manage as Node workflow does not behave as expected or the node remains inconsistent, you can perform a clean rebuild:

1. From Manage Agents, Delete the problematic agent record.

2. From Manage Nodes, remove any stale/duplicate node entries associated with that server (if present).

3. Re‑deploy or re‑register the agent for that server using your normal process (Agent wizard or manual installer).

4. Ensure the agent connects and is visible again in Manage Agents; a corresponding node should be auto‑created (if automatic node creation is enabled — see next section).

This is effectively the approach the customer used in the referenced case: remove agents and nodes, then re‑add them, which restored a consistent state.

---

Additional Checks / Prevention

1. Ensure “Automatically create node” is enabled

To avoid future “agent‑only” entries when new agents are deployed:

1. Go to Settings → All Settings → Agent & Remote Collector (or Agent Settings on older versions).

2. Click Define Global Agent Settings.

3. Confirm that Automatically create node is selected.

This ensures any new agent that registers on a server that is not yet a node will automatically create a corresponding node record.

---

2. Deletion / rename hygiene

When cleaning up or renaming nodes:

• If you intend to decommission a server:

  • Uninstall or delete the agent via Manage Agents, which also removes the associated node (for typical scenarios).

• If you rename a node in Manage Nodes, confirm that:

  • The agent record still points to the correct server.

  • There are no duplicate nodes for the same host.

Limiting who can delete nodes and having a standard process for agent/node removal helps avoid partial cleanup that can result in orphaned agents.