The table is indexed by the MAC address and it is a read only table. So
I have added Private Mib parameter that takes the Key value
from the user as a set parameter. I am able to retrieve the details
of all the parameters for that key value and storing it into a structure.
I want to display these values but when I run the for loop for
requests, the request has the parameter details of the private MIB.
Is there anyway I display the single row for the SET request?
Table X is read only table
It is indexed by MAC address.
Table Y = private Mib
"y" is Table Y parameter that is settable
"y" fetches the MAC address from the user and fetches the data
for that MAC address through Get a single row and
stores it in a "x" structure (this structure has all parameters
of Table X).
I want to display the Table X one row based on whatever I have
stored in "y" structure.
How to retrieve these in single row format??
Dave Shield wrote:
> 2009/11/10 forumdesai@... <forumdesai@...>:
>> But my requirement is I know the key values but I am not aware where
>> (as in which row ) it will appear.
>> It is something like MAC address of the CPEs connected to my system.
> Retrieving information from a MIB table is critically dependent on the
> design of that table. And in particular, the indexing of that table.
> If you need to be able to retrieve information for a particular MAC address,
> then you need a MIB table that is indexed by MAC address. SNMP can
> only work with the indexes that have been defined. It can't handle
> generating indexes for other columns on thefly.
> (It's the "simple" network management protocol, remember!)
> If you need anything else, then you'd have to walk the MAC address
> column, and look for the desired value. Then you could extract the
> index value for that instance, and use a GET request to retrieve the
> rest of the row. There's no real alternative.
> Now all of this could be wrapped within a library routine, so the details
> could be hidden from the end coder (e.g. see the AnyData::SNMP
> perl module, which makes SNMP queries look like SQL).
> But fundamentally, that's what would be needed.