Changes between Version 1 and Version 2 of GENIExperimenter/Tutorials/GENIDesktop/aag/install


Ignore:
Timestamp:
05/16/16 16:07:27 (5 years ago)
Author:
carpenter@vis.uky.edu
Comment:

--

Legend:

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

    v1 v2  
    22
    33'''Execute Experiment:'''
    4   After your slice is ready, you will be able to interact with your nodes. Even though your OVS nodes are now visible to the controller, their tables are empty and therefore they will not forward any packet.
     4After your slice is ready, you will be able to interact with your nodes. Even though your OVS nodes are now visible to the controller, their tables are empty and therefore they will not forward any packet.
    55
    6    2.1 '''Login to hosts'''
    7     To start our experiment we need to ssh our hosts (h1 and h2), you may use any SSH client or the GENI Dekstop's SSH module to access the hosts from the browser (it will load a shell prompt per host on a separate tab).
     6 1. '''Login to hosts'''
     7  To start our experiment we need to ssh our hosts, '''h1''' and '''h2''', you may use any SSH client or the GENI Dekstop's SSH module to access the hosts from the browser.XXXX link
    88
    9     In the terminal of h1, ping h2. This should timeout, since there are no rules installed at the switches.
    10 {{{
     9  In the terminal of '''h1''', ping '''h2'''. This should timeout, since there are no rules installed at the switches.
     10  {{{
    1111user@h1:~$ ping h2
    1212PING h2-link-4 (10.10.5.2) 56(84) bytes of data.
     
    1414From h1-link-0 (10.10.1.1) icmp_seq=2 Destination Host Unreachable
    1515From h1-link-0 (10.10.1.1) icmp_seq=3 Destination Host Unreachable
    16 }}}
    17   2.2 '''Setup Shortest Path Flows'''
    18     Now we want to make h1 and h2 able to communicate using shortest paths. To do so, you have to load the Flow Install module from the list of modules on the left hand side of your screen.
     16  }}}
     17 2. '''Setup Shortest Path Flows'''
     18  Now we want to make h1 and h2 able to communicate using shortest paths. To do so, you have to load the Flow Install module from the list of modules on the left hand side of your screen.
    1919
    20     [[Image(xxx.png)]]
     20  [[Image(xxx.png)]]
    2121
    22     The first section tells you the public IP address where the controller is running, and what controller did you choose when creating the slice.
     22  The first section tells you the public IP address where the controller is running, and what controller did you choose when creating the slice.
    2323
    24     The second section allows you compute shortest paths between all hosts and automatically install the corresponding flow entries at every switch in the path. We need to handle ARP processing as well in order to be able to communicate between hosts. The controller images loaded in the AAG features include ARP processing modules. Therefore, by checking the ARP processing box we will let the controller handle all ARP requests/responses. Then, click on the Initialize button.
     24  The second section allows you compute shortest paths between all hosts and automatically install the corresponding flow entries at every switch in the path. We need to handle ARP processing as well in order to be able to communicate between hosts. The controller images loaded in the AAG features include ARP processing modules. Therefore, by checking the ARP processing box we will let the controller handle all ARP requests/responses. Then, click on the Initialize button.
    2525
    26     The output message should be:
    27     {{{
     26  The output message should be:
     27  {{{
    2828ARP flow entries successfully installed.
    2929Shortest paths successfully installed.
    30     }}}
     30  }}}
    3131
    3232
    33     Now, if we try to ping h2 from h1 we can see that communication is successful.
    34     {{{
     33  Now, if we try to ping h2 from h1 we can see that communication is successful.
     34 {{{
    3535user@h1:~$ ping h2
    3636PING h2-link-4 (10.10.5.2) 56(84) bytes of data.
     
    383864 bytes from h2-link-4 (10.10.5.2): icmp_seq=2 ttl=64 time=1.74 ms
    393964 bytes from h2-link-4 (10.10.5.2): icmp_seq=3 ttl=64 time=1.69 ms
    40     }}}
     40 }}}
    4141
    42 
    43 
    44 
    45   2.3 '''Install Alternate Paths'''
    46     2.3.1 List Flows
     42 3. '''Install Alternate Paths'''
     43    1. List Flows
    4744
    4845
     
    5249      [[Image(list_flows.png)]]
    5350
    54     2.3.2 Delete a Flow
     51    2. Delete a Flow
    5552      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.
    5653
    57     2.3.3 Defining an Alternate Path
     54    3. Defining an Alternate Path
    5855
    59 Defining an Alternate Path
     56      Defining an Alternate Path
    6057
    6158
    62 Using 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.
     59      Using 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.
    6360
    6461
    65 altflow.png
     62      [[Image(altflow.png)]]
    6663
    67 Tip: Select multiple elements by holding the CTRL key and clicking on the desired element.
     64      '''Tip''': Select multiple elements by holding the CTRL key and clicking on the desired element.
    6865
    69 Output
    70 {{{
     66      Output
     67      {{{
    7168End-to-End flow(s) installed successfully.
    72 }}}
     69      }}}
    7370
    74     2.3.4 Testing New Path
     71    4. Testing New Path
    7572
    7673      With the new path installed, you should be able to ping again from h1 to h2.