On 23 June 2011 08:05, Giuseppe Modugno wrote:
> I thought a MIB file is associated to a product.
That's one approach, certainly. And a number of
manufacturers do indeed adopt this way of thinking.
But it's the exact opposite of how SNMP was originally designed.
Think about how things look from
On 22 Jun 2011 at 15:08, Giuseppe Modugno wrote:
> > > Moreover the conditional expressions are very complex so the
> > > facility of DisMan Event would be too limiting.
> >
> > Can you expand on this, please.
>
> Just an example. A low level threshold is associated to each voltage,
> but the
On 22 Jun 2011 at 14:41, Dave Shield wrote:
> > Indeed I have other signals too: temperature, currents, RF powers and so on.
> > Do you suggest to have a different table for each signal?
>
> Yes.
>
> > For example, I have only one temperature sensor: should I create a table
> > with just one row?
On 22 June 2011 14:18, Giuseppe Modugno wrote:
> Indeed I have other signals too: temperature, currents, RF powers and so on.
> Do you suggest to have a different table for each signal?
Yes.
> For example, I have only one temperature sensor: should I create a table
> with just one row?
Yes.
*A
On 22 Jun 2011 at 8:50, Fulko Hew wrote:
> As Dave suggested... use a table.
>
> I have done that exact thing in some of our products.
> (I have tables for voltages, temp sensors, fan spped/control, etc)
> I won't provide a compilable MIB (actually I attached an extract from my MIB),
> but the gen
On 22 Jun 2011 at 10:27, Dave Shield wrote:
> On 22 June 2011 09:54, Giuseppe Modugno wrote:
> > I think DisMan Event MIB has the purpose to allow the user to completely
> > customize the OIDs to monitor and the conditional expressions that trigger
> > notifications.
> > In my case, I don't want t
On Wed, Jun 22, 2011 at 4:54 AM, Giuseppe Modugno
wrote:
> **
> On 22 Jun 2011 at 9:10, Dave Shield wrote:
> > On 22 June 2011 08:50, Giuseppe Modugno
> wrote:
>
... snip ...
> > > I'm wondering what is the best approach between creating 10
> different
> > > notifications with own OI
On 22 June 2011 09:54, Giuseppe Modugno wrote:
> I think DisMan Event MIB has the purpose to allow the user to completely
> customize the OIDs to monitor and the conditional expressions that trigger
> notifications.
> In my case, I don't want to give the user this flexibility.
Then don't.
It woul
On 22 Jun 2011 at 9:10, Dave Shield wrote:
> On 22 June 2011 08:50, Giuseppe Modugno wrote:
> > I'm defining a MIB for a custom electronic equipment. I already extended the
> > Net-SNMP agent with success for GET and SET requests.
> > Now I want to send notifications messages in case of any alarm.
On 22 June 2011 08:50, Giuseppe Modugno wrote:
> I'm defining a MIB for a custom electronic equipment. I already extended the
> Net-SNMP agent with success for GET and SET requests.
> Now I want to send notifications messages in case of any alarm.
First question - do you actually need to define y
I'm defining a MIB for a custom electronic equipment. I already
extended the Net-SNMP agent with success for GET and SET requests.
Now I want to send notifications messages in case of any alarm.
The equipment monitors 10 voltages and each voltage is associated to
an OID: oidV1, oidV2, ..., oidV
11 matches
Mail list logo
