HP StoreVirtual 4000 10.0 HP LeftHand Storage Release Notes (AX696-96225, Nove - Page 13

in the Disk Manager. You must re-install and configure the DSM for MPIO after the operating system upgrade. • DSM for MPIO I/O may stall With the DSM for MPIO installed on configurations with a large number of volumes and iSCSI connections, when a maintenance activity like an upgrade/patch installation, or any other activity that is related to volumes like snapshots or restriping, occurs on the HP LeftHand Storage, there can be delayed I/O. Depending on the application that is using the volume, this delay may cause the application to experience data unavailability or to report other errors. Notifications and alerts • SNMP clients and multi-byte characters SNMP clients must be configured to use UTF-8 encoding to properly display multi-byte characters. • The email alarm does not clear when a DNS server is fixed or comes back online The following warning may display when the system attempts to send an email alert: EID_GLOBAL_CONFIG_MISCONFIGURED: The 'Email' configuration status is 'Misconfigured'. If DNS and the email server are unavailable briefly, the email configuration is deleted. When DNS and the email server become available again, this message displays because the email configuration no longer exists. You must reset the email configuration to stop this warning message and begin receiving email alerts again. Failover Manager • Unable to upgrade a management group to 10.0 that is running a version 8.1 Failover Manager When using a version 10.0 CMC and logging into a Failover Manager running version 8.1, the following error message is displayed: HAL device is missing. If this error message displays, you will be unable to upgrade the management group that contains this Failover Manager. To resolve this issue: 1. Remove the 8.1 Failover Manager. 2. Upgrade the CMC version on the management group. 3. Add a 10.0 Failover Manager to the management group. • HP LeftHand Failover Manager for Microsoft Hyper-V installer hangs on Windows Server 2012 When installing the Hyper-V Failover Manager on a server running Windows Server 2012, the installation hangs. To resolve this issue, you must install .NET 3.5 before installing the Failover Manager. Normally the missing files will be downloaded from Windows Update, but if access to Windows Update is not possible, enabling .NET Framework 3.5 will fail unless an alternate source for the missing files has been specified. If Windows Server 2012 is installed in Server Core installation mode, you must use the command line (DISM.exe) to install .NET 3.5. If Windows Server 2012 is installed as a full installation (in Server with a GUI mode), you can use the command line or Windows Server Manager→Add Roles and Features to install .NET 3.5. NOTE: You will need to change the DVD drive specification. • A degraded FOM can cause management group outage due to manager timeouts If a Failover Manager becomes unresponsive and cannot participate in quorum, the management group cannot respond to commands. However, the management group does not recognize the problem with the Failover Manager, and the management group becomes unresponsive. This issue can be caused if the Failover Manager is installed on the HP LeftHand Storage instead of network hardware other than storage systems. Installing the Failover Manager on the HP LeftHand Storage is not supported. Workarounds 13