[[TOC()]]

[[Include(WikiToC)]]

= !InterDigital !EdgeLink Platform =

== Description ==
In this tutorial we'll demonstrate how to use [wiki:/Hardware/SubSystems/IDEdgeLink#InterdigitalEdgeLink60GHzmmWaveMeshTransportSystem InterDigital EdgeLink mmW Mesh Transport System]. The setup for the experiment is shown in Figure 1.

[[Image(EdgeLink-Setup.jpg, width=600px)]]

In order to access the test bed, create a reservation and have it approved by the reservation service. Access to the resources are granted only after the reservation is confirmed. Please follow the process shown on [wiki:CosmosOverview/Workflow the COSMOS work flow page] to get started. 

== Tutorial Setup ==

 Follow the steps below to gain access to the [wiki:Architecture/Domains/cosmos_sb1 sandbox 1] console and set up nodes with appropriate images.
 
 1. If you don't have one already, sign up for a [wiki:GettingStarted#MakeanAccount COSMOS account]
 1. [wiki:GettingStarted#MakeaReservation Create a resource reservation] on sandbox 1
 1. Prepare your local computer (i.e. laptop) for Edgelink ONOS and Orchestrator status page access:
   * To access the ONOS GUI prepare [wiki:UserGuide/RemoteAccess/SshTunnel ssh tunnel] to the sandbox 1 console and the Network Controller server, port 8181 (i.e. map localhost:8181 to srv1-in3.sb1.cosmos-lab.org:8181) 
   * To access the ORCHESTRATOR GUI prepare [wiki:UserGuide/RemoteAccess/SshTunnel ssh tunnel] to the sandbox 1 console to the Network Controller server, port 8888 (i.e. map localhost:8888 to srv1-in3.sb1.cosmos-lab.org:8888) 
   * If VPN is preferred over SSH then follow the instructions to establish a [wiki:UserGuide/RemoteAccess/VPN VPN tunnel] to the [wiki:Architecture/Domains/cosmos_sb1 COSMOS sandbox 1]. This will be used by the browser to connect to a web server running on the server nodes.
 1. [wiki:UserGuide/RemoteAccess#RemoteAccess Login] into sandbox 1 console (console.sb1.cosmos-lab.org) with multiple SSH sessions as needed.
 1. For this experimentation, srv1-in3 will be used as a controller node, srv1-in1 and srv1-in2 as traffic machines
 1. Check the status and make sure the server and all the devices used in the experiment are turned off:
{{{#!shell
omf stat -t rfdev1-1,rfdev1-2,srv1-in1,srv1-in2,srv1-in3
}}}
  To turn off the resources needed for the experiment:
  {{{#!shell
omf tell -a offh -t rfdev1-1,rfdev1-2,srv1-in1,srv1-in2,srv1-in3
}}}
 1. Load the image on the server [Documentation/Short/LoadImage  omf image loading] commands:
 {{{#!shell
omf load -t srv1-in3 -i idel.ndz  
}}}
 1. Turn the server and Mesh nodes on:
{{{#!shell-session
omf tell -a on -t rfdev1-1,rfdev1-2,srv1-in1,srv1-in2,srv1-in3
}}}
   
== Experiment Execution ==
The Mesh Network Controller (NC) will autonomously detect the available Mesh Nodes and establish links between the GW Node and the detected Mesh Nodes.   
=== Configure Routing between the NC machine and the Gateway Node ===
The communication link between the Controller located on the srv5-lg1 compute machine and the Gateway Node must be established.
{{{#!shell-session
userid@console:~$ ssh native@srv1-in3 
-------------------
password: native
-------------------
native@srv3-lg1:~$ sudo ./Rutgers_Package/setup_routes.sh
}}}

[[CollapsibleStart(Routing Script)]]
The script to setup a communication route between the NC and GW Node
{{{#!shell
#!/bin/bash
route add -host 192.168.200.10 dev enp3s0
route add -net 192.168.150.0/24 dev enp3s0 gw 192.168.200.10
}}}
[[CollapsibleEnd]]

=== Check routes and connections are in place before starting ONOS ===

Display the routing table. NOTE: the user interface displayed in Figure 2 is for example purposes, your NC machine may be different.  The routes for subnets 192.168.150.0, 192.168.200.0 & 192.168.200.10 should be in place as shown in Figure 2.
{{{#!shell
native@srv3-lg1:~$route -n 
}}}
Expected routes are shown as per Figure 2

[[Image(Routing.png, 800px)]]

Figure 3: Routing tables.

=== Verify the GW Node is reachable by the NC Controller ===
{{{#!shell-session
native@srv3-lg1:~$ ping 192.168.200.10
}}}
 === Start the ONOS controller ===
{{{#!shell-session
native@srv3-lg1:~$ ./onos/onos-1.9.0/bin/onos-service start
}}}

[[Image(ONOS.png, 800px)]]

Figure 3: Successful ONOS startup.

=== Services on the Mesh Nodes ===
Each Mesh node is configured to execute the mesh SW upon a power cycle or soft reboot.  You can manually restart the Mesh SW on each node by momentarily removing the ethernet PoE connection to each of the Nodes or use the omf command to “turn off” & “turn on” rfdev1-1 & rfdev1-2 which are the GW Node and NON-GW Node respectively .  A soft reboot of the nodes can be executed by accessing the Wi-Fi debug subnet.
==== The Edgelink GW node can be accessed via the IP address assigned by the debug network ====
{{{#!shell-session
userid@console:>ssh root@srv1-in1
root@srv1-in1:~$ ssh root@10.113.1.102
}}}
==== The EdgeLink NON-GW node can be accessed via the IP address assigned by the debug network ====
{{{#!shell-session
userid@console:>ssh root@srv1-in2
root@srv1-in2:~$ ssh root@10.113.1.103
}}}


Once you have accessed the node via the debug network you can ping the connected node and send iperf data.  From here you can also issue the soft reboot command but ONLY if necessary, to restart the node.  The bridge IP address is 192.168.150.1 and 192.168.150.3 respectively for the  GW Node and the NON-GW Node.
{{{#!shell-session
root@ls1043ardb:#ping 192.168.150.x
(OR to REBOOT)
root@ls1043ardb:#reboot
}}}

== Start the ONOS GUI ==
Open a Google or FireFox browser and enter the url of the ssh or VPN  tunnel established to the COSMOS sandbox 1 for your local machine to connect to a web server running on the server node.
{{{#!shell-session
localhost :8181/onos/ui
}}}
You should see the ONOS login page as shown in Figure 4

[[Image( ONOS-Login.png, 400px)]]

Figure 4: ONOS Login Page

Enter ONOS credentials:
{{{#!shell-session
User :		onos
Password:	rocks
}}}
ONOS topology will display the GW node and the non-GW node as shown in Figure 5 when the network controller detects/registers the nodes.

[[Image( ONOS-Topo.png, 600px)]]

== Start the ORCHESTRATOR ==
The Orchestrator is a thin client application used to provision transport slices, bandwidth reservation and service level agreements (SLA).  See Orchestrator User Guide for additional information.

=== Start the Thin Client Orchestrator ===
Start the !TomCat Service
{{{#!shell-session
native@srv3-lg1:~$ sudo systemctl daemon-reload
native@srv3-lg1:~$ sudo systemctl start tomcat
--------------------------------------
Status of the tomcat service can be verified with the following:
--------------------------------------
native@srv3-lg1:~$ sudo systemctl status tomcat 

}}}
=== Access Orchestrator in a web browser ===
Open a Google or !FireFox browser and enter the url of the ssh or VPN tunnel established to the COSMOS sandbox 1 for your local machine to connect to the TomCat web server running on the server node.
{{{#!shell-session
localhost:8888/orchestrator
}}}
 * The Configuration Page as shown in Figure 6 should appear.

[[Image( ONOS-Config.png, 400px)]]

{{{#!shell-session
Controller IP:			where ONOS is running (via your localhost)
Controller RPC Port:	8181 (this is the port at which ONOS UI is accessed)
}}}
  * Select the Save button

•	Select the Customer Registration page as shown in Figure 7

[[Image( ONOS-Register.png, 400px)]]

Enter credentials:
{{{#!shell-session
Customer ID:		1
Password:			root
}}}

 *Select Register and you should receive a “Registration Successful” indication.

  * At this point you will be able to select from the operations displayed.  
  * Please refer to the Orchestrator User Manual for further directions and capabilities.

== Saving the Node Images ==
If you modify software on the server node save the image by the [omf save image commands] but don't forget to first prepare the node by executing '''as root user''' (this is the example for srv5-lg1 node):
{{{#!shell-session
root@srv5-lg1:~# ./prepare.sh
}}}
This script will “clean” and “dump” old log files and any other unnecessary files that do not need to be saved as part of the image, thereby reducing the size of the saved image.
At the end of this script, the node will shutdown (it might block your ssh window forcing you to open another one); once back on the console, you can save that node disk image with 
{{{#!shell-session
username@console:~# omf save -n srv1-in3.sb1.cosmos-lab.org
}}}
(please note the -n option and the FQDN for the node both of which are mandatory for successful saving operation).