[j-nsp] Trunk port assignment

Bala Venkata balavenkata at netscape.net
Wed Mar 23 01:48:39 EST 2005

Thanks for that response Erik. The intent of my original question
was to see how to config a trunk port to pass a set of vlans easily.
I found how to do that on a riverstone but from your response and 
juniper docs it seems I have to create a logical interface for
*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 ?

Thanks !

 >Message: 3
 >Date: Tue, 22 Mar 2005 15:16:25 +0100
 >From: Erik Haagsman <erik at we-dare.net>
 >Subject: Re: [j-nsp] Trunk port assignment
 >To: Juniper NSP <juniper-nsp at puck.nether.net>
 >Message-ID: <1111500985.27156.5.camel at pcp.we-dare.net>
 >Content-Type: text/plain
 >On Mon, 2005-03-21 at 11:29 +0530, Bala Venkata wrote:
>> How do you mark a port as a 'trunk-port' in JunOS ?
>> Since trunk ports accept only tagged traffic I was
>> thinking of using "vlan-tagging" 
>> [edit interfaces ge-3/0/0]
>> vlan-tagging;
>> description toCE1-ASide;
>> ???
 >You assumed this correctly. When defining the units on the interface 
 >you give each unit that has to carry a certain tagged VLAN it's tag 
 >with the vlan-id keyword.
 >>(but then how would
>> you make a port non-trunk i.e. as an access port ?)
 >By not using tagging on that interface...?

More information about the juniper-nsp mailing list