QoS

1
QoS MPLS deployment activity in Korea Telecom

• Korea Telecom Laboratory
• Yeong-il, Seo
• syi_at_hana.ne.kr

2
Contents

• Introduction to QoS MPLS deployment activity in
  Korea Telecoms commercial internet(Kornet)
• Kornet QoS Implementation steps
• MPLS VPN experiments in Kornet
• MPLS VPN Basic function test
• Baby Giant Frame handling test
• InternetMPLS VPN function test
• VPDNMPLS VPN interoperability function test
• Inter-operability test between Juniper and Cisco
  in MPLS
• Aging test for bug fixed cisco GSR IOS
• Remark

3
Introduction to Korea Telecoms commercial
internet

• Kornet Korea Telecoms commercial internet
• Kornet consist of
• Nation-wide internet Backbone
• 160 GSRs, 540 75XX series routers, 180 GESs
• 2 central POPs,102 regional POPs(35 giga POPs),35
  ADSL aggregation POPs
• Most of links 2.5G POS, GE(10GPOS 4Q.01 in
  central POPs)
• Nation-wide internet exchange center, internet
  data center
• World-wide overseas connections
• Traffic volume 3040Gbps
• 3.5 million high-speed subscribers(LL,ADSL,metro
  Ethernet, etc.)
• Providing various types of B2B service models
  (VPN, VoIP, etc.)

4
QoS MPLS deployment activity in Kornet

• Whats done.
• Diffserv tests with KDD in APAN QBone
• Period Dec.99 Jul.00
• Test results were reported in APAN Tsukuba
  meeting, Beijing meeting.
• MPLS CoS tests with KDD in APAN Qbone
• Period Dec.00 Jan.01
• Test results were reported in APAN Hawaii
  meeting.
• MPLS VPN, TE, FR tests with Cisco, Juniper
  engineers in Kornet TB
• Period Feb.01 now
• Test results will be reported in this
  presentation.

5
QoS MPLS deployment activity in Kornet (cont.)

• What to do.
• Deploying MPLS VPN services in Kornet(4Q,01)
• Deploying MPLS TE,FR applications in Kornet(02)
• Providing differentiated services for Premium
  subscribers(02)
• Providing QoS for VoIP traffic of Kornet
  customers(02)
• Deploying scalable QoS management tool(02)

6
Kornet QoS Implementation steps

• Phase 1
• End-to-End Static QoS infrastructure by using of
  various Diffserv (or CoS) QoS mechanisms
• Static QoS provisioning
• All routers in the network are QoS enabled
• Policing/remarking at the edge of the network
• Provide differentiated treatment of traffic on
  the access and egress links
• Three traffic classes Premium (for high-speed
  subscribers), Best effort(for default, normal
  users), and VoIP traffic of Kornet customer

7
Kornet QoS Implementation steps(Cont.)

• Phase 2 Deployment of scalable QoS management
  system
• Providing of Policy server, Bandwidth broker
  functions
• Providing of QoS monitoring, reporting functions
  
• Final phase End-to-End MPLS Enhancing QoS
• Diffserv (or CoS) aware MPLS Traffic Engineering
• Utilizing MPLS explicit routing to reroute
  traffic for congestion and failure
• Relieve Backbone link congestion and intra-nodal
  congestion
• MPLS should support for Diffserv (or CoS) via
  E-LSP for whole routers(Auto mapping of IP CoS or
  DSCP field
• to MPLS shim headers)

8
MPLS VPN experiments

• Test items
• MPLS VPN Basic function test
• Baby Giant Frame handling test
• InternetMPLS VPN function test
• VPDNMPLS VPN interoperability function test
• Inter-operability test between Juniper and Cisco
  in MPLS
• Aging test for bug fixed cisco GSR IOS
• Place for Kornet testbed
• Cisco official test center (MELBOURNE, AUSTRALIA
  )
• KT Labaratory testbed (Connected to APAN)
• Testbed consist of
• 8 Cisco GSRs, 9 Cisco 75XXs, 5 Cisco 36XXs, 10
  Cisco 26XXs, 5 Juniper routers(M20,M10,M5 in LT
  Lab.)
• Cisco NAS 1 LNS, 1 LNC
• RADIUS authentication server 2 sets
• NAT Firewall 1 set

9
MPLS VPN Testbed total topology
US reg. POP
GR Center
Guro KIX
AP-HUB
MPLS VPN RRS
DR reg. POP
KJ reg. POP
BS reg. POP
HH KIX
HH center
er
10
MPLS VPN Basic function test
11
MPLS VPN Basic function test (Cont.)

• Object
• After setting up basic configurations for MPLS
  VPN service in Kornet, to check Tag-switching
  function, VPN service function, degradation of
  network performance.
• Test scenario
• For basic MPLS function, setting BGP and
  IGP(ISIS) from BB routers to regional POP
  routers.
• For MPLS VPN service, upgrading routers IOS
  version(with Cisco recommended version).
• P IOS 12.0(15)S3
• PE IOS 12.1.(5c)
• Configuration of VRF, RT in each nodes PE
  routers, Internet PE router, RR server routers
• Configuration of MP-BGP
• Configuration of routing protocols between PE
  routers and CE routers(Static, RIPv2, BGP)

12
MPLS VPN Basic function test (Cont.)

• Test result
• To check the basic MPLS VPN functions among MPLS
  VPN subscribers Successful, but a serious Bug
  on Cisco GSR with IOS 12.0(15)S3 was founded!
• To check Tag switching enable function
• To check MP BGP connection set up function
• To check VPN RR connection set up function
• To check routing protocols between PE routers and
  CE routers (Static, RIPv2, BGP)
• To check the access function among same VPN
  subscribers
• Remarks
• What Bug report? As soon as enabling ip tag
  switching on GSR, some special GSRs CPU became
  overloaded(95). Even if in same situation, some
  GSRs were safe, some GSRs became crashed! So,
  this bug was reported to Cisco,and after2 months
  bug fixed IOS released. 12.0(18)S

13
Baby Giant Frame handling test

• Minimum 2 Labels are needed for MPLS VPN service.

14
Baby Giant Frame handling test(Cont.)

• Baby Giant Frame
• Whats the Baby Giant Frame handling ?
• In MPLS VPN service areas, whole Ethernet
  connection parts should handle IP maximum data
  size (1,500bytes) and 2 MPLS labels(8bytes).
• If not, LSP will be broken, PEs cant communicate
  to each other in Baby Giant Frame case.
• Baby Giant Frame handling test
• Cisco catalyst GES, Extreme GES
• Succeeded in handling Baby Giant Frame!
• 3Com GES
• Failed to handle Baby Giant Frame!

15
InternetMPLS VPN function test
16
InternetMPLS VPN function test(Cont.)

• Object
• To provide MPLS VPN users with reliable internet
  access
• To provide a blocking to illegal access from
  internet
• Test scenario
• To exchange full routing information between
  internet PE and VPN PE
• To check a blocking to illegal access from
  different VPN user via internet PE
• To configure routing protocol between internet PE
  and CE(PIX), ex.Static
• To distribute default routing
• By using NAT, to provide internet access service
  in Firewall(PIX)
• To activate Firewall service

17
InternetMPLS VPN function test(Cont.)

• Test result
• Successful Internet access for VPN user
• Successful blocking to illegal access from
  internet
• Successful blocking to illegal access from
  different VPN user via Internet PE
• Remarks
• In case of different VPN users using the same
  private IP addresses, duplication of private IP
  address can occur in Internet VRF.
• To solve this,
• By activating NAT function in CE router of HQ
  site
• By allowing different private IP address block to
  each VPN users under the control of ISP

18
VPDNMPLS VPN interoperability function test
19
VPDNMPLS VPN interoperability function
test(Cont.)

• Object
• To provide MPLS VPN service for Dial-up and ADSL
  users
• Test scenario and result
• To set up LAC(L2TP Access Concentrator) function
  on ADSL NAS(Network Access Server)
• To set up an authentication server on VPN user
  site, check the authentication function for the
  VPDN user and MPLS VPN service access feature of
  VPDN user
• succeeded
• To set up an authentication server on ISP site,
  check the authentication function for the VPDN
  user and MPLS VPN service access feature of VPDN
  user
• succeeded

20
Inter-operability test between Juniper Router
and Cisco Router in MPLS VPN

• Object
• To check inter-operability feature between
  Juniper Router and Cisco Router in MPLS VPN
  service enabled network
• Test environment
• Cisco router Standard LDP supporting IOS
• GSR, 75XX, 72XX 12.0(10)ST
• 4x00, 3600 12.2(1)T
• Juniper router Junos 4.4
• Test scenario and result
• Juniper PE - Juniper P - Juniper MPLS VPN RRS
  succeeded
• Juniper PE - Cisco P - Cisco MPLS VPN RRS
  succeeded
• Cisco PE - Juniper P - Cisco MPLS VPN RRS
  succeeded
• Cisco PE - Juniper P - Juniper MPLS VPN RRS
  succeeded
• Cisco PE - Cisco P - Cisco MPLS VPN RRS
  succeeded

21
Aging test for bug fixed IOS of Cisco GSR

• Test environment
• Replace Cisco GSR IOS with Bug fixed version
  12.0(18)S
• Network condition
• BGP routing table size over 100,000
• Loaded from Smartbit(Packet Generator)
• Test duration 4 days
• Test result
• Reasonable processor consuming!
• Stable operation!
• As PE router, Cisco 3600, 4X00 routers are not
  adequate because of low performance.

22
Remarks

• QoS management tool
• Deploying result of scalable QoS management tool
  in Kornet will be presented in near future.
• VoIP QoS
• Deploying result of VoIP service with QoS in
  Kornet will be presented in near future.
• MPLS enhancing QoS
• Now, Juniper and Cisco accept RSVP for MPLS TE,
  not inter-operable with other vendors in MPLS FR
  feature. Further reaserch standardization
  activity is needed in this area.
• Test and Deploying result of DS aware TE feature
  in Kornet will be presented in near future.
• Deploying result of MPLS management tool in
  Kornet will be presented in near future.
• If you have any questions, please send me email
  to following address! syi_at_hana.ne.kr