The peer route-policy export command specifies a route-policy for filtering routes to be advertised to a peer group.
The undo peer route-policy export command deletes a specified route-policy.
By default, no route-policy is configured for the routes to be advertised to a specified BGP peer group.
Parameter | Description | Value |
---|---|---|
group-name |
Specifies the name of a peer group. |
The name is a string of 1 to 47 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
route-policy-name |
Specifies the name of a route-policy. |
The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
export |
Applies a route-policy to routes to be advertised to a peer group. |
- |
ignore-bit-error |
Ignores bit error detection results when applying the route-policy. |
- |
Usage Scenario
After a route-policy is created, the peer route-policy export command is used to apply a Route-Policy to a peer group so that the routes advertised to a peer group can be controlled. To be specific, only the necessary routes are advertised to the peer group. In this manner, route management is implemented, the scale of the routing table is reduced, and fewer network resources are consumed.
In a bit-error-triggered protection switching scenario, if you want to use the local preference or MED attribute specified in the export routing policy no matter whether bit errors occur, run the peerroute-policy export ignore-bit-error command.Prerequisites
If the command specifies a route-policy that does not exist, use the route-policy command to create the route-policy.
Configuration Impact
If the peer route-policy command is run for a peer group, all the members of the peer group inherit the configuration.
The peer route-policy command is mutually exclusive with the peer route-filter commands. Binding a route-policy after a BGP peer relationship is established may cause peer flapping.<HUAWEI> system-view [~HUAWEI] route-policy test-policy permit node 10 [*HUAWEI-route-policy] quit [*HUAWEI] bgp 100 [*HUAWEI-bgp] group test internal [*HUAWEI-bgp] ipv6-family vpnv6 [*HUAWEI-bgp-af-vpnv6] peer test enable [*HUAWEI-bgp-af-vpnv6] peer test route-policy test-policy export ignore-bit-error
<HUAWEI> system-view [~HUAWEI] route-policy test-policy permit node 10 [*HUAWEI-route-policy] quit [*HUAWEI] bgp 100 [*HUAWEI-bgp] group test [*HUAWEI-bgp] ipv6-family vpnv6 [*HUAWEI-bgp-af-vpnv6] peer test enable [*HUAWEI-bgp-af-vpnv6] peer test route-policy test-policy export