Changes between Version 2 and Version 3 of GEMINI/Tutorial/GEC15/ActiveMeasurements
- Timestamp:
- 10/23/12 11:17:13 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEMINI/Tutorial/GEC15/ActiveMeasurements
v2 v3 1 [[PageOutline]] 1 2 = GEMINI/Tutorial/GEC15/ActiveMeasurements = 2 3 3 4 4 ==== 3.2)Configuring Active Measuremens ====5 ==== Configuring Active Measuremens ==== 5 6 6 7 … … 12 13 13 14 14 ===== 3.2.1Accessing pSConfig UI =====15 ===== Accessing pSConfig UI ===== 15 16 16 17 To configure active measurements we access the pSConfig Web UI. You can find the URL by clicking on the MC node on the GEMINI portal, or by going to https://<gn node>/psconfig. … … 56 57 57 58 58 ==== 3.3Configuring Regular Active Measurements ====59 ==== Configuring Regular Active Measurements ==== 59 60 60 61 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). … … 85 86 [[Image(10-unis-push.png)]] 86 87 87 ===== 3.3.1Applying the Configuration =====88 ===== Applying the Configuration ===== 88 89 89 90 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. … … 95 96 96 97 97 === 4)Run and orchestrate I&M services and experiment services to complete run of experiment ===98 === Run and orchestrate I&M services and experiment services to complete run of experiment === 98 99 [[BR]] 99 100 [wiki:PathControllerDemo Path Controller] 100 101 101 102 102 === 5)Analyze and visualize measurement results after completing run of experiment ===103 === Analyze and visualize measurement results after completing run of experiment === 103 104 104 105 - if necessary, retrieve measurement results from archive service … … 109 110 110 111 111 ==== 5.1 .Visualize Measurement Data ====112 ==== Visualize Measurement Data ==== 112 113 113 114 Doing the user experiment should have given the scheduled active measurements enough time to gather some data. We also generated some heavy traffic during our iperf data transfers. This section of the tutorial covers how to visualize the data for regular active tests. We will also check the passive monitoring graphs again to see how the iperf transfers affected our hosts.
