Simplivity Rapid DR

[thinhnguyen]

Dear All,

I have 2 site that linked toghether by Metrowan. The first site have already deployed simplivity cluster within 3 nodes (omni version 4.0.1 and vSphere 6.7). Now i want to build recovery site with Rapid DR so i deploy simplivity cluster within 3 nodes (omni version 4.0.1 and vSphere 6.7) at the second site , the second cluster same Federation with the first cluster. After deployed the second cluste, i connect uplink cable that is MPLS trunking between 2 sites, it will show the error on both of vcenter:

hpe simplivity plug-in cannot complete the task because it cannot contact the virtual controller

Thank you for your any help.

[Askey_15]

Hi @thinhnguyen ,

Thank you for choosing HPE.

Thank you for the detailed information. I will need additional information on top of this to have a clear picture.

1) Please make sure Port 9190 is open for the vCenter and OVC.

2) Open all the OVC Web Console within the vCenter and look for the duplicate IPs on the imapcted OVC if yes then you will need to open the Web console so that it refresh the IP details and post that you can close the session and check if you are still getting the Duplicate IPs

Please write back to us.

Regards,

Abhishek

[thinhnguyen]

Hi Abhishek,

I have 2 sites, each site have 1 cluster within 3 nodes and 1 vcenter so that mean i have 2 separate federation. The DC site layer 2 trunking with the DR site. If i use RapidDR software for DR solution, the rapidDR host have to see 2 vcenter at both of site or need to config more thing like vcenter linked mode, etc....

Beside that please see my IP table as below:

[gustenar]

@thinhnguyen 

In your first post you indicated you have both sites under the same federation in different clusters. To confirm, you also have one vCenter per cluster and each vCenter has its own Simplivity plugin installed? Also, are these two vCenters in Linked mode? The error that you are describing tells me that there is a communication problem between vCenter and the MVA acting as Event manager for that specific cluster. Make sure that the MVA is using the same management network that the OmniStack controllers are using in that cluster and that you can ping the MVA IP address from all OVCs in that cluster as first step. 

[hdribeiro]

Hi.

@thinhnguyen , any development on this topic?