28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Solution<br />

Configure the more important LSP so that it is more likely to be set up and remain up:<br />

[edit protocols mpls]<br />

aviva@R1# set label-switched-path R1-to-R5 priority 0 0<br />

Then configure intermediate priority LSPs, those less likely to be set up and remain up:<br />

[edit protocols mpls]<br />

aviva@R1# set label-switched-path R1-to-R6 priority 1 3<br />

aviva@R1# set label-switched-path R1-to-R4 priority 4 5<br />

Finally, set up the least important LSP, the one least like to be set up and most likely<br />

to be torn down if there is insufficient bandwidth:<br />

[edit protocols mpls]<br />

aviva@R1# set label-switched-path R1-to-R5-low priority 7 7<br />

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

When you offer a higher level of service for some customers, you want RSVP to be<br />

able to establish those customers’ LSP at all times, even when there might not be<br />

enough bandwidth available on some links because other LSPs are already established.<br />

To provide this level of service, you can prioritize each customer’s LSP so that<br />

some are more important than others. Then, when RSVP calculates the path and sets<br />

up the LSP, RSVP will always be able to establish the more important LSPs, even at<br />

the cost of tearing down a less important LSP. The relative LSP priorities are determined<br />

in advance, when RSVP is establishing the LSP, not when traffic is being forwarded.<br />

If a link has insufficient bandwidth, RSVP establishes the more important<br />

(higher-priority) LSPs first and tears down lower-priority LSPs if necessary.<br />

This recipe prioritizes the four LSPs that originate on router R1. To configure an<br />

LSP’s priority, you include two values in the priority statement, the setup priority<br />

and the hold priority. You express these two priorities with a number from 0 through<br />

7, where 0 is best and 7 is worst. A setup priority of 0 means that this LSP can preempt<br />

any other LSP whose hold priority is worse than 0. Similarly, a hold priority of<br />

0 means that once the LSP is set up, it cannot be preempted. A hold priority of 1<br />

means that it can be preempted only by an LSP with a setup priority of 0. The default<br />

setup priority is 7, which means that one LSP cannot preempt another. The default<br />

hold priority is 0, which means that another LSP cannot preempt this one.<br />

The four LSPs configured in this recipe have different priorities. The LSP R1-to-R5 is<br />

the one being used for the most important customer. It will always be set up (setup<br />

priority of 0) and can never be preempted (hold priority of 0) when RSVP is setting<br />

up another LSP. The other three LSPs, in order from highest to lowest priority, are<br />

R1-to-R6 (setup priority of 1, hold priority of 3), R1-to-R4 (setup priority of 4, hold<br />

priority of 5), and R1-to-R5-low (setup priority of 7, hold priority of 7). The setup<br />

and hold priority values for the different LSP are all evaluated relative to each other.<br />

538 | 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!