●
In a campus design, a network administrator can design
a campus network with one of two models: end-to-end VLANs or local VLANs
●
End-to-end VLAN refers to a single VLAN that is
associated with switch ports widely dispersed throughout an enterprise network
on multiple switches. L2 switched campus network carries traffic for this VLAN
throughout the network. If more than one VLAN in network, trunks request to
carry traffic
●
End-to-end VLAN:
○
Each VLAN geographically dispersed thru network
○
Users are groups into VLAN regardless of physical
location
○
When user moves throughout campus, VLAN membership
stays the same regardless of physical switch
○
Users are associated with a given VLAN for network
management reasons
○
All devices on a VLAN have addresses in same subnet
○
Switches commonly operate in a server/client VTP mode
●
In a local VLAN, all users of a set of geographically
common switches are grouped in a single VLAN regardless of the organizational
function of those users. Usually confined to a wiring closet. VLANs local to
one access switch and trunking to the distribution switch. If users change
locations, their VLAN changes.
●
Local VLAN:
○
Created with physical boundaries in mind, not job
functions of end users
○
Exist usually between access and distribution levels
○
Usually routed at the distribution and core levels to
reach destination on other networks
○
Configure the VTP mode in transparent mode because
VLANs on a given access switch shouldn’t be advertised to other switches in the
network or manually created in other switches VLAN databases
○
Increased convergence time via routing protocols
instead of a spanning tree for L2 networks. Usually recommended to have one to
three VLANs per access layer switches
●
Avoid using VLAN 1 as the “blackhole” for all unused
ports
●
Try to separate voice, data, management, native,
blackhole and default VLANs
●
For trunk ports, turn off DTP and configure manually.
Use IEEE 802.1Q
●
Manually configure access ports
●
Prevent all data traffic from VLAN 1 - only permit
control protocols on it (DTP, VTP, STP{, BPDUs, PAgP, LACP, CDP, etc)
●
Catalyst 2950 and 2955 - Support 64 VLANs with standard
software and 250 VLANs with enhanced software
●
VLANs 1002- 1005 can’t be used - reserved for Token
Ring and FDDI VLANs
●
Catalyst 4500 and 6500 do not support VLANs 1006-1024
●
Catalyst 2970 supports 1005 VLANS but only 128
spanning-tree instances
●
VLAN 0 + 4095 - Reserved for system use only. Not sent
by VTP
●
VLAN 1 - Cisco default - Cannot be deleted
●
VLAN 2-1001 - For ethernet VLANs. Can be deleted,
created and modified
●
VLAN 1002 - 1005 - Cisco defaults for FDDI and Token
Ring. Cannot be deleted
●
VLAN 1006-10024 - For system use only and cannot be
seen
●
VLAN 1025-4094 - Extended. For ethernet VLANs only. Not
supported for VTP versions 1 and 2.. Supported in VTP 3
●
The switchport
host command effectively configures the port for a host device such as a workstation
or server. This feature is a macro for enabling Spanning Tree Portfact and
disabling EtherChanneling on a per-port basis.
●
Use the switchport
command with no keywords to configure interfaces as Layer 2 interfaces on
layer 3 switches
Show vlan field
descriptions
|
Field
|
Description
|
|
VLAN
|
VLAN number
|
|
Name
|
Name, if configured, of VLAN
|
|
Status
|
Status of VLAN (Active or
suspended)
|
|
Ports
|
Ports that belong to the VLAN
|
|
Type
|
Media type of the VLAN
|
|
SAID
|
Security association ID value
of the VLAN
|
|
MTU
|
Maximum transmission unit size
for the VLAN
|
|
Parent
|
Parent VLAN, if one exists
|
|
RingNo
|
Ring number for the VLAN if
applicable
|
|
BridgNo
|
Bridge number for the VLAN if
applicable
|
|
STP
|
Spanning Tree Protocol type
used on VLAN
|
|
BridgMode
|
Bridging mode for this VLAN
|
|
Trans1
|
Translation bridge 1
|
|
Trans2
|
Translation bridge 2
|
|
AREHops
|
Maximum number of hops for
All-Routes Explorer frames
|
|
STEHops
|
Maximum number of hops for
Spanning Tree Explorer frames
|
●
show
mac-address-table interface fa0/1 vlan 2 - displays MAC address table
information for specific interface in VLAN 1
●
show
running-config interface fa0/1 - displays config of a particular interface
●
show interfaces
fa0/1 switchport - displays detailed switch port information as the port
VLAN and operation modes
●
When troubleshooting VLANs, review: physical
connections, switch configuration, and VLAN configuration
●
When configuring an 802.1Q trunk, a matching native
VLAN must be defined on each end of the trunk line. Trunk line is inherently associated with
tagging each frame with a VID
●
ISL - Cisco proprietary trunking encapsulation. Not
really used as much anymore
●
201.1Q - Industry-standard trunking method. Better
support of QoS (802.1p), smaller frame overhead than ISL
●
ISL puts a header and modified FCS on a layer 2 frame
●
802.1Q - adds a 4 byte tag with the EtherType (set to
0x8100 to specify the 802.1Q tag follows), PRI (3-bit 802.1p priority field),
CFI (Canonical Format Identifier - Always set to 0 on ethernet switches and 1
on Token Ring-type networks), and VLAN ID as well as recalculating the existing
FCS
●
To process an 802.1Q tagged frame, a device must enable
MTU of 1522 or higher
●
Baby giants are frames that are larger than the
standard MTU of 1500 bytes but less than 2000 bytes
●
On an 802.1Q trunk port between two devices, both sides
must have the same native VLAN config or CDP will issue a Native VLAN Mismatch
error and issues will arise. Layer 2 loops may emerge
●
Dynamic Trunking Protocol (DTP) negotiates the
operational mode of directly connected switch ports to a trunk port and selects
the appropriate trunking protocol. DTP is recommended practice in multilayer
switched networks because it avoids network issues resulting from trunking
misconfigurations for initial config but once the network is stable, change to
permanent trunk
Trunking mode:
|
Mode in Cisco IOS
|
Function
|
|
Access
|
Interface put into permanent
nontrunking mode and negotiates the link into a nontrunk line regardless of
what neighbor wants
|
|
Trunk
|
Puts interface into permanent
trunking mode and negotiates to convert the link into a trunk link regardless
of what neighbor wants
|
|
Dynamic desirable
|
Makes the interface actively
attempt to convert the link to a trunk line and if the neighbor is set to
trunk, desirable or auto, it will become a trunk interface
|
|
Nonegotiate
|
Puts the interface into
permanent trunking mode but prevents the interface from generating DTP
frames. Use this mode when connecting a device that doesn’t support DTP
|
|
Dynamic auto
|
Makes the interface willing to
convert the link to a trunk link. Becomes a trunk if neighbor is set to trunk
or desirable mode - Default mode for all Ethernet interfaces in Cisco IOS
|
|
|
Dynamic
Auto
|
Dynamic
Desirable
|
Trunk
|
Access
|
|
Dynamic
Auto
|
Access
|
Trunk
|
Trunk
|
Access
|
|
Dynamic
Desirable
|
Trunk
|
Trunk
|
Trunk
|
Access
|
|
Trunk
|
Trunk
|
Trunk
|
Trunk
|
Limited
Connectivity
|
|
Access
|
Access
|
Access
|
Limited
Connectivity
|
Access
|
●
ISL supports VLAN numbers 1-1005, 802.1Q supports
1-4094
●
On trunk links, it is recommended to manually prune the
VLANS that are not used.
●
switchport trunk
native vlan vlan-id - specifies
the native vlan on a trunk interface
●
switchport trunk
allowed vlan {add | except | all | remove} vlan-id, vlan-id... - configure the allowed vlans on a trunk port
●
show interfaces interface_id trunk - Displays the trunk configuration of an interface
●
To troubleshoot a problem with the trunk port, verify
the following configs: Interface modes, native VLAN, encapsulation types
●
When using DTP, ensure that both ends of the trunk are
in the same VTP domain
●
Switches transmit VTP messages only on 802.1Q and ISL
trunks. VTP summary advertisements are transmitted over the management VLAN
(VLAN 1 is the default) using Layer 2 multicast frames every 5 minutes and the
packets are sent to the destination MAC address 01-00-0C-CC-CC-CC with the
logical link control (LLC) code of Subnetwork Access Protocol (SNAP) (AAAA) and
a type of 2003 (in the SNAP header)
●
VTP domain = one switch or several interconnected
switches that share the same VTP environment. Catalyst switches support only a
single VTP domain per switch.
●
In VTP version 3, there is a concept of a primary
server and a secondary server.
●
VTP pruning uses VLAN advertisements to determine when
a trunk connection is flooding traffic needlessly. The default is to carry
traffic for all VLANs in the VTP management domain. VTP Pruning will increase
available bandwidth by restricting flooding traffic to the trunk links that
traffic must use to access the appropriate network devices
●
Catalyst switches run an instance of STP for each VLAN
even if no ports are active in the VLAN or if VTP pruning removes the VLANs
from an interface. VTP pruning prevents flooded traffic from propagating to
switches that do not have members in specific VLANs. However, VTP pruning does
not eliminate the switches’ knowledge of the pruned VLANs
●
Three versions of VTP exist and they are not
interoperable or backwards compatible. Version 3 is not the most frequently
used version
●
Version 2 supports Token Ring, unrecognized
Type-Length-Value (TLV) support, version-independent transparent mode, and
consistency checks
●
If all the switches in a domain are capable of running
VTP version 2, enable VTP version 2 on one VTP server and the VTP server will
propagate the version number to the other VTP version 2-capable switches in the
VTP domain
●
VTP Version 3 - Does not directly handle VLANs. It’s
responsible for distributing a list of databases over an administrative domain.
It has support for extended VLANs (1025 -4094), support for creation and
advertising of Private VLANs, improved server authentication, enhancements to a
mechanism for protecting from the “wrong” database accidentally being inserted
into a VTP domain, interface with VTP version 1 and 2, and configurable on a
per-port basis
●
A switch needs a VTP advertisement request if the
switch has been reset, VTP domain name has been changed or the switch has
received a VTP summary advertisement with a higher configuration revision than
it’s own
●
VTP passwords can be 8-64 characters and the use of VTP
authentication is a recommended practice
●
show vtp status -
displays information about the VTP configuration and the current state in Cisco
IOS
●
show vtp
counters - displays statistics about VTP operation
●
Private VLANs prevent Layer 2 connectivity between end
devices on a switch in the same VLAN without placing the devices into different
IP subnets - prevents IP address wasting. You can restrict some ports on the
switch to reach only specific ports that have a default gateway or backend
server attached. You can restrict some ports on a switch to reach only specific
ports that have a default gateway or backup server attached.
●
Private VLANS are most commonly used with ISPs so they
don’t need to create a special VLAN per customer
●
A port in a Private VLAN can be one of the following
three types:
○
Isolated - has complete Layer 2 separation from other
ports within the same Private VLAN, except for promiscuous ports. Traffic to
the isolated port is completely blocked except from promiscuous ports and vice
versa.
○
Promiscuous - Can communicate with all ports within the
Private VLAN including community and isolated ports. Is part of one primary
VLAN but each promiscuous port can map to more than one secondary Private VLAN.
Promiscuous ports are generally router ports, backup or shared servers, or VLAN
interfaces.
○
Community - these ports communicate among themselves
and with their promiscuous ports. Isolated from other communities or in
isolated ports within their Private VLAN.
●
Private VLAN uses VLANs in the following ways:
○
Primary Private VLAN - The high-level VLAN of the
Private VLAN. A Primary Private VLAN can be composed of many secondary Private
VLANs with the secondary Private VLANs belonging to the same subnet of the
primary Private VLAN. It carries traffic from promiscuous port to isolated,
community, and other promiscuous ports in the same primary Private VLAN
○
Secondary Private VLAN - Is a child to a primary
Private VLAN and is mapped to one Private VLAN. End devices are attached to
secondary Private VLANs
●
Two types of secondary Private VLANs:
○
Community Private VLANs - Ports can community with
other ports in the same community and promiscuous ports of the same Private
VLAN
○
Isolated Private VLANs - Can communicate only with
promiscuous ports. Cannot even communicate with other isolated ports
●
A promiscuous port can service only one primary VLAN.
Can service one isolated VLAN or many community VLANs.
●
Private VLANs span across multiple switches by trunking
the private, isolated, and community VLANs to other devices that support
Private VLAN
No comments:
Post a Comment