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
STATUS current
DESCRIPTION
"Description."
::= { awOduChannels 1 }
-- 1.3.6.1.4.1.3979.7.4.3.2.2.1.1
awOduChannelEntry OBJECT-TYPE
SYNTAX AwOduChannelEntry
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Description."
INDEX { awTopRadioIndex, awOduIndex, awOduChannelIndex }
::= { awOduChannelTable 1 }
If I try to query any of the remaining items individually (`snmpget`,
`snmpgetnext` or `snmpset`), everything works, but when I try to `snmpwalk`
or `snmptable`, I got an error stating "unknown column or not readable".
I tried changing to "not-accessible", but it changed nothing.
Why is net-snmp trying to iterate over "accessible-for-notify" items?
What should I do to fix?
------------------------------------------------------------------------------
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
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
