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
- 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
- peers
- SNMP support
- Diameter server
- DOCSIS protocol
- documentation
- domains
- dynamic RADIUS authorization requests
E
- end-to-end services
- event notification, PCMM network
- configuration statements
- description
- properties, configuring
F
- flexible RADIUS authentication plug-ins
G
- Gx router driver
- application information, configuring
- dynamic PCC rules, configuring
- flow information, configuring
- Gx policies for dynamic PCC rules, configuring
- Gx policies for static PCC rules, configuring
- overview
- policies, configuration statements
- policies, configuring
- policy list, configuring
- QoS information, configuring
- redirect information, configuring
- static PCC rules, configuring
- steering information, configuring
I
- intelligent-service-edge device driver
- configuring initialization scripts
- 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
- Juniper Policy Server. See JPS
L
- login process
M
- manuals
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 servers
- adding application manager groups
- adding objects to directory
- role, in PCMM architecture
- specifying application managers
- specifying SAE communities
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 RKS Pairs (C-Web Interface)
- Configuring Connections to RKSs (SRC CLI)
Configuring RKS Pairs for Associated Application Managers (SRC CLI)
By default, the JPS has four associated application managers. All parameters that share the same application manager name configure the RKS pair to which events associated with a specific application manager are sent.
Use the following configuration statement to configure the associated application manager:
To configure the associated application manager:
- From configuration mode, access the configuration statement
that configures the RKS pair for the associated application manager.
In this sample procedure, the application manager name called 1 is
configured. user@host# edit slot 0 jps rks-interface am 1
- Specify the identifier of the application manager. [edit slot 0 jps rks-interface am 1] user@host# set am-id am-id
If no value is specified, the RKS pair configuration is not defined for this application manager. If you must set trusted to true without defining the RKS pair configuration, you must specify a value for am-id and not specify a value for rks-pair-name.
- (Optional) Specify the RKS pair that the JPS will send
events to when those events are triggered by gate transitions associated
with the application manager specified by am-id with the same application
manager name (am-name). [edit slot 0 jps rks-interface am 1] user@host# set rks-pair rks-pair-name
If no value is specified, the RKS pair configuration is not defined for this application manager. Use when you must set trusted to true without defining the RKS pair configuration.
- (Optional) Specify whether this application manager is
a trusted network element to the JPS. [edit slot 0 jps rks-interface am 1] user@host# set trusted
- (Optional) Verify your configuration.
[edit slot 0 jps rks-interface am 1] user@host# show
Related Documentation
- Configuring RKS Pairs (C-Web Interface)
- Configuring Connections to RKSs (SRC CLI)