Configuring Interface Sets
To configure an interface set, include the interface-set statement at the [edit class-of-service interfaces] hierarchy
level:
[edit class-of-service interfaces]
interface-set interface-set-name {
...interface-cos-configuration-statements ...
}
To apply the interface set to interfaces, include the interface-set statement at the [edit interfaces] hierarchy level:
[edit interfaces]
interface-set interface-set-name {
interface ethernet-interface-name {
... interface-cos-configuration-statements ...
}
}
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 numberlisting 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.
[edit interfaces]
interface-set interface-set-name {
interface ethernet-interface-name {
(unit logical-unit-number | vlan-tags-outer vlan-tag) {
...
}
}
}
The logical interface naming option lists Ethernet interfaces:
[edit interfaces]
interface-set unitl-set-ge-0 {
interface ge-0/0/0 {
unit 0;
unit 1;
...
}
}
The interface naming option lists aggregated Ethernet interfaces:
[edit interfaces]
interface-set demuxset1 {
interface demux0 {
unit 1;
..
}
}
demux0 {
unit 1 {
demux-options {
underlying-interface ae0.1;
}
family inet {
demux-source {
10.1.1.1/24;
}
address 10.1.1.1/24;
}
}
..
ae0 {
unit 1 {
}
..
}
}
class-of-service {
interface-set demuxset1 {
output-traffic-control-profile tcp2;
}
}
}
The S-VLAN option lists only one S-VLAN (outer) tag value:
[edit interfaces]
interface-set svlan-set {
interface ge-1/0/0 {
vlan-tags-outer 2000;
}
}
The S-VLAN naming option lists S-VLAN (outer) tag values:
[edit interfaces]
interface-set svlan-set-tags {
interface ge-2/0/0 {
vlan-tags-outer 2000;
vlan-tags-outer 2001;
vlan-tags-outer 2002;
...
}
}
Ranges are not supported: you must list each VLAN or logical interface separately.