A remote site on AWS has been configured earlier. The time sync drifted too far but that has been fixed.
The remote site in Data Protection has this alert "Remote site connectivity not normal." It is an AWS instance. The remote CVM IP address is 10.162.10.115. The host ipaddress is unknown, the firewall rules are fully open and replication seems to be occuring. There is a site to site VPN specificaly for this instance
It looks as though the aWS remote site was never configured with the local cluster as a remote site which is what most of the webinars and documentation suggest. The IP address will not open a web page on http or https, the only communication available to the AWS node is SSH.
How does the configurationof the remote site get completed or how do I get rid of this alert ??
NCC Version: 3.5.2
LCM Version: 1.4.2381
Nutanix 20170830.124 (in cluster, standard AWS instance)
Already have an account? Login
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Are you still facing the issue?
There is a potential that the issue might be related to VPN Configuration between the sites.
You can refer to the following document to configure the AWS site again, if you feel that there was a configuration issue
You can also perform the following health check to get more information regarding the remote site.
ncc health_checks data_protection_checks remote_site_checks run_all
Hope this helps!
For AWS I don’t think the cause would be the same. Those rules for reflective remote site configuration do not apply to cloud replication in the same way.
When the remote site is another AOS cluster, it is expected you may at some time have a VM running on that remote cluster which would need to replicate and then migrate to this local cluster.
When the remote site is AWS or Azure, configured on Prism Element using Cloud Connect, you only store snapshots there and would not be running on that site, thus we would not have any new data to replicate from AWS to the AOS cluster. The setup described at the link provided by
@HITESH0801 is the full process.
If you run the health check as described, it should give some more specifics on the nature of issue. It may be high ping latency or something else. That check, which is what generates the alert you described, runs through a few tests to determine if connectivity is normal, so the specific failure text from the health check will be helpful in identifying the cause.
For more detail, take a look at the KB article NCC Health Check: remote_site_connectivity_check which describes possible causes and steps to resolve.