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

VCHA deployment fails with error: Verify if management interface (nic0) is configured correctly and is reachable (56980)

Last Updated: 11/8/2023Categories: TroubleshootingTotal Views: 12347Language:
Chinese (Simplified)English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Deploying VCHA might fail if DNS lookup fails

In vpxd.log files you will see entries similar to:

2017-11-24T12:23:48.322Z warning vpxd[7FCAC9CB9700] [Originator@6876 sub=VpxProfiler opID=EventManagerProcessJobs-5a8c4936] EventManagerProcessJobs [TotalTime] took 30000 ms
2017-11-24T12:24:20.700Z error vpxd[7FCAC95AB700] [Originator@6876 sub=vpxUtil opID=ConnectionIpSettingsPageMediator-validate-59588-ngc:70004751-ad] /usr/bin/python failed with error [1] and output [Traceback (most recent call last):
--> File "/usr/lib/vmware-vcha/scripts/ifaces.py", line 235, in <module>
--> main()
--> File "/usr/lib/vmware-vcha/scripts/ifaces.py", line 223, in main
--> ifaceInfos = getIfaceInfo(iface, skipResolveOpt)
--> File "/usr/lib/vmware-vcha/scripts/ifaces.py", line 164, in getIfaceInfo
--> vchaIp, vchaFqdn = iputil.getIpFqdnForEth0(skipResolveOpt)
--> File "/usr/lib/vmware-vcha/scripts/iputil.py", line 200, in getIpFqdnForEth0
--> raise Exception('Unable to get hostname resolved IP address for eth0')
--> Exception: Unable to get hostname resolved IP address for eth0
--> ]
2017-11-24T12:24:20.700Z info vpxd[7FCAC95AB700] [Originator@6876 sub=vpxLro opID=ConnectionIpSettingsPageMediator-validate-59588-ngc:70004751-ad] [VpxLRO] -- FINISH task-699
2017-11-24T12:24:20.700Z info vpxd[7FCAC95AB700] [Originator@6876 sub=Default opID=ConnectionIpSettingsPageMediator-validate-59588-ngc:70004751-ad] [VpxLRO] -- ERROR task-699 -- FailoverClusterConfigurator -- vim.vcha.FailoverClusterConf
igurator.prepare: vim.fault.InvalidState:
--> Result:
--> (vim.fault.InvalidState) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "com.vmware.vim.vcha.error.invalidFailoverNicConfig",
--> arg = <unset>,
--> message = <unset>
--> }
--> ]

Cause

vCenter HA is failing to resolve the vCenter hostname during the initial configuration of HA.

Some reasons for this failure could be:

TCP connections are blocked between vCenter and DNS.

The appliance has a mixed case hostname.

DNS reverse lookup is not working properly.

Hostname is set to localhost.

Resolution

This is a known issue.

Currently, there is no resolution.

Workaround

To workaround this issue, ensure that DNS requests using TCP are allowed between the VCSA and its DNS servers.

Make sure forward and reverse lookup are resolving without timeout.

Verify network settings by running /opt/vmware/share/vami/vami_config_net.

Make sure that there is no block on TCP to DNS server. Run the following command on the vCenter Appliance:

/usr/bin/host -v -W 30 -T <ip of DNS>

Example:
/usr/bin/host -v -W 30 -T 192.168.1.10
-T corresponds to TCP packets to DNS

Verify if the initial HA startup script will run with TCP by running the following script:

cd /usr/lib/vmware-vcha/scripts​

python -c 'import iputil; print iputil.getIpFqdnForEth0()'

Example output

('192.168.0.11', 'vc.mydomain.org')

If your vCenter is a later version of 6.7, or 7.X (these builds use Python v3, earlier versions use Python v2)
The Python command syntax needs to be as follows:
python -c 'import iputil; print(iputil.getIpFqdnForEth0())'

If you get the following syntax error, you are using the incorrect older Python syntax for the command where the VCSA has  Python v3.

File "<string>", line 1
import iputil; print iputil.getIpFqdnForEth0()
^
SyntaxError: invalid syntax

If you get error as below, then you need to enable blocked ports on the firewall.

Traceback (most recent call last):

File "<string>", line 1, in <module>
File "iputil.py", line 200, in getIpFqdnForEth0
raise Exception('Unable to get hostname resolved IP address for eth0')
Exception: Unable to get hostname resolved IP address for eth0.

Once you are able to get the connection succeeded to DNS, the HA deployment should work.

Related Information

This can be also an error for DNS reverse lookup is not working properly.

2022-08-13T10:05:21.025+01:00 error vpxd[06414] [Originator@6876 sub=vpxLro opId=590b2054-cfc2-4473-9b76-5dec9c8dc379] [VpxLRO] Unexpected Exception: N3Vim5Fault12InvalidState9ExceptionE(Fault cause: vim.fault.InvalidState
--> )
--> [context]zKq7AVECAQAAADx5MwEYdnB4ZAAAnuk3bGlidm1hY29yZS5zbwAAV4ksANV8LQC7+TKByewHAWxpYnZpbS10eXBlcy5zbwCBc/0HAYGVcQgBAe9064LqayQBdnB4ZACCe2wkAYKrhCIBgq2UIgGCDMwiAYJHMiMBgmuVYAGCrJZgAYLapWABgj3TXwGCCH1gAQDnWiMAj7AjAFx1NwOHfwBsaWJwdGhyZ
WFkLnNvLjAABA82D2xpYmMuc28uNgA=[/context]
2022-08-13T10:05:21.030+01:00 error vpxd[06414] [Originator@6876 sub=FailoverClusterOperator opId=590b2054-cfc2-4473-9b76-5dec9c8dc379] Exception: N5Vmomi11MethodFault9ExceptionE(Fault cause: vim.fault.InvalidState
--> )
--> [context]zKq7AVECAQAAADx5MwEPdnB4ZAAAnuk3bGlidm1hY29yZS5zbwAAV4ksANV8LQC7+TKBmRwlAXZweGQAgbeWYAGBbplgAYEcpmABgT3TXwGBCH1gAQDnWiMAj7AjAFx1NwKHfwBsaWJwdGhyZWFkLnNvLjAAAw82D2xpYmMuc28uNgA=[/context]
2022-08-13T10:05:21.032+01:00 info vpxd[06414] [Originator@6876 sub=vpxLro opId=590b2054-cfc2-4473-9b76-5dec9c8dc379] [VpxLRO] -- FINISH task-603408
2022-08-13T10:05:21.032+01:00 info vpxd[06414] [Originator@6876 sub=Default opId=590b2054-cfc2-4473-9b76-5dec9c8dc379] [VpxLRO] -- ERROR task-603408 -- Datacenters -- com.vmware.vcenter.vcha.cluster.deploy: vim.fault.InvalidState:
--> Result:
--> (vim.fault.InvalidState) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcha.error.unresolvedFailoverIp",
-->          arg = <unset>,
-->          message = <unset>
-->       }
-->    ]
-->    msg = ""
--> }
--> Args:
-->

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
升级 vCenter Server Appliance 6.7 时：“添加用户失败：cm to group: cis”、“PAM：身份验证令牌不再有效” (55863)

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

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:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant