396# Specify that the IPv6 VPN of VPN instance vpn3 supports up to 1000 routes, and generate an alarmmessage when the number of routes in the IPv6 VPN reaches 700 (70% of the maximum). system-view[Sysname] ip vpn-instance vpn3[Sysname-vpn-instance-vpn3] route-distinguisher 100:3[Sysname-vpn-instance-vpn3] ipv6-family[Sysname-vpn-ipv4-vpn3] routing-table limit 1000 70rr-filter (BGP-VPNv6 subaddress family view)Use rr-filter to create an RR reflection policy so only IBGP routes whose Extended Communities attributematches the specified one are reflected.Use undo rr-filter to restore the default.Syntaxrr-filter extended-community-numberundo rr-filterDefaultAn RR does not filter the reflected routes.ViewsBGP-VPNv6 subaddress family viewDefault command level2: System levelParametersextended-community-number: Specifies the number of an Extended Communities attribute supported bythe RR, in the range of 1 to 199.Usage guidelinesBy configuring different RR reflection policies on different RRs, you can implement load balancing amongthe RRs.Examples# In BGP-VPNv6 subaddress family view, specify an Extended Communities attribute for the RR to filterthe incoming VPNv6 route update packets. system-view[Sysname] bgp 100[Sysname-bgp] ipv6-family vpnv6[Sysname-bgp-af-vpnv6] rr-filter 10tnl-policy (VPN instance view/IPv6 VPN view)Use tnl-policy to associate the current VPN instance with a tunneling policy.Use undo tnl-policy to remove the association.Syntaxtnl-policy tunnel-policy-name
