Launch of Consumer/Home Owner registration process!
We are pleased to announce the commencement of the Consumer/Home Owner Registration Process on Community. Consumers/Home Owners may now proceed to register by clicking on Login/Register. The process is straightforward and designed to be completed in just a few steps.
OIDs missing? (No Such Device)
APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-12-2210:14 AM
OIDs missing? (No Such Device)
Hi everyone.
I am trying to get some external sensor probes monitored in PRTG. Most of my devices are working just fine (with the OID 1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1) but I'm getting No Such Device as an error for two of them. I can see the sensor through the web interface so it is confirmed working. When I use an SNMP tester to walk the OIDs, the entire 1.3.6.1.4.1.318.1.1.10 section does not appear.
My working devices are Smart-UPS RT 3000 RM XLs. The one that doesn't have the OIDs is a Smart-UPS SRT 5000. Any ideas on what could be causing this? Firmware update needed?