Thanks for your update. Yes true but when we were into the ENS stack testing we were using this command regularly at the host level and yes from the dvportgroups we can get the vmnics attached. As you said vsish commands can also be used to get the vmnic information of the VM on a ESXi.
Original Message:
Sent: Dec 25, 2024 01:02 AM
From: Yao Zhang
Subject: How to find which vmnic a VM is using on ESXi?
Hello Sriam,
'net-stats -l' will not give the information related to the vmnics attached to the VMs through the dvport groups directly,
But we can use 'net-stats -l' first to find target VM's network adapter relate-portnumber ID first, and use vsish command to confirm which vmnic a VM is using on ESXi.
Original Message:
Sent: Dec 24, 2024 01:41 AM
From: Sriram ChunchankatteMelukote
Subject: How to find which vmnic a VM is using on ESXi?
Hello,
Another way to get all information related to the dvportsets and the VM connections on the hosts is to run the 'net-stats -l' command on the ESXi host. This will give the information related to the vmnics attached to the VMs through the dvport groups.
Original Message:
Sent: Jan 17, 2011 08:01 PM
From: ppapared
Subject: How to find which vmnic a VM is using on ESXi?
Hello all,
Hopefully this is an easy one for someone. I'm running vSphere4 and using ESXi4. I would like to know if it is possible, from within the vClient, if you can tell which vmnic a VM is using when connected to the Port Group? I have two physical adapters teamed in my vSwitch that my VMs are on. Each VM is only setup for a single nic in its configuration (if that matters). I would like to know if it was possible, from within the vClient, to tell which adapter is being used.
I had one of my fiber connectors go out on one physical adapters that was in the switch that connected to the network so some of my VMs where connected to the network and some of them were not. I figured out if was the fiber connect and replaced it. Everything was fine after that but it got me to thinking about this question.
I don't use vMA to much ( which I plan to start learning more ) and since ESXi only has the troubleshooting console, I didn't know where else to look.
Thanks for the help.