Received BGP prefix but not able to ping it although it's on the RIB

[DavideRanalli76560]

Hi all, I am confused about the fact that I am receiving a prefix from eBGP, the same network is also on the RIB although I am not able to ping it:

R3#show ip route vrf 22 22.22.22.22

Routing Table: 22
Routing entry for 22.22.22.22/32
Known via "bgp 3", distance 20, metric 0
Tag 1, type external
Last update from 1.1.1.1 00:27:15 ago
Routing Descriptor Blocks:
* 1.1.1.1, from 1.1.1.1, 00:27:15 ago
Route metric is 0, traffic share count is 1
AS Hops 2
Route tag 1
MPLS label: none

R3#show ip bgp vpnv4 vrf 22 22.22.22.22
BGP routing table entry for 22:33:22.22.22.22/32, version 3
Paths: (1 available, best #1, table 22)
Not advertised to any peer
Refresh Epoch 2
1 2, (received & used)
1.1.1.1 from 1.1.1.1 (1.1.1.1)
Origin IGP, localpref 100, valid, external, best
rx pathid: 0, tx pathid: 0x0

R3#ping vrf 22 22.22.22.22
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 22.22.22.22, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

why this behavior? Would a host be able to contact that network?

many thanks

David

[MHM Cisco World]

Can you draw the topology ?

[Phil Scott]

Does the destination node have a route in its routing table to get back to the source node? 

[paul driver]

Hello

can you post the output into a file and attach to your OP

sh run | sec router

sh ip vrf interface brief

sh ip route 

sh ip route vrf xx

[Richard Burts · Accepted solution]

David

@Phil Scott asks a very important question. You have a route to get to that address. But does that address (and the router to which it connects) have a route back to your address (or if your traffic is natted on the way out does the remote system have a route to your natted address)?

Perhaps the output of a traceroute to that address might shed some light? Remember that, (assuming that the traceroute will not get all the way to the destination) the last response in traceroute is the last successful communication to you. The problem might be on that device but is quite likely to be on the next device on the path. So is the last entry in your traceroute output the router to which 22.22.22.22 connects?

[DavideRanalli76560]

Thank you all for the valuable support, as mentioned Scott and Richard from the problem was that I didn't advertise on R1 the network 192.168.13.0/24 with the network command on BGP.  Below the topology

Many thanks again

David

[Richard Burts]

David

Thanks for the update. Glad that you have been able to solve the issue and that our suggestions were helpful. Thank you for marking this question as solved. This will help other participants in the community to identify discussions which have helpful information. This community is an excellent place to ask questions and to learn about networking. I hope to see you continue to be active in the community.