Dell PowerFlex 4.6.x Administration Guide

Replace additional CloudLink Center VM members

Use this procedure to replace additional CloudLink Center VM members.

1. Power off the CloudLink 7.1.9 VM cluster member:
   1. From VMware vSphere Client, log in to the vCSA and click Menu > Shortcuts > Hosts and Clusters.
   2. From PFMC datacenter, navigate to PFMC Cluster > CloudLink 7.1.9 VM and click Power > Shut Down Guest OS, and click Yes.
   The connected nodes are connected to another member of an existing cluster. This may be one of the already replaced members or any remaining CloudLink Center 7.1.x. To verify the PowerFlex node or cluster connectivity, use SSH to log in to a PowerFlex node with encrypted disks, and issue a svm status command. It may take several minutes for the agent to connect successfully to another CloudLink Center including an 8.1.x instance.
2. Deploy a new CloudLink 8.1.x OVA:
   1. From the VMware vSphere Client, log in to the vCSA and click Menu > Hosts and Clusters.
   2. From PFMC datacenter, right-click PFMC Cluster and select Deploy OVF Template.
   3. Select the local file and click Upload Files.
   4. Select the CloudLink OVA and click Open > Next and enter the name.
   5. Click Next > Next > Next and select the datastore and virtual disk format: Thin Provision.
   6. Click Next, select the CloudLink Center associated VLAN, and click Next > Finish.
3. Before powering on the CloudLink 8.1.x VM for the first time, configure the network settings to retrieve the same static IP address which was originally assigned to the now powered down 7.1.9 CloudLink Center (in step 1):
   1. Navigate to the VM from the vCenter inventory.
   2. On the Configure tab, expand Settings and select vApp options, and click Edit....
   3. Under OVF Environment transport, select the VMware Tools check box, and click OK.
   4. Under OVF Details for the OVF Environment Transport, click OVF Settings, and ensure that View OVF Environment and OVF Environment Transport: VMware Tools and Installation boot are disabled as VM is in a powered off state.
   5. Under Properties, click ADD and create separate entries for the following values. Ensure you add the key ID and label as specified in the following table for all labels.

      Table 1. Key IDs and labelsEntries you need to create for Key IDs and labels

      Key ID	Label
      cl.interface.0.ip.4.netmask	IPv4 netmask
      cl.interface.0.ip.4.gateway	IPv4 gateway
      cl.interface.0.ip.4.address	IPv4 address
      cl.hostname (optional)	Hostname (optional)

      After each entry, click Save.
   6. For each item created in the previous step, select Set Value and set the static IP address, gateway, netmask, and hostname (optionally).
   7. Snapshot VM after setting values (if desired).
4. Power on the CloudLink 8.1.x VM:
   1. From the VMware vSphere Client, log in to the vCSA, click Menu > Shortcuts > Hosts and Clusters.
   2. From PFMC datacenter, click PFMC cluster, and right-click CloudLink 8.1 VM.
   3. Click Power > Power ON.
5. Once the CloudLink VM boots up, the IP configuration should be set as the static IP address and the web console should be reachable.
6. Browse to the hostname or IP address of the powered on CloudLink Center 8.1.x.
7. From Boot Terms and EULA, accept the terms and conditions and set the secadmin credential password (use recorded value).
8. The initial configuration window appears on top of the main console view.
9. To set the login password to the existing CloudLink 7.1.9 VM login password, click Change password.
10. Set the console password to the existing CloudLink 7.1.9 VM password. This may be defined as a CloudLink console or a OS user. Click Change Console Password.
11. If you configured the optional hostname parameter, the INITIAL CONFIGURATION wizard contains the value. If not, a randomly affixed name appears. If you intend to modify the hostname, enter a name and click Next. The INITIAL CONFIGURATION wizard reloads and may take a minute or so to reconnect. You may have to refresh the browser.
12. Click Next and wait for the browser to refresh.
13. Click Deployment Type and select Add as a Cluster Member, and click Next.
14. Modify the Leaf Cert option to Disabled.
15. When prompted for the server name or IP address, retain the pre-populated IP address of the new VM and click Next.
16. Enter the DNS Server value and click Next.
17. Enter the IP address of the first cluster member replaced along with the secadmin credentials and click Join Cluster.
    This process takes a few minutes to complete.
18. Using the CloudLink UI, locate and populate the following information. Skip parameters where defaults or no custom configuration is specified.

    Table 2. CloudLink Center VM informationThe following table provides the CloudLink Center VM information

    CloudLink parameters	Navigation path	Do the following
    SNMP	Server > SNMP	Add remaining IP addresses (if more than one).
    Syslog	Server > Syslog	Add hosts, port, facility, and protocol.
    DNS	Server > DNS	Add remaining IP addresses (if more than one).
    NTP	Server > Time	Add the NTP server addresses.
    TLS	Server > TLS	If the instance has a custom certificate, provide the corresponding files for the format selected (PEM - certificate and key, signed PEM - certificate, PKCS12 - certificate and password).
    Backup	System > Backup	Set the backup prefix and configure the backup store (if not local, provide the password to restore the configuration).
    E-mail notifications	System > Email Notifications	Modify the configuration and populate with recorded data. Server type, server address, port, sender address, and user (enter the customer-provided password). Add the recipient address.

19. Repeat this process for the remaining cluster members (up to four).