Internet routes, Global Routing table or VRF

Unanswered Question
Apr 5th, 2006
User Badges:

Best practice, Is that you place all internet peering / transit into Global Routing table or into a MPLS VPN..

What is the benefits / disadvantages of both scenarios


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
mheusinger Thu, 04/06/2006 - 04:46
User Badges:
  • Green, 3000 points or more

Helo Peter,

my 0.02$

Internet in Global Routing


- Wellknown configs and behaviour

- separate address-family (separate route refresh, etc.)

- potentially separate RR for internet

- usual memory consumption


- larger Global Routing table

Internet in VRF


- smaller global routing table

- more (useless?) features like as-override


- more memory consumption (RD, RTs)

- higher operational risk ("route-target import" could copy internet table into customer VPN)

- more difficult operation (one BGP table, harder to find VPN customer routes)

So guess what: I would have the internet in the global routing table.

Hope this helps! Please rate all posts.

Regards, Martin


This Discussion