Blog

MIB Smithy 4.7.3, MIB Smithy SDK 4.6.6, and MIB Views 2.0.3 are now available for download. These releases include the following changes/fixes:

7065: SNMPv3 “reportable” flag incorrectly set in reports/responses

The “reportable” field in SNMPv3 msgFlags was incorrectly set when sending reports or responses, which would result in inability to handle inform requests with some agents.

8050: Enumeration as textual convention and table index

MIB validation could report false warnings about possible negative values when using an enumerated TEXTUAL-CONVENTION for the SYNTAX of an object used as a table INDEX. It would also fail to report errors in similar circumstances where negative enumerations are actually defined.

6797: Tnm notifier session default port should be 162 [SDK Only]

When creating sessions using [Tnm::snmp notifier], the default target port is now 162 (the normal target port for SNMP notifications) rather than 161 (the normal target port for SNMP requests).

6808: No callback for timed out Tnm requests [SDK Only]

When using the Tnm interface, SNMP requests (other than walk) using callbacks will now invoke the callback when the request times out or fails for some other reason, with appropriate parameters so the callback can detect the condition.

5108: Individual record preview should show comments [MIB Smithy]

When previewing ASN.1 format, a record’s comments property was typically only included in the preview text when previewing a whole module. The record’s comments are now included when previewing the individual record.

8055: Table View: clarification for non-table OIDs in entry [MIB Smithy, MIB Views only]

When a non-table OID is entered in the Table View’s search entry, it will generate a meaningful message to the user informing them so instead of an SDK API error message.

7319: Window -> Close command causes “wrong # args” error [MIB Smithy only]

A “wrong # args” error could occur when selecting the Window -> Close menu command and has been fixed.

6075: Existing MODULE-IDENTITY should select on create request [MIB Smithy only]

When attempting to create a MODULE-IDENTITY when one already exists, and the editor for the existing one is opened, the existing one will be selected instead of creating a new one. Only one MODULE-IDENTITY is allowed/required per module.

MIB Smithy 4.7.2 and MIB Smithy SDK 4.6.5 are now available for download. These releases include the following changes/fixes:

6601: Return id for wait/cancel when sending traps with delay [SDK]

The [$session trap] command will now return a unique ID, as is done with async requests, allowing the [$session wait] command to be used to wait (specifically) for the trap to be sent when transmission is delayed.

6602: Send messages immediately if no delay/window wait required [SDK]

Based on user feedback, the behavior introduced in SDK 4.6.4 whereby trap and async request APIs always return immediately (before transmission) has been changed to only return before transmission if the it would be delayed. The messaging APIs will service the Tcl event queue prior to returning, until the message is sent -OR- no more immediately serviceable events remain in the queue.

This restores prior API behavior when -delay and -window options are not in use, while preserving the intended fixes for CPU load and handling such delays asynchronously.

6600: Can’t specify SNMPv3 priv password for snmptrapd CLI tool/script

When the snmptrapd CLI tool/sample script was enhanced to allow specifying SNMPv3 auth/priv parameters, the options added were consistent with the other CLI tools/scripts. Unfortunately the -p option was already in use for specifying listener port, resulting in an error when trying to specify privacy protocol.

The option for specifying listener port has been changed from -p to -b to resolve the conflict. Additionally, -B can be used to specify listener address/interface (normally it will listen on all interfaces), and -s to disable use of straps/nmtrapd on Unix.

6620: sysUpTime not included in trap varbinds with Tnm interface

When using the Tnm compatibility interface to send SNMPv2c/v3 traps, sysUpTime was not being included in the sent trap’s varbinds.

MIB Smithy 4.7.1, MIB Smithy SDK 4.6.4, and MIB Views 2.0.2 are now available for download and provide fixes for several bugs. These are mostly fixes in the SDK, which are incorporated into MIB Smithy and MIB Views as well. Issues/changes applicable only to certain products are noted in [brackets].

Changes in these releases:

6515: Help not displayed when using kfmclient [MIB Smithy, MIB Views only]

A missing openURL argument to kfmclient would prevent online help from showing when using the KDE window manager on Unix platforms.

6470: SNMPv3 messages not being sent with privacy

An error in the fix for #5951 in MIB Smithy SDK 4.6.2, which was intended to prevent sending SNMPv3 messages with privacy but without authentication, could prevent messages from being sent with privacy enabled at all.

6468: High CPU utilization when waiting for responses

Handling of delays and waits for pending SNMP requests has been changed to make much better use of the Tcl event queue and timer callbacks in order to prevent high CPU utilization during such times when it should otherwise be doing nothing.

[SDK NOTE: Asynchronous SNMP requests are now queued for transmission via callback from the event queue rather than being sent before API return. Previously, using the -delay option to delay transmission would result in the API not returning until the delay was finished (up to 5 minutes), even with an async request.]

6516: IPv6 messages not being sent on Windows

SNMP messages were not being sent to IPv6 targets on Windows due to using getsockname() with a structure of insufficient size for IPv6 results on that platform. The call would fail, the SDK would be unable to match the target address family with an available socket, so the message would not be sent.

6548: Receiving SNMPv3 auth/priv traps without Engine ID discovery

If the Engine ID in a received SNMPv3 message doesn’t match the configured or discovered local or remote Engine ID for a session, but the user name matches, the session now localizes keys (if configured) to the message’s Engine ID for purposes of authentication/privacy for that message. This allows SNMPv3 auth/priv traps to be received from any source with the same user name and passwords/unlocalized keys, rather than requiring Engine ID discovery first.

6500: Delayed send not accounted for in time window [SDK Only]

When using the -delay and/or -window options for delayed/limited transmission of SNMPv3 messages, USM processing now happens just prior to actual transmission rather than before delay so the time window reflects the time sent, not the request time. Otherwise, a sufficiently long delay would provoke a usmStatsNotInTimeWindows report from the agent.

6504: Cancel pending requests on configuration change [SDK Only]

An SNMP session’s pending requests are now cancelled when session configuration is changed to prevent sending requests to the incorrect target or with incorrect parameters.

6478: Crash when destroying session during callback [SDK Only]

SNMP session and MIB database instances are now reference counted like all other data so that they are only garbage collected when there are no more references. Previously they were GC’ed immediately when destroyed, which could cause a crash if for some reason they were destroyed in a callback.

UPDATE: Solaris builds were delayed due to hardware failure. Replacement parts arrived on Monday and I was able to get the SPARC machine back online. Solaris builds for the above releases are now available.

MIB Smithy SDK 4.6.3 is now available for download. This release fixes a crash/unhandled exception that could occur due to an iterator being used after being invalidated during updates to the internal OID index (such as when importing MIBs). The issue was likely introduced in the 4.6 release as part of the changes made to give each MIB database its own orphans tree.

MIB Smithy SDK 4.6.2 is now available for download. This release fixes two issues introduced in the 4.6 release, and one other minor issue that’s been around for a while was only recently noticed while working on the MIB Views release under OSX.

In recognition of the unreasonable length of time between the 4.5 and 4.6 releases, and the expectation of periodic updates during the support period, I’m making this release available to all customers whose support period was due to expire after October 1, 2012 (if your support was due to expire after that date, but before December 31, 2013, you will find that your support period has been extended to December 31, 2013).

I meant to do this with the 4.6 release, but have been highly focused on getting the other product builds out as well, and similar arrangements will be made for those users.

Changes in this release:

5935: Host IDs not displaying correctly

Host IDs were not displaying correctly in the license message/dialog due to a change in the 4.6 release. The issue only affected formatting for display.

5951: SNMPv3 privacy without authentication regression

A bug was introduced during refactoring for the 4.6 release making it was possible to send SNMPv3 messages with the privacy flag set (and encrypted) but without the authentication flag set or authentication done, which is illegal.

5957: Incomplete cleanup on session closure

The Tcl channels associated with SNMP session sockets were not cleaned up properly upon session closure, which could result in a thread deadlock at application exit time.