Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+RE\s+MIB\s+\&\s+snmpcollect\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+RE\s+MIB\s+\&\s+snmpcollect\s*$/: 2 ]

Total 2 documents matching your query.

1. [nv-l] RE MIB & snmpcollect (score: 1): Author: jmfrancoz AT soluziona DOT com; Date: Wed, 23 Jan 2002 11:42:09 +0100; 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; /usr/local/webapp/mharc-adsm.org/html/nv-l/2002-01/msg00086.html (10,596 bytes)
2. Re: [nv-l] RE MIB & snmpcollect (score: 1): Author: "James Shanks" <jshanks AT us.ibm DOT com>; Date: Wed, 23 Jan 2002 09:16:02 -0500; 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; /usr/local/webapp/mharc-adsm.org/html/nv-l/2002-01/msg00087.html (12,649 bytes)

Current List: 1 - 2
Page: [1]