Personally I think it's a great question - I'm not sure there's a "perfect answer".
We run our full tables into inet.0 - we also merge inet.3 into inet.0 using "traffic-engineering bgp-igp-both-ribs" .... there were a number of reasons for doing this including link-protection etc. By no means am I saying that this was the best route for us to take or one that is the best route to take (pardon the pun here).... I would think it depends on what you want from the network... Cheers, Paul -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Smith Sent: Thursday, January 19, 2012 10:05 AM To: [email protected] Subject: [j-nsp] Internet routes in MPLS network, global table or own VRF? Hi How should the global Internet routes be organized in IP/MPLS network? Should they be put into global (inet.0) routing table or in their own VRF (e.g. internet.inet.0)? Assume same P/PE routers are used to route internet and VRFs. What are the pros and cons of these approaches? Pointers to good materials are appreciated. (please excuse me if this is in the series of stupid questions ;) Thanks. _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
