VIrtual Local Area Network (VLAN)

Matt Carey
A free video tutorial from Matt Carey
Cisco CCNA Instructor - IPversity
4.4 instructor rating • 21 courses • 56,218 students

Learn more from the full course

Cisco Networking Fundamentals - CCNA Prep

Advance your Cisco networking knowledge and prepare for the CCNA exam

05:56:12 of on-demand video • Updated January 2019

  • Cisco Networking
  • Configure Cisco Routers and Switches
  • Knowledge to interview for a networking job
  • Deploy a LAN
  • Troubleshoot networking issues
  • Start a career in networking
English [Auto] In this section, we're going to learn how to configure villans on switches and the difference with support modes that will be used for violent assignments. OK, so let's start out with the basics. Let's say we wanted to assign host and host B here to volunteer. First, we'd have to go to these switch configurations and actually globally define VLAN two. So the first step when configuring villans on switches is to define the VLAN. If the VLAN is not defined on the switch, then the switch will not pass traffic for that VLAN. Once our villains are defined, then we have to configure our switch ports for that VLAN, so for user AI and user BS traffic to be assigned to VLAN to, we have to tell the switchboard to do so for this type of setup, since we just have analysts that do not understand villans and we're simply just trying to put their traffic on Vilan to we would use what's called an access mode, port access mode ports simply just assign any traffic coming from the connected device to the VLAN that you define in the configuration and any traffic egressing access mode port is considered to be untagged, meaning that it does not have any VLAN tag assignments because computers, any type of device that you would connect to an access mode port. We don't assume that it supports villans or understands Belan tag. So when the traffic sent back to the devices that are connected to access more ports, it has no vilan information. So now we've configured the ports that the analysts are connected to, but what about between the switches for this example, since we're only using one VLAN, we could actually configure the switch to switch connections the same way with access mode VLAN to configurations. And then we would have Villon to define throughout the switched path. So that configuration is fine for this example. But what if we had other villans connected to these switches? If any VLAN three traffic were to be sent out of these inter switch connections, the traffic would be dropped because we're only passing traffic for two in this access mode, inter switch configuration. So for this scenario, since we need to pass multiple villans across these ports, then we would use what's called a trunk mode port. So with a trunk mode port, the switches would actually use VLAN tags to assign to the traffic coming from the connected devices. So that switches across the LAN would know what VLAN to send the traffic out to. So let's take a look at how this configuration would flow if user A and user C or two san Ethernet frames to switch one. So here comes these are sees frame and user frame, and since they both entered their access model and parts, the switch would assign the corresponding VLAN to that traffic when their frames were going to be sent out of the switch. One port connected a switch to switch. One would add VLAN tags to those frames. Since the Riverland tags assigned to these frames now switched to nose, which villans to send the traffic to. And that's how we can have multiple villains traverse a switch port, let's look at a quick comparison of access mode and trunk mode ports access mode ports would have devices like computers, printers or cameras connected to them. Trunk mode ports would have devices like switches, VM hosts and autonomous or Fleck's connect access points connected to them. And just always remember that traffic leaving an access mode port is going to be untagged and traffic leaving a trunk mode port is going to be tagged.