[j-nsp] Q-in-Q - QFX5100 [ new ELS CLI ]

[Nitzan Tzelniker]

Hi,

This is an example I got from the TAC before it is supported from
13.2x51-D25

set vlans v10 interface ge-0/0/1.10

set vlans v10 interface ge-0/0/2.10

set vlans v99 interface ge-0/0/2.99

set vlans v99 vlan-id 99 l3-interface irb.99

set interfaces irb unit 99 family inet address 19.0.0.1/24

set interfaces ge-0/0/1 vlan-tagging

set interfaces ge-0/0/1 encapsulation extended-vlan-bridge

set interfaces ge-0/0/1 unit 10 vlan-id-list 100-4000

set interfaces ge-0/0/1 unit 10 input-vlan-map push

set interfaces ge-0/0/1 unit 10 output-vlan-map pop

set interfaces ge-0/0/2 flexible-vlan-tagging

set interfaces ge-0/0/2 encapsulation extended-vlan-bridge

set interfaces ge-0/0/2 unit 10 vlan-id 10

set interfaces ge-0/0/2 unit 99 vlan-id 99

set interfaces ge-0/0/3 unit 0 family ethernet-switching interface-mode
trunk

set interfaces ge-0/0/3 unit 0 family ethernet-switching vlan members v99

set interfaces ge-0/0/4 unit 0 family ethernet-switching interface-mode
trunk

set interfaces ge-0/0/4 unit 0 family ethernet-switching vlan members v99


So just create a vlan (vlan 10 ) and assign the interface to it.

You can have more ports on this vlan but as units on other interfaces not
on ethernet-switching but you can have other vlans mixed e.g.
ethernet-switching with irb on one port and unit on other (vlan 99 )



Nitzan

On Wed, Oct 29, 2014 at 7:28 PM, Giuliano Medalha <giuliano at wztech.com.br>
wrote:

> ​P
> ​eople,
>
> We have a simple environment where we need to configure q-in-q using
> QFX5100 boxes:
>
>
>                    T                     T                        T
> QFX5100(A) ---- QFX5100(B)------QFX5100(C) ----- QFX5100(D)
>
>
>
> T = trunk (interface-mode) 802.1Q
>
> A and D elements need to push and pop C-VLANS.
>
> ​C-VLANs on this simple case are:​
> ​ list between [2500-2600]​
>
>
> ​S-VLAN would be vlan-id 2000​
>
>
> ​We have configured the following:​
>
>
> ​giuliano at CORE-SW-A# show interfaces ge-0/0/23
> flexible-vlan-tagging;
> encapsulation extended-vlan-bridge;
> unit 2000 {
>     vlan-id-list 2500-2600;
>     input-vlan-map push;
>     output-vlan-map pop;
> }
>
>  set vlans S-VLAN interfaces ge-0/0/23.2000  <---- here is not possible to
> configure vlan-id 2000
>
> No problem until now.
>
> But the question now is ...
>
> How can we transport the S-VLAN to a trunk port with familiy
> ethernet-swtiching ?
>
>
> Is it possible ?  We need to create another vlan with vlan-id 2000 ?
>
>
> set vlans V2000 vlan-id 2000
>
> set interfaces xe-0/0/0 unit 0 family ethernet-switching interface-mode
> trunk vlan-members V2000
>
>
> It will work in this environment ?
>
> Anyone had tested it with the last recommended release ?  13.2X51-D26
>
> It works ?
>
>
> Thanks a lot,
>
>
> Giuliano
>
>
>
>
>
> ​
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp