2016-09-25 08:25 AM - edited 2016-09-25 09:03 AM
To set up a ONTAP Cloud HA, three floating IP addresses are required, one of the management IP, and two for NFS/CIFS on each node. Further, all these three floating IP's have to be outside of all our VPC's.
Assuming the HA is configured in 220.127.116.11/24, then
1. Can I assign any IP's outside VPC's, for instance, 10.0.0.10, 10.0.0.11, and 10.0.0.12 for floating IP's.
2. If yes, then I can use 10.0.0.10 for mgmt access, correct?
3. Then how internally the floating IP's can be converted to HA node's IP? what routing tables would look like to support such converstion?
2016-09-25 09:07 AM
You should assign only IPs outside of VPC. As for the IPs themselves you need to "make them up".
The HA will edit the route table of that VPC (Those you select) to point the floating IPs at specific ENIs of the nodes.
In time of need these would be moved around (The tables edited on the fly to point at the other node ENI)
2016-09-25 12:10 PM
the issue here is that I am not able to bring up SM, and getting the following message in the browser.
I assigned 192.168.3.11, .12, and .13 to three floating's. Each node and mediator has it's own subnet, 18.104.22.168/24, 22.214.171.124/24, and 126.96.36.199/24. Do I need to configure proxy server in AWS?
The following is the screen shot when after I invoke System Manager in Menu options
This site can’t be reached
192.168.3.11 refused to connect.