TAGORE INSTITUTE OF ENGINEERING AND TECHNOLOGY Deviyakurichi-636112, Attur (TK), Salem (DT). Website: [Link] (Approved by AICTE, New Delhi and Affiliated to Anna University, Chennai) Accredited by NAAC Department of Artifical Intelligence and Data Science CCS365 - SOFTWARE DEFINED NETWORKS LAB MANUAL Academic Year 2024-2025 (2021 Regulation)TAGORE INSTITUTE OF ENGINEERING AND TECHNOLOGY DEVIYAKURICHI - 636 112, THALAIVASAL TK, SALEM DT. Accredited by NAAC and an ISO Certified Institution ‘Name Reg. No. Semester Branch [Link] / Subject... Coxtified that this is the Bonafide record ofthe Practical done forthe aboue sub ject in the Labaxatory during the period... Staff - in - charge. Head of the Department Submitted for the University Practical Examination held at TAGORE INSTITUTE OF ENGINEERING AND TECHNOLOGY, DEVIYAKURICHI or INTERNAL EXAMINER EXTERNAL EXAMINERCONTENTS [Link] DATE NAME OF THE EXPERIMENTS ‘Setup your own virtual SDN lab i) VirtualBox/Mininet Environment for SDN - [Link] ii) hups:/www [Link]. iii) GNSS PAGE | MARKS NO. FACULTY SIGNATURE Create a simple mininet topology with SDN controller and use Wireshark 10 ‘capture and visualize the OpenFlow ‘messages such as OpenFlow FLOW MOD, PACKET IN, PACKET OUT etc Create a SDN application that uses the Northbound APT to program flow table rules on the switch for various use cases like L2 learning switch, Traffic Engineering, Firewall ete Create a simple end-to-end network service with two VNFs using vim-emu tps://[Link]/containernet/vim- emu 5) Install OSM and onboard and. orchestrate network service.Setup your own virtual SDN lab eo i) Virtualbox/Mininet Environment for SDN - [Link] ae ii) https:/[Link] ili) GNS3 AIM: To Setup your own virtual SDN lab using one of the three options: Virtualbox/Mininet, Kathara, or GNS3 PROCEDURE: i) Virtualbox/Mininet Environment for SDN - http:/mininetorg 1, Download and install Virtualbox from its [official website]. Download and install Mininet from its [official website]. You can choose to install Mininet as a virtual machine image, a native installation, or a source code installation. 3. Launch Mininet and create a virtual network using the command line interface or the graphical user interface. You can also use predefined network topologies or custom scripts to create your network. 4. Connect your virtual network to an SDN controller, such as OpenDaylight, using the OpenFlow protocol. You can download and install OpenDaylight from its [official website]. 5. Test and run different SDN applications and scenarios on your virtual network using the Mininet commands or the SDN controller interface. vOUTPUT: omni bee at oe Daten pen RESULT: ‘Thus, the setup of VirtualBox/Mininet Environment for SDN was installed successfully.[Link]: DATE: 22 Create a simple mininet topology with SDN controller and use Wireshark to capture and visualize the OpenFlow messages such as OpenFlow FLOW MOD, PACKET IN, PACKET OUT ete,. AIM: 1, Create a simple Mininet network with an SDN controller (Ryu). 2. Capture OpenFlow messages, including FLOW_MOD, PACKET_IN, and. PACKET_OUT, using Wireshark. 3. Visualize the captured OpenFlow messages for analysis. PROCEDURE: 1. Install Mininet: Snsure you have Mi this task, 2. Install Ryu SDN Controller: Install Ryu, a popular SDN controller, using pi pip install ryu [Link] the Mininet Topology: Create a Python script (e.g., “mininet_topology.py*) to define your Mininet network topology and start Mininet with the Ryu controller. Here's an example topology with a single switch and two host “python, from [Link] import Mininet from [Link] import SingleSwitchTopo from [Link] import RemoteController # Create a Mininet instance net = Mininet(topo=SingleSwitchTopo(2), controller=RemoteController) # Start Mininet [Link]() 4, Start the Ryu Controller: Ina separate terminal, start the Ryu controller: inet installed on your system. You can use a Linux distribution for ryu-manager 5. Capture OpenFlow Messages with Wireshark: Start Wireshark and select your network interface (e.g., “eth0*). * Apply a display filter to capture only OpenFlow messages. Use the filter expression: “of. «Begin capturing packets by clicking the "Start” button in Wireshark. 6. Generate OpenFlow Messages: In the Mininet terminal, you can use the Mininet CLI to generate OpenFlow messages. For ‘example, you can add a flow rule (FLOW_MOD) or generate traffic (PACKET_OUT).To add a flow rule (FLOW_MOD): mininet> h1 ovs-ofetl add-flow s1 in_port=1,actions=output:2 To generate traffic (PACKET_OUT): mininet> hl ping -c 1 h2 7. Stop Wireshark Capture: ‘Stop capturing packets in Wireshark when you've generated enough OpenFlow messages. OUTPUT: ‘© The Wireshark capture should display OpenFlow messages exchanged between the Ryu controller and the Mininet switch. You will see messages like FLOW_MOD, PACKET_IN, and PACKET_OUT, along with their details. ‘© Use Wireshark’s visualization tools to analyze and inspect the captured OpenFlow messages. You can filter, sort, and drill down into specific messages to understand the communication between the controller and switches. RESULT: This setup allows you to observe and analyze the OpenFlow messaging in a simple SDN network. You can further customize the Mininet topology and generate more complex OpenFlow scenarios for testing and analysis.[Link]: DATE: 3 Create a SDN application that uses the Northbound API to program flow table rules on the switch for various use cases like L2 learning switch, Traffic Engineering, Firewall ete AIM: Develop an SDN application that uses the Northbound API to program flow table rules on SDN switches for different use cases: L2 learning switch, Traffic Engineering, and Firewall. PROCEDURE: 1. Set Up the Development Environment: Install the Ryu SDN controller and any necessary Python libraries. 2. Create the Ryu SDN Application: Create a Python script for your Ryu SDN application, which will implement the Northbound API to program flow rules. 3. L2 Learning Switch Use Case: In your Ryu application, use the Northbound API to program flow rules for basic L2 learning. For example, when a packet arrives, add a flow entry to the switch's flow table based on the source MAC address and port. 4. Traffic Engineering Use Case: Implement traffic engineering rules using the Northbound API. For instance, you can define flow rules to optimize traffic paths or prioritize specific traffic based on application requirements. 5, Firewall Use Case: Implement firewall rules using the Northbound API to drop or allow specific traffic based on criteria such as source/destination IP addresses, ports, or protocols. 6. Run the SDN Application: Start your Ryu SDN application with the Ryu manager using the following command: ryu-manager your_application.py tion: 7. Test the SDN Applic Create a virtual network or use a Mininet topology for testing your SDN application. Generate traffic to see how the application programs the flow table rules.OUTPUT: © For the L2 learning switch use case, the application should program flow rules that ‘enable the switch to learn and forward traffic based on MAC addresses. * In the traffic engineering use case, the application should optimize traffic paths or prioritize certain types of traffic as per your defined rules © Inthe firewall use case, the application should allow or block traffic based on your defined criteria. * The application's output should include log messages or other forms of feedback, showing that it is functioning correctly. RESULT: ‘The result is a working SDN application that leverages the Northbound API to program flow table rules on SDN switches for different use cases. The application should effectively control network traffic based on the specified policies and rules.[Link]: 4 Create a simple end-to-end network service with two VNFs using vim-emu [Link] 5) Install OSM and onboard and DATE: orchestrate network service. AIM: * Create a simple end-to-end network service with two VNFs using vim-emu. Install OSM and onboard and orchestrate the network service. PROCEDURE: 1, Set Up the Environment: Make sure you have a Linux system. You can set up a virtual machine or a dedicated system, = Install the required dependencies, including Docker and Docker Compose. 2. Install vim-emu: Follow the instructions in the vim-emu GitHub repository ([Link] to install vim-emu. 3. Create Network Topology: Define a network topology using vim-emu. You can create a Python script that specifies the network, VNFs, and their interconnections. For example, create a file named “network_topology.py": python from [Link] import Containernet from [Link] import Docker from [Link] import TCLink from [Link] import CLI net = Containernet() vnfl = [Link](‘vnf1', dimage vnf2 = [Link](‘vnf2', dimage 'vnfl_image") 'vnf2_image") [Link](vnfl, vnf2, els=TCLink) [Link]() CLi(net) net.stop0 4, Create VNF Docker Images: Build Docker images for your VNFs. Create a ‘Dockerfile” for each VNF, specifying its requirements and configurations. Build the images using Docker commands.5, Launch the Network Topology: Run your network topology with vim-emu: sudo python network_topology.py This will start the network and deploy the VNFs. 6. Install OSM: Follow the instructions on the OSM GitHub repository ([Link] to install OSM, which includes installing the OSM client and server components. 7, Onboard the Network Service: Use the OSM client to onboard your network service. You'll need to provide a descriptor (e.g.,a TOSCA YAML file) for your service. ‘osm ns-create 8. Instantiate the Network Service: Instantiate the network service using OSM: ‘osm ns-instantiate Replace *~ with a suitable name for your instantiated service.OUTPUT: ‘When running the network topology script with vim-emu, you should see the network and VNFs being deployed. You can test connectivity and traffic between VNFs, After installing OSM and onboarding the network service descriptor, you should see your network service listed within OSM. ‘When instantiating the network service, OSM will orchestrate the deployment of the VNFs and connect them according to your descriptor. RESULT: ‘The result is a fully orchestrated end-to-end network service with two VNFS, established using vim-emu and OSM. The network service is now ready to accept and process traffic as specified in your descriptor.