upgrade to vcsa 7.0(b) - pre-checks alerts

[andvm]

Hi,

Got the attached alerts:

will I still be able to upgrade ESXi's to 6.7 using VUM (especially those which are not supported by 7.0)?

what does the https://unset extension relate to as this is not clear and could not find any related info?

Thanks

[scott28tt]

Moderator: Thread moved to the vSphere Upgrade & Install area, seeing as you're not asking a question about VCP.

[nirmalgnair]

Hi @andvm,

Not sure from which vCenter version you are trying to upgrade but going by the query I hope its 6.7.

The warnings that you have,

Regarding VUM, you can ignore as those are complaining about if at all you have some Custom Baselines, it won't be exported.

But yes you will be able to upgrade ESXi hosts to 7.0 provided they are supported.

Regarding the Extensions warning, we should not be seeing https://unset....!!!

But you can ignore that as well. If you have some third party applications you may have to check if those are supported with 7.0. If you are not sure about this you can check vCenter MOB page.

To check that open Browser and go to https://VCIPorFQDN/mob

If there is no 3rd party applications registered with vCenter and the hosts are compatible to go till 7.0, then you can ignore the warning and continue with the upgrade.

Regards,

Nirmal Nair

[andvm]

Hi,

Would I still be able to upgrade ESXi hosts to 6.7 (for those not supporting 7.0) via VUM once I upgrade to VCSA 7.0 ?

Does not seem that there are 3rd party extensions set so should be fine. Pre-check only shows the  https://unset/ which as I understand I can ignore.

Also seeing this from other post although I do not remember seeing this documented anywhere just by upgrading VCSA to 7.0

"Actually, vCenter 7 will REQUIRE vSAN7 licences. pre-vSAN6 licenses applied to clusters will become evaluation licenses and vSAN6 licenses cannot be applied after the vCenter upgrade"

Will do a backup via VAMI and take a snapshot of the old VCSA 6.7 before starting, let me know if I should consider any other steps?

Thanks

[andvm]

Upgrade to VCSA 7.0 worked but notice the below:

In Upgrade UI got message (at step: Starting VMware vCenter Server) to refresh as could not get progress status - did so but message persisted

Gave it some time and tried to login to the VCSA and it worked showing correct version, inventory etc.

In VASA, noticed that Backup schedules have not been migrated

VCSA was connected to standard switch port group, changed to distributed portgroup and connectivity remained ok as expected.

However I then went to restart the VCSA and connectivity did not restore after its restart.

VCSA connected DVS portgroup is static. Had to login to the ESXi host, change it back to standard port group to regain connectivity.

Does this mean that the VCSA needs to be connected to either an ephemeral portgroup or a standard portgroup so as to remove any dependency from the VCSA itself for port allocations?

Does this mean that any VM that is connected to DVS portgroup static and is restarted while VCSA is down would not get back network connectivity as there is a dependency on the VCSA to be available?

Thanks