MuL SDN Controller HOWTO for pre-packaged VM

Transcription

1 MuL SDN Controller HOWTO for pre-packaged VM 1 P a g e

2 Table of Contents 1 Starting the VM Using MuL controller Mul component overview Running MUL Running MuL s forwarding components Running forwarding components: l2switch Running Applications: fabric Running MuL s core components Run director/core Running Mul topology/routing service Running Applications: cli Running MUL controller in HA mode Running MUL with mininet Run mininet with desired topology Check Openflow connection with MuL Running ping test Running MUL with Linc (Openflow 1.3) Run LINC Check Openflow connection with MuL P a g e

3 1 Starting the VM The pre-packaged VM is Ubuntu based and can be run using any popular virtualization software such as Virtual Box or VMware. The VM has been bundled with Mul v3.3 SDN controller (limited edition commercial release), mininet and LINC openflow 1.4 vswitch. The login information for the VM is: User : kulcloud Password : kulcloud 2 Using MuL controller 2.1 Mul component overview Before running and Mul, one has to understand that MuL has many components, each running as a separate application. 3 P a g e

4 MuL is basically a suite of co-operative applications comprising of: 1) Mul director/core a. Major component of mul b. Handles all low level connections, switches and openflow processing. c. Binary Name : mul 2) Mul services a. These provide basic infra services built on top of mul director b. Currently available : i. Topology discovery service ii. Path finding service iii. Loop detection iv. Dynamically recalculates paths on various network events c. Binary Name : multr 3) MuL system apps a. System apps are built using a common api provided by mul-director and mul-services b. These are hardly aware of Openflow and hence designed to work across different openflow versions provided switches support common requirement of these apps c. Currently available system apps : i. L2 learning app A simple L2 MAC learning application Supports IGMP Snooping Binary Name : mull2sw ii. Fabric app Multi-tenant aware P+V application for data-center Supports network virtualization Binary Name : mulfab iii. Service chaining app Enables service chaining for NFV services. Binary Name : mulmakdi iv. CLI app This provides a common cli based provisioning tool for all MuL components. There are CLI guides available for configuration of various controller components located in the VM directory : /home/kulcloud/mul-release/docs Binary Name: mulcli 4 P a g e

5 MuL has a highly flexible and extensible architecture 2.2 Running MUL By default, many of the core-components of MuL will run on VM boot-up mul, multr and mulcli. These can be stopped or restarted like any other Ubuntu services. For example: $ sudo (stop start restart) mul $ sudo (stop start restart) multr $ sudo (stop start restart) mulcli If it is necessary to re-run or run any of the above by hand, one can stop the respective component and start them from a terminal. For example, to restart mul-core to listen to any custom TCP port: $ sudo stop mul $ sudo mul P d 5 P a g e

6 2.2.1 Running MuL s forwarding components The main forwarding components of MuL are mull2sw, mulmakdi and mulfab depending on the particular use case. Normally it is not advised to run multiple forwarding components at the same time. These forwarding components are not by default on VM boot-up Running forwarding components: l2switch L2switch application provides bare-bones forwarding scheme based on l2 learning. $ sudo mull2sw Possible options to use -d : Daemon mode (Run in background) -s <server-ip> : Controller server ip address to connect (locahost by default) Once we run l2switch app, network wide l2-switching takes place so if you have any hosts connected to an Openflow network they will start pinging each other. This app can work on loopy topologies as long as loop detection is enabled in topo-routing module Running Applications: fabric The fabric app provides a slightly complex forwarding scheme wherein it provides a loop and learning free point to point virtual network connectivity between two or more hosts. Furthermore, it is multi-tenant aware. $ sudo mulfab -d OR (for verbose mode) $ sudo mulfab Possible options to use - -d : Daemon mode (Run in background) -s <server-ip> : Controller server IP address to connect (localhost by default) NOTE This application needs topo-routing service to be also running. 6 P a g e

7 2.2.2 Running MuL s core components The following sections will explain the procedure to follow if one is interested to run each of MuL s components separately or in verbose mode Run director/core $ sudo mul d OR (for verbose mode) $ sudo mul Possible options to use - mul options: -d : Daemon Mode -S <num> : Number of switch handler threads -A <num> : Number of app handler threads -P <port> : Port Number for incoming switch connection -H <peer> : Peer IP address for HA -n : Don't install default flows in switch -p : Enable OF packet dump for all switches -s : Enable ssl for all switch connections -l <level> : Set syslog levels 0:debug, 1:err(default) 2:warning -x : Verify switch-ca cert. Only applicable along with -s option -h : Help For running mul with ssl, kindly refer to MUL-HOWTO-SSL in the release docs Running Mul topology/routing service $ sudo multr -d OR (for verbose) $ sudo multr Possible options to use - -d : Daemon mode (Run in background) -s <server-ip> : Controller server IP address to connect (localhost by default) Running Applications: cli This application provides a unified cli which hooks in with each of the MuL controller components thereby providing a single point of management of all MuL controller components: $ sudo mulcli V d ## Access to fabric cli on telnet port P a g e

8 OR (for verbose mode) $ sudo mulcli V Possible options to use - -d : Daemon mode (Run in background) -s <server-ip> : Controller server ip address to connect (localhost by default) -V <telnet-port> : cli telnet port number -H <peer> : Peer IP address for HA NOTE This application will auto-detect which of the mul s application are present. More comprehensive cli command guide can be found in /home/kulcloud/mulrelease/docs folder inside the VM Running MUL controller in HA mode MUL core component supports multiple controller functionality as defined by Openflow spec v1.3 and above. To use it one has to first enable the necessary functionality in the Openflow switches. Please note that you would need to stop already running mul director component and restart with necessary arguments Mul core can be run in multiple controllers HA mode using the following: $ sudo mul H <IP address of Peer> Example: Controller 1-8 P a g e

9 Controller 2 - NOTE It is recommended that before connecting the switches to controller(s), the controllers be connected in HA-mode. 2.3 Running MUL with mininet Mininet is creates a realistic virtual network, running real kernel, switch and application code, on a single machine (VM, cloud or native), in seconds, with a single command. Please visit mininet.org for more information. It is already installed for ready usage in the VM. The following steps show how to get up and running MuL with mininet Run mininet with desired topology 9 P a g e

10 2.3.2 Check Openflow connection with MuL Considering the fact that all necessary MuL Controller core components run at VM bootup, we just need to check switch connection status. One can also check each switch specific connection detail as follows: Running ping test To run ping test, one has to run any of the forwarding components of MuL. For this example we reply on l2 learning app. Let s get it started: 10 P a g e

11 Now we can try ping in mininet shell: 2.4 Running MUL with Linc (Openflow 1.3) LINC is a pure OpenFlow software switch written in Erlang. It's implemented in operating system's user-space as an Erlang node. Such approach is not the most efficient one, but it gives a lot of flexibility and allows quick development and testing of new OpenFlow features. Please visit for more information. 11 P a g e

12 2.4.1 Run LINC LINC switch is pre-installed in the given VM. We can run it using the following: Check Openflow connection with MuL Now, we can confirm that LINC switch connects to MuL. It is very interesting to note that MuL can manage both Openflow 1.0 and 1.3 at the same time. The following shows an instance when MuL has connected with OF1.0 switches simulated by mininet as well OF1.3 LINC switch simultaneously: 12 P a g e

13 Now we are ready to perform different configurations. Please find how to provision using CLI guide present in /home/kulcloud/mul-release/docs directory in the VM. 13 P a g e

14 Document Revision History Rev. No. Date Revised By Comments MUL release team VM how-to 14 P a g e