cmd_exe_mib example question

[Frank Fock]

Hello Hans,

The tables you mentioned below are empty by default.
That is way you will not see their OIDs in a walk.
You can create rows in the tables using the RowStatus
column of the respective tables.

Hope this helps.

Best regards,
Frank

Hans Bouwers wrote:
> Hello list,
> 
> I have some trouble with the cmd_exe_mib example.
> I built the project in MS VC7 and got it running.
> When I want to get all available oid's, starting from 1.3.1.2.1.1.2
> (sysObjectId), I get subsequently all the system oid's, up until
> oidSnmpProxyDrops.
> Then I get 1.3.6.1.4.1.4976.6.1.2.2.1.0, which represents
> 
> cmdExecutionCmdNextIndex::cmdExecutionCmdNextIndex():
>    MibLeaf("1.3.6.1.4.1.4976.6.1.2.2.1.0", READONLY, new SnmpInt32())
> 
> After that, the next oid is 1.3.6.1.6.3.10.2.1.1.0, which is something from
> the SNMP-FRAMEWORK-MIB, so there's only one oid available from the
> 'cmd_exe_mib-MIB'.
> 
> So, how do I get access to the rest of the (according to the code) available
> oid's:
> 1.3.6.1.4.1.4976.6.1.2.1.1.1 for cmdExecutionCmdConfigEntry
> 1.3.6.1.4.1.4976.6.1.2.2.2.1 MibTable for cmdExecutionCmdEntry
> 1.3.6.1.4.1.4976.6.1.2.3.1.1 MibTable for cmdExecutionOutputEntry
> 
> 
> Any hints appreciated.
> 
> Hans
> 
>