[j-nsp] BGP VPLS support

[Monika M]

Hi,
      In LDP based H-VPLS solution, u-PE is a spoke node. But with respect
to BGP VPLS case, specification is not clear.  It says that each PE has a
VE-ID for each u-PE connected to it. If a PE device advertises two set of
label blocks for different VE IDs configured, then the Peer PEs have many VC
LSPs for this PE for the same VPN. In this case, flooding
of multicast/broadcast packets becomes an issue..

Regards


On 6/15/07, Bourgeois, Jacob (Jake)** CTR ** <bourgeois at alcatel-lucent.com>
wrote:
>
> Monika,
>
> For VEID, my thoughts are this is a outcome derived by the RD and the 2
> bytes populated accordingly, it serves the same function, i.e.
> determining the outgoing label for push operation.  Maybe a developer
> will weigh in on this though, as there is no way to manually configure
> this that I know of.
>
> "u-PE" is somewhat of a grey area as it is defined as a device that is
> service aware, accommodates control plane set up, etc, but may not do
> all of these functions:
>
> 5.  Deployment Options
>
>   In deploying a network that supports VPLS, the SP must decide what
>   functions the VPLS-aware device closest to the customer (the VE)
>   supports.  The default case described in this document is that the VE
>   is a PE.  However, there are a number of reasons that the VE might be
>   a device that does all the Layer 2 functions (such as MAC address
>   learning and flooding), and a limited set of Layer 3 functions (such
>   as communicating to its PE), but, for example, doesn't do full-
>   fledged discovery and PE-to-PE signaling.  Such a device is called a
>   "u-PE".
>
> Maybe this is more of a reference to a spoke in H-VPLS? Anyone who has
> more of a clue please weigh in, this is a particularly interesting topic
> as the service is finding its way into many core's.
>
> Jake Bourgeois
> Alcatel*Lucent
> Member of Consulting Staff
> Services Business Group
> Email: bourgeois at alcatel-lucent.com
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Monika M
> Sent: Thursday, June 14, 2007 6:26 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] BGP VPLS support
>
> As per BGP VPLS RFC 4761 section 3.2.2, "if the PE is connected to
> several
> u-PEs, it has a distinct VEID for each u-PE. It may additionally have a
> VE
> ID for itself, if it itself acts as a VE for that VPLS."
>
> Does Juniper support connecting PE to many u-PEs?. I have this doubt as
> Juniper allows only one site id configuration in the PE router.
> If  connecting to multiple u-PE is supported, can any one point to the
> document (configuration) to achieve this?
>
> TIA,
> Monika.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>