Re-IP

VMware specific discussions

Re-IP

Veeam Logoby mtoms » Thu Oct 01, 2015 1:17 pm

Hi All,

Apologies in advance if this has been asked before.

I'm in the processing of planning the replication to a DR site and will need to utilise the Re-IP facility as the production site is on a different subnet to the DR site. What I want to know is if it is possible to restrict the replicas to use just a portion of the class c subnet rather than the complete range.

e.g. 192.168.1.200 to 192.168.1.220

The reason I want to control this is because I already have some other devices in use on that subnet.

TIA

Matt
mtoms
Influencer
 
Posts: 14
Liked: never
Joined: Mon Nov 17, 2014 12:47 pm
Full Name: Matt Toms

Re: Re-IP

Veeam Logoby v.Eremin » Thu Oct 01, 2015 2:12 pm

You can create individual rules, so that, VM in case of disaster will be assigned an IP address from a correct range. (you can also do it in automatic fashion, using PowerShell). Thanks.
v.Eremin
Veeam Software
 
Posts: 13255
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Re-IP

Veeam Logoby mtoms » Thu Oct 01, 2015 3:39 pm

Hi v.Eremin,

Thanks for the response but I'm not sure I follow. The Re-IP rules screen doesn't appear to allow you set a specific pool of IP addresses to use to assign to the replicas.

Can you provide an example of how to achieve this?

e.g. how can I set it so that the replicas are assigned IP addresses from a range between 192.168.1.10 to 192.168.1.20?

Thanks
mtoms
Influencer
 
Posts: 14
Liked: never
Joined: Mon Nov 17, 2014 12:47 pm
Full Name: Matt Toms

Re: Re-IP

Veeam Logoby v.Eremin » Fri Oct 02, 2015 11:34 am

I mean setting an individual rule (one per VM). Something like 192.168.0.2 -> 192.168.1.12, etc. As I've said, it can be done in automatic fashion with the use of PowerShell. Thanks.
v.Eremin
Veeam Software
 
Posts: 13255
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin


Return to VMware vSphere



Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 29 guests