lab 3.5 RSVP Traffic Engineering & Link Coloring

Lab Topology
masih menggunakan topology yang sama pada lab sebelumnya.

RSVP-signaled MPLS LSP
Mari kita LSP dari HONGKONG ke AMSTERDAM dengan bandwidth request 100Mbps dan enable CSPF (Constrained Shotest Path First)

Konfigurasi router HONGKONG

root# edit logical-systems HONGKONG protocols mpls

[edit logical-systems HONGKONG protocols mpls]
root# set label-switched-path AMSTERDAM bandwidth 100m

[edit logical-systems HONGKONG protocols mpls]
root# show label-switched-path AMSTERDAM
to 192.168.24.1;
bandwidth 100m;


[edit]
root# run show mpls lsp logical-system HONGKONG name AMSTERDAM
Ingress LSP: 8 sessions
To From State Rt P ActivePath LSPname
192.168.24.1 192.168.16.1 Up 0 * AMSTERDAM
Total 1 displayed, Up 1, Down 0

Egress LSP: 8 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 20 sessions
To From State Rt Style Labelin Labelout LSPname
192.168.24.1 192.168.8.1 Up 0 1 FF 300064 299920 AMSTERDAM
Total 1 displayed, Up 1, Down 0


root# run show mpls lsp logical-system HONGKONG name AMSTERDAM detail
Ingress LSP: 8 sessions

192.168.24.1
 From: 192.168.16.1, State: Up, ActiveRoute: 0, LSPname: AMSTERDAM
 ActivePath: (primary)
 LSPtype: Static Configured, Penultimate hop popping
 LoadBalance: Random
 Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary State: Up
 Priorities: 7 0
 Bandwidth: 100Mbps
 SmartOptimizeTimer: 180
 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
 10.0.16.2 S 10.0.1.1 S 10.0.24.2 S
 Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
 10.0.16.2 10.0.1.1 10.0.24.2
Total 1 displayed, Up 1, Down 0

Egress LSP: 8 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 20 sessions

192.168.24.1
 From: 192.168.8.1, LSPstate: Up, ActiveRoute: 0
 LSPname: AMSTERDAM, LSPpath: Primary
 Suggested label received: -, Suggested label sent: -
 Recovery label received: -, Recovery label sent: 299920
 Resv style: 1 FF, Label in: 300064, Label out: 299920
 Time left: 153, Since: Tue Nov 1 04:19:30 2016
 Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
 Port number: sender 1 receiver 52221 protocol 0
 PATH rcvfrom: 10.0.15.1 (ge-0/0/2.8) 36 pkts
 Adspec: received MTU 1500 sent MTU 1500
 PATH sentto: 10.0.21.2 (ge-0/0/2.4) 35 pkts
 RESV rcvfrom: 10.0.21.2 (ge-0/0/2.4) 35 pkts, Entropy label: No
 Explct route: 10.0.21.2 10.0.22.2 10.0.29.2
 Record route: 10.0.15.1 <self> 10.0.21.2 10.0.22.2 10.0.29.2
Total 1 displayed, Up 1, Down 0

[edit]
root# run show route table inet.3 logical-system HONGKONG

inet.3: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.0.1/32 *[RSVP/7/1] 01:16:49, metric 1
 > to 10.0.16.2 via ge-0/0/2.5, label-switched-path SANJOSE
192.168.2.1/32 *[RSVP/7/1] 01:16:46, metric 2
 > to 10.0.16.2 via ge-0/0/2.5, label-switched-path MONTREAL
192.168.5.1/32 *[RSVP/7/1] 01:16:47, metric 2
 > to 10.0.16.2 via ge-0/0/2.5, label-switched-path DENVER
192.168.8.1/32 *[RSVP/7/1] 01:16:49, metric 1
 > to 10.0.15.1 via ge-0/0/2.8, label-switched-path SYDNEY
192.168.12.1/32 *[RSVP/7/1] 01:16:46, metric 2
 > to 10.0.15.1 via ge-0/0/2.8, label-switched-path SAOPAULO
192.168.20.1/32 *[RSVP/7/1] 01:16:48, metric 1
 > to 10.0.21.2 via ge-0/0/2.4, label-switched-path TOKYO
192.168.24.1/32 *[RSVP/7/1] 01:01:18, metric 3
 > to 10.0.16.2 via ge-0/0/2.5, label-switched-path AMSTERDAM
192.168.28.1/32 *[RSVP/7/1] 01:16:47, metric 2
 > to 10.0.21.2 via ge-0/0/2.4, label-switched-path LONDON

 

Mari kita buat LSP dari HONGKONG ke AMSTERDAM melalui TOKYO

[edit logical-systems HONGKONG protocols]
root# edit logical-systems HONGKONG protocols

[edit logical-systems HONGKONG protocols]
root# set mpls path TOKYO 10.0.21.2 strict

[edit logical-systems HONGKONG protocols]
root# set mpls label-switched-path AMSTERDAM primary TOKYO


[edit logical-systems HONGKONG protocols]
root# show mpls
label-switched-path LONDON {
 to 192.168.28.1;
}
label-switched-path TOKYO {
 to 192.168.20.1;
}
label-switched-path MONTREAL {
 to 192.168.2.1;
}
label-switched-path SANJOSE {
 to 192.168.0.1;
}
label-switched-path SAOPAULO {
 to 192.168.12.1;
}
label-switched-path DENVER {
 to 192.168.5.1;
}
label-switched-path SYDNEY {
 to 192.168.8.1;
}
label-switched-path AMSTERDAM {
 to 192.168.24.1;
 bandwidth 100m;
 primary TOKYO;

 }
}
path TOKYO {
 10.0.21.2 strict;
}
path SANJOSE {
 10.0.16.2 
}
interface ge-0/0/2.4;
interface ge-0/0/2.5;
interface ge-0/0/2.8;

lakukan verifikasi path primary atas perubahan LSP tersebut.

[edit]
root# run show mpls lsp logical-system HONGKONG name AMSTERDAM detail
Ingress LSP: 8 sessions

192.168.24.1
 From: 192.168.16.1, State: Up, ActiveRoute: 0, LSPname: AMSTERDAM
 ActivePath: TOKYO (primary)
 LSPtype: Static Configured, Penultimate hop popping
 LoadBalance: Random
 Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary TOKYO State: Up
 Priorities: 7 0
 Bandwidth: 100Mbps
 SmartOptimizeTimer: 180
 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
 10.0.21.2 S 10.0.22.2 S 10.0.29.2 S
 Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
 10.0.21.2 10.0.22.2 10.0.29.2
Total 1 displayed, Up 1, Down 0

Egress LSP: 8 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 20 sessions

192.168.24.1
 From: 192.168.8.1, LSPstate: Up, ActiveRoute: 0
 LSPname: AMSTERDAM, LSPpath: Primary
 Suggested label received: -, Suggested label sent: -
 Recovery label received: -, Recovery label sent: 299920
 Resv style: 1 FF, Label in: 300064, Label out: 299920
 Time left: 150, Since: Tue Nov 1 04:19:30 2016
 Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
 Port number: sender 1 receiver 52221 protocol 0
 PATH rcvfrom: 10.0.15.1 (ge-0/0/2.8) 192 pkts
 Adspec: received MTU 1500 sent MTU 1500
 PATH sentto: 10.0.21.2 (ge-0/0/2.4) 192 pkts
 RESV rcvfrom: 10.0.21.2 (ge-0/0/2.4) 191 pkts, Entropy label: No
 Explct route: 10.0.21.2 10.0.22.2 10.0.29.2
 Record route: 10.0.15.1 <self> 10.0.21.2 10.0.22.2 10.0.29.2
Total 1 displayed, Up 1, Down 0

Sekarang kita buat secondary path dari HONGKONG ke AMSTERDAM melalui SANJOSE

[edit]
root# run show ospf neighbor logical-system HONGKONG
Address         Interface       State          ID         Pri    Dead
10.0.21.2       ge-0/0/2.4      Full     192.168.20.1     128     31
10.0.16.2       ge-0/0/2.5      Full     192.168.0.1      128     37
10.0.15.1       ge-0/0/2.8      Full     192.168.8.1      128     38
[edit]
root# edit logical-systems HONGKONG protocols mpls

[edit logical-systems HONGKONG protocols mpls]
root# set path SANJOSE 10.0.16.2 strict

[edit logical-systems HONGKONG protocols mpls]
root# set label-switched-path AMSTERDAM secondary SANJOSE standby

[edit logical-systems HONGKONG protocols mpls]
root# show
label-switched-path LONDON {
 to 192.168.28.1;
}
label-switched-path TOKYO {
 to 192.168.20.1;
}
label-switched-path MONTREAL {
 to 192.168.2.1;
}
label-switched-path SANJOSE {
 to 192.168.0.1;
}
label-switched-path SAOPAULO {
 to 192.168.12.1;
}
label-switched-path DENVER {
 to 192.168.5.1;
}
label-switched-path SYDNEY {
 to 192.168.8.1;
}
label-switched-path AMSTERDAM {
 to 192.168.24.1;
 bandwidth 100m;
 primary TOKYO;
 secondary SANJOSE {
 standby;
 }
}
path TOKYO {
 10.0.21.2 strict;
}
path SANJOSE {
 10.0.16.2 strict;
}
interface ge-0/0/2.4;
interface ge-0/0/2.5;
interface ge-0/0/2.8;

lakukan verifikasi path primary atas perubahan LSP tersebut.

[edit]
root# run show mpls lsp logical-system HONGKONG name AMSTERDAM detail
Ingress LSP: 8 sessions

192.168.24.1
 From: 192.168.16.1, State: Up, ActiveRoute: 0, LSPname: AMSTERDAM
 ActivePath: TOKYO (primary)
 LSPtype: Static Configured, Penultimate hop popping
 LoadBalance: Random
 Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary TOKYO State: Up
 Priorities: 7 0
 Bandwidth: 100Mbps
 SmartOptimizeTimer: 180
 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
 10.0.21.2 S 10.0.22.2 S 10.0.29.2 S
 Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
 10.0.21.2 10.0.22.2 10.0.29.2
 Standby SANJOSE State: Up
 Priorities: 7 0
 Bandwidth: 100Mbps
 SmartOptimizeTimer: 180
 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 30)
 10.0.16.2 S 10.0.1.1 S 10.0.24.2 S
 Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
 10.0.16.2 10.0.1.1 10.0.24.2
Total 1 displayed, Up 1, Down 0

Egress LSP: 8 sessions
Total 0 displayed, Up 0, Down 0

Transit LSP: 20 sessions

192.168.24.1
 From: 192.168.8.1, LSPstate: Up, ActiveRoute: 0
 LSPname: AMSTERDAM, LSPpath: Primary
 Suggested label received: -, Suggested label sent: -
 Recovery label received: -, Recovery label sent: 299920
 Resv style: 1 FF, Label in: 300064, Label out: 299920
 Time left: 130, Since: Tue Nov 1 04:19:30 2016
 Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
 Port number: sender 1 receiver 52221 protocol 0
 PATH rcvfrom: 10.0.15.1 (ge-0/0/2.8) 203 pkts
 Adspec: received MTU 1500 sent MTU 1500
 PATH sentto: 10.0.21.2 (ge-0/0/2.4) 203 pkts
 RESV rcvfrom: 10.0.21.2 (ge-0/0/2.4) 203 pkts, Entropy label: No
 Explct route: 10.0.21.2 10.0.22.2 10.0.29.2
 Record route: 10.0.15.1 <self> 10.0.21.2 10.0.22.2 10.0.29.2
Total 1 displayed, Up 1, Down 0

mari kita test trafik menuju IP Loopback AMSTERDAM menggunakan LSP AMSTERDAM. Sebelum LSP AMSTERDAM diaktifkan, dari HONGKONG menuju AMSTERDAM melalui SANJOSE.

[edit]
root# run traceroute logical-system HONGKONG 192.168.24.1
traceroute to 192.168.24.1 (192.168.24.1), 30 hops max, 40 byte packets
 1 10.0.16.2 (10.0.16.2) 513.746 ms 39.829 ms 1.428 ms
 2 10.0.1.1 (10.0.1.1) 9.429 ms 3.885 ms 2.256 ms
 3 192.168.24.1 (192.168.24.1) 52.362 ms 3.890 ms 3.514 ms

[edit]
root# edit logical-systems HONGKONG protocols mpls

[edit logical-systems HONGKONG protocols mpls]
root# set label-switched-path AMSTERDAM install 192.168.24.1 active

root# top
root# commit
commit complete

lakukan verifikasi setelah LSP AMSTERDAM di aktifkan. Maka akan terlihat bahwa menuju AMSTERDAM akan melalui TOKYO.

[edit]
root# run show route logical-system HONGKONG 192.168.24.1

inet.0: 25 destinations, 43 routes (25 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.24.1/32 *[RSVP/7/1] 00:02:04, metric 3
 > to 10.0.21.2 via ge-0/0/2.4, label-switched-path AMSTERDAM
 to 10.0.16.2 via ge-0/0/2.5, label-switched-path AMSTERDAM
 [OSPF/10] 03:42:21, metric 3
 to 10.0.21.2 via ge-0/0/2.4
 > to 10.0.16.2 via ge-0/0/2.5
 to 10.0.15.1 via ge-0/0/2.8
 [IS-IS/15] 03:17:26, metric 30
 to 10.0.21.2 via ge-0/0/2.4
 > to 10.0.16.2 via ge-0/0/2.5
 to 10.0.15.1 via ge-0/0/2.8

inet.3: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.24.1/32 *[RSVP/7/1] 00:16:34, metric 3
 > to 10.0.21.2 via ge-0/0/2.4, label-switched-path AMSTERDAM
 to 10.0.16.2 via ge-0/0/2.5, label-switched-path AMSTERDAM

[edit]
root#

[edit]
root# run traceroute logical-system HONGKONG 192.168.24.1
traceroute to 192.168.24.1 (192.168.24.1), 30 hops max, 40 byte packets
 1 10.0.21.2 (10.0.21.2) 82.644 ms 1.933 ms 1.826 ms
 MPLS Label=299968 CoS=0 TTL=1 S=1
 2 10.0.22.2 (10.0.22.2) 146.674 ms 2.179 ms 2.386 ms
 MPLS Label=299904 CoS=0 TTL=1 S=1
 3 192.168.24.1 (192.168.24.1) 2.613 ms 2.064 ms 3.028 ms

LINK COLORING
mari kita buat LSP dari TOKYO menuju SYDNEY menggunakan link administrative blue berdasarkan Link-Coloring.

[edit]
root# edit logical-systems TOKYO
root# set protocols mpls interface ge-0/0/1.4 admin-group blue
root# set protocols mpls admin-groups blue 1

root# edit logical-systems HONGKONG
root# set protocols mpls interface ge-0/0/2.8 admin-group blue
root# set protocols mpls interface ge-0/0/2.4 admin-group blue
root# set protocols mpls admin-groups blue 1

root# edit logical-systems SYDNEY
root# set protocols mpls interface ge-0/0/1.8 admin-group blue
root# set protocols mpls admin-groups blue 1

root# top
root# commit

lakukan perintah dibawah ini untuk verifikasi link administrative yang tealh di konfigurasi.

[edit]
root# run show mpls interface logical-system TOKYO
Interface State Administrative groups (x: extended)
ge-0/0/1.2 Up <none>
ge-0/0/1.4 Up blue

[edit]
root#

[edit]
root# run show mpls interface logical-system HONGKONG
Interface State Administrative groups (x: extended)
ge-0/0/2.4 Up blue
ge-0/0/2.5 Up <none>
ge-0/0/2.8 Up blue

[edit]
root#

[edit]
root# run show mpls interface logical-system SYDNEY
Interface State Administrative groups (x: extended)
ge-0/0/1.8 Up blue
ge-0/0/1.9 Up <none>

 

Leave a comment

Blog at WordPress.com.

Up ↑