Windows Unified Host Utilities 7.1 Release: New Features, Enhancements, and Known Issues, High school final essays of English

Download Windows Unified Host Utilities 7.1 Release: New Features, Enhancements, and Known Issues and more High school final essays English in PDF only on Docsity!

Windows ®^ Unified Host Utilities 7.

Release Notes

January 2018 | 215-12502_A0_UR [email protected]

Cannot add SCSI pass-through disk to SUSE Hyper-V guest using IDE

 - Converting a Hyper-V CSV LUN to enable live and quick migration - controller - booting Uninstalling SP2 from SAN-booted Windows Server 2008 prevents host from - I/O errors running iSCSI MCS with ERL=2 on IPv6 - iSCSI sessions do not reconnect after reboot with mixed IPv4 and IPv6 - MCS is not supported with iSCSI software boot - on the guest Raw (pass-through) disks on a guest OS are not available when running MPIO - Raw (pass-through) disks do not appear in Hyper-V guest OS - Guest OS install on SCSI disk fails - Hyper-V virtual machine files do not work on CIFS share - Hyper-V guest does not boot or loses pass-through disk - SUSE Hyper-V guest loses network when moved to another cluster node - Cluster Configuration fails when attempting to add a virtual machine to a Failover - Correcting a failed virtual machine addition - Ensuring virtual machines can be added to a failover cluster - Unable to add another virtual machine to a failover cluster - Virtual machine does not work after being removed from a failover cluster - Unable to SAN boot with Emulex FC HBA - system after disruption Microsoft iSCSI SW Initiator takes a long time to reconnect to the storage - Disabling the Microsoft iSCSI port-hopping algorithm - Initiator unable to log in to storage system - LUN identifier range 0-254 - MPIO and MCS are not supported together - I/O stops when removing iSCSI connections - Wait between iSCSI logout and login 

• Ways to view current and fixed product bugs
• NetApp product documentation - How to search for documentation on the NetApp Support Site - Links to NetApp product documentation
• Contact technical support - Things to check before you call technical support - Information you must provide to technical support - How to contact NetApp technical support
• Copyright information
• Trademark information
  • notifications How to send comments about documentation and receive update

Windows Unified Host Utilities 7.1 Release Notes

These release notes describe features, enhancements, and known issues in Windows Unified Host Utilities 7.1. These release notes apply to Windows Unified Host Utilities 7.1. Release notes might be updated between product releases. You should periodically check online for updated release notes. Release notes are available in .html and .pdf formats. They are optimized for .html viewing and linking.

Windows Unified Host Utilities 7.1 overview

The Windows Unified Host Utilities enable you to connect a Windows host computer to NetApp storage systems. The Windows Unified Host Utilities include an installation program that sets the required Windows registry and HBA values. Starting with version 5.3, the diagnostic programs for troubleshooting problems with Windows hosts connected to FAS storage systems were replaced by the nSANity program. You can download the latest version of nSANity from the NetApp Support Site.

Information on finding system requirements

NetApp qualifies additional components between releases of the Host Utilities software. For the latest information about the system requirements, see the NetApp Interoperability Matrix Tool.

Related information

NetApp Interoperability Matrix Tool

Features in this Host Utilities release

Windows Unified Host Utilities 7.1 includes support for E-Series storage systems, support for ONTAP 8.2 or later versions, and enhanced iSCSI timeouts for faster failover.

iSCSI driver parameters not set for the Emulex OCe

CNA

The Windows Host Utilities does not set the iSCSI driver parameters for the Emulex OCe converged network adapter (CNA). You need to manually set the driver parameters. For the latest status on this issue, see bug 484444 at Bugs Online.

Related information

NetApp Bugs Online

Setting the iSCSI driver parameters for the Emulex OCe10102 CNA

The Windows Host Utilities installer does not set the iSCSI driver parameters for the Emulex OCe10102 CNA. You need to manually set the parameters.

About this task A reboot is required after you set the parameters.

Steps

1. Load the Windows Registry Editor. 2. Navigate to HKLM\SYSTEM\CurrentControlSet\services\be2iscsi\Parameters\Device \DriverParameters 3. Enter the following value for the ldto parameter: 1 (REG_DWORD) 4. Enter the following value for the eto parameter: 10 (REG_DWORD) 5. Reboot your Windows host.

QLE8242 CNAs not configured automatically

If you install the Windows Host Utilities on a host that includes Data ONTAP DSM for Windows MPIO version 3.4 or earlier, the Windows Host Utilities installer does not automatically configure the required settings for the QLogic QLE8242 converged network adapter (CNA). To correct this issue, do one of the following:

• Upgrade to Data ONTAP DSM 3.5 for Windows MPIO. The DSM installer automatically configures the required settings, unless the QLE8242 driver is version 9.1.9.19 or later. Note: The Windows Host Utilities are no longer required if the Windows host is running Data ONTAP DSM 3.5 or later. While no longer required, installing the Windows Host Utilities on the same host as the DSM is still supported.
• Configure the required settings manually.

For the latest status on this issue, see bug 555108 at Bugs Online.

Important cautions | 7

Related information

NetApp Bugs Online

Setting the adapter timeouts using QConvergeConsole

The adapter requires specific timeout settings that are not set by the current host software.

Before you begin The QConvergeConsole CLI must already be installed on the Windows host computer.

Steps

1. Using the QConvergeConsole CLI, enter the following command to set the adapter LinkDownTimeout to 1: qaucli -pr fc -n port_number lt 1 port_number is the number of the port on a multi-port adapter. The setting must be made to each port of a multi-port adapter. 2. Enter the following command to set the adapter PortDownRetryCount to 10: qaucli -pr fc -n port_number pd 10

port_number is the number of the port on a multi-port adapter. The setting must be made to each port of a multi-port adapter.

Windows Server 2008 R2 upgrade issues

Upgrades to Windows Server 2008 R2 require you to address certain issues. Be sure to read the upgrade information provided by Microsoft. The following issues are especially important.

• Be sure to upgrade to Windows Host Utilities 6.0 before upgrading to Windows Server 2008 R2.
• If you are using the Data ONTAP DSM for Windows MPIO, be sure to upgrade to DSM 3.5 or later before upgrading to Windows Server 2008 R2.
• Be sure to upgrade to DSM 3.5 or later before upgrading to Windows Server 2008 R2.
• You cannot upgrade to Windows Server 2008 R2 while the host is part of a Windows cluster. Remove the host from the cluster before upgrading.
• For iSCSI-booted Windows Server 2008 hosts, there is no way to upgrade to Windows Server 2008 R2. You must do a fresh installation of Windows Server 2008 R2. This is a Microsoft limitation.

Do not manually create files on Windows Server 2008 R

CSV

Manually creating or copying files to a Windows Server 2008 R2 cluster shared volume (CSV) can corrupt the data on the volume. The only files allowed on a CSV are the files written by the Hyper-V administrative tools. This includes any user or application data stored under the C:\ClusterStorage directory on every node.

8 | Windows®^ Unified Host Utilities 7.1 Release Notes

Known problems and limitations

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds to avoid these behaviors, have been identified in this release. To request more information about an individual bug and to explore other bug-related tools, see Bugs Online on the NetApp Support Site.

Running the linux_gos_timeout-install.sh script is no longer

required on Hyper-V guests running Red Hat Enterprise

Linux or SUSE Linux Enterprise Server

You are no longer required to run the linux_gos_timeout-install.sh script to change disk timeouts on Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, or SUSE Linux Enterprise Server 11 Hyper-V guests because the default timeout settings are being used. The linux_gos_timeout-install.sh script that was included in previous versions of the Host Utilities is no longer included in the Windows Unified Host Utilities. Windows Unified Host Utilities 7.1 uses the default disk timeout settings. For more information, see bug ID 814244 in Bugs Online.

Related information

NetApp Bugs Online

Windows Host Utilities 6.0.2 and later only supports SAN

attachments from Windows Server 2012 for certain versions

of Data ONTAP

Windows Host Utilities 6.0.2 and later only supports SAN attachments from Windows Server 2012 to storage systems running Clustered Data ONTAP 8.2 or later and Data ONTAP 8.1.3 or later operating in 7-Mode.

Virtual Fibre Channel is not supported in virtual machines

on Windows Server 2012 hosts

Virtual Fibre Channel is not supported in virtual machines on Windows Server 2012 hosts connected to FAS storage systems running Data ONTAP.

san_version command reports the wrong QLogic driver

version

The san_version.exe command reports the wrong QLogic driver version. For the latest status on this issue, see bug 585473 at Bugs Online.

Related information

NetApp Bugs Online

iSCSI may fail to reconnect automatically on a Windows

Server 2012 host after a storage controller fault

The iSCSI initiator occasionally fails to reconnect automatically on a Windows Server 2012 host after a storage controller fault. The workaround is to manually reconnect the initiator to the target in the ISCSI Initiator Properties dialog box. For the latest status on this issue, see bug 622832 at Bugs Online.

Related information

NetApp Bugs Online

iSCSI may fail to reconnect on a Windows Server 2012 host

after a forced giveback on a clustered storage system

running Emulex 10g and the ToE offload

iSCSI occasionally fails to reconnect on a Windows Server 2012 host after a forced giveback on a clustered storage system running Emulex 10g and the ToE offload. The workaround is to disable ToE on the card. For the latest status on this issue, see bug 620085 at Bugs Online.

Related information

NetApp Bugs Online

Error when installing hotfixes

When installing required Windows hotfixes, you might get an error message saying the hotfix does not apply to your system. Some hotfixes have a dependency on other hotfixes. Install the hotfixes in numerical order to ensure they are accepted. Many hotfixes prompt you to reboot your system. You can wait until all hotfixes are installed before rebooting. If you are installing Windows Host Utilities immediately after the hotfixes, you can wait and reboot when prompted by the Host Utilities installation program.

Oracle 10g RAC Voting Disk using Windows igroup fails with

I/O error during giveback

When using Oracle 10g RAC, you can avoid I/O errors by specify the igroup type to which the LUNs used by Oracle are mapped as linux. I/O to the Oracle Voting Disk in Oracle 10g Real Application Clusters (RAC) on Windows Server 2003 times out during a storage controller giveback. The target drops I/O to the unreachable partner controller if the igroup type for the LUN is windows.

Known problems and limitations | 11

Configuring a pass-through disk for a VM already in the cluster

Use this procedure to configure a pass-through disk for a Windows 2008 R2 Hyper-V HA virtual machine (VM) if the VM is already added to the failover cluster.

Steps

1. In Failover Cluster Manager, verify the disk that will be the pass-through disk is listed in Available Storage. Take the disk offline, but do not delete from the cluster. 2. Using Failover Cluster Manager, shut down the VM to which you are adding the disk. 3. Using Hyper-V Manager, add the pass-through disk to the VM. 4. In Failover Cluster Manager, select the VM and then select Refresh virtual machine configuration in the Action pane. The pass-through disk is added to the group that the VM is in and brought online automatically. 5. Start the VM. The pass-through disk is available.

Cluster Shared Volume not accessible from one node in a

Windows Server 2008 failover cluster

From a node in a Windows Server 2008 failover cluster, if a CSV volume is accessed, an error message "CSV Volume not accessible" is displayed. The event log contains an error message similar to Cluster service failed to create a cluster identity token for Cluster Shared Volumes.

This error is caused by a configuration error such as authentication issues, the inability of the node to contact a domain controller, or the cluster IP address being incorrect. If you fix these issues, the volume should be accessible.

Unable to change load balance policy to Failover using

msdsm

Using the native Microsoft DSM (msdsm), you are unable to change the load balance policy for a LUN to Failover. This problem can happen when multiple paths to the LUN are Active/Optimized. An error message similar to the following is displayed when you attempt to change the load balance policy: The failover policy employs one active/optimized path and all other paths are active/unoptimized, standby or unavailable. The workaround is to manually change the path state for all the paths except one to Standby. Then change the load balance policy to Failover. For the latest status, see bug 249760 at Bugs Online.

Related information

NetApp Bugs Online

Known problems and limitations | 13

Hyper-V live migration and quick migration fail after

converting a CSV LUN to non-CSV

Hyper-V live migration and quick migration do not work after converting a cluster shared volume (CSV) LUN to a non-CSV LUN. You need to follow special procedures to convert a CSV to a non- CSV for successful live migration or quick migration. When a LUN is used as a CSV, you cannot change the Windows drive letter of the virtual hard drive (VHD) to enable live migration or quick migration. Attempting live migration or quick migration with a CSV fails. If you simply remove the LUN from the CSV, the migration also fails. Follow the special procedure for converting a CSV LUN to enable live and quick migrations.

Converting a Hyper-V CSV LUN to enable live and quick migration

Hyper-V live migration and quick migration do not work after cluster shared volume (CSV) LUNs have been converted to non-CSV. This procedure removes the LUN from the CSV and enables migration of the virtual machine.

Steps

1. Shut down the Hyper-V virtual machine (VM). 2. Export the VM configuration. This does not copy the virtual hard drive (VHD), just the VM configuration information. 3. Delete the VM from the Windows cluster and from Hyper-V. Note: Do not import the VM configuration until you are instructed to do so below. 4. Remove the LUN from the CSV and assign an available Windows drive letter. 5. Import the VM you exported. In the VM settings, change the VHD location to point to the drive letter you assigned to the LUN. 6. Add the VM back as an HA resource.

Cannot add SCSI pass-through disk to SUSE Hyper-V guest

using IDE controller

If you add a SCSI pass-through disk using the virtual IDE controller to a Hyper-V virtual machine running SLES, you cannot create a filesystem on the disk. Disk commands such as fdisk also fail. The problem has been observed in both clustered and non-clustered configurations. The workaround is to use the virtual SCSI controller for pass-through disks on SLES virtual machines. For the latest status, see bug 365641 at Bugs Online.

Related information

NetApp Bugs Online

14 | Windows®^ Unified Host Utilities 7.1 Release Notes

MCS is not supported with iSCSI software boot

When using iSCSI software boot with iSCSI multiple connections per session (MCS), the iSCSI boot leading connection cannot be protected. This can lead to disconnection from the boot LUN causing the host to crash. Microsoft does not support MCS for iSCSI software booted hosts. Use MPIO as the high availability solution. Note that mixing MPIO and MCS is not supported. For the latest status, see bug 275185 at Bugs Online.

Related information

NetApp Bugs Online

Raw (pass-through) disks on a guest OS are not available

when running MPIO on the guest

If you run MPIO software on a guest OS (for iSCSI directly from the guest), and you also configure raw (pass-through) disks as SCSI physical disks from the parent, the guest is unable to use the raw disks. This issue occurs with the Data ONTAP DSM for Windows MPIO and the Veritas DMP DSM. When you are running MPIO on the guest, map raw drives as IDE physical disks.

Raw (pass-through) disks do not appear in Hyper-V guest

OS

Raw (pass-through) disks do not appear in a Hyper-V guest OS if Windows Host Utilities is installed on the guest and multipathing support is enabled. When you enable multipathing support for Windows Host Utilities, LUNs on NetApp storage systems are claimed by the Windows MPIO drivers. Raw disks that are also based on NetApp LUNs are not passed to MPIO, and therefore not visible in the guest OS. You can either use multipathing in the guest OS, or you can use raw disks, but not both.

Guest OS install on SCSI disk fails

You cannot boot a Hyper-V virtual machine from a SCSI-mapped disk. Use an IDE-mapped disk for the virtual machine boot disk.

Hyper-V virtual machine files do not work on CIFS share

You cannot use a CIFS share on the storage system to store the virtual hard disk (.vhd file) or virtual machine configuration files for a Hyper-V virtual machine. Store the .vhd file and virtual machine configuration files on a FC or an iSCSI LUN mapped to a drive on the Hyper-V parent system.

16 | Windows®^ Unified Host Utilities 7.1 Release Notes

Hyper-V guest does not boot or loses pass-through disk

If the disk numbers on the Hyper-V parent change so that they no longer match the virtual machine configuration, the guest operating system can fail to boot or the guest can lose access to a pass- through disk. The disk number might change if you delete a LUN mapped to the parent and then reboot the parent. You can fix the problem by modifying the virtual machine configuration to match the new disk identifiers.

SUSE Hyper-V guest loses network when moved to another

cluster node

SUSE guest operating systems on Hyper-V systems lose their network connections when the guest is moved to another node in the Windows cluster. The network loss occurs when the guest uses a dynamic MAC address for its virtual network adapters. Dynamic MAC addresses are the default setting.

The workaround is to always select a static MAC address in the virtual machine Network Adapter settings for SUSE guest operating systems. This problem has been reported to Microsoft.

Configuration fails when attempting to add a virtual machine

to a Failover Cluster

Adding a virtual machine to a failover cluster fails because the hidden available storage resource group belongs to a different node in the cluster.

Correcting a failed virtual machine addition

If adding a virtual machine to a failover cluster fails because the hidden available storage resource group belongs to a different node in the cluster, add the new virtual machine's disk to the correct resource group.

Steps

1. Move the disk to the proper node by using the Failover Cluster Management Console. 2. Add the disk to the proper resource group created by the Virtual Machine Resource Wizard. 3. Manually add a dependency of the Virtual Machine on the Virtual Machine Configuration files. 4. Add a dependency of the Virtual Machine Configuration Files on the Physical Disk. 5. Start the Virtual Machine Resource Group.

Known problems and limitations | 17

Related information

NetApp KB Article 2012694: SAN (storage area network) boot of a Windows 2003 server with

Emulex HBA (host bus adapter) fails

Microsoft iSCSI SW Initiator takes a long time to reconnect

to the storage system after disruption

In a storage system configuration with multiple physical networks or multiple VLANs, the Microsoft iSCSI software Initiator can take several minutes to reconnect to the storage system. During initial target discovery (Add Target), the Microsoft iSCSI software initiator uses the iSCSI SendTargets command to retrieve a list of IP addresses at which the target can be accessed. In a storage system configuration with multiple physical networks or multiple VLANs, it is possible that some of the storage system’s addresses are not accessible to a given host. In this situation, the SendTargets response sent by the storage system will advertise some addresses which are not accessible by that host. When the Microsoft iSCSI initiator loses connectivity to the target (such as during storage system reboot, takeover, and giveback), the initiator attempts to reestablish connectivity to the target using the following default algorithm, which Microsoft calls “port-hopping”:

• Attempt to reconnect over the same IP address which was being used before the disruption.
• Cycle through the other IP addresses from the SendTargets response, attempting to reconnect, until connectivity is reestablished.

Each inaccessible IP address in the list can add a delay of 15-20 seconds, which is the TCP connection establishment timeout. If there are many inaccessible IP addresses in the list, it may take a long time for the iSCSI initiator to cycle through the list before successfully reconnecting to the target. If the total reconnect time exceeds the timeout configured on the host (MaxRequestHoldTime for non-MPIO, or PDORemovePeriod for MPIO), the Windows applications experience I/O errors. This long reconnect time can be minimized by disabling the use of the Microsoft “port-hopping” algorithm by using a specific target IP address for each connection in the iSCSI Initiator.

Disabling the Microsoft iSCSI port-hopping algorithm

Disable the Microsoft iSCSI port-hopping algorithm in the iSCSI Initiator to minimize the recovery time in configurations with many iSCSI target ports.

Steps

1. Open the Microsoft iSCSI initiator applet and select the Targets tab. 2. Click Log On. 3. In the Logon to target dialog box, click Advanced. 4. In the Target Portal list, change the value from Default to one of the storage system IP addresses specified in the Target Portals list on the Discovery tab.

Result After a disruption occurs, the Microsoft initiator uses only the IP address specified to reconnect to the storage system and does not try other IP addresses advertised in the SendTargets response. Note: If the specified IP address is unreachable, no failover occurs.

Known problems and limitations | 19

Initiator unable to log in to storage system

If you set an initiator node name that does not comply with the iSCSI specification, the initiator is unable to log in to the storage system. This is possible because the initiator does not enforce the node name rules, but the storage system does. The storage system console displays the following error message: Invalid value for iSCSI text key, 'InitiatorName=node_name'.

Change the initiator node name to an iSCSI RFC-compliant name by following the rules in the Host

UtilitiesInstallation and Setup Guide. For more information, see bug number 162192 at Bugs Online.

Related information

NetApp Bugs Online

LUN identifier range 0-

The Windows operating system only recognizes LUNs with identifiers from 0 to 254, regardless of the number of LUNs mapped. Be sure that your LUNs are mapped to identifiers in this range.

MPIO and MCS are not supported together

To create a high-availability connection between the Windows host and the storage system, you can use either multipath I/O (MPIO) or iSCSI multiple connections per session (MCS). Using both simultaneously is not supported. Select either MPIO or MCS for high-availability.

I/O stops when removing iSCSI connections

Using iSCSI multiple connections per session (MCS), you remove connections and I/O stops. In some situations, the iSCSI initiator allows you to remove the last active connection without warning. Do not remove the last active connection. If you need to remove an iSCSI connection, make it a standby connection, and ensure another connection is active. Then remove the standby connection.

Wait between iSCSI logout and login

If you use the iSCSI software initiator GUI to log out the last session with an iSCSI target and then immediately log back in to the target, the Windows host does not connect to the iSCSI LUNs. Wait at least 150 seconds after logging out of the last session with an iSCSI target before logging back in.

20 | Windows®^ Unified Host Utilities 7.1 Release Notes