This section describes the replacement procedure for a failed SATADOM disk on a host.

Prerequisites

Ensure that there are at least 4 hosts in the management or workload domain to which the faulty host belongs. If there are less than 4 hosts, add a host to the domain from the capacity pool, if possible.

Procedure

  1. Decommission the affected host.
    1. If you are decommissioning a qualified vSAN Ready Node (i.e. if you did not purchase a fully integrated system from a partner), note the BMC password for the host by navigating to the /home/vrack/bin/directory in the SDDC Manager Controller VM VM and running the lookup-password command.
    2. On the Dashboard page, click VIEW DETAILS for Workload Domain and click the affected domain.
    3. In the PHYSICAL RACKS column, click the physical rack that contains the affected server.
    4. Scroll down to the Hosts section.
    5. In the HOST column, click the host name that shows a critical status (for example, N1 in the example below).
      rack
    6. In the HOST column, click the host name that shows a critical status (for example, N1 in the example below).

      The Host Details page displays the details for this host.

      host

    7. In the HOST column, click the host name that shows a critical status (for example, N1 in the example below).
    8. Note the IP addresses displayed in the NETWORK TWO and MANAGEMENT IP ADDRESS fields.
    9. Click Decommission.

      decomm

      If this host belongs to a workload domain, the domain must include at least 4 hosts. If the domain has fewer than 4 hosts, you must expand the domain before decommissioning the host. If the domain contains only 4 hosts and one of them is dead, click Force decommission to decommission the host.

    10. Click CONFIRM.

      During the host decommissioning task, the host is removed from the workload domain to which it was allocated and the environment's available capacity is updated to reflect the reduced capacity. The ports that were being used by the server are marked unused and the network configuration is updated.

    11. Monitor the progress of the decommissioning task.
      1. On the SDDC Manager Dashboard, click STATUS in the left navigation pane.

      2. In the Workflow Tasks section, click View Details.

      3. Look for the VI Resource Pool - Decommission of hosts task.

      4. After about 10 minutes, refresh this page and wait till the task status changes to Successful.

    12. For qualified vSAN Ready Nodes, change the password on the host to the common password for ESXi hosts. Log in to the BMC console using the password noted in step a and change the OOB password to D3c0mm1ss10n3d!.

      This step is automated for hosts in an integrated system.

  2. Power off the server.
  3. Turn on the chassis-identification LED on the host.
    1. In a web browser, navigate to the Management IP address that you noted down in step 5.
    2. Login with your BMC user name and password.
    3. Following the documentation from your vendor, turn on the chassis-identification LED.

      The chassis-identification LED on the host starts to beacon (flashing on and off).

  4. Replace the faulty SATADOM on the server and power on the server.
  5. Install ESXi on the host. See #GUID-11E870D4-9760-494E-A001-04EA823D873E.
    • Select the SATADOM for installation.

    • Set the root password on the host to EvoSddc!2016.

  6. Reboot the host.
  7. Log in to the server with the following credentials.

    User name: root

    Password: EvoSddc!2016

  8. Perform the following steps on the host.
    1. Assign a static IPv4 address between the range 192.168.100.50 - 192.168.100.73, subnet 255.255.252.0, and gateway 192.168.100.1.
    2. Set the DNS IP to 192.168.1.254.
    3. Enable SSH.
    4. Enable firewall on SSH host and restrict connections to the 192.168.100.0/22 subnet by running the following commands:

      esxcli network firewall ruleset set --ruleset-id=sshServer --allowed-all false

      esxcli network firewall ruleset allowedip add --ip-address=192.168.100.0/22 --ruleset-id=sshServer

  9. SSH to the host and clean the vSAN partitions by running the following commands.

    #esxcli vsan storage automode set --enabled=false

    #esxcli vsan storage list|grep "Is SSD: true" -C5| grep "Display Name" |awk '{print $3}'

    Note the SSD naa.

    #esxcli vsan storage remove -s SSD naa

    Run this command for each diskgroup.

    #esxcli vsan cluster leave

  10. If you were unable to remove the vSAN naa, power cylce the host and re-try step 15.

What to do next

Add the host back to the rack. See #GUID-47B2C555-3184-40B5-BCA9-86033A717786.