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  H  I  J  L  M  N  O  P  Q  R  S  T  U  V

 

A

access policy, examples    1
DHCP    
SRC CLI
PPP    
SRC CLI
action threshold, service schedules    
overview
setting    
SRC CLI
actions.     See policy actions    
aggregate services    1
adding    
SRC CLI
before you configure    
SRC CLI
fragment services
infrastructure services
mandatory services
Python expressions
redundancy
sessions    1
activation
attributes
deactivation
modification
monitoring
timers, configuring    
SRC CLI
apply-groups statement, routers running Junos OS
 

C

captive portal    
using with next-hop action    
SRC CLI
classify-traffic condition    1
application protocol    
defining, SRC CLI
map expressions, SRC CLI
application, setting    
SRC CLI
application-group, setting    
SRC CLI
configuring    
SRC CLI
destination grouped network, configuring    
SRC CLI
destination network, configuring    
SRC CLI
expanded classifiers    1
configuring, SRC CLI
extended classifiers    1
configuring, SRC CLI
ICMP conditions, setting    
SRC CLI
IGMP conditions, setting    
SRC CLI
IPSec conditions, setting    
SRC CLI
Junos OS filter conditions, setting    
SRC CLI
JunosE secondary input policy conditions, setting    
SRC CLI
match direction, setting    
SRC CLI    12
multiple classifiers
packet length, setting    
SRC CLI
PCMM I02 and I03    1
configuring, SRC CLI
port definitions, overview    
SRC CLI
protocol conditions with parameters, setting    
SRC CLI
protocol conditions with ports, setting    
SRC CLI
protocol conditions, setting    
SRC CLI
route class, configuring    
SRC CLI
source grouped network, configuring    
SRC CLI
source network, setting    
SRC CLI
TCP conditions, setting    
SRC CLI
term-precedence, setting    
SRC CLI
ToS byte conditions, setting    
SRC CLI
color actions    1
configuring    
SRC CLI
color mark actions    12
controlled load service, FlowSpec
conventions    
notice icons
text
CoS (class of service)    
ToS byte, setting    
SRC CLI
customer support    1
contacting JTAC
 

D

Data-over-Cable Service Interface Specifications.     See DOCSIS    
default policies    
example    
SRC CLI
DHCP (Dynamic Host Configuration Protocol)    
access policy example    
SRC CLI
Differentiated Services code point, ToS byte    
SRC CLI
DOCSIS policy actions    1
configuring    
SRC CLI
documentation    
comments on
drop profile maps    
configuring    
SRC CLI
drop probability, setting    
SRC CLI
fill level, setting    
SRC CLI
DSCP (Differentiated Services code point), ToS byte    
SRC CLI
 

E

effective period, service schedules
exclusions to service schedule    1
defining    
SRC CLI
expanded classifiers    1
configuring    
SRC CLI
expressions    
map, application protocol conditions    
SRC CLI
parameter definitions
extended classifiers, PCMM    1
configuring    
SRC CLI
external parent groups    
JunosE    
overview    12
external parent groups,    
aggregate rate-limit    
configuring
configuration statements
for JunosE policies    
configuration statements
configuring
hierarchical policy parameter    
configuring
JunosE    
creating
rate-limit profiles    
configuring
 

F

filter actions    1
configuring    
SRC CLI
FlowSpec actions    1
configuring    
SRC CLI
forward actions    1
configuring    
SRC CLI
forwarding class actions    1
configuring    
SRC CLI
fragment services    1
configuring    
SRC CLI
 

G

gates, PCMM
gateSpec actions    1
configuring    
SRC CLI
global parameters    1
configuring    
SRC CLI
predefined    1
viewing with SRC CLI
runtime
types
guaranteed service, FlowSpec
 

H

hierarchical policies    
overview    
1
hierarchical rate-limiting    
JunosE    
1
 

I

infrastructure services    123
 

J

Junos OS ASP policy rules    1
NAT actions    1
configuring, SRC CLI
network, specifying    1
SRC CLI    12
stateful firewall actions, configuring    
SRC CLI
Junos OS filter policy rules    1
conditions, setting    
SRC CLI
Junos OS policer policy rules    1
policer actions    1
configuring, SRC CLI
Junos OS port mirror policy rules    
traffic mirror actions
Junos OS scheduler policy rules    12,  See also drop profile maps    
actions    1
configuring, SRC CLI
QoS conditions, configuring    
SRC CLI
Junos OS shaping policy rules
JunosE IPv6 policy rules    
network, specifying    
SRC CLI    12
JunosE secondary input policy rules    
conditions, setting    
SRC CLI
 

L

local parameters    1
configuring    
SRC CLI
types
loss priority actions    1
configuring    
SRC CLI
 

M

manuals    
comments on
map expressions    
application protocol conditions    
SRC CLI
substitutions
mark actions    1
configuring    
SRC CLI
multiple classifiers, policies
multitask
mutex group    1
adding    
SRC CLI
 

N

NAT (Network Address Translation) policies    
actions    1
configuring, SRC CLI
application protocol condition    
defining, SRC CLI
map expressions, SRC CLI
next-hop actions    1
captive portal feature    
SRC CLI
configuring    
SRC CLI
next-interface actions    1
configuring    
SRC CLI
next-rule actions    1
configuring    
SRC CLI
non-real-time polling service.
notice icons
NRTPS (non-real-time polling service)
 

O

operators in substitution expressions
 

P

packet loss priority.     See loss priority actions    
PacketCable Multimedia Specifications.     See PCMM    
parameter names    
substitutions
parameter value acquisition    12,  See also substitutions    
example
multiple subscriptions
single subscriptions
parameter values, setting in services
parameters    1,  See also substitutions    
defining
definition
fixing
global.     See global parameters    
local.     See local parameters    
ranking sources
runtime.     See runtime parameters    
types
parent groups    12345
PCMM policies    
classifiers
client type 1 support
conditions and actions supported
DOCSIS parameters    1
configuring, SRC CLI
extended classifiers    1
configuring, SRC CLI
FlowSpec parameters    
configuring, SRC CLI
controlled load service
guaranteed service
request specification (RSpec)
traffic specification (TSpec)
gate
gateSpec parameters, configuring    
SRC CLI
I02 and I03 classifiers
marking packets
proxied QoS with policy push
service class name    
configuring, SRC CLI
service flow scheduling types
SessionClassId
traffic profiles
permanent service    1
configuring    
SRC CLI
plug-ins    
authorization
policer actions    1
configuring    
SRC CLI
policies    
defining parameters in repository
policing policies    
example    
SRC CLI
policy actions    1
color    1
configuring, SRC CLI
color mark    12
combining
configuring
DOCSIS    1
configuring, SRC CLI
dynamic profiles    
configuring, SRC CLI
filter    1
configuring, SRC CLI
FlowSpec    1
configuring, SRC CLI
forward    1
configuring, SRC CLI
forwarding class    1
configuring, SRC CLI
gateSpec    1
configuring, SRC CLI
loss priority    1
configuring, SRC CLI
mark    1
configuring, SRC CLI
NAT    1
configuring, SRC CLI
next hop    1
configuring, SRC CLI
next interface    1
configuring, SRC CLI
next rule    1
configuring, SRC CLI
policer    1
configuring, SRC CLI
policy rules supported
QoS profile attachment    1
configuring, SRC CLI
rate limit    1
configuring, SRC CLI
rate limit hierarchy    
overview
parent-group reference, SRC CLI
rate limit types    
configuring, SRC CLI
rate-limit hierarchy    
configuring, SRC CLI    12
reject    1
configuring, SRC CLI
routing instance    1
configuring, SRC CLI
scheduler    1
configuring, SRC CLI
service class name    1
configuring, SRC CLI
stateful firewall    1
configuring, SRC CLI
template activation    
configuring, SRC CLI
traffic class    1
configuring, SRC CLI
traffic mirror    1
configuring, SRC CLI
traffic-shape    1
configuring, SRC CLI
types
user packet class    1
configuring, SRC CLI
policy components    1
policy decision point, description
Policy Editor
policy enforcement point, description
policy engine
policy repository
policy conditions    12,  See also classify-traffic condition    
policy rules supported
types
policy engine
policy examples    
access policy    
SRC CLI
premium service    
SRC CLI
tiered Internet service    
SRC CLI
policy folders    1
configuring    
SRC CLI
policy groups    1
configuring    
SRC CLI
policy lists    1
configuring    
SRC CLI
policy management    
bandwidth management
overview
packet logging
packet mirroring
packet tagging
policy routing
QoS classification and marking
RADIUS support
security
policy objects    
organization
policy overview    
actions.     See policy actions    
conditions.     See classify-traffic condition\    
policy object organization
policy repository, description
policy rules    1
actions supported
conditions supported
configuring    
SRC CLI
Junos Adaptive Services PIC (ASP).     See Junos OS ASP policy rules    
Junos OS filter.     See Junos OS filter policy rules    
Junos OS policer.     See Junos OS policer policy rules    
Junos OS scheduler.     See Junos OS scheduler policy rules    
Junos OS shaping.     See Junos OS shaping policy rules    
precedence    
SRC CLI
types
PPP    
access policy example    
SRC CLI
precedence    
policy rules    
SRC CLI
premium service, example    
SRC CLI
preparation time, service schedules    
overview
setting    
SRC CLI
proxied QoS with policy push
 

Q

QoS (quality of service)    
condition    1
configuring, SRC CLI
PCMM cable networks.     See PCMM policies    
QoS parameters, configuring    
SRC CLI
QoS profile attachment actions    1
configuring, SRC CLI
QoS profile, configuring    
SRC CLI
QoS condition    12
 

R

rate-limit actions    1
configuring    
SRC CLI
example    
SRC CLI
rate-limit hierarchy actions    
configuring    
SRC CLI    12
overview
rate-limit type actions    
configuring    
SRC CLI
rate-limiting, with multiple classifiers
real-time polling service.     See RTPS    
reject actions    1
configuring    
SRC CLI
routers running Junos OS    
policy features    
rate-shaping
routing instance actions    1
configuring    
SRC CLI
RTPS (real-time polling service)    1
configuring    1
SRC CLI
runtime parameters    
viewing with SRC CLI
 

S

scheduleAuth plug-in
scheduler actions    12,  See also drop profile maps    
configuring    
SRC CLI
scopes.     See service scopes    
script services    1
adding    
SRC CLI
example    
ScriptService SPI in Java
ScriptService SPI in Jython
ScriptService interface
service    
3gpp attributes (Gx router driver)    
configuring, SRC CLI
Gx service attributes    
configuring, SRC CLI
service class name actions    1
configuring    
SRC CLI
service flow scheduling types
service schedules    
action threshold, setting    
SRC CLI
authorization schedules, configuring    
SRC CLI
configuring    
SRC CLI
examples    
SRC CLI    1234
exclusions, defining    
SRC CLI
guidelines
overview    1
action threshold
authorization schedules
configuring
effective period
event-based schedules
exclusions
one-time events
preparation time
recurring events
state-based schedules
planning
preparation time, setting    
SRC CLI
weekly-recur-freq
service scopes    12
adding    
SRC CLI
assigning services    
SRC CLI
assigning subscribers    
SRC CLI
assigning VRs    
SRC CLI
configuring    
SRC CLI
example    
SRC CLI
multiple scopes, defining    
SCR CLI
service-mgm-schedules-nonwork
services    
activate-only
adding aggregate    
SRC CLI
adding infrastructure    
SRC CLI
adding normal    
SRC CLI
adding script services    
SRC CLI
aggregate.     See aggregate services    
assigning to service scopes    
SRC CLI
automatic activation
infrastructure.     See infrastructure services    
mutually exclusive
overview
premium service example    
SRC CLI
restricting availability
restricting simultaneous activation
script.     See script services    
setting parameter values
tiered Internet example    
SRC CLI
SessionClassId, PCMM policies
shaping rate.     See traffic shaping    
stateful firewall policies    
actions    1
configuring, SRC CLI
application protocol conditions    
defining, SRC CLI
map expressions, SRC CLI
substitutions    1,  See also parameters    
aggregate services, configuring
comments    1
adding
definition
exceptions, raising
expressions    12
IPv4 addresses
keywords
lists, formatting
maps, formatting
numbers, formatting
operators
parameter names, specifying
ranges
separators
strings, formatting
subordinate expressions
syntax
formatting
map expressions
mathematical expressions
parameter names
validation
support, technical     See technical support    
 

T

technical support    
contacting JTAC
template activation actions    
configuring    
SRC CLI
text conventions defined
tiered Internet service, example    
SRC CLI
traffic mirror actions    1
configuring    
SRC CLI
traffic profiles, PCMM policies
traffic shape actions    
configuring    
SRC CLI
traffic shaping    
actions
policy rules
traffic-class actions    1
configuring    
SRC CLI
traffic-shape actions
 

U

UGS (unsolicited grant service)    1
configuring    
SRC CLI
UGS-AD (unsolicited grant service with activity detection)    1
configuring    
SRC CLI
unsolicited grant service.     See UGS    
unsolicited grant with activity detection.     See UGS-AD    
user packet class actions    1
configuring    
SRC CLI
 

V

validating    
substitutions
value acquisition for parameters    
multiple subscriptions
single subscriptions

Related Documentation

Policy Information Model

Policies are made up of conditions and actions that cause the router to handle packets in a certain way.

  • Condition—Defines values or fields that a packet must contain before an action is triggered; for example, packet direction, network protocol, source and destination ports, application protocol, source and destination networks, packet length, forwarding class, source and destination class
  • Action—Specifies the action that the router takes on packets that match the condition; for example, filter (drop), forward, send to next interface, apply rate and burst size limits, assign a forwarding class

Here are two examples of policies with conditions and actions:

  • A stateful firewall:
    • Condition—Matches input packets to a specific destination network
    • Action—Forwards matching packets
  • Controlled access policy that defines the sites that a subscriber can view:
    • Condition—Traffic to and from the restricted site
    • Action—Access to the site is stopped if the site has a restricted rating

The SRC policy information model is designed to consolidate information models from various devices to provide a standard way to configure policies. This way, similar operations on different devices are represented as a single policy action or condition that is translated to device-specific operations. For example, the SRC policy information model provides an action that forwards traffic. This action is translated into actions such as forward, accept, or simple handoff on various routers. For instances in which policy conditions or actions are significantly different, the model provides support for each type of condition or action. For example, because rate-limiting on routers running JunosE Software is significantly different than policing on routers running Junos OS, the SRC software provides a rate-limit action for routers running JunosE Software and policer action for routers running Junos OS.

For routers running JunosE Software, SRC policies are translated at the COPS-PR or COPS-XDR level, and at the router level. For routers running Junos OS, policies are translated at the Junos XML on BEEP level and at the router level.

The SRC policy model also lets you simplify policy configuration for policy conditions that classify traffic. For JunosE and PCMM policies, you can combine different conditions that classify traffic and configure these conditions to use a single action. In addition for JunosE policies, you can create a condition which actually represents a number of classifiers. The SAE expands the classifier to multiple classifiers before installing them on the router. For routers running JunosE Software, you can also configure hierarchical rate limits to provide dynamic bandwidth sharing.

For more information about multiple classifiers and expanded classifiers, see Policy Components.

Policy Objects

The SRC policy model is made up of objects that are organized as shown in Figure 7.

Figure 7: Policy Object Organization

Policy Object Organization

The following is a description of these objects:

  • Policy folders—Used to organize policy groups.
  • Policy groups—Hold policy lists. You associate policy groups with a service or with an interface. The SAE sends the information in a policy group to the router, and the router uses the information to create policies that it attaches to router interfaces.
  • Policy lists—Used to organize policy rules. You can create policy lists for routers running Junos OS, routers running JunosE Software, for AAA devices, or for PCMM devices. Whether you create a Junos OS policy list, a JunosE policy list, or a PCMM policy list determines the types of policy rules that you can add to the policy list.
  • Parent groups—Used to develop hierarchies of rate-limit actions for policies implemented on routers running JunosE Software.
  • Policy rules—Used to organize the conditions and actions that make up the policy rule. Policy rules consist of conditions that you use to match traffic and actions that specify the action to take if traffic matches the condition. In Junos OS terminology, a policy rule is the same as a term.
  • Conditions—Define match conditions or classifiers that a packet or packet flow must contain; for example, packet direction, network protocol, application protocol, source and destination networks, packet length, forwarding class, and source and destination class
  • Actions—Define the action that the router or CMTS device takes on packets that match conditions

Policy Rules

Routers running JunosE Software support IPv4, IPv6, and L2TP access concentrator (LAC) policy rules, PCMM devices support one type of policy rule, and routers running Junos OS support five types of policy rules:

  • Junos Adaptive Services PIC (ASP)

    Supports stateful firewall and Network Address Translation (NAT) services.

  • Junos OS scheduler

    Supports transmission scheduling and rate control parameters on interfaces that support the per-unit scheduler. Schedulers define the priority, bandwidth, delay buffer size, rate control status, and RED drop profiles to be applied to a particular class of traffic.

  • Junos OS shaping

    Supports setting a shaping rate on PICS that support shaping rate and on interfaces that support the per-unit scheduler.

  • Junos OS filter

    Supports Junos OS firewall filters.

  • Junos OS policer

    Supports policing, or rate limiting, by enabling you to limit the amount of traffic that passes into or out of an interface. It is an essential component of firewall filters that is designed to thwart denial-of-service attacks.

    Policing applies two types of rate limits on the traffic:

    • Bandwidth—Number of bps permitted, on average.
    • Maximum burst size—Maximum size permitted for bursts of data that exceed the bandwidth limit.

Supported Conditions and Actions

The types of conditions and actions that are available for a policy rule depend on the type of rule. Figure 8 shows the types of conditions and actions that are available for Junos OS policy rules. Figure 9 shows the types of conditions and actions that are available for JunosE policy rules. Figure 10 shows the types of conditions and actions that are available for PCMM policy rules.

Figure 8: Junos OS policy Rules with Supported Conditions and Actions

Junos OS policy Rules with Supported
Conditions and Actions

Figure 9: JunosE Policy Rules with Supported Conditions and Actions

JunosE Policy Rules with Supported Conditions
and Actions

Figure 10: PCMM Policy Rules with Supported Conditions and Actions

PCMM Policy Rules with Supported Conditions
and Actions

Policy Conditions

Policy conditions are values or fields that a packet must contain. If a policy rule does not contain a match condition, all packets are considered to match. There are two types of conditions:

  • Classify-traffic condition—Matches can include source and destination addresses or networks; ports, packet types, IP options, TCP flags, network protocol, application protocol
  • QoS condition—Matches the forwarding class of the packet

See also Delivering QoS Services in a Cable Environment.

Multiple Classifiers

JunosE and PCMM policy rules can contain multiple classify-traffic conditions. Having multiple classifiers in a policy rule gives you more flexibility for defining services and allows you to use fewer policy rules for some applications.

If multiple policy rules have the same action, but different classify conditions, you can combine the policy rules into one policy rule. You can also set up one policy rule that has multiple classifiers, each for a different subnet or range of addresses.

If you want to collect accounting data on internal versus external traffic, you can configure one policy rule with a set of classifiers for internal traffic and one policy rule with a set of classifiers for external traffic.

Rate-Limiting with Multiple Classifiers

Multiple classifiers give you more flexibility for rate-limiting policies. Without multiple classifiers, you can rate-limit only individual traffic flows. With multiple classifiers, you can rate-limit the aggregate of traffic flows from all sources.

The following example uses multiple classifiers to rate-limit traffic to 1 Mbps for traffic going to two different subnets.

Policy List je-in
Policy Rule rate-limiter
ClassifyTrafficCondition CTC1
        SourceNetwork:
          any
        DestinationNetwork:
          ipAddress=172.60.40.0/0.0.0.255
ClassifyTrafficCondition CTC2
        SourceNetwork:
          any
        DestinationNetwork:
          ipAddress=172.60.20.0/0.0.0.255
Rate limit action that limits to 1 Mbps
Policy List je-out
Policy Rule forward
ClassifyTrafficCondition
        DestinationNetwork:
          any
        SourceNetwork:
          any
Forward action

Expanded Classifiers

For JunosE policies, you can create classify-traffic conditions that the SAE expands into multiple classifiers before it installs the policy on the router. You can enter a comma-separated list of values in:

  • Source network IP address, mask, and IP operation
  • Destination network IP address, mask, and IP operation
  • Port fields (for port-related protocols)

The software creates a classifier for each possible combination of address and port. The software does not expand classifiers for values that are entered as a range.

You would use this feature in policies that are used in IP multimedia subsystem (IMS) environments. You can also use it to simplify the configuration of JunosE policies.

For example, the following classify-traffic condition has comma-separated lists for IP address, IP mask, and from port:

[edit policies folder f group g list l rule r traffic-condition tc]
user@host# show 
source-network { 
  network { 
    ip-address "[192.1.1.0,192.2.1.1]";
    ip-mask "[255.255.255.0,255.255.255.255]";
    ip-operation "[1,1]";
  }
}

tcp-condition { 
  protocol tcp;
  protocol-operation 1;
  source-port { 
    port { 
      from-port "[80,8080]";
      port-operation eq;
    }
  }
}

The sample classify-traffic condition is expanded into four classifiers that have the following combination of source addresses and source ports. Note that JunosE policies use wildcard, not subnet, masks.

192.1.1.0/0.0.0.255 eq 80192.1.1.0/0.0.0.255 eq 8080192.2.1.1/0.0.0.0 eq 80 192.2.1.1/0.0.0.0 eq 8080

Policy Actions

Junos OS policy rules and PCMM policy rules can have multiple actions. JunosE policy rules can have only one action. The types of actions available for a policy rule depend on the type of rule. See Supported Conditions and Actions. The following table is a description of all actions.

Table 7: Policy Actions

Action

Type of Rule

Description

Color

JunosE

Specifies the color attribute that is applied to the packet when it passes through the router.

Color mark

JunosE

Specifies the color-mark value that is applied to the packet when it passes through a rate-limit action.

DOCSIS

PCMM

Explicitly specifies the Data over Cable Service Interface Specifications (DOCSIS) parameters of the DOCSIS service flow. It supports all DOCSIS service flow scheduling types.

Exception application

JunosE

Specifies an exception to the policy rule for traffic that has a specific application, such as a Web server.

Filter

Junos OS filter

JunosE

Discards all packets that match the classify-traffic condition.

FlowSpec

PCMM

Specifies a traffic profile by using a Resource Reservation Protocol (RSVP)-style FlowSpec.

Forward

Junos OS filter

JunosE

Forwards packets that match the classify-traffic condition; forwards packets to a particular interface and/or a next-hop address.

Forwarding class

Junos OS filter

Assigns a forwarding class to packets that match the classify-traffic condition.

GateSpec

PCMM

Specifies the session class ID in the gate. The session class ID provides a way to group gates into different classes with different authorization characteristics.

Loss priority

Junos OS filter

Assigns a packet loss priority to packets that match the classify-traffic condition.

Mark

PCMM

JunosE

Sets the ToS field in the IP header for IPv4 packets, or sets the traffic-class field in the header for IPv6 packets to a specified value.

NAT

Junos OS ASP

Specifies the type of network address translation (source dynamic, destination static), IP address ranges, and a port range to restrict port translation when NAT is configured in dynamic-source mode.

Next hop

Junos OS filter

JunosE

Specifies the IP address of the next hop; used to create a static route on the router; used for captive portal behavior; Junos OS filters support multiple next hops for load balancing.

Next interface

Junos OS filter

JunosE

Defines an output interface and/or a next-hop address for a policy list; used to create a static route on the router; used for captive portal behavior.

Next rule

Junos OS filter

Causes the router to skip to and evaluate the next rule in the policy list.

Policer

Junos OS policer

Junos OS filter

Specifies rate and burst size limits and the action taken if a packet exceeds those limits.

QoS attachment

JunosE

Specifies the QoS profile that is applied to the packet when it passes through the router.

Rate limit

JunosE

Specifies bandwidth attributes (committed, peak, and excess rates and burst sizes) and the action taken relative to the bandwidth (filter, forward, or mark).

Reject

Junos OS filter

Discards the packet and sends an ICMP destination unreachable message to the client; can set the type of ICMP message to send.

Routing instance

Junos OS filter

Also called filter-based forwarding; directs traffic to a routing instance that is configured on the router.

Scheduler

Junos OS scheduler

Specifies transmission-scheduling and rate-control parameters. Schedulers define the priority, bandwidth, delay buffer size, rate-control status, and RED drop profiles to be applied to a particular class of traffic.

Service class name

PCMM

Specifies that traffic is controlled by a service class that is configured on the CMTS device.

Stateful firewall

Junos OS ASP

Specifies whether to filter, forward, or reject a packet. If a packet is rejected, a rejection message is returned.

Traffic class

JunosE

Specifies the traffic-class profile that is applied to the packet when it passes through the router.

Traffic shape

Junos OS shaping

Specifies the maximum rate of traffic transmitted on an interface.

Traffic mirror

Junos OS filter

Mirrors traffic from a destination to a source or from a source to a destination.

User packet class

JunosE

Specifies the user packet class that is applied to the packet when it passes through the router.

Combining Actions

Junos OS policy rules and PCMM policy rules support multiple actions. For example, in PCMM policies, you can combine a mark action with a DOCSIS parameter action, a service schedule action, or a FlowSpec action. In Junos OS policy rules you can combine the forwarding class action, routing instance action, and loss priority action. The result is that packets that match the condition are assigned to a forwarding class, directed to a routing instance on the router, and assigned a packet loss priority.

Only one of the following actions can exist in a policy rule: next-hop action, next-interface action, forward action, filter action, and reject action.

For example, if you add the next-rule action to a policy rule, do not add a next-hop action, next-interface action, forward action, filter action, or reject action to the same policy rule.

Although you can have only one action in a JunosE policy rule, you can set up a policy list to take two corresponding actions on a packet. To do so, you create a JunosE policy list that has more than one policy rule with the same precedence. For example, you might want a policy rule that marks a packet and a policy rule that forwards the packet to the next interface. Or you could have a policy rule that applies a traffic-class action and a policy rule that forwards the packet to the next hop.

Related Documentation

Modified: 2016-05-26