And I am sure that there is an RFC for what you guys are talking about
(Master.......), correct?
On Wed, Jan 9, 2013 at 6:21 PM, Routing Freak <routingfreak_at_gmail.com>wrote:
> Joseph
>
> People who masturbate regularly always find a way to escape from the
> embarrassment bcoz they know the amount of time they need to masturbate and
> how can they achieve that with ease.
>
> Getting bogged down by nomenclature is what is the order of the day in the
> world of IT.
>
>
> On Thu, Jan 10, 2013 at 1:20 AM, Joseph L. Brunner
> <joe_at_affirmedsystems.com>wrote:
>
> > I can call a rooster a male chicken. I can call a male chicken a rooster.
> >
> > Don't get too caught up in someone else's nomenclature.
> >
> > You're post below reads like a newly masturbating teenager who found his
> > father's playboys and can't remember what drawer to put them back into
> > before daddy get's home...
> >
> > -----Original Message-----
> > From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> > Routing Freak
> > Sent: Wednesday, January 09, 2013 2:38 PM
> > To: Cisco certification
> > Subject: OT:WAN Backbone and Internet in DC
> >
> > Hi all
> >
> > In my customer data centre network, we have primary as well as Disaster
> > Recovery site and we have Inter DC links which is the so-called WAN
> > Backbone. And we have Internet connectivity from my Edge routers on both
> > the Data centers sites to upstream Internet Service Providers I dont
> > understand what is the difference between the WAN Backbone and Internet
> in
> > terminologies in documentations.
> >
> > THis is what my understanding is WAN Backbone is nothing but ur Data
> > centre Interconnect technology that u r going inorder to reach other DC
> > site in case any links to upstream Providers got lost or else any other
> > issue making the traffic.
> >
> > Why do they call as WAN Backbone? Its just a normal DC Interconnect
> > technology where we can use another Service Provider just like a VPN
> > connection to reach another site. I probably feel WAN Backbone used in
> ISP
> > Core network where they have large mesh of LSPs to each and every Edge
> > devices.
> >
> > Whereas the original connection from the Edge routers to the upstream
> ISPs
> > are exclusively for the internet routes and not for any DCI or VPN
> traffic
> > from one DC to another DC
> >
> > In this case when designing the DC sites, we need to have two separate
> > service providers . One for the Internet Routes and another for the DC
> > interconnect
> >
> > On what scenarios does the Inter DC links will be used and in what
> purpose
> > it is required ?
> >
> > I see there are lot of solutions for DC Interconnect ranging from VPLS to
> > Layer 3 VPNs over the internet or else plain Layer 3 routing. Which works
> > best and i see the "It depends" answer coming !! :)
> >
> > Can someone throw light on this more.
> >
> > --
> > Regards
> > Routing Freak
> > CCIE#35889 (SPv3)
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Regards
> Routing Freak CCIE#35889 (SPv3)
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- *Narbik Kocharians *CCSI#30832, CCIE# 12410 (R&S, SP, Security) *www.MicronicsTraining.com* <http://www.micronicstraining.com/> Sr. Technical Instructor YES! We take Cisco Learning Credits! A Cisco Learning Partner Blogs and organic groups at http://www.ccie.netReceived on Wed Jan 09 2013 - 20:03:37 ART
This archive was generated by hypermail 2.2.0 : Sun Feb 03 2013 - 16:27:17 ART