H3C Technologies H3C SR8800 - Manual (Page 371)

360
Step Command Remarks
13. Configure BGP updates to the
peer to not carry private AS
numbers.
peer ip-address public-as-only
Optional
By default, a BGP update carries
private AS numbers.
14. Apply a routing policy for the
peer.
peer ip-address route-policy
route-policy-name { export |
import }
Optional
By default, no routing policy is
applied for a peer.
15. Enable VPN target filtering for
received BGP-VPNv6
subaddress family routes.
policy vpn-target
Optional
Enabled by default
16. Configure the local PE as the
route reflector and specify the
peer as the client.
peer ip-address reflect-client
Optional
No route reflector or client is
configured by default.
17. Enable route reflection
between clients.
reflect between-clients
Optional
Enabled by default
18. Configure a cluster ID for the
route reflector. reflector cluster-id { cluster-id |
ip-address }
Optional
By default, a route reflector uses its
router ID as the cluster ID.
19. Create an RR reflection policy. rr-filter
extended-community-list-number
Optional
NOTE:
For information about IPv6 BGP routing features, see Layer 3—IP Routing Configuration Guide.
Configuring inter-AS IPv6 VPN
If the MPLS backbone that carries the IPv6 VPN routes spans multiple ASs, you need to configure inter-AS
IPv6 VPN.
There are three inter-AS VPN solutions (for more information, see the chapter “Configuring MPLS
L3VPN”). IPv6 MPLS L3VPN supports only inter-AS VPN option A and option C.
Configuration prerequisites
Before configuring inter-AS IPv6 VPN, complete these tasks:
• Configuring an IGP for the MPLS backbone in each AS to implement IP connectivity
• Configuring basic MPLS capabilities for the MPLS backbone of each AS
• Configuring MPLS LDP for the MPLS backbones so that LDP LSPs can be established
NOTE:
The following sections describe inter-AS IPv6 VPN option A and option C. Select one according to your
networking scenario.