Posted: 2023-06-06 04:36 AM
I am writing to report a problem with PowerChute SNMPv3 connection on Windows 11 Pro. I have installed the latest version of PowerChute Serial Shutdown on my Windows 11 Pro machine and configured it to use SNMPv3 protocol. However, I am unable to connect to the PowerChute Agent using Synology SNMPv3 client software. I have verified that the SNMP service is enabled and running on Windows 11 Pro and that the firewall is not blocking the SNMP port (162).
I would appreciate it if someone could guide me to an instruction of how to set up correctly.
Thank you for your assistance.
Posted: 2023-06-06 05:01 AM
Just to be sure, are you trying to poll values or are you looking to receive traps from PowerChute?
I am asking, since I believe the polling (get/get next/walk) are on port 161 whereas the traps are being sent on 162. So if you are trying to poll values from the software and port 161 is not open, that might be the cause.
Posted: 2023-06-06 03:21 PM . Last Modified: 2023-06-06 03:23 PM
Thank you, Tonny, for your reply.
I just want to configure the Synology to read the UPS status so that it can automatically shut down in the event of a power outage.
I disabled the firewall, but unfortunately, it didn't solve the issue.
I have checked the registry, but I cannot find any relevant entries. Is it possible that there should be an entry related to Powerchute?
Posted: 2023-06-07 01:30 AM . Last Modified: 2023-06-07 01:40 AM
First off, I am not familiar with the capabilities in the Synology agent and I do not know your exact setup.
But generally speaking, you would be looking to use traps to get notifications on events or state changes, as relying on data that is being polled means that you will have "blind spots" in between the individual polls.
That said, I believe the manual for PowerChute has a section detailing the available options when it comes to what traps can be sent and what values can be polled (depending on the the connected UPS).
If you are having trouble reading any values at all, my suggestion would be to try to make it as simple at possible and start with SNMPv1 and see if you can get that going, before moving to SNMPv3.