Re: "accessible-for-notify" snmpwalk problem

On 3 April 2012 15:44, Jaques Arantes <[email protected]> wrote:
> I have a MIB where 3 tables contain as first element items marked as
> "not-accessible", like:
>
>
>         -- 1.3.6.1.4.1.3979.7.4.3.2.2.1
>         awOduChannelTable OBJECT-TYPE
>             SYNTAX SEQUENCE OF AwOduChannelEntry
>             MAX-ACCESS not-accessible

That's correct - this is an "internal" MIB definition for the table as a whole.
It's not a leaf object, so can't be queried directly.


>         awOduChannelEntry OBJECT-TYPE
>             SYNTAX AwOduChannelEntry
>             MAX-ACCESS accessible-for-notify

This is wrong.
The 'Entry' object is *also* an internal MIB definition, which cannot
be queried directly.   This should also be defined as "not-accessible".


Please post the whole of your MIB file, so that we can see what
it looks like.

Dave

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
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