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
Managing Services on MX Series Routers Using the Diameter Application
You can use the SRC software to manage services on Juniper Networks routing platforms using the Diameter protocol. The SRC software communicates with the local SRC peer on the device using Diameter messages to dynamically manage services for a subscriber session.
The SRC software includes a Diameter server that forwards AAR, ACR, SRQ, and STR messages from JSRC to the device driver in the SAE and that forwards PPR and ASR messages from the device driver to JSRC. These Diameter messages perform these functions:
- AA-Request (AAR)—Attach subscriber to access network
- Accounting-Request (ACR)—Provide accounting information
- Abort-Session-Request (ASR)—Disconnect subscriber
- Push-Profile-Request (PPR)—Start, modify, or stop service session
- Session-Resource-Query (SRQ)—Initiate synchronization
- Session-Termination-Request (STR)—Detach subscriber from access network
You configure the Diameter peers and a device for each device managed by the SAE. The Diameter server searches all devices of type junos-ise for virtual routers that include the local host in their SAE connections. For these devices, the Diameter server establishes a connection with the peers referenced in the device configuration.
Tasks to set up the management of services on devices using Diameter protocol:
- Configuring JSRC on the MX Series Router
- Configuring the Diameter Application (SRC CLI)
- Adding Network Devices (SRC CLI)
- Configuring Diameter Peers (SRC CLI)
- Configuring the SAE to Manage Network Devices (SRC CLI)
- Configuring JSRC Policies (SRC CLI)