CCNA Notes

200-301 Exam Prep

Progress0/67

0% complete

Practice TestsNew
1Networking Devices2Interfaces And Cables3OSI Model and TCP/IP Suite4Intro to the CLI5Ethernet LAN Switching - Part 16Ethernet LAN Switching - Part 27IPv4 Addressing - Part 18IPv4 Addressing - Part 29Switch Interfaces10The IPv4 Header11Routing Fundamentals - Part 111Static Routing - Part 212Life of a Packet13Subnetting - Part 114Subnetting - Part 215Subnetting (VLSM) - Part 316VLANs - Part 117VLANs - Part 218VLANs - Part 319DTP / VTP20Spanning Tree Protocol - Part 121Spanning Tree Protocol - Part 222Rapid Spanning Tree Protocol23Etherchannel24Dynamic Routing25RIP / EIGRP26OSPF - Part 127OSPF - Part 228OSPF - Part 329First Hop Redundancy Protocol30TCP and UDP31IPv6 - Part 132IPv6 - Part 233IPv6 - Part 334Standard Access Control List35Extended Access Control List36CDP and LLDP37NTP - Network Time Protocol38DNS - Domain Name System39DHCP - Dynamic Host Configuration Protocol40SNMP - Simple Network Management Protocol41SYSLOG42SSH - Secure Shell43FTP and TFTP44NAT (Static) - Part 145NAT (Dynamic) - Part 246QoS (Voice VLAN) - Part 147QoS (Quality of Service) - Part 248Security Fundamentals49Port Security50DHCP Snooping51Dynamic ARP Inspection52LAN Architectures53WAN Architectures54Virtualization and Cloud - Part 154Virtualization (Containers) - Part 254Virtualization (VRF) - Part 355Wireless Fundamentals56Wireless Architectures57Wireless Security58Wireless Configuration59Introduction to Network Automation60JSON, XML, and YAML61REST APIs62Software Defined Networking63Ansible, Puppet, and Chef67CCNA Complete Cheatsheet
/VLANs - Part 2
Topic 175 min read

VLANs - Part 2

/
Tip: Select text to highlight or pin your reading position

17. VLANS : PART 2

Basic VLAN topology from PART 1

imageClick to enlarge

What about THIS Network Topology ?

imageClick to enlarge

Notice this one has TWO Switches (SW1 and SW2) and ENGINEERING (VLAN 10) has two separate locations on the network.

TRUNK PORTS

  • In a small network with few VLANS, it’s possible to use a separate interface for EACH VLAN when connecting SWITCHES to SWITCHES, and SWITCHES to ROUTERS

  • HOWEVER, when the number of VLANS increases, this is not viable. It will result in wasted interfaces, and often ROUTERS won’t have enough INTERFACES for each VLAN

  • You can use TRUNK PORTS to carry traffic from multiple VLANS over a single interface

A TRUNK PORT carrying multiple VLAN connections over single interface

imageClick to enlarge

imageClick to enlarge

How does a packet know WHICH VLAN to send traffic to over the TRUNK PORT ?

VLAN TAGS !

SWITCHES will “tag” all frames that they send over a TRUNK LINK. This allows the receiving SWITCH to know which VLAN the frame belongs to.

TRUNK PORT = “Tagged” ports

ACCESS PORT = “Untagged” ports

VLAN TAGGING

  • There are TWO main TRUNK protocols:
    • ISL (Inter-Switch Link)
    • IEEE 802.1Q (also known as “dot1q”)

ISL is an old Cisco proprietary protocol created before industry standard IEEE 802.1Q

IEEE 802.1Q is an industry standard protocol created by the IEEE (Institute of Electrical and Electronics Engineers)

You will probably NEVER use ISL in the real world; even modern Cisco equipment doesn’t use it.

For the CCNA, you will only need to learn 802.1Q

ETHERNET HEADER with 802.1Q

imageClick to enlarge

  • The 802.1Q TAG Is inserted between the SOURCE and TYPE/LENGTH fields in the ETHERNET FRAME
  • The TAG is 4 bytes (32 bits) in length
  • The TAG consists of TWO main fields:
    • Tag Protocol Identifier (TPID)
    • Tag Control Information (TCI)
      • TCI consists of THREE sub-fields:

imageClick to enlarge

TPID (TAG Protocol Identifier) :

  • 16 bits (2 bytes) in length
  • Always set to a value of 0x8100. This indicates that the frame is 802.1Q TAG

TCI / PCP (Priority Code Point) :

  • 3 bits in length
  • Used for Class of Service (CoS), which prioritizes important traffic in congested networks

TCI / DEI (Drop Eligible Indicator) :

  • 1 bit in length
  • Used to indicated frames that can be dropped if the network is congested

TCI / VID (VLAN ID) :

  • 12 bits in length
  • Identifies the VLAN the frame belongs to
  • 12 bits in length = 4096 total VLANS (2^12), range of 0 - 4095
  • VLANs 0 and 4095 are reserved and can’t be used
  • Therefore, the actual range of VLANs is 1 - 4094

NOTE : Cisco’s ISL also had a VLAN range of 1 - 4094

VLAN RANGES

imageClick to enlarge

NATIVE VLAN

imageClick to enlarge

imageClick to enlarge

imageClick to enlarge

TRUNK CONFIGURATION

imageClick to enlarge

imageClick to enlarge

Many modern switches do not support Cisco’s ISL at all. They only support 802.1Q (dot1q)

However, SWITCHES that do support both (like the one I am using in this example) have a TRUNK encapsulation of “AUTO” by default

To MANUALLY configure the INTERFACE as a TRUNK PORT, you must first set the encapsulation to “802.1Q” or “ISL”. On SWITCHES that only support 802.1Q, this is not necessary

After you set the encapsulation type, you can then configure the interface as a TRUNK

  1. Select the interface to configure

  2. Use “#switchport trunk encapsulation dot1q” to set the encapsulation mode to 802.1Q

  3. Use “#switchport mode trunk” to manually configure the interface to TRUNK

imageClick to enlarge

Use the “#show interfaces trunk” command to confirm INTERFACES on TRUNK

imageClick to enlarge

Commands to allow a VLAN on a given TRUNK

imageClick to enlarge

imageClick to enlarge

Command to change the NATIVE VLAN

imageClick to enlarge

imageClick to enlarge

Setting up our TRUNKS for this Network

imageClick to enlarge

We will need to configure :

SW1 : g0/0 interface (already configure above this section)

SW2: g0/0, and g0/1 interface

SW2 g0/0

imageClick to enlarge

SW2 g0/1

imageClick to enlarge

What about the ROUTER, R1 ?

ROUTER ON A STICK (ROAS)

imageClick to enlarge

imageClick to enlarge

imageClick to enlarge

NOTE the Sub-Interface names (like the network diagram) of 0.10, 0.20 and 0.30

You assign them IP addresses identically like you would a regular interface (using the last usable IP address of a given VLAN subnet)

Sub-interfaces will appear with the “show ip interface brief” command

imageClick to enlarge

They also appear in the “show ip route” command (Route Table)

imageClick to enlarge

ROAS is used to route between multiple VLANs using a SINGLE interface on a ROUTER and SWITCH

The SWITCH interface is configured as a regular TRUNK

The ROUTER interface is configured using SUB-INTERFACES. You configure the VLAN tag and IP address on EACH SUB-INTERFACE

The ROUTER will behave as if frames arriving with a certain VLAN tag have arrived on the SUB-INTERFACE configured with that VLAN tag

The ROUTER will TAG frames sent out of EACH SUB-INTERFACE with the VLAN TAG configured on the SUB-INTERFACE

PreviousVLANs - Part 1
NextVLANs - Part 3