Hide this message
Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at firstname.lastname@example.org
In order to determine multicast routing, NPM must determine the status of all multicast devices in a defined group. These devices may be spread across multiple pollers, and group members may change regularly as devices use and stop using multicast channels. Polling operations and database
Delete operations that are required to update the database may cause spikes in CPU usage on both your polling engines and your database server.
The best approach to resolve this issue is to spread the multicast polling load by staggering multicast polling times. This polling management is performed automatically in SolarWinds NPM version 10.6.
To correct the issue of high CPU usage on polling engines and database servers due to multicast polling, upgrade your SolarWinds NPM installation to version 10.6. For more information, see Network Performance Monitor or download the upgrade from the Customer Portal.