Dell EMC VBlock 540 Converged Infrastructure Administration Guide PDF

Dell EMC VxBlock and Vblock Systems 540 Administration Guide

July 2020 Rev. 1.28

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.

2015 - 2020 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.

Chapter 1: Revision history............................................................................................................. 11

Chapter 2: Introduction..................................................................................................................14

Chapter 3: Intelligent Physical Infrastructure.................................................................................. 15

Chapter 4: Manage compute resources............................................................................................16 Start Cisco UCS Manager ................................................................................................................................................. 16

Directly upgrade firmware at endpoints...................................................................................................................... 16 Upgrade Cisco UCS software with Cisco UCS Firmware Auto Install.................................................................... 17

Activate a Cisco UCS Manager Capability Catalog......................................................................................................... 19 Activate a port license........................................................................................................................................................ 20 Set the time services.......................................................................................................................................................... 20 Add the syslog server......................................................................................................................................................... 20 Delete a syslog server..........................................................................................................................................................21 Add an SNMP server ..........................................................................................................................................................21 Delete an SNMP server...................................................................................................................................................... 22 Create an IP address block in the management pool..................................................................................................... 22 Create a UUID range...........................................................................................................................................................22 Delete a UUID pool.............................................................................................................................................................. 23 Add a WWNN range............................................................................................................................................................23 Delete a WWNN range....................................................................................................................................................... 24 Add a WWPN range............................................................................................................................................................ 24 Delete a WWPN range........................................................................................................................................................25 Add a MAC address range................................................................................................................................................. 26 Delete a MAC pool.............................................................................................................................................................. 26 Create a vNIC template......................................................................................................................................................26 Create boot policies.............................................................................................................................................................27

Create an SD boot policy.............................................................................................................................................. 27 Create a SAN boot policy............................................................................................................................................. 27 Create a LAN boot policy for VxBlock Central deployments................................................................................... 28

Cisco Trusted Platform Module.........................................................................................................................................28 BIOS policy (VMware vSphere 6.7)..................................................................................................................................28 Managing service profile templates.................................................................................................................................. 30

Configure service profile templates............................................................................................................................ 30 Cloning the service profile templates..........................................................................................................................32 Adding vNICs to the service profiles...........................................................................................................................33 Configuring service profile templates for Disjoint Layer 2........................................................................................34 Assigning or modifying a management IPv4 address................................................................................................35 Create a network profile for the IPv6 management address.................................................................................. 35 Assign or modify a management IPv6 address..........................................................................................................36 Assigning service profiles to Cisco UCS blade servers.............................................................................................36 Renaming service profiles.............................................................................................................................................36

Contents

Contents 3

Chapter 5: Manage networking resources....................................................................................... 38 Manage VMware NSX-V Data Center............................................................................................................................. 38 Manage VMware NSX-T Data Center..............................................................................................................................38 Create a named VLAN on both FIs................................................................................................................................... 38 Create a VLAN group on VxBlock Systems.....................................................................................................................38 Add a VLAN to a service profile template........................................................................................................................ 39 Add a VLAN to the Cisco Nexus 1000V Switch..............................................................................................................39 Add a VLAN to the Cisco Nexus switches.......................................................................................................................40 Remove a VLAN from the Cisco Nexus switches...........................................................................................................40 Configure a vPC................................................................................................................................................................... 41 Delete a vPC........................................................................................................................................................................ 42 Add VLANs to a vPC...........................................................................................................................................................42 Remove VLANs from a vPC...............................................................................................................................................42 Add vPCs to VLANs for Disjoint Layer 2 networks.........................................................................................................43 View vPCs assigned to VLANs for Disjoint Layer 2 networks.......................................................................................45 Remove vPCs from VLANs for Disjoint Layer 2 networks.............................................................................................46 Upgrade Cisco Nexus switch software............................................................................................................................ 46 Downgrade Cisco Nexus switch software....................................................................................................................... 47

Chapter 6: Manage Cisco MDS switches......................................................................................... 48 Upgrade Cisco MDS switch software.............................................................................................................................. 48 Downgrade Cisco MDS switch software......................................................................................................................... 49 Configure a VSAN............................................................................................................................................................... 49 Remove a VSAN..................................................................................................................................................................50 Configure a domain ID and priority for a VSAN...............................................................................................................50 Remove a domain ID and priority from a VSAN............................................................................................................... 51 Enable FC interfaces............................................................................................................................................................51 Disable FC interfaces...........................................................................................................................................................51 Move licenses between FC interfaces............................................................................................................................. 52 Create FC aliases.................................................................................................................................................................52 Delete an FC alias................................................................................................................................................................ 53 Create FC zones..................................................................................................................................................................53 Delete an FC zone...............................................................................................................................................................53 Create, modify, and activate zone sets............................................................................................................................54 Creating FC port channels................................................................................................................................................. 54 Remove an FC interface from a port channel................................................................................................................. 55

Chapter 7: Manage storage resources.............................................................................................56 Managing XtremIO..............................................................................................................................................................56 XtremIO................................................................................................................................................................................ 57

Chapter 8: Manage VMware vSphere ESXi 6.x..................................................................................61 Installing the latest VMware vSphere ESXi patch (vSphere 6.0)..................................................................................61 Installing the latest VMware vSphere ESXi patch (vSphere 6.5)..................................................................................61 Installing the latest VMware vSphere ESXi patch (VMware vSphere 6.7)................................................................. 62 Configuring advanced settings for VMware vSphere ESXi (vSphere 6.0)................................................................. 63 Configuring advanced settings for VMware vSphere ESXi (vSphere 6.5)................................................................. 64 Configure advanced settings for VMware vSphere ESXi (VMware vSphere 6.7).....................................................64

4 Contents

Restoring default values for VMware vSphere ESXi advanced settings (vSphere 6.0)........................................... 65 Restoring default values for VMware vSphere ESXi advanced settings (vSphere 6.5)........................................... 65 Restoring default values for VMware vSphere ESXi advanced settings (VMware vSphere 6.7)............................65 Hardening security on VMware vSphere ESXi hosts..................................................................................................... 66 Increasing the disk timeout on Microsoft Windows VMs.............................................................................................. 66 Installing vCenter Server root certificates on web browser (vSphere 6.5)................................................................ 66 Install vCenter Server root certificates on web browser (vSphere 6.7)......................................................................67 Setting up Java and Internet Explorer on the management workstation or VM (vSphere 6.x)............................... 67

Chapter 9: Manage VMware Single Sign On (VMware vSphere 6.x)................................................... 68 VMware vCenter SSO overview....................................................................................................................................... 68 Manage the lockout status of VMware Single Sign On (VMware vSphere 6.5)........................................................68 Manage the lockout status of VMware Single Sign On account (VMware vSphere 6.7).........................................68 Manage VMware Single Sign On default password policies (VMware vSphere 6.0 or 6.5).....................................69 Manage VMware vCenter SSO default password policies (VMware vSphere 6.7)...................................................69 Manage VMware Single Sign On lockout policies (VMware vSphere 6.5)................................................................. 69 Manage VMware Single Sign On lockout policies (VMware vSphere 6.7).................................................................. 70 Add an AD identity source to VMware Single Sign On (IPv4) (VMware vSphere 6.7)............................................. 70 Add Windows AD identity source to VMware SSO (VMware vSphere 6.7)................................................................71 Backing up or restoring the vCenter Server.....................................................................................................................71 Backing up and restoring the vCenter Server and PSC (vSphere 6.5)....................................................................... 72

Backing up the PSC and vCenter Server................................................................................................................... 72 Restoring the vCenter Server...................................................................................................................................... 72 Restoring the PSC......................................................................................................................................................... 72

Redirect VMware vCenter Server to the secondary external VMware Platform Services Controller (VMware vSphere 6.x)................................................................................................................................................... 73

Enabling fault tolerance for the external PSC ................................................................................................................ 73

Chapter 10: Manage virtualization...................................................................................................74 Patch VMware vSphere ESXi hosts with the VUM (VMware vSphere 6.0).............................................................. 74 Patch VMware vSphere ESXi hosts with the VUM (VMware vSphere 6.5).............................................................. 75 Patch VMware vSphere ESXi hosts with the VUM........................................................................................................77 Supported guest operating systems................................................................................................................................. 78 Use VMware Enhanced vMotion Compatibility with Cisco UCS blade servers.......................................................... 78 Enable VMware Enhanced vMotion Compatibility within a cluster...............................................................................78 Manage the VMware vCenter HA configuration.............................................................................................................79 Convert external VMware Platform Service Controllers to embedded ...................................................................... 79

Join Embedded Linked Mode domain......................................................................................................................... 80 Decommission external VMware Platform Service Controllers.................................................................................... 80 Configure the Virtual Flash Read Cache........................................................................................................................... 81

Chapter 11: Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)..........................82 Provision an existing VMware vSphere Distributed Switch...........................................................................................82

Modify a distributed port group...................................................................................................................................82 Create a distributed port group................................................................................................................................... 84 Configure a VMkernel interface...................................................................................................................................85 Associate VMware vSphere ESXi hosts.....................................................................................................................85 Configure jumbo frames............................................................................................................................................... 86 Modify CoS settings .....................................................................................................................................................86

Contents 5

Decommission VMware vSphere Distributed Switch components.............................................................................. 87 Delete a distributed port group ...................................................................................................................................87 Dissociate the VMware vSphere ESXi host...............................................................................................................88

Remove a VMware vSphere Distributed Switch............................................................................................................. 91 Migrate VM distributed port group assignments to a different switch ................................................................. 91 Remove VMkernel ports...............................................................................................................................................92

Configure Disjoint Layer 2 on VMware vSphere Distributed Switch............................................................................92 Create a VMware vSphere Distributed Switch for Disjoint Layer 2 ...................................................................... 92 Create distributed port groups for Disjoint Layer 2 ................................................................................................. 93 Add VMware vSphere ESXi hosts to the VMware vSphere Distributed Switch.................................................. 94

Back up and restore a VMware vSphere Distributed Switch data configuration....................................................... 95 Export a backup of a VMware vSphere Distributed Switch....................................................................................95 Import a backup of a VMware vSphere Distributed Switch.................................................................................... 95 Restore a VMware vSphere Distributed Switch backup..........................................................................................96

Troubleshoot VMware vSphere Distributed Switch....................................................................................................... 96

Chapter 12: Manage the Cisco Nexus 1000V Series Switch................................................................97 Managing licenses................................................................................................................................................................97 Adding hosts.........................................................................................................................................................................97 Creating a port profile......................................................................................................................................................... 97 Modifying the uplink port profiles......................................................................................................................................97 Removing the uplink port profiles......................................................................................................................................98 Modifying vEthernet data port profiles............................................................................................................................ 99 Modifying the QoS settings..............................................................................................................................................100 Upgrading the VEM software........................................................................................................................................... 101 Troubleshooting the Cisco Nexus 1000V Switch........................................................................................................... 101

Chapter 13: Manage VMware NSX with VPLEX on VxBlock Systems.................................................102 Perform a graceful failover............................................................................................................................................... 102 Perform a graceful recovery.............................................................................................................................................104

Chapter 14: Guidelines for backing up configuration files................................................................ 108 Back up configuration files................................................................................................................................................108 Back up network devices running Cisco NX-OS software...........................................................................................108 Back up Cisco UCS FIs......................................................................................................................................................109

Create and run the backup using the Cisco UCS Manager.................................................................................... 110 Create and run the backup using the Cisco UCS CLI............................................................................................... 111 Create and run the backup using scheduled backups.............................................................................................. 111 Configure fault suppression......................................................................................................................................... 112

Back up the VMware vCenter SQL server database.....................................................................................................112 Back up the VNXe configuration...................................................................................................................................... 114

Chapter 15: Back up Cisco MDS switches....................................................................................... 116 Create backups of startup and running configuration files........................................................................................... 116 Scheduling backups of the startup and running configuration files............................................................................. 116 Create a script to purge older copies of the backup files..............................................................................................117 Schedule the task to purge older backup files................................................................................................................ 118

Chapter 16: Configure VMware Enhanced Linked Mode (VMware vSphere 6.0)................................. 119

6 Contents

Introduction......................................................................................................................................................................... 119 VMware ELM with VMware vSphere 6.0 use cases .................................................................................................... 119 Back up and restoring Converged Systems with VMware ELM................................................................................. 120 AMP design (AMP-2S only)............................................................................................................................................. 120 VMware ELM scalability planning..................................................................................................................................... 121

Intra Converged System VMware ELM scalability planning .................................................................................. 122 Inter Converged System VMware ELM scalability planning in Converged Systems in a single physical

data center ...............................................................................................................................................................122 Inter Converged System ELM scalability planning with multiple physical data centers .....................................123

VMware ELM deployment information .......................................................................................................................... 123 VMware ELM dependencies and limitations...................................................................................................................124 VMware ELM references .................................................................................................................................................125 VMware ELM conclusions................................................................................................................................................ 125

Chapter 17: Configure VMware Enhanced Linked Mode (vSphere 6.5U1).......................................... 126 Introduction to ELM (vSphere 6.5U1).............................................................................................................................126 VMware ELM with VMware vSphere 6.5U1 use cases ............................................................................................... 126 Backup and recovery for ELM 6.5...................................................................................................................................126 Backup and recovery guidelines....................................................................................................................................... 127 Converged System AMP design (ELM/VMware vSphere 6.5U1) ............................................................................. 127 VMware ELM scalability planning (vSphere 6.5U1)...................................................................................................... 130

Intra Converged System VMware ELM scalability planning (VMware vSphere 6.5U1)......................................131 Inter Converged System VMware ELM scalability planning in a single physical data center (VMware

vSphere 6.5U1)......................................................................................................................................................... 131 Inter Converged System VMware ELM scalability planning with multiple physical data centers (VMware

vSphere 6.5U1)......................................................................................................................................................... 131 VMware ELM deployment information (VMware vSphere 6.5U1)............................................................................. 132 Verify PSC and PSC Partner Status............................................................................................................................... 133 Determining the VMware vCenter server within a vSphere Domain.......................................................................... 133 Reconfiguring the ring topology.......................................................................................................................................134 VMware ELM references (vSphere 6.5U1).................................................................................................................... 134 VMware ELM conclusions (VMware vSphere 6.5U1)...................................................................................................134

Chapter 18: Manage VMware Embedded Linked Mode (VMware vSphere 6.7)................................... 136 Configure VMware Embedded Linked Mode (VMware vSphere 6.7)........................................................................ 136

Chapter 19: Manage VMware Embedded Linked Mode (VMware vSphere 6.5)...................................139 Configure VMware Embedded Linked Mode (VMware vSphere 6.5)........................................................................139

Chapter 20: Manage VMware Enhanced Linked Mode..................................................................... 142 Back up and restore VxBlock Systems with VMware Embedded Linked Mode (VMware vSphere 6.7).............. 142 VMware Enhanced Linked Mode scalability planning (VMware vSphere 6.7).......................................................... 142 Intra Converged System VMware Enhanced Linked Mode scalability planning........................................................ 143 VMware Enhanced Linked Mode deployment information ......................................................................................... 143 VMware Enhanced Linked Mode references................................................................................................................. 144 VMware Enhanced Linked Mode conclusions (VMware vSphere 6.7)...................................................................... 144

Chapter 21: Set up VxBlock Systems to use VxBlock Central........................................................... 145 Access the VxBlock Central dashboard ......................................................................................................................... 145

Contents 7

Set up a VxBlock System..................................................................................................................................................145 Accept the end user license agreement....................................................................................................................145 Reset and reaccept end user license agreement.....................................................................................................146 Start VxBlock System discovery................................................................................................................................146 Update the Windows Registry ...................................................................................................................................147 Update the IP address tables on the Core VM (optional)...................................................................................... 148

Plan a multisystem clustered environment..................................................................................................................... 148 Associate a Core VM with an existing MSM VM.....................................................................................................149 Form a cluster of MSM VMs...................................................................................................................................... 150 Remove a Core VM from an MSM VM.....................................................................................................................152 Shut down and take a snapshot of the MSM cluster ............................................................................................ 153 Recover the MSM cluster...........................................................................................................................................153 Verify ElasticSearch if the MSM VM is changed.....................................................................................................154

Discover, decommission, or modify a component......................................................................................................... 155 Add Isilon Technology Extension on a VxBlock System..........................................................................................155 Add a component with the configuration editor...................................................................................................... 155 Add eNAS to VMAX3 storage.................................................................................................................................... 156 Edit component credentials in the system.cfg file................................................................................................... 157 Edit component properties with the configuration editor.......................................................................................157 Delete a component with the configuration editor..................................................................................................158

Configure VxBlock Systems and components ..............................................................................................................159 Access the VxBlock Central Shell session................................................................................................................ 159 Run VxBlock Central Shell from a remote host........................................................................................................159 VxBlock Central Shell commands.............................................................................................................................. 160 Components in VxBlock Central Shell....................................................................................................................... 160 View VxBlock Central Shell logs................................................................................................................................. 163 View VxBlock Central Shell jobs................................................................................................................................. 163

Configure Secure Remote Services for VxBlock Central 2.0 and later...................................................................... 163 Ensure that Cisco Discovery Protocol is enabled on Cisco MDS and Nexus Switches ...........................................164 Configure Secure Remote Services for VxBlock Central 1.5 and earlier.................................................................... 164

Register VxBlock Central with a Secure Remote Services gateway.................................................................... 164 Add a software identifier for an MSM VM .............................................................................................................. 165 Retrieve the software ID from the licensing system............................................................................................... 165 Update a Secure Remote Services gateway configuration or software identifier ............................................. 166 Deregister VxBlock Central with Secure Remote Services.................................................................................... 167 Send information to Secure Remote Services......................................................................................................... 167 Secure the connection between VxBlock Central and Secure Remote Services................................................167 Verify Secure Remote Services configuration......................................................................................................... 168 Troubleshoot Secure Remote Services connectivity issues...................................................................................168

Integrate with SNMP........................................................................................................................................................ 169 Provision the SNMP name, location, and contact information fields....................................................................169 SNMP traps, events, and CIM indications ............................................................................................................... 170 Communicate with the network management system............................................................................................ 171 Send SNMP traps in readable format........................................................................................................................ 171 Enable northbound communication through SNMP................................................................................................172

Integrate with AD............................................................................................................................................................... 173 Configure AD.................................................................................................................................................................174 Map roles to AD groups...............................................................................................................................................175

Configure alert profiles and templates to receive notification..................................................................................... 176 Change the default email for alert notifications............................................................................................................. 176

8 Contents

Configure port flapping for switches...............................................................................................................................176 Configure the VMs to use the NTP server..................................................................................................................... 177 Verify the ElasticSearch configuration............................................................................................................................ 177 Manage credentials............................................................................................................................................................ 177

Change the default password for root and VxBlock Central accounts.................................................................178 Use the nonadministrator account.............................................................................................................................179 Change the default CAS password for Core VM.....................................................................................................179 Change the default CAS password for MSM VM................................................................................................... 179 Synchronize the CAS password for the admin user................................................................................................180 Change the default CAS password for the MSP VM to match the MSM VM................................................... 180 Create users with access rights to storage components........................................................................................ 181 Change access credentials for a VxBlock System component ..............................................................................181 Bulk credential script................................................................................................................................................... 182 Manage third party certificates..................................................................................................................................182 Configure connection and download settings.......................................................................................................... 186 Manage credentials for RCM content prepositioning............................................................................................. 189

VxBlock Central Advanced Analytics.............................................................................................................................. 190 Change VxBlock Central Operations Adapter real-time alerts collection cycle interval..................................... 190 Change the VxBlock Central Adapter Collection cycle interval............................................................................. 190

Chapter 22: Manage VxBlock Systems with VxBlock Central............................................................ 191 Change discovery and health polling intervals................................................................................................................ 191 Monitor events and log messages....................................................................................................................................191

Change syslog rotation parameters........................................................................................................................... 192 Forward syslog messages to remote servers........................................................................................................... 192

Customize login banners................................................................................................................................................... 194 Launch VxBlock Central Lifecycle Management........................................................................................................... 195 Back up and restore Core VM..........................................................................................................................................195

Management backup................................................................................................................................................... 196 Change the backup schedule and frequency........................................................................................................... 196 Back up cron tasks.......................................................................................................................................................197 Back up configuration files on demand......................................................................................................................197 Back up databases on demand...................................................................................................................................197 Restore the software configuration.......................................................................................................................... 198 Restore databases....................................................................................................................................................... 198 Back up the Core VM.................................................................................................................................................. 199 Back up and restore the MSM VM and MSP VM................................................................................................... 199 Back up component configuration files.....................................................................................................................199

Ports and protocols........................................................................................................................................................... 201 Open port assignments............................................................................................................................................... 201 Northbound ports and protocols................................................................................................................................201 Southbound ports and protocols...............................................................................................................................202

Reference...........................................................................................................................................................................203 Core VM commands................................................................................................................................................... 203 MSM VM commands..................................................................................................................................................205 MSP VM commands...................................................................................................................................................205 Configuration editor component reference............................................................................................................. 206 Components, APIs, and services for VMs................................................................................................................. 211

Contents 9

Chapter 23: Manage the AMPs......................................................................................................213 Upgrade the Cisco UCS C2x0 Server (CIMC 2.x firmware)........................................................................................213 Upgrade the Cisco UCS C2x0 Server (CIMC 3.x and 4.x firmware)..........................................................................213 Upgrading VNXe3200 software.......................................................................................................................................214 Create a VMware datastore............................................................................................................................................. 214 Change VMware datastore capacity ..............................................................................................................................215 Add a VMware vSphere ESXi host for IPv4 ..................................................................................................................215 Add data store access to a VMware vSphere ESXi Host.............................................................................................216 Configure VMware vSphere ESXi persistent scratch location ................................................................................... 216 Expand an AMP-2S cluster...............................................................................................................................................217 Enable VMware Enhanced vMotion Compatibility.........................................................................................................217 Backing up AMP-2.............................................................................................................................................................219

Create an instance of the configuration repository.................................................................................................219 Create a backup of a configuration repository.........................................................................................................219 Restore a configuration file........................................................................................................................................ 220 Back up targets .......................................................................................................................................................... 220

Chapter 24: Change passwords.....................................................................................................221 Change the Cisco IMC password.................................................................................................................................... 221 Change the Cisco Nexus and MDS series switches admin password........................................................................ 221 Change the Cisco UCS password using the Cisco UCS Manager CLI...................................................................... 222 Change the Cisco UCS password using the Cisco UCS Manager GUI......................................................................222 Change the Intelligent Physical Infrastructure Appliance password...........................................................................222 Change the VMware ESXi host root password using the ESXi host System Customization menu...................... 223 Change the VMware ESXi host root password using the ESXi shell command....................................................... 223 Change the VMware vCenter Server SSO password on a PSC or vCenter Server with an embedded PSC

appliance.........................................................................................................................................................................223 Change the VMware vCenter Server SSO password on a Windows PSC or vCenter Server with an

embedded PSC ............................................................................................................................................................ 224 Change the XtremIO storage management password.................................................................................................224 Unlock the VMware vCenter Server SSO password................................................................................................... 225

10 Contents

Revision history

Date Document revision

Description of changes

July 2020 1.28 Added a chapter about changing passwords.

June 2020 1.27 Updated the section Launch VxBlock Central Lifecycle Management with information about component lifecycle management.

Added the following new topic for VxBlock Central Version 3.0.1 - Change the default email for alert notifications.

Removed topics in the Configure components to send traps section as they appear in the VxBlock Central Installation Guide.

Added support for XtremIO XMS version 6.3.0 with dual stack.

Added the following sections for changing passwords:

Change the Cisco IMC password Change the Cisco Nexus and MDS admin password Change the Cisco UCS password using the Cisco UCS Manager GUI Change the Cisco UCS password using the Cisco UCS Manager CLI Change the Panduit appliance password Change the VMware ESXi host root password using the ESXi host System

Customization menu Change the VMware ESXi host root password using the ESXi shell command Change the VMware vCenter Server SSO password on a PSC or vCenter Server with an

embedded PSC appliance Change the VMware vCenter Server SSO password on a Windows PSC or vCenter

Server with an embedded PSC Change the XtremIO storage management password Unlock the VMware vCenter Server SSO password

May 2020 1.26 Added support for VMware NSX-T Data Center.

Added the section Manage VMware NSX-T Data Center. Updated the section Configuration editor component reference.

March 2020 1.25 Following topics updated for new component support in VxBlock Central 3.0:

Back up component configuration files Configuration editor component reference New topic - Configure Data Domain to forward traps

Updated the topic:

Use a third-party signed certificate on the Core VM

December 2019 1.24 Updated the document with the following:

Added support for AMP Central. Added support for VxBlock Central Version 2.5 release. Added support for VxBlock Central Life Cycle Management Added the topic Make sure Cisco Discovery Protocol is enabled on Cisco MDS and

Nexus Switches

October 2019 1.23 Added a new topic titled Configure Secure Remote Services for VxBlock Central 2.0 and later

1

Revision history 11

Date Document revision

Description of changes

Reworded the existing topic title to Configure Secure Remote Services for VxBlock Central1.5 and earlier and added verification information

September 2019 1.22 Added support for VMware vSphere 6.5 Update 2d and VMware vSphere 6.7 Update 2.

Added note about Workflow Automation to Configuring service profile templates.

Added the topic Reset and re-accept end user license agreement to the section Set up VxBlock Systems to use VxBlock Central.

July 2019 1.21 Updated for VxBlock Central Version 2.0.

SRS configuration feature in the VxBlock Central user interface. Component discovery feature in the VxBlock Central user interface. New VxBlock Central alerts.

June 2019 1.20 Added support for expanding an AMP-2S cluster with Cisco UCS C220 M5 servers.

April 2019 1.19 Fixed JIRA EH-741 in Managing storage resources > Best practices for XtremIO.

March 2019 1.18 Added support for VMware vSphere 6.7.

Added support for Cisco UCS Virtual Interface Cards 1440 and 1480.

December 2018 1.16 Added support for VxBlock Central.

July 2018 1.15 Updated the following sections to include Cisco B480 M5 blade server:

Configuring service profile templates Adding vNICs to the service profiles Configuring service profile templates for Disjoint Layer 2

May 2018 1.14 Updated Best practices for XtremIO

February 2018 1.13 Updated VMware ELM 6.5 content.

Adding a VLAN to a service template - updated steps.

Removed VMware vSphere 5.5 content.

October 2017 1.12 Added a section for configuring VMware Enhanced Linked Mode (vSphere 6.5U1)

ELM dependencies and limitations - updated statement regarding Vision Intelligent Operations.

October 2017 1.11 Added and updated topics for VMware vSphere 6.5.

Updated the following topics:

Starting Cisco UCS Manager - added UCS Manager 3.x changes. Upgrading the Cisco UCS C2x0 Server - split into two topics CIMC 2.x firmware and

CIMC 3.x.

Deleted the topic Backing up network devices running Cisco IOS software - Nexus switches do not run IOS so this topic was not required. Refer to the topic Backing up network devices running Cisco NX-OS software.

Adding a VLAN to a service profile template - removed step 4.

September 2017 1.10 Added a section containing guidance for configuring VMware Enhanced Linked Mode.

August 2017 1.9 Added support for IPv6 on VxBlock Systems.

Added support for the 40 GB option on VxBlock System 540.

June 2017 1.8 Updated the value for Net.TcpipHeapSize in the section Configuring Advanced Settings for VMware vSphere ESXi.

Added the following section to the document:

12 Revision history

Date Document revision

Description of changes

Managing VMware NSX with VPLEX on VxBlock Systems

February 2017 1.7 Added a note about how to determine whether an NX-OS upgrade might need to be done in two stages rather than the usual one.

December 2016 1.6 Added support for AMP-2 with Cisco UCS M4 blades and VMware vSphere 5.5. Removed VLAN 118.

September 2016 1.5 Added support for the Cisco MDS 9396S 16G Multilayer Fabric Switch Added support for AMP-2S and AMP enhancements

August 2016 1.4 Added information about the Cisco MDS 9706 Multilayer Director.

April 2016 1.3 Added a topic for creating vNIC templates.

Added information about the following Cisco switches:

Nexus 3172TQ

October 2015 1.2 Updated to include support for VMware vSphere 6.0 with Cisco Nexus 1000V Switch.

Removed support for VMware vSphere 5.0.

August 2015 1.1 Updated to include VxBlock System 540. Added support for VMware vSphere 6.0 with VMware VDS on the VxBlock System and for existing Vblock Systems.

February 2015 1.0 Initial version

Revision history 13

Introduction This guide contains instructions for managing the Converged Systems after installation at the customer site.

In this document, the Vblock System and the VxBlock System are seen as the Converged System.

The target audience for this document includes those responsible for managing the Converged System, including the system administrator and Dell EMC personnel responsible for remote management. The document assumes that the administrator:

Is familiar with VMware, Dell EMC storage technologies and Cisco compute and networking technologies Is familiar with Converged System concepts and terminology Has Converged System troubleshooting skills

See the Glossary for definitions of terms specific to Dell EMC.

2

14 Introduction

Intelligent Physical Infrastructure The Intelligent Physical Infrastructure (IPI) Appliance provides an intelligent gateway to gather information about power, thermals, security, alerts, and all components in the cabinet.

VxBlock Central or Vision Intelligent Operations uses SNMP to poll the status of the IPI Appliance and then passes the results to VMware vCenter Server.

For cabinet-related operations, such as adding users or cabinet access cards, see the Dell EMC Intelligent Physical Infrastructure Appliance User Manual.

See the release certification matrix (RCM) to identify the recommended firmware version for your IPI Appliance. Contact Dell Technologies Support with any questions.

Connect a laptop to the appropriate subnet and use a browser with the following settings to access the IPI Appliance:

IP address: 192.168.0.253 Mask: 255.255.255.0 Gateway: 192.168.0.1

3

Intelligent Physical Infrastructure 15

Manage compute resources Provision and manage the Cisco UCS servers using the HTML5 web interface on Cisco UCS Manager version 3.2.1 and higher.

These instructions apply to Cisco UCS Manager for a Cisco UCS fourth generation environment must be version 4.0(2b) or higher. For more information about the HTML5 web interface, see the Cisco UCS Manager GUI Configuration Guide for versions appropriate versions.

1. To log in to the Cisco UCS Manager, type: https:// .

2. Enter the virtual cluster IP address of the management port on the FI. 3. If a Security Alert displays, click Yes or Proceed. If a banner window displays, review the message and click OK. 4. In the Login dialog box, enter your username and password. 5. If your Cisco UCS implementation includes multiple domains, select the appropriate domain from the Domain list and click Login.

Start Cisco UCS Manager Cisco UCS Manager, Version 3.2.1 and later releases provides an HTML5 based web interface that can be used in place of the traditional Java-based Cisco UCSM applet.

About this task

These instructions apply for Java-based interfaces on current versions of Cisco UCS Manager. Settings, policies, and pools apply regardless of the interface used.

Prerequisites

For more information about using the HTML5 web interface, see the Cisco UCS Manager GUI Configuration Guide for versions 3.2.1 and higher.

Steps

1. From a web browser, open the web link for Cisco UCS Manager GUI at: http(s)://UCSManager_IP.

2. Type the virtual cluster IP address of the management port on the fabric interconnect.

3. If a Security Alert dialog box is displayed, click Yes to accept the security certificate and continue.

4. In the Cisco UCS Manager window, click Launch UCS Manager.

5. For Cisco UCS Manager versions 3.2.1 and higher, click Launch UCS Manager to launch the HTML page.

6. If a banner window is displayed, review the message and click OK.

7. If a Security dialog box is displayed, check the box to accept all content from Cisco, and click Yes.

8. In the Login dialog box, type your username and password.

9. If your Cisco UCS implementation includes multiple domains, select the appropriate domain from the Domain drop-down list, and then click Login.

Next steps

Directly upgrading firmware at endpoints

Directly upgrade firmware at endpoints Some Converged Systems components require a reboot after being updated. Upgrading Cisco UCS software impacts the Cisco UCS Manager, FIs, I/O modules, chassis, chassis blades, and mezzanine adapters.

Prerequisites

Coordinate firmware upgrades during maintenance windows, and see Cisco documentation for proper upgrade procedures. Download the latest Cisco UCS B-Series GUI Firmware Management Guide.

4

16 Manage compute resources

Run a full state and all configuration backup. For a cluster configuration, verify the high availability status of both FIs shows up and running. Verify servers, I/O modules, and adapters are fully functional. An inoperable server cannot be upgraded. Verify that servers have been discovered. Discovery does not require that you power on the servers or associate them with a service

profile. Verify that the time, date, and time zone of FIs are identical for a cluster using a time source such as NTP.

Cisco documents recommended practices for managing firmware in the Cisco UCS Manager. Ensure that the firmware versions are compatible with the Release Certification Matrix.

Steps

1. Perform the Cisco UCS upgrade as described in the Cisco UCS B-Series GUI Firmware Management Guide for the release being installed.

2. To verify the upgrade, from the Navigation window, select the Equipment tab and Equipment node.

3. From the Work window, select the Firmware Management tab.

4. From the Installed Firmware tab, click Update Firmware. This step may take a few minutes, based on the number of chassis and servers.

5. From the Update Firmware dialog, perform the following:

a. From the Filter menu, select ALL. b. Select the endpoint firmware to update, and click OK.

Next steps

Verify the following:

All components are running the correct version of firmware. No new Cisco UCS faults were introduced because of the upgrade. All hosts have booted successfully.

Upgrade Cisco UCS software with Cisco UCS Firmware Auto Install Upgrade Cisco UCS software using Cisco UCS Firmware Auto Install on Cisco UCS B-Series chassis and blade servers.

About this task

The Cisco UCS Firmware Auto Install feature is performed in two stages that include upgrading the Cisco UCS infrastructure and server firmware.

Upgrading the Cisco UCS infrastructure firmware includes:

FI kernel and system I/O module Cisco UCS Manager

Upgrading the Cisco UCS server firmware includes:

Adapter BIOS CIMC RAID controller Disk firmware

These stages can be manually run or scheduled to run at different times, but never simultaneously. Cisco UCS infrastructure firmware upgrades must be updated first. Different versions of Cisco UCS infrastructure firmware and Cisco UCS server firmware are not supported. Cisco UCS infrastructure firmware upgrades do not support a partial upgrade to some infrastructure components in a Cisco UCS domain. Cisco UCSM does not support managing firmware on fusion I/O or LSI flash cards.

The Cisco UCS firmware auto install feature has the following scheduling options:

Manage compute resources 17

Upgrade stage Scheduling options

Infrastructure firmware Configure an immediate upgrade, or specify a start time. If a start time is not specified, the upgrade begins when the transaction is committed.

You cannot cancel a Cisco UCS infrastructure firmware upgrade after it has begun but can cancel upgrades that are scheduled to occur in the future.

Cisco UCS infrastructure firmware upgrades require an acknowledgment for an administrator user before the primary fabric interconnect is rebooted. The subordinate fabric interconnect reboots automatically.

Server firmware The Dell EMC Host Firmware Policy must be used for Cisco UCS server firmware upgrades and can be configured for an immediate or scheduled upgrade.

The server reboot is based on the maintenance policy that has been configured for each service profile. The default is for an immediate server reboot.

Create and deploy a maintenance policy called VCE_UserAck with the user acknowledgment option selected. This option requires an administrator level user to acknowledge the reboot request for each server.

You cannot cancel Cisco UCS server firmware upgrades after you complete the configuration in the Cisco UCS Install Server Firmware wizard.

A change in the firmware version is required every time that you perform the Cisco UCS firmware auto install.

The Cisco UCS server firmware auto install feature can only be run once per firmware version. You cannot run the Cisco UCS server firmware auto install feature when new servers are added.

Update servers by creating and associating new service profiles with the correct host firmware package.

The upgrade of Cisco UCS software impacts Cisco UCS Manager, FIs, I/O modules, chassis, chassis blades, and mezzanine adapters.

Prerequisites

Reboot as needed when updating Converged System components. Coordinate firmware upgrades during maintenance windows, and see Cisco documentation for proper upgrade procedures.

Download the latest Cisco UCS B-Series GUI Firmware Management Guide. Back up the configuration file into an all configuration backup file and perform a full state backup. The time, date, and time zone of the fabric interconnects must be identical for a cluster using a centralized time source such as NTP. Verify the following:

Both fabric interconnects are up and running for a cluster configuration. All servers, I/O modules, and adapters are fully functional. An inoperable server cannot be upgraded. All servers are discovered. Do not power on servers or associated with a service profile. The software version for the UCS firmware auto install feature is 2.1(1) or later. All endpoints are at Cisco UCS release 1.4 or later to run the Cisco UCS auto install. All endpoints are running the latest firmware release or patch for that release.

For the Cisco UCS Server Firmware Auto Install Feature, perform the following prerequisites:

Remove management firmware packages from all service profile templates and service profiles. Configure and deploy the VCE_UserAck maintenance policy in all new and existing associated service profiles. Complete this task

before configuring host firmware policies to support the Cisco UCS server firmware auto install feature. Create a host firmware policy for the version of code being deployed. During creation of the policy, do not set the package version or

define specific firmware versions. The Cisco UCS Server Firmware Auto Install wizard updates the embedded firmware package version of the policy. Assign this host firmware policy to the service profile templates that are associated with the blade to update using Auto Install. If the service profile does not set the host firmware policy for the blade, the host firmware policy is set to the default.

Do not update the Cisco UCS default host firmware package with server firmware upgrades or reference the package with the server Cisco UCS Auto Install wizard. This action may result in unexpected server reboots. If the default host firmware policy is updated, the blade could reboot if the default maintenance policy (immediate reboot) is configured. Updating the default host firmware package for a new firmware version can trigger an update and immediate reboot of all unassociated servers.

Setting a firmware package version during the initial creation of the host firmware policy could trigger an immediate upgrade of the blade. Depending on the maintenance policy for the service profile, an unexpected server reboot could occur. Cisco has documented practices for managing firmware in the Cisco UCS Manager. Ensure that the firmware versions are compatible with the RCM.

18 Manage compute resources

To perform a Cisco UCS upgrade, see the Cisco UCS B-Series GUI Firmware Management Guide for the specific release being installed.

Steps

1. To upgrade the Cisco UCS Infrastructure Firmware, perform the following:

a. Select the Equipment tab and then select the Firmware Management tab. b. From the Firmware Management tab, select the Firmware Auto Install tab. c. Select Install Infrastructure Firmware Upgrade. d. On the Prerequisites page, do not check any boxes.

NOTE: If no backup was performed or the Management Interfaces Monitoring Policy has not been enabled, do not

perform the upgrade. Do not bypass any of the checks, or ignore faults.

NOTE: Scheduled upgrades are the recommended methodology for Infrastructure upgrades. The secondary FI is

upgraded automatically, but the primary FI is not upgraded without a user acknowledgment.

e. Click Finish.

2. To upgrade Cisco UCS Server Firmware, perform the following:

a. Select the Equipment tab, and the Firmware Management tab. b. From the Firmware Management tab, select the Firmware Auto Install tab. c. Select Install Server Firmware.

d. On the Prerequisites page, do not check any boxes.

NOTE: If no system backup was performed or the Management Interfaces Monitoring Policy has not been

enabled, do not go to the upgrade. Do not bypass any of the checks.

e. On the Select Package Versions page, select the firmware version for the Cisco B-Series Blade software field and click Next. f. On the Select Host Firmware Packages page, select the VCE-HostFirmware package and click Next. g. On the Host Firmware Package Dependencies page, click Next. h. On the Impacted Endpoints Summary page, click Install. i. When appropriate, assign the new host firmware package to the blade servers that require the code upgrade. Reboot the server.

Next steps

If required, follow the Cisco recommended procedures for firmware downgrades. After a downgrade of a Cisco UCS domain to a previous release, delete all features that the downgraded firmware does not support.

NOTE: If your VxBlock System uses Cisco UCS 14xx VICs, and then upgrade the server and the FI to Cisco UCS firmware

version 4.0.1 or higher.

Activate a Cisco UCS Manager Capability Catalog Cisco UCS Manager uses Cisco UCS Manager Capability Catalog to update the display and configure components.

About this task

The catalog is divided by hardware components, such as the chassis, CPU, local disks, and the I/O module. There is one provider per hardware component. Use the catalog to view the list of providers available for that component. Each provider entry includes the vendor, model (PID), and revision. For each provider, you can view details of the equipment manufacturer and the form factor.

Each Cisco UCS Manager update includes Cisco UCS Manager Capability Catalog updates. Unless Cisco Technical Support instructs you otherwise, activate the Capability Catalog update only after you have downloaded, updated, and activated a Cisco UCS infrastructure software bundle.

When you activate a Capability Catalog update, the Cisco UCS Manager immediately updates to the new baseline catalog. In the Cisco UCS instance, you do not need to perform any tasks, reboot components or reinstall the Cisco UCS Manager when you perform an update.

Each Cisco UCS Manager release contains a baseline catalog. In rare cases, Cisco releases an update to the Capability Catalog and makes it available on the same site where you download firmware images.

The catalog update is compatible with Cisco UCS Manager, Release 1.3(1), and later.

Manage compute resources 19

Prerequisites

Download, update, and activate a Cisco UCS infrastructure software bundle before activating a capability catalog.

Steps

See the appropriate Cisco UCS B-Series GUI Firmware Management Guide for your release.

Activate a port license Port licenses for each Cisco UCS FI are factory-installed and shipped with the hardware.

About this task

The Cisco UCS 6296UP Fabric Interconnect has pre-installed licenses for the first 18 unified ports that are enabled in Cisco UCSM.

Expansion modules come with eight licenses that can be used on the expansion module or the base module. The eight default licenses that come with the Cisco UCS 6248UP Fabric Interconnect expansion module can be used to enable ports on the base module. If you uninstall the expansion module, the licenses are also uninstalled. Any default expansion module licenses that the base module is using are uninstalled from the ports on the base module, resulting in unlicensed ports.

The Cisco UCS 6332-16UP Fabric Interconnects have eight pre-installed unified port licenses, and four 40 GB QSFP port licenses. This FI is a fixed switch and does not include any expansion modules.

Port licenses are not bound to physical ports. When a licensed port is disabled, the license is retained for use with the next enabled port. Install licenses to use more fixed ports. If you use an unlicensed port, the Cisco UCSM initiates a 120-day grace period that is measured from the first use of the unlicensed port. Installing a valid license file negates the grace period. The system records the amount of time that was used in the grace period. Each physical port has its own grace period. Initiating the grace period on a single port does not initiate the grace period for all ports.

If a licensed port is not configured, that license is transferred to a port functioning within a grace period. If multiple ports are acting within grace periods, the license is moved to the port whose grace period is closest to expiring.

To avoid inconsistencies during failover, FIs in the cluster should have the same number of licensed ports. If a failover occurs while asymmetry exists, Cisco UCS enables the missing licenses and initiates the grace period for each port used on the failover node.

Converged Systems ship with the appropriate number of FI licenses installed. If more licenses are needed, request a chassis activation kit.

Steps

To view, obtain, download, install, and uninstall an FI license, see the Cisco UCS Manager Configuration Guide for your release.

Set the time services Cisco UCS Manager requires an instance-specific time zone setting and an NTP server to ensure that the correct time is displayed.

About this task

Set up the NTP server to be reachable from the Cisco UCS Manager and set all Converged System devices to the same time.

See the appropriate Cisco UCS Manager Configuration Guide to set the time zone and add an NTP server.

Add the syslog server Logs are sent to the system log server to facilitate reporting alerts and troubleshooting.

About this task

VxBlock Central or Vision Intelligent Operations is configured to receive system log information from the Cisco UCS environment. For more information, see Monitor Cisco UCS Manager using Syslog.

Prerequisites

Deploy a syslog server to be reachable from the Cisco UCS management IP address using an IP address.

20 Manage compute resources

Steps

1. Log in to the Cisco UCS Manager.

2. From the Admin tab, select Faults, Events and Audit Log > Syslog.

3. Under File, for Admin State, click Enabled.

4. In the Level menu, click Critical.

5. In the Server 1 section, for Admin State, click Enabled.

6. Click Critical.

7. In the Hostname field, type the primary syslog server IP address or hostname.

8. In the Facility field, select the appropriate facility.

9. Verify that logs have been received on the syslog server.

Delete a syslog server Delete a syslog server from the Cisco UCS domain using the Cisco UCS Manager.

Steps

1. Log in to the Cisco UCS Manager.

2. From the Admin tab, select Faults, Events, and Audit Log > Syslog.

3. In the appropriate server section, for Admin State, click disabled.

Add an SNMP server An SNMP server enables report alerting, monitoring, and troubleshooting of Cisco UCS Manager and the ability to receive SNMP traps.

About this task

SNMP v3 is the most secure protocol option.

VxBlock Central or Vision Intelligent Operations is configured to receive SNMP information from the Cisco UCS environment.

Prerequisites

Verify that an SNMP server is reachable using a hostname or IP address from the Cisco UCS Manager IP address.

Steps

1. Log in to the Cisco UCS Manager.

2. From the Navigation window, select the Admin tab.

3. From the Admin tab, expand All > Communication Management > Communication Services.

4. Select the Communication Services tab.

5. In the Admin State field, click Enabled.

6. In the Protocol field, set Type to All.

NOTE: You cannot change the default port of 161.

7. In the Community/Username field, type an alphanumeric string between 1 and 32 characters. Do not use @ , \ , " , ? or an empty space. The default is public.

8. In the System Contact field, type a contact. A system contact entry can be up to 255 characters and can be an email address, name, or number.

9. In the System Location field, type the location of the host on which the SNMP server runs.

10. Click Save Changes.

11. Verify that the SNMP server can poll the Cisco UCS Manager and receive traps.

Manage compute resources 21

Delete an SNMP server Remove an SNMP server from the Cisco UCS domain using the Cisco UCS Manager.

Steps

1. Log in to the Cisco UCS Manager.

2. From the Navigation window, select the Admin tab.

3. Expand All > Communication Management > Communication Services.

4. Select the Communication Services tab.

5. In the Admin State field, click Disabled.

6. Click Save Changes.

Create an IP address block in the management pool Cisco UCS Manager reserves each block of IP addresses in the management IP pool for external access that terminates in the CIMC on a server.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Configure service profiles and service profile templates to use IP addresses from the management IP pool. Servers cannot be configured to use the management IP pool. All OOB IPv4 addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect. IPv6 addresses should be in the configured in-band KVM VLAN. Do not assign static IP addresses to the management pool for a server or service profile.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the LAN tab.

3. In the LAN tab, expand Pools > IP Pools.

4. Right-click the VCE-KVM-POOL IP Pool, and select Create Block of IPv4 Addresses or Create Block of IPv6 Addresses.

5. In the Create a Block of IP Addresses window, perform the following:

a. In the From field, type the first IP address in the block. b. In the Size field, type the number of IP addresses in the pool. c. In the Subnet Mask or Prefix field, type the subnet mask or prefix that is associated with the IP addresses in the block.

All IP addresses in the management IP pool must be in the same subnet as the IP address of the fabric interconnect.

d. In the Default Gateway field, type the default gateway that is associated with the IP addresses in the block. e. In the Primary DNS field, type the IP address of the primary DNS server. f. In the Secondary DNS field, type the IP address of the secondary DNS server.

6. Click OK.

Next steps

Configure one or more service profiles or service profile templates to obtain the CIMC IP address from the management IP pool.

Create a UUID range Create a UUID pool using the Cisco UCS Manager.

Prerequisites

Verify that the new UUID range does not exist on any preexisting Cisco UCS compute environment.

22 Manage compute resources

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the Servers tab.

3. On the Servers tab, expand Servers > Pools.

4. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node.

5. Right-click UUID Suffix Pools, and select Create UUID Suffix Pool.

6. In the Define Name and Description window of the Create UUID Suffix Pool wizard, perform the following:

a. In the Name field, type the name of the UUID pool. b. In the Description field, type a description of the pool. c. In the Prefix field, select Derived (the system creates the suffix) or Other (allows you to specify the suffix). d. In the Assignment Order field, select Default for the system to create the order, or Sequential to assign the UUIDs in

sequence. e. Click Next.

7. In the Add UUID Blocks window of the Create UUID Suffix Pool wizard, click Add.

8. From the Create a Block of UUID Suffixes window:

a. Type the first UUID suffix in the pool and the number of UUID suffixes to include in the pool. b. Click OK.

9. Click Finish.

Next steps

Include the UUID suffix pool in a service profile and/or template.

Delete a UUID pool If you delete a UUID pool, addresses are not reallocated from the pool been assigned to vNICs or vHBAs.

About this task

All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until:

Associated service profiles are deleted. The vNIC or vHBA to which the address is assigned is deleted or assigned to a different pool.

Steps

1. Log in to the Cisco UCS Manager.

2. From the Navigation window, select the Servers tab.

3. Select Servers > Pools > Organization Name.

4. Expand the UUID Suffix Pools node.

5. Right-click the pool, and select Delete.

6. If a confirmation dialog box appears, click Yes.

Add a WWNN range Add a range to the WWNN pool using the Cisco UCS Manager. A WWNN pool is a WWN pool that contains only WW node names.

About this task

A WWN pool only includes WWNNs or WWPNs in the following ranges:

20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF

All other WWN ranges are reserved. To ensure that Cisco UCS WWNNs and WWPNs are unique in the SAN fabric, use the WWN prefix 20:00:00:25:B5:XX:XX:XX for all blocks in a pool.

Manage compute resources 23

Prerequisites

Obtain the WWNN information.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the SAN tab.

3. In the SAN tab, expand SAN > Pools.

4. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node.

5. Right-click WWNN Pools, and select Create WWNN Pool.

6. From the WWNN Pool window, perform the following:

a. In the Define Name and Description window, type a unique name and description for the WWNN pool. b. In the Assignment Order field, select Default or Sequential (for Cisco UCS 2.2(2c) or higher, select Sequential), and click

Next.

7. In the Add WWN Blocks window, click Add.

8. In the Create WWN Block window, perform the following:

a. In the From field, type the first WWNN in the pool. b. In the Size field, type the number of WWNNs to include in the pool. c. Click OK.

9. Click Finish.

Next steps

Include the WWNN pool in a vHBA template.

Delete a WWNN range Delete a range from the WWNN pool using the Cisco UCS Manager. If you delete a pool, the addresses are not reallocated from the pool that is assigned to vNICs or vHBAs.

About this task

All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until:

Associated service profiles are deleted. The vNIC or vHBA to which the address is assigned is deleted or assigned to a different pool.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the SAN tab.

3. Select SAN > Pools .

4. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node.

5. Expand the WWNN Pools node.

6. Right-click the WWNN pool to delete and select Delete.

7. If a confirmation dialog box appears, click Yes.

Add a WWPN range Add a range to the World Wide Port Names (WWPN) pool using the Cisco UCS Manager.

About this task

A WWN pool only includes WWNNs or WWPNs in the following ranges:

20:00:00:00:00:00:00:00 to 20:FF:FF:FF:FF:FF:FF:FF 50:00:00:00:00:00:00:00 to 5F:FF:FF:FF:FF:FF:FF:FF

24 Manage compute resources

All other WWN ranges are reserved. To ensure the uniqueness of the Cisco UCS WWNNs and WWPNs in the SAN fabric, use the following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX

Create separate WWPN pools for SAN Fabric A and SAN Fabric B.

Prerequisites

Obtain the WWPN information.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the SAN tab.

3. In the SAN tab, expand SAN > Pools.

4. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node.

5. Right-click WWPN Pools, and select Create WWNN Pool.

6. From the WWNN Pool window, perform the following:

a. In the Define Name and Description window, type a unique name and description for the WWNN pool. b. In the Assignment Order field, select Default or Sequential (for Cisco UCS 2.2(2c) or higher, select Sequential), and click

Next.

7. In the Add WWN Blocks window, click Add.

8. In the Create WWN Block window, perform the following:

a. In the From field, type the first WWPN in the pool. b. In the Size field, type the number of WWPNs to include in the pool. c. Click OK.

9. Click Finish.

Next steps

Include the WWPN pool in a vHBA template.

Delete a WWPN range Delete a WWPN range from the WWPN pool using the Cisco UCS Manager. If you delete a pool, the addresses are not reallocated from the pool that is assigned to vNICs or vHBAs.

About this task

All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until:

Associated service profiles are deleted. The vNIC or vHBA of the address is deleted or assigned to a different pool.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the SAN tab.

3. Select SAN > Pools > Organization_Name > WWPN Pools > WWPN_Pool_Name.

4. Expand the WWPN Pools node.

5. Right-click the WWPN pool that you want to delete and click Delete.

6. If a confirmation dialog box appears, click Yes.

Manage compute resources 25

Add a MAC address range Create a block of addresses to expand an existing MAC address pool.

Prerequisites

Verify that the range of values does not conflict with existing MAC address values.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the LAN tab.

3. Expand LAN > Pools.

4. Expand the node for the organization where you want to create the pool. If the system does not include multitenancy, expand the root node.

5. Right-click MAC Pools, and select Create MAC Pool.

6. In the first window of the Create MAC Pool wizard, perform the following:

a. In the Define Name and Description window, type a unique name and description for the MAC pool. b. In the Assignment Order field, select Default or Sequential (for Cisco UCS 2.2(2c) or higher, select Sequential), and click

Next.

7. In the Add MAC Addresses window, click Add.

8. In the Create a Block of MAC Addresses window, type the first MAC address in the pool and the number of MAC addresses to include in the pool.

9. Click Finish.

Delete a MAC pool Addresses are not reallocated from a deleted pool that have been assigned to vNICs or vHBAs.

Prerequisites

All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until:

Associated service profiles are deleted. The vNIC or vHBA to which the address is assigned is deleted or assigned to a different pool.

For more information, see the Cisco UCS Manager GUI Configuration Guide.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the LAN tab.

3. Select LAN > Pools > Organization Name.

4. Expand the MAC Pools node.

5. Right-click the MAC pool and select Delete.

6. If a confirmation dialog box is displayed, click Yes.

Create a vNIC template vNIC templates are used to create uniform virtual network adapters for service profiles and service profile templates.

About this task

Create a minimum of four vNIC templates for the service profiles. You can create vNIC templates for Disjoint Layer 2 configurations. As a best practice, evenly distribute vNICs between Fabric A and Fabric B.

Steps

1. Log in to Cisco UCS Manager.

26 Manage compute resources

2. From the Navigation window, select the LAN tab, and expand Policies.

3. Under root, right-click vNIC templates and select Create vNIC Template.

4. Type a name for the template up to 16 characters. For example, vNIC-0-Fabric-A.

5. Select Fabric A.

6. Ensure Enable Failover is not selected.

7. Verify Adapter is selected for the target.

8. For Template Type, select Updating Template.

9. For MTU, type 9000.

10. Select all appropriate VLANs. If required, create VLANs.

For a standard Cisco UCS - VDS 6.0 build, map all VLANs to each vNIC template or vNIC unless the environment dictates differently.

11. Select a preconfigured MAC Pool, or create one.

12. Select a QoS policy. VMware Virtual Standard Switch does not support QoS marking. For those adapters, the absence of QoS marking forces traffic back to a best effort QoS policy.

13. For Network Control Policy, select a policy with CDP enabled and Action on Uplink Fail set to Link Down.

The CDP-Link-Loss policy exists.

Create boot policies A boot policy determines the configuration of the boot device, the location from which the server boots, and the order boot devices are invoked.

Create an SD boot policy Add virtual media with the read-only option as the first boot order option, and local SD as the second boot option.

Steps

1. Log in to Cisco UCS Manager.

2. From the Navigation window, select the Servers tab, and expand Policies.

3. Right-click Boot Policies, and select Create Boot Policy.

4. Enter a name for the boot policy.

5. For VMware vSphere 6.x, leave all defaults selected for boot mode.

6. Expand Local Devices, and select Add Local CD/DVD and Add SD Card.

7. Click OK.

Create a SAN boot policy Add virtual media with the read-only option as the first boot order option and local SD as the second boot option.

Steps

1. Log in to Cisco UCS Manager.

2. From the Navigation window, select the Servers tab, and expand Policies.

3. Right-click Boot Policies and select Create Boot Policy.

4. Enter a name for the boot policy.

5. For VMware vSphere 6.x, leave all defaults selected for boot mode.

6. Expand Local Devices, and select Add Local CD/DVD.

7. Expand vHBAs, select Add SAN Boot and in the name field, type vHBA-0.

8. Select Primary, and click OK.

9. Click Add SAN Boot and in the name field, enter: vHBA-1.

10. Select Secondary, and click OK.

11. Click Add SAN Boot Target and Add SAN Boot Target to SAN Primary.

Manage compute resources 27

12. Leave the Boot Target LUN set to 0.

13. In the Boot Target WWPN field, type the WWPN from your storage array.

14. Verify that Type is set to Primary, and click OK.

15. Click the Add SAN Boot Target and Add SAN Boot Target to SAN Primary.

16. Leave the Boot Target LUN set to 0.

17. In the Boot Target WWPN field, type the WWPN from your storage array.

18. Verify Type is set to Secondary click OK.

19. Click Add SAN Boot Target and Add SAN Boot Target to SAN Secondary.

20. Leave the Boot Target LUN set to 0.

21. In the Boot Target WWPN field, type the WWPN from your storage array.

22. Verify Type is set to Secondary and click OK.

Create a LAN boot policy for VxBlock Central deployments Add virtual media with the read-only option as the first boot order option, and local SD as the second boot option.

Steps

1. Log in to Cisco UCS Manager.

2. From the Navigation window, select the Servers tab, and expand Policies.

3. Right-click Boot Policies and select Create Boot Policy.

4. Enter a name for the boot policy.

5. Leave all defaults selected.

6. Expand Local Devices and select Add Local CD/DVD.

7. Expand vHBAs, select Add LAN Boot and enter vHNIC-0 in the name field.

8. For the IP address, type IPv4 or IPv6.

9. Click OK.

10. Repeat these steps for vNIC-1 as secondary.

Cisco Trusted Platform Module The Cisco Trusted Platform Module (TPM) contains authentication and attestation services to provide safer computing in all environments.

Cisco TPM is a chip that securely stores passwords, certificates, or encryption keys that are used to authenticate remote and local server sessions. Cisco TPM is available, by default, as a component in the Cisco UCS B-Series Blade Servers and Cisco UCS C-Series Rack Servers.

See the software stack vendor for configuration and operational considerations relating to the Cisco TPM.

VMware vSphere 6.7 support TPM version 2.0.

BIOS policy (VMware vSphere 6.7) Complete this task to set the BIOS policy for service profiles.

Steps

1. Create a BIOS policy named VCE-Default.

2. Set the following options:

Quiet Boot: Disabled Intel Turbo Technology: Enabled Intel SpeedStep Technology: Enabled Intel Hyper-Threading Technology: Enabled Intel Virtualization Technology: Enabled Intel VT for Directed I/O: Enabled

28 Manage compute resources

CPU Performance: Enterprise Direct Cache Access: Enabled Power Technology: Performance Processor C-state: Disabled Processor C1E: Disabled Processor C3 Report: Disabled Processor C6 Report: Disabled Processor C7 Report: Disabled Energy Performance: Performance Frequency-floor Override: Enabled DRAM Clock Throttling: Performance Package C-state Limit: Platform Default CPU Hardware Power Management: Platform Default Memory RAS Configuration: Maximum Performance Low-voltage Double-data-rate Mode: Performance Mode DRAM Refresh Rate: Platform Default Intel QuickPath Interconnect Snoop Mode: Platform Default CDN: Enabled (VMware vSphere 6.7)

Example:

UCS-FI-A # scope org / UCS-FI-A /org # create bios-policy VCE-Default UCS-FI-A /org/bios-policy* # set quiet-boot-config quiet-boot disabled UCS-FI-A /org/bios-policy* # set lv-dimm-support-config lv-ddr-mode performance-mode UCS-FI-A /org/bios-policy* # set intel-turbo-boost-config turbo-boost enabled UCS-FI-A /org/bios-policy* # set enhanced-intel-speedstep-config speed-step enabled UCS-FI-A /org/bios-policy* # set hyper-threading-config hyper-threading enabled UCS-FI-A /org/bios-policy* # set intel-vt-config vt enabled UCS-FI-A /org/bios-policy* # set intel-vt-directed-io-config vtd enabled UCS-FI-A /org/bios-policy* # set cpu-performance-config cpu-performance enterprise UCS-FI-A /org/bios-policy* # set direct-cache-access-config access enabled UCS-FI-A /org/bios-policy* # set processor-energy-config cpu-power-management performance UCS-FI-A /org/bios-policy* # set processor-c-state-config c-state disabled UCS-FI-A /org/bios-policy* # set processor-c1e-config c1e disabled UCS-FI-A /org/bios-policy* # set processor-c3-report-config processor-c3-report disabled UCS-FI-A /org/bios-policy* # set processor-c6-report-config processor-c6-report disabled UCS-FI-A /org/bios-policy* # set processor-c7-report-config processor-c7-report disabled UCS-FI-A /org/bios-policy* # set processor-energy-config energy-performance performance UCS-FI-A /org/bios-policy* # set frequency-floor-override-config cpu-frequency enabled UCS-FI-A /org/bios-policy* # set dram-clock-throttling-config dram-clock-throttling performance UCS-FI-A /org/bios-policy* # set package-c-state-limit-config package-c-state-limit platform- default UCS-FI-A /org/bios-policy* # set cpu-hardware-power-management cpu-hardware-power-management platform-default UCS-FI-A /org/bios-policy* # set memory-ras-config ras-config maximum-performance UCS-FI-A /org/bios-policy* # set lv-dimm-support-config lv-ddr-mode performance-mode

Manage compute resources 29

UCS-FI-A /org/bios-policy* # set dram-refresh-rate-config dram-refresh platform-default UCS-FI-A /org/bios-policy* # set qpi-snoop-mode vpqpisnoopmode platform-default Perform the following commands on vSphere 6.7 deployments only:

UCS-FI-A /org/bios-policy # scope token-feature "Consistent Device Name Control" UCS-FI-A /org/bios-policy/token-feature # scope token-param cdnEnable UCS-FI-A /org/bios-policy/token-feature/token-param # scope token-settings Enabled UCS-FI-A /org/bios-policy/token-feature/token-param/token-settings # set is-selected yes

UCS-FI-A /org/bios-policy* # commit-buffer

Managing service profile templates Cisco UCS service profiles are used to streamline the configuration and management of Cisco UCS servers. They provide a mechanism for rapidly provisioning servers and their associated network connections with consistency in all details of the environment. They can be set up in advance before physically installing the servers.

Service profiles override identity values on the server at the time of association. Resource pools and policies set up in the Cisco UCS Manager are used to automate administration tasks. Disassociate the service profile from one server and manually associate it with another through an automated server pool policy. Burned-in settings for the UUID and MAC address on the new server are overwritten with the configuration in the service profile. The server change is transparent to the network so there is no required reconfiguration of any component or application to use the new server.

The following system resources are used and managed through resource pools and policies:

Virtualized identity information (including pools of MAC addresses, WWN addresses, management IP addresses, and UUIDs) Ethernet and FC adapter profile policies Firmware package policies Operating system boot order policies

Configure service profile templates Before VMware vSphere ESXi is installed, add vNIC-0 and vNIC-1 only for blade servers with multiple network adapters.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Before creating service profile templates, verify that vNIC templates exist. Configure a minimum of four vNIC templates and two vHBA templates.

NOTE: Template names are provided as examples. Template names vary based on the vNIC templates that exist on the

system.

NOTE: Use the Create New Service Profile workflow, available with VxBlock Central Workflow Automation, to automate

the following process:

Steps

1. Log in to the Cisco UCS Manager.

2. From the Navigation window, select the Servers tab and go to Service Profile Templates.

3. Right-click Service Profile Templates > Create Service Profile Template.

4. From the Identify Service Template window, perform the following:

a. In the Name field, type a name in the following format:

_ _

b. In the Type field, click Updating Template.

30 Manage compute resources

CAUTION: Updating Templates requires a UserAck Maintenance Policy. Failure to apply a UserAck Maintenance Policy may result in unexpected service profile reboots when modifying the Updating Service Profile Template.

c. Create the policy if it does not exist and apply it to the Service Profile Updating Template. If the UserAck Maintenance Policy is not created or used, create a Service Profile Initial Template.

d. In the UUID Assignment field, select created policy, and click Next.

5. On the Networking tab, under How would you like to configure LAN Connectivity? field, select Expert and click Add.

6. On the Create vNIC window, configure vNIC-0.

a. In the Name field, type vNIC-0. b. Select Use LAN Connectivity Template. c. In the vNIC Template field, select vNIC-0-Fabric-A. d. In the Adapter Policy field, select VMQ-Default > OK > Add.

NOTE: Templates that are created for blade servers with multiple physical network adapters should only contain

vNIC-0 and vNIC-1.

7. On the Create vNIC window, configure vNIC-1.

a. In the Name field, type vNIC-1. b. Select Use LAN Connectivity Template. c. In the vNIC Template field, select vNIC-1-Fabric-B. d. In the Adapter Policy field, select VMQ-Default > OK > Add.

NOTE: Templates that are created for blade servers with multiple physical network adapters should only contain

vNIC-0 and vNIC-1.

8. For blade servers with a single network adapter, follow the preceding steps to create the following adapters:

vNIC-2 from the vNIC2-Fabric-A template vNIC-3 from the vNIC-3-Fabric-B template

NOTE: Servers with 1340 or 1380 single network adapter may show a mismatch in the order between vNIC in the

UCS and VMNIC in the ESXi. To resolve the issue, follow the steps in How VMware ESXi determines the order in

which names are assigned to devices (2091560).

9. In the Local Storage field, select UserAck Maintenance Policy, and perform the following:

a. In the SAN Connectivity field, select Expert. b. In the WWNN Assignment field, select Global-WWNN-Pool, and click Add.

10. On the Create vHBA window, configure vHBA-0.

a. In the Name field, type vHBA-0. b. Select Use SAN Connectivity Template. c. In the vHBA Template field, select vHBA-0-Fabric-A. d. In the Adapter Policy field, select VMware > OK > Add.

11. On the Create vHBA window, configure vHBA-1.

a. In the Name field, type vHBA-1. b. Select Use SAN Connectivity Template. c. In the vHBA Template field, select vHBA-1-Fabric-B. d. In the Adapter Policy field, select VMware > OK > Add.

12. Retain the default Zoning settings.

13. For vNIC/vHBA placement, select Specify Manually, and perform the following:

Value or field Servers with a single mezzanine card

B200M4 blades with 1240/1280 or 1340/1380 VIC

B420M3 blades with 1240/1280 VIC

B460 blades with VMware vSphere 6.x

B480M5 blades with 1340/1380 or 1440/1480 VIC

2 vNIC-0 vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

3 vNIC-1 vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

vCon 1 and click >>assign>>.

4 vNIC-2 vCon 1 and click >>assign>>.

N/A N/A N/A N/A

Manage compute resources 31

Value or field Servers with a single mezzanine card

B200M4 blades with 1240/1280 or 1340/1380 VIC

B420M3 blades with 1240/1280 VIC

B460 blades with VMware vSphere 6.x

B480M5 blades with 1340/1380 or 1440/1480 VIC

5 vNIC-3 vCon 1 and click >>assign>>

N/A N/A N/A N/A

6 Select the vHBAs tab.

7 vHBA-0 vCon 1 and click >>assign>>

vCon 1 and click >>assign>>

vCon 1 and click >>assign>>

vCon 1 and click >>assign>>

vCon 1 and click >>assign>>

8 vHBA-1 vCon 1 and click >>assign>>

vCon 2 and click >>assign>>

vCon 3 and click >>assign>>

vCon 2 and click >>assign>>

vCon 3 and click >>assign>>

14. On the vMedia Policy window, retain the default settings.

15. On the Server Boot Order window, select the appropriate boot policy or create a one, and click Next.

16. From the Maintenance Policy field, select Default or User Acknowledgement, and click Next.

17. On the Server Assignment window, perform the following:

a. Select Up for the power state. b. In the Host Firmware field, select the new firmware package and click Next.

18. On the Operational Policies window, select the following:

a. For Bios Policy, select VCE_Default. b. Select External IPMI Management Configuration. c. For IPMI Access Profile, select IPMI. d. Select the Management IP Address.

19. In the Scrub Policy field, select default, and click Finish.

Next steps

For servers with more than one network adapter, add vNIC2, vNIC3, and other vNICs individually after installing VMware vSphere ESXi. Adding vNICs individually forces the vNIC and VMNIC ID numbers to match each host.

Related information

Configuring service profile templates for Disjoint Layer 2 on page 34

Cloning the service profile templates Clone and modify the service profile templates after they have been configured.

About this task

The following table provides sample values that can be used for cloned service profile templates:

Template type Sample name Sample boot policy

Service profile template 2_B200-01

Cloned service profile template 3_B200-01 3_storagesystem_serialnumber FC bandwidth only: service profile template

4_B200-01 4_storagesystem_serialnumber

FC bandwidth only: cloned service profile template

5_B200-01 5_storagesystem_serialnumber

Steps

1. To clone a service profile template, perform the following:

a. Right-click the service profile template that was configured, and click Create a Clone. b. For Clone Name, type a name for the service profile template. c. For Org, select the appropriate organization, and click OK.

32 Manage compute resources

2. To modify the cloned service profile template, perform the following:

a. Select the service profile template, and go to the Boot Order tab. b. Select Modify Boot Policy. c. Select the correct boot policy, and click OK.

3. Repeat steps 1 and 2 for each service template you want to clone and modify.

Next steps

Repeat these steps to clone more templates.

Adding vNICs to the service profiles vNICs can be added to any service profile template or unbound service profile.

About this task

CAUTION: Adding new vNICs to a service profile that is already assigned to a Cisco UCS blade server may trigger a PCIe

reprovisioning of vNICs/vHBAs devices. As a result PCIe addresses or adapter placement may change after reboot.

Service templates that are created for blade servers with multiple network adapters should only contain two network adapters. A minimum of two vNICs must be added to each service profile created from a two vNIC template after VMware vSphere ESXi has been installed.

Prerequisites

Verify VMware vSphere ESXi has been installed on the hosts. If adding vNICs to a service profile, verify that the service profile is unbound from the service profile template.

Steps

1. From the Network tab, click Add.

2. On the Create vNIC window, configure vNIC-2.

a. In the Name field, type vNIC-2. b. Select Use LAN Connectivity Template. c. In the vNIC Template field, select vNIC-2-Fabric-A. d. In the Adapter Policy field, select VMQ-Default > OK > Add.

3. From the Network tab, select Modify vNIC/vHBA Placement, and depending on the blade type, perform the following:

vNIC-2

Half-width blades (B200/B230/B220) with a single mezzanine card

B200M4 or B460M4 blades with 1240/1280 or 1340/1380 VIC

B420M3 blades with 1240/1280 VIC

B460 blades with four adapters

B480M5 blades with 1340/1380 or 1440/1480 VIC

vCon 1 and click >>assign>>.

vCon 2 and click >>assign>>.

vCon 3 and click >>assign>>.

vCon 2 and click >>assign>>.

vCon 3 and click >>assign>>.

NOTE: Servers with 1340 or 1380 single network adapter may show a mismatch in the order between vNIC in the

UCS and VMNIC in the ESXi. To resolve the issue, follow the steps in How VMware ESXi determines the order in

which names are assigned to devices (2091560).

4. Reboot the host.

5. On the Create vNIC window, configure vNIC-3.

a. In the Name field, type vNIC-3. b. Select Use LAN Connectivity Template. c. In the vNIC Template field, select vNIC-3-Fabric-B. d. In the Adapter Policy field, select VMQ-Default > OK > Add.

6. From the Network tab, select Modify vNIC/vHBA Placement and perform the following:

vNIC-3

Manage compute resources 33

Half-width blades (B200, B230, B220) with a single mezzanine card

B200M4 or B460M4 blades with 1240/1280 or 1340/1380 VIC

B420M3 blades with 1240/1280 VIC

B460 blades with four adapters

B480M5 blades with 1340/1380 vNIC-3 or 1440/1480 VIC

vCon 1 and click >>assign>>.

vCon 2 and click >>assign>>.

vCon 3 and click >>assign>>.

vCon 4 and click >>assign>>.

vCon 3 and click >>assign>>.

NOTE: Servers with 1340 or 1380 single network adapter, you may show a mismatch in the order between vNIC in the

UCS and VMNIC in the ESXi. To resolve the issue, follow the steps in How VMware ESXi determines the order in

which names are assigned to devices (2091560).

7. Reboot the host.

Configuring service profile templates for Disjoint Layer 2 Configure service profile templates on half-width, full-width, or quad blades with multiple network physical ports and onboard mLOM ports.

About this task

Add vNIC-4 and vNIC-5 individually to the service profile between reboots after installing VMware ESXi with vNICs 0 through 3. VMware vSphere ESXi interprets the PCI bus enumeration of the vNICs during installation.

CAUTION: Adding new vNICs to a service profile that is already assigned to a Cisco UCS blade server may trigger a PCIe

reprovisioning of vNICs/vHBAs devices. As a result PCIe addresses or adapter placement may change after reboot.

VMware vSphere 5.5 and later releases do not support remapping the VMNICs after the hypervisor is installed without a support ticket due to recent driver changes.

Use vNIC templates to create a template for vNIC-4-Fabric-A and for vNIC-5-Fabric-B.

Steps

1. From the Network tab of the service profile template, click Add.

2. On the Create vNIC window, configure vNIC-4.

a. In the Name field, type vNIC-4. b. Select Use LAN Connectivity Template. c. In the vNIC Template field, select vNIC-4-Fabric-A. d. In the Adapter Policy field, select VMQ-Default > OK > Add.

3. From the Network tab, select Modify vNIC/vHBA Placement, and depending on the blade type, perform the following:

vNIC-4

Half-width blades (B200, B230, B220) with a single mezzanine card

B200M4 or B460M4 blades with 1240/1280 or 1340/1380 VIC

B420M3 blades with 1240/1280 VIC

B460 blades with four adapters

B480M5 blades with 1340/1380 or 1440/1480 VIC

Select vCon 1, and click >>assign>>.

Select vCon 1, and click >>assign>>.

Select vCon 1, and click >>assign>>.

Select vCon 1, and click >>assign>>.

Select vCon 1, and click >>assign>>.

NOTE: Servers with 1340 or 1380 single network adapter may show a mismatch in the order between vNIC in the

UCS and VMNIC in the ESXi. To resolve the issue, follow the steps in How VMware ESXi determines the order in

which names are assigned to devices (2091560).

4. Reboot the host.

5. On the Create vNIC window, configure vNIC-5.

a. In the Name field, type vNIC-5. b. Select Use LAN Connectivity Template. c. In the vNIC Template field, select vNIC-5-Fabric-B. d. In the Adapter Policy field, select VMQ-Default > OK > Add.

6. From the Network tab, select Modify vNIC/vHBA Placement, and depending on the blade type, perform the following:

34 Manage compute resources

vNIC-5

Half-width blades (B200, B230, B220) with a single mezzanine card

B200M4 or B460M4 blades with 1240/1280 or 1340/1380 VIC

B420M3 blades with 1240/1280 VIC

B460 blades with four adapters

B480M5 blades with 1340/1380 or 1440/1480 VIC

Select vCon 1, and click >>assign>>.

Select vCon 2, and click >>assign>>.

Select vCon 3, and click >>assign>>.

Select vCon 3, and click >>assign>>.

Select vCon 3, and click >>assign>>.

NOTE: Servers with 1340 or 1380 single network adapter may show a mismatch in the order between vNIC in the

UCS and VMNIC in the ESXi. To resolve the issue, follow the steps in How VMware ESXi determines the order in

which names are assigned to devices (2091560).

7. Reboot the host.

Related information

Configure service profile templates on page 30

Assigning or modifying a management IPv4 address Assign or modify a management IPv4 address to the service profile or service profile template for Converged Systems using Cisco UCS Manager.

About this task

The IP address is assigned to the service profile or service profile template. Assign the IP address to the service profile instead of the blade. If the service profile moves to another blade, the IP address follows the service profile to the new blade.

With Cisco UCS management software, you can connect to the Cisco UCS Manager, or obtain access to a Cisco KVM Manager. If the Cisco KVM Manager option is used, set the management IP addresses on each service profile or service profile template. A static IP address can only be assigned to a service profile that is not associated with a service profile template. An IP pool must be used to assign management IP addresses to service profiles associated with a service profile template.

Steps

1. From the Servers tab of the Cisco UCS Manager, select Servers > Service Profiles > Root.

2. Select the first service profile or service profile template.

3. From the General tab, select Change Management IP Address.

4. Select Static or the required IP pool from the Management IP Address Policy drop-down menu.

5. Type the IP Address, Subnet Mask, and Gateway for the static address.

6. Repeat this process for all service profiles or service profile templates.

Create a network profile for the IPv6 management address Create an in-band network profile in the Cisco UCS Manager before assigning an IP address to a service profile or service profile template for VxBlock Systems.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the VLAN is configured on the LAN uplink switches and exists in Cisco UCS Manager. Verify that the VLAN group exists in Cisco UCS Manager. Do not select an IP address pool in the in-band network profile.

Steps

1. From the Navigation window of the Cisco UCS Manager, select the LAN tab.

Manage compute resources 35

2. Select LAN and the Global Polices tab.

3. From Inband Profile, select Inband VLAN Group and the VLAN from the Network list, and click Save Changes.

Assign or modify a management IPv6 address Change the management IP address on a service profile or service profile template for VxBlock Systems.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

See Create an in-band network profile for the IPv6 management address assignment to create the IPv6 KVM VLAN, VLAN group, and in- band network profile.

Cisco only supports IPv6 KVM, or CIMC addresses using an in-band profile.

Steps

1. On the Servers tab, select Servers > Service Profiles > Root.

2. Select the service profile or service profile template that you want.

3. On the General tab, click Change Management IP Address.

4. From the Inband tab, select the KVM VLAN in the Network drop-down list.

5. From the Inband IPv6 tab, select Static or the IPv6 IP pool from the Management IP Address Policy drop-down list.

6. If Static is selected, type the IPv6 IP address, prefix, default gateway address, and DNS server addresses, and click OK.

Assigning service profiles to Cisco UCS blade servers Assign service profiles to the Cisco UCS blade servers using the Cisco UCS Manager.

Steps

1. From the Navigation window, select the Servers tab.

2. Select Service Profile Host-01-1 and click Change Service Profile Association.

3. Under Server Assignment, click Select Existing Server.

4. Select the appropriate blade for this profile.

5. Distribute service profiles evenly within a VMware cluster across available chassis. The arrangement depends on the number of installed chassis and blades and the number of hosts in the VMware cluster. Coordinate with the person installing VMware to complete this procedure. For example, four chassis with eight blades per chassis equals 32 blades. Four 8-node VMware clusters equals two blades per chassis:

Assign service profiles 1 and 2 to chassis 1, blades 1 and 2. Assign service profiles 3 and 4 to chassis 2, blades 1 and 2. Assign service profiles 5 and 6 to chassis 3, blades 1 and 2. Assign service profiles 7 and 8 to chassis 4, blades 1 and 2.

Hosts in a VMware cluster should always belong to the same service profile template. For example, hosts 1 through 8 belong to template 1, hosts 9 through 16 belong to template 2.

6. Select Restrict Migration and click OK.

7. Repeat this procedure for all service profiles.

Renaming service profiles Rename service profiles using the Cisco UCS Manager.

Steps

1. From the Navigation window, select the Servers tab.

36 Manage compute resources

2. On the Servers tab, right-click the existing service profile.

3. Select Rename Service Profile.

4. Type the service profile name, and click OK.

Manage compute resources 37

Manage networking resources

Manage VMware NSX-V Data Center For information about managing VMware NSX-V Data Center, see the VMware NSX Data Center for vSphere Administration Guide.

Manage VMware NSX-T Data Center For information about managing VMware NSX-T Data Center, see the NSX-T Data Center Administration Guide.

Create a named VLAN on both FIs Add a named VLAN to both FIs in the Cisco UCS instance to connect to a specific external LAN.

About this task

The VLAN isolates traffic, including broadcast traffic to that external LAN. To ensure proper failover and load-balancing, add VLANs to both FIs.

VLANs in the LAN cloud and FCoE VLANs in the SAN cloud must have different IDs. VLANs with IDs in the range of 3968 to 4048 are reserved and cannot be used. Ethernet traffic is dropped on any VLAN that has an ID that overlaps with an FCoE VLAN ID.

CAUTION: Do not use the same ID for a VLAN and an FCoE VLAN in a VSAN. The result is a critical fault and traffic

disruption for all vNICs and uplink ports using that VLAN.

Prerequisites

Obtain a unique VLAN name and VLAN ID.

Steps

1. Log in to Cisco UCS Manager and select the LAN tab.

2. Expand LAN > LAN CLOUD, right-click LAN Cloud and select Create VLANs.

3. In the Create VLANs window:

a. Type the name of the VLAN in the Name field. b. Select Common/Global to apply the VLANs to both fabrics and use the same configuration parameters in both cases. c. Type the VLAN ID.

4. Click Check Overlap to ensure that the VLAN ID does not overlap with any other IDs on the system.

5. Click OK.

Related tasks

Add a VLAN to a service profile template on page 39

Create a VLAN group on VxBlock Systems Create a VLAN group on VxBlock Systems to use IPv6 features such as an in-band profile within the Cisco UCS Manager.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

5

38 Manage networking resources

Prerequisites

Verify that the selected VLAN is configured on the LAN uplink switches and exists in Cisco UCS Manager.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation, select the LAN tab.

3. Select LAN > VLAN Groups.

4. Right-click VLAN Groups, and select Create VLAN Group.

5. Type the VLAN group name.

6. Select the VLAN from the list, and click Next.

7. In a Disjoint Layer 2 environment, select the required uplink ports or uplink port channels. In a non-Disjoint Layer 2 environment, do not select a specific uplink port or port channel.

8. Click Finish after populating required fields.

Add a VLAN to a service profile template Add a VLAN to a service profile template for both Ethernet interfaces.

Steps

1. Log in to the Cisco UCS Manager and select the Servers tab.

2. Expand Servers > Service Profiles Templates and select the service profile template to which you want to add a VLAN.

3. Expand the service profile and select vNICs, then select an Ethernet interface and click Modify. If Modify is disabled, check the name of the vNIC template which the service profile is attached to, then go to Step 6.

4. Select the VLAN you created, and click OK.

5. Repeat these steps for the other Ethernet interface.

6. Expand LAN > Policies>vNIC Templates.

7. Select the vNIC template, and click Modify VLANs.

8. Select the VLAN you created, and click OK.

9. Repeat these steps for any other applicable vNIC templates on your service profile template.

Next steps

Add the VLANs to the Cisco Nexus 55xxUP switches, the Cisco Nexus 1000V Series virtual switch, and any other switching infrastructure that is required.

Add a VLAN to the Cisco Nexus 1000V Switch Add a VLAN to the Cisco Nexus 1000V Switch using Cisco NX-OS commands.

Prerequisites

Verify that the Cisco Nexus 1000V Virtual Supervisor Modules are up and reachable through the console or the management connection.

Obtain VLAN IDs and names.

NOTE: Obtain approval before changing management settings.

Steps

1. To view VLANs, type: show vlan 2. To create a VLAN, type: configure terminal 3. To assign an ID to the VLAN, type: vlan vlan_id 4. To assign a name to the VLAN, type: name vlan_name 5. To view information about the new VLAN, type: show vlan vlan_id

Manage networking resources 39

Add a VLAN to the Cisco Nexus switches Add a VLAN to the Cisco Nexus switches using Cisco NX-OS commands.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Name VLANs to identify usage. For example, NFS-VLAN-109.

Verify that the Cisco Nexus switches are up and reachable through the console or the management connection.

Verify connectivity information for the Cisco Nexus switches, such as:

Console information Login credentials IPv4/IPv6 address Access method (SSH/TELNET) VLAN names

Steps

1. To view all VLANs, type: show vlan 2. To create a VLAN, type: configure terminal 3. To assign an ID to the VLAN, type: vlan vlan_id 4. To assign a name to the VLAN, type: name vlan_name 5. To view information about the new VLAN, type: show vlan vlan_id

Related tasks

Configure a vPC on page 41

Remove a VLAN from the Cisco Nexus switches Remove a VLAN from the Cisco Nexus switches using Cisco NX-OS commands.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco Nexus switches are up and reachable through the console or the management connection.

Verify connectivity information for the Cisco Nexus switches, such as:

Console information Credentials for logging on IPv4/IPv6 address Access method (SSH or TELNET) VLAN names

Steps

1. To view all VLANs, type: show vlan 2. To enter configuration mode, type: configure terminal 3. To enter VLAN configuration mode, type: vlan vlan_id 4. To delete the specified VLAN, type: no vlan vlan_id

40 Manage networking resources

Configure a vPC Use any available Ethernet port to form a Cisco vPC enabled port channel on Cisco Nexus switches.

About this task

Configure the spanning tree mode on the port channels appropriately. For example, spanning tree mode on port channels towards the aggregation switches can be configured as normal. Spanning tree mode on port channels towards servers and other non-network devices can be configured as edge.

Default port channels are:

PO1 for the network uplink PO50 between the switches PO101 and PO102 from the switch to the FIs PO37 and PO38 for the AMP PO201 and PO202 for the X-Blades (if applicable)

To view ports that are reserved for VLANs, type: show vlan brief IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Using the console or the management connection, verify that you can reach the Cisco Nexus switches. Verify that the Cisco Nexus switches have the vPC and LACP features enabled. Verify that the peering device doing port channeling with the Cisco Nexus switches has the LACP enabled. Verify the appropriate member Ethernet ports are physically cabled. Verify the Ethernet ports that are designated to become members of this port channel. Create a VLAN. Obtain required vPCs, IDs, and the VLANs required for each vPC. Obtain Cisco Nexus switches IPv4/IPv6 address/console information, log in credentials and access method (SSH/TELNET).

Steps

1. Log in to the primary Cisco Nexus switch.

2. To start the configuration, type: Switch-A# config terminal

3. To specify the vPC, type: Switch-A(config)# interface port-channel port_channel_number 4. To add a description, type: Switch-A(config-if)# description description

NOTE: The description should include to, from, and a purpose.

5. To specify switchport mode, type: Switch-A(config-if)# switchport mode mode where mode is Trunk or Access.

6. To specify the Cisco vPC ID, type: Switch-A(config-if)# vpc vPC_ID 7. To enable trunking on the access VLAN or the VLANs, type one of the following:

Switch-A(config-if)# switchport access vlan_id Switch-A(config-if)# switchport trunk allowed vlan vlan_id

8. To set the spanning tree port, type: Switch-A(config-if)# spanning-tree port type type Where type specifies the type: normal/network/edge trunk/etc.

9. To set the state, type: Switch-A(config-if)# no shut 10. To add the appropriate Ethernet ports as members of the vPC:

a. Type Switch-A(config)# interface ethernet port_number b. Type Switch-A(config-if)# switchport mode mode where mode is Trunk or Access (same as the vPC).

c. Type Switch-A(config-if)# channel group channel_number mode active 11. To set the state, type: Switch-A(config-if)# no shut

Manage networking resources 41

12. To save the configuration, type: Switch-A# copy run start 13. Repeat this procedure on the peer switch.

Related tasks

Add a VLAN to the Cisco Nexus switches on page 40

Delete a vPC on page 42

Delete a vPC Delete a vPC from the Cisco Nexus switch.

Steps

1. Log in to the Cisco Nexus series switch.

2. To start the configuration, type: Switch-A# config terminal 3. To delete the appropriate Ethernet port as a member of the vPC, type: Switch-A# interface ethernet port_number 4. Type: Switch-A(config-if)# no channel group channel_number mode active 5. To delete the vPC, type: Switch-A(config)# no interface port-channel port_channel_number

Related tasks

Configure a vPC on page 41

Add VLANs to a vPC VLANs can be added to the trunk of an existing Cisco vPC on the Cisco Nexus series switch.

About this task

Extra VLANs are added to the trunk of an existing vPC when it is modified.

Prerequisites

Verify that the Cisco Nexus series switch is reachable through the console or the management connection. Verify that the Cisco vPC that must be modified is up. Obtain the required Cisco vPC ID and VLANs that must be added to the Cisco vPC. Cisco Nexus series switch connectivity information (IP address/console information), log in credentials and access method (SSH/

TELNET).

Steps

1. Log in to the primary Cisco Nexus series switch.

2. To run the configuration, type: Switch-A# config terminal 3. To specify the port channel, type: Switch-A(config)# interface port-channel

4. To add the VLANs, type: Switch-A(config)# switchport trunk allowed vlan add VLAN_IDs 5. Repeat this procedure on the peer Cisco Nexus series switch.

Related tasks

Remove VLANs from a vPC on page 42

Remove VLANs from a vPC VLANs can be deleted from the trunk of a Cisco vPC.

Steps

1. Log in to the Cisco Nexus series switch.

42 Manage networking resources

2. To run the configuration, type: Switch-A# config terminal 3. Type: Switch-A(config)# interface port-channel port_channel_number 4. To delete the VLAN ID, type: Switch-A(config-if)# switchport trunk allowed vlan remove VLAN_IDs

Related tasks

Add VLANs to a vPC on page 42

Add vPCs to VLANs for Disjoint Layer 2 networks Add vPCs to VLANs for Disjoint Layer 2 networks to define the VLANs that pass over specific uplinks using the Cisco UCS Manager.

About this task

All VLANs must be explicitly assigned to an uplink, including VLANs added after initial deployment. Otherwise, a VLAN is allowed to travel over all uplinks, which breaks the Disjoint Layer 2 concept.

Cisco vPCs 101 and 102 are production uplinks that connect to Cisco Nexus switch. Cisco vPCs 105 and 106 are customer uplinks that connect to external switches. If you use Ethernet performance port channels (103 and 104 by default), vPCs 101 through 104 should have the same VLANs assigned.

Manage networking resources 43

Prerequisites

The procedure provides an example scenario for adding port channels to VLANs for Disjoint Layer 2 networks.

Obtain the vPCs, VLANs, and VLAN-to-port channel assignments.

Steps

1. Log in to the Cisco UCS Manager.

2. To assign VLANs to vPCs 101 and 105 in Fabric A, perform the following:

a. Select the LAN tab. b. Select the LAN node. c. From the LAN Uplinks Manager tab, select VLANs > VLAN Manager. d. Select Fabric A. e. In the Port Channels and Uplinks tab, select Port-Channel 101. f. In the VLANs table, select the VLANs to assign to port channel 101.

Use the CTRL key to select more than one VLAN.

44 Manage networking resources

g. Click Add to VLAN and OK. h. In the Port Channels and Uplinks tab, select Port-Channel 105. i. In the VLANs table, select the VLANs to assign to port channel 105. j. Click Add to VLAN and OK. k. Verify that vPCs 101 and 105 (Fabric B) appear under all required VLANs. See Viewing vPC assigned to VLANs for Disjoint Layer 2

networks.

3. To assign VLANs to vPCs 102 and 106 in Fabric B, perform the following:

a. In VLAN Manager Navigation window, select the LAN tab. b. Select the LAN node. c. In the Work window, select the LAN Uplinks Manager link on the LAN Uplinks tab. d. In the LAN Uplinks Manager, select VLAN Manager. e. Select Fabric B. f. In the Port Channels and Uplinks tab, select Port-Channel 102. g. In the VLANs table, select the VLANs to assign to port channel 102.

Use the CTRL key to select more than one VLAN.

h. Select Add to VLAN, and click OK. i. In the Port Channels and Uplinks tab, select Port-Channel 106. j. In the VLANs table, select the VLANs to assign to vPC 106. k. Select Add to VLAN, and click OK. l. Verify that vPCs 102 and 106 (Fabric B) appear under all required VLANs.

Related tasks

View vPCs assigned to VLANs for Disjoint Layer 2 networks on page 45

Remove vPCs from VLANs for Disjoint Layer 2 networks on page 46

View vPCs assigned to VLANs for Disjoint Layer 2 networks Verify that vPCs have been assigned to VLANs.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the LAN tab.

3. On the LAN tab, select the LAN node.

4. In the Work window, select the LAN Uplinks Manager link on the LAN Uplinks tab.

5. In the LAN Uplinks Manager, select VLANs > VLAN Manager.

6. Click Fabric A or Fabric B to view the vPCs and VLANs on that fabric interconnect.

7. In the VLANs table, expand the appropriate node and the VLAN for which you want to view the assigned ports or vPCs.

Related tasks

Add vPCs to VLANs for Disjoint Layer 2 networks on page 43

Remove vPCs from VLANs for Disjoint Layer 2 networks on page 46

Manage networking resources 45

Remove vPCs from VLANs for Disjoint Layer 2 networks Remove vPCs from VLANs in a Disjoint Layer 2 network.

About this task

If you delete all port or vPC interfaces from a VLAN, the VLAN returns to the default behavior. Data traffic on that VLAN flows on all uplink ports and vPCs. Depending upon the configuration in the Cisco UCS domain, this default behavior can cause Cisco UCS Manager to drop traffic for that VLAN. To avoid dropping traffic, either assign at least one interface to the VLAN or delete the VLAN.

Steps

1. Log in to the Cisco UCS Manager.

2. In the Navigation window, select the LAN tab.

3. On the LAN tab, select the LAN node.

4. In the Work window, select the LAN Uplinks Manager link on the LAN Uplinks tab.

5. In the LAN Uplinks Manager, select VLANs > VLAN Manager.

6. Click Fabric A or Fabric B to view the vPCs and VLANs on that fabric interconnect.

7. In the VLANs table, expand the appropriate node and the VLAN from which you want to delete the assigned ports or vPCs.

8. Select the port or vPC that you want to delete from the VLAN.

NOTE: Hold down the Ctrl key to click multiple ports or vPCs.

9. Click Remove from VLAN.

10. If a confirmation dialog box appears, click Yes.

11. Click Apply if you want to continue to work in the VLAN Manager or click OK to close the window.

Related tasks

View vPCs assigned to VLANs for Disjoint Layer 2 networks on page 45

Add vPCs to VLANs for Disjoint Layer 2 networks on page 43

Upgrade Cisco Nexus switch software Upgrade the system image on the Cisco Nexus 9000 Series Switches.

About this task

Back up the original configuration by typing: copy running-config startup-config Verify that the configuration has been updated and back up the new configuration. There are two switches that require upgrades. Some operational checking is recommended after the first switch is upgraded to ensure

that a platform outage does not occur before upgrading the second switch.

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

See the Cisco website to access the software upgrade code and review release notes.

Depending on the running release, a multistep upgrade may be required. To verify whether multiple upgrade steps are required, see the section in the release notes titled Upgrading or Downgrading to a new release.

Obtain console (terminal) access and management IPv4/IPv6 access. Obtain a Cisco account to download images. Verify that there is an SCP, TFTP, FTP, or SFTP server to upload the Cisco NX-OS image to the switch.

Steps

1. Go to Cisco Support to download the Cisco NX-OS .bin file system software for the Cisco Nexus series switch.

46 Manage networking resources

2. Upload the file to the switch with the copy server (TFTP, SCP, FTP, or SFTP) being used.

3. To back up the switch running the configuration, type: copy running-config startup-config 4. To verify that the switch has enough space for the new image, type: Switch-A# dir bootflash: 5. If there is not enough space, type: delete bootflash:filename 6. To copy the updated images to the switch, type: Switch (config)# copy scp: bootflash:

a. Type the filename of the kickstart bin file from the Cisco download site. For example, n9000-dk9.6.1.2.I2.2(1).bin

b. For VRF, type: management.

c. Type the hostname of the SCP or FTP server. d. Type the username and password.

The system copies the images to the switch, and the following message opens:

***** Transfer of file Completed Successfully ***** 7. To view the impact of the upgrade, type: Switch-A(config)# show install all impact kickstart

bootflash:n9000-dk9.6.1.2.I2.2(1).bin 8. If you are performing a disruptive upgrade, following warning opens:

Switch will be reloaded for disruptive upgrade. Do you want to continue with the installation (y/n)? [n] y Install is in progress, please wait. Performing runtime checks. [####################] 100% -- SUCCESS Setting boot variables. [####################] 100% -- SUCCESS Performing configuration copy. [####################] 100% -- SUCCESS Module 1: Refreshing compact flash and upgrading bios/loader/bootrom/power-seq. Warning: please do not remove or power off the module at this time. Note: Power-seq upgrade needs a power-cycle to take into effect. On success of power-seq upgrade, SWITCH OFF THE POWER to the system and then, power it up. Note: Micro-controller upgrade needs a power-cycle to take into effect. On success of micro-controller upgrade, SWITCH OFF THE POWER to the system and then, power it up. [####################] 100% -- SUCCESS Finishing the upgrade, switch will reboot in 10 seconds. Switch(config)# 2011 Sep 8 18:16:43 Switch Sep 8 18:16:43 %KERN-0-SYSTEM_MSG: Shutdown Ports.. - kernel 2011 Sep 8 18:16:43 Switch Sep 8 18:16:43 %KERN-0-SYSTEM_MSG: writing reset reason 49, - kernel Broadcast message from root (Thu Sep 8 18:16:43 2011): The system is going down for reboot NOW!

9. Type Y to continue the installation.

10. When the switch reboots, to verify that the updated version of the software is running, type: show version 11. From the returned version information, verify that the system image file is the correct version.

Next steps

Some operational checking is recommended after upgrading the first switch to ensure that a platform outage is not experienced before upgrading the second switch.

When you have verified that the configuration has been updated successfully, create a backup of the new configuration.

Downgrade Cisco Nexus switch software Downgrade Cisco Nexus switch software to restore the original version after a failed upgrade.

Steps

To reverse a Cisco Nexus series switch software upgrade, perform the upgrade steps using the earlier version of the software.

Manage networking resources 47

Manage Cisco MDS switches

Upgrade Cisco MDS switch software Upgrade or downgrade the firmware on the Cisco MDS series switches.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Perform operational checking after upgrading the first switch to ensure that a platform outage does not occur before upgrading the second switch.

Obtain console (terminal) and management IPv4/IPv6 access. Obtain a Cisco account to download any images. Access an SCP, TFTP, FTP, or SFTP server to upload the Cisco NX-OS image to the switch. Obtain software upgrade code on the Cisco website. Review Cisco release notes before any upgrade.

Steps

1. To log in to the Cisco MDS switch and save the running configuration, type: copy run tftp://tftp-server/filename or copy run ftp://ftp server/filename

2. From the Cisco Support website, under Select a Task, select Download Software.

3. From the Products list, select Cisco IOS and NX-OS Software.

4. Select Download Software.

5. Select the switch and required software version, and select Download Now.

Sample kickstart filenames are as follows:

m9300-s1ek9-kickstart-mz-npe.6.2.13b.bin m9100-s5ek9-kickstart-mz.6.2.9a.bin

Sample NX-OS file names are as follows:

m9300-s1ek9-mz.6.2.13.bin m9100-s5ek9-mz.6.2.9a.bin m9700-sf3ek9-mz.6.2.9a.bin

6. Download Kickstart and system software with the copy server.

7. To copy the Kickstart and the system files from the FTP copy server to the fabric switch, from the MDS# prompt perform the following:

a. To access the bootflash directory, type: cd bootflash: b. To verify free space, type dir c. To copy the files, type:

copy ftp://ftp_server_addr/filename.bin filename.bin

copy ftp://ftp_server_addr/filename.bin filename.bin

8. To verify storage space on the standby supervisor, from the MDS# prompt, type:

6

48 Manage Cisco MDS switches

cd bootflash:

dir

9. While in configure mode, depending on the Converged System, from the VSJ3X2M9148SB# prompt, type: configure terminal Type configuration commands, one per line. End with CNTL/Z. VSJ3X2M9148SB(config)# no logging level all

10. To verify the impact of the firmware upgrade, depending on the switch, perform the following:

For VBxx-9396S-A#, type: show install all impact kickstart m9300-s1ek9-kickstart-mz-npe.6.2.13b.bin system m9300- s1ek9-mz.6.2.13b.bin

For VBxx-9706-A#, type: show install all impact kickstart m9700-sf3ek9-kickstart-mz.6.2.9a.bin system m9700-sf3ek9-mz.6.2.9a.bin

For VSJ3X2M9148B#, type: show install all impact kickstart m9100-s5ek9-kickstart-mz.6.2.9a.bin system m9100-s5ek9-mz.6.2.9a.bin

11. To view the entire upgrade process, perform the upgrade using the console port. You can log your session to a file for future reference.

12. To install the system and kickstart software, type: install all kickstart system file> For example:

MDS9396S-A# install all m9300-s1ek9-kickstart-mz-npe.6.2.13b.bin system m9300-s1ek9- mz.6.2.13b.bin

MDS9706-A# install all kickstart m9700-sf3ek9-kickstart-mz.6.2.9a.bin system m9700-sf3ek9- mz.6.2.9a.bin

VSJ3X2M9148B# install all kickstart m9100-s5ek9-kickstart-mz.6.2.9a.bin system m9100- s5ek9-mz.6.2.9a.bin

13. After the update finishes, to view the status of the install, type: show install all status

Downgrade Cisco MDS switch software Downgrade Cisco MDS switch software to restore the original version after a failed upgrade.

Steps

See the Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide for your release, and follow the guidelines for downgrading the software.

Configure a VSAN Configure a VSAN, and assign FC interfaces.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection. Obtain required VSANs, names, and FC interfaces that must be assigned to the VSANs. Obtain Cisco MDS switch IPv4/IPv6 address/console information, login credentials, and access method (SSH/TELNET). Name VSANs to identify usage. For example, for VSAN 10: SAN_A.

Manage Cisco MDS switches 49

Steps

1. Log in to the Cisco MDS switch.

2. To view VSANs, type: show vsan 3. To enter the global configuration mode and start the configuration, type: switch# configure terminal 4. To configure the database for VSAN, type: switch(config)# vsan database 5. To specify the VSAN being created, type: switch(config-vsan-db)# vsan vsan_id 6. To specify the VSAN name, type: switch(config-vsan-db)# vsan vsan_id name vsan_name 7. To assign an FC interface to the VSAN, type: switch(config-vsan-db)# vsan vsan_id interface fc slot 8. To update the interface with the VSAN, type: switch(config-vsan-db)# vsan vsan_id fc slot

Remove a VSAN Remove a VSAN and associated FC interfaces.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is reachable through the console or management connection. Obtain required VSANs, names, and FC interfaces. Obtain Cisco MDS switch IPv4/IPv6 address/console information, log in to credentials, and access method (SSH/TELNET).

Steps

1. Log in to the Cisco MDS switch.

2. To view VSANs, type: show vsan 3. To enter the global configuration mode and start the configuration, type: switch# configure terminal 4. To configure the database for VSAN, type: switch(config)# vsan database 5. To delete a VSAN, type: no vsan vsan_id

Configure a domain ID and priority for a VSAN Setting the domain ID and priority ensures that the switch takes a role of a principal switch in that VSAN. The domain ID in the VSAN does not get changed during a fabric merge.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

A unique domain ID must be assigned to the new VSAN added to the switch. When a VSAN is added to a switch in a fabric, the domain manager is used to assign a domain ID and priority to the VSAN. When a switch boots or joins a new fabric, the switch can request a specific domain ID or take any available domain ID.

Verify that the Cisco MDS switch is up and reachable through the console or management connection. Obtain required VSANs, names, and FC interfaces that must be assigned to the VSANs. Verify that the domain ID of the new VSAN matches the domain ID of the existing VSAN for this switch. Obtain Cisco MDS switch IPv4/IPv6 address/console information, login credentials, and access method (SSH/TELNET).

Steps

1. Log in to the Cisco MDS switch.

2. To view VSANs, type: show vsan 3. To view the domain ID of the existing VSAN on the switch, type: switch# show fcdomain domain-list 4. To enter the global configuration mode and start the configuration, type: switch# configure terminal

50 Manage Cisco MDS switches

5. To assign a domain ID, type: switch# fcdomain domain domain_id static vsan vsan_id 6. To assign a priority, type: switch# fcdomain priority 2 vsan vsan_id

Remove a domain ID and priority from a VSAN Remove the domain ID and priority to ensure that the switch is no longer a principal switch in that VSAN. You can then change the domain ID in that VSAN during a fabric merge.

Steps

1. To enter the global configuration mode and start the configuration, type: switch# configure terminal 2. To view the VSAN database, type: switch(config)# vsan database 3. To delete a VSAN, type no vsan vsan_id

Enable FC interfaces Enable FC interfaces on the Cisco MDS switch.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection. Obtain the FC interfaces IDs. Obtain Cisco MDS Switch IPv4/IPv6 address/console information, login credentials, and access method (SSH/TELNET).

Steps

1. Log in to the Cisco MDS switch.

2. To start the configuration, type: switch-A# config terminal 3. To configure the interface, type: switch-A(config)# interface fc interface_id 4. To apply for a license, type: switch-A(config-if)# port-license acquire 5. To enable the interface, type: switch-A(config-if)# no shutdown 6. To verify that the interface is up, type: show interface fc interface_id

Disable FC interfaces Disable FC interfaces on the Cisco MDS switch.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection. Obtain the FC interface IDs. Obtain Cisco MDS Switch IPv4/IPv6 address/console information, login credentials, and access method (SSH/TELNET).

Steps

1. Log in to the Cisco MDS switch.

2. To enter configuration mode, type: switch-A# config terminal 3. To specify the interface, type: switch-A(config)# interface fc interface_id 4. To disable the interface, type: switch-A(config-if)# shutdown

Manage Cisco MDS switches 51

Move licenses between FC interfaces Move licenses between FC interfaces on Cisco MDS switches.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection. Obtain the FC interfaces IDs. Obtain Cisco MDS switch IPv4/IPv6 address/console information, login credentials, and access method (SSH/TELNET).

Steps

1. Log in to the Cisco MDS switch.

2. To view the port licenses, type: show port-license 3. To start the configuration, type: Switch-A# config terminal 4. To configure the interface where license is being moved from, type: Switch-A(config)# interface fcinterface_id 5. To disable the license on that interface, type: Switch-A(config-if)# no port-license 6. To exit, type: Switch-A(config-if)# exit 7. To configure the interface where the license is being moved to, type: Switch-A(config)# interface fcinterface_id 8. To acquire the license on that interface, type: Switch-A(config-if)# port-license acquire 9. To end the configuration, type: Switch-A(config-if)# end 10. To verify that appropriate ports have enabled licenses, type: show port-license

Create FC aliases Create FC aliases.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection Obtain:

Required PWWN of the device VSAN ID of the device Cisco MDS Switch IPv4/IPv6 address/console information, log on credentials and access method (SSH/TELNET)

Steps

1. Log into the Cisco MDS switch.

2. To start the configuration, type: switch-A# config terminal 3. To configure the FC alias, type: switch-A (config)# fcalias name alias_name vsan vsan_id 4. To add the device to the FC alias, type: switch-A (config-fcalias)# member pwwn device_pwwn 5. To verify that the FC alias is configured, type: show fcalias name alias_name

52 Manage Cisco MDS switches

Delete an FC alias Delete an FC alias.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Steps

1. Log in to the Cisco MDS switch.

2. Type: switch-A# config terminal 3. To disable the FC alias, type: switch-A(config)# no fcalias name alias_name vsan vsan_id

Create FC zones Create an FC zone.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection. Obtain:

FC alias for members of the zone VSAN ID of the device Cisco MDS Switch IPv4/IPv6 address/console information, log on credentials and access method (SSH/TELNET)

Steps

1. Log into the Cisco MDS switch.

2. To start the configuration, type: switch-A# config terminal 3. To create the FC zone, type: switch-A(config)# zone name zone_name vsan vsan_id 4. To add the members to the FC zone, type: switch-A(config-zone)# member fcalias fcalias_name 5. To add additional members to the FC zone, type: switch-A(config-zone)# member fcalias fcalias_name 6. To commit the VSAN to the FC zone, type: switch-A(config) # zone commit vsan vsan_id 7. To exit, type: switch-A(config-zone)# end 8. To verify that the zone is configured, type: switch-A(config)# show zone name zone_name

Delete an FC zone Delete an FC zone.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Steps

1. To start the configuration, type: switch-A# config terminal 2. To delete an FC zone, type: switch-A(config)# no zone name zone_name vsan vsan_id

Manage Cisco MDS switches 53

Create, modify, and activate zone sets Create and activate zone sets.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection Obtain:

Names of the zones to be added or removed Name of the zone set to be modified or created VSAN ID of the zone set Cisco MDS Switch IPv4/IPv6 address/console information, log on credentials and access method (SSH/TELNET)

Steps

1. Log on to the Cisco MDS switch.

2. To start the configuration, type: switch-A# config terminal 3. To create or modify the zone set, type: switch-A(config)# zoneset name zoneset_name vsan vsan_id 4. To add members to the zone set, type: switch-A(config-zone)# member zone_name 5. To remove members from the zone set, type: switch-A(config-zone)# no member zone_name

NOTE: When running zone mode enhanced, you must issue the zone commit command for zoning changes to take

effect.

6. To activate the zone set: switch-A(config)# zoneset activate name zoneset_name vsan vsan_id 7. To exit: switch-A(config-zone)# end 8. To verify that the zone is configured, type: show zoneset name zoneset_name vsan vsan_id 9. To verify the active zone set, type: show zoneset active vsan vsan_id

Creating FC port channels Create a FC port channel.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

Verify that the Cisco MDS switch is up and reachable through the console or management connection Obtain:

Required FC interface IDs of port channel members The VSAN IDs of the interfaces Cisco MDS Switch IPv4/IPv6 address/console information, log on credentials and access method (SSH/TELNET)

Steps

1. Log into the Cisco MDS switch.

2. To start the configuration, type: switch-A# config terminal 3. To create the port channel interface, type:

a. switch-A(config)# interface port-channel port-channel_id b. switch-A(config-if)# channel mode active c. switch-A(config-if)# switchport mode F d. switch-A(config-if)# switchport rate-mode dedicated

54 Manage Cisco MDS switches

e. switch-A(config-if)# switchport trunk mode off 4. To add port channel to the VSAN, type: switch-A(config)# vsan vsan_id interface port-channel port-

channel_id 5. To add an FC interface to the port channel, type:

a. switch-A(config)# interface fcinterface_id b. switch-A(config-if)# channel-group port-channel_id force

6. To exit, type: switch-A(config-zone)#end 7. To verify that the port channel is configured, type: switch-A(config)# show interface port-channel port-

channel_id

Remove an FC interface from a port channel Remove an FC interface from a port channel.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Steps

1. To start the configuration, type: switch-A# config terminal 2. To remove an FC interface from the port channel, type: switch-A(config)# interface fcinterface_id 3. Type: switch-A(config-if)# no channel-group 4. To remove a port channel, type: switch-A(config)# no interface port-channel port-channel_id

Manage Cisco MDS switches 55

Manage storage resources

Managing XtremIO The XtremIO storage array provides the storage component for the Converged System. XtremIO is an all-flash system that uses building blocks known as X-Bricks that can be clustered together.

System operation of the XtremIO storage array is controlled by a standalone, dedicated, Linux-based server called XtremIO Management Server (XMS). The XMS host which can be either a physical or virtual server. XtremIO can continue operation when disconnected from the XMS, but cannot be managed.

For more information, see the Dell EMC XtremIO User Guide.

See the XtremIO Host Configuration Guide for guidance on recommended VMware vSphere server settings.

In Managing Tags, locate the following tasks:

Creating and Assigning a New Tag Assigning Tags to Storage Elements Modifying Tags Untagging an Object Removing a Tag

In Managing Volumes and Copies, locate the following tasks:

Creating a Volume Modifying Volume Properties Renaming a Volume Resizing a Volume

In Collecting Performance Data for Selected Volumes, locate the following tasks:

Refreshing a Volume Removing a Volume Managing Volume Tags

In Managing Initiator Groups, locate the following tasks:

Creating an Initiator Group Renaming an Initiator Group Removing an Initiator Group Managing Initiator Group Tags Modifying the Initiators List in an Initiator Group

In Managing Initiators, locate the following tasks:

Renaming an Initiator Modifying an Initiators Operating System Removing an Initiator Renaming an Initiator

In Mapping, locate the following tasks:

Generating LUN Mappings for Volumes and Initiator Groups Deleting LUN Mapping for Selected Volumes and Initiator Groups Modifying LUN Mapping for Selected Volumes and Initiator Groups

In Cluster Operations, locate the following tasks:

Managing the Virtual XMS Deploying a Virtual XMS Expanding the Virtual XMS Configuration

7

56 Manage storage resources

Backing up the Virtual XMS

Managing IP Configuration and Dual Stack Configuration XtremIO XMS version 6.3.0 and higher supports IPv6 and IPv4 connections (Dual Stack) to the management port concurrently for users connection.

The following list provides usage guidelines for the primary and secondary IP addresses and gateway addresses:

The primary IP address and gateway address versions are set during initialization and cannot be modified. The secondary IP address and gateway addresses are optional and can be added or removed. The secondary IP address and gateway

address versions are based on the primary IP address and gateway address. Use the add-xms-secondary-ip-address command to add the secondary IP address and default gateway.

Command structure:

add-xms-secondary-ip-address (xms-secondary-ip-and-sn= | xms-secondary-gw- addr= ) The following is an example for the add-xms-secondary-ip-address command:

xmcli(admin)> add-xms-secondary-ip-address xms-secondary-ip-sn="fd12:3456:789a:1::4/64" xms-secondary-gw-addr="fd12:3456:789a:1::1" XMS Secondary address added Successfully xmcli (admin)> xmcli (admin)> show-xms-info Ethernet Interfaces: Name Index IP Secondary-IP MAC-Address State Received-Bytes Received-Packets Sent-Bytes Sent-Packets Dropped-Packets Eth0 1 10.234.136.40 fd12:3456:789a:1 4 up 1451340 11648 749704 6600 0 xmcli (admin)> show-ip-addresses Name: xms Index: 1 XMS-IP-Addr: 10.234.136.40 XMS-IP-Addr-Subnet: 255.255.255.128 XMS-GW-Addr: 10.234.136.1 XMS-Secondary-IP-Addr: fd12:3456:789a:1::4 XMS-Secondary-IP-Addr-Subnet: ffff:ffff:ffff:ffff:: XMS-Secondary-GW-Addr: fd12:3456:789a:1::1 xmcli (admin)> remove-xms-secondary-ip-address Are you sure you want to remove IP settings? Are you sure? (Yes/No): yes XMS Secondary address removed Successfully xmcli (admin)>

XtremIO A stand-alone Linux-based server called XtremIO Management Server (XMS) controls the system operation of the XtremIO storage array. The XMS host is deployed as a VM on the VxBlock 1000 management infrastructure. XtremIO can continue operation when disconnected from the XMS, but cannot be managed.

For more information, see the Dell EMC XtremIO User Guide.

In Managing Tags, locate the following tasks:

Creating and Assigning a New Tag Assigning Tags to Storage Elements Modifying Tags Untagging an Object Removing a Tag

In Managing Volumes and Copies, locate the following tasks:

Creating a Volume Modifying Volume Properties

Renaming a Volume Resizing a Volume

In Collecting Performance Data, locate the following tasks:

Refreshing a Volume Removing a Volume Managing Volume Tags

In Managing Initiator Groups, locate the following tasks:

Creating an Initiator Group

Manage storage resources 57

Renaming an Initiator Group Removing an Initiator Group Managing Initiator Group Tags Modifying the Initiators List in an Initiator Group

In Managing Initiators, locate the following tasks:

Renaming an Initiator Modifying an Initiators Operating System Removing an Initiator Renaming an Initiator

In Mapping, locate the following tasks:

Generating LUN Mappings for Volumes and Initiator Groups Deleting LUN Mapping for Selected Volumes and Initiator Groups Modifying LUN Mapping for Selected Volumes and Initiator Groups

In Cluster Operations, locate the following tasks:

Managing the Virtual XMS Deploying a Virtual XMS Expanding the Virtual XMS Configuration Backing up the Virtual XMS

Managing IP Configuration and Dual Stack Configuration XtremIO XMS version 6.3.0 and higher supports IPv6 and IPv4 connections (Dual Stack) to the management port concurrently.

The following list provides usage guidelines for the primary and secondary IP addresses and gateway addresses:

The primary IP address and gateway address versions are set during initialization and cannot be modified. The secondary IP address and gateway addresses are optional and can be added or removed. The secondary IP address and gateway

address versions are based on the primary IP address and gateway address. Use the add-xms-secondary-ip-address command to add the secondary IP address and default gateway.

Command structure:

add-xms-secondary-ip-address (xms-secondary-ip-and-sn= | xms-secondary-gw- addr= ) The following is an example for the add-xms-secondary-ip-address command:

xmcli(admin)> add-xms-secondary-ip-address xms-secondary-ip-sn="fd12:3456:789a:1::4/64" xms-secondary-gw- addr="fd12:3456:789a:1::1" XMS Secondary address added Successfully xmcli (admin)> show-xms-info Ethernet Interfaces: Name Index IP Secondary-IP MAC-Address State Received-Bytes Received-Packets Sent-Bytes Sent-Packets Dropped-Packets Eth0 1 10.234.136.40 fd12:3456:789a:1 4 up 1451340 11648 749704 6600 0

xmcli (admin)> show-ip-addresses Name: xms Index: 1 XMS-IP-Addr: 10.234.136.40 XMS-IP-Addr-Subnet: 255.255.255.128 XMS-GW-Addr: 10.234.136.1 XMS-Secondary-IP-Addr: fd12:3456:789a:1::4 XMS-Secondary-IP-Addr-Subnet: ffff:ffff:ffff:ffff:: XMS-Secondary-GW-Addr: fd12:3456:789a:1::1 xmcli (admin)> remove-xms-secondary-ip-address Are you sure you want to remove IP settings? Y Are you sure? (Yes/No): Yes

58 Manage storage resources

XMS Secondary address removed Successfully When creating LUNs or adding new servers, use fewer, larger LUNs on XtremIO storage arrays. For applications requiring the most optimal performance, do not use more than 32 server initiators per XtremIO front-end port.

The following table provides the maximum blade server count for the 10 GB connectivity option:

XtremIO storage array X- Brick count

FC ports per fabric Maximum compute chassis (w/ Cisco UCS 6296UP FIs)

Maximum blade server counts (w/ Cisco UCS 6296UP FIs)

1 2 64 32 half width, full-width, or double-height, full-width blades

2 4 64 64 half width, full-width, or double-height, full-width blades

4 8 64 128 half width, full-width, or double-height, full-width blades

6 12 64 192 half width, full-width, or 128 double-height, full-width blades

8 16 64 256 half width, full-width, or 128 double-height, full-width blades

The following table provides the maximum blade server count for the 40 GB connectivity option:

XtremIO storage array X-Brick count

FC ports per fabric Maximum compute chassis (w/ Cisco UCS 6296UP FIs)

Maximum blade server counts (w/ Cisco 6296UP FIs)

1 2 8 32 half width, 32 full-width, or 16 double- height, full-width blades

2 4 16 64 half width, 64 full-width, or 32 double- height, full-width blades

4 8 32 128 half width, 128 full-width, or 64 double- height, full-width blades

6 12 32 192 half width, 128 full-width, or 64 double- height, full-width blades

8 16 32 256 half width, 128 full-width, or 64 double- height, full-width blades

To balance host clusters, zone four array front-end ports to a single server or spread the VMware vSphere ESXi cluster across several X-Brick building blocks.

If host clusters are heavily imbalanced in the number of hosts, zone the clusters differently. Ensure that all X-Brick building blocks have similar I/O loads. For larger host clusters, consider configuring eight paths depending on I/O requirement.

For servers with two vHBAs, zone each vHBA to both XtremIO Storage Controllers on a single X-Brick building block. If the XtremIO array has multiple X-Brick building blocks, zone the vHBAs to different X-Brick building blocks.

vHBA 0 -> X1-SC1-FC1 and X1-SC2-FC1 vHBA 1 -> X2-SC1-FC2 and X2-SC2-FC2

An example of four X-Brick building blocks and four clusters:

Cluster Port

Cluster 1 X1-SC1-P1

X1-SC2-P1

X3-SC1-P2

X3-SC2-P2

Cluster 2 X2-SC1-P1

X2-SC2-P1

X4-SC1-P2

X4-SC2-P2

Manage storage resources 59

Cluster Port

Cluster 3 X1-SC1-P2

X1-SC2-P2

X3-SC1-P1

X3-SC2-P1

Cluster 4 X2-SC1-P2

X2-SC2-P2

X4-SC1-P1

X4-SC2-P1

For servers with four vHBAs, zone each vHBA to one XtremIO storage controller for four paths as follows:

vHBA XtremIO storage controller

vHBA 0 X1-SC1-FC1

vHBA 1 X1-SC2-FC2

vHBA 2 X2-SC1-FC1

vHBA 3 X2-SC2-FC2

If there is only one VMware vSphere ESXi cluster that is connected to the XtremIO cluster, zone the vHBAs to every XtremIO front- end port in the fabric for hosts with 2 vHBAs.

If there are four vHBAs, zone each vHBA to half the ports in the fabric. For ESXi clusters on VxBlock Systems, zone four paths per server. Increase up to eight paths depending on application requirements. VMware vSphere has a limit of 1024 device paths per server. Consider this limit when configuring more than two vHBAs. XtremIO has a limit of 16,000 paths and 1024 initiators per XtremIO cluster. Configure volumes with a block size of 512 bytes. Format VMware vSphere ESXi VMs as Thick Provision Eager Zeroed.

60 Manage storage resources

Manage VMware vSphere ESXi 6.x

Installing the latest VMware vSphere ESXi patch (vSphere 6.0) Install the latest supported VMware vSphere ESXi patch.

About this task

After you install the latest patch, when you update a VMware vSphere ESXi host to a newer supported build, the host no longer shares the same build.

Use the VUM if upgrading to a newer supported build, however, you can use the CLI to install the patch.

Do not use this procedure for major upgrades.

Prerequisites

Verify that the host is in Maintenance mode and all the VMs are evacuated. Verify the software compatibility for the Cisco Nexus 1000V Series Switch or VMware VDS, PowerPath VE, and the build to which

you are upgrading. You might need to upgrade third-party software before upgrading VMware vSphere ESXi. Obtain the Release Certification Matrix with the version to which you want to update. Look for the supported version of the VMware

patch (build) in the Virtualization section. Determine which patch to install. For supported versions, refer to the appropriate Release Certification Matrix.

Steps

1. Download the latest VMware vSphere ESXi patch supported for this release.

2. Using a browser, navigate to the VMware patch portal.

3. In the Search by Product menu, select ESXi (Embedded and Installable) | 6.x.

4. Click Search.

5. Select and download the latest supported VMware vSphere ESXi patch. For example, ESXi6X0-2017XXXXX.zip

6. Install the patch as described in Patching VMware vSphere ESXi hosts with the VMware Update Manager.

7. To verify the installation, on the VMware vSphere ESXi host Splash Screen (through Cisco UCS vKVM), confirm that the build number matches the update just applied.

8. Reboot the VMware vSphere ESXi host.

Installing the latest VMware vSphere ESXi patch (vSphere 6.5) Install the latest supported VMware vSphere ESXi patch.

About this task

After you install the latest patch, when you update a VMware vSphere ESXi host to a newer supported build, the host no longer shares the same build.

Dell EMC recommends that you use the VMware Update Manager (VUM) if upgrading to a newer supported build, however, you can use the CLI to install the patch.

Do not use this procedure for major upgrades.

8

Manage VMware vSphere ESXi 6.x 61

Prerequisites

Verify that the host is in Maintenance mode and all the VMs are evacuated. Verify the software compatibility for the VMware VDS, PowerPath VE, and the build to which you are upgrading. You might need to

upgrade third-party software prior to updating to the latest release of VMware ESXi. Obtain the Release Certification Matrix and Release Notes with the version to which you want to update. Look for the supported

version of the VMware patch (build) in the Virtualization section. Determine which patch to install. Refer to the appropriate Release Certification Matrix and Release Notes.

Steps

1. Download the latest VMware vSphere ESXi patch supported for this release.

2. Using a browser, navigate to https://www.vmware.com/patchmgr/findPatchByReleaseName.portal.

3. In the Search by Product menu, select ESXi (Embedded and Installable) 6.5.

4. Click Search.

5. Select and download the latest supported VMware vSphere ESXi patch.

6. Install the patch as described in VMware knowledge base article 2008939.

7. To verify the installation, on the VMware vSphere ESXi host Splash Screen (through Cisco UCS vKVM), confirm that the build number matches the update just applied.

8. Reboot the VMware vSphere ESXi host.

Installing the latest VMware vSphere ESXi patch (VMware vSphere 6.7) Install the latest supported VMware vSphere ESXi patch.

About this task

After you install the latest patch, when you update a VMware vSphere ESXi host to a newer supported build, the host no longer shares the same build.

Use the VUM if upgrading to a newer supported build, however, you can use the CLI to install the patch.

Do not use this procedure for major upgrades.

Prerequisites

Verify that the host is in Maintenance mode and all the VMs are evacuated. Verify the software compatibility for the Cisco Nexus 1000V Series Switch or VMware VDS, PowerPath VE, and the build to which

you are upgrading. You might need to upgrade third-party software before upgrading VMware vSphere ESXi. Obtain the Release Certification Matrix with the version to which you want to update. Look for the supported version of the VMware

patch (build) in the Virtualization section. Determine which patch to install. For supported versions, refer to the appropriate Release Certification Matrix.

Steps

1. Download the latest VMware vSphere ESXi patch supported for this release.

2. Using a browser, navigate to the VMware patch portal.

https://www.vmware.com/patchmgr/findPatchByReleaseName.portal

3. In the Search by Product menu, select ESXi (Embedded and Installable) | 6.x.

4. Click Search.

5. Select and download the latest supported VMware vSphere ESXi patch. For example, ESXi6X0-2017XXXXX.zip

6. Install the patch as described in VMware knowledge base article 2008939.

7. To verify the installation, on the VMware vSphere ESXi host Splash Screen (through Cisco UCS vKVM), confirm that the build number matches the update just applied.

8. Reboot the VMware vSphere ESXi host.

62 Manage VMware vSphere ESXi 6.x

Configuring advanced settings for VMware vSphere ESXi (vSphere 6.0) Configure advanced VMware vSphere ESXi settings.

About this task

NFS performance is enhanced when advanced configuration options are set. Apply NFS options before connecting any NFS share to the VMware vSphere ESXi hosts.

You can configure the settings on each host individually using the VMware vSphere client to configure the settings on all VMware vSphere ESXi hosts.

The following advanced settings are available:

Setting Value

Disk.UseDeviceReset 0

NFS.MaxVolumes 256

Net.TcpipHeapSize 32

Net.TcpipHeapMax 512

Prerequisites

If configuring with the script, verify that the VMware PowerCLI is installed on a workstation with administrative access to VMware vCenter

Obtain the IP address and local root user credentials for the VMware vSphere ESXi host or appropriate administrative credentials to the VMware vCenter

Steps

1. In the VMware vSphere client, select the host.

2. Select the Configuration tab.

3. Under Software, select Advanced Settings.

4. Set the parameters in the window.

5. To configure the settings on each VMware vSphere ESXi host in the VMware vCenter using the script:

a. Verify that VMware vSphere PowerCLI is installed on a Microsoft Windows machine. b. Verify that you have network access to the VMware vCenter server. c. Copy the script to a .ps1 file on your hard drive.

d. Modify the $vcenter variable.

6. Execute the script in the VMware vSphere PowerCLI environment.

NOTE: This script does NOT set jumbo frames on the VMNICS. You must perform jumbo frame settings manually or

using another tool.

7. Review the modified Advanced Settings in the Advanced Settings section under the Configuration tab using the VMware vSphere Client on each VMware vSphere ESXi host.

Next steps

Reboot the VMware vSphere ESXi host.

Manage VMware vSphere ESXi 6.x 63

Configuring advanced settings for VMware vSphere ESXi (vSphere 6.5) Configure advanced VMware vSphere ESXi settings.

About this task

NFS performance is enhanced when advanced configuration options are set. Apply NFS options before connecting any NFS share to the VMware vSphere ESXi hosts.

You can configure the settings on each host individually using the VMware Host client.

The following advanced settings are available:

Setting Value

Disk.UseDeviceReset 0

NFS.MaxVolumes 256

Net.TcpipHeapSize 32

Net.TcpipHeapMax 512

Prerequisites

Obtain the IP address and local root user credentials for the VMware vSphere ESXi host.

Steps

1. Log in to VMware Host Client using browser.

2. Click Advanced Settings under the System tab. Search for the parameters that are displayed in the table and update the value.

3. Review the updated value in the Advanced Settings section under the System tab using the VMware Host Client on each VMware vSphere ESXi host.

Next steps

Reboot the VMware vSphere ESXi host.

Configure advanced settings for VMware vSphere ESXi (VMware vSphere 6.7) Configure advanced VMware vSphere ESXi settings.

About this task

NFS performance is enhanced when advanced configuration options are set. Apply NFS options before connecting any NFS share to the VMware vSphere ESXi hosts.

You can configure the settings on each host individually using the VMware Host client.

The following advanced settings are available.

Parameter Value

/Net/TcpipHeapSize 32

/Net/TcpipHeapMax 512

/NFS/MaxVolumes 256

/NFS/HeartbeatFrequency 12

/NFS/HeartbeatTimeout 5

64 Manage VMware vSphere ESXi 6.x

Parameter Value

/NFS/HeartbeatDelta 5

/NFS/HeartbeatMaxFailures 10

Prerequisites

Obtain the IP address and local root user credentials for the VMware vSphere ESXi host.

Steps

1. Log in to the VMware Host Client using a browser.

2. Click Advanced Settings under the System tab. Search for the parameters displayed in the table and update the value.

3. Review the updated value in the Advanced Settings section under the System tab using the VMware Host Client on each VMware vSphere ESXi host.

4. Restart the VMware vSphere ESXi host.

Restoring default values for VMware vSphere ESXi advanced settings (vSphere 6.0) Use this procedure to restore the advanced settings for VMware vSphere ESXi to their default values.

Steps

1. In the VMware vSphere client, select the host.

2. Select the Configuration tab.

3. Under Software, select Advanced Settings.

4. Restore the parameters in the window to their default settings.

NOTE: For parameters that have numerical values, the default setting is most often the minimum value.

Restoring default values for VMware vSphere ESXi advanced settings (vSphere 6.5) Use this procedure to restore the advanced settings for VMware vSphere ESXi to their default values.

Steps

1. In the VMware Host Client, select Manage in navigator pane.

2. Click Advanced Settings under the System tab. Search for the appropriate parameters.

3. Restore the parameters in the window to their default settings.

NOTE: For parameters that have numerical values, the default setting is most often the minimum value.

Restoring default values for VMware vSphere ESXi advanced settings (VMware vSphere 6.7) Use this procedure to restore the advanced settings for VMware vSphere ESXi to their default values.

Steps

1. In the VMware Host Client, select Manage in navigator pane.

2. Click Advanced Settings under the System tab. Search for the appropriate parameters.

3. Restore the parameters in the window to their default settings.

Manage VMware vSphere ESXi 6.x 65

NOTE: For parameters that have numerical values, the default setting is most often the minimum value.

Hardening security on VMware vSphere ESXi hosts About this task

For information on hardening security on the VMware vSphere ESXi hosts, refer to the VMware vSphere Security Hardening Guides.

Increasing the disk timeout on Microsoft Windows VMs Increase the amount of time for a Microsoft Windows VM to wait for unresponsive disk I/O operations.

About this task

Increase the disk timeout value to 190 seconds. VMware tools, version 3.0.2 and later sets the value to 60 seconds. Include this registry setting on all Microsoft Windows VMs and templates to accommodate unresponsive disk I/O operations. For more information, refer the VMware Knowledge Base entry 1014.

Steps

1. Using the Microsoft regedit application, navigate to HKEY_LOCAL_MACHINE > /System > /CurrentControlSet > Services > / Disk.

2. Right-click and select New > DWORD (32-bit) Value.

3. Type the value name TimeOutValue. The name is case sensitive.

4. Set the data type to REG_DWORD.

5. Set the data to 190 (decimal).

6. Reboot the VM.

Installing vCenter Server root certificates on web browser (vSphere 6.5) Install the trusted root certificate authority (CA) certificates.

About this task

Install trusted root certificate authority (CA) certificates. This procedure is applicable for Internet Explorer only. For browsers other than Internet Explorer, refer to respective browser documentation.

Steps

1. Open the Internet Explorer web browser and go to https://vcsa_fqdn.

2. In the vCenter getting started page, select Download trusted root CA certificates and save the file locally.

3. Unzip the downloaded files.

4. Right click on each .crt file and click Open. In the pop up dialog click Install Certificate. Select Local Machine and click Next, Next, and Finish.

NOTE: For more information, refer the VMware Knowledge Base article 2108294.

66 Manage VMware vSphere ESXi 6.x

Install vCenter Server root certificates on web browser (vSphere 6.7) Install trusted root certificates on Internet Explorer only. For browsers other than Internet Explorer, refer to respective browser documentation.

Steps

1. Open Internet Explorer and enter the following URL: https://vcenter_fqdn.

2. From the VMware vCenter Server getting started page, select Download trusted root CA certificates and save one or more files locally.

3. Unzip the downloaded files.

4. Right-click each .crt file and click Open. In the window that appears, click Install Certificate.

5. Select Local Machine and click Next > Next > Finish.

Exact steps may differ depending on the version of the browser. For additional information, see VMware Knowledge Base article 2108294.

Setting up Java and Internet Explorer on the management workstation or VM (vSphere 6.x) Set up Java and Internet Explorer version 11 on the management workstation or VM (element manager) if Unisphere or other web-based applications fail to launch. Configure the Java security setting to support web-based applications.

Prerequisites

vSphere 6.0: Ensure Java version 7 Update 51 or later is installed on the management workstation or VM. vSphere 6.5: Ensure Java version 8 Update 131 or later is installed on the management workstation or VM. Ensure the Java security level complies with your corporate security policy.

Steps

1. Using administrative privileges, log on to Microsoft Windows on the management workstation or virtual machine.

2. Navigate to the Java Windows Control Panel.

3. Select the Security tab.

4. Set the security level to the lowest setting (least secure).

5. Click Edit Site List... which opens in the Exception Site List popup window.

6. Add the URLs of web-based applications. For example: https://ip_address_of_web_based_application 7. Click OK to close the Exception Site List popup window.

8. Click OK to close the Java Windows Control Panel.

Manage VMware vSphere ESXi 6.x 67

Manage VMware Single Sign On (VMware vSphere 6.x)

VMware vCenter Single Sign On (SSO) is an authentication mechanism used to configure security policies and lock out or disable an account for VMware vSphere 6.5. Default policies do not require modification. You may have to modify policies or accounts if regulations require different policies or when troubleshooting a problem.

VMware vCenter SSO overview VMware vCenter SSO is an authentication mechanism used to configure security policies and lock out or disable an account for VMware vSphere. Default policies do not require modification. However, you might have to modify policies or accounts if regulations require different policies or if you are troubleshooting a problem.

Manage the lockout status of VMware Single Sign On (VMware vSphere 6.5) View the lockout status of a VMware Single Sign On (SSO) account for VMware vSphere.

Steps

1. Log in to the VMware vSphere Web Client as a VMware SSO administrator. By default, the VMware SSO administrator username is administrator@vsphere.local.

2. From the home page, select Administration > Single Sign-On > Users and Groups.

3. Each tab shows information from the identity sources about configured accounts on the system. Select the Users tab.

4. The Locked or Disabled columns show the status of each configured VMware SSO account. Right-click the appropriate account and select Enable/Disable or Unlock.

NOTE: The Locked Users and Disabled Users tabs provide information for the identity sources only.

5. Click Yes to confirm.

Manage the lockout status of VMware Single Sign On account (VMware vSphere 6.7) View the lockout status of a VMware Single Sign On (SSO) account for VMware vSphere.

About this task

By default, the VMware SSO administrator username is administrator@vsphere.local.

Steps

1. Log in to the VMware vSphere Client (HTML5) as a VMware SSO administrator.

2. Navigate to Menu > Administration > Single Sign-On > Users and Groups.

3. Each tab shows information from the identity sources about configured accounts on the system. Select the Users tab.

4. Select vSphere.local as the domain.

5. The Locked or Disabled columns show the status of each configured VMware SSO account. Click the ellipsis vertical bar to Enable/ Disable or Unlock.

6. Click Yes to confirm.

9

68 Manage VMware Single Sign On (VMware vSphere 6.x)

Manage VMware Single Sign On default password policies (VMware vSphere 6.0 or 6.5) Manage the VMware Single Sign On (SSO) default password policies for VMware vSphere.

About this task

By default, the VMware SSO passwords expire after 365 days, including the VMware SSO administrator password. You can modify the expiration policy.

Steps

1. Log in to the VMware vSphere Web Client as a VMware SSO administrator. By default, this user is administrator@vsphere.local.

2. From the home page, select Administration > Single Sign-On > Configuration.

3. Select the Policies tab and click Password Policies.

4. To modify the password policy, click Edit.

5. Make the required changes and click OK.

Manage VMware vCenter SSO default password policies (VMware vSphere 6.7) Modify the strict lockout policy of VMware vCenter SSO for VMware vSphere 6.7.

Steps

1. Log in to the VMware vCenter Client (HTML5) as an SSO administrator. By default, this user is administrator@vsphere.local.

2. Navigate to Menu > Administration > Single Sign-On > Configuration.

3. Select the Policies tab and click Password Policies.

4. To modify the lockout policy, select Edit.

5. Make the required changes and click OK.

Manage VMware Single Sign On lockout policies (VMware vSphere 6.5) Modify the strict lockout policy of VMware Single Sign On (SSO) for VMware vSphere 6.5.

Steps

1. Log in to the VMware vSphere Web Client as a VMware SSO administrator. By default, this user is administrator@vsphere.local.

2. From the home page, select Administration > Single Sign-On > Configuration.

3. Select the Policies tab and then select Lockout Policy to view the current lockout policies.

4. To modify the lockout policy, select Edit.

5. Make required changes and click OK.

Manage VMware Single Sign On (VMware vSphere 6.x) 69

Manage VMware Single Sign On lockout policies (VMware vSphere 6.7) Modify the strict lockout policy of VMware Single Sign On (SSO) for VMware vSphere 6.7.

Steps

1. Log in to the VMware vSphere (HTML5) Client as a VMware SSO administrator (default account is administrator@vsphere.local).

2. Navigate to Menu > Administration > Single Sign-On > Configuration.

3. Select the Policies tab and select Lockout Policy.

4. Click Edit.

5. Make any changes and click OK.

Add an AD identity source to VMware Single Sign On (IPv4) (VMware vSphere 6.7) Use this procedure to associate a Windows AD to the VMware SSO service embedded on the VMware vCenter Server. This procedure applies to Embedded PSC Deployments and to separate VMware PSCs for external deployments.

Prerequisites

Obtain network access to the VMware vSphere vCenter Web Client and use AD domain admin privileges.

Embedded deployments 1. Log in to the VMware vSphere Client (HTML5) on the element manager VM using the administrator@vsphere.local

account at: https:// /ui/ 2. Go to Menu > Administration. 3. Select Single Sign On > Configuration > Active Directory Domain. 4. For Embedded PSC deployment, select vCenter server with Embedded PSC and click Join AD. 5. Enter the AD domain, username, and password (with appropriate AD domain administrative rights). 6. Leave Organizational unit blank and click OK. 7. Restart the node.

External deployments 1. Log in to the VMware vSphere Client (HTML5) on the element manager VM using the administrator@vsphere.local account at:

https:// /ui/ 2. Go to Menu > Administration. 3. Select Single Sign On > Configuration > Active Directory Domain. 4. For each PSC:

Select the PSC to join to the AD domain and click JOIN AD. Leave Organizational unit blank and click OK. Log in to https:// :5480/ as root.

Restart the appliance. 5. Select the Identity Sources tab and click ADD IDENTITY SOURCE to enter details for the Active Directory domain being added. 6. Select the Active Directory (Integrated Windows Authentication) under Identity source type. 7. Verify that the domain name that was previously registered to the PSC is assigned to this AD domain registration. 8. Click Use machine account > OK. 9. Select the added AD domain and click SET AS DEFAULT. 10. Log in to VMware vCenter Server through the VMware vSphere Client (HTML5) as the administrator@vsphere.local

administrative user. 11. Assign administrator roles and permissions for domain user accounts or groups that require access to VMware vCenter 6.5.

70 Manage VMware Single Sign On (VMware vSphere 6.x)

By default, only the administrator@vsphere.local account can access VMware vCenter Server until similar permissions are explicitly assigned to domain users.

Add Windows AD identity source to VMware SSO (VMware vSphere 6.7) Associate a Windows AD to the VMware SSO service embedded on the VMware vCenter Server in Embedded PSC Deployments and on separate VMware PSCs for external deployments.

Prerequisites

Obtain network access to the VMware vCenter Client (HTML5) and use AD domain admin privileges.

Procedure for Embedded deployments 1. Log in to the VMware vSphere Client (HTML5) on the element manager VM using the using the

administrator@vsphere.local account at: https:// /ui/ 2. Navigate to Menu > Administration. 3. Select Single Sign On > Configuration > Active Directory Domain. 4. For Embedded PSC deployment, select vCenter server with Embedded PSC and click Join AD. 5. Enter the AD domain, username and password (with appropriate AD domain administrative rights). 6. Leave Organizational unit blank and click OK. 7. Restart the node.

Procedure for External deployments 1. Log in to the VMware vSphere Client (HTML5) on the element manager VM using the using the administrator@vsphere.local

account at: https:// /ui/ 2. Navigate to Menu > Administration. 3. Select Single Sign On > Configuration > Active Directory Domain. 4. Perform the following for each PSC:

Select the PSC to join to the AD domain and click JOIN AD. Leave Organizational unit blank and click OK. Log in to https:// :5480/ as root. Restart the appliance.

5. Select the Identity Sources tab and click ADD IDENTITY SOURCE to enter details for the Active Directory domain being added. 6. Select the Active Directory (Integrated Windows Authentication) under Identity source type. 7. Verify that the domain name that was previously registered to the PSC is assigned to this AD domain registration. 8. Click Use machine account > OK. 9. Select the added AD domain and click SET AS DEFAULT.

While logged in to VMware vCenter Server through the VMware vSphere Client (HTML5) as the administrator@vsphere.local administrative user, assign administrator roles and permissions for domain user accounts or groups that require access to VMware vCenter 6.7.

By default, only the administrator@vsphere.local account can access VMware vCenter Server until additional permissions are explicitly assigned to domain users.

Backing up or restoring the vCenter Server Back up or restore the VMware vCenter PSC for VMware vSphere 6.x. It is recommended to use VCSA Native backup to backup and restore the VMware vCenter server.

About this task

Maintaining a back-up of the PSC configuration ensures continued VMware vSphere access for VMware vCenter Server components. For backup and restore guidelines, see the following:

Manage VMware Single Sign On (VMware vSphere 6.x) 71

File-Based Backup and Restore of vCenter Server Appliance: https://docs.vmware.com/en/VMware-vSphere/6.7/ com.vmware.vcenter.install.doc/GUID-3EAED005-B0A3-40CF-B40D-85AD247D7EA4.html

Image-Based Backup and Restore of a vCenter Server Environment: https://docs.vmware.com/en/VMware-vSphere/6.7/ com.vmware.vcenter.install.doc/GUID-1C73996F-8312-4BBD-A16C-B2C8FC3C0D31.html

Steps

1. Follow the back-up and restore procedure in the VMware knowledge base article KB 2149237.

2. Refer to the Backing Up and Restoring vCenter Server section in the VMware vSphere 6.x Documentation Center, which you can find here:

ESXi and vCenter Server 6.x Documentation > vSphere Installation and Setup > Backing Up and Restoring vCenter Server.

Backing up and restoring the vCenter Server and PSC (vSphere 6.5) The VMware vCenter Server 6.5 supports file-based and image-based backups. You can initiate backup and restore jobs using the GUI or API interfaces. Dell EMC recommends using VCSA native file-based backup to backup/restore PSC/vCenter Server. Dell EMC also recommends following the procedure to recover failed PSCs. All PSCs/VCs in an SSO domain must be backed-up.

A recent backup must be available locally in the recovery site. VCSA Installer of the same version or build should be available for recovery operation. The failed PSC must be powered off and removed from vCenter inventory.

Backing up the PSC and vCenter Server Refer to the File-Based Backup and Restore of vCenter Server Appliance section in the VMware vSphere 6.5 Documentation Center.

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-3EAED005-B0A3-40CF- B40D-85AD247D7EA4.html

Restoring the vCenter Server Refer to the following VMware procedure for file-based restoring to restore the vCenter server.

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-F02AF073-7CFD-45B2-ACC8- DE3B6ED28022.html

Restoring the PSC Complete this task to restore the PSC.

About this task

You must repoint a VMware vCenter server connected to a failed PSC to a surviving PSC to restore vCenter services.

Steps

1. Run the installer of same version/build.

2. Select the restore option.

3. Enter the backup details such as location of the backup files, protocol used with port number, and credentials.

4. Review the backup information and provide the appliance deployment target ESXi.

5. Provide the hostname of the failed PSC and select the deployment size.

6. Select data store and review network settings.

7. Select Finish to start the restoration.

72 Manage VMware Single Sign On (VMware vSphere 6.x)

Redirect VMware vCenter Server to the secondary external VMware Platform Services Controller (VMware vSphere 6.x) For VMware vSphere 6.x, repoint the VMware vCenter Server for authentication under the following conditions: the primary external VMware Platform Services Controller (PSC) fails, there are multiple VMware PSCs replicating, and the PSCs are configured without fault tolerance.

NOTE: VMware vSphere 6.7 is the last VMware vSphere release to support the deployment of external VMware PSCs.

Updates to VMware vSphere 6.x support Enhanced Linked Mode in embedded VMware PSCs, making external VMware

PSCs no longer necessary. Upgrading to VMware vSphere 6.7 update 1 or VMware vSphere 6.5 update 2d enables you to

migrate external VMware PSCs to embedded VMware PSCs. For more information about changing to embedded

VMware PSCs from external VMware PSCs, consult with your Dell Technologies Sales Engineer.

See the Repointing the Connections Between vCenter Server and PSC section of the VMware vSphere Installation and Setup Guide.

Enabling fault tolerance for the external PSC Enable fault tolerance on the external PSC for VMware vSphere 6.x.

About this task

For multiple PSCs, you can create fault tolerant pairing to provide continuous availability for VMware vCenter Server instance authentication.

Prerequisites

1. Read the Providing Fault Tolerance for Virtual Machines section in the VMware vSphere Availability Guide from the VMware vSphere 6.x Documentation Center.

2. Review and resolve all validation and compliance checks needed to ensure fault tolerance is operational. 3. Confirm the PSC VM CD/DVD drive is set to Client Device. 4. Confirm that the VMKernel flagged for fault tolerance logging is created on all appropriate ESXi hosts.

Steps

Follow the Turn On Fault Tolerance procedure in the VMware vSphere Availability Guide of the VMware vSphere 6.x Documentation Center.

Manage VMware Single Sign On (VMware vSphere 6.x) 73

Manage virtualization

Patch VMware vSphere ESXi hosts with the VUM (VMware vSphere 6.0) Patch the VMware vSphere ESXi hosts with VUM.

About this task

Complete this procedure when a new VMware vSphere ESXi host is deployed or requires an update.

Prerequisites

Verify that the patch bundle is listed on the latest version of the Converged Systems Release Certification Matrix.

Steps

1. Set the VMware vSphere ESXi host to Maintenance mode.

2. In the VMware vSphere client, select a host and go to Update Manager > Admin View > Configuration > Patch Download Settings.

3. From the Patch Download Sources window, click Import Patches.

4. From the Select Patches window of the Import Patches wizard, browse to where you saved the patch or package software bundle, and select the file.

5. Click Next and wait until the file upload successfully completes. If the upload fails, verify that the structure of the .zip file is correct or verify that the VUM settings are correct.

6. Click Next.

7. From the Confirm Import window, verify that the package imported into the VUM repository, and click Finish.

8. Select the Patch Repository tab and search for the package and verify that the import worked.

9. Select the Baselines and Groups tab and click Create to create a baseline.

10. From the New Baseline wizard, in the Name field, type the package name. For example, PowerPath.

11. For Host Baselines, click Host Extension.

12. Click Next.

13. Find the package extension and click the down arrow to add it to the Extensions to Add field.

14. Click Next and Finish.

15. You can attach the package baseline to individually selected VMware vSphere ESXi hosts or to multiple hosts at a time by selecting the cluster.

To attach the package baseline to several VMware vSphere ESXi hosts:

a. Go to the Compliance view and select the host that you want from the list to the left of the vSphere client window. Select a folder, cluster, or data center.

b. In the right window, select Update Manager and then click Attach. c. From the Attach Baseline or Group window, under Name, select the package baseline that you created. d. Click Attach.

16. Select Scan, and check the circle in the Compliance box on the upper right side of the screen.

If the circle is... Then...

Blue You have attached the baseline to the VMware vSphere ESXi host for the first time.

10

74 Manage virtualization

If the circle is... Then...

Green You have already attached baselines to the VMware vSphere ESXi host and remediated them. The 100% compliant indicator shows that the extension is already installed.

Red Stage and remediate the baseline (as described in Step 17) to achieve compliance. To verify the remediation, review the information in the Recent Tasks window, or click the Tasks/Event tab.

17. Staging is the process of pushing the package onto individual VMware vSphere ESXi hosts from the VUM server. To stage the baseline:

a. In the Update Manager tab, in the Attached Baselines list in the middle of the screen, select the package baseline that you created, and click Stage.

b. Click Stage. When the Stage Wizard appears, under the Name column in the Baselines list, the package baseline that you created is selected by default.

NOTE: Do not change the default Name selection. In the Host column, all the VMware vSphere ESXi hosts to

which you attached the package baseline are selected by default.

c. Optionally, change the default Host selection to stage the baseline to only one or some of the VMware vSphere ESXi hosts. d. Click Next. e. From the Patch and Extension Exclusion window, verify the information and click Next. f. From the Ready to Complete window, verify the information and click Finish.

18. To remediate the package baseline, perform the following:

a. Select the VMware vSphere ESXi host to remediate.

NOTE: When you remediate the package baseline, packages are installed on hosts that do not have the package.

The package is updated on hosts that have an outdated package.

b. In the Attached Baselines area, select the package baseline that you created and click Remediate. From the Remediate window, in the Baseline Groups and Types area, Extension Baselines is selected by default. In the Baselines list, the package baseline that you created is selected by default.

NOTE: Do not alter default selections. Under Host, all the VMware vSphere ESXi hosts to which you staged the

package baseline are selected by default.

c. Optionally, change the default Host selection to remediate the baseline to only one or some of the VMware vSphere ESXi hosts and click Next.

d. From the Patches and Extensions window, verify the information and click Next. e. From the Host Remediation Options window, in the Task Name field, type a task name.

For example, PowerPath/VE install.

f. In the Task Description field, type a description. For example, PP/VE 5.9 install.

g. Change or maintain remediation time and failure options values in the Remediation Time and Failure Options fields to suit your environment.

h. Click Next. The Ready to Complete window appears with your remediation selections.

i. Verify the information, and click Finish.

Patch VMware vSphere ESXi hosts with the VUM (VMware vSphere 6.5) Patch the VMware vSphere ESXi hosts with VUM.

About this task

Complete this procedure when a new VMware vSphere ESXi host is deployed or requires an update.

Prerequisites

Verify that the patch bundle is listed on the latest version of the Converged Systems Release Certification Matrix.

Manage virtualization 75

Steps

1. Log in to VMware vSphere Web client.

2. Select the VMware vSphere ESXi host, right-click, and select Maintenance mode > Enter Maintenance Mode.

3. In the vSphere Web Client, select the host and select the Update Manager tab.

4. Click Go to Admin View tab.

5. Click Settings.

6. Select Download Settings.

7. In the Download Sources pane, select Import Patches.

8. On the Select Patches File page of the Import Patches wizard, browse to the location where you saved the patch or package software bundle, select the file and click Open.

9. Click Next and wait until the file upload completes successfully. If the upload fails, the .zip file may have been corrupted during the download process or an incorrect .zip file may have been imported. Try downloading the .zip file again and then import.

10. Click Next.

11. On the Ready to complete page of the Import Patches wizard, verify the package that you imported into the VUM repository, and click Finish.

12. Select the Patch Repository tab.

13. Verify that the patch appears in the list.

14. Click the Host Baselines tab.

15. Click Create to create a baseline.

16. In the New Baseline wizard:

a. In the Name and type field, type the package name. For example, PowerPath.

b. For baseline type, click Host Extension. c. Click Next. d. In the Patch Options page, leave defaults selected and click Next. e. In the Criteria page, select Next. f. In the Patches to Exclude page, exclude all patches except PowerPath. g. In the Additional Patches page, click Next. h. Click Finish.

17. Attach the package baseline to the appropriate VMware vSphere ESXi hosts. You can attach the package baseline to individually selected VMware vSphere ESXi hosts or to multiple hosts. Select the cluster in the Inventory > Hosts and Clusters view. To attach the package baseline to an individual VMware vSphere ESXi host, go to the Compliance view. Select the host that you want from the list to the left of the vSphere Web Client pane. To attach the package baseline to several VMware vSphere ESXi hosts:

a. In the list to the left of the vSphere Web client pane, select a folder, cluster, or data center. b. In the right pane, select Update Manager tab and then click Attach Baseline. The Attach Baseline or Baseline Group window

opens. c. Under Individual Baselines page, select the package baseline that was created in Step 16 under Extension Baselines. d. Click OK.

18. Click Scan for Updates, and click OK. Check for the Compliance Status for the attached baseline.

19. Stage the baseline. Staging is the process of pushing the package onto individual VMware vSphere ESXi hosts from the VUM server. To stage the baseline:

a. In the Update Manager tab, in the Independent Baselines list, select the package baseline that was created. b. Click Stage Patches. c. When the Stage Patches Wizard appears, under the Baselines Name column in the Baselines list, the package baseline that

was created is selected by default. Do not alter the default Name selection. d. Click Next. e. In the Hosts window all the VMware vSphere ESXi hosts to which the package baseline is attached are selected by default. f. If required, alter the default Host selection to stage the baseline to only one or some of the VMware vSphere ESXi hosts. g. Click Next. h. In the Patch and Extension Exclusion window, verify the Package information and click Next. i. When the Ready to Complete window appears, verify the information and click Finish.

20. Remediate the package baseline. During this stage, packages are installed on hosts that do not have the package. The package is updated on hosts that have an outdated package. To remediate the baseline:

a. Select the VMware vSphere ESXi host to remediate and click Update Manager tab. b. In the Independent Baselines section, select the package baseline that was created and click Remediate.

76 Manage virtualization

c. From the Remediate page, in the Baseline Groups and Types section, Extension Baselines is selected by default. In the Baselines list, the package baseline that was created is selected by default. Do not alter the selections for default Baseline Groups and Types and Extension Baselines default selections.

d. Click Next. e. In the Select target objects page, all the VMware vSphere ESXi hosts to which the package baseline is staged are selected by

default. Optionally, alter the default Host selection to remediate the baseline to only one or some of the VMware vSphere ESXi hosts.

f. Click Next. g. When the Patches and Extensions window appears, verify the information and click Next. h. In the Advanced options page, click Next. i. Click Next. j. When the Ready to Complete window appears, verify the information and click Finish.

Patch VMware vSphere ESXi hosts with the VUM Patch the VMware vSphere 6.5 or later ESXi hosts with VUM from the VMware vCenter Client when a host is deployed or requires an update.

Prerequisites

Verify that the patch bundle is listed on the latest version of the RCM.

During remediation, packages are installed on hosts that do not have the package and/or the package is updated on hosts that have an outdated package.

Steps

1. Log in to VMware vCenter Client (HTML5) as administrator@vsphere.local .

2. Select Home > Hosts and Clusters.

3. Right-click the VMware vSphere ESXi host and select Maintenance Mode > Enter Maintenance Mode.

4. Select the host and the Updates tab.

5. In the Updates page, click Update Manager Home.

6. Select Updates > UPLOAD FROM FILE.

7. In the Import Patches window, click Browse to patch or package software bundle, select the file, and click Open.

8. Select the Baselines tab, and click New baseline.

9. In the Baseline Definition wizard:

a. In the Name field, type the package name. b. For the Content, select Patch and click Next. c. Select the Matched tab. d. In the patches list, clear all patches and select the patch for the baseline. To find the patch, apply column header filters and click

NEXT. e. In the Add Patches manually window, select Next > Finish.

10. Attach the package baseline to individually selected VMware vSphere ESXi hosts or to multiple hosts by selecting the cluster in the Inventory > Hosts and Clusters view.

Option A: To attach the package baseline to an individual VMware vSphere ESXi host, select the host from the left. Select the Updates tab.

Option B: To attach the package baseline to several VMware vSphere ESXi hosts, perform the following:

a. In the left-side inventory list, select a folder, cluster, or data center. b. In the right window, select the Updates tab and then select Host Updates. c. On the Attached Baselines window, select the package baseline that was previously created and click ATTACH. d. From the Attach list, select the baseline and click ATTACH.

11. Click Overview and under Hosts Compliance, and click CHECK COMPLIANCE.

12. Go to Host Updates to verify the Compliance Status for the attached baseline. If the status is non-compliant, remediate (patch) the host using the patches in the baseline.

13. To stage the baseline, perform the following:

a. In Host Updates, select the package baseline that is created in the Baselines list under Attached Baselines.

Manage virtualization 77

b. Click STAGE. c. From the Stage Patches Wizard, under Install in the Baselines list, verify that the package baseline that was created is

selected. d. In the Hosts pane, all the VMware vSphere ESXi hosts to which the package baseline is attached are selected by default. If

required, alter the default host selection to stage the baseline to only one or some of the VMware vSphere ESXi hosts and click OK.

14. To remediate the baseline, perform the following steps:

a. Select the VMware vSphere ESXi host to remediate and select the Updates tab. b. In Host Updates, under Attached Baselines, select the package baseline that was created and click REMEDIATE. c. In the Remediate window, review the remediation precheck report and address any issues.

All the VMware vSphere ESXi hosts to which the package baseline is staged are selected by default.

d. Click REMEDIATE.

Supported guest operating systems For information about installing supported guest operating systems in VMware VMs, see the VMware Guest Operating System Installation Guide.

If VMware VMs are being configured with IPv6 for VxBlock Systems, a vmxnet driver must be deployed. The deployment should occur automatically when VMware Tools are installed.

NOTE: IPv6 is not supported on VMware vSphere 6.5.

Use VMware Enhanced vMotion Compatibility with Cisco UCS blade servers Ensure Enhanced vMotion Compatibility (EVC) when upgrading Cisco UCS blade servers in a Converged System.

Do not mix Cisco UCS blade server types within a cluster. However, there are instances when it is necessary to mix blade types, including upgrades.

When upgrading Cisco UCS blade servers, consider the following guidelines:

Cisco B200 M1, M2, and B200 M3 UCS Blade Servers support EVC mode Intel Nehalem Generation (Xeon Core i7). Individual Cisco UCS blade servers support several EVC modes, but only Xeon Core i7 is a commonly supported mode across all three Cisco UCS blade servers. If the CPU feature sets are greater than the EVC mode you are enabling, power off all VMs in the cluster. Then, enable or modify the EVC mode.

Cisco UCS Blade Servers B200 M1 and M2 support some additional CPU features such as those features provided in 32-nanometer EVC mode. However, some features might not be enabled in the BIOS due to U.S. export rules. To ensure complete and reliable vMotion compatibility when mixing blade types in a single cluster, use Intel Xeon Core i7 EVC mode.

If all the Cisco UCS blade servers in the cluster have the same CPU type, set the EVC mode to CPU architecture. For example, if the cluster contains all Cisco UCS Blade Servers B200 M1, select Intel Xeon Core i7 EVC mode. Selecting this mode enables vMotion compatibility between Cisco UCS Blade Servers B200 M1 and other hosts. Enable EVC mode only if you are adding or planning to add hosts with newer CPUs to an existing cluster.

Set the EVC mode before you add Cisco UCS blade servers with newer CPUs to the cluster. Setting the EVX mode first eliminates the need to power off the VMs running on the blade servers. Setting a lower EVC mode than the CPU can support may hide some CPU features, which may impact performance. Proper planning is needed if performance or future compatibility within the cluster is the goal.

Enable VMware Enhanced vMotion Compatibility within a cluster Enable VMware Enhanced vMotion Compatibility (EVC) within a cluster.

About this task

The VMware EVC ensures vMotion compatibility for hosts in a cluster. VMware EVC verifies that all hosts in a cluster present the same CPU features to the VMs, even if the CPUs on the hosts are different. The EVC feature uses the Intel FlexMigration technology to mask

78 Manage virtualization

processor features so that hosts can present the feature set of an earlier generation of processors. This feature is required if hosts in a cluster use both Cisco UCS C200 and C220 Rack Servers.

Prerequisites

Before enabling VMware EVC on an existing cluster, ensure that the hosts in the cluster meet requirements. See EVC Requirements in the VMware vSphere ESXi and vCenter Server Documentation.

Steps

1. You can optionally create an empty cluster. If you have already created a cluster, skip this step.

Creating an empty cluster is the least disruptive method of creating and enabling a VMware EVC cluster.

2. Select the cluster for which you want to enable VMware EVC.

3. If the VMs are running with more features than the EVC mode you intend to set, power off the VMs. Then enable EVC and migrate the VMs back into the cluster after enabling VMware EVC.

4. Power off all the VMs on the hosts with feature sets greater than the VMware EVC mode.

5. Migrate the cluster VMs to another host.

6. Edit the cluster settings, and enable EVC.

7. Select the CPU vendor and feature set appropriate for the hosts in the cluster.

8. If you powered off and migrated VMs out of the cluster, turn on the VMs in the cluster and migrate the VMs back into the cluster.

Manage the VMware vCenter HA configuration VMware vCenter HA protects a VMware vCenter Server Appliance (vCSA) against host and hardware failures. The active-passive architecture may reduce downtime when updating a VMware vCSA.

After you configure your VMware vCenter HA cluster, you can perform management tasks such as certificate replacement, SSH key replacement, and SNMP setup. You can also edit the cluster configuration to disable or enable VMware vCenter HA, enter maintenance mode, and delete the cluster configuration.

If your cluster contains fewer than four hosts, you can enable a witness/vCenter or vCenter/vCenter to migrate to the same host. Adjust the DRS rules during maintenance activities to enable this same-host migration. After maintenance activity is complete, reenable the DRS rules as soon as possible. Place all vCenter HA VMs back on separate hosts.

For VMware vSphere 6.7, see the following:

Manage vCenter HA configuration vCenter High Availability

For VMware vSphere 6.5, see the following:

Manage the vCenter HA configuration vCenter High Availability

Convert external VMware Platform Service Controllers to embedded Convert external VMware Platform Service Controllers (PSC) to embedded VMware PSCs for VMware vSphere 6.x.

About this task

Internalize VMware PSCs to simplify the topology.

Prerequisites

For VMware vSphere 6.7, use the convergence tool provided in VMware vSphere Server Appliance (vCSA) 6.7 update 1 or later installer ISO.

For VMware vSphere 6.5, validate that all the VMware vSphere PSCs and VMware vSphere ESXi hosts are upgraded to VMware vSphere 6.5u2d or later.

Back up the external VMware PSC and the VMware vCenter Server.

Manage virtualization 79

For the VMware documentation related to this procedure, see Converging to an Embedded Platform Services Controller Node Using the Command-Line Utility.

Steps

1. Log in to the VMware vCenter Server using the HTML5 Web Client as administrator@vsphere.local 2. Select Hosts and Clusters and right-click AMP Cluster Edit DRS and change the DRS setting from Fully Automated to Manual

on the AMP cluster and click OK.

3. Mount the VMware vCSA 6.7 update 1 or later or VMware vCSA 6.5 update 2d Installer ISO on the Element Manager VM.

4. Connect to the Element Manager using RDP and copy the DVD:/vcsa-converge-cli folder to the desktop.

5. Browse to Desktop\vcsa-converge-cli\templates\converge and open the converge.json file in WordPad.

6. Edit converge.json and update the VMware vSphere ESXi and VMware vSphere vCenter credentials.

a. Replace text inside < > with the appropriate values.

Password fields left blank result in a prompt.

b. If the VMware PSC is joined to an AD domain, update the ad_domain_info. If not, delete the section from the file.

c. Save the file.

7. From the command prompts to change the directory, type:

cd C:\Users\Administrator\Desktop\vcsa- converge-cli\win32

8. To run vcsa-installer.exe, type:

\vcsa-util.exe converge --verify-template-only C:\Users\Administrator\Desktop\vcsa-converge- cli\templates\converge\converge.json

9. If validation is successful, run the command again without the verify-template-only option. If the validation is unsuccessful, fix the errors in the json file and run the command with verify-template-only until the result is successful.

10. When prompted with Did you back up the participating PSC and VC nodes?, type y and press Enter.

11. When prompted with Do you accept the thumbprint?, type 1 and press Enter.

VMware vCenter Server is inaccessible for 10 minutes after successful completion of the migration.

12. To verify that the VMware vCenter Server has an embedded PSC, log in to the management interface:

https:// :5480/

13. Log in to the VMware vCenter Server using the Web client for VMware vSphere 6.5 or the HTML5 client for VMware vSphere 6.7.

14. Select Hosts and Clusters. Right-click the AMP cluster, and change the DRS setting back to Fully Automated.

Join Embedded Linked Mode domain To obtain additional information about Enhanced Linked Mode, see Joining a vCenter Embedded Linked Mode Domain.

Decommission external VMware Platform Service Controllers Decommission the external VMware Platform Service Controllers (PSCs) manually for VMware vSphere 6.x.

About this task

Decommission external VMware PSCs after internalizing the VMware PSC function into VMware vCHA.

Prerequisites

Validate that the external VMware PSC has converted to an embedded VMware PSC. Validate the VMware vCenter lookup service is using the internal VMware PSC.

1. Log in to VMware vCSA management interface at https:// :5480 as root.

80 Manage virtualization

2. Select Access Enable SSH and BASH shell. 3. Enter: shell and press Enter.

4. Log in to the VMware vCenter Server using the SSH client as root.

5. Enter: /usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location --server-name localhost 6. To validate that the VMware vCenter Server uses an internal lookup service, enter:

https:// /lookupservice/sdk

Steps

1. To power off the VMware PCSs and unregister the PSC, enter: cmsso-util 2. Log in to the VMware vCenter Server using the SSH client with VMware vCenter management credentials.

3. To unregister the external VMware PSC, enter:

cmsso-util unregister --node-pnid --username administrator@domain

4. To ensure that replication partners no longer exist, enter:

/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartners -h -u administrator

5. Repeat steps 3 and 4 to delete the remaining external VMware PSCs.

Configure the Virtual Flash Read Cache Configure the Virtual Flash Read Cache (VFRC) for each VM.

Steps

1. Using the VMware vSphere web client, open the Hosts and Clusters view.

2. Right-click the VM, and select Edit Settings.

3. In the Virtual Hardware tab, expand the VMDK that you want to configure with the VFRC.

4. In the Virtual Flash Read Cache field, type a value for the read cache configuration size for the VMDK. Specify the block size using the Advanced option.

5. Repeat Steps 1 - 4 for each VM and associated VMDK that requires VFRC. VMware vSphere does NOT prevent over provisioning. Consider the total available VFRC capacity when configuring the cache size.

Manage virtualization 81

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

The VMware VDS is an enterprise feature of VMware vSphere vCenter Server and requires that the VMware vSphere ESXi hosts are licensed with the VMware vSphere Enterprise Plus edition. A non-Enterprise Plus edition does not support VMware vSphere Distributed Switch (VDS) functionality. No additional license is required to be installed or managed for the VMware VDS.

Provision an existing VMware vSphere Distributed Switch Provision an existing VMware vSphere Distributed Switch (VDS) configuration for VMware vSphere 6.5 or later. You can use an automated workflow or the steps that are provided in this section to provision a VMware VDS.

NOTE: To perform the steps with an automated workflow using VxBlock Central Workflow Automation, see Vxblock

Central Workflow Automation library in the Dell EMC VxBlock Central Workflow Automation Reference Guide.

Modify a distributed port group Modify VMware vSphere Distributed Switch (VDS) distributed port group settings for VMware vSphere 6.5 or later.

About this task

Do not change standard configuration settings. Edit one distributed port group at a time. If several port groups require modification, you may use the VMware PowerCLI or vSphere vCLI or script tools.

The following settings can be modified:

Name VLAN ID Teaming and failover policy Traffic filtering Marking policies

Prerequisites

Identify the VMware VDS that contains the distributed ports. The default switch name is DVSwitch01-A.

Steps

1. Log in to the VMware vCenter Client (HTML5) as administrator@vsphere.local.

2. From the Home tab, click Networking.

3. Right-click the distributed port group and click Edit Settings.

4. See the following table for recommended settings:

Field Description

General Name: The name that is chosen for the distributed port group Port binding: Static Binding Port allocation: Elastic Number of ports: 8 (increases automatically if Elastic is selected for port allocation). Network resource pool: use default setting Description: Add details about distributed port groups.

11

82 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Field Description

Advanced Configure reset at disconnect: Enabled Override port policies: use default setting

VLAN VLAN type: VLAN VLAN ID: Consult your Dell Technologies Sales Engineer

Security Promiscuous mode: Reject MAC address changes: Reject Forged transmit: Reject

Teaming and failover Load balancing: Route based on originating virtual port. The vMotion port group has only one active uplink (associated with vNIC2 Fabric A) and is set to use explicit failover order. The other uplink should be in standby mode.

Traffic shaping Leave at default setting.

Monitoring Leave at default setting.

Miscellaneous Leave at default setting.

5. To edit the Traffic filtering and Marking, perform the following steps:

a. Select the port group, and go to the Configure tab. b. Under Settings, select Traffic Filtering and Marking. c. Click ENABLE AND REORDER. d. In the Enable and Reorder Traffic Rules window, turn on Enable all traffic rules. e. Click OK. f. Click +Add to include the following traffic rules:

Status: Enable this option for Management, vMotion, and NFS distributed port groups. All other port groups should be disabled. Name: Management Traffic Rule

Action tag COS value checkbox is selected. Set CoS to 6 DSCP value checkbox is selected. Set DSCP to 48 Set traffic direction to Ingress.

NOTE: See the VMware vSphere Release Notes for information about ingress and egress parameters.

Traffic qualifier: System Traffic Enable Qualifier: Enabled System Traffic: Management

Name: NFS Traffic Rule

Action tag COS value checkbox is selected. Set CoS to 2 DSCP value checkbox is selected. Set DSCP to 16 Set traffic direction to in Ingress

NOTE: See the VMware vSphere Release Notes for information about ingress and egress parameters.

Traffic qualifier: IP Enable Qualifier: Enabled Protocol number: Any

Name: vMotion Traffic Rule

Action tag COS value checkbox is selected. Set CoS to 4 DSCP value checkbox is selected.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 83

Set DCSP to 26 Set traffic direction to Ingress.

NOTE: See the VMware vSphere Release Notes for information about ingress and egress parameters.

Traffic qualifier: System Traffic Enable Qualifier: Enabled System Traffic: vMotion

Create a distributed port group Create and add virtual VMkernel distributed port groups to an existing VMware VDS for VMware vSphere 6.5 or later.

About this task

Steps

1. Log in to the VMware vCenter Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, click Networking.

3. Right-click DVSwitch01-A and select New Distribution Port Group.

4. From the New Distributed Port Group wizard, perform the following:

a. Enter the name of the distributed port group and click Next. b. Leave Port binding and Port allocation to the default settings Static binding and Elastic. c. Verify Number of Ports is set to eight. d. Set the VLAN type to VLAN and change the VLAN ID. e. Enable Customize default policies configuration. f. Verify Security and Traffic shaping are set to the default. g. For the Teaming and failover section, the following table lists settings for load balancing and uplinks:

Port Group Active uplinks Standby uplinks Unused uplinks Load Balancing

vcesys_esx_mgmt Uplink1

Uplink2

Uplink3

Uplink4

N/A N/A Originating virtual port

vcesys_esx_vmotion Uplink1

Uplink3

Uplink2

Uplink 4

N/A Explicit Failover

vcesys_esx_ft Uplink2

Uplink4

Uplink1

Uplink3

N/A Originating virtual port

vcesys_esx_nfs Uplink1

Uplink2

Uplink3

Uplink4

N/A N/A Originating virtual port

external data Uplink1

Uplink2

Uplink3

Uplink4

N/A N/A Originating virtual port

h. Verify Monitoring and Miscellaneous are set to the default. Do not edit any other settings. i. Click NEXT to view the Ready to complete dialog.

84 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Virtual distributed port groups can be assigned to the VMs. VMkernel distributed port groups require configuration.

Configure a VMkernel interface Configure a VMkernel (Management, vMotion, NFS, or FT) interface for VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

Steps

1. Log in to the VMware vCenter HTML5 Client as administrator@vsphere.local.

2. From Home tab, select Hosts and Clusters.

3. Select the VMware ESXi host, and click the Configure tab.

4. Under Networking, select VMkernel adapters.

5. In the VMkernel adapters window, click Add host networking.

a. Select VMkernel Network Adapter and click Next. b. Under Select an existing network, click Browse. c. Select the port group, and click OK and Next. d. Select the TCP/IP stack and click Next.

For vMotion, select vMotion TCP/IP stack For NFS, select Default TCP/IP stack For FT, ensure that Default TCP/IP, Fault Tolerance Logging service is enabled.

e. Choose IPv4 or IPv6 for IP Settings, enter the IPv4 or IPv6 address and subnet mask, and click Next.

Dual IP stack is not supported.

f. At Ready to Complete, verify the settings and click Finish.

Associate VMware vSphere ESXi hosts Associate a new VMware vSphere ESXi host to an existing VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

Prerequisites

Add VMNICs to the VMware VDS uplinks. From the Add and Manage Hosts wizard, you can associate the VMware vSphere ESXi hosts to the VMware VDS. Verify which VMware VDS to associate with the VMware vSphere ESXi host.

Steps

1. Log in to the VMware vSphere HTML5 Client (HTML5) as administrator@vsphere.local.

2. Select the Home tab and click Networking.

3. Right-click DVSwitch01-A and select Add and Manage Hosts.

4. From the Add Hosts wizard, perform the following:

a. Select Add Hosts and click Next. b. Select New Hosts. c. In the Select new hosts window, select the VMware vSphere ESXi host and click OK.

You can modify multiple VMware vSphere ESXI hosts at a time using the Add and Manage Hosts wizard.

d. Verify that the selected host is displayed in the list and click Next. e. From the Manage physical adapters page, select the following uplinks:

Uplink 2 for vmnic1 and click OK. Uplink 3 for vmnic2 and click OK. Uplink 4 for vmnic3 and click OK

NOTE: Disjoint Layer 2 configurations use VMNIC 4 and 5, respectively.

f. Click Next.

5. Review the Summary results and click Finish.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 85

After adding the host to the VDS, migrate the management VMkernel port and VMNIC 0 to uplink1 on the VMware VDS.

Configure jumbo frames Configure jumbo frames on an existing VMware vSphere Distributed Switch (VDS).

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. Select the Home tab, click Networking.

3. Right-click DVSwitch01-A and select Settings > Edit Settings\.

4. From the Properties tab, select Advanced.

5. Change the MTU value from 1500 to 9000 and click OK.

Modify CoS settings The CoS marking is part of the standard configuration and configured for VMware vSphere 6.5 and later.

About this task

Modify CoS settings for the following distributed port groups:

vcesys_esx_mgmt vcesys_esx_vmotion vcesys_esx_nfs

Steps

1. Log in to the VMware vCenter Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, click Networking.

3. Expand the DVswitch01-A to view the port groups.

4. Select the distributed port group, and select the Configure tab.

5. Select Traffic filtering and marking.

6. Click ENABLE AND REORDER.

7. In the Enable and Reorder Traffic Rules window, turn on Enable all traffic rules and click OK.

8. Click +ADD to open New Traffic Rule wizard.

9. Use the following table to modify settings for each port group:

Traffic setting vcesys_esx_mgmt vcesys_esx_vmotion vcesys_esx_nfs

Name MgmtCOS vMotionCOS NFSCOS Action Tag

Update CoS tag Enable and change value to 6 Enable and change value to 4 Enable and change value to 2 Update DSCP tag Enable and set to 48. Enable and set to 26 Enable and set to 16 Traffic direction Change to Ingress.

Traffic Qualifiers Select System Traffic and Enable Qualifier.

Select System Traffic and Enable Qualifier.

Select IP and Enable Qualifier.

System traffic Set to Management Set to vMotion N/A

Protocol number N/A N/A Select Any.

10. Click OK and repeat the process to modify other port groups.

86 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Decommission VMware vSphere Distributed Switch components For VMware vSphere 6.5 or later, to remove a VMware vSphere Distributed Switch (VDS), delete distributed port groups and dissociate VMware vSphere ESXi hosts.

Delete a distributed port group Reassign all VMs for the distributed port group to a different distributed port group for VMware vSphere 6.5 or later.

Before you delete the port group, ensure that there are no VMs or NIC numbers assigned.

Migrate the VMkernel ports from the VMware vSphere ESXi host that is attached to the VMware vSphere Distributed Switch (VDS).

Migrate VM distributed port group assignments to a different switch Migrate VMs on the distributed port group to a different VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

About this task

Use the VM migration wizard to migrate port group types.

Use the VM migration wizard to migrate the following:

VMware vSphere Standard Switch to VMware VDS VMware vSphere Distributed Switch to VMware VDS

CAUTION: A disconnection may cause the loss of the VMware vCenter Server, which could prevent the VM port group

from migrating.

Prerequisites

VMware vSphere ESXi hosts attached to an existing VMware VDS contain VMs that are powered on. Verify that these VMs are not assigned to any distributed port groups on the new VMware VDS.

Verify an available distributed port group to migrate the powered-on VMs.

If migrating to a different VMware VDS:

Attach at least one VMNIC as an uplink for a new distributed or standard switch. Create the distributed port groups with the same name and VLAN ID as the existing switch.

If migrating to a VMware vSphere Standard Switch:

Create a new standard switch and attach at least one VMNIC as an uplink for the standard switch. vNIC0 and vNIC1 connect to a different set of physical switches than vNIC2 and vNIC3. Do not add vNIC2 and/or vNIC3 to vSwitch0,

because it may cause the VMware vSphere ESXi host to lose network connectivity if management traffic gets switched. If there are no VMNICs available, migrate one VMNIC from the VMware VDS. Keep the second VMNIC on the VMware VDS for VM

traffic to continue to communicate. Create the VM port group with correct VLAN ID to the new standard switch.

Steps

1. Log in to the VMware vSphere Client HTML5 as administrator@vsphere.local.

2. Select the Home tab and click Networking.

3. Expand DVswitch01-A.

4. Right-click the port group that you wish to migrate and select Migrate VM to another network.

5. To migrate VMs to another Network wizard, perform the following:

a. Verify that Source network is selected and click Browse. b. Select the distributed port group or port group to reassign the VMs and click OK. c. Click Next. d. When the list of VMs is displayed, check each VM, and click Next. e. Verify that the source and destination networks are correct and click Finish.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 87

Delete the distributed port group Delete the distributed port group from the VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

Prerequisites

Verify that there is no port assignment for any distributed port group on any VMs.

Steps

1. Log in to the VMware vCenter Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, select Inventories and click Networking.

3. Select the arrow on DVswitch01-A to list the distributed port groups.

4. Depending on the version of VMware vSphere 6.x, perform one of the following:

Right-click the distributed port group, click Delete, and click YES to delete the port group. Right-click the distributed port group and select All vCenter Action > Remove from Inventory and click OK.

Dissociate the VMware vSphere ESXi host Dissociate the VMware vSphere ESXi host from an existing VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

Prerequisites

Reassign all the VMs to a port group on a different distributed switch or standard switch. Migrate all VMkernel ports to a different distributed switch or standard switch. You do not need to remove distributed port groups and uplink adapters.

VM NIC assigned to a distributed port group force an error when an attempt is made to delete the ESXi host from the VMware VDS.

Steps

1. For VMware vSphere vMotion, evacuate all powered on VMs from the VMware vSphere ESXi host.

2. Migrate the VM distributed ports to a different switch.

3. Migrate the VMkernel ports to a different switch.

VMware vSphere vMotion and evacuate all VMs from the VMware vSphere ESXi host Evacuate and vMotion all powered-on VMs to a different VMware vSphere ESXi host to free up the ports on the VMware VDS. VMs can still point to the same distributed port groups from a different VMware vSphere ESXi host, because there are no assigned VMs on the host.

About this task

This procedure requires using the migration VM network wizard that migrates all the VM port assignments to a different switch with no downtime. If this option is not possible, see Migrate VM distributed port group assignments to a different switch.

Prerequisites

Ensure sufficient system capacity exists on other VMware vSphere ESXi hosts to migrate all the powered-on VMs.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. From the Home tab, select Hosts and Clusters.

3. From the left window, select the appropriate VMware vSphere ESXi host and select the VMs tab.

4. From the right window, click Virtual Machines and use the CTRL key to select all of the VMs.

5. Right-click and select Migrate to open the migration wizard.

6. Verify that Change compute resource only is selected and click Next.

88 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

7. Select the destination resource (cluster or VMware vSphere ESXi host) to migrate the VMs and click Next.

8. In the Select networks page, verify that the destination networks are correct and click Next.

9. Verify that Schedule vMotion with high priority (Recommended) is selected and click Next.

10. Review the Ready to complete window and click Finish.

The VMs migrate to a different VMware vSphere ESXi host. If the cluster was chosen as the destination with DRS enabled, VMware vCenter automatically places the VMs with a different VMware vSphere ESXi host.

11. Put the host in maintenance mode to prevent DRS from vMotioning the VMs back to the host.

Migrate VM distributed port group assignments to a different switch Migrate powered on VM distributed port group assignments to a different distributed switch or standard switch for VMware vSphere 6.5 or later. You do not need to perform this procedure if there are VMs are not powered on.

About this task

You can migrate from:

A standard switch to a distributed switch A distributed switch to a standard switch A distributed switch to a distributed switch

Power off VMs that are connected to the distributed port group to remove the distributed port group. Migrate any port group types.

CAUTION: A disconnect may cause the loss of the VMware vCenter Server, which could prevent the VM port group from

migrating.

Prerequisites

Verify the powered-on VMs on all VMware vSphere ESXi host attached to an existing VMware VDS are not assigned to any distributed port groups.

Verify that there is an available distributed port group to which to migrate the powered-on VMs. Create another switch with the following criteria:

If migrating to a different VMware VDS:

Attach at least one VMNIC as an uplink for a the distributed or standard switch. Create the distributed port groups with the same name and VLAN ID as the existing switch.

If migrating to a standard switch:

Create a standard switch, and attach at least one VMNIC as an uplink for the standard switch. vNIC0 and vNIC1 connect to a different set of physical switches than vNIC2 and vNIC3. Do not add vNIC2 or vNIC3 to vSwitch0,

because it could cause the VMware vSphere ESXi host to lose network connectivity if management traffic gets switched. If no VMNICs are available, migrate one VMNIC from the VMware VDS. Keep the second VMNIC on the distributed switch for VM

traffic to continue to communicate. Create the VM port group with correct VLAN ID to the new standard switch.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, click Networking.

3. Expand DVswitch01-A and select the port group where the VMs are connected.

4. Right-click the port group, and select Migrate VMs to another Network.

5. From the Migrate VMs to another Network wizard, perform the following:

a. Verify that Source network is selected. b. Select Browse for the destination network. c. Select the distributed port group or port group to which the VMs and click OK. d. Click Next. e. When the list of VMs is displayed, enable each VM and click Next. f. Verify that the source and destination networks are correct and click Finish.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 89

Migrate the VMkernel ports to a different switch Migrate the VMkernel ports to a different distributed or standard switch for VMware vSphere 6.5 or later.

Prerequisites

Do not associate the VMware vSphere ESXi host with VMkernel ports to the VMware vSphere Distributed Switch (VDS). Create another distributed or standard switch to migrate the VMkernel ports.

The standard or distributed switch must have the minimum support criteria:

Attach at least one VMNIC to an uplink port for a new distributed or standard switch. Ensure that the uplink used has the appropriate VLANs before migrating.

Create the distributed port group with the same name and VLAN ID of what is created in the existing distributed or standard switch If a VMware VDS is created, add the VMware vSphere ESXi host to it so that the VMkernel port can be migrated between the two

distributed switches. This does not apply for a standard switch

VMkernel ports can be deleted from the VMware vSphere ESXi host if a VMNIC is not available to use for an uplink on the distributed or standard switch.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, select Hosts and Clusters.

3. Select the ESXi host and select Configure tab.

4. Under Networking select Virtual switches.

5. Select the distributed or standard switch to migrate the VMkernel adapter.

6. Click Migrate VMkernel network adaptor to the selected switch.

7. From the Migrate VMkernel Network Adapter wizard, perform the following:

a. Select the VMkernel corresponding to vcesys_esx_vmotion and click Next. b. Change the network label to vcesys_esx_vmotion.

c. Change the VLAN ID to 117 and click Next.

d. Verify that the Ready to complete pages contain the correct results and click Finish. e. Wait 60 seconds and then select the VMkernel adapter link under Networking to ensure that the vcesys_esx_vmotion adapter

is on the new switch. f. Repeat this step for each VMkernel network adapter.

Dissociate the VMware vSphere ESXi host from a VMware vSphere Distributed Switch Dissociate the VMware vSphere ESXi host from an existing VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

Prerequisites

Verify that there are no VMs, vNIC uplinks, or VMKernel ports attached to the VMware VDS coming from each VMware vSphere ESXi host.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. From Home tab, click Networking.

3. Right-click DVSwitch01-A and select Add and Manage Hosts.

4. From the Add and Manage Hosts wizard, perform the following:

a. Select Remove hosts and click Next. b. Select Attached hosts. c. From the Select member hosts window, select the VMware vSphere ESXi host to be deleted and click OK.

To modify multiple VMware vSphere ESXI hosts simultaneously, use the Add and Manage Hosts wizard.

d. Verify that the selected host appears in the list and click Next. e. Review the summary in the Ready to complete window and click Finish.

90 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Remove a VMware vSphere Distributed Switch Remove a VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

Prerequisites

You do not need to remove uplink adapters and VMware vSphere ESXI hosts to delete the VMware VDS. Powered on VMs cannot be attached to any distributed port groups. No VMs are permitted on any VMware vSphere ESXi host

connect to the VMware VDS and attached to the distributed port groups.

Migrate VM distributed port group assignments to a different switch If there are VMs on the distributed port group, migrate VM distributed port group assignments to a different distributed or standard switch for VMware vSphere 6.7.

About this task

VMs connected to the distributed port group can be powered-off to remove the distributed port group.

Use the VM migration wizard to migrate any port group types. However, use caution when migrating the VMware vCenter Server VMs, because a disconnect can cause the loss of the VMware vCenter Server, which could prevent the VM port group from migrating.

Use the VM migration wizard to migrate from a VMware vSphere Standard Switch to a VMware VDS, a VMware VDS to a VMware vSphere Standard Switch, or a VMware VDS to a VMware VDS seamlessly.

Prerequisites

Verify the VMs on all VMware vSphere ESXi hosts attached to an existing VMware VDS are not assigned to any distributed port groups.

Verify there is an available distributed port group to which to migrate the VMs. Create another switch with the following criteria:

If migrating to a different VMware VDS:

Attach at least one VMNIC as an uplink for a new distributed or standard switch. Create the distributed port groups with the same name and VLAN ID as the existing switch.

If migrating to a standard switch:

Create a new standard switch and attach at least one VMNIC as an uplink for the standard switch. vNIC0 and vNIC1 connect to a different set of physical switches than vNIC2 and vNIC3. Do not add vNIC2 and/or vNIC3 to

vSwitch0, because it could cause the VMware vSphere ESXi host to lose network connectivity if management traffic gets switched.

If no VMNICs are available, migrate one VMNIC from the VMware VDS. Keep the second VMNIC on the Distributed Switch for VM traffic to continue to communicate

Create the VM port group with the correct VLAN ID to the new standard switch.

Steps

1. Open a browser and type the following URL: https:// /ui/ 2. Log in to the VMware vSphere Client (HTML5) with the administrator@vsphere.local user account (VMware vSphere SSO

account) or other administrative account with appropriate permissions.

3. On the VMware vSphere Client (HTML5) Home tab, click Networking.

4. Expand DVswitch01-A and select the port group where the VMs are connected.

5. Right-click the port group and select Migrate VMs to another Network.

6. From the Migrate VMs to another Network wizard, perform the following:

a. Verify that Source network is selected. b. Select Browse for the destination network. c. Select the distributed port group or port group to which the VMs are to be reassigned and click OK. d. Click Next. e. When the list of VMs appears, enable the checkbox for each VM, and click Next. f. Verify that the source and destination networks are correct and click Finish.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 91

The selected VMs distributed port groups migrate to a new distributed or standard switch.

Remove VMkernel ports Remove VMkernel ports after the VMs have been migrated from the VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later. This procedure requires the FLEX client, because the required functionality is not yet available in HTML5 interface.

Prerequisites

Verify that all VMs have been migrated off the VMware VDS. Use VMware vSphere Web Client (Flex) to perform this procedure.

Steps

1. Log in as administrator@vsphere.local to the VMware vSphere Web Client at:

https:// /vsphere-client 2. On the Home tab, click Networking.

3. Right-click DVswitch01-A and select Add and Manage Hosts.

4. From the Add and Manage Hosts wizard, perform the following:

a. Select Manage host networking and click Next. b. Click Attach hosts. c. From the Select member hosts window, select the VMware vSphere ESXi hosts and click OK. d. Verify that the selected host has been added and click Next. e. From the Select network adapter tasks window, clear Manage physical adapters so that only Manage VMkernel adapters

is selected and click Next. f. Under On this switch, select the VMkernel port by selecting the VMkernel adapter and clicking Assign port group. g. To delete VMKernel ports, under the VMKernel adapter list, select the VMkernel port and click Remove. h. Select the port group that belongs to a different vSwitch and click OK. i. Validate the VMkernel port destination and click Next. j. Verify that No impact is displayed and click Next. k. Review the summary results, and click Finish.

Configure Disjoint Layer 2 on VMware vSphere Distributed Switch Disjoint Layer 2 is not mandatory on VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later.

To use a Disjoint Layer 2 configuration, assign the following to the VMware VDS:

Cisco UCS vNIC 4 (10 Gbps or more depending on VIC hardware) Cisco UCS vNIC 5 (10 Gbps or more depending on VIC hardware)

A separate VMware VDS is created with two dedicated uplinks to isolate Disjoint Layer 2 traffic from all other primary VDS traffic. There must be a single VMware VDS created for each data center, but not for each cluster.

Create a VMware vSphere Distributed Switch for Disjoint Layer 2 Create a VMware vSphere Distributed Switch (VDS) for Disjoint Layer 2 for VMware vSphere 6.5 or later.

About this task

On full-width blades with additional network physical ports to the onboard mLOM ports, add vNICs 4 and 5 to the service profile. VMware vSphere 6.7 or later supports CDN and does not require reboots while adding additional vNICs. Make sure CDN is enabled in the BIOS Policy and mapped to appropriate vNIC name in Service Profile.

92 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. From the Home tab, select Networking.

3. Right-click Datacenter01 and select Distributed Switch > New Distributed Switch.

The Disjoint Layer 2 VMware VDS naming scheme is as follows: DVswitch .

4. From the New Distributed Switch wizard, perform the following:

a. Validate that the cluster location is Datacenter01 or Cluster01 and click Next. b. Select the appropriate distributed switch version, and click Next. c. From the Edit Settings window, change the number of uplinks to 2.

d. Leave Network I/O Control enabled. e. Disable Create a Default port group. f. Click Next to view the Ready to complete window. g. Review the settings and click Finish if everything is correct. Otherwise, click Back to edit changes.

5. Repeat this procedure to create a VMware VDS for each additional workload type.

Set MTU to 9000.

Create distributed port groups for Disjoint Layer 2 Create distributed port groups for Disjoint Layer 2 for VMware vSphere 6.5 or later.

About this task

Set the load-balancing policy for all the VMkernel distributed port groups to Route based on originating virtual port. Disjoint Layer 2 traffic is commonly associated with virtual distributed port groups only, so it would typically be configured with the default settings.

If vcesys_esx_vmotion is configured as Disjoint Layer 2, configure teaming and failover with VMNIC4 in the active state and VMNIC5 in the standby state.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. From Home tab, select Networking.

3. Right-click DVswitch01-DJL2 and select Distributed Port Group > New Distribution Port Group.

4. From the New Distributed Port Group wizard, perform the following:

a. Change the name of the distributed port group. b. Click Next to configure port group settings. c. Under Configure Settings, leave the default values for Port binding and Port allocation. d. Leave Number of Ports at 8.

e. For VLAN type, select VLAN and change the VLAN ID. f. Enable Customize default policies configuration. g. Leave the default values for Security and Traffic shaping. h. Under Teaming and failover, use the settings for load balancing and uplinks as a guide from the following table:

Port group Active uplinks Standby uplinks Unused uplinks Load balancing

New port group example

Uplink1

Uplink2

N/A N/A Originating virtual port

vMotion example Uplink1 Uplink2 N/A Explicit failover

i. Leave the default values for Monitoring and Miscellaneous. j. Do not edit additional settings. k. Click Next to view the Ready to complete dialog. l. Review the settings and click Finish if everything is correct. Click Back to edit changes.

5. Repeat this procedure for each distributed port group that belongs to the Disjoint Layer 2 configuration for the VMware VDS.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 93

Add VMware vSphere ESXi hosts to the VMware vSphere Distributed Switch Add VMware vSphere ESXi hosts and attach a pair of VMNICs as uplinks to the Disjoint Layer 2 VMware vSphere Distributed Switch (VDS).

About this task

Use the Flex client to perform this task. No option to create a VMkernel port group is available in the HTML5 GUI in the VMware VDS Add and Manage hosts wizard.

Steps

1. From the VMware vSphere Client tab, select Networking.

2. Right-click DVswitch01-DJL2 and select Add and Manage Hosts.

3. From the Add and Manage Hosts wizard, perform the following:

a. Select Add Hosts and click Next. b. Click (+) New Hosts. c. Select the VMware vSphere ESXi host for VMware VDS and click OK. d. Verify that the selected host appears and click Next. e. From the Select network adapter tasks window, verify that Manage physical adapters and Manage VMKernel adapters

are enabled and click Next. f. Select vmnic4 and click Assign uplink. g. Select Uplink 1 and click OK. h. Select vmnic5 and click Assign uplink. i. Select Uplink 2 and click OK. j. Click Next. k. Click Next to view the Ready to complete window. l. Review the settings and click Finish if everything is correct. Click Back to edit changes.

4. Add the VMkernel distributed port groups (vMotion, NFS, FT) if they belong to the Disjoint Layer 2 traffic. If not, click Next and go to Step 5.

a. From the Manage VMKernel network adapters window, verify that the host is selected and click (+) New adapter. b. From the Add Networking wizard, select a distributed port group and click Browse. c. Select vcesys_esx_vmotion and click OK. d. Click Next. e. Enable vMotion traffic and click Next. f. Select Use static IPv4/IPv6 Settings and apply IP address/Subnet Mask as specified in the LCS. g. Click Next to view the Ready to complete window. h. Review the settings and click Finish if everything is correct. Click Back to edit changes. i. Repeat this step to create the port groups. Do not enable any check boxes. The MTU must be set to 9000. j. Click Next.

5. Verify that the status appears as No Impact and click Next. If there is a problem with the output, click Back to return to the previous window.

6. Review the summary results and click Finish.

7. Repeat this procedure for the remaining VMware vSphere ESXi hosts.

94 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Back up and restore a VMware vSphere Distributed Switch data configuration A .zip file is created when you export the backup of a VMware vSphere Distributed Switch (VDS) data configuration. The existing VMware VDS data configuration is not overwritten when you import the backup, instead a new version is created. When you perform a restore, the active VMware VDS data configuration is overwritten.

Export a backup of a VMware vSphere Distributed Switch Export the VMware vSphere Distributed Switch (VDS) for VMware vSphere 6.5 or later into a .zip file.

About this task

The VMware VDS configuration includes all the VMware VDS and distributed port group configuration settings.

Prerequisites

Verify that the VMware VDS is configured.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, click Networking.

3. Right-click DVSwitch01-A and select Settings > Export Configuration.

4. Select one of the following:

Distributed switch and all port groups Distributed switch only

5. In the Descriptions field, type DVswitch01-A and click OK.

6. Click Yes to save the configuration file.

Import a backup of a VMware vSphere Distributed Switch Import a backup of a VMware vSphere Distributed Switch (VDS) from an exported configuration file for VMware vSphere 6.5 or later. You can use the same switch and distributed port group configuration.

About this task

If you import a backup of a VMware VDS configuration, the existing VMware VDS does not get overwritten.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, click Networking.

3. Right-click Datacenter and select Distributed Switch > Import Distributed Switch.

4. Click Browse > Select a distributed switch backup file.

5. Select Preserve original distributed switch and port group identifiers.

6. Click Next.

7. Review the import settings and click Finish.

Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x) 95

Restore a VMware vSphere Distributed Switch backup Reset the VMware vSphere Distributed Switch (VDS) configuration to the settings in the configuration file for VMware vSphere 6.5 or later.

About this task

Restore a backup of the VMware VDS configuration resets the settings in the configuration file and overwrite the existing VMware VDS.

Steps

1. Log in to the VMware vSphere Client (HTML5) as administrator@vsphere.local.

2. On the Home tab, click Networking.

3. Right-click the VMware VDS and select Settings > Restore Configuration.

4. Select one of the following:

Restore distributed switch and all port groups Restore distributed switch only

5. Click Browse.

6. Select a distributed switch backup file and click Next.

7. Review the import settings and click Finish.

Troubleshoot VMware vSphere Distributed Switch VMware documentation contains procedures to troubleshoot a VMware vSphere Distributed Switch (VDS).

To manage network health and rollback, from the VMware documentation site, see the following procedures:

View vSphere Distributed Switch Health Check vSphere Networking Rollback Disable Rollback Resolve Errors in the Management Network Configuration on a vSphere Distributed Switch

VMware vSphere documentation

96 Manage the VMware vSphere Distributed Switch (VMware vSphere 6.x)

Manage the Cisco Nexus 1000V Series Switch

Managing licenses For instructions on how install and configure a license for the Cisco Nexus 1000V Switch, refer to the Cisco Nexus 1000V License Configuration Guide for your release.

Adding hosts For instructions on how to add hosts, refer to the Cisco Nexus 1000V VEM Software Installation and Upgrade Guide for your release.

Creating a port profile Management settings should not be changed without Dell EMC approval. This content is for example purposes only.

Steps

1. Log on to the Cisco Nexus 1000V VSM.

2. To start the configuration, type: n1000v# config t 3. To specify the port profile name, type: n1000v(config)# port-profile type vethernet port-profile-name 4. To designate the interfaces as an access port, type: n1000v(config-port-prof)# switchport mode access 5. To grant access, type: n1000v(config-port-prof)# switchport access vlan vlan-id 6. To specify the port group, type: n1000v(config-port-prof)# vmware port-group 7. To confirm that the port profile is created, type: n1000v(config-port-prof)# show port-profile name name

You can view the port profile in VMware vCenter by navigating to Inventory > Networking. The left side of the window displays the port profile you created.

8. To save the configuration: n1000v(config)# copy run start

Modifying the uplink port profiles Modify the trunks that carry VSM to VEM traffic, service console and VMKernel, and VM data traffic and run northbound from the Cisco Nexus 1000V Switch. Recommended VLAN numbers and IP addresses are referenced in this procedure.

About this task

If a naming convention is used that differs from what is recommended, refer to the Logical Configuration Guide.

When modifying the uplink port profile, northbound traffic from the Cisco Nexus 1000V Switch through the Cisco UCS fabric interconnect is affected.

Prerequisites

Verify that VLANs on uplinks exist in Cisco aggregation switches. Verify the use of jumbo frames. Obtain the IP address of the Cisco Nexus 1000V Switch VSM.

Steps

1. Log on to the VSM CLI.

12

Manage the Cisco Nexus 1000V Series Switch 97

2. To modify the UPLINK port profiles for VMware VM traffic, L3 VMotion, NFS, and VSM Layer 3 Control, type the following:

port-profile type ethernet PRODUCTION-UPLINK vmware port-group switchport mode trunk switchport trunk allowed vlan 300 channel-group auto mode on mac-pinning no shutdown state enabled

/* For vSphere 6.0 and later */ port-profile type ethernet VMOTION-UPLINK vmware port-group switchport mode trunk switchport trunk allowed vlan <106 or 117> channel-group auto mode on mac-pinning no shutdown system vlan <106 or 117> state enabled

port-profile type ethernet N1K_L3_CONTROL-UPLINK vmware port-group switchport mode trunk switchport trunk allowed vlan 116 channel-group auto mode on mac-pinning no shutdown system vlan 116 state enabled /* For unified only */ port-profile type ethernet NFS-UPLINK vmware port-group switchport mode trunk switchport trunk allowed vlan 109 channel-group auto mode on mac-pinning no shutdown system vlan 109 state enabled

3. to view the uplinks created under the Cisco Nexus 1000V Switch in the production VMware vCenter, select Inventory > Networking.

Removing the uplink port profiles Remove the uplink port profiles from the trunks that run northbound from the Cisco Nexus 1000V Switch. Northbound traffic from the Cisco Nexus 1000V Switch is affected.

Prerequisites

Verify that VLANs on uplinks exist in Cisco aggregation switches. Verify the use of jumbo frames. Obtain the IP address of the Cisco Nexus 1000V Switch VSM.

Steps

1. Log on to the VSM.

98 Manage the Cisco Nexus 1000V Series Switch

2. Type the following commands:

configure terminal

no port-profile type ethernet PRODUCTION-UPLINK

copy run start

end

Modifying vEthernet data port profiles Modify data port profiles for VMware VM traffic, L3 VMotion, NFS, and VSM Layer 3 Control.

Steps

1. To modify the data port profiles for VMware VM traffic, L3 VMotion, NFS, and VSM Layer 3 Control, type the following commands:

port-profile type vethernet VM-DATA-300 vmware port-group switchport mode access switchport access vlan 300 or no shutdown state enabled copy run start

/* For vSphere 6.0 or later */

port-profile type vethernet VCESYS_ESX_L3VMOTION vmware port-group switchport mode access switchport access vlan 117 or no shutdown pinning id 4 system vlan 117 or service-policy type qos input SET_COS_4 state enabled copy run start

/* For Unified Systems */

port-profile type vethernet VCESYS_ESX_NFS vmware port-group switchport mode access switchport access vlan 109 or no shutdown pinning id 10 system vlan 109 or service-policy type qos input SET_COS_2 state enabled

/***********************/

port-profile type vethernet VCESYS_N1K_L3CONTROL vmware port-group switchport mode access switchport access vlan 116 or no shutdown pinning id 8 capability l3control system vlan 116 or state enabled copy run start

2. To verify the procedure, view the (VM facing) port groups in VMware VCenter. In the following example, the green icon represents UPLINK, and the blue icon represents the VM facing port group:

Manage the Cisco Nexus 1000V Series Switch 99

Modifying the QoS settings Modify QoS settings on the Cisco Nexus 1000V Switch and mark the service console and VMkernel traffic with the appropriate QoS.

About this task

Policing and prioritization of traffic are implemented only when a policy map is applied to an interface. The only exception is that, by default, the QoS value for control and packet VLAN traffic is set to six. This value can be overridden with an explicit QoS policy configured on the interface that carries the control and packet VLAN traffic.

If the VSM VMs are not hosted on the VEM in an VMware vSphere ESXi host that it is managing (for example, the VSM VMs are hosted on separate VMware vSphere ESXi hosts running the regular VMware vSwitch), packets from the VSM are not covered by the QoS policies configured on the Cisco Nexus 1000V DVS. To ensure proper QoS treatment, the VSM packets configure and attach QoS policy on the switchports of the physical switches connected the VMware vSphere ESXi hosts where the VSM VMs are hosted.

This QoS policy colors and marks the control packets only. The upstream switches must be configured with the proper QoS per-hop- behavior to ensure differentiated services.

Steps

1. Log on to the Cisco Nexus 1000V Switch.

2. Type: config t.

For this Converged System: Type:

Unified policy-map type qos SET_COS_2 class class-default set cos 2 policy-map type qos SET_COS_4 class class-default set cos 4 policy-map type qos SET_COS_6 class class-default set cos 6

Block policy-map type qos SET_COS_4 class class-default set cos 4 policy-map type qos SET_COS_6

100 Manage the Cisco Nexus 1000V Series Switch

For this Converged System: Type:

class class-default set cos 6

Upgrading the VEM software For instructions on performing the upgrade, refer to Cisco Nexus 1000V VEM Software Installation and Upgrade Guide for your release.

Troubleshooting the Cisco Nexus 1000V Switch For troubleshooting information and procedures for the Cisco Nexus 1000V Switch, refer to the Cisco Nexus 1000V Troubleshooting Guide for your release.

Manage the Cisco Nexus 1000V Series Switch 101

Manage VMware NSX with VPLEX on VxBlock Systems

This section provides the procedures for failover and recovery of VMware NSX with VPLEX on VxBlock Systems.

This section is not applicable for vSphere 6.5.

The VxBlock System where all the VMware vSphere core VMs (PSCs, VC, and VUM) and VMware NSX VMs (NSX Manager and controllers) reside is the primary site. The other VxBlock System is the secondary site.

All the VMware vSphere core VMs (PSCs, VC, and VUM) and VMware NSX VMs (NSX Manager and controllers) reside on a shared stretched LUN provided by VPLEX in the same stretched VMware vSphere management cluster. The VMs are hosted by VMware vSphere ESXi hosts on Cisco UCS B-Series blades and connected to a separate Layer 3 management port group.

All the customer VMs reside on a shared stretched LUN provided by VPLEX in the same stretched VMware vSphere compute cluster. The VMs are hosted by VMware vSphere ESXi hosts on Cisco UCS B-Series blades and connected to a VXLAN port group. These VMs can reside on any VMware vSphere ESXi host in the primary site or the secondary site.

Perform a graceful failover This procedure explains how to gracefully fail over management components from the primary site to the secondary site.

Steps

1. Disable DRS on the stretched VMware vSphere management cluster.

NOTE:

After migrating VMs to the secondary site, disabling DRS prevents VMs from automatically migrating back to the

primary site. Expect a loss of network connectivity to all the VMs until the SVI is switched over.

a. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters. b. Expand Datacenter to view all the vSphere clusters. c. Left-click the Management VPLEX vSphere cluster and select the Manage tab. d. Click vSphere DRS and select Edit. e. Uncheck the box Turn ON vSphere DRS. This stops the VM from migrating back to the hosts in the primary site after they have

been migrated to the secondary site.

2. Manually power off the NSX Manager and controllers.

NOTE: To reduce the risk of errors, manually power off the NSX Manager and controllers before migrating. This

process prevents errors after connectivity is restored in the secondary site.

a. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters. b. Expand the Management VPLEX vSphere cluster to view the VMs. c. Right-click NSX Manager VM and select Power > Shutdown guest OS. d. Repeat the steps for all the NSX Controllers in the following order:

i. NSX Controller 3 ii. NSX Controller 2 iii. NSX Controller 1

3. Perform a cold migration of the NSX Manager and controllers from the primary site to the secondary site.

NOTE: After the migration, expect a loss of network communication to all the VMs until the SVI is switched over

from the primary site to the secondary site.

a. Right-click NSX Manager VM and select Migrate.

13

102 Manage VMware NSX with VPLEX on VxBlock Systems

b. The Migrate wizard opens. Enter the data values as requested, accept the default settings presented, and use the following configuration information:

Wizard page Selection

Select the migration type Change compute resource

Select a compute resource vcesysmgmt04

Select network vcesys_management

c. Click Finish. d. Repeat the steps for all three NSX controller VMs, using the following information:

Wizard page Selection

NSX controller 1 vcesysmgmt04

NSX controller 2 vcesysmgmt05

NSX controller 3 vcesysmgmt06

e. Verify that each VM successfully migrated to correct ESXi host.

4. Migrate the remaining management components on hosts from the primary site to the secondary site.

NOTE: The DHCP server resides in its local site and should not be migrated to the opposite site.

a. Right-click PSC02 VM and select Migrate. b. The Migrate wizard opens. Enter the data values as requested, accept the default settings presented, and use the following

configuration information:

Wizard page Selection

Select the migration type Change compute resource

Select a compute resource vcesysmgmt05

Select network vcesys_management

c. Click Finish. d. Repeat the steps for the PSC01 VM using the following information:

VM Wizard page Selection

PSC01 Select a compute resource vcesysmgmt04

e. Repeat the migration steps for the remaining management SQL, VC, and VUM VMs, except migrate all the VMs at the same time.

NOTE: It is important to migrate these last three VMs at the same time, because after the VMware vSphere

vCenter Server is migrated, it loses connectivity and migration cannot continue. At this point you are forced to

manually import the VMs from the datastore.

Use the following information:

VMs Wizard page Selection

SQL, VC, and VUM

Select a compute resource vcesysmgmt05

f. Verify that each VM successfully migrated to correct ESXi host.

5. Within the primary site, manually disable the Management SVI (VLAN 136) on the Cisco 9396 switches.

a. Use PuTTY to log in to Cisco 9396-A.

Manage VMware NSX with VPLEX on VxBlock Systems 103

b. Disable the Management SVI by entering the following commands:

configure terminal interface vlan136 (Use the VLAN ID provided in LCS) shutdown exit copy running-config startup-config

c. Repeat the steps to manually disable the Management SVI on Cisco 9396-B.

6. In the secondary site, manually enable the Management SVI (VLAN 136) on the Cisco 9396 switches.

a. Use PuTTY to log in to Cisco 9396-A. b. Enable the Management SVI by entering the following commands:

configure terminal interface vlan136 (Use the VLAN ID provided in LCS) no shutdown exit copy running-config startup-config

c. Repeat the steps to manually enable the Management SVI on Cisco 9396-B.

7. Validate VM connectivity by performing the following steps:

a. Open command prompt and ping each VM to validate network connectivity. b. Log in to the VMware Web Client to validate that VMware vSphere vCenter Server is running properly. c. Validate that all the VMware vSphere ESXi hosts and VMs are connected and online.

8. Manually power on NSX Manager and NSX Controllers within the secondary site by performing the following steps:

a. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters. b. Expand the Management VPLEX vSphere cluster to view the VMs. c. Right-click NSX Manager VM and select Power > Power On. d. Repeat the steps for all the NSX Controllers in the following order:

i. NSX Controller 1 ii. NSX Controller 2 iii. NSX Controller 3

9. Validate that all NSX Controllers are connected and no warnings or errors exist.

a. On the VMware vSphere Web Client Home tab, under Inventories, click Network & Security. b. Left-click Dashboard in the left pane and validate the following:

Ensure that in System Overview that the NSX Manager and all three NSX Controllers show a green square. Ensure that there are no errors or warnings within the Host Preparation Status, Firewall Publish Status, and Logical

Switch Status.

c. To resolve any errors under the Host Preparation Status, select Resolve All to fix.

10. Click Finish. All the VMware vSphere core and NSX Manager and controller components are now running in the secondary site.

Perform a graceful recovery This procedure explains how to gracefully recover management components from the secondary site to the primary site.

Steps

1. Manually power off the NSX Manager and controllers.

NOTE: To reduce the risk of errors, manually power off the NSX Manager and controllers before migrating. This

process prevents errors after connectivity is restored in the secondary site.

a. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters. b. Expand the Management VPLEX vSphere cluster to view the VMs. c. Right-click NSX Manager VM, and select Power > Shutdown guest OS. d. Repeat the steps for all the NSX Controllers in the following order:

i. NSX Controller 3

104 Manage VMware NSX with VPLEX on VxBlock Systems

ii. NSX Controller 2 iii. NSX Controller 1

2. Perform a cold migration of the NSX Manager and controllers from the secondary site to the primary site.

NOTE: After the migration, expect a loss of network communication to all VMs until the SVI is switched over from

the secondary site to the primary site.

a. Right-click NSX Manager VM, and select Migrate. b. The Migrate wizard opens. Enter the data values as requested, accept the default settings that are presented, and use the

following configuration information:

Wizard page Selection

Select the migration type Change compute resource

Select a compute resource vcesysmgmt01

Select network vcesys_management

c. Click Finish. d. Repeat the steps for all three NSX controller VMs, using the following information:

Wizard page Selection

NSX controller 1 vcesysmgmt01

NSX controller 2 vcesysmgmt02

NSX controller 3 vcesysmgmt03

e. Verify that each VM successfully migrated to correct ESXi host.

3. Migrate the remaining management components on hosts from the secondary site to the primary site.

NOTE: The DHCP server resides in its local site and should not be migrated to the opposite site.

a. Right-click PSC02 VM, and select Migrate. b. The Migrate wizard opens. Enter the data values as requested, accept the default settings that are presented, and use the

following configuration information:

Wizard page Selection

Select the migration type Change compute resource

Select a compute resource vcesysmgmt02

Select network vcesys_management

c. Click Finish. d. Repeat the steps for the PSC01 VM using the following information:

VM Wizard page Selection

PSC01 Select a compute resource vcesysmgmt01

e. Repeat the migration steps for the remaining management SQL, VC, and VUM VMs, except migrate the VMs simultaneously.

NOTE: After the VMware vSphere vCenter Server is migrated, it loses connectivity. Unless you migrate the last

three VMs, migration cannot continue. Manually import the VMs from the datastore.

Use the following information:

Manage VMware NSX with VPLEX on VxBlock Systems 105

VMs Wizard page Selection

SQL, VC, and VUM

Select a compute resource vcesysmgmt02

f. Verify that each VM successfully migrated to correct ESXi host.

4. In the secondary site, manually disable the Management SVI (VLAN 136) on the Cisco 9396 switches.

a. Use PuTTY to log in to Cisco 9396-A. b. Disable the Management SVI by entering the following commands:

configure terminal interface vlan136 (Use the VLAN ID provided in LCS) shutdown exit copy running-config startup-config

c. Repeat the steps to manually disable the Management SVI on Cisco 9396 switch B.

5. In the primary site, manually enable the Management SVI (VLAN 136) on the Cisco 9396 switches.

a. Use PuTTY to log in to Cisco 9396-A. b. Enable the Management SVI by entering the following commands:

configure terminal interface vlan136 (Use the VLAN ID provided in LCS) no shutdown exit copy running-config startup-config

c. Repeat the steps to manually enable the Management SVI on Cisco 9396 switch B.

6. Validate VM connectivity by performing the following steps:

a. Open command prompt and ping each VM to validate network connectivity. b. Log in to the VMware Web Client to validate that VMware vSphere vCenter Server is running properly. c. Validate that all the VMware vSphere ESXi hosts and VMs are connected and online.

7. Manually power on NSX Manager and NSX controllers within the secondary site by performing the following steps:

a. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters. b. Expand the Management VPLEX vSphere cluster to view the VMs. c. Right-click NSX Manager VM, and select Power > Power On. d. Repeat the steps for all the NSX Controllers in the following order:

i. NSX Controller 1 ii. NSX Controller 2 iii. NSX Controller 3

8. Validate that all NSX Controllers are connected and no warnings or errors exist.

a. On the VMware vSphere Web Client Home tab, under Inventories, click Network & Security. b. Click Dashboard in the left pane, and verify the following:

Ensure that in System Overview that the NSX Manager and all three NSX Controllers show a green square. Ensure that there are no errors or warnings within the Host Preparation Status, Firewall Publish Status, and Logical

Switch Status.

c. To resolve any errors under the Host Preparation Status, select Resolve All to fix.

9. Enable DRS on the stretched VMware vSphere management cluster.

NOTE:

This step forces all the VMs to recover back from the secondary site to the primary site. Expect a loss of network

communication to all the VMs until the SVI is switched over.

a. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters. b. Expand Datacenter to view all the vSphere clusters. c. Click Management VPLEX vSphere cluster, and select the Manage tab. d. Click vSphere DRS, and select Edit.

106 Manage VMware NSX with VPLEX on VxBlock Systems

e. To force each management VM to vMotion to an assigned host, enable Turn ON vSphere DRS.

10. Click Finish. All the VMware vSphere core and NSX Manager and controller components are now running in the primary site.

Manage VMware NSX with VPLEX on VxBlock Systems 107

Guidelines for backing up configuration files The following section is applicable to AMP-2 only.

Back up configuration files Back up and restore VxBlock System configuration files with VxBlock Central.

For information about performing these tasks, see VxBlock Central online help.

Back up network devices running Cisco NX-OS software Create a configuration file to back up network devices using Cisco NX-OS operating systems.

About this task

IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

Prerequisites

TFTP service must be installed, configured, and active, on the AMP server where the configuration repository exists. Verify that an instance of the configuration repository exists. Obtain login credentials for the device configuration backup. Obtain the network IP address of the configuration backup repository. Obtain the device name and type that matches the model abbreviation that was used to create the repository subdirectory structure.

Steps

1. Log in to the device account using administrator privileges.

2. To confirm that the scheduler feature is enabled, type: SWITCH# show feature | include scheduler scheduler 1 enabled

3. Routing requirements may require you to add VRF management to the end of each copy command. The variable $(TIMESTAMP) in the file name inserts the date/time into the file name when the tasks are run. From the network device, to create the backup task, enter the following command:

SWITCH# conf t SWITCH(config)# scheduler aaa-authentication username login password password SWITCH(config)# scheduler job name cfgBackup SWITCH(config-job)# copy startup-config tftp://IP/device/config/name_startup_$(TIMESTAMP).cfg SWITCH(config-job)# copy running-config tftp://IP/device/config/name_running_$(TIMESTAMP).cfg SWITCH(config-job)# end SWITCH#

4. To schedule the backup task, type:

SWITCH# conf t SWITCH(config)# scheduler schedule name Daily0600 SWITCH(config-schedule)# time daily 06:00 SWITCH(config-schedule)# job name cfgBackup

14

108 Guidelines for backing up configuration files

SWITCH(config-schedule)# end SWITCH# SWITCH# conf t SWITCH(config)# scheduler schedule name Daily1800 SWITCH(config-schedule)# time daily 18:00 SWITCH(config-schedule)# job name cfgBackup SWITCH(config-schedule)# end SWITCH#

5. To confirm the scheduler update, type: SWITCH# show scheduler config config terminal feature scheduler scheduler logfile size 16 end config terminal scheduler job name cfgBackup copy startup-config tftp:// /9500/config/D01-9500-01_startup_$(TIMESTAMP).cfg copy running-config tftp:// /9500/config/D01-9500-01_running_$(TIMESTAMP).cfg end config terminal scheduler schedule name Daily0600 time daily 06:00 job name cfgBackup end config terminal scheduler schedule name Daily1800 time daily 18:00 job name cfgBackup end

6. Verify that the copy statements work by running each individually:

V00101MD9502# copy running-config tftp:// /9500/config/V00101MD9502_running_ $TIMESTAMP.cfg

Trying to connect to tftp server...... Connection to server Established. Copying Started..... TFTP put operation was successful

7. To save the configuration updates, type: SWITCH# copy running-config startup-config

[########################################] 100% 8. To verify the procedure, run each statement individually: V00101MD9502# copy running-config tftp:// /

9500/config/V00101MD9502_running_$TIMESTAMP.cfg

Back up Cisco UCS FIs Restore a system configuration from any full state backup file exported from Cisco UCS Manager.

About this task

Back up using Cisco UCS Manager and take a snapshot of all or part of the system. Configure and export the file to a location on your network. You cannot use Cisco UCS Manager to back up data on the servers.

You can perform a backup while the system is up and running. The backup operation saves information from the management plane and does impact the server or network traffic.

Prerequisites

The TFTP service must be installed, configured, and active, on the AMP server where the configuration repository exists. Obtain login credentials for the device configuration backup. Obtain the network IP address of the configuration backup repository. Obtain the device name and type that matches the model abbreviation that was used to create the repository subdirectory structure.

For example:\6100\config\filename

Guidelines for backing up configuration files 109

Steps

Create and run the backup using either the Cisco UCS Manager GUI or CLI.

Related tasks

Create and run the backup using the Cisco UCS Manager on page 110

Create and run the backup using the Cisco UCS CLI on page 111

Create and run the backup using the Cisco UCS Manager Back up the Cisco UCS fabric interconnects configuration using the Cisco UCS Manager GUI.

About this task

Creating a backup is a one-time only task.

Steps

1. Log in to the Cisco UCS Manager using administrator privileges.

2. To create the backup, perform the following steps:

a. From the Navigation window, select the Admin tab. b. Click the All node. c. From the Work window, select the General tab. d. In the Actions area, select Backup (for UCSM 2.x). e. In the Actions area, select Backup Configuration. (for UCS 3.x) f. In the Backup Configuration window, select Create Backup Operation. g. Set Admin State to Disabled. h. Set Type to Full State. i. Select the Preserve Identifies checkbox. j. Click OK. k. If a confirmation window appears, click OK.

3. To run the backup, perform the following:

a. From the Navigation window, select the Admin tab. b. Select the All node. c. From the Work window, select the General tab. d. In the Actions area, select Backup. e. From the Backup Operations table of the Backup Configuration window, select the backup operation that you want to run. f. In the Admin State field, select Enabled. g. For all protocols except TFTP, type the password in the Password field. h. You can optionally change the content of the other available fields. i. Click Apply.

The Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration window.

j. View the progress of the backup operation by clicking the down arrows on the FSM Details bar. k. To close the Backup Configuration window, click OK. l. The backup operation continues to run until it is completed. To view the progress, reopen the Backup Configuration window.

Related tasks

Create and run the backup using the Cisco UCS Manager on page 110

Create and run the backup using the Cisco UCS CLI on page 111

110 Guidelines for backing up configuration files

Create and run the backup using the Cisco UCS CLI Creating a backup is a one-time only task.

Steps

1. Log in to the Cisco UCS Manager using SSH administrator privileges.

2. To create the backup, type:

UCS-A# scope system UCS-A /system* # create backup tftp://v00001vmfm01/6100/config/device_name_full-state.tar.gz full-state disabled Password: UCS-A /system* # commit-buffer UCS-A /system #

3. To run the backup, type:

UCS-A# scope system UCS-A /system* # scope backup v00001vmfm01 UCS-A /system* # enable Password: UCS-A /system* # commit-buffer UCS-A /system #

Related tasks

Create and run the backup using the Cisco UCS Manager on page 110

Create and run the backup using the Cisco UCS CLI on page 111

Create and run the backup using scheduled backups Create and run the FI backup using scheduled backups.

About this task

The following conditions apply for scheduled backups:

Scheduled backups can be configured for full state. You cannot set the exact time of day that the scheduled backup occurs. The full state backup is a binary file that includes a snapshot of the entire system.

Use the binary file to restore the system during disaster recovery. Use the binary file to restore or rebuild the configuration on the original FI or recreate the configuration on a different FI. You cannot use the binary file for an import.

Full state backups are encrypted. The full state backup policy can be configured as daily, weekly, or biweekly. You cannot modify the maximum number of backup files that the Cisco UCS Manager creates. The option to configure scheduled backups can be found on the Admin tab and on the right side of the screen on the Policy Backup

& Export tab.

Steps

1. To use the Cisco UCS Manager GUI to configure scheduled backups, see the following document:

Cisco UCS Manager GUI Configuration Guide, Release 2.x, UCS Manager GUI Configuration Guide, Release 3.x.

2. To use the Cisco UCS Manager CLI to configure scheduled backups, see the following document:

Cisco UCS Manager CLI Configuration Guide, Release 2.x, UCS Manager GUI Configuration Guide, Release 3.x.

Guidelines for backing up configuration files 111

Configure fault suppression Fault suppression allows you to suppress SNMP trap and Call Home notifications during planned maintenance time.

About this task

A fault suppression task prevents notifications from being sent whenever a transient fault is raised or cleared. Faults remain suppressed until the time duration has expired or the fault suppression tasks have been manually stopped. After the fault suppression has ended, Cisco UCS Manager sends notifications for uncleared, outstanding, suppressed faults. Fault suppression uses fixed time intervals or schedules.

You can specify the maintenance window to suppress faults using fixed time intervals or schedules. Fixed time intervals allow you to create a start time and a duration when fault suppression is active. Fixed time intervals cannot be reused. Schedules are used for one time occurrences or recurring time periods and can be saved and reused.

Fault suppression policies define the causes and fault types to suppress. Only one policy can be assigned to a task. The following table provides the Cisco UCS Manager policies:

Policy Description

default-chassis-all-maint This policy suppresses faults for the Cisco UCS 5108 Blade Server Chassis and components, including all blade servers, power supplies, fan modules, and IOMs. This policy applies only to chassis.

default-chassis-phys-maint This policy suppresses faults for the chassis and all fan modules and power supplies that are installed into the chassis. This policy applies only to chassis.

default-fex-all-maint This policy suppresses faults for the FEX and all power supplies, fan modules, and IOMs in the FEX. This policy applies only to the FEX.

default-fex-phys-maint This policy suppresses faults for the FEX and all fan modules and power supplies in the FEX. This policy applies only to the FEX.

default-server-maint This policy suppresses faults for blade servers and/or rack servers. This policy applies to chassis, organizations, and service profile. When applied to a chassis, only blade servers are affected.

default-iom-maint This policy suppresses faults for IOMs in a chassis or FEX. This policy applies only to chassis, the FEX, and IOMs.

Steps

1. To use the Cisco UCS Manager GUI to configure fault suppression, see: Cisco UCS Manager GUI Configuration Guide, Release 2.x, Cisco UCS Manager GUI Configuration Guide, Release 3.x.

2. To use the Cisco UCS Manager CLI to configure fault suppression, see: Cisco UCS Manager CLI Configuration Guide, Release 2.x, Cisco UCS Manager CLI Configuration Guide, Release 3.x.

Back up the VMware vCenter SQL server database Create backup jobs in a Microsoft SQL server configuration. Frequency depends upon the client RPO.

About this task

Creating backup jobs is not required for VMware vSphere 6.5.

Prerequisites

Confirm that the Microsoft SQL server sa login is enabled and a password is set for the account.

Ensure that the server authentication mode is set to the SQL Server and Windows Authentication mode. Obtain administrator login credentials. Obtain AMP element manager server network address. Obtain VMware vCenter SQL server network address and SQL server login credentials. For more information, see Microsoft Developer Network article for SQL: Change Server Authentication Mode.

Steps

1. Connect to the client AMP environment jump server.

2. From the jump server, use RDP to access the SQL database server, and log in as administrator.

112 Guidelines for backing up configuration files

3. To run the SQL Server Management Studio application, go to the application and select Start > All Programs > Microsoft SQL Server > SQL Server Management Studio.

4. To log in to the application, perform the following:

a. In the Server type field, verify that Database Engine appears. If not, select it. b. If the Server name field is not autofilled, select (local). If no matching account exists, log in with administrator privileges. c. In the Authentication field, verify that Windows Authentication appears. If not, select it, and click Connect.

5. To confirm the list of databases that require backup, from the Object Explorer window, expand Databases > System Databases.

The databases that require backup are in the System Databases (master, model, msdb) and the vcenter and vum databases that appear after the Database Snapshots folder. Depending on the naming standard that has been followed (client or Dell EMC), they should appear as xmgmtvcenter and xmgmtvum, where x is a unique identifier. The tempdb database should be excluded from the backup process creation tasks.

6. Go to, and expand SQL Server Agent > Jobs.

7. To create a backup job, right-click Jobs and select New Job.

a. From the New Job window, in the Name field, enter a name for the backup. b. In the Owner field, delete the default login and enter sa.

c. Change the Category field to Database Maintenance. d. Type a description in the Description field. e. Verify Enabled is checked.

8. To create a job-step entry, under Select a page, select Procedure (Steps), and then click New.

a. From the New Job Step window, in the Step name field, type Backup or other text.

b. Verify that the default value is set in the New Job Step window. c. Leave the Run as field empty. d. In the Database field, select the database. e. Copy and paste this text into the Command area, and modify the @DIRNAME and @DBNAME variables accordingly:

-- SQL Server Transact SQL script to perform database backup -- -- Use this script for each of the databases in the {AMP or AMP-2}. Modify the following variable -- for the shared location of the backup files -- -- DIRNAME = Set location of the backup files -- -- Modify the following variable for the name unique to each database: -- -- DBNAME = Set database name -- DECLARE @DIRNAME VARCHAR(40), @DBNAME VARCHAR(40), @SUFFIX VARCHAR(48), @FILENAME VARCHAR(128); -- SET @DIRNAME = 'I:\Backups\'; SET @DBNAME = 'master'; -- SET @SUFFIX = '_FULL_' + convert(varchar(8),getdate(),112) + '_' + replace (convert(varchar(8), getdate(),108),':','')+ '.bak'; SET @FILENAME = @DIRNAME+@DBNAME+@SUFFIX; BACKUP DATABASE @DBNAME TO DISK=@FILENAME WITH NAME=@DBNAME,SKIP,STATS=20; --

f. Under Select a page, select the Advanced tab. g. For the On success action field, select Quit the job reporting success. h. Under Select a page, select the Advanced tab. You can optionally type a directory location and file name into the Output file

field to capture script log messages. For example, I:/Backups/master.log.

i. Click OK.

9. To create the job schedule, under Select a page, select Schedules, and click New.

a. From the New Job Schedule window, type a Name for the job schedule. b. Use the following table to create the settings:

Guidelines for backing up configuration files 113

For these databases

Make the following settings

master, model, msdb i. In the Frequency section, set the Occurs field to Daily. ii. Verify that the Recurs field is set to 1 day. iii. In the Daily Frequency section, check Occurs once at and set to 06:30 AM. iv. In the Duration section, confirm that the Start date is set to the current date and No end date is

selected.

vcenter, vum i. In the Frequency section, set the Occurs field to Daily. ii. Verify that the Recurs field is set to 1 day. iii. In the Daily Frequency section, check Occurs every, type 4, and select hours.

iv. Set Starting at to 06:30:00 AM and Ending at to 06:29:59 AM. v. In the Duration section, confirm the Start date is set to the current date and No end date is

selected.

c. Verify that the Schedule Type is set to Recurring and confirm Enabled is checked. d. Click OK to accept the schedule update. e. Click OK to complete backup job creation.

10. Repeat the preceding steps starting with step 8 until all databases (excluding tempdb) have a backup job.

11. To create an SQL Server backup file management job, go to step 8 and perform the following:

a. As the job description, type BAK file management.

b. For the database field, select master. c. For the Command field, use this text:

-- SQL Server Transact SQL script to perform backup file management -- -- Use this script to manage the BAK files created by the backup jobs. Modify -- the following variable for the shared location of the backup files -- -- DIRNAME = Set location of the backup files -- DECLARE @dt datetime, @DIRNAME VARCHAR(40) -- SET @DIRNAME = 'I:\Backups\'; -- select @dt = getdate() - 1 EXECUTE master.dbo.xp_delete_file 0,@DIRNAME,N'BAK',@dt

d. Use the same schedule as the master database.

12. To test a backup, right-click a backup job and select Start Job at Step.

Next steps

Monitor the backup location to confirm that backups are performed on schedule.

Back up the VNXe configuration Back up the VNXe storage array used as the AMP shared storage. Unisphere requires a current version of Microsoft Internet Explorer or Mozilla Firefox with Adobe Flash Player 9 or above.

Prerequisites

Obtain the network IP address and/or URL of the VNXe management address. Obtain administrator login credentials for service accounts.

Steps

1. To log into Unisphere, open a URL to the VNXe management address.

2. From the login screen, type the username and password for the account with advanced administrator privileges for the VNXe system. If you are using an LDAP-based account, type the domain/username for the account and click Login.

114 Guidelines for backing up configuration files

For more information, refer to the Configure User Access to Unisphere.

NOTE: If you cannot remember the passwords for the VNXe default administrator or service user accounts, you can

set the passwords back to the default passwords that shipped with your VNXe system.

3. To initiate configuration backup task, select Settings > Service System.

4. Type the service password to access the Service System page.

5. Under System Components, select Storage System.

6. Under Service Actions, select a service action and click Execute service action.

7. If you click Save Configuration, you can save details about the configuration settings on the VNXe system to a local file. Service personnel can use this file to assist you with reconfiguring your system after a major system failure or a system reinitialization.

The configuration details include information about:

System specifications Users Installed licenses Storage resources Storage servers Hosts

The file only contains details about your system configuration settings. You cannot restore your system from this file. Save the configuration settings after each major configuration change to ensure you have a current copy of the file.

Guidelines for backing up configuration files 115

Back up Cisco MDS switches

Create backups of startup and running configuration files Create a backup of the Cisco MDS switch startup and running configuration files. Backups are stored on the Cisco UCS C220 management server.

Prerequisites

Start the TFTP service on each of the management servers. If it does not exist, create the following folder on each management server:

D:\Cisco\MDS\switch-model\config Obtain the int-mdsbackup login ID and password to log in to the Cisco MDS switches.

Steps

1. Log in to the switch using PuTTY with the int-mdsbackup login ID on the Converged System.

2. Use the copy command to create the configuration file backups.

copy startup-config tftp://192.168.101.93/9502/config/V00101MDxxxx_startup_$ (TIMESTAMP).config

copy running-config tftp://192.168.101.93/9502/config/V00101MDxxxx_running_$ (TIMESTAMP).config end

Next steps

Schedule the backup to run regularly.

Related tasks

Scheduling backups of the startup and running configuration files on page 116

Scheduling backups of the startup and running configuration files Create and schedule a job to back up the Cisco MDS switch startup and running configuration files.

Steps

1. From the host, type: config t 2. Type the following commands, one per line and, at the end of each line, type Ctrl-Z:

scheduler aaa-authentication username login password password scheduler job_name switchBackup

3. To create a backup for the startup-config and running-config files, for example, type:

15

116 Back up Cisco MDS switches

copy startup-config tftp://192.168.101.93/9502/config/V00101MDxxxx_startup_$ (TIMESTAMP).config copy running-config tftp://192.168.101.93/9502/config/V00101MDxxxx_running_$ (TIMESTAMP).config end conf t

NOTE: The preceding commands add the date and timestamp to the filenames.

4. Type the following commands, one per line, and at the end of each line, type Ctrl+Z:

scheduler schedule name Daily time daily 23:00 job name switchBackup end

5. To verify the action, type:

show schedule config config terminal feature scheduler scheduler logfile size 16 end config terminal scheduler job name switchBackup copy startup-config tftp://192.168.101.93/xxxx/config/V00101MDxxxx_startup_$ (TIMESTAMP).config copy running-config tftp://192.168.101.93/xxxx/config/V00101MDxxxx_running_$ (TIMESTAMP).config end end config terminal Scheduler schedule name Daily

Time daily 23:00 Job name switchBackup

end After you are satisfied with the job, issue the copy running-config startup-config command to save the configuration.

Create a script to purge older copies of the backup files Create a script that can be scheduled to run to delete old backups of the startup and configuration files.

Steps

To create a script that deletes old backups of the startup and configuration files, copy the VBS script that is included here. Save it to the following file: D:\scripts\delete_old_backups.vbs

CAUTION: This script deletes every file in the D:\Cisco\9xxx\config directory that has a .config file extension and

is older than seven days.

Option Explicit On Error Resume Next Dim oFSO, oFolder, sDirectoryPath

Back up Cisco MDS switches 117

Dim oFileCollection, oFile, sDir Dim iDaysOld ' Specify Directory Path for File Deletion sDirectoryPath = "D:\Cisco\9xxx\config" ' Specify Number of Days Old File to Delete iDaysOld = 7 Set oFSO = CreateObject("Scripting.FileSystemObject") Set oFolder = oFSO.GetFolder(sDirectoryPath) Set oFileCollection = oFolder.Files For each oFile in oFileCollection Specify File Extension 'Specify number with Number of characters in the file extension If LCase(Right(Cstr(oFile.Name), 6)) = "config" Then If oFile.DateLastModified < (Date() - iDaysOld) Then oFile.Delete(True) End If End If Next Set oFSO = Nothing Set oFolder = Nothing Set oFileCollection = Nothing Set oFile = Nothing

Schedule the task to purge older backup files Schedule the script called D:\scripts\delete_old_backups.vbs daily to purge older backup files.

About this task

CAUTION: This script deletes every file in the D:\Cisco\9xxx\config directory with a .config file extension older

than seven days.

Prerequisites

Obtain the password for the [Domain]\svc-vmfms01 account from your VMware administrator.

Steps

1. To run the .vbs script daily at 01:00, select Start > Programs > Accessories > System Tools > Scheduled Tasks

2. Browse to D:\scripts\delete_old_backups.vbs.

3. Use the credentials for the [Domain}\svc-vmfms01 account to run the task.

4. On the Schedule tab, schedule the task to run daily at 1:00 AM.

118 Back up Cisco MDS switches

Configure VMware Enhanced Linked Mode (VMware vSphere 6.0)

Introduction One of the advantages of a Dell EMC Converged System is delivery of a preconfigured physical and logical working system. Converged Systems are physically and logically configured during the manufacturing process. If you have multiple Converged Systems, you can use Enhanced Linked Mode (ELM) with VMware vSphere 6.0 to log in to a single VMware vCenter. Then, you can operate, manage, and maintain multiple VMware vCenter servers. The installation prerequisites, require that VMware vSphere 6.0 ELM be configured on the customer premises.

If you want to configure ELM, Dell EMC recommends that you contact Dell EMC Professional Services to have them perform the site analysis, installation, and configuration.

Dell EMC supports the following ELM with VMware vSphere 6.0 configurations:

One or two VMware vCenter Servers that are linked to two Platform Service Controllers (PSCs) in one Converged System Two or more VMware vCenter Servers that are linked to two or more PSCs across two or more Converged Systems in a data center Two or more VMware vCenter Servers that are linked to two or more PSCs across two or more Converged Systems across two data

centers

The configuration of ELM with VMware vSphere 6.0 is not be addressed in this document. Deployment of ELM with VMware vSphere 6.0 cannot be reversed. ELM with VMware vSphere 6.0 is managed as a complete system and should be considered a fault, operational, and maintenance domain. Any ELM VMware vSphere 6.0 configuration must be compatible with backup and restore processes for the following in a single VMware vSphere 6.0 Single Sign-On domain:

All VMware vSphere PSCs (PSC) All VMware vCenter servers

Use the following links to obtain additional information about Enhanced Linked Mode:

VMware vSphere 6.0 link: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc%2FGUID-6ADB06EF-E342-457E- A17B-1EA31C0F6D4B.html

VMware ELM with VMware vSphere 6.0 use cases ELM with VMware vSphere 6.0 can be used several situations.

The following use cases are focused on single pane of glass management:

ELM with VMware vSphere provides a single interface to manage multiple VMware vCenter servers using two shared VMware vSphere PSCs in the same Converged System.

ELM with VMware vSphere is used to integrate VMware vCenter Management for two Converged Systems in the same data center. ELM with VMware vSphere 6.0 with two Converged Systems is an operational, fault and management domain. Exceeding this approach results in an increase in the complexity of the operational, fault and management domain. Each Converged System has multiple VMware vCenter servers. In this scenario, compute, network, and storage resources are not shared between the two or more discrete VMware vCenter servers that are located in each Converged System.

ELM with VMware vSphere is used to integrate VMware vCenter Management for two Converged Systems in separate data centers. Exceeding this approach results in an increase in the complexity of the operational, fault, and management domain. Compute, network, and storage resources are not shared between the two or more discrete VMware vCenter servers that are located in separate data centers. This configuration is similar to a configuration for two Converged Systems in the same data center, but introduces network latency.

16

Configure VMware Enhanced Linked Mode (VMware vSphere 6.0) 119

Simplify VMware vSphere 6.0 management with more than two Converged Systems or VMware vCenter servers by using an AMP-2S with an SMP/VMP configuration.

Back up and restoring Converged Systems with VMware ELM Use this information to review backup and recovery capabilities.

1. Deploy and test a Data Protection and Recovery solution for the backup and recovery of the management VMware vSphere environment. Testing is especially important with ELM configurations with multiple PSCs that maintain replication synchronization using sequence numbers. See the following links for important backup information:

VMware vSphere 6.0 Backing up and Restoring a VMware vCenter server environment:

https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-539B47B4-114B-49BC-9736- F14058127ECA.html

VMware vSphere 6.0 Backing up and restoring VMware vCenter server 6.0 external deployment models (KB 2110294)

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2110294 Possible VMware vSphere.local domain inconsistencies after restoring a Platform Services Controller 6.0 Node (2086001):

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2086001 2. See the VMware vSphere 6 Data Protection Administration Guide. The document describes how to use the VMware Data Protection

appliance for a direct-to-host emergency restore when VMware vCenter server is not available. The following document describes recommendations, limitations, and unsupported features:

https://docs.vmware.com/en/VMware-vSphere/6.0/vmware-data-protection-administration-guide-60.pdf 3. You need a tested backup and recovery solution for the VMware vSphere 6.0 PSCs and VMware vCenter servers. Do not proceed

with a VMware vSphere 6.0 ELM configuration without it. ELM adds complexity to the backup and recovery solution. The number of PSCs, VMware vSphere 6.0 PSCs, and VMware vCenter servers require different backup strategies.

AMP design (AMP-2S only) Dell EMC manufacturing configures the AMP with VMware vSphere 6.0 (AMP-2S only) using only VMware recommended topologies. Deployment of the PSC and VMware vCenter using a nonrecommended topology may prevent backing up and restoring a VMware vCenter server environment with a PSC.

Review the following link for recommend topologies:

VMware vSphere 6.0 Recommended Topologies

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2108548

Each Converged System participating in ELM must continue to maintain a functioning AMP. Each Converged System VMware vSphere environment must not rely on the VMware vSphere infrastructure of another Converged System to operate correctly. All VMware vSphere 6.0 management VMs in a Converged System must use local storage for the AMP-2P M4, or shared VNXe storage for the AMP-2S M4.

External PSCs are required for VMware vSphere 6.0 ELM. Dell EMC does not recommend embedded VMware PSCs.

Dell EMC does not recommend the deployment of a PSC SSO domain with multiple SSO sites. The deployment of multiple sites impacts the VMware vSphere 6.0 backup and recovery procedure. See the following link for backup limitations with multisite SSO:

VMware vSphere 6.0 Backing up and restoring a VMware vCenter server environment:

https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-539B47B4-114B-49BC-9736- F14058127ECA.html

With VMware vSphere 6.0, you cannot use PSC snapshots with multisite or HA configurations. See the following link: FAQ: VMware PSC in VMware vSphere 6.0 (2113115)

Dell EMC recommends the deployment of the vCSA. However both the vCSA and VMware vCenter for Windows are supported with ELM.

After delivery and implementation, ensure that the AMP servers have network connectivity and sufficient resources to meet any additional workload. A redundant AMP is recommended.

VMware vSphere 6.0 PSC High Availability requires a load balancer. Load Balancers are not used with the Converged System. During deployment, a VMware vCenter must be associated with a local PSC. If a PSC fails, the VMware vCenter must be manually repointed to a secondary PSC.

120 Configure VMware Enhanced Linked Mode (VMware vSphere 6.0)

Standard VMware vSphere 6.0 design for a Converged System includes one VMware vCenter server and a minimum of two PSCs.

For best performance, split multiple VMware vCenter servers between PSCs in the same physical Converged System or physical data center.

At minimum, ELM requires IP connectivity for the ESXI management VLANs between the Converged Systems joined in an ELM configuration. Validate IP connectivity between the two VMware vSphere 6.0 vcesys_esx_mgmt VLANs. Verify that all required protocols and ports are allowed on any firewalls between the two vcesys_esx_mgmt VLANs.

See the following VMware KB article for additional information for VMware vSphere 6.0:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2106283

For VMware vSphere 6.0 management traffic, extend the QoS marking across any metro or WAN links connecting separate physical data centers.

VMware vSphere 6.0 ELM configurations must use consistent IP MTU sizes with physical and logical network switches and VMkernel ports.

VMware ELM scalability planning Determine the number of PSCs and VMware vCenter servers that are needed for an ELM configuration with VMware vSphere 6.0 in an SSO Domain and site.

Determine if the requested number of PSCs and VMware vCenter servers is compatible with VMware vSphere 6.0 configuration maximum limits. Use the following link to see the latest VMware vSphere 6.0 ELM configuration maximums:

https://www.vmware.com/pdf/vsphere6/r60/vsphere-60-configuration-maximums.pdf

The following table provides the ELM with VMware vSphere 6.0 SSO configuration maximum limitations:

Parameter Value

Maximum number of linked VMware vCenter servers per SSO Domain 10

Maximum number of PSCs per VMware vSphere domain 8

Maximum number of PSCs per site, behind a load balancer 4

PSC management limits One PSC 4 VMware vCenter Servers

Two PSCs 8 VMware vCenter Servers

Three PSCs 10 VMware vCenter Servers

Maximum number of VMware solutions that are connected to a single PSC

Each VMware vCenter server is considered a VMware solution.

4

Maximum number of VMware solutions in a VMware vSphere domain

Each VMware vCenter server is considered a VMware solution.

10 (This number includes the VMware vCenter server).

Use the following guidelines when determining the maximum number of VMware vCenter servers per SSO domain configuration:

Determine the number of the linked VMware vCenter servers. This number defines the maximum number of VMware vCenter servers that can be supported in an Enhanced Linked Mode (ELM) configuration. By definition, an ELM consists of a single SSO domain. You can have a maximum of 10 VMware vCenter servers per SSO domain.

Determine the maximum number of PSCs per VMware vSphere Domain. This number defines the maximum number of PSCs that can be part of a single SSO domain. You can have a maximum of 8 PSCs per SSO domain.

The maximum number of PSCs per site behind a load balancer adds another constraint when using a load balancer with your PSCs. You can have a maximum of 4 PSCs behind a load balancer.

Configure VMware Enhanced Linked Mode (VMware vSphere 6.0) 121

Intra Converged System VMware ELM scalability planning Determine the maximum number of VMware vCenter servers with ELM that can be configured in a Converged System that includes two PSCs.

A standard Converged System configuration with two PSCs can have a maximum of eight VMware vCenter servers. Half of the VMware vCenter servers point to the first PSC, while the second half point to the second PSC. Supporting ten VMware vCenter servers in a single Converged System requires three PSCs. Three PSCs in a single Converged System SSO Domain, while viable, is not a standard Converged System design.

NOTE: There is no available capacity to repoint a VMware vCenter server to a different PSC under the following

conditions:

Two PSCs are deployed in a Converged System.

Each PSC has four VMware vCenter servers.

Repointing one of the VMware vCenter servers requires a non-standard three-PSC configuration.

Dell EMC recommends two PSCs which can support two VMware vSphere 6.0 VMware vCenter servers. Minimizing the number of PSCs and VMware vCenter servers in an ELM configuration reduces the size of the fault, operation, management domain, and RCM upgrade complexity. Two VMware vCenter servers can support the number of compute servers in the Converged System. The following table defines the maximum number of compute hosts per Converged System:

VxBlock or Vblock System Type Number of Compute Servers (half-width)

VxBlock or Vblock 350 256

VxBlock or Vblock 540 256

VxBlock or Vblock 740 512

Deployment of more than one VMware vCenter server per Converged System requires the deployment of a redundant AMP server with an external VNXe. Each AMP server must be appropriately scaled to support multiple VMware vCenter servers.

Scale the entire Converged System AMP, network, storage, and compute environment resources appropriately when deploying multiple VMware vCenter servers and the associated resources in a Converged System.

Inter Converged System VMware ELM scalability planning in Converged Systems in a single physical data center Determine the maximum number of which can be configured with ELM and VMware vSphere 6.0.

Scenario 1: Each Converged System is deployed with two PSCs.

A standard Converged System configuration with two PSCs can have a maximum of four Converged Systems. A minimum of one VMware vCenter server is required for each Converged System. The maximum number of VMware vCenter servers with ELM is limited to ten. Each of the four Converged Systems can support more than one VMware vCenter servers. In this configuration, you must maintain the Dell EMC VMware vSphere software Release Certification Matrix (RCM) consistently across all four Converged Systems. Periodically, monitor PSC replication sequence numbers to verify PSC synchronization.

Dell EMC recommends a maximum of two Converged Systems. Minimizing the number of PSCs and VMware vCenter servers in an ELM configuration reduces the size of the fault, operation, management domain, and RCM upgrade complexity. Each Converged System has two PSCs and a maximum of two VMware vCenter servers per Converged System. AMP-2S is recommended to maintain and operate and provide single pane of glass management for more than two Converged Systems.

Deployment of more than one VMware vCenter server per Converged System requires a redundant AMP with an external VNXe. Scale each AMP Server to support multiple VMware vCenter servers.

Scale the entire Converged System AMP, network, storage, and compute environment resources when deploying multiple VMware vCenter servers and the associated resources.

Determine the maximum number of Converged Systems that can be configured with ELM with VMware vSphere 6.0 in a single physical data center.

122 Configure VMware Enhanced Linked Mode (VMware vSphere 6.0)

Inter Converged System ELM scalability planning with multiple physical data centers Determine the maximum number of Converged System which can be configured with ELM with VMware vSphere 6.0 in multiple physical data centers.

Each ELM with VMware vSphere 6.0 configuration requires a minimum of two PSC servers per physical data center. If a primary PSC outage occurs, each VMware vCenter can be repointed to the secondary PSC in the same physical data center. This approach maintains a consistent level of performance, which may not be achievable when SSO authentication must traverse a WAN. A maximum of four physical data centers are supported with an ELM configuration with VMware vSphere 6.0.

A standard Converged System configuration with two PSCs supports a maximum of four Converged Systems with multiple physical data centers. Each Converged System requires a minimum of one VMware vCenter server. ELM has an upper limit of ten VMware vCenter servers. In this configuration, each of the four Converged Systems can support more than one VMware vCenter servers. In this configuration, you must maintain the Dell EMC VMware vSphere software Release Code Matrix (RCM) consistently across all four Converged Systems distributed across two physical data centers. Periodically, you must monitor PSC replication sequence numbers to verify PSC synchronization.

Dell EMC recommends a maximum of two Converged Systems in an ELM configuration with VMware vSphere 6.0 and multiple physical data centers. Dell EMC does not recommend such a large fault tolerant and data protection and recovery domain when:

The ELM configuration includes VMware vSphere 6.0. Four Converged Systems are located in two physical data centers.

Each physical data center supports one Converged System with two PSCs and a maximum of two VMware vCenter servers. Deployment of more than one VMware vCenter server per Converged System requires the deployment of a redundant AMP with an

external VNXe. Each AMP Server must be appropriately scaled to support multiple VMware vCenter servers. Scale the entire Converged System, AMP, network, storage, and compute environment resources when deploying multiple VMware

vCenter servers and the associated resources.

VMware ELM deployment information When deploying VMware ELM, replicate roles, permission, licenses, tags, and policies across linked VMware vCenter servers.

CAUTION: For VMware vSphere 6.0, Dell EMC recommends the following:

A maximum RTT of 100 milliseconds between VMware PSCs at physically separate data centers

A maximum RTT of 10 milliseconds between VMware PSCs in a site

The legacy VMware vSphere Client does not support Enhanced Linked Mode.

With VMware vSphere 6.0, you cannot consolidate multiple SSO domains in each product line.

VMware vSphere 6.0 supports both VMware vCenter Windows and vCSA in Enhanced Linked Mode.

See the following link for VMware vSphere 6.0:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113115

For VMware vSphere 6.0, Dell EMC does not recommend and does not support mixing embedded and external PSCs. A VMware vCenter server with an embedded VMware PSC is appropriate for small environments. You cannot join other VMware vCenter servers or VMware PSCs to this VMware vCenter Single Sign-On domain.

VMware vSphere 6.0 Recommended Topologies link:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2108548

The recommended topology for VMware vSphere 6.0 is to use external PSCs. If you have deployed an extra VMware vCenter in a Converged System using an embedded PSC, you must migrate the installed VMware vCenter to an external PSC. This migration is a one- way irreversible configuration. VMware does not have any supported tools or processes to reverse an ELM configuration. The required topology for ELM with VMware vSphere 6.0 is to use external PSCs. As of 6.0U1 you can repoint a VMware vCenter server to an external PSC. See the following links:

https://blogs.vmware.com/consulting/2015/03/vsphere-datacenter-design-vcenter-architecture-changes-vsphere-6-0-part-1.html

https://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-E7DFB362-1875-4BCF- AB84-4F21408F87A6.html

Migrating to an ELM configuration with VMware vSphere 6.0 is an irreversible configuration. To split an ELM configuration, build a new discrete VMware vSphere 6.0 domain with PSCs, VC, and VUM. Migrate the VMware vSphere hosts and VM guests that you want to

Configure VMware Enhanced Linked Mode (VMware vSphere 6.0) 123

split off to the newly built VMware vSphere domain. Although workarounds have been developed to split a VMware vSphere domain, VMware does not support them.

Dell EMC has made no assumptions regarding VMware vSphere vMotion support between VMware vCenter servers. Cold migration between VMware vCenter servers using a recommended L3 Provision network is possible.

Migration between VMware vCenter servers must meet the VMware requirements.

See the following link for VMware vSphere 6.0:

https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc %2FGUID-3B41119A-1276-404B-8BFB-A32409052449.html

After you deploy ELM with VMware vSphere 6.0, verify PSC associations and replication status for all deployed PSC servers. See the following link for VMware vSphere 6.0:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2127057

Update PSCs sequentially. Each software upgrade of a PSC takes approximately 30 minutes.

If a PSC is decommissioned, do not reuse the original PSC name in the same SSO domain.

If Microsoft Active Directory is deployed as an authentication source, it must be configured consistently for all PSCs in the SSO domain.

Repointing a VMware vCenter to a PSC is possible only under the following conditions:

Two separate VMware vSphere 6.0 environments have been configured using the same SSO domain name and site name. The VMware vCenter that you want to repoint is a replication partner of the existing PSC in the first VMware vSphere environment.

Deploy inter Converged System PSCs in a ring topology, whether they are located in the same physical data centers or across multiple physical data centers.

See the following link for configuring a ring topology with VMware vSphere 6.0:

https://virtualdatacave.com/2017/02/vsphere-6-0-psc-replication-ring-topology/

https://communities.vmware.com/thread/543306

http://blog.jgriffiths.org/?p=1423

Repointing VC to a different PSC is limited to the same domain or between sites with VMware vSphere 6.0. See the following links for repointing with VMware vSphere 6.0:

How to repoint VMware vCenter server 6.0 between External PSC in a site (2113917)

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113917 Repointing VMware vCenter server 6.0 between sites in a VMware vSphere Domain (2131191)

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2131191

VMware ELM dependencies and limitations All VMware PSCs and VMware vCenter Servers participating in an ELM configuration must run the same software build number.

Ensure that your configuration meets the following requirements:

RCMs must be compatible between Converged Systems. VMware vSphere 6.0 PSCs and VMware vCenter servers must run the same build version.

Redundant AMP must be scaled out to support multiple VCs per Converged System. IP MTU sizes must be consistent between Converged Systems. Each Converged System requires a pair of PSCs.

Although ELM enables the use of PSC, Vision Intelligent Operations and VxBlock Central do not support it. They continue to collect data directly from VMware vCenter Servers.

When configuring IP connectivity between Converged Systems, validate IP connectivity between the two VMware vSphere 6.0 vcesys_esx_mgmt VLANs. Verify that all required protocols and ports are allowed on any firewalls between the two vcesys_esx_mgmt VLANs.

See the following VMware KB article for additional information with VMware vSphere 6.0:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displa%20%20yKC&externalId=2106283

All local and remote ELM with VMware vSphere 6.0 components require DNS and NTP support.

124 Configure VMware Enhanced Linked Mode (VMware vSphere 6.0)

VMware ELM references These references provide additional information about VMware ELM.

Link Topic title

2113917 How to repoint a VMware vCenter server 6.0 between External PSCs in a site

2131191 Repointing VMware vCenter server 6.0 between sites in a VMware vSphere Domain

2106736 Using the cmsso command to unregister VMware vCenter server 6.0 from Single Sign-On

2108548 List of recommended topologies for VMware vSphere 6.0

2127057 Determining replication agreements and status with the VMware Platform Services Controller 6.0

VMware ELM conclusions ELM with VMware vSphere 6.0 provides single pane of glass management for up to eight PSCs and ten VMware vCenter servers in a Single Sign-On Domain. It also provides simultaneous single pane of glass management for up to ten VMware vCenter servers. This configuration provides an operational improvement in managing multiple VMware vCenter servers. However, as the number of PSCs and VMware vCenter servers increases, the size of the VMware vSphere 6.0 fault domain becomes larger.

Processes to back up and restore any VMware vSphere component participating in ELM must be reliable and supportable across Converged Systems and data centers. To maintain synchronization of PSC replication, ensure 100% network availability between PSCs in different Converged Systems or data centers. After a PSC outage, synchronization may take some time to occur.

As the size of the SSO Sign-On domain increased, maintenance updates require more planning and coordination. VMware Build Numbers must be consistent in an ELM with VMware vSphere 6.0 configuration. Upgrading any Converged System in an ELM with VMware vSphere 6.0 configuration requires upgrading any other Converged Systems joined to the same VMware vSphere 6.0 Single Sign-On domain. Upgrades are performed in a maintenance window with enough time to install, verify and, if necessary, back out the upgrade. A VMware vSphere 6.0 Single Sign-On domain can be large. The Dell EMC approach for ELM with VMware vSphere 6.0 deployments considers the increased complexity for backup, recovery, and RCM upgrades. Deployment of AMP-2S is recommended for large SSO domains. The following table summarizes ELM with VMware vSphere 6.0 scalability with AMP-2S:

Maximum number of

PSCs

Maximum number of VMware vCenter

servers

Maximum number of VxBlock or Vblock

systems

Maximum number of Data Centers

Deploy ELM Deploy AMP-2S in an

SMP/VMP configuration

2 2 1 1 Y N

4 4 2 2 Y N

4 4 2 2 Y N

> 4 > 4 > 2 > 2 N Y

Configure VMware Enhanced Linked Mode (VMware vSphere 6.0) 125

Configure VMware Enhanced Linked Mode (vSphere 6.5U1)

Introduction to ELM (vSphere 6.5U1) One of the advantages of a Dell EMC Converged System is delivery of a preconfigured physical and logical working system.

Converged Systems are physically and logically configured during the manufacturing process. If you have multiple Converged Systems, you can use Enhanced Linked Mode (ELM) with VMware vSphere 6.5U1 to log in to a single VMware vCenter server. You can then operate, manage, and maintain multiple VMware vCenter servers. Due to the installation prerequisites, VMware vSphere 6.5U1 ELM must be configured on the customer premises. If you want to configure ELM, contact Dell EMC Professional Services to have them perform the site analysis, installation, and configuration.

Scenarios include the following:

Two or more VMware vCenter Servers that are linked to two Platform Service Controllers (PSCs) in one Converged System Two or more VMware vCenter Servers that are linked to two or more PSCs across two or more Converged Systems in a data center Two or more VMware vCenter Servers that are linked to two or more PSCs across two or more Converged Systems across two data

centers

Deployment of ELM with VMware vSphere 6.5U1 cannot be reversed. ELM with VMware vSphere 6.5U1 is managed as a complete system and should be considered a fault, operational, and maintenance domain. Any ELM with VMware vSphere 6.5U1 configuration must use the same backup and restore processes as the PSCs and VMware vCenter servers in the SSO domain.

Using Enhanced Linked Mode 6.5

Use this link to obtain additional information about Enhanced Linked Mode:

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-6ADB06EF-E342-457E- A17B-1EA31C0F6D4B.html

VMware ELM with VMware vSphere 6.5U1 use cases VMware ELM with VMware vSphere 6.5U1 can be used in several situations.

The following use cases are focused on a single pane of glass management:

ELM with VMware vSphere provides a single interface to manage multiple VMware vCenter Servers using two shared VMware vSphere PSCs in the same Converged System.

ELM with VMware vSphere is used to integrate VMware vCenter Management for five Converged Systems in the same data center. ELM with VMware vSphere 6.5U1 with five Converged Systems is an operational, fault, and management domain. Exceeding this limit is not supported. Each Converged System may have multiple VMware vCenter servers. Compute, network, and storage resources are not shared between the two or more discrete VMware vCenter servers that are located in each Converged System.

ELM with VMware vSphere is used to integrate VMware vCenter Management for five Converged Systems in separate data centers. Exceeding this limit is not supported. Compute, network, and storage resources are not shared between the two or more discrete VMware vCenter servers that are located in separate data centers. This configuration is similar to a configuration for two Converged Systems in the same data center, but introduces network latency.

Use AMP-2S with an SMP/VMP configuration to simplify VMware vSphere 6.5U1 management with more than two Converged Systems or VMware vCenter Servers.

Backup and recovery for ELM 6.5 See Backing up and restoring the vCenter Server and PSC (vSphere 6.5U1) in this guide.

17

126 Configure VMware Enhanced Linked Mode (vSphere 6.5U1)

Backup and recovery guidelines Review the backup and recovery guidelines.

You can use the VMware Data Protection appliance for a direct-to-host emergency restore when VMware vCenter server is not available. See the VMware vSphere 6.5 Data Protection Administration Guide document for recommendations, limitations, and unsupported features:

https://docs.vmware.com/en/VMware-vSphere/6.5/vmware-data-protection-administration-guide-61.pdf

With VMware vSphere 6.5U1, you cannot use PSC snapshots with multisite or HA configurations.

Use a tested backup and recovery solution for the VMware vSphere 6.5U1 PSCs and VMware vCenter servers. Without this configuration, do not proceed with a VMware vSphere 6.5U1 ELM configuration. ELM adds complexity to the backup and recovery solution. Factors include the number of PSCs, VMware vSphere 6.5U1 PSCs, and VMware vCenter servers, each of which have differences in their respective backup strategies.

Converged System AMP design (ELM/VMware vSphere 6.5U1) This applies to AMP-2. Dell EMC manufacturing configures the AMP with VMware vSphere 6.5U1 using only VMware recommended topologies.

Deployment of the PSC and VMware vCenter server using a nonrecommended topology may prevent backing up and restoring a VMware vCenter server environment with a PSC.

VMware vSphere 6.5U1 Recommended Topologies https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147672

The following figure includes the following topology:

One SSO domain One SSO site Two or more vCenter Servers with two external PSC in a single Converged System

The following figure includes the following topology:

Configure VMware Enhanced Linked Mode (vSphere 6.5U1) 127

One SSO domain One SSO site One or more VMware vCenter Servers with two external PSC in two or more Converged Systems

The following figure includes the following topology:

One SSO domain One or more SSO sites One or more VMware vCenter Servers with two external PSC in two or more Converged Systems across multiple sites

128 Configure VMware Enhanced Linked Mode (vSphere 6.5U1)

Each Converged System participating in ELM must continue to maintain a functioning AMP. To maintain the original Converged System premise of independence, each VMware vSphere environment must not rely on the VMware vSphere infrastructure of another Converged System to operate correctly. All VMware vSphere 6.5U1 management VMs in a Converged System must use the following:

AMP type Storage

AMP-2P M4 Local storage array

AMP-2S M4 Shared storage array

AMP-2S M4 Shared VNX-e storage array

External PSCs are required for VMware vSphere 6.5U1 ELM. Dell EMC does not recommend embedded VMware PSCs.

Dell EMC recommends the deployment of the vCSA. However both the vCSA and VMware vCenter for Windows are supported with ELM. VMware vCenter 6.5 for Windows is not supported on Converged Systems.

After delivery and implementation, ensure that the AMP servers have network connectivity and sufficient resources to meet any additional workload.

Load balancers are not supported with the Converged System. During deployment, a VMware vCenter server must be associated with a local PSC. If a PSC fails, manually repoint the VMware vCenter server to a secondary PSC.

Standard VMware vSphere 6.5U1 design for a Converged System includes one VMware vCenter server and a minimum of two PSCs.

At minimum, ELM requires IP connectivity for the ESXi management VLANs between the Converged Systems joined in an ELM configuration. Verify the IP connectivity between the two VMware vSphere 6.5U1 vcesys_esx_mgmt VLANs. Also verify that all required protocols and ports are allowed on any firewalls between the two vcesys_esx_mgmt VLANs.

The following table provides the ports that are required between Converged Systems for ELM functionality:

Port Protocol Description Required For Node to Node Communication

389 TCP/UDP Port 389 must be open on the local and all remote instances of VMware vCenter server. Port 389 is the LDAP port for the

Windows installations and appliance deployments of PSC vCenter Server to PSC

VMware vCenter Server to PSC

Configure VMware Enhanced Linked Mode (vSphere 6.5U1) 129

Port Protocol Description Required For Node to Node Communication

Directory Services for the VMware vCenter server group. If another service is running on this port, it might be preferable to delete it or change its port to a different port. You can run the LDAP service on ports from 102565535.

PSC to PSC Platform Services Controller to PSC

2012 TCP Control Interface RPC for vCenter Single sign-on

Windows installations and appliance deployments of PSC

PSC to PSC

2015 TCP DNS Management Windows installations and appliance deployments of PSC

PSC to PSC

See the following VMware KB article for additional information for VMware vSphere 6.5U1 communication port requirements:

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.upgrade.doc/GUID-925370DD-E3D1-455B-81C7- CB28AAF20617.html

Extend the QoS marking for the VMware vSphere 6.5U1 management traffic across any metro or WAN links connecting separate physical data centers.

VMware vSphere 6.5U1 ELM configurations must use consistent IP MTU sizes with physical and logical network switches and VMkernel ports.

VMware ELM scalability planning (vSphere 6.5U1) Determine the number of PSCs and VMware vCenter servers that are needed for an ELM configuration with VMware vSphere 6.5U1 in an SSO Domain and site.

Complete an ELM scalability assessment to determine if the requested number of PSCs and VMware vCenter servers is compatible with VMware vSphere 6.5U1 configuration maximum limits. See the following link for the latest VMware vSphere 6.5U1 ELM configuration maximums:

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.configmax.doc/GUID-BBD10A8B-7BDC-45F3-9CA4- C44EE77749BA.html

The following table provides the ELM with VMware vSphere 6.5U1 SSO configuration maximum limitations:

Parameter Value

Maximum number of linked VMware vCenter Servers per SSO domain

15

Maximum number of PSCs per VMware vSphere domain 10

Maximum number of PSCs per site, behind a load balancer

4

PSC management Limits

One PSC 8 VMware vCenter Servers

Two PSCs 15 VMware vCenter Servers

Maximum number of VMware solutions that are connected to a single PSC

Each VMware vCenter server is considered a VMware solution.

8

Maximum number of VMware solutions in a VMware vSphere domain

Each VMware vCenter Server is considered a VMware solution.

15 (This number includes VMware vCenter Servers).

Maximum number of Converged Systems 5 (with 2 PSCs each)

130 Configure VMware Enhanced Linked Mode (vSphere 6.5U1)

Use the following guidelines when determining the maximum number of VMware vCenter Servers per SSO domain configuration:

The number of linked VMware vCenter Servers defines the maximum number of VMware vCenter Servers that can be supported in an Enhanced Linked Mode (ELM) configuration. By definition, an ELM consists of a single SSO domain. You can have a maximum of 15 VMware vCenter Servers per SSO domain.

Determine the maximum number of PSCs per VMware vSphere domain, which defines the maximum number of PSCs that can be part of a single SSO domain. You can have a maximum of 10 PSCs per SSO domain.

Intra Converged System VMware ELM scalability planning (VMware vSphere 6.5U1) Determine the maximum number of VMware vCenter servers with ELM that can be configured in a Converged System configured with two PSCs.

A standard Converged System configuration with two PSCs can have a maximum of 15 VMware vCenter servers. Half of the VMware vCenter servers point to the first PSC, while the second half point to the second PSC.

The following table defines the maximum number of compute hosts per Converged System:

VxBlock System Number of compute servers (half-width)

VxBlock 350 256

VxBlock 540 256

VxBlock 740 512

AMP-2: Deployment of more than one VMware vCenter server per Converged System requires the deployment of a redundant AMP server with an external storage array. Each AMP server must be appropriately scaled to support multiple VMware vCenter servers.

Scale all Converged System AMP, network, storage, and compute environment resources appropriately when deploying multiple VMware vCenter servers with their associated resources in a Converged System.

Inter Converged System VMware ELM scalability planning in a single physical data center (VMware vSphere 6.5U1) Determine the maximum number of Converged Systems configured with VMware ELM and VMware vSphere 6.5U1.

Scenario 1: Each Converged System is deployed with two PSCs.

A standard Converged System configuration with two PSCs can have a maximum of five Converged Systems. A minimum of one VMware vCenter server is required for each Converged System. The maximum number of VMware vCenter servers with ELM is limited to 15. Each of the five Converged Systems can support more than one VMware vCenter servers. In this configuration, you must maintain the Dell EMC VMware vSphere software Release Certification Matrix (RCM) consistently across all five Converged Systems. Periodically, monitor PSC replication sequence numbers to verify PSC synchronization.

AMP-2S: Deployment of more than one VMware vCenter server per Converged System requires a redundant AMP server with an external storage array. Scale each AMP Server to support multiple VMware vCenter servers.

Scale the entire Converged System AMP, network, storage, and compute environment resources when deploying multiple VMware vCenter servers with its associated resources in a Converged System.

Determine the maximum number of Converged Systems that can be configured with ELM with VMware vSphere 6.5U1 in a single physical data center.

Inter Converged System VMware ELM scalability planning with multiple physical data centers (VMware vSphere 6.5U1) Determine the maximum number of Converged System that can be configured with VMware ELM with VMware vSphere 6.5U1 in multiple physical data centers.

Each VMware ELM with VMware vSphere 6.5U1 configuration requires a minimum of two PSCs per physical data center. If a primary PSC outage occurs, each VMware vCenter server can be repointed to the secondary PSC in the same physical data center. This

Configure VMware Enhanced Linked Mode (vSphere 6.5U1) 131

approach maintains a consistent level of performance. A maximum of five physical data centers are supported with an VMware ELM configuration with VMware vSphere 6.5U1.

A standard Converged System configuration with two PSCs supports a maximum of five Converged Systems with multiple physical data centers. Each Converged System requires a minimum of one VMware vCenter server. ELM has an upper limit of 15 VMware vCenter servers. In this configuration, each of the four Converged Systems can support more than one VMware vCenter servers. Maintain the Dell EMC VMware vSphere software Release Certification Matrix (RCM) consistently across all five Converged Systems that are distributed across physical data centers. Periodically, monitor PSC replication sequence numbers to verify PSC synchronization.

Deployment of more than one VMware vCenter server per Converged System requires the deployment of a redundant AMP system. Each AMP system must be appropriately scaled to support multiple VMware vCenter servers.

Scale all Converged System, AMP, network, storage, and compute environment resources when deploying multiple VMware vCenter servers and the associated resources in a Converged System.

VMware ELM deployment information (VMware vSphere 6.5U1) When deploying VMware ELM, replicate roles, permission, licenses, tags, and policies across linked VMware vCenter servers.

CAUTION: For VMware vSphere 6.5U1, Dell EMC recommends the following:

No higher than 150 milliseconds RTT between VMware PSCs at physically separate data centers

No higher than 10 milliseconds RTT between VMware PSCs in a site

The legacy VMware vSphere Client does not support Enhanced Linked Mode.

With VMware vSphere 6.5U1, you cannot consolidate multiple SSO domains in each product line.

For VMware vSphere 6.5U1, Dell EMC does not recommend and does not support mixing embedded and external PSCs. A VMware vCenter server with an embedded VMware PSC is appropriate for small environments. You cannot join other VMware vCenter servers or VMware PSCs to this VMware vCenter Single Sign-On domain.

Dell EMC has made no assumptions regarding VMware vSphere vMotion support between VMware vCenter servers. Cold migration between VMware vCenter servers using a recommended L3 Provision network is possible.

Migration between VMware vCenter servers must meet the VMware requirements.

After you deploy ELM with VMware vSphere 6.5U1, verify PSC associations and replication status for all deployed PSC servers. See the following link for VMware vSphere 6.x:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2127057

Update PSCs sequentially. Each software upgrade of a PSC may take 30 minutes approximately.

If a PSC is decommissioned, do not reuse the original PSC name in the same SSO domain.

If Microsoft Active Directory is deployed as an authentication source, it must be configured consistently for all PSCs in the SSO domain.

Repointing a VMware vCenter server to a PSC is possible only under the following conditions:

Two separate VMware vSphere 6.5U1 environments have been configured using the same SSO domain name and site name. The VMware vCenter server that you want to repoint is a replication partner of the existing PSC in the first VMware vSphere

environment.

Deploy inter Converged System PSCs in a ring topology, whether they are located in the same physical data center or across multiple physical data centers.

See the following link for configuring a ring topology with VMware vSphere 6.5U1:

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.psc.doc/GUID-62CC201A-01ED-4116-8604-FF123481DAFC.html

Repointing a vCenter server to a different PSC is limited to the same domain with VMware vSphere 6.5U1. See the following link for repointing with VMware vSphere 6.5U1 between External PSCs in a site (2113917):

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-07D2C988-67A5-4FE2- A276-8B99E4909370.html

VMware ELM dependencies and limitations

All PSCs and VMware vCenter servers participating in an ELM configuration must run the same software build number.

Although ELM enables the use of PSC, Vision Intelligent Operations or VxBlock Central does not support it. Vision Intelligent Operations or VxBlock Central continues to collect data from the vCenter servers directly.

132 Configure VMware Enhanced Linked Mode (vSphere 6.5U1)

Ensure that your configuration meets the following requirements:

RCMs must be compatible between Converged Systems. VMware vSphere 6.5U1 PSCs and VMware vCenter servers must run the same build version.

IP MTU sizes must be consistent between Converged Systems. Each Converged System requires a pair of PSCs.

When configuring IP connectivity between Converged Systems, you must verify IP connectivity between the two VMware vSphere 6.5U1 vcesys_esx_mgmt VLANs. Also verify that all required protocols and ports are allowed on any firewalls between the two vcesys_esx_mgmt VLANs.

See the following VMware KB article for additional information with VMware vSphere 6.5U1:

https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.upgrade.doc/GUID-925370DD-E3D1-455B-81C7- CB28AAF20617.html

All local and remote ELM with VMware vSphere 6.5U1 components require DNS and NTP support.

Verify PSC and PSC Partner Status Dell EMC recommends that each PSC have two partners in a ring topology and a single peer in a dual PSC deployment.

About this task

This task includes the following:

Listing the PSC partners Displaying the PSC replication status

Steps

1. Use SSH to connect to the PSC CLI and run the following commands to view and verify PSC partner servers:

shell.set enabled True shell cd /usr/lib/vmware-vmdir/bin ./vdcrepadmin -f showpartners -h localhost -u administrator

2. Use the following command to display replication status:

./vdcrepadmin -f showpartnerstatus -h localhost -u administrator

NOTE: Change numbers are used to maintain replication between adjacent PSCs. Each PSC uses a unique change

number. Each PSC partner should be 0 changes behind.

Determining the VMware vCenter server within a vSphere Domain Complete this task to determine ownership of each vCenter server participating in the same VMware vSphere SSO domain.

About this task

This task shows how to determine ownership in the following ways:

Using the GUI on VCSA Using VCSA CLI commands Using a Windows-based vCenter server

Steps

1. Find ownership using the GUI on the VCSA as follows: Log in to the vCenter server. Under the advanced settings, review the property config.vpxd.sso.admin.uri which specifies the configured PSC.

2. Find ownership using VCSA CLI commands as follows:

a. Use SSH to connect to the VCSA.

Configure VMware Enhanced Linked Mode (vSphere 6.5U1) 133

b. Enter shell.set enabled True.

c. Enter cd /usr/lib/vmware-vmafd/bin.

d. Enter ./vmafd-cli get-ls-location --server-name localhost. The command returns the PSC vCenter server used.

3. Find ownership on a Windows-based VMware vCenter server as follows: Enter C:\Program Files\VMware\vCenter Server \vmafd\vmafd-cli get-ls-location --server-name localhost. The command returns the PSC vCenter server used.

Reconfiguring the ring topology Complete this task to reconfigure the ring topology.

Steps

1. Use SSH to connect to the PSC.

2. Enter shell.set enabled True.

3. Enter cd /usr/lib/vmware-vmdir/bin.

4. Break the old partnership as follows:

a. Use SSH to connect to the PSC CLI that you want to decommission and run the following commands to determine the node-pnid information: Stop all services.

shell.set enabled True shell cd /usr/lib/vmware-vmafd/bin ./vmafd-cli get-pnid -server-name localhost

b. Run the following commands to determine the partner PSC servers:

cd /usr/lib/vmware-vmdir/bin ./vdcrepadmin f showpartners h localhost u administrator service-control -stop -all

c. On one of the partner PSCs of the PSC that you want to decommission, run the following command to decommission the node:

cmsso-util unregister -node-pnid --hostId --username administrator@vsphere.local

5. Use SSH to connect to one of the PSCs which you want to establish a partnership. Provide the FQDN of the peer PSC with which you want to establish partnership. Type ./vdcrepadmin -f createagreement -2 -h server-name -u Administrator -H -u Administrator

VMware ELM references (vSphere 6.5U1) These references provide additional information about VMware ELM.

Link Topic title

2113917 How to repoint a VMware vCenter server 6.5 between External PSCs in a site.

2127057 Determining replication agreements and status with the VMware Platform Services Controller 6.5.

VMware ELM conclusions (VMware vSphere 6.5U1) Conclusions for VMware ELM with vSphere 6.5U1 are provided.

VMware ELM with VMware vSphere 6.5U1 provides a single pane of glass management for the following in a Single Sign-On domain:

Up to 10 VMware Platform Service Controllers (PSC) Up to 15 VMware vCenter servers

134 Configure VMware Enhanced Linked Mode (vSphere 6.5U1)

This single pane of management provides an operational improvement in managing multiple VMware vCenter Servers. As the number of VMware PSCs and vCenter servers increases, the size of the VMware vSphere 6.5U1 fault domain becomes larger.

Processes to back up and restore any VMware vSphere component participating in ELM must be reliable and supportable across Converged Systems and data centers. Maintaining synchronization of VMware PSC replication requires 100 percent network availability between PSCs in different Converged Systems or data centers. After a PSC outage, synchronization may take some time to occur.

As the size of the SSO domain increases, maintenance updates require more planning and coordination. VMware build numbers must be consistent in an ELM with VMware vSphere 6.5U1 configuration. Upgrading any Converged System in an ELM with VMware vSphere 6.5U1 configuration requires a corresponding upgrade for any other Converged Systems joined to the same VMware vSphere 6.5U1 SSO domain.

Perform upgrades in a maintenance window with time allocated to install, verify and, if necessary, back out the upgrade. A VMware vSphere 6.5U1 SSO domain may be large. The Dell EMC approach for ELM with VMware vSphere 6.5U1 deployments assesses the increased complexity for backup and recovery and RCM upgrades. The following table summarizes how ELM with VMware vSphere 6.5U1 scales with AMP:

Maximum number of PSCs

Maximum number of VMware vCenter servers

Maximum number of VxBlock Systems

Maximum number of data centers

Deploy ELM Deploy AMP-2S in an SMP/VMP configuration

2 2 1 1 Y N

4 4 2 2 Y N

4 4 2 2 Y N

4 4 2 2 Y Y

>10 >15 >5 >5 N N

Configure VMware Enhanced Linked Mode (vSphere 6.5U1) 135

Manage VMware Embedded Linked Mode (VMware vSphere 6.7)

One advantage of a Converged System is delivery of a preconfigured physical and logical working system. Converged Systems are physically and logically configured during the manufacturing process.

If you have multiple Converged Systems, you can use Embedded Linked Mode (ELM) with VMware vSphere 6.7 to log in to a single VMware vCenter. You can then operate, manage, and maintain multiple VMware vCenter servers. Due to the installation prerequisites, VMware ELM must be configured on the customer premises. If you want to configure ELM, contact Dell EMC Professional Services to have them perform the site analysis, installation, and configuration.

vCenter Embedded Linked Mode is enhanced linked mode support for vCenter Server Appliance with an embedded Platform Services Controller.

With vCenter Embedded Linked Mode, you can connect a vCenter Server Appliance with an embedded Platform Services Controller together to form a domain. vCenter Embedded Linked Mode is not supported for Windows vCenter Server installations.

Scenarios include the following:

Two or more VMware vCenter Servers with Embedded Platform Service Controller in one Converged System Two or more VMware vCenter Servers with Embedded Platform Service Controller across two or more Converged Systems in a data

center

Embedded Linked Mode is not supported across sites.

Deployment of ELM with VMware vSphere 6.7 cannot be reversed. ELM with VMware vSphere 6.7 is managed as a complete system and should be considered a fault, operational, and maintenance domain. Any ELM with VMware vSphere 6.7 configuration must use backup and restore processes compatible with the associated VMware vCenter servers in the Single Sign-On domain.

Configure VMware Embedded Linked Mode (VMware vSphere 6.7) VMware vCenter Embedded Linked Mode (ELM) is enhanced linked mode support for vCenter Server Appliance with an embedded Platform Services Controller.

About this task

Use Embedded Linked mode with VMware vSphere 6.7 to log in to a single VMware vCenter server. You can then operate, manage, and maintain multiple VMware vCenter servers on multiple Converged Systems.

Converged Systems are physically and logically configured during the manufacturing process. Due to the installation prerequisites, VMware vSphere 6.7 ELM must be configured on the customer premises.

However, if multiple Converged Systems are ordered and the systems are not expected to join the existing customer domain, ELM can be configured during manufacturing. If you want to configure ELM, Dell EMC recommends that you have Dell EMC Professional Services perform the site analysis, installation, and configuration.

The following list outlines some of the guidelines for ELM in a VxBlock System:

Linked VMware vCenter servers must be in the same SSO domain. If different SSO domains are required, linked mode is not possible. A single SSO domain must have no more than 8 linked VMware vCenter servers.

NOTE: Embedded Linked Mode is not supported across physical sites.

The following figure shows a topology with:

A single SSO domain A single SSO site VMware vCenter servers with embedded PSC and two converged systems

18

136 Manage VMware Embedded Linked Mode (VMware vSphere 6.7)

The following figure shows a topology with:

A single SSO domain A single SSO site VMware vCenter servers with embedded PSC and three converged systems

Steps

Log in to the vCenter Server appliance and perform the following steps to create the replication agreement:

a. Log in to the vCenter management interface using root user: https:// :5480/ .Select Access, then enable SSH and BASH shell.

b. SSH into vCenter as root. To log in to shell mode, type shell.

c. To verify the current replication partner, enter the following command:

/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartners -h -u administrator

d. To create a replication partner for the PSC, enter the following command:

Manage VMware Embedded Linked Mode (VMware vSphere 6.7) 137

/usr/lib/vmware-vmdir/bin/vdcrepadmin -f createagreement -2 -h -H Replication Partner IP Address> -u administrator

Deployment of ELM cannot be reversed. ELM is managed as a complete system and should be considered a fault, operational, and maintenance domain. Any ELM configuration must be compatible with backup and restore processes for the associated VMware vCenter servers in a single VMware vSphere SSO domain.

138 Manage VMware Embedded Linked Mode (VMware vSphere 6.7)

Manage VMware Embedded Linked Mode (VMware vSphere 6.5)

One advantage of a Converged System is delivery of a preconfigured physical and logical working system. Converged Systems are physically and logically configured during the manufacturing process.

If you have multiple Converged Systems, you can use Embedded Linked Mode (ELM) with VMware vSphere 6.5 to log in to a single VMware vCenter. You can then operate, manage, and maintain multiple VMware vCenter servers. Due to the installation prerequisites, VMware ELM must be configured on the customer premises. If you want to configure ELM, contact Dell EMC Professional Services to have them perform the site analysis, installation, and configuration.

vCenter Embedded Linked Mode is enhanced linked mode support for vCenter Server Appliance with an embedded Platform Services Controller.

With vCenter Embedded Linked Mode, you can connect a vCenter Server Appliance with an embedded Platform Services Controller together to form a domain. vCenter Embedded Linked Mode is not supported for Windows vCenter Server installations.

Scenarios include the following:

Two or more VMware vCenters with Embedded Platform Service Controller in one Converged System Two or more VMware vCenters with Embedded Platform Service Controller across two or more Converged Systems in a data center Two or more VMware vCenters with Embedded Platform Service Controller across two or more Converged Systems across two data

centers

Embedded Linked Mode is not supported across sites.

Deployment of ELM with VMware vSphere 6.5 cannot be reversed. ELM with VMware vSphere 6.5 is managed as a complete system and should be considered a fault, operational, and maintenance domain. Any ELM with VMware vSphere 6.5 configuration must use backup and restore processes compatible with the associated VMware vCenter servers in the Single Sign-On domain.

Configure VMware Embedded Linked Mode (VMware vSphere 6.5) vCenter Embedded Linked Mode (ELM) is enhanced linked mode support for vCenter Server Appliance with an embedded Platform Services Controller.

About this task

Use Embedded Linked mode with VMware vSphere 6.5 to log in to a single VMware vCenter server. You can then operate, manage, and maintain multiple VMware vCenter servers on multiple Converged Systems.

Converged Systems are physically and logically configured during the manufacturing process. Due to the installation prerequisites, VMware vSphere 6.5 ELM must be configured on the customer premises.

However, if multiple Converged Systems are ordered and the systems are not expected to join the existing customer domain, ELM can be configured during manufacturing. If you want to configure ELM, Dell EMC recommends that you have Dell EMC Professional Services perform the site analysis, installation, and configuration.

The following list outlines some of the guidelines for ELM in a VxBlock System:

Linked VMware vCenter servers must be in the same SSO domain. If different SSO domains are required, linked mode is not possible. A single SSO domain must have no more than 8 linked VMware vCenter servers.

NOTE: Embedded Linked Mode is not supported across physical sites.

The following figure shows a topology with:

A single SSO domain A single SSO site

19

Manage VMware Embedded Linked Mode (VMware vSphere 6.5) 139

VMware vCenter servers with embedded PSC and two converged systems

A single SSO domain A single SSO site VMware vCenter servers with embedded PSC and three converged systems

Steps

Log in to the vCenter Server appliance and perform the following steps to create the replication agreement:

a. Log in to the vCenter management interface using root user: https:// :5480/ .Select Access, then enable SSH and BASH shell.

b. SSH into vCenter as root. To log in to shell mode, type shell.

c. To verify the current replication partner, enter the following command:

type: /usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartners -h -u administrator

d. To create a replication partner for the PSC, enter the following command:

140 Manage VMware Embedded Linked Mode (VMware vSphere 6.5)

/usr/lib/vmware-vmdir/bin/vdcrepadmin -f createagreement -2 -h -H Replication Partner IP Address> -u administrator

Deployment of ELM cannot be reversed. ELM is managed as a complete system and should be considered a fault, operational, and maintenance domain. Any ELM configuration must be compatible with backup and restore processes for the associated VMware vCenter servers in a single VMware vSphere SSO domain.

Manage VMware Embedded Linked Mode (VMware vSphere 6.5) 141

Manage VMware Enhanced Linked Mode Use VMware ELM with VMware vSphere to log in and manage a single VMware vCenter with VMware vCenter Servers for VMware vSphere 6.5 or later.

Due to the installation prerequisites, VMware Enhanced Linked Mode (ELM) must be configured on site. To configure VMware ELM, contact your Dell Technologies Sales Engineer to perform the site analysis, installation, and configuration.

The following VMware ELM scenarios are provided:

Two or more VMware vCenter Servers that are linked to two VMware Platform Service Controllers (PSCs) in one VxBlock System. Two or more VMware vCenter Servers, linked to two or more VMware PSCs, across two or more VxBlock Systems in a data center.

The following list outlines the requirements for VMware ELM in a VxBlock System 1000:

A maximum of two production VMware vCenter Servers in the default AMP-VX (four nodes). Up to eight linked VMware vCenter Servers are allowed in a single VxBlock System 1000 or across multiple VxBlock Systems 1000. A maximum of 625 hosts per linked VMware vCenter Server. Linked VMware vCenter Servers must be in the same VMware SSO domain. If different SSO domains are required, you can have more than eight VMware vCenter Servers.

Do not link the AMP-VX VMware vCenter Server and the VxBlock System VMware vCenter Server.

You cannot reverse deployment of VMware ELM with VMware vSphere 6.7 or VMware vSphere 6.5U1. VMware ELM with VMware vSphere 6.7 or VMware vSphere 6.5U1 is managed as a complete system and should be considered a fault, operational, and maintenance domain. VMware ELM must use the same backup and restore processes as the VMware vSphere PSCs and VMware vCenter servers in the SSO domain.

Back up and restore VxBlock Systems with VMware Embedded Linked Mode (VMware vSphere 6.7) Use VMware vCenter server appliance (vCSA) native backup to back up and restore the VMware vCSA.

For backup and restore guidelines, see the following:

File-based backup and restore of VMware vCenter Server Appliance Image-based backup and restore of a VMware vCenter Server environment

VMware Enhanced Linked Mode scalability planning (VMware vSphere 6.7) Determine the number of PSCs and VMware vCenter servers that are needed for an ELM configuration with VMware vSphere in an SSO domain and SSO site.

The following table provides the ELM with VMware vSphere 6.7 SSO configuration for a VxBlock System. Dell EMC recommends these configuration limits to achieve eight linked VMware vCenter servers while maintaining N+1 redundancy for the PSCs.

Parameter Value

Number of linked VMware vCenter servers per SSO domain 8

Number of PSCs per VMware vSphere domain 5

Number of VMware vCenter servers pointing to a single PSC 2

20

142 Manage VMware Enhanced Linked Mode

Parameter Value

Number of Converged Systems 8

Number of VMware vCenter servers per PSC: First fourth VMware vCenter server

1

Number of VMware vCenter servers per PSC: Fifth eighth VMware vCenter server

2

Intra Converged System VMware Enhanced Linked Mode scalability planning Determine the number of VMware vCenter servers with ELM to configure in a Converged System.

Based on a standard Converged System configuration with two PSCs, it is recommended to have a single VMware vCenter server in a standard Converged System.

As more VMware vCenter servers are deployed into an ELM configuration, an extra PSC is deployed up to the sixth VMware vCenter server.

The first four VMware vCenter servers are associated with the first four PSCs. The fifth through eighth VMware vCenter servers are associated with the first four PSCs as well. The fifth VMware PSC remains unassociated with a VMware vCenter server for quick repointing during failure and maintaining N+1

redundancy. Deployment of more than two VMware vCenter servers may require the deployment of more AMP servers.

VMware Enhanced Linked Mode deployment information When deploying VMware ELM, replicate roles, permission, licenses, tags, and policies across linked VMware vCenter Servers with VMware vSphere 6.7 or later.

CAUTION: Use no higher than 10-ms RTT between VMware PSCs in a site.

With VMware vSphere, you cannot consolidate multiple SSO domains in each product line.

Embedded and External PSCs with VMware vSphere are not supported. If VMware vCenter Servers or VMware PSCs are deployed to their own SSO domain, you cannot join them to existing VMware vCenter SSO domains.

Dell EMC has made no assumptions regarding VMware vSphere vMotion support between VMware vCenter Servers. You can perform cold migration between VMware vCenter Servers using a recommended Layer 3 provisioned network. Migration between VMware vCenter Servers must meet the VMware requirements.

After you deploy ELM with VMware vSphere 6.7, verify VMware PSC associations and replication status for all deployed VMware PSC servers. See Determining replication agreements and status with the Platform Services Controller 6.X (2127057) https:// kb.vmware.com/s/article/2127057

Update PSCs sequentially. Each software upgrade of a PSC may take approximately 30 minutes. If a PSC is decommissioned, do not reuse the original PSC name in the same SSO domain.

If Microsoft AD is deployed as an authentication source, configure it consistently for all PSCs in the SSO domain. You can repoint a VMware vCenter server to a VMware PSC only when it is a replication partner of the existing VMware PSC.

Deploy inter-VxBlock System PSCs in a ring topology.

See Deployment Topologies with External Platform Services Controller Instances and High Availability for configuring a ring topology with VMware vSphere:

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.psc.doc/GUID-62CC201A-01ED-4116-8604-FF123481DAFC.html

Repointing VC to a different PSC is limited to the same domain with VMware vSphere 6.7. See How to repoint VMware vCenter server 6.7 between External PSC in a site (2113917) for repointing with VMware vSphere 6.7:

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.install.doc/GUID-E7DFB362-1875-4BCF- AB84-4F21408F87A6.html

Manage VMware Enhanced Linked Mode 143

VMware ELM dependencies and limitations All PSCs and VMware vCenter servers participating in an ELM configuration must run software that has the same build number.

Ensure that your configuration meets the following requirements:

RCMs must be compatible between Converged Systems. VMware PSCs and VMware vCenter servers must run the same build version.

IP MTU sizes must be consistent between Converged Systems.

Although VMware ELM enables the use of VMware PSC, VxBlock Central or Vision software does not support it. VxBlock Central or Vision software continues to collect data from the VMware vCenter servers directly.

When configuring IP connectivity between Converged Systems, you must validate IP connectivity between the two VMware vSphere 6.7 vcesys_esx_mgmt VLANs. Also verify that all required protocols and ports are enabled on any firewalls between the two vcesys_esx_mgmt VLANs.

See Required Ports for vCenter Server and Platform Services Controller for additional information:

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.upgrade.doc/GUID-925370DD-E3D1-455B-81C7- CB28AAF20617.html

All local and remote ELM components require DNS and NTP support.

The following references provide additional information about VMware ELM:

How to repoint a VMware vCenter server between External PSCs in a site Determining replication agreements and status with the VMware Platform Services Controller

VMware Enhanced Linked Mode references References provide additional information about VMware ELM.

How to repoint a VMware vCenter server between External PSCs in a site Determining replication agreements and status with the VMware Platform Services Controller

VMware Enhanced Linked Mode conclusions (VMware vSphere 6.7) Conclusions for VMware ELM are provided.

Enhanced Linked Mode provides single pane of glass management for up to five PSCs and eight VMware vCenter servers in an SSO domain. It also provides simultaneous single pane of glass management for up to eight VMware vCenter servers. This single pane of glass management provides an operational improvement in managing multiple VMware vCenter servers. As the number of PSCs and VMware vCenter servers increase, the size of the VMware vSphere 6.7 fault domain becomes larger.

Processes to back up and restore any VMware vSphere component participating in ELM must be reliable and supportable across Converged Systems and data centers. Synchronization of PSC replication requires 100% network availability between PSCs in different Converged Systems or data centers. After a PSC outage, synchronization may take some time to occur.

As the size of the SSO domain increases, maintenance updates require more planning and coordination. VMware build numbers must be consistent in an ELM with VMware vSphere 6.7 configuration. Upgrading any Converged System in an ELM with VMware vSphere 6.7 also requires a corresponding upgrade for any other Converged Systems in the same VMware vSphere 6.7 SSO domain. Perform upgrades in a maintenance window with time that is allocated to install, verify, and, if necessary, back out of the upgrade. In a large VMware vSphere 6.7 SSO domain, the Dell EMC approach for ELM with VMware vSphere 6.7 deployments assesses the increased complexity for backup, recovery, and upgrades.

144 Manage VMware Enhanced Linked Mode

Set up VxBlock Systems to use VxBlock Central

VxBlock Central provides sophisticated management for Converged Systems.

VxBlock Central contains the following features:

View the health and RCM compliance of multiple VxBlock Systems. Download software and firmware components to maintain compliance with the current RCM. Configure multisystem AD integration and map AD groups to VxBlock Central roles. Set up compute, storage, networks, and PXE services, manage credentials, and upload ISO images for server installation. Monitor VxBlock System analytics. Manage capacity.

Access the VxBlock Central dashboard The VxBlock Central dashboard allows monitoring the health and compliance of systems, components, and specific elements of components.

About this task

Use a browser to access VxBlock Central. For more information about monitoring the health and compliance, click the Dashboard menu in VxBlock Central.

The dashboard supports a minimum screen resolution of 1280 x 1024.

Steps

1. Go to the MSM VM at https:// .

NOTE: The MSM VM must be able to ping the FQDN of the Core VM. If it cannot, a host file entry for the Core VM

must exist on the MSM VM.

2. Log in with the following default credentials:

Username: admin Password: D@ngerous1

Set up a VxBlock System The procedures in this section need to be performed only once.

Accept the end user license agreement After the VxBlock System is delivered, accept the end user license agreement (EULA) on each VxBlock System in your environment to enable discovery and health polling.

About this task

VxBlock Central does not discover VxBlock System components or poll for health status until you accept the EULA.

To accept the EULA, you must run a command on the Core VM. You must specify EULA acceptance information such as a name, job title, licensee company, and accepting company.

Fields cannot exceed 500 characters or contain angle brackets, < or >.

21

Set up VxBlock Systems to use VxBlock Central 145

Prerequisites

Connect to the Core VM.

Steps

1. Type: startEulaAcceptance 2. Scroll through the EULA until you are prompted to type a name.

3. Enter a name for EULA acceptance, and then press Enter.

4. Enter a job title, and then press Enter.

5. Enter the name of the licensee company, and then press Enter.

6. Optional: Enter the name of the accepting company, and then press Enter.

If you do not specify an accepting company, the value defaults to the licensee company.

7. Enter yes to accept the EULA.

Reset and reaccept end user license agreement Reset the End User License Agreement (EULA) for administrative changes. Reaccept the EULA after reset.

About this task

Reaccept the EULA after reset to enable the discovery and health polling.

Steps

1. To reset EULA, perform the following:

a. Enter: /opt/vce/fm/bin/resetEulaAcceptance b. When prompted, enter yes.

2. To reaccept EULA, perform the following:

a. Enter: startEulaAcceptance b. Scroll through the EULA until you are prompted to enter a name. c. Enter a name for EULA acceptance, and then press Enter. d. Enter a job title, and then press Enter. e. Enter the name of the licensee company, and then press Enter. f. Enter the name of the accepting company, and then press Enter.

If you do not specify an accepting company, the value defaults to the licensee company.

g. Enter yes to accept the EULA.

Start VxBlock System discovery After you configure the VxBlock System configuration file, start the discovery process to connect the Core VM to VxBlock System components.

NOTE: For VxBlock Central Version 2.0 and later, add, configure, and discover Converged Systems using the VxBlock

Central user interface. See Discover Converged Systems online help for more information.

Follow the Simplified VxBlock Central configuration procedure.

Prerequisites

Accept the end user license agreement (EULA). Configure the vblock.xml file or the VxBlock System configuration.

Enable northbound communication using SNMP. Connect to the Core VM.

Steps

1. Type: startFMagent

146 Set up VxBlock Systems to use VxBlock Central

2. After 15 minutes, check FMAgent.log to determine if discovery is complete.

3. To confirm, type:

cd /opt/vce/fm/logs/ grep -i 'current status' FMA* | grep 100 | grep discoverAll

4. Open a web browser and go to https://fqdn:8443/fm/systems where FQDN is the fully qualified domain name of the Core VM.

5. Authenticate to the Central Authentication Service (CAS) service.

Update the Windows Registry Before configuring application hosts on the Core VM, update the Element Manager with new registry keys to enable Windows Management Instrumentation (WMI) support.

About this task

Each application host is a Windows-based VM on an AMP with one or more of the following management software applications:

Navisphere CLI PowerPath/ Electronic License Management Server Unisphere Client Unisphere Server Unisphere Service Manager SMI-S Provider

NOTE: If you previously updated the registry keys to configure applications hosts, you do not need to update them

again.

Steps

1. As a local administrator, connect to the Element Manager VM.

2. To start the Registry Editor, type: regedit 3. Search for HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{76A64158-

CB41-11D1-8B02-00600806D9B6}.

4. Right-click the key, and select Permissions.

5. On the Permissions window, click Advanced.

6. On the Advanced Security Settings window, select Change.

7. In the Select User or Group window, from the From this location field, ensure that the location is your local computer.

8. From the Select User or Group window, enter Administrator in the Enter the object name to select field to change the owner. Click OK > OK.

9. From the Permissions window, select the Administrators group and select Full Control and click OK.

10. Right-click key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{76A64158- CB41-11D1-8B02-00600806D9B6}.

NOTE: Ensure that brackets are included.

11. Select New > String value and type AppID for the name. Right-click and modify the AppID. Set the value to {76A64158- CB41-11D1-8B02-00600806D9B6}.

NOTE: Ensure that brackets are included.

12. Set the Owner and Permissions back to the original settings:

a. Right-click HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{76A64158- CB41-11D1-8B02-00600806D9B6}, and select Permissions.

b. Remove the Full Control permissions for the Administrators group. c. Click Advanced, and select Change. d. In the Select User or Group window, from the From this location field, ensure that the location is your local computer. e. From the Select User or Group window, type NT Service\TrustedInstaller in the Enter the object name to select

field. Click OK > OK > OK.

Set up VxBlock Systems to use VxBlock Central 147

13. Search for key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\AppID.

14. Right-click the key, and select New > Key, and type {76A64158-CB41-11D1-8B02-00600806D9B6}.

15. Right-click the new key, and select New > String value. Type DllSurrogate for the name and leave the value empty.

Update the IP address tables on the Core VM (optional) Run a script to parse the vblock.xml file and update the IP address tables so that VxBlock Central does not block traffic from Converged System components. The vblock.xml file is available in /opt/vce/fm/conf.

Steps

1. To parse the vblock.xml and update IP address table rules to include the IP addresses of Converged System components, type: /opt/vce/fm/bin/runConfigCollector -iptablesOnly

2. To confirm the IP addresses for Converged System components are in the IP address table rules, type:

iptables -L

Plan a multisystem clustered environment Sizing guidelines are provided to plan a multisystem clustered environment.

If your deployment configuration exceeds these guidelines, the system performance degrades and the MSM VM cluster may be unsupported.

When planning an MSM VM cluster deployment, ensure that the topology (including the data centers and VxBlock System involved) is well defined.

VMs are used to provide features and functionality for VxBlock Central.

The following table provides an overview of VxBlock Central VMs:

VM Description

Core Discovers and gathers information about the inventory, location, and health of the VxBlock System

MSM Provides functions to manage multiple VxBlock Systems

In a data center environment, one MSM VM can be associated with up to 8 Core VMs.

MSP (optional) Provides functions for RCM content prepositioning

VxBlock Central includes the Core VM and the multisystem management (MSM) VM as a minimum configuration. For prepositioning, deploy and configure the multisystem prepositioning (MSP) VM as part of the installation process.

Single-site and multisite environments If the VxBlock System has AMP resources to support the Core VM and MSM VMs, cluster multiple MSM VMs together, instead of mapping multiple Core VMs to a single MSM VM.

In single-site cluster deployments, where three MSM VM nodes are supported, the failure of a single MSM VM node does not negatively impact read/write operations in the environment. A minimum of two MSM VM nodes should be operational to prevent data consistency problems.

In multisite cluster deployments, where two MSM nodes are supported, the failure of a single MSM node can impact read/write operations in that particular site only. There is no fault tolerance. If there is a network connectivity failure between the sites, this failure could negatively impact operations on all sites.

The following sizing restrictions apply to single-site and multisite configurations:

In a single-site environment:

Associate an MSM VM with up to two Core VMs. You can run up to three MSM VMs in a data center. You can associate up to two Core VMs with an MSM VM.

148 Set up VxBlock Systems to use VxBlock Central

In a multisite environment, each data center may have no more than two MSM VMs running. Each MSM VM is associated with up to two Core VMs.

You can configure a cluster that includes a maximum of three data centers. You can have up to two MSM VMs in each data center. You can associate each MSM VM with up to two Core VMs.

Latency WAN latency is defined as the latency between data centers in multiple data center deployments. LAN latency is defined as the latency between MSM VM nodes within a data center.

The following latency restrictions apply:

In a three data center deployment, do not exceed 100 milliseconds of WAN latency between data centers. In a two data center deployment with two MSM VM nodes, and four Core VMs, you can have up to 300 milliseconds of WAN latency. In a single-site environment, do not exceed 25 milliseconds of LAN latency between two MSM VM nodes in a data center.

VxBlock Systems The following sizing guidelines apply to VxBlock Systems in a clustered environment:

If you configure an MSM VM cluster in a three data center deployment, you can have up to 12 VxBlock Systems in the cluster. You can have up to two VxBlock Systems in a node with a maximum of one VMAX per MSM VM node. You can attach one Fabric

Technology Extension in the two system node. A VMAX Storage Technology Extension or Fabric Technology Extension is not recommended on a VxBlock System with VMAX storage.

The reference deployment contains a VMAX system with 5000 storage volumes and 390 disks. If your VMAX exceeds 5000 storage volumes and 390 disks, MSM VM cluster performance may be degraded. Reduce the total number of Core VMs in the deployment.

Simultaneous users Dell EMC recommends a maximum of three simultaneous users per MSM node.

LDAP configuration In a large data center environment that spans multiple geographical locations, the AD configuration is replicated to all locations. To prevent MSM VMs from crossing geographical lines to perform AD look ups, use local DNS practices. Doing so ensures that each node can access the local AD server for look ups.

The total number of groups an LDAP user belongs to impacts system response time.

CPU If performance degrades, increase the number of CPU cores. The default number of cores on the MSM VM is four.

Associate a Core VM with an existing MSM VM Associate a Core VM with an existing MSM VM after initial deployment. You can also add a Core VM after an MSM VM cluster is created.

About this task

NOTE: For VxBlock Central Version 2.0 and later, add, configure, and discover Converged Systems using the VxBlock

Central user interface. See Discover Converged Systems online help for more information.

MSM VM provides the addSlibHost.sh wrapper script to add the IP address of a Core VM to an MSM VM. In a single system environment where one Core VM is mapped to a single MSM VM, only run the addSlibHost.sh script under the following conditions:

The Optional Initial System Library IP(s) OVF property is not configured. The property is configured, and there are failures when adding the Core VM on MSM VM first boot.

To ensure that your environment can successfully add a Core VM to an existing MSM VM, run precheck by typing:

Set up VxBlock Systems to use VxBlock Central 149

/opt/vce/multivbmgmt/install/addSlibHost.sh -p IP_address The -p option runs the precheck but does not add the Core VM to the MSM VM.

When you associate a Core VM to an MSM VM, do not perform any operations on that Core VM from any other MSM VMs, until the association is complete.

The script verifies that the IP address has a valid format. If the IP address is valid, the script imports the vblock.xml file and then imports the credentials.

If your Core VM is already associated with your MSM VM, ensure the Core VM is configured to use NTP. To configure the Core VM to use NTP, type:

/opt/vce/multivbmgmt/install/addSlibHost.sh -n IP_address Where the IP address is the server for which you want to set the time. The -n option sets up the NTP on the Core VM, but does not add it to the MSM VM.

Prerequisites

You can associate up four VxBlock Systems with an MSM VM. Take a snapshot of each MSM VM within the cluster. Ensure the firstboot script has completed successfully on the MSM VM where you are adding the Core VM. The subsequent boot

script must not be in progress. To access the logs, go to /opt/vmware/var/log/firstboot and /opt/vmware/var/log/ subsequentboot.

NOTE: The addSlibHost script performs checks on the previous criteria. If your environment does not meet the

criteria, the addSlibHost script displays the failure and does not allow the Core VM to be added.

To ensure that discovery is complete, open a web browser and go to: https://FQDN:8443/fm/vblocks, where FQDN is the fully qualified domain name of the Core VM.

Steps

1. To add the Core VM to an existing MSM VM, type:

/opt/vce/multivbmgmt/install/addSlibHost.sh IP_address

2. Check the /opt/vce/logs/multivbmgmt/addSlibHost.log file if you encounter any problems adding hosts. It may take up to 30 minutes before the data is available.

Form a cluster of MSM VMs The initial MSM VM deployment configures a single VM. After deploying multiple MSM VMs, you can form a cluster of several nodes where each node is a separate MSM VM. The seed node is the first MSM VM in the cluster.

About this task

Configure a cluster for a single site or multisite environment. If configuring a cluster for a single site environment, MSM VMs are in the same data center. For a multisite environment, the MSM VMs are in different data centers. You can mix various types of VxBlock Systems in a single site or multisite clustered environment.

Add MSM VMs to a cluster one at a time, each time joining the same seed node. You cannot join existing clusters together. After an MSM VM has been added to a cluster, it cannot be deleted from the cluster.

Prerequisites

Ensure all MSM VMs for the cluster you want to join are deployed, powered on, and configured.

Take a snapshot of each node before clustering, and after each node is successfully added to the cluster. The FQDN for each Core VM, MSM VM, and MSP VM must not contain underscores or other special characters. Only hyphens

and periods are accepted as special characters. The data center names and cluster name in an MSM VM must begin with an alphanumeric character, and can contain numbers,

letters, and underscores. Use up to 255 characters. If configuring a cluster for a single-site environment, ensure that the data center name is the same for all nodes in the cluster. Verify

the capitalization.

150 Set up VxBlock Systems to use VxBlock Central

If configuring a cluster for a multisite environment, ensure that each site has a unique data center name. In each site, ensure all MSM VMs use the same data center name.

Ensure that the cluster name is the same across all MSM VMs in the cluster and across all sites.

NOTE: The data center names and cluster name cannot be changed after you power on the VMs. To change the data

center names or the cluster name, redeploy all the VMs in the cluster.

In a multisite clustered environment, change your firewall rule to open ports 7000, 7001, and 7199, as these ports are used for Cassandra node-to-node communication.

Ensure that the MSM VMs that join to the cluster have the same MSM VM CAS password.

Steps

To add a node to the cluster:

a. Use DNS recommended practices to ensure the FQDNs for all MSM VMs and Core VMs are resolvable across all data centers.

NOTE: From each MSM VM, resolve the FQDN of any of Core VMs that have been added, regardless of which MSM

VM to which it was added.

b. For all nodes in the cluster, including the node that is being added, enter:

/opt/vce/multivbmgmt/install/docompact_schemas.sh 1000 30

The first parameter of 1000 specifies the threshold of open files that are allowed in Cassandra before compaction begins. If the total number of files open in Cassandra is greater than the value of this parameter, compaction begins.

To check the total number of open files, enter:

lsof -n | grep 'cassandra' | wc -l

NOTE: The value for the first parameter must not exceed the Max open files limit set for Cassandra. The value of

1000 work for most environments, since the standard configuration for Cassandra sets the Max open files limit to

4096.

The second parameter of 30 for the script specifies the waiting time in seconds before compaction starts.

c. On any node that is being clustered to disable the repair cron jobs, enter the following command:

/opt/vce/multivbmgmt/install/cassandra_cluster_maintenance.sh --cron-disable-repair SEED_IP,JOINING_IP

Where:

SEED_IP is the IP address for the seed node in the cluster. All joining nodes must specify the same seed node. JOINING_IP is the IP address for the node that is joining the cluster. If you have multiple JOINING_IP addresses, include them all

and separate them by commas.

d. On the seed node in the cluster, enter:

cat /opt/vce/credential-management/deploy/conf/AOtRN.dat

e. For the next MSM VM to add to the cluster, enter:

/opt/vce/multivbmgmt/install/joinMSMCluster.sh -k KEY -s SEED_IP -v

Where:

KEY is the Credential Manager key for the seed node in the cluster you want to join. You can copy and paste the key value that was retrieved earlier.

SEED_IP is the IP address for the seed node in the cluster. All joining nodes must specify the same seed node. NOTE: Before clustering, some MSM VMs may be configured to use different AD servers. However, after these

nodes are added to a cluster, they must use a single AD server instance. When you add an MSM VM to an existing

cluster, the join script replicates the configuration data from the seed node to each joining node. The script

discards the configuration data from the joining node. To preserve an AD user configuration, use an MSM VM

node with that configuration as the seed node.

-v runs the script in verbose mode, which sends extra messages on the console terminal.

Set up VxBlock Systems to use VxBlock Central 151