From: Weidong Xiao (Weidong.Xiao@vi.net)
Date: Fri Jan 23 2004 - 08:04:56 GMT-3
I was a major player of a datacenter migration project last year. 400 servers. Similar to your topology, excepet that we managed to persuade customers one by one to accept a couple of hours down time. (some were in akward hours, but still much less hassel than to install back-up identical servers)
We used Local Area Mobility. Vlan was not a problem at all.
Dell server worked fine with LAM. Cobalt server needed to be pinged first for the router to know its exsitance. Set arp timeout to its maximum.
You mentioned the distance between A and B is 100 miles, which is a bit long for down time. If you can afford to make a backup for each server in location A, then if you
1. create a backup vlan in site B, put all backup servers in this vlan, enable LAM. Redistribute LAM.
2. shut the switch port of a backup server, manually change its ip to that of its counterpart in site A
3. take the server in site A out of service
4. no shut the switch port of backup server, LAM should kick in, and service resume.
5. After all the backup servers are in service, you can create a vlan using the ip range used in site A, and change all the backup servers to this vlan.
It's a good time to tidy up cables, set U position in a rack corelate to its switch port number, and these kind of thing.
Have fun,
HTH,
Weidong
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> rdanu
> Sent: 20 January 2004 19:02
> To: ccielab@groupstudy.com
> Subject: Datacenter Migration Question
>
>
> I am trying to put together the pieces of a migration puzzle.
> The company I work for is thinking about a possible migration
> of their data center. I thought about several options but Id
> like to see what some of you seasoned professionals might
> advise. A brief scenario is described below, if you have any
> questions feel free to ask. I appreciate any feedback!
>
> Current setup:
> Location A contains 6 production VLANS, and customers access
> everything via a high speed (OC-3) Internet connection.
>
> Migration scenario:
>
> The goal is to transition all the servers from Location A to
> location B. The distance amongst locations is approximately
> 100 miles. No down time is allowed.
>
> Servers at Location A have subnet/VLAN information 10.1.1.0,
> 10.1.2.0, 10.1.3.0. 10.1.6.0.
>
> A private OC-3 will connect Location A to Location B.
>
> Servers will be moved to Location B in batches of 10. There
> are approximately 150 servers in total.
>
> The objective is, to keep all servers working together and
> allow them to co-exist on the same VLANS, at both locations.
>
> Internet access will continue to be provided through Location
> A, until all servers have been migrated to Location B.
>
> In essence, how could the same exact VLANS (same subnets)
> co-exist and communicate with each other at both locations
> via a routed IP network? Is there a method to tunnel VLANS
> through an IP network?
>
> Location A contains CAT5500 Equipment. Location B will have
> CAT3750 Cisco equipment, possibly 4500.
>
> Example:
> Out of a pool of 20 Web servers (Load Balanced at Location A
> from its Internet connection), about 10 will be moved to
> Location B in the 1st trip. We have to make sure that these
> moved servers will preserve the same IP address. The
> requirement is to have the 10 Servers at Location A, and the
> 10 Servers at Location B work together, as if they were next
> to each other.
>
> Thanks
> Richard Danu
>
> ______________________________________________________________
> _________
> Please help support GroupStudy by purchasing your study
> materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:49 GMT-3