Configuration procedure – H3C Technologies H3C S7500E Series Switches User Manual
Page 329
6-104
Figure 6-27
Configure BGP AS number substitution
Loop0
Loop0
Loop0
PE 1
P
PE 2
CE 1
CE 2
VPN 1
VPN 1
Vlan-int12
MPLS backbone
Vlan-int12
Vlan-int11
Vlan-int11
Vlan-int12
Vlan-int11
Vlan-int12
Vlan-int12
Vlan-int11
Vlan-int11
Device Interface IP
address
Device Interface
IP
address
CE 1
Vlan-int11
10.1.1.1/24 P Loop0
2.2.2.9/32
Vlan-int12
100.1.1.1/24
Vlan-int11 30.1.1.1/24
PE 1
Loop0
1.1.1.9/32
Vlan-int12 20.1.1.2/24
Vlan-int11
10.1.1.2/24 PE
2
Loop0
3.3.3.9/32
Vlan-int12
20.1.1.1/24
Vlan-int11
30.1.1.2/24
CE 2
Vlan-int12
10.2.1.1/24
Vlan-int12
10.2.1.2/24
Vlan-int11
200.1.1.1/24
Configuration procedure
1) Configuring basic MPLS L3VPN
z
Configure OSPF on the MPLS backbone to allow the PEs and P device to learn the routes of the
loopback interfaces from each other.
z
Configure MPLS basic capability and MPLS LDP on the MPLS backbone to establish LDP LSPs.
z
Establish MP-IBGP peer relationship between the PEs to advertise VPN IPv4 routes.
z
Configure the VPN instance of VPN 1 on PE 2 to allow CE 2 to access the network.
z
Configure the VPN instance of VPN 1 on PE 1 to allow CE 1 to access the network.
z
Configure BGP between PE 1 and CE 1, and between PE 2 and CE 2 to inject routes of CEs into
PEs.
After completing the above configurations, if you issue the display ip routing-table command on CE
2, you should see that CE 2 has learned the route to network segment 10.1.1.0/24, where the
interface used by CE 1 to access PE 1 resides; but has not learned the route to the VPN (100.1.1.0/24)
behind CE 1. You should see the similar situation on CE 1.
Routing Tables: Public
Destinations : 8 Routes : 8
Destination/Mask Proto Pre Cost NextHop Interface
10.1.1.0/24 BGP 255 0 10.2.1.2 Vlan12
10.1.1.1/32 BGP 255 0 10.2.1.2 Vlan12
10.2.1.0/24 Direct 0 0 10.2.1.1 Vlan12
10.2.1.1/32 Direct 0 0 127.0.0.1 InLoop0
10.2.1.2/32 Direct 0 0 10.2.1.2 Vlan12