Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Interface Sets


To configure an interface set, include the interface-set statement at the [edit class-of-service interfaces] hierarchy level:

To apply the interface set to interfaces, include the interface-set statement at the [edit interfaces] hierarchy level:

Interface sets can be defined in two major ways:

  • As a list of logical interfaces or aggregated Ethernet interfaces (unit 100, unit 200, and so on)

  • At the stacked VLAN level using a list of outer VLAN IDs (vlan-tags-outer 210, vlan-tags-outer 220, and so on).

    The svlan number listing option with a single outer VLAN tag is a convenient way to specify a set of VLAN members having the same outer VLAN tags. Service providers can use these statements to group interfaces to apply scheduling parameters such as guaranteed rate and shaping rate to the traffic in the groups.

Whether using the logical interface listing option for a group of customer VLANs, aggregated Ethernet interfaces, or the S-VLAN set listing option for a group of VLAN outer tags, all traffic heading downstream must be gathered into an interface set with the interface-set statement at the [edit class-of-service interfaces] hierarchy level.

Regardless of listing convention, you can only use one of the types in an interface set. Examples of this limitation appear later in this section.


Interface sets are currently used only by CoS, but they are applied at the [edit interfaces] hierarchy level to make them available to other services that might use them in future.

The logical interface naming option lists Ethernet interfaces:

The interface naming option lists aggregated Ethernet interfaces:

The S-VLAN option lists only one S-VLAN (outer) tag value:

The S-VLAN naming option lists S-VLAN (outer) tag values:


Ranges are not supported: you must list each VLAN or logical interface separately.

Related Documentation