Network Management
How to Monitor Vertiv UPS Devices In-Depth Using Universal Device Pollers (UnDP) in SolarWinds NPM
This article explains how to implement additional UPS performance monitoring for Vertiv/Liebert/Emerson UPS devices in SolarWinds NPM using Universal Device Pollers (UnDP) and vendor-provided MIB files. It covers the native monitoring gap for Vertiv devices, the available THWACK ready-made UnDP package, custom poller creation, assignment, display, and alerting.
First published date
Last published date
Overview
When a Vertiv UPS device is added to SolarWinds via SNMP, the following is monitored natively out of the box:
-
Node up/down status via ICMP
-
Standard SNMP statistics (CPU and Memory utilization, where the device exposes them via SNMP)
SolarWinds NPM includes a dedicated Power Control Unit (PCU) Status widget that displays overall UPS status, battery status, time on battery, battery charge capacity, and firmware version. However, this feature is limited exclusively to APC devices using the PowerNet-MIB. Vertiv, Liebert, and Emerson UPS devices are not supported by the PCU Status widget and do not receive this data natively in SolarWinds NPM.
To poll additional UPS-specific metrics from vendor-provided MIBs on Vertiv devices, the confirmed supported method is Universal Device Pollers (UnDP).
Product section
Resolution
Option A: Use the Ready-Made Vertiv UnDP Package from THWACK (LIEBERT-GP-FLEXIBLE-MIB)
A community-published UnDP package is available on THWACK for Vertiv Emerson Liebert UPS devices using the LIEBERT-GP-FLEXIBLE-MIB. This package includes pre-configured pollers with thresholds and does not require building pollers from scratch.
Download: Vertiv Emerson Liebert UPS Battery Environmentals — THWACK
Pollers included in the package:
|
Poller Name |
Description |
Pre-set Thresholds |
|---|---|---|
|
VertivUPSBatChargePercent |
Battery Charge Percentage |
— |
|
VertivUPSBatStatus |
Battery Status (Normal / On Battery) |
— |
|
VertivUPSBatTimeRemain |
Remaining Runtime (minutes) |
Warning: 60 min / Critical: 30 min |
|
VertivUPSChargeStatus |
Charge Status |
— |
|
VertivUPSOutputFreq |
Output Frequency (Hz) |
Warning: >60.6 or <59.4 |
|
VertivUPSOutputSource |
Power Source (Grid / Battery) |
Warning when on Battery |
|
VertivUPSOutputV |
Output Voltage |
Warning: >130V / Critical: <108V |
|
VertivUPSTempIn |
Internal Temperature (°C) |
— |
|
VertivUPSCtoF |
Temperature in Fahrenheit (Transform) |
Warning: >100°F / Critical: >130°F |
To import the package:
-
Download the
.UnDPfile to the SolarWinds polling engine server. -
Open the Universal Device Poller application:
Start > All Programs > SolarWinds Platform > Universal Device Poller -
Click
File > Import Universal Device Pollers. -
Browse to the
.UnDPfile and clickOpen. -
Select the poller group in the import wizard and click
Import, thenOK. -
The pollers will appear under
All Defined Pollers.
Proceed to Step 3: Assign Pollers to Nodes below.
Option B: Build Custom Pollers from the Vendor-Provided MIB
If your Vertiv devices use a different MIB than LIEBERT-GP-FLEXIBLE-MIB, create custom UnDP pollers manually using the OIDs from the MIB files provided by the vendor.
Note: SolarWinds does not require you to compile or import the MIB file into the platform for polling to work. You only need the OID values from the MIB.
To verify which OIDs your device responds to, use the SolarWinds SNMP Walk tool to perform a full MIB walk against the UPS device:
- Default location:
C:\Program Files\SolarWinds\Orion\SnmpWalk.exe
To create a custom poller:
-
Open the Universal Device Poller application.
-
Click
New Universal Device Poller. -
Enter a descriptive name and assign it to a group (e.g.,
Vertiv UPS). -
In the
OIDfield, enter the OID directly from the vendor MIB file. -
Select the appropriate SNMP Get type:
-
Get— for scalar (single-value) OIDs -
GetNext— for table-based OIDs
-
-
Enable
Keep Historical Dataif historical trending is required for this metric. -
Configure a
Transformif the raw value requires unit conversion (e.g., temperature reported as a scaled integer). -
Click
Finishto save the poller.
Repeat for each metric to be monitored.
Step 3: Assign Pollers to Vertiv UPS Nodes
This step applies to both Option A and Option B.
Important: UnDPs are tied to the polling engine on which they are created. If Vertiv UPS nodes are monitored by an Additional Polling Engine (APE), the UnDP must be created and assigned from that APE — not the Main Polling Engine.
-
In the Universal Device Poller, click
Assign Pollers. -
Expand
All Pollersand check the box next to the Vertiv UPS poller group. -
Click
Next, expandAll Nodes, and select the Vertiv UPS nodes. -
Click
Testto verify each OID responds on the selected nodes.-
Nodes returning
No DataorOID not supportedeither do not support that specific OID or are unreachable via SNMP — deselect those nodes.
-
-
Click
Finishto complete the assignment.
Step 4: Display Poller Data on the Node Details Page
-
Navigate to the Node Details page of a Vertiv UPS node.
-
Click
Customize Page. -
Click the
+icon to add a resource. -
Under
Node Detail Reports, add one or more of the following confirmed resources:-
Universal Device Poller Status— tabular view of current polled values -
Tabular Universal Device Poller— tabular view for table-based pollers
-
-
Click
Done. Allow up to one full polling cycle for data to appear.
Step 5: Configure Alerts on UnDP Data
-
Go to
Alerts & Activity > Alerts > Manage Alerts > Add New Alert. -
Set the scope to
I want to alert on > Node. -
Under
Trigger Condition, add:-
Custom Node Poller — [Unique Poller Name] — Statistic is less than [threshold]
-
-
Configure the desired trigger and reset actions (email, webhook, etc.).
Notes and Limitations
-
UnDPs are tied to the polling engine on which they are created. Creating an UnDP on the Main Polling Engine will not make it available on an APE.
-
There is no built-in per-node threshold differentiation in UnDP. If different UPS units require different thresholds, use Node Custom Properties combined with Custom SQL alert conditions.
-
If the Vertiv device OID is not found in the SolarWinds MIB tree for browsing purposes, enter the OID directly into the OID field — the MIB does not need to be compiled into SolarWinds for polling to work.
-
A Device Studio Node Details poller, if created, overrides the standard
N.Details.SNMP.Genericpoller entirely — not just the specific field being customized. If used, all Node Details fields (Vendor, Machine Type, Description, SysName, Contact, Location, SysObjectID, Software Version) must be explicitly defined in the poller to avoid those fields going blank.
Additional Resources
Please note that Thwack is a community space where users may post any content as a suggestion or recommendations to you for your internal use. The information set forth herein may come from third-party websites or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.