Switching

Expand all | Collapse all

flexible-vlan-tagging vs vlan-tagging

Jump to Best Answer
  • 1.  flexible-vlan-tagging vs vlan-tagging

    Posted 12-14-2020 18:54
    Hello Gents,

    Would you please let me know what is the difference of flexible-vlan-tagging vs vlan-tagging ?
    When to use both of them ?

    Thanks

    ------------------------------
    Rene welbrink
    ------------------------------


  • 2.  RE: flexible-vlan-tagging vs vlan-tagging
    Best Answer

    Posted 12-15-2020 03:18
    Hello.
    vlan-tagging supports one tag, flexible-vlan-tagging supports one tag and two tags (QinQ). You can not use both statements on the interface, just one.


  • 3.  RE: flexible-vlan-tagging vs vlan-tagging

     
    Posted 12-15-2020 05:26
    Hello Rene,

    in addition to smelnik's answer, some devices support only "vlan-tagging" (like legacy EX series), and some devices support both. If your device supports "flexible-vlan-tagging", I'd suggest you to use this one instead of "vlan-tagging", as it provides more flexibility.

    ------------------------------
    ------------------------------
    If my answer provides the solution, please mark my post as "Best Answer".
    If you think my answer helps, please "Recommend" my post.
    ------------------------------



  • 4.  RE: flexible-vlan-tagging vs vlan-tagging

    Posted 12-15-2020 08:49
    Bonjour Rene, 
      we are actually implementing the use of the QinQ (flexible vlan-tagging) on our EX2300 switches - 200+ switches are divided in 16 groups - the traffic of each group is then 2nd tagged using QinQ.   there is a very complete article  here by Juniper on the way to do it 

    Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation

    each group then has access to all vlans 1-4094 in his group without bothering it's neighbors. 
    config on each switch roughly looks like this 
    VLANS 
    root@mrcrn-rouyn-02-SitePrincipal-2020-06-18# show vlans 
    ...
    QinQ-MRCRN-3913 {
        interface ge-0/0/11.3913;
        interface ge-0/0/0.3913;
    }
    ...
    
    CLIENT SIDE: ALL TRAFIC GET A 2ND TAG ADDED OR REMOVED 
    
    root@mrcrn-rouyn-02-SitePrincipal-2020-06-18# show interfaces ge-0/0/0   
    description "MRCRN-QinQ-3913";
    flexible-vlan-tagging;
    encapsulation extended-vlan-bridge;
    unit 3913 {
        vlan-id-list 1-4094;
        input-vlan-map push;
        output-vlan-map pop;
        family ethernet-switching {
            filter {
                input client-filter-1g;
                output client-filter-1g;
            }
            storm-control default;
        }
    }
    
    SUPPLIER SIDE: ALL TRAFIC FLOWING IS BASED ON THE 2ND TAG (DON'T FORGET TO INCREASE MTU))
    root@mrcrn-rouyn-02-SitePrincipal-2020-06-18# show interfaces ge-0/0/11 
    description " CIRCUIT nnn";
    vlan-tagging;
    mtu 1538;
    ...
    unit 3913 {
        vlan-id 3913;
        family ethernet-switching;
    }
    ...​

    hope it helps - have fun !
    Michel



    ------------------------------
    Michel Lapointe
    ------------------------------