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. Search the list for the container you want to rename and type the following command (WARNING: do not modify “NutanixManagementShare” or “SelfServiceContainer”):
Replace “CURRENT_NAME” with the name automatically generated by the system when creating the container, and NEW_NAME with the name you want to assign to this container, without putting any spaces or special characters other than the – and the _
Then check that your container has been correctly renamed with the command:
nutanix@CVM: ncli container list
Activate the data optimization mechanisms
Go to “Storage”, find the container you just renamed, select it and click on “Update”.
In the window that appears, click on “Advanced settings” and check the “Compression” box.
Click “Save” to validate your changes.
It is not recommended to enable ALL data optimization mechanisms on a single container.
The best practice is to create different containers with data optimization mechanisms adapted to the disks of the VMs that you will position on them.
Compression can be enabled in almost all use cases, except on:
containers containing encrypted data
containers containing compressed data
Erasure Coding is recommended in the following use cases:
Nutanix Object
Backups
Archives
File servers
Log servers
Mail servers (depending on usage)
Finally, deduplication should be reserved for the VDI part (virtual desktops).
Enabling this feature allows you to reserve enough storage so that your cluster can continue to operate normally even if a node fails. This automatically excludes clusters of 1 or 2 nodes.
To enable this option, go to “Settings > Rebuild Capacity Reservation” and check the box:
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
Sometimes tasks may be stuck indefinitely on your cluster without ever completing or failing. In this case, you need to take manual action to resolve the issue.
Be careful, this operation is not without risks, which is why I strongly advise you to contact Nutanix support if you are not sure.
The first step is to check how long the task has been running. To do this, go to the tasks page and filter on the tasks currently running:
In this case, we can see that the task has been running for more than 10 months. No doubt, it is crashed and must be canceled manually.
To do this, you must connect to one of the CVMs and type the following command:
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.
Enter the network configuration then click on “Next”:
The last window is new in the latest versions, I advise you to leave the default settings and click on “Deploy”:
A little patience during the deployment:
Once the deployment is complete, go to your Prism Central address and authenticate yourself with the usual default pair of identifiers:
The very first time you log in, you will be asked to set a new password:
Then log in with the new password you just configured. Then validate the conditions of use:
Keep Pulse enabled:
If, like me, you then notice that your cluster is still not registered on Prism Central, return to Prism Element and restart the procedure, this time selecting “Connect”:
Fill in the connection details for your Prism Central and validate to start the recording:
Congratulations, your Prism Central in PC.2024 version is now operational on your Nutanix cluster under AOS 6.8
During my Nutanix cluster deployments, I often came across the question of the test plan to be carried out after each installation.
As I sometimes forgot certain things, I ended up creating a complete, readable and understandable test plan that I am making available to you today.
The test plan presented allows you to check and ensure that all configurations have been set up, that the network and electrical redundancy of your cluster comply with best practices.
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.
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:
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
In Prism Element, you will also see the new name you gave your storage container:
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.
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 configuration
Limitations
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:
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.
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.
