Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Interface Ranges for Physical Interfaces

Junos OS Evolved enables you to group a range of identical interfaces into an interface range. You first specify the group of identical interfaces in the interface range. Then you can apply a common configuration to the specified interface range. Interface ranges reduce the number of configuration statements required. They save time and produce a compact configuration.

Configure Interface Ranges

To configure an interface range, use the interface-range statement at the [edit interfaces] hierarchy level. The interface-range statement accepts only physical networking interface names in its definition. Junos OS Evolved supports interface ranges for Ethernet interfaces: et-fpc/pic/port.

To configure an interface range:

  1. Use the interface-range statement at the [edit interfaces] hierarchy level. Include the name you have chosen for your interface range.

    For example, to configure an interface range named "range1":

  2. To specify a member range, use the member-range start-range to end-range statement at the [edit interfaces interface-range range-name] hierarchy level. For example:

  3. To specify an individual member, use the member statement at the [edit interfaces interface-range range-name] hierarchy level. For example:
  4. You can specify a list of interface range members using regular expressions with the member range of interface names statement. A range for a member statement can contain the following:
    • *—All. Specifies sequential interfaces from 0 through 47.


      The wildcard * in a member statement does not take into account the interface numbers supported by a specific interface type. Irrespective of the interface type, * includes interface numbers ranging from 0 through 47 to the interface group. Therefore, use * in a member statement with caution.

    • num—Number. Specifies one specific interface by its number.

    • [low-high]—Numbers from low to high. Specifies a range of sequential interfaces.

    • [num1, num2, num3]—Numbers num1, num2, and num3 specify multiple specific interfaces.

    Regular expressions and wildcards are not supported for interface-type prefixes. For example, prefixes et and xe must be mentioned explicitly.

    For example:

An interface-range definition can contain both member and member-range statements within it. There is no limit on the number of member or member-range statements within an interface-range definition. However, at least one member or member-range statement must exist within an interface-range definition.

An interface-range definition having just member or member-range statements and no common configuration statement is valid. However, you can optionally add a common configuration statement to an interface range as a part of the interface-range definition. For example:

These defined interface ranges can be used in other configuration hierarchies in places where an interface node exists. For example:

In the preceding example, the interface node can accept both individual interfaces and interface ranges.


To view an interface range in expanded configuration, use the (show | display inheritance) command.

Expanded Interface Range Statements

The operating system expands all member and member-range statements in an interface range definition to generate the final list of interface names for the specified interface range.

An example configuration looks like this before it is expanded:

For the member-range statement, all possible interfaces between start-range and end-range are considered in expanding the members. For example, the following member-range statement:

expands to:

The following member statement:

expands to:

The following member statement:

expands to:

Configuration Inheritance Priority

The interface ranges are defined in the order of inheritance priority. The first interface range configuration data takes priority over subsequent interface ranges.

In this example, interface et-1/1/1 exists in both interface range int-grp-one and interface range int-grp-two:

Interface et-1/1/1 inherits mtu 500 from interface range int-grp-one because it was defined first.

Configuration Inheritance for Member Interfaces

When Junos OS Evolved expands the member and member-range statements present in an interface-range, it creates interface objects if they are not explicitly defined in the configuration. The operating system copies the common configuration to all the interface range's member interfaces.

Foreground interface configuration takes priority over configuration that the interface inherits from the interface range configuration.

In this example, interface et-1/0/1 has an MTU value of 1024 because that is its foreground configuration:

You can verify this in the output of the show interfaces | display inheritance command:

Common Configuration Inheritance

If an interface is a member of multiple interface ranges, that interface will inherit the common configuration from all of those interface ranges.

For example:

In this example, interfaces et-4/0/0 through et-4/0/40 have both hold-time and mtu configured.

Configuration Group Inheritance

Interface range member interfaces inherit configurations from configuration groups like any other foreground configuration. The only difference is that the interface-range goes through a member interfaces expansion before the operating system reads this configuration.

In this example, Junos OS Evolved applies the hold-time configuration to all members of the interface range range1:

You can verify this with show interfaces | display inheritance, as follows:

Configuration Expansion Where Interface Range Is Used

In this example, interface-range range1 is used under the protocols hierarchy:

The interface node present under authenticator expands into member interfaces of the interface range range1 as follows:

The interface range-1 statement is expanded into two interfaces, et-7/1/1 and et-5/0/1, and the operating system copies the configuration retries 1 under those two interfaces.

You can verify this configuration using the show protocols dot1x | display inheritance command.