You are on page 1of 33

Chapter 1: Analyzing The Cisco Enterprise Campus Architecture

CCNP SWITCH: Implementing IP Switching

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

1

Chapter 1 Objectives
 Describe common campus design options and how design choices affect implementation and support of a campus LAN.  Describe the access, distribution, and core layers.  Describe small, medium, and large campus network designs.  Describe the prepare, plan, design, implement, operate, optimize (PPDIOO) methodology.  Describe the network lifecycle approach to campus design.

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

2

Introduction to Enterprise Campus Network Design

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

3

Enterprise Network       Core (Backbone) Campus Data Center Branch WAN Internet Edge Chapter # © 2007 – 2010. Cisco Public 4 . All rights reserved. Inc. Cisco Systems.

Inc.)  There may be several legal regulations that have an impact on a network’s design. Cisco Public 5 .Regulatory Standards (U. All rights reserved.  US regulations on networks include: • Health Insurance Portability and Accountability Act (HIPAA) • Sarbanes-Oxley Act • “Records to Be Preserved by Certain Exchange Members.S. Brokers and Dealers”: Securities and Exchange Commission (SEC) Rule 17a4 Chapter # © 2007 – 2010. Cisco Systems.

proper high-availability (HA) characteristics result in near-100% uptime.easily supports growth and change. Scaling the network is eased by adding new modules in lieu of complete redesigns. Inc. All rights reserved.change in business is a guarantee for any enterprise. Cisco Public 6 .Campus Designs  Modular . These changes drive campus network requirements to adapt quickly.  Resilient . Chapter # © 2007 – 2010.  Flexible . Cisco Systems.

All rights reserved. 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.Multilayer Switches in Campus Networks  Hardware-based routing using Application-Specific Integrated Circuits (ASICs)  RIP. Cisco Systems. Cisco Public 7 . Inc. OSPF.

data center.Cisco Switches  Catalyst 6500 Family – used in campus. and 7000 Families – NX-OS based modular data center switches Chapter # © 2007 – 2010. Cisco Public 8 . Cisco Systems. Inc. and core as well as WAN and branch • Up to 13 slots and 16 10-Gigabit Ethernet interfaces • Redundant power supplies. All rights reserved. 5000. and supervisor engines • Runs Cisco IOS  Catalyst 4500 Family – used in distribution layer and in collapsed core environments • Up to 10 slots and several 10-Gigabit Ethernet interfaces • Runs Cisco IOS  Catalyst 3560 and 3750 Families – used in fixed-port scenarios at the access and distribution layers  Nexus 2000. fans.

Cisco Public  Catalyst 6500 switches with a Supervisor Engine 720 and a Multilayer Switch Feature Card (MSFC3) must software-switch all packets requiring Network Address Translation. 9 . 6500 switches support hardware-based switching with much larger ACLs than 3560 switches. Inc.  ASICs on Catalyst switches work in tandem with ternary content addressable memory (TCAM) and packet-matching algorithms for high-speed switching.  Unlike CPUs. depending on the platform. ASICs integrate onto individual line modules of Catalyst switches to hardware-switch packets in a distributed manner. ASICs scale in switching architectures. All rights reserved. Chapter # © 2007 – 2010. Cisco Systems.Multilayer Switching Miscellany  ASIC-based (hardware) switching is supported even with QoS and ACLs.

medium to high bandwidth Chapter # © 2007 – 2010. CDP. email. SNMP. Inc. less than best-effort traffic. such as peer-to-peer traffic (instant messaging. Cisco Systems. shared network applications. video conferencing). IP phone calls. RMON. All rights reserved. Cisco Public 10 .Traffic Types  Network Management – BPDU. very high bandwidth  Normal Data – File and print services. low bandwidth  IP Multicast – IP/TV and market data applications. low bandwidth  IP Telephony – Signaling traffic and encapsulated voice traffic. Internet browsing. intensive configuration requirements. file sharing. SSH traffic (for example). low to medium bandwidth  Scavenger Class – All traffic with protocols or patterns that exceed normal data flows. database access.

reliable. and secure Chapter # © 2007 – 2010.Client-Server Applications     Mail servers File servers Database servers Access to applications is fast. All rights reserved. Inc. Cisco Public 11 . Cisco Systems.

e-commerce servers. All rights reserved. Cisco Systems.Client-Enterprise Edge Applications  Servers on the enterprise edge. Inc. Cisco Public 12 . and public web servers  Security and high availability are paramount Chapter # © 2007 – 2010. exchanging data between an organization and its public servers  Examples: external mail servers.

Cisco Systems.  Networked Infrastructure Layer – where all IT resources interconnect. Cisco Public 13 . meet business requirements leveraging interactive services layer. Chapter # © 2007 – 2010.  Interactive Services Layer – enable efficient allocation of resources to applications and business processes through the networked infrastructure.Service-Oriented Network Architecture (SONA)  Application Layer – business and collaboration applications. All rights reserved. Inc.

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

Cisco Public 15 .Enterprise Campus Design Chapter # © 2007 – 2010. Inc. Cisco Systems. All rights reserved.

 Building Access Layer: grant user access to network devices.  Building Distribution Layer: aggregate wiring closets and use switches to segment workgroups and isolate network problems. Inc.Building Access. Building Distribution. Cisco Systems. All rights reserved. Chapter # © 2007 – 2010. Cisco Public 16 . and Building Core Layers  Building Core Layer: highspeed campus backbone designed to switch packets as fast as possible. provides high availability and adapts quickly to changes.

Inc. Chapter # © 2007 – 2010.  High-speed layer 3 switching using 10-Gigabit Ethernet.  Uses redundant L3 links.  Implements scalable protocols and technologies and load balancing. Cisco Public 17 .Core Layer  Aggregates distribution layer switches. All rights reserved. Cisco Systems.

All rights reserved.Distribution Layer  High availability. Cisco Public 18 . Inc. Cisco Systems. 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.

Dynamic ARP inspection. DHCP snooping. such as redundant power supplies and First Hop Redundancy Protocols (FHRP).  Security – includes port security. Inc. Cisco Systems. Chapter # © 2007 – 2010. Cisco Public 19 . All rights reserved.  Convergence – provides inline Power over Ethernet (PoE) to support IP telephony and wireless access points.Access Layer  High availability – supported by many hardware and software features. IP source guard.

All rights reserved. Cisco Public 20 . Inc.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.Medium Campus Network  200-1000 end devices  Redundant multilayer switches at distribution layer  Catalyst 4500 or 6500 switches Chapter # © 2007 – 2010. All rights reserved. Cisco Public 21 . Cisco Systems.

Cisco Public 22 . Cisco Systems. 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. All rights reserved. distribution.Large Campus Network      >2000 end users Stricter adherence to core. Inc.

default gateway redundancy. intrusion detection. SSL offload. network analysis  Access layer – connects servers to network Chapter # © 2007 – 2010. firewall. Inc. Cisco Systems. Cisco Public 23 . All rights reserved. load balancing. security. content switching.Data Center Infrastructure  Core layer – high-speed packet switching backplane  Aggregation layer – service module integration.

Cisco Systems. Inc. All rights reserved.PPDIOO Lifecycle Approach to Network Design and Implementation Chapter # © 2007 – 2010. Cisco Public 24 .

Inc. Cisco Public 25 . Chapter # © 2007 – 2010. Design – comprehensive. Implement – build network according to design. Cisco Systems.PPDIOO Phases       Prepare – establish organizational requirements. All rights reserved. Optimize – proactive management of network. Plan – identify initial network requirements. based on planning outcomes. Operate – maintain network health.

Cisco Public  Developing a sound network design aligned with technical requirements and business goals  Accelerating successful implementation  Improving the efficiency of your network and of the staff supporting it  Reducing operating expenses by improving the efficiency of operational processes and tools 26 . Cisco Systems. Inc.Lifecycle Approach  Lowering the total cost of network ownership  Increasing network availability  Improving business agility  Speeding access to applications and services  Identifying and validating technology requirements  Planning for infrastructure changes and resource requirements Chapter # © 2007 – 2010. All rights reserved.

Cisco Systems. Cisco Public 27 . All rights reserved. Inc.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.

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 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. All rights reserved. Cisco Public 28 . Cisco Systems. Inc. and performance Improving the availability. configuring. reliability. and stability of the network and the applications running on it Managing and resolving problems affecting your system and keeping software applications current  Gain business agility:  Accelerate access to network applications and services: Chapter # © 2007 – 2010.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 integrating system components Continually enhancing performance 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.

including steps to verify and check the work of the network engineers implementing the plan Chapter # © 2007 – 2010. All rights reserved. Cisco Public 29 . Inc.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. Cisco Systems.

Cisco Systems.  Any successful architecture must be based on a foundation of solid design theory and principles.  Implementing the increasingly complex set of businessdriven capabilities and services in the campus architecture is challenging if done in a piecemeal fashion. All rights reserved. Chapter # © 2007 – 2010.  As the network evolves. Inc. new capabilities are added. Cisco Public 30 .Chapter 1 Summary  Evolutionary changes are occurring within the campus network. The adoption of an integrated approach based on solid systems design principles is a key to success. usually driven by application data flows.  Evolution requires careful planning and deployments based on hierarchical designs.

Inc. Cisco Public 31 . Cisco Systems.Chapter 1 Labs  Lab 1-1  Lab 1-2 Clearing a Switch Clearing a Switch Connected to a Larger Network Chapter # © 2007 – 2010. All rights reserved.

All rights reserved.Resources  www.com/en/US/products Chapter # © 2007 – 2010. Cisco Public 32 .cisco. Inc. Cisco Systems.

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