Skip to main content

Acropolis Hypervisor Configuration

The following commands help to configure Factory (Nutanix) loaded hypervisor called as Acropolis without reinstalling using Foundation process:

To configure IP Address:  root@ahv# vi /etc/sysconfig/network-scripts/ifcfg-br0 
BOOTPROTO="none“  (set as “static”)

DNS Entry:  root@ahv# vi /etc/resolv.conf

To List Ethernet Interfaces:  manage_ovs show_interfaces 

To verify the interfaces are assigned to br0:  manage_ovs --bridge_name br0 show_uplinks 
To Add 1gb Interface into br0:  manage_ovs --bond_name bond1 --interfaces 1g update_uplinks 

To Configure IP Address in CVM: ssh to CVM (ssh nutanix@ and use sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0, finally reboot the CVM

To Create cluster:  1. cluster -s <cvm_ipaddress> (- - redundancy_factor=3 -> Only if RF3) create 
2.      cluster start

eg: cluster -s,, create

To Set Cluster Name:  # ncli cluster edit-params new-name=cluster_name 
To Add DNS Server:  # ncli cluster add-to-name-servers servers="dns_server

To Add NTP Server: # ncli cluster add-to-ntp-servers servers="ntp_server

To Add External IP Address: # ncli cluster set-external-ip-address external-ip-address=‘Cluster IP Address”

To change CVM VLAN: change_cvm_vlan (SSH to CVM and run this command)

To Set Hostname: # vi /etc/sysconfig/network 
and /etc/hosts (Edit HOSTNAME entry)

To Configure IPMI for AHV:

root@ahv# ipmitool -U ADMIN -P ADMIN lan set 1 ipsrc static
root@ahv# ipmitool -U ADMIN -P ADMIN lan set 1 ipaddr mgmt_interface_ip_addr 
root@ahv# ipmitool -U ADMIN -P ADMIN lan set 1 netmask mgmt_interface_subnet_addr 
root@ahv# ipmitool -U ADMIN -P ADMIN lan set 1 defgw ipaddr mgmt_interface_gateway 
ipmitool lan set 1 plan id lan_id_number

To set VLAN ID for Acropolis Hypervisor (AHV)

ovs-vsctl set port br0 tag=host_vlan_tag 
Confirm Tagging by entering:

ovs-vsctl list port br0 

Cluster Initialization:
  1. http://cvm_ipv6_addr:2100/cluster_init.html.

    . http://NTNX-12AM3K520060-A-CVM.local.:2100/cluster_init.html


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…