SNMP Leaks Memory If the OID Cannot Be DecodedLast reviewed: December 23, 1997Article ID: Q178381 |
The information in this article applies to:
SYMPTOMSOver time, the Windows NT system responsiveness appears sluggish, and Clients may report a gradual decrease in system performance. By tracking the amount of Private Bytes for Snmp.exe, it can be observed that, over time, it increases without decreasing. This is viewable using Windows NT Performance Monitor by selecting the following counter to monitor:
Object: Process Instance: SNMP Counter: Private Bytes CAUSEIf SNMP cannot decode an OID from a network packet, SNMP does not free up the memory, resulting in a memory leak in the Snmp.exe processes. The impact of this leak will be more evident on a system running on a network segment that receive lots of SNMP broadcast traffic.
RESOLUTIONTo resolve this problem, obtain the following fix or wait for the next Windows NT service pack.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
|
Additional query words: SNMP debug
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |