Switching

 View Only
last person joined: 3 days ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.

  • 1.  What VLANs are allowed on QFX platform trunk interface?

    This message was posted by a user wishing to remain anonymous
    Posted 10 days ago
    This message was posted by a user wishing to remain anonymous

    Simple question but havent found a solid answer yet.  All the include adding vlans when trunks are created.  I want to create a trunk but not pass vlans.  Purpose is just to validate L1.  L2 traffic will be allowed later.

    I understand the follow to create the simple trunk.  At this point is all vlans allowed or no vlans allowed.  C vendor would allow all vlans.  Did find a 2013 Juniper blog that said not vlans.  Saw another doc stating tagged but unknown vlans are put into the native vlans.

    What should i be expecting if a tagged packet is received  on the port with a VLAN that exists on the Juniper switch where no vlans are listed on that port?

    set interfaces ae1 aggregated-ether-options lacp active
    set interfaces ae1 unit 0 family ethernet-switching interface-mode trunk



  • 2.  RE: What VLANs are allowed on QFX platform trunk interface?

    Posted 8 days ago

    I hope I interpret your post in the correct way. If you do not add any VLANs to a LAG/ae interface, or any interface, and specify it as a trunk interface, the commit will not succeed:

    me@EX4100-Office# set interfaces ge-0/0/11 unit 0 family ethernet-switching interface-mode trunk

    me@EX4100-Office# commit
    [edit interfaces ge-0/0/11 unit 0 family]
      'ethernet-switching'
        For trunk interface, please ensure either vlan members is configured or inner-vlan-id-list is configured
    error: configuration check-out failed

    If you do not specify any VLAN and configure the interface with mode access (untagged), this results in the default VLAN being applied to the port untagged.

    The best way to test the LAG/LACP is to create a dummy VLAN that only exists on that switch and apply it to the interface.

    set interfaces ae11 aggregated-ether-options lacp periodic fast active
    set interfaces ae11 unit 0 family ethernet-switching interface-mode trunk vlan members dummy
    delete interfaces ge-0/0/11
    set interfaces ge-0/0/11 ether-options 802.3ad ae11
    set vlans dummy vlan-id 1234

    Here, the VLAN dummy appears on  my uplink as well as it is defined with "vlan members all", but since that VLAN doesn't exist there, it doesn't matter.

    me@EX4100-Office# run show vlans dummy

    Routing instance        VLAN name             Tag          Interfaces
    default-switch          dummy                 1234
                                                               ae11.0
                                                               mge-0/2/0.0*  <--- this is my uplink


    Original Message