Routes are not advertised between PE routers

[vladionescu26]

Hello, I am having a problem in which the:

• PE3 doesn't have anything about the LAN behind CE-C1 in its vrf Client-C routing table, but can reach ingress CE-C1;
• PE1 knows all the routes about the LAN behind CE-C2
• CE-C1 can reach anything;
• CE-C2 can only reach CE-C1 ingress port, but nothing after/behind it;
• Also, a ping from the MSW from the CE-C1 LAN can't reach PE3, and is dropped by ingress PE1. (Though it has the whole topology in its routing table)

Basically, the LANs can't reach each other.

I would guess the problem is that PE1 isn't advertising properly to PE3, but don't understand why since PE3 can reach G0/2 CE-C1.

The RT and RD match.
Below is a attached a picture for the topology, I can provide any sort of configuration if needed. 

What could be the problem?

[MHM Cisco World]

What ypu use between PE and CE ? In both sites

MHM

[vladionescu26]

Hello, I used OSPF between the PEs and CEs, I'll provide the configuration below.
Also, I think its important to know I used OSPF and EIGRP between the multilayer switches and CE-C1 and redistributed them in the PE1 - CE-C1 OSPF process. On CE-C2, I advertised the VLANs with the network statement directly in the CE-C2 - PE3 OSPF process.
CE-C1 :
router eigrp 2
network 10.10.11.0 0.0.0.255
redistribute ospf 300 metric 1000 100 255 1 1500
redistribute ospf 1
eigrp router-id 10.10.11.1
!
router ospf 1
redistribute eigrp 2 subnets
redistribute ospf 300 subnets
!
router ospf 300
router-id 192.168.1.11
redistribute ospf 1 subnets
redistribute eigrp 2 subnets
network 11.11.11.11 0.0.0.0 area 0
network 192.168.1.11 0.0.0.0 area 0

PE1

vrf definition Client-C
rd 100:3
route-target export 100:1003
route-target import 100:1003
!
address-family ipv4
exit-address-family
!

router ospf 300 vrf Client-C
router-id 192.168.1.3
redistribute bgp 100 subnets
network 192.168.1.0 0.0.0.255 area 0
!
router ospf 10
mpls ldp autoconfig
network 1.1.1.1 0.0.0.0 area 0
network 10.10.14.1 0.0.0.0 area 0
!
router bgp 100
bgp router-id 1.1.1.1
bgp log-neighbor-changes
neighbor 6.6.6.6 remote-as 100
neighbor 6.6.6.6 update-source Loopback1
!
address-family vpnv4
neighbor 6.6.6.6 activate
neighbor 6.6.6.6 send-community both
exit-address-family
!

address-family ipv4 vrf Client-C
redistribute ospf 300
exit-address-family

PE3

vrf definition Client-C
rd 100:3
route-target export 100:1003
route-target import 100:1003
!
address-family ipv4
exit-address-family
!

router ospf 301 vrf Client-C
router-id 192.168.2.1
redistribute bgp 100 subnets
network 192.168.2.0 0.0.0.255 area 0

!

router ospf 10
mpls ldp autoconfig
passive-interface default
no passive-interface GigabitEthernet0/0
no passive-interface GigabitEthernet0/1
network 3.3.3.3 0.0.0.0 area 0
network 10.10.34.3 0.0.0.0 area 0
network 10.10.35.3 0.0.0.0 area 0
!
router bgp 100
bgp router-id 3.3.3.3
bgp log-neighbor-changes
neighbor 6.6.6.6 remote-as 100
neighbor 6.6.6.6 update-source Loopback1
!
address-family vpnv4
neighbor 6.6.6.6 activate
neighbor 6.6.6.6 send-community both
exit-address-family
!
address-family ipv4 vrf Client-C
redistribute ospf 301
exit-address-family

CE-C2

router ospf 301
router-id 192.168.2.22
network 22.22.22.22 0.0.0.0 area 0
network 172.17.15.0 0.0.0.255 area 0
network 172.17.98.0 0.0.0.255 area 0
network 192.168.2.22 0.0.0.0 area 0

[MHM Cisco World · Accepted solution]

router eigrp 2
network 10.10.11.0 0.0.0.255
redistribute ospf 300 metric 1000 100 255 1 1500
redistribute ospf 1 <<- this need metric
eigrp router-id 10.10.11.1

!

address-family ipv4 vrf Client-C
redistribute ospf 300 <- this need match internal external 1 external 2

Do same for other PE

address-family ipv4 vrf Client-C
redistribute ospf 301 <- this need match internal external 1 external 2
exit-address-family

[vladionescu26]

I made these changes but it did not solve it

[MHM Cisco World]

Can you share config of all routers as text' I will apply to me lab and see what issue 

Thanks 

MHM

[vladionescu26]

Nevermind, I tried again and it is actually working, I probably didn't give it enough time to converge. Thank you sir !

[MHM Cisco World]

dont worry 
you are so welcome 

next time any change you do in bgp run

clear ip bgp <> 
this command make force bgp to update it table 
otherwise you need to wait for at least 15 min 
that why the bgp is called slow protocol 

goodluck 

MHM