The version of netsnmp that is provided by Velocity Software includes many updates as well as testing. The issues in a "z" virtual environment is 1) overhead, 2) validity of data, and 3) complete information. Some of the mibs provided by the base snmp are expensive to utilize but still important, and the mibs provide incomplete data if you have a mainframe mentality where capture ratio is important. By replacing expensive mibs, and adding a significant amount of new metrices, capture ratio becomes very high and operational costs are reduced. SLES10 does have some new accounting features for which I've seen no validation. The reports and displays created that require the Velocity Software version are "ESALNXP, ESALNXA, ESALNXS, ESALNXC and ESALNXU" which represent full process data, WAS Application analysis, process configuration, and linux user analysis.
Stricklin, Raymond J wrote:
SLES10 comes with its own version of net-snmp (5.3.0). Velocity seems to provide a version of net-snmp for SLES10 (5.2.2). SuSE has made it microscopically difficult to remove their net-snmp by placing upon it a dependency from hplip. I would like to make it clear that this is a dependency I do not care about in the least. However, I do want to dot all my i's. So. In the search for a more perfect enlightenment, thus: is there any particular reason why we should not (or would not want to) use SuSE's net-snmp with Velocity? Are there customizations present in Velocity's RPM which we would need? Are there support requirements from Velocity's perspective, to use their net-snmp package? Thanks; ok r.
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
begin:vcard note:If you can't measure it, I'm just not interested version:2.1 end:vcard
