The instructions in this document are applicable to personal computers running the following Operating Systems:

Transcription

1 Preliminary Notes The instructions in this document are applicable to personal computers running the following Operating Systems: Microsoft Windows from version 7 up to 10 Apple Mac OS X from versions 10.8 Mountain Lion up to El Capitan Debian-based Linux, such as Ubuntu (recommended) from versions Precise to Trusty Tahr. It is not recommended to apply the setup to a virtual machine, although possible, as the configuration requires an hypervisor environment (Virtualbox) in the host system. For the aforementioned Operating Systems, the setup makes use of package managers in order to turn the process well controlled (versions, updates), simple to cleanup and not affecting the host environment. 1 Review and enhance the Environment This section will guide you on updating and enhancing your experimental lab environment that was set in Assignment #2, for systems running Windows, Mac OS X and Linux. 1.1 Microsoft Windows Start a Console in order to upgrade your installed programs, beginning by listing the current installs: showstringspaces C:\ > choco list --local-only Confirm that you have the necessary Programs (from Assignment #2) and start the upgrade: showstringspaces C:\ > choco upgrade all After this point, install additional programs, such as a very rich editor for programming (Sublime Text) and an XWindows server (Xming): showstringspaces C:\ > choco install xming C:\ > choco install sublimetext3 1

2 For those programs to work properly in Windows, some environment variables need to be set. In your command prompt open a System Applet for the Control Panel: showstringspaces C:\> sysdm. cpl A System Properties window will open (Fig. 1). Select the TAB named Advanced and click on Environment Variables.... Figure 1: Setting New System Properties DISPLAY Variable In the window that opens create a New... System Variable with name DISPLAY and with Variable value of localhost:0.0, then save and create another System Variable with name SUBLIME and with a Variable value pointing to the folder C:\Program Files \Sublime Text 3 (Fig. 2). Add the following to the end of your PATH variable ;%SUBLIME% then close the System Properties panel and your Console. You will now be able to call the Sublime Text Editor from the command line by issuing the command, such as subl filename, to edit files. For the XWindows server, start XMing and an X icon of the server will be visible in the Taskbar system tray. Hover the mouse over it and it should display something like Xming server - 0:0. 2

3 Figure 2: Setting New System Properties SUBLIME Variable 1.2 Apple Mac OS X Open Terminal and install the following programs using Homebrew after updating and upgrading the current installed packages and Apps: : $ brew update : $ brew upgrade : $ brew cask install xquartz : $ brew tap caskroom / versions : $ brew cask install -- appdir ="/ Applications " sublime - text3 For each command the Terminal will start displaying lots of information, as Homebrew is keeping you updated on what it is doing. This flow of information will be a guide to let you know whether or not the computer is still working, and so, do not interrupt it. 1.3 Linux For a Linux system, namely Ubuntu, the XWindows system is normally already installed. You may just need to install the Sublime Text 3 editor. : $ sudo apt - get update : $ sudo add -apt - repository ppa : webupd8team / sublime -text -3 : $ sudo apt - get update : $ sudo apt - get install sublime - text - installer 3

4 2 New Experiments with SDN First, we need to reconfigure the environment previously prepared in Assignment #2, in order to ensure consistent networking conditions and connectivity. Open a browser and start by downloading the HP VAN SDN Controller Box (1 GB) and two Vagrant files for setting up the SDN Controller VM and the Mininet VM: Controler URL: The Vagrantfile.sdnctrl URL: The Vagrantfile.mininet URL: Open Virtualbox to reconfigure the Networking conditions. We need to ensure that we have a private network for Host-only addresses. Ensure that you have a vboxnet0 with gateway address of as illustrated in Fig. 3 and 4. Figure 3: Setting VirtualBox Private network in Mac OS X or Linux Figure 4: Setting VirtualBox Private network in Windows Now we need to provision through Vagrant a Lab environment with a reconfigured Mininet and the SDN Controller. 4

5 But first we need to clean up the previous Mininet VM configured in in Assignment #2. Open a Console/Terminal and issue the commands as follows. Go to your working folder (MyProjects), where you should have already Mininet, for example in Windows C:\Users\username\Desktop\MyProjects\, in Mac or Linux /Desktop/MyProjects/: : $ cd mininet : $ vagrant destroy : $ vagrant box list : $ vagrant global - status The above commands will destroy the previous instance and VM files, list the Mininet Boxes in your system (you should have there a ktr/mininet (virtualbox, 1.1.0), and list the Vagrant status of your VMs, which should be empty. You may now remove the mininet folder and all files in it. Back to your MyProjects folder, create the following folder tree: sdnlab data... This directory will hold files shared with mininet. hpvansdn... This directory will hold the configuration for the HP VAN SDN Controller VM and its Vagrantfile. mininet... This directory will hold the configuration for the Mininet VM and its Vagrantfile. Now go to the go to hpvansdn folder and move into there the Vagrantfile.sdnctrl you downloaded and rename it to Vagrantfile. Do the same in folder mininet moving into there the Vagrantfile.mininetl you downloaded renaming it to Vagrantfile. The next step is to add the HP VAN SDN Controller Box to Vagrant. Go to your Downloads folder (where you should have a file named hp-vansdn2 5.box ) and issue the following command: : $ vagrant box add -- name hp - vansdn hp - vansdn2_ 5. box This phase may take up a few minutes, depending on the speed of the host system. Now it is time to create and start your new VMs, and so, go to hpvansdn folder and issue the command: : $ vagrant up When finished and if no errors occurred do the same in folder mininet. Confirm that both VMs are correctly configured in the network by issuing the following commands fro your host system: : $ ping : $ ping

6 When ready we will then establish a session with the Mininet system using the following command issued in the mininet folder: : $ vagrant ssh Note that the Mininet Vagrant file enables X11 forwarding. The session is established and you should get the machine prompt: Welcome to Ubuntu LTS ( GNU / Linux generic x86_ 64 ) vagrant@mininet : $ For the SDN Controller, if it started correctly, you should be able to open the App UI. Use a web browser (in Windows do not use Google Chrome but Internet Explorer) and open the URL Please note that it may take take some time (a couple of minutes) until having the UI of the SDN Controller available. Figure 5: HP VAN SDN Controller UI Use the credentials: user=sdn, password=skyline. In Mininet issue the following commands to create a simple network topology to be seen in the Controller: $ sudo mn -- topo =tree,3 --mac -- controller = remote,ip = mininet > pingall In the SDN Controller Open Topology you should be able to see and interact with your network, as illustrated in Fig. 8. 6

7 Figure 6: HP VAN SDN Controller App Additionally, you may get into any host of the network (the command prompt) and run programs, as illustrated in Fig. 7, by issuing in the mininet prompt the followig command (illustrated for host node h1): mininet > xte rm h1 Figure 7: A host Shell (host node h1) To end the Mininet emulation use the command exit at the mininet prompt. 7

8 Figure 8: HP VAN SDN Controller Network It is also advisable to clean any phantom Mininet processes in the system with the command sudo mn -c : mininet > exit vagrant@ mininet : $ sudo mn - c vagrant@mininet : $ You can now exit the session: vagrant@mininet : $ exit logout Connection to closed. In order to stop the Virtual Machines and to verify the global state of all active Vagrant environments on the system, issue the following commands in the respective folders: : $ vagrant halt == > default : Attempting graceful shutdown of VM... : $ vagrant global - status Confirm that the statuses of the VMs is powered off, otherwise they will keep consuming resources of the host system. 8