Changes between Version 13 and Version 14 of GENIExperimenter/Tutorials/GENIDesktop/aag/install

Timestamp:

05/18/16 17:25:40 (8 years ago)

Author:

carpenter@vis.uky.edu

Comment:

--

GENIExperimenter/Tutorials/GENIDesktop/aag/install

@@ -48 +48 @@
   The third section of the '''Flow Install''' module shows a '''List of Existing Flows''' and provides buttons to delete them.
     
-   Click the '''Refresh List''' button to retrieve a list of existing end-to-end flows 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. 
+  Click the '''Refresh List''' button to retrieve a list of existing end-to-end flows 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. 
 
-   [[Image(refreshed_flows.png)]]
+  [[Image(refreshed_flows.png)]]
 
-   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). The format is [''match field'']>>[''action'']@''switch_name''
+  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). The format is [''match field'']>>[''action'']@''switch_name''
      
     
-   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'''. Choose the radio button beside the flow from '''h2''' to '''h1'''. Then press the '''Delete Single Flow''' button. After a short wait, the list will update with the new set of flows listed. 
+  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'''. Choose the radio button beside the flow from '''h2''' to '''h1'''. Then press the '''Delete Single Flow''' button. After a short wait, the list will update with the new set of flows listed. 
 
 
-   Defining an Alternate Path
-   Using the topology view, you will select all the elements (links and nodes) across an alternate path that communicate '''h2''' with '''h1'''. 
-   [[Image(selected_path.png)]]
-    '''Tip''': Select multiple elements by holding the CTRL key and clicking on the desired element.       In the '''New Flow Definition''' section, select '''h2''' as source node and define the path as a one-way flow. Leave the information about ports blank and click the '''Install Flow''' button once.
-      [[Image(install_flow_definition.png)]]
+  Define an alternate path. Using the topology view, you will select all the elements (links and nodes) across an alternate path that communicate '''h2''' with '''h1'''. 
+  [[Image(selected_path.png)]]
+  '''Tip''': Select multiple elements by holding the CTRL key and clicking on the desired element.       In the '''New Flow Definition''' section, select '''h2''' as source node and define the path as a one-way flow. Leave the information about ports blank and click the '''Install Flow''' button once.
+  [[Image(install_flow_definition.png)]]
 
 
 
-      In a few seconds the '''Output''' should say:
-      {{{
+  In a few seconds the '''Output''' should say:
+  {{{
 End-to-End flow(s) installed successfully.
-      }}}
+  }}}
 
-      Click '''Refresh List''' button to confirm the new flow has been installed.
+  Click '''Refresh List''' button to confirm the new flow has been installed.
 
-      With the new path installed, you should be able to ping again from '''h1''' to '''h2'''. 
-      {{{
+  With the new path installed, you should be able to ping again from '''h1''' to '''h2'''. 
+  {{{
 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=2.64 ms
 64 bytes from h2-link-4 (10.10.5.2): icmp_seq=2 ttl=64 time=2.16 ms
-      }}}
+  }}}
 
-      Notice the extra delay added to the communication because we are using a longer path.
+  Notice the extra delay added to the communication because we are using a longer path.