Client application recieves only timeouts once agent is reset
Caleb Hensley <[email protected]> Tue, 14 Sep 2021 16:39:06 -0600
| Newsgroups | gmane.network.net-snmp.devel |
|---|---|
| Message-ID | <CAB9bh6Wf-GOAOc+6r3mfQtTJoEfFPmWOOLgtTdJv5J-n=v+-Ag@mail.gmail.com> |
Hello, Please let me know if this belongs in -users instead. I am using libsnmp30, v5.7.3, in a C++ client application on Debian Stretch. I'm using it to communicate with a managed PoE switch. Using the TUT:Simple_Application on the net-snmp wiki. I am able to set and get PoE status, among other commands. However, if this switch is reset via unplug or via OID command, the only response I get from the switch from then on is a timeout error until I restart the client application. When the application begins, communication works perfectly. Once the switch is turned off, the status from `snmp_sync_response()` reports that it is unsuccessful, but there is no timeout, which seems normal. However, once the switch is back online, the status from `snmp_sync_response()` is a STAT_TIMEOUT until I restart the client application. While these timeouts are happening, I am still able to communicate via snmp CLI (snmpget, snmpset, etc.). Is there any way to refresh the client communication? My fallback is to restart the application, but I would like to find a cleaner solution. Thank you for taking the time to help, -Cal _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders