[c-nsp] BGP Considerations isolated PoP

[Brian Turnbow]

If I understand correctly your third pop will not be connected to your existing 2 pops ?
In that case you will need to set up IBGP via tunnels , it's not pretty but it'll work. 
Or divide your /16 so that the third pop announces part and the other 2 pops announce part and add static routes for connectivity between the POPs. 
Your AS will not get announced back to you from your upstreams in BGP.
Brian 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Mark Tohill
Sent: mercoledì 14 settembre 2005 18.51
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] BGP Considerations isolated PoP

Hi,

 

We have our public AS announcing our /16 network over 2 PoP's to single
upstream providers two adjacent PoP's. iBGP configured as it should be.

 

What are the considerations if a third PoP were to be implemented, yet
this would, for the time being, be essentially isolated from remainder
of our network?

 

Thanks.

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/