2009/4/22 Giuseppe Modugno :
> So you mean to translate each GET request via SNMP
> into GET request via RS232.
Yup.
That's the fundamental purpose of the SNMP agent.
To accept management requests in a standard format (SNMP),
and convert them into equivalent device-dependent requests.
(be that an
On 22 Apr 2009 at 3:30, dan anderson wrote:
> If you can afford the overhead, and the data is small enough that
> RS232's limited bandwidth won't be a bottleneck, why don't you write a
> simple common library, and just let each get data as they need it?
So you mean to translate each GET request vi
> Oh yes, I could use this third approach, but in that case I need to
> write the "retrieval routines" two times: in HTTP and in Net-SNMP
> agent.
If you can afford the overhead, and the data is small enough that
RS232's limited bandwidth won't be a bottleneck, why don't you write a
simple common
On 22 Apr 2009 at 9:41, Dave Shield wrote:
> > Anyway, I wonder how these two applications can live together
> > sharing most of the variables.
> Which variables are you talking about?
> The variables used by whatever it is on this device that
> you are trying to manage?
> Or the variables used
2009/4/22 Giuseppe Modugno :
> I need to let the user to manage a device by SNMP and/or HTTP
> Anyway, I wonder how these two applications can live together sharing
> most of the variables.
Which variables are you talking about?
The variables used by whatever it is on this device that
you are t
I need to let the user to manage a device by SNMP and/or HTTP, as he
wants.
HTTP would be nice for local complex configuration (i.e., during the
first-time installation); SNMP is the best for remote and centralized
management of many devices from different manufacturers.
Of course I need a SNMP
