No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CLI-based Configuration Guide - IP Unicast Routing

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Local PBR

Local PBR

Local PBR applies only to locally generated packets, such as ping packets.

Local PBR on a device can have multiple local PBR nodes. Each local PBR node has a priority. The device attempts to match locally generated packets with rules bound with local PBR nodes in descending order of priority.

Implementation

When sending locally generated packets, a device attempts to match the packets with rules bound with local PBR nodes in descending order of priority. Local PBR supports rules based on access control list (ACL) and packet length.

  • If the device finds a matching local PBR node, it performs the following steps:
    1. Checks whether the priority of the packets has been set.

      • If so, the device applies the configured priority to the packets and continues with the next step.
      • If not, the device continues with the next step.
    2. Checks whether an outbound interface has been configured for local PBR.
      • If so, the device sends the packets through the outbound interface.
      • If not, the device continues with the next step.
    3. Checks whether next hops have been configured for local PBR.
      NOTE:

      Two next hops can be configured for load balancing.

      • If a next hop is configured for packet forwarding in PBR and the next hop is reachable, the device checks whether association between next hop and route is configured.

        • If association between next hop and route is configured, the device detects whether the configured IP address of the route associated with the next hop in PBR is reachable.
          • If the IP address is reachable, the configured next hop takes effect, and the device forwards packets to the next hop.
          • If the IP address is unreachable, the configured next hop does not take effect, and the device checks whether a backup next hop has been configured. If a backup next hop has been configured and is reachable, the device forwards packets to the backup next hop. If no backup next hop is configured or the configured backup next hop is unreachable, the device searches the routing table for a route according to the destination of packets. If no route is available, the device continues with the next step.
        • If association between next hop and route is not configured, the device sends packets to the next hop.
      • If a next hop is configured for packet forwarding in PBR and the next hop is reachable, the device sends packets to the next hop.
      • If the next hop is not configured, the device searches the routing table for a route based on the destination addresses of the packets. If no route is available, the device continues with the next step.
    4. Checks whether a default outbound interface has been configured for local PBR.
      • If so, the device sends the packets through the default outbound interface.
      • If not, the device continues with the next step.
    5. Checks whether default next hops have been configured for local PBR.
      • If so, the device sends the packets to the default next hops.
      • If not, the device continues with the next step.
    6. Discards the packets and generates ICMP_UNREACH messages.
  • If the device does not find a matching local PBR node, it searches the routing table for a route based on the destination addresses of the packets and then sends the packets.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174069

Views: 112832

Downloads: 252

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next