[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.

Configure the action as described in the following sections:

Configuring Color Actions

You can configure color actions for JUNOSe IPv6 policy rules.

Use the following configuration statements to configure color actions:

policies group name list name rule name color name {
color color; 
description description; 
}

To configure a color action:

  1. From configuration mode, enter the color action configuration. For example, in this procedure, ca is the name of the color action.
  2. user@host# edit policies group junose_filter list in rule pr color ca 
    
    
    
  3. (Optional) Configure the color that is applied to a packet when it passes through the router.
  4. [edit policies group junose_filter list in rule pr filter ca]
    
    user@host# set color color 
    
    
    
  5. (Optional) Enter a description for the color action.
  6. [edit policies group junose_filter list in rule pr filter ca]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the color action configuration.
  8. [edit policies group junose_filter list in rule pr filter ca]
    
    user@host# show 
    
    color green;
    
    description "Color action for JUNOSe IPv6 policies";
    

Configuring DOCSIS Actions

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

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.

policies group name list name rule name docsis-best-effort name {
traffic-priority traffic-priority; 

request-transmission-policy request-transmission-policy; 

maximum-sustained-rate maximum-sustained-rate; 

maximum-traffic-burst maximum-traffic-burst; 

minimum-reserved-rate minimum-reserved-rate; 

assumed-minimum-res-packet-size assumed-minimum-res-packet-size; 

description description; 
}

policies group name list name rule name docsis-down-stream name {
traffic-priority traffic-priority; 

maximum-latency maximum-latency; 

maximum-sustained-rate maximum-sustained-rate; 

maximum-traffic-burst maximum-traffic-burst; 

minimum-reserved-rate minimum-reserved-rate; 

assumed-minimum-res-packet-size assumed-minimum-res-packet-size; 

description description; 
}

policies group name list name rule name docsis-non-real-time name {
traffic-priority traffic-priority; 

request-transmission-policy request-transmission-policy; 

maximum-sustained-rate maximum-sustained-rate; 

maximum-traffic-burst maximum-traffic-burst; 

minimum-reserved-rate minimum-reserved-rate; 

assumed-minimum-res-packet-size assumed-minimum-res-packet-size; 

nominal-polling-interval nominal-polling-interval; 

description description; 
}

policies group name list name rule name docsis-real-time name {
request-transmission-policy request-transmission-policy; 

maximum-sustained-rate maximum-sustained-rate; 

maximum-traffic-burst maximum-traffic-burst; 

minimum-reserved-rate minimum-reserved-rate; 

assumed-minimum-res-packet-size assumed-minimum-res-packet-size; 

nominal-polling-interval nominal-polling-interval; 

tolerated-poll-jitter tolerated-poll-jitter; 

description description; 
}

policies group name list name rule name docsis-unsolicited-grant name {
request-transmission-policy request-transmission-policy; 

grant-size grant-size; 

grants-per-interval grants-per-interval; 

tolerated-grant-jitter tolerated-grant-jitter; 

nominal-grant-interval nominal-grant-interval; 

description description; 
}

policies group name list name rule name docsis-unsolicited-grant-ad name {
request-transmission-policy request-transmission-policy; 

nominal-polling-interval nominal-polling-interval; 

grant-size grant-size; 

grants-per-interval grants-per-interval; 

tolerated-grant-jitter tolerated-grant-jitter; 

nominal-grant-interval nominal-grant-interval; 

description description; 
}

policies group name list name rule name docsis-param name {
service-flow-type service-flow-type; 

traffic-priority traffic-priority; 

request-transmission-policy request-transmission-policy; 

maximum-sustained-rate maximum-sustained-rate; 

maximum-traffic-burst maximum-traffic-burst; 

minimum-reserved-rate minimum-reserved-rate; 

assumed-minimum-res-packet-size assumed-minimum-res-packet-size; 

maximum-latency maximum-latency; 

nominal-polling-interval nominal-polling-interval; 

tolerated-poll-jitter tolerated-poll-jitter; 

grant-size grant-size; 

grants-per-interval grants-per-interval; 

tolerated-grant-jitter tolerated-grant-jitter; 

nominal-grant-interval nominal-grant-interval; 

description description; 
}

To configure a DOCSIS action:

  1. From configuration mode, enter the DOCSIS action configuration. For example, in this procedure, DOCSISParameter is the name of the DOCSIS action.
  2. user@host# edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter 
    
    
    
  3. 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.

[edit policies group pcmm list DocsisParameter rule in docsis-param 
DOCSISParameter]
user@host# set service-flow-type service-flow-type 

  1. (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.
  2. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set traffic-priority traffic-priority 
    
    
    
  3. (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.
  1. (Optional) Configure the maximum sustained rate at which traffic can operate over the service flow.
  2. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set maximum-sustained-rate maximum-sustained-rate 
    
    
    
  3. (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.
  4. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set maximum-traffic-burst maximum-traffic-burst 
    
    
    
  5. (Optional) Configure the guaranteed minimum rate that is reserved for the service flow.
  6. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set minimum-reserved-rate minimum-reserved-rate 
    
    
    
  7. (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.
  8. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set assumed-minimum-res-packet-size 
    assumed-minimum-res-packet-size 
    
    
    
  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. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set maximum-latency maximum-latency 
    
    
    
  11. (Optional) Configure the nominal interval between successive unicast request opportunities for this service flow.
  12. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set nominal-polling-interval nominal-polling-interval 
    
    
    
  13. (Optional) Configure the maximum amount of time that unicast request intervals can be delayed beyond the nominal polling interval.
  14. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set tolerated-poll-jitter tolerated-poll-jitter 
    
    
    
  15. (Optional) Configure the size of the individual data grants provided to the service flow.
  16. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set grant-size grant-size 
    
    
    
  17. (Optional) Configure the actual number of data grants given to the service flow during each nominal grant interval.
  18. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set grants-per-interval grants-per-interval 
    
    
    
  19. (Optional) Configure the maximum amount of time that the transmission opportunities can be delayed beyond the nominal grant interval.
  20. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set tolerated-grant-jitter tolerated-grant-jitter 
    
    
    
  21. (Optional) Configure the nominal interval between successive unsolicited data grant opportunities for this service flow.
  22. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set nominal-grant-interval nominal-grant-interval 
    
    
    
  23. (Optional) Enter a description for the filter action.
  24. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# set description description 
    
    
    
  25. (Optional) Verify the DOCSIS action configuration.
  26. [edit policies group pcmm list DocsisParameter rule in docsis-param 
    DOCSISParameter]
    
    user@host# show 
    
    service-flow-type action;
    
    traffic-priority 1;
    
    request-transmission-policy 1;
    
    maximum-sustained-rate 1500;
    
    maximum-traffic-burst 3044;
    
    minimum-reserved-rate 1240;
    
    assumed-minimum-res-packet-size 124;
    
    description "DOCSIS parameter action with a parameter service flow 
    scheduling type";
    

Configuring Filter Actions

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

Use the following configuration statement to configure a filter action:

policies group name list name rule name filter name {
description description; 
}

To configure a filter action:

  1. From configuration mode, enter the filter action configuration. For example, in this procedure, fa is the name of the filter action.
  2. user@host# edit policies group junos_filter list in rule pr filter fa 
    
    
    
  3. (Optional) Enter a description for the filter action.
  4. [edit policies group junos_filter list in rule pr filter fa]
    
    user@host# set description description 
    
    
    
  5. (Optional) Verify the filter action configuration.
  6. [edit policies group junos_filter list in rule pr filter fa]
    
    user@host# show 
    
    description "Filter action for JUNOS policies";
    

Configuring FlowSpec Actions

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.

Use the following configuration statements to configure FlowSpec actions:

policies group name list name rule name flow-spec name {
service-type service-type; 

token-bucket-rate token-bucket-rate; 

token-bucket-size token-bucket-size; 

peak-data-rate peak-data-rate; 

minimum-policed-unit minimum-policed-unit; 

maximum-packet-size maximum-packet-size; 

rate rate; 

slack-term slack-term; 

description description; 
}

To configure a FlowSpec action:

  1. From configuration mode, enter the FlowSpec action configuration. For example in this procedure, fsa is the name of the FlowSpec action.
  2. user@host# edit policies group pcmm list TrafficProfileFlowSpec rule pr 
    flow-spec fsa 
    
    
    
  3. (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:
  1. (Optional TSpec parameter) Configure the guaranteed minimum rate that is reserved for the service flow.
  2. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set token-bucket-rate token-bucket-rate 
    
    
    
  3. (Optional TSpec parameter) Configure the maximum burst size for the service flow.
  4. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set token-bucket-size token-bucket-size 
    
    
    
  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. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set peak-data-rate peak-data-rate 
    
    
    
  7. (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.
  8. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set minimum-policed-unit minimum-policed-unit 
    
    
    
  9. (Optional TSpec parameter) Configure the maximum packet size for the FlowSpec.
  10. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set maximum-packet-size maximum-packet-size 
    
    
    
  11. (Optional RSpec parameter) Configure the average rate.
  12. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set rate rate 
    
    
    
  13. (Optional RSpec parameter) Configure the amount of slack in the bandwidth reservation that can be used without redefining the reservation.
  14. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set slack-term slack-term 
    
    
    
  15. (Optional) Configure a description for the FlowSpec action.
  16. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# set description description 
    
    
    
  17. (Optional) Verify the FlowSpec action configuration.
  18. [edit policies group pcmm list TrafficProfileFlowSpec rule pr flow-spec fsa]
    
    user@host# show 
    
    service-number guaranteed_service;
    
    token-bucket-rate bucketRate;
    
    token-bucket-size bucketDepth;
    
    peak-data-rate peakRate;
    
    minimum-policed-unit minPolicedUnit;
    
    rate reservedRate;
    
    slack-term slackTerm;
    
    description "FlowSpec guaranteed service";
    

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.

Use the following configuration statement to configure forward actions:

policies group name list name rule name forward name {
description description; 
}

To configure a forward action:

  1. From configuration mode, enter the forward action configuration. For example, in this procedure, fwdAction is the name of the forward action.
  2. user@host# edit policies group junose list forward rule pr forward fwdAction 
    
    
    
  3. (Optional) Enter a description for the forward action.
  4. [edit policies group junose list forward rule pr forward fwdAction]
    
    user@host# set description description 
    
    
    
  5. (Optional) Verify the forward action configuration.
  6. [edit policies group junose list forward rule pr forward fwdAction]
    
    user@host# show 
    
    description "JUNOS Forward Action";
    

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.

Use the following configuration statements to configure a forwarding class action:

policies group name list name rule name forwarding-class name {
forwarding-class forwarding-class; 

description description; 
}

To configure a forwarding class action:

  1. From configuration mode, enter the forwarding class action configuration. For example, in this procedure, fca is the name of the forwarding class action.
  2. user@host# edit policies group bod list input rule pr forwarding-class fca 
    
    
    
  3. (Optional) Configure the name of the forwarding class assigned to packets.
  4. [edit policies group bod list input rule pr forwarding-class fca]
    
    user@host# set forwarding-class forwarding-class 
    
    
    
  5. (Optional) Enter a description for the forwarding class action.
  6. [edit policies group bod list input rule pr forwarding-class fca]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the forwarding class action configuration.
  8. [edit policies group bod list input rule pr forwarding-class fca]
    
    user@host# show 
    
    forwarding-class fc_expedited;
    
    description "Expedited forwarding class";
    

Configuring GateSpec Actions

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

Use the following configuration statements to configure GateSpec actions:

policies group name list name rule name gate-spec name {
session-class-id-priority session-class-id-priority; 

session-class-id-preemption session-class-id-preemption; 

session-class-id-configurable session-class-id-configurable; 

description description; 
}

To configure a GateSpec action:

  1. From configuration mode, enter the GateSpec action configuration. For example, in this procedure, gsa is the name of the GateSpec action.
  2. user@host# edit policies group pcmm list GateSpec rule pr gate-spec gsa 
    
    
    
  3. (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.
  4. [edit policies group pcmm list GateSpec rule pr gate-spec gsa]
    
    user@host# set session-class-id-priority session-class-id-priority 
    
    
    
  5. (Optional) Configure the preemption bit in the session class ID. Use the preemption bit to allocate bandwidth to lower-priority sessions.
  6. [edit policies group pcmm list GateSpec rule pr gate-spec gsa]
    
    user@host# set session-class-id-preemption session-class-id-preemption 
    
    
    
  7. (Optional) Configure the configurable bit in the session class ID.
  8. [edit policies group pcmm list GateSpec rule pr gate-spec gsa]
    
    user@host# set session-class-id-configurable session-class-id-configurable 
    
    
    
  9. (Optional) Enter a description for the GateSpec action.
  10. [edit policies group pcmm list GateSpec rule pr gate-spec gsa]
    
    user@host# set description description 
    
    
    
  11. (Optional) Verify the GateSpec action configuration.
  12. [edit policies group pcmm list GateSpec rule pr gate-spec gsa]
    
    user@host# show 
    
    session-class-id-priority 5;
    
    session-class-id-preemption 0;
    
    session-class-id-configurable 5
    

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.

Use the following configuration statements to configure loss priority actions:

policies group name list name rule name loss-priority name {
loss-priority loss-priority; 

description description; 
}

To configure a loss priority action:

  1. From configuration mode, enter the loss priority action configuration. For example, in this procedure, lpa is the name of the loss priority action.
  2. user@host# edit policies group junos list lossPriority rule pr loss-priority lpa 
    
    
    
  3. (Optional) Configure the packet loss priority.
  4. [edit policies group junos list lossPriority rule pr loss-priority lpa]
    
    user@host# set loss-priority loss-priority 
    
    
    
  5. (Optional) Enter a description for the loss priority action.
  6. [edit policies group junos list lossPriority rule pr loss-priority lpa]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the loss priority action configuration.
  8. [edit policies group junos list lossPriority rule pr loss-priority lpa]
    
    user@host# show 
    
    loss-priority high_priority;
    
    description "Loss Priority set to high";
    

Configuring Mark Actions

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

Use the following configuration statements to configure a mark action:

policies group name list name rule name mark name {
description description; 
}

policies group name list name rule name mark name info {
value value; 

mask mask; 
}

To configure a mark action:

  1. From configuration mode, enter the mark action configuration. For example, in this procedure, markAction is the name of the mark action.
  2. user@host# edit policies group junose list mark rule pr mark markAction 
    
    
    
  3. (Optional) Enter a description for the mark action.
  4. [edit policies group junose list mark rule pr mark markAction]
    
    user@host# set description description 
    
    
    
  5. (Optional) Configure the mark value.
  6. [edit policies group junose list mark rule pr mark markAction]
    
    user@host# set info value value 
    
    
    
  7. (Optional) Configure the mark mask.
  8. [edit policies group junose list mark rule pr mark markAction]
    
    user@host# set info mask mask 
    
    
    
  9. (Optional) Verify the mark action configuration.
  10. [edit policies group junose list mark rule pr mark markAction]
    
    user@host# show 
    
    info {
    
      mark-value 10;
    
      mask 255;
    
    }
    
    description "Mark action";
    

Configuring NAT Actions

You can configure NAT actions for JUNOS ASP policy rules.

Use the following configuration statements to configure NAT actions:

policies group name list name rule name nat name {
translation-type translation-type; 

description description; 
}

policies group name list name rule name nat name port {
from-port from-port; 
}

policies group name list name rule name nat name ip-network group-network {
network-specifier network-specifier; 
}

To configure a NAT action:

  1. From configuration mode, enter the NAT action configuration. For example, in this procedure, natAction is the name of the NAT action.
  2. user@host# edit policies group junos list nat rule pr nat natAction
    
    
    
  3. (Optional) Configure the type of network address translation that is used.
  4. [edit policies group junos list nat rule pr nat natAction]
    
    user@host# set translation-type translation-type 
    
    
    
  5. (Optional) Enter a description for the NAT action.
  6. [edit policies group junos list nat rule pr nat natAction]
    
    user@host# set description description 
    
    
    
  7. (Optional) Configure the port range to restrict port translation when the NAT translation type is configured in dynamic-source mode.
  8. [edit policies group junos list nat rule pr nat natAction]
    
    user@host# set port from-port from-port 
    
    
    
  9. (Optional) Configure the IP address ranges.
  10. [edit policies group junos list nat rule pr nat natAction]
    
    user@host# set ip-network group-network network-specifier network-specifier 
    
    
    
  11. (Optional) Verify the NAT action configuration.
  12. [edit policies group junos list nat rule pr nat natAction]
    
    user@host# show 
    
    translation-type "source dynamic";
    
    ip-network {
    
      group-network {
    
        network-specifier 192.168.1.100/32;
    
      }
    
    }
    
    port { 
    
      from-port 2010..2020;
    
    }
    

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.

Use the following configuration statements to configure the next-hop action.

policies group name list name rule name next-hop name {
next-hop-address next-hop-address; 

description description; 
}

To configure a next-hop action:

  1. From configuration mode, enter the next-hop action configuration. For example, in this procedure, nha is the name of the next-hop action.
  2. user@host# edit policies group junose list nexthop-to-ssp rule to-ssp next-hop 
    nha 
    
    
    
  3. (Optional) Configure the next IP address where the classified packets should go.
  4. [edit policies group junose list nexthop-to-ssp rule to-ssp next-hop nha]
    
    user@host# set next-hop-address next-hop-address 
    
    
    
  5. (Optional) Enter a description for the next-hop action.
  6. [edit policies group junose list nexthop-to-ssp rule to-ssp next-hop nha]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the next-hop action configuration.
  8. [edit policies group junose list nexthop-to-ssp rule to-ssp next-hop nha]
    
    user@host# show 
    
    next-hop-address virtual_ipAddress;
    
    description "Next hop action";
    

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.

Use the following configuration statements to configure next-interface actions:

policies group name list name rule name next-interface name {
interface-specifier interface-specifier; 

next-hop-address next-hop-address; 

description description; 
}

To configure a next-interface action:

  1. From configuration mode, enter the next-interface action configuration. For example, in this procedure, nextInterface is the name of the next-interface action.
  2. user@host# edit policies group redirect list input rule redirect next-interface 
    nextInterface 
    
    
    
  3. (Optional) Configure the IP interface to be used as the next interface for packets.
  4. [edit policies group redirect list input rule redirect next-interface nextInterface]
    
    user@host# set interface-specifier interface-specifier 
    
    
    
  5. (Optional) Configure the next IP address where the classified packets should go. This option is available only in JUNOSe policy rules.
  6. [edit policies group redirect list input rule redirect next-interface nextInterface]
    
    user@host# set next-hop-address next-hop-address 
    
    
    
  7. (Optional) Enter a description for the next-interface action.
  8. [edit policies group redirect list input rule redirect next-interface nextInterface]
    
    user@host# set description description 
    
    
    
  9. (Optional) Verify the next-interface action configuration.
  10. [edit policies group redirect list input rule redirect next-interface 
    nextInterface]
    
    user@host# show 
    
    interfaceSpec "name='fastethernet3/0'";
    
    next-hop-address 10.10.227.3;
    
    description "Next-interface action for redirect policy";
    

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.

Use the following configuration statement to configure next-rule actions.

policies group name list name rule name next-rule name {
description description; 
}

To configure a next-rule action:

  1. From configuration mode, enter the next-rule action configuration. For example, in this procedure, nra is the name of the next-rule action.
  2. user@host# edit policies group junos list filter rule next next-rule nra 
    
    
    
  3. (Optional) Enter a description for the next-rule action.
  4. [edit policies group junos list filter rule next next-rule nra]
    
    user@host# set description description 
    
    
    
  5. (Optional) Verify the next-rule action configuration.
  6. [edit policies group junos list filter rule next next-rule nra]
    
    user@host# show configuration policies group junos list filter rule next 
    next-rule nra 
    
    description "Next-rule action";
    
    
    

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.

Use the following configuration statements to configure policer actions:

policies group name list name rule name policer name {
bandwidth-limit bandwidth-limit; 

bandwidth-limit-unit bandwidth-limit-unit; 

burst burst; 

description description; 
}

To configure a policer action:

  1. From configuration mode, enter the policer action configuration. For example, in this procedure, pa is the name of the policer action.
  2. user@host# edit policies group junos list firewallFilterPolicer rule pr policer pa 
    
    
    
  3. (Optional) Configure the traffic rate that, if exceeded, causes the router to take the indicated packet action.
  4. [edit policies group junos list firewallFilterPolicer rule pr policer pa]
    
    user@host# set bandwidth-limit bandwidth-limit 
    
    
    
  5. (Optional) Configure the type of value entered for bandwidth limit.
  6. [edit policies group junos list firewallFilterPolicer rule pr policer pa]
    
    user@host# set bandwidth-limit-unit bandwidth-limit-unit 
    
    
    
  7. (Optional) Configure the maximum burst size. The minimum recommended value is the maximum transmission unit (MTU) of the IP packets being policed.
  8. [edit policies group junos list firewallFilterPolicer rule pr policer pa]
    
    user@host# set burst burst 
    
    
    
  9. (Optional) Enter a description for the policer action.
  10. [edit policies group junos list firewallFilterPolicer rule pr policer pa]
    
    user@host# set description description 
    
    
    
  11. (Optional) Verify the policer action configuration.
  12. [edit policies group junos list firewallFilterPolicer rule pr policer pa]
    
    user@host# show 
    
    bandwidth-limit 1048576;
    
    bandwidth-limit-unit bps;
    
    burst 15000;
    

Configuring the Packet Action for the Policer Action

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

Use the following configuration statements to configure a packet action:

policies group name list name rule name policer name packet-action name ...

policies group name list name rule name policer name packet-action name 
forwarding-class {
forwarding-class forwarding-class; 
}

policies group name list name rule name policer name packet-action name loss-priority 
{
loss-priority loss-priority; 
}

policies group name list name rule name policer name packet-action name parameter {
action 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. user@host# edit policies group junos list firewallFilterPolicer rule pr policer pa 
    packet-action pktAction 
    
    
    
  3. (Optional) Configure the action to take on packets that exceed the bandwidth limit configured in the policer action.
  1. (Optional) Verify the policer action configuration.
  2. [edit policies group junos list firewallFilterPolicer rule pr policer pa 
    packet-action pktAction parameter]
    
    user@host# show 
    
    packet-action pktAction {
    
      parameter {
    
        action PolicyParameterAction;
    
      }
    
    }
    
    bandwidth-limit 1048576;
    
    bandwidth-limit-unit bps;
    
    burst 15000;
    

Configuring QoS Profile Attachment Actions

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 SRC-PE Solutions Guide, Chapter 1, Managing Tiered and Premium Services with QoS on JUNOSe Routers with the SRC CLI.

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.

Use the following configuration statements to configure QoS profile attachment actions:

policies group name list name rule name qos-attach name {
qos-profile qos-profile; 
qos-parameters qos-parameters; 
description description; 
}

To configure a QoS profile attachment action:

  1. From configuration mode, enter the QoS profile attachment action configuration. For example, in this procedure, qos_vod is the name of the QoS profile attachment action.
  2. user@host# edit policies group junose list qos rule input qos-attach qos_vod 
    
    
    
  3. Configure the name of the QoS profile to attach to the JUNOSe interface when this action is taken.
  4. [edit policies group junose list qos rule input qos-attach qos_vod]
    
    user@host# set qos-profile qos-profile 
    
    
    
  5. (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.
  6. [edit policies group junose list qos rule input qos-attach qos_vod]
    
    user@host# set qos-parameters qos-parameters 
    
    
    
  7. (Optional) Enter a description for the QoS profile attachment action.
  8. [edit policies group junose list qos rule input qos-attach qos_vod]
    
    user@host# set description description 
    
    
    
  9. (Optional) Verify the QoS profile attachment action configuration.
  10. [edit policies group junose list qos rule input qos-attach qos_vod]
    
    user@host# show 
    
    qos-profile qp-vod-1024;
    
    description "Action for QoS video-on-demand";
    

Configuring Rate-Limit Actions

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

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

policies group name list name rule name rate-limit name {
type type; 

committed-rate committed-rate; 

committed-burst committed-burst; 

peak-rate peak-rate; 

peak-burst peak-burst; 

excess-burst excess-burst; 

description description; 
}

policies group name list name rule name rate-limit name committed-action mark 
mark-info {
value value; 

mask mask; 
}

policies group name list name rule name rate-limit name committed-action parameter {
action action; 
}

policies group name list name rule name rate-limit name conformed-action mark 
mark-info {
value value; 

mask mask; 
}

policies group name list name rule name rate-limit name conformed-action parameter {
action action; 
}

policies group name list name rule name rate-limit name exceed-action mark mark-info {
value value; 

mask mask; 
}

policies group name list name rule name rate-limit name exceed-action parameter {
action action; 
}

To configure a rate-limit action:

  1. From configuration mode, enter the rate-limit action configuration. For example, in this procedure, rla is the name of the rate-limit action.
  2. user@host# edit policies group junose list rate-limiter rule pr rate-limit rla 
    
    
    
  3. (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.
  4. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set type type 
    
    
    
  5. (Optional) Configure the target rate for the traffic that the policy covers.
  6. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set committed-rate committed-rate 
    
    
    
  7. (Optional) Configure the amount of bandwidth allocated to burst traffic in bytes.
  8. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set committed-burst committed-burst 
    
    
    
  9. (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to excess traffic flow over the committed rate.
  10. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set peak-rate peak-rate 
    
    
    
  11. (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to burst traffic in excess of the peak rate.
  12. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set peak-burst peak-burst 
    
    
    
  13. (Optional) For one-rate rate-limit profiles, specify the amount of bandwidth allocated to accommodate burst traffic.
  14. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set excess-burst excess-burst 
    
    
    
  15. (Optional) Enter a description for the rate-limit action.
  16. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# set description description 
    
    
    
  17. (Optional) Configure the rate-limit action for traffic flows that do not exceed the committed rate to one of the following:
  1. (Optional) Configure the rate-limit action for traffic flows that exceed the committed rate but remain below the peak rate to one of the following:
  1. (Optional) Configure the rate-limit action for traffic flows exceed the peak rate to one of the following:
  1. (Optional) Return to the rate-limit action configuration, and verify the configuration.
  2. [edit policies group junose list rate-limiter rule pr rate-limit rla]
    
    user@host# show 
    
    committed-action { 
    
      forward {
    
      }
    
    }
    
    conformed-action {
    
      forward {
    
      }
    
    }
    
    exceed-action {
    
      filter {
    
      }
    
    }
    
    type 1;
    
    committed-rate 1000000;
    
    committed-burst 125000;
    
    excess-burst 312500;
    

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.

Use the following configuration statements to configure reject actions:

policies group name list name rule name reject name {
message-type message-type; 

description description; 
}

To configure a reject action:

  1. From configuration mode, enter the reject action configuration. For example, in this procedure, rejectAction is the name of the reject action.
  2. user@host# edit policies group junos list filter rule rejectRule reject rejectAction 
    
    
    
  3. (Optional) Configure the type of ICMP destination unreachable message sent to the client.
  4. [edit policies group junos list filter rule rejectRule reject rejectAction]
    
    user@host# set message-type message-type 
    
    
    
  5. (Optional) Enter a description for the reject action.
  6. [edit policies group junos list filter rule rejectRule reject rejectAction]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the reject action configuration.
  8. [edit policies group junos list filter rule rejectRule reject rejectAction]
    
    user@host# show 
    
    message-type network-prohibited;
    
    description "Reject action in JUNOS filter policy";
    

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.

Use the following configuration statements to configure routing instance actions:

policies group name list name rule name routing-inst name {
routing-instance routing-instance; 

description description; 
}

To configure a routing instance action:

  1. From configuration mode, enter the routing instance action configuration. For example, in this procedure, ria is the name of the routing instance action.
  2. user@host# edit policies group junos list bodVpn rule pr routing-inst ria 
    
    
    
  3. (Optional) Configure the routing instance to which packets are forwarded. The routing instance must be configured on the router.
  4. [edit policies group junos list bodVpn rule pr routing-inst ria]
    
    user@host# set routing-instance routing-instance 
    
    
    
  5. (Optional) Enter a description for the reject action.
  6. [edit policies group junos list bodVpn rule pr routing-inst ria]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the routing instance action configuration.
  8. [edit policies group junos list bodVpn rule pr routing-inst ria]
    
    user@host# show 
    
    routing-instance isp2-route-table;
    
    description "Routing Instance Action";
    

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.

Use the following configuration statements to configure scheduler actions:

policies group name list name rule name scheduler-action name {
buffer-size buffer-size; 

buffer-size-unit buffer-size-unit; 

priority priority; 

transmit-rate transmit-rate; 

transmit-rate-unit transmit-rate-unit; 

exact exact; 

description description; 
}

To configure a scheduler action:

  1. From configuration mode, enter the scheduler action configuration. For example, in this procedure, sa is the name of the scheduler action.
  2. user@host# edit policies group junos list qos rule pr scheduler-action sa 
    
    
    
  3. (Optional) Configure the queue transmission buffer size.
  4. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set buffer-size buffer-size 
    
    
    
  5. (Optional) Configure the type of value that you entered for buffer size.
  6. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set buffer-size-unit buffer-size-unit 
    
    
    
  7. (Optional) Configure the packet-scheduling priority. The priority determines the order in which an output interface transmits traffic from the queues.
  8. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set priority priority 
    
    
    
  9. (Optional) Configure the transmit rate.
  10. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set transmit-rate transmit-rate 
    
    
    
  11. (Optional) Configure the type of value entered for transmit rate.
  12. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set transmit-rate-unit transmit-rate-unit 
    
    
    
  13. (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.
  14. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set exact exact 
    
    
    
  15. (Optional) Enter a description for the scheduler action.
  16. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# set description description 
    
    
    
  17. (Optional) Verify the scheduler action configuration.
  18. [edit policies group junos list qos rule pr scheduler-action sa]
    
    user@host# show 
    
    buffer-size 85;
    
    buffer-size-unit buffer_size_percentage;
    
    priority low;
    
    transmit-rate 10485760;
    
    transmit-rate-unit rate_in_bps;
    
    description "Scheduler action for logical interface scheduling";
    

Configuring Drop Profiles

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 routing platform documentation.

Use the following configuration statements to configure drop profiles:

policies group name list name rule name scheduler-action name drop-profile name {
loss-priority loss-priority; 

protocol protocol; 

drop-probability drop-probability; 

drop-profile-type drop-profile-type; 

queue-threshold queue-threshold; 
}


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. user@host# edit policies group junos list qosWithDropProfile rule pr 
    scheduler-action sa drop-profile drop1 
    
    
    
  3. Configure the loss priority.
  4. [edit policies group junos list qosWithDropProfile rule pr scheduler-action sa 
    drop-profile drop1]
    
    user@host# set loss-priority loss-priority 
    
    
    
  5. Configure the protocol type.
  6. [edit policies group junos list qosWithDropProfile rule pr scheduler-action sa 
    drop-profile drop1]
    
    user@host# set protocol protocol 
    
    
    
  7. Configure the relationship between the fill level and drop probability.
  8. [edit policies group junos list qosWithDropProfile rule pr scheduler-action sa 
    drop-profile drop1]
    
    user@host# set drop-profile-type drop-profile-type 
    
    
    
  9. Configure the probability that a packet will be dropped.
  10. [edit policies group junos list qosWithDropProfile rule pr scheduler-action sa 
    drop-profile drop1]
    
    user@host# set drop-probability drop-probability 
    
    
    
  11. Configure the fill level of the queue.
  12. [edit policies group junos list qosWithDropProfile rule pr scheduler-action sa 
    drop-profile drop1]
    
    user@host# set queue-threshold queue-threshold 
    
    
    
  13. (Optional) Verify the drop profile configuration.
  14. [edit policies group junos list qosWithDropProfile rule pr scheduler-action 
    sa drop-profile drop1]
    
    user@host# show 
    
    loss-priority high_priority;
    
    protocol any_protocol;
    
    drop-probability "[75, 100]";
    
    drop-profile-type interpolated;
    
    queue-threshold "[50, 80]";
    

Configuring Service Class Name Actions

You can configure service class name actions for PCMM policy rules. Use the following configuration statements to configure service class name actions:

policies group name list name rule name service-class-name name {
service-class-name service-class-name; 

description description; 
}

To configure a service class name action:

  1. From configuration mode, enter the service class name action configuration. For example, in this procedure, scna is the name of the service class name action.
  2. user@host# edit policies group pcmm list serviceClass rule pr 
    service-class-name scna 
    
    
    
  3. (Optional) Configure the name of a service class on the CMTS device that specifies QoS parameters for a service flow.
  4. [edit policies group pcmm list serviceClass rule pr service-class-name scna]
    
    user@host# set service-class-name service-class-name 
    
    
    
  5. (Optional) Enter a description for the service class name action.
  6. [edit policies group pcmm list serviceClass rule pr service-class-name scna]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the service class name action configuration.
  8. [edit policies group pcmm list serviceClass rule pr service-class-name scna]
    
    user@host# show configuration policies group pcmm list serviceClass rule pr 
    service-class-name scna 
    
    service-class-name scn_up;
    
    description "Service class name action for pcmm service class policy.";
    

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.

Use the following configuration statements to configure stateful firewall actions:

policies group name list name rule name stateful-firewall name {
description description; 
}

policies group name list name rule name stateful-firewall name packet-action reject {
message-type message-type; 
}

policies group name list name rule name stateful-firewall name packet-action 
parameter {
action action; 
}

To configure a stateful firewall action:

  1. From configuration mode, enter the stateful firewall action configuration. For example, in this procedure, sfa is the name of the stateful firewall action.
  2. user@host# edit policies group junos list sfw rule pr stateful-firewall sfa 
    
    
    
  3. (Optional) Set the action to take on a packet to one of the following:
  1. (Optional) Enter a description for the stateful firewall action.
  2. [edit policies group junos list sfw rule pr stateful-firewall sfa]
    
    user@host# set description description 
    
    
    
  3. (Optional) Verify the stateful firewall action configuration.
  4. [edit policies group junos list sfw rule pr stateful-firewall sfa]
    
    user@host# show 
    
    packet-action {
    
      reject {
    
        message-type administratively-prohibited;
    
      }
    
    }
    
    description "Stateful firewall 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.

Use the following configuration statement to configure traffic-class actions:

policies group name list name rule name traffic-class name {
traffic-class traffic-class; 

description description; 
}

To configure a traffic-class action:

  1. From configuration mode, enter the traffic-class configuration. For example, in this procedure, tca is the name of the traffic-class action.
  2. user@host# edit policies group junose list class rule pr traffic-class tca 
    
    
    
  3. (Optional) Configure the name of the traffic-class profile that is applied to a packet when it passes through the router.
  4. [edit policies group junose list class rule pr traffic-class tca]
    
    user@host# set traffic-class traffic-class 
    
    
    
  5. (Optional) Enter a description for the traffic-class action.
  6. [edit policies group junose list class rule pr traffic-class tca]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the traffic-class action configuration.
  8. [edit policies group junose list class rule pr traffic-class tca]
    
    user@host# show 
    
    traffic-class TCent;
    
    description "Traffic class action";
    

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 for JUNOS filter 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:

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

policies group name list name rule name traffic-mirror name {
description description; 
}

To configure a traffic-mirror action:

  1. From configuration mode, enter the traffic-mirror configuration. For example, in this procedure, fromSubnets is the name of the traffic-mirror action.
  2. user@host# edit policies group junos list mirror rule pr traffic-mirror fromSubnets 
    
    
    
  3. (Optional) Enter a description for the traffic-mirror action.
  4. [edit policies group junos list mirror rule pr traffic-mirror fromSubnets]
    
    user@host# set description description 
    
    
    
  5. (Optional) Verify the traffic-mirror action configuration.
  6. [edit policies group junos list mirror rule pr traffic-mirror fromSubnets]
    
    user@host# show 
    
    description "Traffic mirroring action for subnet.";
    

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.

Use the following configuration statements to configure traffic-shape actions:

policies group name list name rule name traffic-shape name {
rate rate; 

description description; 
}

To configure a traffic-shape action:

  1. From configuration mode, enter the traffic-shape configuration. For example, in this procedure, tsa is the name of the traffic-shape action.
  2. user@host# edit policies group junos list trafficShaping rule shaping 
    traffic-shape tsa 
    
    
    
  3. (Optional) Configure the maximum transmission rate.
  4. [edit policies group junos list trafficShaping rule shaping traffic-shape tsa]
    
    user@host# set rate rate 
    
    
    
  5. (Optional) Enter a description for the traffic-shape action.
  6. [edit policies group junos list trafficShaping rule shaping traffic-shape tsa]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the traffic-shape action configuration.
  8. [edit policies group junos list trafficShaping rule shaping traffic-shape 
    tsa]
    
    user@host# show 
    
    rate 10200000;
    
    description "Traffic-shaping action";
    

Configuring User Packet Class Actions

Use this action to put packets in a particular user packet class. You can configure user packet class actions for JUNOSe IPv6 policy rules.

Use the following configuration statement to configure user packet class actions:

policies group name list name rule name user-packet-class name {
user-packet-class user-packet-class; 

description description; 
}

To configure a user packet class action:

  1. From configuration mode, enter the user packet class configuration. For example, in this procedure, upca is the name of the user packet class action.
  2. user@host# edit policies group junose list class rule pr user-packet-class upca 
    
    
    
  3. (Optional) Configure the user packet class that is applied to a packet when it passes through the router.
  4. [edit policies group junose list class rule pr user-packet-class upca]
    
    user@host# set user-packet-class user-packet-class 
    
    
    
  5. (Optional) Enter a description for the user packet class action.
  6. [edit policies group junose list class rule pr user-packet-class upca]
    
    user@host# set description description 
    
    
    
  7. (Optional) Verify the user packet class action configuration.
  8. [edit policies group junose list class rule pr user-packet-class upca]
    
    user@host# show 
    
    user-packet-class 5;
    
    description "User packet class action";
    


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