VRF and Routing Policies for Internet Access Customers

All Internet customers that attach to the TransitNet MPLS/VPN backbone network will belong to the same Internet_Customer VPN. This VPN is necessary so that direct connectivity between these types of customers and the SampleNet VPN sites is possible. All routes will be exported and imported into the VRF using the route target value of 1234:18. For optimal routing, these customers will be able to gain direct connectivity with SampleNet VPN sites across the MPLS/VPN backbone by importing the Snet_Customer VPN routes that contain the 1234:16 route target.

Internet connectivity for these customers will be provided via the external BGP peering point within the TransitNet London POP. Because only one exit point exists, and because there is no requirement to provide full or partial routes to any Internet customers, all PE-routers will carry only the default route, which is provided through configuration of a static default route that points to the Internet exit point. This means that all customers that belong to the Internet_Customer VPN will follow a default route to the TransitNet London POP, where the external BGP peering point is located.

The import a nd export polic ies used for this VPN can be seen in Table 15-5.

Table 15-5. Internet Customer VRF Import/Export Policies

VRF Internet_Customer


Import and export

1234:18 (Internet_Customer)

Import only

1234:16 (Snet_Customer)

    Part 2: MPLS-based Virtual Private Networks