NimbleOS 5.2.1.0 Release Notes...NimbleOS 5.2.1.0 Special Notes Note Description As of vSphere 7.0,...

NimbleOS 5.2.1.0 ReleaseNotes

Version 5.2.1.0

Published June, 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

Thursday June 18, 2020 10:04:29

Document ID

trw1579814111116

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: https://infosight.hpe.com

For all other general support contact information, go tohttps://www.hpe.com/us/en/services/nimble-storage.html.

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

Legal Notices

https://infosight.hpe.com


https://www.hpe.com/us/en/services/nimble-storage.html

Contents

NimbleOS 5.2.1.0..........................................................................................4Important Update Note.........................................................................................................................4

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

New Features in 5.2.1.0.......................................................................................................................8

Documentation...................................................................................................................................10

Verified Update Paths........................................................................................................................11

Known Critical Issues.........................................................................................................................14

Resolved Critical Issues.....................................................................................................................19

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

Known Issues.....................................................................................................................................25

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

Nimble

NimbleOS 5.2.1.0

5.2.1.0Version:

Thursday June 18, 2020 10:04:29Revision:

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 5.0.4.0 or later to update to NimbleOS5.2.1.0.

CRITICAL


NimbleOS 5.2.1.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.

Note

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 with the “Linux Integra-tion Services” kit installed, or with hv_storvsc drivers in such configura-tions can lead to Red Hat bug 1364282, which can cause an unexpectedservice 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

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


NimbleOS 5.2.1.0 Special Notes

DescriptionNote

As of vSphere 7.0, VMware has discontinued the flex client. Consequent-ly, the HPE Nimble Storage vCenter Plugin no longer supports the flexplugin for vCenter 7.0.

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_name. This command returns the Pool capacity (MiB), which isthe "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

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

Important

Numerous host integration toolkits are supported in NimbleOS 5.2.1.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




DescriptionNote

HPE Nimble Storage recommends that you update to HPE NimbleStorage Windows Toolkit (NWT) 7.0.1 or later if you are using MicrosoftVSS Synchronization and NimbleOS 5.1.4.200 or later.

Using application consistent snapshots with earlier versions of NWTand NimbleOS 5.1.4.100 may result in the following error messages:

• In the host's VSS requestor log (C:\ProgramData\Nimble Stor-age\Logs\VssRequestor.log):

PID:1996 TID:5752 ERR reqcommon. cpp:683 Request-Status=QueryStatus(), Function=pAsync->QuerySta-tus(), Error=VSS_E_PROVIDER_VETO, rc=SystemError,ca=ContactSupport

• In the Windows event viewer:

event id 4100: EndPrepareSnapshots method: failedto find LUN s/n <SERIAL_NUMBER> on connected ar-rays. Make sure that the Nimble array version iscompatible with this version of Nimble WindowsToolkit.

event id 4170: Nimble VSS provider is not compati-ble with the current version of the Nimble arraysoftware(). Install appropriate version of theNimble VSS provider.

NWT 7.0.1 resolves this issue.

Important

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

See the NCM for VMware Release Notes 7.0 or later and the latestVMware Integration Guide for further details.

To locate the latest version of the guide, log in to HPE InfoSight. ChooseResources > Nimble Storage Documentation. In the left pane, clickIntegration Guide, then click Connection Manager (NCM) for VMware.From the list displayed, choose the version of the guide that you want.

Important



DescriptionNote

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

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

Fan-Out Replication

You may now use volume snapshot replication to replicate to two destinations simultaneously.

HPE Cybersecurity – Signed Updates

NimbleOS Releases are now digitally signed by HPE. Code signing ensures the authenticity of the provider(it is HPE) and the integrity of the software download.

Fibre Channel Target Driven Zoning

HPE Nimble Storage arrays are now able to program the zones in the Fibre Channel (FC) fabric usinginformation from the initiator groups that have been configured. This removes the requirement for theadministrator to program the FC zones using separate fabric management tools.

Array Upgrade for AFxxxx/CSxxxx to AFxx/HFxx (Offline)

HPE Nimble Storage now supports data-in-place upgrades from the previous generation of arrays to thecurrently shipping arrays. This version of the upgrade process requires a brief down time while the existingarray chassis is replace with the new one, and the media is moved from the older array to the new array.

Support for 10,000 Volumes on AF40 Arrays

The limit on the number of volumes supported by an HPE Nimble Storage AF40 model array is now 10,000,up from 1,000 volumes in previous NimbleOS releases.

Storage Class Memory

NimbleOS now supports new 1.5 TB storage class memory cards. Support is limited to HPE Nimble StorageAF60 and AF80 model arrays.

Synchronous Replication: Witness OVA

The Peer Persistence feature requires an external witness. The Witness is available for download fromInfoSight as a virtual machine packaged as an OVA.


NimbleOS 5.2.1.0 New Features in 5.2.1.0



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


dHCI Automatic Update

HPE Nimble Storage dHCI now provides an Update tab in the HPE Nimble Storage vCenter Plugin thatallows you to perform an automatic update when there is a new version of NimbleOS, ESXi, or HPE NimbleStorage Connection Manager for VMware.

dHCI Server Configuration Limits

The limit on the number of servers supported in a dHCI cluster has increased to 32.

dHCI Support for Intel and AMD Processors

dHCI adds support for ProLiant servers using AMD processors. It continues to maintain support for Intel-basedProLiant servers. The Validated Configuration Matrix provides information about which server models aresupported.

Note You can use either Intel-based ProLiant servers or AMD-based ProLiant servers in your dHCIconfiguration. You cannot use both in the same cluster.


NimbleOS 5.2.1.0 New Features in 5.2.1.0


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 Nimble Storage Documentation page provides a search interface that allows you to search for informationacross all documentation, including support and knowledge base articles, best practices, solutions andintegration guides, product documentation, and configuration matrices.

To go directly to a document, use the navigation pane on the left side of the Nimble Storage Documentationpage. The navigation 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

If you are using an HPE Nimble Storage dHCI-enabled array, you should also check the dHCI DeploymentGuides and Getting Started Guide.

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.


NimbleOS 5.2.1.0 Documentation


Each task described by a workflow document is explained in detail in the GUI Administration Guide and theCLI Administration Guide.

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.

Note A single Host Integration Guide supports multiple version of NimbleOS and the companion IntegrationToolkit software packages. The version number listed on the guide might be different from the version numbersof the NimbleOS and Toolkit software packages that it supports.

Verified Update Paths

Table 1: From Versions 5.x

From Versions 5.x

To VersionFrom Version

5.2.1.05.1.4.200

5.2.1.05.1.4.100

5.2.1.05.1.4.0

5.2.1.05.1.3.100

5.2.1.05.1.3.0

5.2.1.05.1.2.100

5.2.1.05.1.2.0

5.2.1.05.1.1.0

5.2.1.05.0.9.100

5.2.1.05.0.9.0

5.2.1.05.0.8.100

5.2.1.05.0.8.0

5.2.1.05.0.7.300

5.2.1.05.0.7.200

5.2.1.05.0.7.100

5.2.1.05.0.7.0

5.2.1.05.0.6.0

5.2.1.05.0.5.300

5.2.1.05.0.5.200


NimbleOS 5.2.1.0 Verified Update Paths

From Versions 5.x


5.2.1.05.0.5.0

5.2.1.05.0.4.0

5.0.9.1005.0.3.100

5.0.9.1005.0.3.0

5.0.9.1005.0.2.0

5.0.9.1005.0.1.100

5.0.9.1005.0.1.0


From Versions 4.x


5.1.4.2004.5.6.0

5.1.4.2004.5.5.0

5.1.4.2004.5.4.0

5.0.9.1004.5.3.0

5.0.9.1004.5.2.0

5.0.9.1004.5.1.0

5.0.9.1004.5.0.0

5.0.9.1004.4.1.0

5.0.9.1004.4.0.0

5.0.9.1004.3.1.0

5.0.9.1004.3.0.0

5.0.9.1004.2.1.0

5.0.9.1004.2.0.0

5.0.9.1004.1.0.0


From 3.x Versions


5.0.9.1003.9.3.0

5.0.9.1003.9.2.0

5.0.9.1003.9.1.0

5.0.9.1003.9.0.0

5.0.9.1003.8.1.0



From 3.x Versions


5.0.9.1003.8.0.0

5.0.9.1003.7.0.0

5.0.9.1003.6.2.0

5.0.9.1003.6.1.0

5.0.9.1003.6.0.0

5.0.9.1003.5.4.0

5.0.9.1003.5.3.0

5.0.9.1003.5.2.0

5.0.9.1003.5.0.0

5.0.9.1003.4.1.0

5.0.9.1003.4.0.0

5.0.9.1003.3.0.0

5.0.9.1003.2.1.0

5.0.9.1003.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.6.02.3.18.0

2.1.9.12.0.7.02.3.18.02.1.9.04.5.6.02.3.16.0

2.1.9.12.0.6.*2.3.18.02.1.8.04.5.6.02.3.15.0

2.1.9.12.0.5.02.2.9.02.1.7.04.5.6.02.3.14.0

2.1.9.12.0.4.02.2.9.02.1.6.04.5.6.02.3.12.*

2.2.9.02.1.5.04.5.6.02.3.9.*

2.2.9.02.1.4.04.5.6.02.3.8.0

2.2.9.02.1.3.04.5.6.02.3.7.0

2.2.9.02.1.2.04.5.6.02.3.6.0

2.1.9.12.1.1.04.5.6.02.3.4.0

2.1.9.12.1.0.04.5.6.02.3.3.0

4.5.6.02.3.2.1

4.5.6.02.3.2.0

4.5.6.02.3.1.0

3.9.3.02.2.11.0

3.9.3.02.2.10.0



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


3.9.3.02.2.9.0

3.9.3.02.2.7.*

3.9.3.02.2.6.0

3.9.3.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.2.1.0

WorkaroundDescriptionTitleComponentID

Not applicableUnder certain conditions,the Data service may restartduring array internal indexprocessing within a shorttime span. Transactionsduring the processing maytake too long to completewithin the defined timespan, which causes theservice to restart.

Data Servicemay restart unex-pectedly due tohealth check fail-ure.

Data ServiceAS-105458


NimbleOS 5.2.1.0 Known Critical Issues



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


Contact HPE Nimble Stor-age Support.

In rare cases during indexcreation, when a 16 TiBvolume is fully unmapped,the resulting index structurefails verification and bringsdown the Data Serviceleading to an outage.

Index verificationfails if a 16 TiBvolume is com-pletely un-mapped causingData Service togo down


Not applicableDuring snapshot replicationof a dedupe-enabled vol-ume, the downstream arrayfile system may restart dueto an out-of-memory condi-tion.

Snapshot replica-tion of deduplica-tion-enabled vol-umes may leadto File Systemrestart


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 applicableThe Data service mayrestart when Bin Migrationis going on. This can hap-pen when following activi-ties happen together: 1. Binmigration is occurring for avolume. 2. Group Manage-ment service restart (be-cause of any reason). 3.Group Management serviceunable to re-sync with Dataservice after &nb-sp; &nb-sp;restart. This can lead toData service restart but itwill not impact bin migrationas after Data service restartbin migration will resumedautomatically.

Rare race condi-tion betweenData service andGroup Manage-ment servicecause Data ser-vice restart


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

If after 20 minutes the con-troller sensors do not reportgood state, please contactHPE Nimble Storage Sup-port for assistance.

During boot up due to aknown Intel defect the con-troller sensors may reportmissing for a period of timein the array alerts. Afterabout 15-20 minutes, it re-turns to a valid state andthe sensors should reportvalid readings again.

Controller sen-sors missing forAFxx/HFxx ar-rays

PlatformAS-86764

Contact HPE Nimble Stor-age Support if there aremultiple restarts to workaround the issue.

In rare cases while commit-ting large internal transac-tions, the process maytimeout. As a result, theData Service may restart torecover the condition.

Data Servicemay restartwhile committinglarge internaltransactions

PlatformAS-103129





Not applicableDuring internal file opera-tions, processes may bewaiting for a lock to be re-leased. If the wait time ex-ceeds 30 seconds, a ser-vice health check mayrestart the Data service torecover.

Data servicemay restart dur-ing when file op-eration timeoutis exceeded

PlatformAS-86099

In order to add more 4 ormore Proliant Servers, theworkaround is to add up to3 servers at a time from theplugin.

Currently, if customer plansto add 4 or more Proliantsservers in their dHCI deploy-ment via the plugin, the op-eration fails.

Plugin: Cannotadd 4 or moreservers in thedHCI deploy-ment

ProstackAS-104924

The workaround is to createa pool on backup groupleader and retry the com-mand.

Group management servicerestarts during shelf activa-tion on backup group lead-er. This happens when usertries to activate a shelf inBackup group leader whichis not associated with anypool, group managementservice gets restarted be-cause of an empty pool.

Group manage-ment servicerestarts duringshelf activation

System Manage-ment

AS-103976

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 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 applicableIn rare cases, when an ar-ray is not able to transitionto out-of-sync when theBackup Group Leaderdatabase is unresponsive,the Group / Array Manage-ment Service may restartunexpectedly. This occursif the array experiences ahealth check timeout whenthe Management Service isattempting to write to theinternal database.

Array Manage-ment Servicerestarts when at-tempting to writeto the internaldatabase

System Manage-ment

AS-102859

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

Contact HPE Nimble Stor-age Support for assistancein determining the cause ofthe failure.

If a software updateprecheck fails, in somecases it will return only thefailure status without provid-ing additional informationabout the cause of the fail-ure.

Softwareprecheck fail-ures returngeneric errormessage

System Manage-ment

AS-87736





Not applicableThere is a possibility of ac-tive directory lookups failingduring auditing of the login.This will result in failed lo-gins even though authenti-cation succeeds.

Periodic login is-sues due to Ac-tive directorylookups failing

System Manage-ment

AS-92465

Not applicableIn rare occurrences, a cus-tomer-initiated reboot maycause a kernel reboot onthe active controller. Thiswill cause a longer rebootcycle.

Graceful shut-down takeslonger than ex-pected

System Manage-ment

AS-95169

Resolved Critical Issues

Resolved Critical Issues in NimbleOS version 5.2.1.0


No workaround available.In NimbleOS, if the garbagecollection process encoun-ters a media error, the DataService may stop unexpect-edly and restart repeatedly.

Data servicerestarts unex-pectedly whenencountering amedia error


Please contact HPE NimbleStorage Support.

Missing IPMI sensors onController B of AFXX andHFXX arrays may lead toincorrect power supply, fanand temperature readings.This may result in falsepower supply, fan, andtemperature alerts followinga controller reboot orfailover.

False powersupply, fan, andtemperaturereadings onController B ofAFXX and HFXXarrays

PlatformAS-89324

Not applicableThe Data Service may notstart or restart if three disksare in a failed state.

Data Servicemay not startdue to multipledisk failures

PlatformAS-103943

Contact NimbleStorage Support.

In rare cases, a volumecollection and volume own-ership mismatch can be in-troduced. As a result, whenthe Group Managementservice detects the mis-match, it may restart multi-ple times.

Group Manage-ment servicemay restart dueto an ownershipmismatch

System Manage-ment

AS-103460


NimbleOS 5.2.1.0 Resolved Critical Issues

Resolved Critical Issues in NimbleOS version 5.2.1.0


Not applicableIn rare instances, after thedeletion of snapshots, theGroup Management Servicemay restart unexpectedly.This is due to lock acquisi-tion issues with the snap-shot deletion handlingwhere there is a race condi-tion between snapshotdeletion and updating thesnapshot attributes.

Group Manage-ment Servicerestarts aftersnapshot dele-tion

System Manage-ment

AS-104322

Resolved Issues

Resolved Issues in NimbleOS version 5.2.1.0


Not applicableUnder certain conditions,the Data service may restartduring array internal indexprocessing within a shorttime span. Transactionsduring the processing maytake too long to completewithin the defined timespan, which causes theservice to restart.

Data Servicemay restart unex-pectedly due tohealth check fail-ure.


Contact HPE Nimble Stor-age Support if the servicerestarts multiple times.

During a volume move, theData Service may restart onthe destination array if in-coming writes reach theirinternal system limit.

Data Servicemay restart dur-ing volumemove operations


Pause the replication tem-porarily, contact HPE Nim-ble Storage Support to ap-ply a workaround, and thenresume replication. Pleasedo not pause replicationpartner if there are any ac-tive snapshots in replicationprogress.

Due to a data structureoverflow in the NimbleOSreplication module, the DataService may restart unex-pectedly when there is ahigh throughput replicationin progress.

Data Servicerestarts unex-pectedly due toreplication mod-ule



NimbleOS 5.2.1.0 Resolved Issues



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

Host IntegrationAS-99177

Mount the datastore on allthe hosts of the dHCI clus-ter.

During ESXi server soft-ware update, the ESXiserver needs to be put inmaintenance mode. Thisrequires vmotioning the VMto another host in the clus-ter. If this VM is not mount-ed on other hosts in thecluster, the server cannotbe placed in maintenancemode for the update.

Update cannotproceed if alldatastores arenot mounted onall hosts.

ProstackAS-101642

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

Not applicableAudit log entries exceedingthe limit of 24000, wouldinitiate a cleanup of olderentries 5000 at a time. Thiscould cause the groupmanagement service torestart unexpectedly duringprocessing of the cleanup.

Group Manage-ment Servicemay restart dur-ing audit logclean up

System Manage-ment

AS-77312

Reduce the total email ad-dresses to be fewer than255 characters in bothgroups. Then, retry thegroup merge operation.

The maximum length of theemail addresses is 255characters. The GroupManagement servicerestarts when a user tries toinput email addresses thatmay cross the limit of 255characters during groupmerge operation.

Group Manage-ment servicerestarts whenemail lengthcrosses the limit

System Manage-ment

AS-104440

Disable AutomaticSwitchover using the stepsbelow: &nb-sp; 1. Login to thearray GUI &nb-sp; 2. SelectAdministration > Availabil-ity &nb-sp;3. Uncheck the Enablecheckbox for AutomaticSwitchover &nb-sp; 4. ClickSave Use Manual Failoverfor Synchronous ReplicationVolumes in place of ASO.

In rare circumstances, espe-cially in deployments with-out network redundancy, ifthe group leader array losesconnectivity to both thebackup group leader andthe witness, this will resultin Automatic Switchover(ASO). There is a small riskthat not all writes will havebeen mirrored to the partnerarray making ASO an un-safe operation.

Unsafe Automat-ic Switchover(ASO) in theevent of connec-tivity loss.

System Manage-ment

AS-106249





Not applicableWhen network connectivityat a site is flapping, it cancause back to to back auto-shutoffs of the ASD. Theseback to back auto-shutoffsof the ASD can sometimescause a rare ASD crashunder certain conditions.But ASD will come rightback up after the crash andthe system recovers auto-matically

ASD can crashwhen networkconnectivity atthe site is flap-ping

System Manage-ment

AS-95648

NIC migration is automatical-ly triggered whenever thereis a network change - addi-tion or removal of NICs, NICports, missing NICs etc.Historically, NIC informationis saved in the arrays inter-nal database. Under certainconditions, the NIC migra-tion may fail due to a con-flict within the database.This may lead to the GroupManagement Service be-coming unavailable.

Quad port to Du-al port nic migra-tion fails andleads to GroupManagementbeing unavail-able

System Manage-ment

AS-103877

Not applicableThe Group ManagementService may become un-available during a systemdatabase load. In certaininstances, an unexpectedtakeover may occur whensystem is under load due tounavailability of the systemservice.

Group Manage-ment Servicerestart duringsystemdatabase load

System Manage-ment

AS-93904





When attempting to deletea volume collection that isreplicated to the down-stream, make sure thedownstream replicationpartner is not paused.

On a downstream replica-tion partner, the internal ar-ray attributes pertaining tovolumes within a replicatedvolume collection may notbe correctly initialized follow-ing a NimbleOS softwareupdate. If this volume collec-tion is deleted from the up-stream array while thedownstream replicationpartner is paused, the incor-rect attributes may causeGroup Management Serviceto restart on the down-stream replication partner.

Group Manage-ment Servicerestarts whenvolume collec-tion is deleted

System Manage-ment

AS-98363

When deleting a volumecollection that is beingreplicated, make sure thedownstream replicationpartner is not paused.

When a volume collectionis demoted, the internal ar-ray database entries for theassociated volumes maynot update correctly. If thatvolume collection is deletedfrom the upstream while thedownstream replicationpartner is paused, these in-correct values may causethe Group ManagementService to restart unexpect-edly on the downstream ar-ray.

Group Manage-ment Servicerestarts whendeleting volumecollection on thedownstream ar-ray

System Manage-ment

AS-103887

Not applicableIn rare instances the ArrayManagement Service mayrestart unexpectedly after itreceiving a large amount ofinvalid REST API requests.In this case, the REST APIrequest is sent without anobject set, so the segmentin the REST request has anempty object set. When ar-ray attempts to access thesame segment for the ob-ject set information, thatcauses a segmentation faultand leads to an Array Man-agement Service restart.This service restart is non-disruptive.

Array Manage-ment Servicerestarts due toinvalid RESTAPI Requests

System Manage-ment

AS-101941





The Group ManagementService will stabilize follow-ing the restart.

Due to a race condition, theGroup Management Servicemay restart unexpectedlywhen the array is running asnapshot status update op-eration while the snapshotis being deleted.

Group Manage-ment Servicesrestarts followingsnapshot dele-tion

System Manage-ment

AS-103947

The Group ManagementService should self-stabilizefollowing the restart.

In extremely rare instances,due to a race condition withvolume deletion, the GroupManagement service canrestart unexpectedly whenlisting snapshots.

Group Manage-ment servicemay restart dueto a race condi-tion

System Manage-ment

AS-102784

Not applicableWhen updating Users andGroups the ENABLE, DIS-ABLE, and UNLOCK ac-tions now appear under theMore Actions drop-downmenu.

Users andGroups actionshave beenmoved

System Manage-ment

AS-94307

Known Issues

Known Issues in NimbleOS version 5.2.1.0


Not applicableA VVol VM can be protect-ed and may be subsequent-ly replicated to a down-stream array(as configuredin the storage policy). In thecase where this VVol VM isdeleted, a supported “claim”workflow allows us to claimthis VVol VM on the down-stream array. This workflowis not supported at presentif performed on a setupwhere the vCenter versionis 6.5 or above due to vali-dation failures on the vCen-ter. DCPN Ticket:https://dcpn.force.com/Tech-nicalRequestCaseRedesign-Part-ner?Id=5000H00001JRKhf

Vvol Vms cannotbe claimed afterdeleted from thedownstream ar-ray

Host IntergrationPRT-439


NimbleOS 5.2.1.0 Known Issues



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


Data service will be avail-able after restart.

During NimbleOS metadatasync, in rare instances, thedata service may restartunexpectedly. The metada-ta sync operation itself wontbe affected and the restartwill reset the race condition;the data service will stabi-lize after the restart.

Data ServiceRestart due to arace conditionduring metadatasync


The array will continue toshutdown after the Dataservice restart.

Volume manager does notreset internal callbacks dur-ing the shutdown phasecausing the Data service torestart.

Data servicemay restart dur-ing array shut-down


None. The Data ServiceRestart would resume nor-mal I/O operations.

A rare scenario can resultinto a race condition be-tween clone creation andI/O operations on an en-crypted volume; during thistime while fetching the en-cryption keys Data Servicemay restart and resumenormal I/O operations.

Data Servicerestart due to arace condition


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






Remove downstream repli-ca using the correct stepsordered below. 1.Claim the replica volume. 2.Delete all of the snapshotsfor the replica volume. 3.Delete the replica volume.

The service may restartwhen removing the down-stream replica using thesteps below. 1.Deletion of all snapshots forthe replica volume. 2. Claimthe replica volume 3. Deletethe replica volume

Very rare racebetween Volclaim (with allsnapshotsmarked for dele-tion) and spacerecalculation onreplica down-stream volume


Not applicableThe Data Service mayrestart due to a transientresource allocation failure.This happens when theservice cannot complete adisk IO due to transientmemory allocation failure.This does not cause a ser-vice outage as Data servicecontinues normally after arestart.

Data Servicerestart due to re-source allocationfailure.

PlatformAS-103802

Please contact HPE NimbleStorage Support

In rare incidents, controllersdo not power on followingpower cycle.

Controller doesnot power on fol-lowing a powercycle.

PlatformAS-100088

After the controller reboots,BMC firmware is restartedand is functional again auto-matically.

In rare cases, out of ordercommands being sent tothe Baseboard Manage-ment Controller (BMC) mayreturn out of order respons-es that are not handled inthe correct order by Intelli-gent Platform ManagementInterface (IPMI) software. Inthis instance, the IPMImessage queue loses trackof message order. The IPMImessage queue not beingable to return IPMI Watch-dog messages to thewatchdog thread causes thewatchdog thread to timeoutleading to an automatic re-boot. While this BMCWatchdog timeout issue isspecific to the AFx/HFxsystems, this is not a hard-ware issue. Therefore,hardware replacement isunnecessary.

IPMI softwaremay not handlecommand ex-change correctlywith BMC lead-ing to unexpect-ed reboots ofAFx/HFx con-trollers

PlatformAS-90455





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

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

Not applicableIn rare cases, an SSD mayreach its endurance limit butcontinues to pass NimbleDrive Error Recovery algo-rithm. This causes a never-ending process of off-liningand on-lining the drive. Thismay occur for Intel andToshiba SSDs.

SSD hasreached its en-durance limit(wear leveling)but the disk isnot markedfailed.

PlatformAS-91522

Contact HPE Nimble Stor-age Support.

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

Contact HPE Nimble Stor-age Support

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-99334





The only way to resume theupdate would be to failoverto the original group leaderarray and then resuming theupdate through the dHCIvCenter plugin.

When the dHCI unified up-date feature is used to up-date the dHCI stack, theupdate will fail if a GroupLeader Failover occurs dur-ing the process.

An in-progessdHCI updatefails if the groupleader fails over

ProstackAS-103247

Not applicableWhen an ESXi server isadded to dHCI cluster, theupdate page does not getupdated to include thenewly added ESXi server.This refresh happens every4 hours. After the next re-fresh, the new ESXi serversversion will be included andaccounted for on the updatepage.

The updatepage on thedHCI plugintakes 4 hours torefresh

ProstackAS-103769

A valid ESXi license mustbe assigned to the server.

When adding a server withan expired ESXi license tothe dHCI cluster, throughthe vCenter plugin, you maysee an error saying - Failedto submit a task to addserver.

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

ProstackAS-95054

Not applicableWhen the active controlleris being shutdown, the DataService runs into an internalerror condition that causesthe service to restart unex-pectedly. Since the processis already being shutdown,there is no impact to userdata availability.

The Data Ser-vice restarts un-expectedly dur-ing shutdown

SANAS-98042

Not applicableUnder certain conditions,the Data Service on theGroup Leader array mayrestart unexpectedly whileremoving member array.This is due to a race condi-tion when processing SCSIRTPG (REPORT TARGETPORT GROUPS) com-mands. The service shouldstabilize on its own shortlyfollowing the restart.

Data Servicemay restart unex-pectedly whileremoving mem-ber array

SANAS-101325





Not applicableDue to the multi-threadednature of the Alerts andAlarms Service, it is possi-ble for an event with a laterid to be posted prior to anevent with an earlier id.Therefore it will have anearlier timestamp eventhough its ID is higher. Thiscan cause the IDs to appearout of order. However, thealarms in the list are or-dered correctly by times-tamp.

Alarm IDs inalarm list mayappear out of or-der.

System Manage-ment

AS-105431

Run the following commandvia the array CLI: alarm --delete alarm_id

Alarms raised by a memberarray are visible when issu-ing alarm --list even afterthe member array is re-moved from the group.

Member arrayalarms are stillvisible after ar-ray is removedfrom group

System Manage-ment

AS-106124

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

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 applicableEvery night, when inactivekeys for deleted encryptedvolume are deleted by thearray, it creates an audit logentry with root as the userperforming the action.

Purge inactiveencrypted keysappears in auditlog.

System Manage-ment

AS-107980

When the array is unreach-able at the time of AMT Opscommand marked as NULLand aborted, perform theextract/remove the givenAMT Op from the cookietable. So that It should notcause the check conditionfailure.

To perform the autosupportconfiguration validation, Ni-mOs creates one ATM opi.e., SmAsyncWsSendOp.This ATM op will be addedin the cookie table(i.e.,SmAsyncOpCookieTbl ) sothat the asup validate re-sponse request extract/re-move the given ATM opfrom the cookie table andperform the asup response.The real problem is whenthe array intermediately re-ports unreachable, as percode the given AMT opscommand(i.e., specific toAMT operation) marked asNULL and aborted. But thecookie table has this ATMop which is not clean up.So, when the asupVali-dateResp tries to processATM op, since there is novalid AMT ops commandinformation, causing acheck condition which leadsto GMD crash.

Avoid GMDcrash while per-forming the vali-date autosup-port.

System Manage-ment

AS-104185

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






The Automatic SwitchoverService may restart unex-pectedly when the witnessis removed or AutomaticSwitchover is disabled onan array group. In rare in-stances, this may lead to anissue with a database entrywithin the array is notcleared successfully. If thisarray resetup is attemptedon this array, the operationwill fail when the ArrayManagement Service en-counters this stale entry.

Array resetupfails due to previ-ous complica-tions with ArraySwitchover Ser-vice

System Manage-ment

AS-107367

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

Not applicableIf there is a network connec-tivity issue between the wit-ness and Group Leader ar-ray, the group status CLIoutput will update theFailover Mode from Auto-matic to Manual until theconnection is reestablished.It also displays the WitnessStatus as N/A as opposedto Unreachable.

group --statusCLI outputshows incorrectFailover Modeduring networkconnectivity is-sues

System Manage-ment

AS-99704

Not applicableThe array group CLI com-mand with limits option(group --list-limits) displaysnumeric internal identifiersas part of the informationlisted for the volume infor-mation. These numericidentifiers are used by thearray only and can be ig-nored.

Group limitscommand listsinternal identi-fiers

System Manage-ment

AS-101342





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

The workaround would beto delete the alarm usingthe alarm --delete CLI.

When alarm for number ofnics in array net configreaching 120 is triggered, itdoesnt get cleared evenwhen the number of nicsgoes down.

Max limit of 120nics in netconfigalarm does notget cleared

System Manage-ment

AS-87749

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

The service will stabilize onits own following therestarting.

The Array Managementservice may restart unex-pectedly when the array isunder high workload.

Array Manage-ment Servicerestarts unex-pectedly underhigh load

System Manage-ment

AS-101420

Not applicableIn the case where thedownstream array is reach-ing its snapshot rate limitand the user performs thevolume collection handover,the handover will be abortif the limit is surpassed. Analert will be raised but thealert message may bemissing the reason foraborting handover.

Alert for abortedhandover doesnot specify rea-son

System Manage-ment

AS-98650





vol --list can be used to de-termine pool/folder at-tributes of these volumes.

For the volcoll --info outputfor sync replication volumecollections, the Associatedvolumes: and Associatedpinned volumes: fields lackpool/folder qualification forthe associated volumes.

volcoll --info out-put lackspool/folder quali-fications for asso-ciated volumes

System Manage-ment

AS-90286

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 applicableNimbleOS uses a definedstate machine for the repli-cation workflow. At the endof the execution of eachstep defined in the statemachine, it moves to thenext step. If it leads to anyunexpected step throughoutthe workflow then it will leadto assertion failure whichresults in Group Manage-ment service restart.

Group manage-ment servicemay restart dueto assertion fail-ure

System Manage-ment

AS-96143

Not applicableIf a user performs multiplevolume collection han-dovers between two arraysduring a short time span,this may cause a situationwhere both upstream anddownstream array mayclaim volume collectionownership. This is due to arace condition in the work-flow.

Both upstreamand downstreammay claim thevolume collec-tion ownershipwhen excessivehandovers areperformed

System Manage-ment

AS-99520





Update the downstreampools Deduplication settingto match the upstream pool.

If the Default Deduplicationsetting differs for upstreamand downstream pools, theconfiguration of deduplica-tion volumes for replicationmight fail with the followingerror Deduplication not al-lowed since no applicationcategory is assigned to theperformance policy

Configuration ofdeduplicationvolumes for syncreplication mightfail

System Manage-ment

AS-90649

Retry the command for thefailed volumes.

Due to a rare race condi-tion, the Group Manage-ment Service may restartunexpectedly during a bulkvolume update operation.

Group Manage-ment Servicerestarts duringbulk volume up-date

System Manage-ment

AS-95610

Please review the networkand see if there is a consis-tent packet loss and fix anynetwork glitches. If youneed any assistance,please reach out to HPENimble Storage Support.

If the network response toa REST request takes morethan 5 minutes, a threadperforming the REST re-quest times out and as aresult Group ManagementService restarts. The ser-vice stabilizes itself and aslong as the network is serv-ing the requests faster. Asingle instance of the GroupManagement service restartshould not cause any disrup-tions.

Group Manage-ment Servicerestarts due topacket loss innetwork

System Manage-ment

AS-91638

The TTL can be updated onthe snapshots which havea negative value to a cur-rent value. The snapshotmay also be removed if ithas been confirmed it is nolonger needed.

NimbleOS protects the lastreplicated collection, insome cases, the TTL expirydate on those snapshotscan become negative whenthe snapshots exist beyondTTL.

Time to Live(TTL) expirydate on lastreplicated snap-shots can benegative

System Manage-ment

AS-105944

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 restarts unexpected-ly following automaticGroup Leader Failover(AFO). The restart is non-disruptive.

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

System Manage-ment

AS-99615






When the array is poweredon and off excessively, ser-vices may fail to start on thearray.

Services maynot start on thearray after it ispowered on andoff several times

System Manage-ment

AS-101392

Not applicableThe Group 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.

Group 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

This is an intermittent issue,so if the software updatefails in this manner it shouldpass if the software updateis resumed.

The timing is close enoughthat it is possible for the in-dividual array precheckduring software update totake long enough that thehealth check timeout is trig-gered, causing the groupmanagement process torestart and the software up-date to fail.

Health checktimeout maycause softwareupdate failure

System Manage-ment

AS-66997





The ASO checkbox is en-abled by default, howeverASO is not enabled until awitness has been config-ured. In the GUI, navigateto Administration >Availability. If witness isconfigured and the ASOcheck box is checked, dis-able ASO by uncheckingthe box and clicking save.Perform the array softwareupdate again. If the updatecontinues to fail with gener-ic messaging, contact HPENimble Support.

Software updates to5.1.4.200 are not allowedwhen Automatic Switchover(ASO) is configured. If asoftware update to5.1.4.200 fails for this rea-son, a generic software up-date failure message is re-turned in the GUI. Thecause of the failure wouldneed to be determined bylooking at the system config-uration and determining ifASO is configured.

Arrays with Auto-maticSwitchover en-abled fail soft-ware updatewith genericmessage

System Manage-ment

AS-106848

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

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





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

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

Not applicableA member array might notbe listed under the Add Ar-ray to Group option withinthe GUI if the member isconfigured with a differentprotocol (iSCSI vs FibreChannel). Also when thereare multiple arrays in thesubnet, arrays which cantbe discovered within thestipulated time may not belisted in Add Array toGroup.

Member arraymight not be dis-played underAdd Array toGroup option

System Manage-ment

AS-100067

Not applicableIn rare circumstances, fol-lowing an AutomaticFailover (AFO) a race condi-tion may cause the ArrayManagement Service torestart or an unexpectedcontroller takeover.

Array Manage-ment Servicerestarts orTakeover occursunexpectedlyfollowing auto-matic GroupLeader Failover

System Manage-ment

AS-99431

Not applicableWithin the HPE NimbleStorage array GUI, customSSL certificate import is on-ly supported on GoogleChrome version 71 or later.

Custom SSLcertificate importnot supported onolder versions ofGoogle Chrome

System Manage-ment

AS-99343





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

Not applicableDuring group merge, theGUI might show Successfulmessage even though thegroup merge backend pro-cessing fails.

GUI may showSuccessful mes-sage whengroup mergefails

System Manage-ment

AS-87886





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

Edit the pool name and as-sign / un-assign the array ain separate steps.

When attempting to edit astorage pool and assign anarray at the same time, youreceive the following error:Cannot update array listand name or description si-multaneously.

Unable to edit astorage pool andassign an arrayat the same time

System Manage-ment

AS-94575

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

Fix the name conflict on thedownstream array.

When associating multiplevolumes to a volume collec-tion from, the volume asso-ciation for all volumes canfail due to a name conflictfor one of the volumes onthe downstream.

Volume collec-tion associationfor a volume canfail due to aname conflict onthe downstreamarray

System Manage-ment

AS-104099





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.2.1.0 Release Notes...NimbleOS 5.2.1.0 Special Notes Note Description As of vSphere 7.0,...

Documents

Transcript of NimbleOS 5.2.1.0 Release Notes...NimbleOS 5.2.1.0 Special Notes Note Description As of vSphere 7.0,...