Download Implementation of VLan in GNS3 and more Study Guides, Projects, Research Computer Networks in PDF only on Docsity!
PES UNIVERSITY
(Established under Karnataka Act No. 16 of 2013) 100-ft Ring Road, Bengaluru – 560 085, Karnataka, India
Project Based Learning- Computer Networks
Project Report On
Configuration of VLAN using GNS
Team Members:
Sharathkumar S (01FB16EEC258)
Shashidhar G H (01FB16EEC261)
Dinakar G (01FB16EEC354)
Naga Akhil E S (01FB17EEC711)
Under the guidance of
Prof. Kedar Ramachandra
Asst. prof, Dept of ECE
DEPARTMENT OF ELECTRONICS AND COMMUNICATION
ENGINEERING
PES UNIVERSITY, BANGALORE-
CONTENTS
1. Introduction
2. About GNS
3. Methodology (Algorithm, Flowchart)
4. Illustrations
5. Conclusions
6. References
Virtual Local Area Network (VLAN)
VLAN (Virtual Local Network) is a logically separate IP sub network which allows multiple IP networks and subnets to exist on the same-switched network.VLAN is a logical broadcast domain that can span multiple physical LAN segments. It is a modern way administrators configure switches into virtual local-area networks (VLANs) to improve network performance by separating large Layer 2 broadcast domains into smaller ones. By using VLAN, a network administrator will be able to group together stations by logical function, or by applications, without regard to physical location of the users. Each VLAN functions as a separate LAN and spans one or more switches. This allows host devices to behave as if they were on the same network segment. For traffic to move between VLANs, a layer 3 device (router) is required. VLAN has three major functions: i. Limits the size of broadcast domains ii. Improves network performance iii. Provides a level of security
There are different types of VLANs :
1. Default VLAN : At the initial boot up of the switch, All switch ports become a member of the default VLAN, which makes them all part of the same broadcast domain. This allows any network device connected to any of the switch port to communicate with other devices on other switch ports.On Cisco switches the default VLAN is VLAN 1. VLAN 1 has all the features of any VLAN, except that you cannot rename or delete it.
- Data VLAN : A data VLAN that can also be referred to as user VLAN. This is configured to carry only user-generated traffic. The importance of separating user data from other type of VLAN is
proper switch management and control.
- Native VLAN : A native VLAN is assigned to an 802.1Q trunk port. An 802.1Q trunk port supports traffic coming from many VLANs as well as traffic that do not come from a VLAN. The 802.1Q trunk port places untagged traffic (traffic that does not come from a VLAN) on the native VLAN. In summary, the native VLAN observes and identifies traffic coming from each end of a trunk link.
- Management VLAN : A management VLAN is any VLAN you configure to access the management capabilities of a switch. Your configured management VLAN is to be assign with an IP address and subnet mask. Any of a switch VLAN could be configured as the management VLAN if you has not configured or define a unique VLAN to serve as the management VLAN. In some cases, a network administrator proactively defines VLAN 1 as the management VLAN; this enables a loophole for an unauthorized connection to a switch.
- Voice Vlan : Voice VLAN is configured to carry voice traffic. Voice VLANs are mostly given transmission priority over other types of network traffic. Communication over the network is not complete without phone calls. More calls are made over the network than other forms of s message transmission. Sending emails and text messages are also forms of inter-relations but listening to a real voice provides legitimacy and assurance.
Advantages of VLAN :
Security: Security isn't itself achieved by creating a VLAN; however, how you connect that VLAN to other subnets could allow you to filter/block access to that subnet. For instance if you have an office building that has 50 computers and 5 servers you could create a VLAN for the server and a VLAN for the computers. For computers to communicate with the servers you could use a firewall to route and filter that traffic. This would then allow you to apply IPS/IDS,ACLs,Etc. to the connection between the servers and computers.
Link Utilization: (Edit)I can't believe I left this out the first time. Brain fart I guess. Link utilization is another big reason to use VLANs. Spanning tree by function builds a single path through your layer 2 network to prevent loops (Oh, my!). If you have multiple redundant links to your aggregating devices then some of these links will go unused. To get around this you can build multiple STP topology with different VLANs. This is accomplished with Cisco Proprietary PVST, RPVST, or standards based MST. This allows you to have multiple STP typologies you can play with to utilize your previously unused links. In example if I had 50 desktops I could place 25 of them in VLAN 10, and 25 of them in VLAN
- I could then have VLAN 10 take the "left" side of the network and the remaining 25 in VLAN 20 would take the "right" side of the network.
About GNS3 software
Graphical Network Simulator 3(shortened to GNS3) is a network software emulator first released in
- It allows the combination of virtual and real devices, used to simulate complex networks. It uses Dynamips emulation software to simulate Cisco IOS. GNS3 has allowed network engineers to virtualize real hardware devices for over 10 years. Originally only emulating Cisco devices using software called Dynamips, GNS3 has now evolved and supports many devices from multiple network vendors including Cisco virtual switches, Cisco ASAs, Brocade vRouters, Cumulus Linux switches, Docker instances, HPE VSRs, multiple Linux appliances and many others. GNS3 is probably most famous as a platform used for learning and teaching. GNS3 has for years been used by students and network engineers to help practice and prepare for vendor certification exams such as the Cisco CCNA exam. GNS3 provides an easy, cost effective way to new software such as management or SDN software. It allows you to test multi vendor interoperability using a virtual lab environment rather than requiring dedicated physical equipment. An entire GNS3 topology can be created and run on a single laptop. This allows engineers to demonstrate topologies and software to clients and others on the road. Classroom environments can also benefit from a preconfigured lab environment that students use to learn networking concepts and technologies.
GNS3 consists of two software components:
- The GNS3-all-in-one software (GUI)
- The GNS3 virtual machine (VM)
Advantages of GNS3:
Free software Open Source software No monthly or yearly license fees No limitation on number of devices supported (only limitation is your hardware: CPU and memory) Supports multiple switching options (ESW16 Etherswitch, IOU/IOL Layer 2 images, VIRL IOSvL2) Supports all VIRL images (IOSv, IOSvL2, IOS-XRv, CSR1000v, NX-OSv, ASAv) Supports multi vendor environments Can be run with or without hypervisors Supports both free and paid hypervisors (Virtualbox , VMware workstation, VMware player, ESXi, Fusion) Downloadable, free, pre-configured and optimized appliances available to simplify deployment
Native support for Linux without the need for need for additional virtualization software Software from multiple vendors freely available Large and active community (800,000+ members)
Disadvantages of GNS3:
Cisco images need to be supplied by user (download from Cisco.com, or purchase VIRL license, or copy from physical device).Not a self contained package, but requires a local installation of software (GUI)
Algorithm :
Installing GNS3 software and required CISCO routers(eg:C3600,C7200 etc.) Configuring the switches and routers i.e defining the slots(eg:NM-1FE-TX, NM-16ESW etc.) Interfacing client PCs and server using fastethernets as shown in the diagram below
The configuration of devices used are done on Solar-PuTTY tool Assigning IP addresses to VPCS Adding the different VLANs to the VLAN database and trunk the connections to SW1 and SW while configuring router R Configuring SW1 and SW2 so that hosts (VPCS) are assigned to particular VLANs Start pinging from the hosts to check the working of VLAN.The hosts which belong to same VLAN gets pinged and other don’t (i.e hosts in VLAN 2 and VLAN 3 wont ping unless Inter-VLAN routing!!)
Use wireshark to capture the packets
A
Hosts belong to Same VLAN
Stop
ILLUSTRATIONS
1. Installing the required CISCO Routers.
2.Interfacing the client and Server nodes using fastethernet links
- PC3 IP address:192.168.1.
- PC4 IP Address:192.168.2.
4.Adding VLANs to VLAN database:
5.Configuring Client nodes :
SW1:
From PC2:
From PC3:
From PC4:
7.Capturing packets using Wireshark between PC1 and PC3:
