beautypg.com

Configuring inter-as ipv6 vpn – H3C Technologies H3C S6800 Series Switches User Manual

Page 299

background image

286

Step Command

Remarks

9.

Configure BGP updates sent
to the peer to carry only

public AS numbers.

peer { group-name | ip-address
[ mask-length ] } 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
[ mask-length ] } 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
[ mask-length ] } 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
[ mask-length ] } route-limit

prefix-number [ { alert-only |
discard | 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.

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 "

Configuring MPLS L3VPN

"). IPv6

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.