Re: Exception when calling setName on SystemGroup

["Phil Wang" <pywang@nortelnetworks.com>]

I used the UCD one, which is available from
"http://ucd-snmp.ucdavis.edu".

Phil

> "Ha, Bryan [HAL02:HG00:EXCH]" wrote:
> 
> Thanks a lot for your replies. I will see what I can do on NT as well.
> 
> Which SNMP daemon are you using on LINUX ?
> 
> Many thanks,
> 
> Bryan
> 
>      -----Original Message-----
>      From:   Wang, Phil  [SMTP:pywang@americasm01.nt.com]
>      Sent:   Wednesday, October 11, 2000 7:31 PM
>      To:     Duncan, Robert
>      Cc:     Ha, Bryan ; open_networks@openetlab.org;
>      active_networks@openetlab.org; Duncan, Robert
>      Subject:        Re: Exception when calling setName on SystemGroup
> 
>      For the time being, we can the two default communities for
>      different
>      SNMP operations, the "public" community is for read-only (i.e.,
>      SNMPGET)
>      and the "private" one for write (i.e., SNMPSET). They share the
>      same mib
>      view (with read or write permissions).
> 
>      I've made the above two communities working on Linux. However,
>      "snmpd.conf" is a bit tricky at the beginning. -:)
> 
>      Phil
> 
>      Rob Duncan wrote:
>      >
>      > "Wang, Phil " <pywang@americasm01.nt.com> writes:
>      >
>      > > > 2. As I read from the SNMP spec, SNMP requests should
>      indicate the
>      > > > community name it is using, how is that achieved in the API
>      ? Where
>      > > > should I set the community name to be for authentication
>      purpose ?
>      >
>      > > Two communities are used internally by "jmibmap_loopback",
>      they are
>      > > "public" and "private". If you want to use your own
>      communities, you'd
>      > > re-write the a new JMIB mapper.
>      > >
>      > > On the other hand, these Java mibs (e.g., jmib_mib2 for MIB
>      II) are
>      > > automatically generated from their mib texts which do not
>      contain a
>      > > community name. So, the JMIB APIs do not support setting a
>      community
>      > > name. Rob, it that right?
>      >
>      > Yes.  This is a bug in our APIs.  Right now the community
>      strings are
>      > hardwired into the Loopback service implementation.  I'll fix
>      this for
>      > the next release by adding an API for this into the Loopback
>      service,
>      > and probably also by setting some configuration variables
>      somewhere.
>      >
>      > R.