Data Center LAN Migration Guide - Juniper Networks

More documents

Recommendations

Info

Data Center LAN Migration Guide The scenario for transitioning the core data center network in a design upgrade triggered by a consolidation project should encompass the following kinds of tasks, suited to each organization’s case: • Ensure that the power, cooling, airflow, physical rack space, and cabling required for any new equipment has been designed, ordered, and installed (however your organization breaks down these responsibilities between departments, suppliers, and integrators). • Size the new/upgraded switching platforms using your organization’s policy for additional performance and capacity headroom for future growth. • Design should include a pair of switches that can eventually serve as the new collapsed core/aggregation layer. Initial design can be tuned to the exact role the switches will perform. For example, if they will be focused on pure core functions in the initial phase, they can be focused on capacity/functionality required for that role (e.g., IGP policies and area design appropriate to a core data center switch). If they will be focused on pure aggregation functions initially, design can focus on L2 and L3 interface behaviors appropriate to that role. Or, if they will be performing a blended core/aggregation role (as would be appropriate in many two-tier data center networks), a mix of L2 and L3 functions can be designed to fit the network’s requirements. • If the new switches are aggregating existing access layer switches, industry standard protocols (such as 802.1D, 802.1Q, 802.1s, 802.3ad, etc.) should be used to ensure interoperability. • Configuration checklist should include: - IGP and EGP requirements such as area border roles, routing metrics and policies, and possible route redistributions - L2/L3 domain demarcations › VLAN to VRF mapping › Virtualized service support requirements (VPN/VRF) › Default gateway/root bridge mapping › Hot Standby Routing Protocol (HSRP) to Virtual Router Redundancy Protocol (VRRP) mappings - Uplink specifications › Density › Speeds (number of GbE and 10GbE links) › Link aggregations › Oversubscription ratios - Scaling requirements for MAC addresses - Firewall filters (from IOS ACL mapping) - QoS policies - Multicast topology and performance - Audit/compliance requirements should be clarified and any logging or statistics collection functions designed in. - IOS configurations should be mapped to Junos OS as outlined in the section on IOS to Junos OS translation tools. • As noted earlier, a PoC lab could be set up to test feature consistency and implementation in the new Juniper infrastructure. Testing could include: - Interface connections - Trunking and VLAN mapping - STP interoperability with any existing switches - QoS policy (classification marking; rate limiting) - Multicast 42 Copyright © 2012, Juniper Networks, Inc.
Installation Tasks Refer to Figure 14 when considering the tasks described in this section: Figure 15: Aggregation/core layer insertion point Data Center LAN Migration Guide • If the new aggregation layer switches are part of a new POD that includes new access layer switches, the installation should be straightforward. • If the new aggregation layer switches are part of a replacement for existing legacy switches, it is important to create a fallback position in the event of any unforeseen issues. Typically, EX8200 line switches would be provisioned and deployed as a pair, replacing the legacy switches. • Once the EX8200 line switches are installed, they should be connected to the existing core layer. Again, this scenario is appropriate in cases where the organization initially will maintain its existing three-tier architecture. Appropriate IGP and EGP configurations as identified in the preinstallation configuration checklist would have been provisioned and interoperability verified by checking neighbor state and forwarding tables. • An initial access layer switch’s uplinks would then be connected to the EX8200 line switches and connectivity verified as outlined in the post installation checklist. Once this baseline is established, additional access layer switches would then be migrated to the EX8200 line. Post Installation As previously noted, procedures which are similar to those employed when installing a new aggregation switch in a single vendor environment can be used, after physical installation is complete, to verify successful operations. As a best practice, verify: • Access to new configuration via CLI or network management tools. • Interface status for server connections and uplinks via CLI or network management tools. • L2/STP status between network tiers. • QoS consistency between network tiers. • Multicast state (if applicable). • Traffic passing via ping tests. EX8200 EX8216 “West” EX8200 EX8216 “East” Legacy Switch “West” Legacy Switch “East” Legacy Aggregation Layer Switches and Security Applicances Legacy Access Layer • Application connectivity and flows with statistics or end user tests (or both). Copyright © 2012, Juniper Networks, Inc. 43
Page 1 and 2: DATA CENTER LAN MIGRATION GUIDE
Page 3 and 4: Data Center LAN Migration Guide Cha
Page 5 and 6: Copyright © 2010, Juniper Networks
Page 7 and 8: 3-TIER LEGACY NETWORK Ethernet Figu
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: Data Center LAN Migration Guide The
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 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 65 and 66: Data Center LAN Migration Guide 3.
Page 67 and 68: Data Center LAN Migration Guide Cop

Data Center LAN Migration Guide - Juniper Networks

Create successful ePaper yourself

Delete template?

Save as template?