0% found this document useful (0 votes)
113 views

Juniper Mpls Best Practice Part 1

The document discusses configuring static MPLS LSPs between routers in a Juniper network testbed. It describes configuring LSPs from Jakarta to Makasar via Semarang and Surabaya, and the return path from Makasar to Jakarta via Denpasar and Bandung. It shows how the LSP configuration results in traffic taking a specific path, compared to using the IGP route.

Uploaded by

scorcd
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
113 views

Juniper Mpls Best Practice Part 1

The document discusses configuring static MPLS LSPs between routers in a Juniper network testbed. It describes configuring LSPs from Jakarta to Makasar via Semarang and Surabaya, and the return path from Makasar to Jakarta via Denpasar and Bandung. It shows how the LSP configuration results in traffic taking a specific path, compared to using the IGP route.

Uploaded by

scorcd
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 22

Juniper MPLS Best Practice

Part 1
Static LSP Configuration and understanding mpls.0 table

Febrian Setiadi - 860063


What is MPLS?
• Forwarding technique using label value
• “Virtual Circuit” for IP
▫ Unidirectional path
▫ Tunel through the network
• Mapping IP Prefixes to LSPs
• Labels are placed between L2 header and L2
data
• Label stacking is possible
Lab Topology

Loopbacks

Jakarta : 192.168.8.1
Bandung : 192.168.12.1
Semarang : 192.168.16.1
Surabaya : 192.168.36.1
Denpasar : 192.168.40.1
Makasar : 192.168.44.1
IGP Configuration
• After IGP already converged, we’re ready to configure static LSP

jkt@Lab:Jakarta> show configuration protocols ospf


area 0.0.0.0 {
interface all;
}
smg@Lab:Semarang> show configuration protocols ospf
area 0.0.0.0 {
interface all; Preconfigured
}
sby@Lab:Surabaya> show configuration protocols ospf with OSPF, all
area 0.0.0.0 { routers belong
interface all;
} to area 0
bdg@Lab:Bandung> show configuration protocols ospf
area 0.0.0.0 {
interface all;
}
dps@Lab:Denpasar> show configuration protocols ospf
area 0.0.0.0 {
interface all;
}
mks@Lab:Makasar> show configuration protocols ospf
area 0.0.0.0 {
interface all;
}
LSP Configuration
• We’ll setup LSP from Jakarta to Makasar, via Semarang, Surabaya and Makasar

• And returning LSP path from Makasar to Jakarta via Denpasar and Bandung
LSP Configuration

Jakarta performs label imposition (PUSH) , this label should be received by Semarang

jkt@Lab:Jakarta> show
configuration protocols mpls
static-path inet {
192.168.44.1/32 {
next-hop 10.0.11.1;
push 1000001;
}
}
interface all;
LSP Configuration

Semarang performs label swapping 1000001 with 1000002

smg@Lab:Semarang> show What’s on mpls.0 table


configuration protocols mpls
smg@Lab:Semarang> show route table mpls.0
interface all; mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0
interface em1.11 { hidden)
+ = Active Route, - = Last Active, * = Both
label-map 1000001 { 0 *[MPLS/0] 01:51:53, metric 1
next-hop 10.0.0.2; 1 Receive
*[MPLS/0] 01:51:53, metric 1
swap 1000002; 2
Receive
*[MPLS/0] 01:51:53, metric 1
} Receive
1000001 *[Static/5] 01:51:53
} > to 10.0.0.2 via em1.0, Swap 1000002
LSP Configuration

Surabaya performs label swapping 100002 with 100003

What’s on mpls.0 table


sby@Lab:Surabaya> show
configuration protocols mpls sby@Lab:Surabaya> show route table mpls.0
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0
interface all; hidden)
+ = Active Route, - = Last Active, * = Both
interface em2.0 {
0 *[MPLS/0] 02:07:58, metric 1
label-map 1000002 { Receive
1 *[MPLS/0] 02:07:58, metric 1
next-hop 10.0.4.2; Receive
2 *[MPLS/0] 02:07:58, metric 1
swap 1000003; Receive
1000002 *[Static/5] 01:56:46
} > to 10.0.4.2 via em1.4, Swap 1000003

}
LSP Configuration

Denpasar performs label swapping 1000003 with 0  Penultimate Hop Popping

What’s on mpls.0 table


dps@Lab:Denpasar> show route table mp
dps@Lab:Denpasar> show mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0
hidden)
configuration protocols mpls + = Active Route, - = Last Active, * = Both

interface all; 0 *[MPLS/0] 02:19:06, metric 1


Receive
interface em1.60 { 1 *[MPLS/0] 02:19:06, metric 1
label-map 1000003 { 2
Receive
*[MPLS/0] 02:19:06, metric 1
next-hop 10.0.60.2; 1000003
Receive
*[Static/5] 02:04:06
swap 0; 1000003(S=0)
> to 10.0.60.2 via em1.60, Swap 0
*[Static/5] 02:04:06
} > to 10.0.60.2 via em1.60, Pop

}
LSP Configuration
• Reachability from Jakarta
jkt@Lab:Jakarta> show route 192.168.44.1

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


+ = Active Route, - = Last Active, * = Both

192.168.44.1/32 *[Static/5] 02:02:10


> to 10.0.11.1 via em2.11, Push 1000001
[OSPF/10] 02:55:26, metric 3
> to 10.0.80.2 via em1.80
to 10.0.11.1 via em2.11
• Traceroute result from Jakarta
jkt@Lab:Jakarta> traceroute 192.168.44.1
traceroute to 192.168.44.1 (192.168.44.1), 30 hops max, 40 byte packets
1 SMG (10.0.11.1) 0.817 ms 0.750 ms 0.590 ms
MPLS Label=1000001 CoS=0 TTL=1 S=1
2 SBY (10.0.0.2) 1.096 ms 1.061 ms 1.308 ms
MPLS Label=1000002 CoS=0 TTL=1 S=1
3 DPS (10.0.4.2) 1.459 ms 1.347 ms 1.286 ms
MPLS Label=1000003 CoS=0 TTL=1 S=1
4 MKS (192.168.44.1) 2.073 ms 1.642 ms 1.538 ms
LSP vs IGP
• OSPF Reachability
jkt@Lab:Jakarta> show route 192.168.44.1
192.168.44.1/32 *[OSPF/10] 03:17:24, metric 3
> to 10.0.80.2 via em1.80
to 10.0.11.1 via em2.11
jkt@Lab:Jakarta> traceroute 192.168.44.1
traceroute to 192.168.44.1 (192.168.44.1), 30 hops max, 40 byte packets
1 BDG (10.0.80.2) 0.933 ms 0.701 ms 0.684 ms
2 DPS (10.0.70.2) 1.107 ms 1.011 ms 0.988 ms
3 MKS (192.168.44.1) 1.477 ms 1.377 ms 1.500 ms

• Using Static LSP


jkt@Lab:Jakarta> traceroute 192.168.44.1
traceroute to 192.168.44.1 (192.168.44.1), 30 hops max, 40 byte packets
1 SMG (10.0.11.1) 0.817 ms 0.750 ms 0.590 ms
MPLS Label=1000001 CoS=0 TTL=1 S=1
2 SBY (10.0.0.2) 1.096 ms 1.061 ms 1.308 ms
MPLS Label=1000002 CoS=0 TTL=1 S=1
3 DPS (10.0.4.2) 1.459 ms 1.347 ms 1.286 ms
MPLS Label=1000003 CoS=0 TTL=1 S=1
4 MKS (192.168.44.1) 2.073 ms 1.642 ms 1.538 ms
Summary
• While using IGP (OSPF)

Will traverse through


Bandung and Denpasar to
reach Makasar

jkt@Lab:Jakarta> show route 192.168.44.1


192.168.44.1/32 *[OSPF/10] 03:17:24, metric 3
> to 10.0.80.2 via em1.80
to 10.0.11.1 via em2.11
jkt@Lab:Jakarta> traceroute 192.168.44.1
traceroute to 192.168.44.1 (192.168.44.1), 30 hops max, 40 byte packets
1 BDG (10.0.80.2) 0.933 ms 0.701 ms 0.684 ms
2 DPS (10.0.70.2) 1.107 ms 1.011 ms 0.988 ms
3 MKS (192.168.44.1) 1.477 ms 1.377 ms 1.500 ms
Summary
• LSP Configured

Will traverse through


Semarang, Surabaya and
Denpasar to reach Makasar

jkt@Lab:Jakarta> traceroute 192.168.44.1


traceroute to 192.168.44.1 (192.168.44.1), 30 hops max, 40 byte packets
1 SMG (10.0.11.1) 1.618 ms 0.807 ms 0.679 ms
MPLS Label=1000001 CoS=0 TTL=1 S=1
2 SBY (10.0.0.2) 1.088 ms 1.292 ms 1.011 ms
MPLS Label=1000002 CoS=0 TTL=1 S=1
3 DPS (10.0.4.2) 1.307 ms 1.412 ms 1.295 ms
MPLS Label=1000003 CoS=0 TTL=1 S=1
4 MKS (192.168.44.1) 1.635 ms 1.799 ms 1.592 ms
Summary
• Returning Path (Omitting Transit Configuration)
mks@Lab:Makasar> show
configuration protocols mpls
static-path inet {
192.168.8.1/32 {
next-hop 10.0.60.1;
push 1000100;
}
}
interface all;
mks@Lab:Makasar> traceroute 192.168.8.1
traceroute to 192.168.8.1 (192.168.8.1), 30 hops max, 40 byte packets
1 DPS (10.0.60.1) 1.056 ms 0.876 ms 0.805 ms
MPLS Label=1000100 CoS=0 TTL=1 S=1
2 BDG (10.0.70.1) 1.142 ms 1.160 ms 1.153 ms
MPLS Label=1000101 CoS=0 TTL=1 S=1
3 JKT (192.168.8.1) 1.619 ms 1.598 ms 1.455 ms
Appendix – Complete Configuration
jkt@Lab:Jakarta> show configuration protocols {
interfaces { mpls {
em1 { static-path inet {
unit 80 { 192.168.44.1/32 {
vlan-id 80; next-hop 10.0.11.1;
family inet { push 1000001;
address 10.0.80.1/30; }
} }
family mpls; interface all;
} }
} ospf {
em2 { area 0.0.0.0 {
unit 11 { interface all;
vlan-id 11; }
family inet { }
address 10.0.11.2/30; }
}
family mpls;
}
smg@Lab:Semarang> show configuration
protocols {
interfaces {
mpls {
em1 {
interface all;
unit 0 {
interface em1.11 {
vlan-id 0;
label-map 1000001 {
family inet {
next-hop 10.0.0.2;
address 10.0.0.1/30;
swap 1000002;
}
}
family mpls;
}
}
}
unit 3 {
ospf {
vlan-id 3;
area 0.0.0.0 {
family inet {
interface all;
address 10.0.3.1/30;
}
}
}
family mpls;
}
}
unit 11 {
vlan-id 11;
family inet {
address 10.0.11.1/30;
}
family mpls;
bdg@Lab:Bandung> show configuration
interfaces { protocols {
em1 { mpls {
unit 70 { interface all;
vlan-id 70; interface em1.70 {
family inet { label-map 1000101 {
address 10.0.70.1/30; next-hop 10.0.80.1;
} swap 0;
family mpls; }
} }
} }
em2 { ospf {
unit 3 { area 0.0.0.0 {
vlan-id 3; interface all;
family inet { }
address 10.0.3.2/30; }
} }
family mpls;
}
unit 80 {
vlan-id 80;
family inet {
address 10.0.80.2/30;
sby@Lab:Surabaya> show configuration
interfaces { protocols {
em1 { mpls {
unit 4 { interface all;
vlan-id 4; interface em2.0 {
family inet { label-map 1000002 {
address 10.0.4.1/30; next-hop 10.0.4.2;
} swap 1000003;
family mpls; }
} }
unit 9 { }
vlan-id 9; ospf {
family inet { area 0.0.0.0 {
address 10.0.9.1/30; interface all;
} }
family mpls; }
} }
}
em2 {
unit 0 {
vlan-id 0;
family inet {
address 10.0.0.2/30;
sby@Lab:Surabaya> show configuration
interfaces { protocols {
em1 { mpls {
unit 4 { interface all;
vlan-id 4; interface em2.0 {
family inet { label-map 1000002 {
address 10.0.4.1/30; next-hop 10.0.4.2;
} swap 1000003;
family mpls; }
} }
unit 9 { }
vlan-id 9; ospf {
family inet { area 0.0.0.0 {
address 10.0.9.1/30; interface all;
} }
family mpls; }
} }
}
em2 {
unit 0 {
vlan-id 0;
family inet {
address 10.0.0.2/30;
dps@Lab:Denpasar> show configuration
interfaces { protocols {
em1 { mpls {
unit 60 { interface all;
vlan-id 60; interface em1.60 {
family inet { label-map 1000003 {
address 10.0.60.1/30; next-hop 10.0.60.2;
} swap 0;
family mpls; }
} label-map 1000100 {
} next-hop 10.0.70.1;
em2 { swap 1000101;
unit 4 { }
vlan-id 4; }
family inet { }
address 10.0.4.2/30; ospf {
} area 0.0.0.0 {
family mpls; interface all;
} }
unit 70 { }
vlan-id 70; }
family inet {
address 10.0.70.2/30;
mks@Lab:Makasar> show configuration
interfaces { protocols {
em2 { mpls {
unit 9 { static-path inet {
vlan-id 9; 192.168.8.1/32 {
family inet { next-hop 10.0.60.1;
address 10.0.9.2/30; push 1000100;
} }
family mpls; }
} interface all;
unit 60 { }
vlan-id 60; ospf {
family inet { area 0.0.0.0 {
address 10.0.60.2/30; interface all;
} }
family mpls; }
} }
}
lo0 {
unit 44 {
family inet {
address 192.168.44.1/32;
}

You might also like