Re: 回复： 回复： Can snmp support nested tabl es?

I was actually hoping for a textual description of
the actual

But from what I can make out from your description,
the overall MIB structure needs to have entries for
two types of "things" - "ge things" and "bond things".
Yes?

But the syntax and semantics of the information held
for each type of thing is the same (i.e. three IP addresses,
representing interface, gateway and netmask).
Yes?


If that's the case, then I think you can simply use
a single table for everything.   Something like

    myIndex   INTEGER
    myAddress  IpAddress
    myGateway  IpAddress
    myNetmask  IpAddress
    myType      INTEGER { ge(1), bond(2) }
    myDescr    AdminString

plus any other columns that they have in common,

That fact that you tend to regard the two IP-triplets as
distinct structures, is not actually important for modelling
this within SNMP.   The syntax of the data is the same.


If the types of the two structures were different, then
you'd model this using three tables - one for the
ge-specific columns, one for the bond-specific columns,
and one for the information held in common.
  But all three tables would be indexed by the same
MIB object (part of the common table).  The other two
tables would "augment" this basic table.

  See the hrDeviceTable (and related) in the Host
Resources MIB for an example of this.


But for what you've described so far, that's probably
overkill.  You can actually work with just one table.

Dave

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
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