[mrtg] SOLVED! Re: Re: Repost: NT Drive space OID not working

Nick_Ellson at or.blm.gov Nick_Ellson at or.blm.gov
Wed Aug 2 00:15:58 MEST 2000





Thank you Garth!

After adding the entry specified in #1 as you suggested, rebooting my PC,
everything works now!

Whew!!! I can put this mess to bed, thanks again.

Nick









"Garth K. Williams" <garth.williams at home.com> on 08/01/2000 01:25:27 PM
                                                                                
                                                                                
                                                                                


                                                              
                                                              
                                                              
 To:      Nick Ellson/ORSO/OR/BLM/DOI at BLM                     
                                                              
 cc:                                                          
                                                              
                                                              
                                                              
 Subject: Re: [mrtg] Re: Repost: NT Drive space OID not       
          working                                             
                                                              







Hi Nick!

Mind if I get involved?

I just got through helping another soul with the same problem you describe.

Sometimes, (MS bug-don't know why) if you install SNMP performance monitor
(specifically when you register PERMIB.MIB), the SNMP registry hive drops
references to RFC1156.  When this happens, the SysDesc and SysUpTime cannot
be read, and MRTG fails, even though SNMPUTIL.EXE will work fine.  Even
other NMS will read the private enterprise key properly.

I suggest that you start the Registry Editor (start/run/regedt32) and:

1) Check
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/SNMP/Paramters/Extensio
nAgents and check that the RFC1156 entry is registered (see snmpreg.jpg).
If not there, create the key (make it the same as the others, only a
different number) and make the text the same as in the image file.

2) Go to HKEY_LOCAL_MACHINE/Software/Microsoft/RFC1156Agent/CrrentVersion
and see if it is there.  If it is, check to make sure it points to the
inetmib1.dll file (see snmpreg2.jpg)

3) Lastly, confirm that the file inetmib1.dll is in the system32 directory.

Hope this helps!

Garth

Garth K. Williams - Systems Engineer (MCSE, MCP+I, CNA)
Mailto: garth.williams at wtcs.org

Web: http://www.wtcs.org/snmp4tpc
------------------------------------------------------------------------
Home of the "SNMP for the Public Community" Web
Support site for SNMP, Windows 95/98/NT/2000, NetWare and MRTG
------------------------------------------------------------------------

----- Original Message -----
From: <Nick_Ellson at or.blm.gov>
To: <john.hoffman at za.pwcglobal.com>
Cc: <mrtg at list.ee.ethz.ch>
Sent: Tuesday, August 01, 2000 1:25 PM
Subject: [mrtg] Re: Repost: NT Drive space OID not working


>
>
>
>
> The numbers I was getting from "snmputil walk"  suggested that I was
getting
> disk space free. It matched the numbers in My Computer listing details.
>
> Anyway, either way I didn't get any thing but errors from MRTG, yet
snmputil
> could read the numbers.
>
> I just don't know what else to try at this point. I would believe an SNMP
issue
> if snmputil would fail, but not only can it read the value I request, so
can a
> third party package "What's Up Gold" from another system.
>
> You have a working config that does this? May I see it?
>
> Nick
>
>
>
>
>
>
>
>
>
> john.hoffman at za.pwcglobal.com on 08/01/2000 02:27:21 AM
>
>
>
>
>
>
>
>
>  To:      Nick Ellson/ORSO/OR/BLM/DOI at BLM
>
>  cc:      mrtg at list.ee.ethz.ch
>
>
>
>  Subject: Re: [mrtg] Re: Repost: NT Drive space OID not
>           working
>
>
>
>
>
>
>
>
>
>
> Nick,
>
> The OID you are using is representing the Percentage of Disk space
> available/Free. Therefore a "Gauge" option as you indicate.
>
> You're OID =  1.3.6.1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.67.58.0
> Try this one.   1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58.0
>
> This is Disk space used.  If this also fails, you may have an SNMP issue.
>
> I have used both with no problems, yet on NT server and not Workstation.
>
> Regards
>
> John
>
>
>
>
> Nick_Ellson at or.blm.gov on 31/07/2000 08:56:42 PM
>
>
>
> To:   "Stieers, Ken" <KStieers at dainrauscher.com>
> cc:   mrtg at list.ee.ethz.ch
> Subject:  [mrtg] Re: Repost: NT Drive space OID not working
>  Size: 6 Kb
>
>
>
>
>
>
>
> Hi Ken,
>
> When I posted this a while back (two weeks roughly) I had tried all
variations
> of leading "." trailing ".0" and such, no difference.
>
> Here it is without the leading "."
>
> D:\apps\mrtg\run>perl \apps\mrtg\run\mrtg \apps\mrtg\run\mrtg1.cfg
> SNMP Error:
> Received SNMP response with error code
>   error status: noSuchName
>   index 3 (OID: 1.3.6.1.2.1.1.3.0)
> SNMPv1_Session (remote host: "158.68.91.85" [158.68.91.85].161
>                   community: "public"
>                  request ID: 661726980
>                 PDU bufsize: 8000 bytes
>                     timeout: 2s
>                     retries: 5
>                     backoff: 1)
> SNMPGET Problem for 1.3.6.1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.67.58.0
1.3.6.
> 1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.68.58.0 sysUptime sysName on
public at 158.
> 68.91.85
> SNMPGET: Failed to reach target:
"1.3.6.1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.
>
67.58.0&1.3.6.1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.68.58.0:public at 158.68.
91.8
> 5". I tried multiple times! public at 158.68.91.85
>
>
>
>
>
>
>
>
>
>
> "Stieers, Ken" <KStieers at dainrauscher.com> on 07/31/2000 11:23:35 AM
>
>
>
>
>
>
>
>
>  To:      Nick Ellson/ORSO/OR/BLM/DOI at BLM,
>           mrtg at list.ee.ethz.ch
>
>  cc:
>
>
>
>  Subject: RE: [mrtg] Repost: NT Drive space OID not working
>
>
>
>
>
>
>
>
> Use no leading dot (see below):
>
> Target[ORSO109]:
> 1.3.6.1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.67.58.0&1.3.6.
> 1.4.1.311.1.1.3.1.1.5.1.3.6.48.58.48.58.68.58.0:public at 158.68.91.85
>
>
>
>
> --
> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
> Archive     http://www.ee.ethz.ch/~slist/mrtg
> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
>
>
>
> ----------------------------------------------------------------
> The information transmitted is intended only for the person or entity to
which
> it is addressed and may contain confidential and/or privileged material.
Any
> review, retransmission, dissemination or other use of, or taking of any
action
> in reliance upon, this information by persons or entities other than the
> intended recipient is prohibited.   If you received this in error, please
> contact the sender and delete the material from any computer.
>
>
>
>
>
>
> --
> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
> Archive     http://www.ee.ethz.ch/~slist/mrtg
> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
>





--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi



More information about the mrtg mailing list