NimbleOS 5.2.1.200 Release Notes - Hewlett Packard Enterprise...Note Description An extended data...

NimbleOS 5.2.1.200 ReleaseNotes

Version 5.2.1.200

Published July, 2020

Legal Notices

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

Notices

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

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

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

Acknowledgments

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

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

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

UNIX® is a registered trademark of The Open Group.

Publication Date

Wednesday July 22, 2020 18:06:55

Document ID

lji1593466899337

Support

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

Email: https://infosight.hpe.com

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

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

Legal Notices

https://infosight.hpe.com


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

Contents

NimbleOS 5.2.1.200......................................................................................4Important Update Note.........................................................................................................................4

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

New Features in 5.2.1.200...................................................................................................................8

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

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

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

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

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

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

Known Issues.....................................................................................................................................24

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

Nimble

NimbleOS 5.2.1.200

5.2.1.200Version:

Wednesday July 22, 2020 18:06:55Revision:

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

For technical support, contact HPE Nimble Storage Support at:

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

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

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

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

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

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

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

Special Notes

DescriptionNote

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

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

CRITICAL

Arrays must be running NimbleOS 5.0.4.0 or later to update directly toNimbleOS 5.2.1.200.

CRITICAL


NimbleOS 5.2.1.200 Important Update Note

mailto:[email protected]




DescriptionNote

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

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

CRITICAL

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

CRITICAL

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

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

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

CRITICAL

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

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

CRITICAL

As outlined in the current Validated Configuration Matrix, HPE NimbleStorage fully supports Windows guest operating systems on MicrosoftHyper-V, including Virtual Fibre Channel (VFC) connectivity and multi-pathing with HPE Nimble Storage DSM and VSS support. However,Linux guest operating systems running in Hyper-V VFC configurationsare not qualified.

Running Red Hat Linux guest operating systems with the “Linux Integra-tion Services” kit installed, or with hv_storvsc drivers in such configura-tions can lead to Red Hat bug 1364282, which can cause an unexpectedservice outage.

CRITICAL

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

Important

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

Important

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

Important


NimbleOS 5.2.1.200 Special Notes

DescriptionNote

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

Important

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

Then perform the following calculation:

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

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

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

Important

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

Important

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


Important




DescriptionNote

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

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

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

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

• In the Windows event viewer:

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

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

NWT 7.0.1 resolves this issue.

Important

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

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

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

Important



DescriptionNote

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

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

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

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

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

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

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

Important

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

A vVol VM can be protected and may be subsequently replicated to adownstream array (as configured in the storage policy). In the casewhere this vVol VM is deleted, a supported “claim” workflow allows usto claim this vVol VM on the downstream array. This workflow is notsupported at present if performed on a setup where the vCenter versionis 6.5 or above due to validation failures on the vCenter.

VMware DCPN Ticket Reference:

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

Important

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

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) and the integrity of the software download.

Fibre Channel Target Driven Zoning


NimbleOS 5.2.1.200 New Features in 5.2.1.200



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


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

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


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

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

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

Support for 10,000 Volumes on AF40 Arrays

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

Storage Class Memory

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

Synchronous Replication: Witness OVA

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

dHCI Unified Update

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

dHCI Server Configuration Limits

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

dHCI Support for Intel and AMD Processors

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

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


NimbleOS 5.2.1.200 Recent Release Features


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


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

Document Search Interface

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

The Nimble Storage Documentation page provides a search interface that allows you to search for informationacross all documentation, including support and knowledge base articles, best practices, solutions andintegration guides, product documentation, and configuration matrices.

To go directly to a document, use the navigation pane on the left side of the Nimble Storage Documentationpage. The navigation pane organizes documents into categories, including:

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

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

Third-Party Software Notices

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

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

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

2 From the menu, select Resources Nimble Documentation .

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

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

Core User Documentation

The following is the core user documentation for NimbleOS:

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

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

Workflow Documents

There are several workflow guides that contain procedures you can perform using either the CLI or the GUI.Each workflow guide covers a specific, frequently performed task related to HPE Nimble Storage products.


NimbleOS 5.2.1.200 Documentation


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

Hardware

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

Host Integration Guides

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

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

Verified Update Paths

Table 1: From Versions 5.x

From Versions 5.x

To VersionFrom Version

5.2.1.2005.2.1.100

5.2.1.2005.2.1.0

5.2.1.2005.1.4.200

5.2.1.2005.1.4.100

5.2.1.2005.1.4.0

5.2.1.2005.1.3.100

5.2.1.2005.1.3.0

5.2.1.2005.1.2.100

5.2.1.2005.1.2.0

5.2.1.2005.1.1.0

5.2.1.2005.0.10.0

5.2.1.2005.0.9.100

5.2.1.2005.0.9.0

5.2.1.2005.0.8.100

5.2.1.2005.0.8.0

5.2.1.2005.0.7.300

5.2.1.2005.0.7.200

5.2.1.2005.0.7.100

5.2.1.2005.0.7.0


NimbleOS 5.2.1.200 Verified Update Paths

From Versions 5.x


5.2.1.2005.0.6.0

5.2.1.2005.0.5.300

5.2.1.2005.0.5.200

5.2.1.2005.0.5.0

5.2.1.2005.0.4.0

5.0.10.05.0.3.100

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

5.1.4.2004.5.5.0

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



From 3.x Versions


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

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



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


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

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

WorkaroundDescriptionTitleComponentID

Not applicableAfter updating to NimbleOS5.0.x, the Data Service mayrestart if the array is runninglow on memory. This iscaused by changes madein 5.0.x to in-memorycaching.

Data Servicemay restartwhen array islow on memory

Data ServiceAS-104569


NimbleOS 5.2.1.200 Known Critical Issues



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

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

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


Contact HPE Nimble Stor-age Support

Arrays that support dedupli-cation with large dedupedomains may encounterData Service restart. Thecause of the restart is dueto incorrect handling of theFingerprint Index Hash Ta-ble.

Data Servicemay restartwhen assert inFingerprint IndexHash Table isencountered


Not applicableVolume moves transfer datafrom one Nimble array toanother. During this move,if the host sends I/O to theincorrect array, the I/Oneeds to be forwarded tothe correct array owning thedata. This results in higherthan usual I/O latency. Toavoid this issue in VMwareenvironments, the NimbleConnection Manager forVMware needs to be in-stalled on all hosts access-ing the volume.

Volume movemay result in la-tency if NimbleConnectionManager is notinstalled



When the Data Service de-tects a metadata inconsis-tency, the service mayrestart repeatedly and hostscould experience unexpect-ed application behavior.

Data Servicerestarts whendetecting meta-data inconsisten-cy


Contact HPE Nimble Stor-age Support.

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

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






Not applicableWhile committing internaltransactions, Data Servicemay hit a rare race condi-tion. To recover from thisData Service might restart

Data servicemay restart dueto a race condi-tion


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

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


Not applicableA disruption in networkconnections can cause Da-ta Service to restart unex-pectedly.

Data Servicemay unexpected-ly restart


Not applicable, on restartData Service would behavenormally.

Generation delete opera-tions and NVRAM to diskdata flush operation cancause Data Service torestart due to health checkfailure, as it can holdcheckpoint for a long time.

Data Servicemay restart dueto volume man-ager healthcheck failure


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

Pool merge failsdue to too manypending deletes







During data block allocationstatus application program-ming interface (API) execu-tion the file system servicemay restart. This happenswhen data block allocationstart offset is chunk-size-bytes aligned but data blockallocation end offset is notaligned with chunk-size-bytes.

File system ser-vice may restartunexpectedlyduring datablock allocationstatus API execu-tion


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

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



Counters used for spaceaccounting may cause vali-dation to fail. The array maysee a blip in space usagebecause of which writesmay be denied and in worstcase, volume may go of-fline.

Writes may bedenied due tocounters inspace account-ing


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

Delay for firstvVol datastorebecoming acces-sible

Host IntegrationAS-100561





Not applicableThe Data Service on thearray may restart whentimeout for internal commu-nication between arraycontrollers has been exceed-ed. The service restarts torestore the communication.

Data Servicemay restart dueto health checkfailure

PlatformAS-104517

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

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

Controller sen-sors missing forAFxx/HFxx ar-rays

PlatformAS-86764


HPE Nimble Storage hasidentified a rare firmwaredefect in a subset of driveswhich can, under certainwrite intensive workloads,cause the array to under-perform.

Performance af-fecting firmwaredefect in a sub-set of 6TBdrives.

PlatformAS-94961

This issue has been con-firmed as cosmetic. To re-solve this issues, you mayreboot the controller(s) re-porting the illuminated overtemp LED. Please contactHPE Nimble Storage Sup-port if further assistance isneeded.

After performing a softwareupdate to NimbleOS 5.0.x,the over temperature LEDis illuminated on the arrayfront LED panel. However,no alerts are triggered fromthe array software.

Red overtempLED is illuminat-ed after Nim-bleOS softwareupdate to 5.0.x

PlatformAS-76520

Not applicableIn multi-port network cards,the interfaces are initializedstarting with the interfaceclosest to the PCI slot, andending with the interfacefurthest away from the PCIslot. The 4-port 10Gbpstwisted pair NIC used in theHPE NimbleStorage arrayinitializes the ports in re-verse order, causing the ar-ray GUI and physical label-ing to show them in thewrong order.

Array GUI andCLI show quadport 10 GBTwisted Pair NICports in reverseorder

PlatformAS-87507





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

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

PlatformAS-86099

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

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

Plugin: Cannotadd 4 or moreservers in thedHCI deploy-ment

Not applicableAS-104924


In a configuration whereESX hosts connect to peerpersistence arrays usingiSCSI, during BGL con-troller failover, ESX hostsmay temporarily lose ac-cess to peer persistencevolumes, causing virtualmachine to become unre-sponsive and restart of ESXhosts and virtual machinesis needed to bring themback up.

VMWare virtualmachine maybecome unre-sponsive duringBackup GroupLeader (BGL)controllerfailover

SANAS-109904

Please contact HPE NimbleStorage Support

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

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

System Manage-ment

AS-107367





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

AutomaticSwitchover Ser-vice restarts dueto thread limita-tions

System Manage-ment

AS-89701

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

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

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

System Manage-ment

AS-65615

Not applicableGroup Management servicemay restart when internalprocessing fails on arrayswith high snapshot activity.This may cause snapshotsto fail to be deleted.

Group Manage-ment servicemay restart unex-pectedly

System Manage-ment

AS-94594

Please contact HPE NimbleStorage Support.

When there are networkcommunication issues be-tween the Group Leaderand Backup Group Leader,the system goes into anout-of-sync condition. Inrare circumstances, evenafter network connection isrestored, the array groupmay still remain out-of-sync.

Array group re-mains out-of-sync followingnetwork recov-ery.

System Manage-ment

AS-106276

Not applicableThe Group Managementservice may restart duringan array shutdown whileprocessing REST request.No user operations are im-pacted because the array isalready in the middle of ashutdown. The shutdownproceeds normally.

Group Manage-ment servicemay restart dur-ing array shut-down

System Manage-ment

AS-61614





Use unique name whencreating snapshot collec-tion.

If an attempt is made tocreate a snapshot collectionwith same the name of anexisting snapshot collection,an error indicating objectalready exists will be report-ed and the Group Manage-ment service may restart.The service will recover up-on restart.

Group Manage-ment servicemay restart dueto duplicatesnapshot collec-tion name

System Manage-ment

AS-94113

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

Group Manage-ment Servicerestarts underheavy load

System Manage-ment

AS-100254

Not applicableThe Array Managementservice may restart due toa race condition encoun-tered during service shut-down. The service will recov-er after the restart.

Array Manage-ment servicerestart duringservice shut-down

System Manage-ment

AS-98124

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

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

Softwareprecheck fail-ures returngeneric errormessage

System Manage-ment

AS-87736

Not applicableThere is a possibility ofsporadic, transient, activedirectory authentication fail-ures. In these cases, thesystem will recover on itsown, requiring no user inter-action.

Intermittent loginfailures due toActive directorylookups failures

System Manage-ment

AS-92465

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

Graceful shut-down takeslonger than ex-pected

System Manage-ment

AS-95169





There is no workaround forthis issue. Controllerfailover will maintain dataavailability.

The arrays Data Servicemay restart under certainconditions in order to main-tain data availability. Insome cases, the restart ofthis process takes longerthan expected, resulting inan unexpected timeout anda controller failover. Thecontroller experiencing thetimeout will reboot and be-come the standby con-troller. This event is non-disruptive.

Controllerfailover may betriggered by de-layed shutdownof an internal ar-ray process

System Manage-ment

AS-105612

Use volume collections tocheck syncRep volumes, oruse other filters to meet theneeds

There is currently no way tofilter volumes using Syn-chronous Replication withinthe array GUI.

Unable to Filtervolumes usingSynchronousReplication

System Manage-ment

AS-92379

Refresh the page to restorebutton functionality.

After performing a bulk up-date operation from theManage > Data Storage> Volumes > volume-name > Data Protectiontab in the GUI, the pagefooter may not update andprevious button may be un-available.

Page footer inGUI may fail toupdate after bulkupdate operation

System Manage-ment

AS-97968

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

Data Servicecan restart unex-pectedly duringshutdown pro-cess

System InternalsAS-69561



Resolved Critical Issues

Resolved Critical Issues in NimbleOS version 5.2.1.200


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

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

System Manage-ment

AS-109126

Resolved Issues

Resolved Issues in NimbleOS version 5.2.1.200


Before an interface is instate, gracefully removeVLAN tagging from theQuad Port interface. Afteran interface is in state, per-form controller failover torecover the condition. How-ever, with VLAN tagging stillenabled, subsequent eventscan occur. Therefore, con-sider the aforementionedworkaround to minimizechance of a re-occurrence.

When a subnet on the arrayis configured to use VLANtagging, Quad Port inter-faces in that subnet maybecome unresponsive. Asa result, hosts connected toan unresponsive interface,on that VLAN, may experi-ence communication inter-ruption. Over time, thiscondition may occur on ev-ery interface within thatsubnet, causing instabilitywith that subnet.

Interfaces onQuad Port10GbE BaseTand 10GbE SFPcards usingVLAN taggingmay become un-responsive

PlatformAS-109163

Not applicableDue to a NimbleOS soft-ware defect, invalid LUN in-formation response for LUIDs greater than 255 pre-vents connection for HP-UXhosts.

HP-UX cannotaccess nimblevolume ifmapped LU ID isgreater than 255

SANAS-109019


NimbleOS 5.2.1.200 Resolved Critical Issues

Known Issues

Known Issues in NimbleOS version 5.2.1.200


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

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

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


Not applicableIn rare instances, the DataService may restart wheninternal database communi-cation between services isnot available. The servicerestarts to restore the com-munication between ser-vices.

Data Servicemay restart unex-pectedly due tointernaldatabase com-munication


Data service will be avail-able after restart.

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

Data ServiceRestart due to arace conditionduring metadatasync


Not applicableAfter software update, dur-ing a dedupe domain up-grade, there is a chance ofprocess thread deadlockcausing the service torestart. Upgrade is a onetime process so it would re-sult in a single Data Servicerestart.

Data Servicemay restart dur-ing Dedupe Do-main Upgrade


Not Applicable, the DataService will resume normaloperation after restart.

Generation delete loads alarge number of ondiskmetadata blocks which mayprevent block index opera-tion checkpoint from finish-ing. This causes the volumemanager health check to failwhich results in Data Ser-vice restart.

Data Servicemay restart dueto volume man-ager healthcheck failureduring genera-tion deletion



NimbleOS 5.2.1.200 Known Issues



Not applicableWhen a read op finds partialdata in-core, it issues amedia read to get remainingdata. By the time, mediaread returns, the in-coredata is synced, and tree isreopened for deletion. Theread does not expect treeto be in delete state andcauses the Data Service torestart.

Data Servicemay restart unex-pectedly due torace condition


Contact Nimble StorageSupport.

When flash cache GarbageCollection copies forwardlive data of a fragmentedsegment, it could consumemore buffers than provi-sioned and cause the DataService to restart to recov-er.

Data Servicemay restartwhen runningout of buffers


Not applicable.Due to issues in communi-cating with the partner arrayduring replication, there arefew cases where the opera-tion is not able to makeprogress. As a result, thefile system may restart tocorrect this condition.

File systemrestart to recov-er from stalledreplication


Not applicableWhile committing internaltransactions, Data Servicemay hit a rare race condi-tion. To recover from thisData Service might restart

Data servicemay restart dueto a race condi-tion


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

Data Servicecan restart unex-pectedly duringshutdown pro-cess


Not applicableIn rare cases, Data Servicemay restart during snapshotreplication due to the failureof checksum algorithms todetect all network errors.

Data Servicemay restart dueto network errors






Enabling encryption will re-solve the issue

Disabling encryption mightcause NVRAM data to fillup with data waiting formaster passphrase, whichcan cause SynchronousReplicated volumes to goout of sync.

Disabling encryp-tion may causeSynchronousReplicated vol-umes to remainout of sync



A network issue betweenupstream and downstreamcould abruptly stop opera-tions running downstreamcausing them to exit prema-turely, resulting in DataService restart.

Data Servicemay restart ifnetwork issue isencountered be-tween GroupLeader andBackup GroupLeader arrays


Retry operation after a fewminutes to reassign array topool.

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

Unassigning andreassigning ar-ray to a poolwithin 5 minuteswill fail


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

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

Data Servicerestart due to arace condition


The array will continue toshutdown after the Dataservice restart.

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

Data servicemay restart dur-ing array shut-down


Not applicableThe Data Service mayrestart during array shut-down when jobs related tothe Data Service are unableto be gracefully shutdown.The restart should not haveany impact as the array isin shutdown process.

Data Servicemay restart dur-ing array shut-down






Contact HPE Nimble Stor-age Support to increase thememory limit for the service.

In some instances the cim-server service will exceedits memory limit and nolonger be able to start.

Cimserver stopswhen memorylimit is exceed-ed.


Not applicableN-Port ID Virtualization(NPIV) feature with VMsusing RDM luns on ESXhosts is not supported.

NPIV feature isnot supportedfor VMs on ESX


Please contact HPE NimbleStorage Support so theproblematic drive can bereplaced.

In rare instances due toslow IO to one of the disks,the Data Service may hit atimeout and restart unex-pectedly. This issue mayoccur during a NimbleOSsoftware update.

Data Servicerestarts due toslow IO to one ofthe disks

PlatformAS-90096

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

Data Servicerestart due to re-source allocationfailure.

PlatformAS-103802


During controller boot,firmware update may fail tocomplete causing the con-troller to boot to mainte-nance mode.

Replacementcontroller fails toboot to Nim-bleOS

PlatformAS-107299


In rare incidents, controllersdo not power on followingpower cycle.

Controller doesnot power on fol-lowing a powercycle.

PlatformAS-100088





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

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

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

PlatformAS-90455

The restart of the servicewill clear the low memorycondition, no further actionis needed.

Data Service may restart inthe rare case when a con-troller is low on memory.

Data Servicemay restart if acontroller is lowon memory

PlatformAS-99567

Contact HPE Nimble Stor-age Support to review disksfor replacement.

In rare instances, the DataService may restart if thearray has multiple baddrives which make IO han-dling very slow.

Data Servicemay restart if thearray has multi-ple bad drives

PlatformAS-108793

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

NDER processmay lead to hostreconnects

PlatformAS-96053





Not applicableThe Group ManagementService may restart unex-pectedly due to receivebuffer exhaustion on themanagement network inter-face. No visible impact hasbeen reported because ofthis issue.

UnexpectedGroup Manage-ment Servicerestart due to re-ceive buffer ex-haustion

PlatformAS-98885

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

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

Delay with DataService startingduring shelfstate change

PlatformAS-101570

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

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

PlatformAS-91522

Add the disk from the CLIusing the disk add com-mand and output from disklist: 1. Run disk --list 2. Notethe slot number, and shelflocation for the disk labeledforeign. 3. Add the disk:disk --add <slot num-ber> --array <array-name> --shelf_location<shelf location> Note:the --force option may berequired Contact HPE Nim-ble Storage Support if thedisk does not move toresynchronizing state aftercompleting the commands.

Disk will report foreign fordisk state in the GUI Hard-ware page or in the outputof disk --list from the CLI.This typically occurs if diag-nostic data may not havebeen removed after testing.

Replacementdisk reports for-eign for diskstate in GUI/CLI

PlatformAS-99428





Not applicableThe current thermal policyhas a limitation where indi-vidual PCIe componentsare not monitored on card-by-card basis. As a result,the high level temperaturepolicy that is current imple-mented, is sometimes inca-pable of regulating the tem-peratures of individualcards.

Limited thermalmonitoring policyfor PCIe compo-nents

PlatformAS-107489

The controller reboot shouldrestore SAS HBA to normalstate. HPE Nimble Supportmay contact customer tocollect additional diagnos-tics if required.

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

Unexpectedcontrollertakeover due toincorrect state ofthe SAS HBA

PlatformAS-33725

Review the array configura-tion matrix for the arraymodel: https://infos-ight.hpe.com/InfoSight/me-dia/local/ac-tive/34/CSxxx%20Con-fig%20Matrix.pdf Removeany additional cache fromthe expansion shelf that ex-ceeds the max cache limitbased on array model.

ES2 and AFS2 expansionshelves contain additionalslots for upgrading cachecapacity of the array. Olderarray models have a maxi-mum cache limit that can behandled by the array. If ES2or AFS2 expansion shelvesare added to an array andthe cache exceeds the maxcache limit for the arraytype, the data service mayrestart due to running out ofdata pages.

Data servicemay restart ifmaximum cacheexceeded forCS215, CS235,CS300, CS500,CS700 arrays

PlatformAS-93296

Configure the proxy serverwith a username that doesnot include a special charac-ter in the username orpassword.

If the array is configuredwith a proxy server and theconfiguration includes ausername or password thatincludes special characterssuch as $, the update mayfail.

Software updatemay fail if arrayis configuredwith proxy serv-er

PlatformAS-95995



https://infosight.hpe.com/InfoSight/media/local/active/34/CSxxx%20Config%20Matrix.pdf







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 theESXi server update, somecommands need to be runon the server. Runningthese commands fails witherror Error: A general sys-tem error occurred: Internalerror. if the /var is full. Thisis a known issue with 6.7builds running with Emulexdriver which has been fixedas part of ESX 6.7 U2. <ahttps://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-es-xi-67u2-release-notes.html#resolvedissues

dHCI updateworkflow can failif /var mount-point on the hostis full.


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

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

An in-progessdHCI updatefails if the groupleader fails over


After confirming the arrayhas returned to Ac-tive/Standby status, stopthe hung task and run theNimble Add ProStack serv-er task again.

If an array failover occurswhile Nimble Add ProStackserver task is running fromvCenter, the process mayhang and not complete.

Nimble AddProStack servertask may hang ifarray failover oc-curs


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

The updatepage on thedHCI plugintakes 4 hours torefresh


A valid ESXi license mustbe assigned to the server.

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

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




https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-esxi-67u2-release-notes.html#resolvedissues






Admission Control shouldbe disabled on a dHCIcluster for the update toproceed.

For ESXi server update,DRS is used to migrateVMs running on the server.If admission control is en-abled on the dHCI cluster,DRS is not able to migrateVMs off a server.

dHCI updatefails when Admis-sion Control isenabled


Offline the read-only snap-shots where the hosts issending write requests.

When host sends write re-quests to read-only snap-shots, the writes will fail withSCSI Check Condition withadditional status SC-SI_ASC_ASCQ_LU_SOFT-WARE_WRITE_PROTECT-ED. But if Volume Manageris creating snapshot at thesame time, the Data Ser-vice may hit an assert andrestart to recover automati-cally.

Data Servicemay hit assertwhen host sendswrites to read-only snapshotand snapshotcreation is inprogress.

SANAS-86843

Not applicable.During a controller reboot,due to resource contentionbetween new Fibre Channel(FC) connection attemptsand shutdown of the FCmodule, the Data Serviceon the array may restartunexpectedly.

Data Servicerestart duringshutting downFC service onthe standby con-troller

SANAS-100197

Identify the offline volumesor stale targets and initiatea host side cleanup/rescanto avoid repeated login at-tempts and failure to the of-fline or stale targets.

Logins to CHAP authentica-tion enabled volumes couldleak a small amount ofmemory by repeated failedlogin attempts to offline vol-umes or stale targets. Overa period of days and weeks,this leak can result in oneor more of the NimbleOSprocesses running out ofmemory. As a result, Nim-bleOS services may restartunexpectedly.

NimbleOS ser-vices mayrestart unexpect-edly due tomemory leak inlogin path

SANAS-107345





Identify the offline volumesor stale targets and initiatea host side cleanup/rescanto avoid repeated login at-tempts and failure to the of-fline or stale targets.

Logins to CHAP authentica-tion enabled volumes couldleak a small amount ofmemory the size of CHAPusername. Over a period ofdays and weeks, this leakcan result in one or more ofthe NimbleOS processesrunning out of memory. Asa result, NimbleOS servicesmay restart unexpectedly.The issue is exacerbated byrepeated failed login at-tempts to offline volumes orstale targets.

NimbleOS ser-vices mayrestart unexpect-edly due to slowleak with CHAPlogins

SANAS-109412

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

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

SANAS-98042

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

Data Servicemay restart unex-pectedly whileremoving mem-ber array

SANAS-101325

Not ApplicableThis scenario is rare tohappen but presently nothandled gracefully leadingto a File System restart forrecovery. The issue is trig-gered when a write requestwith valid length is receivedin SCSI Command Descrip-tor Block but invalid (zero)value in Data-Out Buffer.

File System ser-vice may restartwhen an invalidwrite request isreceived

SANAS-94761





Not applicableGroup Management Servicemay restart unexpectedlyas one thread has taken aReadWrite lock which hasanother writer thread, whichis waiting for Scale-OutDatabase (SODB) transac-tion to be completed. Theservice restarts due to theSODB transaction exceed-ing the expected timeout.

Group Manage-ment Servicemay restart dueto race condition

System Manage-ment

AS-103766

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

Alarm IDs inalarm list mayappear out of or-der.

System Manage-ment

AS-105431

The problematic alarm canbe manually deletedthrough the CLI command:alarm --delete<alarm_id>

Due to a race condition it ispossible for an alarm to re-main uncleared on the sys-tem even when the alarmcondition it is reporting is nolonger the case. This canhappen if the onset alertand recovery alert weregenerated at close to thesame time.

Alarm may notclear as expect-ed

System Manage-ment

AS-94398

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

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

Member arrayalarms are stillvisible after ar-ray is removedfrom group

System Manage-ment

AS-106124

Not applicableThe eventd process mayrestart unexpectedly in sys-tems with larger configura-tions due to exceedingmemory limit. The servicewill recover after the restart.

Eventd processmay restart dueto exceedingmemory limit

System Manage-ment

AS-99679





Not applicableAlerts and Alarms process-ing service may restart un-expectedly when certainoperation surpass the desig-nated health check timeout.The process will stabilizefollowing the restart.

Alerts andAlarms process-ing service mayrestart unexpect-edly

System Manage-ment

AS-50821

Not applicableThe Eventd process mayinfrequently crash, due to abug in an external libraryused by the DNS resolver.The restart will not impactdata connections to the ar-ray and the process will re-cover after the restart.

Eventd processmay restart inter-mittently

System Manage-ment

AS-46024

Rename the folders to beunique. If the Event Manage-ment service continues torestart or remains unavail-able, contact HPE NimbleStorage Support.

When an alert is raised onone of two folders havingthe same name but are lo-cated in two separate pools,the Event Managementservice may restart repeat-edly.

Event Manage-ment servicerestart when twofolders in differ-ent pools havethe same name

System Manage-ment

AS-101273

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

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

System Manage-ment

AS-71090

Not applicableThe Group ManagementService on the array mayrestart unexpectedly whena SOAP timeout is encoun-tered after trying to createa volume. This occurs dueto a race condition wherethe array attempts to deletethe volume after the cre-ation attempt fails.

Group Manage-ment Servicerestarts followingvolume creationtimeout

System Manage-ment

AS-104640

Not applicableEvery night, when inactivekeys for deleted encryptedvolume are deleted by thearray, it creates an audit logentry with root as the userperforming the action.

Purge inactiveencrypted keysappears in auditlog.

System Manage-ment

AS-107980





Perform the Autosupportvalidation process again.

When autosupport configu-ration validation is per-formed, internal processtracking may abort causingthe Group ManagementService to restart.

Group Manage-ment servicemay restartwhen performingAutosupport Val-idation

System Manage-ment

AS-104185

Not applicableConnection to the Scale-Out Database can not bereinitialized when a transac-tion is in progress. TheGroup Management Servicewill restart to restore connec-tion.

Group Manage-ment servicemay restartwhen connec-tions to Scale-Out Databaseexceeds thresh-old value

System Manage-ment

AS-109127

Not applicableDuring key value metadatahandling, the process maydelete primary keys in onetable of the Scale-OutDatabase (SODB) and thentry to reference the deletedprimary key as foreign keyin another table in SODB.This causes foreign key vio-lations in Postgres andeventually leads the GroupManagement service torestart.

Group Manage-ment servicemay restart dueto key valuemetadata han-dling

System Manage-ment

AS-108146

Not applicableDuring internal databaseprocessing stale table en-tries are cleaned up. TheGroup Management servicemay restart if the array isunder heavy load while thisclean up is performed andinternal processing timesout. The service restarts torecover from the conditionand resumes processing.

Group Manage-ment servicemay restart dueto internaldatabase time-out

System Manage-ment

AS-98792

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

group --statusCLI outputshows incorrectFailover Modeduring networkconnectivity is-sues

System Manage-ment

AS-99704





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

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

Array Manage-ment Servicerestarts duringBackup GroupLeader discov-ery

System Manage-ment

AS-98953

None.Due to a race condition, theArray Management servicemay restart when the arrayis in the process of shuttingdown all services as part ofthe array shutdown. An alertand a process core couldbe generated as a result butthere is no impact to func-tionality. Once the arraypowers back on, all servicesstart up normally.

Array Manage-ment Servicemay restart dur-ing array shut-down

System Manage-ment

AS-106539

No workaround is needed.The service recovers on itsown.

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

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

System Manage-ment

AS-94683

Not applicableDuring software update ofarray group with Peer Per-sistence configuration, Auto-matic Switchover (ASO) isdisabled. If an array goesdown (both controllersdown) during the softwareupdate process, due to apower failure or other unex-pected event, hosts couldlose access to data until thefailed array recovers, or amanual switchover of theaffected volumes is done.

Peer Persis-tence AutomaticSwitchover(ASO) is dis-abled duringsoftware update

System Manage-ment

AS-94649





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

Group limitscommand listsinternal identi-fiers

System Manage-ment

AS-101342

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

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

Max limit of 120nics in netconfigalarm does notget cleared

System Manage-ment

AS-87749

Not applicableThe Array Managementservice may restart unex-pectedly due to an a memo-ry allocation failure whenattempting to synchronizeconfiguration with a mem-ber array. The restart of theArray Management serviceclears the situation.

Array Manage-ment servicerestarts due tomemory alloca-tion issue

System Manage-ment

AS-104812

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

Force deletion ofuser definedperformancepolicy should notbe supported

System Manage-ment

AS-74242





Not applicableVolume move operationscopy both data and associ-ated metadata from thesource array to destinationarray. For groups with multi-array pools, copying themetadata can take a signifi-cant amount of time, andthe estimate calculationmay be inaccurate initially.These estimates will auto-correct themselves by usingfeedback mechanisms.

Volume Migra-tion estimatesmay be inaccu-rate when multi-ple volumes arebeing migrated

System Manage-ment

AS-101832

The service will stabilize onits own following therestarting.

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

Array Manage-ment Servicerestarts unex-pectedly underhigh load

System Manage-ment

AS-101420

Not applicableWhen internal processcommunication fails be-tween processes the GroupManagement service mayrestart to recover.


System Manage-ment

AS-108299

Not applicableIf communication betweenGroup Management andPostgres services does notcomplete within expectedtimeout, the Group Manage-ment service may restart.The restart will resume thecommunication and try thetransaction again.

Group Manage-ment servicemay restart dueto communica-tion timeout ex-ceeded

System Manage-ment

AS-97327

Not applicableThe Group Managementservice may restart unex-pectedly if there is a memo-ry allocation error involvingthe arrays database man-agement system.

Group Manage-ment Servicerestarts due tomemory alloca-tion issue

System Manage-ment

AS-105702

Not applicableArray Management servicesmay be unavailable for ashort time due to restartduring automatic failover.

Array Manage-ment processmay restart dur-ing automaticfailover

System Manage-ment

AS-94835

Not applicableGroup Management servicemay restart due to healthcheck timeout exceeded.The service will recover af-ter the restart.

Group Manage-ment Servicemay restart unex-pectedly

System Manage-ment

AS-97697





Disable automatic failoverand remove witness fromconfiguration.

After Group migration isperformed, backup groupleader becomes groupleader. If witness is discon-nected for more than fiveminutes, the new leader willnot remove quorum.

After group lead-er migration,quorum is notremoved afterwitness discon-nection

System Manage-ment

AS-98434

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

Alert for abortedhandover doesnot specify rea-son

System Manage-ment

AS-98650

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

Both upstreamand downstreammay claim thevolume collec-tion ownershipwhen excessivehandovers areperformed

System Manage-ment

AS-99520

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

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

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

System Manage-ment

AS-90286

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

SynchronousReplication Vol-ume Count Limit

System Manage-ment

AS-89124





Not applicableA deadlock can occur be-tween two managementprocesses when updatingthe replication bandwidththrottle. The ManagementProcess will restart andclear the condition. There isno disruption to data ser-vices and replication willcontinue automaticallywithout intervention.

Group manage-ment processmy restart due toa deadlock whenreplicating

System Manage-ment

AS-59470

Update the downstreampools Deduplication settingto match the upstream pool.

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

Configuration ofdeduplicationvolumes for syncreplication mightfail

System Manage-ment

AS-90649

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

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

Error No mes-sage receivedafter issuing CLIcommand to dis-associate vol-ume from collec-tion

System Manage-ment

AS-98378

Not applicableWhen the system has ahigh number of objects, theGroup Management servicemay restart while runningREST query or CLI com-mand.

Group Manage-ment servicemay restart dueto high memoryusage

System Manage-ment

AS-96241

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

Group manage-ment servicemay restart dueto assertion fail-ure

System Manage-ment

AS-96143





Reduce the total data theupstream group to is tryingto sync with the down-stream group by doing thefollowing: 1) Reduce the to-tal number of volumes inthe upstream protectionpolicy. 2) Reduce the snap-shot frequency of the up-stream protection policy. 3)Reduce the number ofsnapshots retained betweenthe downstream and up-stream.

During snapshot replicationthere is an increase of loadon the downstream group.This burst of replication ac-tivity may trigger a restart ofthe downstream groupmanagement service whenthere are a lot of snapshotsscheduled for replication.

Downstreamgroup manage-ment serviceprocess restartsduring snapshotreplication

System Manage-ment

AS-85198

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

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

Error No mes-sage receivedafter issuing CLIcommand to as-sociate volumeto volume collec-tion

System Manage-ment

AS-90633

Not applicableIf two on-premise arraygroups configured with aNimble Cloud Volumes(NCV) partner are merged,the Cloud Volume replica-tion will stop working.

Cloud Volumesreplication doesnot supportgroup merge

System Manage-ment

AS-88308

Not applicableInternal workflow process-ing related to the replicationpartner object may causethe process to deadlock,resulting in Group manage-ment service restart.

Group manage-ment servicemay restart unex-pectedly

System Manage-ment

AS-105064

Not applicableWhile syncing the configchanges on the down-stream array, group man-agement service mayrestart due to a race condi-tion between protectionpolicy deletion and addingthe volume to the protectionpolicy.

Group manage-ment servicemay restart dueto race condition

System Manage-ment

AS-106490






Arrays with volumes thathave large branch struc-tures may cause internalcommand processing time-out to be exceeded. Thiswill cause the Group Man-agement service to restartdue to health check failure.

Group manage-ment servicemay restart unex-pectedly

System Manage-ment

AS-98155

Retry the command for thefailed volumes.

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

Group Manage-ment Servicerestarts duringbulk volume up-date

System Manage-ment

AS-95610

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

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

Group Manage-ment Servicerestarts due topacket loss innetwork

System Manage-ment

AS-91638

Not applicableDuring a planned arrayshutdown, the Group Man-agement service mayrestart due a race condition.There is no data or manage-ment interruption since theservice is already shuttingdown.

Group Manage-ment servicerestarts duringthe array shut-down

System Manage-ment

AS-108765

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

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

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

System Manage-ment

AS-105944

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

Unmanagedsnapshots re-main aftercleanup is en-abled

System Manage-ment

AS-93113





Set downstream partner onall schedules in the volumecollection to none andthereafter change replica-tion partner on desiredschedules to the new part-ner.

A volume collection cancurrently replicate to onlyone replication partner. Incase of multiple schedulesin a volume collection, edit-ing single protection sched-ule to different replicationpartner violates this con-straint.

Changing replica-tion partner in avolume collec-tion with multipleschedules re-ports the follow-ing error: The re-quest could notbe processed bythe server

System Manage-ment

AS-23891

Not applicableDue to a race condition, theGroup Management Serviceon a downstream groupmay restart while updatingvolume collections from theupstream group.

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

System Manage-ment

AS-105291

Not applicableIf communication betweenGroup Management andPostgres services does notcomplete within expectedtimeout, the Group Manage-ment service may restart.The restart will resume thecommunication and try thetransaction again.

Group Manage-ment servicemay restart dueto communica-tion timeout ex-ceeded

System Manage-ment

AS-97899

Not applicableGroup Management servicemay restart due to memoryexhaustion in configurationsthat approach 10,000 vol-umes and 300,000 snap-shots.

Group Manage-ment servicemay restart dueto memory ex-haustion

System Manage-ment

AS-94517

Contact HPE Nimble Stor-age Support to identifyACLs in forced-delete/cre-ate-retry state, verify theseACLs are associated withsnapshots that no longerexist, and delete theseACLs from the internalNimbleOS database.

In certain scenarios, a vol-ume deletion will not com-plete due to the existenceof a stale ACL associatedwith it. This stale ACL isassociated with a snapshotof the volume that was pre-viously deleted. These vol-umes will not show up in theCLI/GUI as they are in ahidden state.

Deletion of a vol-ume is not com-pleted due to thepresence ofstale ACLs asso-ciated with it

System Manage-ment

AS-105432





Not applicableDuring planned servicestop, such as array shut-down, the Group Manage-ment service may restartdue to a race condition.There is no data or manage-ment interruption since theservice is already shuttingdown.

Group Manage-ment servicemay restart dur-ing array shut-down

System Manage-ment

AS-104965

Not applicableThe Array ManagementService restarts unexpected-ly following automaticGroup Leader Failover(AFO). The restart is non-disruptive.

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

System Manage-ment

AS-99615


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

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

System Manage-ment

AS-101392

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

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

System Manage-ment

AS-100382

Not applicableIf internal database process-ing for array statistics ex-ceeds the expected timeout,the Group Managementservice will restart due tohealth check failure to recov-er.


System Manage-ment

AS-98504

Not applicableIn rare instances, the GroupManagement Service mayrestart unexpectedly whenthe Group Leader andMember array have lostconnectivity due to networkoutage. The service restartrecovers GUI and CLI ac-cess, data services are notimpacted by the restart.

Group Manage-ment Servicemay restart unex-pectedly due tonetwork connec-tivity

System Manage-ment

AS-103982





Not applicableThe Group Managementservice may restart whenservice communication forinternal database process-ing is terminated. The ser-vice restarts to restore con-nections between the ser-vices.


System Manage-ment

AS-105453

Scheduling snapshots tooccur at different times in-stead of all at once mayhelp alleviate this issue.

Group Management servicemay restart on the arraywhen there is a highamount of snapshot activitybeing performed. The ser-vice restart will recover fromthe condition and the snap-shot operations will resume.

Group Manage-ment servicemay restart unex-pectedly whenperforming highsnapshot activity

System Manage-ment

AS-105804

Not applicableIn rare instances, the Pro-cess Management servicerestart may occur duringsoftware update. The sys-tem recovers after therestart of the service.

ProcessManage-ment servicemay restart dur-ing software up-grade

System Manage-ment

AS-95132

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

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

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

System Manage-ment

AS-98694

Not applicableHigh concurrent REST vol-ume reads with statisticsmay cause Group Manage-ment service to restart.Current REST requests willfail, GUI and CLI will be un-available. The system willrecover after the restart ofthe service.

Group manage-ment servicemay restartwhen there aremany REST re-quests for vol-ume statisticsvalues

System Manage-ment

AS-108432





Not applicableInfrequently the GroupManagement service mayencounter an error whileshutting down. If the serviceis being restarted it maytake a few more seconds tostart. GUI and CLI will beunavailable for a few sec-onds.

Group Manage-ment servicemay become un-available whenshut down

System Manage-ment

AS-110123

Not applicableThe Group Managementservice may restart whilecollecting statistics frommember array. This can oc-cur when the request fromthe group leader to memberarray exceeds timeout,causing the service torestart to recover.

Group Manage-ment servicemay restartwhile collectingmember arraystatistics

System Manage-ment

AS-93469

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

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

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

System Manage-ment

AS-106848

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

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

System Manage-ment

AS-72559

Running the software --re-sume_update commandfrom the console will clearthis condition.

Under rare conditions, asoftware update may reportan error even though theactual update has complet-ed successfully. This occurswhen software update takeslonger than 4 hours.

Timeouts duringsoftware update

System Manage-ment

AS-40516





Ignore the error messageand retry the managementoperation

While the volume ownershipis being changed, anymanagement operation in-volving that volume couldfail. This is expected behav-ior. Depending on theprogress of that handoveroperation, managementoperation is failing with dif-ferent errors.

Volume manage-ment operationsmay fail with un-related errormessages whilehandover is in-progress

System Manage-ment

AS-91962

Not applicableGroup Management Servicemight restart unexpectedlywhile creating Peer Persis-tent snapshot during Day-light Saving Time adjust-ment window.

Group Manage-ment Servicemay restart unex-pectedly duringcreation of PeerPersistent Snap-shot

System Manage-ment

AS-92209

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

HPE NimbleStorage arraycompatibility is-sues with MITKerberos trusttypes

System Manage-ment

AS-95212

Not applicableActive Directory Authentica-tion causes the arraysGroup management serviceto wait for a response fromthe Active Directory. If thisresponse is delayed, theGroup Management Servicemay restart unexpectedly.

Active Directoryauthentication insome cases,may lead to aGroup Manage-ment servicerestart

System Manage-ment

AS-104512





Not applicableWhen logging in with a Ac-tive directory (AD) user, de-layed responses from ADmay lead to Group Manage-ment service restart.

Group Manage-ment servicemay restart dueto Active directo-ry communica-tion taking toolong.

System Manage-ment

AS-109549

Not applicableThe Group Managementservice may restart wheninternal database process-ing exceeds the expectedtimeout value. The servicerestarts to recover from thecondition.

Group Manage-ment servicemay restart dueto health checktimeout

System Manage-ment

AS-109805

Delete unused clones orvolumes to bring down thevolume count.

Following operations will failupon reaching the volumelimit: -adding Synchronousreplication schedule to avolume collection -associating a volume to avolume collection with Syn-chronous Replication en-abled -editing a VolumeCollection schedule to addSynchronous Replicationpartner

Enabling syn-chronous replica-tion fails uponreaching volumelimit

System Manage-ment

AS-102893

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

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

Unable to creatededupe enabledvolumes on anew install

System Manage-ment

AS-86545

The Group ManagementService will eventuallyrestart itself

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

Group Manage-ment Service istemporarily un-available afterdeleting volumes

System Manage-ment

AS-101535





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

No CLI supportfor changing theWitness Port

System Manage-ment

AS-92157

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

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

System Manage-ment

AS-99431

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

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

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

System Manage-ment

AS-98177

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

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

Incorrect informa-tion on hardwarepage displayedwhen controlleris down

System Manage-ment

AS-87701

Use Google Chrome orMozilla Firefox browser.

The Array GUI incorrectlyreturns an error when avalid value for the folderoverdraft limit has been en-tered. This happens only inInternet Explorer and Mi-crosoft Edge browsers.

GUI Error whenentering a validfolder overdraftlimit value

System Manage-ment

AS-102299





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

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

Group Merge viaGUI unable toprocess largeamount of con-flicts

System Manage-ment

AS-77372

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

GUI may showSuccessful mes-sage whengroup mergefails

System Manage-ment

AS-87886

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

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

Unable to edit astorage pool andassign an arrayat the same time

System Manage-ment

AS-94575

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

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

System Manage-ment

AS-95591





Fix the name conflict on thedownstream array.

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

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

System Manage-ment

AS-104099

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

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

Array GUI doesnot specifywhich snapshotsare unmanaged

System Manage-ment

AS-93157

The values should reportcorrectly within 24 hours af-ter the update has complet-ed.

The volume performancenumbers displayed in theGUI under Manage >Data Storage > Volumes> Performance Tab maydisplay invalid values tem-porarily after an array soft-ware update.

Volume perfor-mance numbersmay report in-valid values aftersoftware update

System Manage-ment

AS-92634

Not applicableWhen the Group Leader at-tempts to complete theBackup Group Leader pro-motion, if there is not ahealthy data path, theBackup Group Leader pro-motion fails. Despite, thenetwork error, the BackupGroup Leader promotiongoes into a loop and ulti-mately leads to an unexpect-ed restart of the Array Man-agement Service.

Array Manage-ment Servicerestarts whenGroup Leadercannot reachBackup GroupLeader

System InternalsAS-104567



NimbleOS 5.2.1.200 Release Notes - Hewlett Packard Enterprise...Note Description An extended data...

Documents

Transcript of NimbleOS 5.2.1.200 Release Notes - Hewlett Packard Enterprise...Note Description An extended data...