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  C  D  E  F  G  I  J  L  M  N  P  Q  R  S  T  W

 

A

address pools    
assigned IP subscribers    
configuring
address pools.     See IP address pools    
application manager    
role, in PCMM environment
assigned IP subscribers    
PCMM network    12
address pools
IP address pools
setting timeouts
voice over IP
 

C

cable modem termination system.     See CMTS devices    
classify-traffic condition    
match direction, setting    
SRC CLI
client type 1, PCMM
client type 2, PCMM
CMTS devices    
adding objects to directory    
SRC CLI
adding virtual router objects to directory    
SRC CLI
configuration statements    12
role
CMTS locator    
monitoring    
C-Web interface
SRC CLI
COA script services, configuring
configuration wizard    
fair usage    
configuration overview
running
running    12
configuration wizards    
fair usage    
overview
overview    12
conventions    
notice icons
text
custom RADIUS authentication plug-ins
customer support    1
contacting JTAC
 

D

Data over Cable Service Interface Specifications.     See DOCSIS protocol    
Diameter    
peers    
configuring    12
Diameter server    
clients, viewing    
SRC CLI
message flows, viewing    
SRC CLI
message handler, viewing    
SRC CLI
monitoring    
SRC CLI
peers, viewing    
SRC CLI
server process, viewing    
SRC CLI
server requests, viewing    
SRC CLI
statistics, viewing    
SRC CLI
status, viewing    
SRC CLI
DOCSIS protocol
documentation    
comments on
domains    
IP service edge
IP subscriber edge
radio frequency
Dynamic policy changes    
Dynamic policy changes, managing
dynamic RADIUS authorization requests    
RADIUS packets, defining    12
 

E

end-to-end services
event notification, PCMM network    
configuration statements
description
properties, configuring    
SRC CLI
 

F

filter actions    
configuring    
SRC CLI
flexible RADIUS authentication plug-ins    
configuring
forwarding class actions    
configuring    
SRC CLI
 

G

Gx router driver    
application information, configuring    
SRC CLI
dynamic PCC rules, configuring    
SRC CLI
flow information, configuring    
SRC CLI
overview
policies, configuration statements    
SRC CLI
policies, configuring    
SRC CLI
policy list, configuring    
SRC CLI
QoS information, configuring    
SRC CLI
redirect information, configuring    
SRC CLI
static PCC rules, configuring    
SRC CLI
steering information, configuring    
SRC CLI
 

I

IP address pools    
assigned IP subscribers
assigned IP subscribers, configuring    
SRC CLI
local address pools, configuring    
SRC CLI
static pools, configuring    
SRC CLI
 

J

JPS (Juniper Policy Server)    
application manager-to-policy server interface, configuring
application manager-to-policy server interface, monitoring    
C-Web interface    12
SRC CLI
architecture
CMTS devices, monitoring    
C-Web interface
CMTS locator, monitoring    
C-Web interface
SRC CLI
JPS state, monitoring
logging, configuring
logging, modifying
message flows, monitoring    
C-Web interface
SRC CLI
message handler, monitoring    
C-Web interface
SRC CLI
monitoring    
C-Web interface
SRC CLI    12
operational status
overview
policy server-to-CMTS interface, configuring
policy server-to-CMTS interface, monitoring    
C-Web interface    12
SRC CLI
policy server-to-RKS interface, configuring
policy server-to-RKS interface, monitoring    
C-Web interface
SRC CLI
server process, monitoring    
C-Web interface
SRC CLI
starting    
SRC CLI
stopping    
SRC CLI
subscriber address mappings, configuring
subscriber configuration, modifying
JSRC    
JSRC and PTSP configuration example    
SRC CLI
Juniper Policy Server.     See JPS    
 

L

login process    
assigned IP subscribers, PCMM
 

M

manuals    
comments on
MX Series router as a PTSP network device    
MX Series router as a PTSP network device, adding    
SRC CLI
 

N

NIC (network information collector)    
IP address pools, configuring    
SRC CLI
notice icons
 

P

packet mirroring, configuring
PCMM (PacketCable Multimedia)    
application manager, role
client type 1
client type 2
CMTS device, role
configuring SAE    
SRC CLI
creating sessions
description
end-to-end QoS architecture
end-to-end services
integrating SRC software
IP service edge domain
IP subscriber edge domain
logging in subscribers    
assigned IP method
overview
overview
policy server, role
provisioning end-to-end services
record-keeping server
RF domain
SAE
SAE communities
session store
single-phase resource reservation model
SRC software in    
description
traffic profiles
video-on-demand example
videoconferencing example
PCMM device driver    
configuration statements
configuring    
SRC CLI
PCMM record-keeping server plug-in    
configuration statements
configuring    
SRC CLI
description
plug-ins    
PCMM record-keeping server plug-in
policy actions    
filter    
configuring, SRC CLI
forwarding class    
configuring, SRC CLI
forwarding instance    
configuring, SRC CLI
policy groups    
configuring    
SRC CLI
policy servers    
adding application manager groups    
SRC CLI
adding objects to directory    
SRC CLI
role, in PCMM architecture
specifying application managers    
SRC CLI
specifying SAE communities    
SRC CLI
PTSP    
configuring    
SRC CLI
PTSP and JSRC configuration example    
SRC CLI
PTSP configuration example    
SRC CLI
PTSP policies, configuration statements    
SRC CLI
ssr-writer    
SRC CLI
PTSP actions    
PTSP actions, configuring    
SRC CLI    12
PTSP classify-traffic condition    
destination grouped network, configuring    
SRC CLI
destination network, configuring    
SRC CLI
protocol conditions with parameters, setting    
SRC CLI
protocol conditions with ports, setting    
SRC CLI
protocol conditions, setting    
SRC CLI
TCP conditions, setting    
SRC CLI
traffic match conditions, setting    
SRC CLI
PTSP classify-traffic conditions    
creating    
SRC CLI
PTSP classify-traffic conditions, configuring    
SRC CLI
PTSP device driver    
overview
PTSP device driver, configuring    
SRC CLI
PTSP on MX Series router    
PTSP on MX Series router, configuring    
SRC CLI
PTSP policer instance    
PTSP policer instance, configuring    
SRC CLI
PTSP policies    
PTSP policies, configuring    
SRC CLI
PTSP policy list    
PTSP policy list, configuring    
SRC CLI
PTSP policy rules    
network, specifying
PTSP policy rules, configuring    
SRC CLI
PTSP session store    
PTSP device driver session store, configuring    
SRC CLI
PTSP traffic match    
conditions, setting    
SRC CLI
 

Q

QoS (quality of service)    
PCMM environments    
end-to-end QoS architecture
extending to service edge domain
extending to subscriber edge domain
searching for policies in directory
QoS profile-tracking plug-in    
description
QoS profiles, routers running JunosE Software    
how tracking works
managing dynamically
updating directory, using    
qosProfilePublish
quality of service.     See QoS    
 

R

RADIUS    
vendor-specific attributes for wireless ISP roaming
record-keeping server.     See RKS    
RKS (record-keeping server)    
peers, configuration statements
peers, configuring in plug-ins    
SRC CLI
plug-in
plug-in, configuration statements
plug-in, configuring    
SRC CLI
role in PCMM environment
roaming wireless environment
 

S

SAE (service activation engine)    
configuring as an application manager    
SRC CLI
PCMM environment
redundancy.     See SAE communities    
SAE (service activation engine), configuring    
community manager    
SRC CLI
event notification API properties    
SRC CLI
PCMM device driver    
SRC CLI    12
SAE communities    
configuration overview    
SRC CLI
configuration statements
configuring manager    
SRC CLI
defining members    
SRC CLI
description
service flows
services    
voice over IP (VoIP)
session store    
in PCMM environment
single phase resource reservation model, PCMM
subscriber    
wireless environment
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
traffic policies, PCMM
 

W

wireless environment

Using the SRC Software to Support PTSP

When you use the SRC software to support PTSP on MX Series routers, the SRC software can become aware of the subscribers before or after a PTSP session has been created. This topic describes the interaction among the components in the basic scenario and the sequence of events for different situations.

Accessing the Network Before the SRC Cluster Is Notified About a PTSP Session

The CPE connects to the network and the SRC cluster is notified about the connection before a PTSP session is created. In this case, the attachment session exists before the PTSP session. The sequence of events is:

  1. The CPE connects to the network through the access device.
  2. The access device notifies the access manager about the session start.
  3. The access manager forwards the session start notification to the SIC, which translates the attributes into SRC-specific attributes.
  4. The SIC creates an attachment session in the SSR.
  5. (Optional) The subscriber activates a service through the ASG. (In the sequence of events, this step is the earliest one for using the ASG.)
  6. (Optional) The ASG creates a service session in the SSR that is associated with the attachment session. If the attachment session does not exist, the service activation fails.
  7. The CPE accesses the network. The service node detects a new IP flow and creates a PTSP session.
  8. The service node notifies the SAE that is currently managing the MX Series router. The SAE extracts the IP address, and optionally the VPN ID, from the PTSP session information.
  9. The SAE starts managing the PTSP session and calls the SSR reader authentication plug-in to obtain attachment session information from the SSR. The data from the SSR is used in the classification context.
  10. The SAE runs the subscriber classification script, loads a subscriber profile, and creates a subscriber session. The subscriber session activates any subscribed activate-on-login service.
  11. When the subscriber session is completely activated, the SAE installs any active policies on the service node.

Accessing the Network After the SRC Cluster Is Notified About a PTSP Session

The CPE connects to the network and the SRC cluster is notified about the connection after a PTSP session is processed. In this case, the attachment session does not exist before the PTSP session. The sequence of events is:

  1. The CPE connects to the network through the access device.
  2. The CPE accesses the network. The service node detects the new IP flow and creates a PTSP session.
  3. The service node notifies the SAE that is currently managing the MX Series router. The SAE extracts the VPN ID from the PTSP session information.
  4. The SAE starts managing the PTSP session and calls the SSR reader authentication plug-in to obtain attachment session information from the SSR. No information is returned to the SAE because the attachment session does not exist yet.
  5. The SAE creates an unauthenticated (anonymous) subscriber session.
  6. When the subscriber session is completely activated, the SAE installs any active policies on the service node.
  7. The access device notifies the access manager about the session start.
  8. The access manager forwards the session start notification to the SIC.
  9. The SIC creates the attachment session in the SSR.
  10. The SSR notifies the SAE that the attachment session has been modified. The SAE finds any affected subscriber sessions. The SSR notifies all active SAEs in the same cluster.
  11. For any affected subscriber session, the SAE updates the classification context and initiates a login. This login runs the subscriber classification script and compares the result.
    • If the subscriber profile has changed, the existing session is terminated and a new session is created.
    • If the subscriber profile has not changed, the provisioned policies for active services are verified to determine whether they are affected by the updated attachment information.
  12. Any changes are applied to the service node. If no policies have changed but the subscriber identity is different, the SAE changes the subscriber identity on the service node.
  13. The subscriber activates a service through the ASG.
  14. The ASG creates a service session in the SSR.
  15. The SSR notifies all SAEs that a new service session exists.
  16. The SAE that manages PTSP sessions for the attachment session activates a service session for the appropriate subscriber session.

Changing the Network Connection

The CPE connects to the network by different means. The attachment session is modified without changing the IP layer. The sequence of events is:

  1. The CPE connects to the network through the access device in a different manner. For example, a wireless device roams to a different access point.
  2. The access device notifies the access manager about the modified session parameters.
  3. The access manager forwards the notification to the SIC.
  4. The SIC updates the attachment session in the SSR.
  5. The SSR notifies the SAE that the attachment session has been modified. The SAE finds any affected subscriber sessions. The SSR notifies all active SAEs in the same cluster.
  6. For any affected subscriber session, the SAE updates the classification context and initiates a login. This login runs the subscriber classification script and compares the result.
    • If the subscriber profile has changed, the existing session is terminated and a new session is created.
    • If the subscriber profile has not changed, the provisioned policies for active services are verified to determine whether they are affected by the updated attachment information.
  7. Any changes are applied to the service node. If no policies have changed but the subscriber identity is different, the SAE installs a policy on the service node with the changed subscriber identity.

If the IP layer is modified, the existing attachment session is terminated and a new attachment session is created.

Disconnecting from the Network

The network connection is terminated. The sequence of events for attachment session termination is:

  1. The CPE disconnects from the network.
  2. The access device notifies the access manager.
  3. The access manager forwards the notification to the SIC.
  4. The SIC terminates the attachment session in the SSR.
  5. The SSR notifies the SAE.
  6. The SAE terminates the subscriber session.
  7. The SAE terminates the PTSP session on the service node.

Terminating the PTSP Session

The service node detects the end of the PTSP session because of an idle timeout. The sequence of events for PTSP session termination is:

  1. The service node detects an idle timeout, terminates the PTSP session, and notifies the SAE.
  2. The SAE terminates any subscriber session associated with the PTSP session, which terminates any service session and generates final accounting information.

PTSP session termination does not affect the attachment session.

If the attachment session remains active and the CPE accesses the network again, the sequence of events is the same as connecting to the network without a PTSP session.

If the attachment session terminates, the SAE receives a notification and terminates any remaining PTSP sessions associated with the attachment session. If there are no associated PTSP sessions, the SAE ignores the event.

Related Documentation

Modified: 2015-06-19