RE: OT: Using a Router to redirect IP traffic [7:42217]
Thanks to all those who replied about this question. We ended up just setting up a server to redirect httpd requests to the new location. Seems it was alot easier to do that rather than to play around with routing issues. Cheers, - Trevor Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=42895&t=42217 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: OT: Using a Router to redirect IP traffic [7:42217]
This is what I would do in your situation.. -Listing what i have to do to keep the boss happy and save money for your firm. 1. Keep old IP's at the old datacenter, hitting live servers at the new datacenter 2. Prevent the need to a second set of servers with DNS entries seperate from the originals My question first - why can't you leave just one server with a "sorry maintence this weekend" sign up. Its perfectly accetable to allow say 4 hours downtime. Your boss is probably just being a hardass. Unless your Yahoo and can't afford any downtime, tell him to chillout, go back to his boss and be a man. That being said, I would... Get the old router (at the old colo) to do a gre tunnel to the new router and the new colo. At the new colo have the default route point to the other end of the tunnel (at the old colo). The Old colo will be our "ip nat outside", with static routes for the Servers Private IP's (now at the new colo) via the tunnel interface. Now, the new colo, will have NO default route, just a route for the old colo router, via its normal next hop (probably the new colo's edge equipment)... All incoming requests will hit the old router, go thru the gre tunnel, and back out the old router from the servers, after going thru the tunnel. This should work fine, I did something similar when we blew out of Exodus one weekend :) One more gotcha is have your DNS TTL taken as low as you can (say 5 minutes) so you can just have this stupid thing running for a few hours. I dont think you can have both at once, unless you can do a policy route for "it goes out the interface it came in by" so it will be using old colo's and new colo's ip addresses at once. You will still have the downtime from the move of the servers.. but it shouldn't be too much.. if you schedule it right, and have a low TTL in dns, you can get by, with pulling your servers just when your DNS changes, buy the time you get to the new site (and your DNS is mostly changed around the globe, your back up) Even if you had multiple servers (ones at each colo) you still have to account for DNS issues. Bottom line : is a few minutes to hours of downtime, worth buying a new set of servers. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=42227&t=42217 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OT: Using a Router to redirect IP traffic [7:42217]
Hi Trevor, Assuming that your servers have unique public IP addresses and you can get a small new address space from the colocation provider (for use as a NAT pool) then this would be technically feasible using twice-NAT. However, you would be paying your current colo provider for twice the bandwidth that you already consume plus your new provider. You would add hops, delay, packet loss, and complexity. If you do not have at least one spare server (assuming similar platforms) then you will require downtime whne you move each server anyway, so you could change the DNS entry then. Note that you must lower the TTL of DNS entries so as to let cached records expire in time for the change. Note also that if all traffic is web, then you might like to consider HTTP redirection as a technique in case your current DNS TTLs are already too long. rgds Marc Trevor Jennings wrote: > > Hello, > > Where I work, we have a number of servers being co-located at one > location and are planning on moving those servers to another co-location > provider soon. My boss asked me why we could not, when we move the > servers, just place a router at the original ISP to redirect all traffic > from the original ip's to the new ip's rather than having duplicate > servers or adjusting the DNS at the same time. I told him that I wasnt > sure whether it was possible and was told by a friend that its not > really possible to do that. Can anyone confirm that or rather explain why > that is not possible? My Boss's theory was that we would have a router > with 2 ethernet ports and redirect the original ip's to the new ip's > through the second ethernet. > > Cheers, > > - Trevor Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=42223&t=42217 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: OT: Using a Router to redirect IP traffic [7:42217]
Maybe you can put a router running NAT to hide the new addresses behind the old ones. K. Koen Zeilstra Legian --- You know you're a little fat if you have stretch marks on your car. -- Cyrus, Chicago Reader 1/22/82 On Mon, 22 Apr 2002, Trevor Jennings wrote: | Hello, | | Where I work, we have a number of servers being co-located at one | location and are planning on moving those servers to another co-location | provider soon. My boss asked me why we could not, when we move the | servers, just place a router at the original ISP to redirect all traffic | from the original ip's to the new ip's rather than having duplicate | servers or adjusting the DNS at the same time. I told him that I wasnt | sure whether it was possible and was told by a friend that its not | really possible to do that. Can anyone confirm that or rather explain why | that is not possible? My Boss's theory was that we would have a router | with 2 ethernet ports and redirect the original ip's to the new ip's | through the second ethernet. | | Cheers, | | - Trevor | | | | | Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=4&t=42217 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
OT: Using a Router to redirect IP traffic [7:42217]
Hello, Where I work, we have a number of servers being co-located at one location and are planning on moving those servers to another co-location provider soon. My boss asked me why we could not, when we move the servers, just place a router at the original ISP to redirect all traffic from the original ip's to the new ip's rather than having duplicate servers or adjusting the DNS at the same time. I told him that I wasnt sure whether it was possible and was told by a friend that its not really possible to do that. Can anyone confirm that or rather explain why that is not possible? My Boss's theory was that we would have a router with 2 ethernet ports and redirect the original ip's to the new ip's through the second ethernet. Cheers, - Trevor Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=42217&t=42217 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
