The MPLS-OPS Archive

["Christopher Young" <cyoung@juniper.net>]

Marcel,

At least in the Juniper JUNOS-ERX implementation once routes from the 2 CE sites are put into the same vrf on the same PE (multihoming a customer to the same PE, same vrf), they are readily accesible to each other unless you put some form of filtering in place on the routing protocol run between the vrf and CE. If the protocol from vrf to CE was bgp you could try putting a prefix list in place towards the CE peers only allowing the routes from the hub site to be advertised and therefore preventing the 2 CE's from learning that they are directly reachable via the vrf. The only other option I can think of would be to create another vrf for the second CE (new export RT, same import RT) and terminate the second CE in the new vrf. 

As always I would test this in a lab first to ensure that it works properly ;-)


Chris Young


-----Original Message-----
From: Marcel_TUIHANI/opt@OPT.PF [mailto:Marcel_TUIHANI/opt@OPT.PF]
Sent: Monday, March 24, 2003 11:58 AM
To: mpls-ops@mplsrc.com
Subject: [MPLS-OPS]: "Hub and sopke" approach


Can anyone give me one or, i may be several solution about "hub and sopke"
configuration on Cisco equipement.
Actually, I use on my MPLS/VPN network an "Hub and spoke" architecture.
Sites linked on different PE can't communicate together. However, for sites
linked on the same PE, it isn't  possible to prevent that they communicate
directly.

I would like to know, how implement an "Hub and spoke" architecture on the
same PE.
One site central and several distants sites.

Marcel TUIHANI,
Office des Postes et des Télécommunications
Polynésie Française - TAHITI.


-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml