[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bgp convergence problem

Subject: bgp convergence problem
From: mark.tinka at seacom.mu (Mark Tinka)
Date: Thu, 8 May 2014 21:13:19 +0200
In-reply-to: <CAL9jLaaezE6YgaMBZTi+Kvxse_EixS6QGo3zJxRLzpNFTp+qdA@mail.gmail.com>
References: <[email protected]> <[email protected]> <CAL9jLaaezE6YgaMBZTi+Kvxse_EixS6QGo3zJxRLzpNFTp+qdA@mail.gmail.com>

On Thursday, May 08, 2014 06:34:14 PM Christopher Morrow 
wrote:

> :( that's bad news... config hackery is brittle.
> (but fun)

Don't I know :-)... *sigh*

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140508/a6d31a01/attachment.pgp>

References:
- bgp convergence problem
  - From: refresh.lsong at gmail.com (Song Li)
- bgp convergence problem
  - From: mark.tinka at seacom.mu (Mark Tinka)
- bgp convergence problem
  - From: morrowc.lists at gmail.com (Christopher Morrow)

Prev by Date: Getting pretty close to default IPv4 route maximum for 6500/7600 routers.
Next by Date: Getting pretty close to default IPv4 route maximum for 6500/7600 routers.
Previous by thread: bgp convergence problem
Next by thread: AusNOG 2014 Call for Presentations
Index(es):
- Date
- Thread