[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Configuring Actions

Actions define the action taken on packets that match conditions in a policy rule. You create actions within policy rules. The type of action that you can create depends on the type of policy rule. See Supported Conditions and Actions.

Adding Actions

To add an action:

  1. In the navigation pane, right-click a policy rule.
  2. Click New > Action, and select an action from the list.

The <Action> Name dialog box appears.

  1. Enter a name, and click OK.
  2. Select the new action in the navigation pane.
  3. Configure the action as described in the following sections:

Configuring DOCSIS Actions

You can configure Data over Cable Service Interface Specifications (DOCSIS) actions for PacketCable Multimedia Specification (PCMM) policy rules.

Service Flow Scheduling Type

Traffic Priority

Request Transmission Policy

Maximum Sustained Traffic Rate

Maximum Traffic Burst

Minimum Reserved Traffic Rate

Assumed Minimum Reserved Traffic Rate Packet Size

Maximum Downstream Latency

Nominal Polling Interval

Tolerated Poll Jitter

Unsolicited Grant Size

Grants Per Interval

Nominal Grant Interval

Tolerated Grant Jitter

Configuring Filter Actions

Use this action to discard packets. You can configure filter actions for JUNOS filters and JUNOSe policy rules.

Description

Configuring FlowSpec Actions

You can configure FlowSpec actions for PCMM policy rules.

Service Number

Token Bucket Rate

Token Bucket Size

Peak Data Rate

Minimum Policed Unit

Maximum Packet Size

Rate

Slack Term

Configuring Forward Actions

Use this action to forward packets, such as packets that are sent by means of a routing table. You can configure forward actions for JUNOS filters and JUNOSe policy rules.

Description

Configuring Forwarding Class Actions

You can configure forwarding class actions for JUNOS filter policy rules. The forwarding class action causes the router to assign a forwarding class to packets that match the associated classify-traffic condition.

Description

Forwarding Class

Configuring GateSpec Actions

You can configure GateSpec actions for PCMM policy rules. See Session Class ID for more information.

Description

Session Class Id Priority

Session Class Id Preemption

Session Class Id Configurable

Configuring Loss Priority Actions

You can configure loss priority actions for JUNOS filter policy rules. The loss priority action causes the router to assign a packet loss priority to packets that match the associated classify-traffic condition.

Loss Priority

Configuring Mark Actions

Use this action to mark packets. You can configure mark actions for JUNOSe and PCMM policy rules.

Description

Mark Value

Mark Mask

Configuring NAT Actions

You can configure NAT actions for JUNOS ASP policy rules.

NAT Translation Type

IP Network

Port

Configuring Next-Hop Actions

Use this action for the ingress side of the interface to specify the next IP address where the classified packets should go. You can configure next-hop actions for JUNOS filters and JUNOSe policy rules.

Using the Next-Hop Action with the Captive Portal

The captive portal feature is used to intercept HTTP requests from a subscriber to an unauthorized Web resource and redirect the requests to a dedicated Web page, the captive portal page. See Redirecting Traffic to a Captive Portal Web Page in SRC-PE Subscribers and Subscriptions Guide, Chapter 18, Developing a Residential Portal.

In a captive portal environment, you would typically set up a next-hop action on a subscriber's interface that forwards traffic to the redirect engine. In this case, you would set the next-hop address to the address of the redirect server.

When you set up redirect server redundancy, both the active and redundant redirect servers share a virtual IP address so that subscribers can always reach the active redirect server. Subscribers send requests to the virtual IP address, and the router automatically sends the request to the active redirect server by means of a static route. In this case, you would set the next-hop address to the virtual IP address.

Configuring Next-Hop Action

Fill in the following fields to configure the next-hop action.

Description

Next Hop Address

Configuring Next-Interface Actions

Use this action to forward packets to a particular interface and/or a next-hop address. You can configure next-interface actions for JUNOS filters and JUNOSe policy rules. On JUNOSe routers, you can use this action for both ingress and egress parts of the interface.

Description

InterfaceSpec

Next Hop Address

Configuring Next-Rule Actions

You can configure next-rule actions for JUNOS filter policy rules. If a packet matches the classify-traffic condition, the next-rule action causes the router to continue to the next rule in the policy list for evaluation.

Description

Configuring Policer Actions

The policer action specifies rate and burst size limits and the action taken if a packet exceeds those limits. You can create policer actions in JUNOS policer and JUNOS filter policy rules.

Description

Bandwidth Limit

where bw is a local parameter that has a value of 1024 * 1920

Bandwidth Limit Unit

Burst Size Limit (bytes)

where qosRate is a local parameter of type rate

Packet Action

Configuring QoS Profile Attachment Actions

Use this action to specify the name of the QoS profile to attach to the router interface when this action is taken. You can configure QoS actions for JUNOSe policy rules.

The router allows only one QoS profile to be attached to an interface at one time. Therefore, as a subscriber activates and deactivates different services, the QoS profile running on the interface needs to change. The SRC software provides a QoS-tracking plug-in (QTP) that you can use to ensure that as a subscriber activates and deactivates services, the required QoS profile is attached to the subscriber interface. See SRC-PE Solutions Guide, Chapter 1, Managing Tiered and Premium Services with QoS on JUNOSe Routers.

Description

QoS Profile

Configuring Rate-Limit Actions

Use this action to define the quality of service. You can configure rate-limit actions for JUNOSe policy rules.

Description

Rate Limit Type

Committed Rate (bps)

Committed Burst (bytes)

Peak Rate (bps)

Peak Burst (bytes)

Excess Burst (bytes)

Committed Action

The ToS byte can be an integer in the range 0-255 or parameter of type tosByte

Conformed Action

The ToS byte can be an integer in the range 0-255 or parameter of type tosByte

Exceeded Action

The ToS byte can be an integer in the range 0-255 or parameter of type tosByte

Configuring Reject Actions

You can configure reject actions for JUNOS filter policy rules. The reject action causes the router to discard a packet and send an ICMP destination unreachable message.

Description

Message Type

Configuring Routing Instance Actions

You can configure routing instance actions for JUNOS filter policy rules. Use routing instance actions for filter-based forwarding to direct traffic to a specific routing instance configured on the router.

Description

Routing Instance

Configuring Scheduler Actions

You use scheduler actions along with QoS conditions and traffic-shape actions to configure transmission scheduling and rate control. Schedulers define the priority, bandwidth, delay buffer size, rate control status, and random early detection (RED) drop profiles to be applied to a particular class of traffic. You can create scheduler actions in JUNOS scheduler policy rules.

Description

Buffer Size

Buffer Size Unit

Transmit Rate

where bandwidth is a local parameter of type any

Transmit Rate Unit

Exact

Priority

Configuring Drop Profile Maps

The scheduler drop profile defines the drop probabilities across the range of delay-buffer occupancy, thereby supporting the RED process. For a packet to be dropped, it must match the drop profile. When a packet arrives, RED checks the queue fill level. If the fill level corresponds to a nonzero drop probability, the RED algorithm determines whether to drop the arriving packet. Depending on the drop probabilities, RED might drop packets aggressively long before the buffer becomes full, or it might drop only a few packets even if the buffer is almost full.

The SchedulerAction pane displays a table with configured drop profile maps. To configure the table:

Protocol

Loss Priority

Drop Profile Type

Setting Fill Level and Drop Probability

In drop profiles you configure fill level and drop probability as paired values. The values can be either percentage values (segmented) or data points (interpolated). These two alternatives enable you to configure each drop probability at up to 64 fill-level/drop-probability paired values, or to configure a profile represented as a series of line segments. For more information about configuring fill level and drop probabilities, see the JUNOS routing platform documentation.

You can set these value pairs by clicking Show Data Points on the Drop Profile Map Details screen. To add a value pair:

  1. In the data entry field, enter the value for the fill level, press the space bar, and then enter the drop probability value.
  2. Click Add.

Fill Level

Drop Probability

Configuring Service Class Name Actions

You can configure service class name actions for PCMM policy rules.

Description

Service Class

Configuring Stateful Firewall Actions

You can configure stateful firewall actions for JUNOS ASP policy rules. Stateful firewall actions specify the action to take on packets that match the classify-traffic condition.

Description

Packet Action

Configuring Traffic-Class Actions

Use this action to put packets in a particular traffic class. You can configure traffic-class actions for JUNOSe policy rules.

Description

Caption

Keywords

Traffic-Class Profile

Configuring Traffic-Mirror Actions

Use this action to mirror traffic from a destination to a source or from a source to a destination. You can configure traffic-mirror actions only for JUNOS input policy rules.

Before you use traffic-mirror actions, you must configure forwarding options on JUNOS routing platforms for port mirroring and next-hop group. For information about how these features work on the router, see the JUNOS Policy Framework Configuration Guide.

The rule containing a traffic-mirror action must comply with these conditions:

Description

Configuring Traffic-Shape Actions

Traffic-shape actions specify the maximum rate of traffic transmitted on an interface. You can create traffic-shape actions in JUNOS shaping policy rules.

Description

Rate (bps)


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]