- 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
ON THIS PAGE
Example: Configuring a Dynamic Service VLAN Interface Set of Subscribers in a Dynamic Profile
Interface sets enable you to provide hierarchical
scheduling to a group of subscriber interfaces. In this example, by
using the $junos-svlan-interface-set-name internal dynamic
variable when specifying the interface set name, you can locally generate
an interface set name for use by SVLAN interfaces based on the outer
tag of the dual-tagged VLAN. The format of the generated variable
is physical_interface_name - outer_VLAN_tag.
Requirements
Before you begin, configure the subscriber interfaces that you intend to include in the interface set. You can find general configuration instructions for the supported dynamic interface configuration in DHCP Subscriber Interface Overviewand in the following:
For dynamic VLAN interfaces, see Configuring a Static or Dynamic VLAN Subscriber Interface over Aggregated Ethernet.
For dynamic IP demux interfaces, see Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles and Configuring a Static or Dynamic IP Demux Subscriber Interface over Aggregated Ethernet.
For dynamic VLAN demux interfaces, see Configuring Dynamic Subscriber Interfaces Using VLAN Demux Interfaces in Dynamic Profiles.
Overview
Interface sets enable you to provide hierarchical scheduling
to a group of subscriber interfaces. By using the $junos-svlan-interface-set-name internal dynamic variable when specifying the interface set name,
you can locally generate an interface set name for use by SVLAN interfaces
based on the outer tag of the dual-tagged VLAN. The format of the
generated variable is physical_interface_name - outer_VLAN_tag.
This example includes the following statements:
interface-set—Configures the name of the scheduler for dynamic CoS. In this example, you use the$junos-svlan-interface-set-namevariable to obtain the locally generated interface set name for use by SVLAN interfaces based on the outer tag of the dual-tagged VLAN.output-traffic-control-profile—Applies an output traffic scheduling and shaping profile to the interface set.output-traffic-control-profile-remaining—Applies an output traffic scheduling and shaping profile for remaining traffic to the interface set.
Configuration
CLI Quick Configuration
To quickly configure this example, copy the
following commands, paste them into a text file, remove any line breaks,
change any details necessary to match your network configuration,
and then copy and paste the commands into the CLI at the [edit] hierarchy level.
[edit] set dynamic-profiles profile-dhcp-ipdemux interfaces interface-set $junos-svlan-interface-set-name interface $junos-interface-ifd-name unit $junos-underlying-interface-unit set dynamic-profiles profile-dhcp-ipdemux interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit set class-of-service traffic-control-profiles tcp1 scheduler-map schedMap set class-of-service traffic-control-profiles tcp1 shaping-rate 50m set class-of-service traffic-control-profiles tcp1 guaranteed-rate 200k set class-of-service traffic-control-profiles tcp3 scheduler-map ss1q0q1 set class-of-service traffic-control-profiles tcp3 shaping-rate 20m set class-of-service traffic-control-profiles tcp3 guaranteed-rate 5m set class-of-service interfaces interface-set ae0-111 output-traffic-control-profile tcp1 set class-of-service interfaces interface-set ae0-111 output-traffic-control-profile-remaining tcp3
Procedure
Step-by-Step Procedure
To configure an SVLAN interface set of subscriber interfaces:
Access the dynamic profile you want to modify for interface sets.
content_copy zoom_out_map[edit] user@host# edit dynamic-profiles profile-dhcp-ipdemux
Access the dynamic profile interface configuration.
content_copy zoom_out_map[edit dynamic-profiles profile-dhcp-ipdemux] user@host# edit interfaces
Configure the SVLAN interface set in the dynamic profile.
The interface set is created dynamically when the subscriber logs in.
content_copy zoom_out_map[edit dynamic-profiles profile-dhcp-ipdemux interfaces] user@host# edit interface-set $junos–svlan-interface-set-name
Include dynamic IP demux interface creation within the dynamic interface set.
content_copy zoom_out_map[edit dynamic-profiles profile-dhcp-ipdemux interfaces interface-set $junos-svlan-interface-set-name] user@host# set interface $junos-interface-ifd-name unit $junos-underlying-interface-unit
Access the SVLAN interface set name that you expect
$junos-svlan-interface-set-nameto generate. For example, to specify the expected interface set name for aggregated Ethernet interface ae0 and outer VLAN tag 111, include ae0-111 for theinterface-set-namevariable.content_copy zoom_out_map[edit class-of-service interfaces] user@host# edit interface-set ae0-111
Apply traffic shaping and queuing parameters to the SVLAN interface set.
Tip:You must configure the interface set in the static
[edit class-of-service]hierarchy, not in the[edit dynamic-profiles]hierarchy.content_copy zoom_out_map[edit class-of-service interfaces interface-set ae0-111] user@host# set output-traffic-control-profile tcp1
Apply traffic shaping and queuing parameters to any remaining traffic on the SVLAN interface set.
content_copy zoom_out_map[edit class-of-service interfaces interface-set ae0-111] user@host# set output-traffic-control-profile-remaining tcp3
Results
From configuration mode, confirm your configuration
by entering the show dynamic-profiles command and the show class-of-service command. If the output does not display
the intended configuration, repeat the instructions in this example
to correct the configuration.
user@host# show dynamic-profiles
dynamic-profiles {
profile-dhcp-ipdemux {
interfaces {
interface-set "$junos-svlan-interface-set-name" {
interface "$junos-interface-ifd-name" {
unit "$junos-underlying-interface-unit";
}
}
"$junos-interface-ifd-name" {
unit "$junos-underlying-interface-unit";
}
}
}
}
user@host# show class-of-service
class-of-service {
traffic-control-profiles {
tcp1 {
scheduler-map schedMap;
shaping-rate 50m;
guaranteed-rate 200k;
}
tcp3 {
inactive: scheduler-map ss1q0q1;
shaping-rate 20m;
guaranteed-rate 5m;
}
}
interfaces {
interface-set ae0-111 {
output-traffic-control-profile tcp1;
output-traffic-control-profile-remaining tcp3;
}
}
}
Verification
To confirm that the configuration is correct, perform these tasks:
- Verifying the Interfaces that are Included in the Interface Set
- Displaying Information for Active Subscribers
Verifying the Interfaces that are Included in the Interface Set
Purpose
Verify the interfaces that are included in the interface set.
Action
user@host> show class-of-service interface-set
Displaying Information for Active Subscribers
Purpose
Display information for active subscribers.
Action
user@host> show subscribers detail
