On Nov 8, 2:39pm [EMAIL PROTECTED] wrote:
> holdtime-and-a-bit seconds. [Aside: shouldn't the session be refused at
> startup if a mutually agreeable keepalive value can't be negotiated rather
> than being allowed to flap like this?]
Junipers seem to be slightly in the wrong here. A hold tim
NetSecGuy wrote:
> I understand AS is RIS itself, is this some kind of misconfig on their
> end? It seems to be announcing it's entire table every 5 minutes. This
> started late Friday and ended a few hours ago.
FYI, AS is the RIPE NCC's production AS; the RIS project uses AS12654.
There
On Nov 7, 2005, at 8:32 AM, Howard C. Berkowitz wrote:
At 9:44 AM -1000 11/6/05, Randy Bush wrote:
> A peer should never announce a route it has already announced
unless
that route is withdrawn.
one of many counterexamples: change in igp will cause change in
med. any attribute changes
At 9:44 AM -1000 11/6/05, Randy Bush wrote:
> A peer should never announce a route it has already announced unless
that route is withdrawn.
one of many counterexamples: change in igp will cause change in
med. any attribute changes, and announcement is required.
e.g., an internal igp oscil
> A peer should never announce a route it has already announced unless
> that route is withdrawn.
one of many counterexamples: change in igp will cause change in
med. any attribute changes, and announcement is required.
e.g., an internal igp oscillation could cause what the op
describes.
ran
I understand BGP flapping to be announcements followed by
withdraws over a short period. I am seeing a peer with a large
number of announcements and the normal number of withdraws. Is
there a term to describe what I am seeing? I'd like to understand
what is happening, but I've been loo
At the risk of sounding like a total moron, can anyone explain what is happening here?
This is from RIS, specifically RRC00. Here is some sample output of route_btoa from this file:
http://data.ris.ripe.net/rrc00/2005.11/updates.20051106.0430.gz
BGP4MP|1131251415|STATE|193.0.0.56||1|2
BGP4
On Nov 6, 2005, at 1:05 PM, NetSecGuy wrote:
I asked this question on inet-access and it was suggested I try NANOG.
I understand BGP flapping to be announcements followed by withdraws
over a short period. I am seeing a peer with a large number of
announcements and the normal number of wit
I asked this question on inet-access and it was suggested I try NANOG.
I understand BGP flapping to be announcements followed by
withdraws over a short period. I am seeing a peer with a large
number of
announcements and the normal number of withdraws. Is there a term
to describe what I am seeing
