VMware has today announced VSAN. Here are some highlights from the Q&A session:
- VSAN will be GA at March 10 2014
- vSphere 5.5 Update 1 will support VSAN GA
- Beta VSAN upgrades to the GA release are not supported
- VSAN is not a VSA. Performance is much better than any VSA
- Pricing and packaging will covered on the GA date
- Performance of VSAN scales linear as you add more hardware (extra nodes with storage)
- Initial release of VSAN requires SSD and HDD. So using only SSD disks and no HDDs it not possible
- VSAN use cases are for example: VDI, Tier 2/3 workloads and Disaster Recovery cases
- VMware Horizon View will be supported in the GA release
- The minimum for VSAN is 3 ESXi nodes and the maximum is 32 nodes
- The minimum is 1 HDD and 1 SSD. The maximum is 35 HDDs and one SSD per 7 HDDs
- Minimum NIC speed is 1 Gbps, recommended NIC speed is 10 Gbps
- Replication is synchronously
- Every seven HDDs needs a SSD. SSD and HDD Ratio is 1:10 (GB)
- No de-dupe is supported in the GA version
- Hardware vendors such as Dell, HP and Cisco will support VSAN as VSAN Ready nodes. Watch the VMware Compatibility Guide at GA. Link
- You can build your own VSAN with certified hardware
- There will be 13 pre configurations solutions available on the GA date
- JBOD is not supported in the GA release
- What is the difference with MS storage spaces: MS Storage spaces is presenting a file server from dedicated servers and JBODs. VSAN is object storage and doesn’t require dedicated servers, it uses the same servers you have for your compute, and other benefits like flash cache acceleration, storage policy management and automation and more.
Last week ik blogged about the “Broadcom adapter data corruption on ESXi/ESX hosts using the tg3 driver and TSO enabled” NIC problem. Link This week I found two new vSphere NIC issues worth to mention:
Eric Siebert of “vsphere-land” opened the yearly voting for the best VMware and virtualization blogs available. This year there are over 300 blogs that participate in the contest. When casting your votes please keep the following in mind:
- Longevity – Anyone can start a blog but it requires dedication, time & effort to keep it going. Some bloggers start a blog only to have it fall to the wayside several months later. Things always come up in life but the good bloggers keep going regardless of what is happening in their life.
- Length – It’s easy to make a quick blog post without much content, nothing wrong with this as long as you have good content in the post that people will enjoy. But some bloggers post pretty long detailed posts which takes a lot of time and effort to produce. The tip of the hat goes to these guys that burn the midnight oil trying to get you some great detailed information.
- Frequency – Some bloggers post several times a week which provides readers with lots of content. This requires a lot of effort as bloggers have to come up with more content ideas to write about. Frequency ties into length, some do high frequency/low length, some do low frequency/high length, some do both. They’re all good and require a lot of time and effort on the bloggers part.
- Quality – It all comes down to whats in the blog post regardless of how often or how long the blog posts are. After reading a blog post if you come away with learning something that you did not previously know and it benefits you in some way then you know you are reading a quality post. Good quality is usually the result of original content, its easy to re-hash something previously published elsewhere, the good bloggers come up with unique content or put their own unique spin on popular topics.
Last year my blog ended on number 112. This year it is also listed:
So if you like my blog and all the great blogs around please vote (Veeam has great prices available when voting). You can vote by taking the survey here. Link. Voting can be done until 17 March 2014.
VMware has released a new KB article (2072515) on possible data corruption with Broadcom adapters that use the tg3 driver. This problem can occur when:
- The system is configured with greater than 4 GB RAM
- TCP Segmentation Offload (TSO) is enabled on the adapter
- The system is running ESXi/ESX 3.5, 4.x, 5.0, 5.1 and 5.5
- The tg3 driver version is less than v3.135b
The advice is to update to the latest tg3 driver that fix the problem. If you are using Broadcom adapters you need to check the following components on your VMware ESXi hosts to determine if the data corruption problem can occur:
- What is the driver version of the Broadcom tg3 driver. All the tg3 drivers earlier than version 3.135b.v50.1 must be updated
- Is TSO enabled
Check the Broadcom tg3 driver version and if TSO is enabled
- Open a SSH session to the ESXi host.
- Get an overview on all the NICs installed in the ESXi server: esxcli network nic list
- Display the Broadcom tg3 driver version, command: vmkload_mod -s tg3 | grep Version
- Check if TSO is enabled, command: esxcli system settings advanced list -o /Net/UseHwTSO
Is the Int value equal to 1 than TSO is enabled.
So if the tg3 driver version is earlier than version 3.135b.v50.1 and TSO is enabled you need to update the driver!
Update the Broadcom tg3 driver (steps for updating an ESXi 5.1 host):
- Download the new tg3 driver:
- ESXi 5.5: version 3.135b.v55.1 (released on 12/27/2013) or later
- ESXi 5.0 / 5.1: version 3.135b.v50.1 (released on 12/27/2013) or later
- For ESXi/ESX 3.5/4.x, there is currently no fix. The only way is to disable TSO. For more information see the VMware KB article on the end of the blog post.
- Place the host in maintenance mode, command: esxcli system maintenanceMode set -e true
- Upload the driver to a datastore
- Install the updated driver, command: esxcli software vib install -d /vmfs/volumes/datastore location/tg3-3.135b.v50.1-offline_bundle-1502404.zip
- Reboot the host, command: reboot
- Check the tg3 driver version again, command: vmkload_mod -s tg3 | grep Version
- The tg3 driver must have the new versionn number
- Exit maintenance mode. Command: esxcli system maintenanceMode set -e false
Execute the steps on all the ESXi host that have tg3 drivers installed. The VMware KB article can be found here. Link
On Microsoft Technet you can find lists of available hofixes for Microsoft Windows 2012 and Windows Server 2012 R2 Hyper-V and Failover clustering. The following lists gives an overview of the latest hotfixes available per product:
- Windows Server 2012 R2 Hyper-V Hotfixes, Link
- Windows Server 2012 R2 Failover Cluster Hotfixes, Link
- Windows Server 2012 Failover Hotfixes, Link
- Windows Server 2008 R2 Cluster Hotfixes, Link
- Windows 7 VDI image hot fixes, Link
- Windows 2012 R2 hotfixes, Link
On GitHub is a PowerShell script available that checks the host for installed hotfixes and updates for Windows Server 2012 on Hyper-V and the Failover cluster. The script can be found here, Link
Note: Only apply hotfixes when experiencing the problem listed!