BUG: The OID for memPercentCommittedBytesInUse Always Returns Zero

MORE INFORMATION

1. At a command prompt, run the Perfmib.reg tool from the Windows NT 4.0 Resource Kit. This creates the appropriate registry entries for the Perfmib.dll extension agent.
2. Build a Perfmib.mib file and a Perfmib.ini file using the Per2mib.exe tool from the Windows NT 4.0 Resource Kit. For example, at a command prompt, type the following command:

   perf2mib perfmib.mib perfmib.ini memory 200 mem

   This creates a Perfmib.mib file and a Perfmib.ini file. These files are used to expose the Performance Monitor memory object.
3. At a command prompt, stop the SNMP service by typing net stop snmp. (You can also stop the SNMP service using the Services tool in Control Panel.)
4. Find the Mib.bin file in the System32 folder and rename it to Mib.old.
5. Use the following steps to compile a new Mib.bin file (that includes the Perfmib.mib file created in step 2):
   1. At a command prompt, set the default folder to the Windows NT 4.0 Resource Kit folder (for example, type cd ntreskit, where ntreskit is the Windows NT 4.0 Resource Kit folder).
   2. Type the following command: mibcc -n ontreskit\mib.bin -t -w2 smi.mib lmmib2.mib mib_ii.mib perfmib.mib
6. Copy the following files from the Windows NT 4.0 Resource Kit folder (ntreskit) to the System32 folder (%SystemRoot%\System32):
   • Mib.bin
   • Perfmib.bin
   • Perfmib.ini
   • Perfmib.dll
7. At a command prompt, start the SNMP service by typing net start snmp. (You can also start the SNMP service using the Services tool in Control Panel.)
8. After you create the new MIB that contains the Performance Monitor memory objects, you can test it using the Snmputil.exe tool found in the Windows NT 4.0 Resource Kit. To test the MIB:
   1. At a command prompt, type cd ntreskit. This changes the default folder to the resource kit folder.
   2. Use the Snmputil tool to walk the process OID tree. Type the following command:

      snmputil walk localhost public .1.3.6.1.4.1.311.1.1.3.1.1.200.27.0

      Using this command always returns a value of 0 for the memPercentCommitBytesInUse memory counter, regardless of the values for Committed Bytes and Commit Limit. It should return the ratio of the Committed Bytes to the Commit Limit values.