Nokia Lab | LAB 7 RSVP-TE Resource reservation |


Hello!

We're going ahead with constraint-based routing and today let's take a look into one of them in more detail - reservation of bandwidth resources.
I'm using topology and configuration from the previous lab.
Please check my first lab for input information.

Topology example

Lab tasks and questions:
  • Signaling and Reserving Bandwidth Requirements
    • create LSP from R1 to R6. The primary path should have bandwidth constraint (e.g. 500Mbit/s)
      • describe reserving bandwidth process
        • examine signaling with cspf and no cspf option
      • examine opaque LSA
        • check maximum bandwidth, reservable bandwidth, and unreserved bandwidth fields
        • Any changes after LSP signaling?
        • change path bandwidth and check opaque LSA again. Pay attention to Age and Sequence especially. What is a problem that can occur if we have an unstable network and a lot of LSP with bandwidth constraints?
          • How can we decrease the amount of LSA flood?
            • configure Threshold-Triggered IGP TE Updates and examine how it works
  • Bandwidth Reservation Styles
    • configure LSP to_R6 with primary "totally loose" path (bandwidth 200Mbit/s) and standby secondary "totally loose" path (bandwidth 300Mbit/s)
      • find a shared link
        • examine TED
        • What is unreserved bandwidth?
        • What is the default Bandwidth Reservation Style?
        • change Bandwidth Reservation Style and examine TED again
  • Least-Fill Bandwidth Reservation
    • create the next LSPs on R1:
      • to_R6_200 - bandwidth 200Mbit/s
      • to_R6_300 - bandwidth 300Mbit/s
      • to_R6_500 - bandwidth 500Mbit/s
        • examine TED and reserved bandwidth on links. Some links may be underload
        • configure least-fill option and examine TED again
  • LSP Soft Preemption
    • shutdown all previous LSP and create new with the strict path R1 - R2 - R4 - R6:
      • to_R6_strict_300 (bandwidth 300Mbit/s, setup and hold priority equal 4)
      • to_R6_strict_800 (bandwidth 800Mbit/s, setup and hold priority equal 2). Shutdown this LSP
        • make sure that LSP to_R6_strict_300 is in UP state
        • enable LSP to_R6_strict_800 and examine LSP to_R6_strict_300 path in detail
          • describe preemption process
          • What is the operation status of LSP to_R6_strict_300? Why?
        • shutdown LSP to_R6_strict_300 and enable it again
          • What is the operation status of LSP to_R6_strict_300? Why?
  • DiffServ-Aware Traffic Engineering
    • investigate the difference between Maximum Allocation Model (MAM) and Russian Dolls Model (RDM)
      • prepare DiffServ infrastructure for Maximum Allocation Model (MAM) model
        • use Table 1 for RSVP configuration
        • create the next LSPs with the same strict path R1 - R2 - R4 - R6:
          • to_R6_CT0_200Mbit_first (bandwidth 200Mbit/s, hold/setup priority 2, class type 0)
          • to_R6_CT0_200Mbit_second (bandwidth 200Mbit/s, hold/setup priority 2, class type 0)
          • to_R6_CT2_400Mbit (bandwidth 400Mbit/s, hold/setup priority 0, class type 2)
            • examine LSP in detail (operation status, CSPF errors, etc)
      • reconfigure routers to Russian Dolls Model (RDM) approach
        • use Table 1 again
        • examine LSPs status from the previous task in detail. What is the main difference?
      • describe the difference between Maximum Allocation Model (MAM) and Russian Dolls Model (RDM) approaches
Table 1

Traffic type

TE class

Class type

Preemption

Priority

Bandwidth

Gold

2

CT2

0

40

Silver

1

CT1

1

30

Bronze

0

CT0

2

20

      Final configs
      Github project

      Useful debug commands
      show router ospf opaque-database detail
      show router rsvp session detail
      show router mpls lsp detail
      show router mpls path detail
      tools dump router te-database detail
      tools dump router mpls te-lspinfo detail

      Comments

      Post a Comment