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

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

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

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

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

data center. All rights reserved. Cisco Public 8 . Inc. Cisco Systems. and 7000 Families – NX-OS based modular data center switches Chapter # © 2007 – 2010. 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. 5000.Cisco Switches  Catalyst 6500 Family – used in campus. and core as well as WAN and branch • Up to 13 slots and 16 10-Gigabit Ethernet interfaces • Redundant power supplies.

6500 switches support hardware-based switching with much larger ACLs than 3560 switches.Multilayer Switching Miscellany  ASIC-based (hardware) switching is supported even with QoS and ACLs. 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. Inc. depending on the platform. ASICs integrate onto individual line modules of Catalyst switches to hardware-switch packets in a distributed manner. Cisco Systems. 9 .  Unlike CPUs. All rights reserved.  ASICs on Catalyst switches work in tandem with ternary content addressable memory (TCAM) and packet-matching algorithms for high-speed switching. Chapter # © 2007 – 2010. ASICs scale in switching architectures.

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

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

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

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

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

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

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

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

QoS. Cisco Public 18 . Inc.Distribution Layer  High availability. fast path recovery. Cisco Systems. All rights reserved. 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. load balancing.

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

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

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

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

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

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

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

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

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

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. Cisco Systems. 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. reliability. resource capacity. 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. All rights reserved. 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. and performance Improving the availability. Cisco Public 28 . Inc. configuring.

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

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

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

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

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