Description

This article explains why a logical unit 32767 is created for every member link of an aggregated ethernet bundle (802.3ad).

Symptoms

A logical unit 32767 created for every member link of an aggregated ethernet bundle (802.3ad).

Solution

The logical interface unit *.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.

The purpose of the logical unit 32767 is to process L2 control packets such as LACP Marker Packets as per 802.3ad specifications and receive untagged control PDUs on a tagged interface.

Example:
Interface       Admin Link Proto Local                 Remote
fe-0/0/0        up    down
fe-0/0/0.20     up    down aenet --> ae1.20
fe-0/0/0.32767  up    down
fe-0/0/1        up    down
fe-0/0/1.20     up    down aenet --> ae1.20
fe-0/0/1.32767  up    down

​
Interface without any configuration.
root@LAB# show interfaces xe-0/0/2

{master:0}[edit]
root@LAB# run show interfaces terse xe-0/0/2
Interface               Admin Link Proto    Local                 Remote
xe-0/0/2                up    up
xe-0/0/2.16386          up    up

Interface with vlan-tagging configuration.
root@LAB# show interfaces xe-0/0/2
vlan-tagging;

{master:0}[edit]
root@LAB# run show interfaces terse xe-0/0/2
Interface               Admin Link Proto    Local                 Remote
xe-0/0/2                up    up
xe-0/0/2.32767          up    up
 

{master:0}[edit]
root@LAB# show interfaces xe-1/0/5
ether-options {
    802.3ad ae2;
}

{master:0}[edit]
root@LAB# show interfaces xe-0/0/2
ether-options {
    802.3ad ae2;
}

{master:0}[edit]
root@LAB# show interfaces ae2
vlan-tagging;

{master:0}[edit]
root@LAB# run show interfaces terse | match ae2
xe-0/0/2.32767          up    up   aenet    --> ae2.32767
xe-1/0/5.32767          up    up   aenet    --> ae2.32767
ae2                     up    up
ae2.32767               up    up

Former Article Id

18239

Modification History

2022-05-23: Clarify content according to feedback. Publish this as Public KBs.
2017-12-12: Article reviewed for accuracy. Additional examples added for clarity.