441
To configure IS-IS between an MCE and a VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an IS-IS process for a
VPN instance and enter IS-IS
view.
isis
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
MCE. On a VPN site, configure a
common IS-IS process.
3.
Configure a network entity
title.
network-entity
net
By default, no NET is configured.
4.
Redistribute remote site routes
advertised by the PE into IS-IS.
import-route
protocol
[
process-id
|
all-processes
|
allow-ibgp
] [
cost
cost
|
cost-type
{
external
|
internal
} | [
level-1
|
level-1-2
|
level-2
] |
route-policy
route-policy-name
|
tag
tag
] *
By default, IS-IS does not
redistribute routes from any other
routing protocol.
If you do not specify the route level
in the command, the command
redistributes routes to the level-2
routing table by default.
5.
Return to system view.
quit
N/A
6.
Enter interface view.
interface
interface-type
interface-number
N/A
7.
Enable the IS-IS process on
the interface.
isis enable
[
process-id
]
By default, IS-IS is disabled.
Configuring EBGP between an MCE and a VPN site
To run EBGP between an MCE and a VPN site, you must configure a BGP peer for each VPN instance
on the MCE, and redistribute the IGP routes of each VPN instance on the VPN site.
You can configure filtering policies to filter received routes and advertised routes.
1.
Configure the MCE:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter BGP-VPN instance
view.
ip vpn-instance
vpn-instance-name
N/A
4.
Configure an EBGP peer.
peer
{
group-name
|
ip-address
[
mask-length
] }
as-number
as-number
By default, no BGP peer is
configured.
5.
Enter BGP-VPN IPv4
unicast address family
view.
address-family ipv4
[
unicast
]
N/A
6.
Enable BGP to exchange
IPv4 unicast routes with the
peer.
peer
{
group-name
|
ip-address
[
mask-length
] }
enable
By default, BGP does not
exchange IPv4 unicast routes
with any peer.
