Hi All,
Here is my scenario where I need some help. We have a legacy Vmkernel interface for storage and a newly created one. I'd like to retire
the legacy vmkernel interface but my storage team is telling me something is still utilizing it. How can I run a report against
all my datastores to show which vmkernel interface is establishing the connectivity?
Thanks.
What is this vmkernel interface used for in vSphere? How are they determining if it is being used?
Would this help?
$esxName = 'MyEsx'
$esx = Get-VMHost -Name $esxName
$iscsiMgr = Get-View -Id $esx.ExtensionData.ConfigManager.IscsiManager
foreach($iHba in Get-VMHostHba -VMHost $esx -Type iSCSI){
$iscsiMgr.QueryBoundVnics($iHba.Name) |
Select @{N='HBA';E={$iHba.Name}},
@{N='VMK';E={$_.VnicDevice}},
@{N='PG';E={$_.PortgroupName}},
@{N='VSS';E={$_.SwitchName}}
}
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Thanks Luc,
These are NFS volumes, I'm thinking i need it at the datastore level to determine where the connectivity is coming from, perhaps not..
How is that legacy VMKernel configured/defined for NFS?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
It's just a standard Vmkernel interface..
I understand, but how is it linked to the NFS based datastores?
Or is it just that NFS traffic runs over the IP addresses mapped on those VMKernel interfaces?
In that case, you could look at the routing tables, and with the IP address of the NFS server, you should be able to determine over which interface that NFS traffic runs.
Or am I missing something?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference