Those log message would seem to indicate that there was a problem with interface ATM2/0. The clock change removed and clock change done would seem to indicate a signaling problem - which is probably a provider error.
If interface ATM2/0 is how you access your BGP peer the problem on the interface probably explains why BGP is down.
I would suggest that you check with your provider for the state of your connection on ATM2/0.
A route-flap occurs when a BGP network prefix is withdrawn and reannonced; specifically, this happens when a BGP Speaker hears a WITHDRAWN followed by an UPDATE for a prefix. Whenever a network goes down, the rest of the Internet is told about it. Hence, BGP propages this state change throughtout the Internet of course.
If the State Change is caused by Faulty Circuits (frequently going up and down) or from misconfigured routing (redistributing the IGP into th EGP), the internet would experience several hundered BGP State cahnges a second. For every state change, BGP will allocate a time to process the work and pass on the changes to all other BGP neighors.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...