UPS data appears on non‑UPS devices (Power Control Unit Status widget and UPS inventory) in SolarWinds Platform

Symptoms

In affected environments, you may observe one or more of the following:

• On the Node Details view for a non‑UPS node (for example, a switch SW-CORE-01.example.local), the Power Control Unit Status widget is visible and shows UPS information (model, serial number, battery metrics, output status, etc.), even though the device is not a UPS.
• In Manage Nodes or a UPS/Power Control Unit inventory report, non‑UPS devices appear with UPS‑related attributes, such as:
• Name: APC UPS
• Model: Smart-UPS SRT 5000
• Serial Number: identical to a known UPS node
• This behavior is often noticed after an upgrade to a newer SolarWinds Platform core version (for example, from an earlier 2024.x build to a 2025.x build), when PCU/UPS functionality is migrated and discovery is rerun.

Example patterns you might see:

• Node Details page for a switch:
• Device caption: SW-ACCESS-01
• Machine type: Cisco Catalyst XXXX
• Power Control Unit Status widget present, showing a UPS model and serial number.
• Database / SWQL examples (generic):
• PowerControlUnitData_man_1 contains rows such as:
  

  ID   Name     SerialNumber     Model               FirmwareVersion
  ---  -------  ---------------  ------------------  ----------------
  101  APC UPS  AS1234567890     Smart-UPS SRT 5000  UPS 16.0 (ID1044)
  205  APC UPS  AS1234567890     Smart-UPS SRT 5000  UPS 16.0 (ID1044)

  where ID = 101 is a real UPS node and ID = 205 is a non‑UPS device (for example, a switch).
• Pollers table contains entries such as:
  

  PollerType                  NetObject   NetObjectType   NetObjectID
  --------------------------  ----------  -------------   -----------
  PCU.Statistics.SNMP.Generic PCU:101     PCU             101
  PCU.Statistics.SNMP.Generic PCU:205     PCU             205

  indicating that both the UPS and the non‑UPS node have a PCU poller.

These symptoms indicate that UPS (Power Control Unit) entities and pollers are attached to Node IDs that represent non‑UPS devices. Once this association exists, the standard Node Details view and UPS inventory will treat those nodes as UPS hosts.

The resolution has three parts:

1. Confirm which nodes are misclassified as UPS.
2. Clean up incorrect PCU entities and pollers for those nodes.
3. Optionally, reduce the chance of recurrences until you upgrade to a build that contains the fix.

Step 1 – Identify misclassified nodes

You can use either SQL (on the SolarWinds Platform database) or SWQL (via SWQL Studio/SDK) to locate nodes that have PCU pollers and PCU data.

1.1 Find NodeIDs that have PCU pollers

SELECT DISTINCT NetObjectID AS NodeID
FROM Pollers
WHERE NetObjectType = 'PCU';

Cross‑check each NodeID in the Nodes table (or via the SolarWinds Platform web console) to identify which devices are truly UPS hardware and which are non‑UPS (such as switches, routers, hypervisors, etc.).

1.2 Check PCU data for those NodeIDs

SELECT ID, Name, SerialNumber, Model, FirmwareVersion, ManufactureDateTime
FROM PowerControlUnitData_man_1
WHERE ID IN (<list_of_NodeIDs_from_query_above>);

Look for cases where the same UPS model and serial number appear for more than one ID, especially where one ID corresponds to UPS hardware and another ID corresponds to a non‑UPS device.

Make a list of NodeIDs that are not UPS devices but have PCU data and PCU pollers. These are the misclassified nodes you will clean up.

Step 2 – Remove PCU data and pollers from non‑UPS nodes

Warning: The following queries will permanently delete UPS/PCU entries for the specified NodeIDs. Run them only for NodeIDs you have confirmed are not UPS devices.

Assume you identified a set of non‑UPS NodeIDs such as:

NodeID: 205, 310, 412

2.1 Remove PCU statistics for those NodeIDs

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

DELETE s
FROM PowerControlUnitStatistics_1 s
JOIN PowerControlUnitData_man_1 d ON s.ID = d.ID
WHERE d.ID IN (205, 310, 412);

2.2 Remove PCU identity rows (main PCU records)

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

DELETE FROM PowerControlUnitData_man_1
WHERE ID IN (205, 310, 412);

2.3 Remove PCU pollers attached to these NodeIDs

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

DELETE FROM Pollers
WHERE NetObjectType = 'PCU'
  AND NetObjectID IN (205, 310, 412);

2.4 Restart polling services

After the cleanup:

1. Restart the Job Engine / Collector services (or the polling engine services) on the main and any additional polling engines hosting those nodes.
2. Allow a few polling cycles to complete.

Expected outcome:

• The affected non‑UPS nodes no longer have PCU entities or PCU pollers.
• The Power Control Unit Status widget auto‑hides on their Node Details pages.
• These nodes no longer appear in UPS / Power Control Unit inventory.

Step 3 – (Optional) Mitigation for scheduled discoveries with auto‑import

Until you can upgrade to a version that contains the discovery fix, you can reduce the chance of mis‑assignment recurring on scheduled Network Sonar Discovery jobs with auto‑import.

The idea is to clear discovered PCU results for specific discovery profiles before they run, so each run starts from a clean state.

Note: Column names and table structure can vary. Validate in your environment before using this pattern.

Example pattern:

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

-- Replace <ProfileID> with the Discovery Profile ID of the affected auto-import job.
DELETE FROM DiscoveredPowerControlUnitsData_man_1
WHERE DiscoveryProfileID = <ProfileID>;

You can:

• Schedule this as a SQL Agent job to run shortly before the corresponding discovery job, or
• Coordinate manual execution prior to each test if you are troubleshooting.

This does not fix existing misclassified nodes (you still need Step 2), but it can reduce the chance of new non‑UPS nodes being mis‑assigned as UPS by stale discovery results.

Step 4 – Long‑term recommendation (upgrade)

Once a SolarWinds Platform version is available that contains the PCU discovery fix, upgrade to that version to address the underlying discovery behavior. This will help prevent new mis‑assignments during scheduled discovery and auto‑import.

Refer to the SolarWinds release notes for details on PCU/UPS discovery fixes and verify whether your target version includes the relevant correction.

SELECT d.ID       AS NodeID,
       n.Caption  AS NodeCaption,
       n.Vendor
FROM PowerControlUnitData_man_1 d
JOIN NodesData n ON d.ID = n.NodeID
WHERE n.Vendor NOT IN (
  'American Power Conversion Corp.',
  'Eaton Corporation',
  'Emerson Computer Power'
);

If the preview is correct and a full database backup exists, you can run the following scripts.
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.
-- Remove PCU statistics for non-whitelisted vendors
DELETE s
FROM PowerControlUnitStatistics_1 s
JOIN PowerControlUnitData_man_1 d ON s.ID = d.ID
JOIN NodesData n ON d.ID = n.NodeID
WHERE n.Vendor NOT IN (
  'American Power Conversion Corp.',
  'Eaton Corporation',
  'Emerson Computer Power'
);
-- Remove PCU identity rows for non-whitelisted vendors
DELETE d
FROM PowerControlUnitData_man_1 d
JOIN NodesData n ON d.ID = n.NodeID
WHERE n.Vendor NOT IN (
  'American Power Conversion Corp.',
  'Eaton Corporation',
  'Emerson Computer Power'
);
-- Remove PCU pollers for non-whitelisted vendors
DELETE p
FROM Pollers p
JOIN NodesData n ON p.NetObjectID = n.NodeID
WHERE p.PollerType   = 'PCU.Statistics.SNMP.Generic'
  AND p.NetObjectType = 'PCU'
  AND n.Vendor NOT IN (
    'American Power Conversion Corp.',
    'Eaton Corporation',
    'Emerson Computer Power'
  );

-- Replace <ProfileID> with the Discovery Profile ID of the affected auto-import job.
DELETE FROM DiscoveredPowerControlUnitsData_man_1
WHERE ProfileID = <ProfileID>;