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
- Configuring the PTSP Policer Instance (SRC CLI)
- Configuring PTSP Policies (SRC CLI)
- Before You Configure SRC Policies
- Configuring Forwarding Class Actions (SRC CLI)
- Before You Configure SRC Policies
- Configuring Forward Actions (SRC CLI)
- Configuring Forwarding Class Actions (C-Web Interface)
- Parameter Types
- Before You Configure SRC Policies
- Configuring Filter Actions (C-Web Interface)
- Configuring Junos OS Filter Conditions (SRC CLI)
- Parameter Types
- Configuring PTSP Policies (SRC CLI)
- Configuring PTSP Policy Lists (SRC CLI)
- Configuring the PTSP Policer Instance (SRC CLI)
- Configuring PTSP Policy Rules (SRC CLI)
- Configuring PTSP Classify-Traffic Conditions (SRC CLI)
Configuring PTSP Actions
Actions define the action taken on packets that match conditions in a policy rule. You create actions within policy rules.
Topics that discuss how to configure PTSP actions include:
- Configuring Policer-Ref Actions (SRC CLI)
- Configuring Forwarding Instance Actions (SRC CLI)
- Configuring Forwarding Class Actions (SRC CLI)
- Configuring Filter Actions (SRC CLI)
Configuring Policer-Ref Actions (SRC CLI)
Use this action to specify an action that references a PTSP policer instance. You can configure policer ref actions for PTSP policy rules. The policer instance can be shared by different service rules inside the same policy list. Multiple policy rules can reference the same policer instance, so that the traffic matched by those rules is policed by the same policer instance. If the policer instance is shared, all packets matching any of the service rules are policed together.
 | Note: For PTSP you must:
|
Use the following configuration statements to configure a policer-ref action:
policies group name list name rule name policer-ref {policer-ref policer-name ; description description ; }
To configure the policer-ref action:
- From configuration mode, access the statements for the
policer-ref action. user@host# edit policies group name list name rule name policer-ref
- Specify the name of the policer instance you want to reference. [edit policies group name list name rule name policer-ref] user@host# set policer–name
- Enter a description for the action. [edit policies group name list name rule name policer-ref] user@host# set description description
Configuring Forwarding Instance Actions (SRC CLI)
You can configure forwarding instance actions for routers running the PTSP feature. This action specifies a forwarding instance to assign to flows that match this policy.
| Note: For PTSP you must:
|
Use the following configuration statements to configure a forwarding instance action:
policies group name list name rule name forwarding-instance {forwarding-instance;forwarding-unit forwarding-unit ; description description ; }
To configure a forwarding instance action:
- From configuration mode, enter the forwarding instance
configuration. For example: user@host# edit policies group group1 list list1 rule rule1 forwarding-instance
- (Optional) Specify a forwarding instance to assign to
flows matching the policy. user@host# edit policies group group1 list list1 rule rule1 forwarding-instance “_same_”
Allowed values are __same__, or one of the forwarding instances configured on the router. The value __same__ forwards the flow in whatever forwarding instance it came in or is set from static configuration.
- (Optional) Specify a forwarding unit to assign to flows
matching this policy. Forwarding unit specifies the multiservice interface
unit number for forward flows to in order to reach the forwarding
instance specified by the attribute forwarding-instance. Note that
there is only a very loose coupling between this unit number and the
forwarding instance. The binding between them only happens with the
aid of additional router configuration.[edit policies group group1 list list1 rule rule1 forwarding-instance] user@host# set forwarding-unit forwarding-unit
Enter a value in the range 0–16384.
- (Optional) Enter a description for the forwarding instance
action. [edit policies group group1 list list1 rule rule1 forwarding-instance]user@host# set description description
- (Optional) Verify the forwarding instance action configuration.
[edit policies group bod list input rule pr forwarding-instance] user@host# show "'fi1'" forwarding-instance 1 description fi-sample
Configuring Forwarding Class Actions (SRC CLI)
You can configure forwarding class actions for Junos OS filter policy rules. The forwarding class action causes the router to assign a forwarding class to packets that match the associated classify-traffic condition.
The type of action that you can create depends on the type of policy rule. See Policy Information Model.
Use the following configuration statements to configure a forwarding class action:
policies group name list name rule name forwarding-class {forwarding-class; description description; }
To configure a forwarding class action:
- From configuration mode, enter the forwarding class action
configuration.user@host# edit policies group bod list input rule pr forwarding-class
- (Optional) Configure the name of the forwarding class
assigned to packets. [edit policies group bod list input rule pr forwarding-class]user@host# set forwarding-class
- (Optional) Enter a description for the forwarding class
action. [edit policies group bod list input rule pr forwarding-class]user@host# set description description
- (Optional) Verify the forwarding class action configuration.
[edit policies group bod list input rule pr forwarding-class] user@host# show forwarding-class fc_expedited; description "Expedited forwarding class";
Configuring Filter Actions (SRC CLI)
Use this action to discard packets. You can configure filter actions for Junos OS filters and JunosE policy rules. The type of action that you can create depends on the type of policy rule. See Policy Information Model.
Use the following configuration statement to configure a filter action:
policies group name list name rule name filter {description description ; }
To configure a filter action:
- From configuration mode, enter the filter action configuration.user@host# edit policies group junos_filter list in rule pr filter
- (Optional) Enter a description for the filter action. [edit policies group junos_filter list in rule pr filter]user@host# set description description
- (Optional) Verify the filter action configuration.
[edit policies group junos_filter list in rule pr filter] user@host# show description "Filter action for Junos OS policies";
Related Documentation
- Configuring PTSP Policies (SRC CLI)
- Configuring PTSP Policy Lists (SRC CLI)
- Configuring the PTSP Policer Instance (SRC CLI)
- Configuring PTSP Policy Rules (SRC CLI)
- Configuring PTSP Classify-Traffic Conditions (SRC CLI)
