Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
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
- Using the SAE in a PCMM Environment
- PCMM Environment Overview
- Configuring PCMM Record-Keeping Server Plug-Ins (C-Web Interface)
- Initially Configuring the SAE
Configuring PCMM Record-Keeping Server Plug-Ins (SRC CLI)
Use the following configuration statements to configure an RKS plug-in.
shared sae configuration plug-ins name name pcmm-rks {load-balancing-mode (failover | roundRobin);
failback-timer failback-timer;
retry-interval retry-interval ;
maximum-queue-length maximum-queue-length ;
bind-address bind-address ;
udp-port udp-port ;
feid-mso-data feid-mso-data ;
feid-mso-domain-name feid-mso-domain-name ;
trusted-element;
default-peer default-peer ; }
failback-timer failback-timer;
retry-interval retry-interval ;
maximum-queue-length maximum-queue-length ;
bind-address bind-address ;
udp-port udp-port ;
feid-mso-data feid-mso-data ;
feid-mso-domain-name feid-mso-domain-name ;
trusted-element;
default-peer default-peer ; }
To configure an RKS plug-in:
- From configuration mode, access the configuration statements
for RKS plug-ins. In this sample procedure, west-region is the name
of the SAE group, and rksPlugin is the name of the plug-in. user@host# edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks
- Specify the mode for load-balancing RKSs.[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set load-balancing-mode (failover | roundRobin)
- Specify if and when the SAE attempts to fail back to the
default peer.[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set failback-timer failback-timer
- Specify the time the SAE waits for a response from an
RKS before it resends the packet.[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set retry-interval retry-interval
- Specify the maximum number of unacknowledged messages
that the plug-in receives from the RKS before it discards new messages.[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set maximum-queue-length maximum-queue-length
- (Optional) Specify the source IP address that the plug-in
uses to communicate with the RKS. [edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set bind-address bind-address
- (Optional) Specify the source UDP port or a pool of ports
that the plug-in uses to communicate with the RKS.[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set udp-port udp-port
- (Optional) Specify the multiple service operator (MSO)—defined
data in the financial entity ID (FEID) attribute, which is included
in event messages. [edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set feid-mso-data feid-mso-data
- (Optional) Specify the MSO domain name in the FEID attribute
that uniquely identifies the MSO for billing and settlement purposes. [edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set feid-mso-domain-name feid-mso-domain-name
- (Optional) When the SAE is running as a policy server—which
means that the SAE sends event messages directly to the RKS—enable
the SAE as a trusted network element. [edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set trusted-element
- Specify the name of the primary RKS peer to which the
SAE sends accounting packets.
See Configuring Record-Keeping Server Peers for Plug-Ins (SRC CLI).
[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host# set default-peer default-peer - (Optional) Verify your RKS plug-in configuration.
[edit shared sae group west-region configuration plug-ins name rksPlugin pcmm-rks] user@host> show load-balancing-mode failover; failback-timer -1; retry-interval 3000; maximum-queue-length 10000; feid-mso-domain-name abcd.com; trusted-element; default-peer radius01;
- (Optional) Specify an RKS plug-in for specific CMTS devices.
Related Documentation
- Using the SAE in a PCMM Environment
- PCMM Environment Overview
- Configuring PCMM Record-Keeping Server Plug-Ins (C-Web Interface)
- Initially Configuring the SAE
