We have the same problem: it is not possible to set the sysContact mib item,
if you have the mibiisa subagent connectect to snmpdx(master agent).
The sub-agent(which is responsible for mib-2) returns "noSuchName".
This looks like a community problem?
As far as I can see now the communities are set in snmpd.conf, and not in a
mibiisa conf file.
Any help is appreciated here.
Thanks.
Laurens Rauwers
> -----Original Message-----
> From: Mark van Kerkwyk [SMTP:kerkwyk@COMTECH.COM.AU]
> Sent: Friday, February 04, 2000 2:10 PM
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: Re: snmpdx agent on Solaris
>
> Hi James,
> I too could not get any information out of SUN, the support guys were
> trying to be really helpful but they just couldn't find any info on it. I
> finally worked out my problems in 5 mins of creative thinking.
>
> I may have missed part of this thread, too much mail coming in :-(
>
> Jane, send me your config (all /etc/snmp/conf to start with) and the exact
> details of your problem and I'll see if I can see anything.
>
> Mark :-)
>
>
>
>
>
>
> James Shanks <James_Shanks@TIVOLI.COM> on 04/02/2000 23:02:43
>
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView
> <NV-L@UCSBVM.ucsb.edu>
>
>
>
> To: NV-L@UCSBVM.ucsb.edu
>
> cc: (bcc: Mark van Kerkwyk/Sydney/Com Tech/AU)
>
>
>
> Subject Re: snmpdx agent on Solaris
> :
>
>
>
>
>
>
>
> Mark -
> I think the issue is that the SEA 1.03 agent appears to be broken.
> This is not my issue because I know nothing about snmpdx, but perhaps you
> missed
> the two earlier postings by Jane Curry and Elizabeth Bagley who said that
> they
> cannot get the new SEA 1.03 agent to work properly and are getting no help
> at
> all from SUN's FAQs or Incident library so far. Elizabeth said she uses
> the
> same config as for the 1.02 agent and for that level it works fine. other
> than
> to open a problem to SUN, I don't know what to tell her. Do you have some
> insight here?
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
>
>
>
> ======================================================================
> This email message has been swept by MIMEsweeper.
|