1. No category

MPLS on practice with
RouterOS
MPLS
Case study. Implementation in the network of Skywire Technologies, Pty. South Africa
1
About me
●
Alex Vishnyakov, Mikrotik trainer, Cisco
CCNP, FreeBSD, Linux
●
Main areas — BGP and dynamic routing,
MPLS, security
●
Currently working as ISP network team
leader, Skywire Technologies Pty, South
Africa
2
It's time for Africa
3
It's time for Africa
4
Network description
●
B2B only services in SA
●
Presence in all big cities of SA, more than 1500
Km wide network
●
Over thousand of mid-size/large enterprises
●
Last mile services for 2nd largiest Telco in SA
●
Transit of IPv4, L2 and BGPv4 for small ISPs
●
Many VPNs for corporates
●
Over 100 big towers and several hundreds of APs
5
Tasks and goals
Transit and last mile services for ISPs :
1. Provide hundreds of L2 tunnels for Large ISP
2. Provide L3 transit and BGPv4 transit for several smaller ISPs
3. Separate transit IPv4 traffic from our own IPv4 traffic
Internet and voice services for end users :
4. Provide VPN site to site tunnels for customers between
branches. Point to point, point to multipoint.
5. Separate Voice, Internet and Management traffic and routing
6
Task 1 (solution: eoip, l2tp, vlans - ?)
1. Provide hundreds of L2 tunnels for Large ISP (last mile)
7
Task 1
1. Provide hundreds of L2 tunnels for Large ISP (last mile)
L2 VPN MPLS
VPLS,LDP based
8
Task 2 (solution: static routes, ospf - ?)
2. Provide L3 transit(last mile) and BGPv4 transit for several smaller ISPs
9
Task 2
2. Provide L3 transit(last mile) and BGPv4 transit for several smaller ISPs
L3 VPN MPLS
VRF, MP-BGP
10
Task 4 (solution: eoip, l2tp, ipip, gre, pptp, ipsec - ?)
4. Provide VPN site to site tunnels for customers between branches.
Point to point, point to multipoint
11
Task 4
4. Provide VPN site to site tunnels for customers between branches.
Point to point, point to multipoint
L2/L3 VPNs
MPLS, MP-BGP
12
Task 3,5 (solution: different routers, PBR - ?)
3. Separate transit IPv4 traffic from our IPv4 customers
5. Separate Voice, Internet and Management traffic and routing
13
Task 3,5 (solution: different routers, PBR - ?)
3. Separate transit IPv4 traffic from our IPv4 customers
5. Separate Voice, Internet and Management traffic and routing
L3 VPN MPLS
VRF, MP-BGP
14
MPLS is the solution
One common, vendor-independent, strong
technology for tunnels = MPLS
15
P and PE routers
Cisco, Juniper — not cheap at all
Linux, BSD — no stable implementation
Mikrotik — CCR routers
16
MPLS on Mikrotik
(before we started ...)
Results of tests and case studies :
- Stable VPLS, MPLS switching, L2 tunnels
Presentations from MUMs of Tierry Wehr
(2014), Tomas Kirnak (2013), Pat Harris (2013)
- Unstable VRFs ?
http://forum.mikrotik.com/viewtopic.php?t=73820
17
Implementation output
(… after we finished)
VPLS
- L2 tunnels are stable, both MP-BPG and LDP based
- Be careful with MTU on switches
VRF
- By itself is stable in latest RouterOS version (>6.5)
- PPPoE cannot bind to VRF dynamically → we use DHCP
- Traceroute inside VRFs not shown→ we don't propogate TTL
- VRF route leaking issues → we use additional routers
- Route withdraw. Sometimes VRF has static/dynamic routes withdraw
problem … (we don't use dynamic routing between PE-CE). → we have
connected routes mainly + work carefully with redistribution of static
- VRF BGP path selection has issues with choosing right BGP metric → we
use filter with distance manipulation
18
MPLS topology
19
MPLS topology
L2 bridging
OSPF, LDP, iBGP, MPLS
20
Let's implement MPLS
Steps :
1. Bring customer on L2 to PE router
2. OSPF on Distribution/Core layer
3. LDP activation between PE, P routers, MPLS tags
4. iBGP, Route reflectors configuration
5. MP-BGP activation
6. L2 VPLS configuration (LDP based)
7. VRF configuration(L3 tunnels, isolation of traffic)
21
Step 1 — L2 bridging
Bring customer on L2 to PE router
Advantages:
- no need for /30 networks, can be used /24 for all users on one PE
- each customer appear on PE as interface, so we can put him to VPLS or VRF
- different VLANs for different services
- VRF works fine in that setup :-)
Disadvantages:
- Large L2 domains (broadcasts)
- CPEs on one L2 line (can see each other)
ToDo:
- No «default forward» on wireless
- Port isolation (PVLAN isolated) on switches, split horizon on bridges
22
Step 2 — OSPF in
core/distribution
23
Step 3 — LDP activation
24
Step 3 — MPLS tags
25
Step 4 — Address family
MP-BGP configuration
26
Step 5 — iBGP RR
27
Step 6 — VPLS setups
28
Step 7 — VRF setup
29
Step 7 — VRF setup
30
Conclusion
Prerequisites
➔
At lease MTCINE training
Advantages:
➔
Not expensive solid MPLS solution
➔
Fast, reliable L2 tunnels
➔
Use VRF if you have similar setup to ours
➔
Smart routing and TE can be implemented
Disadvantages:
➔
Not full L3 VRF features (route leaking, route withdraw)
➔
Don't provide L3 site to site tunnels over MPLS yet
31
MPLS on practice
Thank you
[email protected]
[email protected]
32