Skip to main content

My Nutanix Notes

IPMI Tool 
~ # /ipmitool lan print1 (To Print the IP Address Info. command must run thru ESXi console)
~ # /ipmitool lan set 1 vlan id 333 (To set the VLAN ID)
~ # /ipmitool lan set 1 vlan id off (To remove the VLAN or disable)
Set time zone for CVMs:

SSH to any CVM

# ncli cluster set-timezone timezone=America\New_York

Test E-Mail config:

#ncli cluster send-test-email recipient=“” subject=“test”

To Stop/Start PRISM Service:
curl http://localhost/h/exit - Prism restart from zeusleader node

curl http://localhost/prism/leader   —> Prism start

Commands to verify the Block-Awareness

  • ncli cluster get-fault-tolerance-state
  • ncli cluster get-domain-fault-tolerance-status  type=rackable_unit
  • ncli cluster get-domain-fault-tolerance-status type=node
  • ncli rack ls - how many blocks are in the cluster

Expand Cluster thru nCLI
# ncli cluster discover-nodes (First Discover the nodes)

nutanix@NTNX-14SM36410061-A-CVM:$ ncli cluster discover-nodes
    Cluster Id                :
    Controller Vm Address     :
    Hypervisor Address        :
    Ip                        : fe80::20c:29ff:fe00:a1e4%eth0
    Ipmi Address              :
    Model String              : NX-3060
    Node Position             : B
    Node Uuid                 : 942205fd-f14c-4540-846b-b80b30eecb40
    Rackable Unit Model       : NX-3060
    Rackable Unit Serial      : 14SM36430046
    Sed Node                  : false

    Svm Id                    :
ncli cluster add-node node-uuid=942205fd-f14c-4540-846b-b80b30eecb40 (Add nodes into cluster using Node UUID)

Shutdown a Nutanix Block/Nodes:

Step 1: Shutdown all VMs, not CVMs

Step 2: SSH to any CVM

Step 3: Issue “cluster stop”, make sure cluster stopped and no errors reported

Step 4: Issue “cluster status”, all processes must be DOWN state

Step 5: Shutdown CVMs one by one . Use “shutdown -P now” command

Step 6: Shutdown ESXi/Hyper-V/KVM Nodes

Start or Power On a Nutanix Block:

Step 1: Power On a node at a time

Step 2: Wait for 10-20 seconds to power on every nodes

Step 3: Make sure all CVMs are powered on

Step 4: SSH to any CVM

Step 5: Type “cluster status” if all process are showing down

Step 6: Type “cluster start”

Step 7: Type “cluster status” to see all process are showing Up

Step 8: Make sure you’re able to access Prism Web Interface

Step 9: Make sure NFS mounts are accessible


Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires.
We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software.

This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment.
When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console.
Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager

Creating DSN

Create a System DSN for this d…

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only.

Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address)

~ # /ipmitool lan set 1 vlan id 333

~ # /ipmitool lan print1
Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : MAC Address             : xx:xx:xx…

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called "vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format.

If you don’t have a VMotion/SVMotion license, use the following command to achieve the same.

From Thick to Thin:

vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk"

It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store.

Use the following command to see real-time usage of thin disk:

du –h "Thindisk.vmdk"

You can notice the big difference of disk usage between of Thin and Thick format disks.

From Thin to Thick:

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk…