Configuring ebgp between mce and vpn site – H3C Technologies H3C SR8800 User Manual
Page 280

269
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
normal IS-IS process.
3.
Configure a network entity
title.
network-entity net
Not configured by default.
4.
Redistribute remote site routes
advertised by the PE.
import-route { isis [ process-id ] |
ospf [ process-id ] | rip
[ process-id ] | bgp [ allow-ibgp ] |
direct | static } [ cost cost |
cost-type { external | internal } |
[ level-1 | level-1-2 | level-2 ] |
route-policy route-policy-name |
tag tag ] *
Optional.
By default, IS-IS does not
redistribute routes of any other
protocol.
If you do not specify the route level
in the command, the command will
redistribute 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 ]
Disabled by default.
NOTE:
For more information about IS-IS, see
Layer 3—IP Routing Configuration Guide.
Configuring EBGP between MCE and VPN site
To use EBGP for exchanging routing information between an MCE and VPN sites, 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 sites.
You also can configure filtering policies to filter the received and sent routes.
1.
Configurations on the MCE
To 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. ipv4-family vpn-instance
vpn-instance-name
N/A
4.
Configure an EBGP peer.
peer { group-name | ip-address }
as-number as-number
N/A
5.
Allow the local AS number to
appear in the AS_PATH
attribute of a received route,
and configure the maximum
number of times that such
case is allowed to appear.
peer { group-name | ip-address }
allow-as-loop [ number ]
Optional.