Hi all
Thank you so much for your help
I am not using cisco. From my understanding from your mail, I should
configure bgp as the following. Right?
What do I should pay attention also?
Seattle: network 66.49.130.0/24
announce out permit: 66.49.130.0/24
announce out deny 0.0.0.0
deny in
On Sat, Jun 25, 2011 at 9:39 PM, Joel Jaeggli joe...@bogus.com wrote:
On Jun 25, 2011, at 6:03 PM, Deric Kwok wrote:
Can we use same AS to advertise different networks in different location?
Assuming you want the two instances to be able talk to each other you just
have to relax loop
Hi
Can we use same AS to advertise different networks in different location?
We would like to use Seattle as production network and New York as testing
eg:
Seattle: network 66.49.130.0/24
New York: network 67.55.129.0/24 and ipv6 network.
Thank you
On Jun 25, 2011 6:04 PM, Deric Kwok deric.kwok2...@gmail.com wrote:
Hi
Can we use same AS to advertise different networks in different location?
We would like to use Seattle as production network and New York as testing
eg:
Seattle: network 66.49.130.0/24
New York: network
On Jun 25, 2011, at 6:03 PM, Deric Kwok wrote:
Hi
Can we use same AS to advertise different networks in different location?
We would like to use Seattle as production network and New York as testing
eg:
Seattle: network 66.49.130.0/24
New York: network 67.55.129.0/24 and ipv6
Yep, we do it that way.
We basically treat each of our datacenter's as their own entity, using
separate space for each, but all with the same AS #. What Joel
mentioned is going to be the major catch, in that for each of the two
disconnected AS's to accept the opposite sites routes, you'd need to
Can we use same AS to advertise different networks in different location?
We would like to use Seattle as production network and New York as testing
eg:
Seattle: network 66.49.130.0/24
New York: network 67.55.129.0/24 and ipv6 network.
you have not made clear whether ny and sea are
7 matches
Mail list logo