FQDN mismatch issues

[akapinos001]

I'm receiving the following error during upgrade:

The source appliance FQDN VCENTERVDIDEV.AD.XXX.XXX must be the same as the source appliance primary network identifier vcentervdidev.ad.XXX.XXX.

Obviously they appear the same FQDN but one is capitalized while the other isn't. I worked with vmware support to change the PNID to all caps, which seemed to work, but it still gave this error. I have a case open but I'd like to know if anyone here has any ideas on how to manage this error. Thank you for any and all help.

[VMAKS · Accepted solution]

Hi akapinos001,

Hope you are doing well.

Thank you for posting your query.

Regarding the error:
The source appliance FQDN VCENTERVDIDEV.AD.XXX.XXX must be the same as the source appliance primary network identifier vcentervdidev.ad.XXX.XXX

Please follow the below and let me know the outcome:

SSH into source VCSA and make the following changes after non-memory, non-quiesced snapshot of the vCenter VM(and PSC if it is external), before implementing any change.

/opt/vmware/share/vami/vami_config_net changed hostname to vcentervdidev.ad.XXX.XXX
Start Stage 2 of Upgrade

Note: This issue happens for case mismatch for upper & lower case.

Regards,
Arun Kumar Sharma
Install / Upgrade
VMware

[spendlet8801]

I tried this except the view the configuration [Option 0] already shows it as all lowercase exactly like it is referenced in name resolution.   However during the upgrade process the installer sees it as a difference between vCenter and vcenter.  I can't figure out where the one with the capital C is configured. 

FQDN:  vcenter.mydomain.com

Source appliance network indentifier: vCenter.mydomain.com

[spendlet8801]

I ended up doing this in the shell

/usr/lib/vmware-vmafd/bin/vmafd-cli set-pnid --server-name localhost --pnid vcenter.mydomain.com

[shivaraj24v]

The resolution is to Go to vCenter Advance settings and search for FQDN. and compare the FQDN with the hostname. If there is a difference just update the Advance setting FQDN as same as Hostname.

[DerekPease]

Spendlet

which system did you do this on?  The source or the destination?

[pkvmw]

Hi @DerekPease ,

the error occurs during the upgrade pre-check and also doesn't allow to proceed, hence there's no real destination VCSA at this point. So to answer your question: You'll need to change the PNID/FQDN on the source VCSA, before initiating the upgrade.

Regards,
Patrik