[j-nsp] Trunk port assignment

[Juan Villasuso]

You can use "ethernet-vpls" as encapsulation for the interface facing to CE. 
This way you don't have to specify a diferent units each VLAN you want to 
transport. See the diference

user at M20# show interfaces ge-0/2/0
vlan-tagging;
encapsulation extended-vlan-vpls;     // also vlan-vpls as encapsulation
unit 0 {
    vlan-id 669;                                   // only vlan 669
    family vpls;
}

user at M20# show interfaces ge-2/0/0
mtu 2000;
encapsulation ethernet-vpls;
unit 0 {                                            // all vlans
    family vpls;
}

Vpls routing-instance is configured same way on both cases and also the BGP 
part.

Hope this helps.

Regards.

-- Juan Villasuso.


----- Original Message ----- 
From: "Bala Venkata" <balavenkata at netscape.net>
To: <juniper-nsp at puck.nether.net>
Sent: Tuesday, March 29, 2005 8:16 AM
Subject: Re: [j-nsp] Trunk port assignment


> Nils-
>
> Thanks for the response. See my comments inlined:
>
>
> nils at tdsdata.net wrote:
>> Bala,
>>
>>> *each* of the vlans and tag it with the vlan id. Is that the only way ?
>>> Again, with riverstone I am able to do:
>>>
>>> "switchport trunk-vlans 601-700,751-850"
>>>
>>> How to map this to JunOS without having to create 200 units ?
>>
>>
>>  From your information it seems to me you're trying to transport a set
>> of VLANs on this gigabit ethernet interface to the other side of your
>> network. On the core-facing interface of this RSTN box, what are you
>> using ? i.e. MPLS based transport (L2VPN or VPLS) or VLAN stacking ?
>
> [Bala 03/29] The core is configured for VPLS transport. You are right, I
> am transporting a set of VLANs from the Riverstone PE to the 'other'
> side of my core. Granted, JNPR and RSTN both don't 'talk' the same VPLS
> language (support diff drafts) but I was wondering what would happen if
> the 'other' side were a Juniper M. Or, how to transport a set of VLANs
> between two Juniper M using VPLS core (specifically BGP-VPLS - one that
> JunOS supports as we speak)
>
>>
>> On a juniper box you can transparantly transport an interface's traffic
>> to another endpoint based on physical or logical interface. I.e. a total
>> port with everything that comes in or a logical interface on this port
>> (vlan,vc,vp, etc.. ).
>>
>> The feature guide of JUNOS describes the various options to transporting
>> layer 2 circuits:
>>
>> http://www.juniper.net/techpubs/software/junos/junos71/feature-guide-71/frameset.htm
>>
>>
>> Chapter "Layer 2 Circuits" (i.e. Circuit Cross Connect or CCC as Michael
>> suggested)
>>
>> Translational Cross Connects and VPLS are described in that guide as 
>> well.
>
> [Bala 03/29] Yes, I did refer to this too. But these seem "point to
> point". What abt a "point to multipoint" solution where I want to
> transport all vlans across an VPLS enabled core ?
>
>>
>>
>> -Nils
>
>
> [Bala 03/29] Thanks !
>
> /bala
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>