Data Center LAN Migration Guide - Juniper Networks

Data Center LAN Migration Guide
Addressing any or all of these trigger events results in deployment of new technology into the access, aggregation,
core, or services tiers of an existing data center network.
Considerations for Introducing an Alternative Network Infrastructure Provider
In some installations, a key consideration when evolving an existing infrastructure is the impact of introducing another
vendor. Organizations can minimize any impact by using the same best practices they employ in a single vendor
network. For example, it is sound practice to test interoperability and feature consistency before an implementation at
any network layer. Many enterprises do this today, since there are often multiple inconsistent versions of an operating
system within a single vendor’s portfolio, or even completely different operating systems within that portfolio. For
example, the firewall or intrusion prevention system (IPS) platforms may have a different OS and interface from the
switching products. Even within a switching portfolio, there may be different operating systems, each supporting
different feature implementations.
It is also sound practice to limit fault domains and contain risks when introducing an additional vendor. This can be
accomplished with a building block design for the target insertion point, when deploying into an existing LAN. This
approach allows for definition of the new insertion as a functional module, testing of the module in proof-of-concept
(PoC) environments before deployment, and clean insertion of the new module into production after testing. As
mentioned earlier, PoC testing is often done as a best practice in a single vendor network as well.
Other steps that can ensure successful insertion of Juniper Networks technology into an existing data center LAN include:
• Training
• Multivendor automation and management tools
Training
The simplicity of Juniper’s implementations typically minimizes the need for extensive training to accompany
deployment; however, Juniper also offers a variety of training resources to accelerate deployments. To start with,
standardization of protocols within the network typically eases introduction, since basic constructs are similar and
interoperability has usually been tested and proven ahead of time by Juniper. Beyond the protocols, differences in
command-line interface (CLI) are usually easier to navigate than people initially think. Time after time, people familiar
with other CLIs find themselves able to make the transition quickly due to the consistent, intuitive nature of Junos
operating system’s implementation (it is easy to learn and use). Junos OS also has a tremendous amount of flexibility
and user support built into it. For example, to ease migration from Cisco’s IOS, there is a Junos OS command to display
a configuration file in a format similar to IOS. Additionally, hands-on training is available in the form of a two-day boot
camp. Customized training can also be mapped to address any enterprise’s specific environment. Training not only
gives an opportunity to raise the project team’s skill level, but also to get experience with any potential configuration
complexities prior to entering the implementation phase of a project.
Junos OS also provides embedded automation capabilities. A library of scripts that automate common operations
tasks is readily available online for viewing and downloading. Categorized by function, the script with the best fit can
easily be found. Refer to the Junos OS Script Library for a complete list: www.juniper.net/us/en/community/junos/
script-automation/library.
Multivendor Automation and Management Tools
In a multivendor environment, it is often critical to establish a foundation of multivendor management tools that
work with existing suppliers as well as with Juniper. There are well established multivendor tools available in the
fault and performance analysis areas. These tools work with equipment from all of the major vendors in the market
including Juniper and other vendors. In the provisioning, configuration, inventory management, and capacity planning
areas, existing third-party tools typically don’t scale or leverage the capabilities and best practices of each vendor’s
equipment. In these situations, it works well to leverage an integrated platform like Junos Space to support the Juniper
infrastructure consistently, and, where possible, to incorporate support for other vendors’ platforms and applications
if the APIs and SDKs of Junos Space can be used to complete that integration. Junos Space provides APIs and SDKs
to customize existing applications, and also enables partners to integrate their applications into this homogenous
application platform.
Copyright © 2012, Juniper Networks, Inc. 29