NimbleOS 5.2.1.600 Release Notes · Volume moves transfer data Not applicable from one Nimble array...

NimbleOS 5.2.1.600 Release Notes

Published March, 2021 Version 5.2.1.600

Legal Notices

Copyright © 2021 by Hewlett Packard Enterprise Development LP

Notices

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

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistentwith FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Com-mercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no controlover 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 the United States and othercountries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/orother countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

All third-party marks are property of their respective owners.

Publication Date

Monday March 1, 2021 14:26:06

Document ID

esg1613755383433

Support

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

Email: [email protected]

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

2

https://infosight.hpe.com

mailto:[email protected]

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

Contents

NimbleOS 5.2.1.600.................................................................................................................4Important Update Note............................................................................................................................................................................................................4

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

New Features in 5.2.1.600.....................................................................................................................................................................................................7

Recent Release Features.........................................................................................................................................................................................................8

Documentation.............................................................................................................................................................................................................................8

Verified Update Paths...........................................................................................................................................................................................................10

Known Critical Issues..............................................................................................................................................................................................................13

Resolved Critical Issues.........................................................................................................................................................................................................24

Resolved Issues.........................................................................................................................................................................................................................25

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

3

NimbleOS 5.2.1.600

5.2.1.600Version:

Monday March 1, 2021 14:26:06Revision:

The release notes describe the major changes, fixes, and known issues for this release of the NimbleOS. They do not includeall 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 cause an email alertand automated case indicating "Standby Controller Not Available" when the firmware update process takes longer than fiveminutes. This is expected behavior and does not affect data services. At the end of the software update, you can check statusof both controllers in the Web UI under Manage > Hardware. One controller will be ACTIVE and the other STANDBY undernormal operating conditions following a successful software update.

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

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

The Documentation page also includes the General Terms and Conditions document. You can display this document byperforming the following steps:

1 In the navigation pane on the HPE InfoSight Documentation page, scroll through the Document Type list and selectSupport Policy.

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

Special Notes

DescriptionNote

HPE Nimble Storage continues to qualify configurations between releases. TheValidated Configuration Matrix provides information about validated configurationsand is updated frequently. It is a good practice to check your system configurationagainst this online tool. The Validated Configuration Matrix tool is available onHPE InfoSight:

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

CRITICAL

Arrays must be running NimbleOS 5.0.4.0 or later to update directly to NimbleOS5.2.1.600.

CRITICAL

An extended data services outage may occur with MS iSCSI initiator and Intel NICsusing the built-in Windows driver e1q60x64.sys (version 11.0.5.21/11.0.5.22).

If you encounter this problem, please update your system to use the latest Windowsdriver.

CRITICAL

Important Update Note 4

mailto:[email protected]

https://infosight.hpe.com



DescriptionNote

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

CRITICAL

Due to a known Red Hat Enterprise Linux bug 1002727, while running virtualizedin VMware ESX, manually rebooting the active controller in presence of heavy IOsusing the reboot --controller command on a Fibre Channel array may trigger anincorrect retry initiated by RHEL guests 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 theseenvironments, we recommend the failover command instead.

CRITICAL

Due to a known Red Hat Enterprise Linux bug 3550561, unexpected applicationbehavior may occur on RHEL 7.5 hosts with kernel-3.10.0-862.3.2.el7 or derivativesusing 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 Nimble Storagefully supports Windows guest operating systems on Microsoft Hyper-V, includingVirtual Fibre Channel (VFC) connectivity and multipathing with HPE Nimble StorageDSM and VSS support. However, Linux guest operating systems running in Hyper-V VFC configurations are not qualified.

Running Red Hat Linux guest operating systems with the “Linux Integration Ser-vices” kit installed, or with hv_storvsc drivers in such configurations can lead toRed Hat bug 1364282, which can cause an unexpected service outage.

CRITICAL

Starting with NimbleOS 5.1.1.0, the size of the software package now exceeds 2GB, which may lead to lengthier software download times. Previously, the sizes ofthe NimbleOS 5.0.x download packages were approximately 1.6 GB, and NimbleOS4.x packages were approximately 900 MB.

Important

After completing the NimbleOS update for array groups configured for SynchronousReplication, download the corresponding version of the Synchronous ReplicationWitness software, and update the witness host.

Important

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

Important

As of vSphere 7.0, VMware has discontinued the flex client. Consequently, the HPENimble Storage vCenter Plugin no longer supports the flex plugin for vCenter 7.0.

Important

Special Notes 5

https://infosight.hpe.com/org/urn%3Ainfosight%3A00000000-0000-0000-0000-000000000001/resources/nimble/software/NimbleOS/Synchronous%20Replication%20Witness

https://infosight.hpe.com/org/urn%3Ainfosight%3A00000000-0000-0000-0000-000000000001/resources/nimble/software/NimbleOS/Synchronous%20Replication%20Witness

DescriptionNote

You can enable deduplication for CS1000, CS3000, CS5000, CS7000, CS700, andCS500 arrays on a volume only if the corresponding storage pool has a Flash toDisk Ratio (FDR) greater than 4%. To calculate the FDR, obtain the "Total arraycapacity (MiB)" and "Total array cache capacity (MiB)" values by using the HPENimble Storage CLI command 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 --info commandwill also show a value for dedupe capacity (MiB).

Note On the HF20H, HF20, HF40, and HF60 platforms, pool --info displays "N/A"as the value for dedupe capacity (MiB). This because you can enable deduplicationfor the entire array.

Important

For connections to the NimbleOS GUI, you must have port 5392 open for the GroupManagement IP address and both diagnostic IP addresses.

Important

Numerous host integration toolkits are supported in NimbleOS 5.2.1.600. It isstrongly recommended that they be installed on all Windows, Linux, and VMwarehosts. For more information about supported toolkits, refer to the Validated Con-figuration Matrix, which is available on HPE Nimble Storage InfoSight:


Important

HPE Nimble Storage recommends that you update to HPE Nimble Storage WindowsToolkit (NWT) 7.0.1 or later if you are using Microsoft VSS Synchronization andNimbleOS 5.1.4.200 or later.

Using application consistent snapshots with earlier versions of NWT and NimbleOS5.1.4.100 may result in the following error messages:

• In the host's VSS requestor log (C:\ProgramData\Nimble Storage\Logs\VssRe-questor.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

Special Notes 6


DescriptionNote

HPE Nimble Storage Connection Manager (NCM) for VMware 7.0 is signed byVMware for ESXi 7.x. It can be installed through the VMware Update Manager oresxcli command without the --no-sig-check flag.

See the NCM for VMware Release Notes 7.0 or later and the latest VMware Integra-tion Guide for further details.

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

Important

Various timeout values affect HPE Nimble Storage targets from Windows/Linuxhosts. Before you update the NimbleOS, install the HPE Nimble Storage WindowsToolkit (NWT) or HPE Nimble Storage Linux Toolkit (NLT) on the host or tune thetimeout values. Timeout details for various operating systems can be found onHPE InfoSight under Resources > Documentation. From the HPE Nimble StorageDocumentation page, locate the article you want.

The following Knowledge Base articles and Integration Guides explain how toconfigure and verify host timeout settings for the major supported operating sys-tems (OS):

• For Windows, refer to https://infosight.hpe.com/InfoSight/media/cms/ac-tive/sup_KB-000052_Windows_Host_Disk_Timeout_Values.whz.

In the context of Microsoft Windows, the following article should also be con-sidered:

https://infosight.hpe.com/InfoSight/media/cms/active/sup_KB-000246_MPIO_Timeout_Parameters_For_MSDSM_And_NimbleDSM_In_Win-dows_2012_R2doc_version_family.whz

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

• For Linux, refer to https://infosight.hpe.com/InfoSight/media/cms/ac-tive/sup_KB-000304_Linux_Host_Disk_Timeout_Values.whz.

Important

vVol VMs cannot be claimed after deleted from the downstream array.

A vVol VM can be protected and may be subsequently replicated to a downstreamarray (as configured in the storage policy). In the case where this vVol VM isdeleted, a supported “claim” workflow allows us to claim this vVol VM on thedownstream array. This workflow is not supported at present if performed on asetup where the vCenter version is 6.5 or above due to validation failures on thevCenter.

VMware DCPN Ticket Reference:

https://dcpn.force.com/TechnicalRequestCaseRedesignPart-ner?Id=5000H00001JRKhf

Important

New Features in 5.2.1.600No new features were introduced in NimbleOS 5.2.1.600.

New Features in 5.2.1.600 7



https://infosight.hpe.com/InfoSight/media/cms/active/sup_KB-000052_Windows_Host_Disk_Timeout_Values.whz

https://infosight.hpe.com/InfoSight/media/cms/active/sup_KB-000052_Windows_Host_Disk_Timeout_Values.whz

https://infosight.hpe.com/InfoSight/media/cms/active/sup_KB-000246_MPIO_Timeout_Parameters_For_MSDSM_And_NimbleDSM_In_Windows_2012_R2doc_version_family.whz



https://infosight.hpe.com/InfoSight/media/cms/active/sup_KB-000304_Linux_Host_Disk_Timeout_Values.whz

https://infosight.hpe.com/InfoSight/media/cms/active/sup_KB-000304_Linux_Host_Disk_Timeout_Values.whz

Recent Release FeaturesThe following features were released in NimbleOS 5.2.1.x:

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) andthe 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 using information from theinitiator groups that have been configured. This removes the requirement for the administrator to program the FC zonesusing 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 the currently shippingarrays. This version of the upgrade process requires a brief down time while the existing array chassis is replace with the newone, 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,000volumes in previous NimbleOS releases.

Storage Class Memory

NimbleOS now supports new 1.5 TB storage class memory cards. Support is limited to HPE Nimble Storage AF60 and AF80model arrays.

Synchronous Replication: Witness OVA

The Peer Persistence feature requires an external witness. The Witness is available for download from InfoSight as a virtualmachine packaged as an OVA.

dHCI Unified Update

HPE Nimble Storage dHCI now provides an Update tab in the HPE Nimble Storage vCenter Plugin that allows you to performan automatic update when there is a new version of NimbleOS, ESXi, or HPE Nimble Storage 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-based ProLiantservers. The Validated Configuration Matrix provides information about which server models are supported.

Note You can use either Intel-based ProLiant servers or AMD-based ProLiant servers in your dHCI configuration. You cannotuse both in the same cluster.

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.

Recent Release Features 8



The Nimble Storage 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 integration guides, productdocumentation, and configuration matrices.

To go directly to a document, use the navigation pane on the left side of the Nimble Storage 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-party 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 section and selectSupport Policy.

4 From the list of documents, select General Terms and Conditions. The document opens in a new browser 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 Deployment Guides and GettingStarted Guide.

Workflow Documents

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

Hardware

Documentation for all hardware components is available on HPE InfoSight. Click the Hardware Guide link in the DocumentType category. Hardware documentation includes array and expansion shelf installation quick start 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 InfoSight Documentationpage, scroll down the navigation pane to the section called Integration Guide.

Documentation 9

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

Verified Update Paths

Table 1: From Versions 5.x

From Versions 5.x

To VersionFrom Version

5.2.1.6005.2.1.500

5.2.1.6005.2.1.400

5.2.1.6005.2.1.300

5.2.1.6005.2.1.200

5.2.1.6005.2.1.100

5.2.1.6005.2.1.0

5.2.1.6005.1.4.200

5.2.1.6005.1.4.100

5.2.1.6005.1.4.0

5.2.1.6005.1.3.100

5.2.1.6005.1.3.0

5.2.1.6005.1.2.100

5.2.1.6005.1.2.0

5.2.1.6005.1.1.0

5.2.1.6005.0.10.0

5.2.1.6005.0.9.100

5.2.1.6005.0.9.0

5.2.1.6005.0.8.100

5.2.1.6005.0.8.0

5.2.1.6005.0.7.300

5.2.1.6005.0.7.200

5.2.1.6005.0.7.100

5.2.1.6005.0.7.0

5.2.1.6005.0.6.0

5.2.1.6005.0.5.200

5.2.1.6005.0.5.0

5.2.1.6005.0.4.0

5.0.10.05.0.3.100

Verified Update Paths 10

From Versions 5.x


5.0.10.05.0.3.0

5.0.10.05.0.2.0

5.0.10.05.0.1.100

5.0.10.05.0.1.0


From Versions 4.x


5.0.10.04.5.6.0

5.0.10.04.5.5.0

5.0.10.04.5.4.0

5.0.10.04.5.3.0

5.0.10.04.5.2.0

5.0.10.04.5.1.0

5.0.10.04.5.0.0

5.0.10.04.4.1.0

5.0.10.04.4.0.0

5.0.10.04.3.1.0

5.0.10.04.3.0.0

5.0.10.04.2.1.0

5.0.10.04.2.0.0

5.0.10.04.1.0.0


From 3.x Versions


5.0.10.03.9.3.0

5.0.10.03.9.2.0

5.0.10.03.9.1.0

5.0.10.03.9.0.0

5.0.10.03.8.1.0

5.0.10.03.8.0.0

5.0.10.03.7.0.0

5.0.10.03.6.2.0


From 3.x Versions


5.0.10.03.6.1.0

5.0.10.03.6.0.0

5.0.10.03.5.4.0

5.0.10.03.5.3.0

5.0.10.03.5.2.0

5.0.10.03.5.0.0

5.0.10.03.4.1.0

5.0.10.03.4.0.0

5.0.10.03.3.0.0

5.0.10.03.2.1.0

5.0.10.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.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

3.9.3.02.2.9.0

3.9.3.02.2.7.*

3.9.3.02.2.6.0


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


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.600

WorkaroundDescriptionTitleComponentID

Contact HPE Nimble StorageSupport.

On Data Service startup followedby a failover, during the recov-ery process, it is possible to hita checksum mismatch. The DataService restarts when the mis-match is encountered. The ser-vice will make three attempts torestart, before disabling the ser-vice.

Data Service dis-abled on array dueto NVRAM Check-sum mismatch

Data ServiceAS-115397

Not applicableDuring disk index processing theautomated task manager reportsstatus to the Data Service. If thetask manager does not respondwithin the expected time of 30seconds, the Data Service willrestart to recover from the con-dition.

Data Service mayrestart unexpected-ly due to healthcheck failure


Known Critical Issues 13



If required, the timeout for thecache checkpoint task can beincreased.

On hybrid arrays, the flash cachecheckpoint task is run periodical-ly to reduce memory/nvramconsumption by the cachebuffers. This task is expected tocompleted within a specifiedamount of time. In certain rarescenarios, this task can beblocked and fail to complete intime. This can result in a restartof the data services daemon. Asingle restart of the data ser-vices daemon should not resultin any interruptions on the clientside.

Data services dae-mon restart


Contact HPE Nimble StorageSupport

In rare instances, the Data Ser-vice may restart unexpectedlywhile performing Volume Man-agement checksum computa-tions.

Data Service mayrestart unexpected-ly


When planning to remove amember array from group,schedule a planned maintenancewindow and place all ESX hostsinto maintenance mode to mini-mize impact to availability. ESXtypically resumes connection tovVol datastores, and reconnectsto VMs, after a period of 15-30minutes automatically without amanual intervention.

Scaled vVol environments with500 vVol VDI VMs or more than5000 Nimble vVol volumes mayexperience IO disruption whenremoving a member array fromgroup. Symptom of problemwould appear as vVol datastoresbeing (inaccessible). Virtual Ma-chine status would also appearas (inaccessible).

Removing memberarray from multi-ar-ray group maycause IO disruptionto scaled vVol envi-ronments


Not applicableVolume moves transfer datafrom one Nimble array to anoth-er. During this move, if the hostsends I/O to the incorrect array,the I/O needs to be forwardedto the correct array owning thedata. This results in higher thanusual I/O latency. To avoid thisissue in VMware environments,the Nimble Connection Managerfor VMware needs to be installedon all hosts accessing the vol-ume.

Volume move mayresult in latency ifNimble ConnectionManager is not in-stalled


Not applicableThe Data service may restartunexpectedly when a checksumverification failure occurs.

Data service mayrestart unexpected-ly






When the Data Service detectsa metadata inconsistency, theservice may restart repeatedlyand hosts could experience un-expected application behavior.

Data Servicerestarts when de-tecting metadatainconsistency



In rare cases during index cre-ation, when a 16 TiB volume isfully unmapped, the resultingindex structure fails verificationand brings down the Data Ser-vice leading to an outage.

Index verificationfails if a 16 TiB vol-ume is completelyunmapped causingData Service to godown


Contact HPE Nimble StorageSupport to identify and replacethe faulty SSD.

If the array encounters a faultySSD with multiple bad segments,the Log-structured File System(LFS) attempts to resolve theerrors. If the array is under highload and LFS has a high humberof block errors to resolve it mayexhaust the IORW buffers caus-ing the Data Service to restartrepeatedly.

Data service mayrestart repeatedlydue to faulty SSD


Not applicableData service may restart due arare race condition between theoperations of shutting down thedata service and resync of thestandby controller. When therace condition is detected theData service restarts to recoverfrom the condition.

Data service mayrestart due to arace condition


Not applicableWhile committing internaltransactions, Data Service mayhit a rare race condition. To re-cover from this Data Servicemight restart



Not applicableDuring snapshot replication ofa dedupe-enabled volume, thedownstream array file systemmay restart due to an out-of-memory condition.

Snapshot replica-tion of deduplica-tion-enabled vol-umes may lead toFile System restart


Not applicableA disruption in network connec-tions can cause Data Service torestart unexpectedly.

Data Service mayunexpectedlyrestart





Not applicableData Services may unexpectedlyrestart due to out of memorycondition while running snapreplication on dedupe enabledvolumes with high compressionratios.



Review network devices toidentify and reduce networkchecksum errors.

In environments with frequentnetwork checksum errors, inter-ruptions of Replication and DataService restarts may occur.

Replication interrup-tions and Data Ser-vice restarts mayoccur due to net-work errors


Not applicable, on restart DataService would behave normally.

Generation delete operationsand NVRAM to disk data flushoperation can cause Data Ser-vice to restart due to healthcheck failure, as it can holdcheckpoint for a long time.

Data Service mayrestart due to vol-ume managerhealth check failure



The Volume Manager monitorsvolume migration progress. Theprocess relies on referencecounts to determine status. Ifthe reference count is notcleared as expected during pro-cessing the migration may stall.

Volume migrationmay stall due toVolume Managerreference counthandling


Not applicableWhen attempting to perform apool merge operation, if thereare a large number of volumesthat must be striped across thepool, and one of the arrays hasa large number of pendingdeletes, then it is possible for theoperation to fail due to the DataService being overloaded.Symptoms of this behavior areif the pool merge operationhangs for several minutes andreturns the following message:The request could not be under-stood by the server.

Pool merge failsdue to too manypending deletes





After updating to 4.x.x.x or5.0.x.x, wait at least 1 hour be-fore updating onto 5.1.x.x+ orcontact HPE Nimble StorageSupport.

After performing a software up-date from 3.x.x.x (or earlier) to4.x.x.x or 5.0.x.x and then updat-ing onto 5.1.x.x+ immediatelyafter the 4.x.x.x or 5.0.x.x updatecompletes, there may not beenough time for an internalmetadata operation to completein the short amount of time thearray is on 4.x.x.x or 5.0.x.x. Asa result, the Data Service can gointo a restart loop leading to anoutage.

Data Service mayrestart repeatedlyafter performingmultiple softwareupdates in shortsuccession


Not applicableThe Data service may restartwhen Bin Migration is going on.This can happen when followingactivities happen together: 1. Binmigration is occurring for a vol-ume. 2. Group Management ser-vice restart (because of any rea-son). 3. Group Management ser-vice unable to re-sync with Dataservice after &nb-sp; restart. This canlead to Data service restart butit will not impact bin migrationas after Data service restart binmigration will resumed automat-ically.

Rare race conditionbetween Data ser-vice and GroupManagement ser-vice cause Dataservice restart


Not applicableData Service may restart whenoperations of volume migrationare stuck waiting for ownershiptransfer completion.

Data Service mayrestart unexpected-ly during volumemigration


Not applicableIf the Data Service is restartedduring a volume move, it wouldresult in incorrect Bin Migrationstate to be recovered, causinganother Data service restart.This is a rare event since it re-quires snapshots to be taken aswell as a Data Service restartduring a volume move.

Data Service restartduring volumemove may causethe service torestart again.



Counters used for space account-ing may cause validation to fail.The array may see a blip inspace usage because of whichwrites may be denied and inworst case, volume may go of-fline.

Writes may be de-nied due to coun-ters in space ac-counting





If after 20 minutes the controllersensors do not report goodstate, please contact HPE Nim-ble Storage Support for assis-tance.

During boot up due to a knownIntel defect the controller sen-sors may report missing for aperiod of time in the array alerts.After about 15-20 minutes, itreturns to a valid state and thesensors should report validreadings again.

Controller sensorsmissing forAFxx/HFxx arrays

PlatformAS-86764


HPE Nimble Storage has identi-fied a rare firmware defect in asubset of drives which can, un-der certain write intensiveworkloads, cause the array tounder-perform.

Performance affect-ing firmware defectin a subset of 6TBdrives.

PlatformAS-94961

Not applicableThe Data Service may restartunexpectedly when array en-counters a disk returning baddata, and the disk has not beenmarked as failed.

Data Service mayrestart unexpected-ly when a disk re-turns bad data

PlatformAS-97925

Not applicableDuring internal file operations,processes may be waiting for alock to be released. If the waittime exceeds 30 seconds, a ser-vice health check may restartthe Data service to recover.

Data service mayrestart during whenfile operation time-out is exceeded

PlatformAS-86099

Contact HPE Nimble StorageSupport to review disks for re-placement.

In rare instances, the Data Ser-vice may restart if the array hasmultiple bad drives which makeIO handling very slow.

Data Service mayrestart if the arrayhas multiple baddrives

PlatformAS-108793

Not applicableThe Data Service on the arraymay restart when timeout forinternal communication betweenarray controllers has been ex-ceeded. The service restarts torestore the communication.

Data Service mayrestart due tohealth check failure

PlatformAS-104517


If the array M.2 boot device isfaulty, the array software updateprecheck and/or Diagnostics forNimble Array uploads may fail.

Array updateprecheck or Diag-nostics for NimbleArray uploads mayfail due to faultyboot device

PlatformAS-94153




Not applicableNimble Drive Error Recovery(NDER) is activated for drivesfailing I/O in an attempt to recov-er the drive. In rare instances,the process may surpass iSCSIhost timeout values, causinghost I/O inaccessibility.

NDER process maylead to host recon-nects

PlatformAS-96053

Not applicableThe current thermal policy hasa limitation where individualPCIe components are not moni-tored on card-by-card basis. Asa result, the high level tempera-ture policy that is current imple-mented, is sometimes incapableof regulating the temperaturesof individual cards.

Limited thermalmonitoring policyfor PCIe compo-nents

PlatformAS-107489

Contact HPE Nimble Support forassistance in restoring array toActive/Standby status.

In rare instances the intercon-nect between controllers may bedown following a controller re-seat.

Array remains insolo/stale aftercontroller reseat.

PlatformAS-51053

Verify that the software updatepackage has been downloadedto the system and then attemptthe software update again usingthe software --resume_updatecommand from the CLI.

During software update fromNimbleOS 3.x versions to laterversion, a failure to extract thesoftware update package mayincorrectly return the errormessage /tmp is out of space.even if there is still space in thedirectory.

Incorrect softwareupdate error mes-sage /tmp is out ofspace.

PlatformAS-93456

In order to add more 4 or moreProliant Servers, the workaroundis to add up to 3 servers at atime from the plugin.

Currently, if customer plans toadd 4 or more Proliants serversin their dHCI deployment via theplugin, the operation fails.

Plugin: Cannot add4 or more serversin the dHCI deploy-ment

dHCIAS-104924

Not applicableThe Data Service on the arraymay restart if a Task Manage-ment Function request to aborta command is received while thecommand is still being complet-ed. The service restarts to recov-er from the condition.


SANAS-112859

Not applicableNormally Fibre Channel sessionlogin/logout happens veryquickly. Under certain condi-tions, it may take long enoughthat SCSI commands will timeoutleading and lead to brief dataunavailable situations.

IO may timeoutduring Fibre Chan-nel session login/lo-gout

SANAS-93191




Review the Fibre Channel fabricfor any issues that may causelost frames.

In rare occasions during periodswhere a large number of FibreChannel commands are abortedand sessions are terminating,the Data Service may occur be-cause of inconsistent or dupli-cate reporting of command ter-mination status. The initial trig-ger of this issue is typically lostframes on the fabric due to con-gestion or hardware failure.

Data Service mayrestart due to FibreChannel commandstate inconsistency

SANAS-91812

Addressing the fabric issuesshould resolve this issue.

Fibre Channel fabric issues (er-rors, congestion, etc.) can pre-vent the array from transferringdata and status to the initiator.This can result in a large amountof aborted commands. In rarecases this may cause problemsfor the Fibre Channel driver andSCSI stack.

Initiator side FibreChannel Fabric in-stability may resultin a large numberof aborted SCSIcommands

SANAS-95159

Not applicableIn rare instances, the controllerkernel may crash if the outstand-ing SCSI command arent proper-ly cleaned up in the Fibre Chan-nel driver during session termi-nation. The kernel crash willcause the controller to reboot torecover from the condition.

Controller may re-boot unexpectedlydue to impropercommand cleanupduring Fibre Chan-nel session termina-tion

SANAS-94636

Not applicableWhen an implicit logout of a Fi-bre Channel session occurs SCSIcommands from the previoussession may not be terminatedproperly causing a restart of thedata service. The service restartsto recover from the condition.

Data Service mayrestart after implicitlogout of FibreChannel Session

SANAS-94746


The Event service may restartunexpectedly when attemptingto load a trusted certificate dueto an issue which impacts certifi-cate management. The servicemay not restart after encounter-ing the issue.

Event service mayrestart unexpected-ly

SecurityAS-117550





The Event service may restartunexpectedly when attemptingto load a trusted certificate dueto an issue which impacts certifi-cate management. The servicemay not restart after encounter-ing the issue.


SecurityAS-115780

Not applicableGroup Management service mayrestart due to a race conditionbetween threads when a volumeaccess control list is removed.The service restarts to recoverfrom the condition.

Group Managementservice may restartdue to race condi-tion

System Manage-ment

AS-110030

Correct the DNS or SMTP config-uration to a valid address byensuring that a ping to the de-fined address succeeds.

Multiple threads are created todeliver emails, however, a non-threadsafe libcurl call is used todispatch them. If there is a mis-configured DNS or SMTP server,the curl call will timeout. If thereare greater than 7 emails waitingto be delivered and all are expe-riencing timeout, the servicehealth check timeout is exceed-ed, causing the Event Manage-ment service to restart.

Flood of timeoutscausing Event Man-agement servicerestart

System Manage-ment

AS-68651

Not applicableAudit log entries exceeding thelimit of 24000, would initiate acleanup of older entries 500 ata time. This could cause thegroup management service torestart unexpectedly duringprocessing of the cleanup.

Group ManagementService may restartduring audit logclean up

System Manage-ment

AS-116981

A Manual Group Leader Failoverwill be required to restore FibreChannel connectivity to thehosts.

An Automatic Failover (AFO) ofthe Group Management Serviceswill not be initiated if all FibreChannel (FC) interfaces on theGroup Leader array fail on bothcontrollers.

No AutomaticFailover in theevent the host los-es all FC connectivi-ty to an array

System Manage-ment

AS-94737




Not applicableThe Automatic Switchover Ser-vice internally creates and closesthreads each time during Auto-matic Failover (AFO) quorumsetup and tear down. This maycause the service to eventuallycrash after reaching the maxi-mum thread limit. The systemrecovers automatically when theAutomatic Switchover Servicerestarts.

AutomaticSwitchover Servicerestarts due tothread limitations

System Manage-ment

AS-89701

A failover can be initiated in or-der to restart the Group Manage-ment Service. You may alsocontact HPE Nimble StorageSupport to restart the servicemanually.

When performing a controllerupgrade to a high-end model,the object limits will still showthe lower limits if the GroupManagement Service is notrestarted.

Group ManagementService must berestarted to unlockadditional volumelimits after con-troller upgrade

System Manage-ment

AS-65615

Not applicableThe Array Management Servicemay be unavailable during orshortly after Automatic GroupLeader Failover events. This maycause the CLI or GUI to be un-available for a brief period oftime until the service startupcompletes.

Array ManagementService may be un-available duringAutomatic Failover

System Manage-ment

AS-116943

Not applicableGroup Management service mayrestart when internal processingfails on arrays with high snap-shot activity. This may causesnapshots to fail to be deleted.

Group Managementservice may restartunexpectedly

System Manage-ment

AS-94594

Not applicableThe Group Management servicemay restart during an arrayshutdown while processingREST request. No user opera-tions are impacted because thearray is already in the middle ofa shutdown. The shutdown pro-ceeds normally.

Group Managementservice may restartduring array shut-down

System Manage-ment

AS-61614





The Snapshot rate limit - Num-ber of snapshots that can betaken for a given minute - is in-troduced in 4.x for distributingsnapshot load to the system. Ifa group surpasses this snapshotrate limit in previous NimbleOSreleases, the software update to4.x is still allowed. However, agroup merge is prevented if thesource or destination array sur-passes the snapshot rate limit.The following error message canbe seen during the group mergevalidation: INFO: Rate of snap-shots in the merged groupwould be greater than support-ed snapshot rate. This could oc-cur if even if the source array(the array being added to theexisting group) has 0 volumesor volume collections.

Group merge fails ifone of the groupsviolates the snap-shot rate limit

System Manage-ment

AS-69136

Use unique name when creatingsnapshot collection.

If an attempt is made to createa snapshot collection with samethe name of an existing snap-shot collection, an error indicat-ing object already exists will bereported and the Group Manage-ment service may restart. Theservice will recover upon restart.

Group Managementservice may restartdue to duplicatesnapshot collectionname

System Manage-ment

AS-94113

Not applicableA system management processcan restart when the system isunder heavy load. The systemrecovers automatically. The Dataservice is not affected.

Group ManagementService restarts un-der heavy load

System Manage-ment

AS-100254

Not applicableThe Array Management servicemay restart due to a race condi-tion encountered during serviceshutdown. The service will recov-er after the restart.

Array Managementservice restart dur-ing service shut-down

System Manage-ment

AS-98124

Contact HPE Nimble StorageSupport for assistance in deter-mining the cause of the failure.

If a software update precheckfails, in some cases it will returnonly the failure status withoutproviding additional informationabout the cause of the failure.

Software precheckfailures returngeneric error mes-sage

System Manage-ment

AS-87736




Not applicableThere is a possibility of sporadic,transient, active directory au-thentication failures. In thesecases, the system will recover onits own, requiring no user inter-action.

Intermittent loginfailures due to Ac-tive directorylookups failures

System Manage-ment

AS-92465

Not applicableGroup Management may be-come unavailable temporarilywhen a large number of restoresare performed on a volume.

Group ManagementServices unavail-able temporarilywhen performingvolume restore

System Manage-ment

AS-98194

Not applicableIn rare occurrences, a customer-initiated reboot may cause akernel reboot on the active con-troller. This will cause a longerreboot cycle.

Graceful shutdowntakes longer thanexpected

System Manage-ment

AS-95169

Not applicableController may reboot unexpect-edly if there is high memory uti-lization for the java and/or jettyprocesses on the array.

Controller may un-expectedly restartdue to high memo-ry utilization

System Manage-ment

AS-84499

Use volume collections to checksyncRep volumes, or use otherfilters to meet the needs

There is currently no way to fil-ter volumes using SynchronousReplication within the array GUI.

Unable to Filter vol-umes using Syn-chronous Replica-tion

System Manage-ment

AS-92379

Refresh the page to restorebutton functionality.

After performing a bulk updateoperation from the Manage >Data Storage > Volumes >volumename > Data Protec-tion tab in the GUI, the pagefooter may not update and pre-vious button may be unavailable.

Page footer in GUImay fail to updateafter bulk updateoperation

System Manage-ment

AS-97968

Resolved Critical Issues

Resolved Critical Issues in NimbleOS version 5.2.1.600



In rare cases, during fingerprintindex lookup and merge opera-tions involving large deduplica-tion domains, index block refer-ences can be mishandled. As aresult, the Data Service can gointo a restart loop, which canlead to extended data unavail-ability.

Multiple Data Ser-vice restarts duringdeduplication fin-gerprint operations


Resolved Critical Issues 24

Resolved IssuesThere are no resolved issues in NimbleOS version 5.2.1.600

Known Issues

Known Issues in NimbleOS version 5.2.1.600


Not applicableA lost wake-up to an operationmay cause the operation block-ing the checkpoint which resultsin Data Service restart.



Contact HPE Nimble StorageSupport to increase the healthcheck timeout on the array

After updating the array toNimbleOS 4.x.x.x or later, a pro-cess runs to convert an on-diskdata-structure specific to Nim-bleOS by initiating an operationthat walks the existing tree ofthis data-structure. In some cas-es, this operation keeps runningeven after the conversion hascompleted successfully, leadingto health check timeout. Thisresults in a Data Service restart.

Data Service restartwhile converting in-ternal data-struc-tures in NimbleOS


Not applicableThe Data Service may restartunexpectedly during a read op-eration when decryption anddecompression fails.



Not applicableA volume that has a chain of atleast three branches, commonin replication or snapshot re-store workflows, may triggerunexpected Data Servicerestarts upon branches beingtrimmed and deleted.

Data Service mayrestart duringbranch point dele-tion


Not applicableIn rare instances, the Data Ser-vice may restart when internaldatabase communication be-tween services is not available.The service restarts to restorethe communication betweenservices.

Data Service mayrestart unexpected-ly due to internaldatabase communi-cation


Resolved Issues 25



If RAID is degraded for an ex-tended period and Data Servicerestarts occur, contact HPENimble Storage to assess adjust-ing allocated buffer resources.

When RAID is degraded, IOneeds to be reconstructed byreading from multiple disks, andan internal buffer may exhaustits allocated resources. In rarecases when multiple disks aredegraded, the Data Service mayrestart unexpectedly.

Data Service mayrestart unexpected-ly when RAID is indegraded mode


Reducing the load on the arrayis the only known workaroundfor this issue.

On CS2XX or CS3XX, the arraymay run out of data pages whenunder a heavy load. This will re-sult in an unexpected Data Ser-vice restart.

Data Service mayrestart unexpected-ly for CS2XX andCS3XX arrays whenunder a heavy load



When trying to allocate datapages for many large FingerprintIndex Hash Table indirectblocks, the process may fail dueto insufficient memory. As a re-sult, the Data Service mayrestart to recover the condition.

Data Servicerestarts unexpect-edly while allocat-ing data pages



When trying to allocate datapages for many large FingerprintIndex Hash Table indirectblocks, the process may fail dueto insufficient memory. As a re-sult, the Data Service mayrestart to recover the condition.

Data Servicerestarts unexpect-edly while allocat-ing data pages


Not applicableIn rare instances during offsetcalculation, the File System ser-vice may restart when attempt-ing to read data for replication.The service restarts to recoverfrom the condition.

File system servicemay restart on up-stream array duringreplication orresync of syn-chronous replica-tion.


Not applicableSoftware update to NimbleOS5.2.1.0 and later triggers an up-date of on-disk data structures.Under certain rare conditions,this update could potentiallytake a long time and result in arestart of the Data Service. Thismay cause a momentary delayin IO but should not result in anysignificant disruption, as the da-ta services daemon is designedto restart efficiently before anyIO timeout can occur.



Known Issues 26



Data service will be available af-ter restart.

During NimbleOS metadatasync, in rare instances, the dataservice may restart unexpected-ly. The metadata sync operationitself wont be affected and therestart will reset the race condi-tion; the data service will stabi-lize after the restart.

Data ServiceRestart due to arace condition dur-ing metadata sync



The Data Service may restartunexpectedly if the VolumeManager health check exceedsexpected time out. The servicerestarts to clear the condition.

Data Service mayrestart due to vol-ume managerhealth check failure


Not applicableAs part of the file system check-point process, internal indexesare required to merge to disk.The health check process usesa heartbeat mechanism to deter-mine if the merge is makingprogress. Under some circum-stances, the process performingthe merge of a batch of updatesto the index fails to heartbeatwithin a deadline. When thathappens, the Data Service mayrestart with a health check fail-ure.

Data Service mayrestart unexpected-ly with health checkfailure when inter-nal index datastructures take toolong to merge


Not applicableUnder certain conditions, theData Service may restart whena large number of internal index-es merge within a short time-span and when some of theseindexes need to merge multipletimes in the same checkpoint. Inthis case, there can be lock con-tention between operations re-sponsible for picking what tomerge and operations process-ing the merge, leading to healthcheck timeout.

Data Service mayrestart unexpected-ly with VM healthcheck failure due tolock contention.


Known Issues 27



Not applicableUnder rare circumstances, inter-nal threads in the Data Servicecan enter a deadlock when con-tending on the same set of re-sources. When the processhealth monitor detects thisdeadlock, it will force the DataService process to restart in or-der to recover from this situa-tion.

Deadlock in DataService processmay cause a restart


Not applicableThe data services daemon peri-odically synchronizes its persis-tent in-memory (NVRAM)structures with its other objectson flash. This process is requiredto complete within a reasonableamount of time. Under certainrare conditions, this process canget delayed and trigger a restartof the data services daemon.This can cause a momentarydelay in IO which the daemonrestarts. There should not beany disruption of IO, since thedaemon is designed to restartwithin any IO timeout limits.



Not applicableThe File System Service mayunexpectedly restart because itis not able to allocate memory.This can happen when the pro-cess in charge of evicting dataout of cache cannot evict fastenough, so the filesystem is un-able to allocate memory for newincoming data.

File System Servicemay restart due tomemory exhaustion


Not applicableIn certain multi-array setupwhere replication is in progressmight encounter a situationwhere peer array is goingthrough a software upgrade andis actually unreachable by otherarray. The other array is howev-er unaware of it because somenetwork device has intervenedthe reachability status of thepeer array. The other arrayneeds to perform certain opera-tions which has a timeout associ-ated with it and undergoes asystem restart to recover.

Multi-array setupwith replicationmight experiencefile system restartswhen peer array isunreachable


Known Issues 28



Not applicableUnder certain circumstances, anunexpected Data Service restartmay be triggered with a genericAsynchronous Task Managerhealth check failure. The DataService restarts and resumesoperation normally, withoutcausing loss of access from theconnected hosts.

Unexpected DataService Restart


NoneData Service may restart whengathering garbage collectiontelemetry if cache subsystem isnot fully initialized.

Data Service mayrestart when gather-ing garbage collec-tion telemetry


Not applicableThe Group Data service mayrestart unexpectedly when outof memory condition is encoun-tered. The service restarts toclear the condition.

Group Data Servicemay restart unex-pectedly


Not applicableWhile the Data service is process-ing Update Entries in back-ground, one of these back-ground operations may exceedthe expected timeout and theservice will restart to recover.



Not Applicable, the Data Servicewill resume normal operationafter restart.

Generation delete loads a largenumber of ondisk metadatablocks which may prevent blockindex operation checkpoint fromfinishing. This causes the volumemanager health check to failwhich results in Data Servicerestart.

Data Service mayrestart due to vol-ume managerhealth check failureduring generationdeletion


Not applicableWhen a read op finds partial da-ta in-core, it issues a media readto get remaining data. By thetime, media read returns, the in-core data is synced, and tree isreopened for deletion. The readdoes not expect tree to be indelete state and causes the DataService to restart.

Data Service mayrestart unexpected-ly due to race condi-tion


Contact Nimble Storage Support.When flash cache Garbage Col-lection copies forward live dataof a fragmented segment, itcould consume more buffersthan provisioned and cause theData Service to restart to recov-er.

Data Service mayrestart when run-ning out of buffers


Known Issues 29



Not applicable.Due to issues in communicatingwith the partner array duringreplication, there are few caseswhere the operation is not ableto make progress. As a result,the file system may restart tocorrect this condition.

File system restartto recover fromstalled replication


Not applicableWhile committing internaltransactions, Data Service mayhit a rare race condition. To re-cover from this Data Servicemay restart.



Not applicableWhile committing internaltransactions, Data Service mayhit a rare race condition. To re-cover from this Data Servicemight restart



Not applicableIf IO to disk are slow or fail, theData Service may restart to tryto recover the condition.

Data Service restartdue to slow disk IOor disk IO failure


Not applicableDue to a race condition, the DataService may restart during agraceful shutdown causing unex-pected Data Services restartmessages to be generated. Thisshould not cause any I/O impactbecause the Data Service is al-ready in the process of shuttingdown.

Data Service canrestart unexpected-ly during shutdownprocess


Pause replication until the net-work link used for replication isstabilized.

During replication, a rare racecondition between adding anddeleting internal recurring taskscan cause a Data Service restart.Arrays that hit this conditiontypically experience a singleservice restart that automatical-ly recovers the condition. How-ever, if the network link used byreplication is unstable, frequentreplication disconnects dramati-cally increase the likelihood ofencountering multiple Data Ser-vice restarts due to this condi-tion.

Data Service mayrestart during inter-nal task scheduling


Known Issues 30



Not applicableIn rare cases, Data Service mayrestart during snapshot replica-tion due to the failure of check-sum algorithms to detect allnetwork errors.

Data Service mayrestart due to net-work errors


Not applicableThe Data Service may restartunexpectedly if Fibre Channelsession termination exceedstimeout to complete. The servicerestarts to recover from thecondition.



Enabling encryption will resolvethe issue

Disabling encryption mightcause NVRAM data to fill upwith data waiting for masterpassphrase, which can causeSynchronous Replicated vol-umes to go out of sync.

Disabling encryp-tion may causeSynchronous Repli-cated volumes toremain out of sync


Perform one of the followingoptions to avoid/mitigate the is-sue: 1. Reduce overall workloadon the array. 2. Reduce copy of-fload workload on the array.Contact HPE Nimble StorageSupport if further assistance isneeded.

Copy offload optimizations fordeduplication were added inNimbleOS versions 5.1.x andlater. The changes may lead toincreased latency when copy of-fload workflows are added to thearray. This is due to an increasein update entries requiring pro-cessing.

Arrays may experi-ence increased la-tency during copyoffload workloadoperations


The array will continue to shut-down after the Data servicerestart.

Volume manager does not resetinternal callbacks during theshutdown phase causing theData service to restart.

Data service mayrestart during arrayshutdown


Not applicableThe Data Service may restartduring array shutdown whenjobs related to the Data Serviceare unable to be gracefullyshutdown. The restart shouldnot have any impact as the arrayis in shutdown process.

Data Service mayrestart during arrayshutdown


Not applicableThe volume manager will decre-ment bin and child volume folderentries during volume deletion.In rare occurrences, anotherthread may decrement the childvolume entry and not the binentry, causing the Data serviceto restart.

Data Service mayrestart on down-stream array due torace condition dur-ing volume deletion


Known Issues 31



Not applicableUnder certain circumstances, anaggressive internal assert maylead to unexpected restart of theData Service.

Aggressive assertmay lead to unex-pected restart ofthe Data Service


No action is required, the alertshould resolve a short time later.

The Group Management servicesynchronizes attributes with theData Service on the array. If theData Service does not send aresponse within 10 seconds, theGroup Management service willgenerate an alert indicating theattribute synchronization maybe delayed. The service will retrythe synchronization, and it willcomplete a short time later whenthe response from the Data Ser-vice has been received.

Attribute synchro-nization may be de-layed


None. The Data Service Restartwould resume normal I/O opera-tions.

A rare scenario can result into arace condition between clonecreation and I/O operations onan encrypted volume; during thistime while fetching the encryp-tion keys Data Service mayrestart and resume normal I/Ooperations.

Data Service restartdue to a race condi-tion


Remove downstream replica us-ing the correct steps orderedbelow. 1. Claim the repli-ca volume. 2. Delete all of thesnapshots for the replica vol-ume. 3. Delete the replica vol-ume.

The service may restart whenremoving the downstream repli-ca using the steps below. 1. Deletion of all snapshots forthe replica volume. 2. Claim thereplica volume 3. Delete thereplica volume

Very rare race be-tween Vol claim(with all snapshotsmarked for dele-tion) and space re-calculation on repli-ca downstream vol-ume


Retry operation after a few min-utes to reassign array to pool.

Assigning an array to a pool im-mediately after unassigning itfrom the same pool will fail withthe following error - Failed toassign arrays to the pool: A ser-vice is not running or is notreachable

Unassigning andreassigning array toa pool within 5 min-utes will fail


Not applicableThe Data Service on the arraycommunicates with the GroupManagement Service to handlearray operations. If the commu-nication between the two ser-vices exceeds timeout, the ser-vice will restart to recover.



Known Issues 32



Reduce the frequency of volumeclone create and delete opera-tions to minimize the likelihoodof occurrence.

Aggressive volume creation anddeletion may cause one of thetree data structures to hit maxi-mum children it can have. Thislimit can occur on volume cre-ation because volume deletiondestroys the children asyn-chronously. The Data Service willrestart when this limit has beenreached.

Aggressive Volumecreation and dele-tion may result inData Service restart


Not applicableThe Group Management servicecommunicates with the VSS ser-vice when creating VSS snap-shots. If this communication isnot able to be completed withinthe expected timeframe, theservice restarts to recover.

Group Managementservice may restartwhen attempting tocreate VSS snap-shot

Host IntegrationAS-113545

Contact HPE Nimble StorageSupport to increase the memorylimit for the service.

In some instances the cimserverservice will exceed its memorylimit and no longer be able tostart.

Cimserver stopswhen memory limitis exceeded.

Host IntegrationAS-108647

Contact Nimble Storage Supportto identify the reason for thepartition filling up and to cleanup the log partition.

Log files generated by processesin the Nimble Operating systemsare rotated and archived usingcertain parameters. Under someconditions, if processes log morethan normal, this can result inthe log partitions being filled up,leading to other issues with crit-ical processes.

Log partition mayfill up

PlatformAS-50033


During controller boot, firmwareupdate may fail to completecausing the controller to boot tomaintenance mode.

Replacement con-troller fails to bootto NimbleOS

PlatformAS-107299

1. Reseat one of the power sup-plies to clear the hang condition.2. Or update NimbleOS to ver-sion 3.6.0.0 or later to minimizethe number of internal com-mands that can trigger this is-sue.

Under certain circumstances, in-ternal commands may cause theintegrated circuit to hang whichcauses both power supplies ofthe head shelf to appear asmissing. The problem does notimpact the power supplys abilityto deliver power to the array.

Both power sup-plies showing up asmissing

PlatformAS-53621

Please contact HPE NimbleStorage Support

In rare incidents, controllers donot power on following powercycle.

Controller does notpower on followinga power cycle.

PlatformAS-100088

Known Issues 33



Referencing the correspondingExpansion Shelf Quick StartGuide, correct the hardware ca-bling issue.

If a shelf is cabled incorrectlyand added to an array, the rawcapacity calculation could failleading to multiple restarts ofthe Data Service.

Incorrect shelf ca-bling can cause aseries of unexpect-ed Data Servicerestarts

PlatformAS-67242

The controller reboot should re-store SAS HBA to normal state.HPE Nimble Support may con-tact customer to collect addition-al diagnostics if required.

When the SAS HBA detectsfaulty states, to recover, the ar-ray needs to reset the SASHBA’s firmware. The SAS HBAfirmware reset can block diskI/Os significantly longer than ourHigh Availability monitoringtimeouts allow. Instead, a con-troller reboot is triggered imme-diately if this state is detected,resulting in an unexpectedtakeover event.

Unexpected con-troller takeover dueto incorrect state ofthe SAS HBA

PlatformAS-33725

Not applicableIn certain conditions, I/Ostracked for certain operationsmay total zero, which triggers acheck exception. The reason forthe incorrect value is variabletruncation. The service restartsto recover from the condition.

File System servicemay be restart ontruncated variableread

PlatformAS-114564

Not applicableThe Data Service may restartunexpectedly when it detects aninternal check error. The restartof the service clears the condi-tion.

Data Service mayunexpectedlyrestart

PlatformAS-90850

Not applicableThe Enclosure Managementservice may unexpectedlyrestart due to a race conditionwhich is resulting from drivestatus which has already beenmarked removed by the DataService. The restart of the ser-vice clears the condition.

Enclosure Manage-ment service mayunexpectedlyrestart due to drivestatus race condi-tion

PlatformAS-95294

Contact HPE Nimble StorageSupport to identify the faultydrive for replacement.

Data Service may become latentand restart when the array hasa faulty drive with a lot of medi-um read and IO timeout errors.

Data Service mayrestart if the arrayhas an faulty drivewith a high numberof medium read er-rors

PlatformAS-110036

Known Issues 34



Please contact HPE NimbleStorage Support so the problem-atic drive can be replaced.

In rare instances due to slow IOto one of the disks, the DataService may hit a timeout andrestart unexpectedly. This issuemay occur during a NimbleOSsoftware update.

Data Servicerestarts due to slowIO to one of thedisks

PlatformAS-90096

The restart of the service willclear the low memory condition,no further action is needed.

Data Service may restart in therare case when a controller islow on memory.

Data Service mayrestart if a con-troller is low onmemory

PlatformAS-99567

Not applicableIn rare circumstances, the arraysdata service may restart unex-pectedly when it encounters arace condition following internaldata striping processing. Thedata service will stabilize follow-ing the restart.

Data Service mayrestart unexpected-ly during internalstriping operation

PlatformAS-113002

Not applicableThe Data Service may restartdue to a transient resource allo-cation failure. This happenswhen the service cannot com-plete a disk IO due to transientmemory allocation failure. Thisdoes not cause a service outageas Data service continues normal-ly after a restart.

Data Service restartdue to resource allo-cation failure.

PlatformAS-103802

Not applicableIn rare circumstances, a kernelmemory management defectmay manifest itself duringmemory unmapping operationsand initiate a controller reboot.If this occurs on the active con-troller, it will result in an unex-pected takeover.

Kernel memorymanagement de-fect may cause anunexpectedtakeover

PlatformAS-116155

Not applicableOn very rare occasions of HBAerror handling, interrupts couldbe turned off long enough forthe NVRAM driver to timeoutwhile trying to complete directmemory access operations. Thecontroller recovers after a re-boot is initiated by the kernel.

Kernel panics whileprocessing host busadapter errors

PlatformAS-46629

Not applicableIn rare circumstances, a kernelfile system defect may manifestitself and cause a controller re-boot. If this occurs on the activecontroller, it will result in an un-expected takeover on the array.

Kernel file systemdefect may causean unexpectedtakeover

PlatformAS-116189

Known Issues 35




Due to an incorrect responsefrom dual flash carrier (DFC)firmware the Array ManagementService might restart intermit-tently.

Array Managementservice may restartunexpectedly

PlatformAS-117809

Not applicableThe Enclosure Managementservice may unexpectedlyrestart when it detects an inter-nal check error. The servicerestart clears the condition.

Enclosure Manage-ment Service mayrestart unexpected-ly

PlatformAS-105053

No workaround is required. Thearray will recover itself automat-ically by restarting the DataService.

On rare occasions, the arraygroups Data Service may fail toinitialize if a shelf state changeoccurs simultaneously.

Delay with DataService startingduring shelf statechange

PlatformAS-101570

Review the array configurationmatrix for the array model: <ahref=https://infos-ight.hpe.com/InfoSight/media/lo-cal/active/34/CSxxx%20Con-fig%20Matrix.pdf>https://infos-ight.hpe.com/InfoSight/media/lo-cal/active/34/CSxxx%20Con-fig%20Matrix.pdf</a> Removeany additional cache from theexpansion shelf that exceeds themax cache limit based on arraymodel.

ES2 and AFS2 expansionshelves contain additional slotsfor upgrading cache capacity ofthe array. Older array modelshave a maximum cache limit thatcan be handled by the array. IfES2 or AFS2 expansion shelvesare added to an array and thecache exceeds the max cachelimit for the array type, the dataservice may restart due to run-ning out of data pages.

Data service mayrestart if maximumcache exceeded forCS215, CS235,CS300, CS500,CS700 arrays

PlatformAS-93296

Add the disk from the CLI usingthe disk add command and out-put from disk list: 1. Run disk --list 2. Note the slot number, andshelf location for the disk la-beled foreign. 3. Add the disk:disk --add <slot number> --array <arrayname> --shelf_location <shelf loca-tion> Note: the --force optionmay be required Contact HPENimble Storage Support if thedisk does not move to resynchro-nizing state after completing thecommands.

Disk will report foreign for diskstate in the GUI Hardware pageor in the output of disk --listfrom the CLI. This typically oc-curs if diagnostic data may nothave been removed after test-ing.

Replacement diskreports foreign fordisk state inGUI/CLI

PlatformAS-99428

Known Issues 36



Not applicableIn rare cases, an SSD may reachits endurance limit but continuesto pass Nimble Drive Error Re-covery algorithm. This causes anever-ending process of off-lin-ing and on-lining the drive. Thismay occur for Intel and ToshibaSSDs.

SSD has reached itsendurance limit(wear leveling) butthe disk is notmarked failed.

PlatformAS-91522

Not applicableIn a rare scenario, EnclosureManagement service may occa-sionally restart upon a drivefailure in system partitions. Therestart of the service clears thecondition.

Enclosure Manage-ment service occa-sionally restarts up-on a drive failure

PlatformAS-86100

Not applicableDue to a possible software de-fect, the red disk slot LED mayilluminate even when there areno issues with the correspondingdrive. This is a cosmetic issuethat does not impact functional-ity.

4U Chassis disk slotLEDs illuminate er-roneously

PlatformAS-116339

Not applicableThe Group Management servicemay restart if an error whileopening interconnect-ips fileoccurs. The service restarts torecover from the condition.


PlatformAS-112701

Not applicableThe File System Service mayrestart during memory allocationif there is not enough memoryavailable. The service restarts torecover from the condition.

File System Servicerestarted unexpect-edly

PlatformAS-116111

Not applicableThe Group Management Servicemay restart unexpectedly dueto receive buffer exhaustion onthe management network inter-face. No visible impact has beenreported because of this issue.

Unexpected GroupManagement Ser-vice restart due toreceive buffer ex-haustion

PlatformAS-98885

Not applicableFile System service may restartunexpectedly when a healthcheck exceeds timeout for vol-ume manager on the array. Theservice restarts to recover fromthe condition.

File System Servicemay restart unex-pectedly

PlatformAS-92471

Known Issues 37




Under rare circumstances, if anarray software update previous-ly failed and reverted, and anarray chassis swap is performedbefore the next software update,the array configuration files maycontain invalid data. This willcause the controllers to rebootand the Array Management ser-vice to restart.

Array may fail toboot following asoftware update ifprevious chassis in-formation is refer-enced

PlatformAS-114390

Please contact HPE NimbleStorage Support to resolve thisissue. This issue is resolved inNimbleOS version 5.0.2.0 andlater.

An attempt to create new VMsin a VMWare vVol environmentfails after updating to NimbleOS4.x.x.x. This occurs when a sys-tem partition within the array isrunning out of space.

VM creation fails inVMWare VVol envi-ronment after up-date to NimbleOS4.x.x.x

PlatformAS-76174

Free up /var disk space bydeleting unwanted log files(/var/log/EMU/mili/mili2d.log)and rebooting the host.

As part of the dHCI updateworkflow which involves the ES-Xi server update, some com-mands need to be run on theserver. Running these com-mands fails with error Error: Ageneral system error occurred:Internal error. if the /var is full.This is a known issue with 6.7builds running with Emulexdriver which has been fixed aspart of ESX 6.7 U2. <ahref=https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-esxi-67u2-release-notes.html#re-solvedis-sues>https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-esxi-67u2-release-notes.html#re-solvedissues</a>

dHCI update work-flow can fail if /varmountpoint on thehost is full.

dHCIAS-103315

The only way to resume the up-date would be to failover to theoriginal group leader array andthen resuming the updatethrough the dHCI vCenter plug-in.

When the dHCI unified updatefeature is used to update thedHCI stack, the update will failif a Group Leader Failover oc-curs during the process.

An in-progess dHCIupdate fails if thegroup leader failsover

dHCIAS-103247

After confirming the array hasreturned to Active/Standby sta-tus, stop the hung task and runthe Nimble Add ProStack servertask again.

If an array failover occurs whileNimble Add ProStack server taskis running from vCenter, theprocess may hang and not com-plete.

Nimble AddProStack servertask may hang ifarray failover oc-curs

dHCIAS-97685

Known Issues 38



Not applicableWhen an ESXi server is added todHCI cluster, the update pagedoes not get updated to includethe newly added ESXi server.This refresh happens every 4hours. After the next refresh, thenew ESXi servers version will beincluded and accounted for onthe update page.

The update pageon the dHCI plugintakes 4 hours to re-fresh

dHCIAS-103769

A valid ESXi license must be as-signed to the server.

When adding a server with anexpired ESXi license to the dHCIcluster, through the vCenterplugin, you may see an errorsaying - Failed to submit a taskto add server.

Addition of a serverwith expired ESXilicense fails

dHCIAS-95054

Admission Control should bedisabled on a dHCI cluster forthe update to proceed.

For ESXi server update, DRS isused to migrate VMs running onthe server. If admission controlis enabled on the dHCI cluster,DRS is not able to migrate VMsoff a server.

dHCI update failswhen AdmissionControl is enabled

dHCIAS-101915

Not applicableThe Data service will wait up to300 seconds for host responseto iSCSI commands. If host doesnot abort commands that takemore than 300 seconds to com-plete, the Data service willrestart.

Data Service mayrestart when hostdoes not issueabort to timed outcommand

SANAS-108946

Not applicable.During a controller reboot, dueto resource contention betweennew Fibre Channel (FC) connec-tion attempts and shutdown ofthe FC module, the Data Serviceon the array may restart unex-pectedly.

Data Service restartduring shuttingdown FC service onthe standby con-troller

SANAS-100197

Known Issues 39



These issues appear to be trig-gered by events external to thecontroller such as host HBA, ca-ble, SFP, zoning or switch issues.Port congestion may also play arole. Migrating volumes to otherarrays or adding additionalHBAs may alleviate the conges-tion.

The Fibre Channel driver statemachine that handles IO aborts,IO timeouts on the fabric, ses-sion logout, and port ownershipchanges relies heavily on theport owner to properly managestate in a timely manner. Thisgenerally works, but there aresituations where the port ownerdoesnt have enough context todo the job properly. This canlead to more IO timeouts, HBAresets, DSD restarts and occa-sionally kernel crashes. A futureversion of the driver will simplifythis process by handling it entire-ly within the driver.

Fibre Channel IOaborts and hangsmay lead to DSD orkernel crash

SANAS-94229

Not applicableDuring port owner failover be-tween the Data Service and theSCSI Failover/Forward Service,outstanding IOs may timeoutand get aborted. This can leadto state machine issues in be-tween the two services whichmay cause one or both servicesto restart. In rare instances, thismay also cause the controller toreboot. The service restartand/or controller reboots to re-cover from the condition.

Data Service, SCSIFailover/ForwardService, and/orcontroller mayrestart unexpected-ly for Fibre Channelarrays

SANAS-92368

Identify the offline volumes orstale targets and initiate a hostside cleanup/rescan to avoid re-peated login attempts and fail-ure to the offline or stale targets.

Logins to CHAP authenticationenabled volumes could leak asmall amount of memory thesize of CHAP username. Over aperiod of days and weeks, thisleak can result in one or more ofthe NimbleOS processes runningout of memory. As a result, Nim-bleOS services may restart unex-pectedly. The issue is exacerbat-ed by repeated failed login at-tempts to offline volumes orstale targets.

NimbleOS servicesmay restart unex-pectedly due toslow leak withCHAP logins

SANAS-109412

Known Issues 40



Identify the offline volumes orstale targets and initiate a hostside cleanup/rescan to avoid re-peated login attempts and fail-ure to the offline or stale targets.

Logins to CHAP authenticationenabled volumes could leak asmall amount of memory by re-peated failed login attempts tooffline volumes or stale targets.Over a period of days andweeks, this leak can result in oneor more of the NimbleOS pro-cesses running out of memory.As a result, NimbleOS servicesmay restart unexpectedly.

NimbleOS servicesmay restart unex-pectedly due tomemory leak in lo-gin path

SANAS-113037

Increase NCMs configuration forminimum number of connectionsper volume from 2 to 4 or high-er.

The NCM (Nimble ConnectionManager) handles the iSCSIconnection counts. Today, theNCM is designed to use a FULLMESH connection mechanism.However, when there are veryfew initiators and target ports,the total connection count willbe minimal. The NCM will defaultto a minimum of 2 connectionsper volume. Increasing the num-ber of connections to 4 or moremay produce the maximumthroughput.

Poor iSCSI perfor-mance seen whenminimum connec-tion count is used

SANAS-111926

Not applicableWhen the active controller isbeing shutdown, the Data Ser-vice runs into an internal errorcondition that causes the serviceto restart unexpectedly. Sincethe process is already beingshutdown, there is no impact touser data availability.

The Data Servicerestarts unexpect-edly during shut-down

SANAS-98042

Not applicableWhen the Data Service is in pro-cess of shutdown, the servicemay restart due to race condi-tion when shutdown threads donot wait or abort pending opera-tion threads.

Data Service mayrestart due to racecondition

SANAS-64790

Not applicableThe Data Service or SCSI HighAvailability Service may restartdue to race condition encoun-tered during process shutdown.

Service may restartdue to race condi-tion

SANAS-89753

Known Issues 41



Not applicableUnder certain conditions, theData Service on the GroupLeader array may restart unex-pectedly while removing mem-ber array. This is due to a racecondition when processing SCSIRTPG (REPORT TARGET PORTGROUPS) commands. The ser-vice should stabilize on its ownshortly following the restart.

Data Service mayrestart unexpected-ly while removingmember array

SANAS-101325

Not ApplicableThis scenario is rare to happenbut presently not handledgracefully leading to a File Sys-tem restart for recovery. The is-sue is triggered when a write re-quest with valid length is re-ceived in SCSI Command Descrip-tor Block but invalid (zero) valuein Data-Out Buffer.

File System servicemay restart whenan invalid write re-quest is received

SANAS-94761


In certain scenarios, off-lining avVol snapshot will not completedue to the existence of a ACLbound with it. The vVol snap-shot cannot be off-lined until thebound ACL has been removed.

Cannot take abound virtual vol-ume snapshot of-fline

System Manage-ment

AS-116512

Not applicableA race condition may occur whileupdating records in the ScaleOut database when two threadsattempt to update the samerecord.


System Manage-ment

AS-110367

Not applicableGroup Management Service mayrestart unexpectedly as onethread has taken a ReadWritelock which has another writerthread, which is waiting forScale-Out Database (SODB)transaction to be completed.The service restarts due to theSODB transaction exceeding theexpected timeout.

Group ManagementService may restartdue to race condi-tion

System Manage-ment

AS-103766

Not applicableGroup Management service mayrestart due to Volume Manage-ment thread and API thread forsnapshot creation/deletion en-tered race condition. The servicerecovers after restart.

Group ManagementService restart dueto race condition

System Manage-ment

AS-105929

Known Issues 42



Not applicableWhen created with the RESTAPI, by default the cloned vol-ume inherits the ACL from theparent volume. There is no wayto set or change the ACL for theclone at the time of creationthrough the REST API. Clientsshould make two REST calls, oneto create the clone and then oneto change the ACL to the de-sired value. In the future, wecould change the REST API tonot set the ACL by default andallow the client to set the ACLat the time of the clone creationto the desired value. This onlyapplies to volumes that haveagent_type set to none

REST API Clone ofvolume does notsupport settingACL at time ofclone creation

System Manage-ment

AS-54302


The Group Management servicecommunicates with the DataService to add the ProtocolEndpoint ACL to the Scale OutDatabase for vVols. If the pro-cess does not complete as ex-pected the Group Managementservice will attempt to retry theoperation. Under some circum-stances, instead of retrying thatoperation, this ACL get erro-neously deleted and any PEreads (REST or cli) followingcould result in GMD restart.

Group Managementservice may restartwhile reading proto-col endpoint infor-mation

System Manage-ment

AS-119873

Not applicableAPI calls occur between theEvent service and Group Man-agement service when an alarmis cleared. The calls will lookupthe alarm ID and onset event inthe Scale Out Database (SODB).If the alarm is cleared before theonset event lookup completesand is not found during thesecalls, the service may restartunexpectedly.


System Manage-ment

AS-83604

Known Issues 43



The problematic alarm can bemanually deleted through theCLI command: alarm --delete<alarm_id>

Due to a race condition it ispossible for an alarm to remainuncleared on the system evenwhen the alarm condition it isreporting is no longer the case.This can happen if the onsetalert and recovery alert weregenerated at close to the sametime.

Alarm may notclear as expected

System Manage-ment

AS-94398

Not applicableDue to the multi-threaded na-ture of the Alerts and AlarmsService, it is possible for anevent with a later id to be post-ed prior to an event with an ear-lier id. Therefore it will have anearlier timestamp even thoughits ID is higher. This can causethe IDs to appear out of order.However, the alarms in the listare ordered correctly by times-tamp.

Alarm IDs in alarmlist may appear outof order.

System Manage-ment

AS-105431

After confirming that the config-uration sync has completed thealarms can be deleted or ac-knowledged through the GUI.

Alarms describing a delayedconfiguration synchronizationto an array may not be clearedproperly after an extended net-work outage and remain activein the GUI.

Alarms for Configu-ration Synchroniza-tion may remain af-ter sync has com-pleted

System Manage-ment

AS-99427

Clear the alarm manually fromthe Command Line Interface: 1.Use alarm --list command to de-termine the alarm ID. 2. Usealarm --delete <ID> com-mand to delete the alarm.

An alarm onset should be setprior to discovery request aspart of alarm processing. Insome cases the discovery re-quest will appear first resultingin the alarm not being cleared.

Configuration syn-chronization recov-ery alarm is notcleared

System Manage-ment

AS-87604

Not applicableThe Eventd process may restartunexpectedly due to a raredeadlock condition between itsthreads. The restart of the pro-cess will clear the condition.

Eventd processmay restart unex-pectedly

System Manage-ment

AS-103567

Not applicableEvent Service may restart whenmemory limit is reached. Theservice will restart to recoverfrom the condition.

Event Servicerestarts due tomemory

System Manage-ment

AS-84502

Rename the folders to beunique. If the Event Manage-ment service continues to restartor remains unavailable, contactHPE Nimble Storage Support.

When an alert is raised on oneof two folders having the samename but are located in twoseparate pools, the Event Man-agement service may restart re-peatedly.

Event Managementservice restartwhen two folders indifferent poolshave the samename

System Manage-ment

AS-101273

Known Issues 44



Not applicableThe Event service may restartunexpectedly due to a memoryaccess issue. The restart will notimpact data connections to thearray and the process will recov-er after the restart.

The Event servicemay restart unex-pectedly

System Manage-ment

AS-85608

Not applicableThe eventd process may restartunexpectedly in systems withlarger configurations due to ex-ceeding memory limit. The ser-vice will recover after the restart.

Eventd processmay restart due toexceeding memorylimit

System Manage-ment

AS-99679

The alarm can be cleared fromthe CLI using the steps below.List the alarms with the follow-ing command to obtain thealarm ID: alarm --list Delete thealarm using the alarm ID ob-tained from the list. alarm --delete <alarmID>

Alarm notifying about delay insnapshot attribute synchroniza-tion is not cleared automaticallyafter successful synchronization.If the alarm is not manuallydeleted it will keep remindingthe customer even after success-ful synchronization.

Snapshot AttributeSynchronizationDelay Alarm is notcleared

System Manage-ment

AS-86837

Not applicableAlerts and Alarms processingservice may restart unexpected-ly when certain operation sur-pass the designated healthcheck timeout. The process willstabilize following the restart.

Alerts and Alarmsprocessing servicemay restart unex-pectedly

System Manage-ment

AS-50821

Not applicableThe Eventd process may infre-quently crash, due to a bug in anexternal library used by the DNSresolver. The restart will not im-pact data connections to the ar-ray and the process will recoverafter the restart.

Eventd processmay restart inter-mittently

System Manage-ment

AS-46024

Not applicableThe array will reuse the sessionto the SMTP server each time itattempts to send an email. If thissession is no longer active, it willreport a failure to send the alert,then open a new session, andsuccessfully send the alert if theSMTP server configuration isvalid.

Event Service mayreport SMTP failureto send alert whenalert is sent success-fully

System Manage-ment

AS-40238

Known Issues 45



The recipient can create an in-bound transport rule to appenda disclaimer to the messagesfrom the problematic sender.The disclaimer will append theexpected CR-LF combination tothe message so that it can bedelivered. (This disclaimer mayconsist of a single charactersuch as a period or a dash.)

When the array sends an alertvia SMTP, the message may berejected by the server indicating550 5.6.11 SMTPSEND.BareLine-feedsAreIllegal. This can occurif the receiving server does notsupport BDAT command forSMTP chunking

Alerts sent viaSMTP may be re-jected

System Manage-ment

AS-72902

Not applicableInternal database maintenanceprocessing may exceed the ex-pected health check timeout.When this occurs, the ArrayManagement service may restartto recover from the condition.

Array Managementservice may restartunexpectedly

System Manage-ment

AS-110436

Not applicableEvery night, when inactive keysfor deleted encrypted volumeare deleted by the array, it cre-ates an audit log entry with rootas the user performing the ac-tion.

Purge inactive en-crypted keys ap-pears in audit log.

System Manage-ment

AS-96966

The Group Management servicewill recover after the crash. Theworkaround would be to nolonger use an excessively longusername, and reduce the user-name to under 255 characters.

An excessively long usernameof over 255 characters will ex-ceed a character limit within thearray groups auditing frame-work. This would cause theGroup Management service torestart unexpectedly.

Group ManagementService restarts dueto excessively longusername

System Manage-ment

AS-82919

Not applicableIf a user tries to create a newuser account, but the user does-nt have the privilege to do so,the user creation will fail. Howev-er, an audit log entry is not cre-ated.

No Audit Log entryis created if userdoes not have theprivilege to createuser

System Manage-ment

AS-71090

Not applicableThe Array Management Serviceprocess may restart after run-ning for a long time due to amemory leak issue. This cancause a short interruption todata service, but it will resumeonce the process has restarted.

Array ManagementService restart

System Manage-ment

AS-116083

Known Issues 46



Not applicableThe Group Management Serviceon the array may restart unex-pectedly when a SOAP timeoutis encountered after trying tocreate a volume. This occurs dueto a race condition where thearray attempts to delete thevolume after the creation at-tempt fails.

Group ManagementService restarts fol-lowing volume cre-ation timeout

System Manage-ment

AS-104640


The GUI relies on REST queriesto obtain FC session information.In environments where there arehigh number of sessions to thearray, the queries can take along time to complete. This willresult in slower GUI response forthe array.

GUI performancemay be slow for Fi-bre Channel (FC)arrays with highsession count

System Manage-ment

AS-112416

Perform the Autosupport valida-tion process again.

When autosupport configurationvalidation is performed, internalprocess tracking may abortcausing the Group ManagementService to restart.

Group Managementservice may restartwhen performingAutosupport Valida-tion

System Manage-ment

AS-104185

Not applicableThis issue is seen when theGroup Leader role migrationcompletes, and the previousleader is left unconfigured. Inthis scenario, the Group Leadermay treat the previous leader asa member array and initiate theBackup Group Leader (BGL)setup. If a customer attempts toremove the array during thisBGL setup, the removal fails.

Array removal willfail if Backup GroupLeader setup is inprogress

System Manage-ment

AS-115935

Not applicableConnection to the Scale-OutDatabase can not be reinitializedwhen a transaction is inprogress. The Group Manage-ment Service will restart to re-store connection.

Group Managementservice may restartwhen connectionsto Scale-OutDatabase exceedsthreshold value

System Manage-ment

AS-109127

Known Issues 47



Not applicableDuring key value metadata han-dling, the process may deleteprimary keys in one table of theScale-Out Database (SODB) andthen try to reference the deletedprimary key as foreign key inanother table in SODB. Thiscauses foreign key violations inPostgres and eventually leadsthe Group Management serviceto restart.

Group Managementservice may restartdue to snapshotkey value metadatahandling

System Manage-ment

AS-105454

Not applicableIn rare scenarios a System Man-agement Service may restart af-ter Software Update. SystemManagement Services such asarray GUI information may beunavailable for a brief period oftime after Software Update.

System Manage-ment service mayrestart after Soft-ware Update

System Manage-ment

AS-117328

Not applicableUnder certain circumstances, theArray Management Service maydetect operations that are stillrunning during a planned shut-down. This may result in an un-expected service restart prior tothe array completing shutdown.

During a plannedshutdown, the Ar-ray ManagementService may restart

System Manage-ment

AS-115493

Not applicableIf there is a network connectivityissue between the witness andGroup Leader array, the groupstatus CLI output will update theFailover Mode from Automaticto Manual until the connectionis reestablished. It also displaysthe Witness Status as N/A asopposed to Unreachable.

group --status CLIoutput shows incor-rect Failover Modeduring networkconnectivity issues

System Manage-ment

AS-99704

No workaround is needed. Theservice recovers on its own.

In Automatic Switchover environ-ments, in rare instances, networkisolation of the Group Leaderand Backup Group Leader maycause the service that handlesthe automatic switchovers torestart unexpectedly.

Network isolationof the Group Lead-er and BackupGroup Leader arraymay lead to Auto-matic Switchoverservice restarts

System Manage-ment

AS-94683

Known Issues 48



Not applicableDuring software update of arraygroup with Peer Persistenceconfiguration, AutomaticSwitchover (ASO) is disabled. Ifan array goes down (both con-trollers down) during the soft-ware update process, due to apower failure or other unexpect-ed event, hosts could lose accessto data until the failed array re-covers, or a manual switchoverof the affected volumes is done.

Peer PersistenceAutomaticSwitchover (ASO)is disabled duringsoftware update

System Manage-ment

AS-94649

This restart is non-disruptive tothe data on the array, and theArray Management recovers af-ter the restart occurs.

The arrays database system maybecome unavailable for a limitedtime when there is a failure insetting up the Backup GroupLeader. When attempting todiscover a new Backup GroupLeader, the Array ManagementService may restart due to a racecondition.

Array ManagementService restartsduring BackupGroup Leader dis-covery

System Manage-ment

AS-98953

None.Due to a race condition, the Ar-ray Management service mayrestart when the array is in theprocess of shutting down allservices as part of the arrayshutdown. An alert and a pro-cess core could be generated asa result but there is no impactto functionality. Once the arraypowers back on, all services startup normally.

Array ManagementService may restartduring array shut-down

System Manage-ment

AS-106539

Not applicableThe array group CLI commandwith limits option (group --list-limits) displays numeric internalidentifiers as part of the informa-tion listed for the volume infor-mation. These numeric identi-fiers are used by the array onlyand can be ignored.

Group limits com-mand lists internalidentifiers

System Manage-ment

AS-101342


The Event service may restartunexpectedly if an invalid net-work interface entry is found inthe Scale Out Database (SODB).

Event Service mayrestart due to in-valid database en-try

System Manage-ment

AS-103275

Known Issues 49



Not applicableThe Array Management servicemay restart unexpectedly dueto an a memory allocation failurewhen attempting to synchronizeconfiguration with a member ar-ray. The restart of the ArrayManagement service clears thesituation.

Array Managementservice restarts dueto memory alloca-tion issue

System Manage-ment

AS-104812

Please contact HPE NimbleSupport.

Following a power outage, it ispossible that the Backup GroupLeader is not assigned to thegroup. This may occur if theSODB database does not startdue to an SSH key issue.

Backup GroupLeader is not as-signed due to pow-er outage

System Manage-ment

AS-99702

Not applicableThe Group Management servicemay restart while collectingstatistics from member array.This can occur when the requestfrom the group leader to mem-ber array exceeds timeout,causing the service to restart torecover.

Group Managementservice may restartwhile collectingmember arraystatistics

System Manage-ment

AS-93469

The only workaround is to im-prove the quality of the networkconnection so that the loss ofTCP packets is minimized.

Service threads within the groupmanagement API handler arerestricted to run for no morethan 5 minutes. In a very lossynetwork, TCP throughput canbe throttled to almost nothingdue to retransmission timeoutback-off. In one observed case,where the API response wasabout 190 KB, the connectionmanaged to send only about 90KB before the 5 minute timeoutoccurred and caused the GroupManagement service restart.

A lossy networkcauses Group Man-agement servicerestart

System Manage-ment

AS-73595

Not applicableThe Controller ManagementService monitors the controllerinterfaces for network connectiv-ity. The Array Management Ser-vice monitors link status to deter-mine if failover is required dueto network connectivity. Due toa race condition the Array Man-agement Service may initiate anarray failover before the Con-troller Management Servicealerts that interface links aredown.

Interface link alertsmay fail due to racecondition

System Manage-ment

AS-53458

Known Issues 50



If array is queried for statistics,then its frequency should be re-duced. This is specially relevantfor the setup where script orsome monitoring tool does statsquery frequently in a loop.

There is a memory leak in thestat (statistics) component ofthe Array Management service.Magnitude of the memory leakis proportional to the frequencyof stats query.

Array Managementservice restart dueto memory alloca-tion exception

System Manage-ment

AS-98297

Manually delete the alarm fromthe command line interface. 1.Login to CLI 2. Find the alarm IDusing: alarm --list 3. Delete thealarm using the ID alarm --delete<ID>

If an IP address is migrated fromone interface port to another,the alarm that was generatedindicating the original interfacedown may not be cleared.

Alarm not clearedafter IP addressmoves to differentinterface

System Manage-ment

AS-92515

The workaround would be todelete the alarm using the alarm--delete CLI.

When alarm for number of nicsin array net config reaching 120is triggered, it doesnt getcleared even when the numberof nics goes down.

Max limit of 120nics in netconfigalarm does not getcleared

System Manage-ment

AS-87749

Not applicableDue to an issue in POCO library,in certain cases, causing theGroup Management service torestart. The service restarts torecover from the condition.

During shutdownthe Group Manage-ment service mayunexpectedlyrestart

System Manage-ment

AS-112702

Not applicableArray Management Service mayrestart unexpectedly when try-ing to start or stop the GroupManagement Service. The sys-tem recovers automatically afterthe Array Management Serviceis restarted

Array ManagementService restartedwhile starting/stop-ping Group Manage-ment Services

System Manage-ment

AS-74556

Not applicableThere is a --force switch avail-able when deleting a perfor-mance policy via the HPE Nim-ble Storage Array CLI. This --force switch does not work andwill fail with the following: ER-ROR: Failed to delete perfor-mance policy. Resource busy.The --force command is notsupported since the specifiedperformance policy should notbe removed without first check-ing its volume or folder associa-tions.

Force deletion ofuser defined perfor-mance policyshould not be sup-ported

System Manage-ment

AS-74242

Known Issues 51



Not applicableVolume move operations copyboth data and associated meta-data from the source array todestination array. For groupswith multi-array pools, copyingthe metadata can take a signifi-cant amount of time, and theestimate calculation may be inac-curate initially. These estimateswill auto-correct themselves byusing feedback mechanisms.

Volume Migrationestimates may beinaccurate whenmultiple volumesare being migrated

System Manage-ment

AS-101832

Not applicableBackup Group Leader (BGL)may be promoted and/or SystemManagement Service mayrestart. This occurs when thereis high load on either the GroupLeader array or the BGL array,or when there is networkthroughput issues between thearrays. The service restarts torecover from the condition.

Array managementservice may restartunder high load ornetwork connectivi-ty issues betweengroup arrays

System Manage-ment

AS-117683

Not applicableThe Array Management servicemay restart on a group config-ured for high availability duringvarious scenarios when GroupLeader to Backup Group Leadercommunication is high or degrad-ed. Scenarios which may causean array management servicerestart include degraded net-work connectivity between GLand BGL arrays.

Array managementservice may restartduring periods ofdegraded networkconnectivity be-tween high avail-able Group Leaderand Backup GroupLeader arrays.

System Manage-ment

AS-116625

Not applicableArray Management services maybe unavailable for a short timedue to restart during automaticfailover.

Array Managementprocess may restartduring automaticfailover

System Manage-ment

AS-94835

The service will stabilize on itsown following the restarting.

The Array Management servicemay restart unexpectedly whenthe array is under high workload.

Array ManagementService restarts un-expectedly underhigh load

System Manage-ment

AS-101420

Known Issues 52



Not applicableArray Management service mayrestart on a group configuredfor high availability during vari-ous scenarios such as whenGroup Leader to Backup GroupLeader communication is at highload or degraded. Scenarioswhich may cause an array man-agement service restart includedegraded or broken networkconnectivity between GL andBGL arrays.

Array managementservice may restarton Group Leader orBackup GroupLeader arrays

System Manage-ment

AS-105041

Not applicableIf communication betweenGroup Management and Post-gres services does not completewithin expected timeout, theGroup Management service mayrestart. The restart will resumethe communication and try thetransaction again.

Group Managementservice may restartdue to communica-tion timeout exceed-ed

System Manage-ment

AS-97327

Not applicableGroup Management service mayrestart due to health checktimeout exceeded. The servicewill recover after the restart.

Group ManagementService may restartunexpectedly

System Manage-ment

AS-97697

Not applicableThe Group Management Servicemay restart unexpectedly whenthe array is under heavy load,has many snapshots scheduled,has performed a group merge inthe past, and has recently per-formed an automatic GroupLeader Failover.

Group ManagementService restarts un-expectedly follow-ing automaticGroup LeaderFailover

System Manage-ment

AS-66341

Not applicableThe Group Management servicemay restart unexpectedly wheninternal database query doesnot complete within the expect-ed time out. The service restartsto clear the condition.

Group Managementservice may restartdue to internaldatabase timeout

System Manage-ment

AS-65676

Not applicableWhen a new internal databaseconnection is established, anumber of prepared_statementsare executed at the beginning.If one of the prepared_state-ments fails the Group Manage-ment Service will restart.

Group ManagementService may restartdue to internaldatabase handling

System Manage-ment

AS-108145

Known Issues 53



Disable automatic failover andremove witness from configura-tion.

After Group migration is per-formed, backup group leaderbecomes group leader. If witnessis disconnected for more thanfive minutes, the new leader willnot remove quorum.

After group leadermigration, quorumis not removed af-ter witness discon-nection

System Manage-ment

AS-98434

Not applicableWhile syncing the configchanges on the downstream ar-ray, group management servicemay restart due to a race condi-tion between protection policydeletion and adding the volumeto the protection policy.

Group managementservice may restartdue to race condi-tion

System Manage-ment

AS-106490

Not applicableGroup management service mayrestart due to the race conditionbetween branch creation for thereplica volume and replica vol-ume deletion. This race condi-tion will cause an assertion fail-ure and lead to Group Manage-ment service restart. This mayimpact management workflows.

Group managementservice may restartdue to assertionfailure

System Manage-ment

AS-113950

Not applicableInternal workflow processing re-lated to the replication partnerobject may cause the process todeadlock, resulting in Groupmanagement service restart.

Group managementservice may restartunexpectedly

System Manage-ment

AS-105064

Not applicableIn the data protection environ-ments, replication partners needto sync their configuration. Incertain situations, the partnerswill attempt to sync all volumecollections as opposed to justthe volume collections that wererecently modified. This may leadto unexpected delays is replica-tion partner sync.

Unexpected delaysin configurationsync between repli-cation partners

System Manage-ment

AS-115200

Not applicableIn the case where the down-stream array is reaching itssnapshot rate limit and the userperforms the volume collectionhandover, the handover will beabort if the limit is surpassed. Analert will be raised but the alertmessage may be missing thereason for aborting handover.

Alert for abortedhandover does notspecify reason

System Manage-ment

AS-98650

Known Issues 54



Not applicableIf a user performs multiple vol-ume collection handovers be-tween two arrays during a shorttime span, this may cause a situ-ation where both upstream anddownstream array may claimvolume collection ownership.This is due to a race conditionin the workflow.

Both upstream anddownstream mayclaim the volumecollection owner-ship when exces-sive handovers areperformed

System Manage-ment

AS-99520

Please reissue the command. Ifthe operation was already per-formed by the earlier command,an appropriate message will bereturned.

Under system busy conditions,when an excessive amount ofoperations are being issued inparallel or too many internal re-tries are occurring to performtasks, you may receive a Nomessage received error after is-suing a CLI command.

Error No messagereceived after issu-ing CLI commandto disassociate vol-ume from collection

System Manage-ment

AS-98378

Not applicableIn rare occurrences, the GroupManagement may restart whena race occurs between threadsthat are disassociating a volumefrom a volume collection andmodifying a schedule for thesame collection. The servicerestarts to recover.


System Manage-ment

AS-81209


Snapshots may display in GUI asreplicated snapshots when theyare not involved in replication.

Snapshots displayas replicated in GUIon array with noreplication config-ured

System Manage-ment

AS-73432

Not applicableThe group --list_limits CLI com-mand does not list the Syn-chronous Replication volumecount Limit. Synchronous Repli-cation on 5.1.0.0 and later canprotect up to 128 volumes.

Synchronous Repli-cation VolumeCount Limit

System Manage-ment

AS-89124

Not applicableIf two on-premise array groupsconfigured with a Nimble CloudVolumes (NCV) partner aremerged, the Cloud Volumereplication will stop working.

Cloud Volumesreplication does notsupport groupmerge

System Manage-ment

AS-88308

Known Issues 55



Not applicableA deadlock can occur betweentwo management processeswhen updating the replicationbandwidth throttle. The Manage-ment Process will restart andclear the condition. There is nodisruption to data services andreplication will continue automat-ically without intervention.

Group managementprocess my restartdue to a deadlockwhen replicating

System Manage-ment

AS-59470

Update the downstream arrayto NimbleOS 3.4.x or later.

Encrypted and deduped vol-umes cannot be replicated from3.4.x and later to previous 3.xreleases because they do notsupport encryption and dedupeat the same time. Note that thisdoes not affect replication from3.4.x and later to 2.3.x where thevolumes will not be deduped onthe downstream running 2.3.x.

Replication ofdedupe and en-crypted volumeswill stall between3.4 and previous3.x releases

System Manage-ment

AS-57574

Not applicableNimbleOS uses a defined statemachine for the replicationworkflow. At the end of the exe-cution of each step defined inthe state machine, it moves tothe next step. If it leads to anyunexpected step throughout theworkflow then it will lead to as-sertion failure which results inGroup Management servicerestart.

Group managementservice may restartdue to assertionfailure

System Manage-ment

AS-96143

Not applicableWhen the system has a highnumber of objects, the GroupManagement service may restartwhile running REST query or CLIcommand.

Group Managementservice may restartdue to high memo-ry usage

System Manage-ment

AS-96241

Update the downstream poolsDeduplication setting to matchthe upstream pool.

If the Default Deduplication set-ting differs for upstream anddownstream pools, the configu-ration of deduplication volumesfor replication might fail with thefollowing error Deduplicationnot allowed since no applicationcategory is assigned to the per-formance policy

Configuration ofdeduplication vol-umes for sync repli-cation might fail

System Manage-ment

AS-90649

Known Issues 56



Please reissue the command. Ifthe operation was already per-formed by the earlier command,an appropriate message will bereturned.

Under system busy conditions,when an excessive amount ofoperations are being issued inparallel or too many internal re-tries are occurring to performtasks, you may receive a Nomessage received error after is-suing a CLI command.

Error No messagereceived after issu-ing CLI commandto associate volumeto volume collec-tion

System Manage-ment

AS-90633

vol --list can be used to deter-mine pool/folder attributes ofthese volumes.

For the volcoll --info output forsync replication volume collec-tions, the Associated volumes:and Associated pinned volumes:fields lack pool/folder qualifica-tion for the associated volumes.

volcoll --info outputlacks pool/folderqualifications forassociated volumes

System Manage-ment

AS-90286

Not applicableThe Group Management servicemay restart due to a race condi-tion between threads when up-dating replication records inScale Out Database (SODB). Theservice restarts to clear the con-dition.

Group ManagementService may restartdue to race condi-tion

System Manage-ment

AS-49720


Arrays with volumes that havelarge branch structures maycause internal command process-ing timeout to be exceeded. Thiswill cause the Group Manage-ment service to restart due tohealth check failure.

Group managementservice may restartunexpectedly

System Manage-ment

AS-98155

Not applicableThe Group Management servicemay restart due to a race condi-tion between replication com-mands and group managementservice restart. The servicerestarts to recover from thecondition.

Group managementservice may restartdue to race condi-tion

System Manage-ment

AS-108119

Not applicableDuring shutdown of the groupmanagement process, the SSLlibrary logging of the debugmessages can cause a race con-dition, resulting in a segmenta-tion violation error. The servicerestarts to recover from thecondition.

Group Managementservice may restartduring processshutdown due torace condition

System Manage-ment

AS-114179

Known Issues 57



Not applicableDuring a planned array shut-down, the Group Managementservice may restart due a racecondition. There is no data ormanagement interruption sincethe service is already shuttingdown.

Group Managementservice restartsduring the arrayshutdown

System Manage-ment

AS-108765

Retry the command for thefailed volumes.

Due to a rare race condition, theGroup Management Service mayrestart unexpectedly during abulk volume update operation.

Group ManagementService restartsduring bulk volumeupdate

System Manage-ment

AS-95610

Please review the network andsee if there is a consistent pack-et loss and fix any networkglitches. If you need any assis-tance, please reach out to HPENimble Storage Support.

If the network response to aREST request takes more than5 minutes, a thread performingthe REST request times out andas a result Group ManagementService restarts. The servicestabilizes itself and as long asthe network is serving the re-quests faster. A single instanceof the Group Management ser-vice restart should not cause anydisruptions.

Group ManagementService restarts dueto packet loss innetwork

System Manage-ment

AS-91638

Confirm all Domain Controllersin the Active Directory environ-ment that is integrated with thearray are reachable.

In environments with an arrayintegrated with Active Directory,the create/validate session codeholds a lock on an underlyingsessions table and then goes toActive Directory to collect moreinformation about the user. Ifthis operation takes too long,the Group Management servicemay timeout to free this lock.

Group Managementservice may restartwhile collecting us-er information fromActive Directory

System Manage-ment

AS-108868

Ensure setup completes success-fully before attempting to discov-er volumes.

If a user runs --resetup followedby setup on an array that waspreviously configured and setupdoes not complete successfully,data IPs may be unconfigureduntil the setup actually com-pletes successfully. As a result,GDD may restart unexpectedlyif any attempts are made to dis-cover the volumes on those un-configured data IPs.

Discovering vol-umes after arrayresetup may causeGroup Data servicerestart

System Manage-ment

AS-66182

Known Issues 58



Not applicableDue to a race condition withsnapshot retention on a down-stream replication partner, theGroup Management service maycrash unexpectedly. The ProcessManagement service automati-cally restarts the Group Manage-ment service after the crash andit should resolve the race condi-tion.

Group Managementservice may restartdue to race condi-tion with snapshotretention on adownstream replica-tion partner

System Manage-ment

AS-117078

Not applicableThe Group Management per-forms queries on the informationstored in the Scale Out Database(SODB) for the array. If thequery does not complete withinthe expected timeframe, theservice may restart to recoverfrom the issue.

Group Managementservice may restartdue to internaldatabase timeout

System Manage-ment

AS-95868

Please refer to the System Lim-its and Timeout Values sectionin the NimbleOS AdministrationGuide.

The group --list_limits CLI com-mand does not list system limita-tion for writable snapshots. Also,no alerts or alarms are generat-ed as as the array group ap-proaches the limit.

System limitation ofwritable snapshotsis not reported byNimbleOS

System Manage-ment

AS-68782

Not applicableGroup Management service mayrestart due to memory exhaus-tion in configurations that ap-proach 10,000 volumes and300,000 snapshots.

Group Managementservice may restartdue to memory ex-haustion

System Manage-ment

AS-94517

Not applicableDue to a race condition, theGroup Management Service ona downstream group may restartwhile updating volume collec-tions from the upstream group.

Group ManagementService may restartdue to a race condi-tion

System Manage-ment

AS-105291

Not applicableIf clones are created using anunmanaged snapshot, then thisunmanaged snapshot will not bedeleted even if cleanup is en-abled.

Unmanaged snap-shots remain aftercleanup is enabled

System Manage-ment

AS-93113

Not applicableIf communication betweenGroup Management and Post-gres services does not completewithin expected timeout, theGroup Management service mayrestart. The restart will resumethe communication and try thetransaction again.

Group Managementservice may restartdue to communica-tion timeout exceed-ed

System Manage-ment

AS-97899

Known Issues 59



Refresh the HPE Nimble Storagearray GUI .

Multiple snapshot deletions canbe deleted in a single request.Back-to-back deletions of multi-ple batches of ten or moresnapshot collections may causethe HPE Nimble Storage arrayGUI interface to hang.

Frequent, multipleSnapshot Collectiondeletions causesGUI to hang

System Manage-ment

AS-65935

The TTL can be updated on thesnapshots which have a negativevalue to a current value. Thesnapshot may also be removedif it has been confirmed it is nolonger needed.

NimbleOS protects the lastreplicated collection, in somecases, the TTL expiry date onthose snapshots can becomenegative when the snapshotsexist beyond TTL.

Time to Live (TTL)expiry date on lastreplicated snap-shots can be nega-tive

System Manage-ment

AS-105944

Contact HPE Nimble StorageSupport to identify ACLs inforced-delete/create-retry state,verify these ACLs are associatedwith snapshots that no longerexist, and delete these ACLsfrom the internal NimbleOSdatabase.

In certain scenarios, a volumedeletion will not complete dueto the existence of a stale ACLassociated with it. This stale ACLis associated with a snapshot ofthe volume that was previouslydeleted. These volumes will notshow up in the CLI/GUI as theyare in a hidden state.

Deletion of a vol-ume is not complet-ed due to the pres-ence of stale ACLsassociated with it

System Manage-ment

AS-105432

Not applicableDuring planned service stop,such as array shutdown, theGroup Management service mayrestart due to a race condition.There is no data or managementinterruption since the service isalready shutting down.

Group Managementservice may restartduring array shut-down

System Manage-ment

AS-104965

Not applicableWhen internal threads encountera locking conflict, the GroupManagement service may restartto recover from the condition.

Group Managementservice may restartunexpectedly dueto a conflict with in-ternal threads

System Manage-ment

AS-62192

Known Issues 60



Not applicableAutomatic Failover demotion ofa Backup Group Leader arraymay be delayed for multipleminutes when an internaldatabase is performing weeklygarbage collection. The GroupLeader is not able to demote theBackup Group leader during aweekly window when an internaldatabase is performing internalgarbage collection. This may lastfor multiple minutes. EventuallyBackup Group Leader demotesucceeds, and a new BackupGroup Leader is selected. TheGroup loses High Availabilityduring this time and the GroupManagement service may restartto recover from the condition.

Automatic FailoverBackup GroupLeader demote maybe delayed in rarecircumstances

System Manage-ment

AS-113375

Scheduling snapshots to occurat different times instead of allat once may help alleviate thisissue.

Group Management service mayrestart on the array when thereis a high amount of snapshotactivity being performed. Theservice restart will recover fromthe condition and the snapshotoperations will resume.

Group Managementservice may restartunexpectedly whenperforming highsnapshot activity

System Manage-ment

AS-105804

Not applicableIn rare instances, the GroupManagement Service mayrestart unexpectedly when theGroup Leader and Member arrayhave lost connectivity due tonetwork outage. The servicerestart recovers GUI and CLI ac-cess, data services are not im-pacted by the restart.

Group ManagementService may restartunexpectedly dueto network connec-tivity

System Manage-ment

AS-103982

Not applicableAfter a controller restarts due toover temperature condition,System Management processesmay restart and take longer tostart up due to slow systemperformance.

System Processesor Systems maystart slowly afterover temperaturerestart

System Manage-ment

AS-115819

Known Issues 61



Not applicableArray Management service mayrestart on a group configuredfor high availability during vari-ous scenarios when GroupLeader to Backup Group Leadercommunication is high or degrad-ed. Scenarios which may causean array management servicerestart include degraded or lostnetwork connectivity betweenGL and BGL arrays.

Array managementservice may restartduring periods ofdegraded networkconnectivity be-tween Group Lead-er and BackupGroup Leader ar-rays.

System Manage-ment

AS-108378

Not applicableIf internal database processingfor array statistics exceeds theexpected timeout, the GroupManagement service will restartdue to health check failure torecover.


System Manage-ment

AS-98504

Please contact HPE NimbleStorage Support

When the array is powered onand off excessively, services mayfail to start on the array.

Services may notstart on the arrayafter it is poweredon and off severaltimes

System Manage-ment

AS-101392

Not applicableThe Group Management servicemay restart when service commu-nication for internal databaseprocessing is terminated. Theservice restarts to restore con-nections between the services.


System Manage-ment

AS-105453

Not applicableThe Array Management Servicerestarts unexpectedly followingautomatic Group Leader Failover(AFO). The restart is non-disrup-tive.

Array ManagementService restarts un-expectedly follow-ing automaticGroup LeaderFailover

System Manage-ment

AS-99615

Not applicableIn rare instances, the ProcessManagement service restart mayoccur during software update.The system recovers after therestart of the service.

Process Manage-ment service mayrestart during soft-ware upgrade

System Manage-ment

AS-95132

Known Issues 62



No workaround available. Toavoid encountering this issue,reduce IO load when performingsoftware update. Software Up-date will succeed after one ormore System Management ser-vice restarts.

The underlying scale-outdatabase competes with CASLand other system processes forIOPS. During software update, amigration script runs against thedatabase. Under heavy file sys-tem load, the migration stepsmay not complete within theexpected amount of time. As aresult, the migration may time-out leading to a restart of theGroup Data Service. After therestart, the migration shouldcomplete as normal without anyuser impact or intervention.

Group Data Servicemay restart whenthe array is underheavy load duringsoftware update

System Manage-ment

AS-110374

The alarms can be deleted man-ually either in the GUI or on theCLI.

After the update to 5.1.x.x orlater, the Snapshot limit warningalarm is no longer used. Thispresents a situation where stalealarms are present on the arrayand they will not be cleared evenif the space situation is rectified.The alarm follows the followingformat: WARNING Mon DDYYYY HH:MM:SS Acknowledged- Volume <volume name>snapshot space usage is overthe configured warning limit.

Snapshot limitwarning alarmspersist after updateto 5.1.x.x or later

System Manage-ment

AS-98694

Confirm the usage level for vol-ume or pool indicated by thealarm is below threshold. Onceconfirmed usage level is belowthreshold, clear the alarm fromthe Command Line Interface(CLI): 1. List the alarms to findthe alert ID alarm --list 2. Deletethe alarm that is no longer validalarm --delete

Alarms are generated on the ar-ray when volume or pools ex-ceed thresholds. In some in-stances the recovery event toclear the alarm when the condi-tion is cleared does not clear thealarm.

Alarm not clearedafter volume orpool drops belowwarning threshold

System Manage-ment

AS-77045

Not applicableInfrequently the Group Manage-ment service may encounter anerror while shutting down. If theservice is being restarted it maytake a few more seconds tostart. GUI and CLI will be unavail-able for a few seconds.

Group Managementservice may be-come unavailablewhen shut down

System Manage-ment

AS-110123

Known Issues 63



Not applicableHigh concurrent REST volumereads with statistics may causeGroup Management service torestart. Current REST requestswill fail, GUI and CLI will be un-available. The system will recov-er after the restart of the service.

Group managementservice may restartwhen there aremany REST re-quests for volumestatistics values

System Manage-ment

AS-108432

The ASO checkbox is enabledby default, however ASO is notenabled until a witness has beenconfigured. In the GUI, navigateto Administration > Availabil-ity. If witness is configured andthe ASO check box is checked,disable ASO by unchecking thebox and clicking save. Performthe array software update again.If the update continues to failwith generic messaging, contactHPE Nimble Support.

Software updates to 5.1.4.200are not allowed when AutomaticSwitchover (ASO) is configured.If a software update to 5.1.4.200fails for this reason, a genericsoftware update failure messageis returned in the GUI. The causeof the failure would need to bedetermined by looking at thesystem configuration and deter-mining if ASO is configured.

Arrays with Auto-matic Switchoverenabled fail soft-ware update withgeneric message

System Manage-ment

AS-106848

This is an intermittent issue, soif the software update fails inthis manner it should pass if thesoftware update is resumed.

The timing is close enough thatit is possible for the individualarray precheck during softwareupdate to take long enough thatthe health check timeout is trig-gered, causing the group man-agement process to restart andthe software update to fail.

Health check time-out may cause soft-ware update failure

System Manage-ment

AS-66997

Not applicableGroup management service mayrestart during software updatedue to race condition involvingunlocking the download lock file.

Group managementservice may restartduring software up-date

System Manage-ment

AS-72559

Initiate the software updateagain and answer the EULAprompt and the software updatewill proceed as expected.

When a software update is initi-ated on the array and theprompt for EULA acceptance isnot answered, the software up-date session will timeout afterseveral hours with a messageindicating Requires Authentica-tion or Contact HPE NimbleStorage Support.

Software update in-activity timeoutmessaging

System Manage-ment

AS-54519

Known Issues 64



If a timeout occurs, the updatecan be completed using thesoftware --resume_update com-mand.

Due to the number of firmwareupdates involved, software up-date going from pre-3.3.x ver-sions to 3.3.x or later could taketoo long and eventually timeout.These update times may takelonger in larger multi-arraygroup configurations. Softwareupdate in smaller array groupsshould complete without inter-vention.

Updating arraygroups from earlierNimbleOS 3.x re-leases to 3.3.x orlater releases couldtimeout

System Manage-ment

AS-57173

Running the software --re-sume_update command from theconsole will clear this condition.

Under rare conditions, a soft-ware update may report an erroreven though the actual updatehas completed successfully. Thisoccurs when software updatetakes longer than 4 hours.

Timeouts duringsoftware update

System Manage-ment

AS-40516

Ignore the error message andretry the management operation

While the volume ownership isbeing changed, any manage-ment operation involving thatvolume could fail. This is expect-ed behavior. Depending on theprogress of that handover oper-ation, management operation isfailing with different errors.

Volume manage-ment operationsmay fail with unre-lated error mes-sages while han-dover is in-progress

System Manage-ment

AS-91962

Not applicableThe Group Management servicemay restart when internaldatabase processing exceedsthe expected timeout value. Theservice restarts to recover fromthe condition.

Group Managementservice may restartdue to health checktimeout

System Manage-ment

AS-109805

Confirm all Domain Controllersin the Active Directory environ-ment that is integrated with thearray are reachable.

In environments with an arrayintegrated with Active Directory,the create/validate session codeholds a lock on an underlyingsessions table and then goes toActive Directory to collect moreinformation about the user. Ifthis operation takes too long,the Group Management servicemay timeout to free this lock.

Group Man-agement servicemay restart whilecollecting user infor-mation from ActiveDirectory

System Manage-ment

AS-113885

Not applicableThe Group Management servicemay restart when user lookup isin process and the winbinddservice does not respond withinthe expected timeframe. Theservice restarts to recover fromthe condition.

Group Managementservice may restartdue to healthchecktimeout

System Manage-ment

AS-115002

Known Issues 65



Add the computer account cre-dentials for the array by addingit to the RODCs password repli-cation policy (PRP) under theAllowed RODC Password Repli-cation Group group.

Array authentication to an Ac-tive Directory Read-Only Do-main Controller (RODC) may fail,resulting in failures to authenti-cate Active Directory users.

Active Directoryauthentication mayfail with Read-OnlyDomain Controller(RODC)

System Manage-ment

AS-107491

Not applicableActive Directory Authenticationcauses the arrays Group manage-ment service to wait for a re-sponse from the Active Directo-ry. If this response is delayed,the Group Management Servicemay restart unexpectedly.

Active Directoryauthentication insome cases, maylead to a GroupManagement ser-vice restart

System Manage-ment

AS-104512

As a local admin on the array,restart the Active Directory inte-gration service by disabling andenabling the integration. Via theGUI: Navigate to Administration-> Security -> MicrosoftActive Directory Click DisableClick Enable Via the CLI: user-auth --disable <domain>userauth --enable <do-main>

The expected configuration isntloaded when the Active Directo-ry integration service starts,leading to failed logins or incon-sistent Active Directory connec-tivity in certain configurations.

Active Directoryconnection failures

System Manage-ment

AS-111166

Not applicableThe Group Management servicevalidates session information inthe Scale Out Database. If thevalidation exceeds the expectedtimeout, the service will restartto recover.

Group ManagementService may restartdue to internaldatabase handling

System Manage-ment

AS-72869

Not applicableIf collection of user group infor-mation from Active Directorytakes longer than expected, theGroup Management servicetimeout may be exceeded. Theservice will restart to resume in-formation collection.

Group Managementservice may restartwhile collecting us-er information fromActive Directory

System Manage-ment

AS-69084

Known Issues 66



Not applicableWhen the HPE Nimble Storagearray is configured to use ActiveDirectory integration, the arrayis joined to one specific domain,as a domain member. Undernormal circumstances, users intrusted domains will also be ableto authenticate to the array. Ifone or more trusted domains arejoined to the forest using an MITKerberos type trust relationship,users and groups in any trusteddomain (e.g. not the domain thearray is joined to) will be unableto authenticate to the array.

HPE Nimble Stor-age array compati-bility issues withMIT Kerberos trusttypes

System Manage-ment

AS-95212


In rare instances, if the array isunder heavy load and GroupManagement service restartswhile new user is being created,the service can fail to start.

Group Managementservice may crashwhile trying to cre-ate users while ar-ray is under heavyload

System Manage-ment

AS-105035

Not applicableThe Group Management Servicemay restart unexpectedly if ittakes longer than 300 secondsto authenticate an Active Direc-tory (AD) user.

Group ManagementService restartswhile authenticat-ing AD users

System Manage-ment

AS-71137

Not applicableCommand to join AD may failbecause of latency in gettingback a response from AD server.This may cause a health checkfailure for Group Managementcausing the restart of the serviceto recover.

Command to joinActive Directory(AD) may fail caus-ing Group Manage-ment serviceRestart

System Manage-ment

AS-66437

Not applicableWhen joining Active Directoryvia GUI or userauth command inCLI, the command is expectedto complete within 300 seconds.If this timeout is exceeded dur-ing the process, the Group Man-agement service will restart torecover.

Group Managementservice may restartwhen joining arrayto Active Directory

System Manage-ment

AS-74830

Not applicableAD communication may be slowleading to a delay in responsesthat may cause Group Manage-ment service to crash. Leavingthe AD domain requires interac-tion with AD wherein this delaycan cause a restart.

Latency in commu-nicating with Activedirectory duringmay cause GroupManagement ser-vice to restart

System Manage-ment

AS-78946

Known Issues 67



Resolve any connectivity issuesbetween the array and ActiveDirectory Domain Controller(s)to avoid unexpected servicerestarts.

If there are connectivity issuesbetween an array with ActiveDirectory integration enabledand an Active Directory DomainController, then the responsesmay take more than 300 sec-onds and timeout. As a result,the Group Management servicemay restart.

Active Directoryconnectivity issuemay result in GroupManagement ser-vice restart.

System Manage-ment

AS-65654

Not applicableDuring extremely rare circum-stances, a bug may cause GroupManagement Services to restartwhile deleting a user. The arraywill recover after Group Manage-ment completes its restart.

Group managementservices mayrestart

System Manage-ment

AS-114105

Not applicableWhen logging in with a Activedirectory (AD) user, delayed re-sponses from AD may lead toGroup Management servicerestart.

Group Managementservice may restartdue to Active direc-tory communicationtaking too long.

System Manage-ment

AS-109549

The Group Management Servicewill eventually restart itself

Enabling and disabling thededupe setting on volumes andconcurrently deleting volumescan cause the Group Manage-ment Services to become tem-porarily unavailable on the array.

Group ManagementService is temporar-ily unavailable afterdeleting volumes

System Manage-ment

AS-101535

Delete unused clones or volumesto bring down the volume count.

Following operations will failupon reaching the volume limit:-adding Synchronous replicationschedule to a volume collection -associating a volume toa volume collection with Syn-chronous Replication enabled -editing a Volume Collectionschedule to add SynchronousReplication partner

Enabling syn-chronous replica-tion fails uponreaching volumelimit

System Manage-ment

AS-102893

Please contact HPE NimbleStorage Support to update thecompression algorithms of theseolder volumes.

After updating to NimbleOS 4.x,volumes initially created whenan array was running NimbleOS1.3.x and earlier may experiencea negative impact on perfor-mance. This is caused by soft-ware changes made to the com-pression algorithm used bythese older volumes.

Performance issuesfor volumes createdwhen array wasrunning NimbleOSversions 1.3.x andearlier

System Manage-ment

AS-84276

Known Issues 68



Once the array is able to deter-mine its deduplication capability,all newly created volumes willhave dedupe enabled, if speci-fied. In order to enable dedupeon the previously created vol-umes, you may run the followingcommand via the HPE NimbleStorage Array CLI: vol --edit<vol_name> --dedupe_en-abled yes

After a CSx000 array is installed,it takes one minute for the arrayto determine its deduplicationcapability. If a volume is createdprior to this, it will not havededupe enabled even if the ar-ray is dedupe capable.

Unable to creatededupe enabledvolumes on a newinstall

System Manage-ment

AS-86545

Not applicableCurrently, there is no CLI sup-port for changing the witnessport. The nimble-witnessd.ser-vice file needs to be editedmanually.

No CLI support forchanging the Wit-ness Port

System Manage-ment

AS-92157

Not applicableA member array might not belisted under the Add Array toGroup option within the GUI ifthe member is configured witha different protocol (iSCSI vs Fi-bre Channel). Also when thereare multiple arrays in the subnet,arrays which cant be discoveredwithin the stipulated time maynot be listed in Add Array toGroup.

Member arraymight not be dis-played under AddArray to Group op-tion

System Manage-ment

AS-100067

Not applicableIn rare instances, the Group Dataservice may restart duringstartup due to a misconfigura-tion in NimbleOS pertaining toa file descriptor limit.

Group Data servicemay restart onstartup

System Manage-ment

AS-107015

Not applicableIn rare circumstances, followingan Automatic Failover (AFO) arace condition may cause theArray Management Service torestart or an unexpected con-troller takeover.

Array ManagementService restarts orTakeover occursunexpectedly fol-lowing automaticGroup LeaderFailover

System Manage-ment

AS-99431

Not applicableWithin the HPE Nimble Storagearray GUI, custom SSL certificateimport is only supported onGoogle Chrome version 71 orlater.

Custom SSL certifi-cate import notsupported on olderversions of GoogleChrome

System Manage-ment

AS-99343

Known Issues 69



To keep the same reminder fre-quency and reset the next re-minder time based on the cur-rent time, change the reminderfrequency to a different value,save it, and change it back andsave it, or use CLI to make thechange.

When updating an alarm fromthe Events > Alarms page inGUI, selecting an alarm andclicking CHANGE REMINDERbutton, without changing thereminder frequency time, andclicking SAVE button, does notchange next reminder time. Thisbehavior is different from CLI.Setting alarm reminder frequen-cy to the same value from CLIresets the next reminder timebased on the current time.

Setting alarm re-minder frequencyto the same valuefrom GUI does notchange next re-minder time

System Manage-ment

AS-98177

When the controller is back up,all the information is displayedcorrectly on hardware page.

When a controller is down, theuser may see incorrect represen-tation of physical ports withinthe Hardware Page of the arrayGUI. This is due to the lack ofinformation from the missingcontroller.

Incorrect informa-tion on hardwarepage displayedwhen controller isdown

System Manage-ment

AS-87701

Use Google Chrome or MozillaFirefox browser.

The Array GUI incorrectly re-turns an error when a valid valuefor the folder overdraft limit hasbeen entered. This happens onlyin Internet Explorer and Mi-crosoft Edge browsers.

GUI Error when en-tering a valid folderoverdraft limit val-ue

System Manage-ment

AS-102299

Not applicableDuring group merge, the GUImight show Successful messageeven though the group mergebackend processing fails.

GUI may show Suc-cessful messagewhen group mergefails

System Manage-ment

AS-87886

To work around this issue: 1.Log into the destination arrayto resolve the conflicts. 2. At-tempt the group merge again.

Currently within the HPE NimbleStorage Array GUI, when per-forming a group merge, if thereis a large amount of groupmerge conflicts (1000 or more),the GUI is unable to process andresolve all of them.

Group Merge viaGUI unable to pro-cess large amountof conflicts

System Manage-ment

AS-77372

Please contact HPE NimbleStorage Support.

When adding a Fibre Channel(FC) array to an existing group,you are unable to change themgmt subnet to Mgmt + Data.You will see the following error:Data subnet Management<SUBNET> must allowgroup traffic

Unable to assigngroup traffic to Fi-bre Channel arraywhen joining arraygroup

System Manage-ment

AS-76896

Known Issues 70



Not applicablePool merge is not allowed ifSynchronous Replication is en-abled and pool merge is not al-lowed when a witness config-ured. If an array group has awitness configured for Automat-ic Switchover and has Syn-chronous Replication configured,when a user tries to perform apool merge, the following erroris generated: “pool merge is notallowed when witness is config-ured”. In this case, if the user re-moves the witness and then re-attempts the pool merge, thefollowing error is then generat-ed: “Pool merge is not allowedwhen involved in sync replica-tion”. This error should super-sede the previous error.

Incorrect orderingof pool merge errormessages whenSynchronous Repli-cation and Witnessare configured

System Manage-ment

AS-95591

Edit the pool name and assign /un-assign the array a in separatesteps.

When attempting to edit a stor-age pool and assign an array atthe same time, you receive thefollowing error: Cannot updatearray list and name or descrip-tion simultaneously.

Unable to edit astorage pool andassign an array atthe same time

System Manage-ment

AS-94575

Fix the name conflict on thedownstream array.

When associating multiple vol-umes to a volume collectionfrom, the volume association forall volumes can fail due to aname conflict for one of the vol-umes on the downstream.

Volume collectionassociation for avolume can fail dueto a name conflicton the downstreamarray

System Manage-ment

AS-104099

Run the following command viaCLI: snap --list --all --unmanaged

The Array GUI does not specifywhich snapshots are unmanagedand no longer belong to a vol-ume collection.

Array GUI does notspecify which snap-shots are unman-aged

System Manage-ment

AS-93157

Click the dropdown arrow andselect a location from the pooland folder navigation tree.

In the Create Replication Partnerwizard, the Inbound Location isno longer automatically populat-ed.

In the Create Repli-cation Partner wiz-ard the inbound lo-cation is no longerautomatically popu-lated

System Manage-ment

AS-67289

Known Issues 71



After a new custom certificatehas been imported or existingcertificate is deleted, pleaseclose the browser where the ac-tion was performed and reopena new one to guarantee a newconnection request to the Nim-bleOS web interface.

After changing a certificate, theGUI may present an error suchas follows: The web service isvery slow or unreachable...

Browser becomesunstable upon cer-tificate change

System Manage-ment

AS-99024

The values should report correct-ly within 24 hours after the up-date has completed.

The volume performance num-bers displayed in the GUI underManage > Data Storage >Volumes > Performance Tabmay display invalid values tem-porarily after an array softwareupdate.

Volume perfor-mance numbersmay report invalidvalues after soft-ware update

System Manage-ment

AS-92634

Not applicableWhen the Group Leader at-tempts to complete the BackupGroup Leader promotion, if thereis not a healthy data path, theBackup Group Leader promotionfails. Despite, the network error,the Backup Group Leader promo-tion goes into a loop and ulti-mately leads to an unexpectedrestart of the Array Manage-ment Service.

Array ManagementService restartswhen Group Leadercannot reach Back-up Group Leader

System InternalsAS-104567

There is no workaround. Toavoid encountering this issue,reduce IO load when performingsoftware update.

The underlying scale-outdatabase competes with CASLand other system processes forIOPS. During software update, amigration script runs against thedatabase. Under heavy file sys-tem load, the migration stepsmay not complete within theexpected amount of time. As aresult, the migration may time-out leading to a restart of theGroup Data Service. After therestart, the migration shouldeventually complete as normalwithout any user impact or inter-vention.

Group Data Servicemay restart whenthe array is underheavy load duringsoftware update


Not applicableThe File System service mayrestart during array shutdown ifit exceeds expected time toshutdown. The service restartsto clear the condition.

File System servicemay restart duringarray shutdown


Known Issues 72



Not applicableDue to a race condition, the DataService may crash during arrayshutdown. Once the array startsagain, all operations resume asnormal.

Data Service maycrash during arrayshutdown


Not applicableDue to a race condition, the DataService can crash during agraceful shutdown causing unex-pected Data Services restartmessages to be generated. Thisshould not cause any I/O impactbecause the Data Service is al-ready in the process of shuttingdown.

Data Service canrestart unexpected-ly during shutdownprocess


Please contact Nimble StorageSupport to increase the scratchpage pool size.

Under unique customer work-loads, the index footprint mayexhaust default scratch page al-location in memory. As a result,the Data Service may restartunexpectedly.

Data Service mayrestart when thearray runs out ofscratch pages


Known Issues 73

Date post:	07-Mar-2021
Category:	Documents
Upload:	others
View:	10 times
Download:	0 times