Specifications

Use the following procedure to configure captive portal content delivery rules in service
sets:
1. Define one or more rules with the rule rule-name statement at the [edit services
captive-portal-content-delivery] hierarchy level. In each rule you specify one or more
terms to match on an application, destination address, or destination prefix list;
where the match takes place; and actions to be taken when the match occurs,
2. (Optional) Define one or more rule sets by listing the rules to be included in the set
with the rule-set rule-set-name statement at the [edit services
captive-portal-content-delivery] hierarchy level.
3. Configure a captive portal content delivery profile with the profile profile-name
statement at the [edit services captive-portal-content-delivery] hierarchy level.
4. In the profile, specify a list of rules with the cpcd-rules [rule-name] statement or a
list of rule sets with the cpcd-rule-sets [rule-set-name] statement. Both statements
are at the [edit services captive-portal-content-delivery profile profile-name] hierarchy
level.
5. Associate the profile with a service set with the captive-portal-content-delivery-profile
profile-name statement at the [edit services service-set service-set-name] hierarchy
level.
•
The “LAC Tunnel Selection Overview” topic in the Junos OS Subscriber Management
Feature Guide incorrectly describes the current behavior for failover between preference
levels. The topic states that when the tunnels at every preference level have a
destination in the lockout state, the LAC cycles back to the highest preference level
and waits for the lockout time for a destination at that level to expire before attempting
to connect and starting the process over.
In fact, the current behavior in this situation is that from the tunnels present at the
lowest level of preference (highest preference number), the LAC selects the tunnel
that has the destination with the shortest remaining lockout time. The LAC ignores the
lockout and attempts to connect to the destination.
•
The Subscriber Management Scaling Values (XLS) spreadsheet previously reported
that 64,000 PPPoE subscribers are supported per interface for Junos OS Release 12.3
and subsequent releases. In fact, the chassis supports 128,000 PPPoE subscribers
beginning in Junos OS Release 12.3.
You can access the latest version of the Subscriber Management Scaling Values (XLS)
spreadsheet from the Downloads box at Junos OS Subscriber Management and Services
Library.
Copyright © 2015, Juniper Networks, Inc.154
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series