Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring 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 the action include:

Configuring Color Actions (SRC CLI)

You can configure color actions for JunosE policy rules. The type of action that you can create depends on the type of policy rule.

Use the following configuration statements to configure color actions:

To configure a color action:

  1. From configuration mode, enter the color action configuration.

  2. (Optional) Configure the color that is applied to a packet when it passes through the router.

  3. (Optional) Enter a description for the color action.

  4. (Optional) Verify the color action configuration.

Configuring Color Mark Actions (SRC CLI)

You can configure color-mark actions to apply a TOS mark value based on the packet’s color. A color-mark can be applied to a packet after it exits a rate-limit hierarchy.

The type of action that you can create depends on the type policy rule. See Policy Information Model.

Use the following configuration statements to configure color actions:

To configure a color mark action:

  1. From configuration mode, enter the color mark action configuration.

  2. (Optional) Specify the green-mark value.

  3. (Optional) Specify the yellow-mark value.

  4. (Optional) Specify the red-mark value.

  5. Specify the mask value to use when marking packets.

  6. (Optional) Enter a description for the color mark action.

  7. (Optional) Verify the color action mark configuration.

Configuring DOCSIS Actions (SRC CLI)

You can configure Data over Cable Service Interface Specifications (DOCSIS) actions for PacketCable Multimedia Specification (PCMM) 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 statements to configure DOCSIS actions. Use the configuration statement for the service flow scheduling type that you want to use for the DOCSIS action. The types are best effort, downstream, non-real-time polling service, real-time polling service, unsolicited grant service, unsolicited grant service with activity detection, or parameter.

To configure a DOCSIS action:

  1. From configuration mode, enter the DOCSIS action configuration. In this procedure, the parameter action is configured as an example.

  2. Assign a parameter as the service flow scheduling type.

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

  3. (Optional) Configure a priority for the service flow. If two traffic flows are identical in all QoS parameters except priority, the higher-priority service flow is given preference.

  4. (Optional) Configure the request transmission policy, which is the interval usage code that the cable modem uses for upstream transmission requests and packet transmissions for this service flow. It also specifies whether requests can be piggybacked with data.

    • For data packets transmitted on this service flow, this option also specifies whether packets can be concatenated, fragmented, or have their payload headers suppressed.

    • For UGS service flows, this option also specifies how to treat packets that do not fit into the UGS grant.

  5. (Optional) Configure the maximum sustained rate at which traffic can operate over the service flow.

  6. (Optional) Configure the maximum burst size for the service flow. This option has no effect unless you configure a nonzero value for the maximum sustained rate.

  7. (Optional) Configure the guaranteed minimum rate that is reserved for the service flow.

  8. (Optional) Configure the assumed minimum packet size for which the minimum reserved traffic rate is provided. If a packet is smaller than the assumed minimum packet size, the software treats the packet as if its size is equal to the value specified in this option.

  9. (Optional) Configure the maximum latency for downstream service flows. It is the maximum latency for a packet that passes through the CMTS device, from the time that the CMTS device’s network side interface receives the packet until the CMTS device forwards the packet on its radio frequency (RF) interface.

  10. (Optional) Configure the nominal interval between successive unicast request opportunities for this service flow.

  11. (Optional) Configure the maximum amount of time that unicast request intervals can be delayed beyond the nominal polling interval.

  12. (Optional) Configure the size of the individual data grants provided to the service flow.

  13. (Optional) Configure the actual number of data grants given to the service flow during each nominal grant interval.

  14. (Optional) Configure the maximum amount of time that the transmission opportunities can be delayed beyond the nominal grant interval.

  15. (Optional) Configure the nominal interval between successive unsolicited data grant opportunities for this service flow.

  16. (Optional) Enter a description for the filter action.

  17. (Optional) Verify the DOCSIS action configuration.

Configuring Dynamic Profile Actions (SRC CLI)

Use this action to install existing dynamic profiles. You can configure dynamic profile actions for devices such as the MX Series routers.

The profile name must match a dynamic profile configured on the device, and the variable name must match a variable configured for the dynamic profile.

Use the following configuration statements to configure a dynamic profile action:

To configure a dynamic profile action:

  1. From configuration mode, enter the dynamic profile action configuration.
  2. Enter the profile name to activate.
  3. (Optional) Enter a description for the dynamic profile action.
  4. From configuration mode, enter the parameters used by the profile.

    For example:

  5. (Optional) Configure the value for the variable.

    For example:

  6. (Optional) Configure the variable type. Variable types are mapped to parameter types.

    For example:

Configuring Exception Application Actions (SRC CLI)

Use the following statements to configure policy actions that specify exceptions to a rule to identify the client application that is a destination for packets.

The type of action that you can create depends on the type of policy rule. See Policy Information Model.

To configure an exception action in a policy rule to specify that traffic be sent to a client application:

  1. From configuration mode, enter the exception application action configuration.

  2. Specify the application type, such as HTTP for Web traffic.

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:

To configure a filter action:

  1. From configuration mode, enter the filter action configuration.

  2. (Optional) Enter a description for the filter action.

  3. (Optional) Verify the filter action configuration.

Configuring FlowSpec Actions (SRC CLI)

A FlowSpec is made up of two parts, a traffic specification (TSpec) and a service request specification (RSpec). The TSpec describes the traffic requirements for the flow, and the RSpec specifies resource requirements for the desired service. You can configure FlowSpec actions for PCMM 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 statements to configure FlowSpec actions:

To configure a FlowSpec action:

  1. From configuration mode, enter the FlowSpec action configuration.

  2. (Optional) Configure the type of FlowSpec service as either controlled_load_service or guaranteed_service. The FlowSpec options available for configuration change depending on the type of service that you select:

    • Controlled load services can contain only TSpec parameters.

    • Guaranteed services can contain both TSpec and RSpec parameters.

  3. (Optional TSpec parameter) Configure the guaranteed minimum rate that is reserved for the service flow.

  4. (Optional TSpec parameter) Configure the maximum burst size for the service flow.

  5. (Optional TSpec parameter) Configure the amount of bandwidth over the committed rate that is allocated to accommodate excess traffic flow over the committed rate.

  6. (Optional TSpec parameter) Configure the assumed minimum-reserved-rate packet size. If a packet is smaller than the minimum policed unit, the software treats the packet as if its size is equal to the value specified in this option.

  7. (Optional TSpec parameter) Configure the maximum packet size for the FlowSpec.

  8. (Optional RSpec parameter) Configure the average rate.

  9. (Optional RSpec parameter) Configure the amount of slack in the bandwidth reservation that can be used without redefining the reservation.

  10. (Optional) Configure a description for the FlowSpec action.

  11. (Optional) Verify the FlowSpec action configuration.

Configuring Forward Actions (SRC CLI)

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 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 forward actions:

To configure a forward action:

  1. From configuration mode, enter the forward action configuration.

  2. (Optional) Enter a description for the forward action.

  3. (Optional) Verify the forward action configuration.

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:

To configure a forwarding class action:

  1. From configuration mode, enter the forwarding class action configuration.

  2. (Optional) Configure the name of the forwarding class assigned to packets.

  3. (Optional) Enter a description for the forwarding class action.

  4. (Optional) Verify the forwarding class action configuration.

Configuring GateSpec Actions (SRC CLI)

You can configure GateSpec actions for PCMM policy rules. See Policy Information Modelfor more information.

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 GateSpec actions:

To configure a GateSpec action:

  1. From configuration mode, enter the GateSpec action configuration.

  2. (Optional) Configure the priority bits in the session class ID. The priority describes the relative importance of the session as compared with other sessions generated by the same policy decision point.

  3. (Optional) Configure the preemption bit in the session class ID. Use the preemption bit to allocate bandwidth to lower-priority sessions.

  4. (Optional) Configure the configurable bit in the session class ID.

  5. (Optional) Enter a description for the GateSpec action.

  6. (Optional) Verify the GateSpec action configuration.

Configuring HTTP Redirect Actions (SRC CLI)

Use the following statements to configure policy actions to redirect Web traffic to a specified URL.

The type of action that you can create depends on the type of policy rule. See Policy Information Model.

To configure an HTTP redirect action in a policy rule to specify that Web traffic be sent to a specified URL:

  1. From configuration mode, enter the HTTP redirect action configuration.

  2. Specify the destination URL to which traffic will be redirected. For example, to redirect the traffic to www.new.com:

Configuring Loss Priority Actions (SRC CLI)

You can configure loss priority actions for Junos OS 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.

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 loss priority actions:

To configure a loss priority action:

  1. From configuration mode, enter the loss priority action configuration.

  2. (Optional) Configure the packet loss priority.

  3. (Optional) Enter a description for the loss priority action.

  4. (Optional) Verify the loss priority action configuration.

Configuring Mark Actions (SRC CLI)

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

The type of action that you can create depends on the type of policy rule. See Policy Information Model.

Note

If you configure more than one mark action in a rate limit, for example, for a committed, conformed, or exceed action, configure the same mask for each action. If you use different masks, the results can be unpredictable.

Use the following configuration statements to configure a mark action:

To configure a mark action:

  1. From configuration mode, enter the mark action configuration.

  2. (Optional) Enter a description for the mark action.

  3. (Optional) Configure the mark value.

  4. (Optional) Configure the mark mask.

    Supported values for the mask are 224 for precedence bits, 252 for DS bits, and 255 to mask all bits.

  5. (Optional) Verify the mark action configuration.

Configuring NAT Actions (SRC CLI)

You can configure NAT actions for Junos OS ASP 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 statements to configure NAT actions:

To configure a NAT action:

  1. From configuration mode, enter the NAT action configuration.

  2. (Optional) Configure the type of network address translation that is used.

  3. (Optional) Enter a description for the NAT action.

  4. (Optional) Configure the port range to restrict port translation when the NAT translation type is configured in dynamic-source mode.

  5. (Optional) Configure the IP address ranges.

  6. (Optional) Verify the NAT action configuration.

Configuring Next-Hop Actions (SRC CLI)

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 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 statements to configure the next-hop action.

To configure a next-hop action:

  1. From configuration mode, enter the next-hop action configuration.

  2. (Optional) Configure the next IP address where the classified packets should go.

  3. (Optional) Enter a description for the next-hop action.

  4. (Optional) Verify the next-hop action configuration.

Configuring Next-Interface Actions (SRC CLI)

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

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 next-interface actions:

To configure a next-interface action:

  1. From configuration mode, enter the next-interface action configuration.

  2. (Optional) Configure the IP interface to be used as the next interface for packets.

  3. (Optional) Configure the next IP address where the classified packets should go. This option is available only in JunosE policy rules.

  4. (Optional) Enter a description for the next-interface action.

  5. (Optional) Verify the next-interface action configuration.

Configuring Next-Rule Actions (SRC CLI)

You can configure next-rule actions for Junos OS 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.

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 next-rule actions.

To configure a next-rule action:

  1. From configuration mode, enter the next-rule action configuration.

  2. (Optional) Enter a description for the next-rule action.

  3. (Optional) Verify the next-rule action configuration.

Configuring Policer Actions (SRC CLI)

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 OS policer and Junos OS filter 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 statements to configure policer actions:

To configure a policer action:

  1. From configuration mode, enter the policer action configuration.

  2. (Optional) Configure the traffic rate that, if exceeded, causes the router to take the indicated packet action.

  3. (Optional) Configure the type of value entered for bandwidth limit.

  4. (Optional) Configure the maximum burst size. The minimum recommended value is the maximum transmission unit (MTU) of the IP packets being policed.

  5. (Optional) Enter a description for the policer action.

  6. (Optional) Verify the policer action configuration.

Configuring the Packet Action for the Policer Action (SRC CLI)

The packet action specifies the action taken on a packet that exceeds its rate limits. You configure packet actions within policer actions.

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 packet action:

To configure a packet action:

  1. From configuration mode, enter the packet action configuration. For example, in this procedure, pktAction is the name of the packet action.

  2. (Optional) Configure the action to take on packets that exceed the bandwidth limit configured in the policer action.

    • Filter—Packets are discarded.

    • Forwarding class—Packets are assigned to the forwarding class that you specify.

    • Loss priority—Packets are assigned the loss priority that you specify.

    • Parameter—The action specified by the parameter is applied. Before you assign a parameter, you must create a parameter of type packetOperation and commit the parameter configuration.

  3. (Optional) Verify the policer action configuration.

Configuring QoS Profile Attachment Actions (SRC CLI)

Use this action to specify the QoS profile and the QoS parameters to attach to the router interface when this action is taken. The QoS profile and the QoS parameters must be configured on the router. 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 Dynamically Managing QoS Profiles.

The QoS parameters allow you to specify rates in QoS profiles as parameters instead of fixed values. The actual values for the parameters can be specified for each interface. Therefore, you can share a QoS profile among different interfaces with different rates.

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 QoS profile attachment actions:

To configure a QoS profile attachment action:

  1. From configuration mode, enter the QoS profile attachment action configuration.

  2. Configure the name of the QoS profile to attach to the JunosE interface when this action is taken.

  3. (Optional) Configure the names and values of the QoS parameters to attach to the JunosE interface when this action is taken. Use map expressions to specify multiple values.

  4. (Optional) Enter a description for the QoS profile attachment action.

  5. (Optional) Verify the QoS profile attachment action configuration.

Configuring Rate-Limit Actions (SRC CLI)

Use this action to define the quality of service. You can configure rate-limit actions for 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 statements to configure rate-limit actions:

To configure a rate-limit action:

  1. From configuration mode, enter the rate-limit action configuration.

  2. (Optional) Specify that the rate-limit profile is either one rate or two rate. The rate-limit type determines the options that you can configure for a rate-limit action.

  3. (Optional) Configure the target rate for the traffic that the policy covers.

  4. (Optional) Configure the amount of bandwidth allocated to burst traffic in bytes.

  5. (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to excess traffic flow over the committed rate.

  6. (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to burst traffic in excess of the peak rate.

  7. (Optional) For one-rate rate-limit profiles, specify the amount of bandwidth allocated to accommodate burst traffic.

  8. (Optional) Set the rate limit to color aware for the rate-limit to process color values.

  9. (Optional) Set the rate limit to support hierarchical rate limits.

  10. (Optional) Configure the rate-limit action for traffic flows that:

    • Do not exceed the committed rate

  11. (Optional) Enter a description for the rate-limit action.

  12. (Optional) Return to the rate-limit action configuration, and verify the configuration.

Configuring Hierarchical Rate-Limit Actions (SRC CLI)

You configure parent groups to create a hierarchy of rate-limits actions.

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 rate-limit actions:

To configure a parent group:

  1. From configuration mode, create a parent group in a policy list—for example, PGShared.

  2. Configure a rate limit for the parent group.

    • Specify that the rate limit is either one rate or two rate. The rate-limit type determines the options that you can configure for a rate-limit action.

    • (Optional) Configure the target rate for the traffic that the policy covers.

    • (Optional) Configure the amount of bandwidth allocated to burst traffic in bytes.

    • (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to excess traffic flow over the committed rate.

    • (Optional) For two-rate rate limit profiles, specify the amount of bandwidth allocated to burst traffic in excess of the peak rate.

    • (Optional) For one-rate rate limit profiles, specify the amount of bandwidth allocated to accommodate burst traffic.

    • (Optional) Set the rate-limit to color aware for the rate-limit to process color values set in the TOS byte of the packet header.

  3. (Optional) Configure the rate-limit actions for traffic flows that:

    • Do not exceed the committed rate and burst size

    • Exceed the committed rate but remain below the peak burst size

    See Configuring Types of Actions for Rate-Limit Actions (SRC CLI).

  4. Enter a description for the parent group.

  5. Step up one level in the edit hierarchy.

  6. (Optional) Configure the parent group to reference an external parent group. For example, to add a reference called epg1-ref:

    • Specify the name of the external parent group that you want to reference. For example, to reference the external parent group epg1:

    • Specify the name of the hierarchical policy parameter for the external parent group. For example, to associate the hierarchical policy parameter called hpp1:

    • Specify the attributes of the hierarchical policy parameter that you are referencing.

      For information about configuring the attributes of the hierarchical policy parameter, see Configuring Hierarchical Policy Parameters for External Parent Groups (SRC CLI).

  7. (Optional) Return to the rate-limit action configuration and verify the configuration.

  8. (Optional) Create another parent group within this parent group. For example:

  9. (Optional) Follow the instructions in this procedure for configuring the parent group.

Configuring Types of Actions for Rate-Limit Actions (SRC CLI)

When you configure a rate-limit action or a rate-limit hierarchy, you specify types of actions for conformed traffic, committed traffic, and exceed traffic.

Before you configure the various types of action, configure the rate limit or parent group (for rate-limit hierarchies) that is to include the actions. See

Use the following configuration statements to configure rate-limit actions from the following hierarchy levels:

  • [edit policies group name list name rule name]

  • [edit policies group name list name parent-group name]

To specify types of actions for rate-limit actions:

  • Specify an action for a rate-limit action or a rate-limit hierarchy:

    Note

    The following examples show the configuration for a committed action. You can configure the same actions for committed actions, conformed actions, and exceed actions.

    • Filter (drop packet).

    • Forward.

    • (For rate-limit hierarchies only) Forward conditionally.

    • (Rate-limit hierarchies only for committed and conformed actions) Forward unconditionally.

    • (For rate-limit hierarchies only) Forward and exit from the rate-limit hierarchy.

    • Mark. If you select mark, enter the mark values.

      Make sure that masks configured with a rate limit action are the same for different mark actions.

    • Parameter. Before you assign a parameter, you must create a parameter of type packetOperation and commit the parameter configuration.

Configuring Reject Actions (SRC CLI)

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

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 reject actions:

To configure a reject action:

  1. From configuration mode, enter the reject action configuration.

  2. (Optional) Configure the type of ICMP destination unreachable message sent to the client.

  3. (Optional) Enter a description for the reject action.

  4. (Optional) Verify the reject action configuration.

Configuring Routing Instance Actions (SRC CLI)

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

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 routing instance actions:

To configure a routing instance action:

  1. From configuration mode, enter the routing instance action configuration.

  2. (Optional) Configure the routing instance to which packets are forwarded. The routing instance must be configured on the router.

  3. (Optional) Enter a description for the reject action.

  4. (Optional) Verify the routing instance action configuration.

Configuring Scheduler Actions (SRC CLI)

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 OS scheduler 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 statements to configure scheduler actions:

To configure a scheduler action:

  1. From configuration mode, enter the scheduler action configuration.

  2. (Optional) Configure the queue transmission buffer size.

  3. (Optional) Configure the type of value that you entered for buffer size.

  4. (Optional) Configure the packet-scheduling priority. The priority determines the order in which an output interface transmits traffic from the queues.

  5. (Optional) Configure the transmit rate.

  6. (Optional) Configure the type of value entered for transmit rate.

  7. (Optional) Specify whether or not to enforce the exact transmission rate. Under sustained congestion, a rate-controlled queue that goes into negative credit fills up and eventually drops packets.

  8. (Optional) Enter a description for the scheduler action.

  9. (Optional) Verify the scheduler action configuration.

Configuring Drop Profiles (SRC CLI)

You configure drop profiles within scheduler actions. Drop profiles support the RED process by defining the drop probabilities across the range of delay-buffer occupancy. 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.

In drop profiles you configure the queue threshold 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 OS documentation.

Use the following configuration statements to configure drop profiles:

To configure drop profiles:

  1. From configuration mode, enter the drop profile configuration. For example, in this procedure, drop1 is the name of the drop profile.

  2. Configure the loss priority.

  3. Configure the protocol type.

  4. Configure the relationship between the fill level and drop probability.

  5. Configure the probability that a packet will be dropped.

  6. Configure the fill level of the queue.

  7. (Optional) Verify the drop profile configuration.

Configuring Service Class Name Actions (SRC CLI)

You can configure service class name actions for PCMM 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 statements to configure service class name actions:

To configure a service class name action:

  1. From configuration mode, enter the service class name action configuration.

  2. (Optional) Configure the name of a service class on the CMTS device that specifies QoS parameters for a service flow.

  3. (Optional) Enter a description for the service class name action.

  4. (Optional) Verify the service class name action configuration.

Configuring Stateful Firewall Actions (SRC CLI)

You can configure stateful firewall actions for Junos OS ASP policy rules. Stateful firewall actions specify the action to take on packets that match the 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 stateful firewall actions:

To configure a stateful firewall action:

  1. From configuration mode, enter the stateful firewall action configuration.

  2. (Optional) Set the action to take on a packet to one of the following:

    • Filter.

    • Forward.

    • Reject. If you set the action to reject, configure the type of ICMP destination unreachable message sent to the client.

    • Parameter. Before you assign a parameter, you must create a parameter of type packetOperation and commit the parameter configuration.

  3. (Optional) Enter a description for the stateful firewall action.

  4. (Optional) Verify the stateful firewall action configuration.

Configuring Template Activation Actions (SRC CLI)

Use this action to activate templates for RADIUS-enabled devices. You can configure template activation actions for AAA policy rules.

The template name and parameters are listed in the custom router template on the IMS AAA Server.

Use the following configuration statements to configure template activation actions:

To configure a template activation action:

  1. From configuration mode, enter the template activation action configuration.

  2. Enter the template name to activate.

  3. (Optional) Enter a description for the template activation action.

  4. From configuration mode, enter the parameters used by the template.

    For example:

  5. (Optional) Configure the value for the variable.

    For example:

  6. (Optional) Configure the variable type. Variable types are mapped to parameter types.

    For example:

  7. (Optional) Verify the template activation action configuration.

Configuring Traffic-Class Actions (SRC CLI)

Use this action to put packets in a particular traffic class. You can configure traffic-class actions for 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 traffic-class actions:

To configure a traffic-class action:

  1. From configuration mode, enter the traffic-class configuration.

  2. (Optional) Configure the name of the traffic-class profile that is applied to a packet when it passes through the router.

  3. (Optional) Enter a description for the traffic-class action.

  4. (Optional) Verify the traffic-class action configuration.

Configuring Traffic-Mirror Actions (SRC CLI)

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 for Junos OS filter input policy rules.

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

The type of action that you can create depends on the type of policy rule. See Policy Information Model.

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

  • It must be combined with forward actions in the same rule. One of the forward actions must accept the traffic if the source and/or destination IP addresses do not match the conditions.

  • It contains either no classify-traffic condition or only one classify-traffic condition.

  • It can be marked for accounting.

Use the following configuration statement to configure a traffic-mirror action:

To configure a traffic-mirror action:

  1. From configuration mode, enter the traffic-mirror configuration.

  2. (Optional) Enter a description for the traffic-mirror action.

  3. (Optional) Verify the traffic-mirror action configuration.

Configuring Traffic-Shape Actions (SRC CLI)

Traffic-shape actions specify the maximum rate of traffic transmitted on an interface. You can create traffic-shape actions in Junos OS shaping 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 statements to configure traffic-shape actions:

To configure a traffic-shape action:

  1. From configuration mode, enter the traffic-shape configuration.

  2. (Optional) Configure the maximum transmission rate.

  3. (Optional) Enter a description for the traffic-shape action.

  4. (Optional) Verify the traffic-shape action configuration.

Configuring User Packet Class Actions (SRC CLI)

Use this action to put packets in a particular user packet class. You can configure user packet class actions for 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 user packet class actions:

To configure a user packet class action:

  1. From configuration mode, enter the user packet class configuration.

  2. (Optional) Configure the user packet class that is applied to a packet when it passes through the router.

  3. (Optional) Enter a description for the user packet class action.

  4. (Optional) Verify the user packet class action configuration.