MIB Smithy 4.0.2 and SDK 3.4.1 Release
September 23rd, 2006 by Muonics, Inc.
New Features (MIB Smithy)
- 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.
MIB Smithy SDK 3.4 Release
November 28th, 2005 by Muonics, Inc.
New Features
- 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.
MIB Smithy 3.3.7 and SDK 3.3.7 Release
October 15th, 2005 by Muonics, Inc.
Miscellaneous Bug Fixes (MIB Smithy)
- 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.
MIB Smithy SDK 3.3.6 Release
September 18th, 2005 by Muonics, Inc.
Several memory leaks and issues with returning session and database names that were introduced by the 3.3.5 changes were fixed in this patch release for MIB Smithy SDK.
MIB Smithy SDK 3.3.5 Release
September 12th, 2005 by Muonics, Inc.
New Features
- 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.