Changes in this release:

741: Allow empty modules in SMI parser

Modules without any assignments in them (which might happen if you create a module in MIB Smithy and save it before defining anything in it) can now be loaded by the SMI parser.

253: Documentation for database -logcommand setting

Documentation has been added for the SMI Database’s -logcommand setting, which allows user control over the formatting of compiler and parser messages.

851: XML version of SNMPv2-SMI errors about IMPORTS

Validating SNMPv2-SMI from XML format caused a false error regarding OBJECT-IDENTITY needing to be imported due to module version not being determined when there is no imports element.

848: Tables are not saved/restored from XML correctly

Single-identifier subtypes (as in the ‘SysORTable’ in ‘SEQUENCE OF SysORTable’) were being assigned by the XML parser to the wrong field, resulting in saved/restored XML files from failing validation on tables.

842: Importing of XML files fails with no error message

The XML parser did not previously support sending log messages through the SMI database’s logcommand, just logchannel. This resulted in error messages not being displayed in the “Tasks” list of MIB Smithy.

844: XML files fail to import with large integers

Due to an arithmetic error in the XML parser’s integer overflow checking, XML files could fail to import with sufficiently large integer values (e.g. in range elements).

914: Dropped notifications during bursts

Notifications could be dropped during bursts of many (or large) packets due to the default receive buffer size provided by the Windows TCP/IP stack. The SDK now requests up to a 1 MB buffer for the trap socket (on all platforms) to reduce the risk of packet loss.

255: MacOSX: tclsh aborts loading SDK without valid license key

With Tk built for Aqua, tclsh would terminate with SIGABRT when not logged in at the console when attempting to display the license dialog. The SDK now checks if Aqua or X11 environments are available to the session before attempting to load Tk.

882: Relaxed case restrictions on database queries

Although the SMI parser was able to handle illegal upper/lowercase first letters for record names, the validation for database queries was still strict. This caused “$db get -fulloid Foo” to succeed but “$db get -fulloid Foo.0″ to error regarding an invalid OID (which it is, but limited the usefulness of the parser’s handling of them).

912: SNMPv1 Trap-PDU encoding incorrect

The SNMPv1 Trap-PDU fields were being encoded in the wrong order when using the SDK to send SNMPv1 traps. Consequently, the SDK could not decode SNMPv1 traps sent to itself.

850: XML parser doesn’t check for equal min/max range values

Both the min and max attributes of the range element in the XML Schema are required, so single range values are generated as equal min and max. However, upon importing an XML file these values were not merged back into one, resulting in validation errors.

818: TRAP-TYPE’s REFERENCE field not preserved

The REFERENCE field of TRAP-TYPEs will no longer be lost when loading MIB modules.

817: Querying CREATION-REQUIRES returns only one element

Querying CREATION-REQUIRES property of a variation will now return all of the symbols listed, rather than only one.

254: snmplib format command documentation corrections

Docs for the snmplib format command were corrected to reflect the actual default format for enumerations (label only) and invalid “-format” argument in example 2.

308: -includes option missing from get capabilities

The documented -includes property for querying AGENT-CAPABILITIES statements was implemented only with the -mandatory-groups synonym, while both -includes and -mandatory-groups were supported for querying conformance modules and only -mandatory-groups was supported for querying MODULE-COMPLIANCE. Both ACs and MCs now support both synonyms.

• A “wrong # args” error could occur when previewing a single OBJECT-TYPE in SMI format (the error did not occur when previewing the whole module).

Changes affecting both MIB Smithy and MIB Smithy SDK:

• The “piberrors” type in the XML-SMI Schema document was not correct and did not match the implementation and has been corrected.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were on-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

• Paths to MIB/PIB files in MIB Smithy project files were previously stored as absolute paths. They are now stored as “relative to project file” paths to make it easier to put them under source control with the MIB/PIB files and check them out in other locations.

Miscellaneous Bug Fixes (MIB Smithy SDK)

• Enumeration comments were sometimes being lost, depending on where they appeared in relation to the enumerations.
• Newlines and excess whitespace were not always being properly collapsed in enumeration comments.
• Comments for the last assignment (such as an OBJECT-GROUP) in a module would wind up being associated with the module rather than (or in addition to) the assignment.

• The “format” subcommand, available to both database and session commands, can be used to format received SNMP data for display using the DISPLAY-HINT, if any, or customizable formats for enumerated INTEGER and OBJECT IDENTIFIER values. These default formats can be configured per-database. The command is available to the TNM “mib” compatibility interface as well.
• SNMP request variable bindings can now take enumerate names and name-and-number forms for enumerated INTEGER values to be included in the varbinds of the request. For example, you can now set a RowStatus object with the value “destroy” or “destroy(6)” in addition to just “6″.
• Added a native SNMP Session “walk” command for performing Get-Next walks of subtrees or entire agents more simply than doing so manually with the “next” command. As with individual requests, asynchronous and synchronous forms are supported, as are session configuration overrides.
• Numerous performance improvements were made, particularly for the SNMP layer’s interaction with its configured SMI database.
• The SMI Database “dump” command can now take an optional channel name to which output is to be sent.
• You can now get the current value for the SNMP Session’s -straps option using cget.
• The SNMP Session “configure” command can now handle an extra layer of [list] wrapping around its arguments so that one can avoid the overhead of eval and quickly clone sessions using “$session new [$session configure]“.

Miscellaneous Bug Fixes

• Received responses that don’t match pending requests are now just dropped, rather than triggering a background error. The background error would sometimes be triggered by cancelling an asynchronous request.
• A lone % at the end of the TNM-style request callback string could lead to a crash.
• The authKeyChange and privKeyChagne commands would crash if not given a salt using the -salt option.
• Errors from TNM-style asynchronous walk callbacks were providing the extra non-pertinent information the background error messages.

• Right-clicking on an implicit node in the Project tree would leave some menu items disabled the next time a real node’s popup menu was shown due to the menu being shown before being configured.
• A record/workspace tab mapping variable was not being properly unset upon renaming a record with the Apply button. This could result in an error when closing and re-opening that record’s workspace or the workspace not being opened for a newly created record of the same type.

Miscellaneous Bug Fixes (MIB Smithy SDK)

• A lone % at the end of the TNM-style request callback string could lead to a crash.
• authKeyChange and privKeyChange commands would crash if not given a salt using the -salt option.

• Added the ability to configure SNMP sessions during creation by including the configure options in the “snmplib new” command.

Bugs fixed in this release:

• SMI Database and SNMP Session commands now behave properly when renamed, including reflection in the “$db get” and “$session mpds” commands.
• Secondary databases and sessions now take the form “smi” and “snmp” rather than “smilib#” and “snmplib#”. Using the pointer value for the hexstring allows for uniqueness without having to scan the list every time a session or database is created.
• Changed error messages resulting from incorrect argument counts for commands to be of a somewhat more standard form. Also corrected some bugs in handling invalid arguments in some APIs.
• The SNMP session “wait” command was causing the process to use up to 99% of the CPU load and now yields to the system properly when there are no events.
• A missing break would cause incorrect results for Tnm snmp session’s “cget -transport” option. Added support for Tnm snmp session “cget -straps” option.
• Tnm snmp session’s “configure” command, when given no arguments in order to return all current settings, returned an unscaled value for timeout (the SDK uses milliseconds, Tnm uses seconds).
• snmplib bind without any arguments was returning the list of scripts for each bound event rather than the list of events that have scripts bound, as it should/is documented.
• Tnm “mib info access” and “mib info status” included the internal-only value “undefined” in results.
• The error given by Tnm “mib walk” with an unknown node name included the variable name in the error rather than the node name.
• The Tcl_Obj for the default SMI database log channel did not have its reference count incremented initially, which could potentially lead to a crash.
• The “snmplib mpds” and “snmp info” commands, which return lists of known SDK native and Tnm compatible SNMP sessions will now only return those sessions of the appropriate type. e.g., “snmplib mpds” will no longer list sessions created with the Tnm “snmp generator” command.
• The snmpTrapOID parameter of the Tnm trap interface was not being included in the variable bindings for the trap.

• Opening the README.RTF and LICENSE.RTF files from the Help menu would result in an error under Windows, as MS Word didn’t recognize the %20’s for spaces.
• The Window|Maximize command did not restore a previously maximized window to normal under Mac OS X. It would do so momentarily, and then return to the maximized (zoomed) state.
• The Aqua “Window” menu could show a “menu” item where the list of open windows were shown that should not be there.
• A focus race condition in the popup calendar used for timestamps in MODULE-IDENTITY’s LAST-UPDATED and REVISIONS fields could lead to a hang, at least under Windows.

Miscellaneous Bug Fixes (MIB Smithy SDK)

• When receiving traps under Unix with the nmtrapd/straps daemon, MIB Smithy could become partially hung by a short read condition until another trap was received.
• Added missing “-straps” option to the “$session cget” command. This option returns the current value for the -straps option, which allows disabling use of the nmtrapd/straps daemon under Unix.

• A stale Tcl_Obj could lead to a hang or crash when sending SNMP requests with varbinds that include syntax, where the syntax (as provided) is a non-base type.
• Querying properties on an object using a symbolic name plus subidentifier, when the object has variations defined, could lead to an infinite loop.
• A crash could occur on exit when database or session commands were invoked in a callback called after the exit started, such as in the handler for a toplevel window.