Once the deployment of the Nutanix Move appliance is complete, it remains to carry out its initial configuration in order to begin setting up future migration plans.
Network setup
To configure the network and switch to fixed IP, you must connect to the Move VM in SSH with the account “admin” and the password “nutanix/4u”. As this is the first connection, you will be asked to change the password.
Once the new password is configured, the network configuration tool launches automatically and you just have to follow the instructions:
Alpine Linux v3.16 (3.16.2) - Nutanix Move
Welcome to Nutanix Move. Please refer to the Move documentation
to know more about the console usage and troubleshooting.
https://www.nutanix.com/products/move/
Do you want to configure static IPv4 address? (y/N)
y
Enter Static IPv4 Address (e.g. 192.168.1.3)
192.168.2.240
Enter Netmask (e.g. 255.255.255.0)
255.255.255.0
Enter Gateway IP Address (e.g. 192.168.1.254)
192.168.2.254
Enter DNS Server 1 IP Address (e.g. 128.91.2.13)
8.8.8.8
Enter DNS Server 2 IP Address (e.g. 128.91.2.14)
8.8.4.4
Enter Domain (e.g. my.dc.domain)
homelab.local
Static IPv4 configuration provided:
ipaddress * 192.168.2.240
netmask * 255.255.255.0
gateway * 192.168.2.254
dns1 * 8.8.8.8
dns2 * 8.8.4.4
domain * homelab.local
Configuring static IPv4 …
WARNING: you are stopping a boot service
WARNING: you are stopping a boot service
Stopping busybox ntpd … [ ok ]
Stopping networking …
lo … [ ok ]
eth0 …
Please wait a few minutes while the reconfiguration completes.
First login
In the “My Apps” menu of the Admin Center, you can click on “Open” to access the Nutanix Move web interface:
The first thing you will be asked to do is accept the End User License Agreement:
You will then be asked to set up a password to secure access to Move:
And finally, choose the type of migration you want to perform. This choice has no impact on the rest of the events, you will be able to perform the 2 types of migration regardless of your choice:
Congratulations, Nutanix Move is now deployed on your Nutanix cluster:
But that’s not all!
Nutanix Move Basic Configurations
There are still a few small configurations to be done to have an optimal Nutanix Move deployment. The appliance configuration is located in the gear menu at the top right, then in “Appliance Settings”:
Among the options that can be customized, the only one that is of real interest to me is the NTP part to ensure consistent time synchronization across your entire Nutanix cluster:
The “Prism Central Registration” part is intended to override the Move authentication that you configured at the first connection by authentication via the accounts present in Prism Central that you wish to authorize to connect to the Nutanix Move appliance:
In the previous article I gave you a presentation of the infrastructure that I set up to produce my series of articles on Nutanix Move.
In this new article, we will see how to deploy the Nutanix Move virtual machine on our Nutanix AHV cluster.
Prerequisites and update of the Move image
The deployment of Nutanix Move on the latest versions of AHV with a Prism Central 2024 must be done from the marketplace, one of the new features of recent versions of Prism Central.
Then, before deploying Nutanix Move, it is necessary to update the disk image integrated into Prism Central. To download the latest version of Move, go to the following link: https://portal.nutanix.com/page/downloads?product=move
You need to download the file “Move QCOW2 file for AHV”:
Then go to Prism Central, in “Infrastructure > Compute and Storage > Images” and click on “Add Image”:
On the next page, click on “+ Add file”, select the image that has just been downloaded from the Nutanix website and click on “Next”:
On the next page, leave as default and click “Save”:
Please wait while the image is transferred and processed:
Once this is done we can move on to deployment.
Nutanix Move deployment
To deploy Nutanix Move, you need to log in to Prism Central and go to the Marketplace menu in the Admin Center. In the drop-down menu at the top of the interface, select “Admin Center” and then click on “Marketplace”:
Then, simply click on the “Get” button in the “Move” box and then on the “Deploy” button on the Move page to start the deployment process:
The page that is then displayed allows you to configure all the parameters that we want to assign to the Move virtual machine that we are going to deploy. The first field to modify is the “Application Name” field that must be filled in:
In the following fields, no changes are needed to the VM name or its hardware configuration:
For disk configuration, modify the image to select the one we transferred to the cluster previously:
Select the network on which to place the Move virtual machine:
Then enter the identifiers to assign to the SSH account:
The virtual machine deployment start:
You can track the VM deployment on the “My Apps” page of the Admin Center, if you click on “Manage”:
Once the deployment is complete and Nutanix Move is functional, the status will change to “Running”:
Before starting the process that will allow you to migrate all of your virtual machines to your new Nutanix AHV environment, a quick overview of the prerequisites is required.
General prerequisites
In terms of general prerequisites, there are a few things to respect and check before starting the migration of your infrastructure.
You can migrate everything, with 2 exceptions
The first thing to know is the types of machines to migrate. You can migrate all of your virtual machines with Nutanix Move, except:
domain controllers
Exchange servers
These are the only 2 restrictions of the software. It is recommended to install a new domain controller, migrate the FSMO roles to it, promote it to a primary domain controller and depromote the old one. Regarding Exchange, you will have to reinstall a server and transfer all of the data from the old server.
Network Flows
Obviously, since we are talking about a migration via the network, it is imperative that the flows are open to allow Nutanix Move to reach the source and destination clusters:
An upcoming update of my flow matrix is planned to integrate the Move part.
Administrator account with privilege
For Nutanix Move to perform the operations required for migrations on the different source and destination clusters, it is imperative to have accounts with administrator rights on these clusters.
Prerequisites specific to VMware ESXi clusters
Supported operating systems
To date, the majority of operating systems used in a professional environment on ESXi are supported by Move.
If one of your virtual machines is not compatible for a Nutanix Move migration (I invite you to carry out tests, unsupported does not mean non-functional), you will then have to consider carrying out a complete and up-to-date reinstallation on the new cluster.
VMware Tools
It is important that VMware tools are deployed on all of your virtual machines so that Nutanix Move can manage the virtual machines hosted on the source ESXi cluster optimally. This will avoid warnings or failures when you launch the migration processes.
If one of your virtual machines is not compatible for a Nutanix Move migration (I invite you to carry out tests, not supported does not mean non-functional), you will then have to consider carrying out a complete and up-to-date reinstallation on the new cluster.
Nutanix Move Agent
On the Hyper-V cluster, for this to work, it will be imperative to deploy the Nutanix Move Agent. I will detail the agent installation procedure in the following articles.
In my previous article, I presented Move, the Nutanix software that facilitates migration to AHV or any other supported hypervisor.
In order to write this series of posts, I set up the most representative environments of what we currently find at our customers. Let me introduce them to you so that you have the migration context.
The source clusters
I set up 2 separate clusters on 2 different hypervisors. The first cluster is a VMWare ESXi cluster on which I deployed 8 virtual machines: 4 Windows Server and 4 Linux.
The second cluster is a Microsoft Hyper-V cluster on which I also deployed 8 virtual machines with the same distribution as the first cluster: 4 Windows Server and 4 Linux.
For convenience, the configuration of the VMs is very succinct. I have carried out default installations of the operating systems.
The Linux VMs are Ubuntu Server 20.04 while the Microsoft ones are Windows Servers 2022.
For local accounts, the Linux VMs have logins in “nutanix” and the Windows VMs in “administrator”. The password for all VMs is “nutanix/4u”.
The only difference in configuration between the virtual machines concerns those hosted on ESXi. Indeed, I deployed the VMWare tools on the latter.
The target cluster
The target cluster will be my Nutanix cluster under AOS 6.8.1 and AHV el8.nutanix.20230302.101026.
All migrations will be carried out via Nutanix Move in its version 5.1.1 which we will deploy in the next article.
Nutanix Move is a software solution designed by Nutanix to facilitate the migration of virtual machines (VMs) from a virtualization environment to a Nutanix infrastructure in a simple, secure way and with minimal downtime.
Key features of Nutanix Move
Nutanix Move allows you to move virtual machines from traditional hypervisors, such as VMware vSphere or Hyper-V, to Nutanix AHV (Acropolis Hypervisor) or other supported hypervisors. It supports various hypervisor environments such as VMware ESXi, Hyper-V, AWS, and Nutanix AHV. It is possible to migrate workloads from public or private cloud environments to Nutanix hyperconverged infrastructures.
Nutanix Move ensures a migration by minimizing the downtime of services and applications, thus allowing continuity of operations during the entire transition process. In addition, you will not have to reconfigure anything once the virtual machine is migrated.
Thanks to an intuitive interface, Nutanix Move simplifies the migration process by automating many manual tasks, which reduces the risk of human error and improves efficiency. However, certain prerequisites must be respected for the migration to take place in the best conditions
Nutanix Move allows you to evaluate workloads before migration, identifying potential issues in order to avoid any negative impact on application performance after migration. It also allows you to simulate your scenarios before executing them.
Use Cases
The use case we have encountered most often in recent months is that of companies seeking to reduce costs related to the explosion in the price of VMware licenses following the acquisition by Broadcom by migrating to Nutanix AHV.
For my part, I was also able to experiment with it on a remote desktop server migration from Hyper-V to Nutanix AHV and I must say that with each migration I am amazed by the simplicity and efficiency of the solution.
Having implemented it several times in a professional context, I can affirm that Nutanix Move is an essential tool for anyone wishing to modernize their IT infrastructure and facilitate their transition to a Nutanix hyperconverged environment.
For those who have already had to implement it, the flow matrix presented on the Nutanix website is not always easy to read.
Many customers ask us during the pre-deployment preparation phase to assist them in opening the flows necessary for the proper functioning of their future Nutanix cluster.
Based on this observation, I took the initiative to create a simplified flow matrix to allow rapid implementation on network filtering equipment.
After a successful installation of a Nutanix cluster, we saw in the previous article that it was imperative to modify the default passwords of your cluster. But that’s not the only thing to do…
Configuring Name Servers
Among the things to do after installing a Nutanix cluster, there is configuring DNS servers.
Go to “Settings > Names Servers” to display the field to add DNS servers:
For my part I would recommend configuring at least 2 to ensure redundancy in case of failure of one of the 2 servers, the limit imposed by Nutanix being 3. I chose Google DNS for my lab for convenience.
Add your DNS servers one by one by entering their address and clicking on “Add”.
Among the things to do after installing a Nutanix cluster, there is also configuring NTP servers and time zone.
Go back to “Settings > NTP Settings” to see the field to add NTP servers.
Nutanix recommendations are as follows:
If possible, synchronize the time of Nutanix clusters with an internal source
If you do not have an internal NTP server, synchronize with recognized national servers
Specify at least 5 reliable and stable time sources with the lowest possible Stratum (3 offers no redundancy, 4 is the minimum to have redundancy, 5 is the publisher recommendation)
Do not use servers that are rate limited
Do not use a Windows time server
My recommendation is therefore to use an internal time server, but if you do not have one, I advise you to use the site: https://www.ntppool.org/
Then, select your geographic area then your country to display the servers closest to your cluster (in my case, France) :
All you have to do is add them one by one by adding their DNS address and clicking on “Add”.
To set the time zone, connect to one of the CVMs via SSH and type the command:
To verify that your cluster is in the correct time zone, you can type the following command which will return the information about your cluster’s timezone:
ncli cluster info | egrep "Timezone"
Timezone : Europe/Paris
You must choose strong passwords to secure your infrastructure and that they are unique!
The minimum complexity required by Nutanix is:
8 characters
1 lowercase letter minimum
1 uppercase letter maximum
1 number minimum
1 special character
Some cluster passwords will also require you to respect certain constraints related to the password history.
Generally speaking, I would recommend that you use a password generator often integrated into your password management software to create your passwords and apply a length of at least 16 characters while respecting the complexity rules indicated above.
Prism Element admin password
This step is essential and you cannot bypass it. If this is your first time logging in, the login is “admin” and the password is “nutanix/4u”. You will be ask to configure a new password respecting the complexity criteria.
CVM “Nutanix” password
If you leave the default password, you will have critical alert messages on your Prism Element interface.
To fix this, connect to the IP of one of the CVMs in your cluster in SSH with the nutanix identifier and the default password nutanix/4u. Then, a simple “passwd” will allow you to configure a new password:
nutanix@NTNX-99110c89-A-CVM:~$ passwd
Changing password for user nutanix.
Current password:
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
nutanix@NTNX-99110c89-A-CVM:~$
Enter the current password, then the new password twice in a row and that’s it!
Hosts passwords
Just, after an installation the passwords of the Nutanix hosts are always the default ones and this will generate critical alerts on the cluster.
To change the “root” password of the hosts, connect to one of the CVMs and type the associated command:
nutanix@NTNX-99110c89-A-CVM:192.168.2.200:~$ echo -e "CHANGING ALL AHV HOST ROOT PASSWORDS.\nPlease input new password: "; read -rs password1; echo "Confirm new password: "; read -rs password2; if [ "$password1" == "$password2" ]; then for host in $(hostips); do echo Host $host; echo $password1 | ssh root@$host "passwd --stdin root"; done; else echo "The passwords do not match"; fi
The system will then ask you to enter the new password twice:
CHANGING ALL AHV HOST ROOT PASSWORDS.
Please input new password:
Confirm new password:
Host 192.168.2.199
Nutanix AHV
Changing password for user root.
To change the “admin” password of the hosts, connect to one of the CVMs and type the associated command:
nutanix@NTNX-99110c89-A-CVM:192.168.2.200:~$ echo -e "CHANGING ALL AHV HOST ADMIN PASSWORDS.\nPlease input new password: "; read -rs password1; echo "Confirm new password: "; read -rs password2; if [ "$password1" == "$password2" ]; then for host in $(hostips); do echo Host $host; echo $password1 | ssh root@$host "passwd --stdin admin"; done; else echo "The passwords do not match"; fi
The system will then ask you to enter the new password twice:
CHANGING ALL AHV HOST ADMIN PASSWORDS.
Please input new password:
Confirm new password:
Host 192.168.2.199
Nutanix AHV
Changing password for user admin.
passwd: all authentication tokens updated successfully.
To change the “nutanix” password of the hosts, connect to one of the CVMs and type the associated command:
nutanix@NTNX-99110c89-A-CVM:192.168.2.200:~$ echo -e "CHANGING ALL AHV HOST NUTANIX PASSWORDS.\nPlease input new password: "; read -rs password1; echo "Confirm new password: "; read -rs password2; if [ "$password1" == "$password2" ]; then for host in $(hostips); do echo Host $host; echo $password1 | ssh root@$host "passwd --stdin nutanix"; done; else echo "The passwords do not match"; fi
The system will then ask you to enter the new password twice:
CHANGING ALL AHV HOST NUTANIX PASSWORDS.
Please input new password:
Confirm new password:
Host 192.168.2.199
Nutanix AHV
Changing password for user nutanix.
passwd: all authentication tokens updated successfully.
For a customer case, we had to create more than 70 subnets on 2 clusters and performing the operation through the graphical interface would have been much too long and tedious. Here is the method to perform the operation in CLI in just a few minutes.
Creating unmanaged subnets
To make my task much easier, I created an Excel file in .csv format in which I put 3 columns:
The idea is to fill the VLAN_NAME and VLAN_ID column with the name of the VLANs and their associated IDs, provided by the customer in the Predelivery Questionnaire:
Which would give:
Save the file and then open it with Notepad++:
Replace the “;” character with a space:
Then replace “vlan=” with “vlan=” to attach the VLAN ID to the command:
Then connect to a CVM in your cluster and copy and paste all the lines at once into the command line interface:
Nutanix Controller VM (CVM) is a virtual storage appliance.
Alteration of the CVM (unless advised by Nutanix Technical Support or
Support Portal Documentation) is unsupported and may result in loss
of User VMs or other data residing on the cluster.
Unsupported alterations may include (but are not limited to):
- Configuration changes / removal of files.
- Installation of third-party software/scripts not approved by Nutanix.
- Installation or upgrade of software packages from non-Nutanix
sources (using yum, rpm, or similar).
** SSH to CVM via 'nutanix' user will be restricted in coming releases. **
** Please consider using the 'admin' user for basic workflows. **
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_10 vlan=10
acli net.create VLAN_26 vlan=26
acli net.create VLAN_27 vlan=27
acli net.create VLAN_28 vlan=28
acli net.create VLAN_29 vlan=29
acli net.create VLAN_30 vlan=30
acli net.create VLAN_31 vlan=31
acli net.create VLAN_32 vlan=32
acli net.create VLAN_33 vlan=33
acli net.create VLAN_34 vlan=34
acli net.create VLAN_35 vlan=35
acli net.create VLAN_36 vlan=36
acli net.create VLAN_37 vlan=37
acli net.create VLAN_38 vlan=38
acli net.create VLAN_39 vlan=39
acli net.create VLAN_40 vlan=40nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_11 vlan=11
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_12 vlan=12
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_13 vlan=13
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_14 vlan=14
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_15 vlan=15
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_16 vlan=16
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_17 vlan=17
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_18 vlan=18
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_19 vlan=19
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_20 vlan=20
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_21 vlan=21
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_22 vlan=22
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_23 vlan=23
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_24 vlan=24
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_25 vlan=25
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_26 vlan=26
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_27 vlan=27
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_28 vlan=28
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_29 vlan=29
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_30 vlan=30
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_31 vlan=31
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_32 vlan=32
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_33 vlan=33
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_34 vlan=34
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_35 vlan=35
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_36 vlan=36
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_37 vlan=37
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_38 vlan=38
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_39 vlan=39
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$ acli net.create VLAN_40 vlan=40
nutanix@NTNX-e854cc31-A-CVM:192.168.2.200:~$
A quick check on the Prism Element interface to confirm that your VLANs have been created correctly:
Then, you must of course redo the cleaning of your file via Notepad to replace with a space or remove the “;” before importing all this into your SSH terminal.
In our example, you will create the following network:
The command first returns general information about the cluster (name, ID, UUID, Version, IPs, etc.):
####################################################
# TIMESTAMP : Fri Jul 26 09:07:43 2024 (UTC +0000) #
####################################################
Cluster Name: MiddleEarth
Cluster Id: 585086141872525258
Cluster UUID: 00061c09-6abd-7835-081e-a4bf0150cfca
Cluster Version: 6.5.2
NCC Version: 4.6.6.3-5e8b6399
CVM ID(Svmid) : 2
CVM external IP : 192.168.2.200
Hypervisor IP : 192.168.2.199
Hypervisor version : Nutanix 20220304.342
IPMI IP : 192.168.2.139
Node serial : BQWL80251503
Model : CommunityEdition
Node Position : A
Block S/N : e854cc31
Then the command will start to return general information about the cluster, namely the hypervisor, the manufacturer, all the node information (position, host name, manufacturer, model, serial number, etc.), the BIOS and management interface information as well:
Running /hardware_info/show_hardware_info [ INFO ]
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Detailed information for show_hardware_info:
Node 192.168.2.200:
INFO:
--------------------------------------------------------------------------------
Updated: Thu, 25 Jul 2024 12:54:59 UTC
Host UUID: 22dd9131-373f-482a-818f-c60b06988a7d
CVM IP: 192.168.2.200
Hypervisor Version:el7.nutanix.20220304.342
NOS Version:el7.3-release-fraser-6.5.2-stable-f2ce4db7d67f495ebfd6208bef9ab0afec9c74af
NCC Version:4.6.6.3-5e8b6399
--------------------------------------------------------------------------------
Nutanix Product Info
+--------------------------------------------------------------------------------------------------+
| Manufacturer | Intel Corporation |
| Product name | CommunityEdition |
| Product part number | CommunityEdition |
| Configured Serial Number | e854cc31 |
+--------------------------------------------------------------------------------------------------+
Chassis
+--------------------------------------------------------------------------------------------------+
| Bootup state | Safe |
| Manufacturer | ............................... |
| Serial number | .................. |
| Thermal state | Safe |
| Version | .................. |
+--------------------------------------------------------------------------------------------------+
Node Module
+--------------------------------------------------------------------------------------------------+
| Node Position | A |
| Bootup state | Safe |
| Host name | NTNX-e854cc31-A |
| Hypervisor type | KVM |
| Manufacturer | Intel Corporation |
| Product name | S2600WTTR |
| Product part number | G92187-372 |
| Serial number | BQWL80251503 |
| Thermal state | Safe |
| Version | G92187-372 |
+--------------------------------------------------------------------------------------------------+
BIOS Information
+--------------------------------------------------------------------------------------------------+
| Release date | 09/02/2020 |
| Revision | 0.0 |
| Rom size | 16384 KB |
| Vendor | Intel Corporation |
| Version | SE5C610.86B.01.01.1029.090220201031 |
+--------------------------------------------------------------------------------------------------+
BMC
+--------------------------------------------------------------------------------------------------+
| Device id | 33 |
| Device available | True |
| Device revision | 1 |
| Firmware revision | 1.61.1 |
| Ipmi version | 2.0 |
| Manufacturer | Intel Corporation |
| Manufacturer id | 343 |
| Product id | 111 (0x006f) |
+--------------------------------------------------------------------------------------------------+
The storage controller is then listed:
Storage Controller
+--------------------------------------------------------------------------------------------------+
| Location | ioc0 |
| Driver name | virtio-pci |
| Manufacturer | Red Hat, Inc. |
| Status | running |
+--------------------------------------------------------------------------------------------------+
| Location | ioc0 |
| Driver name | virtio-pci |
| Manufacturer | Red Hat, Inc. |
| Status | running |
+--------------------------------------------------------------------------------------------------+
Then it’s the turn of all the general information on the installed memory:
Physical Memory Array
+--------------------------------------------------------------------------------------------------+
| Bank | NODE 1 |
| Configured slots | 5 |
| Max size | 384 GB |
| Num slots | 12 |
| Total installed size | 160 GB |
+--------------------------------------------------------------------------------------------------+
| Bank | NODE 2 |
| Configured slots | 6 |
| Max size | 384 GB |
| Num slots | 12 |
| Total installed size | 192 GB |
+--------------------------------------------------------------------------------------------------+
Then the information concerning the power supplies is displayed:
System Power Supply
+--------------------------------------------------------------------------------------------------+
| Location | Pwr Supply 1 FRU (ID 2) |
| Manufacturer | None |
| Max power capacity | 0.0 W |
| Product part number | G84027-009 |
| Revision | None |
| Serial number | EXWD80400190 |
| Status | OK |
+--------------------------------------------------------------------------------------------------+
| Location | Pwr Supply 2 FRU (ID 3) |
| Manufacturer | None |
| Max power capacity | 0.0 W |
| Product part number | G84027-009 |
| Revision | None |
| Serial number | EXWD82000830 |
| Status | OK |
+--------------------------------------------------------------------------------------------------+
| Location | To Be Filled By O.E.M. |
| Manufacturer | To Be Filled By O.E.M. |
| Max power capacity | 0.0 W |
| Product part number | To Be Filled By O.E.M. |
| Revision | To Be Filled By O.E.M. |
| Serial number | To Be Filled By O.E.M. |
| Status | Unknown |
+--------------------------------------------------------------------------------------------------+
Then those concerning the processor(s):
Processor Information
+--------------------------------------------------------------------------------------------------+
| Socket designation | Socket 1 |
| Core count | 10 |
| Core enabled | 10 |
| Current speed | 2400 MHz |
| External clock | 100 MHz |
| Id | 0xbfebfbff000406f1L |
| L1 cache size | 640 KB |
| L2 cache size | 2560 KB |
| L3 cache size | 25600 KB |
| Max speed | 4000 MHz |
| Status | POPULATED |
| Thread count | 20 |
| Type | Central |
| Version | Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz |
| Voltage | 1.8 V |
+--------------------------------------------------------------------------------------------------+
| Socket designation | Socket 2 |
| Core count | 10 |
| Core enabled | 10 |
| Current speed | 2400 MHz |
| External clock | 100 MHz |
| Id | 0xbfebfbff000406f1L |
| L1 cache size | 640 KB |
| L2 cache size | 2560 KB |
| L3 cache size | 25600 KB |
| Max speed | 4000 MHz |
| Status | POPULATED |
| Thread count | 20 |
| Type | Central |
| Version | Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz |
| Voltage | 1.8 V |
+--------------------------------------------------------------------------------------------------+
Next comes the detailed information for each installed RAM unit:
Memory Module
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_A1 |
| Bank connection | NODE 1 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA4F9 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_A2 |
| Bank connection | NODE 1 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401E96DC |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_B1 |
| Bank connection | NODE 1 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401E97B9 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_B2 |
| Bank connection | NODE 1 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA624 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_C1 |
| Bank connection | NODE 1 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA4AB |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_E1 |
| Bank connection | NODE 2 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA625 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_E2 |
| Bank connection | NODE 2 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401E97AC |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_F1 |
| Bank connection | NODE 2 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA591 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_F2 |
| Bank connection | NODE 2 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA5D8 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_G1 |
| Bank connection | NODE 2 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA1E7 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
| Location | DIMM_H1 |
| Bank connection | NODE 2 |
| Capable speed | 2667.000000 MHz |
| Current speed | 2134 MHz |
| Installed size | 32768 MB |
| Manufacturer | Samsung |
| Product part number | M393A4K40CB2-CTD |
| Serial number | 401EA4A9 |
| Type | DDR4 |
+--------------------------------------------------------------------------------------------------+
Then the information concerning the installed network cards:
NIC
+--------------------------------------------------------------------------------------------------+
| Location | eth0 |
| Device name | eth0 |
| Driver name | ixgbe |
| Firmware version | 0x800004f8 |
| Mac address | a4:bf:01:50:cf:ca |
| Manufacturer | Intel Corporation(8086) |
| Product name | Ethernet Controller 10-Gigabit X540-AT2(1528) |
| Sub device | Subsystem device 35c5(35c5) |
| Sub vendor | Intel Corporation(8086) |
| Driver Version | 5.16.5 |
+--------------------------------------------------------------------------------------------------+
| Location | eth1 |
| Device name | eth1 |
| Driver name | ixgbe |
| Firmware version | 0x800004f8 |
| Mac address | a4:bf:01:50:cf:cb |
| Manufacturer | Intel Corporation(8086) |
| Product name | Ethernet Controller 10-Gigabit X540-AT2(1528) |
| Sub device | Subsystem device 35c5(35c5) |
| Sub vendor | Intel Corporation(8086) |
| Driver Version | 5.16.5 |
+--------------------------------------------------------------------------------------------------+
All installed storage disks, HDD and SSD, are then displayed:
SSD
+--------------------------------------------------------------------------------------------------+
| Capacity | 120.0 GB |
| Firmware version | 2.22 |
| Hypervisor disk | True |
| Power on hours | 0 |
| Product part number | OCZ-AGILITY3 |
| Secured boot disk | False |
| Serial number | OCZ-6F95UNJ029ACBIFD |
| Smartctl status | PASSED |
+--------------------------------------------------------------------------------------------------+
| Capacity | 800.0 GB |
| Firmware version | C925 |
| Hypervisor disk | True |
| Manufacturer | WDC |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Secured boot disk | False |
| Serial number | V6V2TU8A |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Location | 5 |
| Capacity | 500.0 GB |
| Firmware version | RVT04B6Q |
| Hypervisor disk | True |
| Power on hours | 3921 |
| Product part number | Samsung SSD 860 EVO 500GB |
| Secured boot disk | False |
| Serial number | S4CNNX0N803693N |
| Smartctl status | PASSED |
+--------------------------------------------------------------------------------------------------+
| Location | 6 |
| Capacity | 800.0 GB |
| Firmware version | C925 |
| Hypervisor disk | True |
| Manufacturer | WDC |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Secured boot disk | False |
| Serial number | V6V2PDUA |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Location | 8 |
| Capacity | 800.0 GB |
| Firmware version | C925 |
| Hypervisor disk | True |
| Manufacturer | WDC |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Secured boot disk | False |
| Serial number | V6V2U2TA |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Location | 9 |
| Capacity | 800.0 GB |
| Firmware version | C925 |
| Hypervisor disk | True |
| Manufacturer | WDC |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Secured boot disk | False |
| Serial number | V6V2SYZA |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Location | 10 |
| Capacity | 500.0 GB |
| Firmware version | RVT04B6Q |
| Hypervisor disk | True |
| Power on hours | 3926 |
| Product part number | Samsung SSD 860 EVO 500GB |
| Secured boot disk | False |
| Serial number | S4CNNX0N803688F |
| Smartctl status | PASSED |
+--------------------------------------------------------------------------------------------------+
| Location | 12 |
| Capacity | 800.0 GB |
| Firmware version | C925 |
| Hypervisor disk | True |
| Manufacturer | WDC |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Secured boot disk | False |
| Serial number | V6V2L6LA |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
HDD
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | C004 |
| Hypervisor disk | True |
| Manufacturer | SEAGATE |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 10500 rpm |
| Secured boot disk | False |
| Serial number | WBN3AW060000C036516V |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | C003 |
| Hypervisor disk | True |
| Manufacturer | SEAGATE |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 10500 rpm |
| Secured boot disk | False |
| Serial number | WBN1FVRH0000K9277TAC |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | C003 |
| Hypervisor disk | True |
| Manufacturer | SEAGATE |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 10500 rpm |
| Secured boot disk | False |
| Serial number | WBN1B7QZ0000K923B2PF |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Manufacturer | Seagate |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 500.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Power on hours | 0 |
| Product part number | Samsung SSD 860 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Manufacturer | Seagate |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Manufacturer | Seagate |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Manufacturer | Seagate |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Manufacturer | Seagate |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 500.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Power on hours | 0 |
| Product part number | Samsung SSD 860 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | C003 |
| Hypervisor disk | True |
| Manufacturer | SEAGATE |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 10500 rpm |
| Secured boot disk | False |
| Serial number | WBN1EH950000K93000FK |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Capacity | 800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Power on hours | 0 |
| Product part number | WUSTR6480ASS204 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | None |
| Hypervisor disk | False |
| Manufacturer | Seagate |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 0 rpm |
| Secured boot disk | False |
| Serial number | None |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | C001 |
| Hypervisor disk | True |
| Manufacturer | SEAGATE |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 10500 rpm |
| Secured boot disk | False |
| Serial number | WBN00K6G0000E802B5B0 |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
| Capacity | 1800.0 GB |
| Firmware version | C003 |
| Hypervisor disk | True |
| Manufacturer | SEAGATE |
| Power on hours | 0 |
| Product part number | ST1800MM0129 |
| Rotation rate | 10500 rpm |
| Secured boot disk | False |
| Serial number | WBN0DZLT0000E837B2FX |
| Smartctl status | OK |
+--------------------------------------------------------------------------------------------------+
And finally, information regarding the GPU(s) possibly installed with residual details regarding the logs displayed:
GPU
+--------------------------------------------------------------------------------------------------+
| Class | Display controller:VGA compatible controller:VGA controller |
| Device | MGA G200e [Pilot] ServerEngines (SEP1) |
| Revision | 5 |
| Slot | 0000:08:00.0 |
| Sub device | Subsystem device 0103 |
| Sub vendor | Intel Corporation |
| Vendor | Matrox Electronics Systems Ltd. |
+--------------------------------------------------------------------------------------------------+
INFO: Hardware Info log file can be found at : /home/nutanix/data/hardware_logs
INFO: NuCollector output written to: /home/nutanix/data/hardware_logs/192.168.2.200_output
INFO: The command to verify the output is: cd /home/nutanix/data/hardware_logs && sha224sum -c output.checksum
Refer to KB 7084 (http://portal.nutanix.com/kb/7084) for details on show_hardware_info or Recheck with: ncc hardware_info show_hardware_info
+-----------------------+
| State | Count |
+-----------------------+
| Info | 1 |
| Total Plugins | 1 |
+-----------------------+
Plugin output written to /home/nutanix/data/logs/ncc-output-latest.log
This command is really useful for quickly exporting an exhaustive list of the entire hardware configuration of your cluster, especially if it is necessary to check compatibility or to transmit the information to support if this proves necessary.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Matomo is an open-source web analytics platform that provides detailed insights into website traffic and user behavior.
