Step
5.
Enter interface view.
6.
Enable OSPFv3 on the
interface.
Configuring IPv6 IS-IS between PE and CE
An IPv6 IS-IS process belongs to the public network or a single VPN instance. If you create an IPv6 IS-IS
process without binding it to a VPN instance, the process belongs to the public network.
For more information about IPv6 IS-IS, see Layer 3—IP Routing Configuration Guide.
To configure IPv6 IS-IS between PE and CE:
Step
1.
Enter system view.
2.
Create an IPv6 IS-IS process
for a VPN instance and enter
IS-IS view.
3.
Configure a network entity
title for the IS-IS process.
4.
Enable the IPv6 capacity for
the IS-IS process.
5.
Return to system view.
6.
Enter interface view.
7.
Enable the IPv6 capacity for
the IS-IS process on the
interface.
Configuring EBGP between PE and CE
Configure the PE:
1.
Step
1.
Enter system view.
2.
Enable BGP and enter BGP
view.
3.
Enter IPv6 BGP-VPN instance
view.
4.
Configure the CE as the VPN
EBGP peer.
5.
Redistribute the routes of the
local CEs.
Command
interface interface-type
interface-number
ospfv3 process-id area area-id
[ instance instance-id ]
Command
system-view
isis [ process-id ] vpn-instance
vpn-instance-name
network-entity net
ipv6 enable
quit
interface interface-type
interface-number
isis ipv6 enable [ process-id ]
Command
system-view
bgp as-number
ipv6-family vpn-instance
vpn-instance-name
peer ipv6-address as-number
as-number
import-route protocol [ process-id ]
[ med med-value | route-policy
route-policy-name ] *
354
Remarks
N/A
By default, OSPFv3 is disabled on
an interface.
Perform this configuration on PEs.
Remarks
N/A
Perform this configuration on PEs.
On CEs, create a normal IPv6 IS-IS
process.
Not configured by default.
Disabled by default.
N/A
N/A
Disabled by default.
Remarks
N/A
N/A
N/A
N/A
A PE must redistribute the routes of
the local CEs into its VPN routing
table so that it can advertise them
to the peer PE.