Dell EMC VxBlock Systems 350 Administration Manual
  1. Manuals
  2. Brands
  3. Dell EMC Manuals
  4. Speaker System
  5. VxBlock Systems 350
  6. Administration manual

Dell EMC VxBlock Systems 350 Administration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Dell EMC
™
®
VxBlock
and Vblock
Systems 350
Administration Guide
Document revision 1.8
October 2017

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VxBlock Systems 350 and is the answer not in the manual?

Questions and answers

Related Manuals for Dell EMC VxBlock Systems 350

Summary of Contents for Dell EMC VxBlock Systems 350

  • Page 1 Dell EMC ™ ® VxBlock and Vblock Systems 350 Administration Guide Document revision 1.8 October 2017...

  • Page 2: Revision History

    September 2017 Added a section containing guidance for configuring VMware Enhanced Linked Mode. September 2017 Updated to support Dell EMC Unity All-Flash 350F, 450F, 550F, and 650F storage arrays for VxBlock System 350. August 2017 Made updates related to IPv6.

  • Page 3: Table Of Contents

    Contents Introduction..............................8 IPI Appliance............................... 9 Managing compute resources......................... 10 Starting Cisco UCS Manager 3.x......................10 Directly upgrading firmware at endpoints..................10 Upgrading with Cisco UCS Firmware Auto Install................12 Activating a Cisco UCS Manager Capability Catalog................15 Activating a port license........................16 Adding a UUID range...........................
  • Page 4 Adding a VLAN to the Cisco Nexus 1000V Switch................42 Adding a VLAN to the Cisco Nexus switches..................43 Removing a VLAN from the Cisco Nexus switches................43 Configuring a vPC..........................44 Deleting a vPC............................. 46 Adding VLANs to a vPC........................46 Removing VLANs from a vPC......................47 Adding vPCs to VLANs for Disjoint Layer 2 networks................
  • Page 5 Setting up Java and Internet Explorer on the management workstation or VM (vSphere 6.x).....76 Managing VMware vCenter SSO for VMware vSphere 6.x..............78 VMware vCenter SSO overview......................78 Unlocking and resetting the VMware vCenter SSO administrator password ........78 Managing the lockout status of VMware vCenter SSO account ............78 Managing VMware vCenter SSO default password policies..............
  • Page 6 Removing the uplink port profiles....................... 118 Modifying vEthernet data port profiles....................118 Modifying the QoS settings ....................... 120 Upgrading the VEM software......................121 Troubleshooting the Cisco Nexus 1000V switch................121 Managing VMware NSX with VPLEX on VxBlock Systems..............123 Performing a graceful failover......................123 Performing a graceful recovery......................
  • Page 7 Inter Converged System ELM scalability planning in a single physical data center....162 Inter Converged System ELM scalability planning with multiple physical data centers....163 ELM deployment information......................163 ELM dependencies and limitations.....................165 VMware ELM References........................166 Conclusions............................166 Configuring VMware Enhanced Linked Mode (vSphere 6.5U1)............168 Introduction to ELM (vSphere 6.5U1)....................168 VMware ELM with VMware vSphere 6.5U1 use cases..............

  • Page 8: Introduction

    In this document, the Vblock System and the VxBlock System are referred to 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: •...

  • Page 9: Ipi Appliance

    IPI Appliance The IPI Appliance provides an intelligent gateway to gather information about power, thermals, security, alerts, and all components in the physical infrastructure of each cabinet. Vision Intelligent Operations uses SNMP to poll the status of the IPI Appliance and then passes the results to VMware vCenter.

  • Page 10: Managing Compute Resources

    Managing compute resources Starting Cisco UCS Manager 3.x Cisco UCS Manager, Version 3.1.1 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 all current versions of the Cisco UCS Manager. Settings, policies, and pools apply regardless of the interface used.
  • Page 11 Before you begin • Coordinate firmware upgrades during maintenance windows and refer to Cisco documentation for proper upgrade procedures. • Download the latest Cisco UCS B-Series GUI Firmware Management Guide. • Run a full state and all configuration backup. • For a cluster configuration, verify the high availability status of both fabric interconnect shows up and running.

  • Page 12: Upgrading With Cisco Ucs Firmware Auto Install

    Related information Cisco UCS Manager GUI Configuration Guide Cisco UCS B-Series GUI Firmware Management Guide Upgrading 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.
  • Page 13 Scheduling options • 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.
  • Page 14 Configure and deploy the VCE_UserAck maintenance policy in all new and existing — associated service profiles. Complete this before configuring host firmware policies to support the Cisco UCS server firmware auto install feature. • Create a new 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.

  • Page 15: Activating A Cisco Ucs Manager Capability Catalog

    On the Prerequisites page, do not check any boxes. Important: If no system backup was performed, critical and/or major faults exist, or the Management Interfaces Monitoring Policy has not been configured or enabled, do not continue with the upgrade. Do not bypass any of the checks. On the Select Package Versions page, select the firmware version for the Cisco B-Series Blade software field and click Next.

  • Page 16: Activating A Port License

    Before you begin Download, update, and activate a Cisco UCS infrastructure software bundle before activating a capability catalog. Procedure Refer to the appropriate Cisco UCS B-Series GUI Firmware Management Guide for your release to update the Cisco UCS Manager Capability Catalog. Related information Cisco UCS Manager GUI Configuration Guide Cisco UCS B-Series GUI Firmware Management Guide...

  • Page 17: Adding A Uuid Range

    Related information Cisco UCS Manager GUI Configuration Guide Adding a UUID range Add a range to a UUID pool using the Cisco UCS Manager. Before you begin Verify the new UUID range does not exist on any pre-existing Cisco UCS compute environment. Procedure Log on to the Cisco UCS Manager.

  • Page 18: Deleting A Uuid Pool

    Cisco UCS Manager GUI Configuration Guide Deleting a UUID pool Delete a UUID pool using the Cisco UCS Manager. If you delete a pool, the addresses are not reallocated from the pool that have 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:...

  • Page 19: Deleting A Wwnn Range

    Before you begin Obtain the WWNN information. Procedure Log on to the Cisco UCS Manager. In the Navigation window, select the SAN tab. In the SAN tab, expand SAN > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multi-tenancy, expand the root node.

  • Page 20: Adding A Wwpn Range

    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. Procedure Log on to the Cisco UCS Manager.

  • Page 21: Deleting A Wwpn Range

    Expand SAN > Pools. Expand the node for the organization where you want to create the pool. If the system does not include multi-tenancy, expand the root node. Right-click WWPN Pools and select Create WWNN Pool. From the WWNN Pool window, perform the following: In the Define Name and Description window, type a unique name and description for the WWNN pool.

  • Page 22: Adding A Mac Address Range

    In the SAN tab, expand SAN > Pools > Organization_Name > WWPN Pools > WWPN_Pool_Name. Expand the WWPN Pools node. Right-click the WWPN pool you want to delete and select Delete. If a confirmation dialog box appears, click Yes. Adding a MAC address range Add a range to the MAC address pool using the Cisco UCS Manager.

  • Page 23: Deleting A Mac Pool

    Deleting a MAC pool Delete a MAC pool using the Cisco UCS Manager. If you delete a pool, the addresses are not reallocated from the pool that have been assigned to vNICs or vHBAs. Before you begin All assigned addresses from a deleted pool remain with the vNIC or vHBA to which they are assigned until: •...

  • Page 24: Creating Vnic Templates

    Procedure Log on to the Cisco UCS Manager. In the Navigation window, select the LAN tab. Expand Pools > IP Pools. Right-click the VCE-KVM-POOL IP Pool and select Create Block of IPv4 Addresses or Create Block of IPv6 Addresses. In the Create a Block of IP Addresses window, perform the following: In the From field, type the first IP address in the block.

  • Page 25: Modifying The Time Zone Setting

    From the Navigation window, select the LAN tab, and expand Policies. Under root, right-click vNIC templates and select Create vNIC Template within the shortcut menu. Type a name for the template that is less than or equal to 16 characters and can be easily identified during service profile creation.

  • Page 26: Adding A Network Time Protocol Server

    On the Work window, select the General tab. From the Timezone drop-down list, select the time zone you want to use for the Cisco UCS instance. Click Save Changes. Adding an NTP server Cisco UCS requires both an instance-specific time zone setting and an NTP server to ensure the correct time appears in the Cisco UCS Manager.

  • Page 27: Adding A Syslog Server

    Adding a syslog server When you add a syslog server, logs are sent to the server to facilitate reporting alerts and troubleshooting. Dell EMC recommends using the syslog server to facilitate the reporting of alerts and troubleshooting. Before you begin Deploy a syslog server so that it is reachable from the Cisco UCS management IP address using an IP address.

  • Page 28: Removing A Syslog Server

    Verify that the logs have been received on the syslog server. Removing a syslog server Remove a syslog server from the Cisco UCS domain using the Cisco UCS Manager. Procedure Log on to the Cisco UCS Manager. From the Server tab, select Faults and Logs. From the Faults and Logs window, select the Logging Controls tab.

  • Page 29: Removing An Snmp Server

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

  • Page 30: Managing Service Profiles

    Related information www.cisco.com Managing service profiles Configuring 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.
  • Page 31 On the Create vNIC window, type the following values in order to configure vNIC-0 and vNIC-1: Order Value vNIC-0 vNIC-1 Name vNIC-0 vNIC-1 Select Use LAN Connectivity Template vNIC Template vNIC-0-Fabric-A vNIC-1-Fabric-B Adapter Policy VMware >OK>Add VMware >OK>Next Templates created for blade servers with multiple physical network adapters should only contain vNIC-0 and vNIC-1.
  • Page 32 For vNIC/vHBA placement, perform the following: Order Value/field Servers with a B200M4 B420M3 B460 blades with single blades (with blades VMware vSphere 5.5 mezzanine card 1240/1280 or (with (if applicable) or 1340/1380 1240/12 vphere 6.0 VIC) 80 VIC) Select Placement Specify Specify Specify...

  • Page 33: Cloning The Service Profile Templates

    Select the Management IP Address. In the Scrub Policy field, select default, and click Finish. What to do next For servers with more than one network adapter, add vNIC2, vNIC3, and other additional vNICs individually after installing VMware vSphere ESXi to force the vNIC and VMNIC ID numbers to match each host.

  • Page 34: Adding Vnics To The Service Templates

    Adding vNICs to the service profiles vNICs can be added to any service profile template or unbound service profile. About this task Adding new vNICs to a service profile already assigned to a Cisco UCS blade server may trigger a PCIe reprovisoning of vNICs/vHBAs devices. As a result PCIe addresses or adapter placement may change after reboot.

  • Page 35: Configuring Service Profile Templates For Disjoint Layer 2

    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 in addition to the 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-3.

  • Page 36: Assigning Or Modifying A Management Ipv4 Address

    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.

  • Page 37: Creating An In-Band Network Profile For The Ipv6 Management Address Assignment

    Procedure Log on to Cisco UCS Manager and select the LAN tab. Expand LAN > LAN CLOUD, right-click on LAN Cloud and select Create VLANs. In the Create VLANs window: Type the name of the VLAN in the Name field. Select Common/Global to apply the VLANs to both fabrics and use the same configuration parameters in both cases.

  • Page 38: Assigning Or Modifying A Management Ipv6 Address

    Assigning or modifying a management IPv6 address on VxBlock Systems Change the management IP address on a service profile or service profile template using the Cisco UCS Manager. About this task IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems.

  • Page 39: Renaming Service Profiles

    Evenly distribute service profiles within a cluster across available chassis. The arrangement depends on the number of Cisco UCS Blade Server Chassis, installed blades, and hosts in the cluster. Coordinate with the person installing VMware to complete this procedure The following table provides an example of four chassis with eight blades per chassis that equals 32 blades: Cisco UCS Blade Server Assign service profiles...

  • Page 40: Managing Networking Resources

    Managing networking resources Managing VMware NSX For information on managing VMware NSX, refer to the VMware NSX for vSphere Administration Guide. Related information VMware NSX for vSphere Administration Guide Creating 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.

  • Page 41: Creating A New Vlan Group

    Related information Adding a VLAN to a service profile template (see page 41) Cisco UCS Manager GUI Configuration Guide Creating a new 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.

  • Page 42: Adding A Vlan To A Vnic Template

    Repeat these steps for the other Ethernet interface. What to do next Add the VLANs to the Cisco Nexus 55xxUP switches, the Cisco Nexus 1000V Series virtual switch, and any other switching infrastructure that is required. Adding a VLAN to a vNIC template Use this procedure to add a VLAN using Cisco UCS Manager.

  • Page 43: Adding A Vlan To The Cisco Nexus Switches

    To assign a name to the VLAN, type: name vlan_name To view information about the new VLAN, type: show vlan vlan_id Related information Cisco Nexus 1000V Port Profile Configuration Guide Adding 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.

  • Page 44: Configuring A Vpc

    About this task IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems. Before you begin 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: •...
  • Page 45 IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems. Before you begin • Verify the Cisco Nexus switches are reachable through the console or the management connection. • Verify the vPC and LACP features are enabled on the Cisco Nexus switches. •...

  • Page 46: Deleting A Vpc

    To add the appropriate Ethernet ports as members of the vPC: Type Switch-A(config)# interface ethernet port_number Type Switch-A(config-if)# switchport mode mode where mode is Trunk or Access (same as the vPC). Type Switch-A(config-if)# channel group channel_number mode active To set the state, type: Switch-A(config-if)# no shut To save the configuration, type: Switch-A# copy run start Repeat this procedure on the peer switch.

  • Page 47: Removing Vlans From A Vpc

    About this task Additional VLANs are added to the trunk of an existing vPC when it is modified. Before you begin • Verify that the Cisco Nexus series switch is reachable through the console or the management connection • Verify that the Cisco vPC that needs to be modified is up •...

  • Page 48: Adding Vpcs To Vlans For Disjoint Layer 2 Networks

    Cisco Nexus 9000 Series NX-OS Software Configuration Guide Adding vPCs to VLANs for Disjoint Layer 2 networks Add vPCs to VLANs for Disjoint Lyer 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.
  • Page 49 Before you begin 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. Procedure Log on to the Cisco UCS Manager. To assign VLANs to vPCs 101 and 105 in fabric A, perform the following: Select the LAN tab.

  • Page 50: Viewing Vpcs Assigned To Vlans For Disjoint Layer 2 Networks

    In the VLANs table, select the VLANs to assign to vPC 106. Select Add to VLAN and click OK. Verify that vPCs 102 and 106 (Fabric B) appear under all required VLANs. Related information Viewing vPCs assigned to VLANs for Disjoint Layer 2 networks (see page 50) Removing vPCs from VLANs for Disjoint Layer 2 networks (see page 50)

  • Page 51: Upgrading Cisco Nexus Series Switch Software

    About this task If you remove all port or vPC interfaces from a VLAN, the VLAN returns to the default behavior and 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.
  • Page 52 • 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.

  • Page 53: Downgrading Cisco Nexus Switch Software

    If you are performing a disruptive upgrade, following warning appears: 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.
  • Page 54 Procedure To reverse a Cisco Nexus series switch software upgrade, perform the upgrade steps using the earlier version of the software. Related information Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide Managing networking resources...

  • Page 55: Managing Cisco Mds Switches

    Managing Cisco MDS switches Upgrading 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. Before you begin •...
  • Page 56 To copy the Kickstart and the system files from the FTP copy server to the fabric switch, from the MDS# prompt perform the following: To access the bootflash directory, type: cd bootflash: To verify free space, type dir To copy the files, type: copy ftp://ftp_server_addr/filename.bin filename.bin copy ftp://ftp_server_addr/filename.bin...

  • Page 57: Downgrading Cisco Mds Switch Software

    Downgrading Cisco MDS switch software Downgrade Cisco MDS switch software to restore the original version after a failed upgrade. Procedure Refer to the release notes section Downgrading Your Cisco MDS SAN-OS Software Image and follow the guidelines before downgrading the software. Related information Cisco.com Configuring a VSAN...

  • Page 58: Removing A Vsan

    To assign an FC interface to the VSAN, type: switch(config-vsan-db)# vsan vsan_id interface fc slot To update the interface with the VSAN, type: switch(config-vsan-db)# vsan vsan_id fc slot Related information Configuring and Managing VSANs Removing a VSAN Remove a VSAN and associated FC interfaces. About this task IPv4 addresses are supported on Vblock Systems and VxBlock Systems.

  • Page 59: Removing A Domain Id And Priority From A Vsan

    About this task IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems. Before you begin • A unique domain ID must be assigned to the new VSAN added to the switch. When a new VSAN is added to a switch in a fabric, the domain manager is used to assign a domain ID and priority to the VSAN.

  • Page 60: Enabling Fc Interfaces

    Enabling 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. Before you begin • Verify that the Cisco MDS switch is up and reachable through the console or management connection.

  • Page 61: Moving Licenses Between Fc Interfaces

    Procedure Log on to the Cisco MDS switch. To enter configuration mode, type: switch-A# config terminal To specify the interface, type: switch-A(config)# interface fc interface_id To disable the interface, type: switch-A(config-if)# shutdown Moving 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.

  • Page 62: Disabling Port Licenses

    Related information Disabling port licenses (see page 62) Cisco MDS 9000 Family NX-OS Licensing Guide, Release 6.x Disabling port licenses Port licenses can be disabled and moved to other interfaces. About this task To configure the switch for other SAN features, refer to the Cisco MDS 9000 NX-OS Fabric Configuration Guide.

  • Page 63: Zoning Guidelines

    A maximum of 192 servers per switch are supported if spread across the three forwarding — engines (e0-e2) on the switch. • The Cisco MDS 9396S 16G Multilayer Fabric Switch and Cisco MDS 9706 Multilayer Director switches use dynamic port mapping for device connectivity. •...

  • Page 64: Managing Storage Resources

    — not configurable. Expanding a storage pool Expand a storage pool on the Dell EMC Unity storage array to increase capacity to grow existing LUNs or create new ones. Before you begin Verify that storage pools exist and disk drives are available to expand the storage pool.

  • Page 65: Allocating Block Storage

    — not configurable. Allocating block storage On the Dell EMC Unity storage array, you can present storage to one or more hosts. About this task You can present additional storage to one or more hosts in the following ways: •...

  • Page 66: Managing Nfs

    NAS servers can share file storage over a variety of protocols including CIFS/SMB, NFS, and FTP. About this task To allocate file storage, first create a NAS server on the Dell EMC Unity storage array. The NAS server is a standalone service with dedicated network interfaces (IPv4/IPv6 address information) to share file through single or multiple NAS protocols.

  • Page 67: Creating A File System

    Procedure Log on to the Dell EMC Unity storage array where you want to create a NAS server. Select Storage > File>NAS Servers. Click + to create a new server.

  • Page 68: Creating Nfs Shares

    An NFS share can have a defined default access type such as No Access. Procedure Log on to the Dell EMC Unity storage array where you want to create the NFS share. Select Storage > File > NFS Shares. Click + to create a NFS share.

  • Page 69: Managing Vmware Vsphere 6 With Ipv6

    Managing VMware vSphere 6 with IPv6 VMware vSphere 6 does not support an IP dual stack network configuration. vSphere 6.5 does not currently support IPv6. Enable IPv6 for all nodes and components except for the following VMware vSphere 6.0 features: VMware feature with IPv6 limitation Workaround IPv6 addresses for VMware vSphere ESXi hosts and...

  • Page 70: Managing Vmware Vsphere Esxi 5.5 And 6.X

    The following releases of VMware vSphere ESXi are supported: • 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.

  • Page 71: Installing The Latest Vmware Vsphere Esxi Patch (Vsphere 6.5)

    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.

  • Page 72: Configuring Advanced Settings For Vmware Vsphere Esxi (Vsphere 6.0)

    Configuring advanced settings for VMware vSphere ESXi (vSphere 6.0) Configure advanced VMware vSphere ESXi settings for compute servers. About this task The following advanced settings are available: Setting Value to configure Default value to restore for Default value to restore for VMware vSphere 5.5 (if VMware vSphere 6.0 applicable)

  • Page 73: Configuring Advanced Settings For Vmware Vsphere Esxi (Vsphere 6.5)

    Modify the $vcenter variable. Execute the script in the VMware vSphere PowerCLI environment. This script does NOT set jumbo frames on the vmknics. You must perform jumbo frame settings manually or using another tool. ########################################################## # Set NFS advanced settings for all servers in vCenter. If # hosts were built using UIM, or built manually, this script can # be run to assist with the configuration of NFS.

  • Page 74: Restoring Default Values For Vmware Vsphere Esxi Advanced Settings (Vsphere 6.0)

    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.

  • Page 75: Restoring Default Values For Vmware Vsphere Esxi Advanced Settings (Vsphere 6.5)

    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. Procedure In the VMware Host Client, select Manage in navigator pane. Click Advanced Settings under the System tab. Search for the appropriate parameters. Restore the parameters in the window to their default settings.

  • Page 76: Installing Vcenter Server Root Certificates On Web Browser (Vsphere 6.5)

    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. Procedure Open the Internet Explorer web browser and go to https://vcsa_fqdn.
  • Page 77 Click Edit Site List... which opens in the Exception Site List popup window. Add the URLs of web-based applications. For example: https:// ip_address_of_web_based_application Click OK to close the Exception Site List popup window. Click OK to close the Java Windows Control Panel. Managing VMware vSphere ESXi 5.5 and 6.x...

  • Page 78: Managing Vmware Vcenter Sso For Vmware Vsphere 6.X

    Managing VMware vCenter SSO for VMware vSphere 6.x VMware vCenter SSO is an authentication mechanism used to configure security policies and lock out or disable an account for VMware vSphere 6.x. Default policies do not require modification. You may have to modify policies or accounts if regulations require different policies or if you are troubleshooting a problem.

  • Page 79: Managing Vmware Vcenter Sso Default Password Policies

    Click Yes to confirm. Managing VMware vCenter SSO default password policies Manage the VMware vCenter SSO default password policies for VMware vSphere. About this task By default, the SSO passwords expire after 365 days, including the SSO administrator password. You can modify the expiration policy to manage administrative passwords.
  • Page 80 Procedure In case of vSphere 6.0, join the SSO VM to the appropriate Windows Active Directory Domain. Restart the server. For vSphere 6.5, move to Step 2 as SSO is integrated with vCenter Server Appliance. Log on to the VMware vSphere 6.x Web Client on the vCenter VM or Element Manager VM using the administrator@vsphere.local account at: https://<VCENTER_FQDN OR IP>:9443/ vsphere-client/ For credentials information, refer to Converged Systems usernames and passwords.

  • Page 81: Backing Up Or Restoring The Vmware External Psc Configuration

    Backing up or restoring the VMware external PSC configuration Back up or restore the VMware vCenter PSC for VMware vSphere 6.x. About this task Maintaining a back-up of the PSC configuration ensures continued VMware vSphere access for VMware vCenter Server components. Procedure Follow the back-up and restore procedure in the VMware knowledge base article 2149237.
  • Page 82 For more information, refer to the VMware Platform Services Controller 6.x FAQs. Managing VMware vCenter SSO for VMware vSphere 6.x...

  • Page 83: Managing Virtualization

    Managing virtualization Patching VMware vSphere ESXi hosts with the VUM (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. Before you begin Verify that the patch bundle is listed on the latest version of the Converged Systems Release Certification Matrix.
  • Page 84 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: Go to the Compliance view and highlight the desired host in the list to the left of the vSphere client window, and select a folder, cluster, or data center.

  • Page 85: Patching Vmware Vsphere Esxi Hosts With The Vum (Vsphere 6.5)

    In the Attached Baselines area, highlight 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.
  • Page 86 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. Click Next and wait until the file upload completes successfully. If the upload fails, then it is possible that the zip file could be corrupted during the download process or the incorrect zip file has been imported.
  • Page 87 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: In the Update Manager tab, in the Independent Baselines list highlight the package baseline that was created. Click Stage Patches.

  • Page 88: Supported Guest Operating Systems

    Supported guest operating systems For information about installing supported guest operating systems in VMware VMs, refer to the VMware Guest Operating System Installation Guide. If VMware VMs are being configured with IPv6 for VxBlock Sytems, a vmxnet driver must be deployed. This should occur automatically when VMware Tools are installed.

  • Page 89: Enabling Vmware Enhanced Vmotion Compatibility Within A Cluster

    Enabling 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 feature set to the VMs, even if the CPUs on the hosts are different. The EVC feature uses the Intel FlexMigration technology to mask processor features so that hosts can present the feature set of an earlier generation of processors.
  • Page 90 In the Virtual Hardware tab, expand the VMDK to be configured with the VFRC. 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. Repeat Steps 1 - 4 for each VM and associated VMDK that requires VFRC.

  • Page 91: Managing Vmware Vds

    Managing VMware VDS The VMware VDS is an enterprise feature of VMware vSphere vCenter Server 6.0 and later 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.
  • Page 92 The following table shows recommended settings: Edit option Field: recommended setting General Name: the name chosen for the distributed port group — Port binding: Static Binding — Port allocation: Elastic — Number of ports: 8 (increases automatically as long as Elastic is —...

  • Page 93: Creating A Distributed Port Group

    Edit option Field: recommended setting Miscellaneous Block all ports: No Creating a distributed port group You can use the VMware vSphere Web Client to create and add virtual and VMKernel distributed port groups to an existing VMware VDS. After you create a distributed port group, you must configure the port group.
  • Page 94 About this task IPv4 addresses are supported on Vblock Systems and VxBlock Systems. IPv6 addresses are supported on VxBlock Systems. Before you begin Create a VMkernel distributed port group. IPv6 is not supported on vSphere 6.5. Procedure From the VMware vSphere Web Client Home tab, under Inventories, select Networking. Right-click DVSwitch01-A and select Add and Manage Hosts.

  • Page 95: Associating Vmware Vsphere Esxi Hosts To An Existing Vmware Vds

    Select the new VMKernel. Select Edit adapter. Select NIC settings. Verify that the MTU setting is set to 1500 (NFS MTU=9000). Click OK and Finish. Repeat steps g through s for each additional VMware vSphere ESXi host to create a new network adapter.

  • Page 96: Configuring Jumbo Frames On Vmware Vds

    From the Select new hosts window, select the VMware vSphere ESXi host to be added and click OK. You can modify multiple VMware vSphere ESXI hosts at a time using the Add and Manage Hosts wizard. The alternative launch method above does not apply to vSphere 6.5. Validate the selected host appears in the list and click Next.

  • Page 97: Configuring Jumbo Frames On Distributed Port Groups

    Configuring jumbo frames on distributed port groups Use this procedure to configure jumbo frames on the NFS distributed port group. Procedure Open a browser and type the following URL: https://<vCenterIP>:9443/vsphere- client You can also launch the VMware vSphere Web Client by selecting Start Menu > All Programs >...

  • Page 98: Decommissioning Vmware Vds Components

    Select Traffic filtering and marking. From the Status drop-down box, select Enable. Select the green plus (+) icon to open the New Network Traffic Rule wizard, and perform the following: For the Name, type: vMotionCOS. For Action, select Tag. Change the CoS value to 4. For VMware vSphere 6.x, change the Traffic direction to Ingress.

  • Page 99: Deleting A Distributed Port Group

    Deleting a distributed port group Delete a distributed port group from an existing VMware VDS. • Before deleting a distributed port group, reassign all powered-on VMs to a different distributed port group. If the VMs are powered off, delete the distributed port group. If you delete a distributed port group with powered-on VMs and network adapter numbers assigned to the distributed port group, the system returns an error.
  • Page 100 Create the VM port group with correct VLAN ID to the new standard switch. — Procedure Open a browser and type the following URL: https://<vCenterIP>:9443/vsphere- client You can also launch the VMware vSphere Web Client by selecting Start Menu > All Programs >...

  • Page 101: Disassociating The Vmware Vsphere Esxi Host

    Right-click the distributed port group and select All vCenter Action > Remove from Inventory and clickOK. Disassociating the VMware vSphere ESXi host Disassociate the VMware vSphere ESXi host from an existing VMware VDS. Before you begin • Reassign all the VMs to a port group on a different distributed switch or standard switch. Otherwise, an error occurs when you attempt to delete the VMware vSphere ESXi host from the VMware VDS.
  • Page 102 Log on to the VMware vSphere Web Client with the administrator@vsphere.local user account (VMware vSphere SSO account) or other administrative account with appropriate permissions. On the VMware vSphere Web Client Home tab, under Inventories, select Hosts and Clusters. From the left window, select the appropriate VMware vSphere ESXi host and select the Related Objects tab.
  • Page 103 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 —...
  • Page 104 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 • Create the distributed port group with the same name and VLAN ID of what is created in the existing distributed or standard switch •...

  • Page 105: Removing A Vmware Vds

    Before you begin Verify that there are no VMs, vNIC uplinks and VMKernel ports attached to the existing VMware VDS coming from each VMware vSphere ESXi host. Procedure Open a browser and type the following URL: https://<vCenterIP>:9443/vsphere- client. You can also launch the VMware vSphere Web Client by selecting Start Menu > All Programs >...
  • Page 106 Migrating VM distributed port group assignments to a different switch If there are powered-on VMs on the distributed port group, migrate VM distributed port group assignments to a different distributed or standard switch. About this task This procedure is not required if there are no powered-on VMs on the distributed port group. VMs connected to the distributed port group can be powered-off to remove the distributed port group.
  • Page 107 On the VMware vSphere Web Client Home tab, under Inventories, click Networking. Right-click DVswitch01-A and select Migrate VM to Another Network. From the Migrate Virtual Machine Networking wizard, perform the following: Verify that Specific network is selected and click Browse. Select the Source network distributed port group or standard port group and click OK.

  • Page 108: Using Disjoint Layer 2 Configuration On Vmware Vds

    Under On this switch, select the VMKernel port by selecting the VMKernel adapter and click Assign port group. If you need to delete VMKernel ports, under the VMKernel adapter list, select the VMKernel port and click Remove. Select the port group that belongs to a different vSwitch and click OK. Validate the VMKernel port destination and click Next.

  • Page 109: Creating Distributed Port Groups For Disjoint Layer 2

    From the New Distributed Switch wizard, perform the following: Change the name of the distributed switch to DVswitch01-DJL2 unless a different cluster name is used in the LCS. Validate that the cluster location is Cluster01. Click Next. Select the appropriate Distributed switch. Click Next.

  • Page 110: Adding Vmware Vsphere Esxi Hosts To Vmware Vds

    Under Configure Settings, leave Port binding and Port allocation as default. Leave Number of Ports at 8. For VLAN type, select VLAN and change the VLAN ID to what was specified in the LCS. Click Next to view the Ready to complete window. Review the settings and click Finish if everything is correct.

  • Page 111: Backing Up And Restoring A Vmware Vds Data Configuration

    Select vmnic5 and click Assign uplink. Select Uplink 4 and click OK. Click Next. Click Next to view the Ready to complete window. Review the settings and click Finish if everything is correct. Otherwise, click Back to edit changes. Add the VMkernel distributed port groups (vMotion, NFS) only if they belong to the Disjoint Layer 2 traffic.

  • Page 112: Importing A Backup Of A Dvswitch Configuration

    About this task The VMware dvSwitch configuration includes all the VMware VDS and distributed port group's configuration settings. Before you begin Verify that the VMware VDS is configured. Procedure Open a browser and type the following URL: https://<vCenterIP>:9443/vsphere- client You can also launch the VMware vSphere Web Client by selecting Start Menu > All Programs >...

  • Page 113: Restoring A Backup Of The Dvswitch Configuration

    Click Next. Review the import settings and click Finish. Restoring a backup of a VMware dvSwitch configuration Reset the configuration of an existing VMware VDS to the settings in the configuration file. About this task Restoring a VMware VDS changes the settings on the selected switch back to the settings saved in the configuration file.
  • Page 114 Related information VMware vSphere Networking guide Managing VMware VDS...

  • Page 115: Managing The Cisco Nexus 1000V Series Switch

    Related information Cisco Nexus 1000V VEM Software Installation and Upgrade Guide Creating a port profile Management settings should not be changed without Dell EMC approval. This content is for example purposes only. Procedure Log on to the Cisco Nexus 1000V VSM.

  • Page 116: Modifying The Uplink Port Profiles

    Related information Cisco Nexus 1000V Port Profile Configuration Guide 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.
  • Page 117 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 */...

  • Page 118: Removing The Uplink Port Profiles

    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. Before you begin • Verify that VLANs on uplinks exist in Cisco aggregation switches. •...
  • Page 119 Procedure 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 <Customer Data VLAN number> no shutdown state enabled copy run start...

  • Page 120: Modifying The Qos Settings

    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: 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.

  • Page 121: Upgrading The Vem Software

    Perform the following: 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...
  • Page 122 Related information Cisco Nexus 1000V Troubleshooting Guide Managing the Cisco Nexus 1000V Series Switch...

  • Page 123: Managing Vmware Nsx With Vplex On Vxblock Systems

    Managing 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.
  • Page 124 Manually power off the NSX Manager and controllers. 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. On the VMware vSphere Web Client Home tab, under Inventories, click Hosts and Clusters.
  • Page 125 Migrate the remaining management components on hosts from the primary site to the secondary site. The DHCP server resides in its local site and should not be migrated to the opposite site. Right-click PSC02 VM and select Migrate. The Migrate wizard opens. Enter the data values as requested, accept the default settings presented, and use the following configuration information: Wizard page Selection...
  • Page 126 In the secondary site, manually enable the Management SVI (VLAN 136) on the Cisco 9396 switches. Use Putty to log in to Cisco 9396-A. 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...

  • Page 127: Performing A Graceful Recovery

    Click Finish. All the VMware vSphere core and NSX Manager and controller components are now running in the secondary site. Performing a graceful recovery This procedure explains how to gracefully recover management components from the secondary site to the primary site. Procedure Manually power off the NSX Manager and controllers.
  • Page 128 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 Verify that each VM successfully migrated to correct ESXi host. Migrate the remaining management components on hosts from the secondary site to the primary site.
  • Page 129 In the secondary site, manually disable the Management SVI (VLAN 136) on the Cisco 9396 switches. Use Putty to log in to Cisco 9396-A. 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...
  • Page 130 Validate that all NSX Controllers are connected and no warnings or errors exist. On the VMware vSphere Web Client Home tab, under Inventories, click Network & Security. 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 ■...

  • Page 131: Managing Amp-2

    Managing AMP-2 Procedures required for managing AMP-2P and AMP-2S are provided in this section. Upgrading the Cisco UCS C2x0 Server (CIMC 2.x firmware) Perform a remote upgrade using KVM with CIMC for the Cisco UCS C2x0 Server firmware. About this task This topic is applicable to servers running CIMC 2.x firmware.

  • Page 132: Upgrading The Cisco Ucs C2X0 Server (Cimc 3.X Firmware)

    After reboot is complete, verify that the VMware vSphere ESXi host is accessible to the AMP-2 vCenter Server instance. Related information Cisco.com Upgrading the Cisco UCS C2x0 Server (CIMC 3.x firmware) Perform a remote upgrade using KVM with CIMC for Cisco UCS C2x0 Server firmware. About this task This topic is applicable to servers running CIMC 3.x firmware.

  • Page 133: Upgrading Vnxe3200 Software

    From the Confirmation screen for the BIOS Update, select Yes. After reboot is complete, verify that the VMware vSphere ESXi host is accessible to the AMP-2 vCenter Server instance. Upgrading VNXe3200 software Upgrade the software of an VNXe3200 storage array using the VNXe Unisphere GUI. Before you begin The VNXe3200 management interface does not support an IPv4 and IPv6 dual stack network configuration.

  • Page 134: Changing The Vmware Datastore Capacity

    • Confirm that the planned data store size does not exceed the recommended 2 TB maximum. • Confirm that adding new data stores does not exceed the total array capacity. Procedure Select Storage > VMware data stores. Select Create to start the VMware Storage Wizard. Specify the following settings: For the type of data store, select VMFS.

  • Page 135: Adding A Vmware Esxi Host For Ipv4

    Procedure Click Storage > VMware Data stores Select a data store and click Details. In the Storage Details section, click the Capacity tab. For the Size setting, type the total amount of space the data store can use for data. For thin-provisioned VMFS data stores, you can increase the storage space, but not decrease it.

  • Page 136: Adding A Vmware Vsphere Esxi Host For Ipv6

    Click Finish to accept the settings and add the VMware host configuration or click Back to modify a setting. The Add ESX Hosts wizard creates the VMware host configuration and adds it to the Unisphere list of VMware hosts. What to do next After you add a VMware host configuration, you can specify its access to a specific storage resource.

  • Page 137: Configuring Vmware Esxi Persistent Scratch Location

    About this task Use the VNXe Unisphere GUI online help for the latest process. Access the online help by clicking the question mark on the right side of the VMware Datastores page. Before you begin • Obtain the IP address and log on credentials for the VNXe array. •...

  • Page 138: Configuring Raid Devices For Amp-2

    Close the Datastore browser. From the Software window, click Advanced Settings. Select the ScratchConfig section. (AMP-2S only) Update the ScratchConfig.ConfiguredScratchLocation parameter. Type the full path to directory. For example: /vmfs/volumes/MIESXI01- MGMT-01/.locker_ESXHostname or /vmfs/volumes/MGMT-DS- NAS/.locker_ESXHostname Hosts must be assigned to respective folders. Issues may occur if two hosts point to the same scratch folder location.

  • Page 139: Disabling Vaai Primitives For Amp-2

    Create one RAID-1 virtual drive using the remaining available capacity of all physical drives. Assign the name: RAID1_MI02 Disabling VAAI primitives for AMP-2 When you install VMware vSphere ESXi on AMP-2, disable the VAAI primitive for each VMware vSphere ESXi host. About this task For more information, refer to VMware Knowledge Base article...

  • Page 140: Creating A Backup Of A Configuration Repository

    • Monitor disk storage resources to prevent overuse issues and data unavailability Procedure To create the backup directory, type: drive :\Cisco. Use the D:\ drive, however, if the D:\ drive is not available, use the C:\ drive. This drive is referenced throughout these instructions.

  • Page 141: Restoring A Configuration File

    What to do next Establish a procedure to restore a single configuration file, the entire repository, and the supporting process to populate it, or restore the complete host where the repository exists. Restoring a configuration file Restore a network or storage device configuration file in the event of failure, corruption, or other data loss event.
  • Page 142 • VMware vCenter Update Manager • VMware SSO Service and SQL Database • Element Manager • Other VMs identified as part of the Core or Optional workloads to manage the Converged System. You must perform configuration backups for these Converged System devices: •...

  • Page 143: Guidelines For Backing Up Configuration Files

    Guidelines for backing up configuration files Backing up configuration files Back up Converged System configuration files with Vision software. As a system administrator, back up and restore Vision System Library and Converged System configuration files with Vision software. IPv6 is not supported by Vision software. For information about performing these tasks, refer to: •...
  • Page 144 Because of routing requirements, you may need to add VRF management to the end of each copy command. The variable $(TIMESTAMP) included in the file name inserts the date/time into the file name when the tasks are executed. From the network device, to create the backup task, type: SWITCH# conf t SWITCH(config)# scheduler aaa-authentication username login password...

  • Page 145: Backing Up Cisco Ucs Fis

    To confirm the scheduler update, type: SWITCH# show scheduler config config terminal feature scheduler scheduler logfile size 16 config terminal scheduler job name cfgBackup copy startup-config tftp://<IP_Address>/9500/config/D01-9500-01_startup_$ (TIMESTAMP).cfg copy running-config tftp://<IP_Address>/9500/config/D01-9500-01_running_$ (TIMESTAMP).cfg config terminal scheduler schedule name Daily0600 time daily 06:00 job name cfgBackup config terminal scheduler schedule name Daily1800...

  • Page 146: Creating And Runnig The Backup Using The Cisco Ucs Manager

    Before you begin • The TFTP service must be installed, configured, and active, on the AMP server where the configuration repository exists. • Obtain log on credentials for the device configuration backup. • Obtain the network IP address of the configuration backup repository. •...

  • Page 147: By Using The Cisco Ucs Cli

    Select the All node. From the Work window, select the General tab. In the Actions area, select Backup. From the Backup Operations table of the Backup Configuration window, select the backup operation that you want to run. In the Admin State field, select Enabled. For all protocols except TFTP, type the password in the Password field.

  • Page 148: Creating And Running The Backup Using Scheduled Backups

    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 # Creating and running the backup using scheduled backups Create and run the FI backup using scheduled backups. About this task The following conditions apply for scheduled backups: •...

  • Page 149: Configuring Fault Suppression

    Configuring 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.
  • Page 150 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.
  • Page 151 Type a description in the Description field. Verify Enabled is checked. To create a new job step entry, under Select a page, select Procedure (Steps), and then click New. From the New Job Step window, in the Step name field, type Backup or other text. Verify that the default value is set in the New Job Step windowType field.
  • Page 152 Use the following table to create the settings: For these Make the following settings databases master, model, In the Frequency section, set the Occurs field to Daily. msdb Verify that the Recurs field is set to 1 day(s). In the Daily Frequency section, check Occurs once at and set to 06:30 AM. In the Duration section, confirm that the Start date is set to the current date and No end date is selected.
  • Page 153 Related information Microsoft Developer Network article for SQL Server 2012: Change Server Authentication Mode Guidelines for backing up configuration files...

  • Page 154: Backing Up Cisco Mds Switches

    Backing up Cisco MDS switches Creating 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. Before you begin • Start the TFTP service on each of the management servers.

  • Page 155: Scheduling The Task To Purge Older Backup Files

    Procedure To create a script that deletes old backups of the startup and configuration files, copy the VBS script below and save it to the following path: D:\scripts\delete_old_backups.vbs 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...
  • Page 156 On the Schedule tab, schedule the task to run daily at 1:00 AM. Backing up Cisco MDS switches...

  • Page 157: Configuring Vmware Enhanced Linked Mode (Vsphere 6.0)

    (vSphere 6.0) Introduction One of the advantages of a Dell EMC Converged System is turnkey delivery of a pre-configured 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 on to a single VMware vCenter and operate, manage and...

  • Page 158: Backing Up And Restoring Converged Systems With Elm

    Due to the increased complexity and size of the VMware vSphere 6.0 fault, operation, and maintenance domain, Dell EMC recommends AMP-2S with an SMP/VMP configuration to simplify VMware vSphere 6.0 management with more than two Converged Systems or VMware vCenter servers.

  • Page 159: Converged System Amp Design

    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. Refer to the following link for backup limitations with multi-site SSO: •...

  • Page 160: Elm Scalability Planning

    Dell EMC recommends the deployment of the VCSA. However both the VCSA and VMware vCenter for Windows are supported with ELM. Ensure that the AMP server(s) have network connectivity and sufficient resources to meet any additional workload. This occurs after delivery and implementation. A redundant AMP is recommended.

  • Page 161: Intra Converged System Elm Scalability Planning

    PSC. In this scenario, the non-standard configuration of three PSCs in a Converged System is necessary to allow the repointing. 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, and management domain and reduces RCM upgrade complexity.

  • Page 162: Inter Converged System Elm Scalability Planning In A Single Physical Data Center

    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 a VMware vSphere 6.0 ELM configuration, reduces the size of the fault, operation and management domain and reduces RCM upgrade complexity.

  • Page 163: Inter Converged System Elm Scalability Planning With Multiple Physical Data Centers

    Converged System with two PSCs and a maximum of two VMware vCenter servers. In this scenario, a Dell EMC AMP-2S solution is easier to maintain and still provides single pane of glass management for the multiple Converged Systems.
  • Page 164 For VMware vSphere 6.0, Dell EMC does not recommend and does not support a mix of embedded and external PSCs. A VMware vCenter server with an embedded VMware PSC is suitable for small environments. You cannot join other VMware vCenter servers or VMware PSCs to this VMware vCenter Single Sign-On domain.

  • Page 165: Elm Dependencies And Limitations

    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.

  • Page 166: Vmware Elm References

    Although a VMware vSphere 6.0 Single Sign-On domain can be large, the Dell EMC approach for ELM with VMware vSphere 6.0 deployments takes into account the increased complexity for backup and recovery and RCM upgrades.
  • Page 167 Dell EMC recommends the deployment of the AMP-2S product for large SSO domains. The following table summarizes ELM with VMware vSphere 6.0 scalability and the AMP-2S. Maximum Maximum number of Maximum number of Maximum number Deploy ELM Deploy number of...

  • Page 168: Configuring Vmware Enhanced Linked Mode (Vsphere 6.5U1)

    (vSphere 6.5U1) Introduction to ELM (vSphere 6.5U1) One of the advantages of a Dell EMC Converged System is turnkey delivery of a pre-configured 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...

  • Page 169: Backup And Restore Converged Systems With Vmware Elm (Vsphere 6.5)

    The VMware vCenter Server 6.5 supports file-based and image-based backups. Backup/Restore jobs can be initiated using GUI or API interfaces.Dell EMC recommends using VCSA Native file-based backup to backup/restore PSC vCenter Server and recommends following the procedure to recover failed PSC’s/ VC’s.

  • Page 170: Backup And Recovery Capabilities

    Procedure Run the installer of same version/build. Select restore option. Enter backup details such as location of backup files, protocol used with port number, and credentials. Review the backup information and provide the appliance deployment target ESXi. Provide the hostname of the failed PSC and select deployment size. Select data store and review network settings.

  • Page 171: Converged System Amp Design (Elm/Vsphere 6.5U1)

    Converged System AMP design (ELM/vSphere 6.5U1) Dell EMC manufacturing configures the AMP with VMware vSphere 6.5U1 using only VMware recommended topologies. Deployment of the PSC and VMware vCenter using a non-recommended topology may prevent backing up and restoring a VMware vCenter server environment with a PSC(s).
  • Page 172 • One Single Sign-On domain • One or more Single Sign-On sites • One or more vCenter Servers with two external Platform Services Controller in two or more Converged Systems across multiple sites. Configuring VMware Enhanced Linked Mode (vSphere 6.5U1)
  • Page 173 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 for Windows is not supported on Converged Systems.

  • Page 174: Vmware Elm Scalability Planning (Vsphere 6.5U1)

    The following table provides the ports required between Converged Systems for ELM functionality: Port Protocol Description Required For Node to Node Communication TCP/UDP This port must be open on the local and all Windows installations vCenter Server to remote instances of vCenter Server. This and appliance Platform Services is the LDAP port number for the Directory...

  • Page 175: Intra Converged System Vmware Elm Scalability Planning (Vsphere 6.5U1)

    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 Maximum number of PSCs per VMware vSphere domain Maximum number of PSCs per site, behind a load balancer One PSC 8 VMware vCenters...

  • Page 176: Inter Converged System Vmware Elm Scalability Planning In Converged Systems In A Single Physical Data Center (Vsphere 6.5U1)

    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.

  • Page 177: Inter Converged System Elm Scalability Planning With Multiple Physical Data Centers (Vsphere 6.5U1)

    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 a mix of embedded and external PSCs. A VMware vCenter server with an embedded VMware PSC is suitable for small environments.
  • Page 178 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 You must update PSCs sequentially. Each software upgrade of a PSC may take 30 minutes approximately.

  • Page 179: Vmware Elm References (Vsphere 6.5U1)

    Although a VMware vSphere 6.5U1 Single Sign-On domain can be large, the Dell EMC approach for ELM with VMware vSphere 6.5U1 deployments takes into account the increased complexity for backup and recovery and RCM upgrades.
  • Page 180 Maximum Maximum Maximum number Maximum number Deploy ELM Deploy AMP-2S in number of number of of VxBlock of Data Centers an SMP/VMP PSCs VMware systems configuration vCenter servers >10 >15 >5 >5 Configuring VMware Enhanced Linked Mode (vSphere 6.5U1)
  • Page 181 Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA in October 2017. Dell EMC believes the information in this document is accurate as of its publication date. The information is subject to change without notice.

This manual is also suitable for:

Vblock systems 350

Table of Contents