[c-nsp] Fw: routes withdraw
Montse Seisdedos
mseisdedos at mediafusion.es
Mon Mar 7 13:33:49 EST 2005
> Hello everybody:
>
> We have a 7206VXR (NPE300) 256 Mb RAM. CPU 7000 256 MHz. I will call it
"A"
> A ebgp neighbor from which we received 95893 prefixes. During normal
running
> 58 Mb of RAM are occupied.
> We advertise these learn routes to a ibgp neighbor. I will call it "B"
> When we clear the ebgp session, or it goes down, we noticed that:
> 1. In A, memory consuption grows slowly til it gets the maximum, i.e.
> 256Mb. No update messages logged in the ibgp neighbor, B.
> 2. When A reaches the mx Ram, update withdraw messages are sent to the
> ibgp neigbor,and some routes are deleted from the B table.
> 3. The memory goes down and again grows till the maximum, and them
some
> other routes are deleted from ibgp neighbor table.
> 4. Again the same proccess. It takes three times to delete the B whole
> table.
>
> My anwser is:
> is this a normal behavior ?
> is there any way to advertise B that all the learn routes form A are no
> longer valid, without Router A runs out of memory and cpu?
>
More information about the cisco-nsp
mailing list