1735: INDEX and AUGMENTS forbidden with RFC1155-SMI, RFC1065-SMI

It is now an error, rather than a warning, for an OBJECT-TYPE to have an INDEX or AUGMENTS clause when imported from RFC1065-SMI or RFC1155-SMI.

1760: TEXTUAL-CONVENTIONs must not derive from other TEXTUAL-CONVENTIONs

It is now an error, rather than a warning, for SMIv2 modules to define TEXTUAL-CONVENTIONs derived from other TEXTUAL-CONVENTIONs. This is also now an error for COPS-PR-SPPI modules, which previously gave no warning.

1747: Additional validation for variant access levels

PIB-MIN-ACCESS is now checked to ensure its values are allowed by COPS-PR-SPPI. MODULE-COMPLIANCE’s PIB-MIN-ACCESS and MIN-ACCESS, and AGENT-CAPABILITIES ACCESS, are now checked to ensure their values are within bounds of the referenced object’s (or PRC’s) MAX-ACCESS or ACCESS value.

1761: Improved version-specific validation with missing IMPORTS

Previously, when a macro (such as OBJECT-TYPE) was not imported as required, certain version-specific validation checks (such as allowed STATUS values) were suppressed, giving only an error about the missing import. Now, the version may be assumed based on other imports that are present, allowing further checks to be performed.

1733: Suppress bit zero warning when no bits are defined

A redundant warning regarding starting BITS at zero when also erroring about needing at least one bit to be defined.

1738: Clarify access keywords in error messages

Validator messages should use the proper access keyword (ACCESS, MAX-ACCESS, PIB-ACCESS, MIN-ACCESS, PIB-MIN-ACCESS) depending on the record type and version (SMIv1, SMIv2, COPS-PR-SPPI) of the record. In some cases, they simply said “ACCESS”.

1701: False errors and changes to BITS DEFVAL validation

The algorithm for checking set bits in hex/binary DEFVALs versus BITS named bit values was not correct, leading to errors for valid DEFVALs. Also, an integer is no longer allowed for DEFVAL with BITS type, and undefined bits may no longer be set in the DEFVAL (previously these were warnings).

1720: Disallow hyphens in COPS-PR-SPPI identifiers

As with SMIv2 modules, which COPS-PR-SPPI derives from, a warning is now produced for identifiers with hyphens in PIB modules.

1717: Wrong range given in INSTALL-ERRORS message

INSTALL-ERRORS was being checked versus the correct allowed range of 1..65535, but the error message indicated 0..65536 was allowed.

1689: False subordinate OID warnings for conformance records

Conformance sub-records were not properly ignored when checking relative structure of the OID tree, causing false errors/warnings to be produced (nothing should be considered relative to these records as they’re purely an implementation detail, not truly separate from the conformance statement).

1682: Value Assignment values missing from error messages

Error messages regarding ASN.1 Value Assignment values not matching the type were giving an empty string for the value rather than the actual value. (Note: only ASN.1 Value Assignments of type OBJECT IDENTIFIER are allowed in MIB and PIB modules; this validation is part of plain ASN.1 support.)

1685: False warning for starting bit zero when using BITS-derived type

A warning message was produced for OBJECT-TYPEs with SYNTAX referencing a TEXTUAL-CONVENTION of type BITS indicating that bits should start at zero even when the TEXTUAL-CONVENTION itself started at bit zero.

1684: Missing error for invalid PIB-REFERENCES

An incorrect function argument was suppressing the error message for PIB-REFERENCES pointing somewhere other than a PRC (row) OBJECT-TYPE.

1759: REVISIONs not sorted properly by XML parser

MODULE-COMPLIANCE REVISIONs are normally sorted when assigned or parsed from normal SMI syntax (with parse-time warning in the latter case), and therefore not checked during validation. They were not sorted properly by the XML parser, however, leaving them out of order with no indication. They are now sorted at parse time from XML as well.

1716: Severity of Value Assignments in SMIv2/SPPI

It’s now an error, rather than a warning, to use ASN.1 Value Assignments other than of type OBJECT IDENTIFIER in SMIv2 and COPS-PR-SPPI modules. It remains a warning for SMIv1 modules, but is now suppressed entirely for modules that aren’t SMI or SPPI (just ASN.1).

1736: Redundant messages for Counter with bad ACCESS

Use of Counter, Counter32, or Counter64 syntax and ACCESS, MAX-ACCESS, or MIN-ACCESS value unknown to the SMI version now produces one error message for the unknown value, rather than a second for the value being disallowed with counter types.

1729: PIB-INDEX may use attributes of other PRCs

An error message was produced if PIB-INDEX referenced an attribute of another PRC (table) rather than an attribute of the same PRC. As this is explicitly allowed by RFC 3159 section 7.5, this check has been removed.

1731: OID in module header forbidden in SMIv2

It’s now an error, rather than a warning, to assign an OID to a module in the module in SMIv2 or COPS-PR-SPPI modules (which use MODULE-IDENTITY instead). It remains a warning in SMIv1 and is now suppresed for modules that are neither SMI or SPPI (just ASN.1).

1728: OBJECT-IDENTITY and Assignment with same OID should be a warning

It is now a warning, rather than an error, when an OBJECT-IDENTITY statement and OID Value Assignment have the same OID, as it is with an OID Value Assignment and other macros having the same OID.

1727: Missing error for INDEX with negative enumerations

An intended warning for an INDEX pointing to an object with possible negative enumerations was not being produced.

1725: Superfluous auxilliary INDEX warnings

The warning for a table using only columns from other tables for indices is no longer generated when already indicating an error because the INDEX clause is not allowed (e.g. on a scalar OBJECT-TYPE).

1711: Undefined symbols should always error if known to be undefined

Dependency check “failed” errors and “skipped” warnings are now more consistent in behavior: e.g., a check is “skipped” with a warning if cross-checking can’t be performed because a module isn’t loaded, while an error is produced if it is loaded but the symbol imported from is not defined.

1710: Mixing SMI and COPS-PR-SPPI base types/macros

It’s now an error, rather than a warning, to import both SMI and COPS-PR-SPPI base types and macros within the same module (note: importing MIB OIDs and TEXTUAL-CONVENTIONs in PIB modules is allowed, provided the underlying base type is the supported by the SPPI).

1690: Wrong format indicated in DEFVAL type/value mismatch errors

When comparing the form of DEFVAL values to an object’s SYNTAX, the wrong keyword for the form of the value was specified in some errors pertaining to hex and binary. The wording of DEFVAL type/value related messages is also now more consistent.

1686: Redundant hex/binary length errors

When validating hex and binary DEFVALs, redundant errors were produced for some types when they were both not of the required length for that type and not the right multiple of digits. There was some inconsistency in whether or not they were checked for capitalization, and the wording of hex/binary related messages was also clarified.

1683: UNIQUENESS value missing from message

A warning message regarding UNIQUENESS values was showing an empty string for the value rather than indicating the actual value warned about.

1708: SMI base modules should not require MODULE-IDENTITY

On the off chance you load SNMPv2-CONF into the SDK and validate it, despite not defining anything other than macros, it will no longer error about needing a MODULE-IDENTITY statement (as with other SMI/COPS base modules).

Changes affecting MIB Smithy, MIB Smithy SDK, and MIB Views:

305: Host ID not matched when interface is disconnected

Windows interfaces that were disconnected were not recognized by the license manager, requiring laptop users to have to swap license keys depending on whether they were on wired or wireless. This is is no longer necessary, as the interfaces are seen whether connected or not.

727: Clarify “trailing hyphens will be stripped” error

The parser message produced for identifiers with illegal trailing hyphens was stripping the hyphen in the error message (indicating the corrected identifier was invalid) yet not automatically correcting the error as it should.

1368: Windows: IPv6-only interface Host IDs not available

Windows interfaces configured to support only IPv6 could not previously be used for licenses keys, but can now.

1406: Circular type references cause crash

A type definition derived from another type definition, which is derived from the first type definition, would lead to a crash due to infinite recursion. (Note: TEXTUAL- CONVENTIONs cannot legally derive from other TEXTUAL-CONVENTIONs.)

Additional changes affecting MIB Smithy SDK:

312: Changing IPs with SNMPv3 loses auth/priv state

Changing the target IP address of an existing SNMPv3 auth/priv session without also setting the auth/priv password did not sufficiently prepare the session to localize keys with the next request, causing the session to switch to no-auth/no-priv.

1354: Timeout of Tnm-style async requests causes error with future request

Upon timeout of a Tnm-style async request, the callback was being invoked using non- Tnm style arguments, which would typically cause an error, when it should not be invoked at all.

483: Updated Tcl/Tk version

The Tcl/Tk base for MIB Views was upgraded to 8.4.19. Among other things, this fixes a crash at startup on later versions of Mac OS X.

605: Application icons for Unix

Full-color application icons have been added to Unix platforms, replacing the old monochrome bitmaps.

1271: TreeView: lexicographic errors can cause loop

In certain circumstances, an agent returning lexicographically incorrect responses to get-next requests could cause branch expansion to loop until a user requested stop, and duplicate branches could be displayed. More protections against lexicographic errors were added to prevent this.

Changes in this release:

673: Instance identifier parsing for SNMP Tools

The variable lists in the SNMP Query, Walk, Trap Watch, and Tree View tools can now be expanded like a tree to display additional index values decoded from instance identifiers.

639: Upgrade TreeCtrl to 2.2.5+

The TreeCtrl version used by MIB Views has been updated to version 2.2.5. Among other things, this may fix issues with artifacts on some platforms.

886: Relaxed OID input validation

OID fields no longer require that input be strictly legal form. If a MIB can be loaded despite illegal identifier capitalization, it should now be possible to do SNMP queries with it.

887: Additional icons for status bar messages

Icons were added to some status bar messages to make them more noticeable.

876: Attempts to contact localhost when unconfigured

Expanding branches in Tree View and attempting queries in SNMP Query now check if an agent has been configured first, just as the Goto entry and Refresh button do, rather than attempting the query with session defaults.

888: Unix: Ctrl-V to paste not working in text boxes

Back-ported a patch to the default Tk text widget bindings to fix bug preventing Ctrl-V from functioning as paste under Unix.

919: MIB Views remains running after windows closed

MIB Views will now exit upon closing the Trap Watch window if it is the last window remaining (except on the Mac, where the menu bar remains).

680: Inconsistent selection colors

Non-Tile components now get their selection colors from the Tile theme for improved consistency in appearance.

643: TreeCtrl +/- buttons don’t redraw sometimes

Due to a TreeCtrl bug under Windows, the expand/collapse buttons in trees would not redraw when pressed if there were no children. This is fixed with the newer TreeCtrl version.

386: Table View sorting indicator doesn’t clear

The sort indicator on the first column in the Table View would not be cleared when sorting on another column unless the user had previously clicked to sort on the first column, leaving two sorting indicators visible.

896: sysDescr not displaying in description bar

The label area under the toolbar of the main GUI will now display the agent’s sysDescr.0 value (if returned on first connect) as it was intended.

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. MIB Views now requests up to a 1 MB buffer for the trap socket (on all platforms) to reduce the risk of packet loss.

• nmtrapd under Linux could max out CPU usage due to Linux-specific handling of select() timeouts.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were non-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

• A “wrong # args” error would occur in the Trap Watch tool when receiving events if the log had grown to 1000 events, the point where it will start to drop old events to keep the log from growing without bound.
• Copying MIB compiler errors/warnings to the clipboard will no longer include tabs for the icon columns, and will include an error or warning keyword depending on message type.

• Added ability to save tables of main GUI trees to text or CSV files.
• Added text editor for correcting parse errors in MIB files. Double-clicking on the parse error in the Add/Remove MIBs dialog, when adding a MIB fails, launches the text editor to the line where the error occurred.

Bug Fixes

• Under some circumstances, WinXP unsets HOMEDRIVE and HOMEPATH, which would prevent MIB Views from finding its license key the default location without re-logging in. The license key is now stored in the Application Data folder by default.