On Fri, 2005-11-11 at 09:34 +0100, Andreas Dunke wrote:
> I need table within a table. After searching the web,
> I learned that this is not possible.
Correct.
You need to use two "parallel" tables.
> I tried to use two indexe. I hope the MIB (see below) is
> correct for this.
Very nearly.
The one thing that seems wrong is the ordering of the indexes
in the camTable:
satEntry OBJECT-TYPE
INDEX { satIndex }
::= { satTable 1 }
camEntry OBJECT-TYPE
INDEX { camIndex, satIndex }
::= { camTable 1 }
You probably want to index this table by {satIndex, camIndex}
which will group all the cameras on one satellite together.
(rather than having the first camera on each satellite,
followed by the second camera on each satellite, etc, etc)
But the basic idea looks right.
> But when I try to generate code with mib2c (v 5.57) I get an error:
>
> I called: mib2c devices
> I answered the following choises:
> - tables where the list of rows is external to the agent
> - An API layer ... This API is also known as "MIBs for Dummies"
That's the problem.
The MfD mib2c framework can only handle generating the code for
one table at a time. You'll need to run mib2c *twice* - once
with 'satTable' and once with 'camTable'
(That's right isn't it, Robert?)
Dave
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
