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.

1 *[MPLS/0] 1d 18:03:41, metric 1<br />

Receive<br />

2 *[MPLS/0] 1d 18:03:41, metric 1<br />

Receive<br />

100368 *[VPN/170] 01:30:28<br />

> via se-5/0/1.0, Pop<br />

100384 *[VPN/170] 01:30:28<br />

> via se-5/0/1.0, Pop<br />

bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)<br />

+ = Active Route, - = Last Active, * = Both<br />

65500:3:10.0.31.0/24<br />

*[BGP/170] 00:43:17, localpref 100, from 192.168.16.1<br />

AS path: I<br />

> via t1-4/0/0.0, label-switched-path RouterG-PE-to-RouterF-PE<br />

65500:3:192.168.14.1/32<br />

*[BGP/170] 00:43:17, localpref 100, from 192.168.16.1<br />

AS path: I<br />

> via t1-4/0/0.0, label-switched-path RouterG-PE-to-RouterF-PE<br />

<strong>Discussion</strong><br />

After Layer 3 VPNs are set up, you should check the routing tables on the PE router<br />

to make sure that the VPN is operating properly and to see which routes and MPLS<br />

labels the router has learned. The show route command in this recipe displays the<br />

contents of all the routing tables on the PE router. Let’s examine the routing tables<br />

individually.<br />

In the VPN configuration, you configured OSPF on the two PE routers and on the P<br />

router. The routes learned from OSPF are in the standard inet.0 routing table. To<br />

display just these routes on the PE router, use the show route table inet.0 command<br />

(see Recipe 8.1).<br />

Because RSVP is running on the routers to support the MPLS LSP, the router creates<br />

the inet.3 table to store all MPLS routes learned from RSVP. Recipe 14.7 explains<br />

the routes in the inet.3 table.<br />

Two of the routing tables are specific to the VPN. The first is the VRF table, which<br />

stores all the IPv4 routes received from the CE routers in the VPN. The JUNOS software<br />

names the VRF table using the name of the routing instance. In our recipe, the<br />

routing instance is named VPN2, so the routing table is named VPN2.inet.0:<br />

aviva@RouterG> show route table VPN2.inet.0<br />

VPN2.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)<br />

+ = Active Route, - = Last Active, * = Both<br />

10.0.16.0/24 *[Direct/0] 01:06:47<br />

> via se-5/0/1.0<br />

10.0.16.2/32 *[Local/0] 01:06:49<br />

Local via se-5/0/1.0<br />

10.0.31.0/24 *[BGP/170] 00:16:51, localpref 100, from 192.168.16.1<br />

AS path: I<br />

> via t1-4/0/0.0, label-switched-path RouterG-PE-to-RouterF-PE<br />

Viewing the VPN Routing Tables | 565<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!