IP Forwarding

[NuhumanMohammad44256]

Ho office application server (local network ip assigned) will be shifted to data center, post this whenever branch location user try to access application server which was there at HO traffic should be redirected DC local network IP.

Connectivity available from Head office to Data center through static route with Head office's all local IP subnet.

is it possible to do IP forwarding whenever request comes to Head Office local network application server ip, ....packet should forward to Data center local network IP

[TJ-20933766]

You could use Network Address Translation so that when users attempt to go to the old address of the server, the router will simply translate the destination to the updated address of the server. This is more of a stop gap solution and would recommend that the clients update the IP address to the real address of the server. If your clients were using DNS to resolve myappserver.company.com then all you would have to do is change the A-record to the new IP address.

[NuhumanMohammad44256]

Thanks for the reply..

as per my understanding NAT will change only source IP address not destination IP, in this case if I use actual IP as natted one

does it work?

[TJ-20933766]

NAT can translate source or destination of a packet

[NuhumanMohammad44256]

Ok, may I know in which end router I have to configure the NAT ?    I have router (a) in HO were the ISP connected and One more router (b) were the link connected to DC

and router (b) connected Metro switch in DC were the DM server going to place.

[NuhumanMohammad44256]

Hi May I please get help on above query ?

[Georg Pauwen]

Hello,

as I understand it, you have users at the data centre in subnet 172.19.108.x/x that are trying to access an application server with IP address 172.19.108.2. You want these users to be automatically rerouted/redirected to the IP address of the new application server at the head office, with IP address 172.16.150.2 ?

I don't think NAT or any sort of policy routing will work, since all you clients are on the local subnet, and no traffic will be routedat all, or hit a layer 3 interface.

Do you have full control over both routers ? Is it an option to configure the routers to essentially extend the address space used at the data centre to the head office ?

[NuhumanMohammad44256]

No you understood completly wrong, users not from data center,   actual user from branch location.

Head office application server (local network ip assigned 172.16.150.X) will be shifted to data center, post this, whenever branch location user try to access application server which was there at HO traffic should be redirected to DC local network IP. (172.19.108.x).

Connectivity available from Head office to Data center through static route with Head office's all local IP subnet.

is it possible to do IP forwarding whenever request comes to Head Office local network application server ip, (172.16.150.X ....packet should forward to Data center local network IP (172.19.108.X

[NuhumanMohammad44256]

Hi Can somebody please help me out finding the solution 

[paul driver]

Hello

sounds like policy nat would be applicable here

You would in theory append nat to the HQ -branch interface which would be advertising the old destination subnet however can you post  topology diagram please it may help to understand better

[NuhumanMohammad44256]

hi find the attached diagram

From head office local lan subnet accessible  to Data center  

[Jon Marshall]

Be aware this is a solution based on the information provided so before you add NAT statements to your branch router you need to make sure it will not break anything else and if you already have NAT statements on that router you need to understand whether this can be added or not. 

On your branch router - 

1) on the LAN interface add this - 

"ip nat inside" 

2) on the WAN interface add this - 

"ip nat outside" 

3) then add this - 

"ip nat outside source static 172.19.108.2 172.16.150.2 add-route" 

the above will translate the destination IP 172.16.150.2 (the old server IP) to 172.19.108.2 (new server IP). 

As stated above this solution is provided as is, it is up to you to make sure it does not break any existing connectivity. 

Jon