A
- address pools
- assigned IP subscribers
- address pools. See IP address pools
- application manager
- assigned IP subscribers
- PCMM network 1, 2
- setting timeouts
- voice over IP
C
- cable modem termination system. See CMTS devices
- classify-traffic condition
- match direction, setting
- client type 1, PCMM
- client type 2, PCMM
- CMTS devices
- CMTS locator
- monitoring
- COA script services, configuring
- configuration wizard
- configuration wizards
- conventions
- custom RADIUS authentication plug-ins
- customer support 1
D
- Data over Cable Service Interface Specifications. See DOCSIS protocol
- Diameter
- Diameter server
- DOCSIS protocol
- documentation
- domains
- Dynamic policy changes
- dynamic RADIUS authorization requests
E
- end-to-end services
- event notification, PCMM network
- configuration statements
- description
- properties, configuring
F
- filter actions
- configuring
- flexible RADIUS authentication plug-ins
- forwarding class actions
- configuring
G
- Gx router driver
- application information, configuring
- dynamic PCC rules, configuring
- flow information, configuring
- overview
- policies, configuration statements
- policies, configuring
- policy list, configuring
- QoS information, configuring
- redirect information, configuring
- static PCC rules, configuring
- steering information, configuring
I
- IP address pools
- assigned IP subscribers
- assigned IP subscribers, configuring
- local address pools, configuring
- static pools, configuring
J
- JPS (Juniper Policy Server)
- application manager-to-policy server interface, configuring
- application manager-to-policy server interface, monitoring
- architecture
- CMTS devices, monitoring
- CMTS locator, monitoring
- JPS state, monitoring
- logging, configuring
- logging, modifying
- message flows, monitoring
- message handler, monitoring
- monitoring
- C-Web interface
- SRC CLI 1, 2
- operational status
- overview
- policy server-to-CMTS interface, configuring
- policy server-to-CMTS interface, monitoring
- policy server-to-RKS interface, configuring
- policy server-to-RKS interface, monitoring
- server process, monitoring
- starting
- stopping
- subscriber address mappings, configuring
- subscriber configuration, modifying
- JSRC
- JSRC and PTSP configuration example
- Juniper Policy Server. See JPS
L
- login process
M
- manuals
- MX Series router as a PTSP network device
- MX Series router as a PTSP network device, adding
N
- NIC (network information collector)
- IP address pools, configuring
- notice icons
P
- packet mirroring, configuring
- PCMM (PacketCable Multimedia)
- application manager, role
- client type 1
- client type 2
- CMTS device, role
- configuring SAE
- 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
- 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
- video-on-demand example
- videoconferencing example
- PCMM device driver
- configuration statements
- configuring
- PCMM record-keeping server plug-in
- configuration statements
- configuring
- description
- plug-ins
- policy actions
- filter
- forwarding class
- forwarding instance
- policy groups
- configuring
- policy servers
- adding application manager groups
- adding objects to directory
- role, in PCMM architecture
- specifying application managers
- specifying SAE communities
- PTSP
- PTSP actions
- PTSP classify-traffic condition
- PTSP classify-traffic conditions
- PTSP device driver
- PTSP on MX Series router
- PTSP on MX Series router, configuring
- PTSP policer instance
- PTSP policer instance, configuring
- PTSP policies
- PTSP policies, configuring
- PTSP policy list
- PTSP policy list, configuring
- PTSP policy rules
- network, specifying
- PTSP policy rules, configuring
- PTSP session store
- PTSP device driver session store, configuring
- PTSP traffic match
- conditions, setting
Q
- QoS (quality of service)
- QoS profile-tracking plug-in
- QoS profiles, routers running JunosE Software
- how tracking works
- managing dynamically
- updating directory, using
- quality of service. See QoS
R
- RADIUS
- record-keeping server. See RKS
- RKS (record-keeping server)
- peers, configuration statements
- peers, configuring in plug-ins
- plug-in
- plug-in, configuration statements
- plug-in, configuring
- role in PCMM environment
- roaming wireless environment
S
- SAE (service activation engine)
- configuring as an application manager
- PCMM environment
- redundancy. See SAE communities
- SAE (service activation engine), configuring
- SAE communities
- configuration overview
- configuration statements
- configuring manager
- defining members
- description
- service flows
- services
- session store
- single phase resource reservation model, PCMM
- subscriber
- support, technical See technical support
T
- technical support
- text conventions defined
- traffic policies, PCMM
W
Download This Guide
Related Documentation
- SSR Database Schema
- Making Modifications to the SSR Database Schema Overview
- Configuring Global and Default Retailer Event Publishers (SRC CLI)
- Adding an MX Series Router as a PTSP Network Device (SRC CLI)
- Configuring Global and Default Retailer Event Publishers (SRC CLI)
- SSR Database Schema
- Making Modifications to the SSR Database Schema Overview
Configuring the SAE to Obtain Information About Subscribers (SRC CLI)
You can configure the SAE to obtain information about dynamic subscribers from the MX Series routers that support PTSP by making attachment session information available to the SAE. Tasks to configure the SAE for this purpose are:
Obtaining Subscriber Session Information from the SSR Database
You can obtain subscriber information from the Session State Registrar (SSR) database. The SSR reader plug-in obtains information about attachment sessions from the SSR to set the values for the plug-in attributes. The SSR reader authentication plug-in can be used by a specific virtual router or for all virtual routers.
Use the following configuration statements to set up an SSR reader plug-in:
To configure the SSR reader plug-in:
- From configuration mode, access the SSR reader plug-in
configuration. user@host# edit shared sae configuration plug-ins name name ssr-reader
- (Optional) Specify the plug-in attribute whose value is
set from the SSR subscriber sessions table. [edit shared sae configuration plug-ins name name ssr-reader]user@host# set read-attributes [read-attributes...]
Configuring Event Publishers
You can configure the event publisher to use the SSR reader authentication plug-in.
To configure the global or default event publisher for PTSP:
- From configuration mode, access the statement that configures
the event publisher. user@host# edit shared sae configuration plug-ins event-publishers
- (Optional) Specify the plug-ins that authenticate subscribers
who are assigned to a virtual router that does not specify an authentication
plug-in. [edit shared sae configuration plug-ins event-publishers]user@host# set default-vr-authentication [default-vr-authentication...]
- (Optional) Specify the plug-ins that authenticate subscribers
who log in through a specific type of device (for example, junos-ptsp). [edit shared sae configuration plug-ins event-publishers]user@host# set device-type-authentication junos-ptsp [plug-ins...]
To specify the plug-ins that authenticate subscribers who log in through a specific virtual router, set the authentication-plug-in option when you are adding the virtual router for the network device. See Adding an MX Series Router as a PTSP Network Device (SRC CLI).
Related Documentation
- Adding an MX Series Router as a PTSP Network Device (SRC CLI)
- Configuring Global and Default Retailer Event Publishers (SRC CLI)
- SSR Database Schema
- Making Modifications to the SSR Database Schema Overview