Traffic Analysis and model synthesis of remote instrumentation - dorii

More documents

Recommendations

Info

2.2. IPv6 Testbed Figure 2 shows the IPv6 test bed that has been setup in the DORII project. LMU USTUTT DFN PIONIER (IPv4) PSNC UC RedIRIS GEANT (IPv6 Transport Network) GRNET (IPv6) CSIC IPv4 Island EUCENTRE (IPv6) OGS GARR (IPv6) CNIT ELETTRA IPv4 Island Native IPv6 Figure 2 IPv6 Testbed Within the DORII network native IPv6 connectivity is provided from GRNET and PSNC through the GRNET and PIONEER networks that are connected through the GÉANT2 network. Furthermore, an IPv6 Test bed is set-up within EUCENTRE and a HellasGrid site in GRNET. Native IPv6 connectivity has been enabled in the access network for EUCENTRE and ariagni.hellasgrid.gr that is a HellasGrid site in Crete. In EUCENTRE, IPv6 is supported in the EUCENTRE LAN, the hosting IE and the VCR, while in ariagni.hellasgrid.gr IPv6 is supported in all the hosts of the Grid site. IPv6 connection between EUCENTRE and ariagni.hellasgrid.gr is provided through the native IPv6 network of GRNET, GÉANT and GARR. The topology of the connection is shown in Figure 2. The EUCENTRE application is written in Java, and thus IPv6 is transparently supported for this application. However, since the gLite middleware is only partially ported to IPv6 at this moment, we were unable to execute tests with IPv6 to the HellasGrid sites. Thus, in order to make some pilot tests with IPv6 support, by using the DORII developed middleware, a special IPv6 enabled test bed is being created. In this test bed, an IPv6 enabled VCR is installed in GRNET in order to be accessible via IPv6 from the IE in EUCENTRE. More specifically, native IPv6 connectivity has been enabled between EUCENTRE and GRNET: • EUCENTRE LAN, hosting the IE • Italian NREN (GARR), GÉANT2 • Greek NREN (GRNET), hosting VCR (IPv6-enabled), SEs and CEs DSA1.5 PUBLIC 8
3. Performance Evaluation Procedure As discussed in [3], to evaluate how the behavior of DORII applications is affected by the network performance, the evaluation procedure illustrated in Figure 3 has been defined. The basic idea behind our approach is to infer the impact of the network on the performance of the applications by measuring QoS metrics at the network layer and correlating them with metrics observed at the application level. Test Definition Test Running QoE Evaluation Statistics Statistics vs. QoE Network Parameter Configuration Guidelines Figure 3 Performance evaluation procedure More specifically, while running each application under test, network statistics are collected: indeed, the network monitoring platform provides delay and bandwidth measurements between specific couples of DORII sites, whereas the IEs, CEs and SEs are monitored by means of SNMP. At the application level, for each step, the end-user has to measure the performance metrics (e.g., the overall execution time) that have to be optimized to improve the QoE from the user’s perspective. DSA1.5 PUBLIC 9
Page 1 and 2: contract # 213110 Deliverable DSA1.
Page 3 and 4: Table of Contents 1. INTRODUCTION..
Page 5 and 6: Executive Summary The content of th
Page 7: Vacuum slits Monochromator Beam sto
Page 11 and 12: •1: Input Data Transfer •2: Dat
Page 13 and 14: Figure 9 Latency from EUCENTRE to s
Page 15 and 16: Table 3 reports the processing time
Page 17 and 18: 4.2. OPATM-BFM 4.2.1. Test Descript
Page 19 and 20: Figure 15 OPATM-BFM -Test Scenario:
Page 21 and 22: SE Start Upload Time Data Transfer
Page 23 and 24: 5. IPv6 Testbed Deployment 5.1.1. I
Page 25 and 26: Figure 24 IPv6 Traffic Monitoring F
Page 27 and 28: 7. List of Acronyms AAI AN API ATM
Page 29 and 30: References [1] EU DORII Project - D

Traffic Analysis and model synthesis of remote instrumentation - dorii

Create successful ePaper yourself

Delete template?

Save as template?