2012/2/6 chengkeke <[email protected]>:
> Error "Bad parse of NOTIFICATION-TYPE" is displayed when define a node with
> OBJECTS is {}/null.
Yes - that is correct.
This is not valid SMI syntax.
> The MIB can be compiled successfully in Mg-Soft browser.
It's quite possible that the Mg-Soft browser handles this problem.
But it still doesn't make it valid.
Whenever you're developing a MIB file, it's a good idea to
pass it through "smilint" or a similar MIB validation tool,
which will flag up any potential problems.
Neither Mg-Soft browser, not the Net-SNMP suite claims to
be particularly strict about checking validity. So some definitions
that are strictly not 100% valid, may be accepted without complain
by one or both of these packages, but be rejected by the other
(or other SNMP software)
> Is it a known issue? Have it fixed in later version?
No it has not been fixed - because it's an error.
> When we define a node with OBJECTS is {} in MIB file
Why are you definining this as empty in the first place?
If you don't need any payload varbinds in the notification,
then just omit the (optional) OBJECTS clause completely.
Dave
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
