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 products
and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. Hewlett Packard Enterprise shall 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, or copying. Consistent
with 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 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 the United States and other
countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other 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 for
HPE InfoSight, click the Create Account link on the main page.
Email: [email protected]
For all other general support contact information, go to https://www.hpe.com/us/en/services/nimble-storage.html.

2
Contents

NimbleOS 5.2.1.600.................................................................................................................4
Important 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

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

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-3-NIMBLE (877-364-6253), option 2.

Important Update Note

Updating NimbleOS can involve an update to component firmware on the standby controller. This can cause an email alert
and automated case indicating "Standby Controller Not Available" when the firmware update process takes longer than five
minutes. This is expected behavior and does not affect data services. At the end 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 a successful 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 this document by
performing the following steps:
1 In the navigation pane on the HPE InfoSight Documentation page, scroll through the Document Type list and select
Support Policy.
2 In the page that appears, select General Terms and Conditions. This document opens in a browser tab.

Special Notes
Note Description
CRITICAL HPE Nimble Storage continues to qualify configurations between releases. The
Validated Configuration Matrix provides information about validated configurations
and is updated frequently. It is a good practice to check your system configuration
against this online tool. The Validated Configuration 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 to NimbleOS
5.2.1.600.

CRITICAL An extended data services outage may occur with MS iSCSI initiator and Intel NICs
using 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 Windows
driver.

Important Update Note 4

Note Description
CRITICAL A service outage may occur on Windows 2012 R2 hosts using Emulex or 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 running virtualized
in VMware ESX, manually rebooting the active controller in presence of heavy IOs
using the reboot --controller command on a Fibre Channel array may trigger an
incorrect 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 these
environments, we recommend the failover command instead.

CRITICAL Due to a known Red Hat Enterprise Linux bug 3550561, unexpected application
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 Nimble Storage
fully supports Windows guest operating systems on Microsoft Hyper-V, including
Virtual Fibre Channel (VFC) connectivity and multipathing with HPE Nimble Storage
DSM 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 to
Red Hat bug 1364282, which can cause an unexpected service outage.

Important Starting with NimbleOS 5.1.1.0, the size of the software package now exceeds 2
GB, which may lead to lengthier software download times. Previously, the sizes of
the NimbleOS 5.0.x download packages were approximately 1.6 GB, and NimbleOS
4.x packages were approximately 900 MB.
Important After completing the NimbleOS update for array groups configured for Synchronous
Replication, download the corresponding version of the Synchronous Replication
Witness software, and update the witness host.
Important Microsoft Offload Data Transfer (ODX) is not supported if the destination volume
has synchronous replication enabled.
Important As of vSphere 7.0, VMware has discontinued the flex client. Consequently, the HPE
Nimble Storage vCenter Plugin no longer supports the flex plugin for vCenter 7.0.

Special Notes 5
Note Description
Important You can enable deduplication for CS1000, CS3000, CS5000, CS7000, CS700, and
CS500 arrays on a volume only if the corresponding storage pool has a Flash to
Disk Ratio (FDR) greater than 4%. To calculate the FDR, obtain the "Total array
capacity (MiB)" and "Total array cache capacity (MiB)" values by using the HPE
Nimble 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 command
will 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 deduplication
for the entire array.

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

Important Numerous host integration toolkits are supported in NimbleOS 5.2.1.600. It is

strongly recommended that they be installed on all Windows, Linux, and VMware
hosts. For more information about supported toolkits, refer to the Validated Con-
figuration Matrix, which is available on HPE Nimble Storage InfoSight:
https://infosight.hpe.com/resources/nimble/validated-configuration-matrix

Important HPE Nimble Storage recommends that you update to HPE Nimble Storage Windows
Toolkit (NWT) 7.0.1 or later if you are using Microsoft VSS Synchronization and
NimbleOS 5.1.4.200 or later.
Using application consistent snapshots with earlier versions of NWT and NimbleOS
5.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: failed
to find LUN s/n <SERIAL_NUMBER> on connected ar-
rays. Make sure that the Nimble array version is
compatible with this version of Nimble Windows
Toolkit.
event id 4170: Nimble VSS provider is not compati-
ble with the current version of the Nimble array
software(). Install appropriate version of the
Nimble VSS provider.

NWT 7.0.1 resolves this issue.

Special Notes 6
 Note Description
Important HPE Nimble Storage Connection Manager (NCM) for VMware 7.0 is signed by
VMware for ESXi 7.x. It can be installed through the VMware Update Manager or
esxcli 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 Integration
Guide, 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/Linux
hosts. Before you update the NimbleOS, install the HPE Nimble Storage Windows
Toolkit (NWT) or HPE Nimble Storage Linux Toolkit (NLT) on the host or tune the
timeout values. Timeout details for various operating systems can be found on
HPE InfoSight under Resources > Documentation. From the HPE Nimble Storage
Documentation page, locate the article you want.
The following Knowledge Base articles and Integration Guides explain how to
configure 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 Timeout
Values 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 downstream
array (as configured in the storage policy). In the case where this vVol VM is
deleted, a supported “claim” workflow allows us to claim this vVol VM on the
downstream array. This workflow is not supported at present if performed on a
setup where the vCenter version is 6.5 or above due to validation failures on the
vCenter.
VMware DCPN Ticket Reference:
https://dcpn.force.com/TechnicalRequestCaseRedesignPart-
ner?Id=5000H00001JRKhf

New Features in 5.2.1.600

No new features were introduced in NimbleOS 5.2.1.600.

New Features in 5.2.1.600 7

Recent Release Features
The 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
HPE Nimble Storage arrays are now able to program the zones in the Fibre Channel (FC) fabric using information from the
initiator groups that have been configured. This removes the requirement for the administrator 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 the currently shipping
arrays. This version of the upgrade process requires a brief down time while the existing array 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 Storage AF60 and AF80
model arrays.
Synchronous Replication: Witness OVA
The Peer Persistence feature requires an external witness. The Witness is available for download from InfoSight 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 that allows you to perform
an 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 ProLiant
servers. 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 cannot
use both in the same cluster.

Documentation
These Release Notes and other user documentation are available on HPE InfoSight:
https://infosight.hpe.com/resources/nimble/docs
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 all
documentation, including support and knowledge base articles, best practices, solutions and integration guides, product
documentation, and configuration matrices.
To go directly to a document, use the navigation pane on the left side of the Nimble Storage Documentation page. 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-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 select
Support 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 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. Each task described by a workflow
document 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 Document
Type 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 Documentation
page, 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 software
packages. The version number listed on the guide might be different from the version numbers of the NimbleOS and Toolkit
software packages that it supports.

Verified Update Paths

Table 1: From Versions 5.x

From Versions 5.x

From Version To Version
5.2.1.500 5.2.1.600
5.2.1.400 5.2.1.600
5.2.1.300 5.2.1.600
5.2.1.200 5.2.1.600
5.2.1.100 5.2.1.600
5.2.1.0 5.2.1.600
5.1.4.200 5.2.1.600
5.1.4.100 5.2.1.600
5.1.4.0 5.2.1.600
5.1.3.100 5.2.1.600
5.1.3.0 5.2.1.600
5.1.2.100 5.2.1.600
5.1.2.0 5.2.1.600
5.1.1.0 5.2.1.600
5.0.10.0 5.2.1.600
5.0.9.100 5.2.1.600
5.0.9.0 5.2.1.600
5.0.8.100 5.2.1.600
5.0.8.0 5.2.1.600
5.0.7.300 5.2.1.600
5.0.7.200 5.2.1.600
5.0.7.100 5.2.1.600
5.0.7.0 5.2.1.600
5.0.6.0 5.2.1.600
5.0.5.200 5.2.1.600
5.0.5.0 5.2.1.600
5.0.4.0 5.2.1.600
5.0.3.100 5.0.10.0

Verified Update Paths 10

 From Versions 5.x
From Version To Version
5.0.3.0 5.0.10.0
5.0.2.0 5.0.10.0
5.0.1.100 5.0.10.0
5.0.1.0 5.0.10.0

Table 2: From Versions 4.x

From Versions 4.x

From Version To Version
4.5.6.0 5.0.10.0
4.5.5.0 5.0.10.0
4.5.4.0 5.0.10.0
4.5.3.0 5.0.10.0
4.5.2.0 5.0.10.0
4.5.1.0 5.0.10.0
4.5.0.0 5.0.10.0
4.4.1.0 5.0.10.0
4.4.0.0 5.0.10.0
4.3.1.0 5.0.10.0
4.3.0.0 5.0.10.0
4.2.1.0 5.0.10.0
4.2.0.0 5.0.10.0
4.1.0.0 5.0.10.0

Table 3: From Versions 3.x

From 3.x Versions

From Version To Version
3.9.3.0 5.0.10.0
3.9.2.0 5.0.10.0
3.9.1.0 5.0.10.0
3.9.0.0 5.0.10.0
3.8.1.0 5.0.10.0
3.8.0.0 5.0.10.0
3.7.0.0 5.0.10.0
3.6.2.0 5.0.10.0

Verified Update Paths 11

 From 3.x Versions
From Version To Version
3.6.1.0 5.0.10.0
3.6.0.0 5.0.10.0
3.5.4.0 5.0.10.0
3.5.3.0 5.0.10.0
3.5.2.0 5.0.10.0
3.5.0.0 5.0.10.0
3.4.1.0 5.0.10.0
3.4.0.0 5.0.10.0
3.3.0.0 5.0.10.0
3.2.1.0 5.0.10.0
3.1.0.0 5.0.10.0

Table 4: From Versions 2.x

From 2.2.x, 2.3.x Versions From 2.1.x Versions From 2.0.x Versions
From Version To Version From Version To Version From Version To Version
2.3.18.0 4.5.6.0 2.1.9.1 2.3.18.0 2.0.8.0 2.1.9.1
2.3.16.0 4.5.6.0 2.1.9.0 2.3.18.0 2.0.7.0 2.1.9.1
2.3.15.0 4.5.6.0 2.1.8.0 2.3.18.0 2.0.6.* 2.1.9.1
2.3.14.0 4.5.6.0 2.1.7.0 2.2.9.0 2.0.5.0 2.1.9.1
2.3.12.* 4.5.6.0 2.1.6.0 2.2.9.0 2.0.4.0 2.1.9.1
2.3.9.* 4.5.6.0 2.1.5.0 2.2.9.0
2.3.8.0 4.5.6.0 2.1.4.0 2.2.9.0
2.3.7.0 4.5.6.0 2.1.3.0 2.2.9.0
2.3.6.0 4.5.6.0 2.1.2.0 2.2.9.0
2.3.4.0 4.5.6.0 2.1.1.0 2.1.9.1
2.3.3.0 4.5.6.0 2.1.0.0 2.1.9.1
2.3.2.1 4.5.6.0
2.3.2.0 4.5.6.0
2.3.1.0 4.5.6.0
2.2.11.0 3.9.3.0
2.2.10.0 3.9.3.0
2.2.9.0 3.9.3.0
2.2.7.* 3.9.3.0
2.2.6.0 3.9.3.0

Verified Update Paths 12

 From 2.2.x, 2.3.x Versions From 2.1.x Versions From 2.0.x Versions
From Version To Version From Version To Version From Version To Version
2.2.5.* 3.9.3.0
2.2.3.* 2.2.11.0
2.2.2.0 2.2.11.0
2.2.1.0 2.2.11.0
2.2.0.0 2.2.11.0

Table 5: From Versions 1.x

From 1.4.x Versions From 1.3, 1.2, 1.1 Versions From 1.0.x Versions
From Version To Version From Version To Version From Version To Version
1.4.12.0 2.1.9.1 1.3.*.* 1.4.6.0 1.0.7.* Contact Support
1.4.11.0 2.1.9.1 1.2.*.* 1.4.6.0 1.0.6.* Contact Support
1.4.10.0 2.1.9.1 1.1.*.* 1.2.2.0
1.4.9.0 2.1.9.1
1.4.8.0 2.1.9.1
1.4.7.0 2.1.9.1
1.4.*.* 1.4.12.0

Known Critical Issues

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-115397 Data Service Data Service dis- On Data Service startup followed Contact HPE Nimble Storage
abled on array due by a failover, during the recov- Support.
to NVRAM Check- ery process, it is possible to hit
sum mismatch a checksum mismatch. The Data
Service restarts when the mis-
match is encountered. The ser-
vice will make three attempts to
restart, before disabling the ser-
vice.

AS-117227 Data Service Data Service may During disk index processing the Not applicable
restart unexpected- automated task manager reports
ly due to health status to the Data Service. If the
check failure task manager does not respond
within the expected time of 30
seconds, the Data Service will
restart to recover from the con-
dition.

Known Critical Issues 13

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-118864 Data Service Data services dae- On hybrid arrays, the flash cache If required, the timeout for the
mon restart checkpoint task is run periodical- cache checkpoint task can be
ly to reduce memory/nvram increased.
consumption by the cache
buffers. This task is expected to
completed within a specified
amount of time. In certain rare
scenarios, this task can be
blocked and fail to complete in
time. This can result in a restart
of the data services daemon. A
single restart of the data ser-
vices daemon should not result
in any interruptions on the client
side.

AS-116051 Data Service Data Service may In rare instances, the Data Ser- Contact HPE Nimble Storage
restart unexpected- vice may restart unexpectedly Support
ly while performing Volume Man-
agement checksum computa-
tions.

AS-77607 Data Service Removing member Scaled vVol environments with When planning to remove a
array from multi-ar- 500 vVol VDI VMs or more than member array from group,
ray group may 5000 Nimble vVol volumes may schedule a planned maintenance
cause IO disruption experience IO disruption when window and place all ESX hosts
to scaled vVol envi- removing a member array from into maintenance mode to mini-
ronments group. Symptom of problem mize impact to availability. ESX
would appear as vVol datastores typically resumes connection to
being (inaccessible). Virtual Ma- vVol datastores, and reconnects
chine status would also appear to VMs, after a period of 15-30
as (inaccessible). minutes automatically without a
manual intervention.

AS-101976 Data Service Volume move may Volume moves transfer data Not applicable
result in latency if from one Nimble array to anoth-
Nimble Connection er. During this move, if the host
Manager is not in- sends I/O to the incorrect array,
stalled the I/O needs to be forwarded
to the correct array owning the
data. This results in higher than
usual I/O latency. To avoid this
issue in VMware environments,
the Nimble Connection Manager
for VMware needs to be installed
on all hosts accessing the vol-
ume.

AS-114277 Data Service Data service may The Data service may restart Not applicable
restart unexpected- unexpectedly when a checksum
ly verification failure occurs.

Known Critical Issues 14

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-90668 Data Service Data Service When the Data Service detects Contact HPE Nimble Storage
restarts when de- a metadata inconsistency, the Support
tecting metadata service may restart repeatedly
inconsistency and hosts could experience un-
expected application behavior.

AS-106021 Data Service Index verification In rare cases during index cre- Contact HPE Nimble Storage
fails if a 16 TiB vol- ation, when a 16 TiB volume is Support.
ume is completely fully unmapped, the resulting
unmapped causing index structure fails verification
Data Service to go and brings down the Data Ser-
down vice leading to an outage.

AS-96371 Data Service Data service may If the array encounters a faulty Contact HPE Nimble Storage
restart repeatedly SSD with multiple bad segments, Support to identify and replace
due to faulty SSD the Log-structured File System the faulty SSD.
(LFS) attempts to resolve the
errors. If the array is under high
load and LFS has a high humber
of block errors to resolve it may
exhaust the IORW buffers caus-
ing the Data Service to restart
repeatedly.

AS-80025 Data Service Data service may Data service may restart due a Not applicable
restart due to a rare race condition between the
race condition operations of shutting down the
data service and resync of the
standby controller. When the
race condition is detected the
Data service restarts to recover
from the condition.

AS-106093 Data Service Data service may While committing internal Not applicable
restart due to a transactions, Data Service may
race condition hit a rare race condition. To re-
cover from this Data Service
might restart

AS-105607 Data Service Snapshot replica- During snapshot replication of Not applicable
tion of deduplica- a dedupe-enabled volume, the
tion-enabled vol- downstream array file system
umes may lead to may restart due to an out-of-
File System restart memory condition.

AS-94834 Data Service Data Service may A disruption in network connec- Not applicable
unexpectedly tions can cause Data Service to
restart restart unexpectedly.

Known Critical Issues 15

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-109826 Data Service Data Service may Data Services may unexpectedly Not applicable
restart unexpected- restart due to out of memory
ly condition while running snap
replication on dedupe enabled
volumes with high compression
ratios.

AS-108094 Data Service Replication interrup- In environments with frequent Review network devices to
tions and Data Ser- network checksum errors, inter- identify and reduce network
vice restarts may ruptions of Replication and Data checksum errors.
occur due to net- Service restarts may occur.
work errors

AS-96300 Data Service Data Service may Generation delete operations Not applicable, on restart Data
restart due to vol- and NVRAM to disk data flush Service would behave normally.
ume manager operation can cause Data Ser-
health check failure vice to restart due to health
check failure, as it can hold
checkpoint for a long time.

AS-108810 Data Service Volume migration The Volume Manager monitors Contact HPE Nimble Storage
may stall due to volume migration progress. The Support
Volume Manager process relies on reference
reference count counts to determine status. If
handling the reference count is not
cleared as expected during pro-
cessing the migration may stall.

AS-95470 Data Service Pool merge fails When attempting to perform a Not applicable
due to too many pool merge operation, if there
pending deletes are a large number of volumes
that must be striped across the
pool, and one of the arrays has
a large number of pending
deletes, then it is possible for the
operation to fail due to the Data
Service being overloaded.
Symptoms of this behavior are
if the pool merge operation
hangs for several minutes and
returns the following message:
The request could not be under-
stood by the server.

Known Critical Issues 16

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-118115 Data Service Data Service may After performing a software up- After updating to 4.x.x.x or
restart repeatedly date from 3.x.x.x (or earlier) to 5.0.x.x, wait at least 1 hour be-
after performing 4.x.x.x or 5.0.x.x and then updat- fore updating onto 5.1.x.x+ or
multiple software ing onto 5.1.x.x+ immediately contact HPE Nimble Storage
updates in short after the 4.x.x.x or 5.0.x.x update Support.
succession completes, there may not be
enough time for an internal
metadata operation to complete
in the short amount of time the
array is on 4.x.x.x or 5.0.x.x. As
a result, the Data Service can go
into a restart loop leading to an
outage.

AS-105639 Data Service Rare race condition The Data service may restart Not applicable
between Data ser- when Bin Migration is going on.
vice and Group This can happen when following
Management ser- activities happen together: 1. Bin
vice cause Data migration is occurring for a vol-
service restart ume. 2. Group Management ser-
vice restart (because of any rea-
son). 3. Group Management ser-
vice unable to re-sync with Data
service after &nbsp;&nbsp;&nb-
sp;&nbsp;&nbsp;restart. This can
lead to Data service restart but
it will not impact bin migration
as after Data service restart bin
migration will resumed automat-
ically.

AS-76236 Data Service Data Service may Data Service may restart when Not applicable
restart unexpected- operations of volume migration
ly during volume are stuck waiting for ownership
migration transfer completion.

AS-106333 Data Service Data Service restart If the Data Service is restarted Not applicable
during volume during a volume move, it would
move may cause result in incorrect Bin Migration
the service to state to be recovered, causing
restart again. another Data service restart.
This is a rare event since it re-
quires snapshots to be taken as
well as a Data Service restart
during a volume move.

AS-109050 Data Service Writes may be de- Counters used for space account- Contact HPE Nimble Storage
nied due to coun- ing may cause validation to fail. Support.
ters in space ac- The array may see a blip in
counting space usage because of which
writes may be denied and in
worst case, volume may go of-
fline.

Known Critical Issues 17

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-86764 Platform Controller sensors During boot up due to a known If after 20 minutes the controller
missing for Intel defect the controller sen- sensors do not report good
AFxx/HFxx arrays sors may report missing for a state, please contact HPE Nim-
period of time in the array alerts. ble Storage Support for assis-
After about 15-20 minutes, it tance.
returns to a valid state and the
sensors should report valid
readings again.

AS-94961 Platform Performance affect- HPE Nimble Storage has identi- Contact HPE Nimble Storage
ing firmware defect fied a rare firmware defect in a Support.
in a subset of 6TB subset of drives which can, un-
drives. der certain write intensive
workloads, cause the array to
under-perform.

AS-97925 Platform Data Service may The Data Service may restart Not applicable
restart unexpected- unexpectedly when array en-
ly when a disk re- counters a disk returning bad
turns bad data data, and the disk has not been
marked as failed.

AS-86099 Platform Data service may During internal file operations, Not applicable
restart during when processes may be waiting for a
file operation time- lock to be released. If the wait
out is exceeded time exceeds 30 seconds, a ser-
vice health check may restart
the Data service to recover.

AS-108793 Platform Data Service may In rare instances, the Data Ser- Contact HPE Nimble Storage
restart if the array vice may restart if the array has Support to review disks for re-
has multiple bad multiple bad drives which make placement.
drives IO handling very slow.

AS-104517 Platform Data Service may The Data Service on the array Not applicable
restart due to may restart when timeout for
health check failure internal communication between
array controllers has been ex-
ceeded. The service restarts to
restore the communication.

AS-94153 Platform Array update If the array M.2 boot device is Contact HPE Nimble Storage
precheck or Diag- faulty, the array software update Support
nostics for Nimble precheck and/or Diagnostics for
Array uploads may Nimble Array uploads may fail.
fail due to faulty
boot device

Known Critical Issues 18

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-96053 Platform NDER process may Nimble Drive Error Recovery Not applicable
lead to host recon- (NDER) is activated for drives
nects failing I/O in an attempt to recov-
er the drive. In rare instances,
the process may surpass iSCSI
host timeout values, causing
host I/O inaccessibility.

AS-107489 Platform Limited thermal The current thermal policy has Not applicable
monitoring policy a limitation where individual
for PCIe compo- PCIe components are not moni-
nents tored on card-by-card basis. As
a result, the high level tempera-
ture policy that is current imple-
mented, is sometimes incapable
of regulating the temperatures
of individual cards.

AS-51053 Platform Array remains in In rare instances the intercon- Contact HPE Nimble Support for
solo/stale after nect between controllers may be assistance in restoring array to
controller reseat. down following a controller re- Active/Standby status.
seat.

AS-93456 Platform Incorrect software During software update from Verify that the software update
update error mes- NimbleOS 3.x versions to later package has been downloaded
sage /tmp is out of version, a failure to extract the to the system and then attempt
space. software update package may the software update again using
incorrectly return the error the software --resume_update
message /tmp is out of space. command from the CLI.
even if there is still space in the
directory.

AS-104924 dHCI Plugin: Cannot add Currently, if customer plans to In order to add more 4 or more
4 or more servers add 4 or more Proliants servers Proliant Servers, the workaround
in the dHCI deploy- in their dHCI deployment via the is to add up to 3 servers at a
ment plugin, the operation fails. time from the plugin.

AS-112859 SAN Data service may The Data Service on the array Not applicable
restart unexpected- may restart if a Task Manage-
ly ment Function request to abort
a command is received while the
command is still being complet-
ed. The service restarts to recov-
er from the condition.

AS-93191 SAN IO may timeout Normally Fibre Channel session Not applicable
during Fibre Chan- login/logout happens very
nel session login/lo- quickly. Under certain condi-
gout tions, it may take long enough
that SCSI commands will timeout
leading and lead to brief data
unavailable situations.

Known Critical Issues 19

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-91812 SAN Data Service may In rare occasions during periods Review the Fibre Channel fabric
restart due to Fibre where a large number of Fibre for any issues that may cause
Channel command Channel commands are aborted lost frames.
state inconsistency and 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 lost
frames on the fabric due to con-
gestion or hardware failure.

AS-95159 SAN Initiator side Fibre Fibre Channel fabric issues (er- Addressing the fabric issues
Channel Fabric in- rors, congestion, etc.) can pre- should resolve this issue.
stability may result vent the array from transferring
in a large number data and status to the initiator.
of aborted SCSI This can result in a large amount
commands of aborted commands. In rare
cases this may cause problems
for the Fibre Channel driver and
SCSI stack.

AS-94636 SAN Controller may re- In rare instances, the controller Not applicable
boot unexpectedly kernel may crash if the outstand-
due to improper ing SCSI command arent proper-
command cleanup ly cleaned up in the Fibre Chan-
during Fibre Chan- nel driver during session termi-
nel session termina- nation. The kernel crash will
tion cause the controller to reboot to
recover from the condition.

AS-94746 SAN Data Service may When an implicit logout of a Fi- Not applicable
restart after implicit bre Channel session occurs SCSI
logout of Fibre commands from the previous
Channel Session session may not be terminated
properly causing a restart of the
data service. The service restarts
to recover from the condition.

AS-117550 Security Event service may The Event service may restart Contact HPE Nimble Storage
restart unexpected- unexpectedly when attempting Support.
ly to load a trusted certificate due
to an issue which impacts certifi-
cate management. The service
may not restart after encounter-
ing the issue.

Known Critical Issues 20

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-115780 Security Event service may The Event service may restart Contact HPE Nimble Storage
restart unexpected- unexpectedly when attempting Support
ly to load a trusted certificate due
to an issue which impacts certifi-
cate management. The service
may not restart after encounter-
ing the issue.

AS-110030 System Manage- Group Management Group Management service may Not applicable
ment service may restart restart due to a race condition
due to race condi- between threads when a volume
tion access control list is removed.
The service restarts to recover
from the condition.

AS-68651 System Manage- Flood of timeouts Multiple threads are created to Correct the DNS or SMTP config-
ment causing Event Man- deliver emails, however, a non- uration to a valid address by
agement service threadsafe libcurl call is used to ensuring that a ping to the de-
restart dispatch them. If there is a mis- fined address succeeds.
configured DNS or SMTP server,
the curl call will timeout. If there
are greater than 7 emails waiting
to be delivered and all are expe-
riencing timeout, the service
health check timeout is exceed-
ed, causing the Event Manage-
ment service to restart.

AS-116981 System Manage- Group Management Audit log entries exceeding the Not applicable
ment Service may restart limit of 24000, would initiate a
during audit log cleanup of older entries 500 at
clean up a time. This could cause the
group management service to
restart unexpectedly during
processing of the cleanup.

AS-94737 System Manage- No Automatic An Automatic Failover (AFO) of A Manual Group Leader Failover
ment Failover in the the Group Management Services will be required to restore Fibre
event the host los- will not be initiated if all Fibre Channel connectivity to the
es all FC connectivi- Channel (FC) interfaces on the hosts.
ty to an array Group Leader array fail on both
controllers.

Known Critical Issues 21

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-89701 System Manage- Automatic The Automatic Switchover Ser- Not applicable
ment Switchover Service vice internally creates and closes
restarts due to threads each time during Auto-
thread limitations matic Failover (AFO) quorum
setup and tear down. This may
cause the service to eventually
crash after reaching the maxi-
mum thread limit. The system
recovers automatically when the
Automatic Switchover Service
restarts.

AS-65615 System Manage- Group Management When performing a controller A failover can be initiated in or-
ment Service must be upgrade to a high-end model, der to restart the Group Manage-
restarted to unlock the object limits will still show ment Service. You may also
additional volume the lower limits if the Group contact HPE Nimble Storage
limits after con- Management Service is not Support to restart the service
troller upgrade restarted. manually.

AS-116943 System Manage- Array Management The Array Management Service Not applicable
ment Service may be un- may be unavailable during or
available during shortly after Automatic Group
Automatic Failover Leader Failover events. This may
cause the CLI or GUI to be un-
available for a brief period of
time until the service startup
completes.

AS-94594 System Manage- Group Management Group Management service may Not applicable
ment service may restart restart when internal processing
unexpectedly fails on arrays with high snap-
shot activity. This may cause
snapshots to fail to be deleted.

AS-61614 System Manage- Group Management The Group Management service Not applicable
ment service may restart may restart during an array
during array shut- shutdown while processing
down REST request. No user opera-
tions are impacted because the
array is already in the middle of
a shutdown. The shutdown pro-
ceeds normally.

Known Critical Issues 22

Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-69136 System Manage- Group merge fails if The Snapshot rate limit - Num- Contact HPE Nimble Storage
ment one of the groups ber of snapshots that can be Support.
violates the snap- taken for a given minute - is in-
shot rate limit troduced in 4.x for distributing
snapshot load to the system. If
a group surpasses this snapshot
rate limit in previous NimbleOS
releases, the software update to
4.x is still allowed. However, a
group merge is prevented if the
source or destination array sur-
passes the snapshot rate limit.
The following error message can
be seen during the group merge
validation: INFO: Rate of snap-
shots in the merged group
would be greater than support-
ed snapshot rate. This could oc-
cur if even if the source array
(the array being added to the
existing group) has 0 volumes
or volume collections.

AS-94113 System Manage- Group Management If an attempt is made to create Use unique name when creating
ment service may restart a snapshot collection with same snapshot collection.
due to duplicate the name of an existing snap-
snapshot collection shot collection, an error indicat-
name ing object already exists will be
reported and the Group Manage-
ment service may restart. The
service will recover upon restart.

AS-100254 System Manage- Group Management A system management process Not applicable
ment Service restarts un- can restart when the system is
der heavy load under heavy load. The system
recovers automatically. The Data
service is not affected.

AS-98124 System Manage- Array Management The Array Management service Not applicable
ment service restart dur- may restart due to a race condi-
ing service shut- tion encountered during service
down shutdown. The service will recov-
er after the restart.

AS-87736 System Manage- Software precheck If a software update precheck Contact HPE Nimble Storage
ment failures return fails, in some cases it will return Support for assistance in deter-
generic error mes- only the failure status without mining the cause of the failure.
sage providing additional information
about the cause of the failure.

Known Critical Issues 23

 Known Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-92465 System Manage- Intermittent login There is a possibility of sporadic, Not applicable
ment failures due to Ac- transient, active directory au-
tive directory thentication failures. In these
lookups failures cases, the system will recover on
its own, requiring no user inter-
action.

AS-98194 System Manage- Group Management Group Management may be- Not applicable
ment Services unavail- come unavailable temporarily
able temporarily when a large number of restores
when performing are performed on a volume.
volume restore

AS-95169 System Manage- Graceful shutdown In rare occurrences, a customer- Not applicable
ment takes longer than initiated reboot may cause a
expected kernel reboot on the active con-
troller. This will cause a longer
reboot cycle.

AS-84499 System Manage- Controller may un- Controller may reboot unexpect- Not applicable
ment expectedly restart edly if there is high memory uti-
due to high memo- lization for the java and/or jetty
ry utilization processes on the array.

AS-92379 System Manage- Unable to Filter vol- There is currently no way to fil- Use volume collections to check
ment umes using Syn- ter volumes using Synchronous syncRep volumes, or use other
chronous Replica- Replication within the array GUI. filters to meet the needs
tion

AS-97968 System Manage- Page footer in GUI After performing a bulk update Refresh the page to restore
ment may fail to update operation from the Manage &gt; button functionality.
after bulk update Data Storage &gt; Volumes &gt;
operation volumename &gt; Data Protec-
tion tab in the GUI, the page
footer may not update and pre-
vious button may be unavailable.

Resolved Critical Issues

Resolved Critical Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-119232 Data Service Multiple Data Ser- In rare cases, during fingerprint Contact HPE Nimble Storage
vice restarts during index lookup and merge opera- Support
deduplication fin- tions involving large deduplica-
gerprint operations tion domains, index block refer-
ences can be mishandled. As a
result, the Data Service can go
into a restart loop, which can
lead to extended data unavail-
ability.

Resolved Critical Issues 24

Resolved Issues
There are no resolved issues in NimbleOS version 5.2.1.600

Known Issues
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-111378 Data Service Data Service may A lost wake-up to an operation Not applicable
restart due to may cause the operation block-
health check failure ing the checkpoint which results
in Data Service restart.

AS-108086 Data Service Data Service restart After updating the array to Contact HPE Nimble Storage
while converting in- NimbleOS 4.x.x.x or later, a pro- Support to increase the health
ternal data-struc- cess runs to convert an on-disk check timeout on the array
tures in NimbleOS data-structure specific to Nim-
bleOS by initiating an operation
that walks the existing tree of
this data-structure. In some cas-
es, this operation keeps running
even after the conversion has
completed successfully, leading
to health check timeout. This
results in a Data Service restart.

AS-109218 Data Service Data service may The Data Service may restart Not applicable
restart unexpected- unexpectedly during a read op-
ly eration when decryption and
decompression fails.

AS-74773 Data Service Data Service may A volume that has a chain of at Not applicable
restart during least three branches, common
branch point dele- in replication or snapshot re-
tion store workflows, may trigger
unexpected Data Service
restarts upon branches being
trimmed and deleted.

AS-102001 Data Service Data Service may In rare instances, the Data Ser- Not applicable
restart unexpected- vice may restart when internal
ly due to internal database communication be-
database communi- tween services is not available.
cation The service restarts to restore
the communication between
services.

Resolved Issues 25
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-81863 Data Service Data Service may When RAID is degraded, IO If RAID is degraded for an ex-
restart unexpected- needs to be reconstructed by tended period and Data Service
ly when RAID is in reading from multiple disks, and restarts occur, contact HPE
degraded mode an internal buffer may exhaust Nimble Storage to assess adjust-
its allocated resources. In rare ing allocated buffer resources.
cases when multiple disks are
degraded, the Data Service may
restart unexpectedly.

AS-62942 Data Service Data Service may On CS2XX or CS3XX, the array Reducing the load on the array
restart unexpected- may run out of data pages when is the only known workaround
ly for CS2XX and under a heavy load. This will re- for this issue.
CS3XX arrays when sult in an unexpected Data Ser-
under a heavy load vice restart.

AS-115328 Data Service Data Service When trying to allocate data Contact HPE Nimble Storage
restarts unexpect- pages for many large Fingerprint Support
edly while allocat- Index Hash Table indirect
ing data pages blocks, the process may fail due
to insufficient memory. As a re-
sult, the Data Service may
restart to recover the condition.

AS-120656 Data Service Data Service When trying to allocate data Contact HPE Nimble Storage
restarts unexpect- pages for many large Fingerprint Support
edly while allocat- Index Hash Table indirect
ing data pages blocks, the process may fail due
to insufficient memory. As a re-
sult, the Data Service may
restart to recover the condition.

AS-77117 Data Service File system service In rare instances during offset Not applicable
may restart on up- calculation, the File System ser-
stream array during vice may restart when attempt-
replication or ing to read data for replication.
resync of syn- The service restarts to recover
chronous replica- from the condition.
tion.

AS-115912 Data Service Data service may Software update to NimbleOS Not applicable
restart unexpected- 5.2.1.0 and later triggers an up-
ly date of on-disk data structures.
Under certain rare conditions,
this update could potentially
take a long time and result in a
restart of the Data Service. This
may cause a momentary delay
in IO but should not result in any
significant disruption, as the da-
ta services daemon is designed
to restart efficiently before any
IO timeout can occur.

Known Issues 26
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-102881 Data Service Data Service During NimbleOS metadata Data service will be available af-
Restart due to a sync, in rare instances, the data ter restart.
race condition dur- service may restart unexpected-
ing metadata sync ly. The metadata sync operation
itself wont be affected and the
restart will reset the race condi-
tion; the data service will stabi-
lize after the restart.

AS-70861 Data Service Data Service may The Data Service may restart Contact HPE Nimble Storage
restart due to vol- unexpectedly if the Volume Support
ume manager Manager health check exceeds
health check failure expected time out. The service
restarts to clear the condition.

AS-85848 Data Service Data Service may As part of the file system check- Not applicable
restart unexpected- point process, internal indexes
ly with health check are required to merge to disk.
failure when inter- The health check process uses
nal index data a heartbeat mechanism to deter-
structures take too mine if the merge is making
long to merge progress. Under some circum-
stances, the process performing
the merge of a batch of updates
to the index fails to heartbeat
within a deadline. When that
happens, the Data Service may
restart with a health check fail-
ure.

AS-87108 Data Service Data Service may Under certain conditions, the Not applicable
restart unexpected- Data Service may restart when
ly with VM health a large number of internal index-
check failure due to es merge within a short time-
lock contention. span and when some of these
indexes need to merge multiple
times in the same checkpoint. In
this case, there can be lock con-
tention between operations re-
sponsible for picking what to
merge and operations process-
ing the merge, leading to health
check timeout.

Known Issues 27
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-61877 Data Service Deadlock in Data Under rare circumstances, inter- Not applicable
Service process nal threads in the Data Service
may cause a restart can enter a deadlock when con-
tending on the same set of re-
sources. When the process
health monitor detects this
deadlock, it will force the Data
Service process to restart in or-
der to recover from this situa-
tion.

AS-115204 Data Service Data service may The data services daemon peri- Not applicable
restart unexpected- odically synchronizes its persis-
ly tent in-memory (NVRAM)
structures with its other objects
on flash. This process is required
to complete within a reasonable
amount of time. Under certain
rare conditions, this process can
get delayed and trigger a restart
of the data services daemon.
This can cause a momentary
delay in IO which the daemon
restarts. There should not be
any disruption of IO, since the
daemon is designed to restart
within any IO timeout limits.

AS-112307 Data Service File System Service The File System Service may Not applicable
may restart due to unexpectedly restart because it
memory exhaustion is not able to allocate memory.
This can happen when the pro-
cess in charge of evicting data
out of cache cannot evict fast
enough, so the filesystem is un-
able to allocate memory for new
incoming data.

AS-111353 Data Service Multi-array setup In certain multi-array setup Not applicable
with replication where replication is in progress
might experience might encounter a situation
file system restarts where peer array is going
when peer array is through a software upgrade and
unreachable is actually unreachable by other
array. The other array is howev-
er unaware of it because some
network device has intervened
the reachability status of the
peer array. The other array
needs to perform certain opera-
tions which has a timeout associ-
ated with it and undergoes a
system restart to recover.

Known Issues 28
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-71309 Data Service Unexpected Data Under certain circumstances, an Not applicable
Service Restart unexpected Data Service restart
may be triggered with a generic
Asynchronous Task Manager
health check failure. The Data
Service restarts and resumes
operation normally, without
causing loss of access from the
connected hosts.

AS-77921 Data Service Data Service may Data Service may restart when None
restart when gather- gathering garbage collection
ing garbage collec- telemetry if cache subsystem is
tion telemetry not fully initialized.

AS-84426 Data Service Group Data Service The Group Data service may Not applicable
may restart unex- restart unexpectedly when out
pectedly of memory condition is encoun-
tered. The service restarts to
clear the condition.

AS-116064 Data Service Data Service may While the Data service is process- Not applicable
restart due to ing Update Entries in back-
health check failure ground, one of these back-
ground operations may exceed
the expected timeout and the
service will restart to recover.

AS-96703 Data Service Data Service may Generation delete loads a large Not Applicable, the Data Service
restart due to vol- number of ondisk metadata will resume normal operation
ume manager blocks which may prevent block after restart.
health check failure index operation checkpoint from
during generation finishing. This causes the volume
deletion manager health check to fail
which results in Data Service
restart.

AS-96779 Data Service Data Service may When a read op finds partial da- Not applicable
restart unexpected- ta in-core, it issues a media read
ly due to race condi- to get remaining data. By the
tion time, media read returns, the in-
core data is synced, and tree is
reopened for deletion. The read
does not expect tree to be in
delete state and causes the Data
Service to restart.

AS-94473 Data Service Data Service may When flash cache Garbage Col- Contact Nimble Storage Support.
restart when run- lection copies forward live data
ning out of buffers of a fragmented segment, it
could consume more buffers
than provisioned and cause the
Data Service to restart to recov-
er.

Known Issues 29
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-108519 Data Service File system restart Due to issues in communicating Not applicable.
to recover from with the partner array during
stalled replication replication, there are few cases
where the operation is not able
to make progress. As a result,
the file system may restart to
correct this condition.

AS-111347 Data Service Data service may While committing internal Not applicable
restart due to a transactions, Data Service may
race condition hit a rare race condition. To re-
cover from this Data Service
may restart.

AS-98979 Data Service Data service may While committing internal Not applicable
restart due to a transactions, Data Service may
race condition hit a rare race condition. To re-
cover from this Data Service
might restart

AS-81739 Data Service Data Service restart If IO to disk are slow or fail, the Not applicable
due to slow disk IO Data Service may restart to try
or disk IO failure to recover the condition.

AS-92170 Data Service Data Service can Due to a race condition, the Data Not applicable
restart unexpected- Service may restart during a
ly during shutdown graceful shutdown causing unex-
process pected Data Services restart
messages to be generated. This
should not cause any I/O impact
because the Data Service is al-
ready in the process of shutting
down.

AS-50446 Data Service Data Service may During replication, a rare race Pause replication until the net-
restart during inter- condition between adding and work link used for replication is
nal task scheduling deleting internal recurring tasks stabilized.
can cause a Data Service restart.
Arrays that hit this condition
typically experience a single
service restart that automatical-
ly recovers the condition. How-
ever, if the network link used by
replication is unstable, frequent
replication disconnects dramati-
cally increase the likelihood of
encountering multiple Data Ser-
vice restarts due to this condi-
tion.

Known Issues 30
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-106924 Data Service Data Service may In rare cases, Data Service may Not applicable
restart due to net- restart during snapshot replica-
work errors tion due to the failure of check-
sum algorithms to detect all
network errors.

AS-113537 Data Service Data Service may The Data Service may restart Not applicable
restart unexpected- unexpectedly if Fibre Channel
ly session termination exceeds
timeout to complete. The service
restarts to recover from the
condition.

AS-97038 Data Service Disabling encryp- Disabling encryption might Enabling encryption will resolve
tion may cause cause NVRAM data to fill up the issue
Synchronous Repli- with data waiting for master
cated volumes to passphrase, which can cause
remain out of sync Synchronous Replicated vol-
umes to go out of sync.

AS-105551 Data Service Arrays may experi- Copy offload optimizations for Perform one of the following
ence increased la- deduplication were added in options to avoid/mitigate the is-
tency during copy NimbleOS versions 5.1.x and sue: 1. Reduce overall workload
offload workload later. The changes may lead to on the array. 2. Reduce copy of-
operations increased latency when copy of- fload workload on the array.
fload workflows are added to the Contact HPE Nimble Storage
array. This is due to an increase Support if further assistance is
in update entries requiring pro- needed.
cessing.

AS-98217 Data Service Data service may Volume manager does not reset The array will continue to shut-
restart during array internal callbacks during the down after the Data service
shutdown shutdown phase causing the restart.
Data service to restart.

AS-94196 Data Service Data Service may The Data Service may restart Not applicable
restart during array during array shutdown when
shutdown jobs related to the Data Service
are unable to be gracefully
shutdown. The restart should
not have any impact as the array
is in shutdown process.

AS-79265 Data Service Data Service may The volume manager will decre- Not applicable
restart on down- ment bin and child volume folder
stream array due to entries during volume deletion.
race condition dur- In rare occurrences, another
ing volume deletion thread may decrement the child
volume entry and not the bin
entry, causing the Data service
to restart.

Known Issues 31
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-57016 Data Service Aggressive assert Under certain circumstances, an Not applicable
may lead to unex- aggressive internal assert may
pected restart of lead to unexpected restart of the
the Data Service Data Service.

AS-110167 Data Service Attribute synchro- The Group Management service No action is required, the alert
nization may be de- synchronizes attributes with the should resolve a short time later.
layed Data Service on the array. If the
Data Service does not send a
response within 10 seconds, the
Group Management service will
generate an alert indicating the
attribute synchronization may
be delayed. The service will retry
the synchronization, and it will
complete a short time later when
the response from the Data Ser-
vice has been received.

AS-101386 Data Service Data Service restart A rare scenario can result into a None. The Data Service Restart
due to a race condi- race condition between clone would resume normal I/O opera-
tion creation and I/O operations on tions.
an encrypted volume; during this
time while fetching the encryp-
tion keys Data Service may
restart and resume normal I/O
operations.

AS-94545 Data Service Very rare race be- The service may restart when Remove downstream replica us-
tween Vol claim removing the downstream repli- ing the correct steps ordered
(with all snapshots ca using the steps below. &nbsp; below. &nbsp; 1. Claim the repli-
marked for dele- 1. Deletion of all snapshots for ca volume. 2. Delete all of the
tion) and space re- the replica volume. 2. Claim the snapshots for the replica vol-
calculation on repli- replica volume 3. Delete the ume. 3. Delete the replica vol-
ca downstream vol- replica volume ume.
ume

AS-86720 Data Service Unassigning and Assigning an array to a pool im- Retry operation after a few min-
reassigning array to mediately after unassigning it utes to reassign array to pool.
a pool within 5 min- from the same pool will fail with
utes will fail the following error - Failed to
assign arrays to the pool: A ser-
vice is not running or is not
reachable

AS-85304 Data Service Data Service may The Data Service on the array Not applicable
restart due to communicates with the Group
health check failure Management Service to handle
array operations. If the commu-
nication between the two ser-
vices exceeds timeout, the ser-
vice will restart to recover.

Known Issues 32
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-111454 Data Service Aggressive Volume Aggressive volume creation and Reduce the frequency of volume
creation and dele- deletion may cause one of the clone create and delete opera-
tion may result in tree data structures to hit maxi- tions to minimize the likelihood
Data Service restart mum children it can have. This of occurrence.
limit can occur on volume cre-
ation because volume deletion
destroys the children asyn-
chronously. The Data Service will
restart when this limit has been
reached.

AS-113545 Host Integration Group Management The Group Management service Not applicable
service may restart communicates with the VSS ser-
when attempting to vice when creating VSS snap-
create VSS snap- shots. If this communication is
shot not able to be completed within
the expected timeframe, the
service restarts to recover.

AS-108647 Host Integration Cimserver stops In some instances the cimserver Contact HPE Nimble Storage
when memory limit service will exceed its memory Support to increase the memory
is exceeded. limit and no longer be able to limit for the service.
start.

AS-50033 Platform Log partition may Log files generated by processes Contact Nimble Storage Support
fill up in the Nimble Operating systems to identify the reason for the
are rotated and archived using partition filling up and to clean
certain parameters. Under some up the log partition.
conditions, if processes log more
than normal, this can result in
the log partitions being filled up,
leading to other issues with crit-
ical processes.

AS-107299 Platform Replacement con- During controller boot, firmware Contact HPE Nimble Storage
troller fails to boot update may fail to complete Support
to NimbleOS causing the controller to boot to
maintenance mode.

AS-53621 Platform Both power sup- Under certain circumstances, in- 1. Reseat one of the power sup-
plies showing up as ternal commands may cause the plies to clear the hang condition.
missing integrated circuit to hang which 2. Or update NimbleOS to ver-
causes both power supplies of sion 3.6.0.0 or later to minimize
the head shelf to appear as the number of internal com-
missing. The problem does not mands that can trigger this is-
impact the power supplys ability sue.
to deliver power to the array.

AS-100088 Platform Controller does not In rare incidents, controllers do Please contact HPE Nimble
power on following not power on following power Storage Support
a power cycle. cycle.

Known Issues 33
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-67242 Platform Incorrect shelf ca- If a shelf is cabled incorrectly Referencing the corresponding
bling can cause a and added to an array, the raw Expansion Shelf Quick Start
series of unexpect- capacity calculation could fail Guide, correct the hardware ca-
ed Data Service leading to multiple restarts of bling issue.
restarts the Data Service.

AS-33725 Platform Unexpected con- When the SAS HBA detects The controller reboot should re-
troller takeover due faulty states, to recover, the ar- store SAS HBA to normal state.
to incorrect state of ray needs to reset the SAS HPE Nimble Support may con-
the SAS HBA HBA’s firmware. The SAS HBA tact customer to collect addition-
firmware reset can block disk al diagnostics if required.
I/Os significantly longer than our
High Availability monitoring
timeouts allow. Instead, a con-
troller reboot is triggered imme-
diately if this state is detected,
resulting in an unexpected
takeover event.

AS-114564 Platform File System service In certain conditions, I/Os Not applicable
may be restart on tracked for certain operations
truncated variable may total zero, which triggers a
read check exception. The reason for
the incorrect value is variable
truncation. The service restarts
to recover from the condition.

AS-90850 Platform Data Service may The Data Service may restart Not applicable
unexpectedly unexpectedly when it detects an
restart internal check error. The restart
of the service clears the condi-
tion.

AS-95294 Platform Enclosure Manage- The Enclosure Management Not applicable

ment service may service may unexpectedly
unexpectedly restart due to a race condition
restart due to drive which is resulting from drive
status race condi- status which has already been
tion marked removed by the Data
Service. The restart of the ser-
vice clears the condition.

AS-110036 Platform Data Service may Data Service may become latent Contact HPE Nimble Storage
restart if the array and restart when the array has Support to identify the faulty
has an faulty drive a faulty drive with a lot of medi- drive for replacement.
with a high number um read and IO timeout errors.
of medium read er-
rors

Known Issues 34
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-90096 Platform Data Service In rare instances due to slow IO Please contact HPE Nimble
restarts due to slow to one of the disks, the Data Storage Support so the problem-
IO to one of the Service may hit a timeout and atic drive can be replaced.
disks restart unexpectedly. This issue
may occur during a NimbleOS
software update.

AS-99567 Platform Data Service may Data Service may restart in the The restart of the service will
restart if a con- rare case when a controller is clear the low memory condition,
troller is low on low on memory. no further action is needed.
memory

AS-113002 Platform Data Service may In rare circumstances, the arrays Not applicable
restart unexpected- data service may restart unex-
ly during internal pectedly when it encounters a
striping operation race condition following internal
data striping processing. The
data service will stabilize follow-
ing the restart.

AS-103802 Platform Data Service restart The Data Service may restart Not applicable
due to resource allo- due to a transient resource allo-
cation failure. cation failure. This happens
when the service cannot com-
plete a disk IO due to transient
memory allocation failure. This
does not cause a service outage
as Data service continues normal-
ly after a restart.

AS-116155 Platform Kernel memory In rare circumstances, a kernel Not applicable

management de- memory management defect
fect may cause an may manifest itself during
unexpected memory unmapping operations
takeover and initiate a controller reboot.
If this occurs on the active con-
troller, it will result in an unex-
pected takeover.

AS-46629 Platform Kernel panics while On very rare occasions of HBA Not applicable
processing host bus error handling, interrupts could
adapter errors be turned off long enough for
the NVRAM driver to timeout
while trying to complete direct
memory access operations. The
controller recovers after a re-
boot is initiated by the kernel.

AS-116189 Platform Kernel file system In rare circumstances, a kernel Not applicable
defect may cause file system defect may manifest
an unexpected itself and cause a controller re-
takeover boot. If this occurs on the active
controller, it will result in an un-
expected takeover on the array.

Known Issues 35
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-117809 Platform Array Management Due to an incorrect response Contact HPE Nimble Storage
service may restart from dual flash carrier (DFC) Support.
unexpectedly firmware the Array Management
Service might restart intermit-
tently.

AS-105053 Platform Enclosure Manage- The Enclosure Management Not applicable

ment Service may service may unexpectedly
restart unexpected- restart when it detects an inter-
ly nal check error. The service
restart clears the condition.

AS-101570 Platform Delay with Data On rare occasions, the array No workaround is required. The
Service starting groups Data Service may fail to array will recover itself automat-
during shelf state initialize if a shelf state change ically by restarting the Data
change occurs simultaneously. Service.

AS-93296 Platform Data service may ES2 and AFS2 expansion Review the array configuration
restart if maximum shelves contain additional slots matrix for the array model: <a
cache exceeded for for upgrading cache capacity of href=https://infos-
CS215, CS235, the array. Older array models ight.hpe.com/InfoSight/media/lo-
CS300, CS500, have a maximum cache limit that cal/active/34/CSxxx%20Con-
CS700 arrays can be handled by the array. If fig%20Matrix.pdf>https://infos-
ES2 or AFS2 expansion shelves ight.hpe.com/InfoSight/media/lo-
are added to an array and the cal/active/34/CSxxx%20Con-
cache exceeds the max cache fig%20Matrix.pdf</a> Remove
limit for the array type, the data any additional cache from the
service may restart due to run- expansion shelf that exceeds the
ning out of data pages. max cache limit based on array
model.

AS-99428 Platform Replacement disk Disk will report foreign for disk Add the disk from the CLI using
reports foreign for state in the GUI Hardware page the disk add command and out-
disk state in or in the output of disk --list put from disk list: 1. Run disk --
GUI/CLI from the CLI. This typically oc- list 2. Note the slot number, and
curs if diagnostic data may not shelf location for the disk la-
have been removed after test- beled foreign. 3. Add the disk:
ing. disk --add &lt;slot number&gt; -
-array &lt;arrayname&gt; --
shelf_location &lt;shelf loca-
tion&gt; Note: the --force option
may be required Contact HPE
Nimble Storage Support if the
disk does not move to resynchro-
nizing state after completing the
commands.

Known Issues 36
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-91522 Platform SSD has reached its In rare cases, an SSD may reach Not applicable
endurance limit its endurance limit but continues
(wear leveling) but to pass Nimble Drive Error Re-
the disk is not covery algorithm. This causes a
marked failed. never-ending process of off-lin-
ing and on-lining the drive. This
may occur for Intel and Toshiba
SSDs.

AS-86100 Platform Enclosure Manage- In a rare scenario, Enclosure Not applicable

ment service occa- Management service may occa-
sionally restarts up- sionally restart upon a drive
on a drive failure failure in system partitions. The
restart of the service clears the
condition.

AS-116339 Platform 4U Chassis disk slot Due to a possible software de- Not applicable
LEDs illuminate er- fect, the red disk slot LED may
roneously illuminate even when there are
no issues with the corresponding
drive. This is a cosmetic issue
that does not impact functional-
ity.

AS-112701 Platform Group Management The Group Management service Not applicable
service may restart may restart if an error while
unexpectedly opening interconnect-ips file
occurs. The service restarts to
recover from the condition.

AS-116111 Platform File System Service The File System Service may Not applicable
restarted unexpect- restart during memory allocation
edly if there is not enough memory
available. The service restarts to
recover from the condition.

AS-98885 Platform Unexpected Group The Group Management Service Not applicable
Management Ser- may restart unexpectedly due
vice restart due to to receive buffer exhaustion on
receive buffer ex- the management network inter-
haustion face. No visible impact has been
reported because of this issue.

AS-92471 Platform File System Service File System service may restart Not applicable
may restart unex- unexpectedly when a health
pectedly check exceeds timeout for vol-
ume manager on the array. The
service restarts to recover from
the condition.

Known Issues 37
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-114390 Platform Array may fail to Under rare circumstances, if an Contact HPE Nimble Storage
boot following a array software update previous- Support
software update if ly failed and reverted, and an
previous chassis in- array chassis swap is performed
formation is refer- before the next software update,
enced the array configuration files may
contain invalid data. This will
cause the controllers to reboot
and the Array Management ser-
vice to restart.

AS-76174 Platform VM creation fails in An attempt to create new VMs Please contact HPE Nimble
VMWare VVol envi- in a VMWare vVol environment Storage Support to resolve this
ronment after up- fails after updating to NimbleOS issue. This issue is resolved in
date to NimbleOS 4.x.x.x. This occurs when a sys- NimbleOS version 5.0.2.0 and
4.x.x.x tem partition within the array is later.
running out of space.

AS-103315 dHCI dHCI update work- As part of the dHCI update Free up /var disk space by
flow can fail if /var workflow which involves the ES- deleting unwanted log files
mountpoint on the Xi server update, some com- (/var/log/EMU/mili/mili2d.log)
host is full. mands need to be run on the and rebooting the host.
server. Running these com-
mands fails with error Error: A
general system error occurred:
Internal error. if the /var is full.
This is a known issue with 6.7
builds running with Emulex
driver which has been fixed as
part of ESX 6.7 U2. <a
href=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>

AS-103247 dHCI An in-progess dHCI When the dHCI unified update The only way to resume the up-
update fails if the feature is used to update the date would be to failover to the
group leader fails dHCI stack, the update will fail original group leader array and
over if a Group Leader Failover oc- then resuming the update
curs during the process. through the dHCI vCenter plug-
in.

AS-97685 dHCI Nimble Add If an array failover occurs while After confirming the array has
ProStack server Nimble Add ProStack server task returned to Active/Standby sta-
task may hang if is running from vCenter, the tus, stop the hung task and run
array failover oc- process may hang and not com- the Nimble Add ProStack server
curs plete. task again.

Known Issues 38
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-103769 dHCI The update page When an ESXi server is added to Not applicable
on the dHCI plugin dHCI cluster, the update page
takes 4 hours to re- does not get updated to include
fresh the newly added ESXi server.
This refresh happens every 4
hours. After the next refresh, the
new ESXi servers version will be
included and accounted for on
the update page.

AS-95054 dHCI Addition of a server When adding a server with an A valid ESXi license must be as-
with expired ESXi expired ESXi license to the dHCI signed to the server.
license fails cluster, through the vCenter
plugin, you may see an error
saying - Failed to submit a task
to add server.

AS-101915 dHCI dHCI update fails For ESXi server update, DRS is Admission Control should be
when Admission used to migrate VMs running on disabled on a dHCI cluster for
Control is enabled the server. If admission control the update to proceed.
is enabled on the dHCI cluster,
DRS is not able to migrate VMs
off a server.

AS-108946 SAN Data Service may The Data service will wait up to Not applicable
restart when host 300 seconds for host response
does not issue to iSCSI commands. If host does
abort to timed out not abort commands that take
command more than 300 seconds to com-
plete, the Data service will
restart.

AS-100197 SAN Data Service restart During a controller reboot, due Not applicable.
during shutting to resource contention between
down FC service on new Fibre Channel (FC) connec-
the standby con- tion attempts and shutdown of
troller the FC module, the Data Service
on the array may restart unex-
pectedly.

Known Issues 39
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-94229 SAN Fibre Channel IO The Fibre Channel driver state These issues appear to be trig-
aborts and hangs machine that handles IO aborts, gered by events external to the
may lead to DSD or IO timeouts on the fabric, ses- controller such as host HBA, ca-
kernel crash sion logout, and port ownership ble, SFP, zoning or switch issues.
changes relies heavily on the Port congestion may also play a
port owner to properly manage role. Migrating volumes to other
state in a timely manner. This arrays or adding additional
generally works, but there are HBAs may alleviate the conges-
situations where the port owner tion.
doesnt have enough context to
do the job properly. This can
lead to more IO timeouts, HBA
resets, DSD restarts and occa-
sionally kernel crashes. A future
version of the driver will simplify
this process by handling it entire-
ly within the driver.

AS-92368 SAN Data Service, SCSI During port owner failover be- Not applicable
Failover/Forward tween the Data Service and the
Service, and/or SCSI Failover/Forward Service,
controller may outstanding IOs may timeout
restart unexpected- and get aborted. This can lead
ly for Fibre Channel to state machine issues in be-
arrays tween the two services which
may cause one or both services
to restart. In rare instances, this
may also cause the controller to
reboot. The service restart
and/or controller reboots to re-
cover from the condition.

AS-109412 SAN NimbleOS services Logins to CHAP authentication Identify the offline volumes or
may restart unex- enabled volumes could leak a stale targets and initiate a host
pectedly due to small amount of memory the side cleanup/rescan to avoid re-
slow leak with size of CHAP username. Over a peated login attempts and fail-
CHAP logins period of days and weeks, this ure to the offline or stale targets.
leak can result in one or more of
the NimbleOS processes running
out 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 or
stale targets.

Known Issues 40
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-113037 SAN NimbleOS services Logins to CHAP authentication Identify the offline volumes or
may restart unex- enabled volumes could leak a stale targets and initiate a host
pectedly due to small amount of memory by re- side cleanup/rescan to avoid re-
memory leak in lo- peated failed login attempts to peated login attempts and fail-
gin path offline volumes or stale targets. ure to the offline or stale targets.
Over a period of days and
weeks, this leak can result in one
or more of the NimbleOS pro-
cesses running out of memory.
As a result, NimbleOS services
may restart unexpectedly.

AS-111926 SAN Poor iSCSI perfor- The NCM (Nimble Connection Increase NCMs configuration for
mance seen when Manager) handles the iSCSI minimum number of connections
minimum connec- connection counts. Today, the per volume from 2 to 4 or high-
tion count is used NCM is designed to use a FULL er.
MESH connection mechanism.
However, when there are very
few initiators and target ports,
the total connection count will
be minimal. The NCM will default
to a minimum of 2 connections
per volume. Increasing the num-
ber of connections to 4 or more
may produce the maximum
throughput.

AS-98042 SAN The Data Service When the active controller is Not applicable
restarts unexpect- being shutdown, the Data Ser-
edly during shut- vice runs into an internal error
down condition that causes the service
to restart unexpectedly. Since
the process is already being
shutdown, there is no impact to
user data availability.

AS-64790 SAN Data Service may When the Data Service is in pro- Not applicable
restart due to race cess of shutdown, the service
condition may restart due to race condi-
tion when shutdown threads do
not wait or abort pending opera-
tion threads.

AS-89753 SAN Service may restart The Data Service or SCSI High Not applicable
due to race condi- Availability Service may restart
tion due to race condition encoun-
tered during process shutdown.

Known Issues 41
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-101325 SAN Data Service may Under certain conditions, the Not applicable
restart unexpected- Data Service on the Group
ly while removing Leader array may restart unex-
member array pectedly while removing mem-
ber array. This is due to a race
condition when processing SCSI
RTPG (REPORT TARGET PORT
GROUPS) commands. The ser-
vice should stabilize on its own
shortly following the restart.

AS-94761 SAN File System service This scenario is rare to happen Not Applicable
may restart when but presently not handled
an invalid write re- gracefully leading to a File Sys-
quest is received 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) value
in Data-Out Buffer.

AS-116512 System Manage- Cannot take a In certain scenarios, off-lining a Contact HPE Nimble Storage
ment bound virtual vol- vVol snapshot will not complete Support
ume snapshot of- due to the existence of a ACL
fline bound with it. The vVol snap-
shot cannot be off-lined until the
bound ACL has been removed.

AS-110367 System Manage- Group Management A race condition may occur while Not applicable
ment service may restart updating records in the Scale
due to race condi- Out database when two threads
tion attempt to update the same
record.

AS-103766 System Manage- Group Management Group Management Service may Not applicable
ment Service may restart restart unexpectedly as one
due to race condi- thread has taken a ReadWrite
tion lock which has another writer
thread, which is waiting for
Scale-Out Database (SODB)
transaction to be completed.
The service restarts due to the
SODB transaction exceeding the
expected timeout.

AS-105929 System Manage- Group Management Group Management service may Not applicable
ment Service restart due restart due to Volume Manage-
to race condition ment thread and API thread for
snapshot creation/deletion en-
tered race condition. The service
recovers after restart.

Known Issues 42
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-54302 System Manage- REST API Clone of When created with the REST Not applicable
ment volume does not API, by default the cloned vol-
support setting ume inherits the ACL from the
ACL at time of parent volume. There is no way
clone creation to set or change the ACL for the
clone at the time of creation
through the REST API. Clients
should make two REST calls, one
to create the clone and then one
to change the ACL to the de-
sired value. In the future, we
could change the REST API to
not set the ACL by default and
allow the client to set the ACL
at the time of the clone creation
to the desired value. This only
applies to volumes that have
agent_type set to none

AS-119873 System Manage- Group Management The Group Management service Contact HPE Nimble Storage
ment service may restart communicates with the Data Support
while reading proto- Service to add the Protocol
col endpoint infor- Endpoint ACL to the Scale Out
mation Database for vVols. If the pro-
cess does not complete as ex-
pected the Group Management
service will attempt to retry the
operation. Under some circum-
stances, instead of retrying that
operation, this ACL get erro-
neously deleted and any PE
reads (REST or cli) following
could result in GMD restart.

AS-83604 System Manage- Event service may API calls occur between the Not applicable
ment restart unexpected- Event service and Group Man-
ly agement service when an alarm
is cleared. The calls will lookup
the alarm ID and onset event in
the Scale Out Database (SODB).
If the alarm is cleared before the
onset event lookup completes
and is not found during these
calls, the service may restart
unexpectedly.

Known Issues 43
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-94398 System Manage- Alarm may not Due to a race condition it is The problematic alarm can be
ment clear as expected possible for an alarm to remain manually deleted through the
uncleared on the system even CLI command: alarm --delete
when the alarm condition it is &lt;alarm_id&gt;
reporting is no longer the case.
This can happen if the onset
alert and recovery alert were
generated at close to the same
time.

AS-105431 System Manage- Alarm IDs in alarm Due to the multi-threaded na- Not applicable
ment list may appear out ture of the Alerts and Alarms
of order. Service, it is possible for an
event with a later id to be post-
ed prior to an event with an ear-
lier id. Therefore it will have an
earlier timestamp even though
its ID is higher. This can cause
the IDs to appear out of order.
However, the alarms in the list
are ordered correctly by times-
tamp.

AS-99427 System Manage- Alarms for Configu- Alarms describing a delayed After confirming that the config-
ment ration Synchroniza- configuration synchronization uration sync has completed the
tion may remain af- to an array may not be cleared alarms can be deleted or ac-
ter sync has com- properly after an extended net- knowledged through the GUI.
pleted work outage and remain active
in the GUI.

AS-87604 System Manage- Configuration syn- An alarm onset should be set Clear the alarm manually from
ment chronization recov- prior to discovery request as the Command Line Interface: 1.
ery alarm is not part of alarm processing. In Use alarm --list command to de-
cleared some cases the discovery re- termine the alarm ID. 2. Use
quest will appear first resulting alarm --delete &lt;ID&gt; com-
in the alarm not being cleared. mand to delete the alarm.

AS-103567 System Manage- Eventd process The Eventd process may restart Not applicable
ment may restart unex- unexpectedly due to a rare
pectedly deadlock condition between its
threads. The restart of the pro-
cess will clear the condition.

AS-84502 System Manage- Event Service Event Service may restart when Not applicable
ment restarts due to memory limit is reached. The
memory service will restart to recover
from the condition.

AS-101273 System Manage- Event Management When an alert is raised on one Rename the folders to be
ment service restart of two folders having the same unique. If the Event Manage-
when two folders in name but are located in two ment service continues to restart
different pools separate pools, the Event Man- or remains unavailable, contact
have the same agement service may restart re- HPE Nimble Storage Support.
name peatedly.

Known Issues 44
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-85608 System Manage- The Event service The Event service may restart Not applicable
ment may restart unex- unexpectedly due to a memory
pectedly access issue. The restart will not
impact data connections to the
array and the process will recov-
er after the restart.

AS-99679 System Manage- Eventd process The eventd process may restart Not applicable
ment may restart due to unexpectedly in systems with
exceeding memory larger configurations due to ex-
limit ceeding memory limit. The ser-
vice will recover after the restart.

AS-86837 System Manage- Snapshot Attribute Alarm notifying about delay in The alarm can be cleared from
ment Synchronization snapshot attribute synchroniza- the CLI using the steps below.
Delay Alarm is not tion is not cleared automatically List the alarms with the follow-
cleared after successful synchronization. ing command to obtain the
If the alarm is not manually alarm ID: alarm --list Delete the
deleted it will keep reminding alarm using the alarm ID ob-
the customer even after success- tained from the list. alarm --
ful synchronization. delete &lt;alarmID&gt;

AS-50821 System Manage- Alerts and Alarms Alerts and Alarms processing Not applicable
ment processing service service may restart unexpected-
may restart unex- ly when certain operation sur-
pectedly pass the designated health
check timeout. The process will
stabilize following the restart.

AS-46024 System Manage- Eventd process The Eventd process may infre- Not applicable
ment may restart inter- quently crash, due to a bug in an
mittently external library used by the DNS
resolver. The restart will not im-
pact data connections to the ar-
ray and the process will recover
after the restart.

AS-40238 System Manage- Event Service may The array will reuse the session Not applicable
ment report SMTP failure to the SMTP server each time it
to send alert when attempts to send an email. If this
alert is sent success- session is no longer active, it will
fully report a failure to send the alert,
then open a new session, and
successfully send the alert if the
SMTP server configuration is
valid.

Known Issues 45
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-72902 System Manage- Alerts sent via When the array sends an alert The recipient can create an in-
ment SMTP may be re- via SMTP, the message may be bound transport rule to append
jected rejected by the server indicating a disclaimer to the messages
550 5.6.11 SMTPSEND.BareLine- from the problematic sender.
feedsAreIllegal. This can occur The disclaimer will append the
if the receiving server does not expected CR-LF combination to
support BDAT command for the message so that it can be
SMTP chunking delivered. (This disclaimer may
consist of a single character
such as a period or a dash.)

AS-110436 System Manage- Array Management Internal database maintenance Not applicable
ment service may restart processing may exceed the ex-
unexpectedly pected health check timeout.
When this occurs, the Array
Management service may restart
to recover from the condition.

AS-96966 System Manage- Purge inactive en- Every night, when inactive keys Not applicable
ment crypted keys ap- for deleted encrypted volume
pears in audit log. are deleted by the array, it cre-
ates an audit log entry with root
as the user performing the ac-
tion.

AS-82919 System Manage- Group Management An excessively long username The Group Management service
ment Service restarts due of over 255 characters will ex- will recover after the crash. The
to excessively long ceed a character limit within the workaround would be to no
username array groups auditing frame- longer use an excessively long
work. This would cause the username, and reduce the user-
Group Management service to name to under 255 characters.
restart unexpectedly.

AS-71090 System Manage- No Audit Log entry If a user tries to create a new Not applicable
ment is created if user user account, but the user does-
does not have the nt have the privilege to do so,
privilege to create the user creation will fail. Howev-
user er, an audit log entry is not cre-
ated.

AS-116083 System Manage- Array Management The Array Management Service Not applicable
ment Service restart process may restart after run-
ning for a long time due to a
memory leak issue. This can
cause a short interruption to
data service, but it will resume
once the process has restarted.

Known Issues 46
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-104640 System Manage- Group Management The Group Management Service Not applicable
ment Service restarts fol- on the array may restart unex-
lowing volume cre- pectedly when a SOAP timeout
ation timeout is encountered after trying to
create a volume. This occurs due
to a race condition where the
array attempts to delete the
volume after the creation at-
tempt fails.

AS-112416 System Manage- GUI performance The GUI relies on REST queries Contact HPE Nimble Storage
ment may be slow for Fi- to obtain FC session information. Support
bre Channel (FC) In environments where there are
arrays with high high number of sessions to the
session count array, the queries can take a
long time to complete. This will
result in slower GUI response for
the array.

AS-104185 System Manage- Group Management When autosupport configuration Perform the Autosupport valida-
ment service may restart validation is performed, internal tion process again.
when performing process tracking may abort
Autosupport Valida- causing the Group Management
tion Service to restart.

AS-115935 System Manage- Array removal will This issue is seen when the Not applicable
ment fail if Backup Group Group Leader role migration
Leader setup is in completes, and the previous
progress leader is left unconfigured. In
this scenario, the Group Leader
may treat the previous leader as
a member array and initiate the
Backup Group Leader (BGL)
setup. If a customer attempts to
remove the array during this
BGL setup, the removal fails.

AS-109127 System Manage- Group Management Connection to the Scale-Out Not applicable
ment service may restart Database can not be reinitialized
when connections when a transaction is in
to Scale-Out progress. The Group Manage-
Database exceeds ment Service will restart to re-
threshold value store connection.

Known Issues 47
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-105454 System Manage- Group Management During key value metadata han- Not applicable
ment service may restart dling, the process may delete
due to snapshot primary keys in one table of the
key value metadata Scale-Out Database (SODB) and
handling then try to reference the deleted
primary key as foreign key in
another table in SODB. This
causes foreign key violations in
Postgres and eventually leads
the Group Management service
to restart.

AS-117328 System Manage- System Manage- In rare scenarios a System Man- Not applicable
ment ment service may agement Service may restart af-
restart after Soft- ter Software Update. System
ware Update Management Services such as
array GUI information may be
unavailable for a brief period of
time after Software Update.

AS-115493 System Manage- During a planned Under certain circumstances, the Not applicable
ment shutdown, the Ar- Array Management Service may
ray Management detect operations that are still
Service may restart running during a planned shut-
down. This may result in an un-
expected service restart prior to
the array completing shutdown.

AS-99704 System Manage- group --status CLI If there is a network connectivity Not applicable
ment output shows incor- issue between the witness and
rect Failover Mode Group Leader array, the group
during network status CLI output will update the
connectivity issues Failover Mode from Automatic
to Manual until the connection
is reestablished. It also displays
the Witness Status as N/A as
opposed to Unreachable.

AS-94683 System Manage- Network isolation In Automatic Switchover environ- No workaround is needed. The
ment of the Group Lead- ments, in rare instances, network service recovers on its own.
er and Backup isolation of the Group Leader
Group Leader array and Backup Group Leader may
may lead to Auto- cause the service that handles
matic Switchover the automatic switchovers to
service restarts restart unexpectedly.

Known Issues 48
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-94649 System Manage- Peer Persistence During software update of array Not applicable
ment Automatic group with Peer Persistence
Switchover (ASO) configuration, Automatic
is disabled during Switchover (ASO) is disabled. If
software update an array goes down (both con-
trollers down) during the soft-
ware update process, due to a
power failure or other unexpect-
ed event, hosts could lose access
to data until the failed array re-
covers, or a manual switchover
of the affected volumes is done.

AS-98953 System Manage- Array Management The arrays database system may This restart is non-disruptive to
ment Service restarts become unavailable for a limited the data on the array, and the
during Backup time when there is a failure in Array Management recovers af-
Group Leader dis- setting up the Backup Group ter the restart occurs.
covery Leader. When attempting to
discover a new Backup Group
Leader, the Array Management
Service may restart due to a race
condition.

AS-106539 System Manage- Array Management Due to a race condition, the Ar- None.
ment Service may restart ray Management service may
during array shut- restart when the array is in the
down process of shutting down all
services as part of the array
shutdown. An alert and a pro-
cess core could be generated as
a result but there is no impact
to functionality. Once the array
powers back on, all services start
up normally.

AS-101342 System Manage- Group limits com- The array group CLI command Not applicable
ment mand lists internal with limits option (group --list-
identifiers limits) displays numeric internal
identifiers as part of the informa-
tion listed for the volume infor-
mation. These numeric identi-
fiers are used by the array only
and can be ignored.

AS-103275 System Manage- Event Service may The Event service may restart Contact HPE Nimble Storage
ment restart due to in- unexpectedly if an invalid net- Support
valid database en- work interface entry is found in
try the Scale Out Database (SODB).

Known Issues 49
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-104812 System Manage- Array Management The Array Management service Not applicable
ment service restarts due may restart unexpectedly due
to memory alloca- to an a memory allocation failure
tion issue when attempting to synchronize
configuration with a member ar-
ray. The restart of the Array
Management service clears the
situation.

AS-99702 System Manage- Backup Group Following a power outage, it is Please contact HPE Nimble
ment Leader is not as- possible that the Backup Group Support.
signed due to pow- Leader is not assigned to the
er outage group. This may occur if the
SODB database does not start
due to an SSH key issue.

AS-93469 System Manage- Group Management The Group Management service Not applicable
ment service may restart may restart while collecting
while collecting statistics from member array.
member array This can occur when the request
statistics from the group leader to mem-
ber array exceeds timeout,
causing the service to restart to
recover.

AS-73595 System Manage- A lossy network Service threads within the group The only workaround is to im-
ment causes Group Man- management API handler are prove the quality of the network
agement service restricted to run for no more connection so that the loss of
restart than 5 minutes. In a very lossy TCP packets is minimized.
network, TCP throughput can
be throttled to almost nothing
due to retransmission timeout
back-off. In one observed case,
where the API response was
about 190 KB, the connection
managed to send only about 90
KB before the 5 minute timeout
occurred and caused the Group
Management service restart.

AS-53458 System Manage- Interface link alerts The Controller Management Not applicable
ment may fail due to race Service monitors the controller
condition interfaces for network connectiv-
ity. The Array Management Ser-
vice monitors link status to deter-
mine if failover is required due
to network connectivity. Due to
a race condition the Array Man-
agement Service may initiate an
array failover before the Con-
troller Management Service
alerts that interface links are
down.

Known Issues 50
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-98297 System Manage- Array Management There is a memory leak in the If array is queried for statistics,
ment service restart due stat (statistics) component of then its frequency should be re-
to memory alloca- the Array Management service. duced. This is specially relevant
tion exception Magnitude of the memory leak for the setup where script or
is proportional to the frequency some monitoring tool does stats
of stats query. query frequently in a loop.

AS-92515 System Manage- Alarm not cleared If an IP address is migrated from Manually delete the alarm from
ment after IP address one interface port to another, the command line interface. 1.
moves to different the alarm that was generated Login to CLI 2. Find the alarm ID
interface indicating the original interface using: alarm --list 3. Delete the
down may not be cleared. alarm using the ID alarm --delete
&lt;ID&gt;

AS-87749 System Manage- Max limit of 120 When alarm for number of nics The workaround would be to
ment nics in netconfig in array net config reaching 120 delete the alarm using the alarm
alarm does not get is triggered, it doesnt get --delete CLI.
cleared cleared even when the number
of nics goes down.

AS-112702 System Manage- During shutdown Due to an issue in POCO library, Not applicable
ment the Group Manage- in certain cases, causing the
ment service may Group Management service to
unexpectedly restart. The service restarts to
restart recover from the condition.

AS-74556 System Manage- Array Management Array Management Service may Not applicable
ment Service restarted restart unexpectedly when try-
while starting/stop- ing to start or stop the Group
ping Group Manage- Management Service. The sys-
ment Services tem recovers automatically after
the Array Management Service
is restarted

AS-74242 System Manage- Force deletion of There is a --force switch avail- Not applicable
ment user defined perfor- able when deleting a perfor-
mance policy mance policy via the HPE Nim-
should not be sup- ble Storage Array CLI. This --
ported force switch does not work and
will fail with the following: ER-
ROR: Failed to delete perfor-
mance policy. Resource busy.
The --force command is not
supported since the specified
performance policy should not
be removed without first check-
ing its volume or folder associa-
tions.

Known Issues 51
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-101832 System Manage- Volume Migration Volume move operations copy Not applicable
ment estimates may be both data and associated meta-
inaccurate when data from the source array to
multiple volumes destination array. For groups
are being migrated with multi-array pools, copying
the metadata can take a signifi-
cant amount of time, and the
estimate calculation may be inac-
curate initially. These estimates
will auto-correct themselves by
using feedback mechanisms.

AS-117683 System Manage- Array management Backup Group Leader (BGL) Not applicable
ment service may restart may be promoted and/or System
under high load or Management Service may
network connectivi- restart. This occurs when there
ty issues between is high load on either the Group
group arrays Leader array or the BGL array,
or when there is network
throughput issues between the
arrays. The service restarts to
recover from the condition.

AS-116625 System Manage- Array management The Array Management service Not applicable
ment service may restart may restart on a group config-
during periods of ured for high availability during
degraded network various scenarios when Group
connectivity be- Leader to Backup Group Leader
tween high avail- communication is high or degrad-
able Group Leader ed. Scenarios which may cause
and Backup Group an array management service
Leader arrays. restart include degraded net-
work connectivity between GL
and BGL arrays.

AS-94835 System Manage- Array Management Array Management services may Not applicable
ment process may restart be unavailable for a short time
during automatic due to restart during automatic
failover failover.

AS-101420 System Manage- Array Management The Array Management service The service will stabilize on its
ment Service restarts un- may restart unexpectedly when own following the restarting.
expectedly under the array is under high workload.
high load

Known Issues 52
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-105041 System Manage- Array management Array Management service may Not applicable
ment service may restart restart on a group configured
on Group Leader or for high availability during vari-
Backup Group ous scenarios such as when
Leader arrays Group Leader to Backup Group
Leader communication is at high
load or degraded. Scenarios
which may cause an array man-
agement service restart include
degraded or broken network
connectivity between GL and
BGL arrays.

AS-97327 System Manage- Group Management If communication between Not applicable

ment service may restart Group Management and Post-
due to communica- gres services does not complete
tion timeout exceed- within expected timeout, the
ed Group Management service may
restart. The restart will resume
the communication and try the
transaction again.

AS-97697 System Manage- Group Management Group Management service may Not applicable
ment Service may restart restart due to health check
unexpectedly timeout exceeded. The service
will recover after the restart.

AS-66341 System Manage- Group Management The Group Management Service Not applicable
ment Service restarts un- may restart unexpectedly when
expectedly follow- the array is under heavy load,
ing automatic has many snapshots scheduled,
Group Leader has performed a group merge in
Failover the past, and has recently per-
formed an automatic Group
Leader Failover.

AS-65676 System Manage- Group Management The Group Management service Not applicable
ment service may restart may restart unexpectedly when
due to internal internal database query does
database timeout not complete within the expect-
ed time out. The service restarts
to clear the condition.

AS-108145 System Manage- Group Management When a new internal database Not applicable
ment Service may restart connection is established, a
due to internal number of prepared_statements
database handling are executed at the beginning.
If one of the prepared_state-
ments fails the Group Manage-
ment Service will restart.

Known Issues 53
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-98434 System Manage- After group leader After Group migration is per- Disable automatic failover and
ment migration, quorum formed, backup group leader remove witness from configura-
is not removed af- becomes group leader. If witness tion.
ter witness discon- is disconnected for more than
nection five minutes, the new leader will
not remove quorum.

AS-106490 System Manage- Group management While syncing the config Not applicable
ment service may restart changes on the downstream ar-
due to race condi- ray, group management service
tion may restart due to a race condi-
tion between protection policy
deletion and adding the volume
to the protection policy.

AS-113950 System Manage- Group management Group management service may Not applicable
ment service may restart restart due to the race condition
due to assertion between branch creation for the
failure replica 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 may
impact management workflows.

AS-105064 System Manage- Group management Internal workflow processing re- Not applicable
ment service may restart lated to the replication partner
unexpectedly object may cause the process to
deadlock, resulting in Group
management service restart.

AS-115200 System Manage- Unexpected delays In the data protection environ- Not applicable
ment in configuration ments, replication partners need
sync between repli- to sync their configuration. In
cation partners certain situations, the partners
will attempt to sync all volume
collections as opposed to just
the volume collections that were
recently modified. This may lead
to unexpected delays is replica-
tion partner sync.

AS-98650 System Manage- Alert for aborted In the case where the down- Not applicable
ment handover does not stream array is reaching its
specify reason snapshot rate limit and the user
performs the volume collection
handover, the handover will be
abort if the limit is surpassed. An
alert will be raised but the alert
message may be missing the
reason for aborting handover.

Known Issues 54
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-99520 System Manage- Both upstream and If a user performs multiple vol- Not applicable
ment downstream may ume collection handovers be-
claim the volume tween two arrays during a short
collection owner- time span, this may cause a situ-
ship when exces- ation where both upstream and
sive handovers are downstream array may claim
performed volume collection ownership.
This is due to a race condition
in the workflow.

AS-98378 System Manage- Error No message Under system busy conditions, Please reissue the command. If
ment received after issu- when an excessive amount of the operation was already per-
ing CLI command operations are being issued in formed by the earlier command,
to disassociate vol- parallel or too many internal re- an appropriate message will be
ume from collection tries are occurring to perform returned.
tasks, you may receive a No
message received error after is-
suing a CLI command.

AS-81209 System Manage- Group Management In rare occurrences, the Group Not applicable
ment service may restart Management may restart when
due to race condi- a race occurs between threads
tion that are disassociating a volume
from a volume collection and
modifying a schedule for the
same collection. The service
restarts to recover.

AS-73432 System Manage- Snapshots display Snapshots may display in GUI as Contact HPE Nimble Storage
ment as replicated in GUI replicated snapshots when they Support
on array with no are not involved in replication.
replication config-
ured

AS-89124 System Manage- Synchronous Repli- The group --list_limits CLI com- Not applicable
ment cation Volume mand does not list the Syn-
Count Limit chronous Replication volume
count Limit. Synchronous Repli-
cation on 5.1.0.0 and later can
protect up to 128 volumes.

AS-88308 System Manage- Cloud Volumes If two on-premise array groups Not applicable
ment replication does not configured with a Nimble Cloud
support group Volumes (NCV) partner are
merge merged, the Cloud Volume
replication will stop working.

Known Issues 55
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-59470 System Manage- Group management A deadlock can occur between Not applicable
ment process my restart two management processes
due to a deadlock when updating the replication
when replicating bandwidth throttle. The Manage-
ment Process will restart and
clear the condition. There is no
disruption to data services and
replication will continue automat-
ically without intervention.

AS-57574 System Manage- Replication of Encrypted and deduped vol- Update the downstream array
ment dedupe and en- umes cannot be replicated from to NimbleOS 3.4.x or later.
crypted volumes 3.4.x and later to previous 3.x
will stall between releases because they do not
3.4 and previous support encryption and dedupe
3.x releases at the same time. Note that this
does not affect replication from
3.4.x and later to 2.3.x where the
volumes will not be deduped on
the downstream running 2.3.x.

AS-96143 System Manage- Group management NimbleOS uses a defined state Not applicable
ment service may restart machine for the replication
due to assertion workflow. At the end of the exe-
failure cution of each step defined in
the state machine, it moves to
the next step. If it leads to any
unexpected step throughout the
workflow then it will lead to as-
sertion failure which results in
Group Management service
restart.

AS-96241 System Manage- Group Management When the system has a high Not applicable
ment service may restart number of objects, the Group
due to high memo- Management service may restart
ry usage while running REST query or CLI
command.

AS-90649 System Manage- Configuration of If the Default Deduplication set- Update the downstream pools
ment deduplication vol- ting differs for upstream and Deduplication setting to match
umes for sync repli- downstream pools, the configu- the upstream pool.
cation might fail ration of deduplication volumes
for replication might fail with the
following error Deduplication
not allowed since no application
category is assigned to the per-
formance policy

Known Issues 56
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-90633 System Manage- Error No message Under system busy conditions, Please reissue the command. If
ment received after issu- when an excessive amount of the operation was already per-
ing CLI command operations are being issued in formed by the earlier command,
to associate volume parallel or too many internal re- an appropriate message will be
to volume collec- tries are occurring to perform returned.
tion tasks, you may receive a No
message received error after is-
suing a CLI command.

AS-90286 System Manage- volcoll --info output For the volcoll --info output for vol --list can be used to deter-
ment lacks pool/folder sync replication volume collec- mine pool/folder attributes of
qualifications for tions, the Associated volumes: these volumes.
associated volumes and Associated pinned volumes:
fields lack pool/folder qualifica-
tion for the associated volumes.

AS-49720 System Manage- Group Management The Group Management service Not applicable
ment Service may restart may restart due to a race condi-
due to race condi- tion between threads when up-
tion dating replication records in
Scale Out Database (SODB). The
service restarts to clear the con-
dition.

AS-98155 System Manage- Group management Arrays with volumes that have Contact HPE Nimble Storage
ment service may restart large branch structures may Support.
unexpectedly cause internal command process-
ing timeout to be exceeded. This
will cause the Group Manage-
ment service to restart due to
health check failure.

AS-108119 System Manage- Group management The Group Management service Not applicable
ment service may restart may restart due to a race condi-
due to race condi- tion between replication com-
tion mands and group management
service restart. The service
restarts to recover from the
condition.

AS-114179 System Manage- Group Management During shutdown of the group Not applicable
ment service may restart management process, the SSL
during process library logging of the debug
shutdown due to messages can cause a race con-
race condition dition, resulting in a segmenta-
tion violation error. The service
restarts to recover from the
condition.

Known Issues 57
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-108765 System Manage- Group Management During a planned array shut- Not applicable
ment service restarts down, the Group Management
during the array service may restart due a race
shutdown condition. There is no data or
management interruption since
the service is already shutting
down.

AS-95610 System Manage- Group Management Due to a rare race condition, the Retry the command for the
ment Service restarts Group Management Service may failed volumes.
during bulk volume restart unexpectedly during a
update bulk volume update operation.

AS-91638 System Manage- Group Management If the network response to a Please review the network and
ment Service restarts due REST request takes more than see if there is a consistent pack-
to packet loss in 5 minutes, a thread performing et loss and fix any network
network the REST request times out and glitches. If you need any assis-
as a result Group Management tance, please reach out to HPE
Service restarts. The service Nimble Storage Support.
stabilizes itself and as long as
the network is serving the re-
quests faster. A single instance
of the Group Management ser-
vice restart should not cause any
disruptions.

AS-108868 System Manage- Group Management In environments with an array Confirm all Domain Controllers
ment service may restart integrated with Active Directory, in the Active Directory environ-
while collecting us- the create/validate session code ment that is integrated with the
er information from holds a lock on an underlying array are reachable.
Active Directory sessions table and then goes to
Active Directory to collect more
information about the user. If
this operation takes too long,
the Group Management service
may timeout to free this lock.

AS-66182 System Manage- Discovering vol- If a user runs --resetup followed Ensure setup completes success-
ment umes after array by setup on an array that was fully before attempting to discov-
resetup may cause previously configured and setup er volumes.
Group Data service does not complete successfully,
restart data IPs may be unconfigured
until the setup actually com-
pletes successfully. As a result,
GDD may restart unexpectedly
if any attempts are made to dis-
cover the volumes on those un-
configured data IPs.

Known Issues 58
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-117078 System Manage- Group Management Due to a race condition with Not applicable
ment service may restart snapshot retention on a down-
due to race condi- stream replication partner, the
tion with snapshot Group Management service may
retention on a crash unexpectedly. The Process
downstream replica- Management service automati-
tion partner cally restarts the Group Manage-
ment service after the crash and
it should resolve the race condi-
tion.

AS-95868 System Manage- Group Management The Group Management per- Not applicable
ment service may restart forms queries on the information
due to internal stored in the Scale Out Database
database timeout (SODB) for the array. If the
query does not complete within
the expected timeframe, the
service may restart to recover
from the issue.

AS-68782 System Manage- System limitation of The group --list_limits CLI com- Please refer to the System Lim-
ment writable snapshots mand does not list system limita- its and Timeout Values section
is not reported by tion for writable snapshots. Also, in the NimbleOS Administration
NimbleOS no alerts or alarms are generat- Guide.
ed as as the array group ap-
proaches the limit.

AS-94517 System Manage- Group Management Group Management service may Not applicable
ment service may restart restart due to memory exhaus-
due to memory ex- tion in configurations that ap-
haustion proach 10,000 volumes and
300,000 snapshots.

AS-105291 System Manage- Group Management Due to a race condition, the Not applicable
ment Service may restart Group Management Service on
due to a race condi- a downstream group may restart
tion while updating volume collec-
tions from the upstream group.

AS-93113 System Manage- Unmanaged snap- If clones are created using an Not applicable
ment shots remain after unmanaged snapshot, then this
cleanup is enabled unmanaged snapshot will not be
deleted even if cleanup is en-
abled.

AS-97899 System Manage- Group Management If communication between Not applicable

ment service may restart Group Management and Post-
due to communica- gres services does not complete
tion timeout exceed- within expected timeout, the
ed Group Management service may
restart. The restart will resume
the communication and try the
transaction again.

Known Issues 59
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-65935 System Manage- Frequent, multiple Multiple snapshot deletions can Refresh the HPE Nimble Storage
ment Snapshot Collection be deleted in a single request. array GUI .
deletions causes Back-to-back deletions of multi-
GUI to hang ple batches of ten or more
snapshot collections may cause
the HPE Nimble Storage array
GUI interface to hang.

AS-105944 System Manage- Time to Live (TTL) NimbleOS protects the last The TTL can be updated on the
ment expiry date on last replicated collection, in some snapshots which have a negative
replicated snap- cases, the TTL expiry date on value to a current value. The
shots can be nega- those snapshots can become snapshot may also be removed
tive negative when the snapshots if it has been confirmed it is no
exist beyond TTL. longer needed.

AS-105432 System Manage- Deletion of a vol- In certain scenarios, a volume Contact HPE Nimble Storage
ment ume is not complet- deletion will not complete due Support to identify ACLs in
ed due to the pres- to the existence of a stale ACL forced-delete/create-retry state,
ence of stale ACLs associated with it. This stale ACL verify these ACLs are associated
associated with it is associated with a snapshot of with snapshots that no longer
the volume that was previously exist, and delete these ACLs
deleted. These volumes will not from the internal NimbleOS
show up in the CLI/GUI as they database.
are in a hidden state.

AS-104965 System Manage- Group Management During planned service stop, Not applicable
ment service may restart such as array shutdown, the
during array shut- Group Management service may
down restart due to a race condition.
There is no data or management
interruption since the service is
already shutting down.

AS-62192 System Manage- Group Management When internal threads encounter Not applicable
ment service may restart a locking conflict, the Group
unexpectedly due Management service may restart
to a conflict with in- to recover from the condition.
ternal threads

Known Issues 60
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-113375 System Manage- Automatic Failover Automatic Failover demotion of Not applicable
ment Backup Group a Backup Group Leader array
Leader demote may may be delayed for multiple
be delayed in rare minutes when an internal
circumstances database is performing weekly
garbage collection. The Group
Leader is not able to demote the
Backup Group leader during a
weekly window when an internal
database is performing internal
garbage collection. This may last
for multiple minutes. Eventually
Backup Group Leader demote
succeeds, and a new Backup
Group Leader is selected. The
Group loses High Availability
during this time and the Group
Management service may restart
to recover from the condition.

AS-105804 System Manage- Group Management Group Management service may Scheduling snapshots to occur
ment service may restart restart on the array when there at different times instead of all
unexpectedly when is a high amount of snapshot at once may help alleviate this
performing high activity being performed. The issue.
snapshot activity service restart will recover from
the condition and the snapshot
operations will resume.

AS-103982 System Manage- Group Management In rare instances, the Group Not applicable
ment Service may restart Management Service may
unexpectedly due restart unexpectedly when the
to network connec- Group Leader and Member array
tivity have lost connectivity due to
network outage. The service
restart recovers GUI and CLI ac-
cess, data services are not im-
pacted by the restart.

AS-115819 System Manage- System Processes After a controller restarts due to Not applicable
ment or Systems may over temperature condition,
start slowly after System Management processes
over temperature may restart and take longer to
restart start up due to slow system
performance.

Known Issues 61
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-108378 System Manage- Array management Array Management service may Not applicable
ment service may restart restart on a group configured
during periods of for high availability during vari-
degraded network ous scenarios when Group
connectivity be- Leader to Backup Group Leader
tween Group Lead- communication is high or degrad-
er and Backup ed. Scenarios which may cause
Group Leader ar- an array management service
rays. restart include degraded or lost
network connectivity between
GL and BGL arrays.

AS-98504 System Manage- Group Management If internal database processing Not applicable
ment service may restart for array statistics exceeds the
unexpectedly expected timeout, the Group
Management service will restart
due to health check failure to
recover.

AS-101392 System Manage- Services may not When the array is powered on Please contact HPE Nimble
ment start on the array and off excessively, services may Storage Support
after it is powered fail to start on the array.
on and off several
times

AS-105453 System Manage- Group Management The Group Management service Not applicable
ment service may restart may restart when service commu-
unexpectedly nication for internal database
processing is terminated. The
service restarts to restore con-
nections between the services.

AS-99615 System Manage- Array Management The Array Management Service Not applicable
ment Service restarts un- restarts unexpectedly following
expectedly follow- automatic Group Leader Failover
ing automatic (AFO). The restart is non-disrup-
Group Leader tive.
Failover

AS-95132 System Manage- Process Manage- In rare instances, the Process Not applicable
ment ment service may Management service restart may
restart during soft- occur during software update.
ware upgrade The system recovers after the
restart of the service.

Known Issues 62
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-110374 System Manage- Group Data Service The underlying scale-out No workaround available. To
ment may restart when database competes with CASL avoid encountering this issue,
the array is under and other system processes for reduce IO load when performing
heavy load during IOPS. During software update, a software update. Software Up-
software update migration script runs against the date will succeed after one or
database. Under heavy file sys- more System Management ser-
tem load, the migration steps vice restarts.
may not complete within the
expected amount of time. As a
result, the migration may time-
out leading to a restart of the
Group Data Service. After the
restart, the migration should
complete as normal without any
user impact or intervention.

AS-98694 System Manage- Snapshot limit After the update to 5.1.x.x or The alarms can be deleted man-
ment warning alarms later, the Snapshot limit warning ually either in the GUI or on the
persist after update alarm is no longer used. This CLI.
to 5.1.x.x or later presents a situation where stale
alarms are present on the array
and they will not be cleared even
if the space situation is rectified.
The alarm follows the following
format: WARNING Mon DD
YYYY HH:MM:SS Acknowledged
- Volume &lt;volume name&gt;
snapshot space usage is over
the configured warning limit.

AS-77045 System Manage- Alarm not cleared Alarms are generated on the ar- Confirm the usage level for vol-
ment after volume or ray when volume or pools ex- ume or pool indicated by the
pool drops below ceed thresholds. In some in- alarm is below threshold. Once
warning threshold stances the recovery event to confirmed usage level is below
clear the alarm when the condi- threshold, clear the alarm from
tion is cleared does not clear the the Command Line Interface
alarm. (CLI): 1. List the alarms to find
the alert ID alarm --list 2. Delete
the alarm that is no longer valid
alarm --delete

AS-110123 System Manage- Group Management Infrequently the Group Manage- Not applicable
ment service may be- ment service may encounter an
come unavailable error while shutting down. If the
when shut down service is being restarted it may
take a few more seconds to
start. GUI and CLI will be unavail-
able for a few seconds.

Known Issues 63
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-108432 System Manage- Group management High concurrent REST volume Not applicable
ment service may restart reads with statistics may cause
when there are Group Management service to
many REST re- restart. Current REST requests
quests for volume will fail, GUI and CLI will be un-
statistics values available. The system will recov-
er after the restart of the service.

AS-106848 System Manage- Arrays with Auto- Software updates to 5.1.4.200 The ASO checkbox is enabled
ment matic Switchover are not allowed when Automatic by default, however ASO is not
enabled fail soft- Switchover (ASO) is configured. enabled until a witness has been
ware update with If a software update to 5.1.4.200 configured. In the GUI, navigate
generic message fails for this reason, a generic to Administration &gt; Availabil-
software update failure message ity. If witness is configured and
is returned in the GUI. The cause the ASO check box is checked,
of the failure would need to be disable ASO by unchecking the
determined by looking at the box and clicking save. Perform
system configuration and deter- the array software update again.
mining if ASO is configured. If the update continues to fail
with generic messaging, contact
HPE Nimble Support.

AS-66997 System Manage- Health check time- The timing is close enough that This is an intermittent issue, so
ment out may cause soft- it is possible for the individual if the software update fails in
ware update failure array precheck during software this manner it should pass if the
update to take long enough that software update is resumed.
the health check timeout is trig-
gered, causing the group man-
agement process to restart and
the software update to fail.

AS-72559 System Manage- Group management Group management service may Not applicable
ment service may restart restart during software update
during software up- due to race condition involving
date unlocking the download lock file.

AS-54519 System Manage- Software update in- When a software update is initi- Initiate the software update
ment activity timeout ated on the array and the again and answer the EULA
messaging prompt for EULA acceptance is prompt and the software update
not answered, the software up- will proceed as expected.
date session will timeout after
several hours with a message
indicating Requires Authentica-
tion or Contact HPE Nimble
Storage Support.

Known Issues 64
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-57173 System Manage- Updating array Due to the number of firmware If a timeout occurs, the update
ment groups from earlier updates involved, software up- can be completed using the
NimbleOS 3.x re- date going from pre-3.3.x ver- software --resume_update com-
leases to 3.3.x or sions to 3.3.x or later could take mand.
later releases could too long and eventually timeout.
timeout These update times may take
longer in larger multi-array
group configurations. Software
update in smaller array groups
should complete without inter-
vention.

AS-40516 System Manage- Timeouts during Under rare conditions, a soft- Running the software --re-
ment software update ware update may report an error sume_update command from the
even though the actual update console will clear this condition.
has completed successfully. This
occurs when software update
takes longer than 4 hours.

AS-91962 System Manage- Volume manage- While the volume ownership is Ignore the error message and
ment ment operations being changed, any manage- retry the management operation
may fail with unre- ment operation involving that
lated error mes- volume could fail. This is expect-
sages while han- ed behavior. Depending on the
dover is in-progress progress of that handover oper-
ation, management operation is
failing with different errors.

AS-109805 System Manage- Group Management The Group Management service Not applicable
ment service may restart may restart when internal
due to health check database processing exceeds
timeout the expected timeout value. The
service restarts to recover from
the condition.

AS-113885 System Manage- &nbsp;Group Man- In environments with an array Confirm all Domain Controllers
ment agement service integrated with Active Directory, in the Active Directory environ-
may restart while the create/validate session code ment that is integrated with the
collecting user infor- holds a lock on an underlying array are reachable.
mation from Active sessions table and then goes to
Directory Active Directory to collect more
information about the user. If
this operation takes too long,
the Group Management service
may timeout to free this lock.

AS-115002 System Manage- Group Management The Group Management service Not applicable
ment service may restart may restart when user lookup is
due to healthcheck in process and the winbindd
timeout service does not respond within
the expected timeframe. The
service restarts to recover from
the condition.

Known Issues 65
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-107491 System Manage- Active Directory Array authentication to an Ac- Add the computer account cre-
ment authentication may tive Directory Read-Only Do- dentials for the array by adding
fail with Read-Only main Controller (RODC) may fail, it to the RODCs password repli-
Domain Controller resulting in failures to authenti- cation policy (PRP) under the
(RODC) cate Active Directory users. Allowed RODC Password Repli-
cation Group group.

AS-104512 System Manage- Active Directory Active Directory Authentication Not applicable
ment authentication in causes the arrays Group manage-
some cases, may ment service to wait for a re-
lead to a Group sponse from the Active Directo-
Management ser- ry. If this response is delayed,
vice restart the Group Management Service
may restart unexpectedly.

AS-111166 System Manage- Active Directory The expected configuration isnt As a local admin on the array,
ment connection failures loaded when the Active Directo- restart the Active Directory inte-
ry integration service starts, gration service by disabling and
leading to failed logins or incon- enabling the integration. Via the
sistent Active Directory connec- GUI: Navigate to Administration
tivity in certain configurations. -&gt; Security -&gt; Microsoft
Active Directory Click Disable
Click Enable Via the CLI: user-
auth --disable &lt;domain&gt;
userauth --enable &lt;do-
main&gt;

AS-72869 System Manage- Group Management The Group Management service Not applicable
ment Service may restart validates session information in
due to internal the Scale Out Database. If the
database handling validation exceeds the expected
timeout, the service will restart
to recover.

AS-69084 System Manage- Group Management If collection of user group infor- Not applicable
ment service may restart mation from Active Directory
while collecting us- takes longer than expected, the
er information from Group Management service
Active Directory timeout may be exceeded. The
service will restart to resume in-
formation collection.

Known Issues 66
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-95212 System Manage- HPE Nimble Stor- When the HPE Nimble Storage Not applicable
ment age array compati- array is configured to use Active
bility issues with Directory integration, the array
MIT Kerberos trust is joined to one specific domain,
types as a domain member. Under
normal circumstances, users in
trusted domains will also be able
to authenticate to the array. If
one or more trusted domains are
joined to the forest using an MIT
Kerberos type trust relationship,
users and groups in any trusted
domain (e.g. not the domain the
array is joined to) will be unable
to authenticate to the array.

AS-105035 System Manage- Group Management In rare instances, if the array is Contact HPE Nimble Storage
ment service may crash under heavy load and Group Support
while trying to cre- Management service restarts
ate users while ar- while new user is being created,
ray is under heavy the service can fail to start.
load

AS-71137 System Manage- Group Management The Group Management Service Not applicable
ment Service restarts may restart unexpectedly if it
while authenticat- takes longer than 300 seconds
ing AD users to authenticate an Active Direc-
tory (AD) user.

AS-66437 System Manage- Command to join Command to join AD may fail Not applicable
ment Active Directory because of latency in getting
(AD) may fail caus- back a response from AD server.
ing Group Manage- This may cause a health check
ment service failure for Group Management
Restart causing the restart of the service
to recover.

AS-74830 System Manage- Group Management When joining Active Directory Not applicable
ment service may restart via GUI or userauth command in
when joining array CLI, the command is expected
to Active Directory to complete within 300 seconds.
If this timeout is exceeded dur-
ing the process, the Group Man-
agement service will restart to
recover.

AS-78946 System Manage- Latency in commu- AD communication may be slow Not applicable
ment nicating with Active leading to a delay in responses
directory during that may cause Group Manage-
may cause Group ment service to crash. Leaving
Management ser- the AD domain requires interac-
vice to restart tion with AD wherein this delay
can cause a restart.

Known Issues 67
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-65654 System Manage- Active Directory If there are connectivity issues Resolve any connectivity issues
ment connectivity issue between an array with Active between the array and Active
may result in Group Directory integration enabled Directory Domain Controller(s)
Management ser- and an Active Directory Domain to avoid unexpected service
vice restart. Controller, then the responses restarts.
may take more than 300 sec-
onds and timeout. As a result,
the Group Management service
may restart.

AS-114105 System Manage- Group management During extremely rare circum- Not applicable
ment services may stances, a bug may cause Group
restart Management Services to restart
while deleting a user. The array
will recover after Group Manage-
ment completes its restart.

AS-109549 System Manage- Group Management When logging in with a Active Not applicable
ment service may restart directory (AD) user, delayed re-
due to Active direc- sponses from AD may lead to
tory communication Group Management service
taking too long. restart.

AS-101535 System Manage- Group Management Enabling and disabling the The Group Management Service
ment Service is temporar- dedupe setting on volumes and will eventually restart itself
ily unavailable after concurrently deleting volumes
deleting volumes can cause the Group Manage-
ment Services to become tem-
porarily unavailable on the array.

AS-102893 System Manage- Enabling syn- Following operations will fail Delete unused clones or volumes
ment chronous replica- upon reaching the volume limit: to bring down the volume count.
tion fails upon -adding Synchronous replication
reaching volume schedule to a volume collection
limit &nbsp;-associating a volume to
a volume collection with Syn-
chronous Replication enabled -
editing a Volume Collection
schedule to add Synchronous
Replication partner

AS-84276 System Manage- Performance issues After updating to NimbleOS 4.x, Please contact HPE Nimble
ment for volumes created volumes initially created when Storage Support to update the
when array was an array was running NimbleOS compression algorithms of these
running NimbleOS 1.3.x and earlier may experience older volumes.
versions 1.3.x and a negative impact on perfor-
earlier mance. This is caused by soft-
ware changes made to the com-
pression algorithm used by
these older volumes.

Known Issues 68
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-86545 System Manage- Unable to create After a CSx000 array is installed, Once the array is able to deter-
ment dedupe enabled it takes one minute for the array mine its deduplication capability,
volumes on a new to determine its deduplication all newly created volumes will
install capability. If a volume is created have dedupe enabled, if speci-
prior to this, it will not have fied. In order to enable dedupe
dedupe enabled even if the ar- on the previously created vol-
ray is dedupe capable. umes, you may run the following
command via the HPE Nimble
Storage Array CLI: vol --edit
&lt;vol_name&gt; --dedupe_en-
abled yes

AS-92157 System Manage- No CLI support for Currently, there is no CLI sup- Not applicable
ment changing the Wit- port for changing the witness
ness Port port. The nimble-witnessd.ser-
vice file needs to be edited
manually.

AS-100067 System Manage- Member array A member array might not be Not applicable
ment might not be dis- listed under the Add Array to
played under Add Group option within the GUI if
Array to Group op- the member is configured with
tion a different protocol (iSCSI vs Fi-
bre Channel). Also when there
are multiple arrays in the subnet,
arrays which cant be discovered
within the stipulated time may
not be listed in Add Array to
Group.

AS-107015 System Manage- Group Data service In rare instances, the Group Data Not applicable
ment may restart on service may restart during
startup startup due to a misconfigura-
tion in NimbleOS pertaining to
a file descriptor limit.

AS-99431 System Manage- Array Management In rare circumstances, following Not applicable
ment Service restarts or an Automatic Failover (AFO) a
Takeover occurs race condition may cause the
unexpectedly fol- Array Management Service to
lowing automatic restart or an unexpected con-
Group Leader troller takeover.
Failover

AS-99343 System Manage- Custom SSL certifi- Within the HPE Nimble Storage Not applicable
ment cate import not array GUI, custom SSL certificate
supported on older import is only supported on
versions of Google Google Chrome version 71 or
Chrome later.

Known Issues 69
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-98177 System Manage- Setting alarm re- When updating an alarm from To keep the same reminder fre-
ment minder frequency the Events &gt; Alarms page in quency and reset the next re-
to the same value GUI, selecting an alarm and minder time based on the cur-
from GUI does not clicking CHANGE REMINDER rent time, change the reminder
change next re- button, without changing the frequency to a different value,
minder time reminder frequency time, and save it, and change it back and
clicking SAVE button, does not save it, or use CLI to make the
change next reminder time. This change.
behavior is different from CLI.
Setting alarm reminder frequen-
cy to the same value from CLI
resets the next reminder time
based on the current time.

AS-87701 System Manage- Incorrect informa- When a controller is down, the When the controller is back up,
ment tion on hardware user may see incorrect represen- all the information is displayed
page displayed tation of physical ports within correctly on hardware page.
when controller is the Hardware Page of the array
down GUI. This is due to the lack of
information from the missing
controller.

AS-102299 System Manage- GUI Error when en- The Array GUI incorrectly re- Use Google Chrome or Mozilla
ment tering a valid folder turns an error when a valid value Firefox browser.
overdraft limit val- for the folder overdraft limit has
ue been entered. This happens only
in Internet Explorer and Mi-
crosoft Edge browsers.

AS-87886 System Manage- GUI may show Suc- During group merge, the GUI Not applicable
ment cessful message might show Successful message
when group merge even though the group merge
fails backend processing fails.

AS-77372 System Manage- Group Merge via Currently within the HPE Nimble To work around this issue: 1.
ment GUI unable to pro- Storage Array GUI, when per- Log into the destination array
cess large amount forming a group merge, if there to resolve the conflicts. 2. At-
of conflicts is a large amount of group tempt the group merge again.
merge conflicts (1000 or more),
the GUI is unable to process and
resolve all of them.

AS-76896 System Manage- Unable to assign When adding a Fibre Channel Please contact HPE Nimble
ment group traffic to Fi- (FC) array to an existing group, Storage Support.
bre Channel array you are unable to change the
when joining array mgmt subnet to Mgmt + Data.
group You will see the following error:
Data subnet Management
&lt;SUBNET&gt; must allow
group traffic

Known Issues 70
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-95591 System Manage- Incorrect ordering Pool merge is not allowed if Not applicable
ment of pool merge error Synchronous Replication is en-
messages when abled and pool merge is not al-
Synchronous Repli- lowed when a witness config-
cation and Witness ured. If an array group has a
are configured witness configured for Automat-
ic Switchover and has Syn-
chronous Replication configured,
when a user tries to perform a
pool merge, the following error
is generated: “pool merge is not
allowed when witness is config-
ured”. In this case, if the user re-
moves the witness and then re-
attempts the pool merge, the
following error is then generat-
ed: “Pool merge is not allowed
when involved in sync replica-
tion”. This error should super-
sede the previous error.

AS-94575 System Manage- Unable to edit a When attempting to edit a stor- Edit the pool name and assign /
ment storage pool and age pool and assign an array at un-assign the array a in separate
assign an array at the same time, you receive the steps.
the same time following error: Cannot update
array list and name or descrip-
tion simultaneously.

AS-104099 System Manage- Volume collection When associating multiple vol- Fix the name conflict on the
ment association for a umes to a volume collection downstream array.
volume can fail due from, the volume association for
to a name conflict all volumes can fail due to a
on the downstream name conflict for one of the vol-
array umes on the downstream.

AS-93157 System Manage- Array GUI does not The Array GUI does not specify Run the following command via
ment specify which snap- which snapshots are unmanaged CLI: snap --list --all --unmanaged
shots are unman- and no longer belong to a vol-
aged ume collection.

AS-67289 System Manage- In the Create Repli- In the Create Replication Partner Click the dropdown arrow and
ment cation Partner wiz- wizard, the Inbound Location is select a location from the pool
ard the inbound lo- no longer automatically populat- and folder navigation tree.
cation is no longer ed.
automatically popu-
lated

Known Issues 71
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-99024 System Manage- Browser becomes After changing a certificate, the After a new custom certificate
ment unstable upon cer- GUI may present an error such has been imported or existing
tificate change as follows: The web service is certificate is deleted, please
very slow or unreachable... close the browser where the ac-
tion was performed and reopen
a new one to guarantee a new
connection request to the Nim-
bleOS web interface.

AS-92634 System Manage- Volume perfor- The volume performance num- The values should report correct-
ment mance numbers bers displayed in the GUI under ly within 24 hours after the up-
may report invalid Manage &gt; Data Storage &gt; date has completed.
values after soft- Volumes &gt; Performance Tab
ware update may display invalid values tem-
porarily after an array software
update.

AS-104567 System Internals Array Management When the Group Leader at- Not applicable
Service restarts tempts to complete the Backup
when Group Leader Group Leader promotion, if there
cannot reach Back- is not a healthy data path, the
up Group Leader Backup Group Leader promotion
fails. Despite, the network error,
the Backup Group Leader promo-
tion goes into a loop and ulti-
mately leads to an unexpected
restart of the Array Manage-
ment Service.

AS-86901 System Internals Group Data Service The underlying scale-out There is no workaround. To
may restart when database competes with CASL avoid encountering this issue,
the array is under and other system processes for reduce IO load when performing
heavy load during IOPS. During software update, a software update.
software update migration script runs against the
database. Under heavy file sys-
tem load, the migration steps
may not complete within the
expected amount of time. As a
result, the migration may time-
out leading to a restart of the
Group Data Service. After the
restart, the migration should
eventually complete as normal
without any user impact or inter-
vention.

AS-80445 System Internals File System service The File System service may Not applicable
may restart during restart during array shutdown if
array shutdown it exceeds expected time to
shutdown. The service restarts
to clear the condition.

Known Issues 72
Known Issues in NimbleOS version 5.2.1.600
ID Component Title Description Workaround
AS-59517 System Internals Data Service may Due to a race condition, the Data Not applicable
crash during array Service may crash during array
shutdown shutdown. Once the array starts
again, all operations resume as
normal.

AS-69561 System Internals Data Service can Due to a race condition, the Data Not applicable
restart unexpected- Service can crash during a
ly during shutdown graceful shutdown causing unex-
process pected Data Services restart
messages to be generated. This
should not cause any I/O impact
because the Data Service is al-
ready in the process of shutting
down.

AS-49046 System Internals Data Service may Under unique customer work- Please contact Nimble Storage
restart when the loads, the index footprint may Support to increase the scratch
array runs out of exhaust default scratch page al- page pool size.
scratch pages location in memory. As a result,
the Data Service may restart
unexpectedly.

Known Issues 73