I was trying to perform a migration between our on-premises vSphere and VMC on AWS. I proceeded with logging into the SDDC, but it was missing all of the HCX information.
-No Bueno, but lucky a quick and easy fix. I decided to take advantage of this cool tool and transfer my notes into a blog. I hope it helps someone in need.
Issue:
- Haven’t logged into VMC on AWS in a while and HCX on the VMC on AWS side doesn’t show anything
Goal:
- Connect to the HCX Appliances and perform a test failover/migration
- Log into the on-premises vSphere client.
-
- I was able to see the HCX configuration.
-
- Beautiful red line up top tells us there’s an upgrade available
- Proceed to upgrade
- Beautiful red line up top tells us there’s an upgrade available
-
-
- Appliance will reboot
-
-
-
- Took about 15-20 minutes to complete
-
2. Log back into the SDDC
- Let’s see if we can see HCX now
Will be redirected to a new site
- Logged in using the cloudadmin creds.
- Nice, friendly banner up top.
3. Begin upgrade process as well
Success!
Successfully upgraded both sites and HCX is now visible. Ready for some migrations!
Resolution:
An upgrade was all that was needed, but I find it weird that I couldn’t even see HCX via the SDDC, but could see it on-premises.
*Note*
Be patient otherwise you will see this error message.
Error Message #2
SummaryError-(Server IP): Response with status: 500 Internal Server Error for URL: https://(vC FQDN)/ui/hcx/hcx-ui/rest/hybridity/api/replications?action=query&vcGuid=969411B5-8B4D-4622-9B14-6723B8793455
recep ivedik
Whoa. That was a fantastic short article. Please keep writing for the reason that I like your style. Devonna Udell Antipus
izle
Say, you got a nice blog article.Thanks Again. Great. Donny Tomasko
izle
I truly appreciate this article post.Much thanks again. Cool. Brooks Heinzle
woodrow salazar
Thanks so much for the blog post.Thanks Again. Great.
lindsay raz
Awesome article post.Much thanks again.
onita lascaro
I think it is a fluent sharing, I will recommend your site to my friends