Re: BGP Established but Peer Ip not pinging

Abdul Farooq · ‎07-27-2022

Hi all,

In the BGP table, BGP is Established but peer IP is not pinging. what is the reason behind that? why peer is not pinging

kindly suggest the same

LOGS:-

BGP local router ID : 172.19.0.26
Local AS number : 64007
Total number of peers : 8 Peers in established state : 7

* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
172.24.17.14 9234 1353 47 0 15331 00:16:59 Established

<R01>ping 172.24.17.14
PING 172.24.17.14: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out

--- 172.24.17.14 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss

%Jul 28 11:27:30:212 2022 R01 BGP/5/BGP_STATE_CHANGED:
172.24.15.14 state is changed from OPENCONFIRM to ESTABLISHED.

Georg Pauwen · ‎07-28-2022

Hello,

hard to say without seeing the configs of both peers, can you post those (sh run) ?

Abdul Farooq · ‎07-28-2022

<MHMUMDOPDAK1MR01>dis cu configuration bgp
#
bgp 65001
router-id 172.19.0.26
preference 120 120 100
network 0.0.0.0
import-route direct
import-route static
import-route ospf 1
import-route ospf 40
import-route ospf 10
undo synchronization
peer 172.16.16.186 as-number 65001
peer 172.16.17.5 as-number 9583
peer 172.24.17.14 as-number 9829
peer 172.16.18.66 as-number 9730
peer 172.16.18.193 as-number 9730
peer 172.16.18.198 as-number 65200
peer 172.16.18.206 as-number 65032
peer 172.16.18.222 as-number 65056
peer 172.16.16.186 description IBGP-Peering
peer 172.16.16.186 route-policy IBGP-ROUTE-FILTER export
peer 172.16.16.186 password cipher $c$3$M7xAXabRIQEvNvqGfe04b+H1fx9my4YyNq4TzO9EmjzPqQOTLM8=
peer 172.16.16.186 next-hop-local
peer 172.16.17.5 description SIFY peering
peer 172.16.17.5 route-policy SIFYOUT export
peer 172.16.17.5 route-policy LPF500 import
peer 172.16.17.5 password cipher $c$3$o7biAAHHgpgIftpURxw+b/h6ebC5hUEemTATPlE/9weYFE0=
peer 172.16.17.5 ignore
peer 172.24.17.14 description BSNL Peering
peer 172.24.17.14 route-policy BSNLOUT export
peer 172.24.17.14 route-policy LPF700 import
peer 172.24.17.14 password cipher $c$3$4uybOceeZhatUdmfdVS7yK4LtqpGgAwJBpwDL/mzh8dV0Mc=
peer 172.16.18.66 description RSI-LINK-PEERING
peer 172.16.18.66 route-policy RSI-PREFIX-OUT export
peer 172.16.18.66 route-policy RSI-PREFIX-IN import
peer 172.16.18.66 password cipher $c$3$YU3Z/ZmHv+hXhihuKT/TU77FIj8+M0VsQ33EJ30Whik3dhI=
peer 172.16.18.193 description RH-HELPDESK-LINK
peer 172.16.18.193 route-policy RH-PREFIX-OUT export
peer 172.16.18.193 route-policy RH-PREFIX-IN import
peer 172.16.18.193 password cipher $c$3$ZHOKHNS7kOEUcIUeXIzrWhr+dbmVXJ3Sq8RQStY=
peer 172.16.18.198 description IPPB-Peering-Pry
peer 172.16.18.198 route-policy IPPB-PREFIX-OUT export
peer 172.16.18.198 route-policy IPPB-PREFIX-IN import
peer 172.16.18.198 route-limit 700
peer 172.16.18.198 password cipher $c$3$CFe0aG8/H2vLI7YSU52IT9wyswG1rJx6Il18
peer 172.16.18.206 description LYRA-Peering-Pry
peer 172.16.18.206 route-policy LYRA-PREFIX-OUT export
peer 172.16.18.206 route-policy LYRA-PREFIX-IN import
peer 172.16.18.206 route-limit 100
peer 172.16.18.206 password cipher $c$3$drBUmbsSEF9ZBNs/7iAiD1rAqmpE/letaH+sirDpJH/jNqc=
peer 172.16.18.222 description TCL-Peering-Pry
peer 172.16.18.222 route-policy TCL-PREFIX-OUT export
peer 172.16.18.222 route-policy TCL-PREFIX-IN import
peer 172.16.18.222 route-limit 700
peer 172.16.18.222 password cipher $c$3$CX8hxtFHZVGnSCaccna3uAmE+N48F9dbcjS5n8viL+SIrUc=
#
ipv6-family
undo synchronization
peer FD00:DA00:EA00:7::CA as-number 65001
peer FD00:DA00:EA00:172:16:17:4:1 as-number 9583
peer FD00:DA00:EA00:172:24:17:12:1 as-number 9829
peer FD00:DA00:EA00:172:24:17:12:2 as-number 9829
peer FD00:DA00:EA00:7::CA description IPv6-IBGP-Peering-MPLS-WAN-ROUTER-2
peer FD00:DA00:EA00:7::CA password cipher $c$3$zVfH9xsNzcHNSevbnopR2kfFdNmSQg9QwDHYSOP7NjCFSJtMW/o=
peer FD00:DA00:EA00:7::CA next-hop-local
peer FD00:DA00:EA00:172:16:17:4:1 description SIFY-V6 Peering
peer FD00:DA00:EA00:172:16:17:4:1 route-policy LPF500 import
peer FD00:DA00:EA00:172:16:17:4:1 password cipher $c$3$a/NUoA7RO7a7YHbiPHiN1V9lNnwmHDNWOAH1KUEu9nyQ88E=
peer FD00:DA00:EA00:172:24:17:12:2 description BSNL-V6 Peering
peer FD00:DA00:EA00:172:24:17:12:2 route-policy LPF700 import
peer FD00:DA00:EA00:172:24:17:12:2 password cipher $c$3$RxPWLNo2TkOsXRVBEVYQ585++cgqAXVdvTpz6PCcc6ZotK8=

Jon Marshall · ‎07-28-2022

BGP uses TCP to establish a peering so it could be that an acl is allowing TCP but blocking ICMP.

Jon

MHM Cisco World · ‎07-28-2022

ping 172.24.17.14 source 172.19.0.26

Try this

Abdul Farooq · ‎07-28-2022

<MHMUMDOPDAK1MR01>ping -a 172.24.17.14 172.19.0.26
PING 172.16.0.2: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out

--- 172.19.0.26 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss

Georg Pauwen · ‎07-28-2022

Hello,

post the full running configs (sh run) of both peers...

MHM Cisco World · ‎07-28-2022

Show ip route 172.24.17.14 longest

The egress interface appear here, using it ip as source of ping and I am sure youn success.