CCNA Exp3 - Chapter03 - VLANS.ppt [Compatibility Mode]

8/3/2019 CCNA Exp3 - Chapter03 - VLANS.ppt [Compatibility Mode]

http://slidepdf.com/reader/full/ccna-exp3-chapter03-vlansppt-compatibility-mode 1/65

Chapter 3 - VLANS

CCNA Ex loration 4.0

Objectives

• Explain the role of VLANs in a network.

• Explain the role of trunking VLANs in a network.

• Troubleshoot the common software or hardwareconfiguration problems associated with VLANs on switchesin a network topology.

Hc vin mng Bach Khoa - Website: www.bkacad.com 2

Role of VLANS

• One of the contributing technologies toexcellent network performance is the

separation of large broadcast domains intosmaller ones with VLANs.

of devices participating in broadcasts andallow devices to be separated into functional

groupings, such as database services for anaccounting department and high-speed datatransfer for an engineering department.

Before VLANS

1 building

• no problem !

Before VLANS

Many building

Before VLANS

• Many building: Problem ? – IT department wants to ensure that student

computers all share the same security featuresand bandwidth controls. How can the networkaccommodate the shared needs of theeo ra hicall se arated de artments? Do ou

create a large LAN and wire each departmenttogether?• It would be great to group the people with the

resources they use regardless of their geographic

location, and it would make it easier to managetheir specific security and bandwidth needs.

VLAN overview

• A VLAN allows a network administrator

to create groups of logically networkeddevices that act as if they are on theirown inde endent network

• These VLANs allow the networkadministrator to implement access and

security policies to particular groups ofusers.

VLANS details

• A VLAN is a broadcast domain created by one or moreswitches.

• The network design above creates three separatebroadcast domains.

Benefit of VLANS

VLAN ID

Extra: Extended Range VLANs

• Configuring Extended-Range VLANs – When the switch is in VTP transparent mode (VTP disabled), you can

create extended-range VLANs (in the range 1006 to 4094 for any switchport commands that allow VLAN IDs).

– Enter the vlan vlan-id global configuration command to access config-vlanmode and to configure extended-range VLANs. – The VLAN database configuration mode (that you access by entering the

vlan database privileged EXEC command) does not support the extendedrange.

– x en e -range con gura ons are no s ore n e a a ase.

Because VTP mode is transparent, they are stored in the switch runningconfiguration file. You can save the configuration in the startupconfiguration file by using the copy running-config startup-configprivileged EXEC command.

– Example:Switch(config)# vtp mode transparent

Switch(config)# vlan 2000

Switch(config-vlan)# endSwitch# copy running-config startup config

VLAN Tagging

No VLAN Tagging

VLAN Tagging

•There are two major methods of frame tagging, Cisco proprietary Inter-Switch Link (ISL) and IEEE 802.1Q.

• ISL used to be the most common, but is now being replaced by 802.1Qframe tagging.

• Cisco recommends using 802.1Q.

• VLAN Tagging and Trunking will be discussed in the next chapter.

802.10

Types of VLAN

• Data VLAN: A data VLAN is a VLAN that is configured tocarry only user-generated traffic.

Types of VLAN

• Default VLAN: – All switch ports become a member of the default VLAN after the

initial boot up of the switch.

– Having all the switch ports participate in the default VLAN makesthem all part of the same broadcast domain. This allows any deviceconnected to any switch port to communicate with other devices onother switch ports.

– The default VLAN for Cisco switches is VLAN 1. VLAN 1 has all thefeatures of any VLAN, except that you cannot rename it and youcan not delete it.

Types of VLAN

• Management VLAN:

– A management VLAN is any VLAN you configure to access themanagement capabilities of a switch.

– VLAN 1 would serve as the management VLAN if you did notproactively define a unique VLAN to serve as the managementVLAN.

– You assign the management VLAN an IP address and subnet

mask. A switch can be managed via HTTP, Telnet, SSH, or SNMP.

Types of VLAN

• Native VLAN:

– A native VLAN is assigned to an 802.1Q trunk port.

– An 802.1Q trunk port supports traffic coming from manyVLANs (tagged traffic) as well as traffic that does notcome from a VLAN (untagged traffic).

– The 802.1Q trunk port places untagged traffic on the

native VLAN. In the figure, the native VLAN is VLAN 99.

Native VLAN

Types of VLAN

• Voice VLAN: – It is easy to appreciate why a separate VLAN is needed to support

Voice over IP (VoIP) – VoIP traffic requires:

• Assured bandwidth to ensure voice quality• Transmission priority over other types of network traffic• Ability to be routed around congested areas on the network•

Voice VLAN

Types of traffic

Switch port membership

Controlling Broadcast Domains withVLANs

Switch 1172.30.1.21

255.255.255.0 172.30.2.12255.255.255.0

ARP Request

Without VLANs – No Broadcast Control

No VLANs

Same as a single VLAN

Two Subnets

172.30.2.10255.255.255.0

172.30.1.23255.255.255.0

• Without VLANs, the ARP Request would be seen by all hosts.

• Again, consuming unnecessary network bandwidth and host processingcycles.

Switch 1172.30.1.21

255.255.255.0

VLAN 1

172.30.2.12

255.255.255.0

VLAN 2

Switch Port: VLAN IDARP Request

With VLANs – Broadcast Control

Two VLANs

Two Subnets

172.30.2.10255.255.255.0

VLAN 2

172.30.1.23255.255.255.0

VLAN 1 1 2 3 4 5 6 .

1 2 1 2 2 1 .

Intra-VLAN Communication

• Communicating with a device in the same VLAN is calledintra-VLAN communication.

Inter-VLAN Communication

• Communicating with a device in another VLAN is calledinter-VLAN communication.

Controlling Broadcast Domains with VLANs and Layer 3 Forwarding

• SVI (switch virtual interface ) – SVI is a logical interface configured for a specific VLAN. You need to configure an

SVI for a VLAN if you want to route between VLANs or to provide IP hostconnectivity to the switch.

– An SVI is a virtual Layer 3 interface that can be configured for any VLAN that exists

on a Layer 3 switch.

VLAN Trunking

VLAN Trunk

• A trunk is a point-to-point link between one or more Ethernet switch interfaces andanother networking device, such as a router or a switch.

• A VLAN trunk does not belong to a specific VLAN, rather it is a conduit for VLANs

between switches and routers.

VLAN Trunk

802.1Q tagging

• EtherType field

– Set to the hexadecimal value of 0x8100. This value iscalled the tag protocol ID (TPID) value. With theEtherType field set to the TPID value, the switch receivingthe frame knows to look for information in the tag controlinformation field.

• Tag control information field – 3 bits of user priority - Used by the 802.1p standard, which specifies how to provide

expedited transmission of Layer 2 frames. A description of the IEEE 802.1p is beyondthe scope of this course; however, you learned a little about it earlier in the discussionon voice VLANs.

– 1 bit of Canonical Format Identifier (CFI) - Enables Token Ring frames to be carriedacross Ethernet links easily.

– 12 bits of VLAN ID (VID) - VLAN identification numbers; supports up to 4096 VLANIDs.

• FCS field

– After the switch inserts the EtherType and tag control information fields, it recalculatesthe FCS values and inserts it into the frame.

Extra: IEEE 802.1p

• IEEE 802.1p is a standard that provides traffic class expediting anddynamic multicast filtering. Essentially, it provides a mechanism forimplementing Quality of Service (QoS) at the MAC (Media Access

Control) level.• Eight different classes of service are available, expressed through the3-bit user_priority field in an IEEE 802.1Q header added to the frame.The way traffic is treated when assigned to any particular class is

undefined and left to the implementation. The IEEE however has made

some broad recommendations.

• 802.1p is used within the IEEE 802.1D and IEEE 802.1Q standards.

Extra: ISL Encapsulation Frame

Native Vlan and 802.1Q

• When you configure an 802.1Q trunk port, a default Port VLAN ID(PVID) is assigned the value of the native VLAN ID.

Extra: Basics of Dynamic Trunking Protocol (DTP)

• Ethernet trunk interfaces support several different trunking modes.

– Access – Dynamic desirable (default mode on Catalyst 2950 and 3550) – Dynamic auto – Trunk – Non-negotiate – dotq-tunnel (Not an option on the Catalyst 2950.)

T ki d

• The trunking modes available in Fast Ethernet and Gigabit Ethernet

Trunking mode

(config-if)#switchport mode trunk

switchport mode access

switchport mode dynamic desirable

switchport mode dynamic auto

Nonegotiateswitchport nonegotiate

E t T ki d

Extra: Trunking mode

• trunk —Configures the port to permanent trunk mode and negotiateswith the connected device on the other side to convert the link to trunkmode. If multiple trunk encapsulations are available, the encapsulationmust be chosen before this command will work.

• access —Disables port trunk mode and negotiates with the connecteddevice to convert the link to nontrunk. This port will belong to only theconfigured access VLAN.

• dynamic desirable —Triggers the port to negotiate the link from

connected device is in the trunk, dynamic desirable, or dynamicauto state. Otherwise, the port becomes a nontrunk port. This is thedefault for IOS switch ports

• dynamic auto —Enables the port to become a trunk only if theconnected device has the state set to trunk or dynamic desirable.

• nonnegotiate —Configures the port to permanent trunk mode. Nonegotiation takes place with the partner. The other side must be trunkor nonegotiate for the trunk to work. You must also specify theencapsulation before choosing this mode.

Trunking mode

Creating VLANs

• Add a VLAN

Extra: Creating VLANs

Switch#vlan database

Switch(vlan)#vlan {vlan_id } [name {vlan_name}]

Switch(vlan)#exit

• switch# vlan database

% Warning: It is recommended to configure VLAN from config mode,as VLAN database mode is being deprecated. Please consult user

documentation for configuring VTP/VLAN in config mode.

Assign VLAN to port

Extra: Configuring Ranges of VLANs

SydneySwitch(config)#interface range fastethernet0/8 ?

, comma

vlan 3

- hyphen

(config)#interface range fastethernet0/8 -12

(config-if-range)#switchport access vlan 3

(config-if-range)#exit

(config)#interface range fastethernet0/8 ,fastethernet0/12

(config-if-range)#switchport access vlan 3

(config-if-range)#exit

Verify VLAN

show vlan

show vlan brief

show interface vlan 2

show interface fa0/18 switchport

Delete Vlan

• (config)# no vlan vlan_id

• # delete flash:vlan.dat

Configure a Trunk link

Extra: switchport trunk

• Remove VLANs from the current list of the trunking line:(config-if)# switchport trunk allowed vlan remove vlan-id

• If a VLAN other than VLAN 1 is to be the Native VLAN, it needs to be identified on thetrunk ports:(config-if)# switchport trunk native vlan vlan-id

Extra: Specify the Trunk Encapsulation

Verify Trunk Configuration

• show interfaces interface-ID switchport

• show interface trunk

Managing a Trunk Configuration

Common Problems with Trunks

Native VLAN mismatchs

Trunk mode mismatch

• Solution: (config-if)# switchport mode trunk

Incorrect VLAN list

• Solution: – S1 f0/3: (config-if)# switchport trunk allowed vlan 10, 20, 99

Mistake of VLAN and IP subnets

Summary

CCNA Exp3 - Chapter03 - VLANS.ppt [Compatibility Mode]

Documents

Transcript of CCNA Exp3 - Chapter03 - VLANS.ppt [Compatibility Mode]

Exp3 - Chapter 3 - VLANs

Iris Chapter03

Chapter03 Balance

Report Exp3

Chapter03 Rev

Chapter03 Strategic

CCNA Exp3 - Chapter02 - Basic Switch Concepts and Configurations_dpf

CCNA Exp3 - Chapter07 - Basic Wireless Concepts and Configuration

CCNA Exp3 - Chapter06 - Inter-VLAN Routing_pdf

pierce chapter03

ThermoSolutions CHAPTER03

OS Chapter03

Chapter03 SAD

03 - Chapter03

Chapter03 Ppt

chapter03 8e

CCNA Exp3 - Chapter02 - Basic Switch Concepts and Configurations

Leadership Chapter03

Chapter03 Research

Chapter03 (1)