Data Center LAN Migration Guide - Juniper Networks
Data Center LAN Migration Guide - Juniper Networks
Data Center LAN Migration Guide - Juniper Networks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Data</strong> <strong>Center</strong> <strong>LAN</strong> <strong>Migration</strong> <strong>Guide</strong><br />
How <strong>Migration</strong>s Begin<br />
Many enterprises have taken on server, application, and data center consolidations to reduce costs and to increase the<br />
return on their IT investments. To continue their streamlining efforts, many organizations are also considering the use of<br />
cloud computing in their pooled, consolidated infrastructures. While migrating to a next-generation cloud-ready data<br />
center design can theoretically take place at any time, most organizations will not disrupt a production facility except<br />
for a limited time-window to perform scheduled maintenance and continuity testing, or for a suitably compelling<br />
reason whose return is worth the investment and the work.<br />
In Chapter 3 of this guide, we identify a series of such reasons—typically stimulated by trigger events—and the way<br />
these events turn into transitions at various insertion points in the data center network. We also cover the best<br />
practices and steps involved in migration at each of the insertion points presented by a specific trigger event. By<br />
following these steps and practices, it is possible to extend migration to legacy network tiers and move safely towards<br />
a simplified data center infrastructure.<br />
Trigger Events for Change and Their Associated Insertion Points<br />
Change in the data center network is typically determined by the type of event triggering the organization to make<br />
that change. What follows is a short description of trigger events which can stimulate an organization to make the<br />
investments related to these events:<br />
• Provisioning a new area of infrastructure area or Point of Delivery (POD) in an existing data center due to<br />
additional capacity required for new applications and services. The new applications may also have higher<br />
performance requirements that cannot be delivered by the existing infrastructure.<br />
• Technology refresh due to either EOL on a given product line or an upgrade to the latest switching and/or server<br />
technology. A refresh can also be driven by the end of an equipment depreciation cycle, company policy regarding<br />
available headroom capacity, or for adding capacity to meet planned future expansion.<br />
• Infrastructure redesign due to increased use of server virtualization.<br />
• <strong>Data</strong> center consolidation due to merger or acquisition, cost saving initiatives, or moving from an existing colocation<br />
facility. Due to the increased scalability, performance, and high availability requirements, data center<br />
consolidation may also require a technology refresh.<br />
• Business continuity and workload mobility initiatives. Delivering HA and VM/application mobility typically involves<br />
“V<strong>LAN</strong> stretching” within or between data centers.<br />
• Upgrade to the core data center network for higher bandwidth and capacity to support new capabilities such as<br />
server virtualization/workload mobility or higher application performance. This may also be due to a technology<br />
refresh as a result of the retirement of legacy equipment which is at end of life (EOL).<br />
• Need for higher performance and scale in security. Existing security gateways, whether integrated in a chassis<br />
or running as standalone appliances, may not be able to deliver the higher performance required to support the<br />
increased traffic from data center consolidation, growth in connected devices, increased extranet collaboration,<br />
and internal/external compliance and auditing requirements. Server, desktop, and application virtualization may<br />
also drive changes in the security model, to increase the strength of security in the new environments and ease<br />
complexity in management. Enhancements can be made to the core, edge, or virtual server areas of the data center<br />
network to deal with these requirements.<br />
• OnRamp to QFabric: QFabric represents the “1” in <strong>Juniper</strong> <strong>Networks</strong> 3-2-1 architecture, dramatically reducing<br />
complexity in the data center by delivering any-to-any connectivity while lowering capital, management, and<br />
operational expenses. QFabric consists of edge, interconnect, and control devices that work together to create a<br />
high-performance, low latency fabric that unleashes the power of the data center. The QFabric technology also<br />
offers unprecedented scalability with minimal additional overhead, supporting converged traffic and making it<br />
easy for enterprises to run Fibre Channel, Ethernet, and Fibre Channel over Ethernet on a single network. The highperformance,<br />
non-blocking, and lossless QFabric architecture delivers much lower latency than traditional network<br />
architectures--crucial for server virtualization and the high-speed communications that define the modern data<br />
center. The first QFabric product, the <strong>Juniper</strong> <strong>Networks</strong> QFX3500, delivers a 48-port 10GbE top-of-rack switch that<br />
provides low latency, high-speed access for today’s most demanding data center environments. When deployed<br />
with the other components, the QFX3500 offers a fabric-ready edge solution that contributes to the QFabric’s highly<br />
scalable, highly efficient architecture for supporting today’s exponential data center.<br />
28 Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.