Dell EMC Converged Systems Powering on and Off Guide

Dell EMC Converged Systems Powering On and Off Guide

June 2021 Rev. 1.49 Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2011 -2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents

Revision history...... 4

Chapter 1: Introduction...... 7

Chapter 2: Power on...... 8 Power on a VxBlock System 1000...... 8 Power on VxBlock and Vblock Systems 740...... 11 Power on VxBlock and Vblock System 540...... 13 Power on VxBlock and Vblock System 300 series...... 15 Power on a VxBlock System 240 and Vblock System 240...... 17 Power on Converged Technology Extensions...... 19 Power on Isilon or PowerScale storage on the VxBlock System 1000 or Converged Technology Extension ...... 21

Chapter 3: Power off...... 23 Power off a VxBlock System 1000...... 23 Power off VxBlock and Vblock Systems 740...... 25 Power off VxBlock and Vblock System 540...... 28 Power off VxBlock and Vblock System 300 series...... 30 Power off a VxBlock System 240 and Vblock System 240...... 33 Power off Converged Technology Extensions...... 34 Power off Isilon or PowerScale storage in a VxBlock System 1000 or Converged Technology Extension ...... 36

Chapter 4: Powering on and off Integrated Data Protection ...... 37 Power on and off Integrated Data Protection with Avamar...... 37 Generate Avamar server shutdown documentation...... 37 Avamar server shut down procedure...... 38 Power on and off Integrated Data Protection with NetWorker...... 38 Power on and off Integrated Data Protection with Data Domain...... 38 Power on and off Integrated Data Protection with VPLEX ...... 40 Power on and off Integrated Data Protection with metro node...... 40 Power on and off Integrated Data Protection with RecoverPoint...... 40 Power on and off Integrated Data Protection with Cyber Recovery...... 41

Chapter 5: References...... 42

Contents 3 Revision history

Date Document Description of changes revision

June 2021 1.49 Updated to support PowerScale storage arrays on the VxBlock System 1000. Added Cyber Recovery power on/off steps.

March 2021 1.48 Updated for the following: ● VMware Cloud Foundation ● Integrated Data Protection support for metro node January 2021 1.47 Added information about VMware vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 (KB article 80472). January 2021 1.46 Removed content about the Vblock System 720, Vblock System 100, and Vblock Specialized Systems for Extreme Applications. November 2020 1.45 Updated power on and off for Vxblock System 1000 with VMware vSphere 7.0 and VMware vSAN. September 2020 1.44 Removed content for Dell EMC PowerProtect X400 appliance. July 2020 1.43 Added support for Dell EMC PowerStore T models. June 2020 1.42 Updated for Dell EMC PowerProtect X400 May 2020 1.41 Added support for VMware NSX-T Data Center 2.5. April 2020 1.40 Updated to add missing information for Isilon (new nodes and back-end switches). February 2020 1.39 Added support for Isilon (new nodes and back-end switches). December 2019 1.38 Added support for AMP Central. September 2019 1.37 Added support for Dell EMC Unity XT storage.

March 2019 1.36 Added support for AMP-VX with VxBlock Central Orchestration and VMware vSphere 6.7. Updated support for Data Domain.

January 2019 1.35 Removed references to powering on and off VxFlex integrated rack. See the Dell EMC VxRack FLEX Administration Guide. December 2018 1.34 Added VxBlock Central VMs to power on and off for VxBlock Systems.

October 2018 1.33 Added powering on and powering off instructions for VxBlock System 1000 with NSX. Removed instructions for VxRack System SDDC.

August 2018 1.32 Added information about the PowerMax Storage Technology Extension for VxBlock System 1000. Added information about PowerMax storage for VxBlock System 1000. Added AMP-3S to VxBlock Systems. Added information about VxFlex Manager.

April 2018 1.31 Added support for VxRack FLEX system 14 G servers. Added support for XtremIO X2 storage.

March 2018 1.30 Updated Powering off the VMware vSAN 6.x cluster procedure.

February 2018 1.29 Added support for AMP-VX. Added support for VxBlock System 1000.

4 Revision history Date Document Description of changes revision

Removed references to Vblock Specialized System for SAP HANA, which reached end of service life.

October 2017 1.28 Powering on Converged Systems - added support for VMware vSphere 6.5. September 2017 1.27 Update power on/off procedures for VxRack System SDDC VMware Cloud Foundation version 2.1.3. Added power on/off procedures for VxRack System SDDC VMware Cloud Foundation version 2.2. September 2017 1.26 Updated links to power on/off procedures for VMAX3 and VMAX All-Flash storage. Updated VxFlex integrated rack power on procedure.

March 2017 1.25 ● Updated VxFlex integrated rack powering off procedure ● Added VxRack System SDDC powering on and off procedures

October 2016 1.24 Updated powering on and off procedures for Vblock System 350 with Dell EMC Unity.

October 2016 1.23 ● Updated VxFlex integrated rack procedures to support ScaleIO 2.0 software ● Updated VxRack System product name ● Updated VxRack System management software information

July 2016 1.22 Added powering on and off procedures for: ● VxFlex integrated rack ● Integrated Data Protection with NetWorker Updated powering on and off procedures for: ● Integrated Data Protection with Avamar ● Integrated Data Protection with Data Domain

April 2016 1.21 Updated power on and powering off instructions to support the VxBlock System 240.

January 2016 1.19 Removed references to products that have reached end of sale: ● Vblock 0 ● Vblock 1 ● Vblock 1U

October 2015 1.18 Updated the power on and power off instructions to add Cisco Nexus 1000V Virtual Supervisor Module Virtual Machine and Cisco Virtual Switch Update Manager Virtual Machine. Updated information about Power Distribution Units (PDUs) to reflect the Intelligent Physical Infrastructure (IPI) components.

August 2015 1.17 Updated to include Converged Systems, Converged Technology Extension for Cisco UCS compute, Converged Technology Extension for VNX storage, VMware vSphere 6.0, and VMware NSX.

February 2015 1.16 Added new sections for Converged Technology Extension for Isilon storage and Integrated Data Protection. Updated with information about Vblock System 540 and Vblock System 740.

December 2014 1.15 Updated with information about AMP-2HA Performance (VNXe3200 storage) for the Vblock System 340.

May 2014 1.14 Updated with information about: ● Customer-provided services. ● New VM names. ● Timing considerations during the power up cycle.

February 2014 1.13 Updated with information for Vblock Specialized Systems for Extreme Applications.

Revision history 5 Date Document Description of changes revision

November 2013 1.12 Updated with information related to VMware vSphere Standard Edition (version 5.1 and later).

October 2013 1.11 Removed information about powering on and powering off Integrated Data Protection. Added a pointer to the Integrated Data Protection Guide.

September 2013 1.10 Updated links to documentation for CLARiiON CX4-480, VMAX 40K Series, VMAX 20K Series, and VMAX 10K Series.

August 2013 1.9 Added missing information about powering off Cisco Nexus switches.

April 2013 1.8 Added RecoverPoint information.

March 2013 1.7 ● Added Vblock System 200 information. ● Updated for Converged System rebranding.

October 2012 1.6 ● Updated links from PowerLink to Support. ● First Customer Ship for Vblock System 700.

July 2012 1.5 ● Added Integrated Data Protection information. ● Updated for VMAX and Converged System branding.

March 2012 1.4 General Availability release.

February 2012 1.3 First Customer Ship for Vblock System 700 model LX.

December 2011 1.2 First Customer Ship for Vblock System 100.

September 2011 1.1 Added links to storage procedures for all Converged Systems.

September 2011 1.0 Initial release.

6 Revision history 1 Introduction

The term Converged Systems includes both VxBlock System and Vblock System. This document assumes that the person who is powering on or powering off the Converged System has the following: ● Familiarization with Converged System concepts and terminology ● Converged System troubleshooting skills See the Glossary for terms, definitions, and acronyms.

Introduction 7 2 Power on

Power on a VxBlock System 1000

Power on each component in the order specified to safely power on a VxBlock System 1000.

Prerequisites Verify that all components are properly installed and cabled. See appropriate hardware documentation for information about LED indicators. Verify that services and physical infrastructure are available before powering on VxBlock 1000. WARNING: If smoke or fire is detected, power must be removed immediately, and appropriate personnel must be notified.

About this task Some components in the power procedure may not be applicable for your system. The Dell EMC VxBlock System 1000 and PowerFlex Rack Physical Planning Guide contains information about power specifications.

Steps 1. Verify that the PDU breakers are OPEN (or OFF). If the breakers are not OPEN, use a small screwdriver or other flat-edged object to power off the circuit breakers. The following figure shows the switches, which are located below the ON and OFF breakers:

2. Connect external AC feeds to the PDUs. 3. Verify that the PDUs have power and a number displays on each PDU LED. 4. To close the PDU circuit breakers in Zone A, perform the following: a. Press the side of the ON switch. b. Verify that all components connected to the Zone A PDUs are lit. 5. To close the PDU circuit breakers in Zone B, perform the following: a. Press the side of the ON switch. b. Verify that all components connected to the Zone B PDUs are lit. 6. Power on the network components in the following order: NOTE: Network components may not have a power button. Network components are on when PDU circuit breakers are closed and the power cables are plugged in.

● Management switches: Wait until the PS1 and PS2 LEDs are solid green.

8 Power on ● Cisco Nexus switches: Wait until the system status LED is green. ● Cisco SAN switches: Wait until the system status LED is green. NOTE: Network components may take up to 10 minutes to power on.

7. If your AMP contains Dell EMC Unity or Dell EMC Unity XT, see Dell EMC Unity Operations for power management information. 8. Power on the storage components using the following table: NOTE: Storage systems can be powered on in any order.

Storage system Procedure Isilon or PowerScale Power on Isilon or PowerScale storage on the VxBlock System 1000 or Converged Technology Extension Dell EMC Unity or Dell EMC Dell EMC Unity Operations Unity XT storage XtremIO X2 XtremIO 6.0 Storage Array User Guide VMAX All Flash VMAX All Flash PowerMax Contact Dell Technologies Support. PowerStore T models Dell EMC PowerStore Power Down and Reboot Procedures Guide

9. Power on the network components in the following order: NOTE: Network components may not have a power button. Network components are on when PDU circuit breakers are closed and the power cables are plugged in.

● FIs: Wait until the system status LED is green. ● Cisco UCS blade server chassis (top and bottom): Wait until the chassis health LED is green. ● Blade servers: Wait until the power LED is green. 10. Power on AMP hosts using power button on the front of the server. 11. For AMPs that contain VMware vSAN, go to VMware Docs and perform one of the following: ● Shutting down the Virtual SAN Cluster (VMware vSphere 6.5) ● Shutting Down and Restarting the vSAN Cluster (VMware vSphere 6.7) ● Shutting Down and Restarting the vSAN Cluster (VMware vSphere 7.0) 12. To remove AMP VMware vSphere ESXi hosts from maintenance mode using the VMware Host Client or the CLI, enter:

esxcli system maintenanceMode set -e false

13. From the VMware vSphere Web Client, power on each VM in the following order: NOTE: Each VM must fully power on before you continue to the next.

● VMware Host Client: AMP VMware Platform Services Controller 2 ● VMware Host Client: AMP VMware Platform Services Controller 1 ● VMware Host Client: AMP VMware vCenter NOTE: Verify that the VMware DRS level is set to automatic on the Management cluster. If the cluster has retreat mode configured, disable retreat mode using the steps in the KB article vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 (80472). ● VMware SDDC Manager ● Management Domain NSX-T Manager 1 ● Management Domain NSX-T Manager 2 ● Management Domain NSX-T Manager 3 ● Management Domain NSX-T Edge Node 1 ● Management Domain NSX-T Edge Node 2 ● VMware vRealize Log Insight Node 1 ● VMware vRealize Log Insight Node 2

Power on 9 ● VMware vRealize Log Insight Node 3 ● VMware vRealize Suite Lifecycle Manager ● VMware vRealize Operations Cluster ● VMware vRealize Orchestration Cluster ● Element Managers ● Secure Remote Services 2 ● Secure Remote Services 1 ● VxBlock 1000 VMware Platform Services Controller n ● VxBlock 1000 VMware Platform Services Controller 2 ● VxBlock 1000 VMware Platform Services Controller 1 ● VxBlock 1000 Workload VMware vCenters with HA - Witness Node ● VxBlock 1000 Workload VMware vCenters with HA - Active Node ● VxBlock 1000 Workload VMware vCenters with HA - Passive Node ● VxBlock 1000 Workload VMware vCenters ● VxBlock Central Core ● VxBlock Central MSM ● VxBlock Central MSP ● VxBlock Central Orchestration Services ● Workload VMware NSX-T Data Center Manager 1 ● Workload VMware NSX-T Data Center Manager 2 ● Workload VMware NSX-T Data Center Manager 3 ● VMware NSX for vSphere Manager ● Ecosystem VMs ● Optional VMs 14. Exit maintenance mode for all VxBlock 1000 VMware vSphere ESXi hosts. 15. For applicable VxBlock 1000 workload and edge hosts, power on virtualized infrastructure components in the following order: NOTE: Each VM must fully power on before you continue to the next.

● VMware NSX-T Data Center Edge Node virtual machines ● VMware NSX for vSphere Controller 3 ● VMware NSX for vSphere Controller 2 ● VMware NSX for vSphere Controller 1 ● VMware NSX for vSphere Load Balancers ● VMware NSX for vSphere Edge Services Gateway ● VMware NSX for vSphere Universal Distributed Logical Routers ● VMware NSX for vSphere Distributed Logical Routers ● All Customer Workloads

16. Power on the remaining virtualized infrastructure components in the following order: ● Managed platforms ● Data Domain Virtual Edition Evaluation ● Avamar Virtual Edition Evaluation ● Avamar Virtual Edition Proxy ● Avamar Virtual Edition For Integrated Data Protection, see the section Powering on and off Integrated Data Protection.

Next steps For additional information on how to power on VMware Cloud Foundation, go to VMware Docs and see the VMware Validated Design Shutdown and Startup.

Related information Powering Integrated Data Protection on and off

10 Power on Power on VxBlock and Vblock Systems 740

To safely power on VxBlock and Vblock Systems 740 including All Flash, power on each component in the order specified.

Prerequisites Before powering on the Converged System, verify proper installation of cabled components. Refer to Cisco documentation for information about the LED indicators. Services such as AD, DNS, NTP, as well as physical infrastructure such as reliable power, adequate cooling, and core network access must be available prior to proceeding with any Converged System power on activity. WARNING: For each component powered on, if smoke or fire is present, immediately power off the component and notify appropriate personnel.

Steps 1. Verify the PDU breakers are in the OPEN (or OFF) positions. If the breakers are not OPEN, use the small screwdriver or other flat-edged object to switch off the circuit breakers. The following illustration shows the switches are located below the ON/OFF breakers:

2. Connect the external AC feeds to the PDUs. 3. Verify PDUs have power and a number appears on each of the PDU LEDs. 4. Press the side of the switch labeled ON to close the PDU circuit breakers on all PDUs for Zone A. This causes the switch to lie flat. Verify components connected to the PDUs on Zone A are lit. 5. Press the side of the switch labeled ON to close the PDU circuit breakers on all PDUs for Zone B. This causes the switch to lie flat. Verify components connected to the PDUs on Zone B are lit. 6. Power on the network components in the following order: a. Management router: Wait until the main power indicator LED changes from blinking green to solid green to proceed. b. Management switches: Wait until the PS1 and PS2 LEDs are solid green to proceed. c. Cisco Nexus switches: Wait until the system status LED is green to proceed. d. Cisco SAN switches: Wait until the system status LED is green to proceed.

NOTE: Network components take up to 10 minutes to power on.

Power on 11 a. FIs: Wait until the system status LED is green to proceed. b. Cisco UCS chassis (top), Cisco UCS chassis (bottom), and so on: For each chassis that you turn on, wait until the chassis health LED is green to proceed. c. All Cisco UCS blades from the Cisco UCS Manager: For each blade that you turn on, wait until the power LED is green to proceed. 13. If Converged Technology Extension for Cisco UCS compute is used, power it on now. 14. If the AMP VMs are set to start automatically with the system (AMP-2P only), skip this step. To connect the VMware vSphere Client directly to the AMP host, first ensure that DNS and NTP services are available and properly configured. Then ensure that the database servers are configured to start at least two minutes before the VMware vSphere Update Manager servers and VMware vCenter servers. Power on the components as follows: a. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. b. Element Managers c. Primary VMware PSC (VMware vSphere 6.0 or later) d. Secondary VMware PSC, if applicable (VMware vSphere 6.0 or later) e. VMware vCSA (if applicable) f. Core g. MSM h. MSP i. VMware NSX Managers (primary first, then secondaries, if any) (optional component) (applies to NSX-T and NSX-V) j. VMware NSX Controllers 1 through 3 (optional components if VMware NSX Manager is deployed) (applies to NSX-V only) k. VxBlock Central Orchestration Services (optional) l. VMware vRO (optional) m. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) n. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding o. VMware SSO servers (if applicable) p. VMware vCenter Server VM q. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) r. Cisco Virtual Switch Update Manager VM (VSUM, optional component, VMware vSphere 5.x only) s. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) t. Any other management VMs Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence. 15. For VMware vSphere 6.x embedded deployment, VMware vCSA should be turned on before other management VMs. VMware PSC and VUM services are integrated within the VMware vCSA. Power on the following components for Converged Systems running VMware vSphere 6.5 or 6.7: a. Cisco UCS C2x0 servers (Wait about 10 minutes for the power status LED to turn solid green before proceeding.) b. VMware PSC (Primary) c. VMware PSC (Secondary) d. VMware vCSA NOTE: Verify that the VMware DRS level is set to automatic on the Management cluster. If the cluster has retreat mode configured, disable retreat mode using the steps in the KB article vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 (80472).

12 Power on c. VMware NSX Edge virtual machines with the suffix -prod 18. For the Converged System (production) virtualized infrastructure: a. Log in to the production VMware vCenter Server and confirm that all VMware ESXi hosts have started. b. Power on any VMs that are not set to start automatically with the system. 19. If a VNX Gateway is used, see the VNX Systems Operations Guide to turn on the gateway. 20. If Integrated Data Protection is used, see the section Powering on and off Integrated Data Protection.

Related information Powering Integrated Data Protection on and off Power on VxBlock and Vblock System 540

To safely turn on a VxBlock and Vblock Systems 540, turn on each component in the order specified.

Power on 13 NOTE: Network components take up to 10 minutes to power on.

7. If HA-AMP is used, refer to the VNXe (31xx/33xx) documentation to power on the VNXe. 8. If AMP-2HA or AMP-2S is used, refer to the VNXe32xx documentation to power on the VNXe32xx. 9. If AMP-3S or AMP Central is used, see Dell EMC Unity Operations for power management on the Dell EMC Unity 300 storage array. 10. Power on the storage components using XtremIO storage array. 11. If a Converged Technology Extension for Isilon storage system or a Converged Technology Extension for VNX storage is used, power it on now. 12. Power on the Cisco UCS components as follows: a. FIs: Wait until the system status LED is green to proceed. b. Cisco UCS chassis (top), Cisco UCS chassis (bottom), and so on: For each chassis that you turn on, wait until the chassis health LED is green to proceed. c. All Cisco UCS blades from the Cisco UCS Manager: For each blade that you turn on, wait until the power LED is green to proceed. 13. If Converged Technology Extension for Cisco UCS compute is used, power it on now. 14. If the AMP VMs are set to start automatically with the system (AMP-2P only), skip this step. To connect the VMware vSphere Client directly to the AMP host, first ensure that DNS and NTP services are available and properly configured. Then ensure that the database servers are configured to start at least two minutes before the VMware vSphere Update Manager servers and VMware vCenter servers. Power on the components as follows: a. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. b. Element Managers c. Primary VMware PSC (vSphere 6.0 or later) d. Secondary VMware PSC, if applicable (VMware vSphere 6.0 or later) e. VMware vCSA (if applicable) f. Core VM g. MSM VM h. MSP VM i. VMware NSX Managers (primary first, then secondaries, if any) (optional component) (applies to NSX-T and NSX-V) j. VMware NSX Controllers 1 through 3 (optional components if VMware NSX Manager is deployed) (applies to NSX-V only) k. VxBlock Central Orchestration Services (optional) l. VxBlock Central VMware vRO (optional) m. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) n. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding o. VMware SSO servers (if applicable) p. VMware vCenter Server VM q. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) r. Cisco Virtual Switch Update Manager VM (VSUM, optional component, vSphere 5.x only) s. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) t. Any other management VMs Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence. 15. For VMware vSphere 6.x embedded deployment, VMware vCSA turn on management VMs as VMware PSC and VUM services are integrated within the appliance. If running VMware vSphere 6.x turn on the following: a. Cisco UCS C2x0 servers (Wait about 10 minutes for the power status LED to turn solid green before proceeding.) b. VMware PSC (Primary) c. VMware PSC (Secondary) d. VMware vCSA NOTE: Verify that the VMware DRS level is set to automatic on the Management cluster. If the cluster has retreat mode configured, disable retreat mode using the steps in the KB article vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 (80472). e. Any other management VMs f. Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence.

14 Power on 16. NSX-V only: For the NSX Edge Cluster (optional cluster if VMware NSX manager is deployed), turn on the components in the following order: a. VMware NSX Distributed-Router-1 (local and/or universal) (optional component) b. VMware NSX Distributed-Router-0 (local and/or universal) (optional component) c. VMware NSX Edge Services Gateways 01-08 (optional components) 17. NSX-T only: For the NSX Edge Cluster (optional cluster if VMware manager is deployed), turn on the components in the following order: a. VMware NSX Edge ESXi hosts b. VMware NSX Edge virtual machines with the suffix -peer c. VMware NSX Edge virtual machines with the suffix -prod 18. For the Converged System (production) virtualized infrastructure: a. Log in to the production VMware vCenter Server and confirm that all VMware ESXi hosts have started. b. Power on any VMs that are not set to start automatically with the system. 19. If the Converged System contains a VNX Gateway, see the VNX Systems Operations Guide to turn on the gateway. 20. If Integrated Data Protection is used, see the section Powering on and off Integrated Data Protection.

Related information Powering Integrated Data Protection on and off Power on VxBlock and Vblock System 300 series

To safely turn on a VxBlock and Vblock Systems 340 or VxBlock and Vblock Systems 350, power on each component in the order specified.

2. Connect the external AC feeds to the PDUs. 3. Verify PDUs have power and a number appears on each of the PDU LEDs.

Power on 15 4. Press the side of the switch labeled ON to close the PDU circuit breakers on all PDUs for Zone A. This causes the switch to lie flat. Verify components connected to the PDUs on Zone A are lit. 5. Press the side of the switch labeled ON to close the PDU circuit breakers on all PDUs for Zone B. This causes the switch to lie flat. Verify components connected to the PDUs on Zone B are lit. 6. Power on the network components in the following order: a. Management router: Wait until the main power indicator LED changes from blinking green to solid green to proceed. b. Management switches: Wait until the PS1 and PS2 LEDs are solid green to proceed. c. Cisco Nexus switches: Wait until the system status LED is green to proceed. d. Cisco SAN switches: Wait until the system status LED is green to proceed.

NOTE: Network components take up to 10 minutes to power on.

Converged System Procedure

VxBlock and Vblock Systems 300 series VNX System Operations

VxBlock and Vblock Systems 350 Dell EMC Unity Operations

11. If a Converged Technology Extension for Isilon storage system or a Converged Technology Extension for VNX storage is used, power it on now. 12. Power on the Cisco UCS components as follows: a. FIs: Wait until the system status LED is green to proceed. b. Cisco UCS chassis (top), Cisco UCS chassis (bottom), and so on: For each chassis that you turn on, wait until the chassis health LED is green to proceed. c. All Cisco UCS blades from the Cisco UCS Manager: For each blade that you turn on, wait until the power LED is green to proceed. 13. If Converged Technology Extension for Cisco UCS compute is used, power it on now. 14. If the AMP VMs are set to start automatically with the system (AMP-2P only), skip this step. To connect the VMware vSphere Client directly to the AMP host, first ensure that DNS and NTP services are available and properly configured. Then ensure that the database servers are configured to start at least two minutes before the VMware vSphere Update Manager servers and VMware vCenter servers. Power on the components as follows: a. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. b. Element Managers c. Primary VMware PSC (VMware vSphere 6.0 or later) d. Secondary VMware PSC, if applicable (vSphere 6.0 or later) e. VMware vCSA (if applicable) f. Core VM g. MSM VM h. MSP VM i. VMware NSX Managers (primary first, then secondaries, if any) (optional component) (applies to NSX-T and NSX-V) j. VMware NSX Controllers 1 through 3 (optional components if VMware NSX Manager is deployed) (applies to NSX-V only) k. VxBlock Central Orchestration Services (optional) l. VMware vRO (optional) m. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) n. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding. o. VMware SSO servers (if applicable) p. VMware vCenter Server VM

16 Power on q. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) r. Cisco Virtual Switch Update Manager VM (VSUM, optional component, VMware vSphere 5.x only) s. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) t. Any other management VMs Verify a delay (minimum of 180 s) between each of the machines during the power-on sequence. 15. For VMware vSphere 6.x embedded deployment, turn on VMware vCSA before other management VMs such as VMware PSC and VUM services are integrated. For VMware vSphere 6.5 or 6.7: a. Cisco UCS C2x0 servers (Wait about 10 minutes for the power status LED to turn solid green before proceeding). b. VMware PSC (Primary) c. VMware PSC (Secondary) d. VMware vCSA NOTE: Verify that the VMware DRS level is set to automatic on the Management cluster. If the cluster has retreat mode configured, disable retreat mode using the steps in the KB article vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 (80472).

e. Any other management VMs f. Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence. 16. NSX-V only: For the NSX Edge Cluster (optional cluster if VMware NSX manager is deployed), turn on the components in the following order: a. VMware NSX Distributed-Router-1 (local and/or universal) (optional component) b. VMware NSX Distributed-Router-0 (local and/or universal) (optional component) c. VMware NSX Edge Services Gateways 01-08 (optional components) 17. NSX-T only: For the NSX Edge Cluster (optional cluster if VMware manager is deployed), turn on the components in the following order: a. VMware NSX Edge ESXi hosts b. VMware NSX Edge virtual machines with the suffix -peer c. VMware NSX Edge virtual machines with the suffix -prod 18. For the Converged System (production) virtualized infrastructure: a. Log in to the production VMware vCenter Server and confirm that all VMware ESXi hosts have started. b. Power on any VMs that are not set to start automatically with the system. 19. If VNX Gateway is used, see the VNX Systems Operations Guide to turn on the gateway. 20. If Integrated Data Protection is used, see the section Powering on and off Integrated Data Protection.

Related information Powering Integrated Data Protection on and off Power on a VxBlock System 240 and Vblock System 240

To safely power on a Converged System, power on one component at a time, in the order specified in this procedure.

Prerequisites Before powering on the Converged System, verify you have properly installed and cabled all Converged System components. Refer to Cisco documentation for information about the LED indicators. Customer-provided services such as Active Directory, DNS, NTP, as well as physical infrastructure such as reliable power, adequate cooling, and core network access must be available prior to proceeding with any Converged System power on activity. WARNING: For each component that is powered on, if smoke or fire is detected, power should be immediately removed and appropriate personnel notified.

Power on 17 Steps 1. Verify the PDU breakers are in the OPEN (or OFF) position. If the breakers are not in the OPEN position, use the small enclosed tool to press the small white tab below each switch for the circuit to open. These switches are located below the ON/OFF breaker. 2. Connect the external AC feeds to the PDUs. 3. Verify power is available to the PDUs and the LEDs on the PDUs display a number. 4. To close the PDU circuit breakers on all PDUs for Zone A, perform the following: a. Press the side of the switch that is labeled ON. This causes the switch to lie flat. b. Verify all of the components connected to the PDUs on Zone A light up. 5. Close the PDU circuit breakers on all PDUs for Zone B. To do this step: a. Press the side of the switch that is labeled ON. This causes the switch to lie flat. b. Verify all of the components connected to the PDUs on Zone B light up. 6. Power on the network components in the following order: a. Management switch - Wait until the PS1 and PS2 LEDs are solid green before proceeding. b. Cisco Nexus aggregation switches—Wait until the system status LED is green before proceeding. NOTE: Network components take about 10 minutes to power on.

7. Power on the storage components. Refer to the VNX5X00 powerup section in the VNX Series Systems Operations Guide. 8. If the Converged System has an attached Converged Technology Extension for Isilon storage system, power it on now. 9. Power on the Converged System (AMP) Cisco UCS C2X0 hosts. The physical AMP has one server, while the virtual AMP has two servers. Wait 10 minutes for the power status LED to turn solid green before proceeding. 10. Skip this step if the AMP VMs are set to start automatically within the system (AMP-2P only). Power on the following components: a. To complete this step, connect the VMware vSphere Client directly to the AMP host, because the AMP VMware vCenter Server is not yet available. Verify DNS and NTP services are available and properly configured. b. Verify the database servers are configured to start at least two minutes before the VMware vCenter servers and the VMware vSphere Update Manager servers. c. VMware VCenter Server Appliance (VCSA) is the default management option for the AMP-2 with M4 servers. Either the VMware vCenter Server Appliance or the VMware vCenter Server VM must be deployed. d. Active Directory/DNS/NTP (if applicable) e. Microsoft SQL Server Database Virtual Machine (vCenter/VUM) (wait two minutes before proceeding) f. VMware Platform Services Controller (Primary) (VMware vSphere 6.0 or later) g. VMware Platform Services Controller (Secondary) (VMware vSphere 6.0 or later) h. VMware Single Sign-on (SSO) Virtual Machine (if applicable) i. VMware vCenter Server Virtual Machine j. VMware vSphere Update Manager Virtual Machine k. Cisco Nexus 1000V Virtual Supervisor Module Virtual Machine (if applicable) l. Any other management VMs 11. To power on the Converged System production hosts, power on all Cisco UCS C2X0 servers from CIMC. 12. For the Converged System (production) virtualized infrastructure: a. Log in to the production VMware vCenter and confirm all VMware ESXi hosts have started. b. Power on any VMs that do not start automatically with the system. 13. If Integrated Data Protection is used, see the section Powering on and off Integrated Data Protection.

Related information Powering Integrated Data Protection on and off

18 Power on Power on Converged Technology Extensions

Power on Converged Technology Extensions for VMAX3, VMAX All Flash, PowerMax, XtremIO, VNX, Dell EMC Unity, or Dell EMC Unity XT components in the order specified.

NOTE: Network components take up to 10 minutes to power on.

Power on 19 Management Array Procedure Dell EMC Unity 300 storage array Dell EMC Unity Operations

10. Power on the storage components using the procedure referenced in the following table:

Converged System Procedure Dell EMC and Dell EMC Unity XT storage Dell EMC Unity power down and power up procedures

PowerMax storage Contact Dell EMC Customer Support.

VMAX and All Flash storage VMAX3 and VMAX All Flash

VNX storage Introduction to the VNX2 Series

XtremIO X1 storage XtremIO Storage Array User Guide

XtremIO X2 storage XtremIO 6.0 Storage Array User Guide

11. If Converged Technology Extension for Isilon storage system or a Converged Technology Extension for VNX storage is used, power it on now. 12. Power on the Cisco UCS components as follows: a. FIs: Wait until the system status LED is green before proceeding. b. Cisco UCS chassis (top), Cisco UCS chassis (bottom), and so on: For each chassis that you turn on, wait until the chassis health LED is green before proceeding. c. All Cisco UCS blades from the Cisco UCS Manager: For each blade that you turn on, wait until the power LED is green before proceeding. 13. If a Converged Technology Extension for Cisco UCS compute is used, power it on now. 14. If the AMP VMs are set to start automatically with the system (AMP-2P only), skip this step. To connect the VMware vSphere Client directly to the AMP host, first ensure that DNS and NTP services are available and properly configured. Then ensure that the database servers are configured to start at least two minutes before the VMware vSphere Update Manager servers and VMware vCenter servers. Power on the components as follows: a. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. b. Element Managers c. Primary VMware PSC (vSphere 6.0 or later) d. Secondary VMware PSC, if applicable (vSphere 6.0 or later) e. VMware vCSA (if applicable) f. Core g. MSM h. MSP i. VxBlock Central Orchestration Services (Optional) j. VMware vRO (optional) k. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) l. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding m. VMware SSO servers (if applicable) n. VMware vCenter Server VM o. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) p. Cisco Virtual Switch Update Manager VM (VSUM, optional component, vSphere 5.x only) q. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) r. NSX-V: ● VMware NSX Managers (primary VM first, then secondaries, if any) (optional component) ● VMware NSX Controllers 1-3 (optional components if VMware NSX Manager is deployed) s. Any other management VMs Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence. 15. If the AMP VMs are set to start automatically with the system (AMP-2P only), skip this step.

20 Power on To connect the VMware vSphere client directly to the AMP host, first ensure that DNS and NTP services are available and properly configured. Then ensure that the database servers are configured to start at least two minutes before the VMware vSphere Update Manager servers and VMware vCenter servers. Power on the components as follows:

a. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. b. VMware vCSA (if applicable) c. VMware vSRA (AMP-2RP only) d. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding. e. VMware PSC (Primary) (vSphere 6.0 or later) f. VMware PSC (Secondary, if applicable) (vSphere 6.0 or later) g. VMware SSO servers (if applicable) h. VMware vCenter Server VM i. VMware vSphere Update Manager VM j. Cisco Virtual Switch Update Manager VM (VSUM, optional component, VMware vSphere 5.x only) k. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) l. NSX-V: ● VMware NSX Managers (primary VM first, then secondaries, if any) (optional component) ● VMware NSX Controllers 1-3 (optional components if VMware NSX Manager is deployed) m. Any other management VMs Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence. 16. Power on the following components for Converged Systems running VMware vSphere 6.x: a. Cisco UCS C2x0 servers (Wait about 10 minutes for the power status LED to turn solid green before proceeding.) b. VMware PSC (Primary) c. VMware PSC (Secondary) d. VMware vCSA e. Any other management VMs f. Verify that there is a delay (minimum of 180 s) between each of the machines during the power-on sequence. 17. For the NSX-V Edge Cluster (optional cluster if VMware NSX manager is deployed): a. VMware NSX Distributed-Router-1 (local and/or universal) (optional component) b. VMware NSX Distributed-Router-0(local and/or universal) (optional component) c. VMware NSX Edge Service Gateways 01-08 (optional components) 18. For the Converged System (production) virtualized infrastructure: a. Log in to the production VMware vCenter Server, and confirm that all VMware ESXi hosts have started. b. Power on any VMs that are not set to start automatically with the system. 19. If a VNX Gateway is used, see the VNX Systems Operations Guide to turn on the gateway. 20. If Integrated Data Protection is used, see Integrated Data Protection for information.

Related information Powering Integrated Data Protection on and off Power on Isilon or PowerScale storage on the VxBlock System 1000 or Converged Technology Extension

Power on the Isilon or PowerScale storage components in the VxBlock System 1000 or Converged Technology Extension. See the relevant procedure to power on the attached Converged System and note the specific step that tells you when to power on the Isilon or PowerScale storage.

Steps 1. Power on the Isilon InfiniBand switches or Ethernet back-end switches in the VxBlock System 1000 or Converged Technology Extension cabinet. 2. Power on the Cisco Nexus switches in the VxBlock System 1000 or Converged Technology Extension cabinet. 3. Using a serial connection, connect to the console port of node 1 with a laptop and a Hyperterminal or similar connection.

Power on 21 4. Power on node 1 first by pressing the power button on the back of the node labeled Node 1. 5. Monitor the status of the boot process for node 1. When node 1 has finished booting, it displays the login prompt. Take note of any error codes or amber lights on the node. Resolve any issues before moving to node 2. 6. Move to node 2, power on, and monitor the boot process. 7. Repeat the procedure for each node in the cluster (in sequential order). When all nodes have completed booting, the system is powered on.

Next steps Return to the steps to power on the rest of the components in the attached Converged System.

22 Power on 3 Power off

Power off a VxBlock System 1000

Power off each component in the order that is specified to safely power off a VxBlock System 1000.

Prerequisites Verify that all startup configurations for Cisco devices have been saved.

Steps 1. Use VMware vCenter to place the VxBlock 1000 workload, edge, and compute hosts and compute VMware vSphere ESXi hosts into maintenance mode. 2. For applicable VxBlock 1000 workload and edge hosts, power off virtualized infrastructure components in the following order: NOTE: Each VM must fully power off before you continue to the next VM.

● All Customer Workloads ● VMware NSX for vSphere Load Balancers ● VMware NSX for vSphere Edge Services Gateway ● VMware NSX for vSphere Universal Distributed Logical Routers ● VMware NSX for vSphere Distributed Logical Routers ● VMware NSX for vSphere Controller 3 ● VMware NSX for vSphere Controller 2 ● VMware NSX for vSphere Controller 1 ● VMware NSX-T Data Center Edge Node virtual machines 3. Power off applicable VxBlock 1000 VMware vSphere ESXi hosts and edge hosts. 4. Power off all Cisco UCS servers from the Cisco UCS Manager. 5. For Integrated Data Protection, see the section Powering on and off Integrated Data Protection. 6. To save Cisco SAN switch configuration changes, enter:

copy running-config startup-config

7. Power off the Cisco SAN switch. 8. Power off the storage components using the following table:

Storage system Procedure Isilon or PowerScale Power off Isilon or PowerScale Storage in a VxBlock System 1000 or Converged Technology Extension Dell EMC Unity and Dell EMC Unity XT Dell EMC Unity Operations XtremIO X2 XtremIO 6.0 Storage Array User Guide VMAX All Flash VMAX All Flash

Power off 23 Storage system Procedure

PowerMax Contact Dell Technologies Support.

PowerStore T models Dell EMC PowerStore Power Down and Reboot Procedures Guide

9. For AMPs that contain VMware vSAN, see the VMware Docs and perform the steps in the respective section: ● Shutting down the Virtual SAN Cluster (VMware vSphere 6.5) ● Shutting Down and Restarting the vSAN Cluster (VMware vSphere 6.7) ● Shutting Down and Restarting the vSAN Cluster (VMware vSphere 7.0) NOTE: To power off the VMs, see steps 11 and 12.

10. Migrate the AMP Management VMware vCenter Server to the first VMware ESXi host of the cluster. 11. Power off virtualized infrastructure components in the following order: ● Managed platforms ● Data Domain Virtual Edition Evaluation ● Avamar Virtual Edition Evaluation ● Avamar Virtual Edition Proxy ● Avamar Virtual Edition For Integrated Data Protection, see the section Powering on and off Integrated Data Protection.

12. From the VMware vSphere Web Client, power off each VM in the following order: NOTE: Each VM must fully power off before you continue to the next.

● Optional VMs ● Ecosystem VMs ● VMware vRealize Operations ● VMware vRealize Orchestration ● VMware vRealize Suite Lifecycle Manager ● VMware vRealize Log Insight 3 ● VMware vRealize Log Insight 2 ● VMware vRealize Log Insight 1 ● VMware NSX for vSphere Manager ● VMware NSX-T Data Center Manager 3 ● VMware NSX-T Data Center Manager 2 ● VMware NSX-T Data Center Manager 1 ● VMware vRealize Operations ● VxBlock Central Orchestration Services ● VxBlock Central MSP ● VxBlock Central MSM ● VxBlock Central Core ● VxBlock 1000 Workload VMware vCenters ● VxBlock 1000 Workload VMware vCenters with HA - Passive Node ● VxBlock 1000 Workload VMware vCenters with HA - Active Node ● VxBlock 1000 Workload VMware vCenters with HA - Witness Node ● VxBlock 1000 VMware Platform Services Controller n ● VxBlock 1000 VMware Platform Services Controller 2 ● VxBlock 1000 VMware Platform Services Controller 1 ● Secure Remote Services 2 ● Secure Remote Services 1 ● Element Managers ● VMware Management NSX-T Edge Node 2 ● VMware Management NSX-T Edge Node 1 ● VMware Management NSX-T Data Center Manager 3 ● VMware Management NSX -T Data Center Manager 2 ● VMware Management NSX -T Data Center Manager 1

24 Power off ● VMware SDDC Manager ● NOTE: In VMware vSphere 7.0 U1, VMware vSphere Cluster Services (vCLS) VMs prevent the hosts from entering maintenance mode. Set the management cluster DRS automation to manual and see the KB article vSphere Cluster Serivces (vCLS) in vSphere 7.0 U1 (80472) to configure retreat mode on the cluster.

VMware Host Client: AMP VMware vCenter ● VMware Host Client: AMP VMware Platform Services Controller 2 ● VMware Host Client: AMP VMware Platform Services Controller 1 13. To place the AMP VMware vSphere ESXi hosts into maintenance mode using the VMware Host Client or CLI, enter:

esxcli system maintenanceMode set -e true -m noAction

14. To power off the AMP VMware vSphere ESXi hosts using the VMware Host Client or the CLI, enter:

poweroff

15. From the front panel of the management console, verify that all hosts are shut down. 16. If your AMP contains Dell EMC Unity or Dell EMC Unity XT, see Dell EMC Unity Operations. 17. Power off the Cisco Nexus switches and management switches. 18. On Zone B, set all PDU power breakers off (OPEN position). 19. On Zone A, set all PDU power breakers off (OPEN position). PDU model QZ1D2Q0BA30P1 does not contain any circuit breakers. To ensure that there is no power beyond the PDUs, disconnect the AC feeds to all PDUs.

Next steps For additional information on how to power on VMware Cloud Foundation, go to VMware Docs and see the VMware Validated Design Shutdown and Startup.

Related information Powering Integrated Data Protection on and off Power off VxBlock and Vblock Systems 740

To safely power off VxBlock and Vblock Systems 740 power off each component in the order specified.

Prerequisites To facilitate powering on the Converged System at a later time, confirm that the management infrastructure VMs are set to start automatically with the system. Also verify that all startup configurations for the Cisco devices are saved.

Steps 1. Shut down the following (production) virtualized infrastructure: a. VMs b. VMware vSphere ESXi hosts Before powering off, use VMware vCenter to put VMware vSphere ESXi in maintenance mode to avoid any IOPs to storage.

2. Power off all Cisco UCS servers from the Cisco UCS Manager. 3. NSX-V only: Shut down the VMware NSX-V Edge (optional component) virtualized infrastructure as follows: a. VMware NSX Distributed-Router-1 (local and/or universal) b. VMware NSX Distributed-Router-0 (local and/or universal) (optional component) c. VMware NSX Edge Service Gateways 01-08 d. VMware Edge Gateway ESXi hosts 4. NSX-T only: Shut down the VMware NSX-T Edge (optional component) virtualized infrastructure in the following order: a. VMware NSX Edge virtual machines with the suffix -prod

Power off 25 b. VMware NSX Edge virtual machines with the suffix -peer c. VMware NSX-T Edge ESXi hosts 5. If a Converged Technology Extension for Cisco UCS is used, power it off now. 6. If Integrated Data Protection is used, see the section Power on and off Integrated Data Protection . 7. If a VNX gateway is used, see the VNX Systems Operations Guide to power off the gateway. 8. To save configuration changes on the Cisco SAN switch, type:

copy running-config startup-config

9. Power off the Cisco SAN switch. 10. If a Converged Technology Extension for VNX storage is used, power it off now. 11. If a Converged Technology Extension for Isilon is used, power it off now. 12. See the VMAX3 and VMAX All Flash documentation to power off storage components. 13. To shut down the AMP-3S or AMP Central virtualized infrastructure, see step 17. For VMware vSphere 6.x embedded deployment, power off the VMware vCSA after management VMs are powered off. Shut down the AMP virtualized infrastructure as follows: a. Any other management VMs b. VMware NSX Controllers 1-3 (optional components if VMware NSX Manager is deployed) c. VMware NSX Managers (secondary VM first, then primary, if any) (optional component) d. Cisco Virtual Switch Update Manager VM (VSUM, optional component, vSphere 5.x only) e. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) f. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) g. VMware vCenter Server VM h. Secondary VMware PSC, if applicable (vSphere 6.0 or later) i. Primary VMware PSC (vSphere 6.0 or later) j. VMware SSO servers (if applicable) k. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding l. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) m. VMware vRO (optional) n. VxBlock Central Orchestration Services (optional) o. Core p. MSM q. MSP r. VMware NSX Edge virtual machines with the suffix -prod s. VMware NSX Edge virtual machines with the suffix -peer t. VMware vCSA (if applicable) u. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. 14. Shut down the AMP virtualized infrastructure as follows for Converged Systems running VMware vSphere 6.x: For VMware vSphere 6.x embedded deployment, the VMware vCSA can be turned off after management VMs are turned off.

a. Any management VMs other than VMware vCenter Server b. VMware PSC (Secondary) c. VMware vCSA d. VMware PSC (Primary) e. Cisco UCS C2x0 servers 15. If HA-AMP is used, see the VNXe (31xx/33xx) documentation to power off the VNXe platform. a. Go to the VNXe Support page. b. In the Search field, type VNXe power cycle. c. See the How to power cycle the VNXe system safely document. d. Power off the remaining AMP components. 16. If AMP-2HA or AMP-2S is used, see the VNXe32xx documentation to power off the VNXe32xx. a. Go to the VNXe3200 online help page. b. Following the instructions to download, extract and launch the online help. c. Click Search, type power, and click Submit. d. Select Power down and power up an AC powered system.

26 Power off e. Follow the instructions for powering off the system. 17. If AMP-3S or AMP Central is used, shut down the virtualized infrastructure as follows: a. Power off all ecosystem and optional management workload VMs except: ● VMware NSX Manager (optional) ● NSX controller (optional) ● VxBlock Central VMware vRO (optional) ● VxBlock Central Orchestration Services (optional) b. Power off all Core VMs except: ● AMP Central VMware vCSA and PSCs ● Production VMware vCSAs and PSCs ● Core, MSM, and MSP c. Power off NSX Controllers and NSX Managers as follows: i. VMware NSX Controllers 3 to 1 in descending order (optional component if VMware NSX Manager is deployed) ii. VMware NSX Managers (secondaries first, then primary) (optional component if VMware NSX Manager is deployed) d. Power off all production VMware vCSAs and PSCs as follows (AMP Central only): i. Secondary production VMware PSCs ii. Primary production VMware PSCs iii. Production VMware vCSAs e. Power off all VxBlock Central VMs as follows: i. VxBlock Central vRO (optional) ii. VxBlock Central Orchestration Services (optional) iii. MSP iv. MSM v. Core f. To power off the VMware vCSA Passive node, VMware vCSA Active node, vCSA, or the vCSA witness node, connect to VMware vSphere ESXi host to which the VM is on. Place all AMP ESXi hosts in maintenance mode before you power off AMP VMware vCSA and PSCs. NOTE: In VMware vSphere 7.0 U1, vSphere Cluster Services (vCLS) VMs prevent the hosts from entering maintenance mode. Set the Management cluster DRS automation to manual and see the KB article vSphere Cluster Serivces (vCLS) in vSphere 7.0 U1 (80472) to configure retreat mode on the cluster.

g. Power off AMP-3S or AMP Central VMware vCSA and PSCs as follows: i. Secondary VMware PSC (optional) ii. Primary VMware PSC (optional) iii. AMP VMware vCSA Passive node - (optional) iv. AMP VMware vCSA Witness node (optional) h. Power off all Cisco UCS C2x0 AMP VMware vSphere ESXi hosts. 18. If AMP-3S or AMP Central is used, see Dell EMC Unity Operations for power management on the array. 19. Power off the Cisco Nexus switches and management switches. 20. On Zone B, switch all PDU power breakers off (OPEN position). 21. On Zone A, switch all PDU power breakers off (OPEN position). PDU model QZ1D2Q0BA30P1 does not contain any circuit breakers. To ensure that there is no power beyond the PDUs, disconnect the AC feeds to all PDUs. The Dell EMC Converged Systems Physical Planning Guide contains information about power specifications.

Related information Powering Integrated Data Protection on and off

Power off 27 Power off VxBlock and Vblock System 540

Power off each component in the order specified.

Steps 1. Shut down the (production) virtualized infrastructure as follows: a. VMs b. VMware vSphere ESXi hosts 2. Power off all Cisco UCS servers from the Cisco UCS Manager. 3. VMware NSX-V only: Shut down the VMware NSX-V Edge (optional component) virtualized infrastructure as follows: a. VMware NSX Distributed-Router-1 (local and/or universal) b. VMware NSX Distributed-Router-0 (local and/or universal) (optional component) c. VMware NSX Edge Service Gateways 01-08 d. VMware Edge Gateway ESXi hosts 4. NSX-T only: Shut down the VMware NSX-T Edge (optional component) virtualized infrastructure in the following order: a. VMware NSX Edge virtual machines with the suffix -prod b. VMware NSX Edge virtual machines with the suffix -peer c. VMware NSX-T Edge ESXi hosts 5. If the Converged Technology Extension for Cisco UCS compute is used, power it off now. 6. If Integrated Data Protection is used, see the section Powering on and off Integrated Data Protection. 7. If a VNX Gateway is used, see the VNX Systems Operations Guide to power off the gateway. 8. To save configuration changes on the Cisco SAN switch, type:

copy running-config startup-config

9. Power off the Cisco SAN switch. 10. If the Converged Technology Extension for VNX storage is used, power it off now. 11. If the Converged Technology Extension for Isilon storage system is used, power it off now. 12. See XtremIO storage array to power off the storage component for VxBlock and Vblock Systems 540. 13. To shut down the AMP-3S or AMP Central virtualized infrastructure, see step 17. For VMware vSphere 6.x embedded deployment, power off the VMware vCSA after management VMs are powered off. Shut down the AMP virtualized infrastructure as follows: a. Any other management VMs b. VMware NSX Controllers 1-3 (optional components if VMware NSX Manager is deployed) c. VMware NSX Managers (secondary VM first, then primary, if any) (optional component) d. Cisco Virtual Switch Update Manager VM (VSUM, optional component, VMware vSphere 5.x only) e. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) f. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) g. VMware vCenter Server VM h. Secondary VMware PSC, if applicable (VMware vSphere 6.0 or later) i. Primary VMware PSC (VMware vSphere 6.0 or later) j. VMware SSO servers (if applicable) k. Microsoft SQL Server Database VM (VMware vCenter/VUM): Wait 2 minutes before proceeding l. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) m. Core n. MSM o. MSP p. VMware NSX Edge virtual machines with the suffix -prod q. VMware NSX Edge virtual machines with the suffix -peer r. VMware vCSA (if applicable)

28 Power off s. Cisco UCS C2x0 servers: Wait 10 minutes for the power status LED to turn solid green before proceeding. 14. For VMware vSphere 6.x embedded deployment, the VMware vCSA can be turned off after management VMs are turned off. If VMware vSphere 6.x is used, shutdown components as follows: a. Any management VMs other than VMware vCenter b. VMware PSC (Secondary) c. VMware vCSA d. VMware PSC (Primary) e. Cisco UCS C2x0 servers 15. If HA-AMP is used, see the VNXe (31xx/33xx) documentation to power off the VNXe platform. a. Go to VNXe Support. b. In the Search field, type VNXe power cycle. c. See the How to power cycle the VNXe system safely document. d. Power off the remaining AMP components. 16. If AMP-2HA or AMP-2S is used, see the VNXe32xx documentation to power off the VNXe32xx. a. Go to VNXe3200 online help. b. Following the instructions to download, extract and launch the online help. c. Click Search, type power, and click Submit. d. Select Power down and power up an AC powered system. e. Follow the instructions for powering off the system. 17. If AMP-3S or AMP Central is used, shut down the virtualized infrastructure as follows: a. Power off all ecosystem and optional management workload VMs except: ● VMware NSX Manager (optional) ● NSX controller (optional) ● VxBlock Central VMware vRO (optional) ● VxBlock Central Orchestration Services (optional) b. Power off all Core VMs except: ● AMP Central VMware vCSA and PSCs ● Production VMware vCSAs and PSCs ● Core, MSM, and MSP c. Power off NSX Controllers and NSX Managers (optional components if VMware NSX Manager is deployed) as follows: i. VMware NSX Controllers 3 to 1 in descending order ii. VMware NSX Managers (secondary first, then primary) d. Power off all production VMware vCSAs and PSCs as follows (AMP Central only): i. Secondary production VMware PSCs ii. Primary production VMware PSCs iii. Production VMware vCSAs e. Power off VxBlock Central VMs as follows: i. VMware vRO (optional) ii. VxBlock Central Orchestration Services (optional) iii. MSP iv. MSM v. Core f. Power off the VMware vCSA Passive node, VMware vCSA Active node, or the VMware vCSA witness node by connecting directly to the VMware vSphere ESXi host to which the VM is on. Place all AMP ESXi hosts in maintenance mode before you power off AMP VMware vCSA and PSCs. NOTE: In VMware vSphere 7.0 U1, vSphere Cluster Services (vCLS) VMs prevent the hosts from entering maintenance mode. Set the Management cluster DRS automation to manual and see the KB article vSphere Cluster Serivces (vCLS) in vSphere 7.0 U1 (80472) to configure retreat mode on the cluster.

g. Power off AMP-3S or AMP Central VMware vCSA and PSCs as follows: i. Secondary VMware PSC (optional) ii. Primary VMware PSC (optional) iii. AMP VMware vCSA Passive node (optional) iv. AMP VMware vCSA Witness node (optional)

Power off 29 h. Power off all Cisco UCS C2x0 AMP VMware ESXi hosts. 18. If AMP-3S or AMP Central is used, see Dell EMC Unity Operations for power management on the array. 19. Power off the Cisco Nexus switches and management switches. 20. On Zone B, switch all PDU power breakers off (OPEN position). 21. On Zone A, switch all PDU power breakers off (OPEN position). PDU model QZ1D2Q0BA30P1 does not contain any circuit breakers. To ensure that there is no power beyond the PDUs, disconnect the AC feeds to all PDUs. The Dell EMC Converged Systems Physical Planning Guide contains information about power specifications.

Related information Powering Integrated Data Protection on and off Power off VxBlock and Vblock System 300 series

To safely power off a VxBlock and Vblock Systems 340 or VxBlock and Vblock Systems 350, power off each component in the order specified.

Steps 1. Shut down the (production) virtualized infrastructure as follows: a. VMs b. VMware vSphere ESXi hosts 2. Power off all Cisco UCS servers from the Cisco UCS Manager. 3. NSX-V only: Shut down the VMware NSX-V Edge (optional component) virtualized infrastructure as follows: a. VMware NSX Distributed-Router-1 (local and/or universal) b. VMware NSX Distributed-Router-0 (local and/or universal) (optional component) c. VMware NSX Edge Service Gateways 01-08 d. VMware Edge Gateway ESXi hosts 4. NSX-T only: Shut down the VMware NSX-T Edge (optional component) virtualized infrastructure in the following order: a. VMware NSX Edge VMs with the suffix -prod b. VMware NSX Edge VMs with the suffix -peer c. VMware NSX-T Edge ESXi hosts 5. If Converged Technology Extension for Cisco UCS compute is attached, power it off now. 6. If Integrated Data Protection is used, see the section Powering on and off Integrated Data Protection. 7. If a VNX Gateway is used, see the VNX Systems Operations Guide to power off the gateway. 8. To save configuration changes on the Cisco SAN switch, type:

copy running-config startup-config

9. Power off the Cisco SAN switch. 10. If Converged Technology Extension for VNX storage is used, power it off now. 11. If the Converged Technology Extension for Isilon storage system is used, power it off now. 12. See the following table to power off storage components:

Storage system on this Converged System Procedure VxBlock and Vblock Systems 300 series VNX System Operations VxBlock System 350 and Vblock System 350 Dell EMC Unity Operations

30 Power off 13. To shut down the AMP-3S or AMP Central virtualized infrastructure, see step 14. For VMware vSphere 6.x embedded deployment, power off the VMware vCSA after management VMs are powered off. Shut down the AMP virtualized infrastructure as follows: a. Any other management VMs b. VMware NSX Controllers 1-3 (optional components if VMware NSX Manager is deployed) c. VMware NSX Managers (secondary VM first, then primary, if any) (optional component) d. Cisco Virtual Switch Update Manager VM (VSUM, optional component, VMware vSphere 5.x only) e. Cisco Nexus 1000V Virtual Supervisor Module VMs (optional component) f. VMware vSphere Update Manager VM (optional, depending on VMware vSphere version) g. VMware vCenter Server VM h. Secondary VMware PSC, if applicable (VMware vSphere 6.0 or later) i. Primary VMware PSC (VMware vSphere 6.0 or later) j. VMware SSO servers (if applicable) k. Microsoft SQL Server Database VM (vCenter/VUM): Wait 2 minutes before proceeding l. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) m. Core VM n. MSM VM o. MSP VM p. VMware NSX Edge VMs with the suffix -prod q. VMware NSX Edge VMs with the suffix -peer r. VMware vCSA (if applicable) 14. If AMP-3S or AMP Central is used, shut down the virtualized infrastructure as follows: a. Power off all ecosystem and optional management workload VMs except: ● VMware NSX Manager (optional) ● NSX controller (optional) ● VMware vRO and VxBlock Central Orchestration Services b. Power off all Core VMs except: ● AMP Central VMware vCSA and PSCs ● Production VMware vCSAs and PSCs ● Core, MSM, and MSP c. Turn off NSX Controllers and NSX Managers (optional components if VMware NSX Manager is deployed) as follows: i. VMware NSX Controllers 3 to 1 in descending order ii. VMware NSX Managers (secondary first, then primary) d. Power off all production VMware vCSAs and PSCs as follows (AMP Central only): i. Secondary production VMware PSCs ii. Primary production VMware PSCs iii. Production VMware vCSAs e. Power off all VxBlock Central VMs as follows: i. VMware vRO (optional) ii. VxBlock Central Orchestration Services (optional) iii. MSP iv. MSM v. Core f. Power off the VMware vCSA Passive node, VMware vCSA Active node, or the VMware vCSA witness node by connecting directly to the VMware vSphere ESXi host to which the VM is on. g. Place all AMP VMware vSphere ESXi hosts in maintenance mode before you power off AMP VMware vCSA and PSCs. NOTE: In VMware vSphere 7.0 U1, vSphere Cluster Services (vCLS) VMs prevent the hosts from entering maintenance mode. Set the Management cluster DRS automation to manual and see the KB article vSphere Cluster Serivces (vCLS) in vSphere 7.0 U1 (80472) to configure retreat mode on the cluster.

h. Power off AMP-3S or AMP Central VMware vCSA and PSCs as follows: i. Secondary VMware PSC (optional) ii. Primary VMware PSC (optional) iii. AMP VMware vCSA Passive node (optional)

Power off 31 iv. AMP VMware vCSA Witness node (optional) i. Power off all Cisco UCS C2x0 AMP VMware vSphere ESXi hosts. 15. If AMP-3S or AMP Central is used, see Dell EMC Unity Operations for power management on the Dell EMC Unity 300 storage array. 16. Power off the Cisco Nexus switches and management switches. 17. On Zone B, switch all PDU power breakers off (OPEN position). 18. On Zone A, switch all PDU power breakers off (OPEN position). PDU model QZ1D2Q0BA30P1 does not contain any circuit breakers. To ensure that there is no power beyond the PDUs, disconnect the AC feeds to all PDUs. The Dell EMC Converged Systems Physical Planning Guide contains information about power specifications.

Related information Powering Integrated Data Protection on and off

32 Power off Power off a VxBlock System 240 and Vblock System 240

To safely power off a Converged System, power off one component at a time, in the specific order that is described in the procedure.

Prerequisites To facilitate powering on the Converged System at a later time, document the location of the management infrastructure VMs on their respective hosts. Also verify that all startup configurations for the Cisco devices are saved.

Steps 1. Shut down the Converged System production hosts in the following order: a. VMs (see below) b. VMware ESXi hosts c. Bare metal hosts d. Cisco UCS C2X0 servers by using CIMC or by pressing the power button. e. If the Converged System contains Integrated Data Protection, see the section Powering on and off Integrated Data Protection. Do one of the following tasks: ● If this is a unified configuration, power off only the DME and control stations and skip the next step. ● If this is a block configuration, go to the next step. 2. Power off all the Cisco C-Series Rack compute servers via the Cisco IMC 3. Connect the VMware vSphere C# Client to the Physical or Logical AMP host directly, not through the VMware vCenter Server or Element Manager. 4. To facilitate powering on the Converged System at a later time, record the ESXi host location for the following virtual machines: ● VMware Single Sign-on (SSO) Virtual Machine (if applicable) ● VMware Platform Services Controller (Primary) (VMware vSphere 6.0 only) ● VMware Platform Services Controller (Secondary) (VMware vSphere 6.0 only) ● Microsoft SQL Server Database Virtual Machine (vCenter/VUM) (optional, only configured if VCSA has not been deployed) ● VMware vCenter Server Virtual Machine ● VMware vSphere Update Manager Virtual Machine ● VMware VCSA Virtual Machine (if applicable) Ensure that there is a delay (minimum of 180 seconds) between each of the machines during the power off sequence. 5. Power off the Converged System AMP hosts as follows: a. Connect to a laptop or to another machine with network IP access to the Converged System. Ensure that the following applications are installed: ● PuTTY ● Unisphere Client ● VMware vSphere C# Client b. Connect the VMware vSphere C# Client directly to the AMP VMware ESXi hosts where the AMP VMs reside using the root account. Do not connect through the AMP VMware vCenter Server or Jump Server. c. Shut down the AMP management VMs in the following order: i. Any management VMs (other than vCenter/VUM/DB) ii. Cisco Nexus 1000V Virtual Supervisor Module VM (if applicable) iii. VMware vSphere Update Manager (VUM) VM iv. VMware vCenter Server VM v. VMware Platform Services Controller (Secondary) (VMware vSphere 6.0 or later) vi. VMware Platform Services Controller (Primary) (VMware vSphere 6.0 or later) vii. VMware Single Sign-on (SSO) VM (if applicable) viii. Microsoft SQL Server Database VM (vCenter/VUM) d. Shut down the AMP Cisco UCS C2X0 servers.

Power off 33 6. Power off the storage components. See Planned powerdown of the VNX in the VNX Series Systems Operations. 7. If the Converged System has an attached Converged Technology Extension for Isilon storage system, power it off now. 8. Power off the Cisco Nexus switches and management switches. Before powering off the switches, to avoid losing any unsaved configuration changes, enter: copy running-config startup-config.

9. On Zone B, turn off all PDU power breakers (OPEN position). 10. On Zone A, turn off all PDU power breakers (OPEN position). To ensure that there is no power beyond the PDUs, disconnect the AC feeds to all PDUs. The physical planning guide for the Converged System contains additional information about power specifications.

Related information Powering Integrated Data Protection on and off Power off Converged Technology Extensions

To safely power off Converged Technology Extensions for VMAX3, VMAX All Flash, PowerMax, XtremIO, VNX, Dell EMC Unity, or Dell EMC Unity XT, power off each component in the order specified.

Steps 1. Shut down the (production) virtualized infrastructure as follows: a. VMs b. VMware vSphere ESXi hosts 2. Power off all Cisco UCS servers from the Cisco UCS Manager (if not previously powered off in Step 1). 3. Shut down the VMware NSX Edge (optional component) virtualized infrastructure as follows: a. VMware NSX Distributed-Router-1 (local and/or universal) b. VMware NSX Distributed-Router-0 (local and/or universal) (optional component) c. VMware NSX Edge Service Gateways 01-08 d. VMware Edge Gateway ESXi hosts 4. If the Converged System has an attached Converged Technology Extension for Cisco UCS compute, power it off now. 5. Connect the VMware vSphere Client or Host to the AMP VMware ESXi host directly, not through the AMP VMware vCenter Server or Element Manager Server. 6. If the Converged System contains Integrated Data Protection, see Integrated Data Protection for information. 7. If the Converged System contains a VNX Gateway, see the VNX Systems Operations Guide to power off the gateway. 8. To save configuration changes on the Cisco SAN switch, type:

copy running-config startup-config Power off the Cisco SAN switch.

9. If the Converged System has an attached Converged Technology Extension for VNX storage, power it off now. 10. If the Converged System has an attached Converged Technology Extension for Isilon storage system, power it off now. 11. See the following table to power off storage components:

Storage system on this Converged System Procedure Dell EMC Unity and Dell EMC Unity XT storage Dell EMC Unity power down and power up procedures

PowerMax storage Contact Dell EMC Customer Support.

34 Power off Storage system on this Converged System Procedure

VMAX and All Flash drive storage VMAX3 and VMAX All Flash

VNX storage Introduction to the VNX2 Series

XtremIO X1 storage XtremIO Storage Array User Guide

XtremIO X2 storage XtremIO 6.0 Storage Array User Guide

12. Shut down the AMP virtualized infrastructure as follows: a. Any management VMs (other than VMware vCenter/VUM/DB/NSX) b. VMware NSX Controllers 3 to 1 in descending order (optional component if VMware NSX Manager is deployed) c. VMware NSX Managers (secondaries first, then primary) (optional component if VMware NSX Manager is deployed) d. Cisco Virtual Switch Update Manager VM (VSUM, optional component, VMware vSphere 5.x only) e. Cisco Nexus 1000V Virtual Supervisor Module VM (optional component) f. VMware vSphere Update Manager (VUM) VM g. VMware vCenter Server VM h. Primary VMware PSC, if applicable (vSphere 6.0 or later) i. Secondary VMware PSC, if applicable (vSphere 6.0 or later) j. VMware SSO VM (if applicable) k. Microsoft SQL Database VM (VMware vCenter/VUM) l. Microsoft SQL Database VM (VMware vCenter/VUM) m. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) n. VMware vRO (optional) o. VxBlock Central Orchestration Services (optional) p. MSP q. MSM r. Core s. VMware vSphere Replication Appliance (vSRA) (AMP-2RP only) t. Cisco UCS C2x0 servers 13. Shut down the AMP virtualized infrastructure as follows for Converged Systems running VMware vSphere 6.5: a. Any management VMs other than VMware vCenter b. VMware PSC (Secondary) c. VMware vCenter Server Appliance (vCSA) d. VMware PSC (Primary) e. Cisco UCS C2x0 servers 14. If HA-AMP is used, see the VNXe (31xx/33xx) documentation to power off the VNXe platform. a. Go to the VNXe Support page. b. In the Search field, type VNXe power cycle. c. See the How to power cycle the VNXe system safely. d. Power off the remaining AMP components. 15. If the Converged System contains an AMP-2HA or AMP-2S, see the VNXe32xx documentation to power off the VNXe32xx. a. Go to the VNXe3200 online help page. b. Follow the instructions to download, extract, and launch the online help. c. Click Search, type power, and click Submit. d. Select Power down and power up an AC powered system. e. Follow the instructions for powering off the system. 16. If AMP-3S is used, see Dell EMC Unity Operations for power management on the management array. 17. Power off the Cisco Nexus switches and management switches. 18. On Zone B, switch all PDU power breakers off (OPEN position). 19. On Zone A, switch all PDU power breakers off (OPEN position). PDU model QZ1D2Q0BA30P1 does not contain any circuit breakers. To ensure that there is no power beyond the PDUs, disconnect the AC feeds to all PDUs. The Dell EMC Converged Systems Physical Planning Guide contains information about power specifications.

Power off 35 Power off Isilon or PowerScale storage in a VxBlock System 1000 or Converged Technology Extension

Power off the Isilon or PowerScale storage components in the VxBlock System 1000 or attached Converged System. See the relevant procedure in this publication for powering off the attached Converged System and note the specific step that tells you when to power off the Isilon or PowerScale storage.

Prerequisites Look at the back panel and confirm that the LEDs on both batteries are green. If either battery is red, it has failed and must be uninstalled from the node. If both batteries are red, replace and verify them before shutting down the node.

Steps 1. Open OneFS and log in as root user. 2. Click CLUSTER MANAGEMENT > Hardware Configuration > Shutdown & Reboot Controls. 3. Select Shut Down. 4. Click Submit. 5. Power off the Cisco Nexus switches in the VxBlock System 1000 or Converged Technology Extension cabinet. 6. Power off the Isilon InfiniBand switches or Ethernet back-end switches in the VxBlock System 1000 or Converged Technology Extension cabinet.

Next steps Verify that all nodes have shut down by looking at the power light indicators on each node. 1. If a Generation 5 node does not power off: a. Using SSH, connect to the node. b. Log in as root and type:

shutdown -p now 2. If a Generation 6 or later node does not power off: a. Using SSH, connect to the node. b. Log in as root and type:

Isi config c. In the subsystem, type:

shutdown #

Where # represents the node number, or type:

shutdown all

If the node still does not power off, force the node to power off by pressing and holding the multifunction button. The button is on the back of the node. 3. If the node still does not respond, press Power on the node three times, and wait five minutes. If the node still does not shut down, press and hold Power until the node powers off. 4. Perform a forced shutdown only with a failed and unresponsive node. Never force a shutdown with a healthy node. Do not attempt any hardware operations until the shutdown process is complete. The process is complete when the node LEDs are no longer illuminated.

36 Power off 4 Powering on and off Integrated Data Protection

The Dell EMC Integrated Data Protection Product Guide provides information about powering on and off components for Converged Systems. Power on and off Integrated Data Protection with Avamar

Integrated Data Protection with Avamar can be powered on or off independently of the Converged System. Verify no backups or restores are running when you power off the Integrated Data Protection with Avamar. Refer to the Avamar Administration Guide for information about powering on and off the system. Refer to the sections about server shutdown and restart for information about using the dpnctl program to power on or power off the Avamar server or selected subsystem. Alternatively, follow the instructions provided in this section to generate shutdown instructions using the SolVe Desktop utility.

Related information Generate Avamar server shutdown documentation Avamar server shut down procedure

Generate Avamar server shutdown documentation

Generate procedures from the SolVe Desktop to shut down the Avamar server.

Steps 1. Download and install the SolVe Desktop software from Support and search for SolVe. 2. Run SolVe Desktop. 3. Re-authorize if prompted and download any available updates for Avamar. 4. Select Avamar and click Begin. 5. Select the following options to generate the Avamar server shutdown documentation:

Option Action Avamar Service Procedures Expand option. ADS Shutdown or Reboot Procedure Select option and click Next. Select Reboot or Shutdown Select Shutdown and click Next. Service Provider Select EMC.

6. Leave the remaining fields blank and click Next to continue. 7. Review the selected options and click Generate to create the required documentation. SolVe Desktop compiles the selected documentation and creates a Microsoft Word file.

Powering on and off Integrated Data Protection 37 Related information Avamar server shut down procedure

Avamar server shut down procedure

Power off Avamar components in the appropriate order.

Prerequisites ● Before shutting down the Avamar grid, verify that you have a validated checkpoint. ● Generate the required documentation from Generating the Avamar server shutdown documentation.

Steps 1. Using winscp, copy the avshutdown.pl script onto the /tmp folder of the Avamar Utility Node or single node server. avshutdown.pl is found at C:\ProgramData\EMC\SolVeDesktop\AVAMAR.SOLVE\Tools.

2. Complete the following sections from the Avamar Data Store Shutdown Procedure document: ● Run the avshutdown.pl Script to suspend garbage collection ● Prepare system for shutdown ● Shut down the Avamar Server Ignore instructions to power the system back on, unless you want to do so.

Related information Generate Avamar server shutdown documentation Power on and off Integrated Data Protection with NetWorker

Powering on and off Integrated Data Protection with NetWorker system requires steps performed in a specific order.

Steps 1. Using the standard Windows shutdown, shut down the following: a. NetWorker Storage Node VM b. NetWorker Server VM c. NetWorker Management Console d. License Server 2. To shut down the VMware Backup Appliance and External Proxies, perform the following steps: a. Open a console to the VMware Backup Appliance through the VMware vSphere client. b. Log in as root. c. Run dpnctl stop to stop all VMware Backup Appliance services. d. Once gsan shut down appears, power down the VMware Backup Appliance through the VMware vSphere Console using Power > Shutdown Guest. Power on and off Integrated Data Protection with Data Domain

Power on and off Integrated Data Protection with Data Domain, including expansion shelves, with steps performed in the specific order. If replication is enabled between the Data Domain system to be powered down and another Data Domain system, disable replication on the partner system.

38 Powering on and off Integrated Data Protection Refer to the Powering a protection system on or off section of the Dell EMC Data Domain Operating System Administration Guide for information about powering on and off the system.

Powering on and off Integrated Data Protection 39 Power on and off Integrated Data Protection with VPLEX

Power on and off Integrated Data Protection with VPLEX.

Steps 1. To power on the Converged Systemwith VPLEX, follow this order: a. Converged System b. Integrated Data Protection solution that contains VPLEX c. VMware vCenter Server/VMware vSphere If VMs are stored on VPLEX volumes that start automatically when the host starts, they do not start until the VPLEX system is running. 2. To power off the Converged System that contains VPLEX, follow this order: a. VMware vCenter server/VMware vSphere b. Integrated Data Protection solution that contains VPLEX c. Converged System 3. To power off VPLEX, use the cluster shutdown and the director shutdown commands, described in the VPLEX GeoSynchrony CLI Reference Guide on https://dell.com/support. Power on and off Integrated Data Protection with metro node

Power Integrated Data Protection with metro node on and off using the steps in this procedure, performed in the order specified.

Steps 1. To power on the Converged System that contains metro node, follow this order: a. Converged System b. Integrated Data Protection solution that contains metro node c. VMware vCenter server/VMware vSphere If VMs are stored on metro node volumes that start automatically when the host starts, they will not start until the metro node system is running.

2. To power off the Converged System that contains metro node, follow this order: a. VMware vCenter server/VMware vSphere b. Integrated Data Protection solution that contains metro node c. Converged System 3. To power off and restart metro node, use the following steps SolVe Desktop or SolVe Online to locate the shutdown procedure named Shutdown Procedure for Both Clusters in a Metro Configuration: a. In SolVe, click Miscellaneous > Admin > Metronode Admin Procedures. b. In the Wizard that opens, click Metronode Management Procedures > Shutdown Procedure. Power on and off Integrated Data Protection with RecoverPoint

Powering Integrated Data Protection with RecoverPoint on and off requires steps performed in the following order.

Steps 1. To power on the Converged System that contains RecoverPoint, follow this order:

40 Powering on and off Integrated Data Protection a. Converged System b. Integrated Data Protection solution that contains VPLEX (if installed) c. RecoverPoint (After powering up, enable consistency groups, if used) d. VMware vCenter server/VMware vSphere 2. To power off the Converged System that contains RecoverPoint, follow this order: a. VMware vCenter server/VMware vSphere b. VPLEX (if installed) c. RecoverPoint (disable or pause consistency groups first, if used) d. Converged System 3. To power on/off RecoverPoint, refer to RecoverPoint Deployment Manager Release 1.1 Product Guide. Power on and off Integrated Data Protection with Cyber Recovery

Power on and off Integrated Data Protection with Cyber Recovery.

Steps Power on 1. To power on the Cyber Recovery environment, perform these steps in the specific order as follows: a. Power on the Cyber Recovery network switch. Ensure the switch is fully booted before proceeding to the next step. b. Power on the Cyber Recovery Management host by physically pressing the power button on the physical host. c. Power on the Data Domain. d. Power on the Avamar Single Node by physically pressing the power button. Power off 2. See the following procedures to power off the following Cyber Recovery environment components in the following order: a. Power off the Avamar Single node as per the steps found in the Dell EMC Converged Systems Powering On and Off Guide. b. Power off the Data Domain as per the steps found in the Dell EMC Converged Systems Powering On and Off Guide. c. Power off the Cyber Recovery Management host with the following steps: i. Log in to the Cyber Recovery Management host as root either through the KVM Console or SSH. ii. To shut down type: shutdown. d. Power off the Cyber Recovery network switch by pulling the power cables. NOTE: Ensure that the running-configuration is copied to the startup-configuration before removing the power.

Powering on and off Integrated Data Protection 41 5 References

Cisco and Dell EMC documentation links are provided as a reference for powering components on and off. Cisco documentation

See the following Cisco documents for more information: NOTE: Authentication may be required to access these documents.

● Cisco 3900 Series and Cisco 2900 Series Hardware Installation Guide ● Cisco Catalyst 4900M Switch Installation Guide ● Cisco Nexus 1000V Series Switches Installation Guides ● Cisco Nexus 3000 Series Switches ● Cisco Nexus 5000 Series Hardware Installation Guide ● Cisco Nexus 9000 Series Switches ● Cisco UCS 6100 Series Fabric Interconnect Hardware Installation Guide ● Cisco UCS 5108 Server Chassis Hardware Installation Guide ● Cisco UCS C200 Server Installation and Service Guide Dell EMC documentation

See the following Dell EMC documents for more information: NOTE: Authentication may be required to access these documents.

● Avamar ● Data Domain ● Dell EMC Unity family storage arrays ● Isilon InfiniBand ● Isilon Ethernet Backend Network ● Isilon and PowerScale F-Series platform ● Isilon S-Series platform ● Isilon NL-Series platform ● Isilon X-Series platform ● Isilon F-Series platform ● Isilon H-Series platform ● PowerMax storage ● RecoverPoint ● VMAX3 Series ● VMAX 40K Series ● VMAX All-Flash storage ● VNX Series ● VNXe Series ● VNX VG2/VG8 Gateway ● VPLEX ● XtremIO storage X1 array ● XtremIO storage X2 array

42 References