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
- Configuring the Fields in the Subscriber Sessions Table (SRC CLI)
- SSR Database Schema
- Modifying Attribute Mapping in an Active SSR Cluster (SRC CLI)
- Modifying the SSR Database Schema in an Active Cluster (SRC CLI)
Configuring the SAE to Write Information About Subscribers to the SSR Database (SRC CLI)
When you use an SRC-managed device—for example, an E Series Broadband Services Router as the access node in a PTSP application—you can configure the SAE to write information about dynamic subscribers directly to the SSR database. To do this, you need to configure the SSR writer and specify the mapping between access subscriber session attributes and the SAE plug-in attributes used to identify service node subscriber sessions.
![]() | Note: Before you configure the SSR writer, we recommend that you configure the mapping between the SAE plug-in attributes and the SSR subscriber sessions table. The subscriber sessions table schema requires the user IP address and VPN ID; see SSR Database Schema. |
Use the following statements to configure the mapping between access subscriber session attributes and the SAE plug-in attributes:
To configure the mapping between access subscriber session attributes and the SAE plug-in attributes:
- From configuration mode, access the statement that configures
the SSR writer plug-in and specify a name for the plug-in configuration.
For example, to configure a plug-in configuration called pc1:[edit]user@host# edit shared sae configuration plug-ins name pc1 ssr-writer
The name you specify for the configuration plug-in must be specified for the user-tracking-plug-in option under the edit shared network device name virtual-router name statement.
- Specify the name of an SAE plug-in attribute to be mapped
to the access session attribute, or literal. For example, to specify
the login-name SAE plugin attribute:[edit shared sae configuration plug-ins name pc1 ssr-writer]user@host# edit plugin-attributes login-name
- Specify the name of either an access plug-in attribute
or a literal to be mapped to the SAE plug-in attribute.
- To specify an access plug-in attribute—for example,
login-name:[edit shared sae configuration plug-ins name pc1 ssr-writer plugin-attributes login-name]user@host# set access-plugin-attributes login-name
- To specify a literal—for example, xyz-name:[edit shared sae configuration plug-ins name pc1 ssr-writer plugin-attributes login-name]user@host# set literal xyz-name
- To specify an access plug-in attribute—for example,
login-name:
Related Documentation
- Configuring the Fields in the Subscriber Sessions Table (SRC CLI)
- SSR Database Schema
- Modifying Attribute Mapping in an Active SSR Cluster (SRC CLI)
- Modifying the SSR Database Schema in an Active Cluster (SRC CLI)