Skip to content

Commit c49cad5

Browse files
Copilotlextm
andcommitted
Add comprehensive review of faulty device issues
Co-authored-by: lextm <425130+lextm@users.noreply.github.com>
1 parent 4a92a21 commit c49cad5

File tree

1 file changed

+138
-0
lines changed

1 file changed

+138
-0
lines changed

FAULTY_DEVICE_ISSUES.md

Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,138 @@
1+
# Faulty Device Issues Review
2+
3+
This document lists all imported issues that are related to faulty or non-standard devices and should be tagged with the `area:faulty-device` label.
4+
5+
## Review Date
6+
2026-02-26
7+
8+
## Criteria for Faulty Device Issues
9+
10+
Issues are classified as "faulty device" related if they meet one or more of the following criteria:
11+
12+
1. **Specific device vendor/model** exhibiting non-standard SNMP behavior
13+
2. **Device returns malformed/truncated/incorrect** SNMP data
14+
3. **Works in other SNMP tools** but not in SharpSnmpLib (indicates device-specific compatibility issue)
15+
4. **Explicitly mentions device bug** or firmware issue
16+
5. **Requires device-specific workaround** rather than a general fix
17+
18+
## Issues Requiring `area:faulty-device` Label
19+
20+
The following imported issues are related to faulty devices but currently **missing** the `area:faulty-device` label:
21+
22+
### #62 - HP Server OctetString Issue
23+
- **Status**: Needs tag
24+
- **Device**: HP server (OID .1.3.6.1.4.1.232.11.2.10.7.0)
25+
- **Issue**: OctetString field returning faulty hex values
26+
- **Reason**: Device-specific data encoding issue
27+
28+
### #83 - Dell iDRAC 8 SNMPv3 Trap Issue
29+
- **Status**: Needs tag
30+
- **Device**: Dell iDRAC 8
31+
- **Issue**: SNMPv3 trap receiving issue
32+
- **Reason**: Works in PowerSNMP Manager but not SharpSnmpLib (device-specific compatibility)
33+
34+
### #89 - MikroTik RouterOS Unsupported Data Type
35+
- **Status**: Needs tag
36+
- **Device**: MikroTik RouterOS
37+
- **Issue**: Unsupported data type 18 exception
38+
- **Reason**: Device uses non-standard SNMP data types
39+
40+
### #101 - Cisco ASA 5510 MsgFlags Issue
41+
- **Status**: Needs tag
42+
- **Device**: Cisco ASA 5510 firewall
43+
- **Issue**: Returns MsgFlags=8, library only handles 0-7
44+
- **Reason**: Works in Net::SNMP, device returns out-of-spec value
45+
46+
### #114 - Fortis Device Data Construction Exception
47+
- **Status**: Needs tag
48+
- **Device**: Fortis device
49+
- **Issue**: Data construction exception with mismatched communities
50+
- **Reason**: Device-specific behavior
51+
52+
### #370 - QNap NAS GetTable Truncation
53+
- **Status**: Needs tag
54+
- **Device**: QNap NAS (Firmware 3.2.3 Build 0209T)
55+
- **Issue**: GetTable returns truncated/misaligned table data
56+
- **Reason**: Works in iReasoning Browser but not SharpSnmpLib (device-specific compatibility)
57+
58+
### #420 - HP v1910-24G Switch VLAN Query
59+
- **Status**: Needs tag
60+
- **Device**: HP v1910-24G switch
61+
- **Issue**: VLAN query issue
62+
- **Reason**: Device-specific behavior
63+
64+
### #436 - Cisco Switch MAC Address per VLAN
65+
- **Status**: Needs tag
66+
- **Device**: Cisco switch
67+
- **Issue**: MAC address retrieval per VLAN in SNMPv3 returns empty data
68+
- **Reason**: Device-specific VLAN context handling required
69+
70+
### #469 - HP OpenView Integration Issue
71+
- **Status**: Needs tag
72+
- **Device**: HP OpenView
73+
- **Issue**: Integration issue
74+
- **Reason**: Device/platform-specific compatibility
75+
76+
### #471 - Dell Server MIBs RFC1212 Loading
77+
- **Status**: Needs tag
78+
- **Device**: Dell server
79+
- **Issue**: RFC1212 loading issue with Dell MIBs
80+
- **Reason**: Device-specific MIB format
81+
82+
### #475 - Citrix Xen GetTable Timeout
83+
- **Status**: Needs tag
84+
- **Device**: Citrix Xen SNMP Agent
85+
- **Issue**: GetTable operations timeout
86+
- **Reason**: Works in iReasoning Browser but not SharpSnmpLib, single OID reads work (device-specific compatibility)
87+
88+
### #630 - HP Switch Firmware Download Status
89+
- **Status**: Needs tag
90+
- **Device**: HP switch
91+
- **Issue**: Firmware download status field issue
92+
- **Reason**: Device-specific behavior
93+
94+
## Issues Already Properly Tagged
95+
96+
The following issues already have the `area:faulty-device` label:
97+
98+
- **#291** - System.ArgumentException truncation error for 32-bit integer coding
99+
- **#318** - Small Bug with Cisco SNMP Trap Messages (Timeticks encoding)
100+
- **#474** - Constraining Request ID values (device truncates to 2 bytes)
101+
- **#608** - Trap listener error (malformed trap messages from device)
102+
- **#693** - Integer32 Truncation Exception (non-minimal BER encoding)
103+
- **#698** - Misleading exception with Eaton PDUs (incorrect username in Report-PDU)
104+
- **#700** - SNMP GetResponse with non-minimal INTEGER request-id
105+
106+
## Summary Statistics
107+
108+
- **Total imported issues reviewed**: 490
109+
- **Issues already tagged with area:faulty-device**: 7
110+
- **Issues that need area:faulty-device tag**: 12
111+
- **Total device-related issues**: 19
112+
113+
## Device Vendor Distribution
114+
115+
- **Cisco**: 3 issues (#101, #318, #436)
116+
- **HP**: 4 issues (#62, #420, #469, #630)
117+
- **Dell**: 2 issues (#83, #471)
118+
- **QNap**: 1 issue (#370)
119+
- **Citrix**: 1 issue (#475)
120+
- **MikroTik**: 1 issue (#89)
121+
- **Fortis**: 1 issue (#114)
122+
- **Eaton**: 1 issue (#698)
123+
- **Unknown/Generic**: 5 issues (#291, #474, #608, #693, #700)
124+
125+
## Recommendations
126+
127+
1. **Add the `area:faulty-device` label** to all 12 issues listed in the "Issues Requiring Label" section
128+
2. **Maintain this label** for device-specific compatibility issues to help:
129+
- Distinguish between library bugs and device non-compliance
130+
- Track which devices have known issues
131+
- Prioritize compatibility improvements
132+
- Document workarounds for specific devices
133+
134+
## Notes
135+
136+
- Issues were reviewed based on their descriptions, comments, and whether they mention specific devices or work in other SNMP tools
137+
- Some older issues may lack sufficient detail to make a definitive determination
138+
- Device-specific issues often require workarounds rather than fixes, as the device behavior cannot be changed

0 commit comments

Comments
 (0)