[nsp] Odd things with BGP and VRF

[Rene Koning]

Steve,

You can use VRF's to isolate the ISP BGP peering routes.
Terminate each peer in a different VRF (be sure to get some
extra memory :). Although there is only one BGP process=20
per router the routes are segregated by Routing Distinguishers.

Ren=E9 Koning

> -----Original Message-----
> From:	Steve Francis [SMTP:sfrancis@expertcity.com]
> Sent:	Wednesday, July 31, 2002 9:49 PM
> To:	cisco-nsp@puck.nether.net
> Subject:	[nsp] Odd things with BGP and VRF
>=20
> Wondering if anyone can tell if this is even possible...
>=20
> I would like to have routers peer with multiple ISP's, getting a full
> routing table from each of them, and iBGP peering as normal.
>=20
> Internally, I need another system to talk BGP to those routers, and =
not
> just get the normal iBGP route updates that consist of the best path
> that router would use, but all the paths it heard from all peers.  =
This
> internal box is going to be doing all sorts of analysis of paths and
> performance, and it needs the full views as presented by each =
provider.
>=20
> I could try and get each provider to set up eBGP multihop to this =
box,
> as well as our regular router peerings, but don't much fancy my =
chances
> of achieving that.
> So I was wondering if I can do want I want with VRF's: something like
> have each external peer be in a different VRF, so that the tables are
> kept separate, but have the internal machine peer with each VRF-bgp =
table.
>=20
> Is that possible? Can you have BGP processes running per VRF?
>=20
> And can one system possibly peer with more than one of them?
>=20
> TIA
>=20
> _______________________________________________
> cisco-nsp mailing list  real_name)s@puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/