🚀 go-pugleaf

I have been adding more and more data reports (snmp queries) under SunNet
Manager 1.2 and have noticed a near linear increase in system resource
consumption. Each new data report starts another copy of na.snmp to support
its snmp query. As system load grew I added more RAM and swap space to 
maintain the SPARC 2 workstation's performance.

Under SunNet Manager 2.0 na.snmp was enhanced to permit it to service
multiple data reports from one copy of na.snmp (the default from Sun is 20
data reports per copy of na.snmp). There are a few variables Sun supplies
in the snm.conf file to allow some tuning of the new na.snmp process.

Under 1.2 I am able to successfully run about 670 data reports, and it looks
like there is some room left to run a few more before the SPARC 2 expires.
Under 2.0 I was unable to run more than 189 data reports. I increased the
time out values for na.snmp* variables in snm.conf, which helped a little,
and also increased "Request Timeout" under the console properties, but am
still unable to get as many data reports to run under 2.0 as I had under
1.2.  Sun has said there is a performance enhancement coming for the 2.0
na.snmp later this year. In the meantime I would like to know if anyone
else has had a similar experience with SunNet Manager 2.0 and how they
increased the number of data reports. I realize the load on na.snmp is also
influenced by the number of mibs (objects) being queried. On average each
query is for about 15 counter type mibs.

Please post your response in this group, or email your response to me at 
rxth31@email.sps.mot.com.

Thanks,
Ralph Thomas