MIB Smithy 3.0 and SDK 3.0 Release
MIB Smithy 3.0 is a new major release containing a number of important new features, including support for designing, editing and validating PIB (Policy Information Base) modules for the COPS (Common Open Policy Service) protocol. Also included are new output and preview formats and GUI improvements for speed in various tables, lists and trees as well as sorting. Usability improvements various SNMP tools have also been made, and a new “mibinfo” command line tool for querying properties of MIB/PIB modules was added. Continue reading MIB Smithy 3.0 and SDK 3.0 Release
MIB Smithy 2.4.11 and SDK 2.4.11 Release
A small number of error and warning messages had invalid argument counts or format codes, which could lead to a crash. These have been corrected with measures taken to make sure they are caught in the future.
MIB Smithy 2.4.10 Release
The correction to -syntaxdecl/-write-syntaxdecl API output in MIB Smithy SDK 2.4.9 introduced a bug in MIB Smithy whereby an error would be produced when attempting to generate XML or SMI output for variations without SYNTAX/WRITE-SYNTAX fields.
MIB Smithy 2.4.9 and SDK 2.4.9 Release
Bug Fixes (MIB Smithy)
- An error could occur when copying a variation record due the above in addition to an incorrect option being specified.
- XML output was not being encoded in UTF-8, which (due to the lack of encoding specification in the header) could render the output invalid if non-UTF-8 characters were in comments. The output is now encoded in UTF-8 and UTF-8 is specified as the encoding in the header (just in case, since it is the default).
Bug Fixes (MIB Smithy SDK)
- Setting a variation’s WRITE-SYNTAX property (-write-syntax) was taking its value from the -syntax option instead, deleting it if -syntax wasn’t specified.
- Querying a variation’s -syntaxdecl or -write-syntaxdecl properties, when none was configured, would return ‘syntax “”‘ rather than an empty string as specified in the documentation.
MIB Smithy 2.4.8 and SDK 2.4.8 Release
The SDK’s “smilib get -indexparts” OID parser was sometimes returning corrupted information for OCTET STRING indexes in converting to hex. The problem is fixed in this patch release.