Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NPM server requests promiscuous mode from the ESXi server

NPM server requests promiscuous mode from the ESXi server

Table of contents

Updated July 18, 2017


This article describes why the NPM server is requesting promiscuous mode from the ESX server where it is hosted.


All NPM versions



Promiscuous mode is a security policy which can be defined at the virtual switch or portgroup level in vSphere ESX/ESXi. A virtual machine, Service Console or VMkernel network interface in a portgroup which allows use of promiscuous mode can see all network traffic traversing the virtual switch. Promiscuous mode is where NIC passes all received traffic to the CPU instead of passing only the frames that the CPU requested to receive.

Placing the guest's network adapter in promiscuous mode causes it to receive all frames passed on the virtual switch that are allowed under the VLAN policy for the associated portgroup. This can be useful for when a sniffer needs to analyze all traffic on the network segment. Solarwinds applications include Netpath & Qoe which require WinPCap to be installed in order to be able to collect the statistics which are used for monitoring purposes.

If you are to disable this mode you will impact the ability of Netpath or QoE to work as expected.



Last modified