En SWITCH v7 Ch02

Chapter 2:
Campus Network Design

Fundamentals
CCNP R&S SWITCH: Implementing IP Switching
Course v6 Chapter #
2007 2010, Cisco Systems, Inc. All rights reserved.
Cisco Public
Chapter 2 Objectives
Enterprise Campus Network Design
Hierachical Network Design: Core Layer, Distribution Layer,
Access Layer
Modular Network Design
Layer 2 Switch Operation
Managing Switching Tables
Types of Multilayer Switching
Route Caching
Topology Based
Chapter #
Cisco Public
Introduction to
Enterprise
Campus Network
Design
Chapter #
Cisco Public
Enterprise Network
Core (Backbone)
Campus
Data Center
Branch
WAN
Internet Edge
Chapter #
Cisco Public
Campus Designs
Modular - easily supports growth and change. Scaling the
network is eased by adding new modules in lieu of
complete redesigns.
Resilient - proper high-availability (HA) characteristics
result in near-100% uptime.
Flexible - change in business is a guarantee for any
enterprise. These changes drive campus network
requirements to adapt quickly.
Chapter #
Cisco Public
Hierachical
Network Design
Chapter #
Cisco Public
Hierarchical Design Model

A campus network is an enterprise network consisting
of many LANs in one or more buildings, all connected
and all usually in the same geographic area. A
company typically owns the entire campus network
and the physical wiring. Campus networks commonly
consist of wired Ethernet LANs and shared wireless
LANs.
Chapter #
Cisco Public
Chapter #
Cisco Public

Ideally, you should design a network with a predictable behavior in
mind to offer low maintenance and high availability. A campus
network needs to recover from failures and topology changes quickly
and in a predetermined manner.
You should scale the network to easily support future expansions and
upgrades. With a wide variety of multiprotocol and multicast traffic,
the network should be capable of efficiently connecting users with the
resources they need, regardless of location.
Chapter #
Cisco Public

Ideally, the network should be arranged so that all end users are
located at a consistent distance from the resources they need to use.
Cisco has refined a hierarchical approach to network design that
enables network designers to organize the network into distinct layers
of devices. The resulting network is efficient, intelligent, scalable, and
easily managed.
Chapter #
Cisco Public
10
Two-Layer Network Hierarchy Emerges
Core Layer Emerges
Traffic Flow Paths Through a Network Hierarchy
Chapter #
Cisco Public
11

A hierarchical LAN design includes the following three
layers:
Access layerProvides endpoints and users direct
access to the network
Distribution layerAggregates access layers and
provides connectivity to services
Core layerProvides connectivity between
distribution layers for large LAN environments
Chapter #
Cisco Public
12

Access Layer:
The access layer exists where the end users are connected to the
network. Access switches usually provide Layer 2 (VLAN) connectivity
between users. Devices in this layer, sometimes called building access
switches, should have the following capabilities:
Low cost per switch port
High port density
Scalable uplinks to higher layers
High availability
Ability to converge network services (that is, data, voice, video)
Security features and quality of service (QoS)
Chapter #
Cisco Public
13

Distribution Layer
The distribution layer provides interconnection between the campus
networks access and core layers. Devices in this layer, sometimes
called building distribution switches , should have the following
capabilities:
Aggregation of multiple access layer switches
High Layer 3 routing throughput for packet handling
Security and policy-based connectivity functions
QoS features
Scalable and redundant high-speed links to the core and access
layers
Chapter #
Cisco Public
14

Core Layer
A campus networks core layer provides connectivity between all distribution
layer devices. The core, sometimes referred to as the backbone, must be
capable of switching traffic as efficiently as possible. Core switches should have
the following attributes:
Very high Layer 3 routing throughput
No costly or unnecessary packet manipulations (access lists, packet filtering).
Redundancy and resilience for high availability
Advanced QoS functions
Chapter #
Cisco Public
15

Core Layer
A campus networks core layer provides connectivity between all distribution
layer devices. The core, sometimes referred to as the backbone, must be
capable of switching traffic as efficiently as possible. Core switches should have
the following attributes:
Very high Layer 3 routing throughput
No costly or unnecessary packet manipulations (access lists, packet filtering).
Redundancy and resilience for high availability
Advanced QoS functions
Chapter #
Cisco Public
16

Collapsed Core
in smaller campus networks, where the cost and scalability of a

separate core layer is not warranted. A collapsed core block is one in
which the hierarchys core layer is collapsed into the distribution layer.
Chapter #
Cisco Public
17

Network Core
A core layer is required to connect two or more switch blocks in a campus
network. Because all traffic passing to and from all switch blocks must cross
the core, A core should consist of two multilayer switches that connect two or
more switch blocks in a redundant fashion. A redundant core is sometimes
called a dual core because it is usually built from two identical switches.
Chapter #
Cisco Public
18
Chapter #
Cisco Public
19
Multilayer Switches in Campus Networks

Hardware-based routing using
Application-Specific Integrated
Circuits (ASICs)
RIP, OSPF, and EIGRP are
supported
Layer 3 switching speeds
approximate that of Layer 2
switches
Layer 4 and Layer 7 switching
supported on some switches
Future: Pure Layer 3
environment leveraging
inexpensive L3 access layer
switches
Chapter #
Cisco Public
20
Multilayer Switches in Campus Networks

best practices redundant hierarchical network design:
Design each layer with pairs of switches.
Connect each switch to the next higher layer with two links for redundancy.
Connect each pair of distribution switches with a link, but do not connect the
access layer switches to each other (unless the access switches support some
other means to function as one logical stack or chassis).
Do not extend VLANs beyond distribution switches. The distribution layer should
always be the boundary of VLANs, subnets, and broadcasts. Although Layer 2
switches can extend VLANs to other switches and other layers of the hierarchy,
this activity is discouraged. VLAN traffic should not traverse the network core.
Chapter #
Cisco Public
21
Multilayer Switching Miscellany

ASIC-based (hardware)
switching is supported even
with QoS and ACLs,
depending on the platform;
6500 switches support
hardware-based switching with
much larger ACLs than 3560
switches.
ASICs on Catalyst switches
work in tandem with ternary
content addressable memory
(TCAM) and packet-matching
algorithms for high-speed
switching.
Catalyst 6500 switches with a

Supervisor Engine 720 and a
Multilayer Switch Feature
Card (MSFC3) must softwareswitch all packets requiring
Network Address Translation.
Unlike CPUs, ASICs scale in
switching architectures.
ASICs integrate onto
individual line modules of
Catalyst switches to
hardware-switch packets in a
distributed manner.
Chapter #
Cisco Public
22
Multilayer Switch Operation

Many Cisco Catalyst switches can also forward frames based on
Layers 3 and 4 information contained in packets. This is known as
multilayer switching (MLS). Naturally, Layer 2 switching is
performed at the same time because even the higher-layer
encapsulations still are contained in Ethernet frames.
Types of Multilayer Switching:
Catalyst switches have supported two basic generations or types of
MLS:
route caching (first-generation MLS) and
topology based
(second-generation MLS).
Chapter #
Cisco Public
23
Route caching: The first generation of MLS, requiring a route

processor (RP) and a switch engine (SE). The RP must process a
traffic flows first packet to determine the destination. The SE listens to
the first packet and to the resulting destination, and then sets up a
shortcut entry in its MLS cache. The SE forwards subsequent
packets belonging to the same traffic flow based on shortcut entries in
its cache.
Chapter #
Cisco Public
24
Route caching: This type of MLS also is known by the names

NetFlow LAN switching , flow-based or demand-based switching , and
route once, switch many . The RP must examine each new traffic flow
and set up shortcut entries for the SE. Even if this method isnt used
to forward packets in Cisco IOSbased Catalyst switches, the
technique can still be used to generate traffic flow information and
statistics.
Chapter #
Cisco Public
25

Topology based: The second generation of MLS, utilizing specialized
hardware, is also organized with distinct RP and SE functions. The RP
uses Layer 3 routing information to build and prepopulate a single
database of the entire known network topology. This database
becomes an efficient table lookup in hardware, and is consulted so
that packets can be forwarded at high rates by the SE.
Chapter #
Cisco Public
26

Topology based: This type of MLS is known as Cisco Express
Forwarding (CEF). A routing process running on the switch downloads
the current routing table database into the Forwarding Information
Base (FIB) area of hardware. CEF is discussed in greater detail in
Chapter 11 , Multilayer Switching.
Chapter #
Cisco Public
27

Catalyst switches can use several methods to forward packets based
on Layer 3 and Layer 4 information. The current generation of
Catalyst multilayer switches uses the efficient Cisco Express
Forwarding (CEF) method. This section describes the evolution of
multilayer switching and discusses CEF in detail. Although CEF is
easy to configure and use, the underlying switching mechanisms are
more involved and should be understood.
Chapter #
Cisco Public
28
Traffic Types
Network Management BPDU, CDP, SNMP, RMON, SSH traffic
(for example); low bandwidth
IP Telephony Signaling traffic and encapsulated voice traffic;
low bandwidth
IP Multicast IP/TV and market data applications; intensive
configuration requirements; very high bandwidth
Normal Data File and print services, email, Internet browsing,
database access, shared network applications; low to medium
bandwidth
Scavenger Class All traffic with protocols or patterns that
exceed normal data flows; less than best-effort traffic, such as
peer-to-peer traffic (instant messaging, file sharing, IP phone calls,
video conferencing); medium to high bandwidth
Chapter #
Cisco Public
29
Switch Operation
Chapter #
Cisco Public
30
L2 forwarding table: The frames destination MAC address, into the

content-addressable memory (CAM), or address
Security ACLs: Access control lists (ACLs) can be used to identify frames
according to their MAC addresses, protocol types (for non-IP frames), IP
addresses, protocols, and Layer 4 port numbers.
QoS ACLs: Other ACLs can classify incoming frames according to quality
of service (QoS) parameters
Chapter #
Cisco Public
31
Tables Used in Switching

Content-Addressable
Memory
All Catalyst switch models use a CAM table for Layer 2 switching. As
frames arrive on switch ports, the source MAC addresses are learned and
recorded in the CAM table. The port of arrival and the VLAN both are
recorded in the table, along with a time stamp. If a MAC address learned
on one switch port has moved to a different port, the MAC address and
time stamp are recorded for the most recent arrival port.
Switch(config)# mac address-table aging-time seconds
Switch(config)# mac address-table static mac-address vlan vlan-id interface type

mod/num
Chapter #
Cisco Public
32

Ternary Content-Addressable Memory
The Catalyst IOS Software has two components that are part of the TCAM
operation:
Feature Manager (FM): After an access list has been created or
configured, the Feature Manager software compiles, or merges, the ACEs
into entries in the TCAM table. The TCAM then can be consulted at full
frame-forwarding speed
Switching Database Manager (SDM): On some Catalyst switch models,
the TCAM is partitioned into several areas that support different functions.
The SDM software configures or tunes the TCAM partitions, if needed, to
provide ample space for specific switching functions.
Chapter #
Cisco Public
33

TCAM Example
Chapter #
Cisco Public
34

CAM Table Operation
Often, you need to know where a user with a certain MAC address is
connected. In a large network, discerning at which switch and switch port a
MAC address can be found might be difficult. Start at the networks center,
or core, and display the CAM table entry for the users MAC address. Look
at the switch port shown in the entry and find the neighboring switch
connected to that port using CDP neighbor information. Then move to that
switch and repeat the CAM table query process. Keep moving from switch
to switch until you reach the edge of the network where the MAC address
physically connects.
Chapter #
Cisco Public
35

TCAM Operation
The TCAM in a switch is more or less self-sufficient. Access lists are
compiled or merged automatically into the TCAM, so there is nothing to
configure. The only concept you need to be aware of is how the TCAM
resources are being used. You can use the show platform tcam utilization
EXEC command shown in Example 2-5 to get an idea of the TCAM
utilization. Compare the Used number of entries to the Max value..
Chapter #
Cisco Public
36

Managing Switching Table Sizes
High-end Cisco switches are designed for efficient multilayer switching at
any location within a network. For example, the versatile Catalyst 4500
and 6500 models can be used equally well in the core, distribution, or
access layer because their hardware contains ample switching engines
and table space for any application. Other models, such as the 2960,
3750, and 3850, have a fixed architecture with limited switching table
space. The CAM, FIB, and other tables must all share resources; for one
table to grow larger, the others must grow smaller.
Chapter #
Cisco Public
37
IPv4 SDM Templates and Memory Partitions
Dual IPv4-IPv6 SDM Templates and Memory Partitions
Chapter #
Cisco Public
38
Commands Used to Monitor and Manipulate the CAM Table
Chapter #
Cisco Public
39
Enterprise
Campus Design
Chapter #
Cisco Public
40
Small Campus Network
<200 end devices

Collapsed core
Catalyst 3560 and 2960G switches for access layer
Cisco 1900 and 2900 routers to interconnect branch/WAN
Chapter #
Cisco Public
41
Medium Campus Network

200-1000 end devices
Redundant multilayer switches at distribution layer
Catalyst 4500 or 6500 switches
Chapter #
Cisco Public
42
Large Campus Network
>2000 end users

Stricter adherence to core, distribution, access delineation
Catalyst 6500 switches in core and distribution layers
Nexus 7000 switches in data centers
Division of labor amongst network engineers
Chapter #
Cisco Public
43
Data Center Infrastructure

Core layer high-speed packet switching backplane
Aggregation layer service module integration, default gateway
redundancy, security, load balancing, content switching, firewall, SSL
offload, intrusion detection, network analysis
Access layer connects servers to network
Chapter #
Cisco Public
44
Chapter 2 Summary
Enterprise Campus Network Design, Hierachical
Network Design: Core Layer, Distribution Layer,
Access Layer, Modular Network Design, Layer 2
Switch
Operation,
Layer
Switch
Operation,
Managing Switching Tables, Types of Multilayer

Switching, Route Caching, Topology Based
Note: CEF chapter 11 Switch Multilayer, plane control
Chapter #
Cisco Public
45
Chapter 1 Labs
Lab 2-1Clearing a Switch Connected to a Larger Network
Chapter #
Cisco Public
46
Resources
http://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/A
ug2014/CampusDesignSummary-AUG14.pdf
http://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/A
ug2014/CVD-CampusWiredLANDesignGuide-AUG14.pdf
Chapter #
Cisco Public
47
Chapter #
Cisco Public
48

En SWITCH v7 Ch02

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

En SWITCH v7 Ch02

Caricato da

Copyright:

Formati disponibili

Chapter 2:

Campus Network Design

CCNP R&S SWITCH: Implementing IP Switching

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

Two-Layer Network Hierarchy Emerges

Core Layer Emerges

Traffic Flow Paths Through a Network Hierarchy

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

Hierarchical Design Model

in smaller campus networks, where the cost and scalability of a

Hierarchical Design Model

Hierarchical Design Model

Multilayer Switches in Campus Networks

Multilayer Switches in Campus Networks

Multilayer Switching Miscellany

Catalyst 6500 switches with a

Multilayer Switch Operation

route caching (first-generation MLS) and

Multilayer Switch Operation

Route caching: The first generation of MLS, requiring a route

Multilayer Switch Operation

Route caching: This type of MLS also is known by the names

Multilayer Switch Operation

Multilayer Switch Operation

Multilayer Switch Operation

Layer 2 Switch Operation

L2 forwarding table: The frames destination MAC address, into the

Tables Used in Switching

Switch(config)# mac address-table aging-time seconds

Switch(config)# mac address-table static mac-address vlan vlan-id interface type

Tables Used in Switching

Tables Used in Switching

Managing Switching Tables

Managing Switching Tables

Managing Switching Tables

Managing Switching Tables

IPv4 SDM Templates and Memory Partitions

Dual IPv4-IPv6 SDM Templates and Memory Partitions

Commands Used to Monitor and Manipulate the CAM Table

Small Campus Network

<200 end devices

Medium Campus Network

Large Campus Network

>2000 end users

Data Center Infrastructure

Managing Switching Tables, Types of Multilayer

Potrebbero piacerti anche