Latest Posts



Translate

Total Pageviews

Wednesday, 9 January 2013

Reserved or overhead ports for virtual switches


Details

To account for overheads such as physical NIC ports (uplinks), CDP traffic, and network discovery, ESX 3.x, ESX/ESXi3.5.x, and ESX/ESXi 4.x allocate and reserve an additional eight ports per virtual switch beyond what is available for virtual machine use. This additional overhead is allocated regardless of the number of ports on the virtual switch, and accounts for the most common product deployment scenarios.

Solution

Configuring a virtual switch from vSphere Client

When configuring a virtual switch from vSphere Client, the ESX machine provides available virtual switch port count, which already reflects the fixed overhead (8, 24, 56, 120, 248, 504, 1016, 2040, and 4088 available ports respectively).
 
Note: Only ESX/ESXi 4.x have 2040 or 4088 ports.
 
Configuring a virtual switch using esxcfg-vswitch command

When configuring a virtual switch using esxcfg-vswitch command, this overhead must be explicitly taken into account when specifying the total number of ports to allocate. Available port counts as displayed in vSphere Client need to be incremented by eight when working with esxcfg-vswitch command. 
 
vSphere Client esxcfg-vswitchTotal Ports
8168 virtual machine + 8 Reserved
243224 virtual machine + 8 Reserved
56*6456 virtual machine + 8 Reserved
120**128120 virtual machine + 8 Reserved
248256248 virtual machine + 8 Reserved
504512504 virtual machine + 8 Reserved
101610241016 virtual machine + 8 Reserved
2040***20482040 virtual machine + 8 Reserved
4088***40964088 virtual machine + 8 Reserved
 
* = System default for new virtual switches in ESX/ ESXi 3.x
** = System default for new virtual switches in ESX/ ESXi 4.x
*** = Only for ESX/ESXi 4.0
 
Note:  Certain higher-complexity product deployment scenarios might require more eight virtual switch ports for overhead.

Typically, each additional uplink connected to the same virtual switch beyond the first six uplinks reduces the number of ports available on that virtual switch for virtual machine use by one.

Deployment scenarios where a very large number of uplinks are teamed together on a single virtual switch might significantly impact the number of  ports on that virtual switch available for virtual machine use, and the overall size of the virtual switch might need to be adjusted accordingly.

The current port utilization data for virtual switches can be reviewed by using the esxcfg-vswitch --list command.

The current overhead utilization on a given virtual switch can be calculated by subtracting the Used Ports value for all PortGroups from the Used Ports value for that virtual switch.

Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008040