On Wed, 2005-04-13 at 13:28, Farazad Farhadzadeh wrote:
> > And did you edit these files in any way?
> > Or did you just copy them exactly as generated by mib2c?
> > 
> i copy them exactly as generated by mib2c without any editing.

Then no - this will *NOT* work.

Mib2c generates a *template* for your MIB code.
It does *NOT* create a fully-working module.

It's up to =>you<= to flesh out this template with the
necessary additional code.   Which will be different
for each MIB, depending on what that MIB actually
does.  It's not possible for mib2c to genetate this
semantic handling automatically.   Nor is it feasible
for us to tell you what to write.
  This is something *you* have got to do.



> > What object value were you trying to retrieve?
> > 
> this is mplsOutSegmentindex

Which has the OID .1.3.6.1.2.1.10.166.2.1.7.1.1
(at least according to RFC 3813)

Two other comments:

- That's the OID of the MIB object itself,
   not of an instance in a particular row.
   So even if you'd written the code to implement
   the MIB table, this wouldn't have worked.

- The object mplsOutSegmentIndex (case matters!)
   is defined as "not-accessible". So even if
   you'd specified a valid instance, this
   *still* wouldn't have worked.


I will repeat the advice I gave you yesterday.
Choose *one* table from this MIB, and start by
trying to implement that.  Preferably choose the
simplest, or most basic.

A quick scan through the MPLS-LSR-STD-MIB suggests
that mplsInterfaceTable is probably the most
obvious starting point.

Dave



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to