Data Center LAN Migration Guide - Juniper Networks

PoC lab could include:
- Interface connectivity
- Trunking and VLAN mapping
- Spanning-tree interoperability with aggregation layer
- QoS policy—classification marking, rate limiting
- Multicast
Data Center LAN Migration Guide
• Provision the new access layer switches into any existing terminal servers for out of band CLI access via SSH.
• Network Automation: The approach to use for automating management in these scenarios depends on which other
vendors’ equipment will be collocated in the data center, what other multivendor tools will be employed (Tivoli,
OpenView, etc.), and how responsibilities will be partitioned across teams for different parts of the infrastructure.
If the insertion is relatively small and contained, and other tools supporting each vendor’s platforms are already
deployed, testing for compatible integration of the Juniper equipment is the best PoC step. However if this insertion
is the start of a longer term, more expanded, strategic deployment of Juniper infrastructure into multiple PODs
and sites (because of the importance of new applications, for example), then it may make sense to also test for
integration of Junos Space into the environment because of the likely value of Space to the installation over time.
Ethernet Design, Network Activate, or other Junos Space data center management applications could be considered.
Space could be deployed as either a physical or a virtual appliance, depending on the allocation of responsibilities
for management and the allocation of resources within the design. VM requirements for running Junos Space are 8
GB RAM and 40 GB hard disk in a production environment. If Junos Space VM is installed for lab/trial purposes, 2 GB
RAM and 8 GB hard disk space is sufficient.
For more information on deploying the Junos Space platform and managing nodes in the Junos Space fabric, please
refer to the technical documentation: www.juniper.net/techpubs/en_US/junos-space1.0/information-products/
index-junos-space.html.
Installation
After comprehensive PoC testing, physical installation of the new POD should be relatively straightforward. As
previously mentioned, if the installation only involves adding new access layer switches to existing racks, switchover
becomes a matter of changing server cables from the old switches to the new ones. If a server refresh is combined
with a switch refresh, those components should be physically installed in the new racks. Uplink interfaces are then
connected to the aggregation switch(es).
Post Installation
Procedures which are similar to installing a new POD within a single vendor environment should be employed after
physical installation is complete. As a best practice, verify:
• Access to the new POD via CLI or network management tools.
• Monitoring and alerting through OSS tools is functional.
• Security monitoring is in place and working. To limit false positives, security tuning should be conducted if a Security
Incident and Event Manager (SIEM) system such as the STRM Series is in place.
• Interface status for server connections and uplinks via CLI or network management tools.
• L2/STP state between access and aggregation tiers.
• QoS consistency between access and aggregation tiers.
• Multicast state (if applicable).
• Traffic is being passed via ping tests and traffic monitoring tools.
• Applications are running as anticipated via end user test, performance management, and other verifications.
Copyright © 2012, Juniper Networks, Inc. 37