Technical Documentation

Configuring Interface Ranges

To configure an interface range, include the interface-range statement at the [edit interfaces] hierarchy level.

The interface-range statement accepts only physical networking interface names in its definition. The following interface types are supported and example CLI descriptors are shown:

  • Ethernet—(xe | ge | fe)-fpc/pic/port
  • Serial—se-fpc/pic/port
  • ATM—at-fpc/pic/port
  • SONET/SDH—so-fpc/pic/port
  • E1/E3—(e1 | e3)-fpc/pic/port
  • T1/T3—(t1 | t3)-fpc/pic/port
  • Channelized—(coc | cstm)n-fpc/pic/port
  • ISDN—isdn-fpc/pic/port
  • DPC—xe-fpc/pic/port

Interfaces can be grouped either as a range of interfaces or using a number range under the interface-range statement definition.

Interfaces in an interface-range definition can be added as part of a member range or as individual members or multiple members using a number range.

To specify a member range, use the member-range statement at the [edit interfaces interface-range name] hierarchy level.

To specify interfaces in lexical order, use the member-range start-range to end-range statement.

A range for a member statement should contain the following:

  • *—All, specifies all available interfaces.
  • num—Number, specifies one specific interface by its number.
  • [low-high]—Numbers between low to high, specifies a range of sequential interfaces.
  • [num1, num2, num3]—Numbers num1, num2, and num3 specify multiple specific interfaces.

Example: Specifying an Interface Range Member Range

member-range ge-0/0/0 to ge-4/0/40;

To specify one or multiple members, use the member statement at the [edit interfaces interface-range name] hierarchy level.

To specify the list of interface range members individually or for multiple interfaces using regex, use the member list of interface names statement.

Example: Specifying an Interface Range Member

member ge-0/0/0;member ge-0/*/*member ge-0/[1-10]/0;member ge-0/[1,2,3]/3;

Regex or wildcards are not supported for interface-type prefixes. For example, prefixes ge, fe, and xe must be mentioned explicitly.

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

Example: Interface Range Common Configuration

Configuration common to an interface range can be added as a part of the interface-range definition, as follows:

[edit]interfaces {+ interface-range foo {+ member-range ge-1/0/0 to ge-4/0/40;+ member ge-0/1/1;+ member ge-5/[1-10]/*;/*Common config is added as part of interface-range definition*/mtu 256;hold-time up 10;ether-options {flow-control;speed {100m;}802.3ad primary;}}}

An interface-range definition having just member or member-range statements and no common configurations statements is valid.

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

Example: Interface-Range foo Used Under the Protocols Hierarchy

protocols {dot1x {authenticator {interface foo {retries 1;}}}}

foo should be an interface-range defined at the [interfaces] hierarchy level. In the above example, the interface node can accept both individual interfaces and interface ranges.

Tip: To view an interface range in expanded configuration, use the (show | display inheritance) command. For more information, see the Junos CLI User Guide.

By default, interface-range is not available to configure in the CLI where the interface statement is available. The following locations are supported; however, some of the hierarchies shown in this list are product specific:

  • protocols dot1x authentication interface
  • protocols dvmrp interface
  • protocols oam ethernet lmi interface
  • protocols esis interface
  • protocols igmp interface
  • protocols igmp-host client num interface
  • protocols mld-host client num interface
  • protocols router-advertisement interface
  • protocols isis interface
  • protocols ldp interface
  • protocols oam ethernet link-fault-management interface
  • protocols lldp interface
  • protocols link-management peer lmp-control-channel interface
  • protocols link-management peer control-channel
  • protocols link-management te-link name interface
  • protocols mld interface
  • protocols ospf area id interface
  • protocols pim interface
  • protocols router-discovery interface
  • protocols rip group name neighbour
  • protocols ripng group name neighbour
  • protocols rsvp interface
  • protocols snmp interface
  • protocols layer2-control bpdu-block interface
  • protocols layer2-control mac-rewrite interface
  • protocols mpls interface
  • protocols stp interface
  • protocols rstp interface
  • protocols mstp interface
  • protocols vstp interface
  • protocols mstp msti id interface
  • protocols mstp msti vlan id interface
  • protocols vstp vlan name interface
  • protocols gvrp interface
  • protocols igmp-snooping vlan name interface
  • protocols lldp interface
  • protocols lldp-med interface
  • protocols sflow interfaces
  • ethernet-switching-options analyzer name input [egress | ingress ] interface
  • ethernet-switching-options analyzer name output interface
  • ethernet-switching-options secure-access-port interface
  • ethernet-switching-options interfaces ethernet-switching-options voip interface
  • ethernet-switching-options redundant-trunk-group group g1 interface
  • ethernet-switching-options redundant-trunk-group group g1 interface
  • ethernet-switching-options bpdu-block interface
  • poe interface vlans pro-bng-mc1-bsd1 interface

Related Topics

Published: 2010-07-14