EMC VSPEX with Brocade Networking Solutions for PRIVATE CLOUD

Transcription

1 Proven Infrastructure EMC VSPEX with Brocade Networking Solutions for PRIVATE CLOUD Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabrics, EMC VNXe and EMC Next- Generation Backup EMC VSPEX Abstract This document describes the EMC VSPEX Proven Infrastructure with Brocade VDX networking for private cloud deployments with Microsoft Hyper-V and EMC VNXe for up to 100 virtual machines using iscsi Storage. October, 2013

2 Copyright 2013 EMC Corporation. All rights reserved. Published in the USA. Published October 2013 EMC believes the information in this publication is accurate of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC 2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered, or to be offered, by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup Part Number H EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

3 Contents Chapter 1 Executive Summary13 Introduction Target audience Document purpose Business needs Chapter 2 Solution Overview 17 Introduction Virtualization Compute Network Storage Chapter 3 Solution Technology Overview 21 Overview Summary of key components Virtualization Overview Microsoft Hyper-V Microsoft System Center Virtual Machine Manager (SCVMM) High Availability with Hyper-V Failover Clustering EMC Storage Integrator Compute Network Overview Brocade VDX Ethernet Fabric switch series Server and Storage Virtualization Automation Support Storage EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC 3

4 Contents Overview EMC VNXe series Backup and recovery EMC Avamar Other technologies EMC XtemSW Cache (Optional) Chapter 4 Solution Architecture Overview 33 Solution Overview Solution architecture Overview Architecture for up to 50 virtual machines Architecture for up to 100 virtual machines Key components Hardware resources Software resources Server configuration guidelines Overview Hyper-V memory virtualization Memory configuration guidelines Brocade network configuration guidelines Overview VLAN Enable jumbo frames MC/S Link Aggregation Brocade Virtual Link Aggregation Group (vlag) Brocade Inter-Switch Link (ISL) Trunks Equal-Cost Multipath (ECMP) Pause Flow Control Storage configuration guidelines Overview Hyper-V storage virtualization for VSPEX Storage layout for 50 virtual machines Storage layout for 100 virtual machines High availability and failover Overview Virtualization layer Compute layer EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

5 Contents Brocade VDX Network layer Storage layer Backup and recovery configuration guidelines Overview Backup characteristics Backup layout for up to100 virtual machines Sizing guidelines Reference workload Overview Defining the reference workload Applying the reference workload Overview Example 1: Custom-built application Example 2: Point of sale system Example 3: Web server Example 4: Decision-support database Summary of examples Implementing the reference architectures Overview Resource types CPU resources Memory resources Brocade network resources Storage resources Implementation summary Quick assessment Overview CPU requirements Memory requirements Storage performance requirements I/O operations per second (IOPs) I/O size I/O latency Storage capacity requirements Determining equivalent Reference virtual machines Fine tuning hardware resources Chapter 5 VSPEX Configuration Guidelines 71 Overview EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 5

6 Contents Pre-deployment tasks Overview Deployment prerequisites Customer configuration data Prepare and Configure Brocade VDX switches Overview Brocade VDX Switch Platform Considerations Prepare Brocade Network Infrastructure Complete Network Cabling Brocade VDX 6710 and 6720 Switch Configuration Summary Brocade VDX 6710 Configuration Step 1: Verify VDX NOS Licenses Step 2: Assign and Verify VCS ID and RBridge ID Step 3: Assign Switch Name Step 4: VCS Fabric ISL Port Configuration Step 5: Create required VLANs Step 6: Create vlag for Microsoft Server Step 7: Configure Switch Interfaces for VNXe Step 8: Connecting the VCS Fabric to an existing Infrastructure through Uplinks Step 9 - Configure MTU and Jumbo Frames Step 10 - AMPP configuration for live migrations Brocade VDX 6720 Configuration Step 1: Verify VDX NOS Licenses Step 2: Assign and Verify VCS ID and RBridge ID Step 3: Assign Switch Name Step 4: VCS Fabric ISL Port Configuration Step 5: Create required VLANs Step 6: Create vlag for Microsoft Server Step 7: Configure Switch Interfaces for VNXe Step 8: Connecting the VCS Fabric to an existing Infrastructure through Uplinks Step 9 - Configure MTU and Jumbo Frames Step 10 - AMPP configuration for live migrations Prepare and configure storage array Overview VNXe configuration Provision storage for iscsi datastores EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

7 Contents Install and configure Hyper-V hosts Overview Install Hyper-V and configure failover clustering Configure Windows host networking Publish VNXe datastores to Hyper-V Connect Hyper-V datastores Plan virtual machine memory allocations Install and configure SQL server database Overview Create a virtual machine for Microsoft SQL server Install Microsoft Windows on the virtual machine Install SQL Server Configure SQL Server for SCVMM System Center Virtual Machine Manager server deployment Overview Create a SCVMM host virtual machine Install the SCVMM guest OS Install the SCVMM server Install the SCVMM Management Console Install the SCVMM agent locally on a host Add a Hyper-V cluster into SCVMM Create a virtual machine in SCVMM Create a template virtual machine Deploy virtual machines from the template virtual machine Summary Chapter 6 Validating the Solution 121 Overview Post-install checklist Deploy and test a single virtual server Verify the redundancy of the solution components Appendix A Bill of Materials 125 Bill of materials Appendix B Customer Configuration Data Sheet 129 Customer configuration data sheet Appendix C References 133 References EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 7

8 Contents EMC documentation Other documentation Appendix D About VSPEX 135 About VSPEX Appendix E Validation with Microsoft Hyper-V Fast Track v3 137 Overview Business case for validation Process requirements Step one: Core prerequisites Step two: Select the VSPEX Proven Infrastructure platform Step three: Define additional Microsoft Hyper-V Fast Track Program components Step four: Build a detailed Bill of Materials Step five: Test the environment Step six: Document and publish the solution Additional resources EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

9 Figures Figure 1. VSPEX private cloud components Figure 2. Compute layer flexibility Figure 3. Example of a highly available network design Figure 4. Logical architecture for 50 virtual machines Figure 5. Logical architecture for 100 virtual machines Figure 6. Hypervisor memory consumption Figure 7. Required networks Figure 8. Hyper-V virtual disk types Figure 9. Storage layout for 50 virtual machines Figure 10. Storage layout for 100 virtual machines Figure 11. High Availability at the virtualization layer Figure 12. Redundant power supplies Figure 13. Network layer High Availability Figure 14. VNXe series High Availability Figure 15. Resource pool flexibility Figure 16. Required resource from the Reference virtual machine pool.. 65 Figure 17. Aggregate resource requirements from the Reference virtual machine pool Figure 18. Customizing server resources Figure 19. Sample Ethernet network architecture Figure 20. VCS Fabric port types Figure 21. VDX Figure 22. Creating VLANs Figure 23. Example VCS/VDX network topology with Infrastructure connectivity Figure 24. Port types Figure 25. VDX Figure 26. VDX Figure 27. Creating VLANs Figure 28. Example VCS/VDX network topology with Infrastructure connectivity EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 9

10 Figures 10 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

11 Tables Table 1. VNXe customer benefits...29 Table 2. Solution hardware...38 Table 3. Solution software...40 Table 4. Network hardware...43 Table 5. Storage hardware...47 Table 6. Backup profile characteristics...54 Table 7. Virtual machine characteristics...56 Table 8. Blank worksheet row...62 Table 9. Reference virtual machine resources...64 Table 10. Example worksheet row...65 Table 11. Example applications...66 Table 12. Server resource component totals...68 Table 13. Blank customer worksheet...69 Table 14. Deployment process overview...72 Table 15. Tasks for pre-deployment...73 Table 16. Deployment prerequisites checklist...74 Table 17. Brocade VDX 6710 and VDX 6720 Configuration Steps...78 Table 18. Tasks for storage configuration Table 19. Tasks for server installation Table 20. Tasks for SQL server database setup Table 21. Tasks for SCVMM configuration Table 22. Tasks for testing the installation Table 23. List of components used in the VSPEX solution for 50 virtual Table 24. machines List of components used in the VSPEX solution for 100 virtual machines Table 25. Common server information Table 26. Hyper-V server information Table 27. Array information Table 28. Network infrastructure information Table 29. VLAN information Table 30. Service accounts Table 31. Hyper-V Fast Track component classification EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 11

12 Tables 12 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

13 Chapter 1 Executive Summary This chapter presents the following topics: Introduction 14 Target audience 14 Document purpose 14 Business needs 15 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 13

14 Executive Summary Introduction Target audience Document purpose EMC VSPEX with Brocade networking solutions are validated and modular architectures built with proven best-of-breed technologies to create complete virtualization solutions on compute, networking, and storage layers. VSPEX helps to reduce virtualization planning and configuration burdens. When embarking on server virtualization, virtual desktop deployment, or IT consolidation, VSPEX accelerates your IT Transformation by enabling faster deployments, choice, greater efficiency, and lower risk. This document is a comprehensive guide to the technical aspects of this solution. Server capacity is provided in generic terms for required minimums of CPU, memory, and network interfaces; the customer can select the server hardware that meet or exceed the stated minimums. The reader of this document is expected to have the necessary training and background to install and configure Microsoft Hyper-V, Brocade VDX series switches, EMC VNXe series storage systems, and associated infrastructure as required by this implementation. The document provides external references where applicable. The reader should be familiar with these documents. Readers should also be familiar with the infrastructure and database security policies of the customer installation. Users focusing on selling and sizing a Microsoft Hyper-V private cloud infrastructure should pay particular attention to the first four chapters of this document. After purchase, implementers of the solution can focus on the configuration guidelines in Chapter 5, the solution validation in Chapter 6, and the appropriate references and appendices. This document serves as an initial introduction to the VSPEX architecture, an explanation on how to modify the architecture for specific engagements and instructions on how to deploy the system effectively. The VSPEX with Brocade VDX private cloud architecture provides the customer with a modern system capable of hosting a large number of virtual machines at a consistent performance level. This solution runs on the Microsoft Hyper-V virtualization layer backed by the highly available VNX family storage. The compute and network components are customer-definable, and should be redundant and sufficiently powerful to handle the processing and data needs of the virtual machine environment. 14 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

15 Executive Summary Business needs The 50 and 100 virtual machines environments are based on a defined reference workload. Because not every virtual machine has the same requirements, this document contains methods and guidance to adjust your system to be cost-effective when deployed. A private cloud architecture is a complex system offering. This document facilitates the setup by providing upfront software and hardware material lists, step-by-step sizing guidance and worksheets, and verified deployment steps. When the last component is installed, there are validation tests to ensure that your system is up and running properly. Following the procedures defined in this document ensures an efficient and painless journey to the cloud. Customers require a scalable, tiered, and highly available infrastructure on which to deploy their business and mission-critical applications. Several new technologies are available to assist customers in consolidating and virtualizing their server infrastructure, but customers need to know how to use these technologies to maximize the investment, support service-level agreements, and reduce the total cost of ownership (TCO). This solution addresses the following challenges: Availability: Stand-alone servers incur downtime for maintenance or unexpected failures. Clusters of redundant stand-alone nodes are inefficient in the use of CPU, disk, and memory resources. Server management and maintenance: Individually maintained servers require significant repetitive activities for monitoring, problem resolution, patching, and other common activities. Therefore, the maintenance is labor intensive, costly, error-prone, and inefficient. Security, downtime, and outage risks are elevated. Ease of solution deployment: While small and medium businesses (SMB) must address the same IT challenges as larger enterprises, the staffing levels, experience, and training are generally more limited. IT generalists are often responsible for managing the entire IT infrastructure, and reliance is placed on third-party sources for maintenance or other tasks. The perceived complexity of the IT function raises fear of risk and may block the adoption of new technology. Therefore, the simplicity of deployment and management are highly valued. Network performance and resiliency: Networking is added locally to provide connectivity between physical servers & storage and existing infrastructure. Network is sized for 1 & 10 GbE performance sizing requirements and is deployed in a HA dual fabric for resiliency. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 15

16 Executive Summary Storage efficiency: Storage that is added locally to physical servers or provisioned directly from a shared resource or array often leads to overprovisioning and waste. Backup: Traditional backup approaches are slow and frequently unreliable. There tends to be inflection points (or plateaus) in the virtualization adoption curve when the number of virtual machines increases from a few to 100 or more. With a few virtual machines, the situation can be manageable and most organizations can get by with existing tools and processes. However, when the virtual environment grows, the backup and recovery processes often become the limiting factors in the deployment. 16 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

17 Chapter 2 Solution Overview This chapter presents the following topics: Introduction 18 Virtualization 18 Compute 18 Network 19 Storage 19 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 17

18 Solution Overview Introduction Virtualization Compute The EMC VSPEX private cloud for Microsoft Hyper-V with Brocade VDX solution provides a complete system architecture capable of supporting up to 100 virtual machines with a redundant server/network topology and highly available storage. The core components that make up this particular solution are virtualization, storage, server, compute, and networking. Microsoft Hyper-V is a leading virtualization platform in the industry. For years, Hyper-V has provided flexibility and cost savings to end users by consolidating large, inefficient server farms into nimble, reliable cloud infrastructures. Features like Live Migration which enables a virtual machine to move between different servers with no disruption to the guest operating system, and Dynamic Optimization which performs Live Migration automatically to balance loads, make Hyper-V a solid business choice. With the release of Windows Server 2012, a Microsoft virtualized environment can host virtual machines with up to 64 virtual CPUs and 1 TB of virtual RAM. VSPEX provides the flexibility to design and implement your choice of server components. The infrastructure must conform to the following attributes: Sufficient processor cores and memory to support the required number and types of virtual machines Sufficient network connections to enable redundant connectivity to the system switches Excess capacity to withstand a server failure and failover in the environment 18 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

19 Solution Overview Network Brocade VDX switches with VCS Fabric Technology enables the implementation of a high performance, efficient, and resilient network with this VSPEX solution. The Brocade VDX switching infrastructure provides the following attributes: Redundant network links for the hosts, switches, and storage. Architecture for Traffic isolation based on industry-accepted best practices. Support for link aggregation. High utilization and high availability networking Virtualization automation Storage The EMC VNX storage family is the leading shared storage platform in the industry. VNX provides both file and block access with a broad feature set which makes it an ideal choice for any private cloud implementation. The following VNXe storage components are sized for the stated reference architecture workload: Host adapter ports Provide host connectivity via fabric into the array. Storage Processors The compute components of the storage array, which are used for all aspects of data moving into, out of, and between arrays along with protocol support. Disk drives Disk spindles that contain the host/application data and their enclosures. The 50 and 100 virtual machine Hyper-V private cloud solutions discussed in this document are based on the VNXe3150 and VNXe3300 storage arrays respectively. VNXe3150 can support a maximum of 100 drives and VNXe3300 can host up to 150 drives. The EMC VNXe series supports a wide range of business class features ideal for the private cloud environment, including: Thin Provisioning Replication Snapshots File Deduplication and Compression Quota Management EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 19

20 Solution Overview 20 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

21 Chapter 3 Solution Technology Overview This chapter presents the following topics: Overview 22 Summary of key components 23 Virtualization 24 Compute 25 Network 27 Storage 29 Backup and recovery 30 Other technologies 30 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 21

22 Solution Technology Overview Overview This solution uses the EMC VNXe series, Brocade VDX switches with VCS Fabric technology, and Microsoft Hyper-V to provide storage, network, and server hardware consolidation in a private cloud. The new virtualized infrastructure is centrally managed to provide efficient deployment and management of a scalable number of virtual machines and associated shared storage. Figure 1 depicts the general solution components. Figure 1. VSPEX private cloud components These components are described in more detail in the following sections. 22 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

23 Solution Technology Overview Summary of key components This section briefly describes the key components of this solution. Virtualization The virtualization layer enables the physical implementation of resources to be decoupled from the applications that use them. In other words, the application view of the available resources is no longer directly tied to the hardware. This enables many key features in the private cloud concept. Compute The compute layer provides memory and processing resources for the virtualization layer software, and for the needs of the applications running within the private cloud. The VSPEX program defines the minimum amount of compute layer resources required, and enables the customer to implement the requirements using any server hardware that meets these requirements. Network Brocade VDX switches, with VCS Fabric technology; connect the users of the Private Cloud to the resources in the cloud and the storage layer to the compute layer. EMC VSPEX solutions with Brocade VDX switches provide the required connectivity for the solution and general guidance on network architecture. The EMC VSPEX solutions also enable the customer to implement a solution that provides a cost effective, resilient, and operationally efficient virtualization platform. Storage The storage layer is critical for the implementation of the private cloud. With multiple hosts to access shared data, many of the use cases defined in the private cloud concept can be implemented. The EMC VNXe storage family used in this solution provides highperformance data storage while maintaining high availability. Backup and recovery The optional backup and recovery components of the solution provide data protection when the data in the primary system is deleted, damaged, or otherwise unusable. The Solution architecture section provides details on all the components that make up the reference architecture. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 23

24 Solution Technology Overview Virtualization Overview Microsoft Hyper-V Virtualization enables greater flexibility in the application layer by potentially eliminating hardware downtime for maintenance, and enabling the physical capability of the system to change without affecting the hosted applications. In a server virtualization or private cloud use case, it enables multiple independent virtual machines to share the same physical hardware, rather than being directly implemented on dedicated hardware. Microsoft Hyper-V, a Windows Server role that was introduced in Windows Server 2008, transforms or virtualizes computer hardware resources, including CPU, memory, storage, and network. This transformation creates fully functional virtual machines that run their own operating systems and applications just like physical computers. Hyper-V and Failover Clustering provide a high-availability virtualized infrastructure along with Cluster Shared Volumes (CSVs). Live Migration and Live Storage Migration enable seamless migration of virtual machines from one Hyper-V server to another and stored files from one storage system to another, with minimal performance impact. Microsoft System Center Virtual Machine Manager (SCVMM) SCVMM is a centralized management platform for the virtualized datacenter. With SCVMM, administrators can configure and manage the virtualization host, networking, and storage resources in order to create and deploy virtual machines and services to private clouds. When deployed, SCVMM greatly simplifies provisioning, management and monitoring of the Hyper-V environment. High Availability with Hyper-V Failover Clustering Hyper-V achieves high availability by using the Windows Server 2012 Failover Clustering feature. High availability is impacted by both planned and unplanned downtime, and Failover Clustering can significantly increase the availability of virtual machines in both situations. Windows Server 2012 Failover Clustering is configured on the Hyper-V host so that virtual machines can be monitored for health and moved between nodes of the cluster. This configuration has the following key advantages: If the physical host server that Hyper-V and the virtual machines are running on must be updated, changed, or rebooted, the virtual machines can be moved to other nodes of the cluster. You can move the virtual machines back after the original physical host server is back to service. If the physical host server that Hyper-V and the virtual machines are running on fails or is significantly degraded, the other members of the Windows Failover Cluster take over the ownership of the virtual machines and bring them online automatically. 24 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

25 Solution Technology Overview If the virtual machine fails, it can be restarted on the same host server or moved to another host server. Since Windows 2012 Server Failover Cluster detects this failure, it automatically takes recovery steps based on the settings in the resource properties of the virtual machine. Downtime is minimized because of the detection and recovery automation. EMC Storage Integrator EMC Storage Integrator (ESI) is an agent-less, no-charge plug-in that enables application-aware storage provisioning for Microsoft Windows server applications, Hyper-V, VMware, and Xen Server environments. Administrators can easily provision block and file storage for Microsoft Windows or for Microsoft SharePoint sites by using wizards in ESI. ESI supports the following functions: Provisioning, formatting, and presenting drives to Windows servers Provisioning new cluster disks and adding them to the cluster automatically Provisioning shared CIFS storage and mounting it to Windows servers Provisioning SharePoint storage, sites, and databases in a single wizard Compute The choice of a server platform for an EMC VSPEX infrastructure is not only based on the technical requirements of the environment, but on the supportability of the platform, existing relationships with the server provider, advanced performance and management features, and many other factors. For this reason, EMC VSPEX solutions are designed to run on a wide variety of server platforms. Instead of requiring a given number of servers with a specific set of requirements, VSPEX documents a number of processor cores and an amount of RAM that must be achieved. This can be implemented with 2 or 20 servers and still be considered the same VSPEX solution. In the example shown in Figure 2, assume that the compute layer requirements for a given implementation are 25 processor cores, and 200 GB of RAM. One customer might want to implement this solution using white-box servers containing 16 processor cores and 64 GB of RAM, while a second customer chooses a higher-end server with 20 processor cores and 144 GB of RAM. The first customer needs four of the servers they chose, while the second customer needs two. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 25

26 Solution Technology Overview Figure 2. Compute layer flexibility Note To enable high availability at the compute layer, each customer needs one additional server to ensure that the system can maintain business operations if a server fails. The following best practices apply to the compute layer: Use a number of identical or at least compatible servers. VSPEX implements hypervisor level high-availability technologies that may require similar instruction sets on the underlying physical hardware. By implementing VSPEX on identical server units, you can minimize compatibility problems in this area. When implementing high availability on the hypervisor layer, the largest virtual machine you can create is constrained by the smallest physical server in the environment. 26 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

27 Solution Technology Overview Implement the available high availability features in the virtualization layer, and ensure that the compute layer has sufficient resources to accommodate at least single-server failures. This enables the implementation of minimal-downtime upgrades and tolerance for single-unit failures. Within the boundaries of these recommendations and best practices, the compute layer for EMC VSPEX can be flexible to meet your specific needs. The key constraint is that you provide sufficient processor cores and RAM per core to meet the needs of the target environment. Network Overview Brocade VDX Ethernet Fabric switch series The VSPEX with Brocade VDX networking validated solution uses virtual local area networks (VLANs) to segregate network traffic of VSPEX reference architecture for iscsi storage traffic to improve throughput, manageability, application separation, high availability, and security. The Brocade VDX networking solution provides redundant network links for each Microsoft Hyper-V Windows server applications, Hyper-V, the VNXe storage array, switch interconnect ports, and customer infrastructure uplink ports. If a link is lost with any of the Brocade VDX network infrastructure ports, the link fails over to another port. All network traffic is distributed across the active links. The Brocade VDX with VCS Fabrics helps simplify networking infrastructures through innovative technologies and VSPEX infrastructure topology design. Brocade VDX 6710/6720 switches support this strategy by simplifying network architecture and deployment while increasing network performance and resiliency with Ethernet fabrics. Brocade VDX with VCS Fabric technology supports active active links for all traffic from the virtualized compute servers to the EMC VNXe storage arrays. The Brocade VDX provides a network with high availability and redundancy by using link aggregation for EMC VNXe storage array. The Brocade network switch infrastructure provides redundant network links for each Hyper-V host, the storage array, the switch interconnect ports, and the switch uplink ports. This configuration provides both redundancy and additional network bandwidth. Automatic and transparent failover is provided using the Brocade VDX networking solution infrastructure or deploying it alongside other components of the solution. Figure 3 shows an example of the highly available network topology. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 27

28 Solution Technology Overview Figure 3. Example of a highly available network design Brocade VDX with VCS Fabric technology supports active active links for all traffic from the virtualized compute servers to the EMC VNXe storage arrays. EMC unified storage platforms provide network high availability or redundancy by using link aggregation. Link aggregation enables multiple active Ethernet connections to appear as a single link with a single MAC address, and potentially multiple IP addresses. In this solution, Link Aggregation Control Protocol (LACP) is configured on VNXe, combining multiple Ethernet ports into a single virtual device. If a link is lost in the Ethernet port, the link fails over to another port. All network traffic is distributed across the active links. Server and Storage Virtualization Automation Support Brocade VCS Fabric technology offers unique features to support virtualized server and storage environments. Brocade network Hypervisor automation; for example, provides secure connectivity and full visibility to virtualized server resources with dynamic learning and activation of port profiles. With configuration of port profiles, the VDX switches support Hyper-V mobility between Microsoft Windows servers. 28 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

29 Solution Technology Overview Storage Overview EMC VNXe series The storage layer is also a key component of any Cloud Infrastructure solution that stores and serves data generated by application and operating systems within the datacenter. A centralized storage platform often increases storage efficiency, management flexibility, and reduces total cost of ownership. In this VSPEX solution, EMC VNXe Series is used for providing virtualization at the storage layer. EMC VNX family is optimized for virtual applications delivering industryleading innovation and enterprise capabilities for file and block storage in a scalable, easy-to-use solution. This next-generation storage platform combines powerful and flexible hardware with advanced efficiency, management, and protection software to meet the demanding needs of today s enterprises. The VNXe series is powered by the Intel Xeon processors, for intelligent storage that automatically and efficiently scales in performance, while ensuring data integrity and security. The VNXe series is purpose-built for IT managers in smaller environments and the VNX series is designed to meet the high-performance, highscalability requirements of midsize and large enterprises. Table 1 shows the customer benefits. Table 1. Feature VNXe customer benefits Next-generation unified storage, optimized for virtualized applications Capacity optimization features including compression, deduplication, thin provisioning, and application-centric copies High availability, designed to deliver five 9s availability Simplified management with EMC Unisphere for a single management interface for all network-attached storage (NAS), storage area network (SAN), and replication needs EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 29

30 Solution Technology Overview Software Suites Local Protection Suite Increases productivity with snapshots of production data. Remote Protection Suite Protects data against localized failures, outages, and disasters. Application Protection Suite Automates application copies and provides replica management. Security and Compliance Suite Keeps data safe from changes, deletions, and malicious activity. Software Packs Backup and recovery VNXe Total Value Pack Includes the Remote Protection, Application Protection and Security and Compliance Suite. EMC Avamar EMC backup and recovery solutions EMC Avamar Business Edition and EMC Data Domain - deliver the protection confidence and efficiency needed to accelerate deployment of VSPEX Private Clouds. Other technologies Our solutions are proven to reduce backup times by 90% and speed recoveries with single step restore for worry-free protection. And our protection storage systems add another layer of assurance, with end-toend verification and self-healing for ensured recovery. Our solutions also deliver big saving. With industry-leading deduplication, you can reduce backup storage by 10-30x, backup management time by 81%, and WAN bandwidth by 99% for efficient DR delivering a 7-month payback on average. You'll be able to scale simply and efficiently as your environment grows. In addition to the required technical components for EMC VSPEX solutions, other technologies may provide additional value depending on the specific use case. These include, but are not limited to the technologies listed below. EMC XtemSW Cache (Optional) EMC XtemSW Cache TM is a server Flash caching solution that reduces latency and increases throughput to improve application performance by using intelligent caching software and PCIe Flash technology. 30 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

31 Server-side Flash caching for maximum speed Solution Technology Overview XtremSW Cache software caches the most frequently referenced data on the server-based PCIe card, thereby putting the data closer to the application. XtremSW Cache caching optimization automatically adapts to changing workloads by determining which data is most frequently referenced and promoting it to the server Flash card. This means that the hottest or most active data automatically resides on the PCIe card in the server for faster access. XtremSW Cache offloads the read traffic from the storage array, which allows it to allocate greater processing power to other workloads. While one workload is accelerated with XtremSW Cache, the array s performance for other workloads is maintained or even slightly enhanced. Write-through caching to the array for total protection XtemSW Cache accelerates reads and protects data by using a writethrough cache to the storage to deliver persistent high availability, integrity, and disaster recovery. Application agnostic XtemSW Cache is transparent to applications, so no rewriting, retesting, or recertification is required to deploy XtemSW Cache in the environment. Minimum impact on system resources XtremSW Cache does not require a significant amount of memory or CPU cycles, as all flash and wear-leveling management is done on the PCIe card, and does not use server resources. However, unlike other PCIe solutions, there is no significant overhead from using XtremSW Cache on server resources. XtemSW Cache creates the most efficient and intelligent I/O path from the application to the datastore, which results in an infrastructure that is dynamically optimized for performance, intelligence, and protection for both physical and virtual environments. XtemSW Cache active/passive clustering support XtemSW Cache clustering scripts configuration ensures that stale data is never retrieved. The scripts use cluster management events to trigger a mechanism that purges the cache. The XtemSW Cache-enabled active/passive cluster ensures data integrity, and accelerates application performance. XtemSW Cache performance considerations The following are the XtemSW Cache performance considerations: On a write request, XtemSW Cache first writes to the array, then to the cache, and then completes the application I/O. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 31

32 Solution Technology Overview Note On a read request, XtemSW Cache satisfies the request with cached data, or, when the data is not present, retrieves the data from the array, writes it to the cache, and then returns it to the application. The trip to the array can be in the order of milliseconds, therefore the array limits how fast the cache can work. As the number of writes increases, XtemSW Cache performance decreases. XtemSW Cache is most effective for workloads with a 70 percent, or more, read/write ratio, with small, random I/O (8 K is ideal). I/O greater than 128 K will not be cached in XtemSW Cache v1.5. For more information, refer to the XtemSW Cache Installation and Administration Guide v EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

33 Chapter 4 Solution Architecture Overview This chapter presents the following topics: Solution Overview 34 Solution architecture 34 Server configuration guidelines 40 Brocade network configuration guidelines 43 Storage configuration guidelines 47 High availability and failover 51 Backup and recovery configuration guidelines 54 Sizing guidelines 55 Reference workload 56 Applying the reference workload 57 Implementing the reference architectures 59 Quick assessment 62 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 33

34 Solution Architecture Overview Solution Overview Solution architecture VSPEX Proven Infrastructure solutions are built with proven best-of-breed technologies to create a complete virtualization solution that enables you to make an informed decision when choosing and sizing the hypervisor, compute, networking, and storage layers. VSPEX eliminates virtualization planning and configuration burdens by leveraging extensive interoperability, functional, and performance testing by EMC. VSPEX accelerates your IT Transformation to cloud-based computing by enabling faster deployment, more choice, higher efficiency, and lower risk. This section is intended to be a comprehensive guide to the major aspects of this solution. Server capacity is specified in generic terms for required minimums of CPU, memory, and network interfaces; the customer is free to select the server and networking hardware that meet or exceed the stated minimums. The specified storage architecture, along with a system meeting the server and network requirements outlined, is validated by EMC to provide high levels of performance while delivering a highly available architecture for your private cloud deployment. Each VSPEX Proven Infrastructure balances the storage, network, and compute resources needed for a set number of virtual machines, which have been validated by EMC. In practice, each virtual machine has its own set of requirements that rarely fit a predefined idea of what a virtual machine should be. In any discussion about virtual infrastructures, it is important to first define a reference workload. Not all servers perform the same tasks, and it is impractical to build a reference that takes into account every possible combination of workload characteristics. Overview The VSPEX Proven Infrastructure for Microsoft Hyper-V private clouds with EMC VNXe is validated at two different points of scale, one with up to 50 virtual machines, and the other with up to 100 virtual machines. The defined configurations form the basis of creating a custom solution. Note VSPEX uses the concept of a Reference Workload to describe and define a virtual machine. Therefore, one physical or virtual server in an existing environment may not be equal to one virtual machine in a VSPEX solution. Evaluate your workload in terms of the reference to achieve an appropriate point of scale. 34 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

35 Solution Architecture Overview Architecture for up to 50 virtual machines The architecture diagram shown in Figure 4 characterizes the validated infrastructure with a Brocade VDX solution for up to 50 virtual machines. Figure 4. Logical architecture for 50 virtual machines EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 35

36 Solution Architecture Overview Architecture for up to 100 virtual machines The architecture diagram shown in Figure 5 characterizes the infrastructure with a Brocade VDX solution validated for up to 100 virtual machines. Figure 5. Logical architecture for 100 virtual machines Note The networking components of either solution can be implemented using 1 GbE or 10 GbE IP networks, if sufficient bandwidth and redundancy meet the listed requirements. Key components The architecture includes the following key components: Microsoft Hyper-V Provides a common virtualization layer to host a server environment. The specifics of the validated environment are listed in Table 2. Hyper-V provides a highly available infrastructure through features such as: Live Migration Provides live migration of virtual machines within a virtual infrastructure cluster, with no virtual machine downtime or service disruption. Live Storage Migration Provides live migration of virtual machine disk files within and across storage arrays with no virtual machine downtime or service disruption. 36 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

37 Solution Architecture Overview Failover Clustering High Availability (HA) Detects and provides rapid recovery for a failed virtual machine in a cluster. Dynamic Optimization (DO) Provides load balancing of computing capacity in a cluster with support of SCVMM. Microsoft System Center Virtual Machine Manager (SCVMM) SCVMM is not required for this solution. However, if deployed, it (or its corresponding function in Microsoft System Center Essentials) simplifies provisioning, management, and monitoring of the Hyper-V environment. Microsoft SQL Server 2012 SCVMM, if used, requires a SQL Server database instance to store configuration and monitoring details. DNS Server DNS services are required for the various solution components to perform name resolution. The Microsoft DNS service running on a Windows Server 2012 is used. Active Directory Server Active Directory services are required for the various solution components to function properly. The Microsoft Active Directory Service running on a Windows Server 2012 is used. Brocade VDX 6710/6720 Ethernet Fabric Network All network traffic is carried by the Brocade Ethernet Fabric network with redundant cabling and switches. User and management traffic is carried over a shared network while iscsi storage traffic is carried over a private, non-routable subnet. EMC VNXe 3150 array Provides storage by presenting Internet Small Computer System Interface (iscsi) datastores to Hyper-V hosts for up to 50 virtual machines. EMC VNXe 3300 array Provides storage by presenting Internet Small Computer System Interface (iscsi) datastores to Hyper-V hosts for up to 100 virtual machines. These datastores for both deployment sizes are created by using application-aware wizards included in the EMC Unisphere interface. VNXe series storage arrays include the following components: Storage Processors (SPs) support block and file data with UltraFlex TM I/O technology that supports iscsi, CIFS, and NFS protocols The SPs provide access for all external hosts and for the file side of the VNXe array. Battery backup units are battery units within each storage processor and provide enough power to each storage processor to ensure that any data in flight is destaged to the vault area in the event of a power failure. This ensures that no writes are lost. Upon restart of the array, the pending writes are reconciled and persisted. Disk-array Enclosures (DAE) house the drives used in the array. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 37

38 Solution Architecture Overview Hardware resources Table 2 lists the hardware used in this solution. Table 2. Solution hardware Hardware Configuration Notes Hyper-V servers Memory: 2 GB RAM per virtual machine 100 GB RAM across all servers for the 50-virtual-machine configuration 200 GB RAM across all servers for the 100-virtual-machine configuration 2 GB RAM reservation per host for hypervisor Configured as a single Hyper-V cluster. CPU: One vcpu per virtual machine One to four vcpus per physical core Brocade Network infrastructure Network: Two 10 GbE NIC ports per server Note To implement Microsoft Hyper-V High Availability (HA) functionality and to meet the listed minimums, the infrastructure should have one additional server. Minimum switching capacity: Two physical VDX 6710/6720 switches* One 1 GbE port per storage processor for management Two 10 GbE ports per storage processor for data For 50 & 100 Virtual Machines Brocade Ethernet Fabric Switch* Two VDX port o 6 x 1 GbE ports per Hyper-V server Brocade Ethernet Fabric Switch Two VDX port o Two 10 GbE ports per Hyper-V server Redundant Brocade VDX Ethernet Fabric configuration 1 GbE iscsi Server option 10 GbE iscsi Server option 38 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

39 Solution Architecture Overview Hardware Configuration Notes Storage Shared infrastructure EMC Next- Generation Backup Common: Two Storage Processors (active/active) Two 10GbE interfaces per storage processor for data For 50 Virtual Machines EMC VNXe 3150 Forty-five 300 GB 15k RPM 3.5-inch SAS disks (9 * 300 GB 4+1 R5 Performance Drive Packs) Two 300 GB 15k RPM 3.5-inch SAS disks as hot spares For 100 Virtual Machines EMC VNXe 3300 Seventy-seven 300 GB 15k RPM 3.5- inch SAS disks (11 * 300 GB 6+1 R5 Performance Drive Packs) Three 300 GB 15k RPM 3.5-inch SAS disks as hot spares In most cases, a customer environment will already have configured the infrastructure services such as Active Directory, DNS, and other services. The setup of these services is beyond the scope of this document. If this configuration is being implemented with non-existing infrastructure, a minimum number of additional servers is required: Two physical servers 16 GB RAM per server Four processor cores per server Two 10 GbE ports per server For 50 virtual machines Avamar Business Edition ½ Capacity For 100 virtual machines Avamar Business Edition Full Capacity Include the initial disk pack on the VNXe. These servers and the roles they fulfill may already exist in the customer environment; however, they must exist before VSPEX is deployed. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 39

40 Solution Architecture Overview Software resources Table 3 lists the software used in this solution. Table 3. Solution software Software Configuration Microsoft Hyper-V Operating system for Hyper-V hosts System Center Virtual Machine Manager Microsoft SQL Server Windows 2012 Datacenter Edition (Datacenter Edition is necessary to support the number of virtual machines in this solution) Version 2012 SP1 Version 2012 Enterprise Edition VNXe Software version Next-Generation Backup Avamar Business Edition 7.0 SP1 for up to 100 virtual machines Server configuration guidelines Overview When designing and ordering the compute/server layer of the VSPEX solution, several factors may alter the final purchase. From a virtualization perspective, if a system workload is well estimated, features like Dynamic Memory and Smart Paging can reduce the aggregate memory requirement. If the virtual machine pool does not have a high level of peak or concurrent usage, the number of vcpus may be reduced. Conversely, if the applications being deployed are highly computational in nature, the number of CPUs and memory to be purchased may need to increase. Hyper-V memory virtualization Microsoft Hyper-V has a number of advanced features that help to maximize performance and overall resource utilization. The most important of these are in the area of memory management. This section describes some of these features and the items to consider in the environment. In general, you can consider virtual machines on a single hypervisor consuming memory as a pool of resources. Figure 6 is an example. 40 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

41 Solution Architecture Overview Figure 6. Hypervisor memory consumption This basic concept is enhanced by understanding the technologies presented in this section. Dynamic Memory Dynamic Memory, which was introduced in Windows Server 2008 R2 SP1, increases physical memory efficiency by treating memory as shared resources and allocating it to the virtual machines dynamically. Actual used memory of each virtual machine is adjusted on demand. Dynamic Memory enables more virtual machines to run by reclaiming unused memory from idle virtual machines. In Windows Server 2012, Dynamic Memory enables the dynamic increase of the maximum memory available to virtual machines. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 41

42 Solution Architecture Overview Smart Paging Even with Dynamic Memory, Hyper-V allows more virtual machines than physical available memory. There is most likely a memory gap between minimum memory and startup memory. Smart Paging is a memory management technique that leverages disk resources as temporary memory replacement. It swaps out less-used memory to disk storage and swaps back in when needed, which may cause performance to degrade as a drawback. Hyper-V continues to leverage the guest paging when the host memory is oversubscribed, as it is more efficient than Smart Paging. Non-Uniform Memory Access Non-Uniform Memory Access (NUMA) is a multi-node computer technology that enables a CPU to access remote-node memory. This type of memory access is costly in terms of performance, so Windows Server 2012 employs a process known as processor affinity, which strives to keep threads pinned to a particular CPU to avoid remote-node memory access. In previous versions of Windows, this feature is only available to the host. Windows Server 2012 extends this functionality into the virtual machines, which can now realize improved performance in SMP environments. Memory configuration guidelines This section provides guidelines to configure server memory for this solution. The guidelines take into account Hyper-V memory overhead and the virtual machine memory settings. Hyper-V memory overhead Virtualized memory has some associated overhead, which includes the memory consumed by Hyper-V, the parent partition, and additional overhead for each virtual machine. Leave at least 2 GB memory for Hyper-V parent partition for this solution. Virtual machine memory In this solution, each virtual machine gets 2 GB memory in fixed mode. 42 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

43 Solution Architecture Overview Brocade network configuration guidelines Overview This section provides for setting up a redundant, highly available network configuration for this VSPEX solution. The guidelines take into account Jumbo Frames, VLANs, and Multiple Connections per Session (MC/S). For detailed network resource requirements, refer to Table 4. Table 4. Network hardware Hardware Configuration Notes Network infrastructure Minimum switching capacity: Two physical switches Two 10 GbE ports per Hyper-V server o Optionally Six 1 GbE ports per Hyper-V server One 1GbE port per storage processor for management Two 10-GbE ports per storage processor for data Redundant Brocade VDX Ethernet Fabric switch configuration VLAN It is a best practice to isolate network traffic so that the traffic between hosts and storage, hosts and clients, and management traffic all move over isolated networks. In some cases physical isolation may be required for regulatory or policy compliance reasons; but in many cases logical isolation using VLANs is sufficient. This solution calls for a minimum of three VLANs for the following usage: Client access Storage Management/Live Migration Figure 7 depicts these VLANs. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 43

44 Solution Architecture Overview Figure 7. Required networks Note Figure 7 demonstrates the network connectivity requirements for a VNXe 3300 using 10 GbE network connections (1 GbE for the Management Network). A similar topology should be created when using the VNXe 3150 array. The client access network is for users of the system, or clients, to communicate with the infrastructure. The Storage Network is used for communication between the compute layer and the storage layer. The Management network is used for administrators to have a dedicated way to access the management connections on the storage array, network switches, and hosts. Note Some best practices call for additional network isolation for cluster traffic, virtualization layer communication, and other features. These additional networks can be implemented if necessary, but they are not required. 44 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

45 Solution Architecture Overview Enable jumbo frames MC/S Brocade VDX Series switches support the transport of jumbo frames. This solution for EMC VSPEX private cloud recommends an MTU set at 9216 (jumbo frames) for efficient storage and migration traffic. Jumbo frames are enabled by default on the Brocade ISL trunks. However, to accommodate end-to-end jumbo frame support on the network for the edge hosts, this feature can be enabled for the interface connected to the Microsoft Hyper-V hosts, and the VNXe. The default Maximum Transmission Unit (MTU) on these interfaces is This MTU is set to 9216 to optimize the network for jumbo frame support. Multiple Connections per Session (MC/S) is configured on each Hyper-V host so that each host network interface has one iscsi session to each VNXe storage processor (SP) interface. In this solution, four iscsi sessions are configured between each host and each VNXe SP (each VNXe iscsi server). Link Aggregation Brocade Virtual Link Aggregation Group (vlag) Brocade Inter- Switch Link (ISL) Trunks A link aggregation resembles an Ethernet channel, but uses the Link Aggregation Control Protocol (LACP) IEEE 802.3ad standard. The IEEE 802.3ad standard supports link aggregations with two or more ports. All ports in the aggregation must have the same speed and be full duplex. In this solution, Link Aggregation Control Protocol (LACP) can be configured to the customer infrastructure network, combining multiple Ethernet ports into a single virtual device. If a link is lost in the Ethernet port, the link fails over to another port. All network traffic is distributed across the active links. Brocade Virtual Link Aggregation Groups (vlags) are used for the Microsoft Hyper-V host and customer infrastructure. In the case of the VNXe, a dynamic Link Aggregation Control Protocol (LACP) vlag is not used with MC/S and iscsi. While Brocade ISLs are used as interconnects between Brocade VDX switches within a Brocade VCS fabric, industry standard LACP LAGs are supported for connecting to other network devices outside the Brocade VCS fabric. Typically, LACP LAGs can only be created using ports from a single physical switch to a second physical switch. In a Brocade VCS fabric, a vlag can be created using ports from two Brocade VDX switches to a device to which both VDX switches are connected. This provides an additional degree of device-level redundancy, while providing active-active link-level load balancing. In VSPEX Stack Brocade Inter-Switch Link (ISL) Trunking is used within the Brocade VCS fabric to provide additional redundancy and load balancing between the iscsi clients and iscsi storage. Typically, multiple links between two switches are bundled together in a Link Aggregation Group (LAG) to provide redundancy and load balancing. Setting up a LAG requires lines of configuration on the switches and selecting a hashbased algorithm for load balancing based on source-destination IP or MAC addresses. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 45

46 Solution Architecture Overview All flows with the same hash traverse the same link, regardless of the total number of links in a LAG. This might result in some links within a LAG, such as those carrying flows to a storage target, being over utilized and packets being dropped, while other links in the LAG remain underutilized. Instead of LAG-based switch interconnects, Brocade VCS Ethernet fabrics automatically form ISL trunks when multiple connections are added between two Brocade VDX switches. Simply adding another cable increases bandwidth, providing linear scalability of switch-to-switch traffic, and this does not require any configuration on the switch. In addition, ISL trunks use a frame-by-frame load balancing technique, which evenly balances traffic across all members of the ISL trunk group. Equal-Cost Multipath (ECMP) Pause Flow Control A standard link-state routing protocol that runs at Layer 2 determines if there are Equal-Cost Multipaths (ECMPs) between RBridges in an Ethernet fabric and load balances the traffic to make use of all available ECMPs. If a neighbor switch is reachable via several interfaces with different bandwidths, all of them are treated as equal-cost paths. While it is possible to set the link cost based on the link speed, such an algorithm complicates the operation of the fabric. Simplicity is a key value of Brocade VCS Fabric technology, so an implementation is chosen in the test case that does not consider the bandwidth of the interface when selecting equal-cost paths. This is a key feature needed to expand network capacity, to keep ahead of customer bandwidth requirements. Brocade VDX Series switches support the Pause Flow Control feature. IEEE 802.3x Ethernet pause and Ethernet Priority-Based Flow Control (PFC) are used to prevent dropped frames by slowing traffic at the source end of a link. When a port on a switch or host is not ready to receive more traffic from the source, perhaps due to congestion, it sends pause frames to the source to pause the traffic flow. When the congestion is cleared, the port stops requesting the source to pause traffic flow, and traffic resumes without any frame drop. When Ethernet pause is enabled, pause frames are sent to the traffic source. Similarly, when PFC is enabled, there is no frame drop; pause frames are sent to the source switch. 46 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

47 Solution Architecture Overview Storage configuration guidelines Overview Hyper-V allows more than one method of utilizing storage when hosting virtual machines. The solutions are tested utilizing iscsi and the storage layout described adheres to all current best practices. The customer or architect with required knowledge can make modifications based on the systems usage and load if necessary. Table 5 lists the required hardware for the storage configuration. Table 5. Storage hardware Hardware Configuration Notes Storage Common: Two storage processors (active/active) Two 10 GbE interfaces per storage processor Include the initial disk pack on the VNXe. For 50 virtual machines EMC VNXe 3150 Forty-five 300 GB 15k RPM 3.5-inch SAS disks (9 * 300 GB 4+1 R5 Performance Drive Packs) Two 300 GB 15k RPM 3.5-inch SAS disks as hot spares For 100 virtual machines EMC VNXe 3300 Seventy-seven 300 GB 15k RPM 3.5- inch SAS disks (11 * 300 GB 6+1 R5 Performance Drive Packs) Three 300 GB 15k RPM 3.5-inch SAS disks as hot spares EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 47

48 Solution Architecture Overview Hyper-V storage virtualization for VSPEX This section provides guidelines to set up the storage layer of the solution to provide high availability and the expected level of performance. Windows Server 2012 Hyper-V and Failover Clustering leverage Cluster Shared Volumes v2 and new Virtual Hard Disk Format (VHDX) features to virtualize storage presented from external shared storage system to host virtual machines. Figure 8. Hyper-V virtual disk types Cluster Shared Volumes v2 Cluster Shared Volumes (CSV) was introduced in Windows Server 2008 R2. They enable all cluster nodes to have simultaneous access to the shared storage for hosting virtual machines. Windows Server 2012 introduces a number of new capabilities with CSV v2, which includes flexible application, file storage, integration with other Windows Server 2012 features, single name space, and improved backup, and restore. New Virtual Hard Disk format Hyper-V in Windows Server 2012 contains an update to the VHD format called VHDX, which has much larger capacity and built-in resiliency. The main new features of VHDX format are: Support for virtual hard disk storage with the capacity of up to 64 TB Additional protection against data corruption during power failures by logging updates to the VHDX metadata structures Optimal structure alignment of the virtual hard disk format to suit large sector disks The VHDX format also has the following features: Larger block sizes for dynamic and differential disks, which enables the disks to meet the needs of the workload 48 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

49 Solution Architecture Overview The 4 KB logical sector virtual disk that enables increased performance when used by applications and workloads that are designed for 4-KB sectors The ability to store custom metadata about the files that the user might want to record, such as the operating system version or applied updates Space reclamation features that can result in smaller file size and enables the underlying physical storage device to reclaim unused space (Trim for example requires direct-attached storage or SCSI disks and Trim-compatible hardware.) Storage layout for 50 virtual machines Figure 9 shows the overall storage layout of the 50 virtual machine solution. Figure 9. Storage layout for 50 virtual machines Storage layout overview The architecture for up to 50 virtual machines uses the following configuration: Forty-five 300 GB SAS disks allocated to a single storage pool as nine 4+1 RAID 5 groups (sold as nine packs of five disks). At least one hot spare allocated for every 30 disks of a given type. At least four iscsi LUNs allocated to the Hyper-V cluster from the single storage pool to serve as datastores for the virtual servers. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 49

50 Solution Architecture Overview Storage layout for 100 virtual machines Figure 10 shows the overall storage layout of the 100 virtual machine solution. Figure 10. Storage layout for 100 virtual machines Storage layout overview The architecture for up to 100 virtual machines uses the following configuration: Seventy-seven 300 GB SAS disks allocated to a single storage pool as eleven 6+1 RAID 5 groups (sold as 11 packs of seven disks). At least one hot spare disk allocated for every 30 disks of a given type. At least 10 iscsi LUNs allocated to the Hyper-V cluster from the single storage pool to serve as datastores for the virtual servers. Note If more capacity is required in either configuration, larger drives may be substituted. To meet the load recommendations, the drives all must be 15k RPM and the same size. If different sizes are utilized, storage layout algorithms may give sub-optimal results. 50 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

51 Solution Architecture Overview High availability and failover Overview Virtualization layer This VSPEX solution provides a highly available virtualized server, network, and storage infrastructure. By implementing the solution in this guide, single-unit failures can survive with minimal or no impact to business operations. Configure high availability in the virtualization layer, and configure the hypervisor to automatically restart failed virtual machines. Figure 11 illustrates the hypervisor layer responding to a failure in the compute layer. Figure 11. High Availability at the virtualization layer By implementing high availability at the virtualization layer, even in a hardware failure, the infrastructure attempts to keep as many services running as possible. Compute layer Use enterprise class servers designed for the datacenter to implement the compute layer when possible. This type of server has redundant power supplies, which should be connected to separate Power Distribution units (PDUs) in accordance with your server vendor s best practices. Figure 12. Redundant power supplies EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 51

52 Solution Architecture Overview Configure high availability in the virtualization layer. The compute layer must be configured with enough resources so that the total number of available resources meets the needs of the environment, even with a server failure, as demonstrated in Figure 11. Brocade VDX Network layer The advanced networking features of the VNX family and Brocade VDX with VCS Ethernet Fabric provide protection against network connection failures at the array. Each Hyper-V host has multiple connections to user and storage Ethernet networks to guard against link failures. These connections should be spread across multiple Brocade Ethernet Fabric switches to guard against component failure in the network. Figure 13. Network layer High Availability Note Figure 13 demonstrates a highly available network topology based on VNXe A similar topology should be constructed if using the VNXe By ensuring that there are no single points of failure in the network layer, the compute layer is able to access storage, and communicate with users even if a component fails. 52 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

53 Solution Architecture Overview Storage layer The VNX family is designed for five 9s availability by using redundant components throughout the array. All of the array components are capable of continued operation in case of hardware failure. The RAID disk configuration on the array provides protection against data loss caused by individual disk failures, and the available hot spare drives can be dynamically allocated to replace a failing disk, as shown in Figure 14. Figure 14. VNXe series High Availability EMC Storage arrays are designed to be highly available by default. Configure the storage arrays according to the installation guides to ensure that no single unit failures cause data loss or unavailability. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 53

54 Solution Architecture Overview Backup and recovery configuration guidelines Overview Backup characteristics This section provides guideline to set up a backup and recovery environment for this VSPEX solution. It describes how to characterize and design the backup environment. This VSPEX solution was sized with the application environment profile shown in Table 6. Table 6. Backup profile characteristics Profile characteristic Value Number of users 500 for 50 virtual machines 1,000 for 100 virtual machines Number of virtual machines Exchange data SharePoint data SQL server User data 50 for 50 virtual machines 100 for 100 virtual machines Note 20% DB, 80% Unstructured 0.5 TB for 50 virtual machines 1 TB for 100 virtual machines Note 1 GB mail box per user 0.25 TB for 50 virtual machines 0.5 TB for 100 virtual machines 0.25 TB for 50 virtual machines 0.5 TB for 100 virtual machines 2.5 TB for 50 virtual machines 5 TB for 100 virtual machines (5.0 GB per user) Daily change rate for the applications Exchange data 10% SharePoint data 2% SQL server 5% User data 2% Retention per data types All DB data User data 14 Dailies 30 Dailies, 4 Weeklies, 1 Monthly 54 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

55 Solution Architecture Overview Backup layout for up to100 virtual machines Avamar Business Edition is a purpose built backup applicance that provides a conveniently sized, turnkey, afforadable, deduplicated backup solution. Designed for mid-market companies, it features simplified management making it ideal for organizations with limited IT resources. And with built-in storage resiliency, it eliminates the requirement and expense of a second replicated system. Powered by industry leading EMC Avamar software, the Avamar Business Edition delivers fast, daily full backups along with one-step recovery for VSPEX Proven Infrastructures. Sizing guidelines The following sections describe definitions of the reference workload used to size and implement the VSPEX architectures, guidance on how to correlate those reference workloads to actual customer workloads, and how that may change the end delivery from the server and network perspective. You can modify the storage definition by adding drives for greater capacity and performance. The disk layouts are created to provide support for the appropriate number of virtual machines at the defined performance level along with typical operations such as snapshots. Decreasing the number of recommended drives or stepping down to a lower performing array type can result in lower IOPS per virtual machine and a reduced user experience due to higher response times. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 55

56 Solution Architecture Overview Reference workload Overview When considering an existing server to move into a virtual infrastructure, you have the opportunity to gain efficiency by right-sizing the virtual hardware resources assigned to that system. Each VSPEX Proven Infrastructure balances the storage, network, and compute resources needed for a set number of virtual machines that have been validated by EMC. In practice, each virtual machine has its own set of requirements that rarely fit a predefined idea of what a virtual machine should be. In any discussion about virtual infrastructures, it is important to first define a reference workload. Not all servers perform the same tasks, and it is impractical to build a reference model that takes into account every possible combination of workload characteristics. Defining the reference workload To simplify the discussion, we have defined a representative customer reference workload. By comparing your actual customer usage to this reference workload, you can extrapolate which reference architecture to choose. For the VSPEX solutions, the reference workload is defined as a single virtual machine. Table 7 lists the characteristics of this virtual machine: Table 7. Virtual machine characteristics Characteristic Value Virtual machine operating system Microsoft Windows Server 2012 Datacenter Edition Virtual processors per virtual machine RAM per virtual machine Available storage capacity per virtual machine I/O operations per second (IOPS) per virtual machine I/O pattern 1 2 GB 100 GB 25 Random I/O read/write ratio 2:1 This specification for a virtual machine is not intended to represent any specific application. Rather, it represents a single common point of reference against which other virtual machines can be measured. 56 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

57 Solution Architecture Overview Applying the reference workload Overview Example 1: Custom-built application Example 2: Point of sale system The reference architectures create a pool of resources that are sufficient to host a target number of Reference virtual machines with the characteristics shown in Table 7. The customer virtual machines may not exactly match the specifications. In that case, define a single specific customer virtual machine as the equivalent of a number of Reference virtual machines, and assume the virtual machines are in use in the pool. Continue to provision virtual machines from the resource pool until no resources remain. A small custom-built application server needs to move into this infrastructure. The physical hardware that supports the application is not fully utilized. A careful analysis of the existing application reveals that the application can use one processor, and needs 3 GB of memory to run normally. The I/O workload ranges from four IOPS at idle time to a peak of 15 IOPS when busy. The entire application consumes about 30 GB of local hard drive storage. Based on the numbers, the following resources are required from the resource pool: CPU resources for one virtual machine Memory resources for two virtual machines Storage capacity for one virtual machine I/Os for one virtual machine In this example, a single virtual machine uses the resources for two of the Reference virtual machines. If the original pool has the resources to provide 100 Reference virtual machines, the resources for 98 Reference virtual machines remain. The database server for a customer s point of scale system needs to move into this virtual infrastructure. It is currently running on a physical system with four CPUs and 16 GB of memory. It uses 200 GB of storage and generates 200 IOPS during an average busy cycle. The following resources are required to virtualize this application: CPUs of four Reference virtual machines Memory of eight Reference virtual machines Storage of two Reference virtual machines I/Os of eight Reference virtual machines EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 57

58 Solution Architecture Overview In this case, the one virtual machine uses the resources of eight Reference virtual machines. To implement this one machine on a pool for 100 Reference virtual machines, the resources of eight Reference virtual machines are consumed and resources for 92 Reference virtual machines remain. Example 3: Web server The web server of the customer needs to move into this virtual infrastructure. It is currently running on a physical system with 2 CPUs and 8 GB of memory. It uses 25 GB of storage and generates 50 IOPS during an average busy cycle. The following resources are required to virtualize this application: CPUs of two Reference virtual machines Memory of four Reference virtual machines Storage of one Reference virtual machines I/Os of two Reference virtual machines In this case, the one virtual machine would use the resources of four Reference virtual machines. If the configuration is implemented on a resource pool for 100 Reference virtual machines, resources for 96 Reference virtual machines remain. Example 4: Decisionsupport database The database server for a customer s decision-support system needs to move into this virtual infrastructure. It is currently running on a physical system with 10 CPUs and 64 GB of memory. It uses 5 TB of storage and generates 700 IOPS during an average busy cycle. The following resources are required to virtualize this application: CPUs of 10 Reference virtual machines Memory of 32 Reference virtual machines Storage of 52 Reference virtual machines I/Os of 28 Reference virtual machines In this case, the one virtual machine uses the resources of 52 Reference virtual machines. If this configuration is implemented on a resource pool for 100 Reference virtual machines, resources for 48 Reference virtual machines remain. Summary of examples The four examples illustrate the flexibility of the resource pool model. In all four cases, the workloads simply reduce the amount of available resources in the pool. All four examples can be implemented on the same virtual infrastructure with an initial capacity for 100 Reference virtual machines, and resources for 34 Reference virtual machines remain in the resource pool, as shown in Figure EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

59 Solution Architecture Overview Figure 15. Resource pool flexibility In more advanced cases, there may be tradeoffs between memory and I/O or other relationships where increasing the amount of one resource decreases the need for another. In these cases, the interactions between resource allocations become highly complex, and are outside the scope of the document. Once the change in resource balance has been examined and the new level of requirements is known, these virtual machines can be added to the infrastructure using the method described in the examples. Implementing the reference architectures Overview Resource types The reference architectures require a set of hardware to be available for the CPU, memory, network, and storage needs of the system. In this VPSEX solution, these are presented as general requirements that are independent of any particular implementation. This section describes some considerations for implementing the requirements. The reference architectures define the hardware requirements for this VSPEX solution in terms of the following basic types of resources: CPU resources Memory resources Brocade network resources Storage resources This section describes the resource types, how to use them in the reference architectures, and key considerations for implementing them in a customer environment. CPU resources The architectures define the number of required CPU cores instead of a specific type or configuration. It is intended that new deployments use recent revisions of common processor technologies. It is assumed that they perform as well as, or better than the systems used to validate the solution. In any running system, it is important to monitor the utilization of resources and adapt as needed. The Reference virtual machine and required hardware resources in the reference architectures assume that there are no more than four virtual CPUs for each physical processor core (4:1 ratio). EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 59

60 Solution Architecture Overview In most cases, this provides an appropriate level of resources for the hosted virtual machines; however, this ratio may not be appropriate in all use cases. Monitor the CPU utilization at the hypervisor layer to determine if more resources are required. Memory resources Each virtual server in the reference architectures is defined to have 2 GB of memory. In a virtual environment, it is common to provision virtual machines with more memory than the hypervisor physically has, due to budget constraints. The memory over commitment technique takes advantage of the fact that each virtual machine may not fully utilize the amount of memory allocated to it. Therefore, it makes business sense to oversubscribe the memory usage to some degree. The administrator has the responsibility to monitor the oversubscription rate such that it does not shift the bottleneck away from the server and become a burden to the storage subsystem via swapping. This solution is validated with statically assigned memory and no over commitment of memory resources. If memory over commit is used in a real-world environment, regularly monitor the system memory utilization, and associated page file I/O activity to ensure that a memory shortfall does not cause unexpected results. Brocade network resources The reference architecture outlines the minimum needs of the system. If additional bandwidth is needed, it is important to add capability at both the storage array and the hypervisor host to meet the requirements. The options for Brocade network connectivity on the server depend on the type of server for either 1 or 10GbE connectivity. The storage arrays have a number of included network ports, and have the option to add ports using EMC FLEX I/O modules and connectivity via 10 GbE. For reference purposes in the validated environment, EMC assumes that each virtual machine generates 25 IOs per second with an average size of 8 KB. This means that each virtual machine is generating at least 200 KB/s of traffic on the storage network. For an environment rated for 100 virtual machines, this comes out to a minimum of approximately 20 MB/sec. This is well within the bounds of modern networks. However, this does not consider other operations. For example, additional bandwidth is needed for the following operations: User network traffic Virtual machine migration Administrative and management operations 60 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

61 Solution Architecture Overview The requirements for each of these vary depending on how the environment is being used. It is not practical to provide concrete numbers in this context. However, the network described in the reference architecture for each solution should be sufficient to handle average workloads for the preceding use cases. The specific network layer connectivity for the Brocade VDX Fabric solution is defined in Chapter 5. Regardless of the network traffic requirements, always have at least two physical network connections that are shared for a logical network so that a single link failure does not affect the availability of the system. Design the network to ensure that the aggregate bandwidth in a failure is sufficient to accommodate the full workload. Storage resources The reference architectures contain layouts for the disks used in the validation of the system. Each layout balances the available storage capacity with the performance capability of the drives. There are a few layers to consider when examining storage sizing. Specifically, the array has a collection of disks that are assigned to a storage pool. From that storage pool, you can provision datastores to the Microsoft Hyper-V cluster. Each layer has a specific configuration that is defined for the solution and documented in the deployment guide. It is generally acceptable to replace drive types with a type that has more capacity with the same performance characteristics or with ones that have higher performance characteristics and the same capacity. Similarly, it is acceptable to change the placement of drives in the drive shelves in order to comply with updated or new drive shelf arrangements. In other cases where there is a need to deviate from the proposed number and type of drives specified, or the specified pool and datastore layouts, ensure that the target layout delivers the same or greater resources to the system. Implementation summary The requirements that are stated in the reference architectures are what EMC considers the minimum set of resources to handle the workloads required based on the stated definition of a reference virtual server. In any customer implementation, the load of a system varies over time as users interact with the system. However, if the customer virtual machines differ significantly from the reference definition, the system may require additional resources. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 61

62 Solution Architecture Overview Quick assessment Overview An assessment of the customer environment helps ensure that you implement the correct VSPEX solution. This section provides an easy-to-use worksheet to simplify the sizing calculations, and help assess the customer environment. Summarize the applications that are planned for migration into the VSPEX private cloud. For each application, determine the number of virtual CPUs, the amount of memory, the required storage performance, the required storage capacity, and the number of Reference virtual machines required from the resource pool. Applying the reference workload provides examples of this process. Fill out a row in the worksheet for each application, as shown in Table 8. Table 8. Blank worksheet row Application CPU (virtual CPUs) Memory (GB) IOPS Capacity (GB) Equivalent Reference virtual machines Example application Resource requirements Equivalent Reference virtual machines Fill out the resource requirements for the application. The row requires inputs on four different resources: CPU, Memory, IOPS, and Capacity. CPU requirements Optimizing CPU utilization is a significant goal for almost any virtualization project. A simple view of the virtualization operation suggests a one-toone mapping between physical CPU cores and virtual CPU cores regardless of the physical CPU utilization. In reality, consider whether the target application can effectively use all of the presented CPUs. Use a performance-monitoring tool, such as Microsoft perfmon to examine the CPU Utilization counter for each CPU. If they are equivalent, implement that number of virtual CPUs when moving into the virtual infrastructure. However, if some CPUs are used and some are not, consider decreasing the number of virtual CPUs that are required. In any operation involving performance monitoring, it is a best practice to collect data samples for a period of time that includes all of the operational use cases of the system. Use either the maximum or 95 th percentile value of the resource requirements for planning purposes. 62 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

63 Solution Architecture Overview Memory requirements Storage performance requirements I/O operations per second (IOPs) Server memory plays a key role in ensuring application functionality and performance. Therefore, each server process has different targets for the acceptable amount of available memory. When moving an application into a virtual environment, consider the current memory available to the system, and monitor the free memory by using a performance-monitoring tool like perfmon, to determine if it is being used efficiently. The storage performance requirements for an application are usually the least understood aspect of performance. Three components become important when discussing the I/O performance of a system. The number of requests coming in, or IOPS The size of the request, or I/O size -- a request for 4 KB of data is significantly easier and faster to process than a request for 4 MB of data The average I/O response time or latency The Reference virtual machine calls for 25 I/O operations per second. To monitor this on an existing system use a performance-monitoring tool like perfmon, which provides several counters that can help here. Logical Disk\Disk Transfer/sec Logical Disk\Disk Reads/sec Logical Disk\Disk Writes/sec The Reference virtual machine assumes a 2:1 read: write ratio. Use these counters to determine the total number of IOPS, and the approximate ratio of reads to writes for the customer application. I/O size The I/O size is important because smaller I/O requests are faster and easier to process than large I/O requests. The Reference virtual machine assumes an average I/O request size of 8 KB, which is appropriate for a large range of applications. Use perfmon or another appropriate tool to monitor the Logical Disk\Avg. Disk Bytes/Transfer counter to see the average I/O size. Most applications use I/O sizes that are even powers of 2 KB (i.e. 4 KB, 8 KB, 16 KB, and 32 KB, and so on) are common. The performance counter does a simple average, so it is common to see 11 KB or 15 KB instead of the common I/O sizes. The Reference virtual machine assumes an 8 KB I/O size. If the average customer I/O size is less than 8 KB, use the observed IOPS number. However, if the average I/O size is significantly higher, apply a scaling factor to account for the large I/O size. A safe estimate is to divide the I/O size by 8 KB and use that factor. For example, if the application is using mostly 32 KB I/O requests, use a factor of four (32 KB / 8 KB = 4). If that application is doing 100 IOPS at 32 KB, the factor indicates to plan for 400 IOPS since the Reference virtual machine assumed 8 KB I/O sizes. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 63

64 Solution Architecture Overview I/O latency Storage capacity requirements Determining equivalent Reference virtual machines The average I/O response time, or I/O latency, is a measurement of how quickly I/O requests are processed by the storage system. The VSPEX solutions are designed to meet a target average I/O latency of 20 ms. The recommendations in the Sizing guidelines section should allow the system to continue to meet that target, however it is worthwhile to monitor the system and re-evaluate the resource pool utilization if needed. To monitor I/O latency, use the Logical Disk\Avg. Disk sec/transfer counter in perfmon. If the I/O latency is continuously over the target, re-evaluate the virtual machines in the environment to ensure that they are not using more resources than intended. The storage capacity requirement for a running application is usually the easiest resource to quantify. Determine how much space on disk the system is using, and add an appropriate factor to accommodate growth. For example, to virtualize a server that is currently using 40 GB of a 200 GB internal drive with anticipated growth of approximately 20% over the next year, 48 GB are required. EMC also recommends reserving space for regular maintenance patches and swapping files. In addition, some file systems, like Microsoft NTFS, degrade in performance if they become too full. With all of the resources defined, determine an appropriate value for the equivalent Reference virtual machines line by using the relationships in Table 9. Round all values up to the closest whole number. Table 9. Resource Reference virtual machine resources Value for Reference virtual machine Relationship between requirements and equivalent Reference virtual machines CPU 1 Equivalent Reference virtual machines = resource requirements Memory 2 Equivalent Reference virtual machines = (resource requirements)/2 IOPS 25 Equivalent Reference virtual machines = (resource requirements)/25 Capacity 100 Equivalent Reference virtual machines = (resource requirements)/ EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

65 Solution Architecture Overview For example, the point of sale system used in Example 2: Point of sale system earlier in the paper requires 4 CPUs, 16 GB of memory, 200 IOPS and 200 GB of storage. This translates to four Reference virtual machines of CPU, eight Reference virtual machines of memory, eight Reference virtual machines of IOPS, and two Reference virtual machines of capacity. Table 10 demonstrates how that machine fits into the worksheet row. Use the maximum value of the row to fill in the column for equivalent Reference virtual machines. Eight Reference virtual machines are required in this example. Table 10. Example worksheet row Application CPU (virtual CPUs) Memory (GB) IOPS Capacity (GB) Equivalent Reference virtual machines Example application Resource requirements Equivalent Reference virtual machines Figure 16. Required resource from the Reference virtual machine pool Once the worksheet has been filled out for each application that the customer wants to migrate into the virtual infrastructure, compute the sum of the equivalent Reference virtual machines column on the right side of the worksheet as shown in Table 11, to calculate the total number of Reference virtual machines that are required in the pool. In the example, the result of the calculation from Table 9 is shown for clarity, along with the value, rounded up to the nearest whole number, to use. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 65

66 Solution Architecture Overview Table 11. Example applications Application Example application #1: Custombuilt application Example application #2: Point of sale system Example application #3: Web server Example application #4: Decision support database Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Server resources CPU (virtual CPUs) Memory (GB) Storage resources IOPS Capacity (GB) (5TB) Reference virtual machines Total equivalent Reference virtual machines 66 The VSPEX private cloud solutions define discrete resource pool sizes. Figure 17 shows 34 Reference virtual machines available after applying all four examples in 100 virtual machine solutions. Figure 17. pool Aggregate resource requirements from the Reference virtual machine 66 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

67 Solution Architecture Overview In the case of Table 11, the customer requires 66 virtual machines of capability from the pool. Therefore, the 100 virtual machine resource pool provides sufficient resources for the current needs as well as room for growth. Fine tuning hardware resources In most cases, the recommended hardware for servers and storage is sized appropriately based on the process described. However, in some cases there may be a requirement to further customize the hardware resources that are available to the system. While a complete description of system architecture is beyond the scope of this document, additional customization can be done at this point. Storage resources In some applications, there is a need to separate application data from other workloads. The storage layouts in the VSPEX architectures put all of the virtual machines in a single resource pool. In order to achieve workload separation, purchase additional disk drives for the application workload and add them to a dedicated pool. It is not appropriate to reduce the size of the main resource pool in order to support application isolation, or to reduce the capability of the pool. The storage layouts presented in the 50 and 100 virtual machine solutions are designed to balance many different factors in terms of high availability, performance, and data protection. Changing the components of the pool can have significant and difficult-to-predict impacts on other areas of the system. Server resources For the server resources in the VSPEX private cloud solution, it is possible to customize the hardware resources for varying workloads. Figure 18 is an example. Figure 18. Customizing server resources To achieve this customization, total the resource requirements for the server components, as shown in Table 12. In the Server Component Totals row, add up the server resource requirements from the applications in the table. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 67

68 Solution Architecture Overview Table 12. Server resource component totals Application Example application #1: Custom-built application Example application #2: Point of sale system Example application #3: Web server Example application #4: Decision support database Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Server resources CPU (virtual CPUs) Memory (GB) Storage resources IOPS Capacity (GB) (5TB) Reference virtual machines Total equivalent Reference virtual machines 66 Server resource component totals In this example, the target architecture required 17 virtual CPUs and 155 GB of memory. This translates to five physical processor cores and 155 GB of memory, plus 2 GB for the hypervisor on each physical server. In contrast, the 100 Reference virtual machine resource pool documented in the VSPEX solution calls for 200 GB of memory plus 2 GB for each physical server to run the hypervisor, and at least 25 physical processor cores. In this environment, the solution can be effectively implemented with fewer server resources. Note Keep high availability requirements in mind when customizing the resource pool hardware. Table 13 shows a blank worksheet. 68 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

69 Solution Architecture Overview Table 13. Blank customer worksheet Application Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Resource requirements Equivalent Reference virtual machines Total equivalent Reference virtual machines Server resource component totals Server resources CPU Memory (virtual (GB) CPUs) Storage resources IOPS Capacity (GB) Reference virtual machines EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 69

70

71 Chapter 5 VSPEX Configuration Guidelines This chapter presents the following topics: Overview 72 Pre-deployment tasks 73 Customer configuration data 75 Prepare and Configure Brocade VDX switches 75 Brocade VDX 6710 and 6720 Switch Configuration Summary 78 Brocade VDX 6710 Configuration 78 Brocade VDX 6720 Configuration 93 Prepare and configure storage array110 Install and configure Hyper-V hosts112 Install and configure SQL server database 115 System Center Virtual Machine Manager server deployment 117 Summary 119 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 71

72 VSPEX Configuration Guidelines Overview The deployment process is divided into the stages shown in Table 14. Upon completion of the deployment, the VSPEX infrastructure should be ready for integration with the existing customer network and server infrastructure. Table 14 lists the main stages in the solution deployment process. The table also includes references to chapters where relevant procedures are provided. Table 14. Deployment process overview Stage Description Reference and documentation 1 Verify prerequisites Pre-deployment tasks 2 Obtain the deployment tools Pre-deployment tasks 3 Gather customer configuration data 4 Rack and cable the components 5 Configure the switches, networks and connect to the customer network Customer configuration data Refer to the vendor documentation. Prepare and Configure Brocade VDX switches 6 Install and configure the VNXe Prepare and configure storage array 7 Configure virtual machine datastores Prepare and configure storage array 8 Install and configure the servers Install and configure Hyper-V hosts 9 Set up SQL Server (used by SCVMM) Install and configure SQL server database 10 Install and configure SCVMM System Center Virtual Machine Manager server deployment 72 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

73 VSPEX Configuration Guidelines Pre-deployment tasks Overview Pre-deployment tasks include procedures that are not directly related to environment, installation, or configuration; however, the results are needed at the time of installation. Examples of pre-deployment tasks are collection of hostnames, IP addresses, VLAN IDs, license keys, installation media, and so on. Perform these tasks before the customer visit to decrease the time required onsite. Table 15. Tasks for pre-deployment Task Description Reference Gather documents Gather tools Gather data Gather the related documents listed in Appendix C. These documents are used throughout the text of this document to provide details on setup procedures and deployment best practices for the components of the solution. Gather the required and optional tools for the deployment. Use Table 16 to confirm that all equipment, software, and appropriate licenses are available before the deployment process. Collect the customer-specific configuration data for networking, naming, and required accounts. Enter this information into the Appendix B for reference during the deployment process. Appendix C EMC documentation Table 16 Deployment prerequisites checklist Appendix B EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 73

74 VSPEX Configuration Guidelines Deployment prerequisites Table 16 itemizes the hardware, software, and license requirements to configure the solution. For additional information on hardware and software, refer to Table 2 and Table 3. Table 16. Deployment prerequisites checklist Requirement Description Reference Hardware Software Licenses Physical servers to host virtual servers: Sufficient physical server capacity to host 50 or 100 virtual machines. Windows Server 2012 servers to host virtual infrastructure servers. Note This requirement may be covered in the existing infrastructure. Brocade VDX Fabric Networking: Switch port capacity and capabilities as required by the virtual server infrastructure. Sufficient 1 or 10GbE ports for connectivity of physical server c to host virtual servers, VNXe, and customer infrastructure. EMC VNXe 3150 (50 virtual machines) or VNXe 3300 (100 virtual machines) multiprotocol storage array with the required disk layout. SCVMM 2012 installation media. Microsoft Windows Server 2012 installation media. Microsoft SQL Server 2012 or newer installation media. Note This requirement may be covered in the existing infrastructure. Microsoft Windows Server 2012 Datacenter Edition license keys. Note This requirement may be covered by an existing Microsoft Key Management Server (KMS). Microsoft SQL Server license key. Note This requirement may be covered by existing infrastructure. SCVMM 2012 license keys. Table 2 Solution hardware 74 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

75 VSPEX Configuration Guidelines Customer configuration data To reduce the onsite time, assemble information such as IP addresses and hostnames as part of the planning process. Appendix B provides a table to maintain a record of relevant information. Expand or contract this form as required. Information may be added, modified, and recorded as deployment progresses. Additionally, complete the VNXe Series Configuration Worksheet, available on EMC Online Support, to provide the most comprehensive array-specific information. Prepare and Configure Brocade VDX switches Overview This section provides the requirements for Brocade network infrastructure needed to support this architecture. For validated levels of performance and high availability, this solution requires the switching capacity that is provided in Appendix B. Brocade VCS (Virtual Cluster Switching) Fabric technology is an Ethernet technology that allows you to create flatter, virtualized, and converged data center networks. Brocade VCS Fabric technology is elastic, permitting you to start small, typically at the access layer, and expand your network at your own pace. Brocade VCS Fabric technology is built upon three core design principles: Performance Automation Resiliency The Brocade VDX switches with VCS Fabric technology are deployed redundantly to form an Ethernet fabric for the VSPEX networking layer. To the rest of the network, the Ethernet fabric appears as a single logical chassis, which able to exchange information among each other using distributed intelligence. Brocade VDX Switch Platform Considerations This section describes the Brocade VDX with VCS Fabrics network switch configuration procedure for the infrastructure connectivity between Microsoft Hyper-V servers, existing customer network, and iscsi attached VNXe storage. At the point of deployment, the new equipment is being connected to the existing customer network and potentially existing compute servers with either 1 or 10 GbE attached NICs. This VSPEX Private Cloud solution is designed with the VDX 6710 for 1GbE attached Microsoft Hyper-V servers and the VDX 6720(24/60 port) switches for 10GbE attached Microsoft Hyper-V servers and is enabled with VCS Fabric Technology. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 75

76 VSPEX Configuration Guidelines The VCS Fabric technology has the following characteristics: It is an Ethernet Fabric switched network. The Ethernet fabric utilizes an emerging standard called Transparent Interconnection of Lots of Links (TRILL) as the underlying technology. All switches automatically know about each other and all connected physical and logical devices. All paths in the fabric are available. Traffic is always distributed across equal-cost paths. Traffic from the source to the destination can travel across two paths. Traffic travels across the shortest path. If a single link fails, traffic is automatically rerouted to other available paths. If one of the links in Active Path #1 goes down, traffic is seamlessly rerouted across Active Path #2. Spanning Tree Protocol (STP) is not necessary because the Ethernet fabric appears as a single logical switch to connected servers, devices, and the rest of the network. Traffic can be switched from one Ethernet fabric path to the other Ethernet fabric path. VCS is enabled by default on the Brocade VDX 6710, however if VCS has been disabled then the following command will enable VCS on the switch. Use the following command to configure the VCS ID and the RBridge ID only if VCS needs to be enabled. switch#vcs enable In addition, it is important to consider the airflow direction of the switches. Brocade VDX switches are available in both port side exhaust and port side intake configurations. Depending upon the hot-aisle, cold-aisle considerations choose the appropriate airflow. For more information, refer to the Brocade VDX 6710 Hardware Reference Manual or the Brocade VDX 6720 Hardware Reference Manual as provided in Appendix B. Prepare Brocade Network Infrastructure The infrastructure network requires redundant network links for each Windows host, the storage array, the switch interconnect ports, and the switch uplink ports. This configuration provides both redundancy and additional network bandwidth. This configuration is required regardless of whether the network infrastructure for the solution already exists or is being deployed alongside other components of the solution. Figure 19 shows a sample redundant Ethernet infrastructure for this solution. The diagram illustrates the use of redundant switches and links to ensure that no single points of failure exist in the network connectivity. 76 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

77 VSPEX Configuration Guidelines Figure 19. Sample Ethernet network architecture Complete Network Cabling Connect Brocade switch ports to all servers, storage arrays, inter-switch links, and uplinks. Ensure that all solution servers, storage arrays, switch interconnects, and switch uplinks have redundant connections. Ensure that the uplinks are connected to the existing customer network. The Brocade VDX 6710 Switch Installation Guide and the Brocade VDX 6720 Switch Installation Guide provide instructions on racking, cabling, and powering the VDX 6710/6720. There are no specific setup steps for this solution. Note: At this point, the new equipment is being connected to the existing customer network. Be careful that unforeseen interactions do not cause service issues on the customer network. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 77

78 VSPEX Configuration Guidelines Brocade VDX 6710 and 6720 Switch Configuration Summary Listed below is the procedure required to deploy the Brocade VDX 6710 and VDX 6720 switches with VCS Fabric Technology in the VSPEX Private Cloud Solution from 50 to 100 Virtual Machines. Table 17. Brocade VDX 6710 and VDX 6720 Configuration Steps Brocade VDX Configuration Steps Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Verify VDX NOS Licenses Assign and Verify VCS ID and RBridge ID Assign Switch Name VCS Fabric ISL Port Configuration Create required VLANs Create vlag for Microsoft Server Configure Switch Interfaces for VNXe Connecting the VCS Fabric to customer s infrastructure Configure MTU and Jumbo Frames AMPP Configuration for live migrations Please see end of this chapter for related documents Brocade VDX 6710 Configuration Use the following procedure to configure a VDX 6710 based fabric. During the switch configuration process, some of the configuration commands may require a switch restart. To save settings across restarts, run the copy running-config startup-config command after making any configuration changes. Note: Before running a command that requires a switch restart, back up the switch configuration using the copy running-config startupconfig, as shown: BRCD6710# copy running-config startup-config This operation will modify your startup configuration. Do you want to continue? [y/n]:y 78 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

79 VSPEX Configuration Guidelines Step 1: Verify VDX NOS Licenses Before starting the switch configurations, make sure you have the required licenses available for the VDX 6710 Switches. In the VSPEX Private Cloud offering for up to 100 Virtual Machines, the Brocade VCS Fabric license is built into NOS. Managing Licenses The following management tasks and associated commands apply to both permanent and temporary licenses. A. Displaying the Switch License ID The switch license ID identifies the switch for which the license is valid. You will need the switch license ID when you activate a license key, if applicable. To display the switch license ID, enter the show license id command in the privileged EXEC mode, as shown. BRCD6710# show license id Rbridge-Id License ID =============================================================== 00:00:05:33:54:C6:3E B. Displaying a License You can display installed licenses with the show license command. The following example displays a Brocade VDX 6710 licensed for a VCS fabric. This configuration does not include FCoE features. BRCD6710# show license rbridge-id: 21 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx VCS Fabric license Feature name:vcs_fabric Refer to the Network OS Administrator s Guide Supporting Network OS v3.0.1 in Appendix C for additional licensing related information. Step 2: Assign and Verify VCS ID and RBridge ID Assign every switch in a VCS fabric the same VCS Fabric ID (VCS ID) and a unique RBridge ID. The VCS ID is similar to a Fabric ID in FC fabrics and the RBridge ID is similar to a Domain ID. The default VCS ID is set to 1 on each VDX switch so it does not need to be changed in a one-cluster implementation. The RBridge ID is also set to 1 by default on each VDX switch, but each switch needs its own unique ID. Value range for RBridge ID is Value range for VCS ID is Assign the RBridge ID, as shown BRCD6710# vcs rbridge-id 21 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 79

80 VSPEX Configuration Guidelines Note: Changing the RBridge ID requires a switch restart to clear any existing configuration on the switch. Before changing the VCS ID or the RBridge ID back up the switch configuration using the command copy running-config startup-config. After assigning a VCS or RBridge ID, verify the configuration using the show vcs command. Please note that the correct Config Mode for VCS is Local-Only, as shown: BRCD6710# show vcs Config Mode: Local-Only VCS ID: 1 Total Number of Nodes 2 Rbridge-Id WWN Management IP Status Host Name 21 >10:00:00:05:33:52:21:8A* Online VDX :00:00:05:33:51:A9:E Online VDX > denotes coordinator or principal switch. * denotes local switch. Step 3: Assign Switch Name Every switch is assigned the default host name of sw0. Use the switchattributes command to set a meaningful host name, as shown: BRCD6710(config)# switch-attributes 21 host-name BRCD6710-RB21 Note: To save settings across restarts run the copy running-config startup-config command after making any configuration changes. Step 4: VCS Fabric ISL Port Configuration The VDX platform comes preconfigured with a default port configuration that enables ISL and Trunking for easy and automatic VCS fabric formation. However, for edge port devices the port configuration requires editing to accommodate specific connections. The interface format is: rbridge id/slot/port number For example: 21/0/49 The default port configuration for the 10GbE ports can be seen with the show running-configuration command, as shown: BRCD6710# show running-configuration interface TenGigabitEthernet 21/0/49! interface TenGigabitEthernet 21/0/49 fabric isl enable no shutdown! <truncated output> 80 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

81 VSPEX Configuration Guidelines There are two types of ports in a VCS fabric, ISL ports, and the edge ports. The ISL port connects VCS fabric switches whereas edge ports connect to end devices or non-vcs Fabric mode switches or routers. Figure 20. VCS Fabric port types Configuring Fabric ISLs and Trunks Brocade ISLs connect VDX switches in VCS mode. All ISL ports connected to the same neighbor VDX switch attempt to form a trunk. Trunk formation requires that all ports between the switches are set to the same speed and are part of the same port group. The recommendation is to have at least two trunks with at least two links in a solution, but the number of required trunks depends on I/O requirements and the switch model. The maximum number of ports allowed per trunk group is normally eight, but the VDX 6710 only has 6 ports that can be used as fabric ISLs. Shown below are the port groups for each VDX platform. Depending on the platform solution and bandwidth requirements, it may be necessary to increase the number of trunks or links per trunk. Figure 21. VDX EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 81

82 VSPEX Configuration Guidelines As shown in Figure 21, ports on the VDX 6710 are 10G ports and form a port group. It is recommended that the VDXs in the VSPEX architecture have Fabric ISLs between them. Between two VDX 6710s, this can be achieved by connecting cables between any two 10G ports on the switches. The ISLs are self-forming. You can use the fabric isl enable, fabric trunk enable, no fabric isl enable, and no fabric trunk enable commands to toggle the port states, if needed. Below is the running configuration of an ISL port on RB21, as an example. BRCD6710# show running-config interface TenGigabitethernet 21/0/49 interface TenGigabitEthernet 21/0/49 fabric isl enable fabric trunk enable no shutdown Verify Fabric ISL and Trunk Configuration BRCD6710-RB21# show fabric isl Rbridge-id: 21 #ISLs: 2 Src Src Nbr Nbr Index Interface Index Interface Nbr-WWN BW Trunk Nbr-Name Te 21/0/49 49 Te 22/0/49 10:00:00:05:33:40:31:93 20G Yes "BRCD6710-RB22" BRCD6710-RB21# show fabric islports Name: BRCD6710-RB21 State: Online Role: Fabric Subordinate VCS Id: 1 Config Mode:Local-Only Rbridge-id: 21 WWN: 10:00:00:05:33:6d:7f:77 FCF MAC: 00:05:33:6d:7f:77 Index InterfaceState Operational State ================================================================= 1 gi 21/0/1 Down 2 gi 21/0/2 Down 3 gi 21/0/3 Down Output Truncated 49 Te 21/0/49 Up ISL (Trunk port, Primary is Te 21/0/50) 50 Te 21/0/50 Up ISL 10:00:00:05:33:00:77:80 "BRCD6710-RB22" (upstream)(trunk Primary) BRCD6710-RB21# show fabric trunk Rbridge-id: 21 Trunk Src Source Nbr Nbr Group Index Interface Index Interface Nbr-WWN Te 21/0/49 49 Te 22/0/49 10:00:00:05:33:6F:27: Te 21/0/50 50 Te 22/0/50 10:00:00:05:33:6F:27:57 82 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

83 VSPEX Configuration Guidelines Step 5: Create required VLANs The steps in this section provide guideline to create required VLANs as mentioned below: VLAN Name VLAN ID VLAN Description Storage VLAN 20 This VLAN is for iscsi traffic Cluster VLAN 30 This VLAN is for cluster live migration Management VLAN 10 Management VLAN To create a VLAN interface, perform the following steps from privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. BRCD6710-RB21# configure terminal Entering configuration mode terminal BRCD6710-RB21(config)# 2. Enter the interface VLAN command to assign the VLAN interface number. BRCD6710-RB21(config)# interface Vlan 20 BRCD6710-RB21(config-Vlan-20)# 3. Create other required VLANs as described in above table. To view defined VLANs on the RBridge use show VLAN brief command. BRCD6710-RB21# show vlan brief Total Number of VLANs configured : 4 VLAN Name State Ports (F)-FCoE, (u)-untagged, (t)-tagged, (c)-converged ======== ================================================ 1 default ACTIVE Gi 21/0/27(t) Po 44(t) Po 55(t) 10 VLAN0010 ACTIVE Gi 21/0/27(t) Po 44(t) Po 55(t) 20 VLAN0020 ACTIVE Gi 21/0/27(t) Po 44(t) Po 55(t) 30 VLAN0030 ACTIVE Gi 21/0/27(t) Po 44(t) Po 55(t) EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 83

84 VSPEX Configuration Guidelines Figure 22. Creating VLANs Step 6: Create vlag for Microsoft Server 1. Configure vlag Port-channel Interface on Brocade VDX 6710-RB21 for Host_A and Host_B. BRCD6710-RB21# configure terminal BRCD6710-RB21(config)# interface Port-channel 44 BRCD6710-RB21(config-Port-channel-44)# mtu 9216 BRCD6710-RB21(config-Port-channel-44)# speed 1000 BRCD6710-RB21(config-Port-channel-44)# description Host_A-vLAG-44 BRCD6710-RB21(config-Port-channel-44)# switchport BRCD6710-RB21(config-Port-channel-44)# switchport mode trunk BRCD6710-RB21(config-Port-channel-44)# switchport trunk allowed vlan all BRCD6710-RB21(config-Port-channel-44)# no shutdown BRCD6710-RB21# configure terminal BRCD6710-RB21(config)# interface Port-channel 55 BRCD6710-RB21(config-Port-channel-55)# mtu 9216 BRCD6710-RB21(config-Port-channel-55)# speed 1000 BRCD6710-RB21(config-Port-channel-55)# description Host_B-vLAG-55 BRCD6710-RB21(config-Port-channel-55)# switchport BRCD6710-RB21(config-Port-channel-55)# switchport mode trunk BRCD6710-RB21(config-Port-channel-55)# switchport trunk allowed vlan all BRCD6710-RB21(config-Port-channel-55)# no shutdown 84 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

85 VSPEX Configuration Guidelines 2. Configure Interface TenGigabitEthernet 21/0/10 and 21/0/11 on Brocade VDX 6710-RB21. BRCD6710-RB21# configure terminal BRCD6710-RB21(config)# interface GigabitEthernet 21/0/10 BRCD6710-RB21(conf-if-gi-21/0/10)# description Host_A-vLAG-44 BRCD6710-RB21(conf-if-gi-21/0/10)# channel-group 44 mode active type standard BRCD6710-RB21(conf-if-gi-21/0/10)# lacp timeout long BRCD6710-RB21(conf-if-gi-21/0/10)# no shutdown BRCD6710-RB21# configure terminal BRCD6710-RB21(config)# interface GigabitEthernet 21/0/11 BRCD6710-RB21(conf-if-gi-21/0/11)# description Host_B-vLAG-55 BRCD6710-RB21(conf-if-gi-21/0/11)# channel-group 55 mode active type standard BRCD6710-RB21(conf-if-gi-21/0/11)# lacp timeout long BRCD6710-RB21(conf-if-gi-21/0/11)# no shutdown 3. Configure vlag Port-channel Interface on Brocade VDX 6710-RB22 for Host_A and Host_B. BRCD6710-RB22# configure terminal BRCD6710-RB22(config)# interface Port-channel 44 BRCD6710-RB22(config-Port-channel-44)# mtu 9216 BRCD6710-RB22(config-Port-channel-44)# speed 1000 BRCD6710-RB22(config-Port-channel-44)# description Host_A-vLAG-44 BRCD6710-RB22(config-Port-channel-44)# switchport BRCD6710-RB22(config-Port-channel-44)# switchport mode trunk BRCD6710-RB22(config-Port-channel-44)# switchport trunk allowed vlan all BRCD6710-RB22(config-Port-channel-44)# no shutdown BRCD6710-RB22# configure terminal BRCD6710-RB22(config)# interface Port-channel 55 BRCD6710-RB22(config-Port-channel-55)# mtu 9216 BRCD6710-RB22(config-Port-channel-55)# speed 1000 BRCD6710-RB22(config-Port-channel-55)# description Host_B-vLAG-55 BRCD6710-RB22(config-Port-channel-55)# switchport BRCD6710-RB22(config-Port-channel-55)# switchport mode trunk BRCD6710-RB22(config-Port-channel-55)# switchport trunk allowed vlan all BRCD6710-RB22(config-Port-channel-55)# no shutdown 4. Configure Interface GigabitEthernet 22/0/10 and 21/0/11 on Brocade VDX6710-RB22. BRCD6710-RB22# configure terminal BRCD6710-RB22(config)# interface GigabitEthernet 22/0/10 BRCD6710-RB22(conf-if-gi-22/0/10)# description Host_A-vLAG-44 BRCD6710-RB22(conf-if-gi-22/0/10)# channel-group 44 mode active type standard BRCD6710-RB22(conf-if-gi-22/0/10)# lacp timeout long BRCD6710-RB22(conf-if-gi-22/0/10)# no shutdown EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 85

86 VSPEX Configuration Guidelines BRCD6710-RB22# configure terminal BRCD6710-RB22(config)# interface GigabitEthernet 22/0/11 BRCD6710-RB22(conf-if-gi-22/0/11)# description Host_B-vLAG-55 BRCD6710-RB22(conf-if-gi-22/0/11)# channel-group 55 mode active type standard BRCD6710-RB22(conf-if-gi-22/0/11)# lacp timeout long BRCD6710-RB22(conf-if-gi-22/0/11)# no shutdown 5. Validate vlag Port-channel Interface on Brocade VDX 6710-RB21 and VDX 6710-RB22 to Host_A and Host_B. BRCD6710-RB21# show interface Port-channel 44 Port-channel 44 is up, line protocol is up Hardware is AGGREGATE, address is c.adee Current address is c.adee Description: Host_A-vLAG-44 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : 1000 Mbit Allowed Member Speed : 1000 Mbit BRCD6710-RB21# show interface Port-channel 55 Port-channel 55 is up, line protocol is up Hardware is AGGREGATE, address is c.adee Current address is c.adee Description: Host_B-vLAG-55 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : 1000 Mbit Allowed Member Speed : 1000 Mbit BRCD6710-RB22# show interface Port-channel 44 Port-channel 44 is up, line protocol is up Hardware is AGGREGATE, address is c.adce Current address is c.adce Description: Host_A-vLAG-44 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : 1000 Mbit Allowed Member Speed : 1000 Mbit BRCD6710-RB22# show interface Port-channel 55 Port-channel 55 is up, line protocol is up Hardware is AGGREGATE, address is c.adee Current address is c.adee Description: Host_B-vLAG-55 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : 1000 Mbit Allowed Member Speed : 1000 Mbit 86 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

87 VSPEX Configuration Guidelines 6. Validate Interface GigabitEthernet 21/0/10 on Brocade VDX6710-RB21 and Interface GigabitEthernet 22/0/10 on Brocade BRCD6710-RB22. BRCD6710-RB21# show interface GigabitEthernet 21/0/10 GigabitEthernet 21/0/10 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_A-vLAG-44 Interface index (ifindex) is MTU 9216 bytes LineSpeed : 1000 Mbit, Duplex: Full Flowcontrol rx: off, tx: off BRCD6710-RB21# show interface GigabitEthernet 21/0/11 GigabitEthernet 21/0/11 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_B-vLAG 55 Interface index (ifindex) is MTU 9216 bytes LineSpeed : 1000 Mbit, Duplex: Full Flowcontrol rx: off, tx: off BRCD6710-RB22# show interface GigabitEthernet 22/0/10 GigabitEthernet 22/0/10 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_A-vLAG 44 Interface index (ifindex) is MTU 9216 bytes LineSpeed : 1000 Mbit, Duplex: Full Flowcontrol rx: off, tx: off BRCD6710-RB22# show interface GigabitEthernet 22/0/11 GigabitEthernet 22/0/11 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_B-vLAG 55 Interface index (ifindex) is MTU 9216 bytes LineSpeed : 1000 Mbit, Duplex: Full Flowcontrol rx: off, tx: off Step 7: Configure Switch Interfaces for VNXe 1. Configure Switch Interfaces for VNXe connections on RB21 and RB22. BRCD6710-RB21# configure terminal Entering configuration mode terminal BRCD6710-RB21(config)# interface GigabitEthernet 21/0/27 BRCD6710-RB21(conf-if-gi-21/0/27)# BRCD6710-RB21(conf-if-gi-21/0/27)# mtu 9216 BRCD6710-RB21(conf-if-gi-21/0/27)# description VNXe-Port-eth2 BRCD6710-RB21(conf-if-gi-21/0/27)# switchport BRCD6710-RB21(conf-if-gi-21/0/27)# switchport mode trunk BRCD6710-RB21(conf-if-gi-21/0/27)# switchport trunk allowed vlan all BRCD6710-RB21(conf-if-gi-21/0/27)# switchport trunk tag native-vlan BRCD6710-RB21(conf-if-gi-21/0/27)# qos flowcontrol tx on rx on BRCD6710-RB21(conf-if-gi-21/0/27)# no shutdown EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 87

88 VSPEX Configuration Guidelines BRCD6710-RB21# configure terminal Entering configuration mode terminal BRCD6710-RB21(config)# interface GigabitEthernet 21/0/28 BRCD6710-RB21(conf-if-gi-21/0/28)# BRCD6710-RB21(conf-if-gi-21/0/28)# mtu 9216 BRCD6710-RB21(conf-if-gi-21/0/28)# description VNXe-Port-eth4 BRCD6710-RB21(conf-if-gi-21/0/28)# switchport BRCD6710-RB21(conf-if-gi-21/0/28)# switchport mode trunk BRCD6710-RB21(conf-if-gi-21/0/28)# switchport trunk allowed vlan all BRCD6710-RB21(conf-if-gi-21/0/28)# switchport trunk tag native-vlan BRCD6710-RB21(conf-if-gi-21/0/28)# qos flowcontrol tx on rx on BRCD6710-RB21(conf-if-gi-21/0/28)# no shutdown BRCD6710-RB22# configure terminal Entering configuration mode terminal BRCD6710-RB22(config)# interface GigabitEthernet 22/0/27 BRCD6710-RB22(conf-if-gi-22/0/27)# BRCD6710-RB22(conf-if-gi-22/0/27)# mtu 9216 BRCD6710-RB22(conf-if-gi-22/0/27)# description VNXe-Port-eth3 BRCD6710-RB22(conf-if-gi-22/0/27)# switchport BRCD6710-RB22(conf-if-gi-22/0/27)# switchport mode trunk BRCD6710-RB22(conf-if-gi-22/0/27)# switchport trunk allowed vlan all BRCD6710-RB22(conf-if-gi-22/0/27)# switchport trunk tag native-vlan BRCD6710-RB22(conf-if-gi-22/0/27)# qos flowcontrol tx on rx on BRCD6710-RB22(conf-if-gi-22/0/27)# no shutdown BRCD6710-RB22# configure terminal Entering configuration mode terminal BRCD6710-RB22(config)# interface GigabitEthernet 22/0/28 BRCD6710-RB22(conf-if-gi-22/0/28)# BRCD6710-RB22(conf-if-gi-22/0/28)# mtu 9216 BRCD6710-RB22(conf-if-gi-22/0/28)# description VNXe-Port-eth5 BRCD6710-RB22(conf-if-gi-22/0/28)# switchport BRCD6710-RB22(conf-if-gi-22/0/28)# switchport mode trunk BRCD6710-RB22(conf-if-gi-22/0/28)# switchport trunk allowed vlan all BRCD6710-RB22(conf-if-gi-22/0/28)# switchport trunk tag native-vlan BRCD6710-RB22(conf-if-gi-22/0/28)# qos flowcontrol tx on rx on BRCD6710-RB22(conf-if-gi-22/0/28)# no shutdown 2. Validate GigabitEthernet Interface on Brocade VDX 6710-RB21 and VDX 6710-RB22 to VNXe. BRCD6710-RB21# show interface gigabitethernet 21/0/27 GigabitEthernet 21/0/27 is up, line protocol is up (connected) Hardware is Ethernet, address is Current address is Fixed Copper RJ45 Media Present Description: VNXe-Port-eth2 Interface index (ifindex) is MTU 9216 bytes LineSpeed : 1000 Mbit, Duplex: Full Flowcontrol rx: on, tx: on Priority Tag disable IPv6 RA Guard disable Last clearing of show interface counters: 1w1d22h Queueing strategy: fifo Receive Statistics: 88 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

89 VSPEX Configuration Guidelines packets, bytes Unicasts: , Multicasts: 25311, Broadcasts: byte pkts: 0, Over 64-byte pkts: , Over 127-byte pkts: Over 255-byte pkts: 348, Over 511-byte pkts: 410, Over byte pkts: 0 Over 1518-byte pkts(jumbo): 304 Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0 Errors: 149, Discards: 0 Transmit Statistics: packets, bytes Unicasts: , Multicasts: 34663, Broadcasts: Underruns: 0 Errors: 0, Discards: 0 Rate info (interval 299 seconds): Input Mbits/sec, 0 packets/sec, 0.00% of line-rate Output Mbits/sec, 1 packets/sec, 0.00% of line-rate Time since last interface status change: 1d14h02m BRCD6710-RB22# show interface gigabitethernet 22/0/27 GigabitEthernet 22/0/27 is up, line protocol is up (connected) Hardware is Ethernet, address is Current address is Fixed Copper RJ45 Media Present Description: VNXe-Port-eth3 Interface index (ifindex) is MTU 9216 bytes LineSpeed : 1000 Mbit, Duplex: Full Flowcontrol rx: on, tx: on Priority Tag disable IPv6 RA Guard disable Last clearing of show interface counters: 1w1d22h Queueing strategy: fifo Receive Statistics: 5281 packets, bytes Unicasts: 1, Multicasts: 5191, Broadcasts: byte pkts: 0, Over 64-byte pkts: 90, Over 127-byte pkts: 5191 Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0 Over 1518-byte pkts(jumbo): 0 Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0 Errors: 0, Discards: 0 Transmit Statistics: packets, bytes Unicasts: 88, Multicasts: , Broadcasts: Underruns: 0 Errors: 0, Discards: 0 Rate info (interval 299 seconds): Input Mbits/sec, 0 packets/sec, 0.00% of line-rate Output Mbits/sec, 0 packets/sec, 0.00% of line-rate Time since last interface status change: 1d08h36m EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 89

90 VSPEX Configuration Guidelines Step 8: Connecting the VCS Fabric to an existing Infrastructure through Uplinks Brocade VDX 6710 switches can be uplinked to be accessible from an existing network infrastructure. On VDX 6710 platforms, you will need to use 10G uplinks for this (ports 49-54). The uplink should be configured to match whether or not the customer s network is using tagged or untagged traffic. The following example can be leveraged as a guideline to connect VCS fabric to existing infrastructure network: Figure 23. Example VCS/VDX network topology with Infrastructure connectivity Creating virtual link aggregation groups (vlags) to the Infrastructure Network Create vlags from each RBridge to Infrastructure Switches that in turn provide access to resources at the core network. This example illustrates the configuration for RB21 and RB Use the channel-group command to configure interfaces as members of a port channel to the infrastructure switches that interface to the core. This example uses port channel 4 on Grp1, RB21. BRCD6710-RB21# configure terminal BRCD6710-RB21(config)# in te 21/0/49 BRCD6710-RB21(conf-if-te-21/0/49)# channel-group 4 mode passive type standard BRCD6710-RB21(conf-if-te-21/0/49)# in te 21/0/50 90 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

91 VSPEX Configuration Guidelines BRCD6710-RB21(conf-if-te-21/0/50)# channel-group 4 mode passive type standard 2. Use the switchport command to configure the port channel interface. In the following example, it is assigned to trunk mode and allows all VLANs on the port channel. BRCD6710-RB21(conf-if-te-21/0/50)# interface port-channel 4 BRCD6710-RB21(config-Port-channel-4)# switchport BRCD6710-RB21(config-Port-channel-4)# switchport mode trunk BRCD6710-RB21(config-Port-channel-4)# switchport trunk allowed vlan all BRCD6710-RB21(config-Port-channel-4)# no shutdown 3. Configure RB22 as shown above. BRCD6710-RB22# configure terminal BRCD6710-RB22(config)# in te 22/0/49 BRCD6710-RB22(conf-if-te-22/0/49)# channel-group 4 mode active type standard BRCD6710-RB22(conf-if-te-22/0/49)# in te 22/0/50 BRCD6710-RB22(conf-if-te-22/0/50)# channel-group 4 mode active type standard BRCD6710-RB22(config)# interface port-channel 4 BRCD6710-RB22(config-Port-channel-4)# switchport BRCD6710-RB22(config-Port-channel-4)# switchport mode trunk BRCD6710-RB22(config-Port-channel-4)# switchport trunk allowed vlan all BRCD6710-RB22(config-Port-channel-4)# no shutdown 4. Use the do show port-chan command to confirm that the vlag comes up and is configured correctly. Note: The LAG must be configured on the MLX MCT as well before the vlag can become operational. BRCD6710-RB21(config-Port-channel-4)# do show port-chan 4 LACP Aggregator: Po 4 (vlag) Aggregator type: Standard Ignore-split is enabled Member rbridges: rbridge-id: 21 (2) rbridge-id: 22 (2) Admin Key: Oper Key 0004 Partner System ID - 0x0001,01-80-c Partner Oper Key Member ports on rbridge-id 21: Link: Te 21/0/49 (0x F) sync: 1 * Link: Te 21/0/50 (0x ) sync: 1 BRCD6710-RB22(config-Port-channel-4)# do show port-channel 4 LACP Aggregator: Po 4 (vlag) Aggregator type: Standard Ignore-split is enabled Member rbridges: rbridge-id: 21 (2) EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 91

92 VSPEX Configuration Guidelines rbridge-id: 22 (2) Admin Key: Oper Key 0004 Partner System ID - 0x0001,01-80-c Partner Oper Key Member ports on rbridge-id 22: Link: Te 22/0/49 (0x F) sync: 1 Link: Te 22/0/50 (0x ) sync: 1 Step 9 - Configure MTU and Jumbo Frames Brocade recommends using Jumbo frames for an iscsi based architecture such as this. Set the MTU to 9216 for the switch ports used for storage network of iscsi, CIFS, or NFS protocols. Consult the Brocade configuration guide for additional details. Configuring MTU Note This must be performed on all RBbridges where a given interface portchannel is located. In this example, interface port-channel 44 is on RBridge 21 and RBridge 22, so we will apply configurations from both RBridge 21 and RBridge 22. Example to enable Jumbo Frame Support on applicable VDX interfaces for which Jumbo Frame support is required: BRCD6710# configure terminal BRCD6710(config)# interface Port-channel 44 BRCD6710(config-Port-channel-44)# mtu (<NUMBER: >) (9216): 9216 Step 10 - AMPP configuration for live migrations Brocade AMPP (Automatic Migration of Port Profiles) technology enhances network-side virtual machine migration by allowing VM migration across physical switches, switch ports, and collision domains. In traditional networks, port-migration tasks usually require manual configuration changes as VM migration across physical server and switches can result in non-symmetrical network policies. Port setting information must be identical at the destination switch and port. Brocade VCS Fabrics support automatically moving the port profile in synchronization with a VM moving to a different physical server. This allows VMs to be migrated without the need for network ports to be manually configured on the destination switch. Please refer AMPP Configuration section of Network OS Administration Guide for AMPP configuration and monitoring. 92 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

93 VSPEX Configuration Guidelines Brocade VDX 6720 Configuration Use the following procedure to configure a VDX 6720 based fabric. During the switch configuration process, some of the configuration commands may require a switch restart. To save settings across restarts, run the copy running-config startup-config command after making any configuration changes. Note: Before running a command that requires a switch restart, back up the switch configuration using the copy running-config startupconfig, as shown: BRCD6720# copy running-config startup-config This operation will modify your startup configuration. Do you want to continue? [y/n]:y Step 1: Verify VDX NOS Licenses Before starting the switch configurations, make sure you have the required licenses available for the VDX 6720 Switches. In the VSPEX Private Cloud offering for up to 100 Virtual Machines, the Brocade VCS Fabric license is built into NOS. VDX and VDX have a Ports on Demand (PoD) incremental license feature. Managing Licenses The following management tasks and associated commands apply to both permanent and temporary licenses. Note: License management in Network OS v3.0.1 is supported only on the local RBridge. You cannot configure or display licenses on remote nodes in the fabric. A. Displaying the Switch License ID The switch license ID identifies the switch for which the license is valid. You will need the switch license ID when you activate a license key, if applicable. To display the switch license ID, enter the show license id command in the privileged EXEC mode, as shown. VDX6720# show license id Rbridge-Id License ID =================================================== 22 10:00:00:05:33:51:A9:E5 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 93

94 VSPEX Configuration Guidelines B. Displaying a License You can display installed licenses with the show license command. The following example displays a Brocade VDX 6720 licensed for a VCS fabric. This configuration does not include FCoE features. VDX6720# show license rbridge-id: 22 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Ports on Demand license - additional 10 port upgrade license Feature name:ports_on_demand_1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Ports on Demand license - additional 10 port upgrade license Feature name:ports_on_demand_2 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx VCS Fabric license Feature name:vcs_fabric Refer to Network OS Administrator s Guide Supporting Network OS v3.0.1 in Appendix C for additional licensing related information. Step 2: Assign and Verify VCS ID and RBridge ID Assign every switch in a VCS fabric the same VCS Fabric ID (VCS ID) and a unique RBridge ID. The VCS ID is similar to a Fabric ID in FC fabrics and the RBridge ID is similar to a Domain ID. The default VCS ID is set to 1 on each VDX switch so it does not need to be changed in a one-cluster implementation. The RBridge ID is also set to 1 by default on each VDX switch, but if more than one switch is to be added to the fabric then each switch needs its own unique ID. Value range for RBridge ID is Value range for VCS ID is Assign the RBridge ID, as shown BRCD6720# vcs rbridge-id 21 Note: Changing the RBridge ID requires a switch restart to clear any existing configuration on the switch. Before changing the VCS ID or the RBridge ID back up the switch configuration using the copy running-config startupconfig command. 94 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

95 VSPEX Configuration Guidelines After assigning a VCS or RBridge ID, verify the configuration using the show vcs command. Please note that the correct Config Mode for VCS is Local-Only, as shown: BRCD6720# show vcs Config Mode: Local-Only VCS ID 1 Total Number of Nodes: 2 Rbridge-Id WWN Management IP Status Host Names 21 >10:00:00:05:33:52:21:8A* Online VDX :00:00:05:33:51:A9:E Online VDX > denotes coordinator or principal switch. * denotes local switch Step 3: Assign Switch Name Every switch is assigned the default host name of sw0, but must be changed for easy recognition and management using the switchattributes command. Use the switch-attributes command to set host name, as shown: BRCD6720# configure terminal BRCD6720(config)# switch-attributes 21 host-name BRCD6720-RB21 Note: To save settings across restarts run the copy running-config startup-config command after making any configuration changes. Step 4: VCS Fabric ISL Port Configuration The VDX platform comes preconfigured with a default port configuration that enables ISL and Trunking for easy and automatic VCS fabric formation. However, for edge port devices the port configuration requires editing to accommodate specific connections. The interface format is: rbridge id/slot/port number e.g 21/0/49 The default port configuration for the 10GbE ports can be seen with the show running-configuration command, as shown: BRCD6720# show running-configuration interface TenGigabitEthernet 21/0/49! interface TenGigabitEthernet 21/0/49 fabric isl enable fabric trunk enable no shutdown!. <truncated output> There are two types of ports in a VCS fabric, ISL ports, and the edge ports. The ISL port connects VCS fabric switches whereas edge ports connect to end devices or non-vcs Fabric mode switches or routers. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 95

96 VSPEX Configuration Guidelines Figure 24. Port types Configuring Fabric ISLs and Trunks Brocade ISLs connect VDX switches in VCS mode. All ISL ports connected to the same neighbor VDX switch attempt to form a trunk. Trunk formation requires that all ports between the switches are set to the same speed and are part of the same port group. The recommendation is to have at least two trunks with at least two links in a solution, but the number of required trunks depends on I/O requirements and the switch model. The maximum number of ports allowed per trunk group is normally eight. Shown below are the port groups for the VDX 6720 platforms. Depending on the platform solution and bandwidth requirements, it may be necessary to increase the number of trunks or links per trunk. Figure 25. VDX EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

97 VSPEX Configuration Guidelines Figure 26. VDX It is recommended that the VDXs in the VSPEX architecture have Fabric ISLs between them. Between two VDX 6720 switches, this can be achieved by connecting cables between any two 10G ports on the switches. The ISLs are self-forming. You can use the fabric isl enable, fabric trunk enable, no fabric isl enable, and no fabric trunk enable commands to toggle the port states, if needed. The following example shows the running configuration of an ISL port on RB21. BRCD6720# show running-config interface TenGigabitethernet 21/0/49 interface TenGigabitEthernet 21/0/49 fabric isl enable fabric trunk enable no shutdown Verify Fabric ISL and Trunk Configuration BRCD6720-RB21# show fabric isl Rbridge-id: 21 #ISLs: 2 Src Src Nbr Nbr Index Interface Index Interface Nbr-WWN BW Trunk Nbr-Name 49 Te 21/0/49 49 Te 22/0/49 10:00:00:05:33:40:31:93 20G Yes "BRCD6720-RB22" BRCD6720-RB21# show fabric islports Name: BRCD6720-RB21 State: Online Role: Fabric Subordinate VCS Id: 1 Config Mode:Local-Only Rbridge-id: 21 WWN: 10:00:00:05:33:6d:7f:77 FCF MAC: 00:05:33:6d:7f:77 Index InterfaceState Operational State 1 Te 21/0/1 Down 2 Te 21/0/2 Down 3 Te 21/0/3 Down Output Truncated 49 Te 21/0/49 Up ISL (Trunk port, Primary is Te 21/0/50) 50 Te 21/0/50 Up ISL 10:00:00:05:33:00:77:80 "BRCD6720-RB22" (upstream)(trunk Primary) BRCD6720-RB21# show fabric trunk EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 97

98 VSPEX Configuration Guidelines Rbridge-id: 21 Trunk Src Source Nbr Nbr Group Index Interface Index Interface Nbr-WWN Te 21/0/49 49 Te 22/0/49 10:00:00:05:33:6F:27: Te 21/0/50 50 Te 22/0/50 10:00:00:05:33:6F:27:57 Step 5: Create required VLANs The steps in this section provide guideline to create required VLANs as mentioned below: VLAN Name VLAN ID VLAN Description Storage VLAN 20 This VLAN is for iscsi traffic Cluster VLAN 30 This VLAN is for cluster live migration Management VLAN 10 Management VLAN To create a VLAN interface, perform the following steps from privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. BRCD6720-RB21# configure terminal Entering configuration mode terminal BRCD6720-RB21(config)# 2. Enter the interface vlan command to assign the VLAN interface number. BRCD6720-RB21(config)# interface Vlan 20 BRCD6720-RB21(config-Vlan-20)# 3. Create other required VLANs as described in above table. To view defined VLANs on the RBridge use show vlan brief command : BRCD6720-RB21# show vlan brief Total Number of VLANs configured : 4 VLAN Name State Ports (F)-FCoE, (u)-untagged, (t)-tagged, (c)-converged ================================================ 1 default ACTIVE Te 21/0/27(t) Po 44(t) Po 55(t) 10 VLAN0010 ACTIVE Te 21/0/27(t) Po 44(t) Po 55(t) 20 VLAN0020 ACTIVE Te 21/0/27(t) Po 44(t) Po 55(t) 30 VLAN0030 ACTIVE Te 21/0/27(t) Po 44(t) Po 55(t) 98 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

99 Brocade VDX 6720 RLOM Brocade VDX 6720 RLOM VSPEX Configuration Guidelines VNXe VDX6720-RB21 10G 10G 10G 10G VDX6720-RB22 20G Brocade Trunk 10G 10G 10G 10G vlag Po 44 vlag Po 55 Host A Host B Figure 27. Creating VLANs Step 6: Create vlag for Microsoft Server 1. Configure vlag Port-channel Interface on Brocade VDX RB21 for Host_A and Host_B. BRCD6720-RB21# configure terminal BRCD6720-RB21(config)# interface Port-channel 44 BRCD6720-RB21(config-Port-channel-44)# mtu 9216 BRCD6720-RB21(config-Port-channel-44)# speed BRCD6720-RB21(config-Port-channel-44)# description Host_A-vLAG-44 BRCD6720-RB21(config-Port-channel-44)# switchport BRCD6720-RB21(config-Port-channel-44)# switchport mode trunk BRCD6720-RB21(config-Port-channel-44)# switchport trunk allowed vlan all BRCD6720-RB21(config-Port-channel-44)# no shutdown BRCD6720-RB21# configure terminal BRCD6720-RB21(config)# interface Port-channel 55 BRCD6720-RB21(config-Port-channel-55)# mtu 9216 BRCD6720-RB21(config-Port-channel-55)# speed BRCD6720-RB21(config-Port-channel-55)# description Host_B-vLAG-55 BRCD6720-RB21(config-Port-channel-55)# switchport BRCD6720-RB21(config-Port-channel-55)# switchport mode trunk BRCD6720-RB21(config-Port-channel-55)# switchport trunk allowed vlan all BRCD6720-RB21(config-Port-channel-55)# no shutdown EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 99

100 VSPEX Configuration Guidelines 2. Configure Interface TenGigabitEthernet 21/0/10 and 21/0/11 on Brocade VDX6720-RB21. BRCD6720-RB21# configure terminal BRCD6720-RB21(config)# interface TenGigabitEthernet 21/0/10 BRCD6720-RB21(conf-if-te-21/0/10)# description Host_A-vLAG-44 BRCD6720-RB21(conf-if-te-21/0/10)# channel-group 44 mode active type standard BRCD6720-RB21(conf-if-te-21/0/10)# lacp timeout long BRCD6720-RB21(conf-if-te-21/0/10)# no shutdown BRCD6720-RB21# configure terminal BRCD6720-RB21(config)# interface TenGigabitEthernet 21/0/11 BRCD6720-RB21(conf-if-te-21/0/11)# description Host_B-vLAG-55 BRCD6720-RB21(conf-if-te-21/0/11)# channel-group 55 mode active type standard BRCD6720-RB21(conf-if-te-21/0/11)# lacp timeout long BRCD6720-RB21(conf-if-te-21/0/11)# no shutdown 3. Configure vlag Port-channel Interface on Brocade VDX RB22 for Host_A and Host_B. BRCD6720-RB22# configure terminal BRCD6720-RB22(config)# interface Port-channel 44 BRCD6720-RB22(config-Port-channel-44)# mtu 9216 BRCD6720-RB22(config-Port-channel-44)# speed BRCD6720-RB22(config-Port-channel-44)# description Host_A-vLAG-44 BRCD6720-RB22(config-Port-channel-44)# switchport BRCD6720-RB22(config-Port-channel-44)# switchport mode trunk BRCD6720-RB22(config-Port-channel-44)# switchport trunk allowed vlan all BRCD6720-RB22(config-Port-channel-44)# no shutdown BRCD6720-RB22# configure terminal BRCD6720-RB22(config)# interface Port-channel 55 BRCD6720-RB22(config-Port-channel-55)# mtu 9216 BRCD6720-RB22(config-Port-channel-55)# speed BRCD6720-RB22(config-Port-channel-55)# description Host_B-vLAG-55 BRCD6720-RB22(config-Port-channel-55)# switchport BRCD6720-RB22(config-Port-channel-55)# switchport mode trunk BRCD6720-RB22(config-Port-channel-55)# switchport trunk allowed vlan all BRCD6720-RB22(config-Port-channel-55)# no shutdown 4. Configure Interface TenGigabitEthernet 22/0/10 and 21/0/11 on Brocade VDX6720-RB22. BRCD6720-RB22# configure terminal BRCD6720-RB22(config)# interface TenGigabitEthernet 22/0/10 BRCD6720-RB22(conf-if-te-22/0/10)# description Host_A-vLAG-44 BRCD6720-RB22(conf-if-te-22/0/10)# channel-group 44 mode active type standard BRCD6720-RB22(conf-if-te-22/0/10)# lacp timeout long BRCD6720-RB22(conf-if-te-22/0/10)# no shutdown 100 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

101 VSPEX Configuration Guidelines EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 101

102 VSPEX Configuration Guidelines BRCD6720-RB22# configure terminal BRCD6720-RB22(config)# interface TenGigabitEthernet 22/0/11 BRCD6720-RB22(conf-if-te-22/0/11)# description Host_B-vLAG-55 BRCD6720-RB22(conf-if-te-22/0/11)# channel-group 55 mode active type standard BRCD6720-RB22(conf-if-te-22/0/11)# lacp timeout long BRCD6720-RB22(conf-if-te-22/0/11)# no shutdown 5. Validate vlag Port-channel Interface on Brocade VDX 6720-RB21 and VDX 6720-RB22 to Host_A and Host_B. BRCD6720-RB21# show interface Port-channel 44 Port-channel 44 is up, line protocol is up Hardware is AGGREGATE, address is c.adee Current address is c.adee Description: Host_A-vLAG-44 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : Mbit Allowed Member Speed : Mbit BRCD6720-RB21# show interface Port-channel 55 Port-channel 55 is up, line protocol is up Hardware is AGGREGATE, address is c.adee Current address is c.adee Description: Host_B-vLAG-55 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : Mbit Allowed Member Speed : Mbit BRCD6720-RB22# show interface Port-channel 44 Port-channel 44 is up, line protocol is up Hardware is AGGREGATE, address is c.adce Current address is c.adce Description: Host_A-vLAG-44 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : Mbit Allowed Member Speed : Mbit BRCD6720-RB22# show interface Port-channel 55 Port-channel 55 is up, line protocol is up Hardware is AGGREGATE, address is c.adee Current address is c.adee Description: Host_B-vLAG-55 Interface index (ifindex) is Minimum number of links to bring Port-channel up is 1 MTU 9216 bytes LineSpeed Actual : Mbit Allowed Member Speed : Mbit 102 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

103 VSPEX Configuration Guidelines 6. Validate Interface TenGigabitEthernet 21/0/10 on Brocade VDX6720-RB21 and Interface TenGigabitEthernet 22/0/10 on Brocade BRCD6720-RB22. BRCD6720-RB21# show interface TenGigabitEthernet 21/0/10 TenGigabitEthernet 21/0/10 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_A-vLAG-44 Interface index (ifindex) is MTU 9216 bytes LineSpeed : Mbit, Duplex: Full Flowcontrol rx: off, tx: off BRCD6720-RB21# show interface TenGigabitEthernet 21/0/11 TenGigabitEthernet 21/0/11 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_B-vLAG 55 Interface index (ifindex) is MTU 9216 bytes LineSpeed : Mbit, Duplex: Full Flowcontrol rx: off, tx: off BRCD6720-RB22# show interface TenGigabitEthernet 22/0/10 TenGigabitEthernet 22/0/10 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_A-vLAG 44 Interface index (ifindex) is MTU 9216 bytes LineSpeed : Mbit, Duplex: Full Flowcontrol rx: off, tx: off BRCD6720-RB22# show interface TenGigabitEthernet 22/0/11 TenGigabitEthernet 22/0/11 is up, line protocol is up (connected) Hardware is Ethernet, address is c.adb6 Current address is c.adb6 Description: Host_B-vLAG 55 Interface index (ifindex) is MTU 9216 bytes LineSpeed : Mbit, Duplex: Full Flowcontrol rx: off, tx: off EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 103

104 VSPEX Configuration Guidelines Step 7: Configure Switch Interfaces for VNXe 1. Configure Switch Interfaces for VNXe connections on RB21 and RB22. BRCD6720-RB21# configure terminal Entering configuration mode terminal BRCD6720-RB21(config)# interface TenGigabitEthernet 21/0/27 BRCD6720-RB21(conf-if-te-21/0/27)# BRCD6720-RB21(conf-if-te-21/0/27)# mtu 9216 BRCD6720-RB21(conf-if-te-21/0/27)# description VNXe-Port-eth2 BRCD6720-RB21(conf-if-te-21/0/27)# switchport BRCD6720-RB21(conf-if-te-21/0/27)# switchport mode trunk BRCD6720-RB21(conf-if-te-21/0/27)# switchport trunk allowed vlan all BRCD6720-RB21(conf-if-te-21/0/27)# switchport trunk tag nativevlan BRCD6720-RB21(conf-if-te-21/0/27)# qos flowcontrol tx on rx on BRCD6720-RB21(conf-if-te-21/0/27)# no shutdown BRCD6720-RB21# configure terminal Entering configuration mode terminal BRCD6720-RB21(config)# interface TenGigabitEthernet 21/0/28 BRCD6720-RB21(conf-if-te-21/0/28)# BRCD6720-RB21(conf-if-te-21/0/28)# mtu 9216 BRCD6720-RB21(conf-if-te-21/0/28)# description VNXe-Port-eth4 BRCD6720-RB21(conf-if-te-21/0/28)# switchport BRCD6720-RB21(conf-if-te-21/0/28)# switchport mode trunk BRCD6720-RB21(conf-if-te-21/0/28)# switchport trunk allowed vlan all BRCD6720-RB21(conf-if-te-21/0/28)# switchport trunk tag nativevlan BRCD6720-RB21(conf-if-te-21/0/28)# qos flowcontrol tx on rx on BRCD6720-RB21(conf-if-te-21/0/28)# no shutdown BRCD6720-RB22# configure terminal Entering configuration mode terminal BRCD6720-RB22(config)# interface TenGigabitEthernet 22/0/27 BRCD6720-RB22(conf-if-te-22/0/27)# BRCD6720-RB22(conf-if-te-22/0/27)# mtu 9216 BRCD6720-RB22(conf-if-te-22/0/27)# description VNXe-Port-eth3 BRCD6720-RB22(conf-if-te-22/0/27)# switchport BRCD6720-RB22(conf-if-te-22/0/27)# switchport mode trunk BRCD6720-RB22(conf-if-te-22/0/27)# switchport trunk allowed vlan all BRCD6720-RB22(conf-if-te-22/0/27)# switchport trunk tag nativevlan BRCD6720-RB22(conf-if-te-22/0/27)# qos flowcontrol tx on rx on BRCD6720-RB22(conf-if-te-22/0/27)# no shutdown BRCD6720-RB22# configure terminal Entering configuration mode terminal 104 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

105 VSPEX Configuration Guidelines BRCD6720-RB22(config)# interface TenGigabitEthernet 22/0/28 BRCD6720-RB22(conf-if-te-22/0/28)# BRCD6720-RB22(conf-if-te-22/0/28)# mtu 9216 BRCD6720-RB22(conf-if-te-22/0/28)# description VNXe-Port-eth5 BRCD6720-RB22(conf-if-te-22/0/28)# switchport BRCD6720-RB22(conf-if-te-22/0/28)# switchport mode trunk BRCD6720-RB22(conf-if-te-22/0/28)# switchport trunk allowed vlan all BRCD6720-RB22(conf-if-te-22/0/28)# switchport trunk tag nativevlan BRCD6720-RB22(conf-if-te-22/0/28)# qos flowcontrol tx on rx on BRCD6720-RB22(conf-if-te-22/0/28)# no shutdown 2. Validate TenGigabitEthernet Interface on Brocade VDX 6720-RB21 and VDX 6720-RB22 to VNXe. BRCD6720-RB21# show interface TenGigabitEthernet 21/0/27 TenGigabitEthernet 21/0/27 is up, line protocol is up (connected) Hardware is Ethernet, address is Current address is Fixed Copper RJ45 Media Present Description: VNXe-Port-eth2 Interface index (ifindex) is MTU 9216 bytes LineSpeed : Mbit, Duplex: Full Flowcontrol rx: on, tx: on Priority Tag disable IPv6 RA Guard disable Last clearing of show interface counters: 1w1d22h Queueing strategy: fifo Receive Statistics: packets, bytes Unicasts: , Multicasts: 25311, Broadcasts: byte pkts: 0, Over 64-byte pkts: , Over 127-byte pkts: Over 255-byte pkts: 348, Over 511-byte pkts: 410, Over byte pkts: 0 Over 1518-byte pkts(jumbo): 304 Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0 Errors: 149, Discards: 0 Transmit Statistics: packets, bytes Unicasts: , Multicasts: 34663, Broadcasts: Underruns: 0 Errors: 0, Discards: 0 Rate info (interval 299 seconds): Input Mbits/sec, 0 packets/sec, 0.00% of line-rate Output Mbits/sec, 1 packets/sec, 0.00% of line-rate Time since last interface status change: 1d14h02m EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 105

106 VSPEX Configuration Guidelines BRCD6720-RB22# show interface TenGigabitEthernet 22/0/27 TenGigabitEthernet 22/0/27 is up, line protocol is up (connected) Hardware is Ethernet, address is Current address is Fixed Copper RJ45 Media Present Description: VNXe-Port-eth3 Interface index (ifindex) is MTU 9216 bytes LineSpeed : Mbit, Duplex: Full Flowcontrol rx: on, tx: on Priority Tag disable IPv6 RA Guard disable Last clearing of show interface counters: 1w1d22h Queueing strategy: fifo Receive Statistics: 5281 packets, bytes Unicasts: 1, Multicasts: 5191, Broadcasts: byte pkts: 0, Over 64-byte pkts: 90, Over 127-byte pkts: 5191 Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0 Over 1518-byte pkts(jumbo): 0 Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0 Errors: 0, Discards: 0 Transmit Statistics: packets, bytes Unicasts: 88, Multicasts: , Broadcasts: Underruns: 0 Errors: 0, Discards: 0 Rate info (interval 299 seconds): Input Mbits/sec, 0 packets/sec, 0.00% of line-rate Output Mbits/sec, 0 packets/sec, 0.00% of line-rate Time since last interface status change: 1d08h36m 106 EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric Technology, EMC VNXe and EMC Next-Generation Backup

107 VSPEX Configuration Guidelines Step 8: Connecting the VCS Fabric to an existing Infrastructure through Uplinks Brocade VDX 6720 switches can be uplinked to be accessible from an existing network infrastructure. On VDX 6720 platforms, you will need to use 10G uplinks for this (ports 49-54). The uplink should be configured to match whether or not the customer s network is using tagged or untagged traffic. The following example can be leveraged as a guideline to connect VCS fabric to existing infrastructure network: Figure 28. Example VCS/VDX network topology with Infrastructure connectivity Creating virtual link aggregation groups (vlags) to the Infrastructure Network Create vlags from each RBridge to Infrastructure Switches that in turn provide access to resources at the core network. This example illustrates the configuration for RB21 and RB Use the channel-group command to configure interfaces as members of a port channel to the infrastructure switches that interface to the core. This example uses port channel 4 on Grp1, RB21. EMC VSPEX with Brocade Networking Solutions for Private Cloud Microsoft Windows Server 2012 with Hyper-V for up to 100 Virtual Machines Enabled by Brocade VDX with VCS Fabric 107