30.1.1.0/24
30.1.1.0/32
30.1.1.2/32
30.1.1.255/32
127.0.0.0/8
127.0.0.0/32
127.0.0.1/32
127.255.255.255/32 Direct
192.168.0.0/24
224.0.0.0/4
224.0.0.0/24
255.255.255.255/32 Direct
# Verify that PE 1 has learned the routes of OSPF process 20 in VPN 2 through OSPF.
[PE1] display ip routing-table vpn-instance vpn2
Destinations : 13
Destination/Mask
0.0.0.0/32
40.1.1.0/24
40.1.1.0/32
40.1.1.2/32
40.1.1.255/32
127.0.0.0/8
127.0.0.0/32
127.0.0.1/32
127.255.255.255/32 Direct
192.168.10.0/24
224.0.0.0/4
224.0.0.0/24
255.255.255.255/32 Direct
The routing information for the two VPNs has been redistributed into the routing tables on PE 1.
C onfiguring the MCE that uses EBGP to advertise VPN
3 0 4 B
routes to the PE
N etwork requirements
5 7 4 B
As shown in
the sites of each VPN can communicate with each other over the MPLS backbone.
Run OSPF in both VPN 1 and VPN 2. Run EBGP between the MCE and PE 1.
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
0
O_ASE2
150 1
Direct
0
Direct
0
0
Routes : 13
Proto
Pre Cost
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
Direct
0
0
O_ASE2
150 1
Direct
0
Direct
0
0
F igure
96, configure the MCE to advertise the routes of VPNs 1 and 2 to PE 1, so that
8 6 8 H
0
30.1.1.2
0
30.1.1.2
0
127.0.0.1
0
30.1.1.2
0
127.0.0.1
0
127.0.0.1
0
127.0.0.1
0
127.0.0.1
30.1.1.1
0
0.0.0.0
0
0.0.0.0
0
127.0.0.1
NextHop
0
127.0.0.1
0
40.1.1.2
0
40.1.1.2
0
127.0.0.1
0
40.1.1.2
0
127.0.0.1
0
127.0.0.1
0
127.0.0.1
0
127.0.0.1
40.1.1.1
0
0.0.0.0
0
0.0.0.0
0
127.0.0.1
385
Vlan30
Vlan30
InLoop0
Vlan30
InLoop0
InLoop0
InLoop0
InLoop0
Vlan30
NULL0
NULL0
InLoop0
Interface
InLoop0
Vlan40
Vlan40
InLoop0
Vlan40
InLoop0
InLoop0
InLoop0
InLoop0
Vlan40
NULL0
NULL0
InLoop0