On 7 Feb 2008 at 9:31, Dave Shield wrote:
> On 07/02/2008, Giuseppe Modugno <[EMAIL PROTECTED]> wrote:
> > If I have just one SNMP agent serving many pieces of equipment, what could 
> > be
> > the structure of the MIB? I think I must register a subtree for each
> > combination of the pieces: The user with a machine composed by A and B 
> > pieces
> > I have two subtrees:
> >    ...enterprises.mycompany.user1.A...
> >    ...enterprises.mycompany.user1.B...
> > The user with a machine composed by A, A and B:
> >    ...enterprises.mycompany.user2.A1...
> >    ...enterprises.mycompany.user2.A2...
> >    ...enterprises.mycompany.user2.B...
>
> Some of this information will be similar for the various types of kit,
> in which case you're probably looking at a shared MIB, perhaps
> containing tables with one row (or group of rows) for each piece
> of attached equipment.
>   (Or else use contexts to have parallel versions of the same
> MIB structure).

I'm sorry Dave, can you make some examples? What do you mean with "...a shared 
MIB"? Of course, two kits with a different combinations of equipments have some 
informations in common, and other not common. The common informations are 
related to common equipments, it there are any.

And what about contexts? Where can I read more about that?


> Some of this information will be specific to a particular type of
> equipment, in which case you're really looking at a separate
> MIB for that particular element.

Usually it is so. But if I create a MIB for each elements, how can I compose 
them in a kit? I'm not able to understand.


> But think in terms of a collection of inter-related and cooperating MIBs,
> rather than one single monolithic MIB to cover everything.

Oh yes, I want to create many MIBs, not only one.

Here it is an example (it's not true). 

Suppose my company produces DVD recorders, DVD players, audio/video mixers, and 
so on. Each product has a RS232 for remote control purpose and each product can 
be associated to a MIB.
Parameters for DVD records DVDREC2000 could be: record (on, off); time; input 
(front, rear); inputType (scart, composite,...); a table with programs to 
record at a certain times; ...
Parameters for DVD players DVDPLA2000 could be: play (on, off); output (front, 
rear); videoOutput (composite, component, scart...)

The MIB for my company should be:
   ...enterprises.mycompany.dvdrec2000.record; .time; .input; .inputType...
   ...enterprises.mycompany.dvdpla2000.play, output, videoOutput...

Now I deliver a kit composed by two DVDREC2000 and three DVDPLA2000. They all 
are connected to a Linux box by a RS485 bus, so the subagent running on the 
Linux box can communicate with each device.
In this combination of devices the user sees only one Ethernet port with a 
single IP address (the Ethernet port of the Linux box).
What is the MIB (or MIBs) I should give to the user in order to manage the 
entire kit with a SNMP manager? The only solution is to make a different set of 
MIBs for each combination of devices. But it's a very bad solution because the 
number of combinations is very big!


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to