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
- Connections to Managed Devices
- Configuring the SAE to Manage PCMM Devices (C-Web Interface)
- Configuring CMTS-Specific RKS Plug-Ins (SRC CLI)
- Initially Configuring the SAE
Configuring the SAE to Manage PCMM Devices (SRC CLI)
The SAE connects to the PCMM device by using a COPS over TCP connection. The PCMM device driver controls this connection.
Use the following configuration statements to configure the SAE to manage CMTS devices:
shared sae configuration driver pcmm {keepalive-interval keepalive-interval ;
tcp-connection-timeout tcp-connection-timeout ;
application-manager-id application-manager-id ;
message-timeout message-timeout ;
cops-message-maximum-length cops-message-maximum-length ;
cops-message-read-buffer-size cops-message-read-buffer-size ;
cops-message-write-buffer-size cops-message-write-buffer-size ;
sae-community-manager sae-community-manager ;
disable-full-sync disable-full-sync ;
disable-pcmm-i03-policy disable-pcmm-i03-policy ;
session-recovery-retry-interval session-recovery-retry-interval ;
element-id element-id ;
default-rks-plug-in default-rks-plug-in ; }
tcp-connection-timeout tcp-connection-timeout ;
application-manager-id application-manager-id ;
message-timeout message-timeout ;
cops-message-maximum-length cops-message-maximum-length ;
cops-message-read-buffer-size cops-message-read-buffer-size ;
cops-message-write-buffer-size cops-message-write-buffer-size ;
sae-community-manager sae-community-manager ;
disable-full-sync disable-full-sync ;
disable-pcmm-i03-policy disable-pcmm-i03-policy ;
session-recovery-retry-interval session-recovery-retry-interval ;
element-id element-id ;
default-rks-plug-in default-rks-plug-in ; }
To configure the SAE to manage CMTS devices:
- From configuration mode, access the configuration statement
that configures the PCMM driver. In this sample procedure, the PCMM
device driver is configured in the west-region group. user@host# edit shared sae group west-region configuration driver pcmm
- Configure the interval between keepalive messages sent
from the COPS client (the PCMM device) to the COPS server (the SAE). [edit shared sae group west-region configuration driver pcmm] user@host# set keepalive-interval keepalive-interval
- Configure the timeout for opening a TCP connection to
the PCMM device.[edit shared sae group west-region configuration driver pcmm] user@host# set tcp-connection-timeout tcp-connection-timeout
- When this SAE is configured as the application manager,
configure the identifier of the application manager. [edit shared sae group west-region configuration driver pcmm] user@host# set application-manager-id application-manager-id
- Configure the time that the COPS server (the SAE) waits
for a response to COPS requests from the COPS client (the PCMM device).
Change this value only if a high number of COPS timeout events appear
in the error log. [edit shared sae group west-region configuration driver pcmm] user@host# set message-timeout message-timeout
- Configure the maximum length of a COPS message.[edit shared sae group west-region configuration driver pcmm] user@host# set cops-message-maximum-length cops-message-maximum-length
- Configure the buffer size for receiving COPS messages
from the COPS client. [edit shared sae group west-region configuration driver pcmm] user@host# set cops-message-read-buffer-size cops-message-read-buffer-size
- Configure the buffer size for sending COPS messages to
the COPS client.[edit shared sae group west-region configuration driver pcmm] user@host# set cops-message-write-buffer-size cops-message-write-buffer-size
- Configure the name of the community manager that manages
PCMM driver communities. Active SAEs are selected from this community. [edit shared sae group west-region configuration driver pcmm] user@host# set sae-community-manager sae-community-manager
- Enable or disable state synchronization with PCMM policy
servers. [edit shared sae group west-region configuration driver pcmm] user@host# set disable-full-sync disable-full-sync
- Enable or disable the SAE to send classifiers to the router
that comply with PCMM IO3. Disable this option if your network deployment
has CMTS devices that do not support PCMM IO3. [edit shared sae group west-region configuration driver pcmm] user@host# set disable-pcmm-i03-policy disable-pcmm-i03-policy
- Configure the time between attempts by the SAE to restore
service sessions that are being recovered in the background when state
synchronization completes with a state-data-incomplete error. [edit shared sae group west-region configuration driver pcmm] user@host# set session-recovery-retry-interval session-recovery-retry-interval
- (Optional) Configure the unique identifier that the SAE
uses to identify itself when it originates in record-keeping server
(RKS) events. [edit shared sae group west-region configuration driver pcmm] user@host# set element-id element-id
- (Optional) Specify the name of the default RKS plug-in
to which the SAE sends events for CMTS devices. [edit shared sae group west-region configuration driver pcmm] user@host# set default-rks-plug-in default-rks-plug-in
- (Optional) Verify your PCMM driver configuration.
[edit shared sae group west-region configuration driver pcmm] user@host# show keepalive-interval 45; tcp-connection-timeout 5; application-manager-id 1; message-timeout 120000; cops-message-maximum-length 204800; cops-message-read-buffer-size 3000; cops-message-write-buffer-size 3000; sae-community-manager PcmmCommunityManager; disable-full-sync true; disable-pcmm-i03-policy true; session-recovery-retry-interval 3600000; element-id 1; default-rks-plug-in rksTracking;
Related Documentation
- Using the SAE in a PCMM Environment
- Connections to Managed Devices
- Configuring the SAE to Manage PCMM Devices (C-Web Interface)
- Configuring CMTS-Specific RKS Plug-Ins (SRC CLI)
- Initially Configuring the SAE