Cisco SDWAN controllers migrate from private to public IP addresses

[EminaBrkanic]

Hello,

I have a customer with on prem controllers. Controllers are using private IP addresses, and they are NATed to public. They had MPLS as one of the WAN connections but now they moved to Internet as both WAN connections. 

I want to have controllers with public IP addresses and to move from private. How can I perform this without downtime?

regards

[MHM Cisco World]

Without downtime I think this hard you need to do in maintenance window 

Note:- as I know if vedge loss connection to controller then traffic not effect except new prefix or policy not push until resolve the connection 

MHM

[Kanan Huseynli]

Hi,

if you dont have lots of controllers and you reserved newer public IPs for controllers, you may just try to build newer controllers (vbond and vsmart) add to your overlay network. You should see new vsmarts immediately. Point to newer vbond (if you use hostname in current configuration, then even better) and that's all.

Only vmanage is left (which is not easy to build newer just with copy-paste method), but it should not be problem if you lose network to vmanage.

Above is just generic approach based on my suggestion, depending on your topology,design order-steps can be defines in detail.

[EminaBrkanic]

Hi Kanan.

That is a good suggestion. I only have one controller of each. I think I have free public IPs. I will update with topology a little bit later, so any additional advice is more than welcome. I am planning migration on production and client is very important.

regards

[EminaBrkanic]

Hi,

Me again. A little late with response but..

V edges are communicating with controllers via public IPs, they do not have private addresses and MPLS anymore. 

All I want to do is to move a way form NAT on controllers and use only public IPs.

Now I have situation like in attachment. 

I do not have redundant controllers. is it possible to add redundant controllers and migrate somehow from private to public?