Changes between Version 1 and Version 2 of GENIExperimenter/Tutorials/GENI_Desktop_and_GEMINI_tables/ExecuteExperiment


Ignore:
Timestamp:
06/24/13 00:59:01 (6 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/GENI_Desktop_and_GEMINI_tables/ExecuteExperiment

    v1 v2  
    1212manually add the GEMINI extensions into an RSPEC).  The purpose of the GN is to be the collection point for all instrumentation and measurement data collected by the slivers.  Since slivers may be in different aggregates, there is one GN per aggregate.  Each GN only collects data from slivers in its aggregate.  This localizes communication, thereby minimizing interference of the I&M data collection mechanism with the running experiment.  It also provides a centralized location(s) where users can go to find detailed information coming from the slivers in an aggregate.
    1313
    14 In this exercise you will use the GENI Desktop to connect to the GN an view live graphs and tables from the running experiment, you will also
     14In this exercise you will use the GENI Desktop to connect to the GN an view additional live graphs and tables not directly available via the GEMINI graphs view used in the previous exercise.
     15You will also be shown how to view detailed packet captures using wireshark.   Lastly, you will learn to X-based applications, and configure the data collection.
    1516
    1617
     18== Access a Global Node ==
    1719
    18 == Ssh'ing into nodes from the GENI Desktop ==
     20In order to access global node information, click the launcher [[Image(launcher.png)]] icon and select the Global Node items from
     21the [[Image(launchermenu.png)].  This will create a button [[Image(GNliveview.png))]] that will allow you to see or configure global nodes.
    1922
    20 To open an ssh session, you must first launch the ssh tool. You can launch the ssh tool by clicking the launch icon [[Image(launcher.png)]] in the upper lefthand corner of the GENI Desktop and then selecting ssh. This will create an ssh button [[Image(ssh.png)]] near the task bar on the bottom. To ssh into nodes, select the node in the topology by left-clicking on the node. Once selected, press the ssh button to ssh into your network. You may need to accept the security certificate if prompted by your browser. You can iconify the ssh button or deiconify the ssh button by clicking ssh in the task bar.
     23A topology may have multiple Global Nodes (GNs), one per aggregate.  Although the GNs appear in the logical and geographic views
     24of the topology, it is not immediately obvious which slivers (nodes) are managed by each of the GNs.  Consequently, to find
     25the GN for any particular node in the topology, one can select the desired sliver (node) and then click on the live view button
     26[[Image(GNliveview.png)]].
    2127
    22 == Viewing traffic from the GENI Desktop  ==
     28== Viewing packet traces  ==
    2329
    24 To view traffic, click on the launcher icon and select gemini graphs. This will create a graph selection window (see below) on your screen. By default, the CPU, ICMP, and IP graphs are selected. Adjust the selection to the graphs you want to see. Select the node or nodes in the topology for which you would like to see graphs. Then click the "add graphs" button. If you have selected multiple nodes, you may prefer to click on "add graphs with titles," as this will clearly identify the node from which the graph is taken. Like the ssh box, you can iconify or deiconify the graph selection box by clicking on the task bar.
     30To view packet traffic traces,
    2531
    26 [[Image(graphselect.png)]]
    27 
    28 == Generating traffic with iperf ==
    29 
    30 The iperf program can be used to generate traffic. Iperf needs to be run on both the source and destination node. Iperf should first be started at the destination in server mode using the command "iperf -s." To run iperf on the source, type "iperf -t 60 -b 100M -c destination" where destination is the IP address (or name) of the node where the iperf server is running.  This will tell iperf to generate traffic for sixty seconds, sending at a rate of one hundred megabits per second. The names of the hosts in your topology can be found in the /etc/hosts.
    31  
     32== Access X-based Applications ==
    3233
    3334== __Exercise Tasks__ ==
    3435
    35  a. '''Task 1:''' Ssh into VM-0 and VM-1.
    36  a. '''Task 2:''' Use iperf to generate traffic between VM-0 and VM-1.
    37  a. '''Task 3:''' View the traffic between VM-0 and VM-1.
     36 a. '''Task 1:''' Bring up a window to view the GN.
     37 a. '''Task 2:''' Find the routing table for VM-1.
     38 a. '''Task 3:''' Bring up wireshark and capture all packets flowing between VM-0 and VM-2.