Re: MPLS/VPN Hub-and-spoke Topology

From: Tarun Pahuja (pahujat@gmail.com)
Date: Sun Dec 16 2007 - 18:58:18 ART


Ken,
       The default behaviour in a MPLS backbone is site-to-site. In some
case the customer wants inter site traffic to specifically go through the
Hub site(Firewalling,Company policy,etc) just like frame relay network.
Therefore, this method has to be implemented to accomplish the task.

HTH,
Tarun

On 12/16/07, Ken Young <CiscoKid@ns.sympatico.ca> wrote:
>
> MPLS/VPN Hub-and-spoke Topology
>
> MPLS and VPN Architectures Page -242
> -OR-
> MPLS and VPN Architectures CCIP Edition Page -260
>
>
> "In either case, it is necessary to define a hub site that contains full
> routing knowledge of all spoke sites that belong to the same VPN. All
> traffic from the spoke sites, destined either for the central site
> services
> or for intersite connectivity, will flow through the central hub
> site. With
> this type of topology, the spoke sites export their routes to the hub
> site,
> and then the hub site re-exports the spoke site route through a second
> interface (either physical or logical) using a different route target so
> that other spoke sites can import the routes. This causes the hub site
> to
> become a transit point for interspoke connectivity."
>
>
> Can someone explain to my why this is done with a second connection?
> Split-Horizon Rule maybe ??
>
> Thanks,
> Ken
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:31 ARST