Release Notes

Table 6. Known issues (continued)
Issue number Functional area Description Workaround
selectCreate. Once one storage-
view is created, then from the main
status dashboard click the Storage
Views circle to create the storage-
views.
VPLEX-27760 UI Performance Dashboard hover-over
statistics window may get stuck across
other pages.
Refresh the page from your
browser.
VPLEX-28028 CLI director tracepath command
fails and returns an error. collect-
diagnostics reports errors that are
related to a failure to capture director
tracepath output.
It is not supported.
VPLEX-28492 CLI collect-diagnostics sub-command
authentication directory-service
shows error.
Ignore the error. It is not supported.
VPLEX-28757 UI Online Help page navigation buttons
(back, forward, up, print) may cut by
page content and be difficult to use.
Buttons are still clickable with
careful attention.
VPLEX-29215 CLI
health-check --configuration
shows several unexpected errors.
It is not supported.
VPLEX-29250 CLI health-check --hardware output is
missing.
It is not supported.
VPLEX-29253 CLI health-check --front-end shows
Checking Front End Path....
Error
It is not supported.
VPLEX-29391 Upgrade Post successful NDU, ndu complete
gives false error NDU data is
not initialized properly:
notifications_settings is not
found.
Ignore this error.
VPLEX-35291 UI In the UI, when configured with
many devices, the Consistency Group
Create wizard can take an excessive
amount of time to load the list of
available virtual volumes.
Skip the Select Virtual Volumes
step of the Consistency Group
Create wizard, and add the
virtual volumes after creating the
consistency group.
Expected behaviors
This section describes expected behaviors in metro node.
● System volumes such as metadata and logging volumes are supported on thin devices. However, metro node relies on these
volumes for system operations. All extents should be pre-allocated, to prevent out-of-space conditions.
● While the clusters are in contact, metro node prevents the same storage volume from being claimed at each cluster.
However, if the clusters are partitioned, metro node cannot prevent the same storage volume from being claimed at both
clusters. If this happens, once metro node detects this, a call home is sent. This issue should be corrected when it is
detected.
● When one leg of a distributed device within a consistency group is unhealthy and marked for a rebuild, you are prevented
from removing the unhealthy leg. A distributed consistency group requires two-legged distributed device members. To avoid
this issue:
1. Use the attach mirror command to attach a new mirror to the healthy leg.
2. Detach the old unhealthy mirror.
Release Notes
9