Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Tripp-Lite UPSes not discoverable via SNMP

We just installed a lot of new Tripp-Lite UPSes with the WEBLXCARD installed. I can run a discovery with only ICMP and find them. When we try with SNMP they are not found. We verified the snmp community string by using it on a network switch and doing a test discovery and found the switch. I have updated the MIBs database.

Do I need to install the specific Tripp-Lite MIBs text file and install it?

Find more posts tagged with

Accepted answers

All comments

ggatten

To discover you may not need the MIB, but to monitor it you will. As deep as the MIB library is, it seems it should still be there?

Your community string on UPS is same as switches? Any ACL/security features on it blocking you? Is SNMP actually enabled on the UPS?

bobmarley

If the MIB is not there, get a copy of it and usually the URL you used to get it at Tripp-Lite is helpful and open a ticket. Support will incorporate into the MIB library and then you can get the update and put it into your system.

John-AVUSD

We have a different community string on one older test switch and we tested the new community string on a new switch. Both were found by the solarwinds network discovery.

John-AVUSD

The Tripp-Like MIB file is a txt file and not any sort of installer. Is there a support doc to install a third-party file?

John-AVUSD

We were able to resolve the issue. I believe my installer was using the CLI. I was able to create a user under " User Accounts -> SNMP Users " with a monitor roll and SNMP ver 2. The user name doesn't matter with SNMP 2 but the community string needs to be there. I don't know what settings were created in the CLI.