Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/encapsulation-edit-interfaces-physical.html

extended-vlan-bridge 

—Use extended VLAN bridge encapsulation on Ethernet interfaces that have IEEE 802.1Q VLAN tagging and bridging enabled and that must accept packets carrying TPID 0x8100 or a user-defined TPID.



Code Block
titleshow interface
Default Value:
ge-0/0/12
  Link-level type: Ethernet,                 other option are:  Flexible-Ethernet, Extended-VLAN-Bridge, ....

ge-0/0/12.0
    Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.200 ]  Encapsulation: ENET2




Code Block
titleshow
root@QFX5110-2# show interfaces ge-0/0/13
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 0 {
    vlan-id 200;
}



{master:0}[edit]
root@QFX5110-2# commit check
[edit interfaces ge-0/0/13]
  'unit 0'
     interface needs to be in a bridge-domain or evpn to support family bridge
error: configuration check-out failed

{master:0}[edit]
root@QFX5110-2#



Code Block
titlesolution add interface to vlan
{master:0}[edit interfaces ge-0/0/16]
root@QFX5110-2# top show interfaces ge-0/0/16
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 0 {
    vlan-id 200;
}


root@QFX5110-2# top show vlans
. . .
vlan200 {
    vlan-id 200;
    interface ge-0/0/12.0;
    interface ge-0/0/16.0;
}