cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10653
Views
10
Helpful
5
Replies

clear ip BGP

knaik99
Level 1
Level 1

Why do we not use above command in ISP network?

Please explain

5 Replies 5

balaji.bandi
Hall of Fame
Hall of Fame

Because it clears all the connection and terminates. Specifies that all current BGP sessions will be reset.

Then the process start to re-establish the session.

 

I do not know what context you were looking, explain more ? if you like detailed reply.

 

 

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Can we have difference between below command---

Clear ip BGP *

clear ip bgp * soft 
clear ip bgp * soft in/out 
clear ip bgp <bgp neigbour> soft in/out 

Hello


@knaik99 wrote:

Can we have difference between below command---

Clear ip BGP *  <--- hard resets all bgp tcp neighbors connections drops peerings , incurs outage, reestablishes bpp relationships with updated adjacency and local rib tables

clear ip bgp * soft <--- soft route refresh adjacency/local rib tables relating to all bgp peers
clear ip bgp * soft in/out
  <--- soft route refresh of adjacency-rib-in or out and local rib table relating to all bgp peers
clear ip bgp <bgp neigbour> soft in/out 
<--- soft route refresh of a specific bgp neighbor adjacency-rib-in or out and local rib table.


 


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

Hello

Clear ip bgp * - will tear-down and reset all bgp tcp connections so it must be used with caution especially on a isp rtr - however you can use a related command that will not be as intrusive as the above that will request and refresh the bgp tables via the bgp route refresh capability, the below commands can do such a job.

clear ip bgp * soft 
clear ip bgp * soft in/out 
clear ip bgp <bgp neigbour> soft in/out  


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

Joseph W. Doherty
Hall of Fame
Hall of Fame
Oh, and to add to what the other posters have already noted, remember if you're dealing with Internet sized route tables, it can take a while to rebuild the peering relationship with even one peer. That's "why" you want to avoid using that command, i.e. you normally don't want to create such a (needless) disruption.

Beside the time it takes, rebuilding the peering relationship is a control plane function, so you may hammer the CPU too. So, even if you only need to reset just one peering relationship, the "soft" option (as mentioned by Paul), is generally preferred.