[114696] in North American Network Operators' Group
Re: Local Peering and Transit - BGP multihoming
daemon@ATHENA.MIT.EDU (ty chan)
Fri May 22 02:14:33 2009
Date: Thu, 21 May 2009 23:14:24 -0700 (PDT)
From: ty chan <chanty_kh@yahoo.com>
To: deleskie@gmail.com, nanog@nanog.org
In-Reply-To: <1184640185-1242970936-cardhu_decombobulator_blackberry.rim.net-1583315332-@bxe1087.bisx.prod.on.blackberry>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Yes, i can get sample of configuration via Google search.
but i am looking for best practices and from experience people.
________________________________
From: "deleskie@gmail.com" <deleskie@gmail.com>
To: ty chan <chanty_kh@yahoo.com>; nanog@nanog.org
Sent: Friday, May 22, 2009 12:42:14 PM
Subject: Re: Local Peering and Transit - BGP multihoming
Google BGP Cisco... Should give you 90% of this.
------Original Message------
From: ty chan
To: nanog@nanog.org
Subject: Local Peering and Transit - BGP multihoming
Sent: May 22, 2009 2:23 AM
Dear all,
In my lab, i manage two ASN (100,200). ASN100 has one transit to ASN300 and local peering to ASN500.
ASN200 has one transit to ASN400. ASN100 do private peering to ASN200. Some policies are required as below:
1. ASN100 customer can only use ASN300 for transit
2. ASN200 customer can only use ASN400 for transit.
3. Local traffic will stay local between ASN100,ASN200 and ASN500.
4. ASN100 and ASN200 are backup each other only if either upstreams is down.
How to configure BGP to meet the above policies? I am using Cisco devise.
best regards,
chanty
Sent from my BlackBerry device on the Rogers Wireless Network
