(Optional) Enabling an RR to Modify Route Attributes Using an Export Policy

Procedure

1. Run system-view

   The system view is displayed.

2. Run bgp as-number

   The BGP view is displayed.

3. Run ipv4-family unicast

   The IPv4 unicast address family view is displayed.

4. Run reflect change-path-attribute

   The RR is configured to modify BGP route attributes using an export policy.

   After the reflect change-path-attribute command is run on an RR, the following configurations (if performed) take effect:

   • apply as-path, which is used to modify the AS_Path attribute of BGP routes.
   • apply comm-filter delete, which is used to delete community attributes from BGP routes.
   • apply community, which is used to modify the community attribute of BGP routes.
   • apply large-community, which is used to modify the Large-community attribute of BGP routes.
   • apply cost, which is used to modify the MED value of BGP routes.
   • apply ip-address nexthop, which is used to modify the next-hop IP address of BGP routes.
   • apply local-preference, which is used to modify the Local_Pref of BGP routes.
   • apply origin, which is used to modify the Origin attribute of BGP routes.
   • apply extcommunity, which is used to modify the route target extended community attribute of BGP routes.

   • apply extcommunity soo { site-of-origin } &<1-16> additive, which is used to modify the SoO extended community attribute of BGP routes.

   

   After the reflect change-path-attribute command is run on the RR, the peer route-policy export command takes precedence over the peer next-hop-invariable and peer next-hop-local commands.

5. Run commit

   The configuration is committed.