Configuring BGP VPNv6 route control

1. Enter system view.

system-view

N/A

2. Enter BGP view.

bgp as-number

N/A

3. Enter BGP VPNv6 address family view.

address-family vpnv6

N/A

4. (Optional.) Configure filtering of advertised routes.

filter-policy { acl6-number | prefix-list ipv6-prefix-name } export [ protocol process-id ]

By default, the PE does not filter advertised routes.

5. (Optional.) Configure filtering of received routes.

filter-policy { acl6-number | prefix-list ipv6-prefix-name } import

By default, the PE does not filter received routes.

6. Configure ACL-based route filtering for the specified peer or peer group.

peer { group-name | ip-address } filter-policy acl6-number { export | import }

By default, no ACL-based route filtering is configured.

7. Configure IPv6 prefix list-based route filtering for the specified peer or peer group.

peer { group-name | ip-address } prefix-list ipv6-prefix-name { export | import }

By default, no IPv6 prefix list-based route filtering is configured.

8. Specify a preferred value for routes received from the peer or peer group.

peer { group-name | ip-address } preferred-value value

The default preferred value is 0.

9. Configure BGP updates sent to the peer to carry only public AS numbers.

peer { group-name | ip-address } public-as-only

By default, a BGP update carries both public and private AS numbers.

10. Apply a routing policy to routes advertised to or received from the peer or peer group.

peer { group-name | ip-address } route-policy route-policy-name { export | import }

By default, no routing policy is applied for a peer.

11. Enable route target filtering for received BGP VPNv6 routes.

policy vpn-target

By default, route target filtering is enabled.

12. Configure the local PE as the route reflector and specify the peer as the client.

peer { group-name | ip-address } reflect-client

By default, no route reflector or client is configured.

13. Specify the maximum number of routes BGP can receive from a peer or peer group.

peer { group-name | ip-address } route-limit prefix-number [ { alert-only | reconnect reconnect-time } | percentage-value ] *

By default, the number of routes that BGP can receive from a peer or peer group is not limited.

14. Enable route reflection between clients.

reflect between-clients

By default, route reflection between clients is enabled.

15. Configure a cluster ID for the route reflector.

reflector cluster-id { cluster-id | ip-address }

By default, an RR uses its own router ID as the cluster ID.

If more than one RR exists in a cluster, use this command to configure the same cluster ID for all RRs in the cluster to avoid routing loops.

16. Configure filtering of reflected routes.

rr-filter extended-community-number

By default, an RR does not filter reflected routes.

Only IBGP routes whose extended community attribute matches the specified community list are reflected.

By configuring different filtering policies on RRs, you can implement load balancing among the RRs.