Changes between Version 7 and Version 8 of Tutorials/ICDCS2013/GettingStartedWithGENI_I/Procedure/Execute
- Timestamp:
- 07/05/13 11:40:21 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/ICDCS2013/GettingStartedWithGENI_I/Procedure/Execute
v7 v8 109 109 == 5. Execute Experiment == 110 110 111 === 5.1 Run your experiment === 112 1. '''Send IP traffic''' The first simple experiment that we will run is to verify the IP connectivity between our hosts. 113 i. Check the interfaces of your nodes. In the terminal type: 111 === 5.1 Send IP traffic === 112 The first simple experiment that we will run is to verify the IP connectivity between our hosts. 113 114 1. Check the interfaces of your nodes. In the terminal type: 114 115 {{{ 115 116 /sbin/ifconfig … … 118 119 * The '''control interface'''. This is the interface you use to access the node, e.g. ssh into your host. The control interface is mainly used for control traffic, i.e. traffic for controlling the node and the experiment. The control interface usually has a publicly routable IP. 119 120 * The '''data interface'''. This is the interface that is used for sending experimental traffic. This is the interface that connects to the other hosts of your experiment through GENI. The links between these interfaces are the ones that allow you to run non-IP experiments. The data interface is the one that has an IP that starts with 10. 120 i. Fill in the worksheet, noting the name and IP address of the control and of the data interfaces for each node.121 1. Fill in the worksheet, noting the name and IP address of the control and of the data interfaces for each node. 121 122 {{{ 122 123 #!html … … 133 134 </table> 134 135 }}} 135 i. When we reserved the resources, we did not specify the IP address for the data interfaces. Instead, do this now. Configure the IP address on the data interface of each node using the desired data IP address from the worksheet :136 1. When we reserved the resources, we did not specify the IP address for the data interfaces. Instead, do this now. Configure the IP address on the data interface of each node using the desired data IP address from the worksheet : 136 137 {{{ 137 138 sudo /sbin/ifconfig <data i/f name> <desired data IP addr>/24 … … 141 142 sudo /sbin/ifconfig eth3742 10.17.1.1/24 142 143 }}} 143 i. Use `/sbin/ifconfig` to confirm the new IP address and mask for each node. The IP address should match what you set it to and the mask should be `255.255.255.0`.144 i. From the client, ping the server. From the terminal window that is logged in to the client type :144 1. Use `/sbin/ifconfig` to confirm the new IP address and mask for each node. The IP address should match what you set it to and the mask should be `255.255.255.0`. 145 1. From the client, ping the server. From the terminal window that is logged in to the client type : 145 146 {{{ 146 147 ping <server data IP addr> -c 5 … … 166 167 }}} 167 168 168 2. '''Send non-IP traffic'''. GENI provides the capability of running non-IP experiments, since you can connect your hosts at Layer 2. For the purpose of this tutorial we have installed in all the hosts a very simple Layer 2 ping program that sends packets using a custom ethernet type. 169 i. Disable the IP on your nodes (being careful to disable IP on the data interface NOT the control interface). In each of the terminals type: 169 170 === 5.1 Send non-IP traffic === 171 172 GENI provides the capability of running non-IP experiments, since you can connect your hosts at Layer 2. For the purpose of this tutorial we have installed in all the hosts a very simple Layer 2 ping program that sends packets using a custom ethernet type. 173 174 1. Disable the IP on your nodes (being careful to disable IP on the data interface NOT the control interface). In each of the terminals type: 170 175 {{{ 171 176 sudo /sbin/ifconfig <data i/f name> 0.0.0.0 … … 185 190 </table> 186 191 }}} 187 i. Try again to ping from the client to the server. In the terminal window of the client type:192 1. Try again to ping from the client to the server. In the terminal window of the client type: 188 193 {{{ 189 194 ping <server data IP addr> -c 5 … … 194 199 }}} 195 200 This time the ping should timeout. 196 i. Start the Layer 2 ping server: In the server terminal window, type:201 1. Start the Layer 2 ping server: In the server terminal window, type: 197 202 {{{ 198 203 sudo /usr/local/bin/pingPlusListener <EtherType from worksheet> 199 204 }}} 200 i. From the client try to ping the server at layer 2. You will need the mac address of the data interface of the server, the name of the data interface of the client, and the !EtherType from your worksheet. In the terminal window of the client, type:205 1. From the client try to ping the server at layer 2. You will need the mac address of the data interface of the server, the name of the data interface of the client, and the !EtherType from your worksheet. In the terminal window of the client, type: 201 206 {{{ 202 207 sudo /usr/local/bin/pingPlus <server mac> <client i/f name> <Eth> … … 213 218 }}} 214 219 215 216 217 218 220 == 6. Analyze Experiment == 219 221