IPv6 @ TCL %5BCompatibility Mode%5D

8/2/2019 IPv6 @ TCL %5BCompatibility Mode%5D

1/34

IPV6

Tata Communications Ltd.(VSNL)

Shailesh Gupta, Vice PresidentRaju Raghavan, Manager


2/34

Contents

Tata Communications ISP Network Journey since Aug15th, 1995

Advantages of IPV6 over IPV4

IPV6 Drivers & design in TCL Network

IPV6 Customers of TCL, India

Expectations from GOI/DOT/TEC for promoting IPV6 in India

Thanks


3/34

TCL Global Network

Mumbai

Ernakulam

Chennai

Colombo

Singapore

Hong Kong

Tokyo

Dubai

Frankfurt

London

New JerseyNew York

Palo Alto

TCL -7xGig

NTT-GIGTCL -2 fGigGoogle - Gig

KDDI-2XDS3

EMIX-2 x DS3

TCL - 3-Gig

TCL -8xGig STM1

5

Santa Clara CT -DS3China

PLDT-DS3

CAT Thailand DS3

KoreaTelecom

STM1

Madrid

Paris

Amsterdam

Chicago

Dallas

TCL -4xSTM4TCL - 2*10GIG

Google-3Gig

SMW-3TAT-14AC-1PEBTIC

Singtel-STM1TM-DS3CHT-DS3

SAFE+TM+APCN-2+J-USReach IPLC

MSN-Gig

Sydney

-

TCL -4xSTM16TCL 2*10GIG

TCL -2xSTM-4

* Dual stack edge and core .** Independent core topologies for IPv4 and IPv6


4/34

FLAG

SEA-ME-WE3

Kolkat

aMUMBAI

International Connectivity

Pacific route

Chennai, India

SINGAPORE

SEA-ME-WE3

SEA-ME-WE2

SAFE

India Singapore

Cable System5.12 TbpsSEA-ME-WE4(RFS by Mid

2005)

Pacific RouteAtlantic Route

Network Administration Rights

Submarine Cable & Carrier Level

Redundancy

TATA Indicom is the Only Carrier

having capacity on 5 out of 5 cables

into India

COCHIN

CHENNAI


5/34

Tata Communications - India Network Footprint

Its all about connectivity ....All Over India

117 location across thethe India.

3-tier Hierarchicaltopology for bettermanagement.

including 4 metros

7 Major Tier 2 cities.

101 Tier 3 cities

* Serves the length and breadth of India.** IPv6 Dual stack edge with MPLS tunneled core.


6/34

International Bandwidth Growth (Mbps)

International Usable Bandwidth

40000

55000

73000

50000

60000

70000

80000

Usable Bandwidth

0.064 10 24 69 211 666 816 834 848 1160 24804800

800010928

0

10000

20000

30000

Aug'95

Jan'96

Jan'97

Jan'98

Jan'99

Jan'00

Feb'01

Jan'02

Jan'03

Jan'04

Jan'05

Jan'06

Dec'06

Feb'07

2008

2009

2009-H2

1140625 times growth in 15 Years


7/34

IPV6 Pool allocated to TCL from APNIC


8/34

IPv6 Drivers anddesign in the TCL

network.


9/34

A perspective on Global IPv6 Business drivers:

Global IPv6 Routes Global IPv6 ASes

The IPv6 routes in the global routing table has grown from 500 prefixes in2004 to around 1200 prefixes in 2008.

The IPv6 ASes in the global routing table has gone from 400 ASes in 2004to around 900 ASes in 2008. A two fold increase. (IPv4 ASes - 28000 )

One of the prime drivers for IPv6 adoption globally hasbeen Service Differentiation and the pursuit of competitiveadvantage (First Mover).


10/34

Fixed Length of 40 bytes = no length

field

Variable

Length

IPv6 Technical strengths over IPv4:

Remove unwanted header fields

Simple header.

8 Fields

Less fields means lesser processing good for devices which have lesser

processing power?


11/34

IPv6 Technical strengths over IPv4: Key

Highlights:

Quality of service Model Enhancements

Preserve existing DiffServ model

Plus Flow Label

More granularity in classifications based on flows.

Plug and Play Architecture:

IPv6 is designed with plug and play in mind.

Stateless Auto configuration auto IP Addressing (In

the absence of a DHCP server).

Link Local auto generated address.


12/34

Tata Communications IPv6 Enabled networks

overview

o TCL India Network:

Serves the length and breadth of India.

IPv6 Dual stack edge with MPLS tunneled core.

o TCL Global network:

Dual stack edge and core .

Independent core topologies for IPv4 and IPv6.


13/34

Tata Communications India model | IPv6 deployment

Model :We had to choose a mechanism that helps in seamless migration without

disrupting existing services.

The TCL network is end to end MPLS enabled.

The obvious choice was to tunnel IPv6 packets over MPLS using the 6PE6PEmechanism.mechanism.

TCL IPv4 MPLS

Cloud

IPV6 CustomerNetwork

IPV6 internet

IPV6 CustomerNetwork

RR

Dual stack

enable the

PE routers.

Enable labeled IPv6

signaling over the

BGP session to RR

Establish

Connection to IPv6

Internet


14/34

TCL International Network | Dual Stack/Multi

Topology:

o Dual stack Backbone and Edge Routers.o Independent topologies for IPv4 and IPv6 to cater to H/W

limitations/issues.

-

Multi-Topology ISIS protocol builds

A B

C

E

A

- IPv6 Topology

- Dual Stack PoPs

D

F


15/34

A few TCL IPv6 highlights globally over the years:

o TCL promoted the experimentation of IPv6 andthe 6bone/6TAP initiative as a member of the

Canarie Policy Board.

.

o TCL provided IPv6 connection to the last

SANOG meeting.


16/34

IPV6 Live customers with TCL, India

Tata - NIXI Mumbai connectivity Getting

few prefixes from RIC & Netmagic 3

prefixes ,one /48 from NIXI(2001:DE8:1::/48), one each from Netmagic

& RIC

Honesty (ISP) at Mumbai

IIT Kanpur 1 Gb

40+ international IPV6 customers


17/34

IPv6 Enterprise Customer DeploymentIPv6 Enterprise Customer Deployment

IPV4 - 3.4 L+ routes in global routing tableIPV6 15000 routes in global routing table


18/34

Expectations from GOI/Regulator/Licensor

NIR for IPV6 to manage resources in a better way & promote usage of IPV6 in India

IPV6 workshop/training for SPs / Corporates. APNIC already organizes such trainings

Invite equipment vendors and Applications vendors to collaborate and create amultivendor IPv6 test bed. (This will help in increasing the IPv6 acceptance in the India

Enterprises)

This should demonstrate IPv6 application interoperability across multipleapplications vendors like Oracle, SAP, Windows, Linux, database applications etc.,

This should demonstrate IPv6 transport interoperability across many IP equipmentvendors such as Cisco, Juniper, Huawei Alcatel etc.,

Free/Subsidized IPV6 session/port with NIXI

Extended Support of OEM for upgrading box to support IPV6.

IPV6 discussion forum for resolving day-day issues


19/34

The more seeminglyimpossible the goal, the more

glorious is the triumph of

achievement!

To ether we canTo ether we canTo ether we canTo ether we can

together we will!together we will!together we will!together we will!


20/34

Backup

Slides


21/34

1. IPv6 Enterprise Customer Deployment (Honesty, Mumbai)

Customer Expectations:

Reachability of customer IPv4 and IPv6 prefixes in Internet Domain.

Customer required Full IPv6 route from Tata Communications (15 K)

Both IPv4 and IPv6 sessions on same link.

Scenario

Customer is having IPv6 prefixes with his own AS number.

wants to run IPv6 BGP session with Tata communications on his existingIPv4 link.

Customer is already running IPv4 BGP session on same link for his IPv6Prefixes.


22/34


Challenges:

Propagating Customer IPv6 prefixes in Internet Domain.

ensuring propagation within Tata communication domain

ensuring propagation within Tele globe domain.

ensuring proper Hand-off between these Two domains. Establishment of IPv6 BGP session and IPv4 BGP session on same link.

Configuring proper route-map and IPv6 Prefix lists.

Proper network and mask configuration w.r.t. /128 mask to avoidroute leakage and improper announcements to Customer as wellas to upstream provider.

Testing


23/34


PE Configs :

interface Vlan2455description 022100167783/Honesty net solutions (India) Private Limited/Bhandup (West)Mumbai/STDILL/20MB/VBLip address 115.113.128.85 255.255.255.252ipv6 address 2403:0:100::1/126ipv6 enable

address-family ipv6no synchronizationnetwork 2403:0:100::/126

neighbor 2403:0:100::2 activateneighbor 2403:0:100::2 prefix-list HONESTY_IPV6 inneighbor 2403:0:100::2 maximum-prefix 1000 100 restart

ipv6 prefix-list HONESTY_IPV6: 1 entriesseq 10 permit 2401:4800::/32 le 64

Testing:PE#sh bgp ipv6 sumBGP router identifier 192.168.196.5, local AS number 4755

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

2403:0:100::2 4 38457 39935 653236 3495885 0 0 3w4d 1


24/34


Testing:PE#sh bgp ipv6 unicast neighbors 2403:0:100::2 routes

BGP table version is 1572300, local router ID is 192.168.196.5Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

r RIB-failure, S StaleOrigin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path*> 2401:4800::/32 2403:0:100::2 50 0 38457 i*> 2401:4800:1::/64 2403:0:100::2 50 0 38457 i

*> 2401:4800:11::/64

2403:0:100::2 50 0 38457 ?

Total number of prefixes 3mu-lvs-lvs-mi01-rt01

ICG#sh ipv6 route 2401:4800:0:21::1

IPv6 Routing Table - 1585 entriesCodes: C - Connected, L - Local, S - Static, R - RIP, B - BGP

U - Per-user Static routeI1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summaryO - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2

B 2401:4800::/32 [200/50]via ::FFFF:192.168.196.5, IPv6-mpls


25/34


Testing:

Trace from Looking Glass

Router: gin-mtt-mcore3Site: CA, Montreal - MTT, TATA COMM. INT. CENTERCommand: traceroute ipv6 2401:4800:1::2

Tracing the route to 2401:4800:1::2

1 if-13-0.mcore4.nqt-newyork.ipv6.as6453.net(2001:5A0:300:100::2) 8 msec 8 msec 8 msec2 2001:5A0:400:100::16 204 msec 200 msec 200 msec3 2001:5A0:2300:100::6 204 msec 204 msec 200 msec4 2401:4800:1::2 208 msec 204 msec 208 msec5 2401:4800:1::2 204 msec 208 msec 204 msec


26/34

192.168.132.232

mu-mhp-vas-mi04-rt01

Gi2/13

NIXI router

76067606

Tata-Mumbai-VashiFibre-to-ElectConvertor(gig)

2. IPV6 Deployment NIXI, Mumbai

ASN : 24029

Note 1:Advertising specific 4755 IPv6 network, 2403::/32 on this session whileaccepting specific NIXI customer (Reliance & Netmagic) ipv6 n/w with no-export

Note2:The ipv6 networks from 6453 (around 1600 prefixes) and 4755 ipv6 n/wavailable in Mumbai ICG were passed to Vashi Micropop during this implementationto cater NIXI customers as well as our customers


27/34

mu-mhp-vas-mi04-rt01#sh run | inc 2001:DE8:1::1neighbor 2001:DE8:1::1 remote-as 24029neighbor 2001:DE8:1::1 description ***eBGP IPV6 with NIXI ***no neighbor 2001:DE8:1::1 activate

neighbor 2001:DE8:1::1 activateneighbor 2001:DE8:1::1 route-map NIXIV6-IN inneighbor 2001:DE8:1::1 route-map NIXIV6-OUT outneighbor 2001:DE8:1::1 maximum-prefix 1000 100 restart 30mu-mhp-vas-mi04-rt01#sh route-map NIXIV6-INroute-map NIXIV6-IN, permit, sequence 10

Match clauses:as-path (as-path filter): 100Set clauses:

community 4755:98 4755:2255 no-exportPolicy routing matches: 0 packets, 0 bytes

mu-mh -vas-mi04-rt01#sh i as- ath-access-list 100AS path access list 100

permit ^24029$permit 18101permit 17439

mu-mhp-vas-mi04-rt01#sh route-map NIXIV6-OUTroute-map NIXIV6-OUT, permit, sequence 10

Match clauses:ipv6 address prefix-list TATAV6

Set clauses:Policy routing matches: 0 packets, 0 bytes

mu-mhp-vas-mi04-rt01#sh ipv6 prefix-list TATAV6ipv6 prefix-list TATAV6: 1 entries

seq 5 permit 2403::/32


28/34

mu-mhp-vas-mi04-rt01#sh run int gi2/13Building configuration...

Current configuration : 381 bytes!interface GigabitEthernet2/13description NIXI DEMO LINK FOR ipv6 TEST | Direct Physical connection to NIXIwitch through Tata owned Opt-to-Elect Convertor | 16Dec08

no ip addressipv6 address 2001:DE8:1::3/64ipv6 enablewrr-queue cos-map 3 1 7

pr or y-queue cos-map

rcv-queue cos-map 1 4 1 3rcv-queue cos-map 1 6 0 2 4 7rcv-queue cos-map 1 8 5 6end

mu-mhp-vas-mi04-rt01#ping ipv6 2001:DE8:1::1

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 2001:DE8:1::1, timeout is 2 seconds:!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/4 ms


29/34

Currently, only a /36 (2403::/36) from the Global space has been used.

8 numbers of /40 used for infrastructure and other 7 cities namely Mumbai,

Chennai, Ernakulam, Delhi, Bangalore, Hyderabad, Kolkata (excel sheetsattached).

As per IPv6 LLD we have calculated /40 subnets into smaller subnets to arrivedifferent WAN/loopback and Customer IP

E.g. Mumbai 2403:0:100:0:0:0:0:0 /40 subnetted to /48s

First 2403:0:100:0:0:0:0:0/48 subnetted to /64s. For customers we will allocate/64 LAN IP.

First 2403:0:100:0:0:0:0:0/64 is further subnetted till we get2403:0:100:0:0:0:0:0 /112 and WAN IP given to first customer.

Please go through the IPv6 LLD.


30/34

IPv6 business drivers : Future?Mobile Internet age:

Smart Phones?

3G and 4G with high BW internet access would be the drivers?

Network Mobility IETF NEMO WG defines IPv6 on mobilenetworks like IPv6 on Cars etc., ?

Refer rfc3963.txt for more information.

Number of IPv6 addresses :

If we do some simple math: (Divide the number of IPv6 addresses by IPv4 addresses)

340,282,366,920,938,463,463,374,607,431,768,211,456 (number of IPv6addresses)

4,294,967,296(number of IPv4 addresses)

= .792 million trillion IPv4 Internets make an IPv6 internet ( from a number of

hosts perspective)


31/34

IPv6 Technical strengths over IPv4:

Granular QoS:

Diffserv / IP Precedence Diffserv / IPPrecedence

+More granularity and differentiation

Flow Label (20 bits): Identifies application

flows Per flow QoS for nextgen applications


32/34

IPv6 Strengths : Plug and Play:

Reboot

Router Solicitation = Please send

subnet prefix.Src= Link Local Address (FE80::/10)

Dst = All routers multicast address (FF02::2)

IPv6 supports plug and play with stateless auto configuration.

A

N

IPv6 Host

Router Advertisement = Subnet

Prefix (IPv6 prefix), lifetime and

autoconfig flag.Src= Link Local Address (FE80::/10)

Dst = All nodes multicast address (FF02::1)

IPv6 has link local addresses, so on a local lan even without any protocol exchanges

the IPv6 can start communicating.


33/34

IPv6 prefix and traffic flow in the Tata

Communications network:

A label is generated forthe IPv6 prefix = Label 10

The Label 10 and the IPv6prefix 2403:1::/48 is

advertised to the remote PEwith IPv6 mapped next hop:FFFF:192.168.1.1

v

Cloud

Advertises an IPv6

Prefix : 2403:1::/48MP BGP

BGP Update

source IPv4

address =

192.168.1.1

BGP Update source

IPv4 address is

converted to IPv6

mapped address

::FFFF:192.168.1.1

RR


34/34

IPv6 prefix and traffic flow in the Tata

Communications network:

The destination PE installsthe route in the routing tablewith ::FFFF.192.168.1. asnext hop.

PoPMPLSLabels

v

Cloud

MP BGP

BGP label is

configured as

Inner label

The IGP label

corresponding to

::FFFF.192.168.1.1

(192.168.1.1) is configured

as the outer label .

IPv6 Packet

IPv6 PacketMPLS LabelsIPv6 Packet

packet toCPE.RR

IPv6 @ TCL %5BCompatibility Mode%5D

Documents

Transcript of IPv6 @ TCL %5BCompatibility Mode%5D