Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring the PTSP Forwarding Instance

Before you can forward PTSP traffic, perform these tasks for each forwarding instance:

1. Configure each PTSP forwarding instance as a routing instance type of forwarding.
2. Configure a firewall filter with an action that specifies the routing instance configured in Step 1.
3. Configure the unit number for the Multiservices interface that specifies the filter configured in Step 2 as the input filter.

   Note: To avoid service set dependency on specific unit numbers, use the same unit number across all Multiservices interfaces where PTSP services are applied.

4. Configure the PTSP forward rule to specify the forwarding instance.

   Note: When the forwarding instance action is performed on the flow, any postservice filters are not applied to the underlying interface.

If you want to forward traffic for PTSP subscribers, you must specify the forwarding instance for specific subscribers based on IP address, network, or prefix list. The match direction for forward rules is always input.

1. Specify the PTSP forward rule that you want to use when configuring a PTSP forwarding instance.
   [edit services ptsp]user@host# edit forward-rule ptspForward
2. Set the term precedence for the forward rule. Term with lowest precedence is evaluated first.
   [edit services ptsp forward-rule ptspForward]user@host# edit term 5
3. Configure the match conditions for the IP address, address range, or prefix list. See Table 1.
   [edit services ptsp forward-rule ptspForward term 5]user@host# set from local-address 200.0.0.1

   Table 1: PTSP Forward Rule Match Conditions

   Match Condition	Description
   application-groups [ application-group-name ]	Application group name defined in the application identification configuration.
   applications	Application name defined in the application identification configuration.
   local-address (address | any-unicast)	Local IP address. IPv4 only.
   local-address-range low low-value high high-value	Local address range. IPv4 only.
   local-prefix-list prefix-list-name	Prefixes in the specified list.

   Note: You can specify match conditions for applications or application groups that support application identification (APPID) services, but we do not recommend specifying the forwarding instance action when you are using these match conditions in PTSP policies. In this situation, some network topologies may route packets in a manner that causes the flow to be dropped. For example, the APPID services might forward some packets on the default routing instance while the PTSP services forward other packets in the same flow to another routing instance.

4. Configure the forwarding instance action with the routing instance name and the unit number.
   [edit services ptsp forward-rule ptspForward term 5]user@host# set then forwarding-instance less-effort-ri 144

   Note: When the forwarding instance action is performed on the flow, any postservice filters are not applied to the underlying interface.