Install and configure Linux Virtual Appliance for DNS and NFS.
- [Instructor] My next step is to install the Control Center VM. The Control Center VM provides DNS and NSF services. DNS is necessary because vCenter won't install unless it has correct name resolution. If you already have a DNS server that you can configure, you can skip installing the Control Center VM. The Control Center VM is available as part of the exercise files that we downloaded as an OVF. So I need to create a VM. Deploy from an OVF.
We'll name it Control Center, and then click on the big blue box here and select the three files that make up the Control Center VM. Don't worry that it only shows two on the screen. They did actually all get selected. We'll select our local storage. Select the network that we want to connect to and make sure that thin is selected for disk provisioning. And then click on Finish. We can follow along in the task to watch the deployment.
Once the deployment has completed successfully, then I need to log on to the virtual machine to configure it. Notice it already started the VM for me. So I just select it and click on the window to launch the console. Log in as root, and you have to make sure that you've clicked inside of the window in order to be able to type. Log in as root, password is VMware1!. Capitol VM. Once we're logged in, we're going to have to configure the Control Center VM for our specific environment.
I've already configured it for 192.168.0 network, as that's a standard network for a lot of home routers. However, if your network is different then you'll have to reconfigure it. This is an openSUSE VM, so the tool we use for configuring it is called YaST. Type yast, and that'll bring up the console for us. We need to go to System, and then arrow over to the right side and go down to Network Settings. Now to navigate inside of YaST, the letter that is shown as highlighted, you can press Alt and that key in order to bring up that menu option.
You can also use Tab and Shift Tab to jump through all of the available options. So I need to edit my ethernet controller here. So I can press Alt I, and then Tab down to the IP address. For the network that I'm on today, the IP address is going to be 172.28.29.73. Then just Tab to next or hit Alt N.
Now I need to configure the DNS. The DNS that I configure here needs to be the Control Center VM itself. So once again, 172, and then I need to configure routing, Alt U. This will be the default gateway for your network. And then Alt O to save everything. Once the network settings are complete, I should be able to do the rest of it through SSH, which provides a slightly better interface.
So Alt Q to quit, and then start up Putty. I need to change the translation so that the in curses screen shows up correctly. So change it to iSO 8859 west Europe. And then I'm going to alter the appearance to make the fonts easier to read.
And then specify the IP address. I can also save it by typing in the name here and then clicking on Save. That way I can bring it up later on. Log in as once again, root. It may come up and ask you to save the key. Just click on okay to get past that screen. Now the Tab functionality works slightly better from inside a Putty session versus the console.
So that's why the switch. Now I need to go down to Network Services and configure my DNS server. Once again, it's currently configured for 192.168 network. So if you're using a different network, you'll need to make changes to it. Also, anytime you make changes, the DNS server has a habit of not starting up. So we need to set it back to start during system boot. First thing that we need to do is set up the forwarder. This will be where the DNS server's going to forward any requests that it does not have a response to.
So I just type in the address here. I'll delete the one that's in here, and then Alt D to enter the new address, 172. This will be the same DNS server that everything else on your network is using. If you're unsure, you can take a look at your network settings. Status, details.
Alt A to add. And then we need to configure our DNS zones. The first zone that we need to add is the reverse lookup. The reverse lookup zone has kind of an odd name. It'll be the first three octets of the IP address, followed by .in-addr.arpa. So in my case, that is 29.28.172.in-addr.arpa.
Click on Add, and then I want to delete the old one. Make sure you have the correct one selected. It does sometimes change the order on you, and Alt T to delete it. Alt I to edit the new one, and I need to add the name server, and this is just the name of the master server. Which is this one. So controlcenter.lab.local, Add, and then go back to basics, and I want to automatically generate these records from the lab.local.
So for every entry I put in there it's going to automatically create the reverse entry. So I just hit Spacebar to check that box there, and then Alt O for okay. Now I have to reconfigure lab.local. Alt I to edit, and everything should be configured correctly here except for the records. Notice these are all currently using 192.168.0 addresses. If you're on a 192.168.0 subnet, and all of these addresses are available, then you're done at this point.
For me I have to go through and change each one of these. So I tab to the value and put in the new one. 73, and then Alt A to add. Then I Tab down to the menu. Go and select the one that I want. And then Alt U to change its value, and you have to Backspace to remove the old value. Alt N to change the value.
Alt U to edit the setting again, and just go through and do this for all of the values in here so that they'll match what you're using on your network. Once all of the entries match what you want for your environment, Alt O to save them, and the last thing we want to do is start up the DNS server. So tab over to Start now. Now it shows the current status as running. So I can do Alt O to save my configuration, and then Alt Q to quit.
Now I should be able to type nslookup, and verify that I can look up the name of my control center. Notice that it failed. Let's go back into YaST and see what happened there. Notice that the name here got switched. When I added a forwarder to my DNS server it actually switched the name server in here.
So I need to change this back to what I had it as before. Which is 172.28.29.73. Alt Q to quit, run the same command again. And now Control Center works. I should also be able to reach in the address on the internet. The last thing that I need to do is fix DNS on my local system.
Because my local desktop is not configured to use the Control Center VM as its name server, it's not going to be able to find vCenter server by its host name. There's two possible ways that I can fix that. One is that I can go in and edit the settings in my IP configuration, and I can point it to the Control Center VM for the name server. The problem with that is if the Control Center VM needs to be shut down for any reason, name service is no longer going to work for my desktop. So a better solution is to add vCenter server into the host file of your local desktop.
To do this, I need to start up Notepad, and you have to start it in administrator mode. So right-click on it and run as administrator, and I want to open up the host file. The host file is under C Windows System 32 Drivers etc, and you'll have to change it off of text documents to all files, and then just open the file. At the bottom here, I want to add in the IP address of my vCenter server, and then press Tab and enter in the name of my vCenter server.
vCenter 65-1.lab.local, and then save this file. It's not necessary to enter in the names of the other servers, because we don't need to access them directly from the desktop. And now I'm ready to install my lab environment using the script.
- 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