Tag Archives: ESX 8

Nutanix on VMware vSphere ESX 8

Posted on by
Reply

Nutanix on VMware KB ID 0001866

Problem

In the wake of Broadcom doing its best to strangle VMware and its discontinuation of free ESX. I thought I’d look at the free alternatives. The most obvious is Nutanix CE (Community Edition) which is both free, and lets you have up to 4 nodes – which is impressive, as Free ESX does not have clustering or access to vCenter.

Honest Opinion: It’s very flaky, if you want a solution that you can just roll out and it work out of the box, then don’t attempt to run this on ESX/VMware. I accept that it’s an unusual deployment scenario, but people will want to test it first, and if you’re moving from VMware to Nutanix you are going to test it in an environment you know. I was going to deploy a three node cluster and attempt to do some VMware > Nutanix migrations. But despite about a week of trawling forums I could not get the cluster to create and launch (yes, I enabled UUID) After a week I thought – OK I’ll try a single cluster, and that’s what I’m doing below

Solution: Nutanix on VMware

You will need a beefy ESX deployment each nodes VM Requirements: 4x vCPU, 64GB vRAM and 750GB of storage.

To get access to the download for the Community Edition you need to go the Nutanix create a login and say you want to test drive Nutanix CE edition, trying to find the download on the website – is confusingly hard. Wait until you get a confirmation email and that will have the link to the page you want.

Note: Remember your Nutanix login details (you will need them later.)

Before you start, the virtual switch(es) that will connect to the Nutanix VM(s) will need to have both promiscuous mode and forged transmits enabled. Note: I run EVE-NG so I have all the security settings set to accept.

Create a New Virtual Machine.

Give the VM a sensible name i.e. Nutanix-CE-Node-1 > Next > Select a host, (or cluster if you have DRS enabled > Next > Select a Datastore with enough free space > Next.

Compatible with > ESX8 >Next > Add 4x vCPUs > Tick ‘Expose hardware assisted virtualisation to the guest OS‘ > Scroll down.

Set the memory to 64GB > Scroll Down > Set the first  Hard Disk to 50Gb > Enable Thin Provisioning > Change the Controller to ‘New SATA Controller” > At this point scroll up select ‘Add Hardware” > Add a further TWO hard disks > they will appear just below the 50GB one you have already configured > Set the second disk to 200GB > Thin Provisioned > New SATA Controller > Scroll down.

Set the last disk to 500GB > Thin Provisioned > New SATA Controller > Ensure the VM is in the correct port group > Set the CD/DVD ROM drive to the Nutanix installer iso image > Select ‘Connect at Power On‘ > Next > Finish.

The following step you should not need to do for a single host cluster, but it is a requirement if your intending on creating multiple cluster hosts > Edit the VM Settings > Advanced Properties > Create a new attribute called disk.EnableUUID and set its value to TRUE > Add > OK

Power on the VM and go grab a coffee > Select AHV (the Nutanix Hypervisor) > Make sure the correct disks are set for H (boot) D (Data) and C (CVM) > Add the host and CVM IP addresses  > Add the subnet and default gateway > Tick create a single cluster and add a DNS server. > Next Page.

Note: If you were not creating a single node cluster, you would obviously leave that option blank, and manually create a multi node cluster by logging into the CVM later (see notes below).

 

This is another flaky thing I don’t like > YOU NEED TO scroll all the way to the bottom of the EULA text then use the tab button > then select I accept with the space bar. If you dont scroll down, the following step fails and sends you back here.

Again good time for a coffee, when it’s done you will see this. Before you type ‘y’ to reboot carry out the next step.

In the VM properties disconnect the DVD iso.

It will take a while but once the VM is up you can SSH into it (use the CVM IP Address!) The default credentials are.

Username: nutanix

Password: nutanix/4u

 

More things I don’t like running Nutanix on VMware: The cluster didn’t come up; you can see that by running cluster status. As you can see a lot of services are listed as down. issue a cluster start command and go get another coffee. Do not proceed until all the services are up.

Browse to https://{CVM-IP-Address}:9440 > Log in with the default credentials and you will be asked to change the password > Do so, then reauthenticate with your new password. Warning this has a different username to the SSH login,

Username: admin

Password: nutanix/4u

Remember way back when we started thinking about Running Nutanix on VMware and I said you would need your Nutanix login credentials you setup on their website.

Note: If you get an error about not being able to contact the NEXT server, that because it’s not using the DNS server you setup above see the following article.

Nutanix: Could Not Reach Next Server

Finally we are runnning Nutanix on VMware.

Additional Notes: Running Nutanix on VMware

Although I could not get it to work, if you want to create a multi-node cluster then you use the following syntax using all the nodes CVM IP addresses (whilst logged into a CVM).

[box]

cluster -s 192.168.100.71,192.168.100.73,192.168.100.75 create

[/box]

Related Articles, References, Credits, or External Links

NA

VMware Enable SSH (vSphere ESX)

Posted on by
 

VMware Enable SSH KB ID 0000299 

Problem

Should you wish to get SSH (remote secure console) access to your ESX  hosts, you need to do the following.

ESX Version 8 and Newer

ESX Version 6.5 and Newer

ESX version 5 and Newer

ESX version 4.1.0

ESX version 4.0.0 and earlier

ESX version 4.0.0 and earlier

Solution

VMware Enable SSH ESX 8.0

Directly on an ESX Host: If you have a stand-alone ESX Server running version 8.x, Log in via the web console >  Select ‘Host’ > Actions > Services > Enable Secure Shell (SSH).

Via vSphere/vCenter: If you want to enable SSH on an ESX host through the vCenter Web client then, from the ‘hosts and datacentres’ view > Select the Host  > Configure > Services > Locate SSH > Start.

Enable SSH Permanently: Some people don’t want this enabled for security reasons, and in production that makes sense, but on my test network I always have SSH enabled. from the same screen as above with SSH selected > Edit Start-up Policy > Select ‘Start an stop with host” > OK.

VMware Enable SSH 6.5

If you have a stand-alone ESX Server running version 6.5, it’s a lot easier to enable ESX access. Select ‘Host’ > Actions > Service > Enable Secure Shell (SSH). Note: You can also enable the direct console access here.

If you want to enable SSH on an ESX host through the vCenter Web client then, from the ‘hosts and datacenters’ view > Select the Host  > Configure > Security Profile > Scroll down to ‘Services’ > Edit.

Locate ‘SSH > Start > OK.

Once enabled you will see the following warning on the hosts summary page, however, in version 6.5 you can suppress this error.

VMware Enable SSH ESX 5

ESX 5 has a built in firewall, which can have SSH opened in the VI clients, or just as with version 4.1.0 you can enable SSH Locally from the console from troubleshooting options.

Enable Remotely

1. Log into the host with the VI client > Select the host > Configuration > Security Profile > Properties.

2. Locate SSH Server > Tick it > Options > You can either manually start it or set it to start automatically.

3. You will see the following warning to “retrieve” the firewall settings (because you have just changed them) > Select Yes.

Note: Having it running will still cause the “Configuration Issues – SSH for the host has been enabled” nag screen on the summary tab of the host.

VMware Enable SSH ESX 4.0.1

Starting with version 4.0.1 you can enable SSH access from the server console.

1. Go to the normal ESX console > Press F2 > Log in >Troubleshooting Options.

2. Select “Enable Remote Tech support” toggle on and off with {enter} if you want to SSH in the server remotely using PuTTy for example > If you want to log on directly at the console choose “Enable Local Tech Support”.

3. Note: Having it running will still cause the “Configuration Issues – Remote Tech support Mode (SSH) for the host {hostname} has been enabled” nag screen on the summary tab of the host.

Grant SSH Access to ESX 4.0.0 and earlier

1. Go to the normal ESXi console.

2. Press ALT+F1 > the screen will change > Type unsupported {enter} > Note: Nothing will appear on the screen till you hit {enter} > Type in the root password and press {enter}.

3. You now need to edit a config file, the only editor we have is vi (sorry) issue the following command,

[box]vi /etc/inetd.conf[/box]

4. The vi editor will open the file, use the arrow keys to move down to the line that says,

[box]#ssh stream tcp nowait root…[/box]

Press I on the keyboard (that puts the vi editor into insert mode) and delete the hash “#” mark from the beginning of the line.

5 Then, to save the changes press {Esc} > type in :wq {Enter} (that’s write the changes and quit if you’re interested).

6. Enter the following command.

[box]

cat /var/run/inetd.pid

[/box]

It will provide you with a number, (in the example below its 4983, yours will be different).

7. Issue the following command.

[box]

kill -HUP {the number you got from above}

[/box]

8. To get back to the usual ESXi screen and exit command line press ALT+F2.

9. You can now connect with an SSH client like Putty.

 

Related Articles, References, Credits, or External Links

Original Article written: 07/12/11

ESX4 – Grant Root User SSH Access

Thanks to Dave Corrasa for the feedback.