346
To do…
Use the command…
Remarks
Create an IPv6 IS-IS process for a
VPN instance and enter IS-IS view
isis
[
process-id
]
vpn-instance
vpn-instance-name
Required
Perform this configuration on PEs.
On CEs, create a normal IPv6 IS-IS
process.
Configure a network entity title for
the IS-IS process
network-entity
net
Required
Not configured by default
Enable the IPv6 capacity for the
IS-IS process
ipv6 enable
Required
Disabled by default
Return to system view
quit
—
Enter interface view
interface
interface-type
interface-number
—
Enable the IPv6 capacity for the
IS-IS process on the interface
isis ipv6 enable
[
process-id
]
Required
Disabled by default
NOTE:
For more information about IPv6 IS-IS, see
Layer 3—IP Routing Configuration Guide.
Configuring eBGP between PE and CE
1.
Configure the PE
To configure eBGP between PE and CE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enable BGP and enter BGP view
bgp
as-number
—
Enter IPv6 BGP-VPN instance view
ipv6-family vpn-instance
vpn-instance-name
Required
Configure the CE as the VPN eBGP
peer
peer
ipv6-address
as-number
as-number
Required
Redistribute the routes of the local
CEs
import-route
protocol
[
process-id
]
[
med
med-value
|
route-policy
route-policy-name
] *
Required
A PE needs to redistribute the
routes of the local CEs into its VPN
routing table so that it can
advertise them to the peer PE.
Configure a filtering policy to filter
the routes to be advertised
filter-policy
{
acl6-number
|
ipv6-prefix
ipv6-prefix-name
}
export
[
direct
|
isisv6
process-id
|
ripng
process-id
|
static
]
Optional
By default, BGP does not filter
routes to be advertised.
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.
Configure the CE
To configure eBGP between PE and CE:
