Hyperflex 3.0(1e) Nested VCenter Install Bug

I recently had to deploy a hyperflex cluster for a client, which was for a DR site.  The cluster was going to use an nested VCenter, meaning VCenter is within the hyperflex cluster itself.  There is some official documentation from Cisco on this, and it seems pretty straight forward.

https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/TechNotes/Nested_vcenter_on_hyperflex.html#reference_8EF12C954D6049E285F924713804F9B6

However I ran into a few issues...

First during the installer, I received an error """INTERNAL_ERROR: something went wrong in executing scripts"

I found the following Cisco Bug article: CSCvk07339

I didn't have the option of using a temporary external vcenter, this was a remote DR site with only the hyperflex hosts and networking equipment available.  Instead I put a fake vcenter cluster name, as mentioned as one of the workarounds.

The install went thru fine, or so I thought.  When I tried to login to HX Connect webpage I received the following error:

Error: no cluster was created


I connected to the storage cluster vip via ssh and checked the cluster health, it was online and healthy.

I decided to create a datastore via cli and did so:

stcli datastore create --name VCENTER --size 500 --unit gb

The datastore showed up on all three of the esxi hosts, so I went ahead and connected to one and deployed the vcenter appliance.  I also created a datacenter and vcenter cluster name. 

I then added all my hyperflex hosts to the vcenter cluster.

After all the hosts were deployed I then reregistered the storage cluster using the following command:

stcli cluster reregister --vcenter-datacenter <DC Name> --vcenter-cluster <Cluster Name>  --vcenter-url <URL or IP of vCenter> --vcenter-user <admin username>

All this worked, and I was able to log into HX Connect again, only issue now is that the cluster was show as being in "An Invalid State".  Great!!!!

The fix was simple, I ran:  

stcli cluster start

And we are good to go....  I hope this has helped you!  

 

Comments

Post a Comment

Popular posts from this blog

Introduction - Exchange 2010 Post Patch CAS Array Errors

Image
Hello Fellow System Engineers... I Hope this blog will help with those hard to find answers... Every once in awhile google fails you.... It is my mission to save your kiester from staying up all night, losing data and damaging your forehead from the dreaded face-plant keyboard smash... we all hate that don't we... This is a collection of the most annoying and difficult problems I have faced, (or will be facing!?) during my IT consultant tenure... You name it, I've probably blundered my way through it... I hope this blog saves you from some of the long nights I had to endure.. Post Exchange Service Pack Upgrade - CAS Server Connectivity Issues I ran into this wonderful issue last night... turned a 2 hour quick Exchange 2010 SP1 to SP3 upgrade into a 4 hour nightmare.. well ok it wasn't so bad.. but it still annoying that microsoft always goofs up exchange updates.. After applying the sp3 patch to both servers in the CAS array we decid...
Read more

"WE COULDN’T COMPLETE THE UPDATES. UNDOING CHANGES" HYPER V 2012 R2 ERROR

Image
Microsoft strikes again... another thoughtfully laid out patch that set my project back close to 16 hours. I am sure you are here because you are desperately trying to figure out why the first few VM's you have tried to build and patch on your 2012 R2 Hyper-V cluster are all stuck.   I would assume you see this wonderful message, and its been HOURS, maybe DAYS and there is no movement.  You probably have even built a new VM and started over thinking it was some sort of weird fluke.. or perhaps there is an issue with your shared storage.. Well no, you did nothing wrong.  The issue is that you chose to use Hyper-V Gen 2 and there is a patch [ KB2920189] t hat does not play well with Gen 2 VMs and SECURE BOOT . So to get around this problem, Power off the VM, its never going to finish.  Go into boot settings and then disable Secure Boot. Now power back on the VM, you will see the same error message, but this time it will go through.  It wi...
Read more