28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

VPN, and routes announced by a remote PE router that match the VRF import policy<br />

for that VPN. Customer sites can access only the routes in their VPN’s VRF.<br />

Maintaining the VRF separate from the standard inet.0 and inet.3 routing tables<br />

prevents a VPN’s private routes from mixing with public (Internet) routes or with<br />

routes from other VPNs.<br />

Each VPN has a policy that associates the VPN’s VRF target or target community<br />

with each route before advertising the route and that filters which routes to advertise.<br />

A VPN label is distributed with each route, independently of the bgp.l3vpn.0<br />

table. VPN routes are directly advertised to other PE routers; they are not distributed<br />

from the VRF table into the bgp.l3vpn.0 table.<br />

The best routes from each VRF table are placed into a forwarding table in the<br />

router’s Packet Forwarding Engine (PFE). This forwarding table is associated only<br />

with the VPN and is separate from the forwarding tables populated by the inet.0<br />

and inet.3 routing tables.<br />

The PE routers also maintain inet.0 and inet.3 routing tables for use with regular<br />

and VPN routing. inet.0 contains the usual intradomain routes (non-VPN routes<br />

only) and external (Internet) routes, including those learned by the IBGP sessions<br />

between PE routers. The inet.3 table stores the MPLS labels learned from the signaling<br />

protocol (either LDP or RSVP) that is used for VPN traffic.<br />

Each VPN always has two policies associated with it. An import policy is applied to<br />

VPN-IPv4 routes learned from other PE routers to determine whether to add the<br />

route to the local bgp.l3vpn.0 table. Nonmatching routes are discarded. An export<br />

policy is applied to the VPN-IPv4 routes advertised by the local PE router to other PE<br />

routers. Nonmatching routes are not advertised.<br />

15.1 Setting Up a Simple Layer 3 VPN<br />

Problem<br />

You want to set up a Layer 3 VPN for a customer who wants a private network for<br />

internal network communication and transactions.<br />

Solution<br />

Creating a Layer 3 VPN for the customer involves setting up your PE and P routers.<br />

The customer (or you) can set up the customer’s routers (the CE routers). The PE<br />

and P routers must run an IGP, IBGP, MPLS, and a signaling protocol (RSVP or<br />

LDP). You establish an MPLS LSP between the PE routers and configure the VPN<br />

itself on the PE routers.<br />

Setting Up a Simple Layer 3 VPN | 555<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!