Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

 A  B  C  D  E  F  G  H  I  L  M  N  P  Q  R  S  T  U  V

 

A

access lines    1
description    12
accesses    
configuring subscriptions    
SRC CLI
accounting    
basic RADIUS accounting plug-in
custom RADIUS accounting plug-ins
flat file accounting plug-ins
flexible RADIUS accounting plug-ins
anonymous subscriber
attributes    
RADIUS accounting
authenticated subscriber
authentication plug-ins    
configuring
types
authorization plug-ins    
configuring
types
 

B

basic RADIUS accounting plug-in    1
configuring    
SRC CLI
basic RADIUS authentication plug-in    1
configuring    
SRC CLI
 

C

captive portal    
preventing access to resources
classification scripts    
conditions    1
glob matching
joining
regular expression matching
configuring    
C-Web interface
descriptions
DHCP classification, C Series Controller    
conditions
configuring, SRC CLI
description
targets
interface classification, C Series Controller    
conditions
configuring, SRC CLI
description
empty policy    12
examples
how it works
targets
structure    
C-Web interface
subscriber classification, C Series Controller    
condition
configuring, SRC CLI
description
DHCP options
enterprise subscriber example
how it works
static IP subscriber example
subscriber group example
targets
target, C Series Controller    
definition
expressions
types
component interactions    
DHCP    
initial login
persistent login
subscriber account login
subscriber logout
enterprise subscribers    
login
remote session activation
PPP    
login
logout
static IP subscribers
subscription activation
subscription deactivation
conventions    
notice icons
text
COPS (Common Open Policy Service)    
DHCP interactions    
initial login
logout
persistent login
subscriber account login
interface startup interactions
PPP interactions    
login
logout
static IP subscriber interactions
subscription activation interactions
subscription deactivation interactions
custom RADIUS accounting plug-ins    1
configuring    
SRC CLI
custom RADIUS authentication plug-ins    1
configuring    
SRC CLI
customer support    1
contacting JTAC
 

D

default retailer authentication plug-ins    
configuring    
SRC CLI
default retailer DHCP authentication plug-ins    
configuring    
SRC CLI
denial-of-service attacks
DHCP (Dynamic Host Configuration Protocol)    
address assignment
classification scripts.     See classification scripts    
options
profiles    
SRC CLI
subscribers    
login process
logout process
documentation    
comments on
 

E

enterprise    
description
enterprise subscribers    1
adding    
SRC CLI
enterprise subscribers, login process
event publishers    
configuring    
SRC CLI
default retailer authentication, configuring    
SRC CLI
default retailer DHCP authentication, configuring    
SRC CLI
description
retailer-specific
service-specific
virtual router-specific
external plug-ins    
configuring    
SRC CLI
 

F

file upload settings for log rotation    
configuring    
SRC CLI
flat file accounting plug-ins    1
configuring    
SRC CLI
configuring headers    
SRC CLI
flexible RADIUS accounting plug-ins    1
attributes, defining    
C-Web interface
configuring
RADIUS packets, defining
flexible RADIUS authentication plug-ins    1
attributes, defining    
C-Web interface
examples
configuring    
SRC CLI
RADIUS packets, defining    
SRC CLI
setting responses    
C-Web interface
FTP server for log rotation    
configuring    
SRC CLI    12
 

G

general properties    
configuring    
SRC CLI
 

H

HTTP proxy    12
HTTPS traffic
 

I

interface classification scripts.     See classification scripts    
interim accounting, configuring on SAE
internal plug-ins    
configuring    
SRC CLI
 

L

LDAP authentication plug-in    1
configuring    
SRC CLI
limiting subscribers plug-in    1
configuring    
SRC CLI
log rotation    
overview    
SRC CLI
logging    
redirect server
login events, description
login process    
enterprise
residential    12,  See also logout process, residential    
DHCP
PPP
summary
login registration    
configuring    
SRC CLI
logout process, residential    
DHCP
 

M

managers    
configuring    
SRC CLI
control over all retailers
management privileges
subscribers and subscriptions
manuals    
comments on
 

N

NAT (Network Address Translation)    
VPNs
notice icons
 

P

plug-ins    
activating service sessions
authentication    
configuring
authorization    
configuring
basic RADIUS accounting    1
configuring, SRC CLI
basic RADIUS authentication    1
configuring, SRC CLI
creating subscriber sessions
custom RADIUS accounting    1
configuring, SRC CLI
custom RADIUS authentication    1
configuring, SRC CLI
defining RADIUS packets    
SRC CLI
DHCP address assignment
event publishers.     See event publishers    
external    
configuring, SRC CLI
flat file accounting    1
configuring, SRC CLI
flexible RADIUS accounting    1
configuring
flexible RADIUS authentication    1
configuring, SRC CLI
internal    1
authorization
configuring RADIUS peers, SRC CLI
configuring, SRC CLI
customizing RADIUS packets
how they work
pool
RADIUS attributes, C-Web interface
tracking
LDAP authentication    1
configuring, SRC CLI
limiting subscribers    1
configuring, SRC CLI
state synchronization    
configuring, SRC CLI
tracking    
configuring, C-Web interface
service sessions
subscriber sessions
policy groups    
empty    12
policy management    
external policy system    12
PPP subscribers    
login process
Web login
prevention, use of unauthorized resources
protocols    
routing
proxy HTTP    12
proxy request management
public addresses, VPNs
 

Q

QoS tracking plug-in
 

R

RADIUS accounting    
attributes
description
RADIUS attributes    
defining in RADIUS plug-ins    
C-Web interface
examples, defining in RADIUS plug-ins    
C-Web interface
RADIUS client library, custom RADIUS plug-ins
RADIUS packets, customizing in plug-ins
RADIUS peers    
configuring in plug-ins    
SRC CLI
RADIUS plug-ins    1,  See also plug-ins    
authentication
UDP port
redirect server    
assessing load    
C-Web interface
configuration statements    
SRC CLI
configuring    
SRC CLI
configuring DNS server for    
SRC CLI
configuring HTTP proxy support    
SRC CLI
configuring redundant    
SRC CLI
directory connection    
SRC CLI
failover
file extensions    
SRC CLI
logging
number of requests    
SRC CLI
protection against denial-of-service attacks
redundancy    123
static route to router
traffic definition    
SRC CLI
verifying    
SRC CLI
redundancy    
redirect server
residential subscribers    1
adding    
SRC CLI
login process.     See login process    
retailers    
subscribers    1
adding, SRC CLI
router subscribers    1
adding    
SRC CLI
routing instances    
VPNs
routing scheme
 

S

SAE (service activation engine)    
classification scripts.     See classification scripts    
login events
login process.     See login process    
SAE (service activation engine), configuring    
interim accounting    
SRC CLI
login registration    
SRC CLI
multiple logins from same IP address    
SRC CLI
reduce reported session time    
SRC CLI
session reactivation timers    
SRC CLI
time for MAC address in cache    
SRC CLI
unauthenticated user DN    
SRC CLI
service activation engine.     See SAE    
service sessions    
activate-on-login    12
activating and tracking
activating with Web application
enterprise, remote activation
sites    123
subscriber    1
adding, SRC CLI
state synchronization plug-in interface    
configuring    
SRC CLI
static IP subscribers, login process
static routing
subscriber classification scripts.     See classification scripts    
subscriber folders    1
adding    
SRC CLI
subscriber sessions    
activating with Web application
creating and tracking
enterprise, creating and activating
subscribers    
3gpp attributes (Gx router driver)    
configuring, SRC CLI
adding    
SRC CLI
enterprise    1
adding, SRC CLI
inheriting properties
inheriting subscriptions
residential    1
adding, SRC CLI
retailer    1
adding, SRC CLI
router    1
adding, SRC CLI
sessions
sites    1
adding, SRC CLI
types
subscriptions    1
access, configuring    
SRC CLI
an orderly deactivation, activation order, specifying    
SRC CLI
configuring    
SRC CLI
multiple per subscriber
support, technical     See technical support    
 

T

targets.     See classification scripts    
technical support    
contacting JTAC
text conventions defined
tracking plug-ins    1
configuring    
C-Web interface
 

U

UDP ports    
RADIUS plug-ins
User Datagram Protocol.     See UDP    
 

V

validating    
VPNs
virtual private networks.     See VPNs    
VPNs (virtual private networks)    
adding    
SRC CLI
configuration requirements
configuration statements
extranet clients, modifying    
SRC CLI
invalid subscriptions
modifying
routing schemes
using NAT
validating

Related Documentation

Classification Scripts Overview

The service activation engine (SAE) uses classification scripts to determine whether it manages router interfaces, to select default policies, to find subscriber profiles, and to choose Dynamic Host Configuration Protocol (DHCP) profiles. The SAE has three classification scripts:

  • Interface classification script—When a subscriber’s IP interface comes up on the router, the router sends the subscriber’s login and interface information to the SAE.

    The SAE runs the interface classification script to determine whether the SAE:

    • Manages the interface and if so, what default policies to send to the router
    • Does not manage the interface, but supports subscriber sessions on JunosE routers for services that use policies managed through an external policy management system
  • Subscriber classification script—If the SAE is managing the interface, the SAE uses the login and interface information that the router sends to run the subscriber classification script to determine which subscriber profile to load into memory. The SAE runs subscriber classification scripts regardless of whether the interface is being managed or not for the devices other than JunosE.
  • DHCP classification script—For DHCP subscribers, the SAE runs DHCP classification scripts to choose DHCP profiles.

How Classification Scripts Work

Classification scripts consist of targets and conditions.

  • A target is the result of the classification script. For example, the result of subscriber classification scripts is an LDAP search string that is used to find a unique subscriber profile. The result of interface classification scripts is a policy group.
  • Conditions are match criteria. The script attempts to match conditions in the script with information sent from the router. For example, match conditions for a subscriber classification script might be login type or domain name. Match conditions for an interface classification script could be interface IP address or interface description.

Each script can have multiple targets, and each target can have multiple conditions. When an object needs classification, the script processes the targets in turn. Within each target, the script processes conditions sequentially. When it finds that the classification conditions for a target match, it returns the target to the SAE. If the script does not find any targets that can be matched, the classifier engine returns a no-match message to the SAE.

Because classification scripts examine conditions sequentially as the conditions appear in the script, you should put more specific conditions at the beginning of the script and less specific conditions at the end of the script.

Interface Classification Scripts

When a subscriber’s IP interface comes up on the router, the router sends the subscriber’s login and interface information to the SAE. For example, the router might send the following information:

IP address=0.0.0.0Virtual router name=default@erx5_ssp58 Interface name=FastEthernet3/1.1PPP login name (PPP)=pebbles@virneo.netUser IP address (PPP)=192.168.55.5Interface speed=100000000Interface description=P3/1.1Interface alias=1st pppoe intRADIUS class=null

The SAE invokes the interface classification script and provides to the script the information that it received from the router. The script engine matches the information sent from the router to the conditions in the interface classification script. The script examines each condition in sequential order to find a match.

  • If it finds a match, the script processing stops, and the target for that condition is returned to the SAE. The target is the path of a policy group.

    This policy group is one of the following:

    • The default policy. In this case, the SAE installs the policy on the interface and begins managing the interface.
    • An empty policy. In this case, the SAE allows subscriber session to start and manages services for the subscriber on routers that run JunosE software. The policies are managed by an external policy management system.
  • If it does not find a match, the script sends a no-match message to the SAE. For JunosE routers, the SAE does not manage the interface (that is, the policies installed through RADIUS or the CLI remain in effect), does not install policies, and does not attempt to log in subscribers. For the other types of devices, the SAE attempts to log in subscribers regardless of whether the interface is being managed or not.

Subscriber Classification Scripts

When the SAE begins managing an interface, it determines whether a subscriber is associated with the interface by running the subscriber classification script. The SAE also runs the subscriber classification script when certain login events occur. See Login Events for a description of login event types.

To find the matching subscriber profile, the SAE uses interface information that it received from the router when the interface became operational (for example, virtual router name, interface name, interface alias). It also uses login information that it received from the router or the portal application when the subscriber attempted to log in (for example, subscriber IP address, login name, or login event type).

When the SAE runs the subscriber classification script, the script engine matches the information sent from the router to the conditions in the subscriber classification script. The script examines each condition in sequential order to find a match.

  • If it finds a match, the script processing stops, and the target for the matching condition is returned to the SAE. The target is an LDAP query that uniquely identifies a subscriber profile. The SAE loads the subscriber entry and uses the entry to create a subscriber session in memory.
  • If it does not find a match, the script sends a no-match message to the SAE. The SAE does not load a subscriber session onto the interface, and services cannot be activated for this session.

DHCP Classification Scripts

DHCP classification scripts choose DHCP profiles. See Assigning DHCP Addresses to Subscribers for information about how DHCP classification scripts are used.

Sharing Information Among Classification Scripts

In many instances, the same classification rule may appear in different classification scripts. You can reuse the same information in different scripts by configuring the information in one script and including that information in another script. Interface, subscriber, and DHCP classification scripts all let you include another script.

Related Documentation

Modified: 2015-06-19