Changes between Version 6 and Version 7 of GENIExperimenter/Tutorials/PortalSimpleLayer2Example/ExecuteExperiment
- Timestamp:
- 03/07/13 19:55:16 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/PortalSimpleLayer2Example/ExecuteExperiment
v6 v7 43 43 <li><FONT COLOR="black">Return to the Slice page. Press the <b>Details</b> button in the row of the slice table for <i>GPO InstaGENI</i>.</font></li> 44 44 <li>Open a new terminal window. Copy the command to the right of <b>Login</b> into that terminal window. You have now logged into your VM.</li> 45 <li><FONT COLOR="black">Return to the Slice page and repeat the previ ewtwo steps for <i>Utah InstaGENI</i> in a second terminal window.</font></li>45 <li><FONT COLOR="black">Return to the Slice page and repeat the previous two steps for <i>Utah InstaGENI</i> in a second terminal window.</font></li> 46 46 </ol> 47 47 </td> … … 59 59 * The '''control interface'''. This is the interface from where you 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. 60 60 * 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. 61 i. Note the name and the MAC address of the control and of the data interfacefor each node. The data interface is the one that has an IP that starts with 10.62 i. Configure the IP address on the data interface :61 i. Fill in the worksheet, noting the name and IP address of the control and of the data interfaces for each node. The data interface is the one that has an IP that starts with 10. 62 i. Configure the IP address on the data interface of each node using the desired data IP address from the worksheet : 63 63 {{{ 64 64 sudo /sbin/ifconfig <data i/f name> <desired data IP addr>/24 … … 68 68 sudo /sbin/ifconfig mv.7.90 10.10.1.1/24 69 69 }}} 70 i. Use `/sbin/ifconfig` to confirm the new IP address .70 i. Use `/sbin/ifconfig` to confirm the new IP address and mask. 71 71 i. From the client, ping the server. From the xterm that is logged in to the client type : 72 72 {{{ 73 ping <server IP addr> -c 573 ping <server data IP addr> -c 5 74 74 }}} 75 75 For example: … … 79 79 An example output should look like : 80 80 {{{ 81 [[inki@r2 ~]$ ping 10.10. 2.1 -c 582 PING 10.10. 2.1 (10.10.2.1) 56(84) bytes of data.83 64 bytes from 10.10. 2.1: icmp_seq=1 ttl=64 time=1.95 ms84 64 bytes from 10.10. 2.1: icmp_seq=2 ttl=64 time=2.27 ms85 64 bytes from 10.10. 2.1: icmp_seq=3 ttl=64 time=2.04 ms86 64 bytes from 10.10. 2.1: icmp_seq=4 ttl=64 time=1.95 ms87 64 bytes from 10.10. 2.1: icmp_seq=5 ttl=64 time=1.72 ms81 [[inki@r2 ~]$ ping 10.10.1.1 -c 5 82 PING 10.10.1.1 (10.10.1.1) 56(84) bytes of data. 83 64 bytes from 10.10.1.1: icmp_seq=1 ttl=64 time=1.95 ms 84 64 bytes from 10.10.1.1: icmp_seq=2 ttl=64 time=2.27 ms 85 64 bytes from 10.10.1.1: icmp_seq=3 ttl=64 time=2.04 ms 86 64 bytes from 10.10.1.1: icmp_seq=4 ttl=64 time=1.95 ms 87 64 bytes from 10.10.1.1: icmp_seq=5 ttl=64 time=1.72 ms 88 88 89 --- 10.10. 2.1 ping statistics ---89 --- 10.10.1.1 ping statistics --- 90 90 5 packets transmitted, 5 received, 0% packet loss, time 4005ms 91 91 rtt min/avg/max/mdev = 1.728/1.992/2.278/0.179 ms