Under Construction

Welcome to the Packet-Optical ONOS tutorial!!! 

In this tutorial, you’ll complete a set of exercises designed to explain the main concepts of the Packet-Optical use case of ONOS. We hope that with this tutorial, you’ll be able to create, configure, and start multi-layer networks on your environment, which can potentially represent a wide area network environment for your application performance studies.

To get you started quickly, the converged packet-optical VM  is  preconfigured  with the needed software environments including ONOS, linc-OE, Mininet, Jave-8, Erlang, linc-oe config generator, etc.

You should be able to Just run this  VM in VirtualBox using the instructions in the next section.

Table of Contents
outline true

Introduction

Service Provider Networks are complex and multi-layer in nature. Without converged packet Optical SDN capability, provisioning and adding bandwidth requires order of days, if not months. Since packet and optical networks are managed independently, each one of them has to be over provisioned to deal with traffic anomalies and failures. This leads to lack of service agility and is a significant source of CAPEX and OPEX overhead for the network operator.

This Tutorial demonstrates how ONOS can help address the challenges of managing multilayer service provider networks, by providing a sample demo on how converged packet-optical networks can be controlled by ONOS. We will introduce an emulated environment for converged control of packet and optical networks for wide area network, and show how it will truly enable service providers to use much more efficient traffic management practices.

Additionally, we will show ONOS’s capabilities as an enabler for cross-layer optimization, and applications on the northbound to control the forwarding planes at both the packet and optical layers. This environment can be used by the architects and developers to demonstrate feasibility of applications such as a multilayer PCE (which it’s basics for demonstrating benefits of converged networks.) This part is not very clear.

With Converged Control Plane, we hope to reduce cycle time to add capacity perhaps in minutes instead of days to a month. ONOS has the ability to add capacity based on traffic demand in real- or near real-time. In addition, when failure happens, instead of using the packet layer resources for recovery, ONOS can reconfigure the optical transport layer for best alternative re-route. With this approach, we are reducing the over-provisioning of resources, since transport layer is cheapest infrastructure to move bits. Finally, with enhanced converged control plane, we could potentially enable new services. Examples include network graph observability and real-time injection of network policies.

Prerequisite

You will need a computer with at least 8GB of RAM such that you can dedicate 4 Gig to your packet-optical VM and at least 5GB of free hard disk space. A faster processor or solid-state drive will speed up the virtual machine boot time, and a larger screen will help to manage multiple terminal windows.

The computer can run Windows, Mac OS X, or Linux – all work fine with VirtualBox, the only software requirement.

To install VirtualBox, you will need administrative access to the machine.

The tutorial instructions requires some prior knowledge of SDN in general, and OpenFlow and Mininet in particular. So please first complete the OpenFlow tutorial and the Mininet walkthrough. 

Before you try Packet-Optical use case, we highly recommend to complete ONOS tutorial too.

OOPs? Found a bug? Questions?

Email us (onos-discuss@onosproject.org) if you’re stuck, think you’ve found a bug, or just want to send some feedback.

Please have a look at the guidelines to learn how to efficiently submit a bug report.

Setup Your Environment

Install required software

You will need to acquire two files: a VirtualBox installer and the Tutorial VM (Link TBD by Marc) .

After you have downloaded VirtualBox, install it, then go to the next section to verify that the VM is working on your system.

Import pre-configured Virtual Machine

Start up VirtualBox, then select Machine>New, give it a name, and select Linux as type and Ubuntu (64 bit) as version. Press Continue.

Next, configure the VM with 2 GB (2048 MB) of memory. ( If you are going to run the bigger topology, Configure the VM with 4 GM ( 4096) of memory, Press Continue.

Select ‘Use an existing virtual hard drive file’, and point it to the vmdk file you downloaded Select "Create".  Note you can also import ".OVA" instead. 

Now you can start the VM by double clicking it; once it starts you can login with user "sdn" and password "rocks".

After some time you should see the desktop view for Ubuntu. You can open a terminal by double clicking Terminal.

This VM Contains the following subsystems / files :

1- ONOS;  Alternatively "ONOS from Scratch" 

2-Mininet; Alternatively "Mininet" 

3-Linc-OE, "Linc-OE GitHub"

4- Linc-OE config Generator ; "Config" which generates Sys.config representing Optical Layer Topology 

5- Mininet Python Scripts ; which starts mininet, and linc-oe" OpticalTest.py",  "opticalTestBig.py" 

6- Erlang ;  

                         wget https://packages.erlang-solutions.com/erlang-solutions_1.0_all.deb

                         sudo dpkg -i erlang-solutions_1.0_all.deb

                         rm erlang-solutions_1.0_all.deb

                         sudo apt-get update

                         sudo apt-get install erlang rebar"How to download Erlang" 

7-Java-8; Which could also be downloaded directly from "ONOS from Scratch"

...

If you've already gone through the ONOS tutorial, you'll already have the ONOS tutorial VM available. If not, check out the Introduction section of the ONOS tutorial to get the VM set up. However, don't log in as tutorial1 - we have a different username for this tutorial.

Email us (onos-discuss@onosproject.org) if you’re stuck, think you’ve found a bug, or just want to send some feedback.

Table of Contents

Starting the tutorial

When you start the VM, you'll be presented with a login screen. If you're already logged in to another tutorial, please log out by clicking the bottom-left icon, clicking "Logout", then click "Logout" again.

Each tutorial in the VM is presented as a different user. Log in to the optical tutorial user with the following credentials:

Username: optical
Password: optical

You'll be deposited on a desktop with a bunch of icons that will be used for the tutorial. Before we get started, double-click on the "Reset" icon. This will pop up a terminal and reset ONOS to make sure there is no state left over from any other tutorials.

Important Command Prompts

Symbol "$" means linux terminal.

...

"(linc@mininet-vm)1>" means Linc-OE CLI command prompt.LINC-OE CLI command prompt.

Resetting

We have provided a simple mechanism which allows you to restart the tutorial from scratch. Simply, click on the 'Reset' icon on your desktop and this will reset ONOS to its initial state. It'll take a few seconds for ONOS to restart and during that time you may not be able to launch your ONOS cli. 

Packet-Optical Topology

...

 (via Python-Script)

Go to mininet/examples:

You should have a file that contain the packet-optical topology sample " opticalTest.py ". This file is a python script which creates the following topology:

...

Each packet node is attached to a host representing a data center.  The The traffic is typically initiated from Hosts attached to the packet networks. 

Note that there is no physical links between the packet nodes.  All All traffic sourced at the data centers are routed through the optical plane. 

...

The tap interfaces are used to interconnect the optical switches and packet nodes. We are utilizing linux tap interfaces for interconnecting the optical switches and packet switches. utilizing Linux tap interfaces for interconnecting the optical switches and packet switches. 

Start ONOS

Double-click the 'Reset' icon on the desktop to start ONOS up with the correct configuration to run packet-optical.

Wait for some time to let ONOS load all the features and modules (about a minute or so).

Start Mininet and Linc-oe

To start Linc-oe and Mininet go to:

Just double click on 'Mininet Small' (terminal icon) at desktop  

or run following in the terminal:

This will create push link and device information to ONOS, creating the topology shown above in the figure and ask you to 'Press any key to push Topology.json to onos...'

Before you press any key you need to run ONOS. To run ONOS

or

This will start ONOS. Now you can Press any key to push Topology.json to ONOS.

.

To verify, once the Mininet prompt appears, double-click the 'ONOS' icon to open the ONOS CLI. Now run the 'summary' command and check that ONOS had 16 devices attached.

Demo 1: Establishing connection between hosts/DataCenters using ONOS-GUI.

To get the ONOS-GUI type the following at the terminal:just double click on 'ONOS GUI' (chrome icon) on Desktop.

or write following in your browser,

or

...

Note: Do not use $ onos-gui to get ONOS GUI.

This will open the ONOS-GUI in a tab in you default browser. You can press z to get the split view of packet and optical plane and press h to see hosts (for more options press /). note: using convention of bold font for user keystrokes

As you can see that there are no host discovered by ONOS. This is due to the fact that ONOS only discovers a host when there is traffic from the host. So let's generate traffic from all hosts.

In the Mininet command prompt: 

...

Now if you send traffic between these host you will see traffic is going through successfully. Note in this tutorial script we have only create one tap interface per packet-optical switch. Which means we cannot setup more then one connection per switch. If you want more then one connection per switch you need to add tap interface accordingly in "opticalTest.py".

Demo 2: Establishing connection between hosts/DataCenters using ONOS-CLI.

You can send Host-to-Host intent using ONOS-CLI too. To do so you have to write enter the following command in ONOS-CLI command prompt. For example purpose I have chosen h3 and h4 below:

...

There is an other way to send Host-to-Host Intent to ONOS with specified bandwidth using BandwidthCalendaring app which is explained in next section. 

Demo 3

...

TBD

...

: Link recovery from optical layer failures

In this section we gonna will demonstrate how failure in the optical layer can be recovered by ONOS in a pinch on second without  without disturbing the traffic flow.

Two To see the what path is taken by traffic sent by a certain host to send traffic ( in the GUI of course), you can click on that Host and click on "show related traffic". You will see something similar to the figure show shown below.

Yellow The yellow path shows the packet layer path, and the purple path shows the optical layer path.

Now we will introduce failure in the optical path of the traffic flow. We need to get into linc-oe console to introduce failure in optical switch. To do so do following,an optical switch:

Just double click on 'LINC-OE' (terminal icon) on Desktop

or write following in the separate terminal:

This will get you into the command prompt of linc-oe. Now you need to figure out which optical switch's switch port will cause failure in the optical path. You do this by clicking on any switch in the purple path, and note noting the DPID of this switch and the switch connected to this switch (which also must be part of optical path). Now you have to figure out what port on each of these switches is responsible for connecting them together. These many There are several ways, but the most reliable ways method is to look into sys.config. In the separate terminal write following commands, open this file:

In the logical_switches section, look for dpids the DPIDs that you just have noted and note the switch Id corresponds corresponding to both DIPDS, . you will see something like,

In my case, the switch Id ID that correspond to DPID "00:00:ff:ff:ff:ff:ff:05" is "7" and DPID , "00:00:ff:ff:ff:ff:ff:07" correspond to switch Id "2". Note the switch Id ID of both the switches. Now in

In the same file there is a section for optical_links,:

Here, {{

...

7,

...

40},{

...

2,

...

           {{10,20},{7,20}}]},

50}} means switch_Id 7 port 40 is connected to switch_Id 2 port 50. You need to find the link port then you want to bring down. In my case its switch 7 port 40.

We know that it's a hectic a task, and we are in the progress of making it easier.

Once you know the switch and port, run the following command in the Linc-oe console to bring that port down.

It will return "ok".

You will see that ONOS will reroute the the traffic as shown in the figure.

Image Added

Playing with a bigger topology.

We have also provided a Python script with bigger topology, "opticalTestBig.py"

We highly encourage you to run that topology and play with it and give us your feedback.

Resetting and getting out of trouble.

If you want to reset Mininet or ONOS, or just want to get out of trouble, do the following.

For resetting Mininet and linc-oe just double click on 'Reset' (terminal icon) on Desktop or type following in mininet console,

It will close the Mininet and LINC-OE. Now you can follow the same procedure describe above to start mininet and linc-oe again.

To reset ONOS, use the Reset icon on the desktop. Note this will clean up Mininet as well, so it's best to exit Mininet before you do this to prevent it hanging

In the above list show all the optical links. {{7,40},{2,50}}, means switch_Id 7 port 40 is connected to switch_Id 2 port 50. You need find the link port then you want to bring down. In my case its switch 7 port 40.

We know its hectic a task and we are in the progress of making it easier.

Once you know the switch and port you need to run following command in Linc-oe console to bring that port down.

It will return "ok".

You will see that ONOS will reroute the the traffic as shown in the figure.

Image Removed

Demo 5: Link recovery from packet layer failures

TBD

Playing with bigger topology.

We have also provide python script with bigger topology, "opticalTestBig.py"

We highly encourage you to run that topology and play with it and give us you feed back.