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

"The source machine hostname '192.168.0.1' resolves to IPv6 address(es) '::ffff:192.168.0.1', but IPv6 networking will not be preserved after the upgrade" while upgrading VCSA 6.5/6.7 fails at precheck (76327)

Last Updated: 3/26/2024Categories: TroubleshootingTotal Views: 10964Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vCenter Appliance 6.5 to 6.7 Upgrade is stuck at Stage 2 at Pre-Checks

vCenter is deployed using IP as PNID

IPv6 is disabled on vCenter

Error stack seen in PreChecks stage on Phase 2 where IP of vCenter is 192.168.0.1:

"Error:
The source machine hostname '192.168.0.1' resolves to IPv6 address(es) '::ffff:192.168.0.1', but IPv6 networking will not be preserved after the upgrade. This will prevent certain services preferring IPv6 from establishing network communication.
Resolution
Either remove the DNS IPv6 entry for hostname '192.168.0.1' or change the network configuration of the source machine to pure IPv6 or in case dual networking stack is needed, set a static IPv6 address."

Command below return values with both ipv4 and ipv6 format (::ffff:IP)

[email-masked] +short VC_IP A VC_IP AAAA
for example below command returns DNS information from localhost:
dig @127.0.0.1 +short 192.168.0.1 A 192.168.0.1 AAAA
for example below command returns DNS information where DNS is 192.168.0.100:
dig @192.168.0.100 +short 192.168.0.1 A 192.168.0.1 AAAA
192.168.0.1
::ffff:192.168.0.1

Cause

Upgrade scripts checks for IPv6 resolution and if seen it will check for configuration of IPv6 on vCenter side. If it's not enabled, it will fail with above error.

Resolution

As stated, resolution is from the error stack:

Either remove the DNS IPv6 entry for hostname '192.168.0.1' or change the network configuration of the source machine to pure IPv6 or in case dual networking stack is needed, set a static IPv6 address.

As per above the options are:

Configure DNS without IPv6 information or

Configure the vCenter to have also IPv6 information

Workaround

Steps to workaround the pre-check:

Add required static IP addresses into /etc/hosts file (all VC and PSC's needed)

Comment (hash) DNS servers in /etc/resolv.conf

Restart dnsmasq service by using systemctl restart dnsmasq.service

Retry the prechecks page which should now allow you to go to next page

Add/enable DNS servers back in /etc/resolv.conf by removing the hash sign

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
适用于 vRA 8.0.0 HA 环境的修补程序解决了阻止某些服务在数据库故障切换事件后恢复的问题 (76222)

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

KB
•
vRealize Automation 7.x での Internet Information Services (IIS) アプリケーション プールのリサイクルの無効化 (76333)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant