ON THIS PAGE
Example: Configuring Layer 2 Subscriber Logical Interfaces for CoS Hierarchical Schedulers Using Static CoS for Differentiating Home and Access Node Networks
Starting in Junos OS Release 15.1, 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 enable an enhanced subscriber management logical interface, such as an MPLS pseudowire logical interface to function as a Layer 2 node in a CoS hierarchical scheduler. A subscriber logical interface is considered to operate at Layer 2 only if you configure CoS three-level hierarchical scheduling on the logical tunnel anchor point on the physical interface (the IFD). When you include the implicit-hierarchy option, a hierarchical relationship is formed between the CoS scheduler nodes at level 1, level 2, and level 3. The implicit-hierarchy option is supported only on MPC/MIC subscriber interfaces and interface sets running over aggregated Ethernet on MX Series routers.
Requirements
This example uses the following hardware and software components:
Junos OS Release 15.1
MX Series Router with MPCs
Overview
You specify an anchor point, which identifies the logical tunnel interface that terminates the pseudowire tunnel at the access node. Consider a scenario in which lt-0/3/0 is the logical tunnel interface, and an MPLS pseudowire transport logical interface, ps1.0, that is anchored on the logical tunnel. Three-level hierarchical scheduling is enabled on the logical tunnel interface for static CoS configuration.
Configuration
To configure an enhanced subscriber management logical interface, such as an MPLS pseudowire logical interface to function as a Layer 2 node in a CoS hierarchical scheduler. perform these tasks:
- CLI Quick Configuration
- Configuring an MPLS Pseudowire Transport Logical Interface Over a Logical Tunnel in a Static CoS Setup
- Results
CLI Quick Configuration
To quickly configure the MPLS pseudowire logical interface to function as a Layer 2 node in a three-level hierarchical scheduler, copy the following commands and paste them into the router terminal window:
[edit] set interfaces lt-0/3/0 set interfaces lt-0/3/0 hierarchical-scheduler implicit-hierarchy set interfaces ps1 set interfaces ps1 description client-port-l2circuit set interfaces ps1 flexible-vlan-tagging set interfaces ps1 anchor-point lt-0/3/0 set interfaces ps1 unit 0 set interfaces ps1 unit 0 encapsulation ethernet-ccc set interfaces ps1 unit 0 output-traffic-control-profile profile-name
Configuring an MPLS Pseudowire Transport Logical Interface Over a Logical Tunnel in a Static CoS Setup
Step-by-Step Procedure
Three-level scheduling on pseudowire logical interfaces over a transport logical interface requires you to apply the traffic-control profiles at both the pseudowire logical interface and the pseudowire transport logical interface. To configure three-level scheduling on pseudowire transport logical interfaces over a logical tunnel physical interface (LT ifd):
Configure the hierarchical scheduler for the physical interface used for the logical tunnel (anchor point). For three-level scheduling the hierarchical scheduler must be set to
implicit-hierarchy.[edit] user@host#edit interfaces lt-0/3/0 user@host#set hierarchical-scheduler implicit-hierarchy
Specify that you want to configure the pseudowire subscriber logical interface device.
[edit] user@host# edit interfaces ps1
Configure a description for the pseudowire subscriber logical interface.
[edit interfaces ps1] user@host# set description client-port-l2circuit
Specify the
flexible-vlan-taggingstatement to indicate that this interface is for use with both VLAN and stacked VLAN ranges.[edit interfaces ps1] user@host# set flexible-vlan-tagging
Specify the logical tunnel (lt) interface that identifies the Packet Forwarding Engine that processes the pseudowire termination.
[edit interfaces ps1] user@host# set anchor-point lt-0/3/0
Specify that you want to configure unit 0, which represents the transport logical interface.
[edit interfaces ps1] user@host# edit unit 0
Specify the ethernet-ccc encapsulation method for the transport logical interface.
[edit interfaces ps0 unit 0] user@host# set encapsulation ethernet-ccc
Specify the traffic-control profile to use on the pseudowire transport logical interface.
[edit class-of-service] user@host#edit interfaces ps 1 user@host#edit unit 0 user@host#set output-traffic-control-profile profile-name
Results
In configuration mode, confirm your configuration by entering the show command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
[edit]
lt-0/3/0 {
hierarchical-scheduler implicit-hierarchy;
}
ps1 {
description client-port-l2circuit;
anchor-point {
lt-0/3/0;
}
flexible-vlan-tagging;
unit 0 {
encapsulation ethernet-ccc;
}
}
Verification
Confirm that the configuration is working properly.
Verifying the Scheduler Hierarchy Configured on the Interfaces
Purpose
Verify the CoS hierarchical scheduler configured on the Layer 2 and Layer 3 interface nodes.
Action
From operational mode, enter the show class-of-service scheduler-hierarchy interface ps0 command.
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.0 200000 0 1 1
ps0.0 RTP 10000000 0 1 1
best-effort 10000000 0 Low Low 950
network-control 10000000 0 Low Low 50
ps0.3221225474 100000 0 1 1
best-effort 5000 0 Medium Low 1000
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 33 33
best-effort 10000000 1900 Low Low 950
network-control 10000000 100 Low Low 50
ps0.3221225474 200000 0 1 1
ps0.3221225474 RTP 100000 30000 500 500
best-effort 30000 3000 Medium Low 250
expedited-forwarding 32000 9000 Low Low 750
pp0.3221225475 100000 10000 166 166
best-effort 5000 1500 Low Low 1
expedited-forwarding 100000 1000 Medium High 500
assured-forwarding 100000 1000 Medium High 500
network-control 100000 2000 High High 1
Meaning
Shows that dynamic pseudowire service logical interface, ps0.3221225474, is stacked over the static pseudowire transport logical interface, ps0.0. Also, the sample output denotes that pp0.3221225475 is stacked over dynamic pseudowire service logical interface, ps0.3221225474.