MIB Smithy SDK

Software Screenshot:
MIB Smithy SDK
Software Details:
Version: 4.7
Upload Date: 18 Feb 15
Developer: Muonics
Distribution Type: Shareware
Price: 349.00 $
Downloads: 9

Rating: nan/5 (Total Votes: 0)

MIB Smithy SDK project is a commercial and dynamic Tcl/Tk extension for developing your own SMI conversion tools and SNMP management scripts.

MIB Smithy SDK includes built-in MIB validation and XML Import support.

What is new in this release:

  • 5876: Set up file associations at install time:
  • MIB Smithy file associations are now registered by the installer, rather than by the application itself, so that Windows can properly manage removal of the associations at uninstall time.
  • 381: Use XML format for project files:
  • MIB Smithy project files are now stored in XML rather than INI format to allow for future features with more complex configurations. When opening an old format (.mip) project file you will be prompted to save to a new (.smproj) file and the project will be converted to the new format.
  • 5720: Reordering notification objects:
  • Reordering commands (Move Up/Move Down) were added to the Objects property for Notification workspaces. As the ordering of the objects affects the on-the-wire encoding of the notifications, they can't be arbitrarily reordered by MIB Smithy the way e.g. group members can, but using the "Select" button tended to put them in alphabetical order.
  • 5127: Change preferences file format to XML:
  • MIB Smithy application preferences are now stored in XML rather than INI format to allow for future features with more complex preferences. Existing preferences will be converted automatically.
  • 5114: Use DOM to generate XML:
  • MIB Smithy now uses an actual DOM implementation to build its XML output format for MIBs (and preferences, project files, etc), rather than rudimentary text operations. This is less prone to introducing malformed XML and may allow for future operations on the DOM document.
  • 5878: Windows: Prefer Application Data folder over Registry for preferences:
  • MIB Smithy will no longer save application preferences to the Windows Registry except as a fallback if it can't save elsewhere. Instead, preferences are saved to the user's Application Data folder. Existing preferences will be imported, and user given the option to remove or preserve the old registry entries.
  • 5932: "Error in custom build script" during MOSY build:
  • Spaces in output directory names were not handled properly when compiling to MOSY format, resulting in an "error in custom build script" message.
  • 5767: Improve Unsigned32/Gauge32 conversion to derived types:
  • SNMP tools will better handle converting Unsigned32 and Gauge32, which have the same on-the-wire encoding, to the proper syntax for display purposes provided appropriate MIBs are loaded.
  • 5781: Missing REFERENCE property pages:
  • The MODULE-COMPLIANCE and AGENT-CAPABILITIES workspaces were missing tabs to allow editing of those macros' REFERENCE properties.
  • 5115: XML-SMI schema corrections:
  • Minor corrections were made to the XML-SMI schema to make the RangeSubspec and Enumeration definitions legal XSD syntax.
  • 5128: Changing module for imported symbol should not add new import:
  • Editing the module name for an existing symbol in the IMPORTS list will now actually change which module it is imported from, rather than causing the symbol to be imported from both modules (unless the "Add" button is used rather than "Modify").
  • 2121: Add support for pre-localized and unlocalized keys:
  • SNMP tool sessions can now be configured directly with unlocalized or localized auth/priv keys, rather than requiring passwords and letting the session manage conversion to keys and key localization.
  • 5801: Add options to CLI tools to specify keys rather than passwords:
  • The bundled CLI tools/sample scripts now have options for specifying SNMPv3 auth/priv keys directly (localized or unlocalized), rather than only allowing passwords to be specified.
  • 2277: Give validator messages unique IDs:
  • All parser and validator messages have been moved to a message table with unique IDs, which are provided in messages printed to the configured log channel and in arguments to the configured log command. The actual IDs are still subject to change with reorganization, but this allows one to (for example) implement filters to effectively disable messages that aren't desired.
  • 1839: ASN.1 Type Assignment with type BITS:
  • An error is now generated at parse time when attempting to use ASN.1 Type Assignment notation (Name ::= Type) with the "BITS" construct (which is not allowed in this form), rather than just quietly correcting it.
  • 5397: XML-SMI XSD: use xsd:token type where appropriate:
  • The XML-SMI Schema was changed to use "xsd:token" rather than "xsd:string" for some types where appropriate. Semantically the schema is unchanged by this as "xsd:token" is a subset of "xsd:string", but "xsd:token" more closely matches the (existing) value restrictions.
  • 1870: Add support for MODULE-CONFORMANCE (RFC-1303):
  • Support was added for parsing, editing, and validating the MODULE-CONFORMANCE construct from RFC 1303 (the SMIv1 predecessor to SMIv2's AGENT-CAPABILITIES). The XML-SMI Schema was also updated to add support.
  • 6065: Add support for MIB Views agent files:
  • Added support for using MIB Views agent files with the MIB Smithy SNMP tools to save and restore SNMP agent settings to/from files.
  • 5809: Remember SNMPv3 Trap Watch configuration:
  • SNMPv3 Trap Watch tool configuration (port, SNMPv3 user name, keys, etc.) is now stored in the user's preferences file and remembered between runs.
  • 5954: Improve GUI responsiveness during walk:
  • The SNMP Walk tool could appear to update in bursts if more CPU time was spent processing messages than allowing for GUI updates. It will now ensure the GUI updates when entries are added to the result table.
  • 5953: Bad option "-fulloid" error in MIB Browser:
  • A ‘Bad option "-fulloid"‘ error could occur in the MIB Browser due to changes introduced in version 4.6 to better handle ambiguous MIB definitions.

What is new in version 4.6.2:

  • Minor bugs were fixed.

What is new in version 4.6:

  • MIB parser/validator messages were clarified, and all messages now have unique IDs associated with the rules that produce them (for filtering support).
  • Support for specifying SNMPv3 keys (unlocalized or pre-localized) for session use, rather than passwords, was added.
  • Support for MODULE-CONFORMANCE (RFC 1303) was added.
  • Minor bugs were fixed.

What is new in version 4.5:

  • Support for decoding KeyChange values was added.
  • New features were added for simplifying OID comparison operations, SNMP session and request configuration, MIB loading, and friendlier formatting of TimeTicks values.
  • Improvements were made to the wrapper providing Scotty compatibility.
  • Minor bugs were fixed.

What is new in version 4.4:

  • This version supports receiving SNMPv3 auth/priv informs and specifying contextName and contextEngineID in SNMPv3 messages.
  • The ability to restrict listening for traps to a specific interface (rather than all interfaces) has been added.
  • Binaries for Mac OS X are now PPC+x86 instead of PPC-only.

What is new in version 4.3:

  • A generic "Invalid OBJECT IDENTIFIER" was given when trying to issue an SNMP request with a symbolic OID that couldn't be fully resolved. It will now instead give an "Unable to resolve OID" error that indicates which parent couldn't be resolved and likely reason.
  • New [smilib scan] and [snmplib scan] commands were added to invert display formatting (i.e., opposite of [smilib format]) where possible. The Scotty/TNM compatibility interface also now supports the Tnm::mib scan command.
  • Scotty/TNM compability now includes the "mib pack" and "mib unpack" commands. (However, OCTET STRINGS remain in binary form; they are not converted to hex as Scotty does).
  • The generic "record search string is ambiguous" error is replaced with an error indicating which string is ambiguous, along with a list of non-ambiguous matches.
  • A new validation rule was added to check that the OBJECT-TYPEs listed in a NOTIFICATION-TYPE or TRAP-TYPE have a valid syntax (i.e., no tables/rows).
  • SNMP sessions using the Scotty/TNM compatibility interface now support -logchannel option of the SDK's native APIs for writing packet traces to a specified channel.
  • A new -logcommand option was added to SNMP sessions as an alternate to -logchannel, which allows packet logging to be done through a callback function.
  • The starting request-id and message-id for an SNMP session is now random, rather than starting at 0 for each session.
  • The Scotty/TNM compatibility interface for SNMP sessions now supports the -delay and -window options for waiting before sending messages and limiting the number of pending requests (rather than being silently ignored options), and are also supported by the SDK's native sessions.
  • Changes have been made to the use of random numbers (e.g. for SNMPv3 authentication/privacy salts) to make them more random.
  • The [smilib format] command will no longer apply DISPLAY-HINT formatting when the syntax given is NULL, to prevent formatting exceptions such as endOfMibView.
  • Implicit subnodes (i.e., OIDs that have no record defined for them but which are parents of other records) are once again included in the [smilib get -subnodes] result.
  • The format for specifying the address and port with the included sample CLI scripts has been changed from address[:port] to address[#port] (e.g. 127.0.0.1#161) to accommodate colon-delimited IPv6 addresses.
  • The Add/Remove Programs icon for the Redistributable SDK is now the same as the regular SDK.
  • When matching SNMPv3 reports to pending requests, only the message-id will be used instead of also matching the request-id. SNMPv3 allows for the possibility that the security model may trigger a report to be sent back by an agent to a manager without the request PDU being parsed, which would cause the request to time out rather than processing the report.
  • When SNMPv3 requests time out, they will no longer be sent with the same engineBoots/engineTime values when resent; instead the time window will be updated and the message re-encoded (and re-encrypted/authenticated if applicable).
  • When a module name referenced by MODULE-COMPLIANCE or AGENT-CAPABILITIES is ambiguous, the validator message incorrectly indicated that it was an IMPORTS module reference that was ambiguous.

Similar Software

JCAM Engine
JCAM Engine

3 Jun 15

scrap2rtf
scrap2rtf

20 Feb 15

Pilot-QOF
Pilot-QOF

11 May 15

MoinMoin
MoinMoin

20 Feb 15

Other Software of Developer Muonics

MIB Views
MIB Views

18 Feb 15

Comments to MIB Smithy SDK

Comments not found
Add Comment
Turn on images!