nv-l
[Top] [All Lists]

Volatile SNMPsets under Solaris

To: nv-l@lists.tivoli.com
Subject: Volatile SNMPsets under Solaris
From: Elizabeth Bagley <Ebagley2@AOL.COM>
Date: Fri, 11 Feb 2000 15:14:24 EST
Hello --

This question delves into specific SNMP info, rather than NetView info.  But, 
it's directly tied to last week's thread on snmpdx problems and it sounds as 
though many of us have run across the problem.

You may recall that we had a problem with SNMPsets of MIB-2 variables not 
persisting across restarts of the SNMP agents under SEA 1.0.3 on Sol 7.  I 
forwarded the information collected from everyone who experienced and did 
troubleshooting for this problem to Sun L2 support in Service Order #4377907.  
L3 support eventually reproduced the problem and turned it over to the Sun 
engineers who have labeled this as an RFE (Request for Enhancement), rather 
than a bug.  This seems strange.

Does anyone know of a specific fact -- statement in an RFC perhaps -- that 
indicates that SNMPsets are supposed to be persistent?  L3 is escalating this, 
but needs supporting documentation that this is a bug and not an RFE.

Thanks,
elizabeth
Tivoli Education


In a message dated Sat, 5 Feb 2000  1:54:14 PM Eastern Standard Time, Ebagley2 
writes:

> Laurens,
>
> If I understand correctly, you're saying that directly editing the 
> sysLocation variable in snmpd.conf file doesn't work.  This worked for me, 
> after I stopped and restarted the service to reload the config files.  I used 
> /etc/init.d/init.snmpdx stop|start. Also, removing the "-r" option from the 
> mibiisa startup line resulted in the volatile, "successful" sets that Mark 
> described. Sadly enough, I recall seeing this under Sol 2.5.1 back in 6/98 as 
> well.
>
> I've forwarded a copy of this thread to the L2 support person at Sun who is 
> helping us with Service Order #4377907.
>
> -elizabeth
> Tivoli Education
>
>
> In a message dated Sat, 5 Feb 2000  8:37:37 AM Eastern Standard Time, Rauwers 
> Laurens <Lrauwers@CS.COM> writes:
>
> > Well that dampner on the solution I discovered yesterday late.
> > I found out that the removal of the -r parameter  did not have any effect.
> > So still not able to write.
> > I also found out that even if I change the f.i. sysLocation param in the
> > /etc/snmp/conf/snmpd.conf file the value still is "system administrators
> > office".
> > This brings me to the conclusion this the daemon gets the values somewhere
> > else.
> > I couldn't find out where.
> > So as far as I am concerned, I see no solution (yet).
> >
> > Laurens Rauwers
> > HITT


<Prev in Thread] Current Thread [Next in Thread>
  • Volatile SNMPsets under Solaris, Elizabeth Bagley <=

Archive operated by Skills 1st Ltd

See also: The NetView Web