Blog

• Improved handling of scroll buttons in tabbed notebooks (that are displayed when there are too many pages to fit into the width of the notebook).
• Corrected no such variable “oid” error that could occur when generating generating AGENT-CAPABILITIES in SMIv2 format, “xmlrequires” in XML format.
• Corrected ‘can’t read “syntax”: no such variable’ error that could occur when previewing as XML.
• Fixed a no such variable error that could occur with notebooks containing all hidden pages (as might happen hiding the Preview page with no other workspace pages open)
• Workaround for buggy third-party combobox that doesn’t show any indication of focus when it’s not editable.
• Corrected typos and minor bugs with XML-SMI-2.0.xsd where it was inconsistent with the implementation.
• Trap Watch tool was not re-establishing the port binding and notification handler, preventing received traps from continuing to be displayed, after the tool was closed and reopened.

As of today, we are pleased to announce a new rate schedule for volume discount end-user licensing that we hope will allow users to take advantage if discounts sooner and save even more in the long run.

The previous schedule was set up for a 15% reduction in price after each tier of 5 licenses, up to a maximum of a 45%. This meant that no discount was available until the 6th license, which would be at 15% discount, and the next rate at the 11th license at 30% discount. Overall, a savings of $2,686.50 for 16 licenses in the case of MIB Smithy Professional.

The new schedule is set up for a 10% reduction in price after each tier of 2 licenses, up to a maximum of a 45%. This means that the 3rd license is available at at 10% discount, and the next discount is at the 5th license for a 20% discount. Overall, a savings of $4,676.50 for 16 licenses in the case of MIB Smithy Professional.

We hope that these new rates provide more accessibility for small to medium sized organizations, and an even greater cost benefit for larger organizations.

Enjoy!

Version 2.2 of MIB Smithy is a minor update expanding on earlier improvements in version 2.1. Further optimizations have been made to make loading MIB files up to 43% faster, and several bugs have been fixed thanks to lots of user feedback.

Significant Changes (MIB Smithy)

• Variations and groups within conformance statements no longer show an expand/collapse icon in the project tree.

Miscellaneous Bug Fixes (MIB Smithy)

• Due to recent API changes, the SEQUENCE OF type was not allowing subtype to be specified through the GUI.
• The LAST-UPDATED value that is automatically assigned to new MODULE-IDENTITY
• statements by the workspace, if none has been specified when the new record is committed, was adding two extra digits.
• GUI workspace for variations now properly allows commits with an empty syntax or write-syntax to indicate that the field should not be generated in the output.
• The Recent Files list was not handling filenames with spaces properly, and instead treating them as multiple files in the list.
• The Variation workspace was not checking the parent record type properly at startup, which prevented the tabs for the DEFVAL and CREATION-REQUIRES fields from being displayed.
• Corrected workspace validation for combobox properties that could previously result in dialogs indicating the value was invalid when it was in fact valid, due to a bug introduced in version 2.1.

Significant Changes (MIB Smithy SDK)

• The default syntax for type definitions is now Integer32, as with objects, rather than “undefined”.
• Improved checking for duplicate record names within the same container where it was possible for some to still slip through (e.g. two modules with the same name in the same file), as well as speed in checking for such duplicates. Benchmarks have shown about a 43% speed improvement in loading approximately 230 MIB files together into a single database.
• Variation -syntax/-write-syntax etc. properties, and the -asn1type property for objects and type definitions, now return an empty string instead of “undefined” when there is no such type information available. POTENTIAL INCOMPATIBILITY
• Implemented changes for multiple-interpreter compatibility. Each interpreter now has its own master smilib/snmplib database/session.

Miscellaneous Bug Fixes (MIB Smithy SDK)

• Incorrect arguments for some LAST-UPDATED and REVISION timestamp checking errors would result in an uninformative error message, or potentially a crash.
• Callback arguments for SNMPv3 header data were providing empty strings rather than the actual parsed values due to a source merge conflict.
• Corrected a Windows build issue that resulted in the root nodes (ccitt, iso, joint-ccitt) not being properly initialized into the new 2.1 name index, which could result in misleading dependency warnings or problems with the SNMP Tools.

Version 2.1 of MIB Smithy is a minor update with a small number of major improvements. A new Trap Watch tool has been added for monitoring incoming traps and notifications, expanding the set of built-in SNMP management tools added in version 2.0. Some optimizations to core indexing and search algorithms have been made that yield huge performance gains in loading and compiling many modules. The performance gains are minor for typical small projects with only a small hand-full of modules, but reach over 95% when about 200 modules are loaded into a single project/database. Performance is less dependent upon number of records and more dependent on record name length than earlier versions. Several bugs (mostly minor) have also been fixed.

Signficiant Changes (MIB Smithy)

• The “Files” tree in the project panel now includes .my, .mi2, .txt and (in professional) .xml files in addition to the .mib files that were shown previously.
• Evaluation version limits have been increased to 5 modules per project.
• Added new Trap Watch tool for monitoring incoming traps and notifications.
• SNMP Table View tool now shows additional columns for data extracted from instance subidentifiers corresponding to each of the table indexes.

Miscellaneous Bug Fixes (MIB Smithy)

• OBJECT-TYPE output for normal SMI format was omitting the AUGMENTS field.
• MOSY output was not including INDEX or AUGMENTS information.
• Numerous minor/random Tcl error corrections that could occur in various more obscure features due to some incomplete conversions to new calling conventions (mostly issues introduced in 2.0).
• Corrected a potential divide by zero error if no variables are returned in SNMP Walk.
• Corrected some extraneous output in XML output generation around compliance group comments.

Signficiant Changes (MIB Smithy SDK)

• Errors that occur in SNMP request callbacks and other event processing now trigger a background error in Tcl rather than being ignored or printed to stdout.
• Added -includes synonym for querying conformance module properties.
• Added -indexdecl/-augmentsdecl options for OBJECT-TYPE records. These options return the “as-declared” INDEX/AUGMENTS fields for the record, while the existing options (-index/-augments) now check the record above and below so that, for example, -index returns sysORIndex for both sysORTable, sysOREntry and each column, while -indexdecl returns sysORIndex only for sysOREntry.
• Added -syntaxdecl property for SMI database ‘set’ operations for objects, typedefs and variations that allow all syntax information to be specified as a single property, as returned by the ‘get’ property of the same name. Variations also add a ‘-write-syntaxdecl’ property to serve the same purpose for WRITE-SYNTAX.
• The default SMI Database log channel is now “stderr” instead of “stdout” for the benefit of conversion scripts designed to send their results to stdout for command line redirects and pipes. Also, logging can now be disabled by configuring the database’s log channel to an empty string (if, for example, all that is desired during validation is a pass/fail result).
• The SNMP session “bulk” subcommand (for sending get-bulk requests) now sends a get-next request instead if the SNMP version being used to send the message is SNMPv1. Superfluous variable bindings (i.e., those that are repeaters according to non-repeaters when max-repetitions is 0) are discarded from the request.
• The get-bulk request’s default non-repeaters/max-repetitions values for are now 0/1 instead of 0/0. The former defaults normally result in an empty response.
• A new indexing scheme and search algorithm for name-based lookups has been implemented that should provide a very large speed improvement for individual databases containing a very large quantity of records.
• The SMI Database’s “log” command now by default adds a newline to the end of the message. Like Tcl’s “puts” command, it may take an optional “-nonewline” argument to suppress the newline.
• Added “-container” query property to all record types, which returns the fully qualified name of the record in which the queried record is contained. This property functions the same as the “-fullname” property except that the name of the queried record is excluded from the result. That is, supposing -fullname returns @File5!SNMPv2-MIB!sysDescr, -container returns only @File5!SNMPv2-MIB.
• Additional internal optimizations which, together with the new name indexing optimizations, yield a greater than 95% performance increase for MIB file loading and validation for large numbers of MIB modules (e.g. hundreds in a single database) where performance could really bottom out previously.
• Added SNMP Session “inform” and “trap” subcommands for sending inform requests and SNMPv1/v2 trap messages.
• Added “oidcmp” SMI Database subcommand for doing OID comparisons, with -limit and -subtree options for controlling the number of subidentifiers compared.
• Added “-indexparts” OBJECT-TYPE query property for parsing column instance subidentifiers into individual elements for each index.
• Added “-localport” SNMP Session option for configuring a port (default 162) for receiving notifications on if a handler is configured. Added “bind” subcommand for configuring handlers for incoming notifications.
• Variable bindings encoding values of type OBJECT IDENTIFIER now accept identifiers, relative OIDs and other forms of OIDs for the value in addition to absolute OIDs.
• Receive errors from the socket now include an error number and, on Unix, an error message to allow for easier problem resolution.

Miscellaneous Bug Fixes (MIB Smithy SDK)

• Version 1.6 changes for suppressing duplicate error/warning messages were not fully merged into version 2.0, so duplicates messages could again appear. This has been corrected.
• There was some inconsistent use of ‘.’ versus ‘:’ in module.descriptor forms for type/value references expected during record modifications versus returned by queries. They should constantly use ‘:’ as the separator now.
• A recent change in supporting multiple synonyms for setting the OID value of objects resulted in a bug that could cause the internal OID tree/index to not be updated.
• A crash could occur when querying the -asn1type (base type) property for an object with a derived-type syntax when the referenced type has not been defined or loaded.
• Some record types were allowing invalid (for that record type) STATUS values to be set (though this would be caught during validation).
• Bug fixes for multiple-interpreter compatibility. A master database and session (smilib and snmplib) are now created in each interpreter that the package is loaded into.
• Enumeration comments that begin after the enumeration but still on the same line should now be associated with the correct enumeration, rather than being associated with the following enumeration.
• An error could occur when sending set requests without a type in the variable bindings indicating “-basetype” as an unknown option (which should be “-asn1type”).
• Corrected a couple of potential memory corruption and leak issues.
• The MSG_SYNTAX_SMIONLY compiler warning could previously result in either a garbage type name being printed or potentially a crash.
• Clarified MSG_ROW_TYPENAME compiler warning, which was giving somewhat ambiguous row/type references.
• Corrected byte ordering issues in IpAddress formatting for callbacks.

Muonics added SNMP management-role (request originator) capabilities to its MIB Smithy series of products starting with version 2.0. Notification (trap/inform) processing was added in version 2.1 (the current version as of this report). Neither version supports agent-role (request processor) capabilities at this time. However, all PDU types are fully parsed by both versions, including requests, before unsupported PDU types are discarded by the dispatcher layer.

Both versions of MIB Smithy SDK, from which all of the MIB Smithy series are derived, have been fully tested with all four of the PROTOS c06-SNMPv1 Test Suites. Version 2.0 binds to any available port for sending requests and receiving responses. Since this was not conducive to testing, a special build was required, with the only difference from the official 2.0 release being a hard-coded binding to ports 161 and 162 as appropriate. Version 2.1 allows configuration of a bind port for receiving notifications, so it was not an issue for that version.

After running the full series of tests we found both versions to behave as expected, with no signs of failure. We have thus concluded that Muonics’ past and current product versions are not susceptible to the security vulnerabilities associated with CA-2002-03.

VU#107186 – Not Vulnerable
VU#854306 – Not Vulnerable