Copyright 2015 EMC Corporation. All rights reserved. Published in the USA.

Transcription

1 This solution guide describes how to deploy an SAP environment on the Federation Enterprise Hybrid Cloud with VMware vrealize Automation as its core. This solution addresses provisioning and key security, migration, and operational efficiency challenges specific to an SAP infrastructure. October 2015

2 Copyright 2015 EMC Corporation. All rights reserved. Published in the USA. Published October 2015 EMC believes the information in this publication is accurate as 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, VMAX, VNX, Isilon, XtremIO, ScaleIO, VPLEX, ViPR, RecoverPoint, Data Domain, Avamar, Data Protection Advisor, 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 listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Federation Enterprise Hybrid Cloud 3.1: Foundation for SAP Solution Guide Part Number H

3 Contents Chapter 1 Executive Summary... 6 Federation Enterprise Hybrid Cloud Solution as an SAP Solution... 7 Solution overview... 7 Key benefits... 8 Chapter 2 Introduction... 9 Document purpose Essential reading Audience Terminology Chapter 3 Technology Overview Technology resources Key components Federation Enterprise Hybrid Cloud Blue Medora vrealize Operations Management Pack for SAP CCMS SAP ERP EMC, VMware, and SAP integration SAP integration Chapter 4 Solution Architecture Design Delivery strategy Foundation infrastructure functionality Automation and self-service provisioning Multitenancy and secure separation Security Workload-optimized storage Elasticity and service assurance Monitoring and resource management Metering and chargeback Modular add-on services Application services Data protection: Backup Data protection: Continuous availability Data protection: Disaster recovery SAP-specific enhancements Chapter 5 Migration Overview Scenarios and procedures Scenario 1: Virtual machines in the same vcenter as Federation Enterprise Hybrid Cloud

4 Contents Scenario 2: Virtual machines in a non-federation Enterprise Hybrid Cloud vcenter that will be connected as an endpoint Validation Creating blueprints to automate the import of virtual machines Importing existing virtual machines Verifying that Federation Enterprise Hybrid Cloud can manage virtual machines Test results Chapter 6 Self-Service SAP Provisioning Overview Automating a standard SAP installation Automating a distributed installation Automating an SAP AAS installation How auto-provisioning works Self-service provisioning Verifying prerequisites Creating an SAP-ready virtual machine template Setting up silent installation scripts Creating application blueprints Deploying the automation workflow Validation Test scenario Test scenario Chapter 7 Networking and Security Overview Multitenant security Solution architecture Logical network topology Validation Test scenario Test objectives Test procedure Test results Chapter 8 Cloud Monitoring and Root Cause Analysis Overview of monitoring SAP monitoring ViPR SRM and vrealize Operations Manager Blue Medora configuration Customized monitoring dashboard Validation Test scenario Test procedure and results Chapter 9 Conclusion Conclusion

5 Contents Figures Figure 1. Federation Enterprise Hybrid Cloud for SAP technology components Figure 2. EMC, VMware, and SAP integration points Figure 3. Federation Enterprise Hybrid Cloud foundation infrastructure features and functionality Figure 4. vrealize Automation catalog view Figure 5. Creating a blueprint for existing virtual machines Figure 6. Importing existing virtual machines Figure 7. Assigning a business group to the imported virtual machines Figure 8. Applying a blueprint to the imported virtual machines Figure 9. Managing machines using the Actions menu Figure 10. Detailed information on the virtual machines managed by vrealize Automation Figure 11. Process flow of a standard SAP installation Figure 12. Distributed SAP installation workflow Figure 13. User workflow in self-provisioning an SAP system using vrealize Automation Figure 14. SAP blueprint interface in vrealize Application Services Figure 15. Auto-provisioning an SAP distributed system Figure 16. Node Properties tab for an SAP distributed installation Figure 17. Service Properties tab for an SAP distributed installation Figure 18. Summary of process flow after provisioning Figure 19. Provisioning an AAS system and associating it to an existing SAP standard system Figure 20. Security logical infrastructure Figure 21. Sample segregation scenario Figure 22. Firewall rules Figure 23. RFC connection test from PIP to EP Figure 24. Test results for firewall rules Figure 25. vrealize Operations performance dashboard for an SAP tenant administrator Figure 26. Tenant A s SAP system DX1 and EP1 performance dashboard Figure 27. End-to-end view from the virtual machine to storage Figure 28. Performance dashboard on EMC ViPR SRM Tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Terminology Solution resources Virtual machine specification and installation media Detailed information on tested SAP systems Use case test results Virtual-machine-to-array performance analysis in EMC ViPR SRM

6 Chapter 1: Executive Summary This chapter presents the following topics: Federation Enterprise Hybrid Cloud Solution as an SAP Solution... 7 Solution overview... 7 Key benefits

7 Chapter 1: Executive Summary All cloud solutions should improve operational efficiency, scale resources up and down as needed, and reduce the total cost of ownership (TCO) over time. Why would a company that already uses either a private or public cloud consider using the other cloud type? To answer this question, compare and understand the key strengths of their respective architectures. Public clouds are complex implementations. The cost of maintaining systems at this level can be very high. As more companies share the expenditure on overheads, leased resources become cheaper for each tenant. Your company does not have to assign resources to maintain the cloud but you will have limited control over your systems. Private clouds reside within your own company. Your internal IT department maintains these systems, giving you full ownership of your critical data and complete control of every part of the infrastructure. You can customize and protect your cloud environment to precisely meet your business needs, deploy technologies that may not be offered in other cloud environments, and respond to incidents more quickly. A hybrid cloud enables you to achieve a balance between cost and criticality by keeping business-critical SAP and non-sap systems in your on-premises Federation Enterprise Hybrid Cloud solution, while keeping the remainder of your systems in a less expensive, remote cloud. You maintain absolute control over your company s privately owned resources. A private-to-public integration is a popular hybrid deployment for a variety of reasons: Lower TCO: Keeping all critical production (PRD) SAP systems in a private cloud while deploying all development (DEV) and quality assurance (QAS) systems on a public cloud is typically less expensive for an organization due to the economies of scale. Resource expansion: A hybrid cloud removes the hardware limits of a private cloud by extending several of its workload and functionalities to a public cloud's much larger resource pool. Testing cloud options: An organization that has yet to build its own cloud can opt to test on a public cloud until they are comfortable enough to invest, build, and manage their own private cloud. Federation Enterprise Hybrid Cloud is a flexible architecture for SAP. You can customize this solution with the following SAP-specific capabilities: Migration of SAP systems into the Federation Enterprise Hybrid Cloud Self-service SAP provisioning Networking and security for SAP landscapes SAP cloud monitoring and root-cause analysis This solution considers the unique requirements of SAP system landscapes in terms of deployment, operations, and evolution. It takes advantage of the strong integration between EMC technologies and the VMware vrealize Suite to deliver a hybrid cloud foundation that is simple to deploy and operate. The solution, developed by EMC and VMware product and services teams, includes EMC scalable storage arrays, integrated EMC and VMware monitoring, and data protection suites to provide the foundation for enabling cloud services within the customer environment. 7

8 Chapter 1: Executive Summary As a direct application of the Federation Enterprise Hybrid Cloud to an SAP environment, this solution offers several key benefits to customers: Rapid implementation: The solution can be designed and implemented in as few as 28 days, in a validated, tested, and repeatable way. This increases the time-to-value for the customer while simultaneously reducing risk. Supported solution: Implementing the Federation Enterprise Hybrid Cloud through EMC results in a solution supported by EMC and further reduces risks associated with the ongoing operations of your hybrid cloud. Defined upgrade path: Customers implementing the Federation Enterprise Hybrid Cloud receive upgrade guidance based on the testing and validation that is completed by the Federation engineering teams. This guidance enables customers, partners, and EMC services teams to perform upgrades faster and with much less risk. Validated and tested integration: Engineers have developed build guides and performed extensive integration testing for the solution, making it simpler to use and manage, and more efficient to operate. Federation: EMC II, Pivotal, RSA, VCE, and VMware form a unique Federation of strategically aligned businesses; each can operate individually or together. The Federation provides customer solutions and choice for the software-defined enterprise and the emerging third platform of mobile, cloud, Big Data, and social networking, which is transformed by billions of users and millions of apps. 8

9 Chapter 2: Introduction This chapter presents the following topics: Document purpose Essential reading Audience Terminology

10 Chapter 2: Introduction This solution guide is the first in a series of guides that describe the design and specific configurations that are needed for an SAP environment to maximize the capabilities of the Federation Enterprise Hybrid Cloud. This solution is a direct application of the Federation Enterprise Hybrid Cloud to an SAP environment. This document describes the foundation infrastructure solution for SAP and serves as a guide for SAP customers who plan to deploy their SAP environment on an existing, fully functional Federation Enterprise Hybrid Cloud foundation infrastructure. The document focuses on the SAP-related architecture, design, and implementation best practices for the deployment. While this document includes some content from the Federation Enterprise Hybrid Cloud 3.1: Concepts and Architecture Solution Guide, it does not include detailed information about products and functionalities specific to Federation Enterprise Hybrid Cloud. This guide provides critical reference information for planning and designing a data protection solution for the hybrid cloud. To understand the concepts, architecture, and functionalities of the Federation Enterprise Hybrid Cloud and how to operate SAP on top of it, you are advised to read the following documents: Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide Federation Enterprise Hybrid Cloud 3.1: Concepts and Architecture Solution Guide Federation Enterprise Hybrid Cloud 3.1: Operations Solution Guide Federation Enterprise Hybrid Cloud 3.1: Security Management Solution Guide This document is intended for the following: SAP implementation consultants, engineers, and administrators Technical architects and cloud solution engineers currently running or planning to implement an SAP environment in a cloud computing model Readers are expected to have basic competency in EMC, VMware, and SAP implementations and operations. The target audience must have a reasonable understanding of cloud computing while being fully aware of what their end users expect. These expectations include security, monitoring, resource management, multitenancy, and service metering. Table 1 defines key terms relevant to this solution that are used in this document. Table 1. Terminology Term BAPI Definition Business Application Programming Interface. A precisely defined interface that provides access to processes and data in business application systems such as R/3. 10

11 Chapter 2: Introduction Term DEV Off premises On premises PRD QAS Definition SAP Development System. An SAP system built for SAP programmers and consultants to develop programs and configurations. The application or service is running on resources (hardware, software, locations) that are owned by a third party and are not under the full control of the enterprise in question. The application or service is running on resources (hardware, software, locations) that are owned by, and are in the full control of, the enterprise in question. SAP Production System. The system used in live operations by end users. SAP Quality Assurance System. A replica of the PRD system that serves as the test environment for configurations and programs designed in the development (DEV) system. 11

12 Chapter 3: Technology Overview This chapter presents the following topics: Technology resources Key components

13 Chapter 3: Technology Overview Table 2 details the hardware and software resources that are used in this solution. Table 2. Solution resources Software Version Purpose Federation Enterprise Hybrid Cloud 3.1 Foundation SAP automation package 3.1 Pre-installed customization containing blueprints to automate SAP services such as: Unattended SAP installation Avamar client and plugin installation/configuration (used in the Backup module) SAP auto start service (used in the Continuous Availability and Disaster Recovery modules) Blue Medora vrealize Operations Management Pack for SAP Computing Center Management System (CCMS) SAP adapter for vrealize Operations SAP Enterprise Resource Planning (ERP) 6.0 EhP 7 SAP application software For a complete, up-to-date list of all software requirements for Federation Enterprise Hybrid Cloud, refer to the following: Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide Latest EMC Simple Support Matrix for Federation Enterprise Hybrid Cloud 3.1 (requires login) This section describes the three key components that are used in this solution: Federation Enterprise Hybrid Cloud 3.1 foundation infrastructure Blue Medora vrealize Operations Management Pack for SAP CCMS SAP Business Suite 7.0 Federation Enterprise Hybrid Cloud 3.1 Figure 1 shows the technology components of the Federation Enterprise Hybrid Cloud for SAP solution, including the vrealize Suite Enterprise components and SAP add-ons. vrealize Suite combines multiple components into a single product to address the complete set of cloud infrastructure capabilities. When used together, the vrealize Suite components provide virtualization, software-defined data center services, policy-based provisioning, disaster recovery, application management, and operations management for SAP ecosystems. 13

14 Chapter 3: Technology Overview Figure 1. Federation Enterprise Hybrid Cloud for SAP technology components The Federation Enterprise Hybrid Cloud for SAP solution includes the following key technology components: VMware vrealize Suite, including: VMware vrealize Automation VMware vrealize Orchestrator VMware vrealize Operations Manager VMware vrealize Configuration Manager VMware vrealize Business Standard VMware vrealize Log Insight VMware vsphere ESXi and VMware vcenter Server VMware vcloud Networking and Security networking VMware NSX for vsphere VMware vcenter Site Recovery Manager (DR only) EMC ViPR software-defined storage EMC VNX, EMC VMAX, EMC ScaleIO, EMC VPLEX, EMC Isilon, and EMC XtremIO storage platforms EMC RecoverPoint (DR only) EMC Avamar and EMC Data Domain data protection platforms EMC ViPR SRM and EMC Data Protection Advisor 14

15 Chapter 3: Technology Overview For detailed information about the solution components, refer to the Federation Enterprise Hybrid Cloud 3.1 documents that are listed in Essential reading. Blue Medora vrealize Operations Management Pack for SAP CCMS Blue Medora vrealize Operations Management Pack for SAP CCMS is an embedded adapter that uses SAP BAPI calls to collect metrics from an SAP server. The management pack enhances vrealize Operations by adding the following capabilities: Out-of-the-box dashboards Workload details view Proactive smart alerts Automated correlation of changed events Heat map views Capacity and trending analysis vrealize Operations provides a comprehensive monitoring solution for SAP in a virtualized environment, while the management pack makes the data more consumable, especially in complex SAP cloud environments. Blue Medora vrealize Operations Management Pack for SAP CCMS enables vrealize Operations Manager to collect health and performance metrics from the SAP CCMS (transaction code RZ20). It provides a unified view of the health, risk, and efficiency of the infrastructure and the SAP applications. Real-time monitoring, displayed as widgets, improves the quality of service and provides early detection of issues that are related to performance, capacity, and configuration. Integrating vrealize Operations with EMC ViPR Analytics enables full end-to-end visibility of the infrastructure, from the SAP-application level, to the virtual machine, down to the LUN, and at every point in between. SAP ERP 6.0 SAP ERP 6.0, powered by the SAP Business Suite 7.0 NetWeaver technology platform, is a fully integrated ERP application that fulfills the core business needs of midsize and large enterprises across all industries and market sectors. SAP ERP 6.0 delivers a comprehensive set of integrated, cross-functional business processes and can serve as a solid businessprocess platform that supports continued growth, innovation, and operational excellence. The Federation Enterprise Hybrid Cloud solution contains key integration points between EMC and VMware products for SAP applications, enabling cloud features such as: Storage services Orchestration Service metering Operational management and monitoring SAP services empower the cloud solution through auto-provisioning using vrealize Application Services and SAP-level operational monitoring through the Blue Medora vrealize Operations Management Pack for SAP CCMS, as Figure 2 shows. 15

16 Chapter 3: Technology Overview Figure 2. EMC, VMware, and SAP integration points In Figure 2: SAP Software Provisioning Manager (SWPM) offers the execution of many system provisioning tasks and encompasses a broad range of platforms and products. The gray boxes represent the Federation Enterprise Hybrid Cloud components The orange box represents the application components The blue boxes represent the integrations points to EMC components The green boxes represent the integration to VMware components SAP integration SAP and most of its supported databases provide an Unattended Installation feature, through which the configuration is (mostly) pre-defined and a script starts installation. These scripts are integrated into vrealize Application Services for complete orchestration, from storage provisioning to full SAP installation. The Blue Medora SAP CCMS pack integrates an SAP system with vrealize Operations Manager, allowing administrators to gain visibility of SAP-level performance without logging in to the actual system. 16

17 Chapter 4: Solution Architecture Design This chapter presents the following topics: Delivery strategy Foundation infrastructure functionality Modular add-on services

18 Chapter 4: Solution Architecture Design The full Federation Enterprise Hybrid Cloud is delivered as one core solution as follows: Foundation infrastructure The essential component of the solution Modular add-ons Enabling features that are optional but highly recommended Application-specific enhancements Enabling features that are designed for a specific application, such as SAP The SAP landscape is then deployed as an application layer to this infrastructure. Minimal SAP-specific customizing is required. The foundation infrastructure is the core of the Federation Enterprise Hybrid Cloud. This section provides an overview of the features and functionality for SAP environments, as shown in Figure 3. Figure 3. Federation Enterprise Hybrid Cloud foundation infrastructure features and functionality Automation and self-service provisioning Cloud users can request and manage SAP applications and compute resources within established operational policies, reducing IT service delivery times from days or weeks to just minutes. Figure 4 shows a sample Federation Enterprise Hybrid Cloud catalog for SAP after the initial deployment of storage, backup, and virtual machine provisioning services. 18

19 Chapter 4: Solution Architecture Design Figure 4. vrealize Automation catalog view Multitenancy and secure separation Physical segmentation of resources can be achieved in vrealize Automation to isolate tenant resources or to isolate and contain compute resources for licensing purposes. This separation can encompass network, compute, and storage resources to ensure appropriate security and performance for each SAP tenant. Security This solution enables SAP customers to enhance security by establishing a hardened security baseline across the hardware and software stacks supporting their Federation Enterprise Hybrid Cloud infrastructure. Workloadoptimized storage This solution enables customers to take advantage of the proven benefits of EMC storage in SAP landscapes running on a Federation Enterprise Hybrid Cloud environment. This solution provides policy-based, software-defined storage management of EMC block and file storage. Elasticity and service assurance This solution uses a combination of tools to provide the environmental visibility and alerts required to proactively ensure service levels in virtual and cloud environments. Using vrealize Automation and tools that are provided by EMC, administrators and end users can dynamically add SAP Additional Application Server (AAS) instances, or adjust disk and compute resources as needed, based on their performance requirements. Monitoring and resource management This solution features automated monitoring capabilities that provide IT administrators with a comprehensive view of the cloud environment to enable intelligent decision-making for resource provisioning and allocation. Metering and chargeback The solution uses VMware vrealize Business Standard to provide cloud administrators with metering and cost information across all SAP business groups in the enterprise. vrealize Business Standard reports the SAP virtual machine and blueprint costs that are based on business units and application groups across the hybrid cloud environment. 19

20 Chapter 4: Solution Architecture Design The Federation Enterprise Hybrid Cloud solution provides modular add-on components for the following services: Application services Data protection: Backup Continuous availability Disaster recovery Public cloud services Application services The Federation Enterprise Hybrid Cloud uses VMware vrealize Application Services to optimize application deployment and release management through logical application blueprints in vrealize Automation. The vrealize Automation drag-and-drop user interface lets you quickly and easily deploy blueprints for applications and databases such as Microsoft Exchange, Microsoft SQL Server, Microsoft SharePoint, Oracle, SAP, and Cloud Foundry. Data protection: Backup Using EMC customizations for VMware vrealize Orchestrator workflows, administrators can quickly and easily set up multitier data protection policies that users can assign when provisioning their virtual machines. The backup infrastructure takes advantage of Avamar and Data Domain features such as deduplication, compression, and VMware integration. Data protection: Continuous availability A combination of EMC VPLEX, VMware vsphere vmotion, and VMware vsphere High Availability enables hybrid cloud users to effectively distribute applications and their data across multiple sites over synchronous distances. With virtual storage and virtual servers working together over distance, your infrastructure can provide load balancing, real-time remote data access, and improved application protection. All migration of live systems is seamlessly run between sites, transparently to users and applications. Data protection: Disaster recovery The Federation Enterprise Hybrid Cloud enables cloud administrators to select disaster recovery protection for their SAP applications and virtual machines when deploying from the vrealize Automation self-service catalog. EMC customizations automatically place these systems on storage that is protected remotely by EMC RecoverPoint. VMware vcenter Site Recovery Manager, through tight integration with the EMC ViPR Storage Replication Adapter, can automate the recovery of all SAP virtual storage and virtual machines at a recovery or failover site. The remaining chapters in this document focus on enabling enhancements or features that require SAP-specific configuration, namely: Migration of SAP systems into the Federation Enterprise Hybrid Cloud Self-service SAP provisioning Networking and security for SAP landscapes SAP cloud monitoring and root-cause analysis For all Federation Enterprise Hybrid Cloud topics beyond the scope of this document, refer to Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide. 20

21 Chapter 5: Migration This chapter presents the following topics: Overview Scenarios and procedures Validation

22 Chapter 5: Migration For organizations that intend to migrate to the Federation Enterprise Hybrid Cloud platform, a simple migration is not enough the virtual machines must be standardized on migration. Federation Enterprise Hybrid Cloud standard virtual machines are provisioned with monitoring and chargeback mechanisms to enable central management. Federation Enterprise Hybrid Cloud can automate this standardization procedure, bringing the virtual machines under the full control of the cloud. This chapter outlines the steps for importing non-federation Enterprise Hybrid Cloud virtual machines into a Federation Enterprise Hybrid Cloud. Full migration and standardization of virtual machines that are not provisioned by Federation Enterprise Hybrid Cloud require Federation Enterprise Hybrid Cloud-based customization of the virtual machine and storage migration to ViPR. A virtual machine managed by Federation Enterprise Hybrid Cloud has the following characteristics: Virtual machine lease and expiration policies vrealize Business chargeback compliance Federation Enterprise Hybrid Cloud monitoring compliance Datastores completely managed by ViPR Controller in Federation Enterprise Hybrid Cloud Because of the variety of cloud provider environments, it is important to preconfigure virtual machines on a case-by-case basis before migrating them. The solution described in this document is just one example. It is strongly recommend to employ EMC professional services to complete these tasks. Virtual machines that not managed by Federation Enterprise Hybrid Cloud fall into one of the following scenarios: Scenario 1: Virtual machines under a vcenter used by the Federation Enterprise Hybrid Cloud solution Scenario 2: Virtual machines in a vcenter that is not managed by Federation Enterprise Hybrid Cloud the vcenter will be connected as an endpoint Scenario 1: Virtual machines in the same vcenter as Federation Enterprise Hybrid Cloud In this scenario, consider an existing virtual data center that is managed by vcenter. You can reuse this vcenter to implement a hybrid cloud environment. All new virtual machines that are created after implementation are automatically registered in the new cloud, but all virtual machines present before the cloud implementation must first be migrated to the new cloud environment. Solution (online migration) To migrate the virtual machines: 1. Perform a Storage vmotion migration in vcenter to Federation Enterprise Hybrid Cloud's ViPR storage under the planned business group. 2. Use Infrastructure Organizer in vrealize Automation to import the virtual machines to the planned business group. 3. Migrate the network to the planned virtual extensible LAN (VXLAN) port group during a maintenance window. 22

23 Chapter 5: Migration Scenario 2: Virtual machines in a non- Federation Enterprise Hybrid Cloud vcenter that will be connected as an endpoint In this scenario, consider a customer with two different environments, where each environment has its own vcenter: one environment is an existing virtual data center, and the other environment is implemented in the Federation Enterprise Hybrid cloud. The customer wants to join the two vcenter environments together. Solution (offline migration) The first option is to migrate both environments at the storage level and then switch from one vcenter to the other vcenter, as follows: 1. Take the system offline and then export the virtual machines to the vcenter managed by Federation Enterprise Hybrid Cloud. Select the ViPR storage under the planned business group. Reconfigure the network to a VXLAN port group. 2. Use Infrastructure Organizer to import the virtual machines to the designated business group. 3. After all virtual machines are imported, disconnect the ESXi hosts from their current vcenter and connect to the vcenter managed by Federation Enterprise Hybrid Cloud. 4. Perform Federation Enterprise Hybrid Cloud customizations for the ESXi hosts according to Federation Enterprise Hybrid Cloud best practices. Alternate solution (online migration) Another solution is to connect the non-cloud environment as an endpoint to the hybrid cloud, as follows: 1. Create a new endpoint in vrealize Automation that connects to the vcenter used by the non-cloud environment. 2. Reconfigure this vcenter to make it compliant with Federation Enterprise Hybrid Cloud, according to the Federation Enterprise Hybrid Cloud best practices. 3. Use Infrastructure Organizer to import the virtual machines to the designated business group. 4. Migrate the network to the planned VXLAN port group during a maintenance window. This section describes how to configure the workflow for Scenario 1 in Federation Enterprise Hybrid Cloud. Migrate the storage to Federation Enterprise Hybrid Cloud s ViPR Controller using Storage vmotion, and then follow these steps to import the virtual machines to the correct business group, using Infrastructure Organizer: 1. Create blueprints to automate the import of virtual machines. 2. Import the existing virtual machines and verify that they can be managed by a Federation Enterprise Hybrid Cloud management application such as chargeback and monitoring agents. Creating blueprints to automate the import of virtual machines We created a new blueprint from the vrealize Automation console to import virtual machines. The blueprint defines how long the virtual machines will be leased or archived, whether you want the virtual machines to be reconfigured, and what the blueprint will cost. In this case, we set the following values, as shown in Figure 5. Lease (days): 30 Archive (days): 2 23

24 Chapter 5: Migration Allow reconfigure: Yes Note: The daily cost value that is specified in the machine blueprint is added to the total cost of the machine. This value can represent a markup for using the machine and for the resources that are consumed by the machine. Figure 5. Creating a blueprint for existing virtual machines Importing existing virtual machines After creating the endpoint and fabric group, and organizing the compute resources for the existing virtual SAP systems, you can import the existing virtual machines into a Federation Enterprise Hybrid Cloud platform through the vrealize Automation Infrastructure Organizer wizard. In this case, we must import two unmanaged, existing virtual machines, as shown in Figure 6. Figure 6. Importing existing virtual machines We assigned these two machines to the Finance Business Group, as shown in Figure 7. 24

25 Chapter 5: Migration Figure 7. Assigning a business group to the imported virtual machines The last step is to select the blueprint for the machines, as shown in Figure 8. Figure 8. Applying a blueprint to the imported virtual machines Verifying that Federation Enterprise Hybrid Cloud can manage virtual machines After importing the virtual machines under the Finance business group, we used the Actions menu to manage them, as shown in Figure 9. Figure 9. Managing machines using the Actions menu The View Details option on the Actions menu displays the detailed machine configuration, as shown in Figure

26 Chapter 5: Migration Figure 10. Detailed information on the virtual machines managed by vrealize Automation As defined in the blueprint, the virtual machine lease period is 30 days. When the lease expires, the virtual machines are destroyed after two (archive) days. You can change the lease period, receive expiration reminders, and expire the leases immediately through the Actions menu, as shown in Figure 9. Test results You can import the existing virtual machines to a Federation Enterprise Hybrid Cloud platform. Through the vrealize Automation Infrastructure Organizer wizard, you can register the existing VMware virtual SAP systems, enable the cloud, and import it into the Federation Enterprise Hybrid Cloud platform. Virtual machines can be migrated, standardized, and managed through the Federation Enterprise Hybrid Cloud platform. 26

27 Chapter 6: Self-Service SAP Provisioning This chapter presents the following topics: Overview How auto-provisioning works Self-service provisioning Validation

28 Chapter 6: Self-Service SAP Provisioning Federation Enterprise Hybrid Cloud, through vrealize Automation, offers many templates and tools to automate tasks within the cloud environment. This chapter explores two powerful applications of the automation features: Self-service SAP provisioning, which enables a fully automated installation of an SAP central system Elasticity, which auto-provisions one or more new AAS instances and integrates them into an existing SAP system Regardless of what you want to automate, the core procedure is the same. Federation Enterprise Hybrid Cloud uses vrealize Automation Application Services scripts to orchestrate processes across several virtual machines. vrealize Automation Application Services can run these scripts from both the VMware environment and the guest operating system (OS) level. You can predefine values that can be passed on later as environment variables, and write flexible and portable scripts, with as many variables as you need. EMC Managed services can customize the scripts for your needs, or you can make your own scripts based on SAP Note vrealize Automation Application Services can also import catalogs from another cloud (VMware vcloud Director, for example) and map these catalogs to the Application Services service catalog to trigger remote cloud operations from the same Federation Enterprise Hybrid Cloud interface. Automating a standard SAP installation The SAP Software Provisioning Manager (SWPM) uses the SAPINST executable to run an unattended installation. To run the installation successfully, you must manually preconfigure each virtual machine on which SAP is to be installed, as follows: 1. Correctly configure the file systems. 2. Set hostnames and create SID-specific mount points. 3. Install the OS. 4. Set the environment variables. 5. Install Java, SAP locales, and SAP cryptographic libraries. 6. Install the database instance. vrealize Automation Application Services fills the preconfiguration gap by allowing the use of custom scripts. By using a combination of out-of-the-box workflows, prebuilt templates, and user scripts, as shown in Figure 11, vrealize Automation fully automates and coordinates the tasks that SAPINST is not able to perform, such as: Provisioning storage and virtual machines from a virtual machine template that is preconfigured for SAP Allowing you to customize the hostname, SID, and other properties immediately before the SAP provisioning process Installing the database instance Performing an unattended SAP installation using predefined, customizable SAPINST parameters 28

29 Chapter 6: Self-Service SAP Provisioning Figure 11. Process flow of a standard SAP installation The result is a self-service interface requiring minimal initial input, and a full-fledged SAP system ready for login. Automating a distributed installation A standard installation is essentially a distributed installation but one in which all the components are in a single host, as in Figure 12. Figure 12. Distributed SAP installation workflow In automating a distributed installation, you use the same deployment strategy as for a standard SAP installation but with the following workflow: 1. Create an ABAP SAP Central Services (ASCS) virtual machine and use a script to install the instance. 2. Connect to ASCS and update the hosts file or domain name service (DNS) server with the new virtual machine. 3. Create a database virtual machine and use a script to install the database instance. 4. Create a Protection and Availability Storage (PAS) virtual machine, connect to the ASCS shared folders, and use a script to install an instance. 29

30 Chapter 6: Self-Service SAP Provisioning To adjust the install scripts: 1. Change the file systems of SAP instances to be different from the database instance. 2. Change the group IDs (GIDs) and user IDs (UIDs) of the SAP and database users to be the same on all instances. 3. Change the SAP product IDs according to the type of SAP instance installed. 4. Run a command that mounts the SAP shared folders, such as the following: /sapmnt/<sid>/exe, /sapmnt/<sid>/profile, and /sapmnt/<sid>/global 5. Update the /etc/hosts files of every virtual machine. Automating an SAP AAS installation If there is a need to scale out the SAP workload, you can provision an AAS instance and automatically attach it to an existing ASCS. Configuring auto-provisioning of an AAS instance is mostly similar to that of a PAS instance, but a few differences must be considered when writing the script: Request the ASCS details (hostname, SID) as user input so that the workflow knows where the provisioned AAS instance should be attached Request the database details (hostname) Figure 13 shows the general automation workflow and shows the components that must be configured in vrealize Automation Application services. Figure 13. User workflow in self-provisioning an SAP system using vrealize Automation vrealize Automation uses the following concepts to enable auto-provisioning: An application (A), a logical container that encapsulates the whole workflow Blueprints such as the vrealize Automation Blueprint (E) and the Application services blueprint (B) that serve as templates for the hardware and software deployment configurations respectively Deployment profiles (C), which serve as the blueprint's customization A cloud provider (D), a cloud component that acts as the buffer between the vsphere virtual machine template that is used by the vrealize automation blueprint and the logical template inside the Application container If there is auto-provisioning, the Small deployment profile is used to implement a blueprint with minimal resources, while the Large profile deploys the same blueprint with larger allocations. 30

31 Chapter 6: Self-Service SAP Provisioning Each Application Services blueprint has two components: a Logical Template and a Service. The Logical Template contains information on the Cloud Provider (D) and the OS version. The application blueprint contains the information needed to provision the virtual machine later. The Cloud Provider contains information about which cloud the application is working on. Application Services extracts the templates from the Cloud Provider depending on the cloud type: a vrealize Automation blueprint (E), a catalog, or even another public cloud template. For this solution, we used a blueprint that clones the virtual machine. The Service contains the information needed to provision the virtual machine, including the script that we want to run against the virtual machine, and the OS that the script is compatible with. This script is the main script that triggers the SAP installation. The Application container can be accessed through a service catalog in vrealize Automation. The service catalog is mapped to an application s deployment profile in Application Services. To enable full self-service provisioning of an SAP system in vrealize Automation: 1. Import the following items from the SAP automation package: a. SAP-ready guest virtual machine template b. Application blueprints 2. Customize the imported items, as follows: a. Change the IP address of SAP VM template. b. Re-register the SAP VM template to vrealize Automation servers. c. Create and publish the deployment profiles. d. Grant entitlements of the published service item to specific business users. For a detailed building process of SAP auto-provisioning, consult EMC professional services. Verifying prerequisites Before you configure the solution, the following must be present: vcenter Server and vrealize Automation vrealize Automation Application Services The component IDs of the SAP systems that you want to include in the self-service portal (see SAP Note ) SAP installation media downloaded from the Marketplace. SAP S-user and authorization are required to download the installation media A mountable network file system (NFS) that contains the SAP installation media. The automation script mounts this file system to the newly created virtual machines Creating an SAPready virtual machine template This section describes the specifications needed for an SAP-ready virtual machine template. Note: The specified resources amounts are initial values. You must observe proper sizing based on business requirements when provisioning. Table 3 shows the virtual machine specifications that are used for testing. 31

32 Chapter 6: Self-Service SAP Provisioning Table 3. Virtual machine specification and installation media Hardware Software SAP Installation media (SAP ECC 6.0 EhP7 SR1) 4-core CPU (1 socket x 4 cores/socket) 8 GB RAM 1 SCSI controller SUSE Linux 11 SP3 Oracle 11.2 SAP ERP 6.0 EhP 7 SAP SWPM 1.0 for Linux X86_64 SAP UC Kernel 741 (D _6) SAP ECC 6.0 EhP7 SR1 Installation export DVD 1 and GB disk space Oracle RDBMS for Linux X86_64 (D ) Oracle CLIENT (CD ) To enable full provisioning of an SAP system: Note: This procedure is applicable to all standard installations, distributed installations, and AAS installations, unless otherwise specified. 1. Ensure that the following packages are installed (check using RPM or YaST) during SUSE Linux Enterprise (SLES) installation: SAP Application Server Base (sapconf) C/C++ compiler and tools gcc (x86_64) gcc-c++ (x86_64) glibc-devel libaio-devel libstdc++ SAP locales (See SAP Note ) Java Developer Kit (see SAP Note ) Bourne Again Shell (bash) and C Shell (csh) Public Domain Korn Shell (ksh) 2. Change the soft and hard limits for SAP and Oracle users to in /etc/sysconfig/sapconf: soft nofile hard nofile soft nofile hard nofile soft nofile hard nofile Reload the sapconf file by running the /etc/init.d/boot.sapconf reload command. 4. Save the virtual machine to a template when all the adjustments are completed. The template will be imported later. Setting up silent installation scripts The automation is enabled using the following executables: VMware vrealize Automation Application Services MAIN SCRIPT, which you must write. EMC recommends that EMC Services customize this main script for you to ensure reliability. RUNINSTALLER to run an unattended Oracle installation. This command is incorporated into the main script. 32

33 Chapter 6: Self-Service SAP Provisioning SAPINST to run the SAP silent installation. The command is relatively simple, but the initial preparation takes some time to set up. SAP Note guides you through the process. Note: Some solution-specific customizations are not discussed in this document. EMC recommends deploying these customizations through EMC Managed services. Creating application blueprints Deploying the automation workflow After the scripts are prepared, create blueprints that incorporate the scripts and workflows to automate the process. When the templates, scripts, and NFS media server are ready, you can combine them in vrealize Application Services. Figure 14 shows the interface. Figure 14. SAP blueprint interface in vrealize Application Services To deploy the automation workflow: 1. Log in to vrealize Automation. Under Catalog, select the deployment profile/catalog item that was created in the application blueprint. 2. Type a description under Request Information. 3. Use the input screen under Properties to customize the details based on the Properties settings that are configured in the application blueprint. 33

34 Chapter 6: Self-Service SAP Provisioning 4. Deploy the workflow and wait for the operations to finish. You can monitor the progress using vcenter. This use case validates the effectiveness and efficiency of the automation feature of Federation Enterprise Hybrid Cloud for SAP. Test scenario 1 A Federation Enterprise Hybrid Cloud user wants to install a new distributed SAP system using the auto-provisioning capability of Federation Enterprise Hybrid Cloud. Our test objective was to fully provision a distributed SAP system in Federation Enterprise Hybrid Cloud using only vrealize Application Services, without any manual procedure aside from the initial input. Test procedure To conduct this test, we configured the automation and deployed a distributed SAP system. Figure 15 shows a sample self-service interface for a user who wants to create a new SAP system from scratch. Figure 15. Auto-provisioning an SAP distributed system Figure 16 shows the Node Properties input screen, where a user can easily customize hostnames and resource allocations. 34

35 Chapter 6: Self-Service SAP Provisioning Figure 16. Node Properties tab for an SAP distributed installation Figure 17 shows the Service Properties tab, which allows a user to specify core SAP-specific properties and other services such as backup and database compression. Figure 17. Service Properties tab for an SAP distributed installation 35

36 Chapter 6: Self-Service SAP Provisioning Test results Figure 18 shows a graphic summary of the whole process flow. Figure 18. Summary of process flow after provisioning The total time to complete an SAP distributed installation is 3 hours and 35 minutes for the database instance, 2 minutes for the ASCS instance, and 42 minutes for the PAS instance. Test scenario 2 A Federation Enterprise Hybrid Cloud user intends to scale out an existing SAP system by attaching a newly provisioned SAP AAS instance. Our test objective was to provision and automatically attach an AAS instance to an existing SAP system without manual operation aside from the initial input. Test procedure To conduct this test, we created a second script that is designed solely to create an AAS instance and attach it to an ASCS instance. Figure 19 shows the self-service interface that results when AAS is added to a standard system (central instance). You can further specify the ASCS details by attaching the AAS to an SAP distributed system. 36

37 Chapter 6: Self-Service SAP Provisioning Figure 19. Provisioning an AAS system and associating it to an existing SAP standard system Test results The average time to attach one AAS instance is around 13 minutes. 37

38 Chapter 7: Networking and Security This chapter presents the following topics: Overview Multitenant security Solution architecture Validation

39 Chapter 7: Networking and Security This chapter introduces the network and security design of the NSX platform, and the network and security integration of a Federation Enterprise Hybrid Cloud solution for SAP. Use this chapter as a reference to begin the networking, security planning, and design process for your hybrid cloud for SAP. Ensure that you have read the Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide to become familiar with the multitenancy concepts (such as tenants, business groups) that are discussed in this chapter. Valid concerns exist about information leakage and unauthorized access to data (noisy neighbors) on a shared network infrastructure. Consumers of the provisioned resources must operate in a dedicated environment while still benefiting from infrastructure standardization. To address these concerns, this solution was designed for multitenancy, with a defense-in-depth perspective that is shown through: Implementation of virtual LANs (VLANs) to enable isolation at Layer 2 in the cloud management pod and where the solution intersects with the physical network Use of VXLAN overlay networks to segment tenant and business group traffic flows Integration with firewalls that function at the hypervisor level to protect virtualized applications and enable security policy enforcement in a consistent fashion throughout the solution Deployment of Edge firewalls to protect the business group and tenant perimeters In this solution, we assigned subnets to predefined business groups on which the firewall rules can be based. This chapter shows how SAP application networks can address data security by isolating different tenants/business groups from each other inside a cloud environment. The solution addresses the challenges of securing authentication and configuration management to comply with industry and regulatory standards through the following features: Secured infrastructure with public key infrastructure (PKI) support for authenticity, non-repudiation, and encryption Authentication sources converged into a single directory to enable a centralized point of administration and policy enforcement Configuration management tools that generate infrastructure reports for audit and compliance purposes The Federation Enterprise Hybrid Cloud can use NSX for vsphere to offer significant advancements over the vcloud Networking and Security feature set. Enhanced networking and security features in NSX include the following: Distributed logical switches: Distributed logical broadcast domains/segments that can span across multiple clusters and to which a VM can be logically connected/wired. This allows for VM mobility without concern for traditional physical Layer 2 boundaries. Distributed logical routers and firewalls: Contain East-West traffic within the hypervisor when the source and target virtual machines reside on the same host. 39

40 Chapter 7: Networking and Security Advanced network services: Load balancer, NAT, VPN: Enables load sharing across a pool of virtual machines with configurable health check monitoring and application-specific rules for service high availability, URL rewriting, and advanced Secure Sockets Layer (SSL) handling. A distributed firewall enables consistent datacenter-wide security policies. Security policies: Can be applied directly to security groups enabling greater flexibility in enforcing security policies. Logical network topology The logical network topology is designed to address the requirements of enabling multitenancy and securing separation of tenants and business groups in Federation Enterprise Hybrid Cloud. The topology is also designed to align with security best practices for segmenting the networks according to the purpose or traffic type. Figure 20 shows the logical topology of the physical and virtual networks that are defined in the Federation Enterprise Hybrid Cloud solution for SAP. Figure 20. Security logical infrastructure Test scenario The default configuration for our environment supports virtual machines belonging to the same business group. More detailed rules can be set depending on customer requirements. In this test environment, we take a simple case of a customer with two tenants, each with one or more business units. Each business unit has a three-system SAP landscape. 40

41 Chapter 7: Networking and Security Test objectives Our objective was to achieve the segregation scheme shown in Figure 21 such that: Federation Enterprise Hybrid Cloud can block all external connectivity outside its business group/tenant Federation Enterprise Hybrid Cloud is flexible enough to allow exceptions to the rules Figure 21. Sample segregation scenario To minimize testing time, we tested only the systems that are shown in blue in Figure 21. Table 4 shows the detailed information about the SAP systems we tested. Table 4. SID Detailed information on tested SAP systems IP Address ED EQ EP HRP PIP Test procedure The high-level steps are as follows: 1. Configure Edge in the Federation Enterprise Hybrid Cloud environment. 2. Configure the firewall rules on Edge, as shown in Figure

42 Chapter 7: Networking and Security Figure 22. Firewall rules Test results We created firewall rules in the Edge to control access to the SAP system. The rules enabled us to define access rules for each of the SAP systems to enhance the network security and monitor firewall logs. The firewall rules block all traffic to EP1 from PIP, except the Remote Function Call (RFC) protocol, which uses TCP port The default rules for the firewall deny all traffic between different subnets. We tested the RFC connection from PIP to EP1, as shown in Figure 23. Figure 23. RFC connection test from PIP to EP1 As shown in Figure 24, the connection between PIP and EP1 was blocked except for RFC port The firewall also captured the network packet and logged the detailed connection information. 42

43 Chapter 7: Networking and Security Figure 24. Test results for firewall rules Table 5 summarizes the test results. This solution can secure your data at the level you require across different clouds without affecting productivity. Table 5. Use case test results From To Expected Result Assessment EQ1 HRP Blocked Blocked Passed EP1 HRP Blocked Blocked Passed HRP EP1 Blocked Blocked Passed PIP HRP Blocked Blocked Passed PIP EP1 Blocked except port 3300 Blocked except port 3300 Passed 43

44 Chapter 8: Cloud Monitoring and Root Cause Analysis This chapter presents the following topics: Overview of monitoring SAP monitoring ViPR SRM and vrealize Operations Manager Blue Medora configuration Customized monitoring dashboard Validation

45 Chapter 8: Cloud Monitoring and Root Cause Analysis Using multiple management interfaces to gather performance and capacity information is not a practical solution when you maintain tens to hundreds of SAP systems. As well as being time-consuming, it often results in mismanaged resources. These systems require end-to-end visibility (from back-end storage to SAP application level) across the entire cloud. This chapter shows how an integrated, automated management solution powered by EMC ViPR SRM and vrealize Operations technologies provides service assurance so that the cloud or tenant administrator can: Obtain virtualized data center visibility (through ViPR SRM) Enable system efficiency and maintain IT compliance to standards and best practices (through ViPR SRM) Use customized and intelligent views and reports to obtain detailed information (through ViPR SRM and vrealize Operations) The solution provides the following capabilities: Real-time performance monitoring and analysis EMC ViPR integration Reporting Configuration validation and compliance EMC ViPR SRM alerting Scheduling and sending reports through messages SAP monitoring using the Blue Medora vrealize Operations Management Pack for SAP CCMS In this chapter, we focus on the first item: real-time performance monitoring and analysis. For information on the remaining capabilities, refer to the Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide. SAP tenant administrators can use role-based performance dashboards to analyze individual metric behaviors and determine the health of an enterprise, in part or as a whole. Blue Medora vrealize Operations Management Pack for SAP CCMS enables vrealize Operations Manager to collect health and performance metrics from the SAP CCMS (transaction code RZ20). It provides a unified view of the health, risk, and efficiency of the infrastructure and the SAP applications. Real-time monitoring, displayed as widgets, improves the quality of service and provides early detection of issues that are related to performance, capacity, and configuration. Enabling this solution requires configuration of ViPR SRM and vrealize Operations Manager and customization of the Blue Medora interface. You can find the detailed procedures in the Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide and in the corresponding product documentation. 45

46 Chapter 8: Cloud Monitoring and Root Cause Analysis To deploy ViPR SRM to manage all data: 1. Deploy ViPR SRM as a virtual appliance in a VMware environment or install the ViPR SRM core software on Linux or Windows Server. 2. Log in to the ViPR SRM GUI and apply the core suite licenses. 3. Enable SNMPv1 on the SAN switch to support switch discovery, data collection, and alert consolidation. 4. Install and configure EMC SMI-S to support EMC VMAX data collection. 5. Install and configure the required solution package for each of the following: a. Solution Package for SAN Switch b. Solution Package for EMC ViPR c. Solution Package for EMC VMAX d. Solution Package for EMC VNX e. Solution Package for VMware vcenter 6. Install vrealize Operations. 7. Install and configure the SAP adapter. 8. Customize the dashboard in vrealize Operations. The monitoring dashboard is easy to customize, providing you with a clear, uncluttered view of the cloud environment. You can find detailed procedures in the relevant product documentation. Figure 25 shows an example of a customized dashboard for the SAP tenant administrator. Figure 25. vrealize Operations performance dashboard for an SAP tenant administrator 46

47 Chapter 8: Cloud Monitoring and Root Cause Analysis This example shows statistics for two SAP systems: DX1 and EP1. The widgets in Figure 25 are numbered 1 through 6 and display the following: 1. Health overview, which shows the health status of a tenant s SAP infrastructure 2. SAP system real-time KPIs, which include the following counters: SAP dialog response time Database response time Total online SAP users Batch utilization 3. Tenant generic scoreboard, which shows the workload and read/write latency of the DX1 and EP1 systems 4. Metric graph of the DX1 and EP1 systems showing: CPU utilization Space usage under the /oracle folder The blue line indicates that the file system of DX1 systems is full, and the tenant administrator can reclaim the space or assign more space to the /oracle folder. Swap space usage 5. Health workload scorecard 6. Health tree of Tenant A s SAP application instances To understand how all these elements work together, we created a test scenario to see these monitoring tools in action. Test scenario In this use case, we simulated an SAP system that was experiencing an abnormally high workload. The simulation shows how a tenant administrator can monitor the SAP systems in real-time and coordinate with the cloud administrator to perform an end-to-end root-cause analysis. Our objective was to determine the root cause of a simulated performance bottleneck using the Federation Enterprise Hybrid Cloud SAP monitoring solution. Test procedure and results This section explains the monitoring and root-cause analysis procedures and the derived conclusion. Monitoring the SAP application We logged in to vrealize Operations Manager to monitor Tenant A s SAP systems to identify the affected area. As shown in Figure 26, EP1 s dialog response time reached 1,124 ms and its database response time reached 785 ms, while DX1 s dialog response time reached 1,292 ms and its database response time reached 986 ms. On the workload generic scoreboard, EP1 s workload reached 21,225 IOPS and the DX1 workload reached 20,609 IOPS. The EP1 and DX1 workloads had high disk latency, but CPU and memory utilization were acceptable. 47

48 Chapter 8: Cloud Monitoring and Root Cause Analysis Figure 26. Tenant A s SAP system DX1 and EP1 performance dashboard Identifying the topology path from virtual machine to storage To efficiently locate the ESXi host and the storage of the affected virtual machine, we quickly retrieved an end-to-end view of the relationship between the virtual machine (saperp6-9v0yqyu) and storage in ViPR SRM, as shown in Figure 27. The virtual machine on the C ESXi server was connected to the VNX storage (VNX2-2852) through two fabric switches. Figure 27. End-to-end view from the virtual machine to storage End-to-end detailed performance analysis of the affected virtual machine Next, we examined more details about the virtual machine, ESXi host, fabric switches, and array. By clicking each of these objects in the topology map and selecting CPU, memory, 48