1 / 13

Progress on test scenario of functionally distributed network architecture

Progress on test scenario of functionally distributed network architecture. 16th NGN-WG TTC Kentaro Ogawa (NTT) E-mail: ogawa.kentaro@lab.ntt.co.jp TEL: +81-422-59-3886 FAX: +81-422-59-4549. Current status.

talon-chan
Download Presentation

Progress on test scenario of functionally distributed network architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Progress on test scenario of functionally distributed network architecture • 16thNGN-WG • TTC • Kentaro Ogawa(NTT) • E-mail: ogawa.kentaro@lab.ntt.co.jp • TEL: +81-422-59-3886 • FAX: +81-422-59-4549

  2. Currentstatus • ◆ TTC reported they completed Scenario X-2 (Basic test for functionality check) between Korea and Japan at the 15th NGN-WG meeting. • ◆ The meeting agreed to cooperate in the promotion of the proposed test scenarios to evaluate the architecture. TTC will move the test scenario to X-2 between China and Japan.

  3. Test scenarios • These scenarios are prepared for checking effectivity and feasibility on proposed architecture in order to confirm if the architecture can solve the problems of increasing network size on NGN. • Scenario X-1 : Preparing and checking for test environmentsusing international lines. • Scenario X-2 : Basic testfor functionality check using NTT’s equipmentsin CJK test-bed using equipment at 2 countries • Scenario X-3 : Basic testfor functionality check using NTT’s equipmentsin CJK test-bed using equipment at 3 countries • Scenario X-4 : new features test on NTT’s platform • Adding new functions for C,J,K on CE, FE and SE • Changing programs for C,J,K on CE, FE and SE • Scenario X-5 : test on own platform • Interoperability check between another vendors equipments (CE,FE,SE) Completed between China and Japan on July 21st (progress from the previous meeting)

  4. Overview of scenario X-2 • Scenario X-2 : Basic testfor functionality check using NTT’s equipmentsin CJK test-bed using equipment at 2 countries • CE at J controls FEs at K or C • CE at K controls FEs at J or C • CE at C controls FEs at K or J • Basic functionality check on CE,FE and SE • Adding new functions check on CE, FE and SE • Changing programs check on CE, FE and SE • Characteristics measurement (delay time, performance, etc. ) • Scalability check in large scale network • Operation check in failure • Etc. Japan Korea/China CE CE L2VPN FE FE FE FE FE ForCES session

  5. Logical network topology for X-2 China NCE Japan Add/Delete CE#2 CE#1 CE#0 SE#2 SE#1 FE#F1 FE#F2 FE#S1 FE#F3 L2VPN FE#F4 Sending/Receiving terminal#1 FE#5 Add/Delete Sending/Receiving terminal#2 External route Add/Delete Data Path Routing information exchange between CEs via NCE ForCES session from CE#0 (for sub-network with SE) ForCES session from CE#1 (for sub-network without SE) ForCES session from CE#2 (backup of CE#1)

  6. Equipment configuration for X-2 μTCA#3 China Japan S W # 3 C E # 0 SE #2 or FE #F5 F E #S1 S E # 1 Control terminal#1 Control terminal#2 Ethernet cable HUB#3 HUB#1 μTCA#2 HUB#2 μTCA#1 bridge S W # 2 V P N F E # F3 F E # F4 C E # 1 C E # 2 F E # F1 F E # F2 S W # 1 NCE L2VPN VPN server MPM Sending/Receiving terminal#1 Sending/Receiving terminal#2

  7. Test item for the scenario X-2 (1/2) 1. Basic functionality check

  8. Test item for the scenario X-2 (2/2) 2. Characteristics measurement *1Value result shown without parentheses is actual measurement time which includes timer process. Value result shown in parentheses is pure routing computation time which excludes timer process. Types of timer are following: T1: SPF delay (Interval from a notification of topology changes to beginning the routing computation in CE) -> 5 sec T2: Neighbor detection (Time taken for added FE to judge its own router type (DR/BDR/DROTHER)) -> 8 sec T3: ForCES heartbeat interval between CE and FE/SE -> 5 sec T4: ForCES heartbeat dead intarval between CE and FE/SE -> 20 sec *2 Communication delay is an RTT measured by a ping from Sending/Receiving terminal#1.

  9. Test scenario for next step • Scenario X-3 : Basic testfor functionality check using NTT’s equipmentsin CJK test-bed using equipment at 3 countries • CE at J control FEs at K and C • CE at K control FEs at J and C • CE at C control FEs at K and J • Basic functionality check on CE,FE,SE • Adding new functions check on CE, SE,FE • Changing programs check on CE, SE,FE • Characteristics measurement (delay time, performance, etc. ) • Scalability check in large scale network • Operation check in failure • Etc.

  10. Overview of scenario X-3 Japan Korea CE CE L2VPN FE FE FE CE FE China FE L2VPN FE ForCES session

  11. Schedule plan 2009 2010 Technical discussion/ Standardization 9thCJKPlenary 15th NGN-WG China 4/8－4/10 16th NGN-WG China 7/22-7/24 17th NGN-WG Korea 10thCJKPlenary 18th NGN-WG Korea Scenario X-2 Scenario X-3 Test-bed X-2 between China and Japan was completed Scenario X-4 and 5 X-2 between Korea and Japan was completed Evaluation for scalability and performance

  12. [FYI] ForCES interoperability test • IETF ForCES WG held the interoperability test of the ForCES protocol in the University of Patras in Rio, Greece, on July 15th and16th. • The scenarios cover the basic ForCES functionality. • In all scenarios, all NEs are comprised of one CE and one FE from different vendors. • All scenarios are tested more than once with permutations of the CE and FE from different vendors. • All parties who have own ForCES implementation could participate in the interoperability test. • For details, please refer to the following draft. • http://www.ietf.org/internet-drafts/draft-ietf-forces-interoperability-02.txt

  13. Thank you for your attention. This work is partly supported by the National institute of Information and Communications Technology (NICT).

More Related