| 113 | {{{ |
| 114 | #!html |
| 115 | <table border="0" cellpadding="0" cellspacing="0"> |
| 116 | <tr> |
| 117 | <td valign="top" align="left"> |
| 118 | <img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/execute.png?format=raw" width="180" height="150" alt="Execute"></a> |
| 119 | </td> |
| 120 | <td> |
| 121 | <h3><u> Step 3: View Results: </u></h3> |
| 122 | For this example experiment we used the install script facility to automatically install the necessary software and kick-off the experiment. In this very simple setup, we have installed and launched a <a href="[http://en.wikipedia.org/wiki/Web_server target="_blank"> web server </a> as well as an <a href="http://en.wikipedia.org/wiki/Iperf" target="_blank"> iperf server</a>, on the server host. On the client, we have started some processes to test both of these services. To view the results of this experiment: |
| 123 | <table border="0"> |
| 124 | <tr> |
| 125 | <td > |
| 126 | <ol type="a"> |
| 127 | <li> Go to <a href="http://portal.geni.net" target="_blank"> the GENI Experimenter Portal </a> press the <b> Use GENI </b> button</li> and from the Drop Down menu select your institution. If you got an account through the GENI Identity Provider, please select <b>GENI Project Office</b>. |
| 128 | <br><b>Tip:</b> Start typing the name of your institution and see the list become smaller. |
| 129 | </li> |
| 130 | <li> You will be transferred to the Login Page of your institution. <b>Fill in </b>your username and password. </li> |
| 131 | </ol> |
| 132 | </td> |
| 133 | |
| 134 | </tr> |
| 135 | </table> |
| 136 | <h3><u> Optional Step 4: Manually generate traffic: </u></h3> |
| 137 | While conducting experiments in GENI, you will often want to run commands directly on the nodes. In this optional step, you will log in to a node and issue commands directly to it. |
| 138 | <ol type="a"> |
| 139 | <li> Follow [wiki:HowTo/LoginToNodes these instructions] and log in to the client node </li> |
| 140 | <li> When you have successfully logged in, run this command:<br> |
| 141 | <code> |
| 142 | iperf -c server -P 2 |
| 143 | </code> <br> |
| 144 | This task shouldn't take more than 30 seconds. Change the number after the ` -P ` argument and watch how the performance is affected while you change the number of parallel TCP connections. |
| 145 | </li> |
| 146 | <li> Scroll all the way down the server iperf log, and look at the logs for your transfers </li> |
| 147 | </ol> |
| 148 | <table border="0"> |
| 149 | |
| 150 | <tr> |
| 151 | |
| 152 | <td > |
| 153 | <ol type="a"> |
| 154 | <li> Follow [wiki:HowTo/LoginToNodes these instructions] and log in to the client node </li> |
| 155 | <li> When you have successfully logged in, run this command:<br> |
| 156 | <code> |
| 157 | iperf -c server -P 2 |
| 158 | </code> <br> |
| 159 | This task shouldn't take more than 30 seconds. Change the number after the ` -P ` argument and watch how the performance is affected while you change the number of parallel TCP connections. |
| 160 | </li> |
| 161 | <li> Scroll all the way down the server iperf log, and look at the logs for your transfers </li> |
| 162 | </ol> |
| 163 | |
| 164 | </tr> |
| 165 | </table> |
| 166 | |
| 167 | |
| 168 | </td> |
| 169 | </tr> |
| 170 | </table> |
| 171 | }}} |
| 172 | |