Introduction to

Enterprise
Campus
Network Design

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 1

Enterprise Network
Core (Backbone) , Campus, Data Center, Branch,
WAN Internet Edge

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 2

© 2006, Cisco Systems, Inc. All rights reserved. 1

Presentation_ID.scr
 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 #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 3

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 #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 4

© 2006, Cisco Systems, Inc. All rights reserved. 2

Presentation_ID.scr
 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 #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 5

Client-Server Applications
 Mail servers
 File servers
 Database servers
 Access to applications is
fast, reliable, and secure

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 6

© 2006, Cisco Systems, Inc. All rights reserved. 3

Presentation_ID.scr
 Client-Enterprise Edge Applications
 Servers on the enterprise
edge, exchanging data
between an organization
and its public servers
 Examples: external mail
servers, e-commerce
servers, and public web
servers
 Security and high
availability are paramount

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 7

Service-Oriented Network Architecture (SONA)

 Application Layer – business and collaboration applications; meet business

requirements leveraging interactive services layer.
 Interactive Services Layer – enable efficient allocation of resources to
applications and business processes through the networked infrastructure.
 Networked Infrastructure Layer – where all IT resources interconnect.

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 8

© 2006, Cisco Systems, Inc. All rights reserved. 4

Presentation_ID.scr
 Borderless Networks
 Enterprise architecture launched by Cisco in October 2009.
 Model enables businesses to transcend borders, access
resources anywhere, embrace business productivity, and
lower business and IT costs.
 Focuses more on growing enterprises into global
companies.
 Technical architecture based on three principles:
• Decoupling hardware from software
• Unifying computation, storage, and network
• Policy throughout the unified system
 Provides a platform for business innovation.
 Serves as the foundation for rich-media communications.

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 9

Enterprise
Campus Design

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 10

© 2006, Cisco Systems, Inc. All rights reserved. 5

Presentation_ID.scr
 Building Access, Building Distribution, and Building
Core Layers
 Building Core Layer: high-
speed campus backbone
designed to switch packets as
fast as possible; provides high
availability and adapts quickly to
changes.
 Building Distribution Layer:
aggregate wiring closets and
use switches to segment
workgroups and isolate network
problems.
 Building Access Layer: grant
user access to network devices.

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 11

Core Layer
 Aggregates distribution layer switches.
 Implements scalable protocols and technologies and load
balancing.
 High-speed layer 3 switching using 10-Gigabit Ethernet.
 Uses redundant L3 links.

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 12

© 2006, Cisco Systems, Inc. All rights reserved. 6

Presentation_ID.scr
 Distribution Layer
 High availability, fast path recovery, load balancing, QoS, and security
 Route summarization and packet manipulation
 Redistribution point between routing domains
 Packet filtering and policy routing to implement policy-based connectivity
 Terminate VLANs
 First Hop Redundancy Protocol

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 13

Access Layer
 High availability – supported by many hardware and software features, such
as redundant power supplies and First Hop Redundancy Protocols (FHRP).
 Convergence – provides inline Power over Ethernet (PoE) to support IP
telephony and wireless access points.
 Security – includes port security, DHCP snooping, Dynamic ARP inspection, IP
source guard.

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 14

© 2006, Cisco Systems, Inc. All rights reserved. 7

Presentation_ID.scr
 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 #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 15

Medium Campus Network

 200-1000 end devices
 Redundant multilayer switches at distribution layer
 Catalyst 4500 or 6500 switches

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 16

© 2006, Cisco Systems, Inc. All rights reserved. 8

Presentation_ID.scr
 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 #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 17

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 #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 18

© 2006, Cisco Systems, Inc. All rights reserved. 9

Presentation_ID.scr
 PPDIOO Lifecycle
Approach to
Network Design
and
Implementation

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 19

PPDIOO Phases
 Prepare – establish organizational requirements.
 Plan – identify initial network requirements.
 Design – comprehensive, based on planning outcomes.
 Implement – build network according to design.
 Operate – maintain network health.
 Optimize – proactive management of network.

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 20

© 2006, Cisco Systems, Inc. All rights reserved. 10

Presentation_ID.scr
 Lifecycle Approach (1)
 Benefits:
• Lowering the total cost of network ownership
• Increasing network availability
• Improving business agility
• Speeding access to applications and services
 Lower costs:
• Identify and validate technology requirements
• Plan for infrastructure changes and resource requirements
• Develop a sound network design aligned with technical requirements
and business goals
• Accelerate successful implementation
• Improve the efficiency of your network and of the staff supporting it
• Reduce operating expenses by improving the efficiency of operational
processes and tools

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 21

Lifecycle Approach (2)

 Improve high availability:
• Assessing the network’s security state and its capability to support the proposed design
• Specifying the correct set of hardware and software releases, and keeping them operational and current
• Producing a sound operations design and validating network operations
• Staging and testing the proposed system before deployment
• Improving staff skills
• Proactively monitoring the system and assessing availability trends and alerts
 Gain business agility:
• Establishing business requirements and technology strategies
• Readying sites to support the system that you want to implement
• Integrating technical requirements and business goals into a detailed design and demonstrating
• that the network is functioning as specified
• Expertly installing, configuring, and integrating system components
• Continually enhancing performance
 Accelerate access to network applications and services:
• Assessing and improving operational preparedness to support current and planned network technologies
and services
• Improving service-delivery efficiency and effectiveness by increasing availability, resource capacity, and
performance
• Improving the availability, reliability, and stability of the network and the applications running on it
• Managing and resolving problems affecting your system and keeping software applications current

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 22

© 2006, Cisco Systems, Inc. All rights reserved. 11

Presentation_ID.scr
 Planning a Network Implementation
 Implementation Components:
• Description of the step
• Reference to design documents
• Detailed implementation guidelines
• Detailed roll-back guidelines in case of failure
• Estimated time needed for implementation
 Summary Implementation Plan – overview of
implementation plan
 Detailed Implementation Plan – describes exact steps
necessary to complete the implementation phase, including
steps to verify and check the work of the network engineers
implementing the plan

Chapter #
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public 23

© 2006, Cisco Systems, Inc. All rights reserved. 12

Presentation_ID.scr