ICMP reply, but ping unsuccessful

[PaulCbl]

Hello,

I have the following topology wher PE4 is a provider edge of an MPLS cloud, and Internet is a simple router.

PE4: F0/0 192.168.54.2/30

Internet E3/1: 192.168.54.1/30

I would like to ping those two router between them. Therefore I ran the following command:

PE4#ping 192.168.54.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.54.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

At first glance I thought a configuration error would prevent the correct ICMP exchange. However after inspecting the link between them, I can see the ICMP packets were sent just fine from both ends. Notice in this screenshot that I took pings from both ways.

On the other end, Internet can ping PE4 just fine.

I expected PE4 to accept the ping replies just fine. What causes this behavior? How can I fix it?

I attached the configuration of PE4 (which I know is quite bloated) for reference.

Thank you for your suggestions

[Martin L]

if you have VRF and  if Network 192.168.54.0 is inside of VRF, so i think you should ping it from vrf, right? like

ping vrf name  192.168.54x

Regards, ML
**Please Rate All Helpful Responses **

[PaulCbl]

You're right, this command works!

My bigger issue was: through the MPLS cloud, a ping to 192.168.54.1 is successful, but "pinging" any route directly connected to "Internet" won't work.
I guessed the issue stemed from this connectivity issue. If I understood correctly, this means is that when "pinging" a route connected to "Internet" from another end of the MPLS cloud, the packets simply can't be routed through the cloud (lack of gateway or similar I guess) hence my "Network unreachable" errors.

If what I said isn't nonsense I think I figured the reason of my issue.

EDIT: for others trying to set up internet access & MPLS, I should have found this doc before: https://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/24508-internet-access-mpls-vpn.html