Data Center LAN Migration Guide - Juniper Networks

More documents

Recommendations

Info

Data Center LAN Migration Guide There are two basic options to provision this design: two physically separate servers connected to two separate access layer switches, or two separate Virtual Chassis units in a Juniper deployment as depicted in Figure 11. AGGREGATION / CORE EX82XX EX82XX 802.3ad LAG 802.1q Trunking 802.3ad LAG 802.1q Trunking 802.3ad LAG 802.1q Trunking EX4200 Virtual Chassis EX4200 Virtual Chassis Figure 12: Inverted U design using two physical servers The bold lines show that there are no loops in this upside down or inverted U design. Load balancers are typically used in this design for inbound server traffic as well as Global Load Balancing Protocol on outbound server traffic. The next option is to use NIC teaming within a VMware infrastructure as depicted in Figure 12. AGGREGATION / CORE EX82XX EX82XX 802.3ad LAG 802.1q Trunking EX4200 802.3ad LAG 802.1q Trunking 802.3ad LAG 802.1q Trunking pNIC1 pNIC2 vNIC1 10.0.1.4/24 vNIC2 10.0.2.4/24 EX4200 Figure 13: Inverted U design with NIC teaming Access Access This option, using network interface teaming in a VMware environment, is the more prevalent form of an inverted U design. NIC teaming is a feature of VMware Infrastructure 3 that allows you to connect a single virtual switch to multiple physical Ethernet adapters. A team can share traffic loads between physical and virtual networks and provide passive failover in case of an outage. NIC teaming policies are set at the port group level. 34 Copyright © 2012, Juniper Networks, Inc.
For more detailed information on NIC teaming using VMware Infrastructure 3, refer to: www.vmware.com/technology/virtual-networking/virtual-networks.html www.vmware.com/files/pdf/virtual_networking_concepts.pdf Data Center LAN Migration Guide The main advantages to the inverted U design are that all ports on the aggregation switches have useable bandwidth 100% of the time, traffic flows between access and aggregation are always deterministic, and there is a deterministic latency to all Virtual Chassis connected to a single aggregation or core switch. Redundant Trunk Groups LAN designs using the EX4200 Ethernet Switch with Virtual Chassis technology also benefit from RTG protocol as a built-in, optimized replacement to STP for sub-second convergence and automatic load balancing. RTG is an HA link feature of the EX Series Ethernet Switches that eliminates the need for STP. In fact, STP can’t be provisioned on an RTG link. Ideally implemented on a switch with a dual-home connection, RTG configures one link as active and forwarding traffic, and the other link as blocking and backup to the active link. RTG provides extremely fast convergence in the event of a link failure. It is similar in practice to Rapid Spanning Tree Protocol (RSTP) root and alternate port, but doesn’t require an RSTP configuration. Layer Three Uplinks Another alternative is to use L3 uplinks from the access layer to the aggregation/core switches. This limits L2 domain and VLANs to a single Virtual Chassis. Equal-cost multipath (ECMP), which is included in the base license for L3 OSPF on EX Series data center switches, is used for uplinks. An advanced license is needed if BGP, IS-IS, or Ipv6 are required. Up to 480 servers can be provisioned with one EX4200 Virtual Chassis. This allows applications to maintain L2 adjacency within a single switch, however servers are typically collocated within a single row which is part of the Virtual Chassis. The VLAN boundary is the access layer for low latency application data transfer. Virtual Chassis extension would allow distant servers to be accommodated as well. These servers would be part of a single Virtual Chassis domain. Virtual Chassis Best Practices These best practices should be followed when deploying and operating the EX4200 at the access layer: • When designing a Virtual Chassis configuration, consider a deployment in which ports are distributed across as many switches as possible to provide the highest resiliency and the smallest failure domain. • When possible, place uplink modules in the Virtual Chassis configuration line card switches, and place uplinks in devices which are separated at equal distances by member hop. • Use the virtual management Ethernet (VME) interface as the management interface to configure Virtual Chassis technology options. • Evenly space master and backup switches by member hop when possible. • When installing a Virtual Chassis configuration, explicitly configure the mastership priority of the members that you want to function as the master and backup switches. • When removing a switch from a Virtual Chassis configuration, immediately recycle its member ID so that the ID becomes the next lowest available unused ID. In this way, the replacement switch automatically is assigned that member ID and inherits the configuration of the original switch. • Specify the same mastership priority value for the master and backup switches in a Virtual Chassis configuration. • Configure the highest possible mastership priority value (255) for the master and backup switches. • Place the master and backup switches in separate locations when deploying an extended Virtual Chassis configuration. • For maximum resiliency, interconnect Virtual Chassis member devices in a ring topology. • When changing configuration settings on the master switch, propagate changes to all other switches in the Virtual Chassis configuration via a “commit sync” command. Refer to Juniper’s Virtual Chassis Technology Best Practices Implementation Guide for more information: www.juniper.net/us/en/products-services/switching/ex-series/ex4200/#literature. Copyright © 2012, Juniper Networks, Inc. 35
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: Data Center LAN Migration Guide •
Page 37 and 38: PoC lab could include: - Interface
Page 39 and 40: Data Center LAN Migration Guide Sig
Page 41 and 42: Data Center LAN Migration Guide The
Page 43 and 44: Installation Tasks Refer to Figure
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?