Junos OS

Expand all | Collapse all

Sub-interface that was auto-generated by Junos

Jump to Best Answer
  • 1.  Sub-interface that was auto-generated by Junos

    Posted 03-06-2020 20:47

    What is sub-interface et-0/0/22.16386 for?  Is it auto-generated by Junos? How do I get rid of it? Impacts?

    Thanks

     

    root@juniper-qfx5k# run show interfaces terse et-0/0/22 
    Interface               Admin Link Proto    Local                 Remote
    et-0/0/22               up    up
    et-0/0/22.16386         up    up  
    
    {master:0}[edit]
    root@juniper-qfx5k#
    


  • 2.  RE: Sub-interface that was auto-generated by Junos

    Posted 03-06-2020 21:06

    Hi, it is interface where RE will receive/send traffic which is not mapped to any configured ifl (unit on physical interface).

    For example LLDP will be mapped to this interface. 



  • 3.  RE: Sub-interface that was auto-generated by Junos
    Best Answer

    Posted 03-06-2020 21:09

    And you can read this KB2277

     

     

    SOLUTION:
    IFL *.32767 is created when vlan-tagging is configured for an interface.
    The *.32767 logical interface is created for the individual interface, the parent link, as well as all child links in the bundle.
    
    Logical unit 32767 is created to keep track of each individual link. This is needed for receiving LACP Marker Packets as per 802.3ad specifications and receiving untagged control PDU’s on a tagged interface.
    And this KB31774.
     
    SUMMARY:
    This article explains when logical interface .16386 is created on EX and QFX Series switches. 
     
    
    SOLUTION:
    IFL *.16386 is created on 10G and 40G interfaces when an SFP module is inserted without any logical unit (IFL) configuration.
    The default IFL (.16386) is added only when there are no IFLs configured on the interface.
    The default IFL on the interfaces is to support VC auto-provisioning on (et-/xe-) interfaces.