Problem
We receive from our NetApps traps these contain filenames in UTF-8 format, if these contain umlauts, then the strings are displayed in HEX instead of string format.
If the trap string contains only the elements equal in simple to ASCII, the conversion is done without any problems.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
SNMPv2-MIB::sysUpTime.0: 1800758647, NETAPP-MIB::productTrapData.0: Possible virus detected. Vserver: DATAPORT_002_HH_NOR_B, vscan server IP: 192.62.100.7, file path: \ABC_002_HH_VOL3\ABC_002_HH_XYZ\ABC\TEST\intern\V_07_Tools\PDFCreator\PDFCreator-1_7_1_setup.exe, client IP: 0.0.0.0, SID: S-1-5-21-2000478354-764733703-1177238915-529645, vscan engine status: 222200008, vscan engine result string: The file was threatened and was successfully deleted.., NETAPP-MIB::productSerialNum.0: 1-80-1235404 |
Solution
In a nutshell: The MIB is wrong, so either request a correct one from the manufacturer or build one yourself or patch the existing one. Annoying, but unfortunately this happens more often...
...
If the device can send really long UTF-8 strings at this point, then there must be no "DisplayString" in the MIB, but something with a TEXTUAL-CONVENTION containing a DISPLAY-HINT of e.g. "65535t".
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...