Re: Local Peering and Transit - BGP multihoming
on issues like this : [1] JFGI -> if fail : [2] man smartnet -> if fail : [3] go back to studying to get that A+ and consider perhaps a yob in redmond On Fri, May 22, 2009 at 4:01 AM, Raymond Dijkxhoorn wrote: > Hi! > > Yes, i can get sample of configuration via Google search. but i am looking for best practices and from experience people. >>> > Then post your suggested config and ask for comments. >>> >> > ...on a suitable list, dedicated to Cisco gear.. >> > > Sorry, yes. :-) Plenty of Cisco lists there to answer 'questions' :-) > > Bye, > Raymond. > > -- Jamie Rishaw // .com.a...@j <- reverse it. ish. [Impressive C-level Title Here], arpa / arpa labs
Re: Local Peering and Transit - BGP multihoming
Hi! Yes, i can get sample of configuration via Google search. but i am looking for best practices and from experience people. Then post your suggested config and ask for comments. ...on a suitable list, dedicated to Cisco gear.. Sorry, yes. :-) Plenty of Cisco lists there to answer 'questions' :-) Bye, Raymond.
Re: Local Peering and Transit - BGP multihoming
Subject: Re: Local Peering and Transit - BGP multihoming Date: Fri, May 22, 2009 at 10:55:14AM +0200 Quoting Raymond Dijkxhoorn (raym...@prolocation.net): > Hi! > >> Yes, i can get sample of configuration via Google search. >> but i am looking for best practices and from experience people. > > Then post your suggested config and ask for comments. ...on a suitable list, dedicated to Cisco gear.. -- Måns Nilsson
Re: Local Peering and Transit - BGP multihoming
Hi! Yes, i can get sample of configuration via Google search. but i am looking for best practices and from experience people. Then post your suggested config and ask for comments. Bye, Raymond.
Re: Local Peering and Transit - BGP multihoming
Yes, i can get sample of configuration via Google search. but i am looking for best practices and from experience people. From: "deles...@gmail.com" To: ty chan ; 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
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
Re: Local Peering and Transit - BGP multihoming
ty chan wrote: > 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. > Is there a reason you are just throwing specs out and expecting the list to do your job for you? I don't mean to be rude, but you should learn how to at least do some of it yourself so you can ask specific questions for the parts you have trouble getting it to work. ~Seth
Local Peering and Transit - BGP multihoming
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
