All work
- Need to check error status code of SNMP PDU when handling SNMP SET responseNMS-3106Jeff Gehlbach
- Opennms Events not handled properly while we configure generic events.NMS-3027Jeff Gehlbach
- Add basic-authentication support to HttpDetectorNMS-2963
- INAP Version of Absolute Change Threshd EvaluatorNMS-2832Resolved issue: NMS-2832OpenNMS Bug Mailing List
- Exporting KSC report to a pdf fileNMS-2821
- search enhancementNMS-2818Resolved issue: NMS-2818OpenNMS Bug Mailing List
- DefaultSiteStatusServiceTests and DefaultSiteStatusServiceIntegrationTsts disabledNMS-2817Resolved issue: NMS-2817Donald Desloge
- clean up alarm API usage in opennms-qosdaemonNMS-2814Resolved issue: NMS-2814OpenNMS Bug Mailing List
- normalize radius codeNMS-2812Resolved issue: NMS-2812Seth Leger
- No easy way to save a zoomed graphNMS-2807
- Graph zooming stops working if a start/end time is specifiedNMS-2805
- Bad digest reports when collecting AND polling with v3 at authPriv (and maybe authNoPriv)NMS-2804Resolved issue: NMS-2804OpenNMS Bug Mailing List
- ADTRAN NetVanta 3205 agent returns INTEGER for ifPhysAddressNMS-2803Resolved issue: NMS-2803OpenNMS Bug Mailing List
- New Technogama.events.xml file for including into next versionsNMS-2801Resolved issue: NMS-2801
- distributed monitor disconnected timeout hardcodedNMS-2797Resolved issue: NMS-2797Seth Leger
- add possibility to threshold without saving dataNMS-2796Resolved issue: NMS-2796
- remote poller startup script should use java.confNMS-2794Resolved issue: NMS-2794OpenNMS Bug Mailing List
- HRULE not working in JRobin graphsNMS-2793Resolved issue: NMS-2793Ron Roskens
- Template KSC reportsNMS-2792
- SnmpTrapHelper method to forward a TL1 autonomous message as a trapNMS-2791Resolved issue: NMS-2791OpenNMS Bug Mailing List
- PostgreSQL performance on searches suffers from '%val%'NMS-2789Resolved issue: NMS-2789Benjamin Reed
- Feature - Threshold breach displayNMS-2788Resolved issue: NMS-2788OpenNMS Bug Mailing List
- Be able to add nodes based on surveillance categoryNMS-2787Resolved issue: NMS-2787Antonio Russo
- Search for surveillance categoriesNMS-2786
- Add a trap to OPENNMS-MIB for forwarding TL1 autonomous messagesNMS-2784Resolved issue: NMS-2784OpenNMS Bug Mailing List
- Current time in notificationsNMS-2783
- many simple forms perform "cancel" instead of "OK" when hitting enterNMS-2782Resolved issue: NMS-2782OpenNMS Bug Mailing List
- Fix concurrency issue in collector as described in 2714NMS-2778Resolved issue: NMS-2778OpenNMS Bug Mailing List
- Concurrency issues on multiprocessor systems cause collection outagesNMS-2777Resolved issue: NMS-2777
- change the remote poller to use the everything jarNMS-2776Resolved issue: NMS-2776Matt Brozowski
- Excessive resources consumed when notifying several uncorrelated eventsNMS-2775
- New in-memory thresholder (collectd) does not handle non-IP interfacesNMS-2774Resolved issue: NMS-2774Alejandro Galue
- Netscreen sub-interface and other hardware support during SNMP data collectionNMS-2773Jeff Gehlbach
- TCPEventProxy timeout code merge to 1.6NMS-2766Resolved issue: NMS-2766OpenNMS Bug Mailing List
- ModelImporterTest throwing database exceptions but still passingNMS-2765Resolved issue: NMS-2765David Hustace
- Fortinet Devices (SNMP query of CPU/MEM and session count)NMS-2764Resolved issue: NMS-2764OpenNMS Bug Mailing List
- Cannot deselect the last user or group in destination pathsNMS-2759
- Alarms on Dates (Asset)NMS-2758
- Service / host outagesNMS-2757Resolved issue: NMS-2757
- backport tl1 integration to 1.5.xNMS-2756Resolved issue: NMS-2756OpenNMS Bug Mailing List
- unnecessarily verbose exception on socket errorNMS-2755Resolved issue: NMS-2755OpenNMS Bug Mailing List
- be more explicit about errors on startupNMS-2754Resolved issue: NMS-2754OpenNMS Bug Mailing List
- mib2.hcbits bugsNMS-2753Resolved issue: NMS-2753Tarus Balog
- snmp match count supportNMS-2752Resolved issue: NMS-2752Tarus Balog
- update versions of dependenciesNMS-2751Resolved issue: NMS-2751OpenNMS Bug Mailing List
- various unit test failuresNMS-2750Resolved issue: NMS-2750OpenNMS Bug Mailing List
- clear alarms should be default actionNMS-2749Resolved issue: NMS-2749OpenNMS Bug Mailing List
- set default nsclient timeout/retriesNMS-2748Resolved issue: NMS-2748OpenNMS Bug Mailing List
- one-line alarms listNMS-2747Resolved issue: NMS-2747Tarus Balog
- separate the ticketing API into it's own projectNMS-2746Resolved issue: NMS-2746OpenNMS Bug Mailing List
50 of 145
Need to check error status code of SNMP PDU when handling SNMP SET response
Description
Environment
Operating System: All
Platform: PC
Acceptance / Success Criteria
None
Lucidchart Diagrams
Created March 2, 2009 at 6:27 PM
Updated September 21, 2021 at 6:23 PM
Hi,
My opennms version is 1.5.93. However, I found this minor bug might exist on all releases of opennms, even chunk.
Problem Description:
When performs a SNMP SET operation on a device, the SET response PDU contain errors (errorStatus is not 0), and return value is correct (return value = set value). In this case, system (OpenNMS) treats it as a successful SET operation. Actually, it fails.
Additional Info:
It is reproducible, and only happened when devices under management had something wrong in their SNMP implementation. And unfortunately, I met that case.
Resolution:
Update processResponse() method of opennms-snmp/opennms-snmp-snmp4j/src/main/java/org/opennms/netmgt/snmp/snmp4j/Snmp4JStrategy.java to check error status code. Here is the diff result of my change proposal:
334d333
< int errorStatusCode = responseEvent.getResponse().getErrorStatus();
346,350c345
< }
< else if (errorStatusCode!=0) {
< log().warn("TTT send: PDU error status code is not 0: " + a);
< }
< else {
—
> } else {
Regards,
Yu Hong