WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple

Does vCenter Server recycle VM MAC Addresses after Cross vCenter vMotion?

10.22.2021 by William Lam // 7 Comments

I recently received a question from a customer who was concerned that after a VM has been migrated from one vCenter Server to another using Cross vCenter vMotion, that the original source VM MAC Address could potentially be recycled and re-used at a later point. Back in 2015, I actually wrote about this very topic and the concerns around VM MAC Address duplication after a Cross vCenter vMotion, which I highly encourage folks to check out if you have not seen this article already.

While re-reading the article, I realized that the article had primarily focused on vCenter Servers that were in Linked Mode or under the same vSphere Single Sign-On (SSO) domain and although I did mention the Cross vCenter vMotion across across different vSphere SSO domains scenario, it looks like the details were a tad bit light.

To quickly summarize, when a VM is migrated from a source vCenter Server to the designation vCenter Server, the VM's MAC Address is added to a MAC Address "block list" on the source vCenter Server. This ensures that the VM MAC Address will not be reallocated by the source vCenter Server which would cause a network conflict. This has been the default behavior since vSphere 6.0 and no additional configuration change is required by customers.

[Read more...]

Categories // Automation, vSphere, vSphere 6.0, vSphere 6.5, vSphere 6.7, vSphere 7.0 Tags // Cross vMotion, mac address, xVC-vMotion

Minimum vSphere edition & features for Tanzu Community Edition (TCE)

10.13.2021 by William Lam // 7 Comments

There have been a number of questions that have been raised by the community regarding the specific vSphere features and/or editions that is needed to deploy Tanzu Community Edition (TCE). I honestly thought I knew the requirements quite well myself but when it came to specific vSphere Editions, it made me second guess on what features TCE actually required for functionality.

I decided to deploy a brand new setup using the latest vSphere 7.0 Update 3 (vCenter Server and ESXi) release, which was all deployed onto a single 11th Gen Intel NUC. Below are my findings which I will share back with TCE folks and enhance our documentation. Ultimately, you just need access to a vCenter Server that is managing an ESXi host which can be a standalone host or one that is within a vSphere Cluster. Hopefully this will be helpful for anyone that wishes to get started.

vSphere Version:

  • As the official TCE documentation states, vSphere 6.7 Update 3 or newer is needed and this is primarily because that is the initial release that incorporates our vSphere CSI driver

vSphere Edition (minimum):

  • vCenter Standard and vSphere Standard
  • vCenter Essentials and vSphere Essentials Plus

Note: I did not have access to a vSphere Essential license but I am pretty confident it should also work.

vSphere Features:

  • Both vSphere HA and DRS is NOT required

Categories // VMware Tanzu, vSphere 6.7, vSphere 7.0 Tags // Tanzu Community Edition

Quick Tip - Changing the size of vSphere Dump Collector for VCSA 6.7 & 7.0

06.01.2021 by William Lam // 3 Comments

When an ESXi host crashes, the generated core dump can be sent over the network to a remote core dump server. The vCenter Server Appliance (VCSA) can be configured as a destination by enabling the built-in vSphere Dump Collector service. By default, the storage repository for the vSphere Dump Collector service is configured to 2GB and can be increased up to 10GB, which is the supported maximum.

In earlier vSphere releases, configuring the vSphere Dump Collector repository size could be done using the vSphere Web (Flash) Client as shown in the screenshot below.

Configure and test of ESXi Dump Collector – Notes from MWhite
Screenshot courtesy from Michael White's blog post https://notesfrommwhite.net/2016/01/20/configure-and-test-of-esxi-dump-collector/

However, as part of the vSphere (HTML5) UI Client transition, it looks like all general VCSA service configurations including the vSphere Dump Collector was not ported over. I can only assume the reasoning for this was due to the infrequency configuring or updating these settings. This has been a question that has come up a few times across both VCSA 6.7 and 7.0 environments and I was recently reminded of the solution and I realized I had not blogged about the solution.

[Read more...]

Categories // vSphere 6.7, vSphere 7.0, vSphere Web Client Tags // Dump Collector

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • …
  • 11
  • Next Page »

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...