Description

Unconfigured Aggregated Ethernet interfaces do not show up in the Interfaces Terse at the edit hierarchy level when running the command ‘#set chassis aggregated-device ethernet device-count <#>’ at the [edit chassis] hierarchy level. This behavior occurs beginning wtih Junos 14.2 (all releases) due to a change implemented to facilitate the naming scheme of an Aggregate Ethernet interface at the logical system level.

Symptoms

Aggregated Ethernet interfaces does not show up after adding them to an MX series router with Junos14.2 (all releases) using the ‘set chassis aggregated-devices ethernet device-count <#>’ command and committing. The ‘show interfaces terse’ command was used to check the available aggregated Ethernet interfaces.

Solution

This behavior specifically applies to Junos 14.2 (all releases). This version facilitates the naming scheme of an aggregate Ethernet interface at the logical system level, as described in the Release Notes: Junos® OS Release 14.2R1 for the EX Series, M Series, MX Series, PTX Series, and T Series .

Beginning with Junos 14.2 (all releases), the command ‘set aggregated-devices ethernet device-count <#>’ committed at the [edit chassis] level changed. The aggregate Ethernet interfaces do not appear in the ‘show interfaces terse’ . The aggregated Ethernet interfaces will appear when they are fully configured at the [edit interfaces] level and have links associated with it.

Example:

Before Junos 14.2, the behavior was:

[edit chassis]
labroot@MX960# show
aggregated-devices {
ethernet {
device-count 5;

labroot@MX960> show interfaces terse
Interface Admin Link Proto Local Remote
...
Search for: ae
ae0 up down
ae1 up down
ae2 up down
ae3 up down
ae4 up down

In Junos 14.2 (all releases), the new behavior is:

[edit chassis]
labroot@MX960# show
aggregated-devices {
ethernet {
device-count 5;

labroot@MX960> show interfaces terse
Interface Admin Link Proto Local Remote
...
Search for: ae
Pattern not found      

Related Information