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 />
IOS Input Page<br />
The main interface for I2J supports upload or cut and paste of IOS configuration files. You can adjust a variety of<br />
translation options, such as outputting verbose IOS comments or consolidating firewall terms. Then use the Translate<br />
button to convert the IOS file into Junos OS. The output is displayed with statistics, the Junos OS configuration output,<br />
and the IOS source with messages.<br />
Figure 11: The I2J input page for converting IOS to Junos OS<br />
<strong>Data</strong> <strong>Center</strong> <strong>Migration</strong> Insertion Points: Best Practices and Installation Tasks<br />
The legacy three-tier design found in many of today’s data centers was depicted in Figure 1. This is the baseline for<br />
layer insertion points addressed in this document. For a specific insertion point such as the access layer, for example,<br />
the recommended <strong>Juniper</strong> best practices pertaining to that layer are provided first. This is then followed by the<br />
recommended preinstallation, installation, and post installation tasks.<br />
Recommended best practices and installation-related tasks focus primarily on currently shipping products and<br />
capabilities.<br />
A dedicated Troubleshooting chapter detailing <strong>Juniper</strong> recommended guidelines for the most commonly encountered<br />
migration and installation issues is also included in this guide.<br />
New Application/Technology Refresh/Server Virtualization Trigger Events<br />
These events are often driven by a lack of capacity in the existing infrastructure to support a new application or service.<br />
They may also occur when an organization is trying to maximize its processor capacity through use of virtual servers.<br />
Redesigns based on these triggers can involve upgrades to either data center access or aggregation tiers (or both) as<br />
described later in this section. They may also involve a redesign across data centers, addressed later in the Business<br />
Continuity and Workload Mobility Trigger Events section. In general, server virtualization poses an interesting set of<br />
design challenges, detailed at the end of this section.<br />
The insertion point for each of these triggers often involves provisioning one or more new Points of Delivery (PODs) or<br />
designated sections of a data center layout, including new switches for the network’s access layer. The new POD(s)<br />
may also include an upgrade of the related aggregation layer which, depending on the requirements, could potentially<br />
later serve as the core in a simplified two-tier design. The process may also involve a core switch/router upgrade or<br />
replacement to increase functionality and bandwidth for each new POD requirement.<br />
For 10GbE server connectivity in a top of rack deployment, <strong>Juniper</strong>’s recommended design would be based on either the<br />
QFX3500 or EX4500. The choice would be based on several factors.<br />
• The QFX3500 would be the preferred platform where sub microsecond latency is required such as a high<br />
performance compute cluster and financial services transactions.<br />
32 Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.