356Step Command Remarks11. Apply an IPv6-prefix list forthe peer to filterreceived/advertised routes.peer ip-address ipv6-prefixprefix-name { export | import }Optional.By default, no IPv6 prefix list isapplied for a peer.12. Specify the preference valuefor the routes received fromthe peer.peer ip-address preferred-valuevalueOptional.0 by default.13. Configure BGP updates to thepeer to not carry private ASnumbers.peer ip-address public-as-onlyOptional.By default, a BGP update carriesprivate AS numbers.14. Apply a routing policy for thepeer.peer ip-address route-policyroute-policy-name { export |import }Optional.By default, no routing policy isapplied for a peer.15. Enable route target filteringfor received BGP-VPNv6subaddress family routes.policy vpn-target Optional.Enabled by default.16. Configure the local PE as theroute reflector and specify thepeer as the client.peer ip-address reflect-clientOptional.No route reflector or client isconfigured by default.17. Enable route reflectionbetween clients. reflect between-clients Optional.Enabled by default.18. Configure a cluster ID for theroute reflector.reflector cluster-id { cluster-id |ip-address }Optional.By default, each RR in a cluster usesits own router ID as the cluster ID.If more than one RR exists in acluster, use this command toconfigure the same cluster ID for allRRs in the cluster to avoid routloops.19. Create an RR reflection policy. rr-filterextended-community-list-numberOptional.By default, an RR does not filter thereflected routes.With an RR reflection policy, onlyIBGP routes whose ExtendedCommunities attribute matches thespecified one are reflected.By configuring different RRreflection policies on different RRs,you can implement load balancingamong the RRs.For information about IPv6 BGP routing features, see Layer 3—IP Routing Configuration Guide.Configuring inter-AS IPv6 VPNIf the MPLS backbone that carries the IPv6 VPN routes spans multiple ASs, you need to configure inter-ASIPv6 VPN.
