From: Charles Huang (charlesny2000@xxxxxxxxx)
Date: Thu Nov 01 2001 - 17:22:39 GMT-3
Hi,
It takes at least 30 seconds to bring back a BGP peer
and we don't have much time in the real lab to keep on
bouncing the peers when ever we change a command.
Does anyone know which of the following commands
require to bounce the BGP peer in order to take affect
of the new commands entered ? with
"soft-reconfiguration inbound" statement which of the
following commands still require to bounce the peers ?
aggregate-address
auto-summary
bgp always-compare-med
bgp bestpath as-path ignore
bgp bestpath compare-routerid
bgp bestpath med confed
bgp bestpath med missing-as-worst
bgp client-to-client reflection
bgp cluster-id
bgp dampening
bgp default local-preference
bgp deterministic med
bgp fast-external-fallover
bgp router-id
default-information originate
default-metric
neighbor advertisement-interval
neighbor advertise-map non-exist-map
neighbor default-originate
neighbor distribute-list
neighbor filter-list
neighbor maximum-prefix
neighbor next-hop-self
neighbor password
neighbor prefix-list
neighbor remote-as
neighbor remove-private-as
neighbor route-map
neighbor route-reflector-client
neighbor send-community
neighbor timers
neighbor update-source
neighbor version
neighbor weight
network
network backdoor
network weight
Thanks for any help!!!
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:00 GMT-3