Jin TanakaAPAN-JP NOC/KDDI/NICT SPARC

Network Engineering Workshop in 27th APAN Kaohsiung Meeting

March 5 2009Kaohsiung Taiwan

DCN Deploymentand

NOC Collaboration Tool

1

Agenda1. DCN Deployment

1) Introduction of DCN 2) DCN live demonstration3) NICT DCN Experiment at SC08 4) Next Steps and Future Work

2. NOC Collaboration Tool1) Importance of Understanding of Application2) Proposal for development of NOC

Collaboration Tool

2

1. DCN Deployment

3

Introduction of DCN• DCN: Dynamic Circuit Network

• Provides connection type of service

• VLAN path is created by user request

- Through the control plane’s WEB interface- Through the API for original client application

• DCN Control Plane Software Suite is developed by Internet2

• Connections crossing multiple domains coordinated using internationally developed IDC protocol

• Internet2 has already started DCN pilot service, they are performing the experiment of inter-domain connection with Europe

4

Illustrated Introduction of DCN

End System

Network2

Network1

Network3

DC/vlsr DC/vlsr

DC/vlsr

DC/vlsrDC/vlsr DC/vlsr

IDC

IDC IDC

End System

User

•Authentication•Schedule Reservation•Request VLAN•Request Bandwidth

•XML Request •XML Request

•XML Topology Exchange •XML Topology Exchange

•Path Creation •Path Creation •Path Creation

Web Interface

End-to-End Ethernet VLAN Path

•Symmetric•Better Performance•Secure • Shorten Provisioning time •Efficient usr of Network Resource

5

DCN Software Suite• OSCARS- Open source project maintained by Internet2 and ESNet - Accept circuit requests - Coordinates requests with other domains- Use IDC protocol which consist of web services as a

messaging among Inter-domain- Web Interface- Book-ahead scheduling of circuits

IDC(Inter-domain Controller)

DC(Domain Controller) • DRAGON- Open source implementation of GMPLS maintained by

MAX, USC ISI EAST, and George Mason University- NSF fund- Provides GMPLS protocol support for devices which do

not support GMPLS- One of the research project of GENI spiral 1, the first

phase of GENI prototyping

6

DCN brief Live Demo

JGN2plusInternet2

APAN-JPTransPAC2

Here!Kaohsiung

Control Plane

Data Plane

• Inter-domain VLAN path creation between Kashima in Japan and Houston in US

192.203.116.8192.203.116.8

7

Kashima, JPMetsähovi, FI

Austin, US

SC08 NICT e-VLBI Experiment Schematic

DCNDynamic Circuit Network

8

NICT SC08 Network Topology

MPLS/L2VPN

9

Other DCN Activities

10

Next Steps and Future Work -1-• Installation of DCN systems in JGN2plus and APAN-JP

- Linux based IDC 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 intra-domain- Connection test over inter-domain between JGN2plus and APAN-JP- Preparation works for the beginning of JGN2plus DCN pilot service

IDC

DC

Otemachi

Kashima

TsukubaFukuoka

11

IDC

DC

• Expand DCN connections to NRENs within APAN- Having a Layer2 Ethernet connection with JGN2plus/APAN-JP

• SingAREN(Singapore), ThaiREN(Thailand), ASGC/ASCC(Taiwan), KOREN(KOREA), CERNET/CSTNET(China)

• Explore appropriate applications for global DCN connections in Asian region

Next Steps and Future Work -2-

KOREN

CERNETCSTNET

ThaiREN

SingAREN

Internet2

12

2. NOC Collaboration Tool

13

• Lead to Facilitation of New Networking Technology- Network engineer should understand research application to facilitate the

adoption of network cyber-infrastructure to support R&E researchers.• DCN, Multi-layer/Hybrid, Optical, Virtualization

- Build advanced common tools and services• Traffic weathermap, NDT, RouteView, DVrelay

- Develop and deploy middleware• perfSONAR, Phoebus, Eduroam

• Strengthen the foundations for sustainable NOC- Joint research activates network connectivity and network operation

among RENs.- Particularly, international collaborative project needs NOC cooperation- Better NOC cooperation bring a better results- Sharing operative information enable NOC to effective operation- To do this, there need more strong cooperation among NOCs, network

admins, and researchers

R&E Applications Motivates Networking

14

NOC’s Aggressive Approach• Work with research communities actively engaged in global

collaborations

• Try to survey and collect information of current global research project as much as possible

• Create collected project lists of collaborative research and make information available to other NOCs

• In addition above, provide necessary information for network operation to other NOCs

• Gain detailed understanding of each research projects and operation problems

• Share results with not only NOC but also other domain research communities, network admins and engineer staff in campus or laboratory.

15

Information-sharing ToolProposal of Integrated “Web based tool” that can share those kind of information among NOCs

• Essential Requirements - NOC information for understanding research projects- Link to NOC own web page of each asian REN/NRENs- Collaborative research project lists/Detailed application lists - Calendering of experiment and event schedule- Documentation management- Authentication for NOC and Network admin

• Wiki based Software - Atlassian Confluence(Enterprise wiki), Clocking IT, Twiki, Mediawiki,

• Do we need support/tracking system among NOCs?- Trac, Redmine, Plone, Request Tracker

• Management - Public web NOC and Network admin with Authentication - APAN-JP NOC install tool and compile content responsibly

16

Information-sharing Tool- Blueprint -

NOC

NOC

ResearchProject List

SearchOngoing

EventOperational/Technical Info

DOCs

Calender

ExternalCalender

NREN

REN

NOC A

NOC C

NOC D

NetAdmins A

Chat/Message

Board

Account

17

Impression Evaluationof Software

• For summary, below is the table showing ranks of each software from 1 to 5 according to four core criteria

Accessible Functional Extensible Operable

Atlassian Confluence 5 4 5 5

Trac 4 5 5 3

Mediawiki 5 3 3 4

Clocking IT 4 5 3 3

18

Atlassian Confluence(Enterprise wiki)

19

What do we need for Further Collaboration?

Subject/Application Convenient Tool Required Software/Hardware

Communication

Video System Polycom, MCU

Communication

IP Phone Skype

CommunicationSMS MSN messenger, iChat, Skype

Communication

Web conference

Acrobat Connect ProCommunication

Web conference Cisco WebEX

Communication

Web conference

Access Grid

Operation Tools

Routing Compath Tool(APAN Route View)

Operation Tools Performance perfSONAROperation Tools

Router/Switch Status Router Proxy

Grasp the Research Project

Collaborative Web WikiGrasp the Research Project Document Management Docshare/Wiki

Grasp the NOC Situation

Contact Point Cyworld, Myspace, Facebook, etc.

Grasp the NOC Situation Scheduling Google Calender/CalDAVGrasp the NOC Situation

Tracking Trac, Redmine

AuthenticationFunction

20

DCN Acknowledgment • Internet2 DCN Staff

- John Vollbrecht- Andrew Lake

• TransPAC2 NOC- Brent Sweeny- John Hicks

• StarLIGHT/SC08 SCinet- Linda Winkler

• NICT Researchers- Mamoru Sekido- Hideki Otsuki

• JGN2plus & APAN-JP NOC Staff

21

References• “Dynamic Networking over TransPAC2” Brent Swenny & Jin Tanaka

http://www.jp.apan.net/meetings/0808-NZ/transpac_update_0808.pdf http://www.jp.apan.net/meetings/0808-NZ/apan-nz-eng-tanaka-rev10.pdf

• “ DCN”, http://www.internet2.edu/dcresearch/

• “Internet2 Dynamic Network Circuit”., http://www.internet2.edu/network/dc/

• “OSCARS”, http://www.es.net/oscars/

• “DRAGON” ,http://dragon.maxgigapop.net/

• “SC08”, http://sc08.supercomputing.org/.

• “Atlassian Confluence”, http://www.atlassian.com/software/confluence/

• “Clokng IT”, http://www.clockingit.com/

• “Media Wiki”, http://www.mediawiki.org/wiki/MediaWiki

• “Trac”, http://trac.edgewall.org/

• “Redmine”, http://www.redmine.org/

• “Plone” http://plone.org/

22