Changes between Version 32 and Version 33 of GEMINIv1.1Tutorial
- Timestamp:
- 10/23/12 10:11:09 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEMINIv1.1Tutorial
v32 v33 399 399 === 3) Configure I&M tools and experiment services === 400 400 401 3.1) Configuring Active Measuremens 401 ==== 3.1) Configuring Active Measuremens ==== 402 402 403 403 … … 452 452 [[Image(psconfig-managepushfailure.png)]] 453 453 454 ===== 3.1.3 Configuring Regular Active Measurements ===== 454 455 ==== 3.2 Configuring Regular Active Measurements ==== 455 456 456 457 Enabling the OWAMP and BWCTL daemons is all we need to perform on-demand active measurements. However, it's usually better to have active measurements running regularly to analyze the performance over time. Throughput and ping tests can be scheduled with a given interval (e.g. every 30 minutes). One-way delay tests are scheduled as a stream (a constant amount of packets is sent per second). … … 481 482 [[Image(10-unis-push.png)]] 482 483 483 ===== 3. .14Applying the Configuration =====484 ===== 3.2.1 Applying the Configuration ===== 484 485 485 486 pSConfig will pull the node's configuration from UNIS every 30 minutes (from the time it was started, not hh:00 and hh:30). Since we don't want to wait this long to start gathering data, we can restart pSConfig on each node by clicking the Apply Config link. This is achieved by ssh'ing to the node and restarting pSConfig, so errors are usually ssh related. … … 489 490 Make sure you apply the configuration on all three nodes. We will now run the user experiment to generate some heavier traffic on the slice before looking at the data. 490 491 491 492 493 494 3.2) Configure selected experiment services495 496 - objectives:497 - binds services together to realize overall reference/actual experiment498 - configures baseline services499 - verifies that they are ready to run500 501 - at completion: configured experiment services, ready to run and process data, which can be observed by I&M services502 492 503 493