Configuring Routing Policies on a BGP Route Receiver

Procedure

1. Run system-view

   The system view is displayed.

2. Run route-policy route-policy-name matchMode node node

   The node of a routing policy is created, and the view of the routing policy is displayed.

3. Run one of the following commands as needed to configure a filtering rule for the routing policy on the BGP route receiver.

   • To match an AS_Path list, run the if-match as-path-filter as-path-acl-number &<1-16> command.

   • To match a community attribute list, run the if-match community-filter { basic-comm-filter-num [ whole-match ] | ext-comm-filter-num } &<1-16> command.

   • To match a route cost, run the if-match cost value command.

   

   The route attribute configured for a BGP route must be the same as that of the route advertised by a BGP route sender.

4. Perform the following steps as required:
   • Run the apply qos-local-id qos-local-id command to apply a QoS policy to the route that meets the matching rule in the routing policy.
     

     When the QoS policy ID, configured by apply qos-local-id qos-local-id, is applied to QPPB, the ID can be configured within the range of the QoS policy ID using qos-local-id qos-local-id behavior behavior-name.

   • Run the apply ip-precedence ip-precedence command to apply IP precedence to the route that meets the matching rule in the routing policy.

   A routing policy consists of multiple nodes. Each node comprises multiple if-match and apply clauses. The if-match clauses define matching rules of a node. The apply clauses define QoS behaviors to be performed on the routes that match the matching rule.

   You can configure multiple if-match clauses for a node. The relationship between these rules is "AND". This means that a route passes the filtering only when it meets all the matching rules.

   The relationship between routing policy nodes is "OR". That is, if a route matches a node of a routing policy, it matches the routing policy. If none of the routing policy nodes is matched, the route does not match the routing policy.

5. Run quit

   Return to the system view.

6. Run bgp as-number

   BGP is enabled and the BGP view is displayed.

7. Run peer ipv4-address route-policy route-policy-name import

   The routing policy is applied to the routes sent from the peer (route sender).

   

   Ensure that BGP peer relationships have been set up before the routing policy is applied.

8. Run commit

   The configuration is committed.