Académique Documents
Professionnel Documents
Culture Documents
Acropolis 5.0
03-Feb-2017
Notice
Copyright
Copyright 2017 Nutanix, Inc.
Nutanix, Inc.
1740 Technology Drive, Suite 150
San Jose, CA 95110
All rights reserved. This product is protected by U.S. and international copyright and intellectual property
laws. Nutanix is a trademark of Nutanix, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
License
The provision of this software to you does not grant any licenses or other rights under any Microsoft
patents with respect to anything other than the file server implementation portion of the binaries for this
software, including no licenses or any other rights in any hardware or any devices or software that are used
to communicate with or in connection with this software.
Conventions
Convention Description
user@host$ command The commands are executed as a non-privileged user (such as nutanix)
in the system shell.
root@host# command The commands are executed as the root user in the vSphere or Acropolis
host shell.
> command The commands are executed in the Hyper-V host shell.
Version
Last modified: February 3, 2017 (2017-02-03 0:51:17 GMT-8)
4
AOS Upgrade to 5.0
Tip: While upgrading does not require cluster downtime, it does create additional load on the
nodes. For this reason, Nutanix recommends that you perform upgrades during times of non-peak
load and shut down any VMs that are not being actively used.
For information about upgrade paths for this release, browse to the Nutanix Support portal and consult
Downloads > Acropolis Upgrade Paths.
Nutanix recommends upgrading your cluster through the Prism web console by using the Upgrade
Software feature, also known as 1-click upgrade, as described in the Nutanix Web Console Guide. This
describes how to upgrade AOS through a command line.
If you are upgrading and use Prism Central to manage your Nutanix clusters, upgrade Prism Central
first, then upgrade AOS on the clusters managed by Prism Central. See:
Upgrading Prism Central
Prism Central Release Notes. This document describes new features, resolved issues, and AOS/
NOS compatibility.
Important: For AHV only, the number of vCPUs per VM is only constrained by the number of
logical processors available to the VM. Any VM with a vCPU setting that is greater than the actual
physical number of CPU cores on the underlying host does not start. This condition also applies
to existing VMs from the AOS version from which you are upgrading. To start these VMs, reduce
the vCPU count to a value equal to or less than the number of actual physical cores. Please see
the System Maximums topic in the Web Console Guide for your AOS version for more information.
This note does not apply to ESX or Hyper-V clusters. [ENG-45727]
Warning: By default, Nutanix clusters have redundancy factor 2, which means they can tolerate
the failure of a single node or drive. Nutanix clusters with a configured option of redundancy factor
3 allow the Nutanix cluster to withstand the failure of two nodes or drives in different blocks.
Never shut down or restart multiple Controller VMs or hosts simultaneously.
Always run the cluster status command to verify that all Controller VMs are up before
performing a Controller VM or host shutdown or restart.
Controller VM Access
Most administrative functions of a Nutanix cluster can be performed through the web console or nCLI.
Nutanix recommends using these interfaces whenever possible and disabling Controller VM SSH access
with password or key authentication. Some functions, however, require logging on to a Controller VM
with SSH. Exercise caution whenever connecting directly to a Controller VM as the risk of causing cluster
issues is increased.
Warning: When you connect to a Controller VM with SSH, ensure that the SSH client does
not import or change any locale settings. The Nutanix software is not localized, and executing
commands with any locale other than en_US.UTF-8 can cause severe cluster issues.
To check the locale used in an SSH session, run /usr/bin/locale. If any environment variables
are set to anything other than en_US.UTF-8, reconnect with an SSH configuration that does not
import or change any locale settings.
Note: Ensure that the latest NCC version for your pre-upgrade AOS/NOS version is installed on
your cluster as part of preparing to upgrade AOS. For information about installing or upgrading
NCC, see the NCC Release Notes.
From the Prism web console Health page, select Actions > Run Checks. Select All checks and
click Run.
If the check reports a status other than PASS, resolve the reported issues before proceeding. If you are
unable to resolve the issues, contact Nutanix support for assistance.
What to do next: Complete preparation with steps specific to the hypervisor (AHV, Hyper-V, vSphere).
Caution: If the ESXi hosts in the cluster have been upgraded to a later version of ESXi, ensure
that all configurations specified by Nutanix have been made. The AOS upgrade fails if ESXi has
not been properly configured.
For instructions on upgrading vSphere on a Nutanix cluster, see vSphere Upgrade in the Nutanix
vSphere Administration guide.
1. If the cluster has iSCSI LUNs, set the ESXi hosts to avoid all paths down.
To check if the cluster has iSCSI LUNs, log on to an ESXi host as root and run esxcfg-scsidevs -m . If
any output other than the node local datastore is returned, log on to each ESXi host in the cluster and
enable the FailVolumeOpenIfAPD option.
root@esx# esxcfg-advcfg -s 1 /VMFS3/FailVolumeOpenIfAPD
This setting prevents the ESXi hosts from entering the all paths down (APD) state, which causes VMs
to stop responding and requires restarting ESXi hosts. For more information, see VMware KB article
1016626 at http://kb.vmware.com.
If the option is enabled, the host displays the following status.
Value of FailVolumeOpenIfAPD is 1
3. If remote replication is configured, ensure that no replication operations are currently in process. You
need to wait for any outstanding replications to complete before upgrading. Replication operations
cannot be in progress or paused during an upgrade.
b. Check replication status of every protection domain that is configured in the cluster.
nutanix@cvm$ ncli protection-domain list-replication-status name="pd_name"
Replace pd_name with the name of the protection domain. Check every protection domain.
If any replication operations are in progress, output similar to the following is displayed.
ID : 12983253
Protection Domain : pd02
Replication Operation : Receiving
Start Time : 09/20/2013 17:12:56 PDT
Remote Site : rs01
Snapshot Id : rs01:54836727
Aborted : false
Paused : false
Bytes Completed : 63.15 GB (67,811,689,418 bytes)
Complete Percent : 84.88122
If no replication operations are in progress, no output is displayed and you can continue
upgrading.
5. Increase the memory of the Controller VM (if needed), depending on your configuration settings for
deduplication and other advanced features.
Perform these steps once for each Controller VM in the cluster. See CVM Memory and vCPU
Configurations (G4/Haswell/Ivy Bridge) on page 15 for memory sizing guidelines.
Caution: To avoid impacting cluster availability, shut down one Controller VM at a time. Wait
until cluster services are up before proceeding to the next Controller VM.
a. Log on to the Controller VM with SSH and shut down the Controller VM.
nutanix@cvm$ cvm_shutdown -P now
d. Select Hardware > Memory and increase the memory configuration to the recommended amount
from the sizing guidelines.
e. Select Resources > Memory and select the Reserve all guest memory check box.
7. Ensure that the Nutanix upgrade installer is not delayed by potential DNS issues by logging on to an
ESXi host and modifying the ESXi SSH daemon settings.
b. Using a text editor such as vi, open the /etc/ssh/sshd_config file and add the string useDNS no .
Caution: To avoid impacting cluster availability, shut down one Controller VM at a time. Wait until
cluster services are up before proceeding to the next Controller VM.
1. Log on to the Hyper-V host with Remote Desktop Connection and start PowerShell.
3. Increase the memory of the Controller VM (if needed), depending on your configuration settings for
deduplication and other advanced features.
See CVM Memory and vCPU Configurations (G4/Haswell/Ivy Bridge) on page 15 for memory sizing
guidelines.
> Set-VMMemory cvm_name -StartupBytes (ram_gb*1024*1024*1024) `
-MaximumBytes (ram_gb*1024*1024*1024) -MinimumBytes (ram_gb*1024*1024*1024)
Replace cvm_name with the name of the Controller VM and ram_gb with the recommended amount
from the sizing guidelines.
Replace cvm_name with the name of the Controller VM that you found from the preceding command.
Replace cvm_name with the name of the Controller VM that you found in step 2.
5. Increase the memory of the Controller VM (if needed), depending on your configuration settings for
deduplication and other advanced features.
See CVM Memory and vCPU Configurations (G4/Haswell/Ivy Bridge) on page 15 for memory sizing
guidelines.
root@ahv# virsh setmaxmem cvm_name --config --size ram_gbGiB
root@ahv# virsh setmem cvm_name --config --size ram_gbGiB
Replace cvm_name with the name of the Controller VM and ram_gb with the recommended amount
from the sizing guidelines in GiB (for example, 1GiB).
Caution: If the ESXi hosts in the cluster have been upgraded to a later version of ESXi, ensure
that all configurations specified by Nutanix have been made. The AOS upgrade fails if ESXi has
not been properly configured.
For instructions on upgrading vSphere on a Nutanix cluster, see vSphere Upgrade in the Nutanix
vSphere Administration guide.
Prepare for the upgrade by following Preparing to Upgrade to AOS 5.0 on page 6.
Also follow Preparing to Upgrade to AOS 5.0 (vSphere) on page 6, Preparing to Upgrade to AOS
5.0 (Hyper-V) on page 8, or Changing CVM Memory Configuration (AHV) on page 8 depending
on the hypervisor.
Download the AOS 5.0 tar file and associated upgrade metadata file and copy both files to /home/
nutanix on one Controller VM in the cluster.
Ensure that no SRM workflows are in progress. If any are, wait until they complete before proceeding
with the upgrade.
1. Log on to the Controller VM that has the Nutanix software tar file.
2. Disable email alerts to avoid spurious alerts when Controller VMs restart during the upgrade.
nutanix@cvm$ ncli alerts update-alert-config enable=false
Before starting the upgrade, the installer checks the state of the cluster and the related upgrade
metadata to ensure the upgrade succeeds. If the pre-upgrade check fails, correct the conditions before
attempting to upgrade.
For each node in the cluster, this command updates the Controller VM image, updates the AOS
packages, and restarts it. Your SSH and any web console sessions to the Controller VM is terminated.
Upgrading the Controller VMs takes approximately 10 minutes per node in the cluster.
During upgrade, a task named HostRestoreVmLocality appears on the All VM Tasks tab. The task,
which restores VMs to their original host after they are migrated by Acropolis, is scheduled during
the upgrade process as part of a group of tasks that check the state of the cluster. In most upgrade
scenarios, no migration is required.
While the upgrade is in progress, you can monitor progress with the following command.
nutanix@cvm$ host_upgrade_status
This command specifies which Controller VMs have completed the upgrade, which is in progress, and
which have not yet been updated. Wait until the upgrade process completes.
If the upgrade fails to complete on a Controller VM after 20 minutes, perform the following steps.
a. Log on to the hypervisor host with SSH or the IPMI remote console (vSphere or AHV) or remote
desktop connection (Hyper-V).
c. Confirm that package installation has completed and that genesis is not running.
nutanix@cvm$ ps afx | grep genesis
nutanix@cvm$ ps afx | grep rc.nutanix
nutanix@cvm$ ps afx | grep rc.local
If any processes are listed, wait five minutes and try again. If none of these processes are listed, it is
safe to proceed.
Enter the nutanix password if prompted. Wait to proceed until the Controller VM has finished starting,
which takes approximately 5 minutes.
The upgrade process writes the following log files on the Controller VMs:
/home/nutanix/data/logs/install.out
/home/nutanix/data/logs/boot.out
/home/nutanix/data/logs/boot.err
/home/nutanix/data/logs/finish.out
/home/nutanix/data/logs/svm_upgrade.tar.out
The Target release version should match the target version, and each Controller VM should show SVM
cvm_ip_address is up to date.
If some Controller VMs are marked as needing to be upgraded, wait 5 minutes and check again. If the
command fails on one or more Controller VMs with a message like Could not connect to zookeeper:
ok, run the command again.
What to do next:
Apply licenses to the cluster. For more information about licensing, see License Management in the
Web Console Guide.
Complete the upgrade by following Completing Upgrade to AOS 5.0 on page 12.
1. If you use SNMP to manage or collect information from the Nutanix cluster, as soon as the upgrade
process is complete, update the Nutanix SNMP MIB file that is used by your network management
system. Until the MIB file is updated, SNMP queries might return erroneous data or data of the wrong
type. To download the latest SNMP MIB file, do the following:
a.
In the web console, click the gear icon , and then click SNMP.
b. In the SNMP Configuration dialog box, click Download MIB, and then save the MIB file to your
local hard drive.
2. If you are upgrading from a version of NOS lower than 3.5, remove old Nutanix SSH keys.
nutanix@cvm$ ncli cluster remove-all-public-keys
3. If the timezone on the Controller VMs was changed from the default before the upgrade, reset the
timezone.
ncli> cluster set-timezone timezone=cluster_timezone
Replace cluster_timezone with the timezone of the cluster (for example, America/Los_Angeles, Europe/
London, Asia/Tokyo).
Restart all Controller VMs in the cluster after changing the timezone. Restart the Controller VM in a
series, waiting until one has finished starting before proceeding to the next.
b.
In the wheel icon pull-down list of the main menu, select Alert Email Contacts.
c. If no email address is listed in Email Alert Contacts and the customer wants to receive email alerts,
click Add, enter one or more addresses, and click Close.
d.
In the wheel icon pull-down list of the main menu, select Email Alert Services.
5. If the customer wants to receive support email messages in addition to alerts, add email addresses.
a.
In the wheel icon pull-down list of the main menu, select Pulse.
b. Enter customer email addresses in the Email Recipients field and click Save.
6. If you deleted schedules from any existing configured protection domains, create new schedules.
3. Verify that the following parameters are set to the expected values.
b. (Hardware) vCPUs: 8
If any of these parameters are set to different values, change them. The Controller VM must be shut
down to change some of the parameters.
b. Resume replication.
nutanix@cvm$ ncli protection-domain resume-replication name="pd_name" \
replication-ids="operation_id"
If the version returned is other than 2.0-5dfbc550, update the VAAI plugin by issuing the following
command.
nutanix@cvm$ for i in `hostips`; do echo $i; scp \
~/data/installer/*5.0*/pkg/nfs-vaai-plugin.vib root@$i:/var/tmp/; \
echo "about to install"; ssh root@$i "esxcli software vib install -v \
/var/tmp/nfs-vaai-plugin.vib -f"; done
Warning: To avoid cluster service interruption, restart one host at a time and wait for the
Controller VM to start before proceeding to the next host.
Replace admin_username with the username of the account that has administrative access to the
Windows AD domain.
Enter the domain administrator password when prompted.
Platform Default
The following table show the minimum amount of memory required for the Controller VM on each node for
platforms that do not follow the default. For the workload translation into models, see Platform Workload
Translation (G5/Broadwell) on page 15.
Note: To calculate the number of vCPUs for your model, use the number of physical cores per
socket in your model. The minimum number of vCPUS your Controller VM can have is eight and
the maximum number is 12.
If your CPU has less than eight logical cores, allocate a maximum of 75 percent of the cores of a
single CPU to the Controller VM. For example, if your CPU has 6 cores, allocate 4 vCPUs.
The following table maps workload types to the corresponding Nutanix and Lenovo models.
Note: Nutanix Engineering has determined that memory requirements for each Controller VM in
your cluster are likely to increase for subsequent releases. Nutanix recommends that you plan to
upgrade memory.
Platform Default
The following tables show the minimum amount of memory and vCPU requirements and recommendations
for the Controller VM on each node for platforms that do not follow the default.
Nutanix Platforms
Dell Platforms
XC730xd-24 32 16 8
XC6320-6AF
XC630-10AF
Lenovo Platforms
HX-3500 24 8
HX-5500
HX-7500