SlideShare a Scribd company logo

VLAN ON PACKET TRACER

BIRLA VISHVAKARMA MAHAVIDYALAY, profile picture
BIRLA VISHVAKARMA MAHAVIDYALAY

This document describes configuring VLANs on switches in a mesh network topology using Cisco Packet Tracer. VLANs are configured to separate devices into two VLANs ("Even" and "Odd") based on whether the last digit of their IP addresses is even or odd. The configuration involves creating the VLANs on each switch and assigning access ports to the appropriate VLAN based on the connected device's IP. Trunk ports are also configured between the switches to allow traffic from both VLANs to pass through the mesh network.

Engineering
1 of 20
Downloaded 19 times
1
2
3
4
5
Most read
6
Most read
7
8
9
10
11
12
13
14
Most read
15
16
17
18
19
20
Affiliated with GTU A Open-Ended Problem Report on VLAN on packet tracer (Mesh topology) Prepared as a part of the requirements for the subject of Data Communication and Networking (2171008) BE IV, Semester VII (ELECTRONICS AND TELECOMMUNICATION) Submitted by: - 1. Prasiddh Makadiya 130080112029 2. Apar Trivedi 130080112057 3. Vatsal Bodiwala 140083112002 PROF. Anish Vahora (Faculty Guide) PROF. MEHUL B SHAH (Head of the Department) Academic year (2016-2017) GUJARAT TECHNOLOGICALUNIVERSITY BIRLA VISHWAKARMA MAHAVIDYALAYA
Virtual Local Area Networks (VLAN):- In a traditional LAN, workstations are connected to each other by means of a hub or a repeater. These devices propagate any incoming data throughout the network. However, if two people attempt to send information at the same time, a collision will occur and all the transmitted data will be lost. Once the collision has occurred, it will continue to be propagated throughout the network by hubs and repeaters. The original information will therefore need to be resent after waiting for the collision to be resolved, thereby incurring a significant wastage of time and resources. To prevent collisions from traveling through all the workstations in the network, a bridge or a switch can be used. These devices will not forward collisions, but will allow broadcasts (to every user in the network) and multicasts (to a pre-specified group of users) to pass through. A router may be used to prevent broadcasts and multicasts from traveling through the network. The workstations, hubs, and repeaters together form a LAN segment. A LAN segment is also known as a collision domain since collisions remain within the segment. The area within which broadcasts and multicasts are confined is called a broadcast domain or LAN. Thus a LAN can consist of one or more LAN segments. Defining broadcast and collision domains in a LAN depends on how the workstations, hubs, switches, and routers are physically connected together. This means that everyone on a LAN must be located in the same area (see Figure1). Figure 1: Physical view of a LAN VLAN's allow a network manager to logically segment a LAN into different broadcast domains (see Figure2). Since this is a logical segmentation and not a physical one, workstations do not
have to be physically located together. Users on different floors of the same building, or even in different buildings can now belong to the same LAN. Physical View Logical View Figure 2: Physical and logical view of a VLAN. VLAN's also allow broadcast domains to be defined without using routers. Bridging software is used instead to define which workstations are to be included in the broadcast domain. Routers would only have to be used to communicate between two VLAN's.
Mesh topology A network setup where each computer and network device is interconnected with one another, allowing for most transmissions to be distributed, even if one of the connections go down. This topology is not commonly used for most computer networks as it is difficult and expensive to have redundant connection to every computer. However, this topology is commonly used for wireless networks. Below is a visual example of a simple computer setup on a network using a mesh topology. A mesh topology can be a full mesh topology or a partially connected mesh topology. In a full mesh topology, every computer in the network has a connection to each of the other computers in that network. The number of connections in this network can be calculated using the following formula (n is the number of computers in the network): n(n-1)/2 In a partially connected mesh topology, at least two of the computers in the network have connections to multiple other computers in that network. This is a cheaper way to build a network that has some redundancy in the event one of the primary computers or connections in the network were to be down. Description:- In this Open-Ended Problem we have design VLAN on Cicso packet Tracer. Switch0, Switch1, Switch2, Switch3 and Switch4 are connected in mesh topology. Three PCs are connected with every switch 0-4. In this problem VLAN is design on based on its IP address. If last pair in dotted decimal formal IP address is odd then it is in VLAN 3 named ‘Odd’. If last pair in dotted decimal formal IP address is even then it is in VLAN 2 named ‘Even’.
VLAN 2 (Even) VLAN 3 (Odd) 192.168.0.2 192.168.0.1 192.168.0.4 192.168.0.3 192.168.0.6 192.168.0.5 192.168.0.8 192.168.0.7 192.168.0.10 192.168.0.9 192.168.0.12 192.168.0.11 192.168.0.14 192.168.0.13 192.168.0.15 Switch0 Switch1 Switch2 Switch3 Switch4 192.168.0.1 192.168.0.4 192.168.0.7 192.168.0.10 192.168.0.13 192.168.0.2 192.168.0.5 192.168.0.8 192.168.0.11 192.168.0.14 192.168.0.3 192.168.0.6 192.168.0.9 192.168.0.12 192.168.0.15 VLAN on packet tracer (Mesh topology)
Command in switch0 Command Line Interface (CLI) :- Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#exit Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#exit Switch(config)#interface fa0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#interface fa0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#interface fa0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#end Switch# Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Command in switch1 Command Line Interface (CLI) :- Switch> Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#exit Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#exit Switch(config)#interface fa 0/1
Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#end Switch# %SYS-5-CONFIG_I: Configured from console by console Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Command in switch2 Command Line Interface (CLI) Switch>en Switch# Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#end Switch# %SYS-5-CONFIG_I: Configured from console by console Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# Switch(config)# Switch(config)# Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#
Switch(config)# Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)# Switch(config-if)#e Switch(config)# Switch(config)# Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
Command in switch3 Command Line Interface (CLI) Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)# Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up Switch(config-if)#e Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk
Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Switch(config-if)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Switch(config-if)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/7 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up Command in switch4 Command Line Interface (CLI) Switch> Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3
Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Switch(config-if)#e Switch(config)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Switch(config-if)#e Switch(config)# Switch(config)#interface fa 0/7
Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up OUTPUT :- Packet Tracer PC Command Line 1.0 PC>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=1ms TTL=128 Reply from 192.168.0.1: bytes=32 time=0ms TTL=128 Reply from 192.168.0.1: bytes=32 time=20ms TTL=128 Reply from 192.168.0.1: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 20ms, Average = 5ms PC>ping 192.168.0.2 Pinging 192.168.0.2 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 192.168.0.2: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.3 Pinging 192.168.0.3 with 32 bytes of data: Reply from 192.168.0.3: bytes=32 time=11ms TTL=128 Reply from 192.168.0.3: bytes=32 time=0ms TTL=128 Reply from 192.168.0.3: bytes=32 time=1ms TTL=128 Reply from 192.168.0.3: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms PC>ping 192.168.0.4 Pinging 192.168.0.4 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.4: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.5
Pinging 192.168.0.5 with 32 bytes of data: Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.5: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PC>ping 192.168.0.6 Pinging 192.168.0.6 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.6: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.7 Pinging 192.168.0.7 with 32 bytes of data: Reply from 192.168.0.7: bytes=32 time=11ms TTL=128 Reply from 192.168.0.7: bytes=32 time=1ms TTL=128
Reply from 192.168.0.7: bytes=32 time=0ms TTL=128 Reply from 192.168.0.7: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms PC>ping 192.168.0.8 Pinging 192.168.0.8 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.8: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.9 Pinging 192.168.0.9 with 32 bytes of data: Reply from 192.168.0.9: bytes=32 time=1ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.9: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PC>ping 192.168.0.10 Pinging 192.168.0.10 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.11 Pinging 192.168.0.11 with 32 bytes of data: Reply from 192.168.0.11: bytes=32 time=11ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.11: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 2ms PC>ping 192.168.0.12
Pinging 192.168.0.12 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.12: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.13 Pinging 192.168.0.13 with 32 bytes of data: Reply from 192.168.0.13: bytes=32 time=2ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.13: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 2ms, Average = 0ms PC>ping 192.168.0.14 Pinging 192.168.0.14 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.14: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
CONCLUSION: Thus, we have designed Virtual LAN and it’s connection.

More Related Content

PPT
CCNA Basic Switching and Switch Configuration
Dsunte Wilson
 
PPTX
Routing protocols
Sourabh Goyal
 
PPTX
Ppt of routing protocols
Bhagyashri Dhoke
 
PPTX
Dynamic routing protocols (CCNA)
Varinder Singh Walia
 
PPT
OSI Layers
Kishore Kumar
 
PPTX
Layer 2 switching
NetProtocol Xpert
 
PPTX
Subnetting Presentation
Touhidul Fahim
 
PPTX
Comparison between-ipv6-and-6 lowpan
Information Technology University
 
CCNA Basic Switching and Switch Configuration
Dsunte Wilson
 
Routing protocols
Sourabh Goyal
 
Ppt of routing protocols
Bhagyashri Dhoke
 
Dynamic routing protocols (CCNA)
Varinder Singh Walia
 
OSI Layers
Kishore Kumar
 
Layer 2 switching
NetProtocol Xpert
 
Subnetting Presentation
Touhidul Fahim
 
Comparison between-ipv6-and-6 lowpan
Information Technology University
 

What's hot (20)

PPTX
Routing Protocols
NetProtocol Xpert
 
PPT
IP Addressing
Kishore Kumar
 
PPTX
CCNA training 101
Rohan Reddy
 
DOCX
Layer 2 & layer 3 switching
Muhd Mu'izuddin
 
PPTX
OSPF Basics
Martin Bratina
 
PPT
CCNA Advanced Routing Protocols
Dsunte Wilson
 
PPTX
VLAN
Varsha Honde
 
PPT
Subnetting
Gichelle Amon
 
PPSX
Subnetting
selvakumar_b1985
 
PPTX
Switching Concepts presentation
zameer Abbas
 
PDF
Communication protocol presentation
Gopi A
 
PPTX
Subnetting made simple
Wamuyu Murakaru
 
PPT
Vlan
Mayank Saxena
 
PDF
6LoWPAN
Pradeep Kumar TS
 
PPTX
Network Layer
reshmadayma
 
PDF
Cisco Live! :: Introduction to Segment Routing :: BRKRST-2124 | Las Vegas 2017
Bruno Teixeira
 
PPTX
BASICS OF ROUTING IN NETWORKS
KABILESH RAMAR
 
PPT
IP Addressing and subnetting
Ali Nezhad
 
PPTX
Multiple Access Protocal
tes31
 
PPT
Ip address and subnetting
IGZ Software house
 
Routing Protocols
NetProtocol Xpert
 
IP Addressing
Kishore Kumar
 
CCNA training 101
Rohan Reddy
 
Layer 2 & layer 3 switching
Muhd Mu'izuddin
 
OSPF Basics
Martin Bratina
 
CCNA Advanced Routing Protocols
Dsunte Wilson
 
VLAN
Varsha Honde
 
Subnetting
Gichelle Amon
 
Subnetting
selvakumar_b1985
 
Switching Concepts presentation
zameer Abbas
 
Communication protocol presentation
Gopi A
 
Subnetting made simple
Wamuyu Murakaru
 
Vlan
Mayank Saxena
 
6LoWPAN
Pradeep Kumar TS
 
Network Layer
reshmadayma
 
Cisco Live! :: Introduction to Segment Routing :: BRKRST-2124 | Las Vegas 2017
Bruno Teixeira
 
BASICS OF ROUTING IN NETWORKS
KABILESH RAMAR
 
IP Addressing and subnetting
Ali Nezhad
 
Multiple Access Protocal
tes31
 
Ip address and subnetting
IGZ Software house
 
Ad

Viewers also liked (20)

PDF
Energy Lines
JACK L. BRAY M.A., CPG, CT
 
DOCX
production diary
A_Melodie
 
PDF
Elizabeth tang hkctu disclourse of lobbying activities
Mongkok anonym
 
PDF
Evolving Approaches to Measuring the Value of New Health Technologies in the US
Office of Health Economics
 
PDF
Redes Sociales aplicadas al pequeño comercio
Dani Ortega
 
PDF
Relationship of body mass index, fat and visceral fat among adolescents
Sports Journal
 
PPTX
Bob's discount furniture and the american red cross to launch scholarship pro...
Bob Smith
 
PPTX
the internet and world wide web
Pros Gayo
 
DOCX
2016 práctica calameo william
william alejandro castiblanco monroy
 
DOCX
Joseph Gigliotti - Resume (Linked-In)
Joseph Gigliotti
 
DOCX
Santa bárbara información del micrositio
marimba de chonta
 
PDF
Mejorador de flujo cacalilao mextra
Irving1601
 
PDF
Req 381
Rogerio Catanese
 
PPS
هل هناك مايزعجك؟؟!!
moath Al-Baltan
 
PDF
Plan de centro 2013 2014
javiermartinmartin
 
PPT
Uses of Different Shot Types
mrstardom
 
PDF
SSI Certificate
D K Associates
 
PPT
Characteristics of life
MRDM3
 
PPTX
Cómo consultar la bibliografía recomendada en el catálogo Trobes
Servei de Biblioteques i Documentacio. Universitat de Valencia
 
PPTX
Trabajo final curso redes sociales
Hugo Princich
 
Energy Lines
JACK L. BRAY M.A., CPG, CT
 
production diary
A_Melodie
 
Elizabeth tang hkctu disclourse of lobbying activities
Mongkok anonym
 
Evolving Approaches to Measuring the Value of New Health Technologies in the US
Office of Health Economics
 
Redes Sociales aplicadas al pequeño comercio
Dani Ortega
 
Relationship of body mass index, fat and visceral fat among adolescents
Sports Journal
 
Bob's discount furniture and the american red cross to launch scholarship pro...
Bob Smith
 
the internet and world wide web
Pros Gayo
 
2016 práctica calameo william
william alejandro castiblanco monroy
 
Joseph Gigliotti - Resume (Linked-In)
Joseph Gigliotti
 
Santa bárbara información del micrositio
marimba de chonta
 
Mejorador de flujo cacalilao mextra
Irving1601
 
Req 381
Rogerio Catanese
 
هل هناك مايزعجك؟؟!!
moath Al-Baltan
 
Plan de centro 2013 2014
javiermartinmartin
 
Uses of Different Shot Types
mrstardom
 
SSI Certificate
D K Associates
 
Characteristics of life
MRDM3
 
Cómo consultar la bibliografía recomendada en el catálogo Trobes
Servei de Biblioteques i Documentacio. Universitat de Valencia
 
Trabajo final curso redes sociales
Hugo Princich
 
Ad

Similar to VLAN ON PACKET TRACER (20)

PPT
Layer2-vlans
soumyaranjan1223
 
PPTX
Presentation
Ismail Miah
 
PPTX
Presentation
Ismail Miah
 
PPT
layer2-network-design.ppt
Patrick Theuri
 
PDF
VLAN
Anuj Kumar
 
PPTX
Vla ns
UDLA
 
PPT
layer2-network-design.ppt
VimalMallick
 
PPT
mod8-VLANs.ppt
SAROORNAGARCMCORE
 
PPTX
VLAN (Virtual Local Area Network) Full details.pptx
Vignesh kumar
 
PPT
Vlan configuration in medium sized network
Arnold Derrick Kinney
 
PPT
Vlan
sanss40
 
PPTX
Presentation on ccna
Rahul Kumar
 
PPTX
Presentation on ccna
Rahul Kumar
 
PDF
Networking
Tarun Jaiswal
 
PPT
Mod8 vlans
Mohan Kumaresan
 
PDF
Vlan.pdf
itwkd
 
PPT
VLAN Virtual Area Network ,Switch,Ethernet ,VIkram Snehi
MR. VIKRAM SNEHI
 
PPT
CCNA- part 9 vlan
Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
 
PPT
Chapter 1 Switch Network Device (1).ppt
desalewminale
 
PDF
Uccn1003 -may10_-_lect03a_-_lan_design_issues
Shu Shin
 
Layer2-vlans
soumyaranjan1223
 
Presentation
Ismail Miah
 
Presentation
Ismail Miah
 
layer2-network-design.ppt
Patrick Theuri
 
VLAN
Anuj Kumar
 
Vla ns
UDLA
 
layer2-network-design.ppt
VimalMallick
 
mod8-VLANs.ppt
SAROORNAGARCMCORE
 
VLAN (Virtual Local Area Network) Full details.pptx
Vignesh kumar
 
Vlan configuration in medium sized network
Arnold Derrick Kinney
 
Vlan
sanss40
 
Presentation on ccna
Rahul Kumar
 
Presentation on ccna
Rahul Kumar
 
Networking
Tarun Jaiswal
 
Mod8 vlans
Mohan Kumaresan
 
Vlan.pdf
itwkd
 
VLAN Virtual Area Network ,Switch,Ethernet ,VIkram Snehi
MR. VIKRAM SNEHI
 
CCNA- part 9 vlan
Sandeep Sharma IIMK Smart City,IoT,Bigdata,Cloud,BI,DW
 
Chapter 1 Switch Network Device (1).ppt
desalewminale
 
Uccn1003 -may10_-_lect03a_-_lan_design_issues
Shu Shin
 

More from BIRLA VISHVAKARMA MAHAVIDYALAY (14)

PDF
VLAN ON PACKET TRACER
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PDF
VLAN on packet Tracer
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Stepper motor interfacing
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPT
E.com
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PDF
Fhss project
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Group 11
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Me presentation
BIRLA VISHVAKARMA MAHAVIDYALAY
 
DOCX
Gujarat technological universit1
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Arithmetic and logical instructions
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Cse presentation
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Group no 11
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPTX
Avs presentation
BIRLA VISHVAKARMA MAHAVIDYALAY
 
DOCX
Automatic room light controller with bidirectional visitor counter
BIRLA VISHVAKARMA MAHAVIDYALAY
 
PPT
Automaticroomlightcontroller[1]
BIRLA VISHVAKARMA MAHAVIDYALAY
 
VLAN ON PACKET TRACER
BIRLA VISHVAKARMA MAHAVIDYALAY
 
VLAN on packet Tracer
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Stepper motor interfacing
BIRLA VISHVAKARMA MAHAVIDYALAY
 
E.com
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Fhss project
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Group 11
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Me presentation
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Gujarat technological universit1
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Arithmetic and logical instructions
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Cse presentation
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Group no 11
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Avs presentation
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Automatic room light controller with bidirectional visitor counter
BIRLA VISHVAKARMA MAHAVIDYALAY
 
Automaticroomlightcontroller[1]
BIRLA VISHVAKARMA MAHAVIDYALAY
 

Recently uploaded (20)

PDF
composite construction of structures.pdf
AinieButt1
 
PPTX
MET 305 2019 SCHEME MODULE 2 COMPLETE.pptx
VinayB68
 
PPTX
Foundation to blockchain - A guide to Blockchain Tech
Davies Chacko
 
PPTX
KTU 2019 -S7-MCN 401 MODULE 2-VINAY.pptx
VinayB68
 
PDF
Arduino robotics embedded978-1-4302-3184-4.pdf
AbdullahEmam4
 
PPTX
bas. eng. economics group 4 presentation 1.pptx
kiribakimoses1993
 
PDF
Evaluating the Democratization of the Turkish Armed Forces from a Normative P...
jpsjournal1
 
PPT
Project quality management in manufacturing
BarMusaTetik
 
PPTX
Strings in CPP - Strings in C++ are sequences of characters used to store and...
sangeethamtech26
 
DOCX
ASol_English-Language-Literature-Set-1-27-02-2023-converted.docx
AYUSHMANAV
 
PPTX
UNIT-1 - COAL BASED THERMAL POWER PLANTS
Chandra Kumar S
 
PPTX
Recipes for Real Time Voice AI WebRTC, SLMs and Open Source Software.pptx
Alberto González Trastoy
 
PPTX
UNIT 4 Total Quality Management .pptx
gokuld13012005
 
PDF
Structs to JSON How Go Powers REST APIs.pdf
Emily Achieng
 
PDF
SM_6th-Sem__Cse_Internet-of-Things.pdf IOT
smceramu
 
PDF
PPT on Performance Review to get promotions
prashant593122
 
PPTX
CARTOGRAPHY AND GEOINFORMATION VISUALIZATION chapter1 NPTE (2).pptx
abhi1361yadav
 
PDF
July 2025 - Top 10 Read Articles in International Journal of Software Enginee...
sebastianku31
 
PPTX
Lesson 3_Tessellation.pptx finite Mathematics
quakeplayz54
 
PDF
Operating System & Kernel Study Guide-1 - converted.pdf
mranoninvisib16
 
composite construction of structures.pdf
AinieButt1
 
MET 305 2019 SCHEME MODULE 2 COMPLETE.pptx
VinayB68
 
Foundation to blockchain - A guide to Blockchain Tech
Davies Chacko
 
KTU 2019 -S7-MCN 401 MODULE 2-VINAY.pptx
VinayB68
 
Arduino robotics embedded978-1-4302-3184-4.pdf
AbdullahEmam4
 
bas. eng. economics group 4 presentation 1.pptx
kiribakimoses1993
 
Evaluating the Democratization of the Turkish Armed Forces from a Normative P...
jpsjournal1
 
Project quality management in manufacturing
BarMusaTetik
 
Strings in CPP - Strings in C++ are sequences of characters used to store and...
sangeethamtech26
 
ASol_English-Language-Literature-Set-1-27-02-2023-converted.docx
AYUSHMANAV
 
UNIT-1 - COAL BASED THERMAL POWER PLANTS
Chandra Kumar S
 
Recipes for Real Time Voice AI WebRTC, SLMs and Open Source Software.pptx
Alberto González Trastoy
 
UNIT 4 Total Quality Management .pptx
gokuld13012005
 
Structs to JSON How Go Powers REST APIs.pdf
Emily Achieng
 
SM_6th-Sem__Cse_Internet-of-Things.pdf IOT
smceramu
 
PPT on Performance Review to get promotions
prashant593122
 
CARTOGRAPHY AND GEOINFORMATION VISUALIZATION chapter1 NPTE (2).pptx
abhi1361yadav
 
July 2025 - Top 10 Read Articles in International Journal of Software Enginee...
sebastianku31
 
Lesson 3_Tessellation.pptx finite Mathematics
quakeplayz54
 
Operating System & Kernel Study Guide-1 - converted.pdf
mranoninvisib16
 

VLAN ON PACKET TRACER

  • 1. Affiliated with GTU A Open-Ended Problem Report on VLAN on packet tracer (Mesh topology) Prepared as a part of the requirements for the subject of Data Communication and Networking (2171008) BE IV, Semester VII (ELECTRONICS AND TELECOMMUNICATION) Submitted by: - 1. Prasiddh Makadiya 130080112029 2. Apar Trivedi 130080112057 3. Vatsal Bodiwala 140083112002 PROF. Anish Vahora (Faculty Guide) PROF. MEHUL B SHAH (Head of the Department) Academic year (2016-2017) GUJARAT TECHNOLOGICALUNIVERSITY BIRLA VISHWAKARMA MAHAVIDYALAYA
  • 2. Virtual Local Area Networks (VLAN):- In a traditional LAN, workstations are connected to each other by means of a hub or a repeater. These devices propagate any incoming data throughout the network. However, if two people attempt to send information at the same time, a collision will occur and all the transmitted data will be lost. Once the collision has occurred, it will continue to be propagated throughout the network by hubs and repeaters. The original information will therefore need to be resent after waiting for the collision to be resolved, thereby incurring a significant wastage of time and resources. To prevent collisions from traveling through all the workstations in the network, a bridge or a switch can be used. These devices will not forward collisions, but will allow broadcasts (to every user in the network) and multicasts (to a pre-specified group of users) to pass through. A router may be used to prevent broadcasts and multicasts from traveling through the network. The workstations, hubs, and repeaters together form a LAN segment. A LAN segment is also known as a collision domain since collisions remain within the segment. The area within which broadcasts and multicasts are confined is called a broadcast domain or LAN. Thus a LAN can consist of one or more LAN segments. Defining broadcast and collision domains in a LAN depends on how the workstations, hubs, switches, and routers are physically connected together. This means that everyone on a LAN must be located in the same area (see Figure1). Figure 1: Physical view of a LAN VLAN's allow a network manager to logically segment a LAN into different broadcast domains (see Figure2). Since this is a logical segmentation and not a physical one, workstations do not
  • 3. have to be physically located together. Users on different floors of the same building, or even in different buildings can now belong to the same LAN. Physical View Logical View Figure 2: Physical and logical view of a VLAN. VLAN's also allow broadcast domains to be defined without using routers. Bridging software is used instead to define which workstations are to be included in the broadcast domain. Routers would only have to be used to communicate between two VLAN's.
  • 4. Mesh topology A network setup where each computer and network device is interconnected with one another, allowing for most transmissions to be distributed, even if one of the connections go down. This topology is not commonly used for most computer networks as it is difficult and expensive to have redundant connection to every computer. However, this topology is commonly used for wireless networks. Below is a visual example of a simple computer setup on a network using a mesh topology. A mesh topology can be a full mesh topology or a partially connected mesh topology. In a full mesh topology, every computer in the network has a connection to each of the other computers in that network. The number of connections in this network can be calculated using the following formula (n is the number of computers in the network): n(n-1)/2 In a partially connected mesh topology, at least two of the computers in the network have connections to multiple other computers in that network. This is a cheaper way to build a network that has some redundancy in the event one of the primary computers or connections in the network were to be down. Description:- In this Open-Ended Problem we have design VLAN on Cicso packet Tracer. Switch0, Switch1, Switch2, Switch3 and Switch4 are connected in mesh topology. Three PCs are connected with every switch 0-4. In this problem VLAN is design on based on its IP address. If last pair in dotted decimal formal IP address is odd then it is in VLAN 3 named ‘Odd’. If last pair in dotted decimal formal IP address is even then it is in VLAN 2 named ‘Even’.
  • 5. VLAN 2 (Even) VLAN 3 (Odd) 192.168.0.2 192.168.0.1 192.168.0.4 192.168.0.3 192.168.0.6 192.168.0.5 192.168.0.8 192.168.0.7 192.168.0.10 192.168.0.9 192.168.0.12 192.168.0.11 192.168.0.14 192.168.0.13 192.168.0.15 Switch0 Switch1 Switch2 Switch3 Switch4 192.168.0.1 192.168.0.4 192.168.0.7 192.168.0.10 192.168.0.13 192.168.0.2 192.168.0.5 192.168.0.8 192.168.0.11 192.168.0.14 192.168.0.3 192.168.0.6 192.168.0.9 192.168.0.12 192.168.0.15 VLAN on packet tracer (Mesh topology)
  • 6. Command in switch0 Command Line Interface (CLI) :- Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#exit Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#exit Switch(config)#interface fa0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#interface fa0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#interface fa0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#end Switch# Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up
  • 7. Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Command in switch1 Command Line Interface (CLI) :- Switch> Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#exit Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#exit Switch(config)#interface fa 0/1
  • 8. Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#exit Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#exit Switch(config)#end Switch# %SYS-5-CONFIG_I: Configured from console by console Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
  • 9. %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Command in switch2 Command Line Interface (CLI) Switch>en Switch# Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#end Switch# %SYS-5-CONFIG_I: Configured from console by console Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# Switch(config)# Switch(config)# Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#
  • 10. Switch(config)# Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)# Switch(config-if)#e Switch(config)# Switch(config)# Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up
  • 11. Command in switch3 Command Line Interface (CLI) Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3 Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)# Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/4, changed state to up Switch(config-if)#e Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk
  • 12. Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Switch(config-if)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Switch(config-if)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/7 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up Command in switch4 Command Line Interface (CLI) Switch> Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#vlan 2 Switch(config-vlan)#name even Switch(config-vlan)#e Switch(config)#vlan 3
  • 13. Switch(config-vlan)#name odd Switch(config-vlan)#e Switch(config)#interface fa 0/1 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/2 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 2 Switch(config-if)#e Switch(config)#interface fa 0/3 Switch(config-if)#switchport mode access Switch(config-if)#switchport access vlan 3 Switch(config-if)#e Switch(config)#interface fa 0/4 Switch(config-if)#switchport mode trunk Switch(config-if)#e Switch(config)#interface fa 0/5 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Switch(config-if)#e Switch(config)#interface fa 0/6 Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed state to up Switch(config-if)#e Switch(config)# Switch(config)#interface fa 0/7
  • 14. Switch(config-if)#switchport mode trunk Switch(config-if)# %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed state to up OUTPUT :- Packet Tracer PC Command Line 1.0 PC>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=1ms TTL=128 Reply from 192.168.0.1: bytes=32 time=0ms TTL=128 Reply from 192.168.0.1: bytes=32 time=20ms TTL=128 Reply from 192.168.0.1: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 20ms, Average = 5ms PC>ping 192.168.0.2 Pinging 192.168.0.2 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
  • 15. Ping statistics for 192.168.0.2: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.3 Pinging 192.168.0.3 with 32 bytes of data: Reply from 192.168.0.3: bytes=32 time=11ms TTL=128 Reply from 192.168.0.3: bytes=32 time=0ms TTL=128 Reply from 192.168.0.3: bytes=32 time=1ms TTL=128 Reply from 192.168.0.3: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms PC>ping 192.168.0.4 Pinging 192.168.0.4 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.4: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.5
  • 16. Pinging 192.168.0.5 with 32 bytes of data: Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=1ms TTL=128 Reply from 192.168.0.5: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.5: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PC>ping 192.168.0.6 Pinging 192.168.0.6 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.6: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.7 Pinging 192.168.0.7 with 32 bytes of data: Reply from 192.168.0.7: bytes=32 time=11ms TTL=128 Reply from 192.168.0.7: bytes=32 time=1ms TTL=128
  • 17. Reply from 192.168.0.7: bytes=32 time=0ms TTL=128 Reply from 192.168.0.7: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 3ms PC>ping 192.168.0.8 Pinging 192.168.0.8 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.8: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.9 Pinging 192.168.0.9 with 32 bytes of data: Reply from 192.168.0.9: bytes=32 time=1ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Reply from 192.168.0.9: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.9: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  • 18. Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms PC>ping 192.168.0.10 Pinging 192.168.0.10 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.11 Pinging 192.168.0.11 with 32 bytes of data: Reply from 192.168.0.11: bytes=32 time=11ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Reply from 192.168.0.11: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.11: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 11ms, Average = 2ms PC>ping 192.168.0.12
  • 19. Pinging 192.168.0.12 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.12: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), PC>ping 192.168.0.13 Pinging 192.168.0.13 with 32 bytes of data: Reply from 192.168.0.13: bytes=32 time=2ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Reply from 192.168.0.13: bytes=32 time=0ms TTL=128 Ping statistics for 192.168.0.13: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 2ms, Average = 0ms PC>ping 192.168.0.14 Pinging 192.168.0.14 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.0.14: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
  • 20. CONCLUSION: Thus, we have designed Virtual LAN and it’s connection.