Sunteți pe pagina 1din 126

© 2003, Cisco Systems, Inc. All rights reserved.

Role of Multilayer Switches in the


Network

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN v2.0—1-26 2-26
Layer 2 Switching

• Hardware-based bridging
• Wire-speed performance
• High-speed scalability
• Low latency
• MAC address

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-27


Impact of Layer 2 Switching

• Layer 2 switched networks have the same


characteristics as bridged networks.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-28
Benefits of Routing

• Optimal path determination


• Traffic management
• Layer 3 security

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-29


Layer 3 Switching

• Hardware-based
packet forwarding
• High-performance
packet switching
• Layer 3 security
• Policy deployment

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-30


Multilayer Switching

• Combines functionality of:


– Layer 2 switching
– Layer 3 switching
– Layer 4 switching
• High-speed scalability
• Low latency

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-31


Fast Ethernet

• Provides client access to the network

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-32


What Is Fast Ethernet?

• Built on Ethernet principles


• Runs at 100 Mbps
• Uses same frame types, lengths, and formats
• Still CSMA/CD
• Same MAC layer, new physical layer

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-33


Gigabit Ethernet

• Enhances client/server performance across the enterprise


• Connects directly to Gbps interfaces on LAN switches that
aggregate traffic from 10- or 100-Mbps segments
• Connects distribution-layer switches in each building with a
central campus core
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-34
10 Gigabit Ethernet

40 Km

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-35


Enterprise Campus Infrastructure

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-36


Selecting Layer 2 or Layer 3 Switching

Layer 2 Switching Layer 3 Switching

Cost Moderate Expensive

Complexity Simpler More complex

Versatility Less versatile More versatile

Typical uses Building Access Building Distribution


Campus Backbone Campus Backbone

• Layer 2 switching supports simple, flat networks.


• Layer 3 switching is useful in hierarchical networks that require
complex routing.
• Layer 3 switching offers advantages of equal cost routing, fast
reconvergence, load balancing, and scalability.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-37
Small Campus Network

• Collapse the Campus Backbone and Building Distribution


submodules in the Campus Backbone submodule.
• Scale up to several Building Access switches.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-38
Large Campus Design

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-39


Summary

• Layer 2 switches provide high-speed scalability to the


wiring closet and Campus Backbone, while multilayer
switches add additional functionality.
• Data-link layer technologies available for use with
switches include varying speeds of Ethernet.
• Switches can be deployed throughout the Campus
Infrastructure module, providing access for hosts,
implementing the distribution module, and providing the
routing functionality in the core module.
• Within the Server Farm module, switches provide access
between the Server Farm and the core.
• In the Enterprise Edge module, switches provide
functionality in the Edge Distribution, E-Commerce, and
VPN/Remote Access modules.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-40


Getting Started with Catalyst
Switches

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN v2.0—1-41 2-41
Cisco IOS File System and Devices

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-42


Managing Cisco IOS Images

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-43


Verifying Memory and Deciphering
Image Filenames

Switch#show flash

Directory of flash:/

2 -rwx 401 Jan 01 1970 00:01:06 env_vars


3 -rwx 2664051 Mar 02 1993 21:58:25 c2950-i6q4l2-mz.121-11.EA1.bin
4 -rwx 108 Mar 01 1993 00:01:20 info
6 drwx 640 Mar 01 1993 00:03:16 html
19 -rwx 108 Mar 01 1993 00:03:16 info.ver
20 -rwx 1636 Mar 01 1993 11:20:55 vlan.dat
23 -rwx 2193 Mar 01 1993 00:09:57 config.text

7741440 bytes total (1101312 bytes free)

• Verify that flash memory has room for the


Cisco IOS image.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-44


Creating a Software Image Backup

• Back up current files prior to updating flash memory.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-45
Loading the Image from the Network

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-46


Cisco IOS copy Command

• NVRAM
• Terminal
• TFTP server
• Erase start
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-47
show and debug Commands

show debug

Processing
Static Dynamic
characteristics

Processing load Low overhead High overhead

Primary use Gather facts Observe processes

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-48


Considerations When Using debug
Commands

• May generate output in a variety of formats that


may not identify the problem
• Require high overhead, possibly disrupting
network device operation
• Useful for obtaining information about network
traffic and router status

Be careful with debug commands!

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-49


The service timestamps Command

Switch(config)#service timestamps debug datetime msec


*Mar 13 22:56:29.702: datagramsize=100, IP 25: s=172.16.1.11 (local), d=10.1.1.1
(Vlan1), totlen 100, fragment 0, fo 0, sending.

Switch(config)#service timestamps log datetime msec


*Mar 13 22:55:46.342: %SYS-5-CONFIG_I: Configured from console by console

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-50


Problem: Cannot Connect Through
Console Port

• Make sure you are using the correct type of


cable.
• Make sure the terminal configuration matches
the switch console port configuration.
• Make sure the cable pinouts are correct for your
supervisor engine.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-51


Problem: Cannot Communicate
with Other Devices

• Check:
– Cabling
– LINK LED
• Make sure that:
– Interface is configured as “no shutdown.”
– IP address, subnet mask, and VLAN membership of the
switch interface are correct.
– Management interface configuration is complete.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-52


Problem: Cannot Communicate
with Host

• If the host is in the same subnet as the switch interface,


make sure the switch interface and the switch port are on
the same VLAN.
• If the host is in a different subnet, make sure the default
gateway is configured with the address of a router in the
same subnet as the switch interface.
• Check the status of the port connection.
• Make sure the host speed and duplex settings are
correct.
• Make sure the switch is learning the MAC address of the
host.
• If possible, connect to another port.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-53


Problem: Cannot Autonegotiate Port
Speed/Duplex

• Make sure autonegotiation is configured on both


ends of the link.
• If autonegotiation fails when you connect a
client NIC to the switch, check the NIC and
drivers to make sure that autonegotiation is
supported.
• If autonegotiation is supported and properly
configured, turn off autonegotiation and set the
speed and duplex manually.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-54


Summary

• In IOS, you use the copy command to transfer IOS software


images and configuration files between the switch and a TFTP
server, or to configure the switch from a file rather than
individual commands.
• As your network grows, you may want to store your Cisco IOS
images and configuration files on a central TFTP server, which
would allow you to control the number and revision level of IOS
images and configuration files you must maintain.
• Basic problems that you may encounter with a Catalyst switch
include not being able to connect through the console port, not
being able to communicate with a host, and not being able to
autonegotiate the speed and duplex mode of a port.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-55


Configuring VLANs and VTP

© 2003, Cisco Systems, Inc. All rights reserved. 2-56


Objectives

Upon completing this module, you will be


able to:
• Configure, verify, and troubleshoot VLANs on a
switched network
• Configure, verify, and troubleshoot VLAN trunks
in a switched network
• Configure, verify, and troubleshoot VTP in a
switched network

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-57


Implementing VLANs

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN 2.0—2-58 2-58
Objectives

Upon completing this lesson, you will be able to:


• Describe the basic features and operation of VLANs on a
switched network
• Compare end-to-end and local VLANs, and determine
when to use each
• Configure static VLANs
• Configure access ports for static VLAN membership
• Verify the VLAN configuration
• Troubleshoot common VLAN problems on a switched
network

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-59


VLAN Overview

• Layer 2
connectivity
• Logical
organizational
flexibility
• Single
broadcast
domain
• Management
• Basic security

A VLAN = A Broadcast Domain = Logical Network (Subnet)

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-60


VLANs Establish Broadcast Domains

• VLANs plus routing limits broadcasts to the domain of origin.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-61
Local VLANs

• Local VLANs generally reside in the wiring closet.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-62
Static VLANs

• All users attached to same switch port must be in the same VLAN.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-63
Configuring VLANs in Global Mode

Switch#configure terminal
Switch(config)#vlan 3
Switch(config-vlan)#name Vlan3
Switch(config-vlan)#exit
Switch(config)#end

Deleting VLANs in Global Mode


Switch#configure terminal
Switch(config)#no vlan 3
Switch(config)#end

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-64


Assigning Access Ports to a VLAN

Switch(config)#interface gigabitethernet 1/1

• Enters interface configuration mode

Switch(config-if)#switchport mode access

• Configures the interface as an access port

Switch(config-if)#switchport access vlan 3

• Assigns the access port to a VLAN

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-65


Verifying the VLAN Configuration

Switch#show vlan [id | name] [vlan_num | vlan_name]

VLAN Name Status Ports


---- -------------------------------- --------- -------------------------------
1 default active Fa0/1, Fa0/2, Fa0/5, Fa0/7
Fa0/8, Fa0/9, Fa0/11, Fa0/12
Gi0/1, Gi0/2
2 VLAN0002 active
51 VLAN0051 active
52 VLAN0052 active

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 1002 1003
2 enet 100002 1500 - - - - - 0 0
51 enet 100051 1500 - - - - - 0 0
52 enet 100052 1500 - - - - - 0 0

Remote SPAN VLANs


------------------------------------------------------------------------------
Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-66
Verifying the VLAN Port Configuration

Switch#show running-config interface {fastethernet |


gigabitethernet} slot/port

• Displays the running configuration of the interface

Switch#show interfaces [{fastethernet | gigabitethernet}


slot/port] switchport

• Displays the switch port configuration of the interface

Switch#show mac-address-table interface interface-id [vlan


vlan-id] [ | {begin | exclude | include} expression]

• Displays the MAC address table information for the specified


interface in the specified VLAN

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-67


Troubleshooting VLANs

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-68


Problem: One Device Cannot
Communicate with Another

• Use the show interface command:


– Make sure the VLAN membership of the switch
port is correct.
– If the host is in the same subnet as the switch
interface, make sure the switch interface and
the switch port to which the host is connected
are assigned to the same VLAN.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-69


Summary
• A VLAN is a logical grouping of switch ports connecting
nodes of virtually any type with no regard to physical
location.
• An end-to-end VLAN spans the entire switched network,
while a local VLAN is restricted to a single switch.
• Static VLANs involve switch ports that you manually
assign to a particular VLAN. You can configure VLANs
using Cisco IOS commands in VLAN configuration mode.
• Once a VLAN has been defined, you can assign switch
ports to it.
• You use show commands to confirm that a VLAN and its
associated ports have been configured correctly.
• To troubleshoot VLANs, you should check the physical
connections, switch configuration, and VLAN
configuration.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-70
Implementing VLAN Trunks

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN v2.0—2-71 2-71
VLAN Trunking

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-72


Switch Ports and Trunk Ports

Command Function

switchport mode access Sets the switch port to


Access port unconditionally be an access port

switchport mode trunk Sets the switch port to


Trunk port unconditionally become a trunk port

switchport mode dynamic Sets the switch port to


Dynamic port dynamically negotiate the status
(access or trunk)

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-73


802.1Q Trunking

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-74


802.1Q Frame

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-75


802.1Q and Layer 2 Encapsulation

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-76


Importance of Native VLANs

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-77


VLAN Ranges and Mappings

VLAN Range Range Usage

0, 4095 Reserved For system use only

1 Normal Cisco default

2-1001 Normal For Ethernet VLANs

Cisco defaults for FDDI


1002-1005 Normal
and Token Ring

1025-4094 Extended For Ethernet VLANs only

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-78


Configuring 802.1Q Trunking

Switch(config)#interface fastethernet 5/8


Switch(config-if)#shutdown
Switch(config-if)#switchport trunk encapsulation dot1q
Switch(config-if)#switchport trunk allowed vlan 1,15,11,1002-1005
Switch(config-if)#switchport mode trunk
Switch(config-if)#switchport nonegotiate
Switch(config-if)#no shutdown

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-79


Verifying 802.1Q Trunking
Switch#show running-config interface {fastethernet |
gigabitethernet} slot/port

Switch#show interfaces [fastethernet | gigabitethernet]


slot/port [ switchport | trunk ]

Switch#show interfaces gigabitEthernet 0/1 switchport


Name: Gi0/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001

. . .

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-80


Problem: A Device Cannot Establish a
Connection Across a Trunk Link

Make sure:
• The Layer 2 interface mode configured on both
ends of the link is valid.
• The trunk encapsulation type configured on both
ends of the link is valid.
• The native VLAN is the same on both ends of the
trunk (802.1Q trunks).

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-81


Summary

• A trunk is a Layer 2 point-to-point link between


networking devices capable of Layer 2 operations. Trunks
carry the traffic of multiple VLANs or multiple networks
over a single physical link.
• 802.1Q protocol is an open standard protocol used to
interconnect multiple Layer 2-capable devices.
• 802.1Q trunks define a native VLAN for frames that are
not tagged by default.
• 802.1Q VLAN numbers are in the range 0 to 4094.
• Switch ports are configured for 802.1Q trunking using
Cisco IOS commands.
• If a problem exists with a trunking link, make sure that the
interface modes, encapsulation types, and native VLANs
are correct on both sides of the link.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-82


Implementing VLAN Trunk
Protocol (VTP)

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN 2.0—2-83 2-83
VTP Protocol Features

• Advertises VLAN configuration information


• Maintains VLAN configuration consistency throughout a
common administrative domain
• Sends advertisements on trunk ports only

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-84


VTP Modes
• Creates, modifies, and deletes
VLANs
• Sends and forwards
advertisements
• Synchronizes VLAN
configurations
• Saves configuration in NVRAM

• Cannot create,
change, or delete • Creates, modifies, and
VLANs deletes VLANs locally
• Forwards only
advertisements • Forwards
• Synchronizes advertisements
VLAN • Does not
configurations synchronize VLAN
• Does not save in configurations
NVRAM • Saves configuration in
NVRAM
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-85
VTP Operation
• VTP advertisements are sent as multicast frames.
• VTP servers and clients are synchronized to the latest revision number.
• VTP advertisements are sent every 5 minutes or when there is a change.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-86


VTP Pruning

• Increases available bandwidth by reducing unnecessary flooded traffic


• Example: Station A sends broadcast, and broadcast is flooded only toward
any switch with ports assigned to the red VLAN.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-87


VTP Versions

• All switches in a management domain must run the same version.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-88
VTP Configuration Guidelines

• Configure the following:


– VTP domain name
– VTP mode (server mode is the default)
– VTP pruning
– VTP password
– VTP trap
• Use caution when adding a new switch into an existing
domain.
• Add a new switch in client mode to prevent the new
switch from propagating incorrect VLAN information.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-89


Configuring a VTP Server

Switch(config)#vtp server

• Configures VTP server mode

Switch(config)#vtp domain domain-name

• Specifies a domain name

Switch(config)#vtp password password

• Sets a VTP password

Switch(config)#vtp pruning

• Enables VTP pruning in the domain

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-90


Configuring a VTP Server (Cont.)

Switch#configure terminal

Switch(config)#vtp server

Setting device to VTP SERVER mode.


Switch(config)#vtp domain Lab_Network

Setting VTP domain name to Lab_Network


Switch(config)#end

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-91


Verifying the VTP Configuration

Switch#show vtp status

Switch#show vtp status

VTP Version : 2
Configuration Revision : 247
Maximum VLANs supported locally : 1005
Number of existing VLANs : 33
VTP Operating Mode : Client
VTP Domain Name : Lab_Network
VTP Pruning Mode : Enabled
VTP V2 Mode : Disabled
VTP Traps Generation : Disabled
MD5 digest : 0x45 0x52 0xB6 0xFD 0x63 0xC8 0x49 0x80
Configuration last modified by 0.0.0.0 at 8-12-99 15:04:49
Switch#

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-92


Verifying the VTP Configuration
(Cont.)

Switch#show vtp counters

Switch#show vtp counters

VTP statistics:
Summary advertisements received : 7
Subset advertisements received : 5
Request advertisements received : 0
Summary advertisements transmitted : 997
Subset advertisements transmitted : 13
Request advertisements transmitted : 3
Number of config revision errors : 0
Number of config digest errors : 0
Number of V1 summary errors : 0

VTP pruning statistics:


Trunk Join Transmitted Join Received Summary advts received from
non-pruning-capable device
---------------- ---------------- ---------------- ---------------------------
Fa5/8 43071 42766 5

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-93


Problem: VTP Not Updating
Configuration on Other Switches

• Make sure switches are connected through trunk


links.
• Make sure the VTP domain name is the same on
the appropriate switches.
• Check that the switch is not in VTP transparent
mode.
• Verify the same password used on all switches
in the VTP domain.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-94


Summary

• VTP is used to distribute and synchronize information


about VLANs configured throughout a switched network.
• If you use VTP in your network, you must decide whether
to use VTP version 1 or version 2. Verify the supervisor
support for VTP before making your decision.
• When a network device is in VTP server mode, you can
change the VLAN configuration and have it propagate
throughout the network.
• Use show commands to verify the VTP configuration.
• Problems with VTP configuration can frequently be traced
to improperly configured trunk links, domain names, VTP
modes, or passwords.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-95


Implementing Spanning Tree
Protocol

© 2003, Cisco Systems, Inc. All rights reserved. 2-96


Examining the Spanning Tree
Protocol

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN v2.0—3-97 2-97
Transparent Bridging

• A switch has the same characteristics as a


transparent bridge.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-98
What Is a Bridging Loop?

• Bridging loops occur any time there is a redundant


path or loop in the bridge network.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-99
Preventing Bridging Loops

• Bridging loops can be prevented by disabling the


redundant path.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-100
Spanning-Tree Bridge ID

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-101


Spanning-Tree Path Cost

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-102


Spanning Tree Port States
• Spanning tree transits each port through several
different states:

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-103


Four-Step Spanning-Tree
Decision Process

• Lowest root BID


• Lowest path cost to root bridge
• Lowest sender BID
• Lowest port ID

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-104


Spanning-Tree Operation
• One root bridge per network
• One root port per nonroot bridge
• One designated port per segment
• Nondesignated ports are blocked

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-105


Spanning Tree Protocol
Root Bridge Selection

• Which switch has the lowest bridge ID?

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-106


Spanning Tree Protocol
Root Port Selection

Fast Ethernet
RP

Ethernet

• SW X is the root bridge


• SW Y needs to elect a root port
• Which port is the root port on SW Y?
• FastEthernet total cost = 0 + 19
• Ethernet total cost = 0 + 100
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-107
Planning Root Bridge Selection

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-108


Per VLAN Spanning Tree

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-109


Per VLAN Spanning Tree (Cont.)

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-110


Summary

• The Spanning Tree Protocol is designed to


prevent bridging loops in a redundant network.
• Spanning Tree Protocol uses the concepts of
root bridges, root ports, and designated ports to
establish a loop-free path through the network.
• Per VLAN Spanning Tree + (PVST+) maintains a
separate spanning tree for each VLAN.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-111


Configuring Spanning Tree
Protocol

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN 2.0—3-112 2-112
Enabling Spanning Tree
Switch(config)#spanning-tree vlan 200

• Enables spanning tree on a specific VLAN


Configuring the Root Bridge
Switch(config)#spanning-tree vlan 200 priority 4096

• Lowers the spanning tree priority, forcing this switch to be the


root bridge

Switch(config)#spanning-tree vlan 200 priority 8192

• Sets the spanning tree priority, enabling this switch to be the


secondary root bridge

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-113


Verifying STP
Switch#show spanning-tree vlan vlan-id

• Displays spanning-tree configuration information


ASW11#show spanning-tree vlan 200

VLAN0200
Spanning tree enabled protocol ieee
Root ID Priority 49352
Address 0008.2199.2bc0
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 49352 (priority 49152 sys-id-ext 200)


Address 0008.2199.2bc0
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Uplinkfast enabled

Interface Port ID Designated Port ID


Name Prio.Nbr Cost Sts Cost Bridge ID Prio.Nbr
---------------- -------- --------- --- --------- -------------------- --------
Fa0/1 128.1 3019 LIS 0 49352 0008.2199.2bc0 128.1
Fa0/2 128.2 3019 LIS 0 49352 0008.2199.2bc0 128.2

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-114


Verifying STP (Cont.)

Switch#show spanning-tree bridge

• Displays spanning-tree bridge information

Switch#show spanning-tree bridge

Hello Max Fwd


Vlan Bridge ID Time Age Dly Protocol
---------------- --------------------------------- ----- --- --- --------
VLAN0200 49352 (49152,200) 0008.2199.2bc0 2 20 15 ieee
VLAN0202 49354 (49152,202) 0008.2199.2bc0 2 20 15 ieee
VLAN0203 49355 (49152,203) 0008.2199.2bc0 2 20 15 ieee
VLAN0204 49356 (49152,204) 0008.2199.2bc0 2 20 15 ieee
VLAN0205 49357 (49152,205) 0008.2199.2bc0 2 20 15 ieee
VLAN0206 49358 (49152,206) 0008.2199.2bc0 2 20 15 ieee

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-115


Summary

• You enable spanning tree on a per-VLAN basis.


• The switch with the lowest bridge ID will become the root
bridge for a VLAN.
• Spanning tree considers port cost when selecting an
interface to put into the forwarding state. You can assign
lower cost values to interfaces to select first.
• You can use a variety of show commands to display
configuration information about spanning tree.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-116


Configuring EtherChannel

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN 2.0—3-117 2-117
Objectives

Upon completing this lesson, you will be


able to:
• Identify the methods available to aggregate
multiple ports, and configure Fast EtherChannel
and Gigabit EtherChannel to form a faster
connection

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-118


Load Balancing with EtherChannel

• Logical aggregation
of similar links
• Viewed as one
logical port
• Switch-level load
balancing
• Redundancy

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-119


Configuring EtherChannel

Switch(config)#interface port-channel port-channel-number

• Creates a port-channel interface

Switch(config-if)#ip address address mask


• Assigns an IP address and subnet mask to the EtherChannel

Switch(config)#interface interface slot/port


• Specifies an interface to configure
Switch(config-if)#channel-group number mode {auto |
desirable | on}

• Configures the interface in a port-channel and specifies the


PAgP mode

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-120


Verifying EtherChannel
Switch#show running-config interface port-channel num

• Displays port-channel information

Switch#show running-config interface interface x/y

• Displays interface information

Switch#show run interface port-channel 1 Switch#show run interface gig 0/9


Building configuration... Building configuration...
Current configuration:
! Current configuration:
interface Port-channel1 !
no ip address interface GigabitEthernet 0/9
no ip directed-broadcast no ip address
end channel-group 1 mode desirable
end

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-121


Verifying EtherChannel (Cont.)
Switch#show etherchannel num port-channel

• Displays port-channel information after configuration


Switch#show etherchannel 1 port-channel
Port-channels in the group:
----------------------

Port-channel: Po1
------------

Age of the Port-channel = 01d:01h:31m:38s


Logical slot/port = 1/0 Number of ports = 2
GC = 0x00020001 HotStandBy port = null
Port state = Port-channel Ag-Inuse

Ports in the Port-channel:

Index Load Port EC state


------+------+------+------------
0 00 Gi0/9 desirable-sl
0 00 Gi0/10 desirable-sl

Time since last port bundled: 00d:20h:04m:38s Gi0/9


Time since last port Un-bundled: 00d:21h:17m:20s Gi0/10
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-122
Summary

• EtherChannel allows you to specify multiple Ethernet


ports of the same type as a single virtual link.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-123


Routing Between VLANs

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN v2.0—5-124 2-124
Port-Based VLANs

• Add ports to a VLAN by using the switchport


interface configuration commands:
– Identify the interface.
– For a trunk port, set trunk characteristics and
define the VLANs to which it can belong.
– For an access port, set and define the VLAN to
which it belongs.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-125


Switch Ports

• Layer 2-only interfaces associated with a physical port


• Access port
– Carries the traffic of and belongs to only one VLAN
• Trunk port
– Carries the traffic of multiple VLANs
– By default is a member of all VLANs in the VLAN
database
• Configure switch ports using the switchport interface
configuration commands

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-126


Layer 3 Switch Virtual Interfaces

• Represent a VLAN of switch ports as one interface to the


routing function in the system
• Created the first time that you enter the vlan interface
configuration command for a VLAN interface
• Configure a VLAN interface for each VLAN for which you
want to route traffic, and assign it an IP address
• Support routing protocol and configurations

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-127


Solution: Routing Between VLANs

• Communications between VLANs requires a Layer 3


services module.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-128
Connecting VLANs with a
Multilayer Switch

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-129


Configuring Inter-VLAN Routing
on a Switch

Switch(config)#ip routing

• Enables IP routing on the switch

Switch(config)#router ip_routing_protocol <options>

• Specifies the IP routing protocol

Switch(config)#interface vlan-id

• Enters interface configuration mode for a specific VLAN

Switch(config-if)#ip address n.n.n.n subnet-mask

• Assigns and IP address to the VLAN

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-130


Verifying Inter-VLAN Routing

• ping tests connectivity to remote hosts.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-131
Verifying the Inter-VLAN Routing
Configuration

Switch#show running-config

• Displays the current configuration

Switch#show ip route

• Displays IP route table information

Switch#show ip protocols

• Displays IP routing protocol information

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-132


Summary

• Multilayer switches support different types of interfaces


that you can use to route between VLANs.
• In Layer 2 switched networks, a routing device is used to
provide communications between VLANs. The router
provides VLAN access to shared resources and connects
to other parts of the network, or provides access to
remote sites across wide-area links.
• Use the ping and show commands to verify inter-VLAN
routing and display configuration and routing
information.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-133


Implementing Router Redundancy
in a Multilayer Switched Network

©©2003,
2003,Cisco
CiscoSystems,
Systems,Inc.
Inc.All
Allrights
rightsreserved.
reserved. BCMSN v2.0—6-134 2-134
Problem: Using Default Gateways

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-135


Router Redundancy

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-136


HSRP Group Members

• HSRP standby groups consist of multiple


routers performing specific roles.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-137
Designating an Active Router

• The active router responds to ARP requests with the MAC


address of the virtual router.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-138


Locating the Virtual
Router MAC Address

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-139


Active and Secondary Router
Interaction

• The active router broadcasts periodic hello messages.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-140


Active and Secondary Router
Interaction (Cont.)

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-141


Multiple HSRP Groups

• Routers can belong to multiple groups on the same subnet in a VLAN.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-142
Addressing HSRP Groups
across Trunk Links

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-143


Multiple HSRP Groups and
Multiple VLANs

• Routers can belong to multiple groups in multiple VLANs.


© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-144
Configuring an HSRP
Standby Interface

• Enabling HSRP on a Cisco router interface automatically


disables ICMP redirects.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-145
Configuring HSRP Standby Priority

• The router in an HSRP group with the highest priority


becomes the forwarding router.
• Default priority is 100.
© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-146
Configuring HSRP Standby Preempt

• Preempt enables a router to resume the forwarding router role.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-147


Displaying the Standby Brief Status

Switch#show standby brief


P indicates configured to preempt.
|
Interface Grp Prio P State Active addr Standby addr Group addr
Vl11 11 110 Active local 172.16.11.114 172.16.11.115

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-148


Debugging HSRP

Switch#debug standby

*Mar 1 00:22:30.443: SB11: Vl11 Hello out 172.16.11.111 Active pri 100 ip 172.16.11.115
*Mar 1 00:22:32.019: SB11: Vl11 Hello in 172.16.11.112 Standby pri 50 ip 172.16.11.115
*Mar 1 00:22:33.331: SB11: Vl11 Hello out 172.16.11.111 Active pri 100 ip 172.16.11.115
*Mar 1 00:22:34.927: SB11: Vl11 Hello in 172.16.11.112 Standby pri 50 ip 172.16.11.115
*Mar 1 00:22:36.231: SB11: Vl11 Hello out 172.16.11.111 Active pri 100 ip 172.16.11.115
*Mar 1 00:22:37.823: SB11: Vl11 Hello in 172.16.11.112 Standby pri 50 ip 172.16.11.115
*Mar 1 00:22:39.163: SB11: Vl11 Hello out 172.16.11.111 Active pri 100 ip 172.16.11.115
*Mar 1 00:22:40.735: SB11: Vl11 Hello in 172.16.11.112 Standby pri 50 ip 172.16.11.115
*Mar 1 00:22:42.119: SB11: Vl11 Hello out 172.16.11.111 Active pri 100 ip 172.16.11.115
*Mar 1 00:22:43.663: SB11: Vl11 Hello in 172.16.11.112 Standby pri 50 ip 172.16.11.115
*Mar 1 00:22:45.067: SB11: Vl11 Hello out 172.16.11.111 Active pri 100 ip 172.16.11.115
*Mar 1 00:22:46.567: SB11: Vl11 Hello in 172.16.11.112 Standby pri 50 ip 172.16.11.115

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-149


Summary

• Router device redundancy identifies multiple


routers as a single virtual router, with one router
acting as the forwarding router and the others
standing by to take over should the forwarding
router fail.
• HSRP defines a standby group of routers, with
one router as the active router.
• Use the standby command from interface
configuration mode to configure HSRP.

© 2003, Cisco Systems, Inc. All rights reserved. BCMSN v2.0—1-150

S-ar putea să vă placă și