close
keyboard_arrow_left
Table of Contents
- play_arrow Subscriber Service Activation and Management
- play_arrow Subscriber Service Activation and Management
-
- play_arrow Configuring Dynamic Filters and Policers
- play_arrow Dynamic Firewall Filters Overview
- play_arrow Configuring Static Firewall Filters That Are Dynamically Applied
- play_arrow Streamlining Processing of Chains of Static Filters
- play_arrow Dynamically Attaching Static or Fast Update Filters to an Interface
- play_arrow Configuring Filters That Are Created Dynamically
- Parameterized Filters Overview
- Unique Identifiers for Firewall Variables
- Configuring Unique Identifiers for Parameterized Filters
- Sample Dynamic-Profile Configuration for Parameterized Filters
- Dynamic Profile After UID Substitutions for Parameterized Filters
- Multiple Parameterized Filters
- Parameterized Filter Processing Overview
- Parameterized Filters Configuration Considerations
- Guidelines for Creating and Applying Parameterized Filters for Subscriber Interfaces
- Parameterized Filter Match Conditions for IPv4 Traffic
- Parameterized Filter Match Conditions for IPv6 Traffic
- Parameterized Filter Nonterminating and Terminating Actions and Modifiers
- Firewall Filter Match Conditions for Protocol-Independent Traffic in Dynamic Service Profiles
- Firewall Filter Terminating and Nonterminating Actions for Protocol-Independent Traffic in Dynamic Service Profiles
- Interface-Shared Filters Overview
- Dynamically Attaching Filters Using RADIUS Variables
- Example: Implementing a Filter for Households That Use ACI-Based VLANs
- Example: Dynamic-Profile Parsing
- Example: Firewall Dynamic Profile
- Example: Configuring a Filter to Exclude DHCPv6 and ICMPv6 Control Traffic for LAC Subscriber
- play_arrow Using Ascend Data Filters to Implement Firewalls Based on RADIUS Attributes
- Ascend-Data-Filter Policies for Subscriber Management Overview
- Ascend-Data-Filter Attribute Fields
- Dynamically Applying Ascend-Data-Filter Policies to Subscriber Sessions
- Example: Configuring Dynamic Ascend-Data-Filter Support for Subscriber Access
- Example: Configuring Static Ascend-Data-Filter Support for Subscriber Access
- Verifying and Managing Dynamic Ascend-Data-Filter Policy Configuration
- play_arrow Configuring Fast Update Filters to Provide More Efficient Processing Over Classic Static Filters
- Fast Update Filters Overview
- Basic Fast Update Filter Syntax
- Configuring Fast Update Filters
- Example: Configuring Fast Update Filters for Subscriber Access
- Match Conditions and Actions in Fast Update Filters
- Configuring the Match Order for Fast Update Filters
- Fast Update Filter Match Conditions
- Fast Update Filter Actions and Action Modifiers
- Configuring Terms for Fast Update Filters
- Configuring Filters to Permit Expected Traffic
- Avoiding Conflicts When Terms Match
- Associating Fast Update Filters with Interfaces in a Dynamic Profile
- play_arrow Defending Against DoS and DDoS Attacks Using Unicast RPF and Fail Filters
- play_arrow Improving Scaling and Performance of Filters on Static Subscriber Interfaces
- play_arrow Configuring Dynamic Service Sets
- play_arrow Configuring Rate-Limiting Premium and Non-Premium Traffic on an Interface Using Hierarchical Policers
- play_arrow Monitoring and Managing Firewalls for Subscriber Access
-
- play_arrow Configuring Dynamic Multicast
- play_arrow Configuring Dynamic IGMP to Support IP Multicasting for Subscribers
- play_arrow Configuring Dynamic MLD to Enable Subscribers to Access Multicast Networks
-
- play_arrow Configuring Application-Aware Policy Control and Reporting
- play_arrow Configuring Application-Aware Policy Control
- Understanding Application-Aware Policy Control for Subscriber Management
- Understanding PCC Rules for Subscriber Management
- Configuring Application-Aware Policy Control for Subscriber Management
- Installing Services Packages for Subscriber Management Application-Aware Policy Management
- Configuring Service Data Flow Filters
- Configuring Policy and Charging Control Action Profiles for Subscriber Management
- Configuring Policy and Charging Control Rules
- Configuring a Policy and Charging Control Rulebase
- Configuring a Policy and Charging Enforcement Function Profile for Subscriber Management
- Identifying the Service Interface That Handles Subscriber Management Application-Aware Policy Control
- Configuring PCC Rule Activation in a Subscriber Management Dynamic Profile
- Enabling Direct PCC Rule Activation by a PCRF for Subscriber Management
- play_arrow Configuring Application Identification
- play_arrow Configuring Reporting for Application-Aware Data Sessions
- Logging and Reporting Function for Subscribers
- Log Dictionary for Template Types
- Configuring Logging and Reporting for Subscriber Management
- Installing Services Packages for Subscriber Management Logging and Reporting
- Configuring an LRF Profile for Subscribers
- Applying Logging and Reporting Configuration to a Subscriber Management Service Set
- Configuring the Activation of an LRF Rule by a PCC Rule
-
- play_arrow Configuring HTTP Redirect Services
- play_arrow Configuring Captive Portal Content Delivery Services for Redirected Subscribers
- HTTP Redirect Service Overview
- Remote HTTP Redirect Server Operation Flow
- Local HTTP Redirect Server Operation Flow (MX Series, ACX7100-48L, ACX7332 and ACX7348)
- Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services
- Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services
- Configuring Routing Engine-Based, Static HTTP Redirect Services
- Configuring Routing Engine-Based, Converged HTTP Redirect Services
- Adding Subscriber Information to HTTP Redirect URLs
- How to Automatically Remove the HTTP Redirect Service After the Initial Redirect
- Example: Configuring HTTP Redirect Services Using a Next-Hop Method and Attaching It to a Static Interface
-
- play_arrow Configuring Subscriber Secure Policy
- play_arrow Configuring Subscriber Secure Policy Traffic Mirroring Overview
- play_arrow Configuring RADIUS-Initiated Subscriber Secure Policy Traffic Mirroring
- RADIUS-Initiated Subscriber Secure Policy Overview
- Subscriber Secure Policy Traffic Mirroring Architecture Using RADIUS
- RADIUS-Initiated Traffic Mirroring Interfaces
- RADIUS-Initiated Traffic Mirroring Process at Subscriber Login
- RADIUS-Initiated Traffic Mirroring Process for Logged-In Subscribers
- RADIUS Attributes Used for Subscriber Secure Policy
- Using the Packet Header to Track Subscribers on the Mediation Device
- Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview
- Guidelines for Configuring Subscriber Secure Policy Mirroring
- Configuring Support for Subscriber Secure Policy Mirroring
- Configuring RADIUS Server Support for Subscriber Secure Policy Mirroring
- Terminating RADIUS-Initiated Subscriber Traffic Mirroring
- play_arrow Configuring DTCP-Initiated Subscriber Secure Policy Traffic Mirroring
- DTCP-Initiated Subscriber Secure Policy Overview
- Subscriber Secure Policy Traffic Mirroring Architecture Using DTCP
- DTCP-Initiated Traffic Mirroring Interfaces
- DTCP-Initiated Traffic Mirroring Process
- DTCP Messages Used for Subscriber Secure Policy
- Packet Header for Mirrored Traffic Sent to Mediation Device
- Configuring DTCP-Initiated Subscriber Secure Policy Mirroring Overview
- Guidelines for Configuring Subscriber Secure Policy Mirroring
- Configuring Support for Subscriber Secure Policy Mirroring
- Configuring the Mediation Device as a User on the Router
- Configuring a DTCP-over-SSH Connection to the Mediation Device
- Configuring the Mediation Device to Provision Traffic Mirroring
- Disabling RADIUS-Initiated Subscriber Secure Policy Mirroring
- Example: Configuring Traffic That Is Mirrored Using DTCP-Initiated Subscriber Secure Policy
- Terminating DTCP-Initiated Subscriber Traffic Mirroring Sessions
- play_arrow Configuring DTCP Messages Used for DTCP-Initiated Subscriber Secure Policy Mirroring
- play_arrow Configuring Subscriber Secure Policy Support for IPv4 Multicast Traffic
- play_arrow Configuring Intercept-Related Information for Subscriber Secure Policy
-
- play_arrow Configuring Stateless, Rule-Based Services Using Application-Aware Access Lists
- play_arrow AACL Overview
- play_arrow Configuring AACL Rules
- play_arrow Example: Configuring AACL Rules
- play_arrow Example: Configuring AACL Rule Sets
- play_arrow Configuring Logging of AACL Flows
-
- play_arrow Remote Device and Service Management
- play_arrow Configuring Remote Device Services Management
- play_arrow Configuring TCP Port Forwarding for Remote Subscriber Services
- play_arrow Configuring IPFIX Mediation for Remote Device Monitoring
- play_arrow Collection and Export of Local Telemetry Data on the IPFIX Mediator
-
- play_arrow Troubleshooting
- play_arrow Contacting Juniper Networks Technical Support
- play_arrow Knowledge Base
-
- play_arrow Configuration Statements and Operational Commands
- [OBSOLETE] applications (Services AACL)
- [OBSOLETE] application-group-any
- [OBSOLETE] application-groups (Services AACL)
- [OBSOLETE] destination-address (Application Aware Access List)
- [OBSOLETE] destination-address-range
- [OBSOLETE] destination-prefix-list (Services AACL)
- [OBSOLETE] from
- [OBSOLETE] match-direction
- [OBSOLETE] nested-applications
- [OBSOLETE] rule
- [OBSOLETE] rule-set
- [OBSOLETE] source-address (AACL)
- [OBSOLETE] source-address-range
- [OBSOLETE] source-prefix-list
- [OBSOLETE] term
- [OBSOLETE] then (Application Aware Access List)
- Junos CLI Reference Overview
list Table of Contents
Configuring Layer 2 Subscriber Logical Interfaces for CoS Hierarchical Schedulers Using Dynamic Profiles for Differentiating Home and Access Node Networks
date_range
06-Dec-23
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:
content_copy zoom_out_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.
content_copy zoom_out_map
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
content_copy zoom_out_map
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.
content_copy zoom_out_map
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
