Re: OOT: Datacentre migration question

From: marc abel <marcabel_at_gmail.com>
Date: Fri, 18 Jan 2013 08:49:23 -0600

To me this is a process question, not a correct answer question. What I
mean is they ask you this looking for your thought process and not a
specific answer.

My process would be something like:

1. Understand the business purpose of all the data centers.
2. Understand the current physical layout
3. Understand constraints of the move, are they tolerant of down time to
physically move the equipment (lift and ship) or will you have to stand up
parallel environments for a quick cutover.
4. When consolidated do the data centers need to maintain
logical separation or can they be integrated to possibly better leverage
common resources (i.e. maybe you only need 4 copies of a database instead
of 9).
5. Are there opportunities to virtualize to reduce footprint, costs, and
add flexibility?
6. Are you able to port the IP addressing schemes in tact or do you need to
re-ip in the process. Consider summarization and routing protocol design
implications here. Can NAT be used to help with these challenges?

As for specific technologies CCIE2323 named a couple good ones.

Virtual context to keep segregation, beyond the Nexus you can extend this
to the ASA's as well.
OTV for magic layer 2 wizardry

Some other technologies

Virtualization
DNS with short lifetime so that you can cutover quickly
NAT for solving IP addressing issues
BGP might allow you to port/re-advertise your public address space

-Marc

On Fri, Jan 18, 2013 at 8:09 AM, Ccie2323 <ccie2323_at_gmail.com> wrote:

> Use Nexus solution, VDC If the consolidated dc still needs to be
> independent of each other. OTV to extent layer 2 to the new dc and migrate
> all servers. Final cutover layer3 to new dc when all parts of the dc has
> been migrated.
>
> On 18 Jan, 2013, at 9:58 PM, Arista Wirawan <arista.wirawan_at_gmail.com>
> wrote:
>
> > Sorry for the OOT. I was interviewed last few days ago and asked this
> > question. It can not get out of my head. So I need to burst it out of my
> > mind. Appreciate if anyone of you can help me. Thank you in advance.
> >
> > Here the question:
> > We want to consolidate from 9 datacentres to 4 datacentre to reduce
> > opex/capex. What is your steps, proces, strategy? New technology that
> > support it?
> > No impact expected on the quality of network services and day to day
> > operation.
> >
> > Sorry if you don't like it please just delete my email.
> > Probably my interviewer also in this milis and read this email.
> >
> > Best Regards,
> > ARISTA
> >
> > ( Please excuse misspelled words, sentence structure and the brevity of
> > this email as it was sent via a mobile device)
> > On 17 Jan, 2013 10:01 PM, "Tauseef Khan" <tasneemjan_at_googlemail.com>
> wrote:
> >
> >> To set the multicast boundary for PIM BSR do i need to block the
> following
> >> two groups on the interface:
> >> 224.0.1.39
> >> 224.0.1.40
> >>
> >> like this?
> >> ip access-list 1 deny 224.0.1.39
> >> ip access-list 1 deny 224.0.1.40
> >> ip access-list 1 permit any
> >>
> >> int gi0/0
> >> ip multicast boundary 1 out
> >>
> >> Rgards
> >>
> >>
> >> Blogs and organic groups at http://www.ccie.net
> >>
> >> _______________________________________________________________________
> >> Subscription information may be found at:
> >> http://www.groupstudy.com/list/CCIELab.html
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Marc Abel
CCIE #35470
(Routing and Switching)
Blogs and organic groups at http://www.ccie.net
Received on Fri Jan 18 2013 - 08:49:23 ART

This archive was generated by hypermail 2.2.0 : Sun Feb 03 2013 - 16:27:17 ART