Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

 A  C  D  E  F  G  I  J  L  M  N  P  Q  R  S  T  W

 

A

address pools    
assigned IP subscribers    
configuring
address pools.     See IP address pools    
application manager    
role, in PCMM environment
assigned IP subscribers    
PCMM network    12
address pools
IP address pools
setting timeouts
voice over IP
 

C

cable modem termination system.     See CMTS devices    
client type 1, PCMM
client type 2, PCMM
CMTS devices    
adding objects to directory    
SRC CLI
adding virtual router objects to directory    
SRC CLI
configuration statements    12
role
CMTS locator    
monitoring    
C-Web interface
SRC CLI
COA script services, configuring
configuration wizard    
fair usage    
configuration overview
running
running    12
configuration wizards    
fair usage    
overview
overview    12
conventions    
notice icons
text
custom RADIUS authentication plug-ins
customer support    1
contacting JTAC
 

D

Data over Cable Service Interface Specifications.     See DOCSIS protocol    
Diameter    
peers    
configuring    12
SNMP support
Diameter server    
clients, viewing    
SRC CLI
message flows, viewing    
SRC CLI
message handler, viewing    
SRC CLI
monitoring    
SRC CLI
peers, viewing    
SRC CLI
server process, viewing    
SRC CLI
server requests, viewing    
SRC CLI
statistics, viewing    
SRC CLI
status, viewing    
SRC CLI
DOCSIS protocol
documentation    
comments on
domains    
IP service edge
IP subscriber edge
radio frequency
dynamic RADIUS authorization requests    
RADIUS packets, defining    12
 

E

end-to-end services
event notification, PCMM network    
configuration statements
description
properties, configuring    
SRC CLI
 

F

flexible RADIUS authentication plug-ins    
configuring
 

G

Gx router driver    
application information, configuring    
SRC CLI
dynamic PCC rules, configuring    
SRC CLI
flow information, configuring    
SRC CLI
Gx policies for dynamic PCC rules, configuring    
SRC CLI
Gx policies for static PCC rules, configuring    
SRC CLI
overview
policies, configuration statements    
SRC CLI
policies, configuring    
SRC CLI
policy list, configuring    
SRC CLI
QoS information, configuring    
SRC CLI
redirect information, configuring    
SRC CLI
static PCC rules, configuring    
SRC CLI
steering information, configuring    
SRC CLI
 

I

intelligent-service-edge device driver    
configuring initialization scripts    
SRC CLI
IP address pools    
assigned IP subscribers
assigned IP subscribers, configuring    
SRC CLI
local address pools, configuring    
SRC CLI
static pools, configuring    
SRC CLI
 

J

JPS (Juniper Policy Server)    
application manager-to-policy server interface, configuring
application manager-to-policy server interface, monitoring    
C-Web interface    12
SRC CLI
architecture
CMTS devices, monitoring    
C-Web interface
CMTS locator, monitoring    
C-Web interface
SRC CLI
JPS state, monitoring
logging, configuring
logging, modifying
message flows, monitoring    
C-Web interface
SRC CLI
message handler, monitoring    
C-Web interface
SRC CLI
monitoring    
C-Web interface
SRC CLI    12
operational status
overview
policy server-to-CMTS interface, configuring
policy server-to-CMTS interface, monitoring    
C-Web interface    12
SRC CLI
policy server-to-RKS interface, configuring
policy server-to-RKS interface, monitoring    
C-Web interface
SRC CLI
server process, monitoring    
C-Web interface
SRC CLI
starting    
SRC CLI
stopping    
SRC CLI
subscriber address mappings, configuring
subscriber configuration, modifying
Juniper Policy Server.     See JPS    
 

L

login process    
assigned IP subscribers, PCMM
 

M

manuals    
comments on
 

N

NIC (network information collector)    
IP address pools, configuring    
SRC CLI
notice icons
 

P

packet mirroring, configuring
PCMM (PacketCable Multimedia)    
application manager, role
client type 1
client type 2
CMTS device, role
configuring SAE    
SRC CLI
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    
assigned IP method
overview
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    
description
traffic profiles
video-on-demand example
videoconferencing example
PCMM device driver    
configuration statements
configuring    
SRC CLI
PCMM record-keeping server plug-in    
configuration statements
configuring    
SRC CLI
description
plug-ins    
PCMM record-keeping server plug-in
policy servers    
adding application manager groups    
SRC CLI
adding objects to directory    
SRC CLI
role, in PCMM architecture
specifying application managers    
SRC CLI
specifying SAE communities    
SRC CLI
 

Q

QoS (quality of service)    
PCMM environments    
end-to-end QoS architecture
extending to service edge domain
extending to subscriber edge domain
searching for policies in directory
QoS profile-tracking plug-in    
description
QoS profiles, routers running JunosE Software    
how tracking works
managing dynamically
updating directory, using    
qosProfilePublish
quality of service.     See QoS    
 

R

RADIUS    
vendor-specific attributes for wireless ISP roaming
record-keeping server.     See RKS    
RKS (record-keeping server)    
peers, configuration statements
peers, configuring in plug-ins    
SRC CLI
plug-in
plug-in, configuration statements
plug-in, configuring    
SRC CLI
role in PCMM environment
roaming wireless environment
 

S

SAE (service activation engine)    
configuring as an application manager    
SRC CLI
PCMM environment
redundancy.     See SAE communities    
SAE (service activation engine), configuring    
community manager    
SRC CLI
event notification API properties    
SRC CLI
PCMM device driver    
SRC CLI    12
SAE communities    
configuration overview    
SRC CLI
configuration statements
configuring manager    
SRC CLI
defining members    
SRC CLI
description
service flows
services    
voice over IP (VoIP)
session store    
in PCMM environment
single phase resource reservation model, PCMM
subscriber    
wireless environment
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
traffic policies, PCMM
 

W

wireless environment

Related Documentation

Configuring Connections to RKSs (SRC CLI)

  1. Specifying Connections to RKSs (SRC CLI)
  2. Configuring RKS Pairs (SRC CLI)

Specifying Connections to RKSs (SRC CLI)

To configure the policy server-to-RKS interface (PKT-MM4) so that policy events can be sent to the RKS, you can configure RKS pairs (see Configuring RKS Pairs (SRC CLI)) and their associated application managers (see Configuring RKS Pairs for Associated Application Managers (SRC CLI)).

Use the following configuration statement to configure the policy server-to-RKS interface:

slot number jps rks-interface { element-id element-id; local-address local-address; local-port local-port; retry-interval retry-interval; local-timeout local-timeout; mso-data mso-data; mso-domain-name mso-domain-name; default-rks-pair default-rks-pair; pending-rks-event-max-size pending-rks-event-max-size; pending-rks-event-max-age pending-rks-event-max-age; held-decs-max-size held-decs-max-size; held-decs-max-age held-decs-max-age; bcid-cache-size bcid-cache-size; bcid-cache-age bcid-cache-age; use-default-when-am-requests-unconfigured-rks; }

To configure the policy server-to-RKS interface:

  1. From configuration mode, access the configuration statement that configures the policy server-to-RKS interface.
    user@host# edit slot 0 jps rks-interface
  2. ier for RKS event origin.
    [edit slot 0 jps rks-interface] user@host# set element-id element-id
  3. (Optional) Specify the source IP address that the plug-in uses to communicate with the RKS.
    [edit slot 0 jps rks-interface] user@host# set local-address local-address

    If no value is specified and there is more than one local address, the JPS randomly selects a local address to be used as the source address.

  4. (Optional) Specify the source UDP port or a pool of ports that the plug-in uses to communicate with the RKS.
    [edit slot 0 jps rks-interface] user@host# set local-port local-port
  5. (Optional) Specify the time the JPS waits for a response from an RKS before it resends the packet.
    [edit slot 0 jps rks-interface] user@host# set retry-interval retry-interval

    The JPS keeps sending packets until either the RKS acknowledges the packet or the maximum timeout is reached.

  6. (Optional) Specify the maximum time the JPS waits for a response from an RKS.
    [edit slot 0 jps rks-interface] user@host# set local-timeout local-timeout
  7. (Optional) Specify the MSO-defined data in the financial entity ID (FEID) attribute, which is included in event messages.
    [edit slot 0 jps rks-interface] user@host# set mso-data mso-data
  8. (Optional) Specify the MSO domain name in the FEID attribute that uniquely identifies the MSO for billing and settlement purposes.
    [edit slot 0 jps rks-interface] user@host# set mso-domain-name mso-domain-name
  9. (Optional) Specify the default RKS pair that the JPS uses unless an RKS pair is configured for a given application manager.
    [edit slot 0 jps rks-interface] user@host# set default-rks-pair default-rks-pair
  10. (Optional) Specify the maximum number of RKS events waiting for Gate-Set-Ack, Gate-Set-Err, Gate-Del-Ack, and Gate-Del-Err messages.
    [edit slot 0 jps rks-interface] user@host# set pending-rks-event-max-size pending-rks-event-max-size
  11. (Optional) Specify the oldest age of RKS events waiting for Gate-Set-Ack, Gate-Set-Err, Gate-Del-Ack, and Gate-Del-Err messages.
    [edit slot 0 jps rks-interface] user@host# set pending-rks-event-max-age pending-rks-event-max-age

    The maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.

  12. (Optional) Specify the maximum number of outstanding Gate-Info requests.
    [edit slot 0 jps rks-interface] user@host# set held-decs-max-size held-decs-max-size
  13. (Optional) Specify the oldest age of outstanding Gate-Info requests.
    [edit slot 0 jps rks-interface] user@host# set held-decs-max-age held-decs-max-age

    The maximum age must be greater than sent-message-timeout of the corresponding CMTS interface.

  14. (Optional) Specify the size of billing correlation ID (BCID) cache.
    [edit slot 0 jps rks-interface] user@host# set bcid-cache-size bcid-cache-size
  15. (Optional) Specify the oldest age of billing correlation ID (BCID) in cache.
    [edit slot 0 jps rks-interface] user@host# set bcid-cache-age bcid-cache-age
  16. (Optional) Specify whether the default RKS pair is used when an application manager requests the use of an unconfigured RKS pair.
    [edit slot 0 jps rks-interface] user@host# set use-default-when-am-requests-unconfigured-rks
  17. (Optional) Verify your configuration.
    [edit slot 0 jps rks-interface] 
    user@host# show 

Configuring RKS Pairs (SRC CLI)

By default, the JPS has four RKS pairs. All parameters that share the same RKS pair name configure the connection to that RKS pair. Any configured RKS pair can be used as the value for the default RKS pair or the RKS pair associated with a specific application manager.

Note: When running more than one JPS in a group to provide redundancy, all the JPSs in that group must have same RKS pair configuration (including the default RKS pair and any configured RKS pairs associated with a specific application manager).

Use the following configuration statement to configure the RKS pair:

slot number jps rks-interface rks-pair rks-pair-name { primary-address primary-address; primary-port primary-port; secondary-address secondary-address; secondary-port secondary-port; }

To configure the RKS pair:

  1. From configuration mode, access the configuration statement that configures the RKS pair. In this sample procedure, the RKS pair called pair1 is configured.
    user@host# edit slot 0 jps rks-interface rks-pair pair1
  2. Specify the IP address of the primary RKS for this RKS pair.
    [edit slot 0 jps rks-interface rks-pair pair1] user@host# set primary-address primary-address

    If no value is specified, the RKS pair is not defined.

  3. (Optional) Specify the UDP port on the primary RKS to which the JPS sends events.
    [edit slot 0 jps rks-interface rks-pair pair1] user@host# set primary-port primary-port
  4. (Optional) Specify the IP address of the secondary RKS for this RKS pair.
    [edit slot 0 jps rks-interface rks-pair pair1] user@host# set secondary-address secondary-address
  5. (Optional) Specify the UDP port on the secondary RKS to which the JPS sends events.
    [edit slot 0 jps rks-interface rks-pair pair1] user@host# set secondary-port secondary-port
  6. (Optional) Verify your configuration.
    [edit slot 0 jps rks-interface rks-pair pair1] 
    user@host# show 
    primary-address ;
    primary-port 1813;
    secondary-address ;
    secondary-port 1813;

Related Documentation

Modified: 2016-05-27