Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring Aggregated Ethernet Interfaces and LACP

 

You can use Ethernet link aggregation to increase bandwidth and resiliency of Ethernet links by bundling or combining multiple full-duplex Ethernet links into a single virtual link. This virtual link interface is known as an aggregated Ethernet Interface. This topic provides an overview of the aggregated Ethernet Interface and explains how to configure an aggregated Ethernet Interface and its various features.

Aggregated Ethernet Interfaces Overview

Link aggregation of Ethernet interfaces is defined in the IEEE 802.3ad standard. The Junos OS implementation of 802.3ad balances traffic across the member links within an aggregated Ethernet bundle based on the Layer 3 information carried in the packet. This implementation uses the same load-balancing algorithm used for per-flow load balancing.

Note

For information about configuring circuit cross-connects over aggregated Ethernet, see Circuit and Translational Cross-Connects Overview.

For information about mixed rates and mixed modes on an aggregated Ethernet bundle, see Understanding Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles.

Platform Support for Aggregated Ethernet Interfaces

You configure an aggregated Ethernet virtual link by specifying the link number as a physical device and then associating a set of ports that have the same speed and are in full-duplex mode. The physical interfaces can be Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ, Gigabit Ethernet IQ2 and IQ2-E, or 10-Gigabit Ethernet IQ2 and IQ2-E. Generally, you cannot use a combination of these interfaces within the same aggregated link; however, you can combine Gigabit Ethernet and Gigabit Ethernet IQ interfaces in a single aggregated Ethernet bundle.

Starting with Junos OS Release 13.2, aggregated Ethernet supports the following mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers:

  • Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.

  • Member links of different rates: 10-Gigabit Ethernet, 40-Gigabit Ethernet, 50-Gigabit Ethernet, 100-Gigabit Ethernet, and OC192 (10-Gigabit Ethernet WAN mode)

Note
  • Member links of 50-Gigabit Ethernet can only be configured using the 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).

  • Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP. This 100-Gigabit Ethernet member link can be included in an aggregated Ethernet link that includes member links of other interfaces as well. In releases before Junos OS Release 13.2, the 100-Gigabit Ethernet member link configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP cannot be included in an aggregated Ethernet link that includes member links of other interfaces.

Tip

Going forward:

  • Aggregated Ethernet link with member links of different modes will be referred as 10-Gigabit Ethernet mixed mode aggregated Ethernet link.

  • Aggregated Ethernet link with member links of different rates will be referred as mixed rate aggregated Ethernet link.

  • These aggregated Ethernet links will generically be referred as mixed aggregated Ethernet links.

Table 1 lists the platforms and corresponding hardware components that support mixed aggregated Ethernet bundles.

Table 1: Platform Support Matrix for Mixed Aggregated Ethernet Bundles

Rate and Mode

Supported Platform

Supported FPCs

Supported PICs

10-Gigabit Ethernet LAN and WAN

(WAN rate: OC192)

T640, T1600, T4000, and TX Matrix Plus routers

  • T4000 FPC5 (T4000-FPC5-3D)

  • 10-Gigabit Ethernet LAN/WAN PIC with Oversubscription and SFP+ (PF-24XGE-SFPP)

  • 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-12XGE-SFPP)

  • Enhanced Scaling FPC3 (T640-FPC3-ES)

  • 10-Gigabit Ethernet PIC with XENPAK (PC-1XGE-XENPAK)

  • Enhanced Scaling FPC4 (T640-FPC4-ES)

  • Enhanced Scaling FPC4-1P (T640-FPC4-1P-ES)

  • T1600 Enhanced Scaling FPC4 (T1600-FPC4-ES)

  • 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PD-5-10XGE-SFPP)

  • 10-Gigabit Ethernet LAN/WAN PIC with XFP (PD-4XGE-XFP)

40-Gigabit Ethernet, 100-Gigabit Ethernet

T4000 and TX Matrix Plus routers

  • T4000 FPC5 (T4000-FPC5-3D)

  • 100-Gigabit Ethernet PIC with CFP (PF-1CGE-CFP)

 

T640, T1600, T4000, and TX Matrix Plus routers

  • Enhanced Scaling FPC4 (T640-FPC4-ES)

  • Enhanced Scaling FPC4-1P (T640-FPC4-1P-ES)

  • T1600 Enhanced Scaling FPC4 (T1600-FPC4-ES)

  • 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4)

    Note: This PIC is available packaged only in an assembly with the T1600-FPC4-ES FPC.

  • 40-Gigabit Ethernet PIC with CFP (PD-1XLE-CFP)

Enhanced LAG Support on MX Series Routers

Starting in Junos OS Release 14.2, you can configure an enhanced link aggregation group (LAG) on MX Series routers. When you associate a physical interface with an aggregated Ethernet interface, the physical child links are also associated with the parent aggregated Ethernet interface to form a LAG.

In the absence of enhanced LAG support, one child next hop is created for each member link of an aggregated Ethernet interface for each VLAN interface. For example, an aggregate next hop for an aggregated Ethernet interface with 16 member links leads to the installation of 17 next hops per VLAN created. Thus the number of next hops supported on the routers with aggregated Ethernet interfaces is significantly reduced.

With the enhanced LAG support, when the [edit chassis network-services enhanced-ip] statement is configured, child next hops are not created for member links and, as a result, a higher number of next hops can be supported.

Note that the enhanced LAG feature is only supported when the router’s network services is set to operate in the enhanced-ip mode. This feature is not supported when the router’s network services is set to operate in the enhanced-ethernet mode.

Enhanced LAG Support on PTX Series Routers

Starting in Junos OS Release 18.1, Junos OS supports removal of child next hop usage for aggregated Ethernet Interfaces and clients on PTX Series routers with FPC3-PTX-U2 and FPC3-PTX-U3. Removal of child next hop usage helps reduce the memory and CPU resources required to support aggregated Ethernet Interfaces and improves the overall system performance and scaling numbers. This feature is enabled by default if the network services mode on the router is configured to enhanced-mode. You can disable this feature by using the set chassis aggregated-devices disable-lag-enhanced. You must reboot the router for the configuration to take effect.

Previously, each unicast next hop over aggregated Ethernet Interfaces resulted in creation of a number of children next hops as well. For an aggregated Ethernet Interface with 16 member links, addition of one unicast next hop over the aggregated Ethernet Interface results in installing total of 17 next hops. As a result, with aggregated Ethernet configuration, the number of next hops supported decreases in proportion to the number of aggregated Ethernet links.

Note

Child next hop optimizations are supported for aggregated Ethernet Interfaces, Interfaces that make use of aggregated Ethernet Interfaces, and for both unicast and multicast scenarios. For more information, see Configuring Aggregated Ethernet Interfaces on PTX Series Packet Transport Routers.

Configuration Guidelines for Aggregated Ethernet Interfaces

  • For Junos OS Evolved, when a new interface is added as a member to the aggregated Ethernet bundle, a link flap event is generated. When you add an interface to the bundle, the physical interface is deleted as a regular interface and then added back as a member. During this time, the details of the physical interface are lost.

  • For Junos OS Evolved, there is no restriction on the maximum number of AE interfaces in a mixed-rate AE bundle. Because all child logical interfaces belong to same AE physical interface and share the same selector, using much less load balance memory, mixed-rate AE interface configurations should go through even if they exceed 64 logical interfaces.

  • Aggregated Ethernet for subscriber management supports only gigether-options on the member link interfaces. If you configure ether-options on the member link interfaces, subscriber management does not work properly. The ether-options configuration will cause issues with subscriber accounting and statistics.

  • Aggregated Ethernet interfaces can use interfaces from different FPCs, DPCs, PICs, or MPCs.

  • All Juniper routers support at least eight physical interfaces per aggregated Ethernet bundle. See maximum-links configuration page for platform specific limits.

  • On M Series and T Series routers, you can create a maximum of 1024 logical interfaces on an aggregated Ethernet interface.

  • Simple filters are not supported for interfaces in aggregated Ethernet bundles:

    • On M Series routers, simple filters are supported in Gigabit Ethernet Enhanced Intelligent Queuing interfaces only, except when the interface is part of an aggregated Ethernet bundle.

    • On MX Series routers, simple filters are supported in Enhanced Queuing Dense Port Concentrator (EQ DPC) interfaces only, except when the interface is part of an aggregated Ethernet bundle.

    For more information about simple filters, see the Class of Service Feature Guide (Routers and EX9200 Switches).

  • On the aggregated Ethernet bundle, no IQ-specific capabilities such as MAC accounting, VLAN rewrites, and VLAN queuing are available. For more information about IQ-specific capabilities, see Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs.

  • Aggregated Ethernet interfaces can be either tagged or untagged, with LACP enabled or disabled. Aggregated Ethernet interfaces on MX Series routers support the configuration of flexible-vlan-tagging and native-vlan-id on dual-tagged frames, which consist of the following configuration statements:

    In all cases, you must set the number of aggregated Ethernet interfaces on the chassis. You can also set the link speed and the minimum links in a bundle.

    For more information on tagging in PTX Serious routers, see Configuring Aggregated Ethernet Interfaces on PTX Series Packet Transport Routers.

  • When configuring mixed aggregated Ethernet bundles on T640, T1600, T4000, and TX Matrix Plus routers, consider the following:

    • A maximum of 16 member links can be configured to form a mixed aggregated Ethernet link.

    • Link Aggregation Control Protocol (LACP), aggregated Ethernet link protection, and LACP link protection are supported only on mixed aggregated Ethernet link configured on a 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).

    • Traffic distribution is based on the hash calculated on the egress packet header. Hash range is fairly distributed according to member links’ speed. This guarantees hash fairness but it does not guarantee fair traffic distribution depending on the rate of the egress streams.

    • Packets are dropped when the total throughput of the hash flow exiting a member link (or multiple hash flows exiting a single member link) exceeds the link speed of the member link. This can happen when egress member link changes because of a link failure and the hash flow switches to a member link of speed that is less than the total throughput of the hash flow.

    • Rate-based CoS components such as scheduler, shaper, and policer are not supported on mixed rate aggregated Ethernet links. However, the default CoS settings are supported by default on the mixed rate aggregated Ethernet links.

    • Load balancing is performed at the ingress Packet Forwarding Engine. Therefore, you must ensure that the egress traffic on the aggregated Ethernet link enters through the hardware platforms that support mixed aggregated Ethernet bundles. Table 1 lists the platforms and corresponding hardware components that support mixed aggregated Ethernet bundles.

    • Mixed aggregated Ethernet links can interoperate with non-Juniper Networks aggregated Ethernet member links provided that mixed aggregated Ethernet load balancing is configured at egress.

    • Load balancing of the egress traffic across the member links of a mixed rate aggregated Ethernet link is proportional to the rates of the member links.

    • Egress multicast load balancing is not supported on mixed aggregated Ethernet interfaces.

    • Changing the edit interfaces aex aggregated-ether-options link-speed configuration of a mixed aggregated Ethernet link, which is configured on the supported interfaces of on T640, T1600, T4000, and TX Matrix Plus routers, leads to aggregated Ethernet link flapping.

    • When configuring a mixed aggregated Ethernet link on a 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4), ensure that you add both the 50-Gigabit Ethernet interfaces of the 100-Gigabit Ethernet PIC with CFP to the aggregated Ethernet bundle. Moreover, both these 50-Gigabit Ethernet interfaces must be included in the same aggregated Ethernet bundle.

    • When a mixed aggregated Ethernet link is configured on a 100-Gigabit Ethernet PIC with CFP, changing aggregated Ethernet link protection or LACP link protection configurations leads to aggregated Ethernet link flapping.

    • For a single physical link event of an aggregated Ethernet link configured on a 100-Gigabit Ethernet PIC with CFP, the packet loss performance value is twice the original value because of the two 50-Gigabit Ethernet interfaces of the 100-Gigabit Ethernet PIC with CFP.

    • The show interfaces aex command displays the link speed of the aggregated Ethernet interface, which is the sum of the link speeds of all the active member links.

  • Use the show interfaces aggregate-interface extensive and show interfaces aggregate.logical-interface commands to show the bandwidth of the aggregate. Also, the SNMP object identifier ifSpeed/ifHighSpeed shows the corresponding bandwidth on the aggregate logical interface if it is configured properly.

Configuring an Aggregated Ethernet Interface

On Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces on M Series and T Series routers, you can associate a physical interface with an aggregated Ethernet interface.

Note

On a Junos Fusion, you can include extended ports (physical interface on a satellite device that provides a connection to servers or endpoints) or local ports in link aggregation groups (LAGs) and MC-LAGs, but not both. For information on extended ports, see Understanding Junos Fusion Ports .

To configure an aggregated Ethernet interface:

  1. Specify that you want to configure the link aggregation group interface.
  2. Configure the aggregated Ethernet interface.

You specify the interface instance number x to complete the link association; x can be from 0 through 127, for a total of 128 aggregated interfaces on M Series and T Series routers and can be from 1 through 480, for a total of 480 aggregated interfaces on MX Series routers. For MX Series routers running Junos release 14.2R3 and later you can configure a maximum of 1000 aggregated interfaces. Aggregated interfaces are numbered from ae0 through ae4092.

Note

On MX2010 and MX2020 routers you can configure a maximum of 800 aggregated interfaces.

You must also include a statement defining aex at the [edit interfaces] hierarchy level. You can optionally specify other physical properties that apply specifically to the aggregated Ethernet interfaces; for details, see Ethernet Interfaces Overview, and for a sample configuration, see Example: Configuring Aggregated Ethernet Interfaces.

Note

In general, aggregated Ethernet bundles support the features available on all supported interfaces that can become a member link within the bundle. As an exception, Gigabit Ethernet IQ features and some newer Gigabit Ethernet features are not supported in aggregated Ethernet bundles.

Gigabit Ethernet IQ and SFP interfaces can be member links, but IQ- and SFP-specific features are not supported on the aggregated Ethernet bundle even if all the member links individually support those features.

You need to configure the correct link speed for the aggregated Ethernet interface to eliminate any warning message.

Note

Before you commit an aggregated Ethernet configuration, ensure that link mode is not configured on any member interface of the aggregated Ethernet bundle; otherwise, the configuration commit check fails.

Configuring Aggregated Ethernet Interfaces on PTX Series Packet Transport Routers

IEEE 802.3ad link aggregation enables you to group Ethernet interfaces to form a single link layer interface, also known as a link aggregation group (LAG) or bundle. Link aggregation can be used for point-to-point connections. It balances traffic across the member links within an aggregated Ethernet bundle and effectively increases the uplink bandwidth. Another advantage of link aggregation is increased availability because the LAG is composed of multiple member links. If one member link fails, the LAG continues to carry traffic over the remaining links.

This topic describes how to configure aggregated Ethernet interfaces on PTX Series Packet Transport Routers.

Support for Aggregated Ethernet Interfaces

On PTX Series Packet Transport Routers, aggregated Ethernet support includes the following features:

  • A consistent interface type (et fpc/pic/port) across all Ethernet interfaces.

  • Ability to bundle multiple Ethernet interfaces

  • Ability to bundle mixed-rate links on the same aggregated Ethernet interface

  • Fault tolerance

  • Load balancing between child links

  • Advanced features including flexible VLAN tagging and Ethernet services encapsulation

Understanding Aggregated Ethernet Interfaces on Junos OS Evolved

In PTX Series routers running Junos OS Evolved such as PTX1003 Series routers, VLAN-tagged aggregated Ethernet interfaces behave differently than interfaces that are not tagged.

  • In an untagged LAG, child IFL members are created. Requests are made per child IFL member. The results are aggregated and displayed in the CLI.

  • In a VLAN-tagged LAG, extra child IFLs are not created as part of the aggregated Ethernet bundle. Link IFL statistics and marker statistics for child IFLs are not displayed.

How to Configure Aggregated Ethernet Interfaces

Aggregated Ethernet interfaces can use interfaces from different FPCs or PICs. The following configuration is sufficient to get an aggregated Gigabit Ethernet interface up and running.

Configuring LACP for Aggregated Ethernet Interfaces

For aggregated Ethernet interfaces, you can configure the Link Aggregation Control Protocol (LACP). LACP is one method of bundling several physical interfaces to form one logical interface. You can configure both VLAN-tagged and untagged aggregated Ethernet with or without LACP enabled.

Note

Starting with Junos OS Release 14.1, you can configure aggregated Ethernet interfaces with LACP on logical systems within an MX Series router.

For Multichassis Link Aggregation (MC-LAG), you must specify the system-id and admin key. MC-LAG peers use the same system-id while sending the LACP messages. The system-id can be configured on the MC-LAG network device and synchronized between peers for validation.

LACP exchanges are made between actors and partners. An actor is the local interface in an LACP exchange. A partner is the remote interface in an LACP exchange.

LACP is defined in IEEE 802.3ad, Aggregation of Multiple Link Segments.

LACP was designed to achieve the following:

  • Automatic addition and deletion of individual links to the aggregate bundle without user intervention

  • Link monitoring to check whether both ends of the bundle are connected to the correct group

The Junos OS implementation of LACP provides link monitoring but not automatic addition and deletion of links.

The LACP mode can be active or passive. If the actor and partner are both in passive mode, they do not exchange LACP packets, which results in the aggregated Ethernet links not coming up. If either the actor or partner is active, they do exchange LACP packets. By default, LACP is turned off on aggregated Ethernet interfaces. If LACP is configured, it is in passive mode by default. To initiate transmission of LACP packets and response to LACP packets, you must configure LACP in active mode.

Note

LACP can link together multiple different physical interfaces, but only features that are supported across all of the linked devices will be supported in the resulting link aggregation group (LAG) bundle. For example, different PICs can support a different number of forwarding classes. If you use link aggregation to link together the ports of a PIC that supports up to 16 forwarding classes with a PIC that supports up to 8 forwarding classes, the resulting LAG bundle will only support up to 8 forwarding classes. Similarly, linking together a PIC that supports WRED with a PIC that does not support it will result in a LAG bundle that does not support WRED.

To enable LACP active mode, include the lacp statement at the [edit interfaces interface-name aggregated-ether-options] hierarchy level, and specify the active option:

Note

The LACP process exists in the system only if you configure the system in either active or passive LACP mode.

If you restart the Link Aggregation Control Protocol (LACP) process consecutively without adequate sleep or pause time between the successive restarts, the LACP links might flap. To avoid this problem, you must restart the LACP process only after the refresh time of the periodic packet management (PPM) process is completed.

To restore the default behavior, include the lacp statement at the [edit interfaces interface-name aggregated-ether-options] hierarchy level, and specify the passive option:

Starting with Junos OS Release 12.2, you can also configure LACP to override the IEEE 802.3ad standard and to allow the standby link always to receive traffic. Overriding the default behavior facilitates subsecond failover.

To override the IEEE 802.3ad standard and facilitate subsecond failover, include the fast-failover statement at the [edit interfaces interface-name aggregated-ether-options lacp] hierarchy level.

When you configure the accept-data statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level, the router processes packets received on a member link irrespective of the LACP state if the aggregated Ethernet bundle is up.

Note

When you use the accept-data statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level, this behavior occurs:

  • By default, the accept-data statement is not configured when LACP is enabled.

  • You can configure the accept-data statement to improve convergence and reduce the number of dropped packets when member links in the bundle are enabled or disabled.

  • When LACP is down and a member link receives packets, the router does not process packets as defined in the IEEE 802.1ax standard. According to this standard, the packets should be dropped, but they are processed instead because the accept-data statement is configured.

For more information, see the following sections:

Configuring the LACP Interval

By default, the actor and partner send LACP packets every second. You can configure the interval at which the interfaces send LACP packets by including the periodic statement at the [edit interfaces interface-name aggregated-ether-options lacp] hierarchy level:

The interval can be fast (every second) or slow (every 30 seconds). You can configure different periodic rates on active and passive interfaces. When you configure the active and passive interfaces at different rates, the transmitter honors the receiver’s rate.

Note

Starting with Junos OS Release 11.4, source address filtering does not work when LACP is enabled., This behavior is not applicable to T Series routers and PTX Series Packet Transport Routers. For more information about source address filtering, see Configuring MAC Address Filtering for Ethernet Interfaces.

Percentage policers are not supported on aggregated Ethernet interfaces with the CCC protocol family configured. For more information about percentage policers, see the Routing Policies, Firewall Filters, and Traffic Policers Feature Guide.

Generally, LACP is supported on all untagged aggregated Ethernet interfaces. For more information, see Configuring Untagged Aggregated Ethernet Interfaces.

For M Series Multiservice Edge Routers with enhanced Flexible PIC Concentrators (FPCs) and T Series routers, LACP over VLAN-tagged aggregated Ethernet interfaces is supported. For 8-port, 12-port, and 48-port Fast Ethernet PICs, LACP over VLAN-tagged interfaces is not supported.

LACP Fast Periodic, which is achieved by configuring fast (every second) intervals for periodic transmission of LACP packets, is supported with graceful Routing Engine switchover (GRES) on MX Series routers only.

To force active and standby links within an aggregated Ethernet, you can configure LACP link protection and system priority at the aggregated Ethernet interface level using the link-protection and system-priority statements. Configuring values at this level results in only the configured interfaces using the defined configuration. LACP interface configuration also enables you to override global (chassis) LACP settings.

LACP link protection also uses port priority. You can configure port priority at the Ethernet interface [gigether-options] hierarchy level using the port-priority statement. If you choose not to configure port priority, LACP link protection uses the default value for port priority (127).

Note
  • When using LACP link protection, you can configure only two member links to an aggregated Ethernet interface: one active and one standby.

  • LACP link protection supports per-unit scheduling configuration on aggregated Ethernet interfaces.

To enable LACP link protection for an aggregated Ethernet interface, use the link-protection statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level:

By default, LACP link protection reverts to a higher-priority (lower-numbered) link when that higher-priority link becomes operational or a link is added to the aggregator that is determined to be higher in priority. However, you can suppress link calculation by adding the non-revertive statement to the LACP link protection configuration. In nonrevertive mode, once a link is active and collecting and distributing packets, the subsequent addition of a higher-priority (better) link does not result in a switch and the current link remains active.

If LACP link protection is configured to be nonrevertive at the global ([edit chassis] hierarchy) level, you can add the revertive statement to the LACP link protection configuration to override the nonrevertive setting for the interface. In revertive mode, the addition of a higher-priority link to the aggregator results in LACP performing a priority recalculation and switching from the current active link to the new active link.

Caution

If both ends of an aggregator have LACP link protection enabled, make sure to configure both ends of the aggregator to use the same mode. Mismatching LACP link protection modes can result in lost traffic.

We strongly recommend that you use LACP on both ends of the aggregator, when you connect an aggregated Ethernet interface with two member interfaces of MX Series routers to any other vendor device. Otherwise, the vendor device (say a Layer 2 switch, or a router) will not be able to manage the traffic coming from the two link aggregated Ethernet bundle. As a result, you might observe the vendor device sending back the traffic to the backup member link of the aggregated Ethernet interface.

Currently, MX-MPC2-3D, MX-MPC2-3D-Q, MX-MPC2-3D-EQ, MX-MPC1-3D, MX-MPC1-3D-Q, and MPC-3D-16XGE-SFPP do not drop traffic coming back to the backup link, whereas DPCE-R-Q-20GE-2XGE, DPCE-R-Q-20GE-SFP, DPCE-R-Q-40GE-SFP, DPCE-R-Q-4XGE-XFP, DPCE-X-Q-40GE-SFP, and DPCE-X-Q-4XGE-XFP drop traffic coming to the backup link.

Configuring LACP System Priority

To configure LACP system priority for aggregated Ethernet interfaces on the interface, use the system-priority statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level:

The system priority is a 2-octet binary value that is part of the LACP system ID. The LACP system ID consists of the system priority as the two most-significant octets and the interface MAC address as the six least-significant octets. The system with the numerically lower value for system priority has the higher priority. By default, system priority is 127, with a range of 0 to 65,535.

Configuring LACP System Identifier

To configure the LACP system identifier for aggregated Ethernet interfaces, use the system-id statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level:

Starting with Junos OS Release 13.3, youmust not configure the LACP system identifier by using the system-id system-id statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level to be all zeros (00:00:00:00:00:00). If you attempt to commit a configuration with the system identifier to be all zeros, an error occurs during the commit operation.

The user-defined system identifier in LACP enables two ports from two separate routers (M Series or MX Series routers) to act as though they were part of the same aggregate group.

The system identifier is a 48-bit (6-byte) globally unique field. It is used in combination with a 16-bit system-priority value, which results in a unique LACP system identifier.

Configuring LACP administrative Key

To configure an administrative key for LACP, include the admin-key number statement at the [edit interfaces aex aggregated-ether-options lacp] hierarchy level:

Note

You must configure MC-LAG to configure the admin-key statement. For more information about MC-LAG, see Configuring Multichassis Link Aggregation on MX Series Routers.

Configuring LACP Port Priority

To configure LACP port priority for aggregated Ethernet interfaces, use the port-priority statement at the [edit interfaces interface-name gigether-options 802.3ad aeX lacp] or [edit interfaces interface-name fastether-options 802.3ad aeX lacp] hierarchy levels:

The port priority is a 2-octet field that is part of the LACP port ID. The LACP port ID consists of the port priority as the two most-significant octets and the port number as the two least-significant octets. The system with the numerically lower value for port priority has the higher priority. By default, port priority is 127, with a range of 0 to 65,535.

Port aggregation selection is made by each system based on the highest port priority and is assigned by the system with the highest priority. Ports are selected and assigned starting with the highest priority port of the highest priority system and working down in priority from there.

Note

Starting with Junos OS Release 9.3, port aggregation selection (discussed previously) is performed for the active link when LACP link protection is enabled. Without LACP link protection, port priority is not used in port aggregation selection.

On link aggregation group (LAG) interfaces, when a member (child) link goes down, its state changes from current to expired. This link might flap from the current state to the expired state and back to current state when it receives intermittent LACP protocol data units (PDUs) and keepalive timeouts. Such flapping can adversely affect the traffic on the link.

To prevent excessive flapping of a LAG child link, you can configure a hold-up timer on the LAG interface that is applicable to all member links on that particular interface. To hold up, in networking terms, means to prevent the transitioning of an interface from down to up for a specified time interval.

When configured, the hold-up timer is triggered when an LACP state machine tries to move to the current state from the expired or default state when it receives an LACP PDU. The hold-up timer is triggered only if the LACP state machine had acquired the current state at least once earlier. The timer is not triggered if LACP attempts to transition to the current state for the first time. LACP monitors the PDUs received on the child link but prevents the link from transitioning to current state. If no flapping is observed when the link receives the PDUs, the hold-up timer expiries and triggers the member link to transition back to the current state. This transition is triggered as soon as the hold-up timer expires and not necessarily when the link receives a PDU.

To configure LACP hold-up timer for LAG interface, use the hold-time up statement at the [edit interfaces aex aggregated-ether-options lacp] hierarchy level.

Note
  • The hold-up timer keeps running even when the interface that receives the LACP PDU moves to the port disable state. The timer is then restarted if, before the timer expires, the interface comes up again and receives an LACP PDU from its neighbor. This ensures that the timer is maintained even during a quick physical port flap.

  • When the following events occur, a hold-up timer is not triggered until the member link acquires the current state after the event:

    • LACP daemon restart

    • Deactivation and reactivation of child or aggregated Ethernet interface

    • Deletion and reconfiguration of child or aggregated Ethernet interface

    • System reboot

    • Routing Engine switchover

Tracing LACP Operations

To trace the operations of the LACP process, include the traceoptions statement at the [edit protocols lacp] hierarchy level:

Sample Configuration for Configuring Aggregated Ethernet LACP on Tagged and Untagged Interfaces

Following configurations are examples of configuring aggregated Ethernet LACP on VLAN-tagged and untagged interfaces:

LACP with VLAN-Tagged Aggregated Ethernet

LACP with Untagged Aggregated Ethernet

Configuring Junos OS for Supporting Aggregated Devices

Junos OS supports the aggregation of physical devices into defined virtual links, such as the link aggregation of Ethernet interfaces defined by the IEEE 802.3ad standard.

Tasks for configuring aggregated devices are:

To define virtual links, you need to specify the associations between physical and logical devices within the [edit interfaces] hierarchy, and assign the correct number of logical devices by including the device-count statement at the [edit chassis aggregated-devices ethernet] and [edit chassis aggregated-devices sonet] hierarchy levels:

The aggregated interfaces are numbered from ae0 through ae4091. The maximum number of aggregated interfaces supported by different routers is listed below:

  • For PTX Series routers, you can configure a maximum of 128 aggregated interfaces.

  • For M Series and T Series routers, you can configure a maximum of 128 aggregated interfaces (LAG bundles).

  • In Junos release 14.2R2 and earlier, you can configure a maximum of 480 aggregated interfaces on MX Series routers.

  • In Junos release 14.2R3 and later, you can configure a maximum of 1000 aggregated interfaces on MX240, MX480, and MX960 routers.

  • In Junos release 14.2R3 and later, you can configure a maximum of 800 aggregated interfaces on MX2010 and MX2020 routers.

  • In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 480 aggregated interfaces on MX240, MX480, and MX960 routers.

  • In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 800 aggregated interfaces on MX2010 and MX2020 routers.

For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical interfaces is 64, numbered from as0 through as63. In releases before Junos OS Release 13.2, the maximum was 16.

Link Aggregation Control Protocol (LACP) is one method of bundling several physical interfaces to form one logical interface. You can configure both VLAN-tagged and untagged aggregated Ethernet with or without LACP enabled. LACP exchanges are made between actors and partners. An actor is the local interface in an LACP exchange. A partner is the remote interface in an LACP exchange.

LACP link protection enables you to force active and standby links within an aggregated Ethernet. You configure LACP link protection by using the link-protection and system-priority statements at either the chassis or interface level and by configuring port priority at the interface level using the system-priority statement. Configuring LACP parameters at the chassis level results in all aggregated Ethernet interfaces using the defined values unless overridden by the LACP configuration on a specific interface.

Note

LACP link protection also uses port priority. You can configure port priority at the Ethernet interface [gigether-options] hierarchy level using the port-priority statement. If you choose not to configure port priority, LACP link protection uses the default value for port priority (127).

See also

To enable LACP link protection for aggregated Ethernet interfaces on the chassis, use the link-protection statement at the [edit chassis aggregated-devices ethernet lacp] hierarchy level:

By default, LACP link protection reverts to a higher-priority (lower-numbered) link when that higher-priority link becomes operational or a link is added to the aggregator that is determined to be higher in priority. However, you can suppress link calculation by adding the non-revertive statement to the LACP link protection configuration. In nonrevertive mode, after a link is active and collecting and distributing packets, the subsequent addition of a higher-priority (better) link does not result in a switch, and the current link remains active.

Best Practice

(MX Series) In a highly scaled configuration over aggregated Ethernet, we recommend that you prevent the router from performing such a switch by including the non-revertive statement. Failure to do so may result in some traffic loss if a MIC on which a member interface is located reboots. Using the non-revertive statement for this purpose is not effective if both the primary and secondary interfaces are on the MIC that reboots.

Caution

If both ends of an aggregator have LACP link protection enabled, make sure to configure both ends of the aggregator to use the same mode. Mismatching LACP link protection modes can result in lost traffic.

Configuring System Priority

To configure LACP system priority for aggregated Ethernet interfaces on the chassis, use the system-priority statement at the [edit chassis aggregated-devices ethernet lacp] hierarchy level:

The system priority is a 2-octet binary value that is part of the LACP system ID. The LACP system ID consists of the system priority as the two most-significant octets and the interface MAC address as the six least-significant octets. The system with the numerically lower value for system priority has the higher priority. By default, system priority is 127, with a range of 0 through 65,535.

To configure the maximum links limit, use the maximum-links statement at the [edit chassis aggregated-devices] hierarchy level:

Configuring PPM on Junos Fusion

If you use Junos Fusion with Junos OS Release 14.2R3, you need to ensure that link aggregation (and STP) work properly by configuring timers for the periodic packet management (PPM) daemons on the aggregation and satellite devices. We recommend using the following timer values:

Starting in Junos OS Release 14.2R4, the timer values that ensure proper link aggregation and STP functions are configured by default if you use Junos Fusion with Junos OS.

Configuring the Number of Aggregated Ethernet Interfaces on the Device

By default, no aggregated Ethernet interfaces are created. You must set the number of aggregated Ethernet interfaces on the routing device before you can configure them.

For M Series and T Series routers you can configure a maximum of 128 aggregated interfaces (LAG bundles). On MX Series routers running Junos release 14.2R2 and earlier, you can configure a maximum of 480 aggregated interfaces. For MX Series routers running Junos release 14.2R3 and later you can configure a maximum of 1000 aggregated interfaces. For MX2010 and MX2020 routers you can configure a maximum of 800 aggregated interfaces. In all cases the aggregated interfaces are numbered from ae0 through ae4092

Note

On a Junos Fusion Fabric, you can include extended ports (physical interface on a satellite device that provides a connection to servers or endpoints) or local ports in link aggregation groups (LAGs) and MC-LAGs, but not both. For information on extended ports, see Understanding Junos Fusion Ports .

For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical interfaces is 16, numbered from as0 through as15.

  1. Specify that you want to access the aggregated Ethernet configuration on the device.
  2. Set the number of aggregated Ethernet interfaces.

You must also specify the constituent physical links by including the 802.3ad statement at the [edit interfaces interface-name fastether-options] or [edit interfaces interface-name gigether-options] hierarchy level.

On aggregated Ethernet interfaces, you can set the required link speed for all interfaces included in the bundle. Generally, all interfaces that make up a bundle must have the same speed. If you include in the aggregated Ethernet interface an individual link that has a speed different from the speed that you specify in the link-speed parameter, an error message is logged. However, there are exceptions.

Starting with Junos OS Release 13.2, aggregated Ethernet supports mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers. For example, these mixes are supported:

  • Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.

  • Member links of different rates: 10-Gigabit Ethernet, 40-Gigabit Ethernet, 50-Gigabit Ethernet, 100-Gigabit Ethernet, and OC192 (10-Gigabit Ethernet WAN mode)

Starting with Junos OS Release 14.1R1 and 14.2, support for mixed rates on aggregated Ethernet bundles is extended to MX240, MX480, MX960, MX2010, and MX2020 routers.

Starting with Junos OS Release 14.2, aggregated Ethernet supports mixed link speeds on PTX Series Packet Transport Routers.

Note
  • Member links of 50-Gigabit Ethernet can only be configured using the 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).

  • Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP. This 100-Gigabit Ethernet member link can be included in an aggregated Ethernet link that includes member links of other interfaces as well. In releases before Junos OS Release 13.2, the 100-Gigabit Ethernet member link configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP cannot be included in an aggregated Ethernet link that includes member links of other interfaces.

To configure member links of mixed rates and mixed modes on T640, T1600, T4000, TX Matrix Plus, and PTX routers, you need to configure the mixed option for the [edit interfaces aex aggregated-ether-options link-speed] statement.

To set the required link speed:

  1. Specify that you want to configure the aggregated Ethernet options.
  2. Configure the link speed.

    speed can be in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000).

    Aggregated Ethernet interfaces on the M120 router can have one of the following speeds:

    • 100m—Links are 100 Mbps.

    • 10g—Links are 10 Gbps.

    • 1g—Links are 1 Gbps.

    • oc192—Links are OC192 or STM64c.

    Aggregated Ethernet links on EX Series switches can be configured to operate at one of the following speeds:

    • 10m—Links are 10 Mbps.

    • 100m—Links are 100 Mbps.

    • 1g—Links are 1 Gbps.

    • 10g—Links are 10 Gbps.

    • 50g—Links are 50 Gbps.

    Aggregated Ethernet links on T Series, MX Series, PTX Series routers, and QFX5100, QFX10002, QFX10008, and QFX10016 switches can be configured to operate at one of the following speeds:

    • 100g—Links are 100 Gbps.

    • 100m—Links are 100 Mbps.

    • 10g—Links are 10 Gbps.

    • 1g—Links are 1 Gbps.

    • 40g—Links are 40 Gbps.

    • 50g—Links are 50 Gbps.

    • 80g—Links are 80 Gbps.

    • 8g—Links are 8 Gbps.

    • mixed—Links are of various speeds.

    • oc192—Links are OC192.

Configuring Multicast Statistics Collection on Aggregated Ethernet Interfaces

T Series and TX Matrix routers support multicast statistics collection on aggregated Ethernet interfaces in both ingress and egress directions. The multicast statistics functionality can be configured on a physical interface thus enabling multicast accounting for all the logical interfaces below the physical interface.

The multicast statistics information is displayed only when the interface is configured with the multicast-statistics statement, which is not enabled by default.

Multicast statistics collection requires at least one logical interface is configured with family inet or inet6; otherwise, the commit for multicast-statistics will fail.

The multicast in/out statistics can be obtained via interfaces statistics query through CLI and via MIB objects through SNMP query.

To configure multicast statistics:

  1. Include the multicast-statistics statement at the [edit interfaces interface-name] hierarchy level.

An example of a multicast statistics configuration for an aggregated Ethernet interface follows:

To display multicast statistics, use the show interfaces interface-name statistics detail command.

Example: Configuring Aggregated Ethernet Interfaces

Aggregated Ethernet interfaces can use interfaces from different FPCs, DPCs, or PICs. The following configuration is sufficient to get an aggregated Gigabit Ethernet interface up and running.

Understanding Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles

You can configure the member links of an aggregated Ethernet bundle with any combination of rates— also known as mixed rates— on T Series, MX Series, and PTX Series routers. The bandwidth that is provided by an aggregated Ethernet bundle can be utilized completely and efficiently when the links are configured with different rates.

You can configure mixed modes on T Series routers. In a mixed-mode configuration, the member links of an aggregated Ethernet bundle are configured in LAN mode as well as in WAN mode for 10-Gigabit Ethernet interfaces. For information on the first Junos OS release that supports aggregated Ethernet bundles on the various Juniper Networks routers, see Feature Explorer.

The following sections provide an overview about mixed rates and mixed modes on various platforms:

Aggregated Ethernet Bundle with Mixed Rates and Mixed Modes on T Series Routers

The following sections explain mixed rates and mixed modes on T Series routers:

Understanding Mixed Rates and Mixed Modes

Starting with Junos OS Release 13.2, aggregated Ethernet supports the following mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers:

  • Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.

  • Member links of different rates: 10-Gigabit Ethernet, 40-Gigabit Ethernet, 50-Gigabit Ethernet, 100-Gigabit Ethernet, and OC192 (10-Gigabit Ethernet WAN mode)

Note
  • Member links of 50-Gigabit Ethernet can only be configured using the 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).

  • Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP. This 100-Gigabit Ethernet member link can be included in an aggregated Ethernet link that includes member links of other interfaces as well.

    In releases before Junos OS Release 13.2, the 100-Gigabit Ethernet member link configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP cannot be included in an aggregated Ethernet link that includes member links of other interfaces.

Going forward:

  • An aggregated Ethernet link with member links of different modes is referred to as 10-Gigabit Ethernet mixed-mode aggregated Ethernet link.

  • An aggregated Ethernet link with member links of different rates is referred to as mixed-rate aggregated Ethernet link.

  • These aggregated Ethernet links will generically be referred to as mixed aggregated Ethernet links.

Platform Support Matrix for Mixed Aggregated Ethernet Bundles

Table 2 lists the platforms and corresponding hardware components that support mixed aggregated Ethernet bundles.

Table 2: Platform Support Matrix for Mixed Aggregated Ethernet Bundles

Rate and Mode

Supported Platform

Supported FPCs

Supported PICs

10-Gigabit Ethernet LAN and WAN

(WAN rate: OC192)

T640, T1600, T4000, and TX Matrix Plus routers

  • T4000 FPC5 (T4000-FPC5-3D)

  • 10-Gigabit Ethernet LAN/WAN PIC with Oversubscription and SFP+ (PF-24XGE-SFPP)

  • 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-12XGE-SFPP)

  • Enhanced Scaling FPC3 (T640-FPC3-ES)

  • 10-Gigabit Ethernet PIC with XENPAK (PC-1XGE-XENPAK)

  • Enhanced Scaling FPC4 (T640-FPC4-ES)

  • Enhanced Scaling FPC4-1P (T640-FPC4-1P-ES)

  • T1600 Enhanced Scaling FPC4 (T1600-FPC4-ES)

  • 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PD-5-10XGE-SFPP)

  • 10-Gigabit Ethernet LAN/WAN PIC with XFP (PD-4XGE-XFP)

40-Gigabit Ethernet, 100-Gigabit Ethernet

T4000 and TX Matrix Plus routers

  • T4000 FPC5 (T4000-FPC5-3D)

  • 100-Gigabit Ethernet PIC with CFP (PF-1CGE-CFP)

 

T640, T1600, T4000, and TX Matrix Plus routers

  • Enhanced Scaling FPC4 (T640-FPC4-ES)

  • Enhanced Scaling FPC4-1P (T640-FPC4-1P-ES)

  • T1600 Enhanced Scaling FPC4 (T1600-FPC4-ES)

  • 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4)

    Note: This PIC is available packaged only in an assembly with the T1600-FPC4-ES FPC.

  • 40-Gigabit Ethernet PIC with CFP (PD-1XLE-CFP)

Guidelines to Follow When Configuring Aggregated Ethernet Bundles with Mixed Rates and Mixed Modes

In addition to the configuration guidelines for aggregated Ethernet interfaces in Aggregated Ethernet Interfaces Overview, you must consider the following as well when configuring mixed modes and mixed rates on aggregated Ethernet bundles on T640, T1600, T4000, and TX Matrix Plus routers:

  • A maximum of 16 member links can be configured to form a mixed aggregated Ethernet link.

  • Link Aggregation Control Protocol (LACP), aggregated Ethernet link protection, and LACP link protection are supported only on mixed aggregated Ethernet bundles configured on a 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).

  • Traffic distribution is based on the hash calculated on the egress packet header. Hash range is fairly distributed according to member links’ speed. This guarantees hash fairness but it does not guarantee fair traffic distribution depending on the rate of the egress streams.

  • Packets are dropped when the total throughput of the hash flow exiting a member link (or multiple hash flows exiting a single member link) exceeds the link speed of the member link. This can happen when egress member link changes because of a link failure and the hash flow switches to a member link of speed that is less than the total throughput of the hash flow.

  • Rate-based CoS components such as scheduler, shaper, and policer are not supported on mixed-rate aggregated Ethernet links. However, the default CoS settings are supported by default on the mixed-rate aggregated Ethernet links.

  • Load balancing is performed at the ingress Packet Forwarding Engine. Therefore, you must ensure that the egress traffic on the aggregated Ethernet link enters through the hardware platforms that support mixed aggregated Ethernet bundles. Table 2 lists the platforms and corresponding hardware components that support mixed aggregated Ethernet bundles.

  • Mixed aggregated Ethernet links can interoperate with non-Juniper Networks aggregated Ethernet member links provided that mixed aggregated Ethernet load balancing is configured at egress.

  • Load balancing of the egress traffic across the member links of a mixed-rate aggregated Ethernet link is proportional to the rates of the member links.

  • Egress multicast load balancing is not supported on mixed aggregated Ethernet interfaces.

  • Changing the [edit interfaces aex aggregated-ether-options link-speed] configuration of a mixed aggregated Ethernet link, which is configured on the supported interfaces of on T640, T1600, T4000, and TX Matrix Plus routers, leads to aggregated Ethernet link flapping.

  • When configuring a mixed aggregated Ethernet link on a 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4), ensure that you add both the 50-Gigabit Ethernet interfaces of the 100-Gigabit Ethernet PIC with CFP to the aggregated Ethernet bundle. Moreover, both these 50-Gigabit Ethernet interfaces must be included in the same aggregated Ethernet bundle.

  • When a mixed aggregated Ethernet link is configured on a 100-Gigabit Ethernet PIC with CFP, changing aggregated Ethernet link protection or LACP link protection configurations leads to aggregated Ethernet link flapping.

  • For a single physical link event of an aggregated Ethernet link configured on a 100-Gigabit Ethernet PIC with CFP, the packet loss performance value is twice the original value because of the two 50-Gigabit Ethernet interfaces of the 100-Gigabit Ethernet PIC with CFP.

  • The show interfaces aex command displays the link speed of the aggregated Ethernet interface, which is the sum of the link speeds of all the active member links.

Aggregated Ethernet Bundles with Mixed Rates on MX Series Routers and PTX Series Routers

The following sections explain mixed rates on aggregated Ethernet bundles:

Understanding Mixed Rates

Starting with Junos OS Release 14.2, support for mixed rates on aggregated Ethernet bundles is extended to MX240, MX480, MX960, MX2010, and MX2020 routers, thereby enabling you to configure the member links with any combination of rates— 10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet— on an aggregated Ethernet bundle.

You must configure the mixed statement explicitly at the [edit interfaces interface-name aggregated-ether-options link-speed] hierarchy level to:

  • Enable the mixed-rate configuration on all the aggregated Ethernet bundles on the egress side of the Modular Port Concentrators (MPCs).

  • Enable the router to detect child links of different speed values in the aggregated Ethernet bundle.

You can also configure the minimum bandwidth on an aggregated Ethernet bundle when you configure mixed rate on that aggregated Ethernet bundle.

Note

The minimum-link statement cannot be configured with mixed rates.

Mixed rates cannot be configured for aggregated Ethernet bundles on the egress side of the Dense Port concentrators (DPCs).

When you configure mixed rate on a homogeneous aggregated Ethernet bundle— where all the links in the bundle are of the same speed— the aggregated Ethernet bundle goes down and then comes up with the mixed-rate configuration.

Platform Support Matrix for Mixed Aggregated Ethernet Bundles on MX Series Routers

Table 3 lists the platforms and corresponding MPCs that support mixed aggregated Ethernet bundles on MX Series routers.

Table 3: Platform Support Matrix for Mixed Aggregated Ethernet Bundles on MX Series Routers

Supported MPCs

Supported Platform

Initial Release

16x10GE (MPC-3D-16XGE-SFPP)

MX240, MX480, MX960, MX2010, and MX2020

14.2R1

MPC1E (MX-MPC1-3D; MX-MPC1E-3D; MX-MPC-1-3D-Q; MX-MPC1E-3D-Q)

MX240, MX480, MX960, MX2010, and MX2020

14.2R1

MPC2E (MX-MPC2-3D; MX-MPC2E-3D; MX-MPC2-3D-Q;MX-MPC2E-3D-Q; MX-MPC2-3D-EQ;MX-MPC2E-3D-EQ; MX-MPC2-3D-P)

MX240, MX480, MX960, MX2010, and MX2020

14.2R1

MPC3E (MX-MPC3E-3D)

MX240, MX480, MX960, MX2010, and MX2020

14.2R1

MPC4E (MPC4E-3D-32XGE-SFPP and MPC4E-3D-2CGE-8XGE)

MX240, MX480, MX960, MX2010, and MX2020

14.2R1

MPC5E (6x40GE+24x10GE;6x40GE+24x10GEQ;2x100GE+4x10GE; 2x100GE+4x10GEQ)

MX240, MX480, MX960, MX2010, and MX2020

14.2R1

MPC6E (MX2K-MPC6E)

MX2010 and MX2020

14.2R1

MPC7E (Multi-Rate) (MPC7E-MRATE)

MX240, MX480, MX960, MX2010, and MX2020

15.1F4

 
 

MPC7E 10G (MPC7E-10G)

MX240, MX480, MX960, MX2010, and MX2020

15.1F5

MPC8E (MX2K-MPC8E)

MX2010 and MX2020

15.1F5

MPC9E (MX2K-MPC9E)

MX2010 and MX2020

15.1F5

MPC10E (MPC10E-15C-MRATE)

MX240, MX480, and MX960

19.1R1

Supported Features

The following features are supported on mixed-rate aggregated Ethernet bundles on MX Series routers and PTX Series Routers:

Note

Starting with Junos OS Release 19.2R1, you can configure any number of aggregated Ethernet Interfaces in a mixed rate aggregated Ethernet bundle on MX Series routers and PTX Series routers. In earlier releases, you can configure only 64 aggregated Ethernet Interfaces in a mixed-rate aggregated Ethernet bundle.

  • Load balancing of traffic in proportion to the member-link speed.

  • Non link-protect mode. For more information, see Configuring Scheduler on Aggregated Ethernet Interfaces Without Link Protection.

  • LACP for slow and fast interval for periodic transmission of LACP packets.

  • Port-based network access control (NAC).

  • Scheduler parameters for aggregated interface member links in a scaled manner with the member-link-scheduler scale statement at the [edit class-of-service interfaces] hierarchy level.

  • Layer 3 features only.

  • Configuration of following statements as percentages only for mixed rates at the [edit class-of-service schedulers scheduler-name] hierarchy level:

    • buffer-size

    • excess-rate

    • shaping-rate

    • transmit-rate

  • Configuration of the following statements for mixed rates at the [edit class-of-service schedulers scheduler-name] hierarchy level:

    • drop-profile-map

    • excess-priority

    • priority

    • transmit-rate (rate-limit | exact)

  • The shared-bandwidth-policer statement at the [edit firewall policer policer-name] hierarchy level.

  • The scheduler-maps map-name statement at the [edit class-of-service] hierarchy level.

  • Unicast load balancing, where the load balancing happens on ingress-only selectors.

  • Mulitcast load balancing

  • Make-before-break (MBB) for multicast LDP (MLDP) and fast reroute (FRR).

  • Source class usage (SCU) and destination class usage (DCU) accounting.

  • Families inet, inet6, mpls and iso.

  • Enhanced IP network services.

  • LDP tunneling and OAM link fault management (LFM).

The following features are not supported on mixed-rate aggregated Ethernet bundles on MX Series routers and PTX Series routers:

  • Adaptive load balancing

  • Hierarchical schedulers on aggregated Ethernet bundles and the scheduling on logical interfaces (per-unit scheduling).

  • Shaping rate, where traffic shaping is achieved by specifying the amount of bandwidth to be allocated to a logical interface.

  • The output-traffic-control-profile statement at the [edit class-of-service interfaces interface-name] hierarchy level.

  • Ingress queuing.

  • Options that are configured with nonpercentage values at the [edit class-of-service schedulers scheduler-name] hierarchy level.

  • The member-link-scheduler replicate statement at the [edit class-of-service interfaces interface-name] hierarchy level.

  • Mixing LAN mode and WAN mode.

  • Aggregated Ethernet link protection and link protection on a 1:1 model.

  • LACP link protection.

  • Layer 2 features.

  • The target-routing-instance (routing-instance-name | default) statement at the [edit access domain map domain-map-name] hierarchy level.

Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles

The following sections explain how to configure mixed rates and mixed modes on various platforms:

Configuring Mixed Rates and Mixed Modes on an Aggregated Ethernet Bundle on T Series Routers

In releases before Junos OS Release 13.2, all interfaces that form an aggregated Ethernet bundle must have the same speed and must be in full-duplex mode. Starting with Junos OS Release 13.2, aggregated Ethernet supports mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers. Following mixed rates and mixed modes are supported:

  • Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.

  • Member links of different rates: 10-Gigabit Ethernet, 40-Gigabit Ethernet, 50-Gigabit Ethernet, 100-Gigabit Ethernet, and OC192 (10-Gigabit Ethernet WAN mode)

Note
  • Member links of 50-Gigabit Ethernet can be configured using only the 50-Gigabit Ethernet interfaces of the 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).

  • Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP. This 100-Gigabit Ethernet member link can be included in an aggregated Ethernet link that includes member links of other interfaces as well. In releases before Junos OS Release 13.2, the 100-Gigabit Ethernet member link configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP cannot be included in an aggregated Ethernet link that includes member links of other interfaces.

To configure member links of an aggregated Ethernet bundles in mixed rate or mixed mode on T640, T1600, T4000, and TX Matrix Plus routers:

  1. Go to [edit chassis] hierarchy level.
  2. Configure the number of aggregated logical devices available to the router:
  3. Go to the [edit interfaces] hierarchy level.
  4. Configure the minimum number of links that are required for the aggregated Ethernet bundle to be labeled up:
    Note

    By default, only one link needs to be up for the bundle to be labeled up.

  5. Configure the link-speed statement and specify the mixed option for the link-speed statement to indicate the mixed-rate and mixed-mode support for the aggregated Ethernet bundle configuration.
    Note

    It is mandatory to configure the mixed option for aggregated Ethernet bundles for the PD-1CE-CFP-FPC4 PIC.

    On aggregated Ethernet bundles in MX Series routers, when the mixed statement at the [edit interfaces aex aggregated-ether-options link-speed] hierarchy level is not configured, the mixed rate configuration is applied by default.

  6. Configure the members links of the aggregated Ethernet bundle.
  7. Configure an interface family and an IP address for the aggregated Ethernet bundle.
  8. Commit the configuration.

Configuring Mixed Rates on Aggregated Ethernet Bundles on MX Series Routers

Starting with Junos OS Release 14.1R1 and 14.2, support for mixed rates on aggregated Ethernet bundles is extended to MX240, MX480, MX960, MX2010, and MX2020 routers. You can now configure the member links with any combination of rates—10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet—on an aggregated Ethernet bundle.

To configure mixed rates on an aggregated Ethernet bundle on MX Series routers:

  1. Go to the [edit chassis] hierarchy level.
  2. Configure the number of aggregated logical devices available to the router.
  3. Go to the [edit interfaces] hierarchy level.
  4. Configure the link-speed statement and specify the mixed option for the link-speed statement to indicate the mixed-rate support for the aggregated Ethernet bundle configuration.
  5. Configure the members links of the aggregated Ethernet bundle:
  6. Configure an interface family for the aggregated Ethernet bundle as inet, inet6, or mpls:
  7. Configure the minimum bandwidth unit as bps, gbps, kbps, or mbps and the bandwidth value from 1 through 128,000.
  8. Commit the configuration.

Configuring Tagged Aggregated Ethernet Interfaces

To specify aggregated Ethernet interfaces, include the vlan-tagging statement at the [edit interfaces aex] hierarchy level:

You must also include the vlan-id statement:

You can include this statement at 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]

For more information about the vlan-tagging and vlan-id statements, see 802.1Q VLANs Overview.

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 4 lists untagged aggregated Ethernet and LACP support by PIC and router.

Table 4: 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.

Understanding Independent Micro BFD Sessions for LAG

Starting with Junos OS Release 13.3, this feature is supported on the following PIC/FPC types:

  • PC-1XGE-XENPAK (Type 3 FPC)

  • PD-4XGE-XFP (Type 4 FPC)

  • PD-5-10XGE-SFPP (Type 4 FPC)

  • 24x10GE (LAN/WAN) SFPP, 12x10GE (LAN/WAN) SFPP, 1x100GE Type 5 PICs

  • All MPCs on MX Series with Ethernet MICs

  • FPC-PTX-P1-A on PTX5000 with 10-Gigabit Ethernet interfaces

  • FPC2-PTX-P1A on PTX5000 with 10-Gigabit Ethernet interfaces in Junos OS Release 14.1 and later

  • All FPCs on PTX Series with Ethernet interfaces in Junos OS Release 14.1R3 and later 14.1 releases, and Junos 14.2 and later

Tip

See PTX Series PIC/FPC Compatibility for a list of PICs that are supported on each PTX Series FPC.

Note

Micro-BFD configuration with interface addresses is not supported on PTX routers on FPC3 and QFX10000 line of switches.

The Bidirectional Forwarding Detection (BFD) protocol is a simple detection protocol that quickly detects failures in the forwarding paths. A link aggregation group (LAG) combines multiple links between devices that are in point-to-point connections, thereby increasing bandwidth, providing reliability, and allowing load balancing. To run a BFD session on LAG interfaces, configure an independent, asynchronous mode BFD session on every LAG member link in a LAG bundle. Instead of a single BFD session monitoring the status of the UDP port, independent micro BFD sessions monitor the status of individual member links.

The individual BFD sessions determine the Layer 2 and Layer 3 connectivity of each member link in the LAG. Once a BFD session is established on a particular link, the member links are attached to the LAG and the load balancer either by a static configuration or by the Link Aggregation Control Protocol (LACP). If the member links are attached to the LAG by a static configuration, the device control process acts as the client to the micro BFD session. When member links are attached to the LAG by the LACP, the LACP acts as the client to the micro BFD session.

When the micro BFD session is up, a LAG link is established and data is transmitted over that LAG link. If the micro BFD session on a member link is down, that particular member link is removed from the load balancer, and the LAG managers stop directing traffic to that link. These micro BFD sessions are independent of each other despite having a single client that manages the LAG interface.

Note
  • Starting with Junos OS Release 13.3, IANA has allocated 01-00-5E-90-00-01 as the dedicated MAC address for micro BFD. Dedicated MAC mode is used by default for micro BFD sessions, in accordance with the latest draft for BFD over LAG.

  • In Junos OS, MicroBFD control packets are always untagged by default. For L2 aggregated interfaces, the configuration must include vlan-tagging or flexible-vlan-tagging in the Aggregated Ethernet with BFD. Otherwise, the system will throw error while committing the configuration.

  • When you enable MicroBFD on an aggregated Ethernet Interface, the aggregated Interface can receive MicroBFD packets. Starting with Junos OS Release 19.3 and later, for MPC10E and MPC11E MPCs, you cannot apply firewall filters on the MicroBFD packets received on the aggregated Ethernet Interface. For MPC1E through MPC9E, you can apply firewall filters on the MicroBFD packets received on the aggregated Ethernet Interface only if the aggregated Ethernet Interface is configured as an untagged Interface.

Micro BFD sessions run in the following modes:

  • Distribution Mode—Micro BFD sessions are distributed by default at Layer 3.

  • Non-Distribution Mode—You can configure the BFD session to run in this mode by including the no-delegate-processing statement under periodic packet management (PPM). In this mode, the packets are being sent or received by the Routing Engine at Layer 2.

A pair of routing devices in a LAG exchange BFD packets at a specified, regular interval. The routing device detects a neighbor failure when it stops receiving a reply after a specified interval. This allows the quick verification of member link connectivity with or without LACP. A UDP port distinguishes BFD over LAG packets from BFD over single-hop IP.

Note

IANA has allocated 6784 as the UDP destination port for micro BFD.

To enable failure detection for LAG networks for aggregated Ethernet interfaces:

  • Include the bfd-liveness-detection statement in the configuration.

  • Specify a hold-down interval value to set the minimum time that the BFD session must remain up before a state change notification is sent to the other members in the LAG network.

  • Specify the minimum interval that indicates the time interval for transmitting and receiving data.

  • Starting with Junos OS Release 14.1, specify the neighbor in a BFD session. In releases prior to Junos OS Release 16.1, you must configure the loopback address of the remote destination as the neighbor address. Beginning with Junos OS Release 16.1, you can also configure this feature on MX series routers with aggregated Ethernet interface address of the remote destination as the neighbor address.

    Note

    On T1600 and T4000 routers, you cannot configure the local aggregated Ethernet Interface address of the remote destination as the neighbor address.

    Caution

    Deactivate bfd-liveness-detection at the [edit interfaces aex aggregated-ether-options] hierarchy level or deactivate the aggregated Ethernet interface before changing the neighbor address from loopback IP address to aggregated Ethernet interface IP address. Modifying the local and neighbor address without deactivating bfd-liveness-detection or the aggregated Ethernet interface first might cause micro BFD sessions failure.

    Note

    Beginning with Release 16.1R2, Junos OS checks and validates the configured micro BFD local-address against the interface or loopback IP address before the configuration commit. Junos OS performs this check on both IPv4 and IPv6 micro BFD address configurations, and if they do not match, the commit fails.

Note

This feature works only when both the devices support BFD. If BFD is configured at one end of the LAG, this feature does not work.

For the IPv6 address family, disable duplicate address detection before configuring this feature with AE interface addresses. To disable duplicate address detection, include the dad-disable statement at the [edit interface aex unit y family inet6] hierarchy level.

Example: Configuring Independent Micro BFD Sessions for LAG

This example shows how to configure an independent micro BFD session for aggregated Ethernet interfaces.

Requirements

This example uses the following hardware and software components:

  • MX Series routers with Junos Trio chipset

  • T Series routers with Type 4 FPC or Type 5 FPC

    BFD for LAG is supported on the following PIC types on T-Series:

    • PC-1XGE-XENPAK (Type 3 FPC),

    • PD-4XGE-XFP (Type 4 FPC),

    • PD-5-10XGE-SFPP (Type 4 FPC),

    • 24x10GE (LAN/WAN) SFPP, 12x10GE (LAN/WAN) SFPP, 1X100GE Type 5 PICs

  • PTX Series routers with 24X10GE (LAN/WAN) SFPP

  • Junos OS Release 13.3 or later running on all devices

Overview

The example includes two routers that are directly connected. Configure two aggregated Ethernet interfaces, AE0 for IPv4 connectivity and AE1 for IPv6 connectivity. Configure micro BFD session on the AE0 bundle using IPv4 addresses as local and neighbor endpoints on both routers. Configure micro BFD session on the AE1 bundle using IPv6 addresses as local and neighbor endpoints on both routers. This example verifies that independent micro BFD sessions are active in the output.

Topology

Figure 1 shows the sample topology.

Figure 1: Configuring an Independent Micro BFD Session for LAG
Configuring an Independent Micro BFD
Session for LAG

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Router R0

Router R1

Configuring a Micro BFD Session for Aggregated Ethernet Interfaces

Step-by-Step Procedure

The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see “Using the CLI Editor in Configuration Mode” in the CLI User Guide.

Note

Repeat this procedure for Router R1, modifying the appropriate interface names, addresses, and any other parameters for each router.

To configure a micro BFD session for aggregated Ethernet interfaces on Router R0:

  1. Configure the physical interfaces.
  2. Configure the loopback interface.
  3. Configure an IP address on the aggregated Ethernet interface ae0 with either IPv4 or IPv6 addresses, as per your network requirements.
  4. Set the routing option, create a static route, and set the next-hop address.Note

    You can configure either an IPv4 or IPv6 static route, depending on your network requirements.

  5. Configure the Link Aggregation Control Protocol (LACP).
  6. Configure BFD for the aggregated Ethernet interface ae0, and specify the minimum interval, local IP address, and the neighbor IP address.
  7. Configure an IP addresse on the aggregated Ethernet interface ae1.

    You can assign either IPv4 or IPv6 addresses as per your network requirements.

  8. Configure BFD for the aggregated Ethernet interface ae1.
    Note

    Beginning with Junos OS Release 16.1, you can also configure this feature with the AE interface address as the local address in a micro BFD session.

    Beginning with Release 16.1R2, Junos OS checks and validates the configured micro BFD local-address against the interface or loopback IP address before the configuration commit. Junos OS performs this check on both IPv4 and IPv6 micro BFD address configurations, and if they do not match, the commit fails.

  9. Configure tracing options for BFD for troubleshooting.

Results

From configuration mode, enter the show interfaces, show protocols, and show routing-options commands and confirm your configuration. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

If you are done configuring the device, commit the configuration.

Verification

Confirm that the configuration is working properly.

Verifying That the Independent BFD Sessions Are Up

Purpose

Verify that the micro BFD sessions are up, and view details about the BFD sessions.

Action

From operational mode, enter the show bfd session extensive command.

user@R0> show bfd session extensive

Meaning

The Micro BFD field represents the independent micro BFD sessions running on the links in a LAG. The TX interval item, RX interval item output represents the setting configured with the minimum-interval statement. All of the other output represents the default settings for BFD. To modify the default settings, include the optional statements under bfd-liveness-detection statement.

Viewing Detailed BFD Events

Purpose

View the contents of the BFD trace file to assist in troubleshooting, if required.

Action

From operational mode, enter the file show /var/log/bfd command.

user@R0> file show /var/log/bfd

Meaning

BFD messages are being written to the specified trace file.

Deleting an Aggregated Ethernet Interface

There are two approaches to deleting an aggregated Ethernet interface:

  • You can delete an aggregated Ethernet interface from the interface configuration. The Junos OS removes the configuration statements related to aex and sets this interface to down state.

  • You can also permanently remove the aggregated Ethernet interface from the device configuration by deleting it from the device-count on the routing device.

To delete an aggregated Ethernet interface:

  1. Delete the aggregated Ethernet configuration.

    This step changes the interface state to down and removing the configuration statements related to aex.

  2. Delete the interface from the device count.
Release History Table
Release
Description
Starting with Junos OS Release 19.3 and later, for MPC10E and MPC11E MPCs, you cannot apply firewall filters on the MicroBFD packets received on the aggregated Ethernet Interface. For MPC1E through MPC9E, you can apply firewall filters on the MicroBFD packets received on the aggregated Ethernet Interface only if the aggregated Ethernet Interface is configured as an untagged Interface.
Starting with Junos OS Release 19.2R1, you can configure any number of aggregated Ethernet Interfaces in a mixed rate aggregated Ethernet bundle on MX Series routers and PTX Series routers.
Starting in Junos OS Release 18.1, Junos OS supports removal of child next hop usage for aggregated Ethernet Interfaces and clients on PTX Series routers with FPC3-PTX-U2 and FPC3-PTX-U3.
Beginning with Junos OS Release 16.1, you can also configure this feature on MX series routers with aggregated Ethernet interface address of the remote destination as the neighbor address.
Beginning with Release 16.1R2, Junos OS checks and validates the configured micro BFD local-address against the interface or loopback IP address before the configuration commit.
In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 480 aggregated interfaces on MX240, MX480, and MX960 routers.
In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 800 aggregated interfaces on MX2010 and MX2020 routers.
Starting in Junos OS Release 14.2R4, the timer values that ensure proper link aggregation and STP functions are configured by default if you use Junos Fusion with Junos OS.
In Junos release 14.2R3 and later, you can configure a maximum of 1000 aggregated interfaces on MX240, MX480, and MX960 routers.
In Junos release 14.2R3 and later, you can configure a maximum of 800 aggregated interfaces on MX2010 and MX2020 routers.
If you use Junos Fusion with Junos OS Release 14.2R3, you need to ensure that link aggregation (and STP) work properly by configuring timers for the periodic packet management (PPM) daemons on the aggregation and satellite devices.
In Junos release 14.2R2 and earlier, you can configure a maximum of 480 aggregated interfaces on MX Series routers.
For MX Series routers running Junos release 14.2R3 and later you can configure a maximum of 1000 aggregated interfaces. For MX2010 and MX2020 routers you can configure a maximum of 800 aggregated interfaces.
Starting in Junos OS Release 14.2, you can configure an enhanced link aggregation group (LAG) on MX Series routers.
Starting with Junos OS Release 14.2, aggregated Ethernet supports mixed link speeds on PTX Series Packet Transport Routers.
Starting with Junos OS Release 14.2, support for mixed rates on aggregated Ethernet bundles is extended to MX240, MX480, MX960, MX2010, and MX2020 routers, thereby enabling you to configure the member links with any combination of rates— 10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet— on an aggregated Ethernet bundle.
Starting with Junos OS Release 14.1R1 and 14.2, support for mixed rates on aggregated Ethernet bundles is extended to MX240, MX480, MX960, MX2010, and MX2020 routers.
Starting with Junos OS Release 14.1, you can configure aggregated Ethernet interfaces with LACP on logical systems within an MX Series router.
Starting with Junos OS Release 14.1R1 and 14.2, support for mixed rates on aggregated Ethernet bundles is extended to MX240, MX480, MX960, MX2010, and MX2020 routers.
Starting with Junos OS Release 14.1, specify the neighbor in a BFD session. In releases prior to Junos OS Release 16.1, you must configure the loopback address of the remote destination as the neighbor address.
Starting with Junos OS Release 13.3, youmust not configure the LACP system identifier by using the system-id system-id statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level to be all zeros (00:00:00:00:00:00).
Starting with Junos OS Release 13.3, IANA has allocated 01-00-5E-90-00-01 as the dedicated MAC address for micro BFD.
Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP.
For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical interfaces is 64, numbered from as0 through as63.
For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical interfaces is 16, numbered from as0 through as15.
Starting with Junos OS Release 13.2, aggregated Ethernet supports mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers.
Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP.
Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP. This 100-Gigabit Ethernet member link can be included in an aggregated Ethernet link that includes member links of other interfaces as well.
Starting with Junos OS Release 13.2, aggregated Ethernet supports mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers.
Starting with Junos OS Release 13.2, 100-Gigabit Ethernet member links can be configured using the two 50-Gigabit Ethernet interfaces of 100-Gigabit Ethernet PIC with CFP.
Starting with Junos OS Release 12.2, you can also configure LACP to override the IEEE 802.3ad standard and to allow the standby link always to receive traffic. Overriding the default behavior facilitates subsecond failover.
Starting with Junos OS Release 11.4, source address filtering does not work when LACP is enabled.
Starting with Junos OS Release 9.3, port aggregation selection (discussed previously) is performed for the active link when LACP link protection is enabled.