Thank you everyone. I will be going for confederations.
Sincerely,
-Tim
On Sun, Dec 30, 2012 at 1:19 PM, Chris Morrow wrote:
>
>
> On 12/30/2012 12:31 PM, tim tiriche wrote:
>> I didn't mean confederations.
>>
>
> yes you did, according to your diagram...
>
>> May be a diagram would be better.
On 12/30/2012 12:31 PM, tim tiriche wrote:
> I didn't mean confederations.
>
yes you did, according to your diagram...
> May be a diagram would be better.
>
> Current design: (ASN: 1234)
>
> (Customer-A) --(ebgp) --[[ (Area 10) --- (Area 0) --- (Area 20) ]]--
> (ebgp)-- (Customer-B)
>
> IGP
I didn't mean confederations.
May be a diagram would be better.
Current design: (ASN: 1234)
(Customer-A) --(ebgp) --[[ (Area 10) --- (Area 0) --- (Area 20) ]]--
(ebgp)-- (Customer-B)
IGP is running in Area 0 for P2P and loopbacks.
Area10, Area0 and Area20 are part of one Administravie domain
re
(Android mail sucks, sorry)
I think the OP means confederation not 'private islands' And they'll have
to do some planning to move to confederations.
More importantly, why get rid of your igp? Are you not already doing route
reflection and/or ibgp full mesh ?
"Justin M. Streiner" wrote:
>
On Fri, 28 Dec 2012, tim tiriche wrote:
We have multi area OSPF and would like to migrate the multi area to
private ASN BGP islands.
How are you defining an 'island'?
Main ASN:1234
Problem:
In the current OSPF areas there is an e-BGP Peering and Transit with customer.
After migration, how
We have multi area OSPF and would like to migrate the multi area to
private ASN BGP islands.
Main ASN:1234
Problem:
In the current OSPF areas there is an e-BGP Peering and Transit with customer.
After migration, how can i ensure that customer peer using the Main
ASN:1234 and transport it over the
6 matches
Mail list logo
