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.

Receive<br />

100064 *[LDP/9] 5d 01:00:51, metric 1<br />

> via t1-4/0/0.0, Pop<br />

100064(S=0) *[LDP/9] 5d 01:00:51, metric 1<br />

> via t1-4/0/0.0, Pop<br />

100080 *[LDP/9] 5d 01:00:51, metric 1<br />

> via t1-4/0/0.0, Swap 100000<br />

This table is the MPLS label-swapping table and is actually a switching table rather<br />

than a routing table. Instead of a prefix in the first column, you see a label value. In<br />

this output, the first three entries correspond to reserved labels, defined in RFC<br />

3032. These three entries are learned from MPLS (as indicated by [MPLS/0] in the second<br />

column) and are always in the mpls.0 routing table. The remaining three entries<br />

are for incoming labels that MPLS assigns to each upstream neighbor. Label 100064<br />

has two entries because the stack value in the MPLS header can be different in different<br />

packets. In the first entry label, 100064, the S (stack) bit is 1, so this label matches<br />

packets that have only one label on their stacks. The second entry, 100064(S=0), has<br />

the stack bit set to 0 and is used when the stack depth is not 1. That is, it is used<br />

when the packet is carrying more than one label. For both labels, the operation pops<br />

the top label off the stack. The third label, 100080, has a swap operation associated<br />

with it.<br />

You can quickly check all the routes learned from LDP with the show route protocol<br />

ldp command:<br />

aviva@RouterG> show route protocol ldp<br />

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

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

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

192.168.16.1/32 *[LDP/9] 1d 23:03:35, metric 1<br />

> via t1-4/0/0.0, Push 100000<br />

192.168.17.1/32 *[LDP/9] 1d 23:03:35, metric 1<br />

> via t1-4/0/0.0<br />

__juniper_private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0<br />

hidden)<br />

mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)<br />

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

100064 *[LDP/9] 1d 23:03:35, metric 1<br />

> via t1-4/0/0.0, Pop<br />

100064(S=0) *[LDP/9] 1d 23:03:35, metric 1<br />

> via t1-4/0/0.0, Pop<br />

100080 *[LDP/9] 1d 23:03:35, metric 1<br />

> via t1-4/0/0.0, Swap 100000<br />

This output displays the routes for the LDP FECs, stored in inet.3, and the labelswitching<br />

state stored in mpls.0.<br />

Use the show route forwarding-table mpls command to see the active MPLS routes in<br />

the Routing Engine’s forwarding table:<br />

496 | Chapter 14: MPLS<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!