Changes between Version 28 and Version 29 of GENIExperimenter/Tutorials/GENIDesktop/aag

Timestamp:

05/16/16 15:35:22 (8 years ago)

Author:

carpenter@vis.uky.edu

Comment:

--

GENIExperimenter/Tutorials/GENIDesktop/aag

@@ -56 +56 @@
     Once the allocation is complete the GENIDesktop will automatically load the Slice View page. 
     Here the allocated topology will be shown. Note that two extra nodes have been automatically added to your topology. One is the AAG Contoller, ```AAGCTRL0``` and the other is the Global Node ```GDGN0```. These nodes provide the OpenFlow controller and the measuring controller respectively. 
+
     [[Image(final_topo.png)]]
 
@@ -66 +67 @@
     [[Image(welcome.png)]]
 
- 1. '''Execute Experiment:'''
+ 2. '''Execute Experiment:'''
   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. 
 
-1.1 Login to hosts
+   2.1 '''Login to hosts'''
     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). 
 
@@ -79 +80 @@
 From h1-link-0 (10.10.1.1) icmp_seq=2 Destination Host Unreachable
 From h1-link-0 (10.10.1.1) icmp_seq=3 Destination Host Unreachable
+}}}
+  2.2 '''Setup Shortest Path Flows'''
+    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. 
+
+    [[Image(xxx.png)]]
+
+    The first section tells you the public IP address where the controller is running, and what controller did you choose when creating the slice. 
+
+    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. 
+
+    The output message should be: 
+    {{{ARP flow entries successfully installed.
+Shortest paths successfully installed.
+}}}
+
+
+    Now, if we try to ping h2 from h1 we can see that communication is successful. 
+{{{user@h1:~$ ping h2
+PING h2-link-4 (10.10.5.2) 56(84) bytes of data.
+64 bytes from h2-link-4 (10.10.5.2): icmp_seq=1 ttl=64 time=7.40 ms
+64 bytes from h2-link-4 (10.10.5.2): icmp_seq=2 ttl=64 time=1.74 ms
+64 bytes from h2-link-4 (10.10.5.2): icmp_seq=3 ttl=64 time=1.69 ms
 }}}