Install ESXi on to a Gigabyte Brix (or Intel NUC).
- [Instructor] Now that I have the image copied over to the USB drive, I can insert it into the back of the Gigabyte BRIX and boot it into the ESXi installer. But before doing so, there's a couple settings that I need to check in the BIOS. The first one under Advanced, CPU Configuration, I need to verify that the Intel Virtualization Technology is enabled. It should be by default, so that one should be okay. Under SATA configuration, I need to verify that the SATA Mode says AHCI, instead of RAID.
By default, it'll probably be set to RAID, so you do have to double check this one on the BRIX. Next, I need to check the boot settings. I need to make sure that my first boot option is the USB drive, and if I'm going to install to the SSD, then I need to make sure that the second boot option is the UEFI version of the disk. Notice it shows up twice, once as UEFI and once as P3. If it's selected as P3, then it's not going to boot properly. I'm going to install it onto the USB drive that I'm using to do the install, so the second boot option never matters.
Once I've verified that, save and exit. Yes, and it should now boot up into the ESXi installer. You may run into a problem at this point. If it says something about, can't load the video drivers, verify that the resolution of your monitor is not set too high. So I want to press Enter to continue, F11 to accept the license agreement.
Now at this point, all of ESXi is installed into memory. So I can install back to the same disk that I just used to load ESXi. This frees up the entire SSD for me to use as a VMFS volume to hold virtual machines. It does have existing data, and I want to go ahead and override it. Select the keyboard default. For the root password, I'm going to use VMR1 Bang for all of the passwords. If there is any possibility of your lab environment being exposed to the public, I recommend using strong passwords.
Press F11 to confirm the install. Once the installation is completed, it's asking me to remove the installation media, but since I just recorded over it, there's no need to do that. All I need to do is hit Enter to reboot. Once the ESXi host is booted, it'll bring us to this yellow and gray screen that's referred to as the DCUI, or Direct Console User Interface.
From here, we can do the initial configuration by pressing F2. Username is root. Type in the password that we set. And the first thing that we want to do is configure the management network. The vmnic0 is sufficient. It's the only adapter that we have on the BRIX. We don't want to set a VLAN in most cases. If you do have the ability to create VLANs in your environment, then you do have the option of doing so. We need to change the IP Version4 configuration.
Right now, it is set to dynamic, so it picked up that IP address off of the network, and that can work, in many situations. However, because it can change later on, it's nice if we can set it to something static. Just make sure that it's not being used anywhere else in your environment. So, I want to change this. And I can verify that that isn't being used anywhere else by doing a ping. Press Enter, and then, we need to edit the DNS configuration.
This information originally came from the DHCP server, so that should be sufficient. However, I want to change the Hostname here. Because this is my physical host, I'm going to call it pESXi65 for the version, dash one, just in case I later want to add a second one. And I'm going to be using lab.local as my domain. Press Escape, and it's going to verify that we want to apply the changes and restart the management network.
Hit Y for yes. Now, I want to go down to Troubleshooting Options, and I want to enable the ESXi Shell, and enable SSH. These will give us a warning later on, but it does allow for us to have faster access to the host. Now, I can press Alt + F1, and I can login to the host. And I can verify that my routing is working, esxcfg-route -l to look at the route, and then, I can try to ping the default router.
Now that I can ping the router, that's all we have to do from the console of the ESXi host. Now everything else, we should be able to do through the web interface. vSphere 6.5 no longer supports the Windows vSphere client, so we use the new built-in web interface to manage the ESXi host. To access the web interface, we simply go to the IP address of the ESXi host. It'll give us a warning about the connection not being private because we don't have a CA signed certificate.
Proceed past that. Once the login screen comes up, we'll log in as root, and the password we specified during install. The built-in interface looks very similar to vCenter Server so it should be easy to navigate. We'll close out all of the warning messages here. And the first thing that we want to do is add our datastore, so click on New datastore, create a new VMFS datastore.
We'll name it after the ESXi host. Go with the default partitioning options. Then, once the task is completed, our new datastore should show up in the list. The next thing we want to do is create a new port group to add our virtual ESXi host to. There's two reasons for creating a new port group. One is if we were using VLANs, we could put it on a separate VLAN.
The second reason is the security settings. Because we're going to be running a ESXi host on this port group, we need to allow Promiscuous mode, as well as MAC address changes and Forged transmits. I'll call it Host Network, click on Add, and now, we're ready to begin installing the components of our lab environment.
- Virtual machine benefits
- Building a lab environment with a mini PC
- Working with ESXi and vCenter Server
- Installing a control center VM
- Using the HTML5 client and the web client
- Adding an ESXi host and use Remote Console
- Configuring vSAN and storage profiles
- Adding NFS datastore
- Deploying a virtual machine from OVA
- Performing a cloning operation
- Using templates
- Performing a vMotion migration
- Working with snapshots