Get-VirtualSwitch - NumPortsAvailable Question

[jt30605]

When i run the get-virtualswitch cmdlet, the output for NumPortsAvailable is completely wrong. Am I missing something?

Example:

One of my hosts returns this for vSwitch1

Name : vSwitch1

NumPorts : 64

NumPortsAvailable : 61

I know the NumPorts is 64 instead of 56 due to the 8 reserved, but the NumPortsAvailable shows that I'm only using 3 ports on this vSwitch. In fact, there are 46 ports being used on this vSwitch.

Anyone have any idea why the NumPortsAvailable value is so off?

[LucD]

We seem to have had a similar report some months ago, see Get-VirtualSwitch available ports wierdness.

But there was no solution, the problem apparently went away after some time.

[jt30605]

Well that sucks. I wanted to use it as part of a daily report, guess I'll leave that info out.

[LucD]

Did you try the advises from the other post ?

Does esxcfg-vswitch -l also return wrong numbers ?

And what does the vCenter client show ?

[jt30605]

Running esxcfg-vswitch -l returns the correct values. I ran the code snipet from the other post and got the same incorrect numbers. The networking tab in the vCenter client looks fine.

[LucD · Accepted solution]

Can you give the following script a go and check if it changes anything ?

$esxName = <ESX-hostname>
$esx = Get-VMHost $esxName | Get-View

$netSys = Get-View $esx.ConfigManager.NetworkSystem
$netSys.RefreshNetworkSystem()
$esx.UpdateViewData()

$esx.Config.Network.Vswitch | %{
	Write-Host "vSwitch" $_.Name "Port#" $_.NumPorts "Available" $_.NumPortsAvailable
}

This script is similar to using the panel in the vSphere client.

[jt30605]

I ran this today and got the same incorrect values. It then occured to me that I had not updated PowerCLI since updating my host to U1. I updated the PowerCLI and the issue is now fixed. Guess I should have thought of that first. Thanks for all of your help with this LucD.

[timparkinsonShe]

I was the person who posted the other thread. Actually the problem went away and then came back again. I just gave up on it. Maybe I'll try an updated PowerCLI on the machine that was generating the report I was trying to run.