Let us learn more on the vultr floating ip with the support of our Vultr support services at Bobcares.

Floating IP in Vultr

A floating IP address is one that may be readily transferred or moved between instances or servers inside the Vultr architecture.

It increases flexibility and convenience for managing cloud infrastructure. This is how it works:

1. Static Public IP:

   When we establish a VPS or instance on Vultr, we assign it a dynamic public IP address by default. If the instance is stopped, restarted, or transferred, the IP address may change.

   However, maintaining a static IP address is advantageous for certain use cases, particularly when we need to keep a constant IP for services such as hosting websites or running specialized apps.

2. Floating IP Assignment:

   We may allocate a static IP address to a specific instance or server in the account using Vultr’s Floating IP functionality.

   As it is readily relocated or reassigned to a new instance inside the Vultr account, this IP address becomes a “floating” IP address.

3. Portability and High Availability:

   We may use the Floating IP to rapidly move the given IP address to another server in the Vultr account.

   This capability is very beneficial in circumstances when we need to ensure that the services or applications are always available.

   If one server fails, for example, we can immediately change the Floating IP to a backup server, reducing downtime.

4. Simple Management:

   To administer the Floating IP capability, Vultr provides a user-friendly UI and API.

   Through the Vultr control panel or programmatically using the API, we may simply associate, dissociate, or reassign a Floating IP to other instances.

5. Usage Cases:

   Floating IPs are commonly used for load balancing, failover settings, and smooth migration.

   We may spread incoming traffic over different servers for load balancing by utilizing a load balancer and linking it with the Floating IP.

   In the event of a server failure, the Floating IP may be routed to a backup server for seamless failover.

   Furthermore, if we need to move your services to a different server or data center, we may change the Floating IP to the new server to minimize service disruption.

Test the Floating IP

Check that BIRD is advertising the route to the floating IP address.
# birdc show route
BIRD 1.6.8 ready.
192.0.2.2/32 dev dummy1 [direct1 20:58:21] * (240)

To test launch two terminal windows. The session linked to the server will be referred to as the SSH session, while the session at the local workstation will be referred to as the Local session.

Ping the Reserved IP address in the Local session. We should get some responses.

$ ping 192.0.2.2
64 bytes from 192.0.2.2: icmp_seq=12 ttl=44 time=42.863 ms
64 bytes from 192.0.2.2: icmp_seq=13 ttl=44 time=49.471 ms
64 bytes from 192.0.2.2: icmp_seq=14 ttl=44 time=42.547 ms
64 bytes from 192.0.2.2: icmp_seq=15 ttl=44 time=43.489 ms


Remove the fake interface from the SSH session. Rep this step for each time.

# ip link set dummy1 down

Pings will start to fail in the Local session.

Request timeout for icmp_seq 68
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71


After that check the the route again in the SSH session.

# birdc show route

BIRD recognizes that the UI has vanished and cancels the route. To verify, run this command on all instances. Enable the dummy1 interface on only one instance of the SSH session.

# ip link set dummy1 up

The pings have resumed in the Local session.

64 bytes from 192.0.2.2: icmp_seq=82 ttl=44 time=42.863 ms
64 bytes from 192.0.2.2: icmp_seq=83 ttl=44 time=49.471 ms
64 bytes from 192.0.2.2: icmp_seq=84 ttl=44 time=42.547 ms
64 bytes from 192.0.2.2: icmp_seq=85 ttl=44 time=43.489 ms


Remove the dummy1 interface from the specified instance. Pings will start failing again in the Local session.

Repeat these instructions for each instance. Pings on the floating IP will continue once each instance becomes accessible. Repeat the testing until we are confident that the floating IP is operating as expected.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now seen more on how to set up the vultr floating ip with the support of our tech support team.