How to Install vRealize Operations

First step is to obtain the vRealize Operations Manager Appliance and install it via your VMware server.  Once the Appliance is uploaded and the installation is complete you will see the below screen on your VM.

2.PNG

Once you go to the URL you will find the Initial Setup screen.

1.PNG

I chose new Installation and started by setting the Administrator’s Password.

3.PNG

I then accepted the default certificate.

4.PNG

I named my Cluster Node.  We can add additional nodes later.

5.PNG

I then completed the install by clicking Finish.6.PNG

Now we wait, the Appliance will configure itself.

7.PNG

Then we need to start vRealize Operations Manager

8.PNG

9.PNG

Eventually the Node will show a State of Running and Online.

10.PNG

Once the node is up and running you will have to login

11.PNG

Note that the login username is admin and not root.

Now we have to do more configuration.

12.PNG

Accept the EULA, enter our Product Key, and opt in or out of CEIP.15.PNG

13.PNG

14.PNG

15.PNG

Finally we configure the installation.

16.PNG

First in order to gather information of our VMs and ESXI servers we need to configure the vSphere Adapter.

17.PNG

18.PNG

20.PNG19.PNG

20.PNG

Once the adapter is configured you should see Collecting.

21

For a time you will see your items in a grey color while the information is aggregated.

22.PNG

After a while you see the aggregation working and less and less grey.

Capture.PNG

Advertisements

How to Apply Updates to VCenter 6.0

Starting after Update 1 for VCenter 6.0 you are able to update your Vcenter from the Web Interface.  Unfortunately for me, I have pre-version one installed so I need to update via SSH.

First step is login via SSH to your VCenter as the Root User using your SSO Administrator User and password

Capture.PNG

Next you download the Update for your VCenter from here.

Once the update is downloaded, you will need to mount the ISO to your VCenter VM.

Then we execute

software-packages install –iso –acceptEulas

Capture.PNG

The update will inform you when completed and instruct you to reboot

How to Install VSphere Appliance 6.0

There is only so many installations of a Windows or Linux box you can do before you ask yourself if there is any easier way to do this.  In order to use templates and automate your VM building tasks, one of the choices is to use Vsphere with a variety of tools that plug in like Vagrant, Chef, or Puppet.

First we must acquire the VCSA 6.0 ISO and have a VM or other Windows Host on which to run the VSphere installer from.  For me this is just my Windows 10 Laptop.

First we browse the ISO to /vcsa/VMWare-ClientIntegrationPlugin-6.0.0.exe and install the Plugin.  This is needed to run the installer which is Web Browser Based.

Once installed Capture.PNGwe open vcsa-setup.html

Capture.PNG

 

 

 

 

 

 

 

 

On Internet Explorer, you will be prompted twice to accept the Client Integration Plugin Access to your system.   Accept the access and you will see the Install Window for vCenter Server Appliance 6.0

Capture.PNG

Capture.PNG

First we click Install and Accept the License AgreementCapture.PNG

Then we enter the IP, User, and Password for our ESXi Host

Capture.PNG

You will be prompted to trust your SSL Certificate, and since its the default install certificate it will be for localhost.localdomain.  If you have changed your hostname it won’t match and won’t be trusted.  You can click Yes to accept and continue.

Capture.PNG

The installer will Validate your setup and if any connection issues are found, it will let you know.  Then it asks you to set the appliance name, and OS Password.  Set these as appropriate.  When setting the OS Password be sure to have an uppercase, lowercase, and special character as it is required by the installer.

Capture.PNG

For our installation, since it is such a small VCenter Install, we are going to go with the Embedded Platform Service Controller.

Capture.PNG

Next we create our SSO or Single Sign On Domain.  If you plan to have Active Directory Integration, you need to be sure that your Domain Name and Site Name are different than your Active Directory Forest Name.

Capture.PNG

Next you pick your Appliance Size.  The Tiny Size fits our installation well, but just incase we decided to bigger, I have decided to go to the Small Size.

Capture.PNG

Next Select your Datastore.  Be sure there is enough space to fit your VMs.  The Installer states 150GB is needed, so I have chose a Datastore that has at least that.  I have also enabled Thin Disk Mode as it only allocates storage as needed.

Capture.PNG

We chose the embedded database.

Capture.PNG

We chose the appropriate Network Settings.  Since my entire homelab is 10Gbe, I want to be sure that I am using a 10gbe Virtual Switch/Network.

Capture.PNG

The installer will warn you not to use DHCP, but if you do reservations of DHCP address you will be fine.  Finally accept the Customer Improvement Settings and Finish the installer so that it can build your VMs.  If you want to see how the installer is doing, hop over to your Web Page for your ESXi host.

Capture.PNG

Once the VM is built you can also watch it do the installation.

Capture.PNG

Once it’s finished, verify you can login and off you go!

Capture.PNG

No 10gbe NICs showing in VMware 6.X with X10SDV-7TP4F

When I started building my VMware ESXi server, I did not have a Switch that could handle 10Gbe SFP+.  Now that I have a Dell X1052, I figured I would cable up a 10Gbe DAC and get moving.  Much to my surprise, I received a link light on the switch, but not on the motherboard.

Capture.PNG

Digging into the VMware side, I noticed that the 10Gbe NICs are not available, only the 1Gbe NICs.

Capture

A quick Google search brought me to a great site for VMware knowledge, tinkertry.com.  It appears that the drivers for the 10Gbe are not loaded.  So following the directions here, we open the SSH Console and enter the following command.

esxcli software vib install -v https://cdn.tinkertry.com/files/net-ixgbe_4.5.1-1OEM.600.0.0.2494585.vib –no-sig-check

We then reboot our host to get the new VIB to be loaded.

Capture

Low and behold on reboot we see the two 10gbe NICs.

Capture

Easy ESXi Patch Updates

If you are not familiar with v-front.de and you have a ESXi servers, you are really doing yourself a dis-service.  v-front.de maintains a repository of all ESXi updates and makes it very easy for you to update your servers when the newest patches come out.

Lately I have been having a series of interested GUI crashes with ESXi no matter what OS or Browser I use.  Knowing I was a bit behind on patches, I decided to update.

From their patching site I was able to grab the latest software profile and install it.  The steps are easy to do this and I will detail it here.

    1.  Enable the SSH Shell for your ESXi Host. At the Host Tab, click Actions -> Services – Enable Secure Shell (SSH).
    2. Going to the patching site and clicking on the latest update, v-front.de lists us the steps how to update our host.
      esxcli network firewall ruleset set -e true -r httpClient
      esxcli software profile update -p ESXi-6.5.0-20170404001-standard
      -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
      esxcli network firewall ruleset set -e false -r httpClient
    3. Reboot and then verify that the vibs have updated
      [root@esxi:~] esxcli software vib list | grep esx-base
      esx-base                       6.5.0-0.19.5310538                    VMware    VMwareCertified     2017-05-13
      [root@esxi:~] esxcli software vib list | grep esx-ui
      esx-ui                         1.18.0-5270848                        VMware    VMwareCertified     2017-05-13
      [root@esxi:~] esxcli software vib list | grep vsan
      vsan                           6.5.0-0.19.5310540                    VMware    VMwareCertified     2017-05-13
      vsanhealth                     6.5.0-0.19.5310541                    VMware    VMwareCertified     2017-05-13

Cannot Create Datastore on VMware ESXi 6.5

I have been in the process of rebuilding my Plex Server and restoring the data.  I popped in four 4TB WD Red NAS Drives and attached them to my 12G Controller.  I figured it would be easy to create a datastore across the Raid 5 Drive and contine on my way.   Unfortunately that was not the case, and I kept recieving errors similar to the one seen below.

Snip20170417_1.pngWhile rather annoying, what I believe happens is that the Drives had a previous partition on them that ESXi just can not read or write to.  So what we have to do is do some configuration in the ESXi Shell.

First we need to enable SSH on this host, which is very simple.  At the Host Tab, click Actions -> Services – Enable Secure Shell (SSH).  ESXi will enable the service and pop up a reminder warning for you.

Snip20170417_2.png

Next we SSH into our ESXi Host.

Snip20170417_3.png

We then need to determine the Disk ID of the Device we wish to fix.  For us this is easy, as ESXi appends this to the name of the Device under Storage ->Devices. Snip20170417_4.png

From there we go back to the Shell and cd to /dev/disks where we should see a bunch of disk IDs.

Snip20170417_5.png

Then we run partedUtil mklabel /dev/disks/diskid msdos

Snip20170417_6.png

Then we run through the steps to create the new Datastore and after a bit of a wait we should see the new Datastore created.

Snip20170417_8.png

So there we have it, we have our Plex Datastore and I can create my new disk and start sharing my Media much to my fiancee’s enjoyment.   She has really missed her Power Rangers.  Also don’t forget to turn off SSH access for safety’s sake.

 

 

Hardware Passthrough in VMware ESXi 6.5

VMware ESXi 6.5 continues to improve the simplicity of using its platform more and more as new editions come out.  Today I’ll show you how simple it is to passthrough a hardware device to a VM.

In this case we are going to passthrough the motherboard disk controller, and LSI 2116 to a VM in order to work on a disk that I will write about in a later post.

From the main ESXi home page we click on Manage and then Hardware.

Snip20170328_1.png

You will be presented with a long list of all the hardware components that your system presents to ESXi.  For our purposes we need to find the LSI 2116 Controller.  Click the checkbox next to the device and you will get a notification stating you need to reboot in order to enable the passthrough of this device.

Snip20170328_2Snip20170328_3

Now we simply reboot the system.  Once the system is back up we take the VM we wish to use the hardware on.  Simple Edit the Settings on the VM and Click Add other Device and Select PCI Device

Snip20170328_5

Then we chose or device from the drop down.  For us, since we only have this one device passed, that is the only choice.   Save the configuration and you will clearly see the device added.

Snip20170328_7.png

In our case we have added a 10K Disk to the Storage Controller that has a unique setup on it, but more on that later.  Once we’ve booted an OS, or in our case the CentOS 7 Installer, I am happy to see that the disk shows up.

Snip20170328_8.png