[j-nsp] cogent bgp example?
Frances Albemuth
frances.cincinattus at gmail.com
Fri Aug 22 23:54:55 EDT 2008
From a theoretical perspective there is nothing inherently unstable
about this configuration from a layer two or layer three standpoint.
I've heard that people have had issues with peculiar emergent
qualities of the implied route reflection and aggregation topology,
however.
-FC
On Thu, Aug 21, 2008 at 1:17 PM, manolo <mhernand1 at comcast.net> wrote:
> Not the Junos config itself. I was not being specific its not from the user
> hardware sites its an issue on the cogent side. The 2 peer setup has never
> been stable for me with Foundry, Cisco or Juniper. Only when I get them to
> give me a standard single peer setup.
>
>
> Manolo
>
> Korey Verlsteffen wrote:
>>
>> Hi Manolo,
>>
>> Can you point out the flaws in this comfig for me and make
>> recommendations? I'm not a junos expert, but I've never had any problems
>> with this config running a few 1Gb/s links at near capacity. I'm always
>> looking to improve my setup.
>>
>>
>> - Korey
>> ----- Original Message ----- From: manolo To: Korey Verlsteffen Cc:
>> seph ; juniper-nsp at puck.nether.net Sent: Thursday, August 21, 2008 12:28 PM
>> Subject: Re: [j-nsp] cogent bgp example?
>>
>>
>>
>>
>> Be careful with this cogent setup under high load. It tends to break
>> quite easily. I have a long documented history of having to prove it to
>> cogent how bad it really is. I am glad to see cogent doesn't learn from
>> its mistakes.
>>
>>
>>
>> Manolo
>>
>> Korey Verlsteffen wrote:
>> >> Hi, I'm a small site and I'm just getting ready to go live with a
>> >> cogent connection. But, I'm finding myself a bit confused by their
>> >> Peer A / Peer B description. I can find some examples of multihop
>> >> things, but none seem very clear.
>> >>
>> >> Can someone send a basic cogent bgp setup?
>> >>
>> >> thanks
>> >> seph
>> >> >
>> >
>> > Peer A starts the initial connection to Cogent. Peer B is for
>> advertising the routes.
>> >
>> > A.A.A.A = Cogent Peer A IP address
>> > B.B.B.B = Cogent Peer B IP address
>> > X.X.X.X = Your interface IP (assigned by Cogent)
>> >
>> > protocols { > bgp { > group
>> Cogent-Peer-A {
>> > type external;
>> > neighbor A.A.A.A {
>> > import cogent-peer-policy; ### Set this policy to allow
>> all from Cogent Peer A
>> > authentication-key "xxx"; ### Set your bgp password
>> that was assigned to you from Cogent
>> > export my-bgp-network; ### Policy that advertises your
>> routes to Cogent
>> > peer-as 174;
>> > } > } > group
>> Cogent-Peer-B {
>> > type external;
>> > local-address X.X.X.X;
>> > neighbor B.B.B.B {
>> > multihop {
>> > ttl 6;
>> > } > import cogent-policy; ### Policy
>> to allow all routes from Cogent or filter them as needed
>> > authentication-key "xxx"; ### Set your bgp password
>> that was assigned to you from Cogent
>> > peer-as 174;
>> > } > } >
>> > You will need to set your IP assigned by Cogent on the loop back
>> interface >
>> > interfaces {
>> > lo0 {
>> > description Loopback;
>> > unit 0 {
>> > family inet {
>> > address 127.0.0.1/32;
>> > address X.X.X.X/32;
>> > }
>> > }
>> > }
>> >
>> > Don't forget to setup your policies.
>> >
>> >
>> > Sincerely,
>> >
>> > Korey Verlsteffen
>> > kverlsteffen at securenetsystems.net
>> > http://www.securenetsystems.net
>> >
>> >
>> > _______________________________________________
>> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>> >
>> >
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list