Sie sind auf Seite 1von 21

Interconnecting Cisco Networking

Devices Part 1
ICND1 100-105

Instructor
Paul A. Parker

1
Chapter 11

Implementing Ethernet Virtual LANs

2
Chapter 11
Implementing Ethernet Virtual LANs
v Foundation Topics
▼ Virtual LAN Concepts
➘  By default all switch interfaces are in the same broadcast domain.
➘  The most common reasons for creating smaller broadcast domains
with VLANs is the following:
➘  To reduce CPU overhead on each device by reducing the number of devices that
receive each broadcast frame
➘  To reduce security risks by reducing the number of hosts that receive copies of
frames that the switches flood (broadcasts, multicasts, and unknown unicasts)
➘  To improve security for hosts that send sensitive data by keeping those hosts on a
separate VLAN
➘  To create more flexible designs that group users by department, or by groups that
work together, instead of by physical location
➘  To solve problems more quickly, because the failure domain for many problems is
the same set of devices as those in the same broadcast domain
➘  To reduce the workload for the Spanning Tree Protocol (STP) by limiting a VLAN to
a single access switch

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 3


Chapter 11
Virtual LAN Concepts
v Creating Multiswitch VLANs Using Trunking
▼ VLAN trunking relies on VLAN tagging when sending a frame
from one switch to another to identify the VLAN for the frame.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 4


Chapter 11
Virtual LAN Concepts
v The 802.1Q and ISL VLAN Trunking Protocols
▼ Both IEEE 802.1Q and Cisco ISL tag each frame with a VLAN ID,
however, 802.1Q inserts an extra 4-byte header into the original
frame’s Ethernet header where ISL wraps the existing Ethernet
header with the VLAN header.
▼ The native VLAN ID defaults to VLAN 1 and is unique to 802.1Q
as ISL does not support the concept.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 5


Chapter 11
Virtual LAN Concepts
v Forwarding Data Between VLANs
▼ VLANs create their own broadcast domain and therefore require
different subnets.
▼ In order for VLANs to communicate with each other they need a
router to forward packets between the VLANs.
▼ The typical switch use Layer 2 forwarding logic and are often
referred to as a “Layer 2” switch.
▼ The multilayer switch, or Layer 3 switch, provides some features
of a router and are able to forward packets between different
VLANs.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 6


Chapter 11
Virtual LAN Concepts
v Routing Packets Between VLANs with a Router
▼ Routers support trunking to allow switches to utilize one interface
to support multiple
VLANs.
▼ This configuration is
sometimes called
“router-on-a-stick”
because the device
has a single physical
link.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 7


Chapter 11
Virtual LAN Concepts
v Routing Packets with a Layer 3 Switch
▼ Using a single physical interface sets limits on the bandwidth that
a switch has to forward packets between different VLANs.
▼ The layer 3 switch over comes this limit by providing routing
between the VLANs in the same physical switch.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 8


Chapter 11
VLAN Configuration and Verification
v Creating VLANs and Assigning Access to an Interface
▼  Step 1. To configure a new VLAN, follow these steps:
➘  A. From configuration mode, use the vlan vlan-id global configuration
command to create the VLAN and to move the user into VLAN configuration
mode.
➘  B. (Optional) Use the name name VLAN subcommand to list a name for the
VLAN. If not configured, the VLAN name is VLANZZZZ, where ZZZZ is the 4-
digit decimal VLAN ID.
▼  Step 2. For each access interface (each interface that does not trunk,
but instead belongs to a single VLAN), follow these steps:
➘  A. Use the interface command to move into interface configuration mode
for each desired interface.
➘  B. Use the switchport access vlan id-number interface subcommand to
specify the VLAN number associated with that interface.
➘  C. (Optional) To disable trunking on that same interface, so that the interface
does not negotiate to become a trunk, use the switchport mode access
interface subcommand.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 9


Chapter 11
VLAN Configuration and Verification
v VLAN Trunking Protocol (VTP)
▼ VTP is a Cisco proprietary tool that advertises VLANs configured
on a switch to neighboring switches.
▼ A Cisco switch can use one of three VTP modes: server, client, or
transparent.
▼ A switch in server or client mode has the following:
➘  The server switches can configure VLANs in the standard range only
(1–1005).
➘  The client switches cannot configure VLANs.
➘  The show running-config command does not list any vlan
commands.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 10


Chapter 11
VLAN Configuration and Verification
v VLAN Trunking Configuration
▼ The configuration can predefine trunk settings or negotiation
settings for the following:
➘  The type of trunking: IEEE 802.1Q, ISL, or negotiate which one to
use
➘  The administrative mode: Whether to always trunk, always not
trunk, or negotiate
▼ The switchport mode command has these options:

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 11


Chapter 11
VLAN Configuration and Verification
v Expected Trunking Operational Mode

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 12


Chapter 11
VLAN Configuration and Verification
v Implementing Interfaces Connected to Phones
▼ The older non-IP phones used a category of UTP cabling that
often did not support 100-Mbps or 1000-Mbps Ethernet.
▼ Most offices had a single UTP cable running from the wiring
closet to each desk, but now two devices (the PC and the new IP
phone) both needed a cable from the desktopto the wiring closet.
▼ Installing a new cable to every desk would be expensive, plus
you would need more switch ports.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 13


Chapter 11
VLAN Configuration and Verification
v Data and Voice VLAN Concepts
▼ Data VLAN: Same idea and configuration as the access VLAN on
an access port, but defined as the VLAN on that link for
forwarding the traffic for the device connected to the phone on
the desk (typically the user’s PC).
▼ Voice VLAN: The VLAN defined on the link for forwarding the
phone’s traffic. Traffic in this VLAN is typically tagged with an
802.1Q header.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 14


Chapter 11
VLAN Configuration and Verification
v Data and Voice LAN Configuration and Verification
▼ Step 1. Use the vlan vlan-id command in global configuration
mode to create the data and voice VLANs if they do not already
exist on the switch.
▼ Step 2. Configure the data VLAN like an access VLAN, as usual:
➘  A. Use the interface type number command global configuration
mode to move into interface configuration mode.
➘  B. Use the switchport access vlan id-number command in
interface configuration mode to define the data VLAN.
➘  C. Use the switchport mode access command in interface
configuration mode to make this port always operate in access mode
(that is, to not trunk).
▼ Step 3. Use the switchport voice vlan id-number command in
interface configuration mode to set the voice VLAN ID.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 15


Chapter 11
VLAN Configuration and Verification
v IP Telephony Ports on Switches
▼ Configure these ports like a normal access port to begin:
Configure it as a static access port and assign it an access VLAN.
▼ Add one more command to define the voice VLAN (switchport
voice vlan vlan-id).
▼ Look for the mention of the voice VLAN ID, but no other new
facts, in the output of the show interfaces type number
switchport command.
▼ Look for both the voice and data (access) VLAN IDs in the output
of the show interfaces type number trunk command.
▼ Do not expect to see the port listed in the list of operational
trunks as listed by the show interfaces trunk command.

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 16


Chapter 11
Exam Preparation Tasks

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 17


Chapter 11
Command References
v Configuration Commands

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 18


Chapter 11
Command References
v Configuration Commands

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 19


Chapter 11
Command References
v EXEC Commands

CCENT/CCNA ICND1 Interconnecting Cisco Networking Devices Part 1 20


Questions?

21

Das könnte Ihnen auch gefallen