Changes between Version 4 and Version 5 of GEMINI/Tutorial/GEC15/ActiveMeasurements
- Timestamp:
- 10/23/12 11:22:42 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEMINI/Tutorial/GEC15/ActiveMeasurements
v4 v5 3 3 4 4 5 == == Configuring Active Measuremens ====5 == Configuring Active Measurements == 6 6 7 7 … … 13 13 14 14 15 === == Accessing pSConfig UI =====15 === Accessing pSConfig UI === 16 16 17 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. … … 31 31 [[Image(0-unis.png)]] 32 32 33 === == Enabling Services =====33 === Enabling Services === 34 34 35 35 After we've made sure to have a recent copy of the topology information, we can move on to the Manage Services administration page. On this page we will enable the services required to perform on-demand and regularly scheduled tests. We start by enabling the one-way latency services on VM1. Make sure to save the changes before continuing to the next node. … … 57 57 58 58 59 === = Configuring Regular Active Measurements ====59 === Configuring Regular Active Measurements === 60 60 61 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). … … 86 86 [[Image(10-unis-push.png)]] 87 87 88 ==== = Applying the Configuration =====88 ==== Applying the Configuration ==== 89 89 90 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 95 96 96 97 98 === Run and orchestrate I&M services and experiment services to complete run of experiment ===99 [[BR]]100 [wiki:PathControllerDemo Path Controller]101 102 103 === Analyze and visualize measurement results after completing run of experiment ===104 105 - if necessary, retrieve measurement results from archive service106 97 107 - analyze and format results as desired, for visualization with presentation service108 109 - as appropriate, store analyzed results and/or visualization in storage service110 98 111 99 … … 140 128 [[Image(perfadmin-owampgraph.png)]] 141 129 130 142 131 The graph above shows two spikes measured latency and a lost packet during one of those. These spikes correspond to the iperf data transfers where we were saturating the links. 143 132 … … 146 135 147 136 While it's good to be able to query each service for its data, sometimes it's better to have access to all measurements in our slice on the same page. perfAdmin provides this option on the left menu for each of the regular testing measurement types currently supported (One-way Delay, Ping and Throughput). When we access one of these pages, perfAdmin will query each known service storing measurements of the given type for all the related metadata. It then builds a single page that we can use to query for a particular measurement's data. For example, if we go to the One-Way Delay page we should be able to see the measurements stored in both nodes VM1 and VM4. 137 148 138 149 139
