Data Center LAN Migration Guide - Juniper Networks

More documents

Recommendations

Info

Data Center LAN Migration Guide Introduction to the Migration Guide IT has become integral to business success in virtually all industries and markets. Today’s data center is the centralized repository of computing resources enabling enterprises to meet their business objectives. Today’s data center traffic flows and performance requirements have changed considerably from the past with the advent of cloud computing and service-oriented architecture (SOA)-based applications. In addition, increased mobility, unified communications, compliance requirements, virtualization, the sheer number of connecting devices, and changing network security boundaries present new challenges to today’s data center managers. Architecting data centers based on old traffic patterns and outdated security models is inefficient and results in lower performance, unnecessary complexity, difficulty in scaling, and higher cost. A simplified, cloud-ready, two-tier data center design is needed to meet these new challenges—without any compromise in performance. Migrating to such a data center network can theoretically take place at any time. Practically speaking, however, most enterprises will not disrupt a production data center except for a limited time window to perform scheduled maintenance and business continuity testing. Luckily and within this context, migration to a simpler two-tier design can begin at various insertion points and proceed in controlled ways in an existing legacy data center architecture. Juniper’s Data Center LAN Migration Guide identifies the most common trigger events at which migration to a simplified design can take place together with design considerations at each network layer for a successful migration. The guide is segmented into two parts. For the business decision maker, Chapter 1: Why Migrate to Juniper will be most relevant. The technical decision maker will find Chapters 2 and 3 most relevant, particularly Chapter 3, which covers the data center “trigger events” that can stimulate a transition and the corresponding insertion points, designs, and best practices associated with pre-install, install, and post-install tasks. Audience While much of the high-level information presented in this document will be useful to anyone making strategic decisions about a data center LAN, this guide is targeted primarily to: • Data center network and security architects evaluating the feasibility of new approaches in network design • Data center network planners, engineers, and operators designing and implementing new data center networks • Data center managers, IT managers, network and security managers planning and evaluating data center infrastructure and security requirements Data Center Architecture and Guide Overview One of the primary ways to increase data center efficiency is to simplify the infrastructure. Most data center networks in place today are based on a three-tier architecture. A simplified two–tier design, made possible by the enhanced performance and more efficient packaging of today’s Ethernet switches, reduces cost and complexity, and increases efficiency without compromising performance. During the 1990s, Ethernet switches became the basic building block of enterprise campus network design. Networks were typically built in a three-tier hierarchical tree structure to compensate for switch performance limitations. Each tier performed a different function and exhibited different form factors, port densities, and throughputs to handle the workload. The same topology was deployed when Ethernet moved into the data center displacing Systems Network Architecture (SNA), DECnet, and token ring designs. 6 Copyright © 2012, Juniper Networks, Inc.
3-TIER LEGACY NETWORK Ethernet Figure 1: Multitier legacy data center LAN Data Center LAN Migration Guide Data Center Interconnect WAN Edge Aggregation Layer This multitiered architecture, shown in Figure 1, worked well in a client/server world where the traffic was primarily “north and south,” and oversubscription ratios at tiers of the network closest to the endpoints (including servers and storage) could be high. However, traffic flows and performance requirements have changed considerably with the advent of applications based on SOA, increased mobility, Web 2.0, unified communications, compliance requirements, and the sheer number of devices connecting to the corporate infrastructure. Building networks today to accommodate 5 to 10 year old traffic patterns is not optimal, and results in lower performance, unnecessary complexity, and higher cost. A new data center network design is needed to maximize IT investment and easily scale to support the new applications and services a high-performance enterprise requires to stay competitive. According to Gartner, “Established LAN design practices were created for an environment of limited switch performance. Today’s highcapacity switches allow new design approaches, thus reducing cost and complexity in campus and data center LANs. The three-tier concept can be discarded, because all switch ports can typically deliver rich functionality without impacting performance.” 1 Copyright © 2012, Juniper Networks, Inc. 7 Core Access Layer Servers NAS FC Storage FC SAN 1 Neil Rikard “Minimize LAN Switch Tiers to Reduce Cost and Increase Efficiency,” Gartner Research ID Number: G00172149 November 17, 2009
Page 1 and 2: DATA CENTER LAN MIGRATION GUIDE
Page 3 and 4: Data Center LAN Migration Guide Cha
Page 5: Copyright © 2010, Juniper Networks
Page 9 and 10: Why Migrate? Data Center LAN Migrat
Page 11 and 12: The Case for a High Performing, Sim
Page 13 and 14: Why Juniper? Data Center LAN Migrat
Page 17 and 18: Junos Pulse SRX5000 Line SRX3000 Li
Page 19 and 20: Data Center LAN Migration Guide A k
Page 21 and 22: Data Center LAN Migration Guide For
Page 23 and 24: MPLS/VPLS for Data Center Interconn
Page 25 and 26: Junos Space applications include: D
Page 29 and 30: Data Center LAN Migration Guide Add
Page 31 and 32: TRIGGER EVENT NETWORK INSERTION LAy
Page 33 and 34: Data Center LAN Migration Guide •
Page 35 and 36: For more detailed information on NI
Page 37 and 38: PoC lab could include: - Interface
Page 39 and 40: Data Center LAN Migration Guide Sig
Page 41 and 42: Data Center LAN Migration Guide The
Page 43 and 44: Installation Tasks Refer to Figure
Page 45 and 46: Data Center LAN Migration Guide In
Page 47 and 48: Data Center LAN Migration Guide •
Page 49 and 50: Data Center LAN Migration Guide At
Page 51 and 52: Data Center LAN Migration Guide Ste
Page 53 and 54: Juniper Professional Services Data
Page 55 and 56: Copyright © 2010, Juniper Networks
Page 57 and 58:
Hardware Data Center LAN Migration
Page 59 and 60:
OSI Layer 3: Network Troubleshootin
Page 61 and 62:
The commands presented in this sect
Page 63 and 64:
Copyright © 2010, Juniper Networks
Page 65 and 66:
Data Center LAN Migration Guide 3.
Page 67 and 68:
Data Center LAN Migration Guide Cop
show all

Data Center LAN Migration Guide - Juniper Networks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?