Ever wondered what prechecks are running when importing a vCenter into VCF9? Always wondered what might be a showstopper for an import? Guess you’re on the right blog 🙂
Imagine you have the following vSphere Environment:
- Multiple Standalone Hosts
- Dual Hosts in Clusters from Robo locations
- Multiple Datacenters with diverse configurations
- vmk0 on a standard vSwitch
- Aria Components that need to be migrated
How does something look like?
Apart from the fact that the legacy-esx-01 is red because Automation is hogging the vCPU it is kind of an interesting scenario especially as such robo sites or robo vCenters might come up more often, especially when there is a need to converge everything into a new WLD.
As of right now, the Hosts legacy-esx-03 till 06 are simply configured with their management IP. No Datastore, no VDS, no shared Storage, no local Storage, no NTP.
So what will VCF Operations 9 say if i’m gonna import such a WLD? Lets see 🙂
Go into VCF9 Opersions Inventory View, select your WLD where you wish to import that vCenter and click “Add Workload Domain –> Import vCenter”:
Follow the wizard trough each step:
And after checking the Thumbprint the first validation is going to happen with the following results:
This is simply a small post to show which prechecks are done against a vCenter and the Hosts. Maybe that is helpful for somebody 🙂