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

Horizon DAAS Appliance deployment failure due to invalid IPV6 address conversion from the prefix-based MAC address (67120)

Last Updated: 1/19/2023Categories: TroubleshootingTotal Views: 4672Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In Horizon DaaS 8.0, appliances such as Secondary Service Provider, Resource Manager and Tenant deployment fail due to an invalid IPV6 address conversion from the prefix-based MAC addresses.

In the desktone.log file, the following entries can be seen.

2019-01-23 04:40:17,359 WARN [com.desktone.vmgr.desktopfactory.vmware.vcenter.DesktopFactoryVCenterImpl]-[pool-127-thread-1] Unable to establish connection with new VM at address 'fe80::168bb:ccff:fedd:ba2d%eth1', could possibly be due to invalid ethernet cards; result: ProcessResult com.desktone.util.ProcessUtil$ProcessResult@607ea7cb
exitValue = 255
stderr = [ssh: Could not resolve hostname fe80::168bb:ccff:fedd:ba2d%eth1: Temporary failure in name resolution]
stdout = []

Under Reservations, you will notice that the task fails at around 45%

Cause

MAC address to IPV6 address conversion logic has an issue.

Appliance can't be deployed when it is configured with prefix-based MAC address allocation
.It will work for some of the mac addresses for which the hexadecimal and binary value of the first octet will be the same post 6th bit inversion.

For example: The following mac addresses will work as the hexadecimal and binary value of first octet will be same post 6th bit inversion.

a) 00:05:69
b) 00:0C:29

Resolution

This issue has been fixed in 8.0.1 release.
Horizon DaaS 8.0.1 Release Notes

Users were not able to deploy the secondary service provider appliance (SP2) because the IPv6 address was not being generated correctly from the MAC address. This has been fixed so that the IPv6 address now generates correctly and the deployment occurs as expected. [2213658]

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon DaaS On Premise Platform

VMware Horizon DaaS

VMware Horizon

Related Versions:

VMware Horizon DaaS On Premise Platform 8.0.x

Take Our Survey

Support Assistant