VMware ESX Interfaces Automatically Monitored after Upgrade to SolarWinds Platform 2025.2.x

8/6/2025 9:50 PM

8/6/2025 9:56 PM

After upgrading to SolarWinds Platform 2025.2.0 or 2025.2.1, some users may observe that interfaces on VMware ESX hosts are being automatically added to monitoring, even though these interfaces were not manually selected for monitoring. This behavior can result in alerts being triggered for interfaces that are shown as down, which were not previously managed.

 

This is most commonly reported when:

• ICMP-only VMware ESX nodes (polling via VMAN) suddenly show additional interfaces.
• Deleted interfaces reappear shortly after being removed.
• Unexpected alerts are triggered (e.g., alerts related to interfaces that were not monitored prior to upgrade).

 

This issue can be replicated by:

1. Adding a vCenter or ESX host via the Virtualization Add Node wizard.
2. Observing that new physical interfaces are added and monitored automatically.
3. Deleting the interfaces.
4. Waiting a few minutes - the interfaces reappear and begin generating alerts.

Virtualization Manager

There is currently no option in the SolarWinds Platform Web Console to disable the automatic polling of VMware ESX interfaces. To prevent these interfaces from being added and monitored, you must disable the associated poller using a SQL query.

 

1. Connect to the SolarWinds Platform server.
2. Open Database Manager from the SolarWinds Platform folder of the start menu.
3. Select Add Orion Server and expand the SQL Server in bold.
4. Right-click the SolarWinds Platform database and select New Query.
5. Paste one of the two options below and select Execute Query.

 

Option 1: Disable globally for all ESX hosts

-- 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.

UPDATE [dbo].[Pollers]
   SET [Enabled] = 0
WHERE [PollerType] = 'N.VMware.VMwareService.Interfaces'

Option 2: Disable only for specific nodes

Replace nodeid1, nodeid2, etc. with the corresponding Node IDs:

-- 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.

UPDATE [dbo].[Pollers]
   SET [Enabled] = 0
WHERE [PollerType] = 'N.VMware.VMwareService.Interfaces' AND [NetObjectID] IN (nodeid1, nodeid2, ...)

After running the script(s):

1. Wait a few minutes to ensure the poller is no longer active.
2. Delete the unwanted interfaces from the Nodes. They should no longer return.
3. Restart the SolarWinds Orion Module Engine service if interfaces still reappear after several polling cycles.