Re: [nv-l] RE MIB & snmpcollect

["James Shanks" <jshanks@us.ibm.com>]

I would use GAUGE.
If the MIB that this OID came from were converted from SNMP V2 to SNMP V1, then the type would be given as GAUGE.
And if you had such a MIB, that's how xnmcollect would put it into snmpCol.conf.   SNMP V1 is what snmpCollect  understands.
The only real difference between GAUGE and GAUGE32 is the size of the value returned, and I believe that snmpCollect has big enough buffers that this does not matter.  

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group

jmfrancoz@soluziona.com 01/23/2002 05:42 AM

To:        nv-l@lists.tivoli.com         cc:                 Subject:        [nv-l] RE MIB & snmpcollect

Sorry again Paul,

But I have to activate the new variable into the file (snmpCol.conf) like
GAUGE32 or GAUGE; for instance:


Option 1:
MIB .1.3.6.1.4.1.9.9.109.1.1.1.1.5 cpmCPUTotal5min units GAUGE32 R
C ROUTER_A 120 0.000000 0.000000 xA s 58720263 ALL -

or on the oder hand:

Option 2:
MIB .1.3.6.1.4.1.9.9.109.1.1.1.1.5 cpmCPUTotal5min units GAUGE R
C ROUTER_A 120 0.000000 0.000000 xA s 58720263 ALL -


What option I have to choose?

Thanks:

Jose



---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)