OVH Community, your new community space.

Failover IP vs RipeBlock


skegyuk
04-07-2014, 08:53
Hi,

The RIPE block will be sequential e.g. 10.1.1.100 - .102 - .103 - .104 - .105 etc as for the FO will be random IP's.

Danny

heise
04-07-2014, 01:52
What are the differences between a RipeBlock of 16 IPs over 16 Failover IPs?

Update:
Advantage
-IPs are in sequence
-use vRack if it were supported in SYS

Disadvantage
-Your name gets published, you need abuse@
-You have to use (route) all IPs




Here is the mail you get when you order a Ripe-Block. It clarifies, what to expect:

Dear Customer,

Further to your request, we have just assigned a block of 16 IP
addresses that will be routed via 12.23.34.45(YOURserverIP):

1.2.3.160/28

You can use the IP addresses of this block in 2 ways:


1 - Configuration within a dedicated server


In this case, all IPs of your block 1.2.3.160/28 are usable.

Please use of one of the following guides for the configuration:

- If used in virtual machines: http://guide.ovh.com/BridgeClient.

- If used on the same interface network of your server: http://guide.ovh.com/AjouterAliasIp.

In general, all IPs must have the following netmask:
255.255.255.255, and the gateway is composed of the main IP of the server ending in .254


2 - Configuration within a virtual rack (vRack) or on a Dedicated Cloud offer


If you use this block in a virtual rack or a Dedicated Cloud, the following addresses must be freed up:

Network IP : 1.2.3.160
IP for router n°1 : 1.2.3.172
IP for router n°1 : 1.2.3.173
Gateway IP : 1.2.3.174 (not usable)
Broadcast IP: : 1.2.3.175

Then use the sub-netmask 255.255.255.240.


For your information, your block has the following characteristics:

1.2.3.160/28
Network IP :1.2.3.160
Broadcast IP :1.2.3.175
Gateway IP :1.2.3.174
Netmask :255.255.255.240


Kind regards,