Hi!

Vivekanandan> Iam having an Index element which is also an OBJECT for Vivekanandan> an NOTIFICATION-TYPE object. And Iam having the Vivekanandan> MAX-ACCESS of this Index element as Vivekanandan> "accessible-for-notify". The smilint tool gives an Vivekanandan> warning that "Index element should be not-accessible", Vivekanandan> which is wrong for this case. So an extra check should Vivekanandan> be put for this also.

An interesting situation! :-) However, RFC 2578, Section 7.7 doesn't allow another MAX-ACCESS value than not-accessible in this case. Your MIB should not use the not-accessible index object in the notification type's OBJECTS clause, but another column of the conceptual table.

And in most cases this even makes sense :-): Notifications are raised on specific conditions. You usually want to carry not only the instance information but also some information about this condition, e.g. the current status on a status change notification or a current rate on a threshold notification.

-frank