Escolar Documentos
Profissional Documentos
Cultura Documentos
Acropolis 5.0
Contents
Copyright.................................................................................................................. 7
License....................................................................................................................................... 7
Conventions............................................................................................................................... 7
Default Cluster Credentials........................................................................................................7
Version....................................................................................................................................... 8
Module 5: Networking........................................................................ 65
Exercises..................................................................................................................................66
Networking.....................................................................................................................66
Module 6: VM Management............................................................... 69
Exercises..................................................................................................................................70
Creating a VM...............................................................................................................70
Exercises..................................................................................................................................84
Enabling NGT............................................................................................................... 84
Exercises..................................................................................................................................88
VM Network Management............................................................................................ 88
5
Exercises................................................................................................................................141
Hypervisor Integration................................................................................................. 141
6
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
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: January 2, 2017 (2017-01-02 19:02:00 GMT-5)
8 | Copyright
Module 1
Introducing the Nutanix Enterprise Cloud Platform
Topics: This module describes Nutanix Acropolis and Nutanix Prism,
which comprise the Nutanix product family. Nutanix Acropolis
• Exercises consists of Distributed Storage Fabric (DSF), App Mobility Fabric
(AMF), and the native Nutanix hypervisor, AHV. Additionally,
this module introduces Prism Element and Prism Central and
describes their functionality. Finally, this module introduces the
Nutanix cluster components.
Duration
Objectives
One-Click Upgrade
In this exercise, you perform a one-click upgrade of the NCC utility on your lab cluster. If time allows,
your instructor will also have you perform a one-click upgrade of the AOS on your lab cluster.
In this exercise, you perform a one-click upgrade of the NCC utility on your lab cluster.
1. Open a web browser. Into the browser’s URL bar, enter your assigned cluster’s external virtual IP
address provided to you on your exercise handout. If you receive a certificate warning window,
click through to accept the self-signed certificate so that you get to the Prism login window.
4. In the Upgrade Software window, click the NCC link in the row of links along the top of the
window.
| 11
Figure: NCC Link
5. At this point, your cluster will attempt to contact the software update server at Nutanix to see if
there is an update available for your cluster’s NCC utility. On your exercise handout, write down
the version number of NCC that your cluster is running. In the following example, the cluster is
running NCC version 2.2.5.
6. What you do next depends on your cluster’s Internet connectivity. If your cluster can contact the
software update server at Nutanix, you would see the most current version of NCC available
for download/update after a few seconds. At that point, you could simply select that version
and proceed. On the other hand, if your cluster cannot contact the Nutanix software update
server, you will have to perform a manual upload of the current NCC binary update file and its
corresponding JSON descriptor file to your cluster before performing the update. This second
option, performing a manual upgrade, is what you will do in this exercise. To begin, click upload
the NCC binary to upload the NCC binary.
| 13
Figure: Click on the Upload the NCC Binary Link
7. When you click on the upload the NCC binary link, two buttons appear. Click the first button
(labeled as button #1 in the following image) to select the NCC upgrade JSON metadata file from
your local computer, which you have previously downloaded from the Nutanix software update
web page.
8. Click the second button (labeled as button #2 in the following image). This button enables you to
select the NCC update binary file, which you have also previously downloaded from the Nutanix
software update web page. In this exercise, the location of both of these files will either be
provided to you by your instructor or will be on the exercise handout sheet.
9. Click Upload Now to upload these files to your cluster. Your files would have automatically been
uploaded if your cluster were connected to the Internet.
| 15
Figure: Upload the Files to the Your Cluster
10. Wait for the NCC files to upload to your cluster. As the files upload, a message and progress bar
appear to indicate that the upload is in progress.
11. When the update files have successfully uploaded to your cluster, click Upgrade.
| 17
Figure: Click the Upgrade Button
12. Click Yes to confirm the update to the new version of NCC. Although the NCC update completes
in a short period of time, you will most likely see a progress bar.
| 19
Figure: Close the Window
14. Using the PuTTY client on your desktop, log in to your assigned cluster using the cluster external
virtual IP address in your exercise handout, accepting any security alert warnings that may pop
up. For the login credentials, enter nutanix for the user and use the password specified in your
exercise handout.
15. Verify the version of NCC from the command line by entering the following command (notice the
double dash characters): ncc --version
16. Check the version of NCC on which your cluster is now running. Is it different from the version
number you recorded earlier? In the following screen, you can see the cluster's NCC has been
updated to version 2.2.8.
In this task, you perform a one-click upgrade of the AOS on your assigned lab cluster. The
exercise begins with the assumption that you are logged into a desktop that has access to your lab
environment.
1. If you do not have a browser window open and logged into your assigned cluster’s Prism UI,
you need to open a web browser from your assigned desktop and enter your assigned cluster’s
external virtual IP address provided to you on your exercise handout into the browser’s URL
bar. If you receive any sort of certificate warning window, click through to accept the self-signed
certificate so that you get to the cluster login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
| 21
Figure: Login Admin
4. In the Upgrade Software window, click the Acropolis link in the row of links along the top of the
window.
5. At this point, your cluster will attempt to contact the software update server at Nutanix to see
if there is an AOS update available. Make a note of the AOS version number your cluster is
running. In the following screen, you can see that the example cluster was running AOS version
4.7.
My cluster's version of AOS is:
| 23
Figure: Acropolis Version
6. You will perform a manual upgrade in which your cluster does not require Internet connectivity. To
begin, find the blue link as shown in the following screen.
7. Click on the upload the Acropolis base software binary link to upload the Acropolis base
software binary. You are presented with two buttons. The first (labeled in the following image
as button #1) lets you select the AOS upgrade JSON metadata file from your local computer
(which you have previously downloaded from the Nutanix software update web page). The
second (labeled in the following image at button #2) lets you select the AOS update binary file
(which you have also previously downloaded from the Nutanix software update web page). In this
exercise, the location of both of these files will be provided to you by your instructor or will be on
the exercise handout.
| 25
Figure: Upgrade JSON and AOS
8. After you have selected the AOS update JSON and binary files (shown in the following screen),
click the Upload Now button to upload these files to your cluster. This step would have been
automatically performed if your cluster were connected to the Internet.
9. After you have clicked the Upload Now button, wait for the AOS files to be uploaded to your
cluster. As the files are uploaded, a message and a progress bar appear.
| 27
Figure: Upload Now Progress
10. When the update files have successfully been uploaded to your cluster, click the Upgrade button,
and then select Upgrade Now in the pop-up menu.
Note: As this update takes some time (45 minutes or more), your instructor may decide to
proceed with the class while you wait for the update to complete.
11. Click Yes to confirm the update to the new version of AOS. A progress bar appears as the update
progresses.
| 29
Figure: Confirm Upgrade
12. You can also click the Open link (circled in the previous screen) to expand the dialog box and get
additional per-node details about the update’s progress.
13. As part of updating AOS, each CVM will be rebooted in turn. At some point, the CVM you have
been accessing via your web browser will reboot and you will lose the connection in your browser
window. When that happens, wait a few minutes and reconnect after the CVM has rebooted.
Note: CVM reboots typically take 5-7 minutes each.
14. When you log in to the cluster again in your web browser, you are asked whether you want to
enable Pulse notifications. Click the No Thanks button.
Figure: No Thanks
| 31
15. Verify the version of AOS by clicking on the Admin menu in the upper right corner of your
browser window and select About Nutanix.
| 33
34 | Introducing the Nutanix Enterprise Cloud Platform
Module 2
Administering the Nutanix Cluster
Topics: In this module, you learn how to install a Nutanix block, including
rack mounting. You learn to determine the power and network
• Exercises requirements for your block, and how Nutanix assigns a name to
each node in a block according to product type.
Objectives
Installation Exercise
In this exercise, you use your course manual and/or online documentation to review the
requirements for installing a Nutanix cluster.
In this exercise, you:
• Review network and environment.
• Review node naming.
Answer the following:
2. Given 6 nodes in two blocks, how many IP addresses are required? ____________
3. Given 5 nodes in two blocks, how many subnets are required for the proper communication of the
Controller VMs and the hypervisor? _______________
4. By default, what TCP port must be open to use Prism Central in an AHV hypervisor cluster?
_____________
1. Refer to the following picture. Identify the power buttons for Node A, B, C, and D.
| 37
38 | Administering the Nutanix Cluster
Module 3
Configuring the Cluster
Topics: This module covers how to configure a Nutanix cluster, including
how to set up a name server and configure network connections.
• Exercises You learn how to set up filesystem whitelists as well as NTP,
SMTP, and SNMP servers. The module also goes over how
to change the language settings in Prism. There is a thorough
discussion of how Nutanix provides cluster security. You learn
how to configure user authentication, install an SSL Certificate,
and control access to the cluster. Finally, this module explains the
Data-at-Rest Encryption schema used to protect data stored on
disks and how to configure it.
Objectives
In this exercise, you configure an NTP time server for your Nutanix cluster.
1. If you are not already logged into your cluster’s Prism interface, do so now.
3. In the NTP Servers window, enter the IP address of the NTP server specified on your exercise
handout. Then click the Add button.
| 41
42 | Configuring the Cluster
Module 4
User Interfaces
Topics: In this module, you learn how to manage Nutanix clusters using
the web console (Prism Element). You learn how to use the
• Exercises various menus to monitor the health of your clusters and how
to respond to events and alerts, as well as how to configure
and manage multiple clusters using Prism Central. This module
covers how to register clusters with Prism Central and how to
use the Nutanix Command Line Interface (nCLI) to perform other
administrative operations. This module also covers the Nutanix
REST API and how to use Nutanix PowerShell cmdlets to help
manage clusters.
Objectives
In this exercise, you familiarize yourself with Prism Element, the Nutanix management GUI.
In this exercise, you perform the following tasks:
• Connect to Prism.
• Explore Prism features.
• Explore Prism views.
In this task, you register a cluster with Prism Central.
1. From a browser on your student desktop, refer to the exercise handout and enter the IP address
of your cluster virtual IP or a Controller VM.
2. In the login screen, enter the credentials as provided in your exercise handout sheet.
3. Select the Admin icon on the upper right, and then click the About Nutanix link.
44 | User Interfaces
Figure: About Nutanix
1. Select the Health page from the dashboard selection pull-down menu.
| 45
Figure: Select Health Page
46 | User Interfaces
If the Health Page Tutorial does not automatically launch, it can be found under the ? (Help)
menu in the upper right.
| 47
Figure: Select VM Dashboard
4. According to the VM Overview page, how many VMs are in the cluster? ________
48 | User Interfaces
Figure: Select Table View
6. Why are there no VMs listed here, when the Overview page said that there were VMs in the
cluster? _____________________________________________
| 49
Figure: Pull-Down Menu
2. Also, explore the features available under the gear icon.
50 | User Interfaces
Figure: Gear Icon
3. Explore the functions available under the Admin menu.
| 51
Figure: Admin Menu
4. Enter some text in the Search box and click the magnifying glass icon.
2. When you have a familiarity with the Prism management interface, return to the Home page by
clicking on the large N in the middle of the page.
52 | User Interfaces
Figure: N Box
nCLI Exercise
In this exercise, you explore Nutanix Command Line Interface (nCLI), learn how to obtain help inside
nCLI, and how to use nCLI to read and create objects in the cluster.
In this exercise, you:
• Use basic nCLI commands and get help.
• Perform read operations.
• Build a container.
In this task, you access the nCLI shell and perform some basic commands.
1. Open PuTTY and connect to your training cluster IP address using the credentials supplied on
your exercise handout.
2. From the command prompt, display a list of the SSD disks in the cluster by entering the
command ncli disk list | grep SSD.
3. From the command prompt, display a list of the HDD disks in the cluster by entering the
command ncli disk list | grep HDD.
4. From the command prompt, enter the nCLI shell by entering the command ncli .
| 53
Figure: nCLI Shell
6. To display help for the datastore entity, enter the command datastore help.
7. To get help on the container entity, use the command container help.
8. What command would you enter to get nCLI help for user accounts?
9. Based on the previous step, what command would you enter to list user accounts?
54 | User Interfaces
Figure: Exit the nCLI Shell
nCLI (contd)
In this task, you use the nCLI shell to answer the following questions.
2. List all the storage pools in the cluster by entering the following command storagepool list.
How many storage pools does the cluster have?
3. List all the storage containers in the cluster by entering the command container list. How many
storage containers does the cluster have?
5. List all virtual machines on the cluster by entering the command virtualmachine list. How many
virtual machines are there in the cluster?
6. Display information about the cluster by entering the command cluster info.
1. What software version is running on the cluster?
2. How many nodes and blocks are in the cluster?
3. What is the cluster time zone?
| 55
Figure: Exit nCLI Shell
8. You can combine bash shell commands and nCLI commands to filter and format nCLI output. To
count the number of SSDs in the cluster, enter the command ncli disk list | grep SSD | wc –
l.
nCLI (contd)
In this task, you create and delete a storage container using nCLI.
1. From the command prompt, enter the nCLI shell by entering the command ncli.
56 | User Interfaces
Figure: nCLI Shell
2. To list the parameters for the container create command, enter the command container
create. Then press the Tab key.
3. To get help with the container create command, enter the following command: container
create help
4. The name of the storage pool is a required argument to the container create command. Use the
storagepool list command and note the unique name of the default-storage-pool-nnnnn on
the cluster using the command storagepool list.
| 57
5. Create a container named cli-container1 by entering the command container create
name=”cli-container1” sp-name=“default-storage-pool-nnnnn”.
6. Use the same container create command to create a second container named cli-container2
on the default storage pool.
7. Verify that these two containers were created by using the command container list.
9. Select the Storage tab in the Prism interface, then the Table link, and then click the Storage
Container button. Verify that the two containers cli-container1 and cli-container2 were created.
10. Delete cli-container1 by highlighting cli-container1 and selecting the Delete link.
58 | User Interfaces
Figure: Delete Container
12. Verify that the cli-container1 has been deleted, and that the cli-container2 remains.
| 59
Figure: Confirm Container Remains
15. Use the container list command to verify that both cli-container1 and cli-container2 have
been deleted from the cluster by issuing the container list name=”cli-container1” and
container list name=”cli-container2” commands.
Add User
In this exercise, you add a local (i.e. non-domain) user account to your Nutanix cluster. This user can
then log in and perform cluster tasks based on the level of access they have been granted.
In this exercise, you perform the following tasks:
• Add a user to your cluster.
• Test the new user by logging into their account.
1. If you are not already logged into your cluster’s Prism interface, do so now.
60 | User Interfaces
Figure: User Management
| 61
5. Click Save.
6. Log out of the Prism interface by clicking the Admin menu and select Sign Out.
62 | User Interfaces
Figure: Sign Out
7. Log in to the Prism interface using the credentials of the account you just created earlier.
8. After you have logged back in, click the gear icon and see if you can see or access User
Management. What did you notice? Are you allowed to administer user accounts?
| 63
Figure: Access User Management
64 | User Interfaces
Module 5
Networking
Topics: In this module, you learn about network management in Acropolis,
including how Acropolis uses Open vSwitch (OVS) for network
• Exercises management. Additionally, you learn how to configure bridges,
bonds, and VLANs so that you can change the default network
configuration based on networking best practices. You also learn
how to change the IP address, netmask, and the default gateway
of the nodes during the imaging process.
Objectives
Networking
In this exercise, you apply the Nutanix recommended configuration in which 10g and 1g interfaces
are separated and added to unique bonds. This ensures that Controller VM and user VM traffic
remain separated with access to like infrastructure in the event of a link failure. In this exercise, you
create a new bridge on each AHV host and create bonds.
In this exercise, you apply the Nutanix recommended configuration in which 10g and 1g interfaces
are separated and added to unique bonds. This ensures that Controller VM and user VM traffic
remain separated with access to like infrastructure in the event of a link failure. Note: It is a Nutanix
Best Practice to manage the AHV environment through Prism or by using SSH to access the
Controller VM. In your environment, avoid connecting directly to the AHV hosts unless you have
specific configuration tasks that require it.
In this exercise, you perform the following tasks:
• Create a new bridge on each AHV host.
• Create bonds.
In this task, you create a new bridge on each AHV host where, in a subsequent task, you will move
the 1GbE NICs.
2. List the existing bridges for each Nutanix node in the cluster. nutanix@cvm$ allssh ssh
root@192.168.5.1 "ovs-vsctl show"
You should see a single bridge named “br0”.
3. To view additional network interface information, type the following command: nutanix@cvm$
allssh manage_ovs show_interfaces
4. Create bridge “br1” on each Acropolis host in the cluster. nutanix@cvm$ allssh ssh
root@192.168.5.1 "ovs-vsctl add-br br1"
In this task, you create a new bond and move the 1GbE NICs on your clusters nodes to that bond.
66 | Networking
nutanix@cvm$ allssh manage_ovs --bridge_name br0 --bond_name bond0 --interfaces 10g
update_uplinks
2. Verify that this operation has succeeded using the following command. nutanix@cvm$ allssh
manage_ovs --bridge_name br0 show_uplinks
You should see the following response: Uplink ports: bond0 Uplink ifaces: eth3 eth2
Note: The actual interface names displayed will depend on your host NIC
configuration. You should see all 10GbE interfaces listed.
3. Add only the 1GbE uplinks to br1 in the Controller VM using the 1g interface shortcut.
nutanix@cvm$ allssh manage_ovs --bridge_name br1 --bond_name bond1 --interfaces 1g
update_uplinks
4. Verify that this operation has succeeded using the following command. nutanix@cvm$ allssh
manage_ovs --bridge_name br1 show_uplinks
You should see the following response: Uplink ports: bond1 Uplink ifaces: eth0 eth1
Note: The actual interface names displayed will depend on your host NIC
configuration. You should see all 1GbE interfaces listed.
2. Verify connectivity to the cluster using the following command where CVM-IP is the IP address of
one of the Controller VMs in your cluster: ssh nutanix@CVM-IP ping CVM-IP
| 67
68 | Networking
Module 6
VM Management
Topics: In this module, you learn about VM management in Acropolis.
You learn how to create a guest VM in Acropolis and how to use
• Exercises the Nutanix Image Service to import and then apply a new image
• Exercises to a guest VM. You also learn how to create a Windows VM.
• Exercises Next, you install Nutanix guest tools (NGT), a software bundle
that enables the advanced functionality provided by Nutanix.
After you have deployed NGT, you can use the self-service
restore feature to do a self-service recovery from the Nutanix data
protection snapshots. You then learn to customize VMs using
Cloud-Init and Sysprep. Finally, this module illustrates important
VM management terminology: MapReduce Tiering, live migration,
High Availability, and Data Path Redundancy.
Objectives
Creating a VM
In these exercises, you create a Windows VM. First, you create three networks: one unmanaged
VLAN network, one managed VLAN network, and an unmanaged network on the native VLAN
(VLAN 0). Then you upload ISO images, create a VM, power on the VM, and install Windows.
In this exercise, you create three networks: one unmanaged VLAN network, one managed VLAN
network, and an unmanaged network on the native VLAN (VLAN 0).
In this exercise, you:
• Create an unmanaged network.
• Create a managed network.
• Create VLAN 0.
In this task, you create an unmanaged network.
70 | VM Management
3. In the Network Configuration dialog box, select the +Create Network button.
4. In the Create Network dialog box, fill out the fields as follows:
• Name: Unmanaged Network
• VLAN ID: <see your exercise handout>
• Enable IP Address Management: NOT checked
6. Click the Close button to exit the Create Network dialog box.
| 71
Create Managed and Unmanaged Networks (contd)
1. From the Prism interface gear pull-down menu, select Network Configuration.
2. In the Network Configuration dialog box, select the +Create Network button.
3. In the Create Network dialog box, fill out the fields as follows:
• Name: Managed Network
• VLAN ID: <see your exercise handout>
• Enable IP Address Management: CHECKED
• Network IP Address/Prefix Length: <see your exercise handout>
• Gateway IP Address: <see your exercise handout>
5. In the Add IP Pool dialog box, fill out the fields as follows:
• Start Address: <see your exercise handout>
72 | VM Management
• End Address: <see your exercise handout>
Using the first two tasks in this exercise as your guide, create a third network named VLAN 0 as
an unmanaged network.
| 73
Creating a Windows VM Exercise
In this exercise, you create a Windows VM, including installing Virt-IO drivers using the AHV image
service. You will use the VM created in this exercise as a template in other exercises, where you will
clone it for use in each respective exercise. This way you always have the original VM image in case
something goes wrong.
In this exercise, you perform several tasks. You:
• Upload ISO images.
• Create a VM.
• Power on the VM and install Windows.
In this task, you upload the Windows and Nutanix Virt-IO ISO images. Note: If you have previously
uploaded the Windows ISO image, you may skip this task, and move on to the next task.
74 | VM Management
3. In the Create Storage Container dialog box, create a container named ISOs.
| 75
Figure: Image Configuration
2. In the Image Configuration dialog box, click the +Upload Image button.
76 | VM Management
Figure: Create Image Completed Fields
4. Click the Choose File button.
5. Select the Windows ISO file from the location specified on your exercise handout.
6. Click the Save button.
Note: The Windows ISO upload may take a few minutes to complete.
| 77
Figure: Upload Nutanix Virtual I/O Drivers
4. When the image has completed uploading, click the Close button in the Image Configuration
dialog box.
In this task, you create a Windows VM and connect it to the unmanaged network.
78 | VM Management
Figure: Select VM
| 79
Figure: Complete Create VM Dialog Box
3. Complete the Create VM dialog box with the following information. If a field is not specified, leave
it with the default value.
1. Name: Windows-nnn where nnn is your training cluster number
2. VCPU(s): 1
3. Number of Cores per VCPU: 2
4. Memory: 4
80 | VM Management
Figure: Add Disk Dialog Box
In this task, you power on the new VM, and install the Windows Server 2012 operating system.
4. After the machine powers on, select the Launch Console link.
| 81
Figure: Launch Console
5. In the console of the Windows VM, install the Windows Server 2012 R2 Standard (Server with a
GUI)
1. In the Windows Setup dialog, click the Next button and then click the Install now button.
2. In the Windows Setup dialog, highlight Windows Server 2012 R2 Standard (Server with a
GUI), then click the Next button.
3. Accept the license terms and click the Next button.
4. Select Custom Install Windows only (advanced).
82 | VM Management
Figure: Click Browse
7. Navigate to the E: Nutanix VirtIO drive, Windows Server 2012 R2 folder, and click the OK
button.
| 83
Figure: Select Available Driver
9. Select the 40GB Drive 0 and then click the Next button.
Exercises
Enabling NGT
In this exercise, you enable Nutanix Guest Tools (NGT) in a VM.
84 | VM Management
Enabling NGT
1. If you are not already logged into your cluster’s Prism interface, do so now.
5. Click the Clone link below the table of VMs so that you are operating on a copy of the original
VM.
6. In the Clone VM window, enter NGT Test VM in the Name field. Leave all other fields at their
default values.
10. Scroll down in the Update VM window until you get to the VM’s CDROM drive(s). For any
CDROM drive present, click the up-arrow eject button to eject any media still possibly in the drive.
| 85
Figure: Eject Button
12. Click the Manage NGT link below the table of VMs.
86 | VM Management
13. In the Manage Nutanix Guest Tools (NGT) window, click the Enable Nutanix Guest Tools check
box.
14. In the same window, make sure both of the following check boxes are selected:
• Self Service Restore (SSR)
• Volume Snapshot Service (VSS)
Figure: VSS
16. Click the Power on link in the row of links below the table of VMs.
17. After the VM has powered on, click the Launch Console link in the row of links below the table of
VMs.
18. Click the ctl-alt-del icon in the row of icons in the upper left corner of the VM Console window.
19. Log in to the Windows VM as the user administrator with the password nutanix/4u.
| 87
20. In the Windows VM, bring up a Windows File Explorer window by clicking the folder icon in the
taskbar.
23. In the Nutanix Guest Tools Setup window, click the check box to agree to the license terms and
then click the Install button.
24. The installation of the Nutanix Guest Tools takes a minute or two. When the installation has
completed, click the Close button.
Exercises
VM Network Management
In these exercises, you perform VM network management tasks. First, you upload a CentOS ISO
to a container called ISO and provision a CentOS VM. Then you clone your Windows VM on one
network and move it to another network.
88 | VM Management
Provisioning a CentOS VM Exercise
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout. If you receive any sort of certificate
warning window(s), click through to accept the self-signed certificate so that you get to the cluster
login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
| 89
Figure: Image Configuration
90 | VM Management
Figure: Create Image
Fill in these Create Image window fields with the following values:
• NAME: CentOS_ISO
• IMAGE TYPE: ISO
• CONTAINER: default-container-<NNNNN>
7. Click Save.
8. Consult with your instructor to find out where the ISO repository resides.
In this task, you create a VM and install CentOS 7. This task begins with the assumption that you are
logged into your lab environment.
1. Select VM dashboard and click the Table tab. Click the +Create VM button.
| 91
Figure: Create VM
2. Scroll down the window and click the pencil icon next to the CD-ROM to select the CentOS ISO
for OS installation.
Figure: Create VM
92 | VM Management
3. Select CentOS_ISO for the CDROM.
Fill in these Update Disk window fields with the following values:
• TYPE: CDROM
• OPERATION: Clone from Image Service
• IMAGE: CentOS_ISO
4. Click Update.
| 93
Figure: Add New Disk
Fill in these Add New Disk window fields with the following values:
• TYPE: DISK
• OPERATION: Allocate on Storage Container
• BUS TYPE: SCSI
• STORAGE CONTAINER: default-container-<NNNNN>
• SIZE (GB): 40
6. Click Add.
94 | VM Management
Figure: Add New NIC
9. Click Save.
10. At the VM dashboard, select the Table tab. Select the CentOS VM and click Power on. Click
Launch Console.
| 95
Figure: Installation Destination
96 | VM Management
Figure: Begin Installation
15. Click ROOT PASSWORD to configure the password for root user.
17. Click USER CREATION. Create a user named student and set his password as nutanix/4u.
| 97
Figure: User Creation
20. At the VM dashboard, select the Table tab. Select the CentOS VM and click Power Off.
98 | VM Management
Figure: Update VM
24. Select the CentOS VM and click Power On. At the CentOS VM console, log in as student.
25. At the command prompt, run the ip addr sh command to display the IP address on the VM NIC.
| 99
Figure: Run ipaddr shr
The CentOS VM does not receive an IP address from the DHCP address pool. This is an
expected outcome because CentOS 7 minimal has its network adapter disabled by default.
26. Run the nmcli d command at the command prompt to confirm eth0 is disconnected.
27. Run the nmtui command to launch the network management user interface.
28. Enter Edit a connection and navigate to <Edit …>. Press Enter.
100 | VM Management
Figure: Edit Connection
29. Press the Tab key to move the cursor and select Automatically connect.
30. Press the Tab key to move the cursor to OK and press Enter.
31. At the command prompt, run the service network restart command.
32. At the command prompt, run the ip addr sh command to verify that the VM has an IP address.
| 101
Figure: Run ip addr sh
33. At the command prompt, run the ping 10.30.0.1 command to verify connectivity to the default
gateway.
Figure: Ping IP
In this exercise, you clone your Windows VM on one network and move it to another network. This
exercise assumes you have previously created a Windows VM. If you have not yet done so, please
complete the Create a Windows VM exercise now.
In this exercise. you perform the following tasks:
• Observe a VM on an unmanaged network
• Move the VM to a managed network
In this task, you observe the behavior of a VM attached to an unmanaged network.
4. In the row of links below the table of VMs, select the Clone link.
5. In the Name text field of the Clone VM window, enter Network VM Test.
7. Click the Power On link in the row of links below the table of VMs.
8. Open a console window to the Windows VM you cloned in the previous steps.
102 | VM Management
Figure: Ctrl Alt Del icon
10. Right-click on the network icon in the system tray and select Open Network and Sharing
Center.
12. In the Ethernet Status dialog box, click the Properties button.
13. In the Ethernet Properties dialog box, highlight Internet Protocol Version 4 (TCP/IPv4) and click
the Properties button.
| 103
Figure: Ethernet Properties
104 | VM Management
Figure: Obtain IP Addresses
15. Cancel and close all Network and Sharing Center dialog boxes.
19. What does this tell you about the state of DHCP services available to the Windows VM?
___________________________________________________
In this task, you add and remove virtual NICs attached to the managed and unmanaged networks.
1. On the Prism management interface for your cluster, select the VM dashboard. Select the Table
view.
2. Highlight the Windows VM and select the update link (pencil icon).
3. In the Update VM dialog box, scroll down to the Network Adapters (NIC) area and click the +Add
New NIC link.
| 105
Figure: Add New NIC
4. In the Create NIC dialog box, select Managed Network from the VLAN Name pull down list.
Then click the Add button.
5. When complete, click the Save button in the Update VM dialog box.
6. In the VM Table view of the Prism management interface, hover your mouse over the IP address
cell for the Windows VM.
106 | VM Management
Figure: Mouse Over IP
8. Return to the remote console of the Windows VM and issue the ipconfig command in the
Command Prompt window.
10. What are the IPv4 addresses reported from the ipconfig command?
___________________________________________________________
12. Highlight the Windows VM and click the update link (pencil icon).
13. In the Update VM dialog box, scroll down to the Network Adapters (NIC) area, and delete the
virtual NIC on the unmanaged network by clicking the X adjacent to it.
14. When asked, “Are you sure you want to delete the NIC?”, click the Yes button.
15. When the operation completes, click the Save button in the Update VM dialog box.
16. When the operation completes, hover over the IP address cell for the Windows VM.
17. Return to the command prompt on the Windows VM and issue the ipconfig command.
a. Does the information returned from the ipconfig command agree with what was shown in the
Prism management interface? __________________________________
| 107
108 | VM Management
Module 7
Health Monitoring and Alerts
Topics: In this module, you learn how to use the Health Dashboard
to monitor cluster health and how to configure health checks
• Exercises for various components. You also learn how to monitor cluster
• Exercises performance and how to handle system alerts and events. In
addition, this module covers how to customize email alerts.
Objectives
Performance Monitoring
In this exercise, you use the Analysis dashboard to monitor write IOPS on a performance chart. You
to configure a performance chart using the Analysis dashboard. By generating write I/Os from a
CentOS VM, you see a real time performance graph on the performance chart.
In this exercise, you begin by deploying a CentOS VM on your cluster. You then set up a
performance chart on the Prism web console for monitoring VM disk write I/O. Finally, you configure
the VM to write zero to its local disk and monitor its write IOPS on the performance chart.
In this task, you create a CentOS VM from the Prism web console. The exercise begins with the
assumption that you are logged into your lab environment.
Note: Skip this task if a CentOS VM has been provisioned in the cluster.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout. If you receive any sort of certificate
warning window(s), click through to accept the self-signed certificate so that you get to the cluster
login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
3. From the main menu, select VM dashboard and then select Table tab. If a CentOS VM already
exists, skip the remaining steps in the task.
In this task, you create a performance chart to monitor VM disk I/O. This exercise begins with the
assumption that you are logged into your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout. If you receive any sort of certificate
warning window(s), click through to accept the self-signed certificate so that you get to the cluster
login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
3. Select Analysis dashboard and click New Entity Chart where an entity can be a host, a VM, a
container, and so on.
4. Fill in the New Entity Chart fields with the following values:
| 111
1. Chart title: VM disk write I/O
2. Entity type: Virtual Machine
3. Entity: CentOS VM Name
4. Metric: Storage Controller IOPS-Write
5. Click Save.
In this task, you configure the CentOS VM to write data to its local disk using Linux command dd and
then monitor its write IOPS on the performance chart. The exercise begins with the assumption that
you are logged into your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout. If you receive any sort of certificate
warning window(s), click through to accept the self-signed certificate so that you get to the cluster
login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
| 113
dd if=/dev/zero of=/root/bigfile bs=64k count=500000 oflag=direct
This command will write 500,000 64k blocks to the root directory.
Exercises
Health Alerts
In this exercise, you manage alerts on the Alert dashboard. You begin by generating an alert
on the Alert dashboard, and then you use the Alert dashboard for alert viewing, filtering,
acknowledgement, and resolution.
In this exercise, you use the Alert dashboard to manage alerts. You generate an alert and
subsequently view the alert, create a filter, acknowledge the alert, and resolve it.
In this task, you generate an alert by stopping the Stargate service. This exercise begins with the
assumption that you are logged into your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout into the browser’s URL bar. If you receive
any sort of certificate warning window(s), click through to accept the self-signed certificate so that
you get to the cluster login.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
3. PuTTY to one of the CVM IP addresses and run genesis stop stargate on nCLI.
4. Confirm that the Stargate service is down by running the cluster status command on nCLI.
| 115
Figure: Confirm Stargate Service is Down
5. PuTTY to the underlying AHV host by running the ssh root@192.168.5.1 command on nCLI.
6. Run the route command to display the routing table. Confirm that the host route 192.168.5.2/32
appears in the routing table.
7. Select the Alert dashboard and set the filter to the Warning level. It may take several minutes for
the Stargate alert to appear.
9. PuTTY to the same CVM and run the genesis restart stargate command on nCLI. Confirm that
the Stargate service is UP by running the cluster status command. It may take a few minutes
for the Stargate service to come back up.
| 117
Figure: Stargate Service Up
10. PuTTY to the underlying AHV host by running ssh root@192.168.5.1 on nCLI.
11. Run the route command on nCLI. Confirm that the host route 192.168.5.2/32 has been deleted
from the routing table.
12. Select the Stargate alert on the Alert dashboard and click the Resolved button.
| 119
120 | Health Monitoring and Alerts
Module 8
Distributed Storage Fabric
Topics: This module covers how Nutanix manages storage to protect
data and optimize cluster capacity. It explains how to use the
• Exercises Storage Dashboard to monitor storage space for performance
• Exercises and reliability to prevent problems. You learn about compression,
erasure coding, and deduplication to get the most out of existing
storage capacity. This module also covers how to create a storage
container and a storage pool. You also learn about in-place
hypervisor conversion, hypervisor integration with existing storage,
and networking, including vLANs.
Objectives
Storage
In this exercise, you add two additional drives to a VM populating each of the two drives with a large
text file. You place one of the added drives onto a container with compression enabled and place the
other added drive onto a container that does not have compression enabled. You then compare the
two drives in the VM and in the Prism interface to see how their storage use compares.
Storage Exercises
In these exercises, you add two additional drives to a VM populating each of the two drives with a
large text file. You place one of the drives onto a container with compression enabled, and place the
other added drive onto a container that does not have compression enabled. You then compare the
two drives in the VM and in the Prism interface to see how their storage use compares.
This exercise consists of the following tasks:
1. Create a new container with compression enabled.
2. Add two additional virtual disks to your VM.
3. Format the new disks in Windows.
4. Create a large file in each of the VMs new virtual disks.
5. Observe the result of compression savings.
In this task, you create a new storage container with compression enabled.
1. If you are not already logged into the Prism web interface, log in to your cluster using the IP
address and login credentials provided on your exercise handout now.
3. Before you create a new container, examine the Capacity Optimization box in the lower-left
corner of the browser window. Does it indicate any savings due to compression? (It should not,
as we have not yet enabled compression on any containers).
5. In the Create Storage Container window, enter Compressed-Container in the Name text box.
| 123
Figure: Compressed Container
6. Click the Advanced Settings button. The advanced container settings are displayed.
7. Select the Compression check box, leave the Delay in Minutes field at 0 to enable compression
on write.
8. Click the Save button to complete the creation of the storage container.
Storage (contd)
In this task, you add two additional virtual disks to your VM. One of these drives will be placed
onto the uncompressed default-container while the other drive will be placed onto the compressed
container that you just created in the previous task. In a subsequent task, you populate both of these
virtual disks with a large compressible file so that you can compare them.
1. If you are not already in the VM dashboard, switch to the VM dashboard now.
| 125
Figure: Select VM Dashboard
3. Click to select the VM you are using for this exercise (your VM name will likely differ from the one
in the screens shown).
Figure: Select VM
4. If the VM is powered on, click the Power Off Actions button (below the table of VMs) and select
Power off.
5. Click the Update link in the links below the table of VMs.
| 127
Figure: Update
6. In the Update VM dialog box, click the + Add New Disk link.
7. Enter the following values into the Add Disk box (leaving all other fields at their default values):
1. Storage Container: Compressed-Container
2. Size (GiB): 10
8. Click the Add button to add this second disk to your VM.
9. Repeat the previous steps to add a second additional 10GB drive to the VM with the second
added disk placed into the default-container. Make sure you add this second drive to the default-
container.
| 129
Storage (contd)
In this task, you format the second drive in your Windows VM so that you can then populate the new
drive with a large file.
1. Click the Power on link in the row of links below the VM table.
2. When the VM has powered on, click the Launch Console link in the same row of links.
3. In the upper-right corner of the VM console window, click the ctl-alt-del link to log in to your VM.
The credentials should have been set when you created the VM. If you do not know the login
credentials, ask your instructor.
4. If it is not already running, start the Windows Server Manager by clicking Start Menu > Server
Manager.
| 131
Figure: Click File and Storage Services
6. Click Disks.
7. In the list of disks, click to select either of the two offline 10GB drives in the list.
8. Right-click the drive and select Bring Online. Click Yes in the Bring Disk Online window.
9. Bring the second 10GB disk online by repeating the previous steps.
10. Right-click the drive again, this time selecting New Volume…
11. In the New Volume Wizard… do the following in the following windows:
1. In the Before You Begin window, click Next .
2. In the Server and Disk window, click Next .
3. Click OK to confirm the Offline or Uninitialized Disk dialog box.
4. Click Next in the Size window.
5. In the Drive Letter or Folder window, note the drive letter used and then click Next. The drive
letter used is: _____
6. In the File System Settings window, click Next .
7. In the Confirmation window, click Create and wait for the drive to be formatted and brought
online.
8. Click Close.
12. Repeat the previous New Volume Wizard steps for the second 10GB virtual disk drive and note
the drive letter assigned to that disk drive here: _____
13. When you have created new volumes on the two drives, the Server Manager window should look
something like the following screen:
| 133
Figure: Server Manager
Storage (contd)
In this task, you create a large file with some compressible content in your VM.
2. Switch to the VM dashboard, click the Table tab, and select your VM.
4. Scroll down until you see the (first) CDROM device and click the pencil icon. Fill out the Update
Disk window as follows:
1. Operation: Clone from Image Service
2. Image: CubicDesignTools
3. Click the Update link.
| 135
Figure: Update Disk
5. Click the Launch Console link in the row of links below the table of VMs and log in to your VM as
administrator.
6. Open a Windows File Explorer window, double-click the CD Drive, and then double-click the
CubicDesign-tools installer.
Figure: CubicDesign
8. In the Windows File Explorer window, click the C: drive and then open the folder System tools
package. Scroll down and double-click Disk Tools.
9. In the File Generator window, make sure the File Generator tab is selected and fill out the fields
as follows (any field not mentioned should be left at its default value):
• Number of files > Generate: 1
• File size: Click the GBytes radio button and enter 5 into the number box
• File name > Output folder (text box): E:\. Note: It’s OK to leave Random name selected.
• File content: Select the Fill the files with the content radio button. Note: When you are
finished, the File Generator window should look something like the following screen.
| 137
Figure: File Generator
10. Click the Create button to create the large file. This may take up to a minute to complete.
Note: If you want, you can use a Windows File Browser window to monitor the progress of the file
creation.
11. Repeat the File Generator step, generating a large file on the second virtual disk drive you added
to your VM. When the second file has been created, you can close the File Generator window
12. When you have generated your two large files, examine the drives in the Windows File Explorer
to see how much space these files have consumed.
Storage (contd)
In this task, you enable the compression feature in your storage container, then clone the VM with
the large file and observe the result of the container’s compression.
1. Switch back to the Storage dashboard and click the Overview tab.
2. Examine the Capacity Optimization box in the lower-left corner of the browser window. Does it
show any savings due to compression?
Note: The capacity savings may take some time to realize and display in the Prism interface, but
you should be seeing some level of savings right away.
6. Look below the table of containers in the Storage Container Details box.
• Is Compression on?
• What is the value for Compression Delay?
• How much space has been saved due to compression?
• What is the current compression ratio?
7. Use the following screen to locate the values asked for in the previous step.
| 139
Figure: Locate Values
Hypervisor Integration
In this exercise, you investigate Nutanix integration with vSphere.
In this exercise, you integrate Nutanix nodes running ESXi to vCenter environment. You add
Nutanix nodes running ESXi to a vCenter and present a storage container to the hosts as their NFS
datastore.
In this task, you verify CVM network connectivity in a vSphere environment. You also present a
container to ESXi hosts. This exercise begins with the assumption that you are logged into a desktop
that has access to your lab environment.
1. `From your assigned desktop, open a web browser and enter your assigned cluster’s external
virtual IP address provided to you on your exercise handout. If you receive a certificate warning
window, click through to accept the self-signed certificate so that you get to the cluster log in as
displayed in the following screen.
Figure: Prism Login Screen
2. Log in to your cluster with the credentials provided to you in your exercise handout.
| 141
Figure: Login Admin
3. Log in to vCenter from the vSphere client on the virtual desktop. Locate your datacenter in the
vCenter.
4. If your datacenter does not have your Nutanix nodes added, right click your datacenter and select
Add Host. Otherwise, go to step 7.
5. Enter the IP address of an ESXi host (one of your Nutanix nodes) and its root credential as
provided in your exercise handout.
7. Click the + beside an ESXi host in your datacenter. A VM will appear under the host. This VM
is the CVM that has a name such as NTNX-<cluster name>-<block serial num>-<node
position>.
8. Select an ESXi host in your datacenter. On the Configuration tab, click the Storage link. You
should see a local datastore with a name such as NTNX-<block serial num>-<node position>.
No other datastore is seen by the ESXi host.
9. Click the Networking link. You should see two vSphere standard switches (VSS): vSwitch0 and
vSwitchNutanix.
| 143
Figure: Two vSphere Standard Switches
Note that the CVM has two vNICs with one vNIC sitting on vSwitch0 and another vNIC sitting on
vSwitchNutanix.
vSwitchNutanix is an internal-only vSwitch, serving communication between the CVM and a
VMKernel port (vmk1).
vSwitch0 is connected to the physical network via the host network adapters. CVMs
communicate with each other via their vSwitch0.
10. In the Prism web console, select the Storage dashboard. Go to the Storage Container tab,
select the default container and click Update.
By default, a container is unmounted on all ESXi hosts. Select Mount on all ESXi hosts and
click Save.
| 145
146 | Distributed Storage Fabric
Module 9
AHV Workload Migration
Topics: In this module, you learn about workload migration in AHV. You
learn to migrate VM disks created in ESXi to AHV.
• Exercises
Objectives
Migrating a VM
In this exercise, you use the Nutanix Image Service to migrate an ESXi VM workload to AHV. To
accomplish this task, you:
• Prepare an ESXi VM for migration
• Migrate the VM disks from ESXi and convert them to AHV format
• Create a new VM in AHV and bring the disks online
Migrating a VM Exercises
1. In the AHV cluster, create a container called VM_Migrate-<your initials>. Note: your-initials are
your name’s initials and are used so that if you are sharing a cluster with a lab partner, you each
have a uniquely named container to use for this in exercise.
1. Select Storage from the drop-down list.
2. Click Table view.
| 149
Figure: Log In to the VCenter Server
2. Click Hosts and Clusters.
3. In the Prism browser window, click the gear icon and select Filesystem Whitelist.
4. Enter the IP address of one of the cluster’s CVMs where the container you created earlier
resides, using the format of nnn.nnn.nnn.nnn/ xxx.xxx.xxx.xxx (IP address/subnet mask). The
system will not accept CIDR notation for this entry.
| 151
Figure: Enter IP Address
5. Click Add to save the entry, and then click Close to close the window.
Migrating a VM (contd)
In this task, you migrate the VM from the ESXi cluster to your AHV cluster.
5. The Add Storage dialog box is displayed. Select Network File System and click Next.
| 153
Figure: Enter Network File System Details
7. Click Finish.
9. In the Migrate Virtual Machine dialog box, select Change datastore and click Next.
10. Select the VM_Migrate-<your initials> datastore that you created earlier. Ensure that the
Compatibility shows as Validation succeeded. Click Next.
12. When the VM’s storage has completed migration to the AHV cluster storage container, power off
the VM.
Migrating a VM (contd)
In this task, you create a new VM in AHV cluster using the data from the VM you migrated in the
previous task and power the VM on to verify a successful migration.
1. If you are not already logged into Prism, log in to Prism now.
| 155
4. Enter the VM details (same as you entered in the ESXi cluster). Enter the Name, VCPU(s),
Number of cores per VCPU and Memory fields.
5. Click the Add new disk button. The Add Disk dialog box is displayed. In the Add Disk window,
enter the following:
1. TYPE: DISK.
2. From the Operation drop-down list, select Clone From ADFS File.
3. From the Bus Type drop-down list, select SCSI.
4. In the Path field, enter a forward slash and then select the container in which the VM is
migrated (e.g. VM_Migrate-<your initials>). Again enter a slash and select the VM name.
Once again, enter a slash and select the flat.vmdk file for the VM.
5. Enter the size of the disk in the Size (GIB) field.
6. Click Add.
Note: The previous screen (particularly the disk path field) will vary from your lab environment.
7. Click Save.
| 157
Figure: Click Save
8. Click the Table tab, then select the VM and click Power On.
10. Log in to the VM and check the desktop. Do you see the folder you created earlier in the
exercise?
Objectives
Acropolis Block Services (ABS) enables a Nutanix cluster to present volumes or LUNs to external
physical servers or virtual machines. Along with Nutanix web scale architecture, ABS provides a
scaled out SAN solution for enterprise IT.
In this exercise, you configure Acropolis Block Services.
These exercises requires two clusters: your own cluster and your peer cluster. Consult with your
instructor if you are unsure of who your peer cluster is.
These exercises are composed of several tasks. You:
• Configure a volume group in your own cluster.
• Enable iSCSI initiator function on a Windows 2012 VM in your peer cluster.
• Configure your volume group to permit access from your peer Windows 2012 VM.
• Investigate how vDisks in a volume group are distributed for load balancing across the CVMs in
the cluster.
In this task, you learn how to create a volume group in your own cluster. The task begins with the
assumption that you are logged into your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout into the browser’s URL bar. If you receive
any sort of certificate warning window(s), click through to accept the self-signed certificate so that
you get to the cluster login as displayed in the following screen.
160 | Services
Figure: Login Screen
2. Log in to your cluster with the credentials provided to you in your exercise handout.
| 161
Figure: Cluster Details
Enter the External Data Services IP address as provided in your exercise handout for your cluster
and click Save.
External physical servers or VMs will be pointing to this external data services IP address as their
iSCSI discovery portal.
5. Create a volume group named trainingXX-vg where XX = <01, 02, 03, … your cluster
number>.
6. Add three vdisks of 10G each to the volume group in the default-container-nnnnn.
162 | Services
Figure: Create Volume Group
7. Select Share across multiple iscsi initiators or multiple VMs. Click Save.
| 163
Figure: Click Save
In this exercise, you configure a Windows 2012 VM as an iSCSI initiator. You configure a Windows
2012 VM in your peer cluster as an iSCSI initiator. The exercise begins with the assumption that you
are logged in to your peer cluster.
1. At the VM dashboard, select the Windows 2012 VM and click Launch Console.
164 | Services
Figure: Launch Console
3. Select Microsoft iSCSI Initiator Service. Start the service and set the startup type as
automatic.
| 165
Figure: Automatic
4. At the Windows 2012 VM command prompt, enter firewall.cpl to bring up the firewall control
panel.
166 | Services
5. Click Allow an app or feature through Windows firewall.
7. At the Windows 2012 VM command prompt, enter iscsicpl.exe to bring up iSCSI control panel.
| 167
Figure: Select Configuration Tab
9. Click the Change button to modify the initiator name. Rename the initiator name to
iqn.1991-05.com.microsoft:win-1 and click OK.
In this task, you configure your volume group to permit your peer Windows 2012 VM access. You
configure your peer Windows 2012 VM to point to your external data services IP address as its
iSCSI discovery portal. You then confirm that three new disks appear in your peer Windows 2012
VM and the Windows 2012 VM iSCSI initiator name appear on your volume group. The task begins
with the assumption that you are logged in to your own cluster.
2. At the Storage page, Table view, select Volume Group and highlight the volume group you
created in task 1. Click Update.
168 | Services
Figure: Update Volume Group
3. Click the Access Control check box then click the Add New Client button.
4. Enter the peer Windows 2012 VM IP address that will connect to the iSCI. Click Add button.
| 169
Figure: Enter IP
5. In the Update Volume Group dialog box, click the Save button
6. Access the Console of your Windows 2012 VM. If it was previously closed, bring up the iSCSI
Control panel by entering the command iscsicpl.exe.
170 | Services
Figure: Bring Up iSCSI Control Panel
7. Click on the Discovery tab and click Discover Portal to add a target portal.
| 171
Figure: Add Target Portal
8. Enter your cluster External Data Services IP address and click OK.
9. Go to the Targets tab and click Refresh. It should discover three targets.
172 | Services
Figure: Discover Targets
10. Select each of the targets and click Connect. You should have the targets connected.
| 173
Figure: Connect Targets
Note their IQNs, which should be end with tgt0, tgt1, and tgt2 respectively.
11. At the Windows 2012 VM command prompt, enter diskmgmt.msc to bring up disk management
utility.
174 | Services
Figure: Bring up Disk Management
12. Go to the Storage dashboard in Prism, and select the Volume Group tab. You will see that the
Windows 2012 VM IQN appears as an iSCSI initiator being connected to the volume group.
13. Before proceeding to the next task, close out all windows you have opened in this task.
In this task, you investigate how vDisks in a volume group are distributed for load balancing across
the CVMs in the cluster.
1. The following commands are used in this investigation:
a. pithos_cli -lookup iscsi_client_params -iscsi_initiator_name=<Initiator IQN>
b. acli vg.get <volume group name>
| 175
c. vdisk_config_printer -nfs_file_name <vdisk UUID>
When a volume group is created, 32 virtual targets are created and associated with it. The existence
of a virtual target is backed by a vDisk in the volume group. A virtual target without the backing of a
vDisk does not exist.
The command in (a) demonstrates virtual target distribution among the CVMs.
The command in (b) identifies the UUID of the vDisks in the volume group.
The command in (c) associates a vDisk with a virtual target.
1. Use PuTTY to SSH into your cluster IP address and enter the command pithos_cli -lookup
iscsi_client_params -iscsi_initiator_name=<Initiator IQN>. By default, 32 virtual targets are
created for a volume group. Their target number will correspond to the LUN ID of their backing
vDisk. They are distributed across the CVMs in the cluster. For instance, 10 targets are owned by
CVM ID 2, and 11 targets are owned by CVM ID 3 and 4 respectively. These virtual targets do not
exist unless they are backed by a vDisk in the volume group.
2. To identify the vDisks and their UUIDs in the volume group, enter the command: acli vg.get
<volume group name>
176 | Services
Figure: Identity vDisks
3. To identify the virtual target that is backed by a given vDisk enter the command
vdisk_config_printer . Remember that target number corresponds to the LUN ID of the vDisk.
4. In this example, the following targets are backed by the vDisks in the volume group:
1. iqn.2010-06.com.nutanix:<volume group name>…-tgt0
2. iqn.2010-06.com.nutanix:<volume group name>…-tgt1
3. iqn.2010-06.com.nutanix:<volume group name>…-tgt2
| 177
178 | Services
Module 11
Business Continuity
Topics: Nutanix offers data protection solutions for virtual datacenters.
Nutanix provides data protection functions at the VM, file, and
• Exercises volume group level, so VMs and data remain safe in a crash-
consistent environment.
In this module, you learn the various failure scenarios. You learn
the strategies that Nutanix provides to protect your data against
such failures.
Objectives
VM High Availability
In this exercise, you observe how a Nutanix cluster responds and manages guest virtual machines
when a host fails. You manage VM High Availability and observe how enabling this feature effects
the creation of guest virtual machines.
In this exercise. you:
1. Fail a node
2. Configure VM High Availability
In this exercise, you observe how a Nutanix cluster responds and manages guest VMs when a host
fails. You manage VM high availability and observe how enabling this feature effects the creation of
guest VMs.
In this exercise, you perform the following tasks:
• Fail a node
• Configure VM high availability
In this task, you fail a node where a guest VM resides and observe the cluster response and guest
VM status.
5. Refer to the exercise handout, and using your web browser, connect to the IPMI interface for the
node on which the HA-Lab is running.
6. Refer to the exercise handout and log in to the node IPMI interface.
| 181
Figure: Power Down the VM
Note: You may need to refresh your browser page to observe the node status change to
Host is currently off.
8. Return to the browser window or tab where you connected to the Prism interface. NOTE: If you
are connected to Prism Element on the node that you powered down, you must connect your web
browser to either the Cluster IP address, another CVM, or Prism Central to manage the cluster.
11. Is this different than the host on which it was originally running?
13. Return to the browser window or tab for the host IPMI interface Click the Power On button .
14. After a few moments, observe the status of the cluster. Once the Data Resiliency Status
displays OK, continue the next step of this task.
15. Return to the Prism VM page and select the Table view.
16. Observe the status of the HA-Lab guest VM. On which node is the VM running?
17. How does this compare to the node on which it was running before and after the node was
powered down?
18. Why?
In this task, you observe the impact and benefits of the VM high availability feature.
1. Verify that you have created and powered on the HA-Lab VM from the previous task.
| 183
2. From the gear menu, select Manage VM High Availability.
3. Read the text in the Manage VM High Availability dialog box. Note that with VM high availability
disabled, AOS will not reserve and guarantee memory to start VMs in the event of a node failure.
4. Enable VM high availability by selecting the Enable HA check box. Note that AOS is now
reserving memory to guarantee that VMs will be started in the event of a node failure.
Figure: Enable HA
6. When the dialog box appears to advise that some VMs might need to be migrated, click OK.
| 185
Figure: Accept Defaults in the Clone VM Dialog Box
3. When the clone is complete and appears in the VM Table, the clone is complete. Highlight the
new clone in the VM Table view and select the Power On link.
8. When the Power On Action fails, view the task on the Prism Task page.
10. Return to the gear menu and select Manage VM High Availability.
11. In the Manage VM High Availability dialog box, clear the Enable HA check box and click the
Save button to disable VM high availability.
| 187
Figure: Disable HA
13. Highlight the last VM created (the one that failed to power on).
14. Select the Power On link and attempt to power on the VM.
Figure: Power On
16. Why?
17. What does this tell you about using the VM high availability feature?
18. Delete all instances of the HA-Lab VM you created in this task.
Data Protection
In this exercise, you learn how to configure a protection domain for protecting VMs in your cluster.
This exercise involves several tasks. You:
1. Configure a protection domain and perform VM snapshot and restore.
2. Configure a remote site for asynchronous replication.
3. Initiate failover from your cluster to the remote site.
4. Initiate failback from the remote site.
In this exercise, you configure a protection domain for protecting VMs in your cluster.
In this task, you configure a protection domain to protect your Windows 2012 VM. You then use this
protection domain for taking a snapshot of the VM. The task begins with the assumption that you are
logged into your lab environment.
There are four tasks in this exercise. In these tasks, you:
1. Configure a protection domain and perform VM snapshot and restore.
2. Configure a remote site for asynchronous replication.
3. Initiate failover from your cluster to the remote site.
4. Initiate failback from the remote site.
In this exercise, you will work with another cluster (your peer cluster). Consult with your instructor
who your peer cluster is.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout into the browser’s URL bar. If you receive
any sort of certificate warning window(s), click through to accept the self-signed certificate so that
you get to the cluster login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
3. From the main menu, select the VM dashboard. Select the Table tab and locate your Windows
2012 VM in the table.
4. If no Windows 2012 VM exists in your cluster, follow the Create windows VM exercise to create
a windows 2012 VM . Otherwise, select Windows 2012 VM and click Update.
Figure: Update VM
5. At the Update VM window, scroll down to the Disks section. If the parameter EMPTY is set to
true for a CDROM, go to the next CDROM.
| 191
Figure: Update Disk
7. Verify that the OPERATION field is set to Empty CDROM. Click Update.
9. From the main menu, select the Data Protection dashboard. Click the +Protection Domain
button. Select Async DR under +Protection Domain.
10. In the Data Protection window, click the +Protection Domain button. Select Async DR under
+Protection Domain. Enter trainingXX-PD where XX is your initials. . Click Create to create the
protection domain.
11. Select your Windows 2012 VM under the Unprotected Entities and click Protect Selected
Entities by clicking the Protect Selected Entities link in the lower-left corner of the window.
12. You should see your Windows VM being moved to the Protected Entities section. Click Next.
| 193
Figure: Click Next
14. Configure your local schedule to repeat every 60 minutes and the retention policy to keep the last
one snapshot. Click Create Schedule.
17. Select Local Snapshots tab. You should see a snapshot. Select the snapshot and click Restore.
18. In the Remote Snapshot window, select your Windows VM and click OK.
19. Go to the VM dashboard and select the Table tab. You should see the VM restored from the
snapshot. This VM should be powered off.
| 195
Figure: Restored VM Powered Off
In this task, you configure your peer cluster as a remote site and take a remote snapshot. You also
verify your VM has been successfully replicated to the peer cluster. Do consult with your instructor if
you are not sure who your peer cluster is. The exercise begins with the assumption that you logged
into your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout in to the browser’s URL bar. If you receive
any sort of certificate warning window(s), click through to accept the self-signed certificate so that
you get to the cluster login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
3. Repeat steps 1 and 2 to log in to the peer cluster. Do consult with your instructor if you are not
sure who your peer cluster is.
4. Select the gear icon and click Network Configuration. Verify that a VM network has been
created for VLAN 0 in your peer cluster .
5. Select the Storage dashboard and click the Table tab. Verify that a storage container named
VM_Migrate has been created in your peer cluster.
6. In your Data Protection dashboard, select Physical Cluster under +Remote Site.
7. In the Remote Site window, enter the following information: REMOTE SITE NAME: <Your peer
cluster name>-RS ADDRESSES: <Your peer cluster IP address>
| 197
Figure: Remote Site
8. Configure NETWORK MAPPING between your cluster and your peer cluster (you may have to
scroll down in the Remote Site window to see the NETWORK MAPPING section). Select your
VM network for VLAN 0 in the Source Cluster field and your peer VM network for VLAN 0 in the
Destination Cluster field.
9. Configure VSTORE NAME MAPPING between your cluster and your peer cluster. Two mappings
should be created: one from your default container to your peer VM_Migrate container, and a
second one from your VM_Migrate container to your peer default container.
10. Click the Save button to save your remote site configuration.
11. Log in to your peer cluster. Select the Data Protection dashboard and click the Table tab. Select
the Remote Site tab. Verify your peer cluster has configured your cluster as their remote site.
Also verify there are two Vstore mappings: one from their default container to your VM_Migrate
container and another one from their VM_Migrate container to your default container.
12. At your cluster, select your protection domain and click Take Snapshot. Select the check box
beside your remote site and click Save.
| 199
Figure: Replicate Protection Domain
13. Select your protection domain and select the Replications tab. You should see an outgoing
replication.
14. Go to your peer’s Data Protection dashboard. Your protection domain should now appear, and it
also should be in the inactive mode. You should also see an incoming replication when you select
the Replications tab.
In this task, you initiate protection domain failover to the peer cluster. You verify that the Windows
VM (in this example, My2012R2) appears as a VM in the peer cluster. You further verify the
protection becomes active in the peer cluster and inactive in the local cluster. The exercise begins
with the assumption that you are logged into your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your exercise handout into the browser’s URL bar. If you receive
any sort of certificate warning window(s), click through to accept the self-signed certificate so that
you get to the cluster login as displayed in the following screen.
2. Log in to your cluster with the credentials provided to you in your exercise handout.
| 201
Figure: Prism Admin Login
3. In yourData Protection dashboard, select the Table tab and then select the Async DR tab.
Select your protection domain and click Migrate.
5. Go to the VM dashboard, select the Table tab. Confirm that the Windows VM is gone.
6. Confirm that the protection domain became inactive in the local cluster.
7. At the peer cluster main menu, select VM dashboard and select Table tab. Confirm that your
Windows VM is seen in the table and it should be in the powered off state.
8. Verify that the protection domain becomes active in the peer cluster.
| 203
Figure: Protection Domain Active
In this task, you initiate protection domain failback to the local cluster. Failback can be achieved
by initiating failover at the peer cluster. Prior to this action, verify that the windows VM does not
exist in the local cluster and that the protection domain is inactive in the local cluster. After failover
is initiated at the peer cluster, the windows VM will fail back to the local cluster. Verify that the
protection domain is active in the local cluster and that the Windows VM can be powered back on.
This exercise begins with the assumption that you are logged in to your lab environment.
1. From your assigned desktop, open a web browser, enter your assigned cluster’s external virtual
IP address provided to you on your lab handout into the browser’s URL bar. If you receive any
2. Log in to your cluster with the credentials provided to you in your exercise handout.
3. At your peer cluster’s Data Protection dashboard, select the Table tab and then the Async DR
tab. Select your protection domain and click Migrate. Select your cluster in the Migrate Protection
Domain window and click Save.
4. In your cluster’s VM dashboard, select the Table tab. Your Windows VM should have failed back
to your cluster.
| 205
Figure: Confirm Protection Domain is Inactive
Objectives
Prism Central
In this exercise, you register your cluster with a Prism Central server and explore the features and
benefits of Prism Central.
In this exercise, you register your cluster with a Prism Central server and explore the features and
benefits of Prism Central.
In this exercise, you perform the following tasks:
• Register a cluster with Prism Central.
• Explore Prism Central features and benefits.
• Take a deeper dive into cluster planning.
In this task, you register a cluster with Prism Central.
3. Complete the Prism Central Registration form with the information provided in the exercise
handout.
5. Log in to the Prism Central server using the address and credentials provided in the exercise
handout.
6. From the Prism Central home dashboard, verify your cluster has been registered with Prism
Central. You should see your cluster listed in the Impacted Clusters box in the upper-left corner
of your browser window.
Note: It may take a minute or two for your cluster appear in the Impacted Clusters box.
| 209
Figure: Impacted Clusters
8. Click the Launch Prism Element button in the upper-right corner of your browser window.
9. Verify that you are taken to the Prism Element page for your training cluster.
In this task, you explore some of the features and benefits of Prism Central.
1. Log in to the Prism Central server using the IP address and credentials provided in the exercise
handout.
3. Click to select your cluster in the Impacted Cluster box. In the cluster information page, examine
the recent historical CPU usage, memory usage, IOPs, bandwidth, and latency use of your
cluster. Do all of the values displayed appear to be in a normal range (e.g. is your cluster
experiencing any heavy or anomalous behavior)?
4. Click the Alerts link to see if your cluster has any current outstanding alerts. Note: If your cluster
does have any outstanding alerts, you will not be addressing them in this exercise at this time.
5. Click the X in the upper-right corner of the browser to close the cluster overview.
| 211
Figure: Click Close
6. Back in the Prism Central Home dashboard, click the Explore link.
7. By default, you should be taken to an Entities browser window that displays VM entities.
8. Are the VMs being displayed only for your cluster or for all clusters registered with Prism Central?
Note: If you cannot tell from your lab environment, you can answer this question from the screen
from the previous exercise step.
10. For the selected VM, examine the CPU usage, memory usage, and other displayed fields.
1. Is the VM experiencing any sort of load that might cause concern?
2. Can you determine from this display how many VDPUs have been assigned to the VM?
3. Can you determine from this display how much RAM has been assigned to the VM?
11. Notice the row of buttons in the upper-right corner of the browser window.
| 213
Figure: Notice Row of Buttons
12. Click on the … More button. What other VM-related options do you see?
13. Click on the links VM NICs, Snapshots, Virtual Disks, and Alerts to see what information is
displayed for each of these links.
14. Click on the VM name pull down menu in the upper-right corner of the browser window. Do you
see all of the other VMs listed in the pull down menu?
15. Click to select one of the other VMs. You should be switched to the overview dashboard for that
VM.
16. Click the X in the upper-right corner of the browser window to return to the Entities window.
| 215
Figure: Click Clusters
18. How many clusters have been registered with your Prism Central?
Note: The number may vary depending on your lab environment and how many students have
registered their clusters with this Prism Central server.
19. Click on the Hosts, Disks, and Storage Containers links to examine the information they
present to you.
20. Click the Analysis link. Notice the form presented pretty much mimics the same Analysis
dashboard you would see when managing a single cluster via Prism Element.
22. What are the similarities and differences you see here, when comparing to the items displayed in
Prism Element on the individual cluster?
24. What benefits do you see in using Prism Central in a multi-cluster environment?
| 217
Figure: Click Planning Link
2. Click the Get Started button to explore the effects of future cluster use and/or growth.
3. From the information presented in the New Scenario window answer the following questions:
1. What is the target length in months?
2. Are there any workloads assigned to the scenario?
3. Does the overall runway indicate the cluster will experience any problems during the scenario
target window?
4. Let’s explore how your cluster would react to the adding of a VDI workload. Click the + Add
Workload link.
| 219
Figure: Add Workload Complete
6. Click the Add Workload button to add this workload to your cluster scenario.
7. According to Prism Central’s scenario planner, will your cluster be able to handle this load for the
next six months? Hint: Examine the Overall Runway and look for any bars that are red.
8. If your cluster will not be able to handle the new scenario, what could you do to ensure that it can
handle the new scenario before your deploy the new VDI desktops?
9. Click the X in the upper-right corner of the browser window to close the New Scenario window
(we are not going to save this scenario in this exercise). Click No to confirm you do not want to
save this scenario.
Objectives
In this exercise, you Nutanix Cluster Check (NCC). NCC enables you to perform cluster health
checks, collect cluster logs to send to Nutanix support, clean up old core files, and several other
functions. In this exercise, you explore a few of these features.
In this task, you use the NCC utility’s built-in help. The task begins with the assumption that you are
logged into a desktop that has access to your lab environment.
Note: This exercise was written using NCC version 2.2.8. If your cluster is running a
different version of NCC, your output may vary from the example outputs shown in this
exercise document.
1. Using the PuTTY utility on your desktop, log in to a CVM in your assigned cluster. Fill out the
Host Name (or IP address) field in the PuTTY Configuration window using the cluster external
virtual IP address specified in your exercise handout.
3. The NCC utility provides you with a lot of built-in help. To get the top-level help displayed, enter
the command ncc. The output should look something like the following screen. Note: Any row
with the letter M in the Type column indicates a module that consists of multiple sub-entities. You
explore one of those next.
4. Explore the health_checks module by entering the command: ncc health_checks. Notice the
majority of the health checks themselves consist of additional sub-modules.
| 223
Figure: NCC Health Checks Output
5. Dig one level deeper into the built-in help NCC offers. Type the command ncc health_checks
network_checks. Notice that as you dive deeper into the help screens, you will begin to see the
letter P under the Type column. Entries labeled P (for Plugin) represent individual checks NCC
performs. Also notice that at most levels, there is a special Plugin labeled run_all that allows you
to run all of the various checks at that level.
6. Explore NCC’s built-in help until you are satisfied in your understanding of its functionality.
In this task, you have the NCC utility find and remove any old core dump files that have been taking
up disk space on your CVMs. Core files are typically used by Nutanix support to debug particular
issues that you may have been experiencing on your cluster. Once the problem has been resolved,
core files are not needed, and you can reclaim the space that they are using.
1. Examine what file-level capabilities NCC has built-in. Enter the command ncc file_utils. The
output should look something like the following screen. You will now remove any old core files.
Of the various options available to you, can you figure out what command you should enter to
remove old core files?
2. If you guessed the command: ncc file_utils remove_old_cores to remove old core files,
congratulations! Enter the command now to remove old core files.
3. Similarly, you may have noticed the NCC file utilities can also remove old fatal log files. Like core
files, fatal logs are generally used in debugging specific problems and once the problem has
been resolved, the old fatal log files may not be needed. Enter the command now to remove old
fatal log files (yes, we’re leaving this as an exercise for you to figure out on your own!).
In addition to cleaning up old cores and log files, you can have NCC collect your cluster’s log files (or
various sub-groups of log files) for transmission to support staff in assisting with resolving any issues
you may be experiencing.
1. Run the command ncc. Determine what module you would use to collect log files. Enter the name
of the module here: _____________________________________________________
2. Run the appropriate NCC command to get help with the log collector module. What command
would you use to get help with the NCC log collector module? ________________________
3. To begin, you will collect only the alerts logs. To collect alerts only, run the command ncc
log_collector alerts. The tail end of the output should look something like the following screen.
Note: The output includes a line indicating the path to the tar file created that contains all of the
alert logs from all of the cluster’s CVMs.
| 225
Figure: NCC log Collector Alerts
4. Now run the appropriate NCC command to collect all of the log files on all of your CVMs. Feel
free to ask your instructor if you need help determining the exact NCC command that you will
need to use. What is the path to the resultant log bundle created from the command you just
entered? _____________________________________________________________________
Note: This command may take several minutes to run to completion.
Perhaps the most common use of the NCC utility is to check the health of a Nutanix cluster,
hardware, hypervisor, and other configuration settings. In this task, you explore NCC health checks.
1. Examine the health of your inter-CVM connections. To do this, enter the command ncc
health_checks network_checks inter_cvm_connections_check. The tail end of the output will look
something like the following screen. Note that in this case, the check passed successfully.
2. Run the entire battery of NCC health checks by running the command ncc
health_checks_run_all. The tail end of the output will look something like the following screen.
| 227
228 | Concluding the Installation
Module 15
Lifecycle Operations
Topics: In these exercises, you perform a number of lifecycle operations.
The first task simulates adding a node to an existing cluster.
• Exercises This is accomplished by taking one of the student clusters,
destroying it (effectively making its nodes look "new"), then
adding nodes to one ore more of the remaining clusters in the lab
environment. WARNING: As it is likely that you will be working in
multiple pairs of teams doing this exercise in parallel, with some
teams destroying their clusters while other teams re-use nodes
from those same destroyed clusters (adding them to their non-
destroyed clusters), it is important that you add nodes from your
partner team's cluster and not nodes from some other randomly-
selected (i.e. not your lab partner team's) cluster. Please follow the
exercise steps closely to ensure that you are using the right nodes
when you are performing the add node operation.
In the second task, you remove a node from an existing Nutanix
cluster. Removing a node is typically done in several situations,
such as when you want to:
• retire old hardware
• move a node from one cluster to another
• split a larger cluster into two smaller clusters.
Lifecycle Operations
In these exercises, you perform a number of lifecycle operations. The first task simulates adding a
node to an existing cluster. This is accomplished by taking one of the student clusters, destroying
it (effectively making its nodes look "new"), then adding nodes to one ore more of the remaining
clusters in the lab environment. WARNING: As it is likely that you will be working in multiple pairs of
teams doing this exercise in parallel, with some teams destroying their clusters while other teams
re-use nodes from those same destroyed clusters (adding them to their non-destroyed clusters), it
is important that you add nodes from your partner team's cluster and not nodes from some other
randomly-selected (i.e. not your lab partner team's) cluster. Please follow the exercise steps closely
to ensure that you are using the right nodes when you are performing the add node operation.
In the second task, you remove a node from an existing Nutanix cluster. Removing a node is
typically done in several situations, such as when you want to:
• retire old hardware
• move a node from one cluster to another
• split a larger cluster into two smaller clusters.
In these exercises, you perform a variety of lifecycle operations exercises. The first task simulates
adding a node to an existing cluster. You also remove a node from an exisiting Nutanix cluster.
In this exercise, you:
1. Add a node to an existing cluster
2. Remove a node from an exisiting Nutanix cluster
Add Node
This exercise simulates adding a node to an existing cluster. This is accomplished by taking one
of the student clusters, destroying it (effectively making its nodes look “new”), then adding those
nodes to one or more of the remaining clusters in the lab environment. WARNING: It is likely that
you will be working in a lab environment with multiple pairs of teams doing this exercise in parallel.
Some teams will be destroying their clusters while other teams will re-use nodes from those same
destroyed clusters (adding them to their non-destroyed clusters). It is important that you add nodes
from your partner team’s cluster and not nodes from some other randomly selected (i.e. not your
lab partner team’s) cluster. Please follow the exercise steps closely to ensure that you are using the
right nodes when you are performing the add node operation.
Before you can begin to add a new node to your cluster, your team must choose a cluster to destroy
and a cluster to which you will add the nodes. In this exercise, we refer to the former as Team
Destroy and the latter as Team AddNode. Team Destroy will destroy their cluster, adding the nodes
in that cluster to a pool of available nodes to be added to other clusters. Team AddNode will then
use one or more of the nodes from their partner team’s destroyed cluster (again be careful in that
you select the right nodes in a large lab environment) to add to their Team AddNode's cluster.
Task 1: Preparing to Add a Node
Working in teams of two clusters, choose one cluster to be Team Destroy and one cluster to be
Team AddNode.
In this task, Team Destroy will destroy their cluster in preparation for adding its nodes to their partner
Team AddNode’s cluster. All of the steps in this task are to be performed by Team Destroy only. This
is important! We do not want to destroy clusters unnecessarily.
1. In the next task, it is important that your partner team, Team AddNode, adds nodes from your
cluster only. To maximize the chance of success we will have you make a note of the block ID of
your cluster.
1. Using a browser, log in to your cluster using its external virtual IP address from your exercise
handout and login credentials from your exercise handout.
2. Click the dashboard pull-down list and select the VM dashboard.
Figure: VM Dashboard
3. Click the Table tab.
| 231
Figure: Table Tab
4. Click to select the Include Controller VMs check box.
2. Using PuTTY on your VDI desktop, have one member of Team Destroy log in to one of the CVMs
in your cluster. Fill out the Host Name (or IP Address) field in the PuTTY Configuration window
using the IP address of one of your cluster CVMs specified in your exercise handout.
4. If your cluster has any powered on VMs, you need to power them off now. If your cluster does not
have any powered on VMs, you can continue to the next step.
5. From the PuTTY command line, stop your cluster by entering the command cluster stop. Enter
Y when asked to confirm the operation. This command will take a minute or two to run.
| 233
Figure: Cluster Stop
6. From the PuTTY command line, destroy your cluster by entering the command cluster destroy.
Enter Y when asked to confirm the operation. This command will take a minute or two to run.
7. Exit the PuTTY window. Your cluster’s nodes are now in a state where they can be added to
another cluster as if they were new nodes.
In this task, you use one (or more) of the nodes from the cluster destroyed in the previous task,
adding it (them) to the Team AddNode cluster. All of the steps in this task are to be performed by
Team AddNode only. Note: It is possible that there may be several teams performing this exercise in
parallel. Therefore, it is important that you add the correct nodes to the correct clusters. Be mindful
of the steps in this exercise and you should be OK.
1. Team AddNode, using a browser on your VDI desktop, log in to the Prism UI for your cluster
using your cluster’s external virtual IP address specified in your exercise handout. Log in using
the credentials provided on your exercise handout.
3. In the Expand Cluster window, find the nodes that you will be adding to your cluster. Notice the
nodes are organized by block ID (but labeled as Serial Number). The following screen shows a
single cluster with the nodes available for adding organized in groups by block ID/Serial Number.
WARNING: You may have more than one block displayed in your lab environment. Be careful
that you select only nodes from the correct block.
4. Select the node or nodes that you will be adding to Team AddNode’s custer. It is very important
you select only nodes from the block ID corresponding to nodes from your partner team’s cluster.
You noted this block ID in the previous task. Make sure no nodes from any other blocks are
selected before you proceed. The following screen shows the check box you would check to
select all of the nodes in the desired block.
| 235
Figure: Select Node
5. Click the desired check box to select the nodes to be added to Team AddNode’s cluster.
When you have done this, you are presented with fields for specifying the node’s names and
IP addresses. In our lab environment, because we are essentially recycling nodes from a
previously existing cluster, all the fields will be filled in for your with correct values. In a production
environment, where these nodes would be factory new, you would have to fill out the IP address
fields as appropriate for your management network environment. Give the Expand Cluster
window a look over, including scrolling down as necessary before proceeding. When you are
ready to proceed, scroll down to the bottom of the Expand Cluster window and click Next.
6. You are now at the Host Configuration page in the Expand Cluster window. As the node has an
installed hypervisor, Expand Cluster will not image (install a hypervisor and CVM into) the node,
but instead will only add the nodes to your cluster. Click the Expand Cluster button in the lower-
right corner of the window to add the nodes to your cluster.
| 237
Figure: Host Node Expand Cluster
7. The expand cluster operation may take a few minutes to complete during which time you will see
a progress bar as shown in the following screen.
8. After a minute or two, you should see a completed progress bar indicating cluster expansion has
successfully completed.
| 239
Figure: Expand Cluster Completed
10. If you are not on the Prism Home dashboard, click Home in the dashboard pull-down list now
to switch to the Home dashboard. Note how many nodes are now in the cluster. In the following
screen, you can see the cluster has expanded from its original three nodes.
Remove Node
In this exercise, you remove a node from an existing Nutanix cluster. Removing a node is typically
done in one of several situations: when retiring old hardware, moving node from one cluster to
another, and splitting a larger cluster into two smaller clusters.
In this exercise, you are removing a single node from a cluster.
Before you remove a node from your cluster, verify that the cluster contains a minimum of four
nodes.
1. Using either the Firefox or Chrome browser, log in to the Prism web console for your cluster using
the IP address of any of the cluster’s CVMs as specified in your exercise handout. Log in using
the credentials specified in your exercise handout.
2. Make sure you are in the Home dashboard. If you are not, click the Nutanix logo in the top center
of the menu bar to return to the Home dashboard.
| 241
Figure: Home Dashboard
3. Look in the lower-left corner of the Home dashboard and verify the number of nodes in your
cluster is at least four. In the following screen, the cluster has six nodes.
In this task, you identify which node you will remove from the cluster. In terms of our lab
environment, it does not really matter which node you remove, but, to keep things simple, we will
have you remove the node with the highest IP address.
1. Double click the PuTTY client on your VDI desktop and log in to one of your cluster’s CVMs using
the IP address of any of your cluster’s CVMs specified in your exercise handout. Log in using the
user credentials nutanix and the password specified in your exercise handout.
2. Generate a list of the nodes in your cluster along with their node IDs (you will need the node ID
of the node you will be removing in a subsequent exercise task). At the PuTTY command prompt,
enter the command ncli host list. Hint: The node ID is actually in the output line labeled Uuid.
3. Identify the node with the highest IP address (you may have to press the space bar to page
through the output from the previous command). Note here the node’s ID value from the Uuid
output line for the appropriate node. Host Id: ______________________
In this task, you schedule the node to be removed. The removal operation, although dynamic, does
take some time and, in a subsequent task, you monitor the removal progress.
Continuing in the PuTTY session you established in the previous task, begin the node removal
operation by entering the command ncli host remove-start id=<enter-the-host-id-from-the-
previous-lab-task>
Note: It is important that you enter the correct value for the id parameter in the previous
command.. Hint: Utilizing copy/paste from your PuTTY window is probably the easiest way to
ensure you have entered the correct value.
1. The following screen shows the node remove command having been entered but the
operation not yet started (i.e. the enter key has not yet been pressed).
| 243
Figure: Node Remove Command Entered
2. The following screen shows the result after having entered the node remove command.
In this task, you check the (ongoing) status of the node removal operation. Depending on how busy
your cluster is, node removal may take 20 minutes or longer.
1. Continuing in the PuTTY session you established in the previous task, check the status of the
node removal operation by entering the command ncli host get-remove-status. The following
screen shows the output of the command while the node removal is still in progress.
2. Continue to re-enter the previous command from time to time to monitor the node removal status.
When the remove node operation has completed, you see the output from the previous command
change as shown in the following screen.
Finally, you use the Prism UI to verify that the node removal operation has successfully completed.
Note: You may have to wait several minutes for the node removal operation to complete before
performing this task successfully.
1. If you are not already logged into the Prism web console, log in to the Prism web console for your
cluster with the credentials provided to you in the exercise handout.
2. Just as you did back in task 1, go to the Home dashboard (if you are not already there) and verify
the number of nodes in your cluster. The number should now be one less than you recorded in
task 1. If you compare the following screen to the similar screen at the beginning of this exercise,
you see the cluster now has one fewer node, five instead of six.
| 245
Figure: Verify Node