Well, I tried editing a copy of the old cisco mib, unloaded that one, and
loaded my copy. The oddest thing happened - I could build a mib apple
using it, and during the build it showed that it was a counter. But on
running
the mib apple, it handled it as an integer. I don't know what snmpcollect
would make of it.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
========================================================================
I attempted to edit the snmpcol.conf, and it definitely did NOT work. It
didn't cause any harm to the system, but caused problems with snmpcollect.
Thinking back, I didn't try editing the mib file first before loading -
perhaps you could try this.
As I only needed the values for reporting purposes, I just collected on the
integer values, and calculated the delta values in custom reports.
Regards,
Matt Moore
-----Original Message-----
From: lclark@us.ibm.com [mailto:lclark@us.ibm.com]
Sent: Friday, 10 March 2000 15:43
To: NV-L@tkg.com
Subject: Re: [NV-L] How to coerce a mib on NT?
Wow, I just searched the archives and found that Matt Moore asked this one
last
June. No answer, though. Matt, did you try this, and did it work?
>Thanks, but unfortunately there is no mib.coerce file on NT. The only
>reference to data types I can see is in the snmpcol.conf file. If I edit
the
>data types directly in this file, will this cause me any grief?
>eg. Can I change INTEGER to COUNTER below
>MIB .1.3.6.1.4.1.9.2.2.1.1.12 5 locIfInCRC.5 units INTEGER R netview
>C smartset:Routers 0xffffffff 300 >=3D 1.000000 < 100.000000 % d 58720263
>Regards,
>Matt Moore
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
==========================================================
I tried threatening it ....:)
On AIX, we have the mib.coerce file that is mostly used to change useful
Cisco mib variables from INTEGER to COUNTER so we can graph them
as rates of change, since they really are like counters in that they
continue to grow from boot time. On NT, I don't see that file, and mib
appls I make to look at the locIf variables don't work as expected (flat
line 6543 instead of flat line 0). Is there a way to do this on NT?
Another possiblity, but I don't know how to go about it, is maybe faking
the mib. I had to unload a cisco-if mib last week to get the MIB-II
Interface variables back to Counter, because the Cisco-if mib file re-
defined them as Counter32, then redefined Counter32 as Integer. What
would happen if I just changed the old cisco mib so that the locIf stuff
was Counter instead of Integer? Anybody tried this?
All guesses are welcome..
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|