cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3848
Views
0
Helpful
6
Replies

BGP Neighbor in Active State , but still getting ping from CE to PE from router. what is the reason ?

BGP configuration having no problem .

1 Accepted Solution

Accepted Solutions

Hello
It would also be better to remove any prefix-list, route-map then one the secession is established then re-apply them.

Do you have any access-list applied that could be preventing the peering?

Can you post the output from, debug ip bgp

FYI -Lastly soft-reconfiguration inbound  its very resource intensive and isnt required nowadays with the introduction of route refresh

 

res

Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

6 Replies 6

Hello

Are these peers directly connected or multihop -when you say the ce and pe rtrs respond to ping are these the two devices that are trying to create a peer relationship?

 

The active state is basically stating tcp communication isn't verified between the neighbour op addresses- so check the communication between peer address not just the physical connections!

 

Ping from <source peer -destination peer>

 

res

paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Hii Sir , thanks for your reply

 

Peers are directly connected. I have checked ping from source peer to destination peer , it is getting.

what will be the reason ?

Helli

Can you post the bgp config for each rtr?

Do have bgp logging enabled ?

 

res

paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Hi Paul ,

for your reference 

router bgp <AS>
bgp router-id <Loopback>
bgp log-neighbor-changes
neighbor <PE Neighbor> remote-as <AS>
neighbor <PE Neighbor> description *** Peer EBGP ***
neighbor <PE Neighbor> password 7 xxxx
!
address-family ipv4
network <LAN > mask 255.255.255.0
network <Loopback> mask 255.255.255.255
neighbor <PE Neighbor> activate
neighbor <PE Neighbor> soft-reconfiguration inbound
neighbor <PE Neighbor> prefix-list Deny-WAN-IP in
neighbor <PE Neighbor> route-map PREVENT-TRANSIT out
exit-address-family

 

Hello
It would also be better to remove any prefix-list, route-map then one the secession is established then re-apply them.

Do you have any access-list applied that could be preventing the peering?

Can you post the output from, debug ip bgp

FYI -Lastly soft-reconfiguration inbound  its very resource intensive and isnt required nowadays with the introduction of route refresh

 

res

Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

hii paul ,

 

Anyway thanks  for your reply.

 

will post debug ip bgp later .

 

Is debug command cause problem in production network ?