Changes between Version 30 and Version 31 of GENIExperimenter/Tutorials/GENIDesktop/aag


Ignore:
Timestamp:
05/16/16 15:42:10 (5 years ago)
Author:
carpenter@vis.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/GENIDesktop/aag

    v30 v31  
    108108
    109109
     110
     111  2.3 '''Install Alternate Paths'''
     112    2.3.1 List Flows
     113
     114
     115      The Flow Install module allows you to list existing end-to-end flows (Refresh List button) you have added using the GENI Desktop as well as individual flow entries (possibly) installed using other tools that interact with the controller REST API.
     116
     117      Note that end-to-end flows display the path a flow follows from one host to another instead of displaying low-level details. For individual flow entries, information about the match fields is shown (e.g. ARP flows).
     118      [[Image(list_flows.png)]]
     119
     120    2.3.2 Delete a Flow
     121      With the flows listed, it is straightforward to remove an existing path. For this tutorial we will leave the communication from h1 to h2 intact (i.e. shortest path), but you will select and remove the flow that goes from h2 to h1.
     122
     123    2.3.3 Defining an Alternate Path
     124
     125Defining an Alternate Path
     126
     127
     128Using the topology view, you will select all the elements (links and nodes) across an alternate path that communicate h2 with h1. In the flow definition section, select h2 as source node and define the path as a one-way flow. Leave the information about ports blank and install the new flow.
     129
     130
     131altflow.png
     132
     133Tip: Select multiple elements by holding the CTRL key and clicking on the desired element.
     134
     135Output
     136{{{
     137End-to-End flow(s) installed successfully.
     138}}}
     139
     140    2.3.4 Testing New Path
     141
     142      With the new path installed, you should be able to ping again from h1 to h2.
     143      {{{
     144user@h1:~$ ping h2
     145PING h2-link-4 (10.10.5.2) 56(84) bytes of data.
     14664 bytes from h2-link-4 (10.10.5.2): icmp_seq=1 ttl=64 time=2.64 ms
     14764 bytes from h2-link-4 (10.10.5.2): icmp_seq=2 ttl=64 time=2.16 ms
     148      }}}
     149
     150      Notice the extra delay added to the communication because we are using a longer path.
     151
     152
    110153  * [wiki:GENIExperimenter/Tutorials/GENIDesktop/05032016/ready_init_instr View resources while they are being created, initialized and Instrumentized]
    111154 1. '''[wiki:GENIExperimenter/Tutorials/GENIDesktop/05032016/GENI_Desktop_runcmd Running Experiments:]''' Load and execute code
     
    113156 1. '''[wiki:GENIExperimenter/Tutorials/GENIDesktop/05032016/GENIDesktop_CLI GENIDesktop CLI:]''' Perform GENIDesktop operations using a Command Line Interface.
    114157
    115 == Create Experiment ==
    116158
    117 1. Login to GENIDesktop
    118 
    119 1.1 === Create Slice ===
    120 1.2 === Allocate Resources using JACKS and the GENIDesktop ===
    121 
    122 1.3 ==== Wait for slice to be allocated and instrumentized ===
    123 
    124 The controller node will automatically be added by the GENIDesktop when the slice is allocated.
    125 
    126 In this tutorial we will be using [http://www.openvswitch.org/ Open vSwitch (OVS)] to represent OpenFlow Software Switches and XEN VMs to represent hosts. The controller node is automatically added by the GENIDesktop. The general topology is:
    127  [[Image(topo.png)]]
    128 
    129 1.
    130 1.