Configuring Inter-As Ipv6 Vpn - HP 10500 Series Configuration Manual

Step
9. Configure BGP updates sent
to the peer to carry only
public AS numbers.
10. Apply a routing policy to
routes advertised to or
received from the peer or peer
group.
11. Enable route target filtering
for received BGP-VPNv6
routes.
12. Configure the local PE as the
route reflector and specify the
peer as the client.
13. Enable route reflection
between clients.
14. Configure a cluster ID for the
route reflector.
15. Configure filtering of reflected
routes.

Configuring inter-AS IPv6 VPN

If the MPLS backbone spans multiple ASs, you must configure inter-AS IPv6 VPN.
There are three inter-AS VPN solutions (for more information, see
MPLS L3VPN supports only inter-AS VPN option A and option C.
Before configuring inter-AS IPv6 VPN, complete these tasks:
• Configure an IGP for the MPLS backbone in each AS to ensure IP connectivity.
Configure basic MPLS for the MPLS backbone of each AS.
•
Configure MPLS LDP for the MPLS backbones so that LDP LSPs can be established.
•
The following sections describe inter-AS IPv6 VPN option A and option C. Select one according to your
network scenario.
Command
peer { group-name | ip-address }
public-as-only
peer { group-name | ip-address }
route-policy route-policy-name
{ export | import }
policy vpn-target
peer { group-name | ip-address }
reflect-client
reflect between-clients
reflector cluster-id { cluster-id |
ip-address }
rr-filter
extended-community-list-number
189
Remarks
By default, a BGP update carries
both public and private AS
numbers.
By default, no routing policy is
applied for a peer.
By default, route target filtering is
enabled.
By default, no route reflector or
client is configured.
By default, route reflection
between clients is enabled.
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.
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.
"Configuring MPLS L3VPN"). IPv6