How to Set Up SNMP Monitoring for Your UPS System
Why SNMP Monitoring Is Essential
SNMP (Simple Network Management Protocol) allows your UPS to communicate with network management systems, enabling remote monitoring, automated alerts, and automatic server shutdown during extended outages. For any professional IT environment — from a single server room to a multi-site data center — SNMP monitoring is considered mandatory infrastructure.
What You Need
- SNMP/Network management card: Installed in the UPS's communication slot
- Ethernet connection: From the SNMP card to your LAN
- IP address: Static IP recommended for the SNMP card
- MIB files: Voltronic-specific MIB files for your NMS
- NMS platform: Nagios, Zabbix, PRTG, SolarWinds, or similar
Step 1: Install and Configure the SNMP Card
- Power off the UPS communication slot (some support hot-swap)
- Insert the SNMP card into the network management card slot
- Connect an Ethernet cable from the card to your network switch
- Access the card's web interface using the default IP (check documentation)
- Configure: IP address, subnet mask, gateway, DNS, SNMP community strings
- Set SNMPv3 credentials for secure communication (recommended over SNMPv1/v2c)
Step 2: Import MIB Files into Your NMS
MIB (Management Information Base) files define the data points available from the UPS. Import the Voltronic UPS MIB into your monitoring platform to access OIDs for:
- Input voltage, frequency, and current
- Output voltage, frequency, current, and load percentage
- Battery voltage, charge level, temperature, and runtime remaining
- UPS status (online, on battery, bypass, fault)
- Alarm conditions
Step 3: Configure SNMP Traps
SNMP traps are alerts pushed from the UPS to your NMS when specific events occur:
| Trap Event | Severity | Action |
|---|---|---|
| Utility power failure | Warning | Alert IT team, start timer for shutdown |
| Low battery | Critical | Initiate automatic server shutdown |
| UPS overload | Critical | Alert immediately, shed non-critical loads |
| Battery replacement needed | Warning | Schedule maintenance |
| Over temperature | Warning | Check cooling, reduce load |
| Utility power restored | Informational | Cancel shutdown, log event |
Step 4: Automatic Server Shutdown
Configure shutdown agents on your servers that communicate with the UPS via SNMP or the UPS vendor's shutdown software:
- Windows: Install Voltronic's shutdown agent or use the built-in Windows UPS service
- Linux: Use NUT (Network UPS Tools) or apcupsd with SNMP driver
- VMware ESXi: Configure the UPS as a network-connected UPS in host settings
- Shutdown sequence: VMs first, then hosts, with adequate time between steps
Best Practices
- Use SNMPv3 with authentication and encryption — never leave SNMPv1/v2c community strings as "public"
- Place the SNMP card on a management VLAN, not the production network
- Test the full shutdown sequence quarterly to verify it works end-to-end
- Monitor SNMP card firmware and update regularly
Frequently Asked Questions
Common SNMP monitoring questions.
Frequently Asked Questions
What is the difference between SNMP polling and traps?
Polling is when the NMS actively queries the UPS at regular intervals (e.g., every 30 seconds) for status data. Traps are event-driven alerts pushed by the UPS to the NMS when something changes (power failure, low battery, etc.). Best practice is to use both: polling for regular status updates and dashboards, traps for immediate alerting on critical events.
Can I monitor multiple UPS units from one NMS?
Yes, that is the primary advantage of SNMP monitoring. Each UPS with an SNMP card has its own IP address and can be added as a separate device in your NMS. You can create dashboards showing all UPS units, their status, load levels, and battery health in a single view.
Do I need a dedicated network for UPS monitoring?
While not strictly required, placing UPS SNMP cards on a dedicated management VLAN is strongly recommended. This isolates management traffic from production, improves security, and ensures monitoring remains accessible even during network congestion or attack scenarios.
