Few feature in this post that might interest you in relation to Displaying NetFlow Traffic from Vmware Virtual Center Server Distribution Switch to Physical Switch Interfaces .
Once configured V.D.Switch under VCS NetFlow will Alert you once the traffic will be hitting the port from any unmanaged interface and will mention the # port for each unmanaged interface as below this co relating each interface index.
4/26/2014 3:08 PM EventImg NetFlow Receiver Service [TESTORION] is receiving flow data from unmanaged interface '#105'on 192.168.1.99 and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.
4/26/2014 3:07 PM EventImg NetFlow Receiver Service [TESTORION] is receiving flow data from unmanaged interface '#100'on 192.168.1.99 and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.
4/26/2014 3:07 PM EventImg NetFlow Receiver Service [TESTORION] is receiving flow data from unmanaged interface '#101'on 192.168.1.99 and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.
4/26/2014 3:07 PM EventImg NetFlow Receiver Service [TESTORION] is receiving flow data from unmanaged interface '#107'on 192.168.1.99 and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.
4/26/2014 3:07 PM EventImg NetFlow Receiver Service [TESTORION] is receiving flow data from unmanaged interface '#102'on 192.168.1.99 and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.
4/26/2014 3:07 PM EventImg NetFlow Receiver Service [TESTORION] is receiving flow data from unmanaged interface '#10'on 192.168.1.99 and it does not support SNMP. Click the "Add this interface" to manage interface and process its flow data.
4/26/2014 3:06 PM EventImg NetFlow Receiver Service [TESTORION] is receiving a NetFlow data stream from an unmanaged device(192.168.1.99). The NetFlow data stream from 192.168.1.99 will be discarded. Please use Orion Node management to manage this IP address in order to process this NetFlow data stream, or just use Manage this device.
You can always assign the IP address to V.D.Switch with exact same ip address you have for any of your Physical Switch (preferably connected directly to the ESX host ) and pretend the traffic is actually been sent by the physical switch . in below example i have selected one of my Cisco 48 port Switch .
You can chose any directly connected switch to ESX .
Assign the same IP Address to the VDS under VCS while creating the VDS (Port Group ) .
make sure you have added the same numbers of port what you have on physical switch .i have 48 port switch therefor i have selected 48 ports as below.
By default dynamic port will be assigned to each VM you can changed that binding static under the VDS switch if required .
On this point you can Change the port ID under port Group what is assigned to the VM please note that will reflect the interface index number for each interface on physical switch.
(for example port ID 10 will reflect Physical Interface 10 on the physical switch )
you can move your VM's to any of the interface under VM NIC Advanced Settings.
assign the required port to move the VM NIC on the port Group .
Once the traffic will be received each you will have the switch added under NetFlow Sources as below. assuming the traffic is been sent by physical switch connected to the ESX and each Physical NIC will be representing for each VM connected to same Virtual port under VDS.
You can further changed description on each physical interface name the VM Connected on the port will help you further finding the traffic related to the assigned VM.