Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
 

Related Documentation

 

Configuring Untagged Aggregated Ethernet Interfaces

When you configure an untagged Aggregated Ethernet interface, the existing rules for untagged interfaces apply. These rules are as follows:

  • 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.
  • You cannot include the vlan-id statement in the configuration of the logical interface.

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.

For more information about configuring LACP, see Configuring Aggregated Ethernet LACP.

Example: Configuring Untagged Aggregated Ethernet Interfaces

Configure an untagged aggregated Ethernet interface by omitting the vlan-tagging and vlan-id statements from the configuration:

[edit interfaces]
fe-5/0/1 {fastether-options {802.3ad ae0;}}
ae0 {# vlan-tagging; OMIT FOR UNTAGGED AE CONFIGURATIONSunit 0 {# vlan-id 100; OMIT FOR UNTAGGED AE CONFIGURATIONSfamily inet {address 13.1.1.2/24 {vrrp-group 0 {virtual-address 13.1.1.4;priority 200;}}}}}
 

Related Documentation

 

Published: 2013-02-13

Supported Platforms

 

Related Documentation

 

Published: 2013-02-13