Hi Team,
■ Inquiry Details
We have received a report from an end-user stating that while they can compile the attached MIB file using the MIB tool in Spectrum, the file is not being read correctly.
We would like to clarify the following two points:
[Point 1]
The user reported that the text in the DESCRIPTION field appears garbled (character encoding issues).
Since MIB files containing multi-byte characters in the DESCRIPTION field are non-compliant with RFC standards, is it correct to assume that Spectrum does not support them? Specifically, is our understanding correct that Spectrum is not designed to load MIB files that include multi-byte strings?
[Point 2]
After removing the multi-byte characters from the DESCRIPTION and attempting to load the MIB file again, it appears that the TRAP-TYPE definitions failed to load.
However, after modifying the TRAP-TYPE definitions and changing the display names as shown below, the file was successfully loaded:
TimeStamp → newTrap1
DeviceID → newTrap2
MessageID → newTrap3
Is it correct to understand that the strings "TimeStamp," "DeviceID," and "MessageID" are reserved words within Spectrum?
We searched the Spectrum documentation for these strings, but they are not listed as reserved words.
Is this a documented limitation, or are these names conflicting with pre-installed standard MIBs (e.g., RFC-defined objects) within Spectrum?"
Regards,