VIPR Controller: Discover ESX host clusters, then add vCenter Later

Hi Heather,

if credentials is your only Query, The admin should be fine. You can also ignore the discover by unchecking the discover option.

Once the Vcenter is ready, The Vcenter would automatically pull the host details into ViPR Controller and its clusters and its datastore info too.

Thanks,

Sathyaprakash Mohandass

hi Sathyaprakash,  thank you for your reply,

I added 2 ESX MGT hosts from a chassis manually as type ESX, however I was not able to provision storage to them via VIPR C, either via Create Volume for VMware, error is:

This service is missing required data. This could be caused by:

• No Options available for field: vCenter
• Required assets (Host, Switches, Storage Arrays) are not defined or you do not have permission.
• The system is busy discovering assets (Host, Switches, Storage Arrays).
• Unable to connect to a ViPR backend server.

I'm looking into this, but not sure how to correctly add individual ESX hosts.

The aliased HBA WWN's do not show up in the Fabric Manager switches.

VIPR is able to see and provision to other hosts, I have an authentication provider for the domains.

Hi Heather,

When you added your ESX Host to vipr-c, I assume it was from the Physical->Host screen (with type ESX), Correct?

Did you manually add the initiators to it?

What is its status when you view it from Physical->Host screen?

Do you have any existing vCenters?  Maybe you could use an existing vCenter and migrate it to your new vcenter when it is created.  If you think this may be an option, please make sure you read this KB first:

524225 : ViPR Controller: How to migrate an ESX cluster from one vCenter to another while retaining the existing storage. https://support.emc.com/kb/524225

I hope this helps!