Progress on test scenario of functionally distributed network architecture

Progress on test scenario of Progress on test scenario of

functionally distributed network functionally distributed network

architecturearchitecture

16th NGN-WGTTC

Kentaro Ogawa (NTT)E-mail: [email protected]

TEL: +81-422-59-3886FAX: +81-422-59-4549

2

◆ 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.

Current status

3

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 environments using international lines.

Scenario X-2 : Basic test for functionality check using NTT’s equipments in CJK test-bed using equipment at 2 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)

Test scenarios

Completed between China and Japan on July 21st(progress from the previous meeting)

4

Scenario X-2 : Basic test for functionality check using NTT’s equipments in 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.

FE FEFE

CEJapan Korea/China

L2VPN

ForCES session

FE

CE

FE

Overview of scenario X-2

5

Logical network topology for X-2

FE#F1 FE#F3FE#F2

CE#2

Japan China

L2VPN

ForCES session from CE#1 (for sub-network without SE)

FE#F4

CE#1

FE#S1

CE#0

SE#1

ForCES session from CE#2 (backup of CE#1)

ForCES session from CE#0 (for sub-network with SE)

Data Path

NCE

FE#5

SE#2

Add/Delete

External route

Sending/Receiving terminal#1


Routing information exchange between CEs via NCE

Add/Delete

Add/Delete

6

Equipment configuration for X-2

FE#

F3

CE#1

FE#

F4

V 　P 　N 　

SW#2

bridge

Japan China

μTCA#1 μTCA#2

FE#

F1

NCE FE#

F2

SW#1

CE#2

HUB#2



SE#2orFE#F5

SE#1

FE#

S1

CE#0

SW#3

μTCA#3

Controlterminal#1

Controlterminal#2

HUB#3

VPNserve

r

L2VPN

MPM

Ethernet cable

HUB#1

7

Test item for the scenario X-2 (1/2)

No. Top tier No. Middle tier No. Bottom tier System conf.

Result

1 System boot operation

1 CE-FE system boot 1 Check for the correct operation of the CE-FE system boot across two countries.

CE － FE

2 Route change operation

1 Route add/delete 1 Check for the correct operation of the routing computation after adding a route to an FE in Korea or China.

CE － FE

　　　　 2 Check for the correct operation of the routing computation after deleting a route from an FE in Korea or China.

CE － FE

3 Node change operation

1 FE add/delete 1 Check for the correct operation of the routing computation after adding an FE in Korea or China.

CE － FE

　　　　 2 Check for the correct operation of the routing computation after deleting an FE in Korea or China.

CE － FE

4 SE operation 1 SE sub-network boot

1 Check for the correct operation of the SE sub-network boot in Korea or China.

CE －FE+SE

　 2 SE reachability 1 Check for the reachability from an FE in Japan to an SE in Korea or China.

CE －FE+SE

　　 3 SE add/delete 1 Check for the correct operation of the routing computation after adding an SE in Korea or China.

CE －FE+SE

　　　　 2 Check for the correct operation of the routing computation after deleting an SE in Korea or China.

CE －FE+SE

1. Basic functionality check

8

Test item for the scenario X-2 (2/2)

No. Top tier No.

Middle tier No.

Bottom tier System conf.

Result [msec]

1

Routing computation time after the route change

1 Route add/delete

1 Measure the routing computation time after adding a route to an FE in Korea or China. ( include T1)

CE － FE

　　　　 2 Measure the routing computation time after deleting a route from an FE in Korea or China. ( include T1)

CE － FE

2

Routing computation time after the node change

1 FE add/delete 1 Measure the routing computation time after adding an FE in Korea or China. (include T1+T2)

CE － FE

　　　　 2 Measure the routing computation time after deleting an FE in Korea or China. ( include T1+T3+T4)

CE － FE

3 SE-related measurement

1 Communication delay via an SE

1 Measure the communication delay without an SE using ICMP.

CE － FE

2 Measure the communication delay via an SE using ICMP.

CE －FE+SE

　　 2 SE add/delete 1 Measure the routing computation time after adding an SE in Korea or China. ( include T1)

CE －FE+SE

　　　　 2 Measure the routing computation time after deleting an SE in Korea or China.( include T1+T3+T4)

CE －FE+SE

2. Characteristics measurement

*1 Value 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


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.

Test scenario for next step

10

FE FEFE

CE

ForCES session

Japan Korea

L2VPN

FE

CE

FE China

L2VPN

FE

CE

Overview of scenario X-3

11

Schedule plan

20102009

Technical discussion/Standardization

Test-bed

9th CJK Plenary15th NGN-WGChina4/8 － 4/10

Scenario X-4 and 5

Scenario X-2

Scenario X-3

X-2 between Korea and Japan was completed

16th NGN-WGChina7/22-7/24

X-2 between China and Japan was completed

17th NGN-WGKorea

10th CJK Plenary18th NGN-WGKorea

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).

Progress on test scenario of functionally distributed network architecture

Documents

Transcript of Progress on test scenario of functionally distributed network architecture