Edge-Core AS5700-54X, Справочное руководство CLI, Страница: 942 / 1116

Chapter 29
| IP Routing Commands
Border Gateway Protocol (BGPv4)
– 942 –
clear ip bgp
This command clears connections using hard or soft re-configuration.
Syntax
clear ip bgp {* | as-number | external | peer-group group-name |
neighbor-address } [ in [ prefix-list ] | out | soft [ in | out ]]
* – All BGP peering sessions.
as-number – All peering sessions within this autonomous system number.
(Range: 1-4294967295)
external – All eBGP peering sessions.
peer-group group-name – A BGP peer group containing a list of
neighboring routers configured with the neighbor peer-group command.
neighbor-address – IPv4 address of a neighbor.
in – Inbound sessions.
prefix-list – The outbound route filter (ORF) prefix list. This option triggers
a new route refresh or soft re-configuration, which updates the ORF prefix
list. This option is ignored unless ORF capabilities have been enabled using
the
neighbor capability orf prefix-list command or ORF capability
information has been received from a sending peer. If ignored, a normal
inbound soft reset is performed.
out – Outbound sessions.
soft – Uses soft re-configuration for the reset, which does not tear down
the session.
Command Mode
Privileged Exec
Default Setting
None
Command Usage
◆
Use this command to initiate a hard reset or soft re-configuration. A hard reset
clears and rebuilds specified peering sessions and routing tables. Soft re-
configuration uses stored information to reconfigure and activate routing
tables without clearing existing sessions. It uses stored update information to
allow you to apply a new BGP policy without disrupting the network.
◆
To generate new inbound updates from stored information without resetting
peer sessions, you must preconfigure the local router using the
neighbor
capability orf prefix-list command, which causes the router to store all received
updates. Note that storing updates is memory intensive and should only be
applied to critical links.
Outbound soft configuration requires no memory or preconfiguration.
Outbound re-configuration can be used on the other side of a peering session
to make initiate a new inbound policy on the local side.