RSVP - Dynamic Label Switch Path Ver - 1

Download PNETLab Platform
PNETLAB Store
PNETLab.com
RSVP – Dynamic Label Switch Path
Lab Topology:
The lab network topology is illustrated below:
Lab Objective:
The objective of this lab exercise is for you to learn and understand how to configure Dynamic
Label Switch Path for RSVP on Junos devices.
Login with the account: root/pnetlab@123
Task:
Each Router (R3, R4, R5) configure 02 Label Switch Path to Loopback 0 of R1, R2.
From R1, R2 configure Label Switch Path to these Loopback 0 of Routers (R3, R4, R5).
Make sure in inet.3 table of R3, R4, R5 has Loopback of R1, R2 base on RSVP Protocol, and vice
versa.
1
PNETLAB Store
PNETLab.com
Solution
Task1: Basic IP and IGP Configuration.

Configure hostnames and IP addresses, ISIS on all routers as illustrated in the network topology.
R1:
set system host-name R1
set interfaces ge-0/0/0 description To_R2-ge-0/0/0
set interfaces ge-0/0/0 unit 0 family inet address 10.1.2.1/24
set interfaces ge-0/0/0 unit 0 family iso
set interfaces ge-0/0/0 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 1.1.1.1/32
set interfaces lo0 unit 0 family iso address 49.0001.0000.0000.0001.00
set protocols isis level 2 disable
set protocols isis level 1 wide-metrics-only
set protocols isis interface ge-0/0/0.0 point-to-point
set protocols isis interface lo0.0 passive
R2:
R3:
2
PNETLAB Store
PNETLab.com

R4:
R5:
3
PNETLAB Store
PNETLab.com
Task 2: Configure MPLS and RSVP Protocol on all Router’s Interface
Router Configuration
set protocols mpls interface ge-0/0/0.0
R1 set protocols rsvp interface ge-0/0/0.0
set protocols rsvp interface ge-0/0/1.0
Task 3: Configure Label Switch Path to Loopback 0 of R1, R2 from R3, R4, R5. And vice versa
Router Configuration
set protocols mpls label-switched-path lsp_R3_TO_R1 to 1.1.1.1
R3 set protocols mpls label-switched-path lsp_R3_TO_R2 to 2.2.2.2
Task 4: Verify the solution

Checking on R1, R5. Other Routers do the same.
- Let’s check interface running RSVP, MPLS and LSPs has established on Routers
R1:
4
PNETLAB Store
PNETLab.com
root@R1> show mpls interface

Interface State Administrative groups (x: extended)
ge-0/0/0.0 Up <none>
root@R1> show rsvp interface

RSVP interface: 2 active
Active Subscr- Static Available Reserved Highwater
Interface State resv iption BW BW BW mark
ge-0/0/0.0 Up 4 100% 1000Mbps 1000Mbps 0bps 0bps
root@R1> show mpls lsp

Ingress LSP: 3 sessions
To From State Rt P ActivePath LSPname
3.3.3.3 1.1.1.1 Up 0 * lsp_R1_TO_R3
4.4.4.4 1.1.1.1 Up 0 * lsp_R1_TO_R4
5.5.5.5 1.1.1.1 Up 0 * lsp_R1_TO_R5
Total 3 displayed, Up 3, Down 0
Egress LSP: 3 sessions

To From State Rt Style Labelin Labelout LSPname
1.1.1.1 3.3.3.3 Up 0 1 FF 3 - lsp_R3_TO_R1
1.1.1.1 5.5.5.5 Up 0 1 FF 3 - lsp_R5_TO_R1
1.1.1.1 4.4.4.4 Up 0 1 FF 3 - lsp_R4_TO_R1
Transit LSP: 3 sessions

2.2.2.2 3.3.3.3 Up 0 1 FF 299920 3 lsp_R3_TO_R2
2.2.2.2 4.4.4.4 Up 0 1 FF 299952 3 lsp_R4_TO_R2
4.4.4.4 2.2.2.2 Up 0 1 FF 299936 300064 lsp_R2_TO_R4
root@R1>
R5:
root@R5> show mpls interface
Interface State Administrative groups (x: extended)
root@R5> show rsvp interface

RSVP interface: 2 active
Active Subscr- Static Available Reserved Highwater
Interface State resv iption BW BW BW mark
root@R5> show mpls lsp

5
PNETLAB Store
PNETLab.com
To From State Rt P ActivePath LSPname

1.1.1.1 5.5.5.5 Up 0 * lsp_R5_TO_R1
2.2.2.2 5.5.5.5 Up 0 * lsp_R5_TO_R2

5.5.5.5 2.2.2.2 Up 0 1 FF 3 - lsp_R2_TO_R5
5.5.5.5 1.1.1.1 Up 0 1 FF 3 - lsp_R1_TO_R5

1.1.1.1 4.4.4.4 Up 0 1 FF 300208 300016 lsp_R4_TO_R1
3.3.3.3 2.2.2.2 Up 0 1 FF 300192 300048 lsp_R2_TO_R3
4.4.4.4 1.1.1.1 Up 0 1 FF 300224 3 lsp_R1_TO_R4
root@R5>
- Verify: Make sure in inet.3 table of R5 has Loopback of R1, R2 base on RSVP Protocol,
and vice versa.
R1:
root@R1> show route table inet.3 protocol rsvp
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
3.3.3.3/32 *[RSVP/7/1] 00:03:46, metric 10

> to 10.1.3.3 via ge-0/0/1.0, label-switched-path lsp_R1_TO_R3
4.4.4.4/32 *[RSVP/7/1] 00:02:51, metric 20
5.5.5.5/32 *[RSVP/7/1] 00:03:42, metric 20
root@R1>
R5:
root@R5> show route table inet.3 protocol rsvp
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
1.1.1.1/32 *[RSVP/7/1] 00:03:02, metric 20

2.2.2.2/32 *[RSVP/7/1] 00:03:02, metric 10
6
PNETLAB Store
PNETLab.com
root@R5>
Now, Let’s start to analyst one Label Switch Path from R1 to R5 to clarify some thing:
root@R1> show mpls lsp name lsp_R1_TO_R5 detail

5.5.5.5
From: 1.1.1.1, State: Up, ActiveRoute: 0, LSPname: lsp_R1_TO_R5
ActivePath: (primary)
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
10.1.2.2 S 10.2.5.5 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
10.1.2.2 10.2.5.5


root@R1>
With ERO, RRO above, we understood that Label Switch Path was created dynamically with IGP
best path (from Loopback 0 of R1 to Loopback 0 of R5 via R2)
- Computed ERO: 10.1.2.2 S 10.2.5.5 S
- Received RRO: 10.1.2.2 10.2.5.5
Finish this LAB!

RSVP - Dynamic Label Switch Path Ver - 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RSVP - Dynamic Label Switch Path Ver - 1

Uploaded by

Copyright:

Available Formats

Download PNETLab Platform

RSVP – Dynamic Label Switch Path

Task1: Basic IP and IGP Configuration.

set interfaces ge-0/0/0 unit 0 family mpls

Task 2: Configure MPLS and RSVP Protocol on all Router’s Interface

Task 4: Verify the solution

root@R1> show mpls interface

root@R1> show rsvp interface

root@R1> show mpls lsp

Egress LSP: 3 sessions

Transit LSP: 3 sessions

root@R5> show rsvp interface

root@R5> show mpls lsp

To From State Rt P ActivePath LSPname

Egress LSP: 2 sessions

Transit LSP: 3 sessions

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

3.3.3.3/32 *[RSVP/7/1] 00:03:46, metric 10

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

1.1.1.1/32 *[RSVP/7/1] 00:03:02, metric 20

root@R1> show mpls lsp name lsp_R1_TO_R5 detail

Egress LSP: 3 sessions

Transit LSP: 4 sessions

You might also like