• Deploying UnityVSA HA

    PDF

    Deploying UnityVSA HA

    Set up the VM environment for UnityVSA HA

    Procedure
    1. Log into vCenter as a user with administrative privileges.
    2. Verify that the selected ESXi host meets the required configuration, as outlined in Requirements for installing UnityVSA HA.
    3. (On-premises only) Verify, and if necessary, configure the host network configuration.
    4. Check whether there are three available, unused VLANs in the network environment to use for deploying the CMI, HB0, and HB1 networks.
    5. (Unity Cloud Edition only) If you are deploying to VMC, verify that four network segments have been created.
      Three network segments are for deploying the CMI, HB0, and HB1 networks. One network segment is for I/O.
    6. (Optional, on-premises only) Verify that a vSphere switch has been created.
      You can create a switch later using the Deployment Utility. If you choose to create a switch before deployment, observe the following guidelines:
      1. Determine which port groups are associated with which subnets so you can ensure that the VM's network adapters are assigned to the correct subnet.
        • Ethernet port 0 is associated with network adapter 6.
        • Ethernet port 1 is associated with network adapter 7.
        • Ethernet port 2 is associated with network adapter 8.
        • Ethernet port 3 is associated with network adapter 9.

        To verify which VM network adapter is mapped to which UnityVSA Ethernet port, compare the MAC address for the network adapter in the vSphere VM Hardware summary to the MAC address for the Ethernet port in Unisphere.

        To display the MAC address in Unisphere, select System > System View > Enclosures. Select the rear view of the Disk Processor Enclosure (DPE) and click an Ethernet port to display information about the port, including its MAC address. Take note of the Ethernet port name, for example, SPA Ethernet Port 3, since the port name is used when creating iSCSI and replication network interfaces.

      2. If the network environment supports jumbo frames, verify that the MTU value for the switch on the ESXi host is set to the same value as the UnityVSA Ethernet ports.

        If the UnityVSA VM sets an MTU value higher than the MTU value set on ESXi, the UnityVSA VM MTU value defaults to the smaller value. In vSphere, select Edit Settings on the Virtual switch to check the MTU value.

        In Unisphere, select the Settings icon, and then select Access > Ethernet. MTU is not displayed by default so you must select the Customize icon, select Columns, and then click MTU.

        The VMware Knowledge Base article iSCSI and Jumbo Frames configuration on VMware ESXi/ESX (1007654) provides more information.

      NOTICE  

      Do not modify the VM, such as changing the virtual hardware configuration (CPU, memory, NICs, and so on). Modifying the VM causes UnityVSA to boot in service mode to prevent invalid configurations.

    Download the UnityVSA HA files

    Before you begin

    To obtain a UnityVSA Professional Edition license and download UnityVSA HA files, you must set up a product support account. If you do not already have an account, go to your product support site to set one up.

    Procedure
    1. Using a web browser, go to your product support site.
      The files for Unity Cloud Edition are available from the VMware Cloud Marketplace website.
    2. Select UnityVSA.
    3. Locate the available downloads.
    4. Select each of these files and save them to your computer: UnityVSA OVA file, TBN OVA file (as necessary), and the UnityVSA HA Deployment Utility.

    Deploy UnityVSA HA on an on-premises ESXi host with the UnityVSA Deployment Utility

    Before you begin
    1. Follow the directions for setting up the VM environment in Set up the VM environment for UnityVSA HA.
    2. Install and launch the UnityVSA Deployment Utility.
    3. Select Deployment Utility for UnityVSA in On-premise VMware Data Center.
    When you deploy UnityVSA HA on an EXSi host, you can choose whether to deploy with or without a Tie Breaker Node (TBN). A TBN provides increased protection from network failures, because it resolves situations where one SP cannot detect the other SP. For UnityVSA HA, the TBN is a minimal VM running a network heartbeat client, which exchanges heartbeat messages with both SPA and SPB.
    Procedure
    1. Select whether to deploy the new UnityVSA with or without a TBN. If you choose not to deploy the new UnityVSA with a TBN now, you can add a TBN to the UnityVSA after it is created. For information, see Deploy a tie breaker node to an existing UnityVSA HA using the GUI.
    2. Provide the login credentials and IP details for the vCenter service. When you deploy UnityVSA with HA, the hosts must be managed under the same vCenter datacenter.
    3. Select the UnityVSA OVA file to use for the deployment.
    4. Select a separate ESXi host for each SP deployment. For high availability reasons, Dell EMC does not recommend deploying both SPs to a single ESXi host.
    5. On the System Datastores page:
      • Select one datastore for each SP to create its private system drive. Each SP needs at least 60 GB space for private system data.
      • Select one shared datastore for a shared system drive between both SPs. The shared datastore needs at least 40 GB free space.
      Note:  It is a best practice to select three different datastores in this step.
    6. Select two other shared datastores for storage-based heartbeats between the two SPs.
      Note:  The virtual disks that are created from the heartbeat datastores are only 2 MB in size.
    7. Select the network mappings for the management and data networks, making sure that:
      • The management network is on a network accessible by the workstation that is used to access Unisphere.
      • The data networks are on networks accessible by the host that will attach to the UnityVSA.
    8. Configure the internal network. To deploy UnityVSA HA, both SPs must communicate over a distributed switch. You can either create a switch, or select an existing one:
      • If creating a switch, you must provide two uplink ports for each ESXi host for redundancy. Each uplink port should also connect to a different network infrastructure switch. Enter the VLAN IDs for the HBO, HBI, and CMI networks.
      • If selecting an existing switch, each ESXi host must provide for two uplink ports for redundancy. Enter the VLAN IDs for the HB0, HB1, and CMI networks.

      Whether you use an existing switch or create one, three port groups are created, which are for HB0 (Heartbeat 0), HB1 (Heartbeat 1), and the Common Messaging Interface (CMI). Each of them needs a nonzero unique VLAN ID. If you leave the VLAN input empty, the deployment utility automatically chooses an unused VLAN ID for each port group.

      If you deploy the SPs on different ESXi hosts, the physical switches must support VLAN and be configured as trunking mode instead of access mode. Access mode enables only specific VLANs to pass.

    9. Enter the UnityVSA system name and IP address information.
    10. (Applies to deploying UnityVSA HA with a TBN) On the Configure Tie Breaker Node Properties page, enter the name of the TBN VM, and then select the OVA file, host, and datastore to use for the TBN. You must also select two ports for the TBN.
      Note:  It is a best practice to select a host for the TBN that has not been used for other purposes. It is also recommended that you choose two separate ports for the TBN.
    11. Review the settings, and select Deploy.
    12. If you deployed the UnityVSA HA with a TBN, use the Unisphere GUI to enable the TBN function. You can do this in the Initial Configuration Wizard or by accessing the Tie Breaker Node page in the Management settings. For information, see Enable or change the tie breaker node on a UnityVSA HA.

    Deploy Unity Cloud Edition with the UnityVSA Deployment Utility

    Before you begin
    1. Obtain the template file for your deployment type and upload it to the VMC content library. You can also add the template file directly to your VMC content library from the VMware Cloud Marketplace website.
    2. Verify that at least four network segments have been created. Three network segments are for deploying the CMI, HB0, and HB1 networks. One network segment is for I/O.
    3. Install and launch the UnityVSA Deployment Utility.
    4. Select Deployment Utility for UnityVSA in VMware Cloud for AWS.
    The deployment process for Unity Cloud Edition differs from the deployment process for on-premises ESXi servers.
    Procedure
    1. Provide the login credentials and FQDN for the vCenter service.
      Note:  When you deploy Unity Cloud Edition HA, the hosts are managed under the same vCenter datacenter.
    2. Select the cluster on which to deploy Unity Cloud Edition.
    3. Select the Unity Cloud Edition template that you uploaded to the library and model type to use for the deployment.
    4. Configure the external network mappings for the management and data networks, making sure that:
      • The management network is on a network accessible by the workstation that is used to access Unisphere.
      • The data networks are on networks accessible by the host that will attach to the Unity Cloud Edition.
      • The user account that you are using has Network.Assign privileges on the selected network segment.
    5. Configure the internal network mappings for Common Messaging Interface (CMI) and network-based heartbeat connections.
      • The internal network mappings cannot use the same network segments as the external network.
      • Each of the three mappings must be unique.
      • The mappings cannot be in use by another VM.
      • The user account that you are using should have Network.Assign privileges on the selected network segment.
    6. Enter the Unity Cloud Edition system name and management IP address.
    7. Review the settings and click Deploy.
    After you finish
    Note:   To guarantee HA capability, the SPA and SPB VMs must remain on separate hosts. To keep the VMs separated, you must create an anti-affinity policy in the VMC GUI.
    1. Log in to the VMC GUI.
    2. Create a VM-VM anti-affinity policy that separates the two SP VMs. For more information about creating a VM-VM anti-affinity policy, see VMware documentation.
    3. If the SP VMs are powered off, power them on.
    4. Ensure the two SP VMs move to separate hosts before you start provisioning.

    Deploy a UnityVSA HA on an on-premises ESXi host using the UnityVSA HA Deployment Utility CLI

    You can deploy a UnityVSA HA using the UnityVSA HA Deployment Utility CLI instead of the GUI. To access the CLI:

    1. Follow the directions for setting up the VM environment in Set up the VM environment for UnityVSA HA.
    2. Download the UnityVSA HA Deployment Utility CLI from your support website.
    3. Perform the following based on your operating system:
      • On Windows, double-click the installer executable and follow the prompts. The default installation location is as follows:
        • For the x86-64 package, C:\Program Files\EMC&#xnityVSA Deploy Utility CLI.
        • For the i586 package, C:\Program Files (x86)\EMC&#xnityVSA Deploy Utility CLI.
      • On Linux, type: rpm -ihv <filename>, where filename is the name of the installer executable. The default installation location is:

        /opt/EMC/UnityVSADeployUtilityCLI/

    4. To launch the UnityVSA client and see the options and examples, perform the following in a command prompt based on your operating system:
      • From a Windows operating system, type:
                                      UnityVSADeployUtilityCLI-<arch>-<version>.exe --h
                                    

        where <version> is the version of the client installed.

      • From a Unix operating system, type:
                                      UnityVSADeployUtilityCLI --h 
                                    

    Manage virtual disks for Unity Cloud Edition

    Before you begin
    1. Install and launch the UnityVSA Deployment Utility.
    2. Select UnityVSA Disk Management Utility.

    Unity Cloud Edition HA requires the SPA and SPB VMs to connect to and share each disk file. To share a disk file in VMware, you must provision it as a thick eager zeroed disk.

    The VMC GUI does not support provisioning thick eager zeroed disks. The UnityVSA Disk Management Utility provides a graphical interface to add and manage disks for Unity Cloud Edition HA without requiring the SDK or PowerCLI.

    Procedure
    1. Provide the vCenter FQDN and login credentials.
    2. Select the Unity Cloud Edition HA for which you want to manage storage.
      Note:  The first five disks on the Unity Cloud Edition are system disks and are not listed in the Manage Disk table.
    3. Choose the management action that you want to perform:
      • To add a disk, choose the size of the disk and then click Add.
      • To fix a disk that is not connected to both SPs, select the disk and click Fix Disconnected Disks.

        A disk file that is not attached to both SPs is marked with a red X icon.

    4. When you have finished managing your disks, close the Disk Management Utility.

    Add virtual disks to a UnityVSA HA deployment

    When you create the UnityVSA VM, five virtual disks (vmdks) are automatically created for the VM's system data. These are the virtual disks identified as 1-5. Do not modify or delete these disks.

    You must add at least one virtual disk for user data. You can add more virtual disks, up to the system limit (16), when additional storage for user data is needed. The minimum virtual disk size is 10 GB. A disk appears as faulted if it is smaller than 10 GB and larger than the storage size allowed by the UnityVSA edition and version. To view your system's limits, in Unisphere select the Settings icon, and then select Software and Licenses > System Limits.

    The following considerations apply to virtual disks in a UnityVSA HA deployment:

    • For optimal performance, it is recommended that you create the virtual disks used to provide user data on a different datastore than the one where UnityVSA is deployed. Failure to follow this recommendation can lead to system and I/O performance degradation.
    • When you add a virtual disk, you must add it to both SPA and SPB.
    • You can only connect ten virtual disks for user data to the first VMware paravirtual SCSI controller provided with the UnityVSA. If you add an 11th virtual disk, select the second controller. Make sure this controller is of type VMware paravirtual. If the SCSI controller is a different type, UnityVSA can have boot problems and can fail to recognize the new virtual disks attached to it.
    • Allow up to 60 seconds for UnityVSA to recognize and display the newly attached virtual disks.
    • Using vSphere to modify the physical configuration of a UnityVSA VM (such as adding or removing network interfaces or modifying the VM's cache size) is not supported, except for adding virtual disks to store user data.
    • Although resizing a virtual disk through VMware is not supported in UnityVSA, if the virtual disk is not part of a storage pool, you can remove it from UnityVSA and add a new one of the preferred size. Resizing virtual disks that are already part of a storage pool can result in a failed, unrecoverable pool.
    • Important: Never add a virtual disk to an SP VM that already has a disk with the same UUID. This can happen when a virtual disk has been added to a SP VM and you mistakenly trying to add it again. This will make the SP VM hang and have undetermined consequences, such as an SP panic and data unavailability.
    Procedure
    1. In vSphere, right-click on the UnityVSA SPA VM, and select Edit > Settings.
    2. In the New Device field on the Virtual Hardware tab, select Add New Device, and then select Hard Disk.
    3. Enter the size of the disk you want to add, and select Thick Provision Eager Zeroed as the provisioning method.
    4. Finish stepping through the wizard, and select Finish.
    5. When the disk creation process completes, return to the home page.
    6. Right-click on the UnityVSA SPB VM, and select Edit > Settings
    7. On the Virtual Hardware tab, select Add New Device > Existing Hard Disk.
    8. Select the existing vmdk file created in step 5.
    9. Finish stepping through the wizard, and select Finish.