VMware Cloud Community
mifrasmm
Enthusiast
Enthusiast
Jump to solution

VCenter HA Error

Hi

currently im Deploying vCenter High Availability with network addresses in separate subnets. I have configured passive & witness node and enable routing between.

     While im deploying last stage getting below error, Please let me know if any idea about this .

Thanks for helping

The operation is not allowed in the current stage

The management interface (NIC0) IP address does not map to the vCenter Server PNID.

I have verified my DNS ( REV/FWD ) resolve successfully

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
mifrasmm
Enthusiast
Enthusiast
Jump to solution

Above is sorted.

Error im went through.

1. The operation is not allowed in the current state.

   Failed to get management network information. Verify if management interface (NIC0) is configured correctly and is reachable.

Solution: Create DNS entry for passive node

2. Errors "Failed to ssh connect peer node x.x.x.x"

     Solution:  strictly follow the order to start the clone of Active node to create Passive and Witness VMs only after wizard reaches a certain point and asks user to start the clone operation

3. error message MethodFault.summary error during the finalization process

     Solution:  hostname mismatch

          you can verifying cat /etc/hostname all nodes should be same

View solution in original post

0 Kudos
14 Replies
asajm
Expert
Expert
Jump to solution

Hi mifrasmm

Check this VMware article

VMware Knowledge Base

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

asajm​ yes i did same as above KB. but still im getting this error

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Just a guess. Does the vCSA's hostname contain upper case letters?

Which vCSA version/build do you use?

André

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

initially we have configured with UPPERCASE but i have changed after that to lower case.

Version: 6.7.0.30000

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

... but i have changed after that to lower case

How did you do this? By modifying the existing vCSA (if so, how?), or by deploying a new one?

Please double-check that your DNS entries (forward, and reverse) also use lower case letters.

André

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

Hi Andre,

I just modified in /etc/vmware/systemname_info.json

DNS Entries fine both FWR/REV resolving

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Assuming that you rebooted the vCSA after editing the file, and https://kb.vmware.com/kb/2147932​ is still the valid for vCSA 6.7U2, that should be fine.

Maybe there are some log files which contain some hints.

André

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

Im getting this error while runing

root@UAENIP595VC01 [ ~ ]# /var/log/vmware/vcha/prepare-vcha

bash: /var/log/vmware/vcha/prepare-vcha: No such file or directory

root@UAENIP595VC01 [ ~ ]#

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Are there any log files in that folder (/var/log/vmware/vcha)?

André

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

root@UAENIP595VC01 [ ~ ]# cd /var/log/vmware/vcha/

root@UAENIP595VC01 [ /var/log/vmware/vcha ]# ls

checkLazyImportUpgrade.log  sshConnect.log  vcha-hacheck.log

destroy_vcha.log            vcha-1.log.gz   vcha.log

fixVchaConfigFiles.log      vcha-2.log.gz   vcha-scripts.log

prepare-vcha.log            vcha-3.log.gz   verify-postgres-setup.log

prestart-vcha.log           vcha-4.log      vmware-vcha.log

Log file

https://pastebin.com/4V7F1ekF

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Can you please compress/zip the log files and attach (see lower right of the reply window) them to a reply post?

André

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

a.p.​ no optio yo upload directly .

WeTransfer

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

Hey

is anything wrong on global gateway? showing vcenter HA gateway only?

Gateway.png

0 Kudos
mifrasmm
Enthusiast
Enthusiast
Jump to solution

Above is sorted.

Error im went through.

1. The operation is not allowed in the current state.

   Failed to get management network information. Verify if management interface (NIC0) is configured correctly and is reachable.

Solution: Create DNS entry for passive node

2. Errors "Failed to ssh connect peer node x.x.x.x"

     Solution:  strictly follow the order to start the clone of Active node to create Passive and Witness VMs only after wizard reaches a certain point and asks user to start the clone operation

3. error message MethodFault.summary error during the finalization process

     Solution:  hostname mismatch

          you can verifying cat /etc/hostname all nodes should be same

0 Kudos