Archives for 2017

Nutanix VirtIO 1.1 Drivers Released

If you are a Nutanix customer and using AHV (Acropolis Hypervisor), I have some great news for you. We have released VirtIO 1.1 drivers, and the big deal is that they are now Microsoft WHQL signed. I know the lack of signing was holding back some customers for production workloads. No longer!

VirtIO 1.1And there’s a nice Nutanix install wizard:

Nutanix VirtIOPlease do note, this signed driver package is for 64-bit operating systems only. The supported operating systems are:

  • Windows 7
  • Windows 8.x
  • Windows 10
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

You can directly download the drivers from here. We have them in both .MSI format and ISO, depending on your needs. All of the related documentation can be found here, including the special case of 32-bit operating systems. And don’t forget, if you want to inject the VirtIO drivers into your Windows ISO, check out my blog post here.

Nutanix AOS 5.1 & Companions are now GA

For the second time this year, Nutanix has released a major feature upgrade to AOS and companion software. Now available, is AOS 5.1! Top of the list of new features is vSphere 6.5 support for NX platforms (Nutanix branded gear). vSphere 6.5 support for OEM platforms is coming soon. But that’s not the only new feature. Here’s a rundown of some (not all) of the new features:

  • 1-click controller VM (CVM) memory upgrade
  • XenServer support on NX-1065-G5, NX-3060-G5, NX-3175-G5 (optionally with NVIDIA M60)
  • All-flash clusters now support adding hybrid nodes (e.g. cold storage only nodes). Minimum 2 AF nodes.
  • Automatic “admin” account password sync across all CVMs, Prism Web console, and SSH interfaces.
  • Docker container management through self-service portal.
  • Prism 1-click feature to install Docker host VM
  • Post-process compression is enabled by default on all new containers with Pro and Ultimate licenses
  • 1-click centralized upgrades from Prism Central
  • 1-click Prism central cluster registration and Prism Central Deployment
  • Pulse (telemetry) enabled for Prism Central
  • Auto-resolved alerts
  • User defined alerts
  • Graphics and compute mode for NVIDIA M60 GPU
  • CHAP authentication for Acropolis Block Services
  • Hot-plug CPU and memory on AHV VMs
  • Metro availability and synchronous replication supported across hardware vendors (NX, Dell, Lenovo). Async support continues.
  • VirtIO drivers updated to v1.1
  • Dynamically increase EC-X strip size as cluster is expanded
  • Much improved storage efficiency reporting in Prism (compression, dedupe, EC-X, etc.)
  • Disk rebuild time estimation
  • AFS supports Mac OS v10.10, v10.11, v10.12
  • Acropolis Block Service enhanced OS support (Solaris 11, RHEL 6, 7, 6.8)

Tech Preview Features include:

  • Software only support for UCS B-series blades
  • GPU pass-through for AHV guest VMs
  • Support 3rd-party network function VMs (e.g. load balancer, firewall, etc.) routed through Open vSwitch (OVS).

Companion Software Updates

  • Prism Central 5.1
  • Acropolis File Services (AFS) 2.1
  • Acropolis Container Services (ACS) 1.0
  • Foundation 3.7.2

Helpful Links

As of 5/1/2017, AOS 5.1 has not been enabled for automatic download and 1-click upgrades. As always, if you don’t want to wait for the automatic download switch to be flipped (in the near future), you can grab the AOS binary from the support portal and use our 1-click upgrade process. As always, thoroughly read the full release notes on the support portal before attempting an upgrade.

Nutanix AHV (Hypervisor) Update Released

Fresh off the press, is an updated version of the Nutanix hypervisor, AHV. Today we released AHV-20160925.43. Features include broader support for the AOS 5.0.x family, and a tech preview feature of hot plugging memory and CPU on VMs. A number of bug fixes were also incorporated. Noteworthy, is a network stack issue that has been fixed. This issue could be experienced by any customer, so upgrading is encouraged.

If you are using AHV, you are encouraged to check out the release notes here. AHV is 1-click upgrade enabled, so you can easily update your cluster in an automated fashion with no VM downtime.

 

VMware Horizon 7.1 is now GA

About a month ago, VMware released news of an updated version of Horizon, version 7.1. As it turns out, the day it was announced I was at a customer site doing a Horizon install and they were all excited about the 7.1 features. They were most interested in Blast Extreme with the adaptive transport. Now, the wait is finally over to get your hands on the bits. In case you missed what’s new 7.1, check out this great VMware blog post here.

A small sample of new features includes:

VMware Blast Extreme
URL Content Redirection Enhancements
Horizon for Linux 7.1 Desktops Enhancements
Improved Smart Card Authentication
Enhanced Instant Clones
Pod Cloud Architecture Enhancements
ADM and ADMX Template files
Enhanced IPv6 Support

And more!

Full release notes are here.

VMware Workstation/Fusion and vSphere 6.5b Released

Hot off the press, are three updates for VMware products. First, Workstation Pro 12.5.4 was released, which addresses a critical security issue. According to VMware “This vulnerability might allow a guest to execute code on the operating system that runs VMware Workstation 12 Pro.” You can read the full release notes here. The dowload is available here. Fusion was also struck by the same bug, and has been updated to 8.5.5. Those release notes are here.

Applicable to a broader audience, is a minor patch release for vSphere 6.5, called vSphere 6.5b. Not much is “new”…just enhancement to timezone features, and additional HTML5 Web client functionality. A number of bugs are addressed, which is to be expected. One notable change is that users without any vCenter permissions are now not able to login to the web client. Previously, any user (typically via AD) could login to the web client but they would not see any inventory since they had zero permissions. Now, unless you have explicit vCenter permissions it will not allow you to login.

The full vSphere 6.5b release notes are located here.

Critical Zerto 5.0 update for Nutanix customers

If you are a Nutanix customer, and using Zerto, Zerto has release a very critical patch. Unpatched, the bug could result in data integrity issues. This has been seen in the field, particularly with Microsoft SQL. So it’s very imperative that you review the Zerto release notes and upgrade to Zerto 5.0 U2 ASAP.

The issue manifests itself during CVM failover operations and result in lost writes.  These failover operations are normally transparent to the guest, and in no way interrupt the normal I/O data path. The Nutanix business critical apps team was able to reproduce the issue in house at will, and confirmed Zerto 5.0 U2 has resolved the issue. Zerto is a great partner, and they were extremely helpful in resolving this issue. The issue is not exclusive to SQL, but is more readily apparent since DBAs do routine integrity checks which will fail if the bug has been triggered.

I do not know if versions prior to 5.0 U2 (such as the 4.x version) will receive the patch. Check with your Zerto account team. If the patch won’t be back ported, then you need to plan on upgrading to 5.0 U2 ASAP. We have many joint customers, that absolutely love the Zerto features coupled with Nutanix simplicity.

My boss, Michael Webster, also has a write up about this issue which you can find here.

Nutanix AOS 5.0.1 enabled for 1-click upgrades

Earlier this year Nutanix released AOS 5.0, which contained dozens and dozens of new features and enhancements. As Nutanix customers know, we have 1-click upgrades for AOS. Prism will automatically notify you when there is an updated AOS version available. While customers can immediately download new releases from the portal and use 1-click upgrades, Nutanix delays the automatic notification on major releases until the first maintenance release comes out. This allows customers that want the absolute latest code to download it manually, but gives more conservative customers time for the release to mature before it’s automatically downloaded by Prism.

As of this week, AOS 5.0.1 will now automatically appear in Prism as a 1-click upgrade option. So if you have been holding off on AOS 5.0 until the first maintenance release, you need not wait any longer. Check Prism for software updates and you should see AOS 5.0.1 available.

Released: Nutanix AOS 4.7.5 and other tools

Nutanix has released an updated version of the AOS 4.7 family, which is now bumped up to AOS 4.7.5  If you have already upgraded to AOS 5.0.x, which came out earlier this year, you can ignore this post. Those of you with Nutanix support portal access can download the 4.7.5 release notes here. Since this is a minor release, it’s mostly bug fixes and minor new features. One new feature that is noteworthy, is a new 1-click SATA-DOM firmware upgrade feature for Nutanix NX and Dell XC platforms with hypervisors other than Hyper-V. Nutanix takes security extremely seriously, and as such, this update addresses a variety of CVEs. So even if the new features or other bug fixes don’t seem all that interesting, personally I would recommend the upgrade due to the security patches.

In addition to AOS 4.7.5, minor revs to related products are out as well:

  • Prism Central 4.7.5 can be downloaded here. The Prism Central release notes are available here and the Upgrade Guide is available here.
  • Nutanix Cluster Check (NCC) is now at version 3.0.0.2. It can be downloaded here and the release notes can be found here.
  • Foundation 3.7, which is the Nutanix Cluster deployment tool, is now out. Download Foundation 3.7 here and read the release notes here.
  • AHV version 20160601.50 which can be downloaded here and the upgrade instructions can be found here.

Nutanix customers really enjoy the 1-click upgrade for many components, so when we release a new batch like this, it takes minimal time to update the environment. And no VM downtime is required, which makes scheduling maintenance windows easier.

Microsoft SQL 2016 Unattended Install

Continuing my 2017 series on unattended Microsoft SQL installs, this post will cover SQL 2016 on Windows Server 2012 R2. If you want the unattended install for SQL 2012, check out my post here or for SQL 2014, go here. I’m using the same drive configuration for SQL 2016, as I did for 2014. These drives are:

C: OS
D: SQL Binaries
K: SQL Databases
L: SQL Logs
T: TempDB
Z: CD-ROM

So let’s get started on getting SQL 2016 installed via an unattended script. New to SQL 2016 is the removal of the .Net Framework 3.5 dependency. However, you must be running SQL 2016 CU2 or later per this KB article to resolve a database mail issue. You can easily install the baseline SQL 2016 via this unattended install, then download and install the latest CU or Service Pack afterwards. I’m assuming you have your various drives mounted, formatted, and ready to go. Next, download the two files below and save them to the root of your D drive.

SQL-2016-base.ini
SQL-2016-base.cmd

1. Open the SQL-2016-base.ini file with your favorite editor and modify all of the paths. They are sprinkled throughout the file, so be sure to check every line. New to SQL 2016 is the ability to customize TempDB files during the installation process. This allows you to follow SQL best practices and optimize the performance of SQL out of the gate. This is a great improvement. As you can see from the snippet below, there are various TempDB parameters you can tweak. All environments are different, so adjust these parameters as necessary.
2017-03-01_13-39-242. Save the ini. If your CD-ROM is not using the Z: drive, open the SQL-2016-base.cmd file and change the path as needed. If you aren’t using a D drive and have these scripts elsewhere, change the path to the ini file.

3. Open a command prompt and run the SQL-2016-base.cmd file with an argument of the group which you want to be added to the SQL studio to administer the instance. Use the format domain\group. If you just want a local group, you can use BuiltIn\Group. Note: This is a change from SQL 2012/2014 where you could use MachineName\Group.

2017-03-01_13-44-124. Sit back and relax, and give it 10 minutes or more. You will see the SQL installer GUI flash through various screens in an automated fashion. If the install was successful, at the end you should see the following status. Setup result 3010 means you need to reboot the VM. Reboot the VM now. If you don’t reboot with the setup code 3010, then the next piece we install will fail.

2017-03-01_13-45-265. Unlike previous versions of SQL, the main installer no longer has the SQL Studio components. So you can’t perform a single unattended install and come away with a working SQL Studio configuration. So, go back to the mounted SQL 2016 ISO and click on Setup.

6. In the left pane click Installation. In the right pane, click on Install SQL Server Management Tools. This will not launch the tools installer, but will rather redirect you to a Microsoft webpage here to download the latest version of the SQL management studio.

2017-03-01_13-48-41

7. After the download has completed, I find it best to launch it the old fashion way and use the GUI. Click through the wizard and wait for the install to complete. If you do want to launch it via the command line, you can use the following switches:

SSMS-Setup-ENU.exe /install /passive /norestart /log log.txt

However, there is no visual indication of what is going on and the command appears to instantly complete. So the only way you know what’s going on is by looking at the log and waiting for the install to complete. Frankly, I’d rather watch a GUI than monitoring a log file.

And there you go! Due to Microsoft changes in the installer, installing SQL 2016 is slightly harder due to the separate SQL Management Tools installer. But, even so, that’s only an extra 5 minutes of work.

Microsoft SQL 2014 Unattended Installation

Continuing my 2017 series on unattended Microsoft SQL installs, this post will cover SQL 2014 on Windows Server 2012 R2. If you want the unattended install for SQL 2012, check out my post here. I’m using the same drive configuration for SQL 2014, as I did for 2012. These drives are:

C: OS
D: SQL Binaries
K: SQL Databases
L: SQL Logs
T: TempDB
Z: CD-ROM

So let’s get started on getting SQL 2014 installed via an unattended script. First, SQL 2014 requires .NetFramework 3.5. Unfortunately, in the basic Windows Server 2012 R2 install, this is an optional feature that is not installed. Frankly I think the easiest way is via the GUI, although you can use PowerShell as well.

  1. Open the Add Roles and Features wizard.
  2. Click through the wizard until you get to the Features section.
  3. Expand .Net Framework 3.5 Features and tick the box next to .NET Framework 3.5. 2017-02-28_14-52-04
  4. Click Next, then enter the path to the .Net Framework 3.5 binaries. At this point, mount your Windows Server 2012 R2 ISO to the VM, then use the path CD-Drive:\sources\sxs2017-02-28_14-53-34
  5. Wait for the installation to complete, and just to be safe, reboot the VM.

At this point .Net Framework 3.5 is installed, and I’m assuming you have your various drives mounted, formatted, and ready to go. Next, download the two files below and save them to the root of your D drive.

SQL-2014-base.ini
SQL-2014-base.cmd

Open the SQL-2014-base.ini file with your favorite editor and modify all of the paths. They are sprinkled throughout the file, so be sure to check every line. Save the ini. If your CD-ROM is not using the Z: drive, open the SQL-2014-base.cmd file and change the path as needed. If you aren’t using a D drive and have these scripts elsewhere, change the path to the ini file.

6. Open a command prompt and run the SQL-2014-base.cmd file with an argument of the group which you want to be added to the SQL studio to administer the instance. Use the format domain\group. If you just want a local group, you can use MachineName\Group.

2017-03-01_12-41-26   7. Sit back and relax, and give it 10 minutes or more. You will see the SQL installer GUI flash through various screens in an automated fashion. If the install was successful, at the end you should see:

2017-02-28_16-02-58

And there you go! If you are installing multiple SQL servers using the same configuration, I highly recommend the unattended method.

© 2017 - Sitemap