Configuring Layer 2 Subscriber Logical Interfaces for CoS Hierarchical Schedulers Using Dynamic Profiles for Differentiating Home and Access Node Networks
In certain Broadband Remote Access Server (B-RAS) deployments, when you use an interface set to denote a home network, it might be necessary to configure the home network and the access node (such as a digital subscriber line access multiplexer, or DSLAM) in a scheduler hierarchy. This method of hierarchical scheduler is necessary in agent circuit identifier (ACI) VLANs because a home or an ACI is always an interface set in such topologies. You can configure a subscriber logical interface or an interface set at Layer 3 over an underlying enhanced subscriber management logical interface that functions as a Layer 2 node. You can configure a the Layer 2 logical interface in a CoS dynamic profile.
Before you apply CoS attributes to VLANs:
Create a basic dynamic profile.
Consider a scenario in which a Layer 3 interface set, ACI-set aci-1006-ps0.3221225479, is stacked over dynamic a MPLS pseudowire service logical interface, ps0.3221225479, at Layer 2. You can configure only one traffic-control-profile under a dynamic profile. You must define the output-traffic-control-profile that binds the traffic-control profile to the interface within the same dynamic profile as the interface. Two traffic control profiles are defined to apply an output traffic scheduling and shaping profile to the MPLS pseudowire logical interface. These control profiles are an-tcp to be applied for TCP subscribers that are terminated at the access mode and an-tcp-remaining, which is a remaining traffic-control profile to a logical interface to provide minimal CoS scheduling when you have not configured or over-provisioned Layer 3 schedulers.
To apply CoS attributes, such as shaping, at the household level, you must set and define the CoS policy for the agent-circuit-identifier VLAN interface set using the dynamic profile for the agent-circuit-identifier interface set (not the subscriber profile). You can also configure a traffic-control profile and a remaining traffic-control profile for a dynamic interface set.
The following example is a CoS profile for an ACI set using a unique-ID based dynamic scheduler map:
Configure a CoS dynamic profile with a simple traffic-control profile that is applied to the dynamic interface set that represents the ACI VLAN.
The following example is a CoS profile for an ACI set using a unique ID-based dynamic scheduler map:
aci-set-profile {
variables {
ds1q0q2DP uid;
ds1q1q2DP uid;
be1_dp uid;
ef1_dp uid;
af1_dp uid;
nc1_dp uid;
}
interfaces {
interface-set "$junos-interface-set-name" {
interface "$junos-interface-ifd-name";
}
}
class-of-service {
traffic-control-profiles {
tcp2 {
inactive: scheduler-map ss1q0q1DP;
shaping-rate 50m;
guaranteed-rate 30m;
overhead-accounting bytes -20;
}
tcp3 {
scheduler-map "$ds1q1q2DP";
shaping-rate 30m;
guaranteed-rate 10m;
overhead-accounting bytes -20;
}
}
interfaces {
interface-set "$junos-interface-set-name" {
output-traffic-control-profile tcp2;
output-traffic-control-profile-remaining tcp3;
}
}
scheduler-maps {
"$ds1q0q2DP" {
forwarding-class be scheduler "$be1_dp";
forwarding-class af scheduler "$af1_dp";
forwarding-class nc scheduler "$nc1_dp";
}
"$ds1q1q2DP" {
forwarding-class ef scheduler "$ef1_dp";
forwarding-class af scheduler "$af1_dp";
forwarding-class nc scheduler "$nc1_dp";
}
}
schedulers {
"$be1_dp" {
transmit-rate percent 25;
priority low;
drop-profile-map loss-priority low protocol any drop-profile d3;
drop-profile-map loss-priority medium-low protocol any drop-profile d2;
drop-profile-map loss-priority medium-high protocol any drop-profile d1;
drop-profile-map loss-priority high protocol any drop-profile d0;
}
"$ef1_dp" {
transmit-rate percent 25;
priority low;
drop-profile-map loss-priority low protocol any drop-profile d3;
drop-profile-map loss-priority medium-low protocol any drop-profile d2;
drop-profile-map loss-priority medium-high protocol any drop-profile d1;
drop-profile-map loss-priority high protocol any drop-profile d0;
}
"$af1_dp" {
transmit-rate percent 25;
priority low;
drop-profile-map loss-priority low protocol any drop-profile d3;
drop-profile-map loss-priority medium-low protocol any drop-profile d2;
drop-profile-map loss-priority medium-high protocol any drop-profile d1;
drop-profile-map loss-priority high protocol any drop-profile d0;
}
"$nc1_dp" {
transmit-rate percent 25;
priority low;
drop-profile-map loss-priority low protocol any drop-profile d3;
drop-profile-map loss-priority medium-low protocol any drop-profile d2;
drop-profile-map loss-priority medium-high protocol any drop-profile d1;
drop-profile-map loss-priority high protocol any drop-profile d0;
}
}
}
}
You can use the show class-of-service scheduler-hierarchy
interface interface-name command to verify
the CoS hierarchical schedulers configured on the interfaces. For
example, the following output illustrates that ACI-set aci-1003-demux0.3221225482
is stacked over demux0.3221225482.
user@host> show class-of-service scheduler-hierarchy interface ge-0/2/0
Interface/ Shaping Guarnteed Guaranteed/ Queue Excess
Resource name rate rate Excess weight weight
kbits kbits priority high/low
ge-0/2/0 1000000
ge-0/2/0 RTP 1000000 0 1 1
best-effort 1000000 0 Low Low 950
network-control 1000000 0 Low Low 50
demux0.3221225482 100000 80000 500 500
demux0.3221225482 RTP
30000 20000 125 125
best-effort 30000 19000 Low Low 950
network-control 30000 1000 Low Low 50
aci-1003-demux0.3221225482 out-of-scheduler-resources
From the following sample output, you can verify that ACI-iflset aci-1001-ps1.3221225472 is stacked over a static pseudowire transport logical interface, ps1.0
user@host> show class-of-service scheduler-hierarchy interface ps1
Interface/ Shaping Guarnteed Guaranteed/ Queue Excess
Resource name rate rate Excess weight weight
kbits kbits priority high/low
lt-0/3/0 10000000
lt-0/3/0 RTP 10000000 0 1 1
best-effort 10000000 0 Low Low 950
network-control 10000000 0 Low Low 50
ps1.0 100000 0 1 1
ps1.0 RTP 500000 0 1 1
best-effort 400000 0 Low Low 1000
aci-1001-ps1.3221225472
200000 10000 500 500
best-effort 160000 2000 Low Low 1000
From the following sample output, you can verify that ACI-set aci-1006-ps0.3221225479 is stacked over the dynamic pseudowire service logical interface, ps0.3221225479.
user@host> show class-of-service scheduler-hierarchy interface ps0
Interface/ Shaping Guarnteed Guaranteed/ Queue Excess
Resource name rate rate Excess weight weight
kbits kbits priority high/low
lt-0/3/0 10000000
lt-0/3/0 RTP 10000000 0 1 1
best-effort 10000000 0 Low Low 950
network-control 10000000 0 Low Low 50
ps0.32767 10000000 2000 50 50
best-effort 10000000 1900 Low Low 950
network-control 10000000 100 Low Low 50
ps0.3221225479 100000 0 1 1
ps0.3221225479 RTP 40000 20000 500 500
best-effort 5000 3000 Medium Low 1
expedited-forwarding 40000 2000 Medium High 1000
aci-1006-ps0.3221225479
100000 10000 250 250
best-effort 5000 1500 Medium Low 1
expedited-forwarding 100000 1000 Medium High 500
assured-forwarding 100000 1000 Medium High 500
network-control 100000 2000 High High 1