Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Untagged Aggregated Ethernet Interfaces

 

Packet tagging provides a logical way to differentiate traffic on ports which support multiple virtual local area network (VLAN). While you must configure aggregated Ethernet interfaces to receive tagged traffic, you must also configure aggregated Ethernet interfaces that can receive untagged traffic.

To configure an aggregated Ethernet interface as untagged, remove the vlan-tagging statement at the [edit interfaces aex] hierarchy level and remove the vlan-id statement from the following hierarchy levels:

  • [edit interfaces interface-name unit logical-unit-number]

  • [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Note

You can configure only one logical interface (unit 0) on the port. The logical unit 0 is used to send and receive LACP or marker protocol data units (PDUs) to and from the individual links.

Table 1 lists untagged aggregated Ethernet and LACP support by PIC and router.

Table 1: Untagged Aggregated Ethernet and LACP Support by PIC and Platform

PIC Type

M Series

LACP

T Series

LACP

4-port Fast Ethernet PIC Type 1

Yes

Yes

Yes

Yes

1-port Gigabit Ethernet PIC Type 1

Yes

Yes

Yes

Yes

2-port Gigabit Ethernet PIC Type 2

Yes

Yes

Yes

Yes

4-port Gigabit Ethernet PIC Type 2

Yes

Yes

Yes

Yes

1-port 10-Gigabit Ethernet M160

Yes

Yes

NA

NA

10-port Gigabit Ethernet PIC Type 3

Yes (M120, M320)

Yes

Yes

Yes

1-port 10-Gigabit Ethernet PIC Type 3

N/A

NA

Yes

Yes

8-port Gigabit Ethernet PIC Type 3

Yes

Yes

Yes

Yes

The 8–port Fast Ethernet PIC does not support untagged aggregated Ethernet or LACP.

Syslog messages are logged if you try to configure an untagged aggregated Ethernet interface using an unsupported PIC type.