NimbleOS 5.1.4.0 Release Notes - Hewlett Packard Enterprise · VMware has announced End of General...

NimbleOS 5.1.4.0 ReleaseNotes

Version 5.1.4.0

Published February, 2020

Legal Notices

© Copyright 2020 Hewlett Packard Enterprise Development LP. All rights reserved worldwide.

Notices

The information contained herein is subject to change without notice. The only warranties for Hewlett PackardEnterprise products and services are set forth in the express warranty statements accompanying such productsand services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterpriseshall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, orcopying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documen-tation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standardcommercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprisehas no control over and is not responsible for information outside the Hewlett Packard Enterprise website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in theUnited States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the UnitedStates and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Java® and Oracle® are registered trade-marks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Publication Date

Tuesday February 25, 2020 17:57:58

Document ID

sgr1569525085495

Support

All documentation and knowledge base articles are available on HPE InfoSight at https://infosight.hpe.com.To register for HPE InfoSight, click the Create Account link on the main page.

Email: [email protected]

For all other general support contact information, go to https://www.nimblestorage.com/customer-support/.

2Copyright © 2019 by Hewlett Packard Enterprise Development LP. All rights reserved.

Legal Notices

https://infosight.hpe.com

mailto:[email protected]

https://www.nimblestorage.com/customer-support/

Contents

NimbleOS 5.1.4.0..........................................................................................4Important Update Note.........................................................................................................................4

Special Notes.......................................................................................................................................4

New Features in 5.1.4.0.....................................................................................................................10

Recent Release Features..................................................................................................................10

Documentation...................................................................................................................................12

Verified Update Paths........................................................................................................................13

Known Critical Issues.........................................................................................................................17

Resolved Critical Issues.....................................................................................................................20

Resolved Issues.................................................................................................................................23

Known Issues.....................................................................................................................................26

Copyright © 2019 by Hewlett Packard Enterprise Development LP. All rights reserved.

Nimble

NimbleOS 5.1.4.0

5.1.4.0Version:

Tuesday February 25, 2020 17:57:58Revision:

The release notes describe the major changes, fixes, and known issues for this release of the NimbleOS.They do not include all individual fixes and internal changes.

For technical support, contact HPE Nimble Storage Support at:

mailto:[email protected] (877-364-6253), option 2.

Important Update NoteUpdating NimbleOS can involve an update to component firmware on the standby controller. This can causean email alert and automated case indicating "Standby Controller Not Available" when the firmware updateprocess takes longer than five minutes. This is expected behavior and does not affect data services. At theend of the software update, you can check status of both controllers in the Web UI under Manage > Hardware.One controller will be ACTIVE and the other STANDBY under normal operating conditions following asuccessful software update.

All third-party software notices can be found on HPE InfoSight (https://infosight.hpe.com) on the Resources >Documentation page:

https://infosight.hpe.com/resources/nimble/docs

The Documentation page also includes the General Terms and Conditions document. You can display thisdocument by performing the following steps:

1 In the navigation pane on the HPE InfoSight Documentation page, scroll through the Document Typelist and select Support Policy.

2 In the page that appears, select General Terms and Conditions. This document opens in a browsertab.

Special Notes

DescriptionNote

HPE Nimble Storage continues to qualify configurations between releas-es. The Validated Configuration Matrix provides information about vali-dated configurations and is updated frequently. It is a good practice tocheck your system configuration against this online tool. The ValidatedConfiguration Matrix tool is available on HPE InfoSight:

https://infosight.hpe.com/resources/nimble/validated-configuration-matrix

CRITICAL

Arrays must be running NimbleOS 4.5.4.0 or 5.0.4.0 or later to upgradeto NimbleOS 5.1.4.0.

CRITICAL

Internet Explorer 10 and earlier versions are not supported in NimbleOS4.x and later.

CRITICAL


NimbleOS 5.1.4.0 Important Update Note

mailto:[email protected]




DescriptionNote

An extended data services outage may occur with MS iSCSI initiatorand Intel NICs using the built-in Windows driver e1q60x64.sys (version11.0.5.21/11.0.5.22).

If you encounter this problem, please update your system to use thelatest Windows driver.

CRITICAL

A service outage may occur on Windows 2012 R2 hosts using Emulexor Broadcom Fibre Channel HBAs with firmware/driver prior to 11.2.Update the Emulex or Broadcom firmware/driver to 11.2 or later

CRITICAL

Due to a known Red Hat Enterprise Linux bug 1002727, while runningvirtualized in VMware ESX, manually rebooting the active controller inpresence of heavy IOs using the reboot --controller command on aFibre Channel array may trigger an incorrect retry initiated by RHELguests running the following kernel versions:

• 6.4 and earlier• 6.5 without the patch• 7.0 without the patch

This incorrect retry logic may lead to unexpected application behavior.In these environments, we recommend the failover command instead.

CRITICAL

Due to a known Red Hat Enterprise Linux bug 3550561, unexpectedapplication behavior may occur on RHEL 7.5 hosts with kernel-3.10.0-862.3.2.el7 or derivatives using Emulex FC FCoE HBAs (lpfc driver)and raw devices. To avoid this issue:

• If running RHEL 7.6, update to kernel-3.10.0-957.el7 or later.• If running RHEL 7.5z, update to kernel-3.10.0-862.25.3.el7 or later.

CRITICAL

As outlined in the current Validated Configuration Matrix, HPE NimbleStorage fully supports Windows guest operating systems on MicrosoftHyper-V, including Virtual Fibre Channel (VFC) connectivity and multi-pathing with HPE Nimble Storage DSM and VSS support. However,Linux guest operating systems running in Hyper-V VFC configurationsare not qualified. Running Red Hat Linux guest operating systems withthe “Linux Integration Services” kit installed, or with hv_storvsc driversin such configurations can lead to Red Hat bug 1364282, which cancause an unexpected service outage.

CRITICAL

Starting with NimbleOS 5.1.1.0, the size of the software package nowexceeds 2 GB, which may lead to lengthier software download times.Previously, the sizes of the NimbleOS 5.0.x download packages wereapproximately 1.6 GB, and NimbleOS 4.x packages were approximately900 MB.

Important

Starting with NimbleOS version 5.1.3.0, the array group now uses JavaDevelopment Kit (JDK) version 1.8.0.212.

This addresses several security vulnerabilities identified in the previousversion of the JDK listed here.

Important


NimbleOS 5.1.4.0 Special Notes

https://nvd.nist.gov/vuln/search/results?form_type=Basic&results_type=overview&query=8u131&search_type=all

DescriptionNote

HPE Nimble Storage CS2xx (except CS235) and CS4xx arrays areblocked from updating to NimbleOS 5.1.1.0 and later releases by default.These arrays will be allowed to update in special circumstances, suchas for group merge and evacuation purposes, and temporary data mi-gration workloads. Contact HPE Nimble Storage Support if you wish toupdate your CS2xx or CS4xx array to NimbleOS 5.1.x.x.

Important

After completing the NimbleOS update for array groups configured forSynchronous Replication, download the corresponding version of theSynchronous Replication Witness software, and update the witnesshost.

Important

Microsoft Offload Data Transfer (ODX) is not supported if the destinationvolume has synchronous replication enabled.

Important

Starting with NimbleOS version 5.0.7.0, the Fibre Channel HBAs willuse an updated firmware (11.4.204). The new firmware addresses anissue in which some 16Gb Fibre Channel HBAs might not auto-negotiateto 16Gb on all ports due to a timing issue within the code of the previousversion of the firmware.

Important

As of vSphere 6.5, VMware is discontinuing the Thick Client (also knownas the desktop or C# Client). As a result, the HPE Nimble StoragevCenter Plugin is deprecating the Thick Client and future releases ofNimbleOS will not support it.

Important



https://infosight.hpe.com/resources/nimble/software/NimbleOS/Synchronous%20Replication%20Witness

DescriptionNote

Starting with version 5.0.3.0, NimbleOS includes a restriction that pre-vents you from enabling deduplication when you are using a CS3000,CS5000, CS7000, HF20, HF40, or HF60 array that has fewer than sixSSDs. This restriction is necessary to prevent the possibility of significantperformance issues.

Because NimbleOS 5.0.2.0 and 5.0.1.0 did not enforce this restriction,arrays upgrading from those releases may already have volumes withdeduplication enabled. Any array upgrading to 5.0.3.0 or later withdeduplicated volumes will continue to operate as a dedupe capablearray, regardless of the number of installed SSDs. Such configurationsare not recommended by HPE Nimble Storage.

The following table lists the number of SSDs required for the differentarrays:

Required Number of SSDsArray Model

2 SSDsHF20H

4 SSDsHF20H upgraded to full population

4 SSDsHF20H fully populated and upgrad-ed to HF40H

6 SSDsHF20, HF40, HF60

4 SSDsCS500

4 SSDsCS700

3 SSDsCS1000

6 SSDsCS3000

6 SSDsCS5000

6 SSDsCS7000

Important

You can enable deduplication for CS1000, CS3000, CS5000, CS7000,CS700, and CS500 arrays on a volume only if the corresponding storagepool has a Flash to Disk Ratio (FDR) greater than 4%. To calculate theFDR, obtain the "Total array capacity (MiB)" and "Total array cachecapacity (MiB)" values by using the HPE Nimble Storage CLI commandpool --info pool_name. This command returns the Pool capacity (MiB),which is the "Total array capacity (MiB)", and the Pool cache capacity(MiB), which is the "Total array cache capacity (MIB)".

Then perform the following calculation:

FDR = "Total array cache capacity (MiB)"/"Total array capacity(MiB)" * 100

If the array has sufficient capability for deduplication, the pool --infocommand will also show a value for dedupe capacity (MiB).

Note On the HF20H, HF20, HF40, and HF60 platforms, pool --infodisplays "N/A" as the value for dedupe capacity (MiB). This becauseyou can enable deduplication for the entire array.

Important



DescriptionNote

For connections to the NimbleOS GUI, you must have port 5392 openfor the Group Management IP address and both diagnostic IP addresses.

Important

VMware has announced End of General Support for vSphere 5.0, 5.1,and 5.5, which includes vSphere Hypervisor ESXi 5.0, 5.1, and 5.5, andvCenter Server 5.0, 5.1, and 5.5. To maintain your full level of supportand subscription from VMware, you should upgrade to a supportedversion of vSphere. Refer to the VMware Knowledge Base articleKB51491.

Important

During deployment of a desktop using VMware Horizon View, a VVol(mapping to a disposable disk) is created. A clone of this VVol is alsocreated and placed within a directory under the virtual machine directorynamed sdd.

When this desktop is deleted from Horizon View, VMware fails to deletethe VVol clone of the disposable disk; only the disposable disk itself isdeleted. This will be fixed in the next vSphere release. VMware bugnumber 1807857 should be used to track this fix.

This issue occurs on all versions of VMware Horizon and vSphere thatsupport VVols:

• Horizon 6 version 6.1 and later• vSphere 6.0 and later

Important

On Windows Server 2012, 2012 R2, 2016, and 2019, the disk optimiza-tion process may record the following error in the Application event log:"The volume was not optimized because an error was encountered:Neither Slab Consolidation nor Slab Analysis will run if slabs are lessthan 8 MB. (0x8900002D)". Although Windows records this as an Errorin the event log, the event can be safely ignored for HPE Nimble Storagevolumes. HPE Nimble Storage volumes do not benefit from or requireslab consolidation.

Important

Numerous host integration toolkits are supported in NimbleOS 5.1.4.0.It is strongly recommended that they be installed on all Windows, Linux,and VMware hosts. For more information about supported toolkits, referto the Validated Configuration Matrix, which is available on HPE NimbleStorage InfoSight:


Important

Hosts leveraging VSS integration with HPE Nimble Storage WindowsToolkit (NWT) 2.1 and earlier will not work with NimbleOS 3.x. and later.

Important

TRIM on ReFS is not supported by Microsoft on Windows Server ver-sions prior to 2019.

Important



https://kb.vmware.com/s/article/51491?lang=en_US#q=end%20of%20general%20support%20for%20vsphere%205%205


DescriptionNote

HPE Nimble Storage Connection Manager (NCM) for VMware 6.1.0 issigned by VMware for ESXi 6.x. It can be installed through the VMwareUpdate Manager or esxcli command without the --no-sig-checkflag.

See NCM for VMware Release Notes 6.1.0 or later and the latestVMware Integration Guide for further details. To locate the latest versionof the guide, log in to HPE InfoSight. Choose Resources > NimbleStorage Documentation. In the left pane, click Integration Guide,then click Connection Manager (NCM) for VMware. From the list dis-played, choose the version of the guide that you want.

Important

Performing a group merge from a source group that contains runningHyper-V virtual machines requires additional care. Group merges requirechanges to the discovery IP address that can adversely impact runningsystems. Therefore, if you perform a group merge, you should plan amaintenance outage to gracefully stop all applications and Hyper-Vvirtual machines on the source group to eliminate unexpected downtimecaused by changing IP address during the group merge process. Atypical group merge should take only a few minutes to complete andthen virtual machines and applications can be restarted.

The group merge and pool merge operations will also have impact onSCVMM. The impact will depend on whether the source and destinationgroups or pools are under SCVMM's management.

Please refer to the SMI-S Integration Guide which includes details aboutSCVMM and the impacts in these situations before performing mergeoperations.

Important

Various timeout values affect HPE Nimble Storage targets from Win-dows/Linux hosts. Before you update the NimbleOS, install the HPENimble Storage Windows Toolkit (NWT) or HPE Nimble Storage LinuxToolkit (NLT) on the host or tune the timeout values. Timeout detailsfor various operating systems can be found on HPE InfoSight underResources > Documentation. From the HPE Nimble Storage Docu-mentation page, locate the article you want.

The following Knowledge Base articles and Integration Guides explainhow to configure and verify host timeout settings for the major supportedoperating systems (OS):

• For Windows, refer to KB-000052: Windows Host Disk TimeoutValues.

In the context of Microsoft Windows, the following article should alsobe considered:

KB-000246 MPIO Timeout Parameters for MSDSM and NimbleDSMin Windows 2012 R2

• For VMware, refer to the Common Tasks and Best Practices >Host Timeout Values section of the VMware Integration Guide.

• For Linux, refer to KB-000304: Linux Host Disk Timeout Values.

Important





https://infosight.hpe.com/InfoSight/media/kb/active/htr1455131698674.whz/index.html


https://infosight.nimblestorage.com/InfoSight/media/kb/active/htr1455131726154.whz

https://infosight.nimblestorage.com/InfoSight/media/kb/active/htr1455131726154.whz


DescriptionNote

The Backup Repository performance policy introduced in NimbleOS4.2 cannot be used when replicating against a downstream array runningan older release. Replicated volumes need to be associated at the timeof creation with a performance policy that either exists downstream orthat can be manually created on the downstream array.

Important

New Features in 5.1.4.0The following new features are introduced in NimbleOS 5.1.4.0.

SSL Certificate Management GUI Application

The SSL Certificate Management GUI application provides a user-friendly interface to install, import, create,verify and delete various kinds of certificates and certificate signing requests (CSR) for the Certificate Authorityto process.

Usage Analytics

HPE Nimble Storage uses Google Analytics to gather data related to GUI usage. The data gathered is usedto evaluate and improve the product.

Recent Release FeaturesThe following features were release in NimbleOS 5.1.x:

Synchronous Replication

This feature provides the ability to synchronously replicate data between two arrays located in separatedatacenters. Synchronous replication provides automatic protection against array or site failure.

Manual Group Leader Failover

This feature supports the ability to move the group leader functionality from one array to another when arraysare grouped. This allows the retirement of the array supporting the group leader functionality.

Group Scoped iSCSI Target

This feature allows multiple LUNs to be accessed through a single iSCSI target, which reduces the numberof connections required when configuring a large number of LUNs.

Space Reporting Changes

This feature provides simplified space reporting when using data reduction tools, such as compression anddeduplication. Arrays will now show logical mapped usage, which more closely aligns with HPE InfoSightand hosts in terms of pre-reduction space usage reported at the volume level. Going forward, reserves willonly be thin (0%) or thick (100%). Volume quotas become volume limits. Snapshot quotas no longer exist.

Folder Level Space Enforcement

Expanded the functionality for enforcing space usage within individual folders. In addition, NimbleOS actuallyenforces limits, and introduces the concept of overdraft, which allows a folder to exceed the usage limitbefore the limit is enforced.

Multi-protocol (iSCSI/FC) Access to Same Array

This feature allows both the iSCSI and Fibre Channel protocols to be used simultaneously on a single arrayor group to access different LUNs.

Custom Password Management Policies

This feature provides improved password policies to enable greater security for user access to the HPENimble Storage array.

vCenter Plugin HTML5 Client


NimbleOS 5.1.4.0 New Features in 5.1.4.0

This feature improves the vCenter plugin by leveraging HTML5 technology to better interact with VMwarevCenter.

Deduplication Support for CS1000 Hybrid Arrays

Deduplication is now available on HPE Nimble Storage CS1000 hybrid arrays.

Note Deduplication is not supported on HPE Nimble Storage CS1000H arrays.

There are certain restrictions for using this feature. Before you enable deduplication on hybrid arrays, reviewthe product documentation for complete details.


NimbleOS 5.1.4.0 Recent Release Features

DocumentationThese Release Notes and other user documentation are available on HPE InfoSight:


You can manually reach the documentation page by logging onto HPE InfoSight and selecting Resources >Nimble Storage > Documentation.

Document Search Interface

There are several methods you can use to locate the documents you need.

The Documentation page provides a search interface that allows you to search for information across alldocumentation, including support and knowledge base articles, best practices, solutions and integrationguides, product documentation, and configuration matrices.

To go directly to a document, use the navigation pane on the left side of the Documentation page. Thenavigation pane organizes documents into categories, including:

• Document Type• Nimble Software and Solutions• Software Version• Integration• Platform

You can use the page scroll bar to move up and down the navigation pane.

Third-Party Software Notices

All third-part software notices can be found in the Documentation Portal on HPE InfoSight.

Here are the steps to manually access the third-party software notices.

1 Log in to HPE InfoSight (https://infosight.hpe.com) .

2 From the menu, select Resources Nimble Documentation .

3 In the left navigation pane of the Documentation Portal, scroll through the Document Type sectionand select Support Policy.

4 From the list of documents, select General Terms and Conditions. The document opens in a newbrowser tab.

Core User Documentation

The following is the core user documentation for NimbleOS:

• GUI Administration Guide• CLI Administration Guide• SNMP Reference• Command Reference• REST API Reference

Workflow Documents

There are several workflow guides that contain procedures you can perform using either the CLI or the GUI.Each workflow guide covers a specific, frequently performed task related to HPE Nimble Storage products.Each task described by a workflow document is explained in detail in the GUI Administration Guide and theCLI Administration Guide.


NimbleOS 5.1.4.0 Documentation


Hardware

Documentation for all hardware components is available on HPE InfoSight. Click the Hardware Guide link inthe Document Type category. Hardware documentation includes array and expansion shelf installation quickstart guides, installation, upgrade, and replacement guides, and comprehensive hardware guides.

Host Integration Guides

Host Integration Guides are available from HPE InfoSight. To locate these documents on the HPE InfoSightDocumentation page, scroll down the navigation pane to the section called Integration Guide. The availableguides include the following:

• Linux Integration Guide• OpenStack Cinder Driver Integration Guide• SMI-S Integration Guide• UCS Director Open Automation Module Integration Guide• VMware Integration Guide• Windows Integration Guide

Note The version numbers of the host integration guides match the version numbers of their companionIntegration Toolkit software packages.

Integration Toolkits

The following Integration Kits include documents that are associated with the toolkit software. You can searchfor them by entering the HPE Nimble Storage software type and version. The following integration toolkitsare supported:

• HPE Nimble Storage Adaptive Flash Cinder Driver for OpenStack• HPE Nimble Storage AIX ODM• HPE Nimble Storage Connection Manager (NCM) for Linux• HPE Nimble Storage Connection Manager (NCM) for VMware• HPE Nimble Storage PowerShell Toolkit (PSTK)• HPE Nimble Storage Replication Adapter (SRA)• HPE Nimble Storage UCS Director Open Automation for Cisco UCS Director• HPE Nimble Storage Windows Toolkit (NWT)

Note To download Integration Kit software, go to HPE InfoSight (https://infosight.hpe.com), then chooseResources > Software Downloads.

Verified Update Paths

Table 1: From Versions 5.x

From Versions 5.x

To VersionFrom Version

5.1.4.05.1.3.100

5.1.4.05.1.3.0

5.1.4.05.1.2.100

5.1.4.05.1.2.0

5.1.4.05.1.1.0

5.1.4.05.0.8.0


NimbleOS 5.1.4.0 Verified Update Paths


From Versions 5.x


5.1.4.05.0.7.300

5.1.4.05.0.7.200

5.1.4.05.0.7.100

5.1.4.05.0.7.0

5.1.4.05.0.6.0

5.1.4.05.0.5.200

5.1.4.05.0.5.0

5.1.4.05.0.4.0

5.0.8.05.0.3.100

5.0.8.05.0.3.0

5.0.8.05.0.2.0

5.0.8.05.0.1.100

5.0.8.05.0.1.0


From Versions 4.x


5.1.4.04.5.5.0

5.1.4.04.5.4.0

5.0.8.04.5.3.0

5.0.8.04.5.2.0

5.0.8.04.5.1.0

5.0.8.04.5.0.0

5.0.8.04.4.1.0

5.0.8.04.4.0.0

5.0.8.04.3.1.0

5.0.8.04.3.0.0

5.0.8.04.2.1.0

5.0.8.04.2.0.0

5.0.8.04.1.0.0




From 3.x Versions


5.0.8.03.9.2.0

5.0.8.03.9.1.0

5.0.8.03.9.0.0

5.0.8.03.8.1.0

5.0.8.03.8.0.0

5.0.8.03.7.0.0

5.0.8.03.6.2.0

5.0.8.03.6.1.0

5.0.8.03.6.0.0

5.0.8.03.5.4.0

5.0.8.03.5.3.0

5.0.8.03.5.2.0

5.0.8.03.5.0.0

5.0.8.03.4.1.0

5.0.8.03.4.0.0

5.0.8.03.3.0.0

5.0.8.03.2.1.0

5.0.8.03.1.0.0


From 2.0.x VersionsFrom 2.1.x VersionsFrom 2.2.x, 2.3.x Versions

To VersionFrom VersionTo VersionFrom VersionTo VersionFrom Version

2.1.9.12.0.8.02.3.18.02.1.9.14.5.5.02.3.18.0

2.1.9.12.0.7.02.3.18.02.1.9.04.5.5.02.3.16.0

2.1.9.12.0.6.*2.3.18.02.1.8.04.5.5.02.3.15.0

2.1.9.12.0.5.02.2.9.02.1.7.04.5.5.02.3.14.0

2.1.9.12.0.4.02.2.9.02.1.6.04.5.5.02.3.12.*

2.2.9.02.1.5.04.5.5.02.3.9.*

2.2.9.02.1.4.04.5.5.02.3.8.0

2.2.9.02.1.3.04.5.5.02.3.7.0

2.2.9.02.1.2.04.5.5.02.3.6.0

2.1.9.12.1.1.04.5.5.02.3.4.0



From 2.0.x VersionsFrom 2.1.x VersionsFrom 2.2.x, 2.3.x Versions


2.1.9.12.1.0.04.5.5.02.3.3.0

4.5.5.02.3.2.1

4.5.5.02.3.2.0

4.5.5.02.3.1.0

3.9.2.02.2.11.0

3.9.2.02.2.10.0

3.9.2.02.2.9.0

3.9.2.02.2.7.*

3.9.2.02.2.6.0

3.9.2.02.2.5.*

2.2.11.02.2.3.*

2.2.11.02.2.2.0

2.2.11.02.2.1.0

2.2.11.02.2.0.0


From 1.0.x VersionsFrom 1.3, 1.2, 1.1 VersionsFrom 1.4.x Versions


Contact Support1.0.7.*1.4.6.01.3.*.*2.1.9.11.4.12.0

Contact Support1.0.6.*1.4.6.01.2.*.*2.1.9.11.4.11.0

1.2.2.01.1.*.*2.1.9.11.4.10.0

2.1.9.11.4.9.0

2.1.9.11.4.8.0

2.1.9.11.4.7.0

1.4.12.01.4.*.*



Known Critical Issues

Known Critical Issues in NimbleOS version 5.1.4.0

WorkaroundDescriptionTitleComponentID

When planning to removea member array from group,schedule a planned mainte-nance window and place allESX hosts into mainte-nance mode to minimizeimpact to availability. ESXtypically resumes connec-tion to vVol datastores, andreconnects to VMs, after aperiod of 15-30 minutes au-tomatically without a manu-al intervention.

Scaled vVol environmentswith 500 vVol VDI VMs ormore than 5000 NimblevVol volumes may experi-ence IO disruption whenremoving a member arrayfrom group. Symptom ofproblem would appear asvVol datastores being (inac-cessible). Virtual Machinestatus would also appear as(inaccessible).

Removing mem-ber array frommulti-arraygroup maycause IO disrup-tion to scaledvVol environ-ments

Data ServiceAS-77607

Not applicableWhen attempting to performa pool merge operation, ifthere are a large number ofvolumes that must bestriped across the pool, andone of the arrays has alarge number of pendingdeletes, then it is possiblefor the operation to fail dueto the Data Service beingoverloaded. Symptoms ofthis behavior are if the poolmerge operation hangs forseveral minutes and returnsthe following message: Therequest could not be under-stood by the server.

Pool merge failsdue to too manypending deletes


Not applicableOn new array installations,when creating the first vVoldatastore on the host, thereis a possibility that thedatastore is inaccessibleinitially. However, it will be-come accessible within 5minutes.

Delay for firstvVol datastorebecoming acces-sible

Host IntegrationAS-100561


NimbleOS 5.1.4.0 Known Critical Issues



None. The controller rebootis enough to restore theHigh Availability state.

The array runs post-mortemanalysis when one of theessential NimbleOS ser-vices terminates abnormal-ly. In rare occasions, suchanalysis may consumeenough memory to trip theout-of-memory threshold, atwhich point, the controlleris rebooted in an attempt torestore normal service. HPENimble Storage is currentlystudying ways to run post-mortem analysis with alower memory footprint im-pact.

Unexpectedcontrollertakeover due toout-of-memorycondition

PlatformAS-95087

A Manual Group LeaderFailover will be required torestore Fibre Channel con-nectivity to the hosts.

An Automatic Failover(AFO) of the Group Manage-ment Services will not beinitiated if all Fibre Channel(FC) interfaces on theGroup Leader array fail onboth controllers.

No AutomaticFailover in theevent the hostloses all FC con-nectivity to anarray

System Manage-ment

AS-94737

Reenter passphrase afterAutomatic Failover.

If encrypted volumes areconfigured and AutomaticFailover happens, encrypt-ed volumes wont come on-line automatically after theother array takes overGroup Management ser-vices. The user will need toenter the passphrase onnew group leader array inorder to bring the encryptedvolumes back online.

AutomaticFailover ofGroup Servicesis not supportedfor EncryptedVolumes

System Manage-ment

AS-93553

Not applicableThe Automatic SwitchoverService internally createsand closes threads eachtime during AutomaticFailover (AFO) quorum set-up and tear down. This maycause the service to eventu-ally crash after reaching themaximum thread limit. Thesystem recovers automati-cally when the AutomaticSwitchover Service restarts.

AutomaticSwitchover Ser-vice restarts dueto thread limita-tions

System Manage-ment

AS-89701





A failover can be initiated inorder to restart the GroupManagement Service. Youmay also contact HPE Nim-ble Storage Support torestart the service manually.

When performing a con-troller upgrade to a high-end model, the object limitswill still show the lower lim-its if the Group Manage-ment Service is not restart-ed.

Group Manage-ment Servicemust be restart-ed to unlock ad-ditional volumelimits after con-troller upgrade

System Manage-ment

AS-65615

Not applicableA system managementprocess can restart whenthe system is under heavyload. The system recoversautomatically. The Dataservice is not affected.

Group Manage-ment Servicerestarts underheavy load

System Manage-ment

AS-100254

There is no workaround. Toavoid encountering this is-sue, reduce IO load whenperforming software update.

The underlying scale-outdatabase competes withCASL and other systemprocesses for IOPS. Duringsoftware update, a migra-tion script runs against thedatabase. Under heavy filesystem load, the migrationsteps may not completewithin the expected amountof time. As a result, the mi-gration may timeout leadingto a restart of the GroupData Service. After therestart, the migration shouldeventually complete as nor-mal without any user impactor intervention.

Group Data Ser-vice may restartwhen the arrayis under heavyload during soft-ware update

System Manage-ment

AS-81279

Not applicableDue to a race condition, theData Service can crashduring a graceful shutdowncausing unexpected DataServices restart messagesto be generated. Thisshould not cause any I/Oimpact because the DataService is already in theprocess of shutting down.

Data Servicecan restart unex-pectedly duringshutdown pro-cess

System InternalsAS-69561



Resolved Critical Issues

Resolved Critical Issues in NimbleOS version 5.1.4.0


Not applicableAs in-memory space forFingerprint Index (FI) isconsumed, the arrayswitches to higher adaptivesampling levels in order toreduce the rate of utilizationof FI memory. However, ifthe array consumes FImemory too quickly, whichtypically happens during aData Service restart, thiscreates a race conditionwhere two different threadsare changing adaptivesampling levels at the sametime. This may lead to addi-tional Data Service restarts.The problem is more pro-nounced in CS1000 arraysthat have deduplication en-abled.

Unexpected Da-ta Servicerestarts onCS1000 arrayswith deduplica-tion enabled


Not applicableUnder certain conditions, onarrays with a large numberof SSDs - additional expan-sion shelves and/or largerSSDs - the number of SSDsegments populated canexceed the limit that thepaged vector can hold.Once the vector runs out ofentries, the Data Servicemay restart unexpectedly.

Unexpected Da-ta Servicerestarts on ar-rays with a largenumber of SSDS


Not applicableDuring a software update,after the standby controlleris updated to the newerversion and a failover isperformed to the standbycontroller, under certainconditions, encryption mayget disabled, and volumesmay possibly go offline.This can happen when up-dating from NimbleOS ver-sion 5.1 and above.

After an update,encryption maybe disabled andhosts may expe-rience I/O out-age



NimbleOS 5.1.4.0 Resolved Critical Issues



Not applicable.If a vVol is highly fragment-ed, the array may experi-ence an unexpected DataService restart when thehost requests data block al-location status for a largeoffset range on that volume.

Unexpected Da-ta Servicerestart when ahost requestsdata block alloca-tion status for alarge offsetrange on a vVolvolume which ishighly fragment-ed.


Not applicable.In rare instances, data mi-gration or space deletionmay pause when the DataService internal processingisnt prioritized correctly.

Data migrationor space dele-tion may pausemomentarily dueto Data Serviceprocessing


Not applicableFor iSCSI Group-ScopedTargets (GST), each iSCSIData IP Address is treatedas a separate iSCSI targetport. If there are more than16 iSCSI target ports config-ured on an array, the SCSIRTPG (Report Target PortGroup) command receivedon a Group-Scoped targetmay cause memory incon-sistency. As a result, theData Service may experi-ence multiple restarts.

Data Servicemay restart ifthere are morethan 16 iSCSItarget portalsconfigured forGroup-ScopedTargets on eacharray

SANAS-101583

Change the Encryption se-curity mode to Availablemode before attempting thesoftware update. It can bechanged back to Secure af-ter the Software Update hasbeen completed. Encryptionsecurity mode can be modi-fied within the GUI via Ad-ministration > Security> Encryption > SystemStartup Mode Or, via CLI,issue the following com-mand: group --edit --encryp-tion_mode available

Under certain conditions, anarray group with encryptedvolumes and with Encryp-tion security mode set toSecure may require the re-entry of a passphrase follow-ing a software update.These volumes will be inac-cessible until thepassphrase is re-entered.

Encrypted vol-umes may re-quirepassphrase re-entry following asoftware update

System Manage-ment

AS-94871





The Backup Group Leadername will need to be updat-ed in the Scale-OutDatabase. Please contactHPE Nimble Storage Sup-port.

Under rare circumstances,following a Group LeaderFailover, the Group Manage-ment and Group Data ser-vice may become unavail-able. This may occur whenthe Configuration Databaseis marked with completionstate and the transaction toupdate Scale-Out Databasefails or times out. Thiscauses a mismatch be-tween the Configuration andScale-Out Databases.

Group Manage-ment and GroupData servicerestarts afterGroup LeaderFailover.

System Manage-ment

AS-95763

Please contact HPE NimbleStorage Support.

In certain situations, informa-tion about the Group Lead-ers SSH key may be mis-configured. This may leadto failures in passwordless-SSH connections betweenthe Group Leader andBackup Group Leader ar-rays. When this happens, itmay take longer to set upthe Backup Group Leader,and in some cases, thegroup setup will go out-of-sync.

Passwordless-SSH connectionfails betweenGroup Leaderand BackupGroup Leader

System Manage-ment

AS-95637

Confirm all Domain Con-trollers in the Active Directo-ry environment that is inte-grated with the array arereachable.

In environments with an ar-ray integrated with ActiveDirectory, the create/vali-date session code holds alock on an underlying ses-sions table and then goesto Active Directory to collectmore information about theuser. If this operation takestoo long, the Group Manage-ment service may timeoutto free this lock.

Group Manage-ment servicemay restartwhile collectinguser informationfrom Active Di-rectory

System Manage-ment

AS-60659

Not applicableThere are currently issueswith global search function-ality within the Nimble arrayGUI. Currently, the AdminUser search is not casesensitive. Also, the VolumeCollection, PerformancePolicy, and Chap Accountsearches do not display fil-tered results properly.

Global SearchIssues within theArray GUI

System Manage-ment

AS-96222



Resolved Issues

Resolved Issues in NimbleOS version 5.1.4.0


Not applicableDynamic CPU and diskweight currently depend onthe number of internal datastructures and disk space.There is no mechanism toincrease this weight depen-dent on the amount ofpending deletions. By thetime the weight increasesbecause of low disk space,a large amount of deletionshave already accumulatedand the array encountersother disk space delaymechanisms.

Disk index syn-chronization notprocessing dele-tions fastenough


Not applicable.Deleted space may be freedslowly because checksumoperations are runningwhen the system is criticallylow on space.

Checksum oper-ations runningon a systemmay causedeleted space tobe freed slowly.


To workaround this issue,refresh the web page andlogin to the array again torestart the setup process.However, in some in-stances, you may need tocontact HPE Nimble Stor-age Support in order tohave the arrays web servicerestarted.

When creating a newvCenter Server during dHCIsetup, some customers maysee an error message stat-ing that the vCenter OVA ismissing from the array dueto an API failure. The issuemight arise from a failed orexpired session.

dHCI setup errorduring deploy-ment - vCenterOVA is missingfrom the array

Not applicableAS-102347

Not applicableUnder rare circumstances,the Array Management ser-vice may restart on memberarray after a failover occurs.While in the process of set-ting the role for the memberarray, a notification is sentfrom the Group Leader,which can lead to a racecondition causing the ser-vice restart.

Array manage-ment servicerestarted due torace condition.

System Manage-ment

AS-94673


NimbleOS 5.1.4.0 Resolved Issues



Pause replication until thepool merge successfullycompletes

In certain situations, thepool merge operation maycause resource contention,resulting in replication oper-ations to fail a health check.This may also cause theGroup Management Serviceand the Nimble array GUIto become temporarily un-available.

Group Manage-ment service un-available duringpool merge

System Manage-ment

AS-97005

No workaround.The Group ManagementService may restart unex-pectedly when attemptingto create for key-value (KV)pair metadata for systemobjects such as Volumes,Snapshots, Snapshot Col-lections etc. This couldhappen only when the KVscrubber task (scheduled torun once weekly) is runningat the same time the GroupManagement Service is al-so trying to create new KVpair metadata.

Group Manage-ment Servicerestarts whentrying to createkey-value (KV)pair metadata

System Manage-ment

AS-96004

Restarting the AutomaticSwitchover service on theBackup Group Leader recov-ers from this failure. Thiscan be done by issuing afailover on the BackupGroup Leader.

In rare instances, if thegroup --migrate commandis issued on the GroupLeader array and the Back-up Group Leaders Automat-ic Switchover Service hap-pens to restart at the sametime (due to different rea-son), it is possible that theBackup Group Leader wontbe able to promote itself asleader.

Issuing group --migrate could re-sult with noGroup Leader ifthere is a failureon Backup lead-er

System Manage-ment

AS-95263

Not applicable. The ArraySwitchover Service recov-ers after the restart.

The witness log collectionrequested through the ArraySwitchover Service causesthe array to exceed memoryallocations. If the ArraySwitchover Service exceedsthe memory limits, the ser-vice is restarted by ProcessManagement Service as aprecaution.

ArraySwitchover Ser-vice restarts dueto memory is-sues

System Manage-ment

AS-95493





Not applicableUnder rare circumstances,the Group Managementservice on the array mayrestart unexpectedly after areplication partner is delet-ed. This occurs if a periodicconnection task betweenthe partners happens to berunning at the same time.

Group Manage-ment ServiceRestarts afterdeleting replica-tion partner

System Manage-ment

AS-92937

Not applicablePool partner creation mayfail during a group merge ifSynchronous Replication isbeing configured when net-work outage is taking place.

Partner creationfails duringgroup merge op-eration due tonetwork issueand Syn-chronous Repli-cation config

System Manage-ment

AS-98990

Not applicableWhen running the partner --list command via the arrayCLI, the output shows alarge throttle limit set for thereplication partner. This in-formation is inaccurate.

Replication part-ner throttle limitis displayed in-correctly

System Manage-ment

AS-89950

Not applicableIn rare instances, the GroupManagement Service of anarray group may restart un-expectedly due to raceconditions that exist withinthe internal processing ofsnapshot collection creationand deletions.

Group Manage-ment Servicemay restart dueto snapcoll cre-ation/deletionworkflows

System Manage-ment

AS-87192

If a user needs to delete areplica volume, the replicavolume must first beclaimed (i.e., change owner-ship to the current group).The CLAIM option is avail-able in the detail page forthe replica volume.

A replica volume cannot bedeleted, which is why thedelete operation is notavailable within the HPENimble Storage Array GUI.

Replica volumecannot be delet-ed

System Manage-ment

AS-94429





Increase the limit of thefolder to be larger than thecurrent mapped usage ofthe folder and bring thenecessary volumes backonline. View the OfflineReason of the volume in theGUI or CLI using the follow-ing command: vol --list Viewif a volume is non-writablein the GUI or CLI with thiscommand: vol --info <vol-ume name> | grepnon_writable To take vol-ume out of read-only modefrom CLI use the followingcommand: vol --edit <vol-ume name> --readonlyno

Upon updating from a pre-5.1.x.x software version toa post-5.1.x.x version, vol-umes can be taken of-fline/read-only due to folderlimits being enforced post-5.1.x.x and changes to theway that volume usage isreported. There is a conver-sion that occurs on the limitto help account for this dif-ference in usage; however,it does not account for clonesavings. This can cause thelimit to not be increasedsufficiently to account forthe new method of spacereporting.

After update to5.1.x.x, volumesin a folder with alimit are takenoffline due tofolder limit beingexceeded

System Manage-ment

AS-99849

Not applicableDue to a timing issue, theGroup Management Servicemay restart unexpectedlywhen a user is deletedwhile a user task is stillpending.

UnexpectedGroup Manage-ment ServiceRestart whenuser is deletedwhile user actionis pending

System Manage-ment

AS-93297

Known Issues

Known Issues in NimbleOS version 5.1.4.0


If RAID is degraded for anextended period and DataService restarts occur, con-tact HPE Nimble Storage toassess adjusting allocatedbuffer resources.

When RAID is degraded, IOneeds to be reconstructedby reading from multipledisks, and an internal buffermay exhaust its allocatedresources. In rare caseswhen multiple disks are de-graded, the Data Servicemay restart unexpectedly.

Data Servicemay restart unex-pectedly whenRAID is in de-graded mode



NimbleOS 5.1.4.0 Known Issues



Not applicableWhen zero data is writtento an upstream volume in-volved in SynchronousReplication, an internal flagis not passed properlyamong various layers fromupstream to downstream.Then, zero data on the up-stream is treated as SCSIunmaps on the down-stream. As a result, a largespace reporting discrepancycan occur between the up-stream and downstreamvolumes.

Space reportingdiscrepancy be-tween upstreamand downstreamvolume in Syn-chronous Repli-cation configura-tion


Retry operation after a fewminutes to reassign array topool.

Assigning an array to a poolimmediately after unassign-ing it from the same poolwill fail with the followingerror - Failed to assign ar-rays to the pool: A serviceis not running or is notreachable

Unassigning andreassigning ar-ray to a poolwithin 5 minuteswill fail


To see the correct poolswithin the group, close thecreateDatastore dialog andlaunch the dialog again, se-lecting the group for creat-ing datastore.

When attempting to createa vVol datastore, changingthe selection of the groupdoes not fetch the latestgroup-related pools data.This is caused by a cachingissue.

Error: Could notfind pool in vVoldatastore cre-ation wizard


When this problem occurs,click on any item in themenu (Home, vVOLVMs,etc). and then click on thedatastore to show the prop-er results.

The list view result is notdisplayed properly afterswitching between theVMFS/vVOL datastorewhen clicking paginationrapidly, without waiting forthe resulting pages to load.

Datastore list isnot displayingproperly if previ-ous and nextbuttons arerapidly clickedrepeatedly.


No workaroundWhen you use the HPENimble Storage vCenterPlugin for the HTML 5client, the NimbleOS arraytable header displays ablank instead of displayingthe vVol virtual machine ti-tle. This does not affect howthe client performs.

Instead of vVolVM name, blankspace is dis-played in vCen-ter plugin






Not applicableThe Nimble Drive Error Re-covery (NDER) is activatedfor drives failing I/O in anattempt to recover the drive.In rare cases, the processsurpass the typical SCSItimeout of 60 seconds,causing host I/O inaccessi-bility.

NDER processmay lead to hostreconnects

PlatformAS-96053

Active controller will operateas expected after the faultystandby controller is dis-abled. (1) Remove the re-booting standby controllerfrom the chassis or contactHPE Nimble Storage Sup-port to remotely power offthe rebooting standby con-troller from the arrays activecontroller. (2) Then reseator disk --remove | add thefailed SSDs to recover theSSDs.

In a rare case, when thestandby controller is in areboot loop, this may dis-rupt the Data Service. As aresult, the array will reportseveral failed SSDs.

Data Servicedisrupted whenstandby con-troller is in a re-boot loop

PlatformAS-49747

No workaround is required.The array will recover itselfautomatically by restartingthe Data Service.

On rare occasions, the ar-ray groups Data Servicemay fail to initialize if a shelfstate change occurs simul-taneously.

Delay with DataService startingduring shelfstate change

PlatformAS-101570

Contact HPE Nimble Stor-age Support.

In rare cases, multi-bit ECCerrors on the NVRAM cardmay cause the Data Serviceto restart unexpectedly.

Multi-bit Error-Correcting Code(ECC) errors onNVRAM cardcaused DataService restart

PlatformAS-56942

Address the network storm,and then perform a con-troller failover.

On lower-end platforms witha lower number of CPUcores, a network stormcould keep the kernel busyserving network interruptrequests, and ultimatelydelay IO requests. This inturn causes IOs to timeoutand causes a Data Servicerestart to recover.

Network stormcauses writes toslow down to apoint where Da-ta Servicerestarts due to ahealth check fail-ure

PlatformAS-55765






In rare cases, heavy loadcompounded by unalignedworkloads on high-endplatforms with many CPUcores can cause theNVRAM driver to becomeoverloaded when all coresare busy. The Data Servicemay restart unexpectedlywith a health check error.

NVRAM over-loaded on highend platformsunder heavystress

PlatformAS-56600

Schedule time for a SalesEngineer to field-image thearray.

Upon removing an arrayfrom a group and removingany expansion shelves fromthat array, the array willneed to be re-imaged priorto any array reuse.

Removing an ar-ray from a groupleaves the arrayin an unusablestate.

PlatformAS-32895


When the SAS HBA detectsfaulty states, to recover, thearray needs to reset theSAS HBA’s firmware. TheSAS HBA firmware resetcan block disk I/Os signifi-cantly longer than our HighAvailability monitoring time-outs allow. Instead, a con-troller reboot is triggeredimmediately if this state isdetected, resulting in anunexpected takeover event.

Unexpectedcontrollertakeover due toincorrect state ofthe SAS HBA

PlatformAS-33725

A valid ESXi license mustbe assigned to the server.

When adding a server withan expired ESXi licensethrough the vCenter plugin,you may see an error say-ing - Failed to submit a taskto add server.

Addition of aserver with ex-pired ESXi li-cense fails

Not applicableAS-95054





NoneIn NimbleOS, the Data Ser-vice and the SCSI HighAvailability Service use thesame logic for processingFibre Channel connections.Due to a software defect inthe Fibre Channel connec-tion termination logic, eitherof these services may stopunexpectedly with a corefileand restart. The softwaredefect occurs when code-paths related to connectiontermination are simultane-ously processed: - process-ing a Connection_Lossevent from the FC driver, forconnection A - performingan implicit logout of connec-tion A, due to receipt of aNew_Connection event fora conflicting connection B(between the same host/ar-ray ports). The restart of theaffected service causes abrief interruption in the ar-rays ability to service incom-ing requests.

Data Service orSCSI High Avail-ability ServiceRestart whenprocessing FibreChannel connec-tions

SANAS-94539

Not applicableWhen shutting down or re-booting the array in aplanned or unplanned fash-ion, or working with HPENimble Storage Support torestart the service individu-ally, the Data Service maycrash unexpectedly duringits normal shutdown se-quence. The service will re-cover automatically. Thereshould be no impact sincethe service is already in theshutdown sequence.

Data Servicemay restart unex-pectedly duringshutdown

SANAS-89933

None required. The processis shutting down.

While the group manage-ment process is shuttingdown, it may experience afault that causes a restartattempt.

Group Manage-ment restartswhile shuttingdown

SecurityAS-56019





Validate the DNS serversdefined on the array andeliminate any inaccessibleor unresponsive DNSservers. If all defined DNSservers have been con-firmed and the Event ser-vice continues to crash,contact HPE Nimble Stor-age Support.

Due to the use ofSIGALARM signals to indi-cate a DNS timeout inlibcurls standard system re-solver, when the signalhappens it can sometimesswitch the application con-text to the signal handler,causing the Event serviceto crash unexpectedly.

The Event ser-vice may crashduring applica-tion contextswitch

System Manage-ment

AS-82317

Correct the DNS or SMTPconfiguration to a valid ad-dress by ensuring that aping to the defined addresssucceeds.

We create multiple threadsto deliver emails, but weuse a non-threadsafe libcurlcall to dispatch them.Therefore, the lock needsto be around libcurl call. Ifthere is a misconfiguredDNS or SMTP server, thecurl call will timeout. If thereare greater than 7 emailswaiting to be delivered andall are suffering a timeout,we will starve the healthchecking for more than the300-second health checktimeout causing the EventManagement service torestart.

Flood of time-outs causingEvent Manage-ment servicerestart

System Manage-ment

AS-68651

Re-run array removal toclear the group leadermetadata.

In some cases when thereis high load, array removalcan take longer than usualand timeout, which leads toan intermediate state wherethe group leader believesthe array still belongs to thegroup, but the array hasbeen removed.

Array removalmight not com-plete in time

System Manage-ment

AS-28992

Not applicableIf a user tries to create anew user account, but theuser doesnt have the privi-lege to do so, the user cre-ation will fail. However, anaudit log entry is not creat-ed.

No Audit Log en-try is created ifuser does nothave the privi-lege to createuser

System Manage-ment

AS-71090

Not applicableIn rare cases, a memory in-consistency causes an un-expected Group Manage-ment Daemon (GMD)restart.

UnexpectedGroup Manage-ment restart dueto memory incon-sistency

System Manage-ment

AS-55005





No workaround is needed.The service recovers on itsown.

In Automatic Switchoverenvironments, in rare in-stances, network isolationof the Group Leader andBackup Group Leader maycause the service that han-dles the automaticswitchovers to restart unex-pectedly.

Network isola-tion of the GroupLeader andBackup GroupLeader arraymay lead to Auto-maticSwitchover ser-vice restarts

System Manage-ment

AS-94683

This restart is non-disrup-tive to the data on the array,and the Array Managementrecovers after the restartoccurs.

The arrays database sys-tem may become unavail-able for a limited time whenthere is a failure in settingup the Backup GroupLeader. When attempting todiscover a new BackupGroup Leader, the ArrayManagement Service mayrestart due to a race condi-tion.

Array Manage-ment Servicerestarts duringBackup GroupLeader discov-ery

System Manage-ment

AS-98953

Please contact HPE NimbleSupport.

Following a power outage,it is possible that the Back-up Group Leader is not as-signed to the group. Thismay occur if the SODBdatabase does not start dueto an SSH key issue.

Backup GroupLeader is not as-signed due topower outage

System Manage-ment

AS-99702

Not applicableThere is a --force switchavailable when deleting aperformance policy via theHPE Nimble Storage ArrayCLI. This --force switchdoes not work and will failwith the following: ERROR:Failed to delete perfor-mance policy. Resourcebusy. The --force commandis not supported since thespecified performance poli-cy should not be removedwithout first checking itsvolume or folder associa-tions.

Force deletion ofuser definedperformancepolicy should notbe supported

System Manage-ment

AS-74242





Please reissue the com-mand. If the operation wasalready performed by theearlier command, an appro-priate message will be re-turned.

Under system busy condi-tions, when an excessiveamount of operations arebeing issued in parallel ortoo many internal retries areoccurring to perform tasks,you may receive a No mes-sage received error after is-suing a CLI command.

Error No mes-sage receivedafter issuing CLIcommand

System Manage-ment

AS-90633

Not applicableThe group --list_limits CLIcommand does not list theSynchronous Replicationvolume count Limit. Syn-chronous Replication on5.1.0.0 and later can protectup to 128 volumes.

SynchronousReplication Vol-ume Count Limit

System Manage-ment

AS-89124

Not applicableSome internal operationsmay timeout when configur-ing the replication partner,and the following errormessage occurs: Failed tosynchronize configurationto partner. Internally, it willretry as needed in order tocomplete the necessaryprocess to set the Syn-chronous Replication part-ner. No user action is neces-sary.

While editing theschedule to as-sign the Syn-chronous Repli-cation partnerfor a volume col-lection, the fol-lowing error oc-curs: Failed tosynchronizeconfiguration topartner.

System Manage-ment

AS-98561

Not applicableOn rare occasions, a veryslow network (or networkissues like dropped pack-ets) can cause a restart ofthe Group Managementservices. However, replica-tion and other services willresume where they left offprior to the restart.

Network issuesmay causerestart of GroupManagementservice

System Manage-ment

AS-28589





Not applicableAdding or removing vol-umes to a volume collectionwhile replication is inprogress for that volumecollection could potentiallylead to a restart of theGroup Management ser-vices. This does not have asignificant impact however,since replication (and otherservices) resume wherethey left off before therestart

Adding/removingvolumes whilereplication is inprogress maycause GroupManagementrestart

System Manage-ment

AS-44941

Not applicableIn a rare timing issue, theGroup Management Servicefor an array group mayrestart unexpectedly if asnapshot is deleted whileits checksums are beingsent to the downstream ar-ray.

Group Manage-ment Servicerestarts unex-pectedly whensnapshot isdeleted

System Manage-ment

AS-100171

Not applicableIf clones are created usingan unmanaged snapshot,then this unmanaged snap-shot will not be deletedeven if cleanup is enabled.

Unmanagedsnapshots re-main aftercleanup is en-abled

System Manage-ment

AS-93113

Not applicableThe Array ManagementService may restart unex-pectedly when the array isunder heavy load, hasmany snapshots scheduled,has performed a groupmerge in the past, and hasrecently performed an auto-matic Group LeaderFailover.

Array Manage-ment Servicerestarts unex-pectedly follow-ing automaticGroup LeaderFailover

System Manage-ment

AS-100382





The alarms can be deletedmanually either in the GUIor on the CLI.

After the update to 5.1.x.xor later, the Snapshot limitwarning alarm is no longerused. This presents a situa-tion where stale alarms arepresent on the array andthey will not be clearedeven if the space situationis rectified. The alarm fol-lows the following format:WARNING Mon DD YYYYHH:MM:SS Acknowledged- Volume <volumename> snapshot spaceusage is over the config-ured warning limit.

Snapshot limitwarning alarmspersist after up-date to 5.1.x.x orlater

System Manage-ment

AS-98694

Not applicableIn rare cases, the standardmemory allocator does notreuse freed memory effi-ciently during heavy work-loads. When Group Manage-ment Daemon (GMD) utiliza-tion becomes too high,GMD may restart to recov-er.

UnexpectedGroup Manage-ment restart dueto high memoryutilization

System Manage-ment

AS-49590

Not applicableGroup management servicemay restart during softwareupdate due to race condi-tion involving unlocking thedownload lock file.

Group manage-ment servicemay restart dur-ing software up-date

System Manage-ment

AS-72559

Not applicableWhen the HPE NimbleStorage array is configuredto use Active Directory inte-gration, the array is joinedto one specific domain, asa domain member. Undernormal circumstances,users in trusted domainswill also be able to authenti-cate to the array. If one ormore trusted domains arejoined to the forest using anMIT Kerberos type trust re-lationship, users and groupsin any trusted domain (e.g.not the domain the array isjoined to) will be unable toauthenticate to the array.

HPE NimbleStorage arraycompatibility is-sues with MITKerberos trusttypes

System Manage-ment

AS-95212





Once the array is able todetermine its deduplicationcapability, all newly createdvolumes will have dedupeenabled, if specified. In or-der to enable dedupe on thepreviously created volumes,you may run the followingcommand via the HPENimble Storage Array CLI:vol --edit <vol_name>--dedupe_enabled yes

After a CSx000 array is in-stalled, it takes one minutefor the array to determineits deduplication capability.If a volume is created priorto this, it will not havededupe enabled even if thearray is dedupe capable.

Unable to creatededupe enabledvolumes on anew install

System Manage-ment

AS-86545

The Group ManagementService will eventuallyrestart itself

Enabling and disabling thededupe setting on volumesand concurrently deletingvolumes can cause theGroup Management Ser-vices to become temporarilyunavailable on the array.

Group Manage-ment Service istemporarily un-available afterdeleting volumes

System Manage-ment

AS-101535

Not applicableCurrently, there is no CLIsupport for changing thewitness port. The nimble-witnessd.service file needsto be edited manually.

No CLI supportfor changing theWitness Port

System Manage-ment

AS-92157

Click the X-icon button todelete any unused/emptyinput fields under the sec-tion of FQDN or IP Address-es.

When generating a customcertificate, the user is al-lowed to add empty FQDNor IP Address input fieldson the form and then clickthe GENERATE button.This will produce an errormessage popup (modal)returned from the network(backend).

User is able tosubmit emptyFQDN or IP Ad-dresses whenrequesting cus-tom certificate

System Manage-ment

AS-100989

Not applicableOn the certificate list page,although every listed certifi-cate entry has a checkboxnext to it, the user cannotchoose multiple selectionsfor deletion. The user is al-lowed to only select oneentry to delete at a time.

Only one certifi-cate may be se-lected at a time.

System Manage-ment

AS-99584

Not applicableWithin the HPE NimbleStorage array GUI, cus-tomer SSL certificate importis only supported on GoogleChrome version 71 or later.

Custom SSLcertificate importnot supported onolder versions ofGoogle Chrome

System Manage-ment

AS-99343





Not ApplicableThe PASSWORD refers tothe one the user needs toenter for the PKCS12 bun-dle file to be imported. Thecorrect phrasing should beBUNDLE PASSWORD.

Ambiguity ofPASSWORDwhen importinga PKCS12 bun-dle

System Manage-ment

AS-99353

Not applicableWithin the Nimble ArrayGUI when browsing to theDiagnostics page underAlerts and Monitoring,clicking save without updat-ing the user analyticscheckbox value incorrectlyshows a successful mes-sage.

Clicking savewithout updatingthe user analyt-ics checkboxvalue incorrectlyshows a suc-cessful message

System Manage-ment

AS-100463

To keep the same reminderfrequency and reset thenext reminder time basedon the current time, changethe reminder frequency toa different value, save it,and change it back andsave it, or use CLI to makethe change.

When updating an alarmfrom the Events > Alarmspage in GUI, selecting analarm and clickingCHANGE REMINDER but-ton, without changing thereminder frequency time,and clicking SAVE button,does not change next re-minder time. This behavioris different from CLI. Settingalarm reminder frequencyto the same value from CLIresets the next remindertime based on the currenttime.

Setting alarm re-minder frequen-cy to the samevalue from GUIdoes not changenext remindertime

System Manage-ment

AS-98177

When the controller is backup, all the information isdisplayed correctly onhardware page.

When a controller is down,the user may see incorrectrepresentation of physicalports within the HardwarePage of the array GUI. Thisis due to the lack of informa-tion from the missing con-troller.

Incorrect informa-tion on hardwarepage displayedwhen controlleris down

System Manage-ment

AS-87701

To work around this issue:1. Log into the destinationarray to resolve the con-flicts. 2. Attempt the groupmerge again.

Currently within the HPENimble Storage Array GUI,when performing a groupmerge, if there is a largeamount of group mergeconflicts (1000 or more), theGUI is unable to processand resolve all of them.

Group Merge viaGUI unable toprocess largeamount of con-flicts

System Manage-ment

AS-77372





Delete the appropriate pro-tection schedule with asnapshot interval of lessthan five minutes to meetthe system limits of theseprotections schedules, andretry the group merge oper-ation.

The GUI shows a generalerror message during groupmerge when the total countof snapshot schedules witha snapshot interval of lessthan five minutes exceedsfive: System limits for thenumber of protectionschedules would be violatedafter adding the array. Cur-rent limit is 5.

GUI shows ageneral errormessage duringgroup mergewhen, for thetwo groups, thetotal number ofsnapshot sched-ules with a snap-shot interval ofless than fiveminutes exceedsfive

System Manage-ment

AS-21697

The user can navigate tothe Stack Vision Summarypage from the link at the topof the page

The Stack Vision menuwhen clicked should alwaysshow the Summary page asthe landing page. Whenclicked for the first time itcorrectly shows the Summa-ry page as the landingpage. If the user then navi-gates to the Details pageand again clicks on theStack vision menu, thelanding page is the Detailspage instead of Summarypage.

Stack Visionmenu displaysthe Details Pageinstead of Sum-mary Page

System Manage-ment

AS-99656

Pool merge is not allowedif Synchronous Replicationis enabled and pool mergeis not allowed when a wit-ness configured. If an arraygroup has a witness config-ured for AutomaticSwitchover and has Syn-chronous Replication config-ured, when a user tries toperform a pool merge, thefollowing error is generated:“pool merge is not allowedwhen witness is config-ured”. In this case, if theuser removes the witnessand then re-attempts thepool merge, the followingerror is then generated:“Pool merge is not allowedwhen involved in sync repli-cation”. This error shouldsupersede the previous er-ror.

Incorrect order-ing of poolmerge errormessages whenSynchronousReplication andWitness are con-figured

System Manage-ment

AS-95591





Run the following commandvia CLI: snap --list --all --unmanaged

The Array GUI does notspecify which snapshots areunmanaged and no longerbelong to a volume collec-tion.

Array GUI doesnot specifywhich snapshotsare unmanaged

System Manage-ment

AS-93157

After a new custom certifi-cate has been imported orexisting certificate is delet-ed, please close the brows-er where the action wasperformed and reopen anew one to guarantee anew connection request tothe NimbleOS web inter-face.

After changing a certificate,the GUI may present an er-ror such as follows: Theweb service is very slow orunreachable...

Browser be-comes unstableupon certificatechange

System Manage-ment

AS-99024



NimbleOS 5.1.4.0 Release Notes - Hewlett Packard Enterprise · VMware has announced End of General...

Documents

Transcript of NimbleOS 5.1.4.0 Release Notes - Hewlett Packard Enterprise · VMware has announced End of General...