Re: about the problem of index

On 23/03/07, Clement Hsu <m934020022@gmail.com> wrote:
> dot11GroupAddressesEntry OBJECT-TYPE
> INDEX { ifIndex,
> dot11GroupAddressesIndex}
> ::= { dot11GroupAddressesTable 1 }


> When I perform snmpwork, I got the following result:
>
> IEEE802dot11-MIB::dot11GroupAddressesStatus.1.0 = INTEGER: active(1)
> IEEE802dot11-MIB::dot11GroupAddressesStatus.2.0 = INTEGER: active(1)
> IEEE802dot11-MIB::dot11GroupAddressesStatus.3.0 = INTEGER: active(1)
> IEEE802dot11-MIB::dot11GroupAddressesStatus.4.0 = INTEGER: active(1)

Yes - that looks reasonable.


> but the exact result should be
>
> IEEE802dot11-MIB::dot11GroupAddressesStatus.1 = INTEGER: active(1)
> IEEE802dot11-MIB::dot11GroupAddressesStatus.2 = INTEGER: active(1)
> IEEE802dot11-MIB::dot11GroupAddressesStatus.3 = INTEGER: active(1)
> IEEE802dot11-MIB::dot11GroupAddressesStatus.4 = INTEGER: active(1)

No it shouldn't.
Look at the definition of dot11GroupAddressesEntry, in particular the INDEX
clause. There are two objects listed here, so this table takes two index
values (exactly as you're seeing).
What makes you think that there should only be one?

Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders