• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Network loss after HA initiated failover

Duncan Epping · Mar 25, 2010 ·

I had a discussion with one of my readers last week and just read this post on the VMTN community which triggered this article.

When you create a highly available environment take into account that you will need to have enough vSwitch ports available when a failover needs to occur. By default a vSwitch will be created with 56 ports and in general this is sufficient for most environments. However when two of your hosts fail in a 10 host cluster you might end up with 60 or more VMs running on a single host. If this would happen several VMs would not have a vSwitch port assigned.

The most commonly used command when creating an automated build procedure probably is:

esxcfg-vswitch -a vSwitch1

This would result in a vSwitch named “vSwitch1” with the default amount of 56 ports. Now it is just as easy to set it up with 128 ports for instance:

esxcfg-vswitch -a vSwitch1:128

Always design for a worst case scenario. Also be aware of the overhead, some ports are reserved for internal usage. You might want to factor in some additional ports for this reason as for instance in the example above you will have 120 ports available for your VMs and not the 128 you specified.

Related

Server dvswitch, ESX, esxi, ha, networking, Scripting, scripts, tips, vSphere, vswitch

Reader Interactions

Comments

  1. afokkema says

    25 March, 2010 at 16:47

    Or you can use the following command:

    /usr/bin/vmware-vim-cmd hostsvc/net/vswitch_setnumports vSwitch1 128

    if you want to use vmware-vim-cmd 😉

  2. Bouke Groenescheij says

    25 March, 2010 at 16:55

    I just don’t get why VMware still defaults it to 56? These days virtualisation ratios are getting higher and higher. The thing what I’m also missing is the impact of choosing a higher amount of ports other than than the total amount of configurable switches. Is a 56 port switch faster then a 120 one? Why not just configure 2040 or 4088 ports???

  3. Jason Boche says

    25 March, 2010 at 17:06

    Another hidden gotcha here is that changing the number of ports on a vSwitch after it is created requires a host reboot which will then put the cluster at N-2.

    Cascading impacts – DOH!

  4. Duncan Epping says

    25 March, 2010 at 18:34

    @Bouke you could do that if you are sure you will keep the same amount of vSwitches. As you know a host is “limited” in the amount of vSwitch / vDS ports it can have… But I agree. You could easily use a higher number without causing any issues. It is not going to be slower etc.

  5. PiroNet says

    26 March, 2010 at 19:28

    Hi Duncan, don’t you have any sort of buffer(s) attached to the vSwitch that you may need to increase if you add more ports to it?

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Also visit!

For the Dutch-speaking audience, make sure to visit RunNerd.nl to follow my running adventure, read shoe/gear/race reviews, and more!

Do you like Hardcore-Punk music? Follow my Spotify Playlist!

Do you like 80s music? I got you covered!

Copyright Yellow-Bricks.com © 2026 · Log in