Configuring routing between pes – H3C Technologies H3C SR8800 User Manual

Page 369

Advertising
background image

358

Step Command

Remarks

7.

Configure a filtering policy to
filter received routes.

filter-policy { acl6-number |
ipv6-prefix ipv6-prefix-name }

import

Optional
By default, the PE does not filter

received routes.

2.

Configurations on a CE

To configure EBGP between PE and CE:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter BGP view.

bgp as-number N/A

3.

Enter IPv6 BGP subaddress
family view.

ipv6-family

Required

4.

Configure the PE as the EBGP
peer.

peer ipv6-address as-number
as-number

Required

5.

Configure route redistribution

and advertisement.

import-route protocol [ process-id ]
[ med med-value | route-policy
route-policy-name
] *

Optional
A CE needs to advertise its VPN
routes to the connected PE so that

the PE can advertise them to the

peer CE.

NOTE:

After an IPv6 BGP-VPN instance is configured, exchange of BGP routes for the VPN instance is the same
as exchange of ordinary BGP routes.

The configuration commands available in IPv6 BGP-VPN instance view are the same as those in IPv6
BGP subaddress family view. For more configuration commands in the two views, see

Layer 3—IP

Routing Configuration Guide.

Configuring routing between PEs

To configure routing between PEs:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter BGP view.

bgp as-number Required

3.

Configure the remote PE as
the peer.

peer ip-address as-number
as-number

Required

4.

Specify the source interface

for route update packets.

peer { group-name | ip-address }
connect-interface interface-type
interface-number

By default, BGP uses the outbound
interface of the best route to the
BGP peer.

5.

Enter BGP-VPNv6 subaddress

family view.

ipv6-family vpnv6

Required

Advertising