Got it

Policy-Based Routing (PBR)

Latest reply: Dec 22, 2018 03:34:42 2106 5 1 0 0

Overview of PBR

Different from the routing table mechanism, the Policy-Based Routing (PBR) mechanism selects routes based on the customized policy, but not the routing table.

 

Using PBR, the FW selects routes based on the customized policies and not based on the routing table and forwards packets based on attributes, such as the incoming interface, source security zone, source and destination IP addresses, user, service type, and application type.  PBR takes priority over, but does not take place of the routing table mechanism. PBR provides guidance for forwarding the traffic of certain services.

PBR Components

A PBR rule consists of matching conditions and an action. The FW supports the following matching conditions:

The same as a Traffic Policy

  • Source security zone
  • Incoming interface
  • IP address or MAC address
  • User
  • Service type
  • Application
  • DSCP Value

 

The forwarding action of the PBR rule is implemented on the traffic only when the traffic matches all matching conditions.

 

The FW:

  • If PBR exist, implements PBR.
  • If not forward based on the existing routing table.

PBR Rule Matching Sequence

The FW will look up the first rule based on the matching sequence.

If none PBR rule is matched, the FW forwards packets based on the route table.

 

When the policy-based route specifies single egress and the next hop or outbound interface is unreachable, the FW discards the packet.

To enhance reliability, configure the FW to monitor the reachability of the next hop If the next hop is unreachable, the FW looks up the routing table to avoid packet loss.

Precautions

PBR-based intelligent uplink selection cannot be used together with the IP spoofing attack defense or URPF function

Configuring PBR Using the Web UI

  1. Choose Network > Route > Intelligent Uplink Selection.

 

  1. Click the Policy Route tab, then click Add.

 

  1. Set the name and description of the PBR rule.


Policy-Based Routing (PBR)-2784715-1 

  1. Configure a tag for the policy.

The tag identifies and categorizes the policy.

 

  1. Set the matching conditions of the PBR rule.

 

  1. Set the action of the PBR rule.

 Policy-Based Routing (PBR)-2784715-2

Policy-Based Routing (PBR)-2784715-3

 

  1. Select the Egress Type

 

Policy-Based Routing (PBR)-2784715-4

 

Single Egress Mode

 

 

Policy-Based Routing (PBR)-2784715-5

Policy-Based Routing (PBR)-2784715-6

 

 

  1. Choose the selection mode from the list.

 

  1. Selection Mode is Load balancing based on link bandwidth

Use the Bandwidth of the links to choose the Outgoing Interface. Remember that Ethernet Interface Adjust their Bandwidth to match the current Speed but Serial Links need to configure manually the Bandwidth to match the real speed.

 

  1. Selection Mode is Load balancing based on link quality

Link quality indicators

When you set the link selection mode to load balancing by link quality, you can set one or more link quality parameters to evaluate the link quality. The FW supports three link quality parameters:

 

  • Packet loss ratio: Packet loss ratio is the default link quality parameter. After sending multiple probe packets, the FW counts the number of dropped packets and calculates the packet loss ratio. The packet loss ratio is the number of reply packets divided by the number of probe packets. Packet loss ratio is a decisive parameter to evaluate link quality.

 

  • Delay: Subtracting the probe sending time from the reply receiving time is the delay. The average delay of the N probe packets sent by the FW is the final delay.

 

  • Jitter: The absolute value of the difference between two adjacent probe delays is jitter. The average jitter of the N probe packets sent by the FW is the final jitter.

 

Detection Times

Number of link quality detection times.

Detection Interval

Interval at which link quality detection is performed.

Destination Subnet Mask Bits

Mask length of link quality detection.

Protocol

Protocol for health check. Different protocols are used in different probe mode.

 

  • Simple TCP: Indicates that TCP packets are used to check network connectivity. A link is considered available upon the reply to the first detection packet by the destination device, not completion of the three-way handshake.

 

  • ICMP: Sends ICMP probe packets.

 

3.  Selection Mode is Load balancing based on link weights

Weight

Weight of the member interface.

 

In intelligent uplink selection, the FW forwards traffic to different links based on the link weight ratio. Therefore, the link with a larger weight forwards more traffic, and the link with a smaller weight forwards less traffic.

 

  1. Selection Mode is Active/standby backup based on link priorities

Priority

Priority of the member interface.

 

A great priority value indicates a high priority.

 

 

  1. Enable Sticky Session in case it is need it

 

Sticky Session

With this function enabled, after traffic selects a link for the first time, the FW generates a corresponding sticky session entry.  The subsequent traffic is forwards through the outgoing interface recorded in the entry.

 

  • Disable: disables the sticky session function.

 

  • Source IP Address: based on source IP addresses. In this mode, traffic from one source IP address or network segment is forwarded through one outgoing interface.

 

  • Destination IP Address: based on destination IP addresses. In this mode, traffic to one destination IP address or network segment is forwarded through one outgoing interface.

 

  • Source IP & Destination IP Address: one source IP address  to one destination IP is forwarded through one outgoing interface.

 

 

 

  1. Select the Outgoing WAN Interface/Carrier/Interface Group

 

Follow-up Procedure

  1. If the policy-based route has multiple outbound interfaces and Selection Mode is set to Load balancing based on link quality, you can view the quality of each link in the link quality check table.
  2. Choose Network > Route > Intelligent Uplink Selection.
  3. On the Link Quality Check Table tab, click Refresh to view the latest information.

 

 

Operation

Command

Check the PBR configuration.

display policy-based-route rule { all [ slot slot-id cpu cpu-id ] | name rule-name }

display policy-based-route app-cache { all | { tcp | udp } ip-address port } [ slot slot-id cpu cpu-id ]

 

 

 Policy-Based Routing (PBR)-2784715-7


Policy-Based Routing (PBR)-2784715-8

Policy-Based Routing (PBR)-2784715-9 Policy-Based Routing (PBR)-2784715-10Policy-Based Routing (PBR)-2784715-11Policy-Based Routing (PBR)-2784715-12Policy-Based Routing (PBR)-2784715-13

 

 


This post was last edited by DiegoXD at 2018-10-24 14:02.

This article contains more resources

You need to log in to download or view. No account? Register

x

Usage Scenario

A routing policy is used to filter routes and set route attributes for the routes that match the routing policy. A routing policy consists of multiple nodes. One node can be configured with multiple if-match and applyclauses.

The if-match clauses define matching rules for this node, and the apply clauses define behaviors for the routes that match the rules. The relationship between if-match clauses is "AND". That is, a route must match all the if-match clauses. The relationship between the nodes of a routing policy is "OR". That is, if a route matches one node, the route matches the routing policy. If the route does not match any node, the route fails to match the routing policy.

You can run the display route-policy command to view the number of routes that match and do not match the routing policy.

Procedure

After a routing policy is created, the system prompts "Info: New Sequence of this List !" and displays the Route-Policy view. The system displays no prompt when a routing policy is deleted.

This post was last edited by Torrent at 2018-10-31 07:00.
View more
  • x
  • convention:

PBR feture is very useful for routing configuration, it can be configured based on IP address, policy, users, or interface, it is very flexible for change the routes, thanks for your sharing
View more
  • x
  • convention:

Need more tools
View more
  • x
  • convention:

Good idea
View more
  • x
  • convention:

Using PBR, the FW selects routes based on the customized policies and not based on the routing table and forwards packets based on attributes, such as the incoming interface, source security zone, source and destination IP addresses, user, service type, and application type. PBR takes priority over, but does not take place of the routing table mechanism. PBR provides guidance for forwarding the traffic of certain services.

thanks for sharing
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.