vce systems deploy and implement guide · 2020-06-21 · vce™ systems deploy and implement guide...

VCE™ SystemsDeploy and Implement Guide

Revision 1.0

DELL EMC CONFIDENTIALSubject to Confidentiality Use Restrictions

VCE Systems Deploy and Implement Guide Revision History

Date Revision Description ofchanges

Originator Owner

July 13, 2016 1.0 Initial release. Lawrence Jackson

Claire O'Keeffe

Mitch Mortenson

VCE Systems Deploy and Implement Guide Revision History | 2DELL EMC CONFIDENTIAL

Subject to Confidentiality Use Restrictions

Contents

VCE Systems Deploy and Implement Guide............................................................................................ 5Documentation references..................................................................................................................... 6PS PMO process flows...........................................................................................................................6System-specific references.................................................................................................................... 8Cisco, EMC and VMware documentation...............................................................................................9Task overview...................................................................................................................................... 10

Obtaining D&I requirements and customer deliverables - D&I team...................................................11

Preparing for Deployment and Implementation.....................................................................................16

Installation prerequisites - First Responders.........................................................................................18Assumptions.........................................................................................................................................19Verifying the location with the customer...............................................................................................21Cabling requirements........................................................................................................................... 21

Installing at the customer site - First responders..................................................................................23Unloading the inventory........................................................................................................................23When you arrive................................................................................................................................... 23Unpacking VCE System IPI cabinets................................................................................................... 24Moving the VCE System from the loading dock to the data center...................................................... 34Positioning the cabinet......................................................................................................................... 34Grounding and eathing the VCE System............................................................................................. 37Vertical Exhaust Ducts......................................................................................................................... 37Cabinet ganging bracket kits................................................................................................................ 37Establishing inter-cabinet cables..........................................................................................................38General cabling tips..............................................................................................................................41Cabling a Vblock System in the Vblock System 300 family Vblock System 540 and in the VblockSystem 700 family................................................................................................................................ 42Cabling the patch panels......................................................................................................................44Installing lithium ion batteries in EMC VNX and DAEs.........................................................................44Preparing and cabling the EMC VNX and DAEs..................................................................................46Connecting to the EMC Symmetrix VMAX........................................................................................... 48

Post-installation checklist...............................................................................................................49

Powering on the VCE System - First Responders.................................................................................50

Networking tasks - Network Resource and First Responders............................................................. 51Customer network status......................................................................................................................53

Customer network is ready............................................................................................................ 53Customer network is not ready...................................................................................................... 55

Storage tasks - Storage Resource and First Responders.................................................................... 57Task overview for the storage engineer............................................................................................... 57Storage requirements...........................................................................................................................57Verify all EMC supported devices are in "Install" status on the EMC Installed Base........................... 58

3 | ContentsDELL EMC CONFIDENTIAL


Virtualization tasks - Virtualization Resource and First Responder....................................................60Virtualization Engineer......................................................................................................................... 60

Compute tasks - Compute Resource and First Responders................................................................62

Compute Engineer....................................................................................................................................63

CRG tasks - D&I team...............................................................................................................................64

D&I Closure - Network, Storage, Compute, and Virtualization resources...........................................66

Appendix: Tasks performed at customer sites - First responders...................................................... 68Appendix: FI Install and cable.............................................................................................................. 68Appendix: Re-Rack service.................................................................................................................. 68Appendix: Blade mezzanine replacement............................................................................................ 69Appendix: Line-Card install.................................................................................................................. 70

Contents | 4DELL EMC CONFIDENTIAL


VCE™ Systems Deploy and Implement GuideThis guide describes how members of the D&I team contribute to installing VCE™ Systems at customersites, verifying the installation, establishing uplinks, enabling storage, and configuring the hosts andservers.

Each role of the team contributes differently - the First Responders (as a minimum requirement) are at thecustomer sites providing installation support, while the Network, Storage, Virtualization and Computeengineers may provide their support on site or remotely at the discretion of VCE.

The engineering resources may be cross trained in multiple competencies.

The responsibilities and activities of each role of the team are described in the following table:

Role Responsibilities Remote Activities

First Responders On-site specialists that "rack andstack" the system, establish powerconnections, provide inter-cabinetcabling, and support the resourceengineers through Test Planexecution.

They are the on-site resource thatprovides "eyes and hands" for theremote engineers.

Network engineers These Network resources work withthe on-site First Responders toestablish a customer uplink ortemporary network connection thatsimulates the customer uplink, whichenables the D&I team to proceed.

The Network engineers may workremotely with the on-site FirstResponders.

Storage engineers The Storage resources work with theon-site First Responders to enablestorage for boot LUNs and DataLUNs, which are critical for theVMware environment. Withoutstorage, the blades cannot boot,preventing the VM team fromproceeding. They must also workwith the VM team for providingbackend storage to the customer'sVM environment.

The Storage engineers may workremotely with the on-site FirstResponders.

Virtualization engineers The Virtualization resources workwith the on-site First Responders,and are responsible for configuringand administrating of all VM guestservers, ESXi hosts, and VCEVision™. They must also work withthe Storage team for providingbackend storage to the customer'sVM environment.

The Virtualization engineers maywork remotely with the on-site FirstResponders.

5 | VCE™ Systems Deploy and Implement GuideDELL EMC CONFIDENTIAL


Role Responsibilities Remote Activities

Compute engineers The Compute resources work withthe on-site First Responders, and areresponsible for configuring andadministrating of all UCSinfrastructure, both blade and rackmount servers.

The Compute engineers may workremotely with the on-site FirstResponders.

The VCE Glossary provides terms, definitions, and acronyms that are related to VCE products.

To suggest documentation changes and provide feedback about this book, send an email to [email protected]. Include the name of this book, the topic name where your comment applies, andyour feedback.

Documentation references

Before you start installing, configuring, and powering up the VCE System, ensure that you have thefollowing documentation available for reference.

For information about... Refer to the...

Planning for a Vblock® System installation VCE Vblock System Physical Planning Guides

Assembling and cabling VCE Systems VCE Physical Build Guide

Configuring Vblock Systems to meet the specific needsof a customer

VCE Vblock System Logical Build Guides

Supported versions of Vblock components VCE Vblock Systems Release Certification Matrixdocuments

Procedures for powering on and powering off VblockSystems

VCE Vblock Systems Powering On and Off Guide

Gathering data that is needed to configure the VblockSystem

VCE Vblock System Logical Configuration Survey

Customer data center physical requirements VCE Vblock Systems Site Survey

on the VCE Partner Portal or Unified Dashboard

Configuration information for the customer site VCE Configuration Reference Guide

Note: This document is developed at the customer siteand is delivered at the conclusion of the installation.

Reading the cable labels See Reading the cable labels in the VCE Physical BuildGuide.

The cable cypher See Cable Cypher in the VCE Physical Build Guide.

Technical issues and how to manage them See the Knowledge Base in the VCE Sales force forguidance.

Z drive for VCE Eng Ops > Global Projects \\Nasdprd102v3\VCE_ENG_OPS\Global Projects

PS PMO process flows

VCE™ Systems Deploy and Implement Guide | 6DELL EMC CONFIDENTIAL


https://docs.vce.com/bundle/O_GLOSSARY/page/GUID-E5B5E1DA-8455-460A-8391-12F5783BE2A3.html

mailto:[email protected]?Subject=Documentation Feedback&body=Document: VCE Systems Deploy and Implement Guide. Please provide your comments:

The following table describes PS PMO process flows for Project Managers responsible for D&I.

For information about: See:

Project Workbook - PS Delivered D&IProject Workbooks are setup in the Initiating Phase, butare used by Project Managers to manage projectsthroughout the lifecycle of the project. The Workbookcontains information critical to the customer, project andservice delivery. This workbook is specific to PS deliveredDeployment & Implementation engagements.

https://inside.emc.com/docs/DOC-197327

Pre-Sales to PS Internal Kickoff TemplateThe Pre-Sales to PS Internal Kickoff Template should beused to assist in facilitating the conversation required tosuccessfully transition from Sales to Professional Services.


Pre-Sales to PS Transition ProcessThe Pre-Sales to Professional Services transition is arequired component of all service engagements. The Pre-Sales to PS Internal Kickoff meeting can be held any timeafter the opportunity has moved to Strong Upside orgreater. The Pre-Sales to PS Internal Kickoff meeting isrequired before proceeding to the Customer facing ProjectKickoff meeting.


Deployment Checklist ProcessThe Deployment Checklist (i.e. Deployment AuditChecklist, Consolidated Checklist, D&I Checklist) is arequired deliverable to be completed by ProfessionalServices on all VCE System deployments. This documenthelps to ensure that specific tasks and validations havebeen performed during the deployment.


Creating an As Built Document SetThe As-Built tool is a plug-in installed into Microsoft Excel.This tool creates an As-Built Document Set which containscomprehensive information about the Vblock system andproject engagement. This Document Set should beprovided to the customer at the end of Vblockengagement. The document set is a snapshot in time inthe form of a ZIP file that contains spreadsheets and otherinformation. The contents of the document set can becustomized based on customer requirements andengagement specifics.


Pre-Implementation Planning MeetingThe Pre-Implementation Planning meeting allows theProject Manager to hand off specific deliverables,documents or requirements for the successful execution ofthe project. Best Practice is to conduct this meeting viaWebEx, to facilitate a conversation with the entire team,providing opportunity to review documentation, askquestions and establish a repoire. In addition to the PMand D&I Team, all internal stakeholders should be invitedto the WebEx. However, if schedules do not permit,handoff via email is acceptable.










System-specific references

Before you start installing, configuring, and powering up the VCE System, ensure that you have thefollowing system files and tools available.


What the customer ordered OM_MultiBOM_{Opportunity ID}{Date time}.xlsx file onthe Build Entry page of the Unified Dashboard at: http://mts.ent.vce.com/Unified%20Dashboard/, or the BuildList in the Floor file (which is derived from the BoM).

Solutions Abstract {Opportunity ID}-{Customer}-{System}-Solutions-Abstract-{Version}.Xls file on SFDC, or the Build Entrypage at: http://mts.ent.vce.com/Unified%20Dashboard/

Site Survey {Opportunity ID}_{Customer}_Site_Survey_{Version}.docm file on the Build Entry page at: http://mts.ent.vce.com/Unified%20Dashboard/.

Floor (elevations and cabling) Floor_ {Customer}_{Opportunity ID}_{System}.xlsx in theView Archive link at: http://mts.ent.vce.com/Unified%20Dashboard/.

Port map Port_Map_{Customer}_{Opportunity ID}_{System}.xlsx inthe View Archive link at: http://mts.ent.vce.com/Unified%20Dashboard/.

Licensing {number} - C240 Licenses.pdf or {number} - ScannedLicenses.PDF in the View Archive link at: http://mts.ent.vce.com/Unified%20Dashboard/.

BOL Packing List {Opportunity ID}_{Customer}VxBlock.PDFin the View Archive link at: http://mts.ent.vce.com/Unified%20Dashboard/.

LCS Z Drive at \\Nasdprd102v3\VCE_ENG_OPS\GlobalProjects

Logical Build CRG Output Shutdown notification email from PM (Domestic only)

Customer location (for EMC support) EMC site ID - used in License Activation Codes (LACs)and in the Unified Dashboard.

Cisco components See architecture guides at: http://www.cisco.com/c/en/us/solutions/enterprise/design-zone-collaboration/index.html

CRG Script https://wiki.ent.vce.com/display/PS/Script+Files

Knowledge Transfer Slides https://wiki.ent.vce.com/display/GTP/Knowledge+Transfer

Vblock Modular Diagram https://wiki.ent.vce.com/pages/viewpage.action?title=Modular+Vblock+Systems+connectivity+diagrams&spaceKey=GS#

Vblock System Test Plans https://docs.vce.com/search?q=Test+plan

Deployment Checklist https://wiki.ent.vce.com/display/DCBSP/Deployment+Checklist



http://mts.ent.vce.com/Unified%20Dashboard/













http://www.cisco.com/c/en/us/solutions/enterprise/design-zone-collaboration/index.html



https://wiki.ent.vce.com/display/PS/Script+Files

https://wiki.ent.vce.com/display/GTP/Knowledge+Transfer

https://wiki.ent.vce.com/display/GTP/Knowledge+Transfer

https://wiki.ent.vce.com/pages/viewpage.action?title=Modular+Vblock+Systems+connectivity+diagrams&spaceKey=GS#



https://docs.vce.com/search?q=Test+plan

https://wiki.ent.vce.com/display/DCBSP/Deployment+Checklist

https://wiki.ent.vce.com/display/DCBSP/Deployment+Checklist


As-Built https://wiki.ent.vce.com/display/VCDC/VCE+As-Built+Maker+Tool

Cisco, EMC and VMware documentationThe following table provides links to documentation for each of the product lines that are discussed in thisguide.

Product Description Link to documentation

Cisco UCS Servers High-density, rack-mount server for production-level network infrastructure, web services, andmaintenance data center, branch, and remoteoffice applications.

http://www.cisco.com/c/en/us/products/servers-unified-computing/product-listing.html

Cisco switches Physical and virtual switches providing highspeed, high availability, and scalability to VCEsystems.

http://www.cisco.com/c/en/us/products/switches/product-listing.html

EMC Products and Solutions EMC product catalog. http://www.emc.com/en-us/products-solutions/products.htm

VMware Virtualization Provides a scalable and extensible system thatforms the foundation for virtualizationmanagement.

www.vmware.com/solutions/



https://wiki.ent.vce.com/display/VCDC/VCE+As-Built+Maker+Tool

https://wiki.ent.vce.com/display/VCDC/VCE+As-Built+Maker+Tool

HTTP://WWW.CISCO.COM/C/EN/US/PRODUCTS/SERVERS-UNIFIED-COMPUTING/PRODUCT-LISTING.HTML



HTTP://WWW.CISCO.COM/C/EN/US/PRODUCTS/SWITCHES/PRODUCT-LISTING.HTML



http://www.emc.com/en-us/products-solutions/products.htm



HTTP://WWW.VMWARE.COM/SOLUTIONS/

Task overviewThe following figure shows the phases that a VCE system goes through from manufacturing todeployment. After Manufacturing builds and ships the system, all system-related documents andcustomer-requirement files are available for the D&I team. When the system arrives at the Customer site,the on-site First Responders are responsible for setting up, cabling and powering on the VCE systems.The First Responders then provide a support role to the remote Network, Storage, Virtualization andCompute teams to finish deploying the system.

Copyrights and trademarksCopyright 2016 VCE Company, LLC. All Rights Reserved. VCE, VCE Vision, VCE Vscale, Vblock,VxBlock, VxRack, VxRail, and the VCE logo are registered trademarks or trademarks of VCE CompanyLLC. All other trademarks used herein are the property of their respective owners.



Obtaining D&I requirements and customerdeliverables - D&I teamLocating information about system deliverables for customers.

About this task

The D&I team receives customer requirements from several sources:

• Pre-Implementation Planning Meeting - The Project Manager should schedule a planningmeeting with the D&I team (or at least send a Handoff via email if schedules do not permit), tohand off documented deliverables and requirements for the deployment and installation. For moreinformation, see the Pre-Implementation Planning Meeting at: https://inside.emc.com/docs/DOC-199416.

• Unified Dashboard - The D&I team can also review the following information at http://mts.ent.vce.com/Unified%20Dashboard/ prior to arriving at a customer location.

Before you begin

Obtain the Opportunity ID or Customer Name from the Project Manager for use on the UnifiedDashboard. For more documentation references, see Additional documentation references (see page 6), System-specific references (see page 8), and Cisco EMC and VMware documentation (see page 9).

Obtain the VCE and Customer Sales Agreement as described in http://www.vce.com/asset/documents/onsite-deployment-service.pdf.

11 | Obtaining D&I requirements and customer deliverables - D&I teamDELL EMC CONFIDENTIAL






http://www.vce.com/asset/documents/onsite-deployment-service.pdf

http://www.vce.com/asset/documents/onsite-deployment-service.pdf

Procedure

1 Use the Opportunity ID or Customer Name on the Unified Dashboard for searching the UnifiedDashboard (http://mts.ent.vce.com/Unified%20Dashboard) to review how the system wasconfigured.

The Build Entry page in the Unified Dashboard provides non-configuration information about theorder. Use View All for a larger image display.

— Administrative Data: The top of the page displays administrative information such as BuildStatus, Assigned TPM, and Primary VArch/PSPM.

— Configuration Summary: This section only represents the infrastructure and configurationutilized for the system being built. Non-configured hardware does not appear in this summarybut could on the build list.

— Comments: This section provides information on non-standard build information so that anyindividual reviewing the Build Entry page is informed on any build customization. Additionally,any open issues preventing/delaying the assessment/QA approval such as pending PCCs,Site Survey, etc., lists and describes the Issue, comment of resolution, and date of closure.

— Special Build Instructions: This section informs Production of any non-standardrequirements that are needed to meet customer expectations and reflects the buildinstructions at the bottom of the Build List in the Floor document.

Obtaining D&I requirements and customer deliverables - D&I team | 12DELL EMC CONFIDENTIAL


http://mts.ent.vce.com/Unified%20Dashboard

2 Scroll down to view the Files for the final BoM, the final Solutions Abstract, and the final SiteSurvey:

— Files: The final BOM, the final Solution Abstract, and the final Site Survey files are uploadedto this section of the Build Entry page.

The Floor File, Gateway Configuration, and Port Map may not be the latestversion on this page. See the Archive folder for the latest version of these files.

Any material that ships in the tote and not installed in the system is included in thecomments column of the Build List within the Floor File next to the correspondingmaterial being shipped in the tote and not noted in the Special Build instructions.

— IAs / DS: Any Impact Assessments (IAs) or Deal Support (DS) tickets that are listed in SFDCthat affect physical build are listed in this section.

— Issues: Any hardware missing from the BOM that has to be added through MFGEmpowerment (other than POUs and Side Panels) is listed in this section. Additionally, anyissues found when reviewing the Site Survey are recorded as an issue.

— PCC: BOM changes that occur after initial booking are noted in the issues section of thedatabase before and while the build is in the factory. D&I PCCs are not noted.

— Site Survey: This document has two main sections:

Section A - Required for Build, which details critical customer site requirements, such as:

— UID

— POUs and Power receptacles

— Location of Cable Trays and Power Receptacles

— Required Customer Uplink Speed

— Cabinet Separation and Data Center Floor Layout



— Information provided in the Site Survey, which indicates the required POUs and PowerWhips (as necessary) through MFG Empowerment.

Site Survey issues are noted on the build entry when there are significantchanges from the original document submitted, (e.g. power, uplinks andseparation)

Section B - Required for Delivery

3 Use the View Archive link to view Images, licenses, LACs, the final Floor file, the Gatewayconfiguration, BOL files, and the final Port Map.

The Floor and Port Map files from other Unified Dashboard locations may not bethe latest versions.

Obtaining D&I requirements and customer deliverables - D&I team | 14DELL EMC CONFIDENTIAL


4 Review the Power shutdown notification email ("…Logical build is now complete…"). This email,which is distributed by the PM, provides the latest CRG Output and Hand-Off Notes originatingfrom the Logical team.

5 Locate the Customer's Project Folder on the shared repository and review the LCS Document,and the Logical Build CRG Output and Handoff Notes. The folder can be found in the year andquarter of project kick-off in \\Nasdprd102v3\VCE_ENG_OPS\Global Projects.



Preparing for Deployment and Implementations

Before the Deployment and Implementation begins, some tasks can be completed in advance. Thisimproves efficiency ensuring a smooth and speedy delivery. These tasks are carried out by the TechnicalLead assigned to the project, with assistance by any member of the team.

See System-specific references (see page 8) to locate references for tasks.

Task Detail Team Member

Review Solutions Abstract All team members should ensurethey are aware of what system isbeing installed.

All

Review LCS Review the Logical ConfigurationSummary to discover the low leveldetails of the Vblock System.

All

CRG Download the latest CRG Softwareand prepare the configuration filefrom the details found in the LCS.

Tech Lead/Any

Credentials File Prepare an Excel spreadsheet listingComponent Type, Device Name,Device IP address, Username,Password to ensure the team isready to log in to all componentsimmediately.

Tech Lead/Any

Deployment Checklist Download the latest DeploymentAudit Checklist. Customize theInformation Page.

Tech Lead/Any

Cisco Smart Call Home Prepare the Cisco Smart Call Homeconfiguration for Cisco Switches,MDS, and UCS, even though thecontract IDs may not be available atthis time.

Network, Compute, Storage

As-Built Document Collector Install and prepare the As-BuiltCollector by customizing thespreadsheet created by the As-BuiltTool.

Tech Lead/Any

Vblock System Diagram If a diagram is to be provided to thecustomer, it can be created and/orcustomized in advance. It can bedone using the LCS information andthe modular diagram template. It isadvantageous to the networkengineer as it ensures a thoroughunderstanding of the system that willbe deployed.

Network

Preparing for Deployment and Implementations | 16DELL EMC CONFIDENTIAL


Task Detail Team Member

Knowledge Transfer Download and customize therelevant KT slide decks. They shouldcontain information relevant to thesystem being deployed, be up todate, and cover all components.

All

17 | Preparing for Deployment and ImplementationsDELL EMC CONFIDENTIAL


Installation prerequisites - First RespondersThis section describes the installation requirements, protocols and assumptions that must be adhered toby the First Responders before proceeding with the installation.

Before you beginBefore you begin reviewing the installation prerequisites:

• The D&I team has reviewed the references in Obtaining D&I requirements and customerdeliverables - D&I team (see page 11).

Safety cautions and warnings

To avoid temperature, humidity and other changing climate conditions, the VCE System cabinet mayneed to acclimate to the environmental changes. For example, the system may need to stand in place for24 hours before you can begin powering on the system.

Use caution when moving the VCE System cabinet because the cabinet is top heavy.

Electrostatic discharge (ESD)

To ensure overall product quality and to eliminate the possibility of damage fromelectrostatic discharge, observe ESD handling procedures.

All implementation personnel must attend an ESD training class prior to performing any system or boardhandling. For safety reasons, it is recommended that implementation personnel use heel straps on bothfeet or wrist straps where applicable.

Safe handling of lithium ion batteries

For a guideline on the safe handling of lithium ion batteries, see Safe handling of lithium ion batteries inthe VCE Physical Build Guide.

Power requirements

Power must be installed by the customer's Facilities Management before the VCE System arrives on site.For details about power, refer to the Physical Planning Guide.

Installation prerequisites - First Responders | 18DELL EMC CONFIDENTIAL


Required tools

Be sure to have the following tools available before you begin the installation. To view a complete list oftools used in the manufacturing of VCE Systems, see Tools and accessories in the VCE Physical BuildGuide.

• RJ45 crossover cable (only for logical installation)

• Cisco Console Cable Cables SFP for temporary link

• Cat6a Ethernet cable to reach from the N3K-A to N5K-A or N9K-A.

• 1 GbE SFP, SKU: STOK-GE_T-01-A, P/N: SFP-GE-T.

Desc:1 Gigabit Ethernet copper RJ-45 connector.

• 3/8" drive socket 9/16" standard

• Scissors for plastic straps

• Wire cutters for plastic straps

• 9" torpedo level

• #1, #2, and #3 Phillips screwdrivers

• 3/8" drive socket 3/8" standard

• 3/8" drive ratchet

• 3/8" drive extension, 3" long

• Two sets of ESD heel or wrist straps

• 6mm Hex wrench (for leveling the VCE System)

• Work gloves (gloves must be worn when using tools, as per the VCE EHS orientation for D&Iteams.)

• Safety glasses

• Safety boots

• Ear plugs, if necessary

• T25 Torx wrench (star shape) (for IPI cab fasteners)

• Power adapter (to provide laptop power from the PDU) IEC C13, or C14 to BS13

• High visibility vest, if necessary

Assumptions

19 | Installation prerequisites - First RespondersDELL EMC CONFIDENTIAL


This guide assumes the VCE System has been installed only by VCE Professional Services or by certifiedVCE partners. This guide also assumes that the person who is installing, configuring, and powering upthe VCE System:

• Has ensured that the computer has the following utilities and tools or equivalents:

— VMware vSphere Client - VCE FTP

— A terminal emulation program that supports SSH, such as PuTTY - for example, see thePuTTY web site at http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

— An EMC VNXe Connection Utility - EMC Support

— The latest version of Java - Java.com

— A Multi-port Mini switch, such as the 5 Port 10/10Mbps N-way mini switch - for example, seethe W-Linx Technology SW-005CM-X.

— Determine if WI-FI is available.

— A CAT-5/5e RJ-45 In-Line Coupler -For example, see the Insignia Inline network cablecoupler

— PowerCLI

— CRG

— UCS Power Tools

— Switch Backup Script

— Diff Tool

• Provide VCE on-site and/or off-site representatives with access to the customer's systems andnetworks (including, without limitation, remote systems and remote network access) as necessaryto perform the Service during normal VCE business hours or at mutually agreed times as definedunder customer responsibilities in the service offering data sheet.

• Has ensured that all safety checks have been completed, per the EHS D&I training:

— Customer or Partner must not power on the VCE System without permission from all VCEteam members.

— Before the VCE System is powered on, earth or ground the VCE System.

• Has referenced the cable cypher for reading the cable labels.

• In addition, this guide assumes that the following tasks have been completed:

— Reviewed the logical configuration. Refer to the customer's Logical Configuration Survey.

— Prepared the site for installation. Refer to the customer's Site Survey.

For details about installation planning, site preparations, and physical specifications, refer tothe VCE System Physical Planning Guides.



HTTP://WWW.CHIARK.GREENEND.ORG.UK/~SGTATHAM/PUTTY/DOWNLOAD.HTML

Verifying the location with the customer

Before you begin the installation, have a conversation with the customer to:

• Verify the exact location of the cabinet, not the general location. Sometimes the location isassigned with grid coordinates in the data center.

• Ask the customer: "How do they want the racks justified on the floor?"

— Justify the front or back door to the tile/grid line.

— Front or back of the racks themselves, so that the doors overlap a tile/gridline.

— Align the VCE racks to the others in the row/column of racks in the DC.

• Verify the orientation of the racks (front to back) to properly utilize the hot/cold aisle structure ofthe DC

• Validate that the layout matches the floor file elevation document.

Cabling requirements

See Cabling in the VCE Physical Build Guide for a complete description of cabling for the VCE System.

Floor tiles

If the data center has a raised floor, ensure that there are slotted floor tiles to drop the power through.The customer or data center are responsible for this information. Ensure that the holes to put the whipsthrough are large enough for the plug, especially when working with 60 AMP PDUs.

Be sure not to move tiles unless you verify it with the customer or data center.

Important: Some data centers have alarms set to their tiles. If that is the case, before you remove anytiles, obtain clearance from the customer. If you remove tiles without clearance, alarms couldgo off. When you remove tiles, be sure to follow the safety rules to prevent equipment orpersonnel from falling through the opening. If power is top down from the ceiling, ensure thatladders or mobile scaffolding is provided.

Verify the power

Before you begin the installation, determine the power attributes (see the BoM for the PDU type thatindicates requirements 60A, 3 phase, type of connection, etc.) then have a conversation with thecustomer to:

• Verify the power and ensure the receptacles correctly match what is installed in the VCE System.If they are different, notify your PM immediately.

• Verify that the whips are long enough. Sometimes the overhead power does not include a whipfrom the receptacle side. Ensure that the VCE whips will reach. Sometimes you need to flip thepower distribution unit (PDU) around to accommodate the length of the whip.

21 | Installation prerequisites - First RespondersDELL EMC CONFIDENTIAL


• Ask the customer: Who is allowed to plug in and touch the power receptacles, and when?Sometimes the power can only be plugged in by certain personnel during a particular time frame.Refer to the VCE Vblock Systems Site Survey, and verify with the on-site personnel.

• Ask the customer if they have a labeling system for the power whips. Some customers prefer tocolor code and/or label each power whip to ensure redundancy when plugging them into thepower sources. For example, a customer labels the power whips with two different colors: 1) oneside blue and 2) one side orange. Ask the customer if they want us to label and drop the powerwhips following their system or are they going to do it.

Network uplinks and customer core

The network uplinks and cables to the customer core are typically not applicable to the job of the firstresponder, but it is definitely a good conversation to have with the customer. At this point all you're tryingto do is make sure the cables have either been run, or are planned to be done before the actual D&Istarts. If they need details such as cable/SFP type and quantity, refer them to the Solution Summary/Abstract or the LCS. All of the particulars should have been determined before the build was started inmanufacturing.

Sometimes the customer has purchased the service for VCE to supply and run the cables to their core.For details, refer to Cabling in the VCE Physical Build Guide for a complete description of cabling for theVCE system.

Customer Cabling Requirements

Some customers and data centers are very particular about their cabling. Refer to the following table tohelp guide the conversation.

Important: Do not connect a cable unless it has a label on it. If additional labels are needed, and if timepermits, submit a request for labels from Manufacturing. Otherwise, ask the customer for alabel maker or contact your PM for approval to purchase a label maker. It is important to havelabels on the cables for future work on the VCE System. If the customer needs an upgrade ormaintenance, and the cables are not labeled, it becomes very difficult and time consumingtrying to work with unlabeled cables.

Cabling type Topic

Inter-rack cabling Sometimes customers do not allow inter-rack cabling, and the cabling mustgo overhead or under the plenum. Verify the customer cablingrequirements.

Overhead/Under floor cabling Depending on where you are, sometimes this work can be done only bythe data center or union workers. Work with the customer and the workers.

• If you are cabling, know the customer and data center standards.

• Know where to enter and exit the cable trays (ladder racks).

• Do fiber and copper have separate trays?

• Are cable waterfalls required, and available?

• Is slack to be coiled in the rack, run out of and back in the rack, or keptin the cabinets?

• When running the cables, try to keep the VCE cables separate anduntangled from other customer cables. To keep the cables separate,put Velcro on the VCE cables every few feet.

• Be aware of obstacles such as fire alarms and sprinkler heads.



Installing at the customer site - First responders

This topic describes the First Responder tasks for reviewing inventory, unpacking and installing thesystem cabinets, becoming familiar with the customer data center site, inter-cabinet cabling, andpowering on the system. As the "eyes and hands" for the resource engineers, they are on site from themoment the system is unpacked through completion of the test plan.

Before you begin

Before you begin reviewing the Installing at the Customer Site procedures, make sure:


• The First Responders have reviewed the installation requirements, protocols and assumptions inthe Installation prerequisites - First Responders (see page 18).

Unloading the inventory

If you are at the customer's site before or while the shipping company is unloading the VCE System:

• Find the bill of lading and verify what was shipped. Notify the PM of any discrepancies.

• Let the shippers or movers do their job. They have a contract to unload, unpack, and move thecabinets into place.

• If the Cisco UCS chassis is shipped separately, put them into the racks and the shippers canassist you even though it is not their responsibility. The labels next to the RUs on the front of thecabinet correlate with the proper location of each Cisco UCS Chassis. There may be up to fourUCS Chassis per cabinet.

• Your help is always appreciated by the shippers. If the delivery floor is big enough, you can assistwith the unloading and unpacking of the racks in tandem with the shippers.

When you arrive

Immediately upon your arrival, if you notice any damages occurred or there are missing components,contact your PM and report the issues. Do not wait. If something is damaged or if a part needs to beshipped overnight, the PM needs to know immediately because installation time needs to be usedjudiciously.

Recycling packaging and carton instructions

Recycle the packaging and cartons or ask the shipper to take them, which is usually stated in theircontract or in the VCE Vblock Systems Site Survey.

23 | Installing at the customer site - First respondersDELL EMC CONFIDENTIAL


Verifying the VCE System inventory

• The VCE System inventory would not be on the bill of lading or the packaging list form theshippers, as it is not that detailed.

• Ensure all VCE System components are there, such as the correct number of blades, chassis,DAEs, and correct EMC VNX model. Refer to the BOM or the Logical Configuration Summary.

Examining the cabinet location

• If you have not done so already, take a walk from the dock to the data center and understand theroute you are going to take, and the placement for the VCE System in the data center.

• Make a note of anything protruding or hanging from the walls, such as pipes, fire alarms, fireextinguishers, pictures, door hinges, or tile pullers.

• Make a note of and verify that the VCE System does not hit anything hanging from the ceiling,such as fire sprinklers, pipes, EXIT signs, magnetic door locks (under door jams), securitycameras, or ladder racks.

• An example of something to look out for:

In the picture, the ladder rack is positioned too low, so that when the power is plugged in, the rear door ofthe VCE System cabinet cannot be opened.

Unpacking VCE System IPI cabinetsRemove packaging materials and shipping brackets, and roll the VCE System cabinet from its shippingpallet. This tasks requires a three-person team to safely roll the cabinet off the pallet.

About this task

You will need the following tools:

• Cutters to remove packing straps

• Socket driver

Installing at the customer site - First responders | 24DELL EMC CONFIDENTIAL


• 22 mm (7/8 in.) socket

• 16 mm (5/8 in.) socket

• 9/16 in. (14 mm) socket



Procedure

1 Remove shipping materials and ramps.

a Remove the straps and corrugated packaging from the system.



b Remove the ramps and any boxes or other materials from both sides of the cabinet.

Do not pull a ramp down from the top. To release the ramp from the pallet,grasp the ramp, pull it straight back toward you, then pull it straight up to free itfrom the screws.

c Remove the poly bag.



2 Attach the unloading ramp

a Insert the ramp brackets into the pallet notches in the rear of the pallet.

Important: Cabinets are rolled from the pallet, rear side first. Note the ROLL OFFDIRECTION markings on the pallet.



b If your shipment includes a two-piece ramp, attach part A to the pallet and part B to part A.



3 Remove the cabinet shipping brackets from pallet and cabinet frame.

a Open the rear cabinet doors (ramp side) and detach the shipping bracket by removing three16 mm bolts from the frame and four 9/16 in. bolts from the pallet.

b Remove and the bracket and bolts. Set aside bolts and brackets for reuse or recycling.

c Close and latch the rear doors.



d Open the front cabinet door (opposite the ramp) and detach the door bracket by removingtwo 22 mm nuts.

e Remove the bracket from the frame. Set aside nuts and bracket for reuse or recycling.

The cabinet is heavy. Make certain you have sufficient help and secure footingbefore removing the final bolts from the pallet and rolling the cabinet onto theramp. Do not stand on the ramp, in front of the cabinet.



f Open the front door and detach the shipping bracket by removing three 16 mm bolts from theframe and four 9/16 in. bolts from the pallet.

g Remove the bracket and bolts. Set aside bolts and brackets for reuse or recycling.

The cabinet is heavy. Make certain you have sufficient help and secure footingbefore rolling the cabinet onto the ramp. Do not stand on the ramp, in front ofthe cabinet.



4 Roll the cabinet down the ramp. Using a three-person team, balance and guide the cabinet fromthe sides and the pallet.



What to do next

After the cabinet has been removed from the pallet, the ramps, brackets, fasteners, and packagingmaterials can be recycled or reused.

3.6 Moving the VCE System from the loading dock to the datacenter

• After you are familiar with the site layout, move the racks. Follow all safety guidelines and takeyour time. Depending on the customer environment, two people might be required to move arack, one in front, and one in back.

• If you have enough space, move rack one first so that you can put it directly into its final locationand avoid having to re-arrange it later.

• Depending on the space available, bring the other racks in, in order, but do not put them in theirfinal location. You will need space to work and cable. Leave about 6-12'' between the racks towork with. If you have to, set aside the next few racks until you are ready to work with them.

Positioning the cabinetPlacing the cabinets in the Data Center.

Procedure

1 Verify the cabinet layout - Verify that the cabinets are located properly according to the customerrequest. For best practice, the cabinet layout goes from left to right as indicated in Elevations inthe floor document viewing the Vblock System from the front.

2 Verify the floor tile position for dropping power down.

Important: Verify the floor tile position for dropping power down for a data center with a raisedfloor. If this is not checked, you might have to undo hours of work later on!

— Before you drop the feet for any rack, ensure that the floor tiles with cutouts for the powerdrops are in the proper place for all racks. For example, all the tiles are in a place where thepower can drop down without interference and all racks will be able to sit in their final locationwithout having a wheel or foot go through a tile cutout.

— Sometimes the cutouts in the tiles are not in the correct location. In this case, the tiles mayneed to be rotated. However, before you move or rotate any tiles, be sure to check if you canmove the tiles yourself.

3 Drop the cabinet feet and level:

a Set, place, and level the first rack immediately- provided that you have the space, and thefloor tiles are correct. Now you have a starting point that does not move, and a target rack tojustify the rest of the racks.

You do not have to level the racks as you go. You can do them all at the end whenall the cabling has been completed. However, it has been found that leveling themas you go keeps the racks more lined up in the end.



b Ask the customer for approval of the work so that you do not have to undo everything later.

c After you get the customer's approval, complete the cabling for each component thatconnects into the first rack. Keep in mind, some cables will span farther than just one rackapart. SAS, Cat6, and Twinax cables can all go as far as from racks 1 to rack 5, dependingon the setup.

d Ensure that the cabling between the racks is done properly. For cabling details, see Cablingstandards and best practices in the VCE Physical Build Guide.

e Verify that the cables are not outside the bar. Cables between the side bars could getcrushed if the racks were to be put together.

f Establish all inter-cabinet cables first and then apply Velcro.

g Use the Velcro to make everything neater and to control the cables as much as possible.

h With very slow and controlled movements, so as not to overstretch or shear a cable, movethe racks closer together.



i After moving the rack, drop the feet, as shown in the following illustration. This is one of thefour feet on the cabinet.

j Using a 6-mm hex key with a drill or ratchet, lower the leveling screw (CW), until the cabinetwheels next to the bolt are off the ground and able to spin freely.

k Place the level at the top of the front of the cabinet then raise or lower the feet (while stillkeeping the wheels of the ground) until the cabinet is level.

l Due to inconsistencies in how the racks are made, and uneven flooring, rolling the racks intoplace may result in some uneven gaps between cabinets.



m After you level the rack at the front and back, and with the rack next to it (at the same height,)you need to correct for any gaps. Very carefully push or nudge the rack to close the gap. Bemindful of the alignment you want and ensure that you do not accidentally push the otherrack(s) out of alignment. A rack with no gap looks like this. Anything other than this is notacceptable.

Grounding and earthing the VCE System

It is the customer's responsibility to ground and earth the VCE System. For information on grounding andearthing for a VCE System, refer to the following example: http://www.panduit.com/ccurl/88/656/Reference%20Architecture%20Design%20Guide%20Part%203,0.pdf

Vertical Exhaust Ducts

Some cabinets require Vertical Exhaust Ducts (VED). For more information, see:

• http://www.panduit.com/heiler/InstallInstructions/N-VEDforNandSTypeCabinets--5950--ENG.pdf

• https://wiki.ent.vce.com/display/PE/VED+IPI+Cabinet

Cabinet ganging bracket kitsGanging bracket kits may be included in some VCE Systems to connect cabinets together at thecustomer's site.



HTTP://WWW.PANDUIT.COM/CCURL/88/656/REFERENCE%20ARCHITECTURE%20DESIGN%20GUIDE%20PART%203,0.PDF

HTTP://WWW.PANDUIT.COM/CCURL/88/656/REFERENCE%20ARCHITECTURE%20DESIGN%20GUIDE%20PART%203,0.PDF

HTTP://WWW.PANDUIT.COM/HEILER/INSTALLINSTRUCTIONS/N-VEDFORNANDSTYPECABINETS--5950--ENG.PDF

https://wiki.ent.vce.com/display/PE/VED+IPI+Cabinet

Cab 1.0 to IPI ganging bracket kit, STOK-Q304-00:

Ganging brackets are identified by the types of cabinets they are designed to connect. See thedescriptions in the table that follows:

SKU Part Number Description

STOK-Q304-00-A BVBGB12B Ganging Bracket Kit, Cab 1.0 to IPI, BLK

STOK-Q304-00-B BVBGB12W Ganging Bracket Kit, Cab 1.0 to IPI, WHT

STOK-0006-00-A FNS-KIT Ganging Bracket Kit, Cab 1.0 to Cab 1.0, BLK

STOK-Q279-00-A VCE-SCNKIT Ganging Bracket Kit, IPI to IPI, BLK

Establishing inter-cabinet cablesThis chapter describes how the First Responders establish inter-cabinet connections.

Procedure

1 The inter-cabinet cables to be plugged in are bundled and wrapped with white Velcro aroundthem. All loose cables should be plugged in -- the only exceptions are the fiber cables that arelabeled SPARE or CUSTOMER NET.



2 You can safely assume all cables that are unplugged are going to another rack because all in-rack cabling is done within the factory. However, always verify the cables by reading the cablelabels.



3 Locate cables in one of the following locations:

— Under the side-rack middle support beams

— Under the side-rack middle support beams

— These SAS cables are attached to the center horizontal cross brace on the side of the cab.



— This white Cat6 cable connects to an N3K in another cabinet. This cable has been routeddown the fingers and secured to the middle crossbar.

General cabling tips

• Do your best to match how the cabling looks from the factory.

• Run the cables though the cable management whenever possible.

• Keep the cabling neat. Avoid having the cabling crisscrossed, like spaghetti, and not cleanlooking.



• Use the Velcro to make clean looking groups of cables. On the left, the cables are not organizedbut on the right, the cables are neat, tied with Velcro.

• The right side power cable is routed up and behind the connectors, along the channel, and downthe left rear frame. The left side power cable is routed up and behind the connectors, along thechannel, and down the right rear frame. All power connectors are sealed within an ESD bag,secured with a zip tie, and attached to the frame.

In the future, someone from VCE might have to come back and unplug everything. The neater thecabling, the easier it is to make sense of it when taking it apart.

If there are two of the same pieces of hardware in the VCE System, the cabling must be identicalfor both components.

Cabling a VCE System in the Vblock System 300/540/740family



Cabling the Cisco UCS chassis

When you cable the Cisco UCS chassis, perform the following tasks:

• Cable the fabric extenders

• Cable the fabric interconnects

• Cable the switches

• Cable the storage arrays

Cabling the fabric extenders

In the back of the Cisco UCS chassis, cable the Fabric Extenders:

• Connect 4 Twinax cables from each Fabric Extender to a Fabric Interconnect.

• Fabric Extender 1 is on the left, Fabric Extender 2 is on the right, looking at the back of a CiscoUCS chassis.

• Fabric Extender 1 connects to Fabric Interconnect-A, Fabric Extender 2 connects to FabricInterconnect-B. Keep track of which rack you are in and which rack the cables are coming fromand going to. Chassis 1/A is in the same rack as Fabric Interconnect-A and so cabling fromFabric Interconnect-A to Fabric Extender1 will already be done.

• In a typical Vblock System 300 Family or a Vblock System 700 Family build, all Twinax and fibercables that connect to a Fabric Interconnect should already be connected to the FabricInterconnects on the Fabric Interconnect side of the cable. Only the management and heartbeatcables for the Fabric Interconnects should remain unconnected.

• The management cables connect from the AMP switch. The management cable to FI A willconnect from AMP switch A, and the FI B will connect from AMP switch B.

• The heartbeat cables connect to the L1 and L2 ports on the front of the Fabric Interconnect. Oneside was already connected in the factory, if they are in separate racks. These cables, whenunconnected, are usually found on top of the fabric interconnect or Cisco UCS chassis in racksone or two.

• Observe how the cable passthrough unit is used in the rack it is plugged in on, and mimic thiswhen you connect the fabric Interconnect in the other rack.

Cabling the Cisco Nexus 5500 Series Switches

Cables that connect to the Cisco Nexus 5500 Series Switches are:

• Customer uplinks are typically fiber cables.

• Twinax cables (or fiber cables in some cases) connect from the Fabric Interconnects. Both FabricInterconnect-A and Fabric Interconnect-B connect to each switch. Usually four cables from eachfabric interconnect connect to each Cisco Nexus 5500 Series Switch.

• Twinax cables (or fiber cables in some cases) connect from the other Cisco Nexus 5500 SeriesSwitch as keep alive or heartbeat cables. Usually, two cables are used.



• If there is unified storage (data movers and control stations for NFS/CIFS storage) twinax cablewill connect from the data movers. One cable from each data mover to each switch, for a total offour cables per switch, is typical - However, this can change depending on the customer. Thearchitecture for this will be listed in the LCS.

• If there is a unified network (a VCE System without Cisco MDS switches) fiber cables will connectfrom the EMC VNX storage array to each Cisco Nexus 5500 Series Switch. The number ofconnections varies, depending on the EMC VNX model. There are additional fiber cables comingfrom the fabric interconnects for the SAN network. All of this cabling was already done at thefactory.

All of the fiber cable going to and from the N5K should already be connected in factory.You will actually be connecting the devices via the patch panels, as explained in Cabling the patch panels (see page 44).

• If there is a segregated network, a VCE System with Cisco MDS switches, no (fiber) cablesconnect between the Cisco MDS switch and the Cisco Nexus 5500 Series Switch.

Cabling the Cisco Nexus 30XX (AMP) switches

• Connect: Single copper cable between M0 ports on the front of the switches.

• Connect: Two Twinax cables between the switches at the back.

Cabling the Cisco MDS switches

For a segregated network (when there are Cisco MDS switches present) all SAN traffic will pass throughthe MDS switches. All cables that connect directly to the MDSs should already be plugged in. Theconnections into the MDS that you need to be concerned with will happen at the patch panel. See Cablingthe patch panels (see page 44).

Cabling the patch panels

• A small fiber patch panel is located at the top of every rack.

• Connect inter-rack Patch A in rack 1, inter-rack Patch B in rack 2, and so on.

• Read the floor diagram from manufacturing to verify the number to letter conversion. Verify thatevery patch panel has all its cables plugged in. Verify that all patch panel connections are tight,especially the connection in the back. The cabling tends to come loose and is harder to plug incompletely.

When plugging the cables into the rear of the patch panel, it is usually considerably easier to remove thepatch module, then plug them in. To do this, first unplug the cables from the front of the panel. Then,reach up and behind the panel, pinch the prongs on either side of the module and pull the module out.Once the panel is out, you can easily attach the cables to the rear. Then re-insert the panel and attachthe front cables.

Installing lithium ion batteries in EMC VNX and DAEs



About this task

The SPS Li-ion batteries are installed in the SPS tray from the front. For example, the EMC VNX 8000storage array has four battery slots:

Each battery weights approximately 28 pounds (12.701 kg).

Before you begin

See Safe handling of lithium ion batteries in the VCE Physical Build Guide.

Procedure

1 Grasp the SPS battery by its handle and, with the wheel latch on the bottom right, slide thebattery into the slot of the SPS enclosure (1).

2 Engage the battery by pressing the wheel latch while pushing the battery farther into the slot ofthe SPS enclosure (2). The battery clicks into place and the status indicator above the wheellatch shows yellow, indicating that the battery is engaged but not connected.

3 Connect the battery by pressing the battery's wheel latch while pushing the battery completelyinto the slot of the SPS enclosure (3). The battery clicks into the final position and the statusindicator shows green indicating that the battery is connected.



Preparing and cabling the EMC VNX and DAEs

Use the following guidelines for cabling the EMC VNX and DAEs:

All EMC numbering starts from 0. For example, a four bus system will be numbered from 0-3.

• The EMC VNX and DAEs operate in a daisy chain type of interconnect. All DAEs from one busconnect to each other.

• The key to cabling an EMC VNX properly is to first understand how many busses there are inyour particular EMC VNX. On the back of the EMC VNX storage processor (SP), locate only theA side. Look at the SAS cables and determine how many busses there are from the number ofdifferent colored labels on them. A number may be indicated, in addition to the number of colors,which makes it easier.

— An EMC VNX1 model can have 2, 4, 6, or 8 busses.

— An EMC VNX2 can have up to 16 busses.

• See Understanding DAE and SAS cabling labels and routing in the VCE Physical Build Guide.

• The DAEs connect between each other in order, from the lowest number in the bus chain to thenext highest in the bus chain, and so on. When connecting the cable itself, the diamond side ofthe cable connects to the lower enclosure, and the circle side connects to the higher side. Locatethe symbols on the metal ends of each SAS cable. For example:

— DAE bus 0, enclosure 0 connects from its diamond slot to the circle slot on DAE bus 0,enclosure 1.

— DAE bus 0, enclosure 1, connects from its diamond slot to the circle side of bus 0, enclosure2.

• Find all the spare LCC cables in rack 1 and run them to the other racks. A 16 bus system mighteven have DAE Link Controller Cards (LCC) cables stretching all the way out to rack 3 becausethere is not enough space for 16 DAEs in the first 2 racks with all the other hardware. The LCCcables plug into the circle symbol port of each DAE.

— Cables from SPA connect to the A side of the DAEs.

— Cables from SPB connect to the B side of the DAEs.

— When looking from the rear of the cabinets, the A side is on the right, and the B side is on theleft, which applies to both SPs and DAEs.

• When you run the LCC cables, keep them neat and try to match them to how the factory ran theexisting SAS cables. Create one neat conduit along each side of the racks going to the DAEs. Nocables crossing over each other and no knots. When going between racks, run the cablesthrough the center of the rack horizontally and somewhere vertically between the top of the CiscoUCS chassis and the bottom of the Cisco MDS switch or Cisco Nexus switch. There are cablemanagement hooks you can use. Do not run the cables through the same cable managementhooks as all the Twinax and Cat6 cables because they would create too much clutter.



The following illustration shows the slack of the LCC cables being kept neatly out of the way andseparated from everything else.

• After connecting the LCC cables, run the copper SAS cables to match the colors and order.

Location of the symbol on cable Connection location

If the diamond mark cables hang on the sides of theracks from the factory to be plugged in…

They connect to the DAEs lower in the chain, closerto zero and to the storage processor.

If the diamond mark end of a cable is from rack 2… Connect it to rack 1.

If the dot or circle mark is in rack 2… Plug into the DAEs in rack 3.



• The following illustration shows proper SAS cabling on the side of the VCE System.

• The following illustration shows proper SAS cabling in the back of the VCE System.

Connecting to the EMC Symmetrix VMAX

Here are some guidelines when cabling a VMAX:

• EMC is responsible for inter-EMC Symmetrix VMAX cabling.

• All fiber cables that connect to an EMC Symmetrix VMAX come from the Cisco MDS or Nexusswitches through the fiber patch panels. Run these cables out of the VCE System racks and backinto the EMC Symmetrix VMAX racks. Cable the storage array very neatly in accordance with thecustomer requirements. Refer to Customer cabling guidelines.

• When cabling in the EMC Symmetrix VMAX rack, use the bars on the top for slack management.Connect the VCE System rack to the existing fiber in the EMC Symmetrix VMAX rack through thefiber bridge, a small male to male connector. This connector is the same as the patch panel, butwithout the patch module itself. Match up the labels and you are finished with the cabling.



Post-installation checklist

Complete the following task list after you install and cable the VCE System.

Task Notes

When finished connecting the cables to the cabinets,verify with the customer that they are satisfied with theappearance of the VCE System. You want the customerto be completely satisfied with the appearance of theVCE System before you leave their site.

Ensure that all cables in the VCE System cabinet aresnug and that all existing connections are solid.

Ensure that the racks are level.

Before powering on the VCE System, ensure that allpower and ground connections are secure. Inform allD&I team members that the VCE System is going live.

Ensure that the area surrounding the VCE System isclean, free of Velcro, cable wrappers, cable caps, andzip ties. It needs to look better than when you arrived.

Provide photos of the completed rack implementation, ifand only if this is within the security guidelines of thedata center or company.



Powering on the VCE System - First Responders

This chapter describes how the First Responders using indicators, health checks, and visual indicators,power on the VCE system.

Before you begin reviewing the Powering on procedures, make sure:



• The First Responders have reviewed the tasks for inventory, unpacking and installing the systemcabinets, becoming familiar with the customer data center site, inter-cabinet cabling, andpowering on the system in Installing at the customer site - First responders (see page 23)

Verification and power on overview

Important: Do not power on the VCE System until:

• Permission is received from the customer, and the Network and Storage resources.

• Ensure that all cables are connected tightly and all the slack is neat. No messy cabling. Use lotsof Velcro.

• The VCE System has been acclimatized to its environment.

Powering on the VCE System

For instructions on the power on sequence for the VCE System, refer to the VCE Vblock ™ SystemPowering On and Powering Off Guide.

Ensure that this power on sequence is followed to prevent problems while booting theblades.

Verifying the status LEDs

After powering on, it takes a while for all the devices to do their respective power on self test. Waitapproximately ten minutes and then start looking for amber lights. Make a note of these lights and informthe PM.

Powering on the VCE System - First Responders | 50DELL EMC CONFIDENTIAL


Networking Tasks - Network Resource and FirstResponders

This chapter describes how the Network resource, working remotely or on site with the First Responder(at the discretion of VCE), establishes an uplink, or a temporary workaround link.

Before you begin reviewing the Network procedures, make sure:

• The D&I team has reviewed the references in Obtaining D&I requirements and customerdeliverables - D&I team (see page 11) and completed the tasks in Preparing for Deployment andImplementation (see page 16).


• The First Responder have reviewed the tasks for inventory, unpacking and installing the systemcabinets, becoming familiar with the customer data center site, inter-cabinet cabling, andpowering on the system in Installing at the customer site - First responders (see page 23)

• The First Responders using indicators, health checks, and visual indicators, have powered on theVCE system as described in Powering on the VCE System - First Responders (see page 50).

Network Engineer

Network engineers require implementation and troubleshooting skills in Cisco Nexus and Catalystswitches, and an understanding of a wide variety of customer switches, routers and networkinginfrastructure, included but not limited to the following topics:

• Cisco Data Center Technologies:

— Nexus VPC

— Awareness of UCS for troublehooting

— VRFs

• Cisco Routing & switching technologies

— L2 configuration

— Spanning Tree Protocols

— LACP

— CDP

— Management Services

■ Cisco CallHome

■ Syslog

■ SMTP

51 | Networking Tasks - Network Resource and First RespondersDELL EMC CONFIDENTIAL


■ NTP

Task overview for the Network engineer

The Network engineer works with the First Responders to establish an uplink from the VCE System to thecustomer network. If the customer network is not ready for connection, a temporary network connectionbypassing the customer is installed, enabling the Network, Storage and Virtualization teams to proceedwith some of their tasks using the internal routing.

Connecting to the customer network

Establishing a connection through the customer network allows you to enable the VCE system tocommunicate with the internal (home) network site. Having this connection enables work to proceed forthe Network, Storage and Virtualization teams.

One of the best views of the Network can be found in the LCS:

Networking Tasks - Network Resource and First Responders | 52DELL EMC CONFIDENTIAL


Another view of the network can be found in the Vblock connectivity diagrams.

The Vblock connectivity diagrams are available from: https://wiki.ent.vce.com/pages/viewpage.action?title=Modular+Vblock+Systems+connectivity+diagrams&spaceKey=GS#

Customer network status

Discuss with your customer to determine if the customer network is ready or not ready for connecting tothe VCE System.

The following tasks apply to the N3K (example: Cisco Nexus 3048, 3064, and 3172PQswitches), the N5K (example: Cisco Nexus 5548 and 56128P switches) and N9K (example:Cisco Nexus 9396 and 9372PX switches).

Customer Network is Ready





If customer network support indicates that the resource network is ready:

Task Examples Success Indicator

1. Clean up the factory configuration:

• Removing the default route fromthe N3K management switches.

• Add the route to themanagement VLAN gateway.

• Clean up the temporary linkmade between N3K andN5K/N9K in Logical Build.

• Remove secondary interfacesused for temp NTP and DNS

• Remove ESX_MGMT SVIs andVLANs from AMP switches

• If L3 uplinks, add floating staticto other switch

• Remove HSRP fromVblock_Mgmt interface

Use the ports numbersas per the port map.

# no ip route <0.0.0.0/0> <10.1.12.1> # ip route <0.0.0.0/0> <10.2.16.254> # default interface E/51 #shut

Ability to successfully ping from N3Kto the management gateway.

2. Config uplinks <- customerconfirms configurations

Use the ports numbersas per the port map.

#show run interface E/52-53

Check the configuration and confirmwith the customer that the requiredVLANS are allowed on the uplinkports.

#Switchport Trunk allowed VLAN add XYZ

VCE System connectivity isestablished from the managementand production to the customernetwork.

3. Physically connect uplinks

• One link first, check that STProot has moved to core, thenadd the other(s)

Plug in the customer uplink cable(copper/fiber) into the correspondingconfigured ports of the VCE SystemN3K and N5/9K

Green lights on the port.

#Show Interface "Uplink"

4. Determine if all traffic is working ->Ping VCE System Gateway(Management VLAN Next Hop), pingDNS (NTP, SMTP)

5. Test (From N3Ks)

• If successful, ensure the test VMcan ping Management Services,then proceed to next step (6.).

VCE Systemconnects tocustomer, and VM

# ping <Gateway IP> # ping <DNS IP> # ping <NTP IP>

Success is proven when the VCESystem N3K is able to reach themanagement VLAN gateway, DNS,NTP or any other specified IPaddress on the customer network.



and Storagesupport start theirtasks.

• If not successful, proceed to Customer network is not ready(see page 55) and continuetroubleshooting.

6. Run CRG, Test plan, DeploymentChecklist, LCS Audit

Refer to the Deployment Checklistand Test plan documents.

Depends upon the selectedDeployment Checklist option (Testplan has only Pass or Fail options).

7. KT Actual configurations presented onWebex. See also: https://wiki.ent.vce.com/display/DCBSP/Customer+Knowledge+Transfer+Slides

Customer is satisfied withpresentation.

Customer network is not ready

About this task

If the customer informs you that the network is not ready, the Network engineer directs the FirstResponder to install a temporary network cable that will enable an Ethernet connection between theNexus N3K-A and the Nexus N5/9K-A. This temporary connection allows the team (VM and Storage) tocontinue to configure devices on the VCE system and to make some progress on the D&I.

This task applies to Nexus 3048 and Nexus 3064 (N3K) for the AMP Management switches, and theNexus 5548 (N5K) and Nexus 9396 (N9K) for the VCE System Production switches, in systems withAMP-2. A single Cat6a Ethernet cable with SFP is installed temporarily, and is removed before uplinking.

A temporary connection can only be established before uplinking to the customer network.If a temporary link is established while uplinking to the customer network, a spanning treeloop may occur.

Before you begin

Confirm the number of VPCs that are configured on the site.

Creating an incorrect number of VPCs may result in STP problems.

Acquire the required components:

• Cat6a Ethernet cable to reach from the N3K-A to N5K-A or N9K-A.

• 1 GbE SFP, SKU: STOK-GE_T-01-A, P/N: SFP-GE-T.

Desc:1 Gigabit Ethernet copper RJ-45 connector.

• Tag or label to mark the cable as temporary.



HTTPS://WIKI.ENT.VCE.COM/DISPLAY/DCBSP/CUSTOMER+KNOWLEDGE+TRANSFER+SLIDES




Procedure

1 Insert a 1 GbE SFP in the rightmost (highest numbered) open port on the N5K-A or N9K-A slot 1.

2 Connect a Cat6a Ethernet cable to the N5K-A or N9K-A SFP.

3 Mark a tag or label to identify the cable as temporary, and attach to the Ethernet cable. Forexample: "temp N3K-N5K"

4 Connect the other end of the Cat6a cable to the rightmost open port on the N3K-A slot 1.

5 Inform the Storage and VM engineers, and other resources that a temporary Ethernet connectionhas been established, and includes the N3A and N5K-A/N9L-A ports used for the temporarycable. The VCE team proceeds to the configuration/test plan (Cisco call home, etc.), and the VCEnetwork engineer works with the customer to resolve the customer network issues.

6 If customer network issues are:

— Not resolved by end of week -> Reschedule the D&I and KT.

— Resolved -> Remove the temporary patch and proceed to step 1 in Customer network isready (see page 53).

A schematic of the Temporary Workaround Uplink follows:



Storage Tasks - Storage Resource and FirstResponders

This chapter describes how the remote Storage resource, working with the First Responders, enables theboot LUNs and Data LUNs .

Before you begin reviewing the Storage procedures, make sure:



• The First Responder have reviewed the tasks for inventory, unpacking and installing the systemcabinets, becoming familiar with the customer data center site, inter-cabinet cabling, andpowering on the system in Installing at the customer site - First responders (see page 23).

• The First Responders using indicators, health checks, and visual indicators, have powered on theVCE System as described in Powering on the VCE System - First Responders (see page 50).

• The remote Network resource, working with the First Responder, has established an uplink, or atemporary workaround uplink, as described in Networking tasks - Network resource and FirstResponders (see page 51).

Task overview for the storage engineer

Working with the First Responders, the Storage resource enables the boot LUNs and Data LUNs, whichis critical for the VMware environment. Without storage, the blades cannot boot, preventing the VM teamfrom proceeding.

Storage requirements:

Vblock 340 requirements

On the Vblock 340, the VNX array provides backend storage to the customer's production VMenvironment, which is dependent on the switching infrastructure (MDS or 5K/9K switches). Handoffs mustoccur between the VM team and the Storage team.

The on-site resource (First Responder) must power on all VNX components after the Vblockcabinets are powered on.


On the Vblock 540, the XtremIO provides backend storage to the customer's production VM environment,which is dependent on the AMP. Handoffs must occur between the VM team and the Storage team.

The on-site resource (First Responder) must power on the XtremIO controllers after the Vblockcabinets are powered on.

57 | Storage Tasks - Storage Resource and First RespondersDELL EMC CONFIDENTIAL



On the Vblock 740, the VMAX provides backend storage to the customer's production VM environment.

EMC CE must power on and setup the VMAX prior to the Vblock cabinets being powered on.

Verify all EMC supported devices are in "Install" status onthe EMC Installed Base

Verify that all storage device serial numbers are marked "Install". If any are not marked as Install, correctthe status yourself or open a ticket with the EMC Installed Base (IB) group to have them change thestatus to "Install." If any devices are not in "Install" status, you will not be able to deploy them or openEMC service requests for them.

Starting the storage portion of the VCE System Deployment Checklist

Open the Deployment Checklist document (Excel spreadsheet) and start performing the storage tasks.Depending on the VB model, there will be tasks for different storage devices. Following tasks arecommon to VB200, VB300, VB500 and VB700 models:

• PowerPath license verification

• DCNM (MDS call-home) setup

• ESRS setup and device deployment

• MDS switch setup completion and verification

• Backup configuration for all storage devices (including MDS switches)

The Deployment Checklist document is normally provided by the PM and is part of thehandoff to the D&I team.

Storage tasks

The following tasks are for storage D&I tasks.


(Pre D&I activity)

1. Gather storage parameters:

• Model type

• Host name

• IP address

• Device Serial Number

• EMC Site ID

• Contact information

Gather information from:

• LCS

• Floor file

• factory CRG file

• EMC Support portal

• EMC Install Base

- -

Storage Tasks - Storage Resource and First Responders | 58DELL EMC CONFIDENTIAL



2. Verify that all EMCsupported devices are in the"Install" status in the EMCInstall Base.

- - View devices in EMC Install Base.

3. Run Deployment Checklist See Deployment Checklist Complete all tasks in Deployment Checklist

4. Run VBx00 series Test plan See VCE x00 Series Test Plandocument

- -

5. Run CRG See VCE Underground VCEConfiguration Reference Guide(CRG) scripts

• XML files that contain device configurationdata.

• All storage for successful ESRSdeployment.

• Receiving test emails.

6. KT https://wiki.ent.vce.com/display/DCBSP/Customer+Knowledge+Transfer+Slides

Customer is satisfied

59 | Storage Tasks - Storage Resource and First RespondersDELL EMC CONFIDENTIAL





Virtualization Tasks - Virtualization Resourceand First Responder

This chapter describes how the remote Virtualization resource, working with the First Responders,configures and administers all VM guest servers, ESXi hosts, and VCE Vision.

Before you begin reviewing the Virtualization procedures, make sure:






• The Storage resource, working with the First Responders, has enabled the boot LUNs and DataLUNs as described in Storage tasks - Storage Resource and First Responders (see page 57).

Virtualization Engineer

Virtualization engineers require implementation and troubleshooting skills in VCE Vision, and anunderstanding of VMware infrastructure, included but not limited to the following topics:

• Cisco rack mount servers

• Blade servers

• Vision

• Windows 2008 servers

• Windows 2012 servers

• Microsoft SQL database

• VMware

Task overview for the Virtualization engineer

Working with the First Responders, the Virtualization engineer configures and administers all VM guestservers, ESXi hosts, and VCE Vision.

Virtualization Tasks - Virtualization Resource and First Responder | 60DELL EMC CONFIDENTIAL


Configuring the customer virtualization infrastructure

Prerequisites

• Networking configured with customer uplinks

• Power to the VCE System storage

Vblock 100 and 200 series do not include a Cisco UCS, and all hosts are managedindividually.


1. Connect to AMP servers via theCIMC through an Internet browser. Http://10.xx.xx.xx

Access to KVM console

2. Verify the ESXi on AMP host isbooted up and has connectivity tothe network.

Ping ESXi host Ping ESXi host succesfully

3. Power on AMP VM in a specificorder:

1 SQL

2 PSC/SSO

3 VCenter

4 Remaining AMP VMs (exceptVision VMs)

-- Successfully log in to the AMP VMs

4. Validate DNS entries for AMPVMs NSlookup


5. Bring up VCE Vision VM servers

• Core - accept EULA

• Multi System Management(MSM) - specify the FQDN.

Http://msm<server_name>.com


6. Run Deployment Checklist Review the Deployment Checklist Complete all tasks in DeploymentChecklist

7. Run x series Test plan Review the VCE x00 Series TestPlan document

8. Run CRG Review the VCE Underground VCEConfiguration Reference Guide(CRG) scripts

XML files that contain deviceconfiguration data. All storage forsuccessful ESRS deployment.Receiving test emails.


Customer is satisfied.

61 | Virtualization Tasks - Virtualization Resource and First ResponderDELL EMC CONFIDENTIAL





Compute Tasks - Compute Resource and FirstResponder

This chapter describes how the remote Compute resource, working with the First Responders, configuresand administers all Cisco UCS components.

Before you begin reviewing the Compute procedures, make sure:






• The Storage resource, working with the First Responders, has enabled the boot LUNs and DataLUNs as described in Storage tasks - Storage Resource and First Responders (see page 57).

• The Virtualization resource, working with the First Responders, configures and administers all VMguest servers, ESXi hosts, and VCE Vision as described in Virtualization - Virtualization Resourceand First Responder (see page 60).

Compute Tasks - Compute Resource and First Responder | 62DELL EMC CONFIDENTIAL


Compute Engineer

Compute engineers require implementation and troubleshooting skills in Cisco UCS and VCE Vision, andan understanding of VMware infrastructure, included but not limited to the following topics:

• Cisco rack mount servers

• Blade servers

Task overview for the Compute engineer

Working with the First Responders, the Compute engineer configures and administers all VM guestservers, ESXi hosts, VCE Vision, and Cisco UCS.

Configuring the customer compute infrastructure

Prerequisites

• Networking configured with customer uplinks

• Power to the VCE System storage

Vblock 100 and 200 series do not include a Cisco UCS, and all hosts are managedindividually.


1. Connect to AMP servers via theCIMC through an Internet browser. Http://10.xx.xx.xx

Access to KVM console

2. Verify the ESXi on AMP host isbooted up and has connectivity tothe network.

Ping ESXi host Ping ESXi host successfully

3. Ensure there are no errors andconfirm with the team that thesystem is health.

-- --

4. Run Deployment Checklist Review the Deployment Checklist Complete all tasks in DeploymentChecklist

5. Run x series Test plan Review the VCE x00 Series TestPlan document

--

6. Run CRG Review the VCE Underground VCEConfiguration Reference Guide(CRG) scripts

XML files that contain deviceconfiguration data. All storage forsuccessful ESRS deployment.Receiving test emails.


Customer is satisfied.

63 | Compute EngineerDELL EMC CONFIDENTIAL





CRG - D&I teamThis chapter describes how the remote resources, working with the First Responders, successfully runthe CRG.

Before you begin

Before you begin reviewing the CRG procedures, make sure:






• The Storage resource, working with the First Responders, has enabled the boot LUNs and DataLUNs as described in Storage - Storage Resource and First Responders (see page 57).

• The Virtualization resource, working with the First Responders, configures and administers all VMguest servers, ESXi hosts, VCE Vision, and Cisco UCS as described in Virtualization -Virtualization Resource and First Responder (see page 60)

• The Compute resource, working with the First Responders, configures and administers all CiscoUCS components as described in Compute tasks - Compute Resource and First Responders(see page 62).

CRG - D&I team | 64DELL EMC CONFIDENTIAL


Procedure

Any team member can run the prepared CRG script referenced in Obtaining D&I requirements andcustomer deliverables - D&I team (see page 11). Instructions are included in the CRG package.

65 | CRG - D&I teamDELL EMC CONFIDENTIAL


D&I Closure - Network, Storage, Compute, andVirtualization resourcesThis chapter describes how the remote resources, working with the First Responders, hand off to thecustomer the VCE System "As-Built."

Before you begin

Before you begin reviewing the Knowledge Transfer (KT) procedures, make sure:






• The Storage resource, working with the First Responders, has enabled the boot LUNs and DataLUNs as described in Storage - Storage Resource and First Responders (see page 57).

• The Virtualization resource, working with the First Responders, configures and administers all VMguest servers, ESXi hosts, and VCE Vision as described in Virtualization - Virtualization Resourceand First Responder (see page 60).

• The Compute resource, working with the First Responders, configures and administers all CiscoUCS components as described in Compute tasks - Compute Resource and First Responders(see page 62).

• The remote resources, working with the First Responders, have successfully run the CRG, asdescribed in CRG (see page 64).

Handoff to Customer

To successfully close the D&I, the following must be completed:

• Deployment Audit Checklist fully populated

• Compare VCE Vblock configuration against LCS, record changes

• Ensure there are no errors in any Vblock component

• Complete Test Plan, obtain signature

• Take Backups of all components and save them on the Element Manager's D Drive

D&I Closure - Network, Storage, Compute, and Virtualization resources | 66DELL EMC CONFIDENTIAL


• Finalize As-Built Document Package as referenced in System-specific references (see page 8)

• Finalize Credentials spreadsheet

• Remove temp files from/tidy up Element Manager if appropriate

• Upload necessary documentation to the Z Drive, including DAC for PM.

Knowledge Transfer presentations from:

Begin the presentation with a demonstration of the As-Built package, explaining all of the content. Followthis with presentations by all resources. KT slide decks can be found as referenced in System-specificreferences (see page 8).

• VM

• Compute

• Storage

• Networks

67 | D&I Closure - Network, Storage, Compute, and Virtualization resourcesDELL EMC CONFIDENTIAL


Appendix: Tasks performed at customer sites -First Responders

Appendix: FI Install and cable

Planning

This task is not typically performed alone, and usually in addition to a new chassis or 2 or 4. Get the fullscope of the work, such as:

• Which model of FI ?

• What type of cables ?

• Have the cables been ordered? Are they the proper length?

• Get the elevation and port map guide from the Varch or PM. You need to know where it is beinginstalled, and where the cables are going.

Requirements

• Screwdrivers: Philips head # 2 and flathead screwdriver

• Velcro

• FR field physical installation guide

• VCE Physical Build Guide

Execution Tasks

This task is essentially the same as installing any other rack. However, keep in mind the VCE Systemyou're attaching it to is most likely live. You cannot unplug and plug things in to move cables around andmake it look better.

Make the cabling look as good as you can while being consistent with the rest of the racks.

If you are allowed to, go back though the other racks and add Velcro to them to make it look better aswell. Be careful of loose cables though, and be gentle.

Appendix: Re-Rack service

Planning

This task always takes more time than expected. Please plan accordingly. This task is a sizeable amountof work, especially when it is upwards of three racks.

Appendix: Tasks performed at customer sites - First Responders | 68DELL EMC CONFIDENTIAL


Before un-racking, TAKE A LOT OF PICTURES. The racking should go back together better than itlooked the first time.

Because it will take a lot of time, check what hours you're allowed to work in the Data Center. Expectsome long days.

Requirements

• Full tool kit

• Lots of time

• Elevation diagrams w/serial numbers (makes it easy to verify order)

Execution Tasks

1 Take a picture of everything!

2 Un-cable everything, try to keep it separated per device, so that it's easier to put It back together

3 Either move the VCE rack to be unloaded next to the target rack, or get a cart of some sort tostart moving equipment onto while unracking. Remove a device, then its corresponding rail(s).Try to do one device at a time, so that you can keep them all at the proper Rack Unit (RU) level.

4 Once everything is in the new rack, verify with your pictures to make sure everything is in the rightplace.

5 Cable it up. Make it look better than before.

6 Repeat until out of racks.

Appendix: Blade mezzanine replacement

Planning

• What access do you have?

• Do you have the tracking numbers - to verify that the replacement parts are on site.

• What is the "change window?"

Requirements

• Phillips #2 and smaller (1/8th?) flathead

• ESD wrist strap

• Change management window? Depends on customer and work environment.

Procedure

1 Make sure blade is in maintenance mode. Have the indicator light on to guarantee you're lookingat the right blade.

69 | Appendix: Tasks performed at customer sites - First RespondersDELL EMC CONFIDENTIAL


2 Pull out the blade and open the cover.

3 When removing and installing the cards, make sure not to touch the circuit boards themselves.Only grab the cards from the edges.

4 Unscrew and pull out the old card.

5 Install and screw in the new card.

6 Replace cover and put the blade back in.

7 Contact logical and see if it comes up right.

Appendix: Line-Card install

Planning

This task is usually not done separately…it is typically associated with other equipment upgrades.

Live equipment - change window.

Requirements

• Phillips 2

• Static strap

Planning

Usually not done alone…typically associated with other equipment upgrades

Live equipment - change window

Requirements

• Phillips 2

• Static strap

Procedure

1 Remove the blanking panel.

2 Install the new card -- watch out to make sure it lines up with the chassis slots -- do not force it in.

Appendix: Tasks performed at customer sites - First Responders | 70DELL EMC CONFIDENTIAL


The information in this publication is provided "as is." Dell Inc. makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitnessfor a particular purpose.

Use, copying, and distribution of any software described in this publication requires an applicable software license.

Copyright © 2016 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks ofDell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA inRevision 1.0.

Dell EMC believes the information in this document is accurate as of its publication date. The information is subject tochange without notice.

71 | CopyrightDELL EMC CONFIDENTIAL


vce systems deploy and implement guide · 2020-06-21 · vce™ systems deploy and implement guide...

Documents