Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

In an NSX-T environment cloned VMs are unable to connect to the network (59444)

Last Updated: 2/27/2024Categories: Known IssueTotal Views: 16507Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

In an NSX-T environment the following symptoms are observed:

A newly deployed VM cannot connect to the network.

The VM deployment mechanism involved a clone operation. This could be a manual deployment or from an automated provisioning platform/tool such as vRealize Automation.

The following errors are seen in the ESXi logs:

hostd.log:
2019-01-21T17:41:21.912Z info hostd[11D81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 118 : Error message on vm on esxi in ha-datacenter: Failed to connect virtual device 'Ethernet0'.

vmware.log:
2019-01-21T17:41:21.769Z| vmx| I125: VMXNET3 user: failed to connect Ethernet0 to network 0d95a802-1dc8-4434-94fb-a7fc95ebf663.
2019-01-21T17:41:21.769Z| vmx| I125: [msg.device.badconnect] Failed to connect virtual device 'Ethernet0'.

vmkernel.log
2019-01-21T17:41:21:52.209Z cpu20:683363 opID=55b9b200)NetPort: 3203: blocking traffic on DV port ad9ecc75-87a8-4997-b9c8-48cb2921b7d7
2019-01-21T17:41:21:41.326Z cpu218:696440)NetPort: 3203: blocking traffic on DV port ad9ecc75-87a8-4997-b9c8-48cb2921b7d7

net-dvs output on the ESXi shows the port as blocked

com.vmware.common.port.block = true , propType = POLICY

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

The vmx file, which is the configuration file of a VM, contains information about how that VM connects to the network.
In an NSX-T environment you will see entries similar to this sample output:

ethernet0.externalId = "9286ab5d-a342-41e0-9623-9a027c67c466"
ethernet0.opaqueNetwork.id = "0d95a802-1dc8-4424-94fb-a7fc95ebf653"
ethernet0.opaqueNetwork.type = "nsx.LogicalSwitch"

“opaqueNetwork.id” is the UUID of the NSX logical switch
“externalId” is the UUID of the VIF that the VM is using to connect to the logical switch

Whenever a VM connects to an NSX logical switch, the VIF and switch ID are stored in the vmx file.
Each VM vNIC should have a unique VIF.
There is a known issue in vSphere that results in a VM’s VIF not being removed during vNIC edits or clone operations.

This results in the new VM using the same VIF in its vmx file as an existing VM.

When VMs with the same externalId/VIF connect to the logical switch, the switch will think it is the same VM and attempt to connect them to the same switchport.
Only one vNIC can be connected to a switchport and therefore only one VM will be able to connect.

Resolution

The issue is resolved in:

ESX 6.5, Patch ESXi650-201811002 available at VMware Patch Downloads. For more information on downloading patches, see How to download patches in Customer Connect (1021623).

ESXi 6.7 Patch ESXi670-201901001 available at VMware Patch Downloads. For more information on downloading patches, see How to download patches in Customer Connect (1021623).

Workaround

To workaround the problem:

Before using any VM or VM template as a source for cloning:

Power off the VM.

Edit the vmx config file.

Delete the line “ethernetN.externalId”, where N is the vNIC number.

This will prevent any cloned VMs getting the same VIF.

For existing VMs that are having the problem:

Power off the VM.

Edit its vmx file and delete the line “ethernetN.externalId”, where N is the vNIC number.

Note: it is safe to remove all the lines that have “ethernetN.externalId” when a VM is powered off.
When the VM is powered on again, a new unique VIF will be created for any vNIC that connects to a NSX logical switch.
The new VIF will then be written back to the vmx file.

Related Information

The same behavior will occur if any third party software which is copying a vmx file during a clone or backup does not remove pre-existing “ethernetX.externalId” information, which is unique to the original VM.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vSAN 健全性サービス - クラスタの健全性 - 再同期操作の調整 (2149504)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center

Take Our Survey

Support Assistant