Dynamic Circuit Network(DCN) Deployment

Transcription

1 Advanced Platform Services on JGN2plus Dynamic Circuit Network(DCN) Deployment Jin Tanaka KDDI/NICT KOREN Workshop Nov. 6th

2 1. DCN Brief Review DCN Multidomain Control Plane Global Dynamic Circuit Example of DCN Utility Deployment Status in Japan Benefits of Using DCN Outline 2. Expansion of DCN connection to APAN region How to Connect to DCN? (Data Plane) Installation of Control Plane Software (Control Plane) 3. Issues and Advices on Development of Data Plane Efficient Construction of Layer2 Network Taking Care of Network Performance Challenges in Multidomain DCN Operation 4.Introduction of NICT SC09 DCN demo Fenius Interface Space Weather Forecast over dynamic provisioned networks 2

3 1.DCN Brief Review 3

4 DCN Multidomain Control Plane Web Interface XML Request Authentication Schedule Reservation Request VLAN Request Bandwidth XML Request XML Topology Exchange XML Topology Exchange Network2 Network3 Network1 User EndtoEnd Ethernet VLAN Path Better Performance Symmetric Secure Shorten Provisioning time Efficient use of Network Resource End System End System 4

5 Example of DCN Utility NICT evlbi Correlation over DCN at SC08 Metsähovi, FI Kashima, JP DCN Dynamic Circuit Network Austin, US 5

6 NICT SC08 Network Topology MPLS/L2VPN 6

7 internet2 7

8 Deployment Status in Japan Installation of DCN systems in JGN2plus and APANJP Linux based and DCs DCN Software Suite version 0.4 Establish control plane(dcn.jgn2plus.jp) and data plane on a nationwide Connection test on multiple VLSRs in JGN2plus intradomain Connection test over interdomain between JGN2plus and APANJP Preparation works for the beginning of JGN2plus DCN pilot service DC Fukuoka Tsukuba Kashima Otemachi 8

9 Control/Data Planes logical diagram 9

10 Benefits of Using DCN Enable user to create on demand endtoend L2 VLAN path Researchers/campus network operators can provision VLAN path through Web Interface by themselves Save significant network provisioning time Possible use for interactive realtime application, events over the network Provides speedy implementation of research activities and experiments Reduce the burden of multidomain network coordination No need to coordinate the path among multiple networks in each use case Facilitate the smooth implementation of international collaboration researchs Schedule management of finite network resources reservation scheduler prevents the network performance degradation by crosstraffic collision Especially effective in stationary and huge data transmission Improvement of network performance in US section Internet2 DCN controls the Layer1 level and provides dedicate circuit secured the bandwidth Avoids a negative impact of crosstraffic in the sharednetworkspecific Users and application can use DCN web service API to request circuits DCN API can be used into your applications or scripts DCN API enables users to develop the original client software appropriate for own application Realization of integrated client software cooperate with DCN and application 10

11 2.Expansion of DCN connection to Asian region 11

12 Expansion into to Asian Region Internet2 ION KOREN CERNET CSTNET ThaiREN DC SingAREN Expand DCN connections to NRENs within APAN Having a Layer2 Ethernet connection with JGN2plus/APANJP SingAREN(Singapore), ThaiREN(Thailand), ASGC/ASCC(Taiwan), KOREN(KOREA), CERNET/CSTNET(China) Explore appropriate applications for global DCN connections in Asian region 12

13 How to connect to DCN? Web Interface XML Request Authentication Schedule Reservation Request VLAN Request Bandwidth XML Request XML Topology Exchange XML Topology Exchange Network1 User Network2 Network3 EndtoEnd Ethernet VLAN Path End System End System 13

14 Connecting to DCN 1 Physical Connection from National networks interconnect Layer2 Ethernet VLANs Campus Other NREN DCN or Basic Layer2 VLAN Other NREN in ASIA JGN2plus JGN2plus DCN APANJP NRENs within APAN region, Physical Link to JGN2plus DCN POPs Tokyo/Otemachi, Kyusyu, Kashima, Tsukuba POPs Layer2 connection via APANJP Link should be Layer2 ethernet supporting VLANs Universities and campuses in each NRENs, Physical Link to NRENs POPs Typical connection is Ethernet VLANs 14

15 Connecting to DCN 2 Linking to DCN Option1: Static VLAN Web Interface Authentication Schedule Reservation Request VLAN Request Bandwidth XML Request XML Topology Exchange Your Network JGN2plus DCN Internet2 or other DCN User End System Static VLAN Create Static VLAN from NRENs to JGN2plus DCN Static VLAN from user to edge of JGN2plus DCN POPs Dynamic VLAN from edge of JGN2plus DCN to remote DCN connected User Users request connection from JGN2plus End System 15

16 Connecting to DCN 3Linking to DCN Option2: Own DCNWeb Interface Authentication Schedule Reservation Request VLAN Request Bandwidth XML Request XML Topology Exchange XML Topology Exchange XML Request Internet2 or other DCN NREN within Asian region creates and installs own DCN End System JGN2plus DCN Your Network User Static connection from user to your local DCN Local DCN has its own Users request circuit over DCN from your local to JGN2plus End System 16

17 Installation of Control Plane Software Web Interface XML Request Authentication Schedule Reservation Request VLAN Request Bandwidth XML Request XML Topology Exchange XML Topology Exchange Network1 Network2 Internet2 or other DCN Network3 EndtoEnd Ethernet VLAN Path User End System End System 17

18 Control Plane Software 1 Domain Controller DC(Domain Controller) VLSR JGN2plus and APANJP hardware HP ProLiant DL360 G5 Intel Xeon X GHz DualCore DDR2667 2GB * 2 SAS146GB*2 (RAID1) 10/100/1000 baset * 2 DRAGON(Dynamic Resource Allocation via Gmpls Optiacl Network) Open source implementation of GMPLS maintained by MAX, USC ISI EAST, and George Mason University VLSR (Virtual Label Switched Router) Zebra PC based control plane software Provides GMPLS protocol support for devices which do not support GMPLS OSPFTE, RSVPTE Provision the Ethernet Switch and SONET/SDH Switch Switch setting method: SNMP, CLI, TL1, other script Provisioning request via CLI, XML System Requirements for Installation DRAGON System Linux BOX RedHat Enterprise Base (Kernel version or later) Software Requirements DRAGON Software package (VLSR, NARB, RCE, ASTB) Dependencepackage (SSH, GNU Compiles, NetSNMP, libxml2, zlib1.2.3) 18 18

19 Installation of Control Plane Software Web Interface XML Request Authentication Schedule Reservation Request VLAN Request Bandwidth XML Request XML Topology Exchange XML Topology Exchange Network1 User Network2 Network3 EndtoEnd Ethernet VLAN Path End System End System 19

20 Control Plane Software 2 InterDomain Controller (Interdomain Controller) JGN2plus and APANJP hardware HP ProLiant DL360 G5 Intel Xeon X GHz DualCore DDR2667 2GB * 2 SAS146GB*2 (RAID1) 10/100/1000 baset * 2 OSCARS Open source project maintained by Internet2 and ESnet Accept circuit requests from users Use protocol which consist of web services as a messaging among Interdomain Web User Interface function for users Bookahead and manage the scheduling of circuits System Requirements for Installation OSCARS System Linux BOX RedHat Enterprise (Kernel version or later) OSCARS Package Software ThirdParty Library and Package Requirements OSCARS Package Software MySQL5.0 / JDK5.0 / Tomcat 5.5 / Axis / Rampart 1.4.1/ Ant 1.7 SMTP(sendmail) for notification of circuit activity NTP source 20 20

21 3.Issues and Advices on Development of Data Plane 21

22 Efficient Construction of Layer2 Network Hybrid or Coexistence with IP production Network Only Japan, Korea, and Thailand are currently providing Layer2 backbone services in Asian region It it fact that most NREN networks are build up with Layer3 and transport research traffic with IP packets There are barriers: A few carriers can provide widearea ethernet service in Asia Difficulty in Layer2 network operation In principle, DCN needs pointtopoint Layer2 VLAN connection MPLS/L2VPN function is a good solution to provide Layer2 VLAN connection on backbone router Costeffective: There is no need to procure ethernet infrastructure besides current IP infrastructure If your router support MPLS, you don t need purchase ethernet backbone switch Operation side: Solid performance in APANJP/TransPAC2/CERNET/UniNet, etc. Multi vender Interoperability problem remains an issue Since router has lager interface queue buffer than switch, MPLS brings the expected performance Ethernet MPLS Router or L3 Switch SONET/SDH 622M MPLS Router or L3 Switch Ethernet Packet MPLS over POS Packet 22

23 Take care of Network Performance Performance of Data Plane Network Even though we use DCN technology, it is difficult to create bandwidth guaranteed E2E circuits on Asian region Since DCN is partially shared network, it should be considered longdistance Layer2 shared network To my knowledge, it is very difficult to provide better performance over longdistance Layer2 network rather than Layer3 network Capability of Layer2 switch Buffer size of interface queue Wire rate VLANbased QoS Though DCN system specified the bandwidth exceeding manuallyset XML topology cannot be reserved by user basically, it is expected to design data plane network without such bottleneck as Saturation Point (a) and Bandwidth Conversion Point n x 1G 1G X 10G 1G X GigE SONET OC12(622M) X a) Saturation Point b)bandwidth Conversion Point 1G 1G DCN 10G DCN 1G 1G 1G 23 23

24 Challenges in Multidomain DCN Operation Difficulty of Troubleshooting of Multidomain DCN NOC for DCN has not been deployed even in US and Euro, Global Dynamic Circuit is operated based on DCN control plane engineers and software developers community In this situation, the DCN endtoend path creation between JPUS becomes failure No problem on JGN2plus control plane and data plane Contact the US DCN developer and then the problem was finally resolved There are absolutely no operational information for DCN like usual Internet2 IP network Pause to realize importance of operational information Multidomain operation for multidomain DCN Circuit Network monitoring tools and systems for multidomain environment is indispensable to DCN operation DCN path is created over existing multiadmin/multidomain infrastructures, so we would need more various operational information beside current operation data Operational status of underlaying data plane network Circuit, equipment over endtoend/multidomain network DCNspecific event status on and DC software Usage / Number of DCN circuits User accounts for authentication Solutions: 1. Development of perfsonardriven operation tool for multidomain DCN 2. Improvement of DCN control plane softwares 3. Need more stronger collaboration among R&E NOCs 24

25 4.Introduction of NICT SC09 DCN demo 25

26 Fenius Interface Interoperable Issue on multidomain dynamic provisioning Each country develop control plane system with an original interface Internet2 Internet2 ESnet Europe Harmony HPDMnet / AutoBAHN (GEANT) Korea Dynamic KL KISTI Japan Glambda NICT AIST KDDI NTT Interface Standardization is progressing by OGF NSIWG The transfer proxy for each interface is developing by GLIF community before standardization => Fenius Common API Jetty Common API Web UI Client Common API Monitoring Client Glambda Translator Common API Translator Glambda Common API Web UI Client Common API Monitoring Client Common web service API Common internal API Common API Harmony Translator Harmony Harmony Translator Harmony Network Provisioning Service 26

27 27

28 Conclusions DCN overview Creates on demand endtoend L2 VLAN path between devices connected to DCN Reduce the burden of multidomain network coordination and provides speedy implementation of research activities and experiment leads to the promotion of the international collaboration on R&E networks Expansion of DCN on APAN region NRENs needs physical data connection, and control plane access to DCN MAY have control plane connection NRENs can create local DCN using available open source control plane software Issues and advices for data plane deployment MPLS/L2VPN is a good solution to make layer2 connection over APAN network Care about capability of Layer2 switch Improve interoperability of Multidomain/MultiInterface Interface Standardization is progressing by OGF NSIWG Fenius is developed as an interim solution that translates different type of interface to original interface of each country 28

29 Reference URLs DCN Software Suite OSCARS OSCARS Web Services Specification DRAGON DCN Working Group Wiki Test Guide perfsonar SC08 SC09 GLIF GNI task force 29