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
Configuring the PTSP Device Driver Session Store (SRC CLI)
In most cases, all attributes have reasonable defaults and should not require configuration. The configuration should be changed only by advanced users wishing to tune the performance.
Use the following configuration statements to configure the PTSP device driver session storage configuration:
shared sae configuration driver junos-ptsp session-store
{ maximum-queue-age maximum-queue-age;maximum-queued-operations maximum-queued-operations;maximum-queue-size maximum-queue-size;maximum-file-size maximum-file-size;minimum-disk-space-usage minimum-disk-space-usage;rotation-batch-size rotation-batch-size;maximum-session-size maximum-session-size;disk-load-buffer-size disk-load-buffer-size;network-buffer-size network-buffer-size;retry-interval retry-interval;communications-timeout communications-timeout;load-timeout load-timeout;idle-timeout idle-timeout;maximum-backlog-ratio maximum-backlog-ratio;minimum-backlog minimum-backlog;}
To configure the PTSP device driver session storage:
- From configuration mode, access the statements for the
driver session storage. user@host# edit shared sae configuration driver junos-ptsp session-store
- (Optional) Specify the maximum age that a queue of buffered
store operations (such as adding a session to the store or removing
a session from the store) can reach before the queue is written to
a session store file.[edit shared sae configuration driver junos-ptsp session-store] user@host# set maximum-queue-age maximum-queue-age
Enter a value for the number of milliseconds in the range 0–2147483647. A value of –1 indicates that there is no limit. A value of 0 causes the session store to write each store operation to a session store file immediately.
- (Optional) Specify the number of buffered store operations
that are queued before the queue is written to a session store file.[edit shared sae configuration driver junos-ptsp session-store] user@host# set maximum-queued-operations maximum-queued-operations
Enter an integer in the range 0–2147483647. A value of –1 indicates that there is no limit. A value of 0 causes the session store to write each store operation to a session store file immediately.
- (Optional) Specify the maximum size that a queue of buffered
store operations can reach before the queue is written to a session
store file. [edit shared sae configuration driver junos-ptsp session-store] user@host# set maximum-queue-size maximum-queue-size
Enter the number of bytes in the range 0–2147483647.
- (Optional) Specify the maximum size of session store files.
When a file reaches this size, a new file is created. [edit shared sae configuration driver junos-ptsp session-store] user@host# set maximum-file-size maximum-file-size
Enter the number of bytes in the range 0–2147483647.
- (Optional) Specify the percentage of space in all session
store files that is used by live sessions. When the space in the session
store files that is used by live sessions decreases to this percentage,
the oldest session store file is compacted and appended to the newest
session store file, and then the oldest session store file is deleted. [edit shared sae configuration driver junos-ptsp session-store] user@host# set minimum-disk-space-usage minimum-disk-space-usage
Enter a percentage of disk space in the range 1–100. We recommend a range of 30-50.
- (Optional) Specify when the oldest session store file
is rotated. The value specifies the number of sessions that are rotated
from the oldest file to the newest file at the same time. While a
set of sessions is rotated, no other session store activity can take
place[edit shared sae configuration driver junos-ptsp session-store] user@host# set rotation-batch-size rotation-batch-size
Enter an integer in the range 0–2147483647.
- (Optional) Specify the maximum size of a single subscriber
or service session. Use this parameter to reserve memory for an internal
buffer. [edit shared sae configuration driver junos-ptsp session-store] user@host# set maximum-session-size maximum-session-size
Enter the number of bytes in the range 0–2147483647.
- (Optional) Specify the size of the buffer that is used
to load all of a session store's files from disk at startup. [edit shared sae configuration driver junos-ptsp session-store] user@host# set disk-load-buffer-size disk-load-buffer-size
Enter the number of bytes in the range 0–2147483647.
- (Optional) Specify the size of the buffer that holds messages
or message segments that are waiting to be sent to passive session
stores.[edit shared sae configuration driver junos-ptsp session-store] user@host# set network-buffer-size network-buffer-size
The number of bytes entered must be larger than or equal to 21 plus maximum-session-size and less than 2147483647.
- (Optional) Specify the time interval to be allowed between
attempts by the active session store to connect to missing passive
session stores. [edit shared sae configuration driver junos-ptsp session-store] user@host# set retry-interval retry-interval
Enter the number of milliseconds in the range 0–2147483647.
- (Optional) Specify the amount of time in milliseconds
that a session store should wait before closing when it is blocked
from reading or writing a message. This timeout does not apply when
a session store is waiting for a remote session store to load its
state from disk. [edit shared sae configuration driver junos-ptsp session-store] user@host# set communications-timeout communications-timeout
Enter the number of milliseconds. (A nonpositive number means wait forever. This is not recommended.)
- (Optional) Specify the amount of time in milliseconds
that an active session store should wait for a passive session store
or a passive session store waits for an active session store to load
its data from disk before it closes the connection to the session
store. [edit shared sae configuration driver junos-ptsp session-store] user@host# set load-timeout load-timeout
Enter the number of milliseconds. (A nonpositive number means wait forever. This is not recommended.)
- (Optional) Specify the amount of time that a passive session
store waits for activity from the active session store before it closes
the connection to the active session store. This timeout applies after
the session store startup and initial update processes are complete. [edit shared sae configuration driver junos-ptsp session-store] user@host# set idle-timeout idle-timeout
Enter the number of milliseconds in the range 0–2147483647.
- (Optional) Specify the maximum backlog ratio. Along with
the minimum backlog size, this ratio specifies when the active session
store closes the connection to a passive session store because of
a backlog of messages waiting to be sent. After the startup and initial
update processes are complete, if the backlog becomes too large, the
connection to the passive session store is closed. After the retry
interval ends, a new connection is opened.
If the backlog of unsent operations (in bytes) divided by the total size (in bytes) of all live store operations is greater than this number, the connection is closed.
[edit shared sae configuration driver junos-ptsp session-store] user@host# set maximum-backlog-ratio maximum-backlog-ratioEnter a floating point number.
- (Optional) Specify the size of the minimum backlog. Along
with the maximum backlog ratio, this number specifies when the active
session store closes the connection to a passive session store because
of a backlog of messages waiting to be sent to the passive session
store. After the startup and initial update processes are complete,
if the backlog becomes too large, the connection to the passive session
store is closed. After the retry interval ends, a new connection is
opened. If the maximum backlog ratio is met, the active session store
does not close the connection unless the backlog of messages (in bytes)
is greater than this number.[edit shared sae configuration driver junos-ptsp session-store] user@host# set minimum-backlog minimum-backlog
Enter the number of bytes in the range 0–2147483647.
