Mpls pe/ce

Hi Rene,

I should say that your site really helped me a lot in getting my CCNP. Big Thanks!
Regarding the lab above, i am just quite puzzled why I am unable to ping CE2 (5.5.5.5) from CE1 (1.1.1.1)

I checked thoroughly the configs and it seems no difference
Below is my routing table from my PE1 and could see that i could reach via my GRE Tunnel although when i checked the CEF Table it still goes to my P router.

Gateway of last resort is not set

C    192.168.12.0/24 is directly connected, FastEthernet0/0
     1.0.0.0/32 is subnetted, 1 subnets
B       1.1.1.1 [20/0] via 192.168.12.1, 02:00:39
     2.0.0.0/32 is subnetted, 1 subnets
C       2.2.2.2 is directly connected, Loopback0
     3.0.0.0/32 is subnetted, 1 subnets
O       3.3.3.3 [110/11] via 192.168.23.3, 00:16:25, FastEthernet0/1
O    192.168.45.0/24 [110/30] via 192.168.23.3, 00:16:25, FastEthernet0/1
     4.0.0.0/32 is subnetted, 1 subnets
O       4.4.4.4 [110/21] via 192.168.23.3, 00:16:27, FastEthernet0/1
<strong>C    192.168.24.0/24 is directly connected, Tunnel0
     5.0.0.0/32 is subnetted, 1 subnets
B       5.5.5.5 [200/0] via 192.168.45.5, 00:16:21</strong>
C    192.168.23.0/24 is directly connected, FastEthernet0/1
O    192.168.34.0/24 [110/20] via 192.168.23.3, 00:16:28, FastEthernet0/1
PE1#show ip cef 5.5.5.5
5.5.5.5/32, version 39, epoch 0, cached adjacency 192.168.23.3
0 packets, 0 bytes
  via <strong>192.168.45.5</strong>, 0 dependencies, recursive
    next hop 192.168.23.3, FastEthernet0/1 via 192.168.45.0/24
    valid cached adjacency

Hi Eleever,

Good to hear my work has been useful to you :slight_smile:

Your PE1 router is using 192.168.45.5 as the next hop for 5.5.5.5.

192.168.45.5 is reached by using 192.168.23.3 as the next hop, that’s your P router.

You need to make sure that your PE1 (and PE2) router prefers to use the tunnel interface. You could do this by playing with the metric, administrative distance or filtering.

Rene