Users Guide

Boot error message for missing SD card

The XC730xd system has only one SD card. When you start the system, the following error message is displayed:

The secondary SD card is missing, not responding, or in write-protected mode. Do one of the

following:

1. Install an SD card media in the secondary SD card slot.

2. Reseat or replace the SD card media.

3. If the secondary SD card is intentionally not installed or write-protected mode is

expected, then no response is required.

The message is a known issue and you must ignore it.

Deployment outline

The ow of tasks in deploying the XC Series Hyper-Converged Appliance is shown here.

Figure 5. Deployment workow process.

First time boot scripts for Nutanix Acropolis

Nutanix Acropolis nodes have been per-congured and do not require additional rst-time boot conguration. These nodes boot to

the hypervisor and are ready to be clustered after the CVM has all services up and running.

Create Nutanix storage cluster

• Use the Nutanix web-based tool to create a Nutanix storage cluster from all locally discovered nodes that are ready to be

clustered. During this process, the following parameters are set:

– Cluster maximum Redundancy Factory (RF)

– Cluster name

– Cluster virtual IP (optional for AHV and vSphere)

– Subnet mask and default gateway (iDRAC, hypervisor and CVM)

– Domain Name Server(s) (DNS)

– Network Time Protocol (NTP) servers (hypervisor NTP N/A for Hyper-V)

– Hypervisor hostnames

– Node IPs (iDRAC, hypervisor and CVM)

– Re-installation of new hypervisor and CVM (optional with Nutanix Foundation CVM)

• Option to create Nutanix storage cluster manually using command line interface.

NOTE: In Acropolis base (NOS) 4.5, a new web-based clustering tool called Nutanix Foundation CVM replaces the

earlier used cluster initialization page (deprecated). Nodes with Acropolis base (NOS) 4.5 or later installed in factory

uses Nutanix Foundation CVM for initial deployment while those installed with NOS prior to Acropolis base (NOS) 4.5

will continue to use the traditional cluster initialization page.