VIP Kolkata Call Girl Dum Dum 👉 8250192130 Available With Room
PLNOG16: Jak zbudować Punkt Wymiany Ruchu używając urządzeń Junipera, Aleksander Bury, Robert Woźny
1. How to build a successful IXP
with Juniper
Robert Woźny
robert.wozny@orange.com
Orange Polska
PLNOG Tech Olympics
Warsaw, 1st of March, 2016
Aleksander Bury
abury@juniper.net
Juniper Networks
2. Orange Polska is the largest telecommunication carrier in Poland and major
in CEE region.
As Telekomunikacja Polska, national operator in Poland in 2000 the company
joined the international Orange Group and in 2014 was rebranded to Orange
Polska. Being a part of Orange Group allows to operate according to Orange
standards, participate in international projects and provide top quality
services for over 20 milion of retail subscribers and over 300 international and
domestic carriers.
Orange Polska operates an extensive domestic and international network
providing comprehensive portfolio of voice, roaming and data services in
Poland and worldwide. Company’s mission is to follow customers’ needs,
provide customised services and consequently increase the share in
wholesale market.
Orange Polska is the leading telecommunication service provider
in Poland and CEE market.
4. what is an IXP?
Definition: An Internet Exchange Point (IXP) is a place where multiple ISPs interconnect their
networks together. Potentially many peering sessions can be established across a single well-
populated IXP peering fabric or across private peering sessions over (typically) fiber cross
connects.
ISP A ISP B
ISP C
ethernet
switch
Private Peering
across a Cross-Connect
Public Peering
across a Shared
Public Peering Switch
Definition: Peering Port Fees are the monthly recurring costs associated with peering across
a shared peering fabric.
5. Every member has physical connection to
Platform at a particular speed. Through
this connection every member receives a
static IP address with the same network
mask. The participants have direct visibility
towards the IP addresses and are able to
establish direct BGP session among each
other.
The scheme illustrates how the Route
Server is functioning and how does
member A find the network of a client of
member B and when receives traffic for it
sends it through the shared switching
infrastructure.
how it works
Member B
Network
Member A
Network
Shared Infrastructure
Shared Infrastructure
Route ServerMember A
Network
Member B
Network
6. TPIX - Introduction
The TPIX facilitates Internet interconnection in the Poland through Public Peering. It was
created to fulfil the market needs.
Member types – To name a few:
• ISPs & Telcos
• Academic Networks
• Content Providers & Hosting Companies
• CDNs
• Gaming Companies
• Streaming Media
• E-Commerce Companies
• Large Enterprises
7. TPIX - not only for …
TPIX is more than just a Public Peering Service:
• Internet exchange: OpenPeering / Public Peering switch
• Voice Interconnect: IPX services
• Multicast IPTV access
• Multicast exchange
• Closed User Groups (a shared VLAN between multiple ports)
• Private Interconnect (i.e. with Tier 1, Orange)
• IP Transit
• Aggregation Port
Cost reduction due to access to variety of services through a single port!
• low fees for 1/10/100GEth ports
• affordable (low) price for access outside Warsaw
8.
9. before we start…
What to do if you’re about to start a new IXP:
1.Market Research:
• low cost peering platform for the Orange’s customers (and other).
• high price for an access to existing IXP (exceeds the IP transit’s price)
2.Build a community:
• (try to) be neutral - build/buy the access and sign an agreement
• be pragmatic
3.Build a platform: Switches, Servers, Software and Space…
10. TPIX - early 2010 requirements list
1.Network devices:
• capable of 20-40Gbps peak traffic
• 40 customer ports
• 10Mbps, 100Mbps, 1Gbps, 10Gbps ports
• flexible configuration (i.e.: multiple services on single port)
2.Portal/website: tpix.pl webpage using the existing infrastructure
3.Services: quarantine vlan, route-server, public peering
4.Central location with good connectivity options:
• LIM Building
• OPL: Piękna / Nowogodzka: former Polish NAPs
11. TPIX - 2010 hardware (grow to scale)
1.Network devices: (retracted from the OPLs networks)
• Juniper MX960 for a service core
• Cisco 7600 for an access (later replaced with an Juniper EX4500)
2.Servers: x86 servers - quarantine, route servers (redundancy)
MSA
MX960 Core
Nowogrodzka
7600
Access
7600
Access
TPNET
LIM Piękna
12. TPIX - 2010 Core - MX960
• used by Orange (low cost of implementation)
• advanced support for ethernet bridging / switching
First architecture: Bridge domains
• flexible VLAN support - rewrite tags
• layer 2 filtering - ethertype, src/dst macs, etc
• layer 3 filtering
Integrated bridging and routing (IRB)—Support for both Layer 2 bridging and
Layer 3 routing on the same interface. Frames are bridged if they are not sent to
the router's MAC address. Frames sent to the router's MAC address are routed
to other interfaces configured for Layer 3 routing.
Client C
Client D
Client BClient A
bridge domain
VLAN 100
802.1q
trunk
VLAN BVLAN AVLAN D
VLAN C
TPIX L3
domain
IRB
13. TPIX - 2015-2016 reconstruction (scale to grow)
• connected capacity (customers only): ~ 850 Gbps
• new devices introduced: MX2020, QFX5100, vMX
• new cards: MPC4E - high port density, lower TCO
• 100Gbps ports (MX960/MX2020)
Architecture: VPLS
• smooth transition
• increased reliability & monitoring
• fast reroute & QoS
• Layer 2 CUG: VPLS based
• Layer 3 services: Multicast (ng-mvpn)
LIM PięknaNowogrodzka
14. TPIX - 2010-2016 bugs and problems
• unknown unicast problem: Bridge Domains / VPLS
• RPD crash: MPLS ping
• ….
• more ports, more cards…