[j-nsp] Kompella L2VPN question urgent-Multiple CE connections

[shahryar khan]

Hi,

As metioned in the duiagrams the problem is related to
transporting multiple ATM pvcs across the MPLS
backbone. The option chjosen in our case was by using
Kompella draft.

My issue is that is there a better way of povisionin
this setup, in which we require 9 * (n*(n-1)/2) PVC's
between different sites?

e.g assumming just three sites, we will be having 18
pvcs from each site (9 going to each of the othe two
sites). We shall be using unique site-ids for every
circuit.

So, is there an optimal way of doing this? and how can
we makwe it more scalable as we add more sites (means
more PVC end points)?

Shahryar 

 

--- Sanad Palislamovic <spalislam at gmail.com> wrote:

> Don't quote me on this, but if I remember correctly,
> L2VPNs are
> point-to-point, meaning site to site.  To build a
> full mash of sites and be
> part of same VPN, I think you must either L3VPNs. 
> If no routing involved,
> you can use "vrf-table-label" (allows secondary DA
> lookup), or VPLS.
> 
> My 2 cents
> 
> Senad
> 
> 
> On 1/23/06, shahryar khan <kshahryark at yahoo.co.uk>
> wrote:
> >
> > Hi ,
> >
> >            10/33                       10/33
> >     CE1 ---------- PE1------------ PE2------- CE2
> >         ---10/34--                    -10/34-
> >         ---10/35--                    -10/35-
> >
> > We have like 4 CE devices with 9 PVC's going
> towards every other site ( i
> > have shown just 2 sites with 3 pvcs only) . This
> makes a full mesh of 9PVC's
> > going towards every site. While using Kompella
> someone said that there seems
> > to be a limitation that if more than one logical
> circuit connects to the
> > same ce, then a different Site-id and a different
> L2VPN has to be used.
> > Please note that the VPI/VCI numbers could be the
> same on different Sites as
> > well.
> > In my opinion, that as a unique site-id shall be
> assigned to different
> > PVC's and remote-site id also configured, this
> scenario should work
> > neverthess as a unique label per site would be
> generated in any case. The
> > only thing is that the configuration would be very
> lengthy.
> > Is there a better way to configure the L2VPN ?
> > Best Regards
> > Shahryar
> >
> >
> >
> > ---------------------------------
> > To help you stay safe and secure online, we've
> developed the all new
> > Yahoo! Security Centre.
> > _______________________________________________
> > juniper-nsp mailing list
> juniper-nsp at puck.nether.net
> >
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> 



	
	
		
___________________________________________________________ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com