Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM 12 may crash F5s due to an F5 memory leak

NPM 12 may crash F5s due to an F5 memory leak

Table of contents
Created by Robert Stidman, last modified by Michael Perez on Feb 02, 2017

Views: 1,401 Votes: 1 Revisions: 8

Updated June 13, 2016


Servers polled with NPM 11.x and lower that are moved to an NPM 12 system for polling may crash and need to be rebooted after an NPM poll, likely due to a known issue with an F5 memory leak.  


NPM v12 and F5 devices


It is suggested to work with F5 on this issue. Refer to SOL14036: The BID-IP snmpd process may leak memory when polling for the number of members in a pool.  (© 2015 F5 Networks, Inc. All rights reserved.  Available at, obtained on June 15, 2016)  Please note that some customers have reported similar impact on versions not listed in the article.  


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any. 




Last modified