| < Prev | Back to Table of Contents | Next > |
Known Issues
The following are some of the most important known issues you are likely to encounter with this version of the product. If you don't see a problem listed here, it does not necessarily mean we are not aware of it. However, you may wish to contact Technical Support to be sure.
-
You may notice the Notification Workspace lacks an Enterprise property. To specify the enterprise and integer values for an SMIv1 TRAP-TYPE, define the notification as you would an SMIv2 notification (that is, specifying enterprise.0.value as the OID value). It is not necessary to convert the module to SMIv1 - MIB Smithy will do the conversion automatically so long as TRAP-TYPE is imported in the module instead of NOTIFICATION-TYPE.
-
Non-MIB Documentation (i.e., RFC text) is not preserved when MIBs are saved to text files, due to format analysis issues. The text is stripped from the MIB when loaded. Now that XML support is available, we will be expanding such capabilities to allow much better control over creating and formatting document text. For now, we recommend only editing MIB files without non-MIB text, or saving your changes to a different file if you are importing MIBs from an RFC document.
-
MACRO definitions are not preserved in output generated by MIB Smithy. However, MACRO definitions generally only exist within the SMI specification documents (SMIv2 forbids new macros from being defined in information modules), which should not, in general, be modified.
-
Receiving of SNMPv3 Inform Requests is not currently supported (although they are supported with SNMPv2c). SNMPv3 informs require that the recipient respond to get requests so that engine ID discovery takes place, as the engine ID sent in the message is that of the recipient. This is not yet supported in the SDK but should be soon, along with other agent-role behavioral support.
| < Prev | Back to Table of Contents | Next > |