Koç.net’s Multiprotocol Label Switching Solution VPN is created especially for needs of corporate world. Koç.net’s MPLS VPN offering is a network-based IP VPN service built on a converged MPLS backbone. Koç.net is the first MPLS provider in Turkey and 6th MPLS/VPN provider in the world.

Koç.net innovative and converged MPLS backbone allows our customers to prioritize their network application traffic with CoS capabilities, so the performance of high-priority applications like voice or video is not compromised by other applications, such as email. Koç.net offers a completely flexible service which gives our customers the ability of share their data securely, quickly and cost- effectively.
Koç.net MPLS VPN solution provides:

  • Flexibility: Koç.net MPLS VPN structure supports different access technologies from SDSL to metro ethernet with different speed options from 64 Kbps to 34 Mbps.
  • Security: Fibre optic circuits protected by SONET or SDH are highly resistant to tampering-providing an extra level of security and restorability.
  • Reliability: High standards of accuracy and system availability, including 99.97 percent availability for point of presence POP-to-POP service.
  • Expandability: The service is designed to be flexible, so transmission capabilities can readily expand to meet changing requirements.
  • Cost-efficiency: Koç.net MPLS coverage and competitive prices help customers to get the maximum value by decreasing the bandwidths with CoS definitions and using the cheaper access technologies
  • Simplicity: International Private Line offers a single point of contact to manage the end-to-end solution

Available Access Technologies:

  • ADSL/SDSL
  • Leased Line
  • Metro Ethernet

Basic Network Architecture

Koç.net is a Cisco Powered Network. Frame-mode MPLS is running on the core. Six Provider routers (P) are High-end Cisco routers. Besides this, Provider Edge (PE) routers are also High-end Cisco routers. Over MPLS-enabled network, Layer-3 VPN services, end-to-end Quality of Service Voice over IP services are given to customers. MPLS/TE is also deployed over the network in order to balance the traffic flowing through the core. P-PE and PE_PE Tunnels are implemented, particularly. In MPLS operation, TDP is on and OSPF is the IGP being run. For VPNv4 prefixes, MP-BGP is the default routing protocol.

There are thirty-two point of presences (PoP’s), including Frankfurt PoP. Over these POP locations, customers are connected through several transmission mechanisms, such as Leased Lines, Frame Relay, DSL, etc. and all are attached to a VPN for their purposes.

Network Management-Reporting

Istanbul is the capital city of industry so Koç.net NOC has been built in Istanbul after several site surveys in fully owned campus area. However, all Management Systems in Istanbul NOC (Network Operation Centre) have backups in DRC in Ankara. Ankara Disaster Recovery Centre makes it possible to run Koç.net managed services in case of a disaster in main data centre. Every item on MPLS backbone can be up & running in few seconds from Ankara DRC.


CA Unicenter Enterprise Umbrella system has been chosen to be running on Koç.net NOC. CA Unicenter Serviceplus Service Desk Trouble ticket and workflow management system is used for automatic trouble ticket generation and problem management, escalation, bonding to a partner system etc... Ciscoworks 2000 was deployed and used for Configuration and Inventory Management of Cisco Devices.

This architecture enables Koç.net web based reporting and customer support;

  • Requests and problems from external customers can be posted via web, phone, e-mail, or fax.
  • MRTG Graphs will be accessible over web site for Bandwidth usage,
  • Availability reports can be reached over web
  • Trouble ticket reports can be reached over web
  • Incident reports can be reached over web
  • Security breaches reports can be reached over web

MPLS Interconnection Architecture at the Physical Layer

The interconnection can be implemented via a Local Loop or by means a Local cable. In terms of transmission capacity the standard values are: E1, E3 or OC-3. For local cabling Fast Ethernet or Gigabit Ethernet connections are available.

MPLS Interconnection Architecture at the Transport Layer

The transport layer interconnection depends on the interface used. Koç.net proposes the following transport protocols:

  • Frame Relay encapsulation for E1/E3/OC3-STM-1POS cards
  • Encapsulation  dot1Q for Fast Ethernet card

MPLS Interconnection architecture at the IP Layer

The Koç.net IP interconnection model is based on the following standard:
- RFC2547bis Option A (VRF – VRF)

For each customer VPN, a Virtual Channel/Circuit (VC) is dedicated across the interface. At the IP level, each VPN generates its own Virtual Routing and Forwarding (VRF) table and its own corresponding dot1Q or FR sub-interface (VC). The routing protocol between the two ASBRs is external-BGP. The following figure provides a sketched representation of the main features of RFC 2547 bis Option A.
Currently there is no implementation of Inter AS MPLS IP VPN on Koç.net backbone.

MPLS “ToS Transparency” Feature

The “ToS Transparency” is a network feature that allows transparently transporting the Type of Service (ToS) field of the IP packet Label without to modify the value all within the
IP/MPLS network (CE <= => PE <= => P <= => PE <= => CE).
The routing and priority are managed within the network according to MPLS label information.
Koç.net guarantees the implementation of the ToS transparency feature across its own network.

MPLS-Classes Of Services

The Class of Service (CoS) Model is based on “precedence” bits. There are three classes of which are Gold, Silver and Bronze. The Gold class is the real-time traffic and marked with Precedence 5, MPLS Exp. Bits 5. The Silver class, the business traffic in contract, is based on Precedence values of 1, 4 and 6, MPLS Exp. Bits 1, 4 and 6 as well. For the Bronze class the default-class is used, for specific purposes, Precedence 0, 2 and 3 values are in common. LLQ is implemented throughout the network, including PE-CE and CE-PE connections in order to reach to desired Quality of Service. In LLQ operation, priority class is used for Gold class traffic and the desired bandwidth is given for this class for good voice and video quality. The Silver class is allocated for a certain amount of bandwidth and the rest is for default class that can be named as bulk data. For Silver and default class, WRED is in taken into consideration for a better throughput.

 

CoS

 

IP Prec

EXP

Koç.Net

Gold

Real Time

5

5

Silver

Business

6

6

4

4

1

1

Bronze

Default

0,2,3

0

Infrastructure Standards
Koç.net Autonomous System Border Router (ASBR) and PE consist of the Cisco System Router 7206/7513/12000.

CE Access Configuration

Koç.net connects the CE to PE routers using Layer 2 WAN Protocols,  HDLC, Frame Relay, PPP, ATM  ( For G.SHDSL Connections). Static Routing, eBGP, OSPF, RIP Version 2 are supported .VRF aware EIGRP can be supported with 12.4 or later series IOS in PE routers

CE Management Principles

Customer routers that are connected to Koç.net backbone, could be managed by Koç.net or Customer. Both options are available. If routers will be managed by customer, WAN IP addresses must be exported to management VRF of the customer network.

Structure deployed on the Koç.net backbone;

  • Is flexible and expandable.
  • Utilized technology keeps operation and equipment costs at minimum level.
  • Operates with high security and high speed.
  • Expert employees detect problems instantly and provide solutions for them. 7x24 Call centre and operation are available for help.
  • Has the highest performance with today’s technology.
  • Operates with Service Level Agreement (SLA).
  • Disaster Recovery Centre provides uninterrupted access with backup lines.
  • Automated System & Network Management enables troubleshooting problems even before you are aware of them.
  • Koç.net maintains educated and certified technical staff in order to keep this system up and running.

Availability & SLA

  • Local tail availability: % 97
  • Backbone availability : %99,7
  • Backbone delay: 60 msn
  • Backbone packet loss: 0,9 msn