Cloud Volumes ONTAP

Tthree floating IP's in setting up Cloud OnTap HA?

heightsnj

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 172.12.0.0/24, then

 

My questions:

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?

 

 

 

 Thanks!

3 REPLIES 3

yaronh
Are you inside the VPC? More precise is the machine you are browsing from is in a subnet whose route table has the floating IPs? Please check

yaronh

Hi,

 

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)

 

Yaron

heightsnj

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, 172.12.0.0/24, 172.12.20.0/24, and 172.12.40.0/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.

Try:

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public