Toward the road to NGI: IPv6 multicast operation of IPv6-CJ backbone

Transcription

1 Towad the oad to NGI: IPv6 multicast opeation of IPv6-CJ backbone Li Zimu, Wang Jilong, Li Xing, Wu Jianping, An Changqing China Education and eseach Netwok (CENET) Cente Tsinghua Univesity, Beijing PC Telephone: {lizimu, xing, Masukawa Hioshi, Hitachi, Hitoshi Yoshida, Hitachi, Suzuki Yuichi, NEC, Moino Masaaki, NEC, Abstact As an IP laye potocol offes the scalable point-to-multipoint delivey necessay fo using goup communication applications on the Intenet, IP multicasting has been becoming a easonable way to educe heavy taffic on backbone in a cetain situation whee same packets flow fom one souce to multiple destinations, especially in the Next Geneation Intenet (NGI) in which temendous PCs, AI machine, cell phones etc. communicate with each othe with IPv6 addesses. IPv6-CJ is the most impotant IPv6 joint poject suppoted by Japan and China govenments and moe than 20 oganizations and companies fom Japan and China take pat in this poject. This pape depicts in detail of IPv6 multicast opeation of IPv6-CJ backbone which consisted of thee diffeent IPv6 oute vendes: Hitachi, NEC and Fujisu. IPv6 multicasting inteopeability between these outes is exploed and a novel method is poposed to solve the multicast inteopeable poblem. By an ingenious multicast bidge, a host with pim6sd and oute6d on FeeBSD 5.4, Hitachi oute can multicasting IPv6 packets fom Beijing to Fujisu oute in Shanghai and NEC oute in Guangzhou without native IPv6 multicast suppot on IPv6-CJ backbone. The tial shows how to establish well-designed IPv6/IPv4 multicast bidge between diffeent vendes IPv6 oute and gives some valuable hints fo IPv6 multicasting between multicast islands. The expeience will be geat helpful fo IPv6 multicast migation fom IPv4 to IPv6 in eal-wold and fo futue IPv6 multicast opeation in NGI envionment which possible be consisted of many outes fom diffeent vendes. Configuations of outes and tunnels ae povided as well as diagnostic infomation is analyzed. Key wods: NGI, IPv6, multicast, tunnel, oute

2 Intoduction CNGI-6IX 1G 45M Tokyo 2.5G POS 1G Ethenet 100M Ethenet BUPT BUAA Tsinghua CAS CSS BIT PKU Beijing Guangzhou SCNU SCUT SCUT IPv6-CJ Backbone TongJi SJTU FuDan Shanghai SHU JNU SCAU DHU ECNU (2) China Education and eseach Netwok 1. Intoduction IPv6-CJ is the lagest IPv6 joint poject by now suppoted by Japan and China govenment stated 3 yeas ago and will be finished at the end of Apil The poject is opeated by CIAJ (Communications and Infomation netwok Association of Japan ) and CENET (China Education and eseach Netwok). Its content is to establish an IPv6 test-bed between Japan and China and do eseaches on IPv6 key technologies include IPv6 oute, migation of IPv4 to IPv6, IPv6 multicast, IPv6 QoS, IPv6 netwok management and opeation, IPv6 mobile, IPv6 secuity, IPv6 applications and etc. on the test-bed. Moe than 20 oganizations and companies including Hitachi, NEC, Fujisu, Tsinghua Univesity, Shanghai Jiao Tong Univesity and South China Univesity of Technology take pat in this poject. IPv6-CJ testbed is as shown above which consists of 2.5Gbps backbone and Beijing, Shanghai and Guangzhou. It also connects with Japan by a 45Mbps cicuit and with CNGI-6IX (China Next-Geneation Intenet IPv6 exchange cente) by a 1Gbps cicuit. Thee Japan vendes, Hitachi, NEC and Fujisu, povide IPv6 outes fo this poject in which Beijing edge oute, coe outes and outes ae povided by Hitachi and Guangzhou coe outes and outes ae povided by NEC and Shanghai coe outes and outes ae povided by Fujisu. IPv6-CJ Backbone is a 2.5Gbps POS ing with six IPv6 coe outes fom thee Japan vendes, Hitachi, NEC and Fujisu, of whom each one povides two outes of them. This ing achitectue gives the backbone bette availability and taffic balance. Since IPv6 multicast is a key technology of NGI, multicasting tial on IPv6-CJ, especially multicasting among diffeent IPv6 vendes oute, plays an impotant ole in the eseach. The expeience will be geat helpful to multicast opeations and multicast applications in NGI envionment which might be consisted of many IPv6 outes fom diffeent vendes. This pape descibes the detail opeation of this IPv6 multicasting inteopeability tial among diffeent outes fom many vendes and shows some valuable hints fo IPv6 multicast opeation and futhe IPv6 multicast eseach.

3 IPv6-CJ Multicasting testbed MBidge Beijing POS IPv6 multicast Media Seve FE multicast unicast tunnel HITACHI G2000 BJ2 HITACHI G2000 BJ1 OC48-POS GZ6 NEC IX5010 OC48-POS NEC CX5210 GZ1 GZ2 NEC CX5210 multicast:mld+pim-sm+bs unicast: OSPFv3+IPng OC48-POS SH2 SH1 FUJITSU 980 FUJITSU 980 IPv6 multicast Media Client Shanghai IPv6 multicast Media Client Guangzhou (3) China Education and eseach Netwok 2. IPv6-CJ multicasting testbed and design 2.1 IPv6-CJ multicasting testbed The IPv6-CJ multicasting testbed is as shown above in which media souce in Beijing connects with the Hitachi coe oute G H (BJ2) and one media client in Shanghai connects with its local coe oute Fujisu 980 (SH2) and anothe media client in Guangzhou connects with its local oute NEC IX5010 (GZ6). Since NEC IX5210 is designed as backbone oute with fast outing and switching capability, it does not suppot IPv6 multicast at this time. Howeve the oute NEC IX5010 (GZ6) does. Now that Hitachi G H does not have the ability to un multicast on tunnel inteface, a multicast bidge called MBidge as shown above, a host with FeeBSD, has to be established to enable IPv6 multicasting with not only BJ2 but also GZ6. As shown above, the host MBidge has two physical links with BJ2 of which one link woks as tunnel and the othe woks as native. In this design, IPv6 unicasting path fom Beijing to Guangzhou is Media Seve BJ2 BSD BJ2 GZ1 GZ6 Media Client wheeas IPv6 multicasting path is Media Seve BJ2 tunnel GZ6 Media Client. The tunnel fom MBidge to GZ6 can be eithe of IPv6 and IPv4. It implies that IPv6 multicast islands, which cannot multicasting diectly in a native IPv6 netwok, can multicast though IPv6 tunnel o that IPv6 islands which isolated by IPv4 ocean can multicast IPv6 messages though IPv4 tunnel. Contast to cuent Intenet dominated by Cisco outes, NGI might be a lage inte-netwok consists of many diffeent vendes outes in which situation that the tial and expeience of IPv6-CJ multicasting among diffeent outes will be of valuable. 2.2 IPv6-CJ multicasting design To simplify the tial, we d like BJ2 to be the P (endezvous Point) and also BJ2 plays as BS (Bootstap oute) of the IPv6 multicast tee because Hitachi IPv6 outes have the equiement that P oute should also be a BS and they must wok togethe. PIM-SM and MLDv1 ae deployed to best fit the futue NGI multicasting situation. Windows 2003 Seve Evaluation with steaming sevice woks as Media Souce and Windows Media Playe woks as Media Client. A PC with FeeBSD 5.4 with pim6sd woks as tunnel host. Unicast potocols ae OSPFv3 and IPng. Details ae shown as the following figue. Fo the media client in Shanghai in the figue, we will not descibe it in detail fo the eason that Fujisu 980 woks well with Hitachi G H in IPv6 multicast. We will focus ou study on IPv6 multicast opeation between Hitachi and NEC outes.

4 IPv6 Multicasting among diffeent vendes oute em0 :2 :e000:7::/64 MBidge.2 xl /30 :e000:8::/64 V4 pefix: V6 pefix: 2001:251: FE0/4 FE0/5 :1.1 GZ6 :2 :e101:1::/64 :1 :e000:2::1 IPv6-CJ :4000:5::2 :1 :4001:1::/64 : backbone / BJ2 Media Seve FE0/7 POS0 VLAN11 VLAN31 Media Client Beijing Hitachi G H 20H NEC IX5010 Guangzhou Multicast Addess: FF3E:40:2001:1::1 Loopback: 2001:251:e00e::12 P: 2001:251:e00e::12 BS: 2001:251:e00e::12 Goup Addess: FF3E:40:2001:1::/64 Loopback: 2001:251:e00e::46 (4) China Education and eseach Netwok 3. IPv6-CJ multicasting among diffeent vendes oute 3.1 Tunnel between diffeent vendes oute Fo MBidge, an IPv6 tunnel inteface is defined as gif0 as shown in Figue-1. Noticed that the tunnel itself has no inteface addess, which is anothe method to define tunnel inteface to simplify the addess management. Tunnel inteface infomation of MBidge is as following: gif0: flags=c251<up,pointopoint,unning,allmulti,link2,multicast> mtu 1460 tunnel inet6 2001:251:e000:8::2 --> 2001:251:4000:5::2 inet6 fe80::204:75ff:fe0a:713a%gif0 pefixlen 64 scopeid 0xa Unde this tunnel configuation, tunnel outing must be configued to make sue of its playing well as shown in Figue-3 whee fe80::4cff:fee0:40b0 is VLAN11 s local-link addess calculated fom its MAC addess 00:00:4c:e0:40:b0. Thus multicast message will be outing to GZ6 diectly though gif0. Coesponding to MBidge, tunnel definition must be configued on GZ6 as shown in Figue-4 to enable the tunnel woking. It should be noticed that a static oute must be configued to make sue that multicast messaged to P is outing though the IPv6 tunnel. 3.2 Multicasting among diffeent vendes oute To enable IPv6 multicasting, BJ2 should act as a P, the oot of the multicast tee, and un PIM-SM on evey inteface of the multicast tee as figue-2. The eason of unning IPng on inteface fe0/4 and fe0/5 is to exchange potocol messages with MBidge who unning oute6d as its default IPv6 potocol. Since OSPFv3 is the default IGP of IPv6-CJ backbone, edistibute IPng into OSPFv3 is done by the expot command. On MBidge, pim6sd (vesion a) woks as mediate IPv6 multicasting elay node between Hitachi oute and NEC oute. Note that PIM will be activated on all intefaces by default, we modify some default settings to educe multicast message noise as figue-5. Following is intefaces state: Mif PhyIF Local-Addess/Pefixlen Scope Flags 0 gif0 fe80::204:75ff:fe0a:713a/64 10 NOLISTENE D PIM 1 xl0 2001:251:e000:8::2/64 0 DISABLED NOLISTENE 2001:251:e000:8:204:75ff:fe0a:713a/64 0 fe80::204:75ff:fe0a:713a/ em0 2001:251:e000:7::2/64 0 NOLISTENE D PIM 2001:251:e000:7:208:74ff:feb4:2176/64 0 fe80::208:74ff:feb4:2176/64 2 (In all of the figues, lines with commented mak (#) illustate the details of multicasting ove IPv4 tunnel.)

5 IPv6-CJ multicasting opeation Figue-1 # /etc/c.conf ipv6_gateway_enable="yes" ipv6_oute_enable="yes" ipv6_oute="/us/sbin/oute6d #IPv6 tunnel gif_intefaces="gif0 gifconfig_gif0="2001:251:e000:8::2 2001:251:4000:5::2 # gateway_enable="yes" # oute_enable="yes" # IPv4 tunnel # gifconfig_gif0=" Figue-2 pim6 yes { spase { inteface pos0; inteface fe0/7; inteface fe0/4; candidate-p yes { goup { ff3e:40:2001:1::/64; candidate-bs yes; } ipng yes { inteface fe0/4; inteface fe0/5; expot poto ipng { poto ospf6; (5) Figue-3 #/etc/c.local # Tun66 oute add -inet6 2001:251:4001:1::2 fe80::4cff:fee0:40b0%gif0 ifconfig gif0 mtu 1460 oute add -inet6 default 2001:251:e000:7::1 # Tun64 # oute add -inet6 2001:251:4001:1::2 fe80::d219:9e8a%gif0 # oute add default Figue-4 ipv6 ipng egiste vlan 11 enable enable ipv6 ipng egiste vlan 31 enable enable ipv6 pimv6 domain egiste 1 sm ipv6cjgz ipv6 pimv6 inteface egiste 1 vlan 11 ipv6 pimv6 inteface egiste 1 vlan 31 tunnel egiste tun :251:4000:5::2 2001:251:e000:8::2 ipv6 inteface enable tun66 1 ipv6 inteface status tun66 1 up ipv6 outing-table 2001:251:e00e::12 ### tunnel egiste tun ### ipv6 inteface enable tun64 1 ### ipv6 inteface status tun64 1 up ### ipv6 outing-table 2001:251:e00e::12 Figue-5 #/etc/pim6sd.conf phyint gif0 enable; phyint xl0 disable; phyint xl0 nolistene; phyint em0 nolistene; phyint gif0 nolistene; China Education and eseach Netwok 3.3 Multicasting diagnosis When media client at Guangzhou acquies a pogam fom media seve at Beijing, it will join the multicasting goup managed by P (BJ2). Following is the moute infomation of P: (S,G) 1 oute Goup Addess Souce Addess ff3e:40:2001:1::1:1 2001:251:e101:1::2 Uptime 6hous Expies 03:10 Asset 00:00 Flags FT Potocol SM in-coming: fe0/7 upsteam: Diect eg-sup: 0s downsteam: fe0/4 uptime 6hous expies 02:44 (*,G) 1 oute Goup Addess P Addess ff3e:40:2001:1::1:1 2001:251:e00e::12 Uptime 6hous Expies 02:44 Asset 00:00 Flags Potocol SM in-coming: localhost upsteam: This oute downsteam: fe0/4 uptime 6hous expies 02:44 On MBidge, we can see IPv6 multicasting state coesponding to the above infomation by pim6stat and netstat g commands: Multicast outing Table Souce Goup P-add Flags (*,G) IN6ADD_ANY ff3e:40:2001:1::1:1 2001:251:e00e::12 WC P P-Set Cuent BS addess: 2001:251:e00e::12 Pio: 0 Timeout: 160 P-addess(Upsteam)/Goup pefix Pio Hold Age 2001:251:e00e::12(fe80::200:87ff:fe28:1c74%em0) ff3e:40:2001:1::/ IPv6 Multicast Fowading Cache Oigin Goup Packets Waits In-Mif Out-Mifs 2001:251:e101:1::2 ff3e:40:2001:1::

6 Conclusion & Futue wok IPv6 multicasting suppoted by many outes Hitachi, NEC, Fujisu, Cisco, Junipe Basic potocol: PIM, MLD Multicasting among diffeent vendes oute is useful in NGI envionment China and Japan ae woking actively on IPv6 testing, deployment, &D IPv6 device, application, standads, CNGI (China Next Geneation Intenet) IPv6-CJ is a good stat, moe coopeation needed (6) China Education and eseach Netwok 4. Conclusion and futue wok IPv6 multicasting might educe geat backbone taffic in NGI and it is suppoted by many vendes such as Hitachi, NEC, Fujisu, Cisco, Junipe and so on. Basic potocols like MLD, PIM (ASM, SSM ) ae being developed to meet NGI equiements. This pape studies IPv6 multicasting among diffeent vendes outes in IPv6-CJ testbed in detail and shows some valuable techniques and expeience to do this. As IPv6-CJ s motivation, IPv6 is an oppotunity fo Asian counties, China and Japan need woking actively on IPv6 testing, deployment and &D. IPv6-CJ is a good stat in IPv6 joint eseach poject suppoted by govenment and we believe that it benefits both counties. efeences [1] S. Deeing,. Hinden. Intenet Potocol, Vesion 6 (IPv6) Specification. IETF equest fo Comments, daft standad, FC Decembe 1998 [2] B. Capente, K. Mooe. Connection of IPv6 Domains via IPv4 Clouds. IETF equest fo Comments, poposed standad, FC Febuay [3] edistibuting outing Potocols, Cisco Systems, 2002 [4] W. Pakhust, Cisco Multicast outing & Switching, McGaw-Hill, 1999 [5] C. Waitzman, Distance Vecto Multicast outing Potocol FC 1075, Novembe 1988 [6] D. Estin, D. Fainacci, Potocol Independent Multicast-Spase Mode (PIM-SM): Potocol Specification, FC 2362, June 1998 [7]. Hinden, S. Deeing, IP Vesion 6 Addessing Achitectue, FC 2373, July 1998 [8] B. Fenne, M. Handley, H. Holbook, I. Kouvelas, Potocol Independent Multicast - Spase Mode (PIM- SM): Potocol Specification (evised), daft-ietf-pim-sm-v2-new-09.txt, Febuay 2004 [9] Configuation Guide - Hitachi Gigabit oute G2000, Hitachi, 2002 [10] NEC IX5210 command handbook, NEC, 2002 [11] GeoSteam 920/980 Use s Guide, Fujisu, 2002 [12]