VSAN does not see all disks due to previous partitions

During my testing out of VSAN I ran into an issue where VSAN was unable to see all of the disks in the box.  This can occur if there was something loaded on those disks.  The way around this is you need to SSH into the server and list the disks to see if there are partitions.

Step 1: List the disks and look for parititions.  Below you can see there are 2 partitions on this disk.

ls /dev/disks/naa*
/dev/disks/naa.600605b00896b6e01acf437ab22efc8e /dev/disks/naa.600605b00896b6e01acf4384b2c815fa
/dev/disks/naa.600605b00896b6e01acf437ab22efc8e:1 /dev/disks/naa.600605b00896b6e01acf4384b2c815fa:1
/dev/disks/naa.600605b00896b6e01acf437ab22efc8e:2 /dev/disks/naa.600605b00896b6e01acf4384b2c815fa:2

Step 2:  Delete all the partitions

partedUtil delete /dev/disks/naa.600605b00896b6e01acf437ab22efc8e 1

After this you may need to disable and re-enable the VSAN check box to see the new disks.


Back to Basics: Troubleshooting VM Network Connectivity

Sometimes those of us that have been doing virtualization for a while forget that others that haven’t been doing it don’t always know where to look at.  So, in this post I am going to go over the things to check when you are having issues connecting to a VM.

1.  First step to check is whether the OS has the proper network information, ip, gateway, subnet to get out.


2.  If step 1 is good, you then want to check under the settings of the VM and make sure that the virtual nic is connected.


3.  Next, check to make sure you are connected to the proper virtual network.  If you have a standard switch and a VDS, make sure you select the right one.

network2  4.  Make sure that your portgroup is configured correctly and your switch has physical uplinks connected.  Check that the VLAN ID is correct.network35.  Final thing to check is whether the VLAN is authorized and ports enabled for the physical port that the phsycial NIC is connected to.

6.  Beyond this you would need to check the physical switch configurations to make sure it is configured properly for the traffic.

Vsphere 6 Announced!

This has been a crazy year for me both personally and professionally.  I was just awarded the vExpert 2015 award and I am greatly honored.  I am hoping to get more posts out this year so I can keep it running.

First post of the year will obviously cover some of this new announcement.  There are many changes and many of the experts in the industry have done a lot of work so I will just be compiling the list of links here.  As I get more acquainted with the technology and involved I will begin making more posts about it.

Vsphere 6 Announcement: https://blogs.vmware.com/vsphere/2015/02/announcing-vsphere-6.html?src=vmw_so_vex_mjone_319

vExpert Vsphere 6 compilation list: http://blogs.vmware.com/vmtn/2015/02/vsphere-6-0-vexpert-blog-articles.html?src=vmw_so_vex_mjone_319

28 Days of February Announcements: https://onecloud.vmware.com/?cid=70180000000NktD&src=socialmedia_15Q1_vmw28days_US_28_og_GP#sf36045131?src=vmw_so_vex_mjone_319

Vsphere 6 What’s New: https://www.vmware.com/files/fr/pdf/vsphere/VMware-vSphere-Platform-Whats-New.pdf?src=vmw_so_vex_mjone_319

Here is a brief list of changes:

– Clusters can now support up to 64 hosts

– Vmotion enhancement: Long Distance Vmotion, Cross Switch Vmotion, and Cross Vcenter Vmotion

– Fault Tolerance Enhancement: Up to 4 vCPU’s supported

-VVOLS – VM-aware storage arrays

-Content Library – a new way to store templates/isos in a central repository that all Vcenters can use.

Temporarily adjust the Customization Wizard missing from Web Client

It was brought up on the forums earlier this year and I have confirmed that this is an issue in Vsphere 5.5 U1.  There is an option in the C# thick client when trying to deploy a VM where you can select the a Customization Spec and then choose to temporarily adjust before deployment.  See screen below:



This is a great option for those that want to keep most of the details, but maybe want to just change the IP address. This option appears to now be gone in the web client.  So, until it is resolved users will have to continue using the thick client for this.

If you look at the screenshots below, you can attempt to choose that option, but it takes you to a screen to create a brand new PERMANENT customization spec.  I plan on following up with VMware to determine if this was by design somehow.





Automated ESXi Cisco UCS Firmware Upgrade using Powertool

I have completed a script that will allow you to put a host into maintenance mode, verify service profile based on MAC address, and then change your firmware policy.

Requirements for the Script:
Cisco Powertool 1.x or later
Vmware Powercli 5.x or later
Maintenance Policy is User Ack
Ensure your VMNIC0 is matched up with your first Vnic template in order.

In line 34 you will need to modify the hardcoded VNIC to whatever you have named as your 1st PCI vnic on your Service Profile Template. This also assumes you have connected to UCS manager in a Powertool window.

Now for the script!
Read more of this post

VisualESXtop Installation/Usage

So, I was reading the tech blog o’ sphere recently and came across a fling I’d heard a bit about, but hadn’t really looked at. I just recently downloaded it and I have to say it is pretty cool for a V1 release.

The VMware Fling I am talking about is: Visual ESXTop

What is Visual ESXtop? It is a java based gui that will give you real time data just like ESXTOP without having to use resxtop on yoru VMA or directly onto the host. That’s right, you can run this from your linux or windows desktop.

Where can I get it? http://labs.vmware.com/flings/visualesxtop

How do I run it? First, extract the folder to the directtory of your choosing. On windows, you will need java (1.6) although I got it working with 1.7 and you need to put java into your path Variable.

Read more of this post

VCenter 5.0 to 5.1 U1 Upgrade while Separating or Splitting out Services (Part 2): Web Client upgrade

In part 1 we installed SSO and we will now install the web client.  This step does not have to be done next, but I recommend it because it will allow you to login with your domain credentials as you install things and you can see services being registered.I have the Web Client currently running on our Vcenter server so that when logging into the Web Client and the Vcenter Application server are same name and it is an easy transition to using the web client.  You can split out the web client onto it’s own server and uninstall your old web client later, but for this guide we will assume you are upgrading your existing installation.  The install will require a reboot so if you need to put in change control or let users know before upgrading now is the time to do so.

A couple items to note prior to installation:

a. Any local groups will not be imported into the permissions for your new Vcenter once that is upgraded.  All other permissions and groups should get imported during the Vcenter upgrade.

b.  For an upgrade, it should recognize the domain source that the server you install on is joined to.

Let’s get this going!
1.  Log onto your vcenter or your current web client server and run the installer for the Web Client from your 5.1 U1 Vcenter download.  Hit next.



2.  Keep default ports or set the ports for connecting to the web client and hit next.


3.  Enter the password for the default user you created during the SSO install and the FQDN of your SSO server that was built.


4.  Install the default certificates for the web client.  You can replace these at a later date with your CA signed certificates using the SSL Automation Tool provided by VMware, but I have found that self signed are sufficient for most organizations.


5.  Choose install and wait for the install to complete.




6.  Restart your system or choose no and restart when available.


7.  Installation is done, but you will want to set your Default domain so that when you upgrade the Vcenter Service you will be able to login.  Go the the web browser https://FQDN.webclient.com:9443 and login with the default username admin@system-domain and the password you set.


8.  Click on Home -> Administration -> Configuration.  Your Identity source for your domain should already be listed there.  On the bottom under Default Domains make sure your domain is down there and move it to the top of the list and hit the save button


9.  If you ever have an issue, you can always login with admin@system-domain.

Part 3 will be to install the Inventory service on it’s own server.  Don’t worry about the existing Inventory service, we will remove that during the Vcenter Service install.