Team Leader - Nutanix Technology Champion - Nutanix NTC Storyteller

Julien DUMUR
Infrastructure in a Nutshell
Updating HYCU 4.9.0 to 5.0.0

HYCU update 5.0.0 has just been released! Update your infrastructure!

Preparing for the update

Updating to HYCU 5.0.0 requires that you are already at least 4.9.0.

To be able to update your controller, you must first download the latest version available here: https://download.hycu.com/ec/v5.0.0/hycu-5.0.0-1488.qcow2

Next, connect to your Nutanix cluster and transfer the previously downloaded image as shown in the screenshot:

Importing the HYCU 5.0.0 image on the Nutanix cluster

It is imperative that you name the image exactly like the file you just downloaded.

The preparation is complete, we can move on to the update.

HYCU Update

On your HYCU interface, click on the toothed wheel then on “Software Upgrade”:

HYCU Software Upgrade menu

If you created your image correctly in the previous step, you can now select version 5.0.0 and click “Software Upgrade”:

Selecting version 5.0.0

Validate the current job cancellation warning window to start the update:

Running jobs cancellation warning

Wait for the update which lasts approximately 5 to 10 minutes:

HYCU update in progress

You can monitor the progress of operations from your Prism console:

Update tasks in Prism

Once the update is complete, you can reconnect to your HYCU instance and check the version at the bottom left:

HYCU version 5.0.0 displayed

Link to Release Note: https://download.hycu.com/ec/v5.0.0/help/en/HYCU_ReleaseNotes.pdf

Documentation link: https://download.hycu.com/ec/v5.0.0/help/en/HYCU_UserGuide.pdf

Read More
Adding a Nutanix AHV cluster to HYCU 4.9.0

After writing an update to the article on deploying the solution, here is the update on adding a source to your HYCU controller.

Prerequisites for adding a Nutanix AHV cluster

Among the first prerequisites, the Data Service IP must be configured on your Nutanix cluster:

Data Services IP configured on the Nutanix cluster

To be able to add a Nutanix AHV cluster as a source on your HYCU controller, you will need an account capable of connecting to your cluster and to your Prism Central if you have one.

I recommend using a dedicated account and not using the admin account of your cluster whose password will change regularly.

Dedicated hycu account in Local User Management

Last point, obvious but always good to remember, the HYCU VM and your cluster / Prism Central must be able to communicate.

Once all the prerequisites have been met, you can proceed to adding the cluster to your controller.

Adding the Nutanix cluster to HYCU

On your HYCU interface, in the toothed wheel at the top right, click on source:

Sources menu in HYCU settings

Add your Nutanix cluster (IP_ADDRESS:9440) with the service account that you have dedicated to HYCU then click on “Next”:

Adding the Nutanix cluster with the service account

Repeat the operation if you have a Prism Central:

Adding Prism Central in HYCU

Your cluster is added to your controller:

Cluster added to the HYCU controller

You can find it in the “HYPERVISOR” tab of the “Sources” window:

Cluster in the Hypervisor tab of the sources

And on the home page of your HYCU controller:

Cluster on the HYCU controller home page

Your Nutanix cluster is ready to be backed up.

Read More
Deploying HYCU 4.9.0 on Nutanix AHV

It’s been a while since I wrote the first tutorial for deploying HYCU on a Nutanix AHV cluster and since that day, the overall procedure has changed slightly. The opportunity for me to write an updated version and share it with you.

Download HYCU 4.9.0

To retrieve the HYCU QCOW2 image in version 4.9.0, you must go to the site https://support.hycu.com/ and authenticate or create an account if you do not have one.

HYCU Support portal

The direct link is: https://download.hycu.com/ec/v4.9.0/hycu-4.9.0-5310.qcow2

Otherwise, follow the guide!

Once logged in, click on “HYCU for Private Cloud & Data Centers”

HYCU for Private Cloud and Data Centers

In the “Product download” section, click on “HYCU version 4.9.0”

HYCU version 4.9.0 download

Check “I agree the HYCU…. » and click “Continue” to view the download options.

HYCU image download options

Click “Download .qcow2” to start downloading the image. Now let’s move on to the Nutanix cluster.

Transferring the image to the Nutanix AHV cluster

To transfer the image to your cluster, I invite you to follow my dedicated tutorial: https://juliendumur.fr/en/nutanix-ahv-upload-image-to-your-cluster/

Otherwise, connect to Prism Element, then go to the settings and open the “Image Configuration” section:

Prism Element Image Configuration section

Click on “Upload image”, fill out the form and select the previously uploaded image:

Importing the HYCU image in Prism Element

For simplicity in managing your images, I recommend naming your image according to the HYCU-VERSION-BUILD model.

Click “Save” to start the transfer and wait until your image is processed by the cluster and ACTIVE.

Preparing the virtual machine

Create a new virtual machine on your cluster:

Creating the HYCU VM

For the name, you must name the machine hycu-version-build. Concerning the technical characteristics, you can refer to the table present in the official documentation to allocate the correct quantity of vCPU / Cores / Memory / Additional Data Disk:

HYCU VM vCPU, memory and disks

Then assign the network of your choice to the machine and the configuration will be complete.

Finalizing the installation

To finalize the configuration of your HYCU machine, start it.

On the console, you will have the choice of machine type: select “HYCU Backup Controller”.

HYCU Backup Controller choice in the console

Complete the configuration form:

HYCU controller configuration form

Wait while the settings are applied to your machine, then go to: https://IP-HYCU-CONTROLLER:8443

HYCU 4.9.0 login page

The default login and password are admin / admin.

HYCU 4.9.0 dashboard

Read More
Renaming the default storage container in CLI on Nutanix AHV

When deploying a new cluster, the default storage container name is automatically generated and is not particularly aesthetically pleasing.

To rename it, there is only one solution: go through the Command Line Interface.

To carry out this operation, connect to a CVM in your cluster and list all the existing containers on the cluster:

nutanix@CVM: ncli container list

All the containers and their associated details will then be displayed. Find the container you want to rename in the list and type the following command:

nutanix@CVM: ncli container edit name=CURRENT_NAME new-name=NEW_NAME

Replace “CURRENT_NAME” with the name automatically generated by the system when creating the container, and NEW_NAME with the name you wish to assign to this container, leaving no spaces or special characters other than – and _

Then check that your container has been correctly renamed with the command:

nutanix@CVM: ncli container list
ncli container list output showing the renamed container

In Prism Element, you will also see the new name you gave your storage container:

Renamed storage container in Prism Element

Read More
Prism Central pc.2024.1 release notes

Nutanix has just announced the availability of version 6.8 eSTS of AOS and with this new version comes a lot of new features including…. Prism Central version pc2024.1!

I am not going to detail all the features added or updated in this new version of AOS and let you consult the Release Notes which detail their content.

I decided to focus on a feature that arrives with the new version of Prism Central awaited by many customers who have a modest infrastructure: Prism Central X-Small.

Prism Central X-Small

Among all the new features made available by the new pc2024.1 version of Prism Central, one feature addition caught my attention: Prism Central X-Small.

Until now, the deployment of Prism Central was only possible according to 3 templates:

TemplateVM configurationLimitations
Small6 vCPU / 28Gb RAM / 500Gb Storage2500 VMs / 10 Clusters / 200 Nodes
Large10 vCPU / 46Gb RAM / 2500Gb Storage12500 VMs / 25 Clusters / 500 Nodes
X-Large14 vCPU / 62Gb RAM / 2500Gb Storage12500 VMs / 25 Clusters / 500 Nodes

Like the X-Large deployment which offers an imposing configuration of Prism Central, until now a minimum size deployment was missing. Prism Central X-Small fills this void:

VM configurationLimitations
4 vCPU
18Gb RAM
100Gb Storage
500 VMs
5 Clusters
50 Nodes

As you can see, this Prism Central template has a lightweight hardware configuration, this is not the only point of differentiation with other deployment templates.

Indeed, due to its configuration, this deployment of Prism Central does not allow you to exploit all the functionalities usually offered. Here are the points of differentiation:

SupportedUnsupported
Multi-cluster management (Up to 5)Scale-out
VM managementFlow Virtual Networking
Host managementFlow Network Security
Infrastructure management, monitoring and healthSelf-Service
Enterprise authentication and RBACIntelligent Operations
REST APIsNutanix Kubernetes Engine
Comprehensive searchObjects
Life Cycle Manager (LCM)Files
Pulse InsightsFoundation Central
Prism Central Backup and RestoreFoundation
CategoriesQuotas
ProjectsMulti-site DR
Microservices infrastructeMarketplace
Identity and access managementReporting and Dashboards
Security dashboard
Nearsync / Synchronous replication

If you want to benefit from a feature not supported by Prism Central X-Small, you will need to consider deploying a Small / Large / X-Large template.

Use cases

The main use case that immediately comes to mind is the following:

  • a simple infrastructure
  • 1 to 3 modest-sized clusters
  • a hundred virtual machines
  • no need for additional services (Flow, Self-Service, NKE, etc.)

This is the type of installation that we encounter in many SMEs or local authorities for example, the arrival of Prism Central X-Small is therefore timely.

Read More
SSH keys and Cluster Lockdown on Nutanix AHV

It’s in Nutanix’s roadmap! Password authentication is in the sights of the publisher who intends to put an end to it and warn its users via an informational alert:

Prism alert: the cluster is using password based SSH access

The objective is to gradually switch clients to SSH key authentication in order to impose it in a future version of its hypervisor.

Creating SSH keys

Supported SSH encryption algorithms are:

  • AES128-CTR
  • AES192-CTR
  • AES256-CTR

If you already have such a key pair, you can proceed directly to cluster integration.

To create an SSH key pair, we will need a tool like PuttyGen.

PuTTYgen window to generate an SSH key pair

Click “Generate” and move the mouse cursor over the window. Then indicate a passphrase then save the public key and the private key.

WARNING: be sure to use a strong, non-predictable passphrase.

Passphrase and key saving in PuTTYgen

We must now integrate the public key into the cluster.

Integration of the public key on the cluster

To integrate your public key into your cluster, connect to the Prism interface and go to “Settings > Cluster Lockdown”

Cluster Lockdown menu in Prism settings

Click on “New Public Key”, give it a name, paste the public key content and validate.

Adding a public key with New Public Key

At this stage, classic password authentication and SSH key authentication are both active and functional, it is time to test.

Testing and activation of the cluster lockdown feature

First, we will test authentication via SSH key. Don’t panic, whatever happens, even if the SSH connection via the keys does not work after activating the cluster lockdown, you can always backtrack via the Prism interface.

Configure your favorite SSH connection tools, integrate your private key then launch a connection to your Nutanix cluster. First, enter the login you want to use, here I chose “nutanix”:

SSH login to the CVM with a public key and passphrase prompt

Then enter the passphrase that you configured when creating your SSH key. Validate, you are now connected to your cluster via your SSH key without having to use the password for the “nutanix” account.

Now let’s deactivate password authentication by returning to the “Settings > Cluster Lockdown” menu. Uncheck the “Enable Remote Login with Password” box:

Enable Remote Login with Password box unchecked

Try logging in again using the “nutanix” account and the usual password and notice that you can no longer log in with this method:

Password-based SSH login refused

Try with your private key and the associated passphrase :

Successful SSH login with the private key

Your cluster is now SSH accessible only via the SSH key system. If there are several administrators working on the server, don’t forget to repeat the operation for each of them.

Important point: remember to keep your private keys in a safe place and use a strong passphrase.

Official documentation

The Nutanix official documentation: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_7:mul-security-cluster-lockdown-pc-t.html

Read More
Mastering Nutanix AHV updates with LCM

Updating a hyperconverged cluster can sometimes be time-consuming and present certain risks of production interruption if the process is poorly managed.

Nutanix has optimized the process of updating its clusters so that it is as simple and automated as possible, the famous “1-click upgrade”.

Life Cycle Manager on Prism Element

LCM has slight differences between Prism Element and Prism Central. This is what the interface looks like on Prism Element:

LCM on Prism Element allows you to manage updates to some of the bricks in your cluster:

  • AHV
  • AOS
  • Cluster Maintenance Utilities
  • File
    Flow
  • Foundation
  • Licensing
  • NCC

These are the bricks that you can update through Prism Element.

Life Cycle Manager on Prism Central

LCM on Prism Central allows you to manage the updating of the remaining bricks which are mainly the software bricks:

Life Cycle Manager: inventory

The LCM Inventory, whether on Prism Element or Prism Central, allows you to list all the software and hardware versions installed on your cluster, as well as any updates or firmware available:

LCM inventory of software and hardware versions

The inventory process lasts around ten minutes:

It then allows access to all installed and available versions:

LCM: the recommended update order

With the multitude of software bricks and the hardware part, it is not always easy to know in what order to update the different modules.

The first step of updating your cluster takes place on Prism Central:

The actions to be carried out in order:

You must then switch to Prism Element for the second step:

The actions to be carried out in order:

  • LCM inventory
  • NCC Check and Upgrade
  • Foundation Upgrade
  • AOS Upgrade
  • Firmware Upgrade
  • AHV Upgrade

It is recommended to do another LCM inventory once the AHV update is complete to verify that there are no hardware updates remaining to be applied.

Finally comes the last step, again on Prism Central:

The actions to be carried out in order:

  • LCM inventory
  • All software updates (Nutanix Files, Self-Services (Calm), NKE (Karbon), NDB, Flow…)

To carry out the desired updates, simply check them then click on “View upgrade plan”:

Selecting updates and the View upgrade plan button

Once the update plan has been developed by LCM, you must click one last time to start the process:

Each step of the process requires time because the cluster multiplies checks at each step to verify the conformity of the installed updates:

It is important to specify that the cluster update process, with the exception of certain software bricks, does not cause a service shutdown if good practices are respected regarding fault tolerance.

Official Nutanix documentation

Official documentation: https://portal.nutanix.com/page/documents/details?targetId=Acropolis-Upgrade-Guide-v6_5:upg-upgrade-recommended-order-t.html

Read More
VMware vs Nutanix features comparison

Following the takeover of VMWare by the giant Broadcom and the subsequent runaway prices, many customers are looking for alternative solutions. Unfortunately, it is not always easy to find your way around.

VMWare vs Nutanix comparison

The most complicated thing when we are used to a technical solution is to make a radical change.

Will we find all the features we use? What do the names correspond to? What prospects for possible developments among competitors?

I took the time to make a comparison of the different VMWare and Nutanix bricks:

I hope this will help you see things more clearly and shed light on a possible future choice.

Read More
Deploying Nutanix Self-Service

Nutanix has a tool for automating the deployment and life cycle of applications: Nutanix Self-Service (formerly Calm).

I’ll show you how to deploy Nutanix Self-Service on your Nutanix cluster.

Nutanix Self-Service Overview

Self-Service (formerly Calm) streamlines application management, deployment, and scalability across hybrid clouds through self-service, automation, and centralized role-based governance.

Nutanix Self-Service overview: self-service, lifecycle and hybrid cloud

Deploy Nutanix Self-Service

To deploy Nutanix Self-Service, you must have a functional Prism Central on your cluster. Indeed, almost all of Nutanix’s complementary building blocks are managed by Prism Central, so don’t look for it on Prism Element.

In the side menu, look for the “Services” section and click on “Calm” (the old name for Nutanix Self-Service):

Enable App. Orchestration (Calm) button

Deployment is very simple, then just click on “Enable App. Orchestration”:

Enable App Management and Nutanix seeded blueprints options

The first box must be checked to be able to deploy Self-Service, the second is optional but highly recommended because it allows access to the online catalog offering a plethora of ready-to-use blueprints.

Once you have made your choice, click on “Save” and wait around ten minutes while Self-Service deploys:

Completed Self-Service deployment tasks

Once deployment is complete, a new Volume Groups will be available on your Nutanix cluster:

Calm volume group created by Self-Service

That’s it, Nutanix Self-Service is deployed and ready to use:

Welcome to Calm screen
Read More
Locked admin account on Nutanix AHV

It happens that the admin account of a Nutanix cluster is locked due to too many authentication failures and that you can no longer connect to it.

Prism login page showing Account locked due to too many failed attempts

Most of the time, this is the result of changing the password of the admin account on the cluster if it is used on other systems such as Nutanix Move or HYCU for example.

Here’s how to reset the password for the “admin” account of a cluster

Remove the “admin” account from routines

To begin with, if you do not want the problem to recur, you must remove the “admin” account from the cluster from the elements that can cause this. This could be backup software, a Nutanix brick (Move for example), possibly a monitoring tool.

It is important not to use the “admin” account of a cluster to connect a tool to the cluster.

Reset “admin” password

Connect by SSH to a CVM of the Nutanix cluster on which the account is locked with the “root” account.

Then enter the following command:

passwd admin

Enter the new password twice, the password is reset.

Unlock the “admin” account

To unlock the “admin” account, enter the following command:

allssh sudo faillock --user admin --reset

The “admin” account is now unlocked.

Read More