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    
classify-traffic condition    
match direction, setting    
SRC CLI
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
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 policy changes    
Dynamic policy changes, managing
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

filter actions    
configuring    
SRC CLI
flexible RADIUS authentication plug-ins    
configuring
forwarding class actions    
configuring    
SRC CLI
 

G

Gx router driver    
application information, configuring    
SRC CLI
dynamic PCC rules, configuring    
SRC CLI
flow information, 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

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
JSRC    
JSRC and PTSP configuration example    
SRC CLI
Juniper Policy Server.     See JPS    
 

L

login process    
assigned IP subscribers, PCMM
 

M

manuals    
comments on
MX Series router as a PTSP network device    
MX Series router as a PTSP network device, adding    
SRC CLI
 

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 actions    
filter    
configuring, SRC CLI
forwarding class    
configuring, SRC CLI
forwarding instance    
configuring, SRC CLI
policy groups    
configuring    
SRC CLI
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
PTSP    
configuring    
SRC CLI
PTSP and JSRC configuration example    
SRC CLI
PTSP configuration example    
SRC CLI
PTSP policies, configuration statements    
SRC CLI
ssr-writer    
SRC CLI
PTSP actions    
PTSP actions, configuring    
SRC CLI    12
PTSP classify-traffic condition    
destination grouped network, configuring    
SRC CLI
destination network, configuring    
SRC CLI
protocol conditions with parameters, setting    
SRC CLI
protocol conditions with ports, setting    
SRC CLI
protocol conditions, setting    
SRC CLI
TCP conditions, setting    
SRC CLI
traffic match conditions, setting    
SRC CLI
PTSP classify-traffic conditions    
creating    
SRC CLI
PTSP classify-traffic conditions, configuring    
SRC CLI
PTSP device driver    
overview
PTSP device driver, configuring    
SRC CLI
PTSP on MX Series router    
PTSP on MX Series router, configuring    
SRC CLI
PTSP policer instance    
PTSP policer instance, configuring    
SRC CLI
PTSP policies    
PTSP policies, configuring    
SRC CLI
PTSP policy list    
PTSP policy list, configuring    
SRC CLI
PTSP policy rules    
network, specifying
PTSP policy rules, configuring    
SRC CLI
PTSP session store    
PTSP device driver session store, configuring    
SRC CLI
PTSP traffic match    
conditions, setting    
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 PTSP Classify-Traffic Conditions (SRC CLI)

Before you configure PTSP classify-traffic conditions, review the following topics:

  • Policy Management Overview
  • Policy Components
  • Policy Information Model

Topics that discuss configuring PTSP classify-traffic conditions include:

Creating PTSP Classify-Traffic Conditions (SRC CLI)

You create classify-traffic conditions within policy rules. Use the following configuration statements to create a classify-traffic condition:

policies group name list name rule name traffic-condition name {match-direction match-direction; description description;}

To add a classify-traffic condition:

  1. From configuration mode, create a classify-traffic condition inside a policy rule that has already been created and configured. For example, to create a traffic-condition called condition1 within policy rule rule1:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1
  2. (Optional) Specify the direction of the packet flow on which you want to match packets.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1]user@host# set match-direction match-direction

    Set to one of the following values:

    • input
    • output
    • both
    • Parameter of type matchDirection
  3. (Optional) Provide a description of the classify-traffic condition.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1]user@host# set description description
  4. (Optional) Verify your PTSP classify-traffic condition configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1]
    user@host# show 
    match-direction output;
    description "Destination classifier";

Configuring Destination Networks for PTSP Classify-Traffic Conditions (SRC CLI)

Use the following configuration statements to add destination networks to a PTSP classify-traffic condition:

policies group name list name rule name traffic-condition name destination-network network {ip-address ip-address; ip-mask ip-mask; }

To add a destination network to a PTSP classify-traffic condition:

  1. From configuration mode, enter the destination network within a classify-traffic condition. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network network
  2. (Optional) Specify the IP address of the destination network or host.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network network]user@host# set ip-address ip-address

    Where ip-address is one of the following values:

    • IP address
    • Predefined global parameter:
      • gateway_ipAddress—IP address of the gateway as specified by the service object.
      • interface_ipAddress—IP address of the router interface.
      • service_ipAddress—IP address of the service as specified by the service object.
      • user_ipAddress—IP address of the subscriber.
      • virtual_ipAddress—Virtual portal address of the SAE that is used in redundant redirect server installations.
    • Parameter of type address
  3. (Optional) Configure the IP mask of the destination network or host.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network network]user@host# set ip-mask ip-mask

    Where ip-mask is one of the following values:

    • IP address mask
    • Predefined global parameter:
      • interface_ ipMask—IP mask of the router interface.
      • service_ ipMask—IP mask of the service as specified by the service object.
      • user_ ipMask—IP mask of the subscriber.
    • Parameter of type address.
  4. (Optional) Verify your destination network configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network network]
    user@host# show 
    ip-address interface_ipAddress;
    ip-mask interface_ipMask;
    

Configuring Destination Grouped Networks for PTSP Classify-Traffic Conditions (SRC CLI)

Use the following configuration statements to add destination networks in a grouped format to a classify-traffic condition:

policies group name list name rule name traffic-condition name destination-network group-network {network-specifier network-specifier; }

To add a grouped destination network to a classify-traffic condition:

  1. From configuration mode, enter the destination network within a classify-traffic condition. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network group-network
  2. (Optional) Configure the IP address of the destination network or host.

    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network group-network]user@host# set network-specifier network-specifier
  3. (Optional) Verify your destination network configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 destination-network group-network] 
    user@host# show 
    network-specifier any;

Configuring Protocol Conditions for PTSP Classify-Traffic Conditions (SRC CLI)

The procedure in this topic shows how to configure protocol conditions that do not include port conditions.

Use the following configuration statements to add general protocol conditions to a PTSP classify-traffic condition:

policies group name list name rule name traffic-condition name protocol-condition {protocol protocol; }

To add general protocol conditions to a classify-traffic condition:

  1. From configuration mode, enter the general protocol condition configuration. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-condition
  2. Configure the protocol matched by this classify-traffic condition.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-condition]user@host# set protocol protocol

    Enter the protocol matched by this classifier list, one of the following values:

    • Predefined global parameter—Use a ? at the command line to see a list of valid protocols.
    • Protocol number in the range 0–255.
    • String expression.
    • Parameter of type protocol.
  3. (Optional) Verify your protocol condition configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-condition]
    user@host# show 
    protocol 0;
    

Configuring Protocol Conditions with Ports for PTSP Classify-Traffic Conditions (SRC CLI)

Use the following configuration statements to add general protocol conditions with ports to a PTSP classify-traffic condition:

policies group name list name rule name traffic-condition name protocol-port-condition {protocol protocol; }
policies group name list name rule name traffic-condition name protocol-port-condition destination-port port {from-port from-port; }
policies group name list name rule name traffic-condition name protocol-port-condition source-port port {from-port from-port; }

To add general protocol conditions with ports to a PTSP classify-traffic condition:

  1. From configuration mode, enter the protocol port condition configuration. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition
  2. Configure the protocol matched by this classify-traffic condition.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition]user@host# set protocol protocol

    UDP is the only valid value for PTSP.

  3. (Optional) Enter the destination port configuration for the protocol port configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition]user@host# edit destination-port
  4. (Optional) Configure the destination port.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition destination-port port]user@host# set from-port from-port

    Where from-port is one of the following values:

    • service_port—A predefined global parameter that is the port of the service as specified by the service object
    • Integer in the range 0–65535
    • Expression—A range of port numbers; for example, 10..20
    • Parameter of type port

    Use a range of ports to specify port numbers that are greater than or less than a specified port number. For example:

    • To set a range of ports that is greater than 10, use 11..65535.
    • To set a range of ports that is less than 200, use 0..199.
  5. (Optional) Enter the source port configuration for the protocol port configuration.
    user@host# up [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition]user@host# edit source-port
  6. (Optional) Configure the source port.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition source-port port]user@host# set from-port from-port[edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition source-port port]user@host# up

    Where from-port is one of the following values:

    • service_port—A predefined global parameter that is the port of the service as specified by the service object.
    • Integer in the range 0–65535
    • Expression—A range of port numbers; for example, 10..20.
    • Parameter of type port

    Use a range of ports to specify port numbers that are greater than or less than a specified port number. For example:

    • To set a range of ports that is greater than 10, use 11..65535.
    • To set a range of ports that is less than 200, use 0..199.
  7. (Optional) Verify your protocol condition configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 protocol-port-condition]
    user@host# show 
    protocol udp;
    destination-port { 
     port { 
            from-port service_port;
      }
    }
    source-port {
      port {
           from-port service_port;
      }
    }

Configuring Protocol Conditions with Parameters for PTSP Classify-Traffic Conditions (SRC CLI)

Use the following configuration statements to configure classify-traffic conditions that contain a parameter value for the protocol:

policies group name list name rule name traffic-condition name parameter-protocol-condition {protocol protocol; }
policies group name list name rule name traffic-condition name parameter-protocol-condition proto-attr destination-port port {from-port from-port; }
policies group name list name rule name traffic-condition name parameter-protocol-condition proto-attr source-port port {from-port from-port; }

To configure a protocol condition that contains a parameter value for the protocol:

  1. From configuration mode, enter the parameter protocol condition configuration. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition
  2. Assign a parameter as the protocol matched by this classify-traffic condition.

    Before you assign a parameter, you must create a parameter of type protocol and commit the parameter configuration.

    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition]user@host# set protocol protocol
  3. (Optional) Enter the protocol attribute configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition]user@host# edit proto-attr
  4. (Optional) Enter the destination port configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr]user@host# edit destination-port port
  5. (Optional) Configure the TCP or UDP destination port.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr destination-port port]user@host# set from-port from-port

    Where from-port is one of the following values:

    • service_port—A predefined global parameter that is the port of the service as specified by the service object.
    • Integer in the range 0–65535.
    • Expression—A range of port numbers; for example, 10..20.
    • Parameter of type port.

    Use a range of ports to specify port numbers that are greater than or less than a specified port number. For example:

    • To set a range of ports that is greater than 10, use 11..65535.
    • To set a range of ports that is less than 200, use 0..199.
  6. (Optional) Enter the source port configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr destination-port port]user@host# up [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr]user@host# edit source-port port
  7. (Optional) Configure the TCP or UDP source port.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr source-port port]user@host# set from-port from-port[edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr source-port port]user@host# up[edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr source-port]user@host# up[edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition proto-attr ]user@host# up

    Where from-port is one of the following values:

    • service_port—A predefined global parameter that is the port of the service as specified by the service object.
    • Integer in the range 0–65535.
    • Expression—A range of port numbers; for example, 10..20.
    • Parameter of type port.

    Use a range of ports to specify port numbers that are greater than or less than a specified port number. For example:

    • To set a range of ports that is greater than 10, use 11..65535.
    • To set a range of ports that is less than 200, use 0..199.
  8. (Optional) Verify the parameter protocol configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 parameter-protocol-condition]
    user@host# show 
    protocol protocol;
     destination-port {
        port {
          from-port service_port;
        }
      }
    }

Configuring TCP Conditions for PTSP Classify-Traffic Conditions (SRC CLI)

Use the following configuration statements to add TCP conditions to a PTSP classify-traffic condition:

policies group name list name rule name traffic-condition name tcp-condition {protocol tcp; }

Because the protocol is already set to TCP, do not change the protocol or protocol-operation options.

policies group name list name rule name traffic-condition name tcp-condition destination-port port {from-port from-port; }
policies group name list name rule name traffic-condition name tcp-condition source-port port {from-port from-port; }

To add TCP conditions to a PTSP classify-traffic condition:

  1. From configuration mode, enter the TCP configuration. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition
  2. (Optional) Enter the protocol for the TCP configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition]user@host# set protocol protocol

    For PTSP this is set to TCP.

  3. (Optional) Enter the destination port configuration for the TCP configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition]user@host# edit destination-port port
  4. (Optional) Configure the destination port.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition destination-port port]user@host# set from-port from-port

    Where from-port is one of the following values:

    • service_port—A predefined global parameter that is the port of the service as specified by the service object.
    • Integer in the range 0–65535.
    • Expression—A range of port numbers; for example, 10..20.
    • Parameter of type port.

    Use a range of ports to specify port numbers that are greater than or less than a specified port number. For example:

    • To set a range of ports that is greater than 10, use 11..65535.
    • To set a range of ports that is less than 200, use 0..199.
  5. (Optional) Enter the source port configuration for the TCP configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition source-port port]user@host# up [edit policies group group1 list list1 rule rule1 traffic-condition condition1]user@host# edit source-port port
  6. (Optional) Configure the source port.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition source-port port]user@host# set from-port from-port[edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition source-port port]user@host# up

    Where from-port is one of the following values:

    • service_port—A predefined global parameter that is the port of the service as specified by the service object.
    • Integer in the range 0–65535
    • Expression—A range of port numbers; for example, 10..20.
    • Parameter of type port

    Use a range of ports to specify port numbers that are greater than or less than a specified port number. For example:

    • To set a range of ports that is greater than 10, use 11..65535.
    • To set a range of ports that is less than 200, use 0..199.
  7. (Optional) Verify the TCP condition configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 tcp-condition]
    user@host# show 
    protocol tcp;
    protocol-operation is;
    destination-port {
     port {
            from-port service_port;
      }
    }
    source-port { 
      port { 
           from-port service_port;
      }
    }

Configuring Traffic Match Conditions for PTSP Classify-Traffic Conditions (SRC CLI)

Use the following configuration statements to configure traffic match conditions for PTSP classify traffic conditions.

policies group name list name rule name traffic-condition name traffic-match-condition {application [application...]; application-group [application-group...]; nested-application [nested-application...];term-precedence term-precedence;}

To add traffic match conditions to PTSP classify-traffic conditions:

  1. From configuration mode, enter the traffic condition configuration. For example:
    user@host# edit policies group group1 list list1 rule rule1 traffic-condition condition1 traffic-match-condition
  2. (Optional) Configure the application protocol to match.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 traffic-match-condition]user@host# set application [application...]
  3. (Optional) Configure a list of application groups to match for this policy.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 traffic-match-condition]user@host# set application-group [application-group...]
  4. (Optional) Configure a list of nested applications to match this policy.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 traffic-match-condition]user@host# set nested-application [nested-application...]

    Separate items in the list with commas.

  5. (Optional) Configure the term-precedence for this term in a given policy in relation to other terms. Lower precedence terms are searched first. Precedence matters only within the same class of policies, either dynamic or static. Terms with the same precedence may be evaluated in any order.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 traffic-match-condition]user@host# set term-precedence term-precedence

    Enter an integer in the range 1–254.

  6. (Optional) Verify the filter condition configuration.
    [edit policies group group1 list list1 rule rule1 traffic-condition condition1 traffic-match-condition]
    user@host# show 
    term—precedence 100;
    application—group group1;
    }

Modified: 2015-06-19