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

best practice for advertising peering fabric routes

Subject: best practice for advertising peering fabric routes
From: mark.tinka at seacom.mu (Mark Tinka)
Date: Wed, 15 Jan 2014 14:55:15 +0200
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]>

On Wednesday, January 15, 2014 09:57:32 AM Michael Hallgren 
wrote:

> I don't think you need route-reflection in a 5 node iBGP.

I'm for doing it now and not worrying about it later.

Also, don't originate your routes from your peering router 

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/20140115/1fadf437/attachment.bin>

References:
- best practice for advertising peering fabric routes
  - From: elouie at yahoo.com (Eric A Louie)
- best practice for advertising peering fabric routes
  - From: elouie at yahoo.com (Eric A Louie)
- best practice for advertising peering fabric routes
  - From: m.hallgren at free.fr (Michael Hallgren)

Prev by Date: [VoiceOps] (cross post) VoIP heat charts...
Next by Date: best practice for advertising peering fabric routes
Previous by thread: best practice for advertising peering fabric routes
Next by thread: best practice for advertising peering fabric routes
Index(es):
- Date
- Thread