280
Step Command
Remarks
6.
Apply an export routing
policy.
export route-policy
route-policy
By default, routes to be advertised
are not filtered.
Make sure the routing policy
already exists. Otherwise, the
device does not filter routes to be
advertised.
For information about routing
policies, see
Layer 3—IP
Routing
Configuration Guide.
7.
Apply a tunnel policy to the
VPN instance.
tnl-policy
tunnel-policy-name
By default, only one tunnel is
selected (no load balancing) in this
order: LSP tunnel and CR-LSP
tunnel.
The specified tunnel policy must
have been created.
For information about tunnel
policies, see "
Configuring routing between a PE and a CE
You can configure IPv6 static routing, RIPng, OSPFv3, IPv6 IS-IS, EBGP, or IBGP between a PE and a CE.
Configuring IPv6 static routing between a PE and a CE
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure an IPv6 static
route for a VPN instance.
ipv6 route-static
vpn-instance
s-vpn-instance-name ipv6-address prefix-length
{ interface-type interface-number
[ next-hop-address ] | nexthop-address [
public
]
|
vpn-instance
d-vpn-instance-name
nexthop-address } [
permanent
] [
preference
preference-value ] [
tag
tag-value ] [
description
description-text ]
By default, no IPv6 static
route is configured for a
VPN instance.
Perform this configuration
on the PE. On the CE,
configure a common IPv6
static route.
For more information
about IPv6 static routing,
see
Layer 3—IP Routing
Configuration Guide
.
Configuring RIPng between a PE and a CE
A RIPng process belongs to the public network or a single VPN instance. If you create a RIPng process
without binding it to a VPN instance, the process belongs to the public network.
For more information about RIPng, see
Layer 3—IP Routing Configuration Guide
.
To configure RIPng between a PE and a CE: