1

I have a MIB where 3 tables contain as first element items marked as "accessible-for-notify", 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?

EDIT:

In my init_awOduChannelTable() function the items were being initialized this way:

tblnfo->min_column = 1;
tblnfo->max_column = 5;

I changed it to:

tblnfo->min_column = 2;
tblnfo->max_column = 5;

So now it skips the "accessible-for-notify" column, as suggested by @rbelli.

Thanks.

4

1 回答 1

1

您可以将代码更改为从第 2 列而不是第 1 列开始。您可以将值更改min_column为struct netsnmp_table_registration_info值 2。如果您需要更精细的调整，您可以更改netsnmp_column_info *valid_columns;字段并说明每列有效的列。

于 2012-04-03T19:38:29.183 回答