HPE simplicity distributed using multiple base mva

[bmpark]

Good morning
I would like to inquire about the distribution of HPE SimpliVity.
Currently configured environment.
1 vcenter
2 data centers
15 clusters
60 to 70 Hosts
OVC 4.1.2 to 5.0.0

Both regional and ip bands vary by cluster.
Communication between ovc is unstable because it is an environment where a host is added from a vcenter in the center after distributing offline by region.

MVA has been installed in the current environment, and we are going to use it to redistribute it sequentially and reconfigure it. VMs are installed, so it is impossible to work after initialization, and we will redistribute them sequentially by region.

This is an inquiry.
Distribution was carried out using the simplicity deployment manager at the base, and communication tests are performed with specific ovc at a base other than MVA in the pre-distribution test, resulting in 22,80,443,9390,9190,22122 port errors.
Is there a reason to look at a specific ovc in a base other than mva in the distribution test? And is it possible to set it up?

There is a security issue about firewall opening between bases, so ovc is not currently communicated between bases.

[Joshua610 · Accepted solution]

Thank you for the time to investigate and gather supporting documentation. 

I have provided an explanation and documentation to assist with your query. Please review the following. 

In regards to ports for SimpliVity - please reference this guide as to see what & why each port is needed.
https://support.hpe.com/hpesc/public/docDisplay?docId=sv2849en_us&docLocale=en_US

SimpliVity requires proper communication amongst all variables within the environment in order to perform properly.

On this link you can see the communication "flow" within the SimpliVity federation as well as desired ports that allow this to be achieved. (Nice image provided)
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005173en_us&docLocale=en_US&page=GUID-37086374-F3AB-472C-BFBD-47218FCF186A.html

References regarding MVA:
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005173en_us&page=GUID-A2BD7BB4-7A99-4B00-90EA-4FC88A73CDF8.html
"When a federation is running as centrally-managed, the HPE OmniStack REST API is available using the Management Virtual Appliance IP address on port 443."

Prerequisites:
"The network selected for Management Virtual Appliance deployment must be able to communicate (routable) with all other Virtual Controllers (port 443) and vCenter Servers in the federation."
&&
"All clusters in the federation must be running the same HPE OmniStack version."
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005173en_us&page=GUID-ECBB5643-6092-4BC2-9C6F-C8FCE070322D.html

Troubleshooting steps for MVA located:
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005173en_us&page=GUID-B8DB4775-68D6-41CF-BF82-164D6194A613.html

All references are pulled from the Admin Guide:
Administration Guide
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005173en_us&docLocale=en_US

Please look through the provided documents in order to help assist. If after reviewing you still have further questions please let me know, thank you.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".