EMC® VNX®

VNX Operating Environment for Block 05.33.008.5.119

VNX Operating Environment for File 8.1.8.119
EMC Unisphere 1.3.8.1.0119

Release Notes
P/N 302-000-403
REV 20
August, 2015

The software described in this document is intended for the VNX5200,

VN5400, VNX5600, VNX5800, VNX7600, VNX8000, VNX-F5000, and VNX-
F7000 but the following software packages are intended for general use with
VNX and CLARiiON products:
 Unisphere Host software, CLI, and Utilities
 Unisphere Service Manager
 ESRS IP Client
The software versions are the same for all platforms. Topics include:
Revision history ........................................................................................... 2
Software media, organization, and files .................................................... 3
New features and enhancements ............................................................... 4
Localization updates ............................................................................ 7
Java support .......................................................................................... 7
Fixed problems ............................................................................................ 9
VNX Operating Environment for Block 05.33.008.5.119, VNX
Operating Environment for File 8.1.8.119, EMC Unisphere
1.3.8.1.0119 .................................................................................. 9
Fixed in previous releases ......................................................................... 25
Known problems and limitations.............................................................. 48
Documentation .......................................................................................... 89
Configuring VNX Naming Sevices ...................................................... 89
Using VNX Replicator .......................................................................... 90
Where to get help....................................................................................... 91

1
Revision history

Revision history

Rev Date Description

20 August, 2015 Updated for 05.33.008.5.119 (Block OE), 8.1.8.119 (File OE), and 1.3.8.1.0119
(Unisphere)
19 April, 2015 Updated for 05.33.006.5.102 (Block OE) and 8.1.6.101 (File OE).
18 April, 2015 Updated Block OE fixes from previous document version.
17 March, 2015 Updated for 05.33.006.5.096 (Block OE), 8.1.6.96(File OE), and 1.3.6.1.0096
(Unisphere).
16 December, 2014 Updated for the release of VNX for Block 05.33.000.5.081.
15 December, 2014 Updated the Data at Rest Encryption (D@RE) feature description
14 December, 2014 Editorial update.
13 November, 2014 Updated fixes and known issues for release:
• 05.33.000.5.079 (Block)
• 8.1.3.79 (File)
12 October, 2014 Editorial update.
11 October, 2014 Updated for a security advisory.
10 September, 2014 The known issues list has been updated.
09 September, Updated software revision numbers:
2014 • 05.33.000.5.074 (Block)
08 July, 2014 Updated for release:
• 05.33.000.5.072 (Block)
• 8.1.3.72 (File)
• 1.3.3.1.0072-1 (Unisphere)
06 March 2014 Updated fixes from previous document version.
05 February2014 SP3 release:
• 05.33.000.5.051 (Block)
• 8.1.2.51 (File),
• 1.3.2.1.0051 (Unisphere)
04 January 2014 Changed symptom description for AR607962 in the Fixed problem section under VNX
Operating Environment for Block 05.33.000.5.038.
03 January 2014 SP2.2 release 05.33.000.5.038 (Block)
02 November 2013 SP2.1 release 05.33.000.5.035 (Block)
01 October 2013 SP2 release 05.33.000.5.034 (Block), 8.1.1.33 (File), 1.3.1.1.0033 (Unisphere),
1.3.1.1.0033 (ESRS IP Client), 8.1.1.33 (VIA), and 1.3.1.1.0033 (USM)

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
2
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Software media, organization, and files

These release notes contain supplemental information about:

 EMC VNX Operating Environment (OE) for Block
 EMC VNX Operating Environment (OE) for File
System Management
Unisphere UI
Platform
Security
Replication
CIFS
ESRS (Control Station)
RecoverPoint FS
Migration
 Unisphere
Unisphere Analyzer
Unisphere Host software, CLI, and Utilities
Unisphere Quality of Service (QoS) Manager
 Virtual Provisioning
 FAST Cache and FAST VP
 EMC SnapView for:
VNX OE for Block
Admsnap
Admhost
 EMC SAN Copy for VNX OE for Block
 EMC MirrorView/Asynchronous and MirrorView/Synchronous for VNX OE for
Block
 EMC Serviceability for VNX OE for Block, VNX OE for File, and Unisphere
Unisphere Service Manager (USM)
VNX Installation Assistant (VIA)
EMC Secure Remote Support (ESRS) IP Client
 EMC Snapshots for:
VNX OE for Block
SnapCLI
 Virtualization for EMC VNX for:
VNX OE for Block
VNX OE for File

Software media, organization, and files

The VNX OE for Block version 05.33.008.5.119 and the VNX OE for File version 8.1.8.119 are
available in their respective upgrade bundles.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
3
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
New features and enhancements

To upgrade to the VNX OE for Block version 05.33.008.5.119 or the VNX OE for File
version 8.1.8.119, use the Unisphere Service Manager (USM) System Software
wizards. For the latest version of USM, go to EMC Online Support at
Support.EMC.com and choose Support by Product > VNX2 Series > Downloads.

You must perform VNX File OE upgrades before performing upgrades for any attached
VNX Block systems.

You can also obtain updated versions of the following software at Support.EMC.com:
 Unisphere version 1.3.8.1.0119
Unisphere Host Agent version 1.3.8.1.0119
VNX for Block CLI version 7.33.8.119
Unisphere Storage System Initialization Utility version 1.3.8.1.0119
Unisphere Server Utility version 1.3.8.1.0119
 Unisphere Service Manager version 1.3.8.1.0119
 VNX Installation Assistant version 8.1.8.119
 EMC Secure Remote Support IP Client version 1.3.8.1.0119

Online access to VNX installation documents

As of March 2015, VNX2 systems do not ship with printed installation manuals. EMC recommends
downloading the latest version of this documentation from the VNX product page at
support.emc.com or from mydocuments.emc.com > VNX Series > Install VNX2 or VNX-F series.

New features and enhancements

Fixed-block deduplication with file system data

For VNX unified systems, this release introduces the ability to enable and disable fixed-block
deduplication on a specific file storage pool that is built from VNX for Block storage pool thick or
thin LUNs, or on a file system that is created on a metavolume. The Deduplication enabler must be
installed on the system. This feature allows you to maximize efficiency on file data that contains
duplicate information, as well as frees up space on VNX for Block storage pools for reuse.
You can enable deduplication on a VNX for File storage pool if it does not use shared disks (volumes
that are sliced or striped from a LUN), and also if it contains only file systems that use the split ufs
Log Type (default). You can also enable deduplication on a file system that is created on a
metavolume if the metavolume does not use shared disks, and if the file system uses a split log file.

Thin LUN low-space handling enhancements

For VNX unified systems, this release introduces the ability to handle low-space conditions in a VNX
for Block storage pool that contains thin LUNs used for VNX for File storage. When the Free Capacity

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
4
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 New features and enhancements

in a VNX for Block storage pool drops below the Low Space Threshold, affected file systems and
read/write checkpoints are remounted as read-only, and replication sessions will be stopped. This
helps prevent out-of-space conditions.

The Low Space Threshold is a system-assigned value for each VNX for Block storage pool where VNX
for File OE file systems are in use, and built on thin LUNs only. This value does not apply to thick
LUNs.

The value of the Low Space Threshold varies by system. It is based on the total number of Data
Movers multiplied by the memory of each Data Mover. For example, a VNX5400 system that has four
Data Movers, each with 6 GB memory, is assigned a Low Space Threshold of 24 GB for each VNX for
Block storage pool where file systems are in use and built on thin LUNs.

Once the Low Space Threshold is reached on the VNX for Block storage pool, file systems and
read/write checkpoints are remounted as read-only and replication sessions are stopped. To
recover from a Low Space condition, action must be taken to increase the space above the Low
Space Threshold on the VNX for Block storage pool. For example: adding storage to the pool;
migrating LUNs; and performing space reclaim on file systems.

Once space becomes available, file systems, read/write checkpoints, and replication sessions can
be restored to normal operation, either by using Unisphere (Storage > File Systems > Mounts >
Restore), or by running the CLI server_mount server_2 -restore -all command. If the low-space
condition occurred on the source side of a replication session, the replication session is
automatically restarted once the restore operation is completed. However, if the low-space
condition occurred on the destination side...the replication session must be manually stopped and
then restarted from the Source side of the replication session.

Automatic notification of new firmware updates

When logged into a system, the latest version of USM automatically scans for and notifies
you if a disk firmware update is available. If an update is available a popup message is
displayed at the bottom of the System page.
A popup message will be displayed and will contain the name of the sytem for which there is
a firmware update.
Clicking on either the popup message or the icon displayed at the bottom of the page will
launch the USM Online Disk Firmware Upgrade (ODFU) wizard, where you can see which
updates are available for your system and proceed with a non-disruptive disk firmware
update.
This feature is supported on all VNX systems, but is not supported on legacy CLARiiON,
Celerra, or VNX Gateway systems.
Changes to Proactive Sparing – New Resiliency mode
The criteria to fault a drive once it enters proactive sparing have been changed in this release. Drives
being proactively spared will no longer be faulted because of media errors. This will enable the RAID
group to stay redundant for a longer period of time when drives are reporting media errors during
proactive sparing. This is called Resiliency mode.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
5
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
New features and enhancements

Drives that are reporting a large number of media errors may exhibit slow response times
which may propagate to the host. In environments where hosts cannot ride through these
periods of slowness, the original proactive sparing criteria which fault drives that continue to
report media errors may be preferable. To make this change, contact EMC Support.
At this time, this feature is available on select drives only (TLAs 005049675 and
005049677).
Support for IPv6 configurability
For Block-only systems, the main enhancement for Block-only SPs is the ability to customize
all 128-bits of the IPv6 address using the naviseccli command-line interface. In addition,
some IPv6 settings can be enabled, disabled, or set from the Unisphere GUI interface.
Use the following naviseccli example to custom configure all 128-bits of the IPv6 address:
/nas/sbin/naviseccli -h networkadmin -set -ipv6 -manual -address
3ffe:80c0:22c:4c:1319:8a2e:370:7348 -gateway
fe80::21e:67ff:fe6a:50a9
For Unified/File arrays, the setting of IPv6 addresses on the Unified/File SPs has also been
enhanced, but with several restrictions:
• Before using IPv6 on the SPs, the IPv6 address and gateway must first be set on the
primary Control Station.
• Also, the first 64-bits of the SP IPv6 address (Control Station Prefix), must be based
on the Prefix value used by Control Station 0.
• Never use naviseccli to set IPv6 addresses on the SPs for Unified/File systems, as it
will break IPv6 communications.
• Always use the Control Station command-line script, clariion_mgmt, to configure the
Proxy ND service and SP IPv6 addresses for Unified/File systems.
Two main options:
Use the following example to start the Proxy ND service while automatically configuring IPv6
addresses on the SPs based on the Control Station prefix and the array's WWN identifier (EUI-
64 format): /nas/sbin/clariion_mgmt -start -use_proxy_nd
Or, use the following example to start the Proxy ND service, while specifying the first 64-bits
based on the Control Station Prefix value, and customizing the last 64-bits of the address
(InterfaceID): /nas/sbin/clariion_mgmt -start -spa_ip6
2620:0:170:420a::11 -spb_ip6 2620:0:170:420a::12 -use_proxy_nd.

Configuring virtual ports

When configuring second and successive virtual ports (vports) on an existing physical
interface on the SP, only the newly added virtual port is reinitialized, and not the physical
interface or previously set virtual ports.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
6
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 New features and enhancements

File space reclaim

For file systems that are built on thin LUNs from VNX for Block storage pools, you can now
free up (reclaim) space in the pool after files and checkpoints have been deleted. You can
reclaim space in the storage pool from either a Production File System (PFS) on a thin LUN or
a checkpoint (SavVol) on a thin LUN.
To do this, choose one of the following methods:
• Manually run a file system or checkpoint space reclaim process when needed.
• Create a schedule to automatically run a file system or checkpoint space reclaim process daily,
weekly, or monthly when required.

CBFS Technical Debt

The CBFS file deduplication functionality was enhanced. Concurrency of CBFS metadata was
improved to allow more parallel metadata access. Latency, CPU usage, and locking contention
issues were reduced. Deduplication memory usage was reduced to allow an increase of speed in
other functionalities.

Localization updates
Localization of Unisphere, USM, VIA: Chinese, Japanese, and Korean.
Localization of Unisphere Initialization wizard: Chinese, Japanese, Korean, French, German, Italian,
Spanish, and Portuguese.

Java support
The following 32 bit Java Platforms are verified by EMC and compatible for use with Unisphere,
Unified Service Manager (USM), and VNX Installation Assistant (VIA):
• Oracle Standard Edition 1.7 up to Update 75
• Oracle Standard Edition 1.8 up to Update 25
The 32-bit JRE is required, even on 64 bit systems.
JRE Standard Edition 1.6 is not recommended because Oracle has stopped support for this edition.

IMPORTANT: Some new feature/changes may not take effect in the Unisphere GUI after an upgrade.
To avoid this, EMC recommends clearing your Java cache after an upgrade.

VNX2 Block-to-Unified Upgrades

In this latest release, EMC will support Block-to-Unified upgrades for the VNX2 family of products.
This type of upgrade changes an existing VNX 5200, 5400, 5600, 7600, or 8000 block-only model to
a Unified system of the same model number.

Block-to-Unified upgrades are available to customers through an EMC Professional Services

engagement only and is not a customer installable procedure.

VNX2 In-Family Data-in-Place Conversion

This version of VNX OE supports in-family data in place (DIP) conversion from
VNX5200/5400/5600/5800 to a higher model VNX2 series system, up to a VNX7600. In-family DIP

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
7
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
New features and enhancements

conversions in the VNX2 series DPE-based systems re-use the chassis within the initial system,
replacing only the storage processors and Data Movers (File or Unified) with those needed for the
resulting system and do not involve disconnecting any component cabling.

The above conversion is available to customers through an EMC Professional Services engagement
and is not a customer installable procedure.

16Gb/s 4-port Fibre Channel I/O module

New 4-port 16Gb/s Fibre Channel I/O module available and supported on the VNX2 storage
processors (SPs). Available for ordered systems, as an upgrade into empty SP I/O module slots on
existing VNX2 systems, or as a swap upgrade of existing 8Gb/s Fibre Channel I/O modules. The
swap upgrade is performed by a service provider. This I/O module does not support Fibre Channel
connectivity to File OE Data Movers.

Firmware
The following firmware variants are included with this release:
• If a lower revision is installed, the firmware is automatically upgraded to the revision
contained in this version.
• If a higher revision is running, the firmware is not downgraded to the revision contained
in this version.
Enclosure type Current firmware version
15 Drive 3.5” DAE 1.54
25 Drive 2.5” DAE 1.54
60 Drive 3.5” DAE 8.07
120 Drive 3.5” DAE 15.12

Platform BIOS BMC FW POST

MT 33.30 25.00 68.10
JF 33.40 25.00 60.10

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
8
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Fixed problems
VNX Operating Environment for Block 05.33.008.5.119, VNX Operating Environment
for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119
Category Details Symptom Fix Version

VNX File OE, Platforms: All The creation of a 2TB file system from ViPR The code was updated to increase the Exists in version:
System Severity: High failed. XML API session timeout. 8.1.0.15
Management Tracking: Fixed in:
64298388/ 8.1.8.119
654578/ 655198
VNX File OE, Platforms: All User experienced a slow host write The code has been enhanced with a Exists in version:
CBFS Severity: High response time or a timeout. scalable muticore friendly mechanism for 7.0.2.9
processing and signaling a transaction Fixed in:
Tracking: 384143
journal. This reduces I/O latency and
8.1.8.119
increases IOPS.
VNX File OE Platforms: All The server_date did not reflect the The code has been updated so that the Exists in version:
Severity: Medium sync_delay option set by the customer. server_date timesvc command now 7.0.54.502
Tracking: shows the sync_delay option as it was Fixed in:
56244034/ set by the customer. 8.1.8.119
600639
VNX File OE, Platforms: All A user was unable to mount replication The code was updated to pass the Exists in version:
NFS Severity: Medium destination checkpoints via NFSv4 if the access policy to checkpoints on the 7.1.55.3
Tracking: access policy of the file system was not destination system. Fixed in:
54333266/ NATIVE. 8.1.8.119
610491
VNX File OE Platforms: All When using the nas_checkup, a warning is The code was updated to exclude the Exists in version:
Severity: Medium returned for parameter canRunRT whose canRunRT parameter while checking for 7.1.71.1
Tracking: current and default values are not the same. default values. Fixed in:
56242026/ 8.1.8.119
613387

VNX File OE Platforms: All When a file was overwritten and the file Updated the code by fixing the checks in Exists in version:
Severity: Medium system was full, the new file creation is the file space reservation. 7.0.54.502
Tracking: allowed, even if the new file size was larger Fixed in:
54995532/ than the old file size. Writing this much data 8.1.8.119
generated a QUOTA_EXCEEDED error. The
613405
end result was that the old file was lost and
the new file couldn’t be created.
VNX File OE Platforms: All Execution of the command, The code was updated to disallow the Exists in version:
Severity: High nas_replicate –switchover, failed. creation of interconnects when the 5.6.51.3
/nas/site/cshosts file contains an Fixed in:
Tracking:
47184462 / invalid CMU value. 8.1.8.119
613479/ 485477
VNX File OE Platforms: All A Db chk failed to detect an invalid entry The code was updated with the ability to Exists in version:
Severity: High that was inserted manually into the detect invalid entries within files. 6.0.41.4
/nas/server/slot_2/ufs file. Fixed in:
Tracking:
54593730/ 8.1.8.119
613485

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
9
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX Block OE Platforms: All LUNs with little or no I/O were implicitly Updated the code to discount non-I/O Exists in version:
Severity: Medium trespassed. commands against the ALUA counter. 05.33.000.5.038
Tracking: Fixed in:
62840900/ 05.33.008.5.119
643410
VNX File OE Platforms: All The Control Station rebooted unexpectedly The code has been modified to avoid the Exists in version:
Severity: Medium after 485 days of uptime. situation which caused the reset. 7.0.40.1
Tracking: Fixed in:
53513236/ 8.1.8.119
649331
VNX File OE, Platforms: All The command nas_cs -set - The issue was resolved by updating the Exists in version:
System Severity: Medium dns_domain backup failed. code’s domain name validation rules. Previous versions
Management Tracking: 649841 of code
Fixed in:
8.1.8.119
VNX File OE, Platforms: All A bug check was initiated on the Data Mover The code has been updated to ensure Exists in version:
SnapSure Severity: Medium when PMDV was deleted while the prefetch PMDV will wait for the I/O to complete 6.0.70.4
Tracking: I/O still exists. before deletion. Fixed in:
59553716/ 8.1.8.119
651820
VNX File OE, Platforms: All When the dbms_backup script is run as The code has been updated to exclude Exists in version:
Platform Severity: Medium nasadmin, a failure occurred because the servers that have ACL set. Only the 7.1.56.5
Services nasadmin didn’t see the server when ACL servers that have ACL=0 will be included. Fixed in:
Tracking:
was set.
55783542/ 8.1.8.119
651834
VNX File OE, Platforms: All When the FS is paused, the nas_fs - The code now allows the nas_fs - Exists in version:
Install, Severity: Medium info <fs_name> -o mpd command info <fs_name> -o mpd command 7.1.65.8
Configure cannot retrieve the Multi-Protocol Directory to get Multi-Protocol Directory Fixed in:
Tracking:
54065574/ information. Information when the FS is paused. 8.1.8.119
652192
VNX File OE, Platforms: All A Data Mover bugchecked with error code The code has been updated to ensure Exists in version:
Storage Severity: Medium 0x00009d5fd7. that the initial inquiry data is validated 7.1.65.8
Tracking: before it is cached. Fixed in:
61627400/ 8.1.8.119
652203
VNX File OE, Platforms: All A server exceeded the timeout value during The code has been updated to reduce Exists in version:
Storage Severity: High a boot operation. any boot time delay. 7.1.65.800
Tracking: Fixed in:
60532776/ 8.1.8.119
652204

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
10
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

VNX File OE, Platforms: All When executing cpio -m on a Solaris For cached writes, the code was updated Exists in version:
UFS Severity: Medium client to migrate files an NFS share folder, to not use the file's modified time when 8.1.2.51
Tracking: the modified time of the files were not kept flushing data to disk. The cached Fixed in:
63811662/ as expected. timestamp is used instead. 8.1.8.119
655693
VNX Block Platforms: All Pool LUNs were offline after creating a large The code has been updated to fix this Exists in version:
OE, CBFS Severity: Medium number of LUNs at the same time. issue. 05.33.000.5.051
Tracking: Fixed in:
64781490/ 05.33.008.5.119
659363
VNX File OE, Platforms: All Thousands of defunct sysadmin accounts The code now prevents sending a Exists in version:
System Severity: Medium were created on the Control Station. request to the domain master when the 8.1.1.33
Management global adminstrator account could not be Fixed in:
Tracking:
found.
64507704/ 8.1.8.119
661838/ 664516
VNX Block OE Platforms: All A single SP rebooted with 0x5900000. Updated the code to detect and avoid the Exists in version:
Severity: Medium condition that caused the reboot. 05.33.000.5.038
Tracking: Fixed in:
64975010/ 05.33.008.5.119
661855
VNX Block Platforms: All The management servers re-started EMC has added the -np switch to a Exists in version:
OE, System Severity: Low frequently on both SPs. naviseccli command issued on the 05.33.000.5.038
Management Tracking: Control Station to avoid this issue. Fixed in:
60933588/ 05.33.008.5.119
662081
VNX Block Platforms: All An error message with 0x715281e8 was The code has been updated to include Exists in version:
OE, Severity: Medium reported in the navi log. creating and accessing 05.33.000.5.051
MirrorView FarQueryAndHoldListMutex in the Fixed in:
Tracking:
64921968/ global namespace. 05.33.008.5.119
662696
VNX Block Platforms: All The system was unable to create FAST The code has been updated so that an Exists in version:
OE, Severity: Medium Cache during a non disruptive upgrade. error is shown to the user when an NDU 05.33.000.5.072
Unisphere Tracking: is in progress, and the FAST cache Fixed in:
65169048/ creation cannot proceed during the NDU. 05.33.008.5.119
664516
VNX Block OE Platforms: All A single SP rebooted with bugcheck 7E The code has fixed a condition that led to Exists in version:
Severity: Medium [SYSTEM_THREAD_EXCEPTION_NOT_HA the reboot and bugcheck. 05.33.000.5.038
NDLED].
Tracking: Fixed in:
65263512/ 05.33.008.5.119
666561
VNX File OE, Platforms: All An NFS export created on a VDM appeared The code has been updated and now Exists in version:
System Severity: Low in the Unisphere GUI, but then disappeared blocks NFS export indications when the 8.1.2.51
Management later. export is created on a VDM. Fixed in:
Tracking:
64979880/ 8.1.8.119
666806

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
11
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX Block Platforms: All Storage Processor B was very slow to The code was updated and a command Exists in version:
OE, System Severity: Medium respond to any commands and had to be re- issued by APL will retrieve array 05.33.000.5.038
Management started. environment data. Fixed in:
Tracking:
65228246/ 05.33.008.5.119
666980
VNX File OE, Platforms: All The /nas/log/cmd_log showed that The issue was resolved by enhancing the Exists in version:
System Severity: Low nas_storage -sync command was code to prevent triggering trespass 05.33.000.5.038
Management executed every 5 minutes. handling code when a non-File LUN is Fixed in:
Tracking:
60933588/ trespassed. 05.33.008.5.119
667347
VNX Block Platforms: All Unisphere Analyzer disk statistics are not The code has been fixed to properly Exists in version:
OE, Analyzer Severity: Low always updated (may show 0). update the statistics. Previous versions
Tracking: 667981 of code
Fixed in:
05.33.008.5.119
VNX Block Platforms: All The USM report wizard creates folders with The issue was resolved by correctly using Exists in version:
OE, USM, Severity: Low multiple version strings when it creates and API when generate the string for the 05.33.000.5.072
Unisphere saves the reports. folder name.
Tracking: Fixed in:
65466552/ 05.33.008.5.119
668662
VNX File OE, Platforms: All The destination file system replication or Fixed in code. Exists in version:
SnapSure Severity: Medium migration was corrupt, but the source file 8.1.1.33
system was clean. Fixed in:
Tracking:
63316290/ 8.1.8.119
669268
VNX File OE, Platforms: All 5 weekly historical statistical files were The issue was resolved by ensuring that Exists in version:
System Severity: Low found in every time a database table is created, it 7.1.56.5
Management Tracking: /nas/jserver/sdb/control_statio gets assigned a default weeksToKeep
Fixed in:
62954784/
n/data_movers/fs_capacity/ parameter.
directory, instead of the expected files. 8.1.8.119
669470
VNX Block Platforms: All Incomplete I/O requests were seen by an An internal code issue was corrected so Exists in version:
OE, Severity: Medium ESX server under a workload with that the I/O requests complete in a 05.33.000.5.038
MirrorView Tracking: overlapping write requests. timely manner. Fixed in:
60859568/ 05.33.008.5.119
669717
VNX Block OE Platforms: All Relocation failed when a scheduled window Fixed in code. Exists in version:
Severity: Medium ends. This may cause LUNs to go offline. 05.33.000.5.051
Tracking: 673991 Fixed in:
05.33.008.5.119
VNX Block Platforms: All The USM DAE install wizard's cabling The USM DAE install Wizard's cabling Exists in version:
OE, USM Severity: Low suggestion was incorrect. suggestion has been updated and is now 05.33.000.5.038
correct.
Tracking: Fixed in:
65637828/ 05.33.008.5.119
676161

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
12
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

VNX File OE, Platforms: All Customer encountered a bugcheck with The code has been updated to account Exists in version:
UFS Severity: High divide exception. for the bug that lead to this issue. 8.1.1.33
Tracking: Fixed in:
66354048/ 8.1.8.119
677685
Unisphere, Platforms: All The naviseccli storagegroup XML output did Updated the naviseccli output of the Exists in version:
CLI Severity: Medium not report the host name within the XML storagegroup –list -host so that the 05.32.000.5.207
Tracking: elements. host name displays in between XML tags. Fixed in:
65503296/ 05.33.008.5.119
678064
Unisphere, Platforms: All Unisphere Host Agent logged message: This message was removed from the Exists in version:
Host Severity: Low EV_RAIDGroupState::RAIDGroupOpP Unisphere Host Agent. 05.33.000.5.052
Software, CLI, riorityConvert - Enum out of
Tracking: range, -1. Fixed in:
Utilities
65814450/ 05.33.008.5.119
678938
NDMP Platforms: All A backup report showed 0MB is processed Fixed in code. Exists in version:
Severity: High after a successful backup. Previous versions
Tracking: of code
64121286/ Fixed in:
680458 8.1.8.119
VNX File OE, Platforms: All A customer encountered a bad bn error on Fixed in code. Exists in version:
UFS Severity: Medium the destination side when performing an Previous versions
Tracking: offload copy operation. of code
60825130/ Fixed in:
680460 8.1.8.119
Unisphere Platforms: All An error message was returned when The fixed code avoids the PSM error Exists in version:
Severity: Medium generating certificate signing request via the when replacing the certificate signing 05.32.000.5.207
Setup page. request.
Tracking: Fixed in:
64280272/ 05.33.008.5.119
684304
VNX Block OE Platforms: All A single SP bugchecked due to a condition The code has been updated to add lock Exists in version:
Severity: Medium between the aggregate I/O cancelation path protection and now avoids the 05.33.000.5.074
Tracking: and the normal I/O path. occurrence. Fixed in:
67016532/ 05.33.008.5.119
684704
Unisphere Platforms: All When Unisphere Central is in the system’s The code has been updated and now Exists in version:
Analyzer, Severity: Low domain, the GUI's Statistics/Retrieve filters out Unisphere Central nodes from 05.32.000.5.209
Unisphere Tracking: Archive page did not display the NAR files the system drop downs on the Retrieve Fixed in:
Central 64983040/ for retrieval. Users were required to use CLI Archive and Performance Data Logging
as a workaround to list and retrieve NAR pages. 05.33.008.5.119
686352/ 673140
files.
VNX Block OE Platforms: All A single storage processor bugcheck Changed the SAS backend code to Exists in version:
Severity: Medium (0x03302004) occurred. handle a certain unexpected command. 05.32.000.5.209
Tracking: Fixed in:
62922652/ 05.33.008.5.119
686495

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
13
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX Block Platforms: All A pool expansion failed. The issue was fixed by performing a full Exists in version:
OE, Severity: Medium poll request. 05.32.000.5.015
Unisphere
Tracking: Fixed in:
64586292/ 05.33.008.5.119
686517
VNX Block Platforms: All A single storage processor bugcheck Changed the code to handle unexpected Exists in version:
OE, Fibre Severity: Medium (0x01901004, 0x0190101A) occurred when states from connected devices under 05.32.000.5.207
Channel a Fibre Channel logout command was these conditions.
Tracking: Fixed in:
61787212/ received while processing a link down
event. 05.33.008.5.119
687024/ 687026
VNX File OE, Platforms: All When creating a fast clone (for a vmdk Modified the code’s version file removal Exists in version:
UFS Severity: Medium image), the Data Mover hung, or returned logic to avoid deadlock. 7.1.76.4
with a message, sync: no progress.
Tracking: Fixed in:
66254656/ 8.1.8.119
687722
VNX File OE, Platforms: All Share paths were not canonicalized before The code has been updated to Exists in version:
CIFS Severity: Low stored in the share databases. canonicalize paths to store them and 6.0.70.4
Tracking: add code to canonicalize existing paths, Fixed in:
61227688/ if required. 8.1.8.119
688267
VNX Block OE Platforms: All The FEDisk code path was executed multiple The code has been updated to Exists in version:
Severity: Medium times, so that the memory finally was incorporate boundary handling, which 05.33.000.5.052
Tracking: consumed out. resolves a memory leak issue. Fixed in:
67384810/ 05.33.008.5.119
688757

VNX File OE, Platforms: All A Data Mover failover command failed with The issue was resolved by improving Exists in version:
System Severity: Medium an unclear error message, Execution error cause detection and returning 8.1.2.51
Management Tracking: failed: valid_entry: Routine clearer error message. Fixed in:
failure. [EXTRACTOR.set_entry.
64647466/ 8.1.8.119
692625

VNX File OE, Platforms: All When a storage pool encounters an error Fixed in code. Exists in version:
Virtual Severity: Medium and goes offline, it's possible that the 05.33.000.5.052
Provisioning Tracking: command Naviseccli storagepool
Fixed in:
-list still shows the status as OK.
67699060/ 05.33.008.5.119
692639
VNX File OE, Platforms: All Single SP bugcheck happened when the The code has been updated to reduce Exists in version:
Virtual Severity: Medium array was under high pressure from external the pressure on the array under these 05.33.006.3.235
Provisioning I/Os and internal background operations, conditions.
Tracking: 692912 Fixed in:
while at the same time the other SP
rebooted. 05.33.008.5.119

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
14
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

VNX File OE, Platforms: All The Installation process failed when the The code now checks the IP addresses of Exists in version:
Platforms Severity: Medium same IP was assigned to SPA and SPB. SPA and SPB to ensure they are not the 8.1.3.72
Tracking: same. Fixed in:
67650918/ 8.1.8.119
693125
VNX Block Platforms: All An error was returned when several Fixed in code. Exists in version:
CLI Severity: Low naviseccli connection -pingnode All previous
or naviseccli connection - versions
Tracking: 693686
traceroute commands were executed at
Fixed in:
the same time.
05.33.008.5.119
VNX File OE Platforms: All When a file is detected by an antivirus, there The code now adds the IP address of the Exists in version:
Severity: Medium is no information about the anti virus engine anti virus engine which has detected the Previous versions
Tracking: which has detected the virus. virus in the log event. of code
64309006/ Fixed in:
693813 8.1.8.119
VNX File OE Platforms: All An error was encountered: The code has been updated to refuse the Exists in version:
Severity: High ../ufslog.cxx at line: 11125 : operations that caused the error. 8.1.2.51
sync: no progress reducing
Tracking: dirty list. Fixed in:
66537256/ 8.1.8.119
693832
VNX Block, Platforms: All A single processor bugcheck (0xE1198006) Fixed in code. Exists in version:
MirrorView Severity: Medium occurred. 05.33.000.5.052
Tracking: Fixed in:
68061026/ 05.33.008.5.119
695711
Unisphere Platforms: All The User Names column of the User Quotas The issue was resolved by optimizing the Exists in version:
Severity: Medium List in Unisphere populated with names very user names lookup algorithm in the 8.1.3.79
slowly. code.
Tracking: Fixed in:
58851466/ 8.1.8.119
696532
Unisphere, Platforms: All The Host Agent service could not be started Fixed in code. Exists in version:
Host Severity: Medium successfully on Red Hat Enterprise Linux 7. 05.32.000.5.216
Software, CLI, Tracking: Fixed in:
Utilities 67949012/ 05.33.008.5.119
696546
VNX File, Platforms: All Symmetrix poller shut down and never The issue was resolved by adding the Exists in version:
System Severity: Low restarted. ability to restart Symmetrix poller 7.1.56.5
Management Tracking: automatically to the code. Fixed in:
63091868/ 8.1.8.119
696681
VNX Block Platforms: All A storage processor rebooted due to Fixed in code. Exists in version:
OE, Virtual Severity: Medium bugcheck code 0x E111805F. 05.33.000.5.052
Provisioning Tracking: Fixed in:
68222912/ 05.33.008.5.119
697328

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
15
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX Block Platforms: All Unable to create a clone if the clone The code is updated to use the Exists in version:
OE, Severity: Medium destination LUN is a metaLUN and the metaLUN's configured capacity instead 05.33.000.5.074
Unisphere metaLUN has a configured capacity. of LUN's capacity when checking
Tracking: Fixed in:
destination LUN's size.
68384336/ 05.33.008.5.119
698899/ 703769
VNX File OE, Platforms: All SRM queries caused frequent Control The issue was resolved by caching the Exists in version:
System Severity: Medium Station reboots due to an out-of-memory output of Symmetrix pools queries in the 8.1.1.33
Mangement condition. updated code.
Tracking: Fixed in:
65172254/ 8.1.8.119
699436/ 699435
VNX File OE, Platforms: All After a VNX for File upgrade, the CIFS server The issue was resolved by removing the Exists in version:
System Severity: Medium was no longer available. –Force option when a virtual device 7.1.76.4
Management Tracking: gets deleted from the Unisphere GUI. Fixed in:
68106062/ 8.1.8.119
698162
68191680/
700842/ 700096
CBFS Platforms: All The LUN prepare process was frozen. The code has been updated to fix a Exists in version:
Severity: Medium reference count leak. 05.33.000.5.079
Tracking: Fixed in:
68016422/ 05.33.008.5.119
700220
VNX Block OE Platforms: All A single storage processor bugcheck When replacing system drive, please wait Exists in version:
Severity: Medium occurred while replacing a system drive. for at least 30 seconds before inserting 05.33.000.5.074
the new drive.
Tracking: Fixed in:
68250170/ 05.33.008.5.119
700491
VNX File OE, Platforms: All In the time zone of UTC+14 (or UTC+13 The naviseccli autotiering command now Exists in version:
Unisphere Severity: Low during daylight savings time), when works as expected in all time zones. 8.1.2.51
upgrading the Unisphere File software, the
Tracking: Fixed in:
68621960/ post upgrade check was failing with "Error
3501: Storage API code=4562: 8.1.8.119
700810
SYMAPI_C_CLAR_CIL_FAILURE Failure
during Clariion Interface Layer's attempt to
obtain data from Clariion array". The
control station "nas_storage -c -a"
command also failed, with the same error.
The naviseccli command autotiering -info -
schedule (from the control station or to the
array) failed with: -GMTOFF:Value 840 is
greater than maximum. The maximum value
is 780.
VNX File OE, Platforms: All Command nas_fs -info -all failed The issue was resolved by caching the Exists in version:
System Severity: Medium with a backtrace. output of Symmetrix pools queries. 8.1.1.33001
Management Tracking: Fixed in:
67458600/ 8.1.8.119
699981/ 701067

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
16
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

VNX Block Platforms: All LDAP login failed if there was no leaf Fixed in code. Exists in version:
OE, Severity: Medium certificate in an LDAP configuration. 05.33.000.5.079
Unisphere Tracking: Fixed in:
68540890/ 05.33.008.5.119
701325/680720
VNX Block OE Platforms: All Errors occured when a drive went end of life Fixed in code. Exists in version:
Severity: Medium and reported drive faults at the same time. 05.33.000.5.038
Tracking: Fixed in:
68458206/ 05.33.008.5.119
701988
VNX Block OE Platforms: All SP A rebooted due to a bugcheck. The code has been updated to ensure all Exists in version:
Severity: Medium references have successfully allocated 05.33.006.3.250
pages before proceeding to start a front-
Tracking: 702129 Fixed in:
end transfer.
05.33.008.5.119
VNX Block Platforms: All A Navi Cimom dump was seen due to The MVS admin code has been updated Exists in version:
OE, Severity: Medium memory leaks in MirrorView/S admin. to avoid this issue. 05.32.000.5.015
MirrorView Tracking: Fixed in:
55507470/ 05.33.008.5.119
702768
VNX File OE, Platforms: All A user encountered an error that states the Fixed in code. Exists in version:
System Severity: Medium following when upgrading from a previous 8.1.6.96
Mangement Tracking: 703739 version of code: 8.1.6.101
Error: File system has mount
Fixed in:
record present, but is not in
use in filesys table. 8.1.8.119
Error: File system is found not
in use, yet there is rw/ro
server in its entry in
$NAS_DB/volume/filesys file.
VNX Block Platforms: All Single SP bugcheck. The code has been updated so that a Exists in version:
OE, Platforms Severity: Medium client message and sequenceTag will be 05.33.000.5.081
Tracking: handled correctly. Fixed in:
69045616/ 05.33.008.5.119
704235
VNX File OE, Platforms: All After a client reboot, a server panicked Fixed in code. Exists in version:
NFS Severity: Medium when NFSV4 locks were held by the client. 8.1.3.79
Tracking: Fixed in:
68927792/ 8.1.8.119
704534
Unisphere Platforms: All If Snapshots were taken on dedup enabled Fixed the GUI to show N/A in both of Exists in version:
Severity: Medium LUNs in a pool, the GUI incorrectly showed these fields for dedup LUNs. 05.33.006.5.096
Tracking: 706194 values in the Snapshot Allocations and Fixed in:
Snapshot Subscriptions fields under LUN
properties. 05.33.008.5.119

VNX File OE, Platforms: All MoverStats statSet="NFS-All" XML API query The code implemented a "v3aai" counter Exists in version:
System Severity: Low did not return "v3aai" counter. in Jserver and XML API . 8.1.6-34229
Management
Tracking: 706255 Fixed in:
8.1.8.119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
17
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX File OE Platforms: All An incoherency was seen in the NFS The code has been updated to resolve Exists in version:
Severity: Medium statistics counters. this issue. 8.1.6
Tracking: 706261 Fixed in:
8.1.8.119

VNX Block Platforms: All During a power failure, the storage pool was The code was updated to only mark the Exists in version:
OE, NFS Severity: Medium incorrectly marked as recovery needed. LUN as recovery needed, not the storage 05.33.000.5.051
Tracking: pool. Fixed in:
64781490/ 05.33.008.5.119
706840
CIFS Platforms: All When Vista or Windows 2008 server clients The code was fixed to properly handle Exists in version:
Severity: Medium access to a share and compress files, an the rename of a directory in these 2.4.3.21980
attempt to rename a directory resulted in circumstances.
Tracking: Fixed in:
blocked SMB2 threads on the Data Mover
67948752/ 8.1.8.119
706949 and a loss of access to the CIFS share.

Vnx Block Platforms: All Attempting to destory a mirror resulted in Fixed a code issue related to I/O Exists in version:
OE, Severity: Medium one or both storage processors rebooting cancellation. Now, the destroy operation 05.33.000.5.074
MirrorView Tracking: unexpectedly. completes correctly. Fixed in:
69335508/ 05.33.008.5.119
707403
CIFS Platforms: All Audit security settings were not correctly The code has been updated to fix a Exists in version:
Severity: Medium restored after a reboot on Data Movers with condition during VDM initialization that 8.1.6
many VDMs and large File System caused this issue.
Tracking: 708253 Fixed in:
configurations.
8.1.8.119

VNX Block OE Platforms: All Customer sees the badly formed log entry. Fixed in code. Exists in version:
Severity: Medium 05.33.000.5.079
Tracking: Fixed in:
69505944/ 05.33.008.5.119
709249
SnapSure Platforms: All When SavVol is larger than 2G, auto-extend The code has been updated to fix this Exists in version:
Severity: Medium cannot stop until all the space in a pool is issue. 7.1.76.401
consumed.
Tracking: Fixed in:
69343968/ 8.1.8.119
711230/ 712801

VNX Block OE Platforms: All The host can experience timeouts due to a Fixed in code. Exists in version:
Severity: Medium bad drive which is streaming hardware 05.33.000.5.074
Tracking: errors. Fixed in:
69490164/ 05.33.008.5.119
711777

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
18
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

VNX Block Platforms: All Storage processor bugchecks occurred Changed iSCSI data port code to improve Exists in version:
OE, iSCSI Severity: High (various, including 0x05900000 and handling of broadcast/multicast packets. 05.33.000.5.038
Driver Tracking: 0x0000001E) on an iSCSI connected Fixed in:
65654434/ storage system due to a packet storm
received by the iSCSI data ports. 05.33.008.5.119
711927/ 671492
VNX Block OE Platforms: All A log entry was recorded in the Windows Fixed in code. Exists in version:
Severity: Medium event log when BBU state was temporarily 05.33.000.5.081
Tracking: unknown. Fixed in:
69682770/ 05.33.008.5.119
712701
CIFS Platforms: All A server might receive invalid kerberos Fixed in code. Exists in version:
Severity: High tickets during SMB authentication, leading Previous versions
to an unexpected error. of code
Tracking:
66615986/ Fixed in:
713081 8.1.8.119

VNX File OE Platforms: All Customer get STATUS_INTERNAL_ERROR for Fixed the internal code that lead to this Exists in version:
Severity: Medium FSCTL_QUERY_ALLOCATED_RANGES request issue. 8.1.2.51
on compressed file.
Tracking: Fixed in:
69662042/ 8.1.8.119
713354

CBFS Platforms: All A service processor bugcheck Fixed in code. Exists in version:
Severity: Medium (0x0000007E) occurred when a LUN 05.33.000.5.052
Tracking: recovery was running. Fixed in:
69776356/ 05.33.008.5.119
713410
VNX File OE, Platforms: All An IPv6 network tool may cause a condition Updated the code for IPv6 handling of Exists in version:
Network Severity: Medium on the Data Mover. network packets to avoid this error. 8.1.3.722
Tracking: Fixed in:
69685320/ 8.1.8.119
713567

Unisphere Platforms: All An unknown exception error message was The code has been fixed to refine the Exists in version:
QoS Manager Severity: Medium encountered when stopping NQM. exception handling to make the error 05.32.000.5.215
Tracking: message as user-friendly as possible. Fixed in:
66928156/ 05.33.008.5.119
713632
Unisphere, Platforms: All Failed to create or expand pool if Fixed in code. Exists in version:
CLI Severity: Medium Management Server was restarted. 05.33.000.5.052
Tracking: Fixed in:
69873438/ 05.33.008.5.119
714173
MirrorView Platforms: All If a storage processor was shut down, the Corrected handling of the error condition, Exists in version:
Severity: Medium peer storage processor rebooted which prevents the reboot. 05.33.000.5.052
unexpectedly due to incorrect handling of
Tracking: Fixed in:
69898952/ an error condition within MirrorView/S.
05.33.008.5.119
715224

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
19
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX File OE, Platforms: All As the load of CPU reaches 12%, mail gets As a fix we have modified the sendmail Exists in version:
Platform Severity: Medium rejected with following error messages config files, which will not reject the mail 7.1.72.1
Services grep "rejecting connections" 80% of CPU load.
Tracking: Fixed in:
/var/log/maillog |tail -20 Apr 25 02:15:46
61526254/ 8.1.8.119
715294 WKPSVNN-PTCC-2165 sendmail[2543]:
rejecting connections on daemon MTA: load
average: 14 Apr 25 02:16:01 WKPSVNN-
PTCC-2165 sendmail[2543]: rejecting
connections on daemon MTA: load average:
14
VNX File OE, Platforms: All UDoctor cannot take the correct Fixed in code. Exists in version:
UDoctor Severity: Medium recommended action. 7.1.76.4
Tracking: Fixed in:
64430016/ 8.1.8.119
715296

VNX File OE, Platforms: All ViPR SRM Client was unable to retrieve NFS The issue was resolved by implementing Exists in version:
System Severity: Medium v4.1 statistics via XML API. NFS v4.1 statistics in XML API. 8.1.3-72
Management Tracking: 717380 Fixed in:
8.1.8.119

CIFS Platforms: All The LDAP configuration file (ldap.conf) is The code is updated to wait for the Exists in version:
Severity: Medium present in the /.etc directory, but completion of LDAP services, before 8.1.3.72
incomplete. allowing NFS/CIFS to use the LDAP name
Tracking: Fixed in:
69680002/ service.
8.1.8.119
718807

CBFS Platforms: All A single storage processor bugcheck The code was adjusted to fix this issue. Exists in version:
Severity: Medium occurred because the log space could not 05.33.000.5.074
be released normally.
Tracking: Fixed in:
69319126/ 05.33.008.5.119
719632
Unisphere Platforms: All Analyzer is not showing LUN utilization Correct the logic not showing the Exists in version:
Analyzer Severity: Medium when it reaches 100%. threshhold value. 05.33.000.5.081
Tracking: Fixed in:
69878898/ 05.33.008.5.119
720666
NFS Platforms: All Under NFSV4 load, the server may crash in Fixed in code. Exists in version:
Severity: Medium some special circumstances. 8.1.3.72
Tracking: Fixed in:
70410652/ 8.1.8.119
720785

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
20
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

CIFS Platforms: All A permissions error occurred for CIFS users The code has been updated to allow non- Exists in version:
Severity: Medium when changing a directory. administrator CIFS users to change the 8.1.2.51
Tracking: directory. Fixed in:
69929998/ 8.1.8.119
721410

VNX Block OE Platforms: All An ESX Storage Vmotion failed at 40% Fixed in code. Exists in version:
Severity: Medium migrating Virtual Machines between LUNs in 05.33.000.5.074
Tracking: the same Storage Pool. Fixed in:
70271682/ 05.33.008.5.119
721881
VNX File OE Platforms: All When a system running an earlier version of To prevent the issue, the customer Exists in version:
Severity: High code was used as a destination to create a should create the destination file system 8.1.6.96
Tracking: 722333 replicationV2 session, the destination file from meta volume with the same log type Fixed in:
system had a mismatched log type between of source file system.
the Control Station and VNX for File OE. 8.1.8.119

To resolve the mismatched file system

created already, customer should ask
support engineer help to resolve it.

CIFS Platforms: All On a compressed file, the following Fixed the code that lead to this issue. Exists in version:
Severity: Medium message was received: 8.1.2.51
Tracking: STATUS_INTERNAL_ERROR for Fixed in:
FSCTL_QUERY_ALLOCATED_RANGES.
69662042/ 8.1.8.119
722593

VNX Block OE Platforms: All When a single strorage processor bugcheck The code has been fixed so that LUNs Exists in version:
Severity: Medium occurred, a LUN was inaccessible on the will be a good state even if one storage 05.33.000.5.052
Tracking: other storage processor. processor has a bugcheck. Fixed in:
70634516/ 05.33.008.5.119
722759
VNX File OE Platforms: All LDAP user failed to login via SSH into The issue was resolved by allowing Exists in version:
Severity: Medium Control Station following Control Station autocreation of a local user for the 7.1.72.1
failover. corresponding LDAP user during login via
Tracking: Fixed in:
SSH.
60586898/ 8.1.8.119
617060
60893710/
623870/ 724173
CIFS Platforms: All A bug check occurred (0x000072e499) Fixed in code. Exists in version:
Severity: Medium when unmounting a file system and Previous versions
Tracking: stopping the virus checker at the same time. of code
58454314/ Fixed in:
724284 8.1.8.119

CIFS Platforms: All CIFS users can't access SFTP with homedir Fixed in code. Exists in version:
Severity: Medium and FQDN domain. Previous versions
Tracking: 724359/ of code
70440966 Fixed in:
8.1.8.119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
21
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

NFS Platforms: All NFS writes are slow after pNFS client Fixed in code. Exists in version:
Severity: Medium switches over the I/O to NFS after a failure. 7.1.76.412
Tracking: Fixed in:
68729530/ 8.1.8.119
725727

CIFS Platforms: All CEPA reports actual path while deleting the when the file is acceded via a symlib Exists in version:
Severity: Medium file instead of symlink path. memorize the path used during the open Previous versions
Tracking: instead of trying to get the path from the of code
triggerSet.
65618098/ Fixed in:
736528 8.1.8.119

VNX Block OE Platforms: All Storage processor B rebooted due to The code has been updated to use a Exists in version:
Severity: Medium bugcheck code 0x0000007E. local variable to store information. 8.1.8.35731
Tracking: Fixed in:
71419220/ 8.1.8.119
737617/ 745754

NFS Platforms: All pNFS: The datamover returns The code has been updated so that the Exists in version:
Severity: Medium NFS4_ERR_TOOSMALL to the Linux client Data Mover returns an smaller layout that 7.1.76.4
Tracking: when the layout description (list of extents) fits the client buffer size. Fixed in:
68729530/ doesn't fit in the client buffer size. The client
falls back to NFS. 8.1.8.119
738744

Unisphere Platforms: All Tree Quotas drop down list on User Quotas The issue was resolved by implementing Exists in version:
Severity: Medium GUI page was missing existing tree quotas. an enhanced algorithm of building tree 8.1.6.101
Tracking: quotas drop down list. Fixed in:
71623624/ 8.1.8.119
739543

VNX Block Platforms: All In a rare instance, a single SP bugcheck Fixed in code. Exists in version:
OE, Virtual Severity: Medium (0xC0000021E) occurred. 05.33.000.5.051
Provisioning Tracking: 653263 Fixed in:
05.33.008.5.119

VNX File OE Platforms: All When executing cpio -m on a Solaris client Fixed in code. Exists in version:
Severity: Medium to migrate files to a NFS share folder, the 8.1.2.51
modified time of the files were not kept as
Tracking: Fixed in:
63811662/ expected.
8.1.8.119
655693

VNX Block OE Platforms: All A storage processor rebooted due to a Fixed in code. Exists in version:
Severity: Medium bugcheck code 0x03006001. 05.33.000.5.051
Tracking: Fixed in:
64252492/ 05.33.008.5.119
663772

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
22
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed problems

Category Details Symptom Fix Version

VNX File OE Platforms: All Customer received an out of memory The issue was resovled by fixing the code Exists in version:
Severity: High issue with bugcheck text that stated, flaw in data cache flush algorithm. 8.1.2.51
couldn't get a free page, due to a
Tracking: Fixed in:
65340286/ bug in the data cache flush algorithm.
8.1.8.119
669498

VNX Platforms: All Backup report shows 0MB is processed The code has been enhanced to show Exists in version:
Severity: Medium after a successful backup. the correct information on the report. Previous versions
Tracking: of code
64121286/ Fixed in:
680458 8.1.8.119

VNX File OE Platforms: All Under certain network configurations ndp x The routing logic has been fixed to Exists in version:
Severity: Medium route commands generate a route that is handle the event. 8.1.3.722
Tracking: missing a next hop. Fixed in:
66737082/ 8.1.8.119
682013

VNX File OE Platforms: All A single SP bugcheck occurred when the Fixed in code. Exists in version:
Severity: Medium VNX2 array was under pressure that 05.33.006.3.235
Tracking: 643402 included external I/Os and internal Fixed in:
background operations, while at the same
time the other SP is rebooting.
VNX Block OE Platforms: All A single storage processor bugcheck Fixed in code. Exists in version:
Severity: Medium (0xE111805F) occurred when 05.33.000.5.052
Tracking: creating/destroying many LUNs and Fixed in:
performing LUN migration at the same time.
68492010/ 05.33.008.5.119
700300

VNX File OE Platforms: All The VNX for File OE bugchecked The code has been updated to protect Exists in version:
Severity: Medium (0x000068df41, 0x0000000008) during against these race conditions. 8.1.3.79
NFSV4 access with a message saying, Page
Tracking: Fixed in:
Fault Interrupt.
68781348/ 8.1.8.119
704740

VNX Block OE Platforms: All An NDU attempt from a previous version of The code has been fixed with updated Exists in version:
Severity: Medium VNX Block OE failed a rule check due to a enclosure firmware and a rules check to 05.33.006.5.096
Tracking: default SAS address being detected. correct situations where default SAS is Fixed in:
69194110/ detected.
05.33.008.5.119
715753 Please see KnowledgeBase article
196087 for more details.
SnapView Platforms: All SnapView sessions were stopped with an The code has been updated to call the Exists in version:
Severity: Medium error message: a100402d. invalidated pages. 04.30.000.5.525
Tracking: Fixed in:
62970312/ 05.33.008.5.119
724669

VNX Block Platforms: All An added system disappeared after Fixed in code. Exists in version:
OE, ESRS Severity: Medium relaunching ESRS. 05.33.006.5.096
Tracking: Fixed in:
71611654/ 05.33.008.5.119
724452

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
23
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed problems

Category Details Symptom Fix Version

VNX Block OE Platforms: All Storage processor B encountered a Code has been updated. Now, a 10 Exists in version:
Severity: High bugcheck code 0x0000001E. second timer starts when a 05.33.000.5.052
Storage processor A encountered a CPD_TPM_TAKE_OFFLINE request is
Tracking: Fixed in:
70890884/ bugcheck code 0x05900000. received from the OSW. The timer
prevents hanging. 05.33.008.5.119
745687

VNX Block OE Platforms: All LUNs with little to no I/O were implicitly The code was updated to that it will not Exists in version:
Severity: Medium trespassed. count non-I/O commands against the 05.33.000.5.038
Tracking: ALUA counter. Fixed in:
61018100/ 05.33.008.5.119
636333

VNX Block OE Platforms: All A single storage processor bugcheck Fixed in code. Exists in version:
Severity: Medium occurred due to the handling of a rare SAS 05.33.000.5.074
Tracking: controller\firmware issue.
67626278/ Fixed in:
699803 05.33.008.5.119

VNX Block Platforms: All A single SP bugcheck occurred The code has added a lock protection to Exists in version:
OE, Snap Severity: Medium (0x000000d1) and host I/O was removed resolve the racing issue of host I/O 05.33.000.5.072
Clones for the clone source LUN. removal.
Tracking: Fixed in:
67742876/ 05.33.008.5.119
691992

VNX OE Platforms: All A race condition between the removal of a Fixed in code. Exists in version:
Block, Host Severity: Medium CAS command and its completion resulted 05.33.000.5.051
Tracking: in an SP bugcheck (0x05900000). Fixed in:
64825240/ 05.33.008.5.119
659963

VNX Block OE Platforms: All When configuring IPv4 on iSCSI or a The code has been updated to fix this Exists in version:
Severity: Medium management port, the IP configuration will issue and now the 4th octet can be 255. 05.33.006.5.102
Tracking: fail if the 4th octet is 255 and subnet mask Fixed in:
72704554/ is less than 24 bits.
05.33.008.5.119
749117

VNX Block OE Platforms: All VNX cannot be used in a Read-Only Domain The kerberos issue has been fixed in the Exists in version:
Severity: Medium Controller environment (RODC) for code. Previous versions
Tracking: W2K8_R2/W2K12 domains. of code
67585474/ Fixed in:
734750 05.33.008.5.119

LDAP, VNX Platforms: All An external Open LDAP server configured to Introduced a retry with binding to the Exists in version:
deny anonymous connection on the LDAP server when an anonymous
Severity: Medium 6.0.40.8
RootDSE showed error messages in the log connection is denied.
Tracking: file. Fixed in:
58961190/ 8.1.8.119
720929

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
24
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Fixed in previous releases

Category Description Tracking Fixed in
version
Unisphere, ESX server lost its path to the storage system. 63964894/651722 05.33.006.5.096
NQM, VNX Block
OE
VNX File OE, A storage pool reached an out of space condition resulting in a 717000 8.1.6.101
system Data Mover panic when a file system whose name contained a
management space tried to use the pool. This file system was not automatically
unmounted after the panic which resulted in recurring panics on
the Data Mover.
VNX File OE, The command /nas/bin/nas_cs -info reported the IPv4 655932 8.1.6.96
system Gateway value incorrectly.
management
VNX File OE, Startup and termination errors appeared when the deduplication 652523 8.1.6.96
system enabler was installed on the system but was not in use.
management
VNX File OE, Limitations for nas_halt . 566413, 566887 8.1.6.96
Replication
VNX File OE A SavVol used for either SnapSure or Replication was 711230/ 69343968 8.1.6.96
automatically extended due to reaching the HWM. However, even
if the SavVol had sufficient free space after the auto-extension, if
the SavVol size was larger than 2TB, the auto-extension kept
repeating automatically until the size reached 16TB or all of the
free space in the pool was used if there was not enough free
space to reach 16TB. There were many informational messages
similar to:
CS_PLATFORM:SVFS:INFO:20:::::Slot2:1424053636: ckpt_3Xday_for30days_054
autoextension succeeded. in the sys_log..

VNX File OE A file system was created directly on top of meta volumes that did 704369 8.1.6.96
not belong to any pools. A command to extend this file system by
specifying another volume failed with the message:
Error 2237: Execution failed: Segmentation fault: Operating system signal.
[FS_EXEC.pre_exec].

VNX File OE The server_mount command did not validate command options. 506271 8.1.6.96
The command attempted to run, even with invalid (misspelled)
options, and did not work.

VNX File OE When adding two volumes with same name, the Data Mover (DM) 54676948/ 613383 8.1.6.96
performed a GP exception bugcheck.

VNX File OE The trunk.LoadBalance parameter accepted invalid values, 57768114/ 613397 8.1.6.96
preventing the load balancing feature from working as expected.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
25
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE A large number of messages similar to the following accumulated 58237744/ 613403 8.1.6.96
in the the system server_log:
NFS3:NfsGssRequest::doStreamProcessing: RPC protocol violation, verf
size <n>
In additon, the Data Mover (DM) performed an out of msgb
bugcheck.

VNX File OE During a file system failover, when a file system with DFS shares 59133330/ 613406 8.1.6.96
was replicated from version 5.6.49 (or earlier) to a later version,
the destination side running the higher version failed to
unmount, leaving it in a frozen state.

VNX File OE When the VNX control station accumulated multiple weeks of 58504016/ 618756 8.1.6.96
historical data, the Jserver ran out of internal memory and re-
started. This prevented accurate file system statistics from
appearing in Unisphere and interrupted the system from
generating appropriate file system alerts.

VNX File OE File storage rescan failed to diskmark LUNs with identifiers equal 61572438/ 625553 8.1.6.96
or greater than 10000, preventing users from using the LUNs as
File-side disk volumes.

VNX File OE When automatic file system extension was enabled for a file 680653 8.1.6.96
system, the Data Mover (DM) on which the file system was
mounted was not eligible for remote DR.

VNX File OE VBB restore did not restore CIFS related attributes if a file was 61065884/ 631900 8.1.6.96
created on NFS share.

VNX File OE Setting the NDMP module log level to LOG_DBG2, caused a File 62110602/ 632115 8.1.6.96
side OE bugcheck with the following alert:
NDMP: 10: Thread rest004 DAR: waiting for finish of previous file, thrdId=4,
write_owner=3, bufpt=0x1c58a9ffb, bufend=0x1c58aa000, bufpt string

VNX File OE When generating user quotas, Unisphere took an extended period 61862190/ 8.1.6.96
of time to populate the user name information. 631383/634746

VNX File OE When using Unisphere to view a VNX system running a 05.33 61727774 /636371 8.1.6.96
version of File OE targeting a VNX system running a 05.32 version
of the File OE, the Search LUN page did not return any results.

VNX File OE CIFS clients were unable to delete symbolic links with targets that 61689146/ 639434 8.1.6.96
pointed to absolute path (that is, paths beginning with /).

VNX File OE Using the File CLI server_stats cifs.user command to 62007318/ 643364 8.1.6.96
monitor a user name with the following format:
DOMAIN\\\\username
caused a File OE "Page Fault Interrupt" bugcheck or caused
memory corruption.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
26
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE When configuring the LDAP Service to use Kerberos 60419804/ 646763 8.1.6.96
authentication, the vbb restore process caused a system
bugcheck.

VNX File OE Log files generated by the server_stats/nas_stats process and the 60520098/ 647406 8.1.6.96
statsd daemon were not properly cleaned up in the directory
/nbsnas/stat_groups. Eventually the number of files grew to
excessive size.

VNX File OE The checkpoint auto extension was occasionally skipped, 59015588/ 651818 8.1.6.96
producing log entries such as:
2013:96104480787::Slot4:1384521607: ckpt_h_f00385_001
autoextension skipped: used 89, HWM 90%.
This led to condition where the save volume was full and the
checkpoint remained inactive.

VNX File OE In reverse replication operations, systems encountered an error 57418482/ 651819 8.1.6.96
that forced them to retry the operation. This produced messages
such as:
“priIp:10.10.16.78, secIp:127.0.0.1 not found";
"CmdReplicatev2ReverseSec::startingRep fsId: 0 not found"; and/or
"VersionSetContext::removeReplicaContext() failed
If the reverse replication operation issue was not resolved in a
timely manner, the Data Mover (DM) performed a "couldn't get a
free page" bugcheck or an out of memory bugcheck.

VNX File OE While performing a diagnostic check, USM displayed incorrect 63613130/ 651218 8.1.6.96
information about pool space."

VNX File OE A Data Mover (DM) bugcheck occurred with the following 652194/ 652194 8.1.6.96
message:
Memcpy size 0x7fff8 is too large
VNX File OE A corrupted server message block (SMB) request contained a 59848028/ 652199 8.1.6.96
corrupted length value that was larger than the available data.
This caused a large memory allocation that failed and resulted in
a Data Mover (DM) bugcheck.

VNX File OE An incorrectly formatted Service Principal Name (SPN) indentifier 60584052/ 652201 8.1.6.96
- lacking either the service component or hostname value -
caused a Data Mover (DM) to bugcheck.

VNX File OE When the system experienced a hardware resume checksum 57606950/ 652210 8.1.6.96
error, a call home message was not generated.

VNX File OE SRM queries caused frequent Control Stations reboots due to out- 65172254/ 679760 8.1.6.96
of-memory condition

VNX File OE The VNX File CLI command nas_fs -info -all failed with a 67458600/ 8.1.6.96
backtrace. 699981/700863
VNX File OE The VNX File CLI command nas_pool -info id=42 failed with 56276112/ 579242 8.1.6.96
the following error: 55669828 / 587686
Error 2237: Execution failed: Segmentation fault: Operating system signal. 657156
[LINKED_LIST.first]

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
27
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE When working with a deduplicated file system, the VNX OE 58909740/ 662444 8.1.6.96
incorrectly reported that the file system was extended to its
maximum size and generated log messages such as the
following:
Couldn't reserve -1 blocks for inode 3976589. Error encountered -
NoSpace
The condition most commonly occurred on file systems where the
autoextension feature was enabled.
VNX File OE When attempting to mount a file system named with an invalid 64938512/ 663866 8.1.6.96
character, everything after the invalid character was ignored. This
sometimes led to unexpected behavior for the file system.
For example, MIXED file systems could be treated as native file
systems because the accesspolicy=MIXED setting was ignored.
VNX File OE After a standby operation in an IPv6 environment, when a VNX 64936446/ 668537 8.1.6.96
Data Mover (DM) took over for as the primary system DM, its IP
address could not be accessed.
VNX File OE In an IPv6 environment on a VNX system with static routes 64936446/ 668538 8.1.6.96
configured, the VNX Data Mover (DM) experienced a "Page Fault
Interrupt" bugcheck.
VNX File OE In a statically routed environment with supernetted subnets, IPv6 64635042/ 668539 8.1.6.96
networking did not work on a VNX Data Mover (DM) because the
IPv6 routing logic did not select the appropriate source IP address
for a given remote destinatlion.

VNX File OE IPv6 static routes to supernetted networks were created using the 64635042/ 674559 8.1.6.96
"server_ip -route -create" command. Under some circumstances
the Data Mover (DM) did not recognize these static routes until it
was rebooted.

VNX File OE IPv6 traffic from a VNX Data Mover (DM) failed in particular 64635042/ 674560 8.1.6.96
configurations.

VNX File OE Unisphere returned an alert that the Block OE software version 66124824 / 676340 8.1.6.96
was not compatible with the File OE software version.

VNX File OE Occasionally during synchronous replication failover operations, 700784 8.1.6.96
the source Data Mover (DM) experienced a bugcheck because the
source LUN became read-only.

VNX Block OE LUNs sometimes failed to come online after a power failure or 579483, 545677 05.33.006.5.096
Virtual Provision after resolving a hardware failure that led to the offline condition.

VNX Block OE, If the kernel decided to move the deduplicated domain from one 649682 05.33.006.5.096
Block Dedup SP to another, the kernel would try to stop this effort. As a result,
the second SP experienced a sharing violation.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
28
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE Initiating a non-disruptive Upgrade (NDU) of the VNX OE bundle 66051036/ 05.33.006.5.096
while also installing a large number of enablers and creating a 673828
Synchronous Mirror led to failures when creating legacy
SnapView sessions.

VNX Block OE Non-disruptive Upgrade (NDU) failed due to the Windows 613202 05.33.006.5.096
command bcdedit failing to run. An error message displayed:
The data area passed to a system call is too small"
should exist in c:\temp\ndu-bcdedit-log.out.

VNX Block OE One SP would not go online after it was restarted. The SP will 645883 05.33.006.5.096
became pingable but the getagent command failed as timeout.

VNX Block OE If a user sent IO to a RAID Group before expanding a LUN, only a 633096 05.33.006.5.096
small number of slices were moved to new raid group.

VNX Block OE Event ID 10 from source WMI was logged in the Application log 657111 05.33.006.5.096
after every reboot6

VNX Block OE If a user modified a property of an 10GB iSCSI port, the modified 648479/ 659444 05.33.006.5.096
portentered a degraded state resulting in suboptimal
performance.

VNX Block OE A user migration session changed to a system migration 656149 05.33.006.5.096
(compression/ deduplication) session unexpectedly, then stuck
in SYNCHRONIZED state.

VNX Block OE Creation of a snapshot or snap session was supported only on 640680 05.33.006.5.096
LUNs less than 256TB.

VNX Block OE Failure mode and effects analysis was improperly handling 546173/ 548762 05.33.006.5.096
internal fault reporting for the battery backup unit.

VNX Block OE Any failure of the read for a RAID Group capacity resulted in an 565361/ 567110 05.33.006.5.096
“insufficient capacity” error message, even if capacity was not
the cause of the error.

VNX Block OE Seagate drive write performance was not optimal. 53114380/ 564310 05.33.006.5.096
584313
VNX Block OE In rare occurences, when a LUN was reset the trespass operation 47877908/ 607594 05.33.006.5.096
did not complete, causing bugcheck 0xE111805F.

VNX Block OE Unable to change the network port for VNX management interface 61370926/ 628608 05.33.006.5.096
to auto.

VNX Block OE The VNX Management Server was not accessible because a 61640548/ 627975 05.33.006.5.096
connection limit was reached.
62520788/ 638971
63182168/ 643064
63607866/ 647050
64209578/ 667181
60322976/ 613498
67604626/690953

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
29
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE If both the VNX A1 and B1 power supplies were missing or 637601 05.33.006.5.096
faulted, the system incorrectly reported fans 1,2,5,and 6 as "Ok"
even though they were faulted and no longer running. If both the
VNX A0 and B0 power supplies were missing or faulted, the
system incorrectly reported fans 3,4,8,and 9 as faulted.

VNX Block OE Unisphere returned a battery "Not Ready" alert during the weekly 58482710 /642288 05.33.006.5.096
battery tests even when the battery was healthy.

VNX Block OE If the Storage Processor (SP) did not have a serviceable power 62898824/ 640321 05.33.006.5.096
supply, the SP would shutdown during local SPS testing.

VNX Block OE If a system battery backup unit (BBU) was not ready, and the 63502640/ 647811 05.33.006.5.096
other system BBU was in test mode, the cache status was
reported as failed.

VNX Block OE If connections to one the VNX Storage Processor’s (SP) link 63823874/ 649179 05.33.006.5.096
control cards (LCCs) became unreliable, the IO was not properly
redirected to the other system SP. This could result in a system
unavailability, with event logs showing the LCC going up and
down.

VNX Block OE The maximum transmission unit (MTU) size for VNX Storage 63910430/ 650471 05.33.006.5.096
Processor (SP) iSCSI ports operated at 14 less than the value set
for them.

VNX Block OE During a period of heavy I/O, storage processor bugchecks 60487186/ 650678 05.33.006.5.096
(various including 0xDAAAEEEE, 0x0000007E) occurred when
hosts cancelled I/O during data movement between LUNs (such
as that initiated by FAST Cache, migration and so on).

VNX Block OE When attempting a non-disruptive upgrade (NDU) for a VNX 63260516/ 651506 05.33.006.5.096
system, connectivity to the system was temporarily interrupted
while the system detected the default expander SAS address.

VNX Block OE Request from Storage Resource Management (SRM) software

05.33.006.5.096
issued using the EMC XML API failed with an HTTP 503 [Service
unavailable] error.

VNX Block OE The Storager Processor (SP) Setport command did not reboot the 654611 05.33.006.5.096
SP when the command completed running.

VNX Block OE When upgrading the VNX OE, if a drive failed (and was building to 64483380/ 656693 05.33.006.5.096
a hotspare) while one system Storage Processor (SP) was
upgraded and the other was not, the hotspare operation failed
and the RAID group became degraded.

VNX Block OE A single Storage Processor (SP) bugcheck (various, including 65771190/ 05.33.006.5.096
0x05900000 and 0x0000001e) occurred in the FAST Cache driver 671378/717629
when it was unable to acquire an internal resource.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
30
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE Attempts to expand a virtual provisioning pool for a direct LUN 64499178/ 657304 05.33.006.5.096
(DLU) failed with error code 712d8e0e because an internal create-
mapping request and it’s I/O write operation required the same
memory.

VNX Block OE An attempt to expand a LUN failed with the 712d8e0e error code. 64472012/ 657569 05.33.006.5.096
VNX Block OE Could not re-configure a VNX system IO module. 64483380/ 661513 05.33.006.5.096
VNX Block OE Service interruption sometimes occurred during a non-disruptive 63260516/ 665700 05.33.006.5.096
upgrade array if a default expander SAS address existed.

VNX Block OE After a non-disruptive upgrade to the VNX Block OE package 66051036/ 673856 05.33.006.5.096
05.33.000.5.072 or 05.33.000.5.074, with enablers installed,
when a MirrorView/S session was created, the SnapView session
failed.

VNX Block OE Rebuild rates were slow, sometimes taking days or weeks weeks 65259884 / 05.33.006.5.096
to complete. 664411/680711

VNX Block OE A RAID group double faulted. 661327 05.33.006.5.096

USM An unexpected error occurred during USM Online Disk Firmware 644788 1.3.6.1.0096
Upgrade (ODFU).

Unisphere, Two hosts with the same name were displayed in the host list in 548376, 566546 Power Path 5.7
Powerpath Unisphere.
SP2
Unisphere, host Unisphere, the Unisphere Service Manager (USM), or the VNX 697449/ 1.3.6.1.0096-1
software Installation Assistant (VIA) did not work correctly because the 697215/699525
Java Runtime Environment (JRE) on the host was not supported.

Unisphere host LDAPS did not work if the LDAPS server's certificate contained a 65187126/ 666544 1.3.6.1.0096-1
software certificate chain.

Unisphere CLI An incorrect error message - I/O module - was reported when a 61304630/ 654455 1.3.6.1.0096-1
mezzanine card was in a faulted state.

Unisphere CLI Error 0x60000500 was reported when restoring an offline Storage 62707090/ 654457 1.3.6.1.0096-1
Pool that used RAID 3 or RAID 6.

Unisphere CLI SNMP MIB read requests reported incorrect information about 63916164/ 655157 1.3.6.1.0096-1
VNX2 arrays.

Unisphere CLI Sending test SNMP traps produced core dumps. 63316528/ 654719 1.3.6.1.0096-1

Unisphere If Unisphere with the Analyzer was enabled and USM was running 560704, 649788 05.33.006.5.096
on the same host, Analyzer Real-Time statistics sometimes failed
to update.

Unisphere Could not create a FS on Windows 2012 with Chrome. 642579 1.3.6.1.0096

Unisphere CLI command response time was slow in some conditions. 60933588/ 619647 1.3.6.1.0096

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
31
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
Unisphere When running the getlun Block CLI command to retrieve disk 58886038/ 624200 1.3.6.1.0096
statistics, the returned Prct Idle and Prct Busy values were
inaccurate.

Unisphere In some circumstances, the Unisphere Search LUN page returned 61727774/ 628463 1.3.6.1.0096
no results for searches, even when the Search criteria matched
existing LUNs.

Unisphere The Tree Quota usage did not display properly in Unisphere, when 61551390/ 631797 1.3.6.1.0096
the soft and hard limit were set to zero.

Unisphere Unisphere did not allow users to create hidden CIFS shares. 61918032/ 631865 1.3.6.1.0096

Unisphere, USM Unisphere and USM did not operate correctly in Chrome. 635310 1.3.6.1.0096

USM Unified Service Manager (USM) showed incorrect information 63613130/ 651218 1.3.6.1.0096
about available pool space while performing a diagnostic check.

Unisphere During the user login/authentication process, user accounts were 58357456/ 652208 1.3.6.1.0096
locked out after three incorrect attempts.

Unisphere Using Unisphere to create Mirrorview secondary LUN images 59188084/ 654433 1.3.6.1.0096-1
failed for LUNs with mixed RAID types if no disks were available.

Unisphere When a CIFS share was created with the VNX File CLI and then 498866/ 654499 1.3.6.1.0096
modified with Unisphere, some configuration options were not
avaialble.

Unisphere In Unisphere, the "Copy to Hotspare" option was grayed out for 62067244/59395272/ 1.3.6.1.0096
disks associated with mixed RAID type storage groups. 606329/654723

Unisphere The Unisphere Analyzer application stopped without apparent 64649720/ 660841 1.3.6.1.0096
reason.

Serviceability When installing the ESRS IP Client on a Windows Server 2012 or 64018344/ 656572 8.1.6.96
ESRS above system (which are not supported), the ESRS environment
check incorrectly reported the OS as Windows 2008 (which is
supported).

VNX File OE, SECURITY: Oracle JRE/JDK Multiple Vulnerabilities (CPU-FEB-2013) 541017, 543319 8.1.1.33
System mgt - UNIX/Linux – JRE.

VNX File OE, FC port did not function after P2P to tape (DDR) attempted. 587501, 591030 8.1.2.51
System mgt
VNX File OE, Data Mover completely hung and was unresponsive. FileMover 56871206 8.1.1.33
System Mgt (DHSM) users using the partial recall policy could experience a /580075
hang if they were reading a file that was larger than 4GB.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
32
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE, Temporary Checkpoints flooded the Control Station. Users were 570984 8.1.1.33
System Mgt unable to create their own checkpoints or file systems.

VNX File OE, FS was taken offline because of reAcquire failure. cbfs:CBFSA: 627477, 620510, 8.1.3.72
System Mgt UFS: 3: Unmounting fs 5: Reason: VBM 651332
processToBeModified reAcquire failure

VNX File OE, LUN was taken offline and during LUN recovery, FSCK would not 619255, 596690, 8.1.3.72
System Mgt report corresponding corruption at CBFS SliceMap metadata. 608904, 610756,
618451, 618971,
637794, 639663,
644557, 646120
VNX File OE, SP paniced due to IOD watchdog timeout. 601275, 615600 8.1.3.72
System Mgt
VNX File OE, The VNX System Management Daemon crashes with an 601412 8.1.2.51
System OutOfMemoryException message recorded in the
Management /nas/log/nas_log.al.mgmtd.crash file.
VNX File OE, DART panicked while downloading a large file (more than a few 55032486 8.1.1.33
Security GB) using SCP (secure copy over ssh). /578783
VNX File OE, RecoverPoint Failover Consistency Group failed in both directions 563551, 571761 8.1.1.33
RecoverPoint FS
VNX File OE, NFS Under certain circumstances, our internal FS layer returns invalid 641492 8.1.3.72
uninitialized status on NFS write. This results in a memory
corruption.
VNX File OE, NFS In NFS 4.1, the system may hang when it reconnects. 629752 8.1.3.72
VNX File OE, NFS When using the parameter nfs.manageGids. The system could 63288760/646572 8.1.3.72
panic if the client accessed an NFS export with user as root.
VNX File OE, NFS When the user mapping service was not started or not configured 59549160/621157 8.1.3.72
on a Linux client, the client had access issues through NFSV4.
VNX File OE, NFS Inability to access the Data Mover via NFS V4 from a client using 58917286/621161 8.1.3.72
UDP for NFSV4.
VNX File OE, NFS A System Watchdog panic occurred with the error: 61114502/622178 8.1.3.72
file: ../sched.cxx at line: 1909 : SYSTEM WATCHDOG

VNX File OE, NFS When there was invalid syntax in the host list (access, ro, rw or 638559
root), the export was accepted without errors. When the export
options were processed, the host list was analyzed and the error 8.1.3.72
is only printed in the log. It is not clear to the user that his host
list is wrong.
VNX File OE, NFS The Data Mover hung when a file-system was mounted with the 54489848/641100
option ntcredential and when replication was used.
8.1.3.72
VNX File OE, Windows Quotas View of a CIFs Share were not displayed from 52223586 8.1.1.33
CIFS one VNX when the drive was mapped. The user quota information /554095
was missing (using Window MMC Quota management) when
several CIFS users were mapped to the same Unix Id.
VNX File OE, User sees a panic when using FS that was mounted with the 639006
CIFS ceppnfs option.
8.1.3.72
VNX File OE, User encounters a 'bad bn' error code when performing an offload 632014
CIFS copy operation.
8.1.3.72

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
33
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE, YP requests hung indefinitively when the domain was removed. 61583520/638168
CIFS
8.1.3.72
VNX File OE, Could not access CIFS server with NULL session. 618728
CIFS
8.1.3.72
VNX File OE, Server lost connectivity to Domain Controllers on the reboot after 60226850/617052 8.1.3.72
CIFS adding a specific Service Principal Name to a server using the
server_cifs server_N -setspn -add command.

VNX File OE, CIFS clients failed to access a file due to a lock conflict. File 59688542/619315 8.1.3.72
CIFS system unmounts or a freeze operation hangs.

VNX File OE, When enumerating open sessions or open files on a CIFS server 6037558/620402 8.1.3.72
CIFS which belonged to a Data Mover with many servers, the reports
may have included information that belonged to other CIFS
servers.

VNX File OE Applying the latest security related hot fix to any current VNX2 675307 8.1.3.79
release (8.1.0, 8.1.1, 8.1.2 and 8.1.3) will cause upgrades using
USM (Unisphere Service Manager) to a later release to fail.
Upgrades using CLI would remove the hot fix, which will have to
be re-applied after completing the upgrade.
VNX File OE When the pool name has a space, the fs_extend_handler puts 610831 8.1.3.72
error messages in apl_tm.log.
VNX File OE Oracle Siebel clusters crashes the application when trying to 60238902/634648 8.1.3.72
access NFS export.
VNX File OE FS offline with corruption detected and recovery (FSCK) reports 621305, 614391 8.1.3.72
corruption on the File System SuperBlock.
FS marks a SuperBlock related transaction complete, even the
modification on the SuperBlock has not been persistent. If a
panic happens before the system has a chance to write the
SuperBlock again (periodical 30 seconds), it results in a lost-write
conditions on the SuperBLock, thus the corruption.
VNX File OE Unable to configure LDAPS if LDAP server certificate 'Subject 572543 8.1.3.72
Name' property didn't have LDAP server URL and in the certificate
'Subject Alternative Name' property it had the LDAP server URL.
VNX File OE ProcessMFCExtent error handling 583674 8.1.3.72
VNX File OE When all the initiators are visible in a storage group except one 584290 8.1.3.72
initiator (which is in the ~management storage group), the
Connect button on the Initiators tab on the Host List page showed
the error "Found no user created Storage groups to
reconnect on subsystem xxx" and did not put the initiator in
the requested storage group.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
34
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE All dedup-enabled LUNs on pool 0 went offline. 603082, 602262, 8.1.3.72
611854, 621903,
626956, 644194
VNX File OE The following error was displayed: 632514 8.1.3.72
DEDUP OFFLINE: Pool Gold, all luns are offline and
need recovery

VNX File OE Subfolder contents were not being restored when the Restore 47151218/613372 8.1.3.72
option on the previous version tab in WindowsExplorer was used
with C$ path.
VNX File OE A SYSTEM WATCHDOG panic, or a GP exception panic or a 61243802/623117 8.1.3.72
isAValidIndBlkBuf: bad bn panic, or a Corrupted indirect block
panic, or a mangled directory entry panic, or a Page Fault Interrupt
panic, and/or a number of other symptoms occurred.
VNX File OE LDAP Service Connection configuration failed on attempt to add 52658438/613483 8.1.3.72
server certificate in PKCS7 format
VNX File OE An install issue occurred when using non-default account for the 54342902/613486 8.1.3.72
nasadmin role
VNX File OE GUI showed a faulted DM but nas_server -l did not. 60433682/ 618249 8.1.3.72
VNX File OE A loss of CIFS access occurred and the Data Mover did not 642440 8.1.3.72
respond to any commands.
VNX File OE User could not initiate ROBV on the RAID Group with a number 62946704/ 8.1.3.72
larger than 256. 649286
VNX File OE When performing an EI recover, an incorrect message that the 53678158/ 8.1.3.72
Data Mover needed to be rebooted was received. 613386
VNX File OE When CS0 failed-over to CS1, and the Pre-Upgrade Health Check 57195216/ 8.1.3.72
(PU HC) had been run on CS1, The PUHC reports a failure due to 613396
not being able to find some commands under /nas_standby.
VNX File OE Reading a DHSM offline file could cause a Data Mover panic if 61225828/ 8.1.3.72
there were connection issues between the primary storage and 629252
secondary storage or another failure of reading remote data.
VNX File OE When using Filemover (DHSM), files with a modification time 53114380 8.1.1.33
earlier than 1970/01/01 could not be recalled. /563271
VNX File OE After changing the admin password for a CIFS client 568365 8.1.2.51
connection, the original credential is be retained in the
Kerboros cache for the file system. This can cause a password
mismatches and make the CIFS client unable to access CIFS
data.
VNX File OE Windows XP (and earlier) clients cannot navigate directories 591553 8.1.2.51
created with newer clients (for example, Windows 8 or
Windows 2012 server OS) that support the SMB3 protocol.
VNX File OE • The Windows Event Viewer cannot open a VNX security audit 591565 8.1.2.51
log file that was previouslyopened in UNIX (NFS).
VNX File OE Unable to access CIFS shares from Windows 7/Windows 2008, 592737 8.1.2.51
although Windows XP/2003 clients can access the shares
without problem. Unable to unmount check point file systems
that were mounted in a VNX virtual data mover (VDM)
environment. The unmount process is interrupted when a CIFS
client accesses the check point though the .ckpt directory.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
35
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE In Windows, previous versions of deleted files cannot be 593570 8.1.2.51
retrieved with the Restore Previous Version option if the widelinks
feature is enabled for a CIFS server. Deleted files can only be
retrieved through the .ckpt directory.
VNX File OE When the VNX default server names (for example, server_2 ) are 598131 8.1.2.51
renamed (for example, to server_hr), the migrate_system_conf
command generates the following error:
Error! Invalid source <movername> is provided
VNX File OE The VNX File OE reboot occurs after a failover with a message 603272 8.1.2.51
similar to the following:
GP exception. Virt ADDRESS: <addr>. Err code: 0
VNX File OE When the Windows audit auto-archive feature is enabled for a 607285 8.1.2.51
VNX virtual data mover (VDM) but disabled on a VNX data mover
(DM), auto-archive does not work correctly after:
• Restarting the DM
Unloading/loading the VDM
VNX File OE A VNX Data Mover (DM) exeriences a "couldn't get a free 602155 8.1.2.51
page" bug check.
VNX File OE The Data Mover experienced a "GP exception" bug check. 595437 8.1.2.51
VNX File OE When permanently unmounting a split-log filesystem and all its 52621636/ 8.1.2.51
checkpoints, a VNX Data Mover (DM) failover fails with the 597422
following error:
replace_ufslog: failed to complete command
VNX File OE When one or more Data Movers (DMs) are powered off or pulled 600826 8.1.2.51
out from the system, the nas_rdf -restore function finishes
without returning an error code.
VNX File OE Windows 8 or 8.1 and W2012/R2 servers are occasionally not 602082 8.1.2.51
allowed to access a CIFS share on a VNX Data Mover (DM) when
browsing the server UNC path \\<server or IP>.
A pop-up window appears with a \\server\share is not accessible
message.
VNX File OE The Data Mover experienced a rolling panic when the nas_fs - 602139 8.1.2.51
translate command was run on the Control Station to convert the
access policy of a file system from UNIX or SECURE to MIXED.
When running the nas_fs -translate control station command
to convert a file system access policy from UNIX or SECURE to
MIXED, the VNX File OE goes into a rolling panic.
A workaround invlved removing the following option from the
boot.cfg file:
accesspolicy=MIXED

VNX File OE Avamar backup fails, and server log is filled with alert messages. 602168 8.1.2.51
VNX File OE NFS mounts did not complete successfully. NFS mount threads 604117 8.1.2.51
were hung. If all of the NFS mount threads were hung the Data
Mover could panic.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
36
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX File OE When a VNX Data Mover (DM) is associated with a large number 605740 8.1.2.51
of file systems, and the fiile systems contain a large number of
directories that remain open or are frequently opened, this can
exhaust VNX system memory and cause the a Data Mover (DM)
bug check.
VNX File OE When a SavVol is unavailable at boot time, any relevant 607082 8.1.2.51
Production File Systems (PFS) are mounted, invalidating any
associated checkpoints.
VNX File OE On a Data Mover (DM) with several concurrent backup sessions 605163 8.1.2.51
running for long time, it is possible for the DM to reboot.
VNX Block OE, After attempting to destroy a storage pool, the destroy operation 578172 05.33.000.5.034
Virtual would fail. The storagepool –list command displayed:
Provisioning Current Operation: Destroying
Current Operation State: Failed
Current Operation Status: Subroutine failure
(0x4000803c)

VNX Block OE, A LUN shrink on a deduplication-enabled LUN failed to complete 578421 05.33.000.5.034
Virtual only when all the LUNs in the deduplication domain were empty
Provisioning (had no data). In this case lun -list showed the "Current
Operation" as Shrink indefinitely. In this state, the LUN could not
be shrunk, expanded, or snapped; it could only be destroyed. I/O
to the LUN was unaffected.
VNX Block OE, A single SP panic occurred with BugCheck code 7E. 578490 05.33.000.5.034
Virtual
Provisioning
VNX Block OE, LUNs failed to come online following an SP reboot. 579050 05.33.000.5.034
Virtual
Provisioning
VNX Block OE, A create LUN operation could result in an internal error if the 573637 05.33.000.5.034
Virtual operation happened when the peer SP was rebooting and the
Provisioning peer SP was also the preferred path to service IO for the LUN.
VNX Block OE, LUN expand failed with “Unrecognized Thin Provisioning Driver 575603 05.33.000.5.034
Virtual error code: 36365”. This could happen if an SP panicked when
Provisioning hitting a particular boundary condition during LUN shrink; the
symptom was observed during a subsequent LUN expand.
VNX Block OE, A pool and all its LUNs went offline following an SP reboot. 576389 05.33.000.5.034
Virtual
Provisioning
VNX Block OE, Host IOs failed to a Pool LUN which was reporting ready after the 576467 05.33.000.5.034
Virtual system recovered from a dual SP reboot/panic.
Provisioning
VNX Block OE, Snap creation failed and the snapshot was left in an errored state 571738, 574415 05.33.000.5.034
Virtual when the source LUN was in the middle of a trespass.
Provision, VNX
snapshots
VNX Block OE, After a LUN encountered an internal error during a trespass, it 534327, 539374 05.33.000.5.072
Virtual Provision could not be brought back online.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
37
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE, Single SP panic occurred because a CDCA (cache dirty/can’t 557018, 632291 05.33.000.5.072
Virtual Provision assign) condition after dual SP reboots.

VNX Block OE, A LUN destroy command completed succesfully, but the LUN still 567511, 585191 05.33.000.5.034
Virtual Provision remained in the system.

VNX Block OE, A single SP reboot can occur when multiple rollback processes 583999 05.33.000.5.051
SnapView are in simulatneously active.

VNX Block OE, Snap creation failed with the error message: “The operation 577314 05.33.000.5.034
Snapshots cannot be performed because the LUN is ‘Preparing’. Wait for the
LUN’s Current Operation to complete ‘Preparing’ and retry the
operation.”
VNX Block OE, LDAP host queries do not report IPv6 addresses. 602169
Security
05.33.000.5.072
VNX Block OE, An incremental SAN Copy session or aMirrorView/A session 560498, 561780 05.33.000.5.072
SANCopy for sometimes failed to be removed.
Block
VNX Block OE, A single SP panic can occur when multiple rollback processes are 583999 05.33.000.5.051
Platforms in simulatneously active.

VNX Block OE, A flase message is presented to the user saying that the 59070064/602429 05.33.000.5.072
Platform management switch type has changed, when no change has been
made.
VNX Block OE, IPv6 would not work on SPA. 59876582/610818 05.33.000.5.072
Platform
VNX Block OE, IPv6 configuration failed when the network prefix started with 59876582/614231, 05.33.000.5.072
Platform fc00:: 633470

VNX Block OE, Data was unavailable when one of the SPs was rebooting. Error 61296778/622987 05.33.000.5.072
Platform Code 0x25 is displayed.
VNX Block OE, When more than 64 FC front-end ports were configured on an 63411674/645909 05.33.000.5.072
Platform array, not all of the ports were visible to the hosts and/or switch.
Several were assigned duplicate WWNs.
VNX Block OE, SP queue statistics are disabled and displayed as zero in the GUI 565385, 588543 05.33.000.5.072
Platform and CLI.
VNX Block OE, In a system configured for large deduplication, a mismatched 605245 05.33.000.5.038
Dedup deduplication counter size/cast (64-bit/32-bit) can cause data
loss.
VNX Block OE, When attempting to delete a deduplication LUN while there were 574723 05.33.000.5.034
Dedup some active copy requests in-progress, the deduplication LUN
could get stuck in destroying state.
CBFS I/O to the affected LUN will hang if the error path is hit. The 646502 05.33.000.5.072
system may bigcheck due to IO timeout.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
38
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE, SCSI GET_LBA_STATUS commands maps to VMFR commands 628196 05.33.000.5.072
CBFS from MLU to CBFS. When there are many of these commands sent
to the system, the CPU is busy and leads to a panic.
This happens when running:
- Win2K12, TRIM enabled
- RecoverPoint, Thin Extender enabled
VNX Block OE, Watchdog Panic due to two COREs holding spinlock for a long 619482 05.33.000.5.072
CBFS time.

VNX Block OE, Some mapping cannot proceed and the following error is 626128 05.33.000.5.072
CBFS returned:
CBFSA: UFS: 4: IndUsableList::Load failed to get free
entry. System may be <NL>
CBFSA: stressed! CurrentNumAllocatedEntries (368260)
MaxEntries (368255)

VNX Block OE, When shrink was performed while deduplication was running and 577233 05.33.000.5.034
Dedup in the process of collecting data to be deduplicated, the
deduplication job stuck in a loop and it did not make any
progress.
VNX Block OE Some disks remained in the Transitioning state for more than 1 577106 05.33.000.5.034
VNX day after being reenabled.
Block OE
VNX Block OE mgmtd used almost 100% CPU on Disaster Recovery-side Control 645614 / SR63207028 05.33.000.5.038
Station.
VNX Block OE Unisphere allowed users to set the speed on the port of an 1Gb 649466 05.33.000.5.072
iSCSI/TOE IO Module to either 10Mb, 100Mb, or 1Gb.
VNX Block OE A subset of LUNs in a storage pool remain offline following 542529, 545677 05.33.000.5.072
double-faulted disk removal.
VNX Block OE When a VNX5200 or VNX5400 system was installed with the 618635 05.33.000.5.072
maximum number of I/O modules, but at least one I/O module is
uninitialized, occasionally an alert message occured indicating
that an uninitialized I/O module had exceeded the system limit.
VNX Block OE An SP bug check occurred during software upgrade or installation 556166, 562545 05.33.000.5.072
operations.
VNX Block OE The serial attached SCSI (SAS) status LED for Port 2 on Base 566542 05.33.000.5.051
Module was not ON.
VNX Block OE Running the naviseccli ndu –list command in engineering 567026 05.33.000.5.072
mode sometimes showed a default version
VNX Block OE Incorrect current output for the DC power supply was reported. 591576, 593267 05.33.000.5.072
VNX Block OE Unexpected results occurred when a storage processor rebooted 67209396/688738 05.33.000.5.081
during data in place encryption. 67136530/686425
67173272/686779
VNX Block OE A storage processor became unresponsive when updating SAS 66040194/674144 05.33.000.5.079
controller firmware during an NDU from an OE version earlier than
05.33.000.5.072 to an OE version 05.33.000.5.072 (or later).

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
39
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE A storage processor bugcheck (0x01901004) occurred when the 65185426/663684 05.33.000.5.079
fibre channel speed setting was manually changed via Unisphere 65365958/665952
GUI or CLI.
VNX Block OE Coherency errors were reported during an NDU to 65298752/ 664729 05.33.000.5.079
05.33.000.5.074 from an earlier version of code (prior to
05.33.000.5.072).
VNX Block OE Repeated storage processor bugcheck (including 0x0000001e) 65270166/672994 05.33.000.5.079
occurred following an NDU failure.
VNX Block OE Coherency errors were reported during an NDU when one SP was 684145 05.33.000.5.079
running 05.33.000.5.074 and the other SP was running an earlier
version of code (prior to 05.33.000.5.072).
VNX Block OE A single storage processor bugcheck (various, including 65789046/671288 05.33.000.5.072
0x05900000 and 0x0000007e) occurred. 66357332/677368
VNX Block OE After upgrading to VNX for Block OE version 05.33.000.5.072, 664045 05.33.000.5.072
coherency errors are reported in the system logs.
VNX Block OE Hardware modules are being indicted in logs/traces by ESP due 637319 05.33.000.5.072
to underlying issues in our environment path.
VNX Block OE User gets data corrupted error, but in disk array those sectors 627961/635306 05.33.000.5.072
have been recovered.
VNX Block OE A LUN 's Address Offset value is incorrect. 621573 05.33.000.5.072
VNX Block OE The Raid Group enters a cycle of full rebuild, followed by a short 621540 05.33.000.5.072
period where the copy starts and the drive position goes offline.
VNX Block OE Under heavy I/O load utilizing FAST Cache, an internal timer may 622564 05.33.000.5.072
trigger a single processor bug check.
VNX Block OE Thin Lun 131 of Pool 1 went offline with error code 0xE12D8D0D. 62859966/639466 05.33.000.5.072
VNX Block OE Drives were faulted if their firmware did not support Enhanced 580959 05.33.000.5.072
Queuing. The drives were marked as Faulted with a reason
indicating enhanced queuing check.
VNX Block OE During powerup of an enclosure or during a power glitch, one or 613776, 629616 05.33.000.5.072
more drives did not progress to the “ready” state.
VNX Block OE During an LCC, SLIC, or Base Module replacement, multiple drives 622581, 626540 05.33.000.5.072
within a RAID group went offline, causing rebuild logging to
initate.
VNX Block OE SPA and SPB encountered error code 0x05900000 in the Data 62778786/639100 05.33.000.5.072
Mover Library (DML).
VNX Block OE The user experiences intermittent 1 second latency spikes. 60964096/648029 05.33.000.5.072
VNX Block OE User saw two of the same enclosures, when they only had one. 60659572/616891 05.33.000.5.072
VNX Block OE Scheduled Battery Backup Unit (BBU) checks showed a BBU was 612219 05.33.000.5.072
faulted, even though the component was operational.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
40
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE The amber LED was illuminated when a cable was connected to 612801 05.33.000.5.072
iSCSI ports.
VNX Block OE Unisphere and FBECLI Peer Info reported IO module limits 618635 05.33.000.5.072
incorrectly.
VNX Block OE Under heavy front-end FCoE I/O, a single storage 593740 05.33.000.5.072
processor bug check (0x01901008) occurred.
VNX Block OE A panic occurred with error code 0x0340201a. 62294340/637286 05.33.000.5.072
VNX Block OE SP bug-checked during shut down if there were many TLU/DLUs in 627774, 616729, 05.33.000.5.072
failover mode. 627776
VNX Block OE Requests for overlapping cache pages between the Fast Cache 05.33.000.5.072
Idle Cleaner and the host request resulted in a deadlock that
timed out after 10 seconds.
VNX Block OE A VNX single Storage Processor (SP) reboots when a host 594685 05.33.000.5.051
performs a 1MB write operation to the system that is attached to
a Recoverpoint Appliance (RPA) system for replication
VNX Block OE MirrorView Asynchronous connections are fractured on a VNX 595166 05.33.000.5.051
system. The following symptoms can occur:
Deduplication LUNS are temporarily unable to
provide I/O and multiple snapshots remain in a
destroying state in the deduplication domain.
Single storage processor (SP) reboot after LUN expansion
VNX Block OE When a drive is removed, no event is logged to indicate the 593320 05.33.000.5.051
reason for the drive fault.
The Taken offline event (ID 7167802f) is dropped from both the
Windows event log and the VNX event log because the string
length exceeded the maximum character limit.
VNX Block OE After a driver reset, an unexpected SP reboot occurs producing an 593659 05.33.000.5.051
alert/log message such as the following: CPD PANIC -FCOEDMQL 1
(FE5)
VNX Block OE An inaccurate VNX call-home message is generated which 595715 05.33.000.5.051
indicates that a backup battery unit (BBU) is missing when it is
actually present. This can potentially cause BBU status
indications to show the component status as degraded
VNX Block OE Storage processor bugchecks (0x00000041) occurred due to 596197 05.33.000.5.051
excessive traffic on the management ports.
VNX Block OE The VNX generates warning messages (BMS found XXX entries) 597131 05.33.000.5.051
because the number of Background Media Scan (BMS) log entries
recorded for vault drives quickly reaches defined thresholds.
VNX Block OE Coherency errors for RAID-1 and RAID-6 occasionally do not 599355 05.33.000.5.051
generate the proper XOR sector trace messages in debug
operations (performed by EMC Support).
VNX Block OE A dial home event is generated even though no fault has 599721 05.33.000.5.051
occurred.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
41
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
VNX Block OE SPA and SPB panic within minutes of each other, and their 607962 05.33.000.5.038
associated LUNs and DMs go offline.
This problem occurs every 90-99 days in the following systems:
VNX5200, VNX5400, VNX5600, VNX5800, VNX7600
This problem occurs in a VNX8000 system every 80 days.
VNX Block OE When the weekly BBU test time arrives, SPA and SPB can start 601545 05.33.000.5.038
their BBU test at the same time. Later when the BBU test
completes, the test is not set as completed and the BBU test will
start again repeatedly.
VNX Block OE After a reboot pool luns can go offline. The mount may fail due to 606436 05.33.000.5.038
an unexpected slice object state initialized from slice cache. 608736
VNX Block OE When copper twinaxial cables that supported iSCSI connections 58805510 05.33.000.5.035
were in use, iSCSI hosts experienced data unavailable (DU) after /599567
a non-disruptive upgrade (NDU) to VNX OE for Block version
05.33.000.5.034.
VNX Block OE Could not upgrade the drive firmware for Micron Buckhorn SAS 573654 05.33.000.5.034
drives which had a drive firmware size of over 2 MB.
VNX Block OE Panic occurred while shutting system down. 574220 05.33.000.5.034
VNX Block OE SP B reported a panic and created a Dump file on SP B. 574235 05.33.000.5.034
VNX Block OE The SP Fault LED blink rates were half the expected rate during 577670 05.33.000.5.034
normal and degraded boot scenarios.
VNX Block OE Physical power switches on the SPs were automatically turned 578752 05.33.000.5.034
OFF during a power down. Array did not power up after power
glitch (or short term power loss).
VNX Block OE Battery Backup Unit (BBU) A: Not Ready || Battery Backup Unit B: 593666 05.33.000.5.034
Not Ready was reported in Unisphere.
VNX Block OE The BBU self test was in a cycle where the tests repeated 584042 05.33.000.5.034
continuously.
VNX Block OE An on-array debug utility/process was inadvertently left enabled 504517 05.33.000.5.034
in the shipping version of the VNX OE for Block code.
VNX Blcok OE, False-positive logs and user traces indicated MVA thread 545496 05.33.000.5.072
MirrorView/A, starvation.
MirrorView/S for
Block
USM, An unexpected error was received while running the Install DAE 574069 1.3.1.1.0033
Serviceability wizard. The error was seen during the Connect to SPB/SPA
Bus/Loop step. USM stopped the wizard with a message saying a
fault had been detected on the storage system.
USM, Install Software wizard keept reporting Control Station reboot 575966 1.3.1.1.0033
Serviceability timeout, and waiting for the suggested 3 minutes did not solve
the problem.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
42
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
USM, The VNX for Block OE packages were not automatically committed 577921 1.3.1.1.0033
Serviceability after running the USM software wizards to perform an upgrade.

USM When running the Disk Replacement wizard in USM, the state of a 576837, 577469 1.3.1.1.0033
replaced disk remains unchanged.
USM USM was unable to view certain information in the report page. 61047728/621079 1.3.3.1.0072-1
USM A Data Mover error occurred during Installation. 51004590/613374 1.3.3.1.0072-1
USM Customers are unable to complete an NDU via USM because of 643460 1.3.3.1.0072-1
a timeout.
Unisphere, Pool statistics are not updated after destroying LUNs. 612574 1.3.3.1.0072-1
Virtual
Provisioning,
Unisphere Host
Software, CLI,
and Utilities
Unisphere, When power source was restored from the failure state, LUNs may 539374, 646381 1.3.3.1.0072-1
Virtual have stayed offline after backend retruned to the normal state.
Provisioning
Unisphere, Unexpected SP reboot. 619259 1.3.3.1.0072-1
Virtual
Provisioning
Unisphere, When uninstalling the ESRS IP Client, the ESRS IP Client would 577404 1.3.1.1.0033
Serviceability, sometimes report that ConnectEMC, one of the ESRS IP Client
ESRS IP Client components, could not be uninstalled.

Unisphere, The USM registration wizard sometimes fails with the error: 595816 1.3.1.1.0051
Serviceability The version of management software installed on the storage system does
not suport the storage system registration ….
Unisphere, USM application stops when at the VNX OE for File Installation 594553 1.3.1.1.0051
Serviceability Status stage of the Install Software wizard. It displays the
following message:
Retrieving data. Please wait ...
Unisphere, FAST In Fast Cache configurations, when a drive is removed from the 592310 1.3.2.1.0051
Cache, FAST VP enclosure and then reinserted after a hot spare has been
activated, both the new hot spare and the removed disk appear
when you run the cache -fast -ino CLI command or when you view
system information though Unisphere
Unisphere, ESRS Unishphere Host Agent, ConnectEMC, and VNX for Block CLI are 623176 1.3.3.1.0072-1
IP Client always installed on the system’s drive, even if the installation
path is changed to another drive.
Unisphere, ESRS Unable to install ESRS IP Client version 1.3 when selecting proxy 600457 1.3.2.1.0051
IP Client server connection option.

Unisphere Information in the Unisphere Service Manager (USM) Available 603183 1.3.1.1.0051
Service Manager Storage tab does not show all bus/loop information associated
with the VNX configuration.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
43
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
Unisphere Host CQECC00606857-CIMOM_PerfCounter_Exceeded.dmp.zip 576807, 59729 1.3.3.1.0072-1
software, CLI, generated on DAE testing secondary array.
and Utilities
Unisphere Host If the host timezone was 'UTC + x', the commmand 'naviseccli 616366, 631684 1.3.3.1.0072-1
Software, CLI, analyzer -status' failed with an error.
and Utilities
Unisphere Host Unable to configure LDAPS on Off Array Management server. 58009364/593000, 1.3.3.1.0072-1
Software, CLI, 591485
and Utilities
Unisphere Host To fix outputting 'Get Drives for a Tier' audit log message 58005674/ 1.3.3.1.0072-1
Software, CLI, 613959
and Utilities
Unisphere Host The Storage Processor (SP) was unmanaged when the SR numbers: 1.3.3.1.0072-1
Software, CLI, Management Server restarted due to improper memory 51019358, 53107146,
and Utilities manipulation. 56043768, 56047852,
56774788, 58603098,
59247626, 59892166,
60874054, 60951330,
61083608
AR numbers:
528255,543184,
577835,78959,
586192,93053,
593077,96368,
603192,05252,
610054,616203,
618190,619026,
622270, 622015
Unisphere Host Using VASA with Unisphere sometimes resulted in a memory 59002892/ 1.3.3.1.0072-1
Software, CLI, leaks due to the misuse of an internal string, where the 616454
and Utilities management process eventually produced a dump file and
restarted.

Unisphere Host Improper internal library management resulted in a restart of the 1.3.3.1.0072-1
Software, CLI, management process when the SP will be temporarily 58312648/ 622224
and Utilities unmanaged.

Unisphere Host Navisphere CLI (naviseccli) segfaults and dumps. 60874280/623692 1.3.3.1.0072-1
Software, CLI,
and Utilities
Unisphere Host Pool creation failed on Unisphere with Japanese language pack. 59815336/ 616387 1.3.3.1.0072-1
Software, CLI,
and Utilities

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
44
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
Unisphere Host Storage Pool creation failed when a removed drive was selected. 618360 1.3.3.1.0072-1
Software, CLI,
and Utilities
Unisphere Host Fail Safe Network feature for bxgv2 devices could not be tested 647510 1.3.3.1.0072-1
Software, CLI, by bringing down the ports using software commands.
and Utilities
Unisphere Host A blue screen error occurs on Windows server 2012 64-bit 632609 1.3.3.1.0072-1
Software, CLI, environment with MPIO enabled when running Unisphere Host
and Utilities Agent.
Unisphere Host When power source was restored from the failure state, LUNs may 539374, 646381 1.3.3.1.0072-1
Software, CLI, have stayed offline after backend retruned to the normal state.
and Utilities
Unisphere Host The Virtual Provisioning feature is in a degraded state. 616361 1.3.3.1.0072-1
Software, CLI,
and Utilities
Unisphere Host Unexpected SP reboot. 619259 1.3.3.1.0072-1
Software, CLI,
and Utilities
Unisphere When opening a Unisphere Analyzer (NAR) file obtained from a 593280 1.3.1.1.0051
Analyzer VNX system with no defined pools or LUNs the following error
message is generated:
An unknown error has occurred.
Unisphere When VNX LUNs are connected to multiple hosts, searching 579127 1.3.1.1.0051
Analyzer Unisphere Analyzer (NAR) files based on a Host criteria does not
show all connections.
Unisphere Unable to create a network device using the Unisphere wizards or 612485, 614365 1.3.3.1.0072-1
the Unisphere management screens.
Unisphere Unisphere and the CLI did not accurately display the 60-drive Disk 563290, 564080 1.3.3.1.0072-1
Array Enclosure (DAE) information after replacing a 25-drive DAE
with a 60-drive DAE.
Unisphere After completing installation with the VNX Installation Assistant 566078 1.3.2.1.0051
(VIA), the system sometimes remained in an unfused state.
Unisphere The user received a security message when closing Unisphere if 568652, 570148 1.3.1.1.0033
using JRE 7u21 or later.
Unisphere Creatingf FAST Cache could fail if created at the same time as the 561400, 597279 1.3.3.1.0072-1
storage pool.
Unisphere Unisphere would sometimes hang after connecting a newly- 563392, 564522 1.3.3.1.0072-1
created LUN to a storage group when the creation of more than
100 LUNs was in process.
Unisphere Unisphere hung after attaching LUNs to a storage group on a 574400, 574986 1.3.3.1.0072-1
VNX5800 with a large configuration.
Unisphere When running a compression command, the followng error code 592568, 589781 1.3.1.1.0033
was sometimes returned
Output: Unrecognized Error Code: (0xe12d8110)

Unisphere User was unable to login with LDAP accounts when using 65187126/665689 1.3.3.1.0072-1
certification chains.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
45
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Fixed in previous releases

Category Description Tracking Fixed in

version
Unisphere From within the GUI, a user can create a VNX Snapshot using a 637800, 618792 1.3.3.1.0072-1
single quote mark in the name. For example, te'st.
The user is unable to delete the snapshot using that name. The
user receives an error message, te'st - Cannot destroy
snapshot. the specified snapshot does not exist.

Unisphere The Unisphere GUI Get Diagnostic Files option truncated the 555002, 537437, 1.3.3.1.0072-1
retrieved size of files larger than 4 GB. GUI truncated diagnostic 628171
file transfers.
Unisphere Unauthenticated HTTP Requests were sent to Tomcat. Error pages 578520 1.3.3.1.0072-1
displyed for HTTP 404 for non-existent addresses.
Unisphere Failed to change the SP name. 8215634/ 59420, 1.3.3.1.0072-1
594205
Unisphere FAST Cache creation failed at 14%. 58483984/597279 1.3.3.1.0072-1
Unisphere Issues with ECOM could result in the following symptoms: 597295, 62770, 1.3.3.1.0072-1
1. CQ 601785: hardware exception dump. When open 2 GUI 637243
session on same laptop, hardware exception dump may be
generated.
2. CQ 602079: ECOM will return inaccurate message "No provider
found to handle this request".
3. CQ 606857: Memory lead happened due to BSAFE/SSL.
Unisphere Unable to login to Block array using LDAP account. 53681376/ 600034 1.3.3.1.0072-1
Unisphere Peer Boot State is showing UNKNOWN in Unisphere. 59060556 / 602760 1.3.3.1.0072-1
Unisphere LDAP timeout. 58765738/ 1.3.3.1.0072-1
604355
Unisphere Unable to view the Tiering info [LUN Properties/Tiering > Tier 58106360/604472 1.3.3.1.0072-1
Details].
Unisphere The Data Mover experienced an updateDouble failure in 61897752/ 1.3.3.1.0072-1
relocateIndexSlot panic. 632237
Unisphere LDAP is not working on multiple Unisphere storage domains. 6128260/ 622499 1.3.3.1.0072-1
Unisphere Not able to list the Symmetrix LUN View for the file systems in 615316 1.3.3.1.0072-1
Unisphere.
Unisphere Edit and Use Configuration buttons are disabled in Available 615749 1.3.3.1.0072-1
Configurations Page of Unisphere.
Unisphere When creating a RAID Group with automatic disk selection mode, 616360 1.3.3.1.0072-1
the creation process failed with an error message indicating that
the RAID Group could not be created with the selected drive
types.
Unisphere Using Java 1.7 versions on PC/host to access Unisphere prevents 61766992/627950 1.3.3.1.0072-1
a new language setting from taking effect.
Unisphere IPv6 addresses appeared in the domain list when IPv6 was 575343 1.3.1.1.0033
configured on the CS and received any operation that involved
setup_slot.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
46
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Fixed in previous releases

Category Description Tracking Fixed in

version
Unisphere The Unisphere SP Properties dialog box shows the speed of the 593974 1.3.1.1.0051
management port as as 10Mbps, even if it is actually set to Auto.
Any modifications made in the SP Properties dialog changes the
requested speed from Auto to 10Mbps.
Unisphere When using Unisphere version 1.3.0 to log in to a domain with a 598046 1.3.1.1.0051
legacy Celerra system, the client reports that the Celerra system is
“Not Logged in”.
Unisphere Unisphere off-array applications will not launch in Java 7 Update 595857 1.3.1.1.0051
45. This is caused by a known issue of Java 7 Update 45.
Unisphere When running VNX Unisphere, a Java warning appears saying that 596623 1.3.1.1.0051
future Java versions will not work with the application

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
47
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block The user will see the vault Manually replace the faulted
Platforms: All USM doesn't display the
OE, USM, disk as faulted, and USM disk, log out of USM, log in
correct message after a
Unisphere Off Severity: Medium cannot go to the next step. again. USM will detect the
drive replacement is
Array Tools complete. new vault disk.
Tracking: 742030
Exists in versions:
05.33.008.5.119
VNX Block When the Unisphere GUI is Move to another GUI page
Platforms: All A VNX for Block CLI
OE, open and the user is on the and the CLI commands will
command failed with an
Unisphere Severity: Medium LUNs page, the CLI may proceeded normally.
error message:
Exception: End of reply with a failure due to a
Tracking: 749558 data stream. connection issue.
Exists in versions:
05.33.008.5.119
VNX Block When the CLI command When the error message
Platforms: All Execution of the
OE, System server_reclaim server_reclaim is 2237 is displayed for
Management Severity: Medium command fails. executed, there may be an server_reclaim, retry the
error message 2237 same CLI command again to
Tracking: 747548 displayed. resolve the issue.

Exists in versions:
05.33.008.5.119
Unisphere, The user cannot log into Use USM to log into EMC
Platforms: All When enabling support
VNX EMC support. There will be Support.
options in Unisphere, single
Severity: Medium error, cannot connect
sign on fails and results in
An error occurred to sso.emc.com.
Tracking: 750931 Exists in versions:
popup message.
05.33.008.5.119
USM, A control station upgrade To restore the missed home
Platforms: All A USM upgrade failed and
Unisphere Off operation failed in USM and directories, failover to the
the user had insufficent
Array Tools Severity: Medium returned following error previously activated control
permissions to run a CLI
message: stderr: station.
command. The message ID
Tracking: 748953 Could not chdir to
was 15569322006. home directory
/home/GlobalAdmin1: Exists in versions:
No such file or 05.33.008.5.117
directory.
05.33.008.5.119

USM, Multiple launches of the Start the ODFU Wizard by

Platforms: All The ODFU wizard hangs on
Unisphere Off ODFU wizard from the icon clicking Software > Disk
the Prepare for Disk
Array Tools Severity: Medium or popup results in hanging Firmware > Install Disk
Firmware Installation page.
on the Prepare for Disk Firmware Online.
Tracking: 745970 Firmware Installation page.
Exists in versions:
05.33.008.5.119

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
48
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All The progress of a pool or The progress of a pool’s Restart Unisphere by using
Severity: Medium LUN operation is frozen. On deduplication operation net stop k10governor
another SP, the display is as hangs. and net start
Tracking: 741477
expected. k10governor
Exists in version:
1.3.8.1.0119

USM, Platforms: All While using VIA to set a host Communication with the Don't use the FQDN host
Unisphere Off Severity: Medium name with FQDN, system failed. name. To specify a host
Array Tools Tracking: 736612 communication with the name, the maximum number
VNX repeatedly failed. of characters is 64, excluding
white spaces and dot
characters.
Exists in versions:
05.33.008.5.119
Install, Platforms: All A Block-to-Unified upgrade Block-to-Unified upgrade The user should follow the
Upgrade, VNX Severity: Medium failed due to misconnected failed. instruction in VIA to
Block OE, FC cables from one Data reconnect the FC cable and
Tracking: 652467
VNX File OE Mover to SPA and SPB. then continue with the
ugprade. If the BTU upgrade
failed later due to the ndf
partition being offline, then
retry the upgrade.
Exists in versions:
05.33.008.5.119
8.1.8.119
VNX Block OE Platforms: All When a power failure for the A poll LUN failed. Wait for the Storage
Severity: Medium entire array (DPE and DAEs) Processor to recover from the
happened, a bugcheck bugcheck.
Tracking: 720833
occurred. Exists in versions:
05.33.008.5.119

VNX Block Platforms: All A Speed change from AUTO Changing 16G FC to AUTO Reboot the affected SP or pull
OE. Fibre Severity: Medium to 16G-only will not login fails. cable on the affected port.
Channel Tracking: 742243 without link bounce. A
Speed change from 16G- Exists in versions:
only to AUTO will not login
without some link bounce. 05.33.008.5.119

VNX, Platforms: All When trying to connect a When adding a host to a The Success in the message
Unisphere Severity: Medium host to storage group, a storage group, a confusing should be ignored. The
Tracking: 744343 message is returned, saying: popup message was operation actually failed.
Results from call to received. It is unclear if the Do not use capital letter(s) in
add host(s) to the operation failed, or if it was initiator IQN name.
storage group: successful.
Exists in version:
The overall
operation failed. 05.33.008.3.270
Error details: 05.33.008.5.119
Success

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
49
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All Some thin LUNs in a pool It is normal that consumed Functions as designed.
Severity: Medium don't show the Consumed capactiy changed to N/A Exists in version:
Capacity in the LUN after dedup is enabled.
Tracking: 745895 05.33.008.3.270
properties field.
05.33.008.5.119

Unisphere Platforms: All Some new feature/changes This issue was found when Clear the JAVA cache after an
Severity: Medium do not take effect on the host had connected to upgrade .
Tracking: 746018 Unisphere GUI after array the SPs/CS IP before an Exists in version:
upgrade. upgrade and the Java cache
05.33.008.5.119
was enabled.

USM, Disk Platforms: All Clicking on the Disk Multiple windows are Close the existing Online
Firmware, Severity: Low Firmware Upgrade opened when launching the Firmware Upgrade Wizard
Unisphere Off Tracking: 746384 notification to start an Online Firmware Upgrade window before starting the
Array Tools Online Firmware Upgrade wizard. wizard.
Wizard window and then Exists in version:
also clicking on Software >
05.33.008.5.119
Disk Firmware > Install Disk
Firmware Online opens a
second window.
VNX File OE, Platforms: All After launching VIA, the VIA window closes after Run the Windows ipconfig
VNX Welcome screen appears. If clicking Next from Welcome command to check if the
Installation Severity: Medium Next is clicked the VIA screen. system has more than six
Assistant application closes. connections. If so, disable
(VIA) Tracking: 600962/ any unused connections to
593647 make the total number six or
less. Retry the VIA operation.
Exists in versions:
8.1.3.72
8.1.3.79
8.1.6.96
8.1.6.101
8.1.8.119
VNX File OE, Platforms: All VIA fails to change the An error message displays Repair any network
VNX sysadmin password on the continuously when trying to connectivity issues on the
Installation Severity: Medium Apply page change the password on the storage system. Wait 10
Assistant storage system and the retry minutes, then click Retry.
(VIA) Tracking: 566667 fails.
Exists in versions:
All 8.1 releases.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
50
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE, Platforms: All VIA window closes after After launching VIA, the Run Windows ipconfig
VNX clicking Next from Welcome Welcome screen appears. If command to determine if the
Installation Severity: Medium screen. Next is clicked, the VIA system has more than six
Assistant application closes. connections. If so, disable
(VIA) Frequency: Rarely the unused connections to
under specific make the total number no
circumstances more than six and retry the
VIA operation.
Tracking: 593647
Exists in versions:
All 8.1 releases.
VNX File OE, Platforms: All After File install & VIA When connecting a VNX via Check the checkbox "Always
Unisphere execution, the initial a CS IP where the CS's trust content from this
Unisphere login to a Unified certificate cannot be publisher".
Severity: Low verified, a web browser
system fails with a
Connection Error. generates a popup, “Do you Exists in versions:
Tracking: 573444 Subsequent login attempts wish to continue?” It also All 8.1 releases.
succeed. provides a checkbox,
"Always trust content from
this publisher". If it is
unchecked, the login screen
will not display and there
will be communication
errors with the CS.

The Java pop up warning

does not appear until you
click Show Options.
VNX File OE, Platforms: All CS cannot be added to the If the hostname was not Ensure there is a public CS IP
system Severity: Medium master domain. File mapped to a public entry in /etc/hosts. If there is
management Tracking: 648929 functions in Unisphere were Operating System IP, the CS not, add one.
disabled as a result. could not be added to Exists in version:
master domain.
8.1.3.72
As a result, the File Function 8.1.3.79
in the Unisphere GUI was
disabled if the user logged 8.1.6.96
in with the domain user 8.1.6.101
account. 8.1.8.119
VNX File OE, Platforms: All Unisphere incorrectly After fixing a compatibility Manually delete the alert
system Severity: Low displays alerts that the VNX problem, Unisphere from the GUI.
management Block OE and VNX File OE displayed alerts that the Exists in version:
Tracking: 646174
versions are not compatible. VNX Block OE and VNX File
8.1.3.72
OE versions are not
compatible. 8.1.3.79
8.1.6.96
8.1.6.101
8.1.8.119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
51
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE, Platforms: All SSL Certificate Weak Public SSL Certificate Weak Public If the current certificate uses
system Severity: Medium Key Strength. Key Strength Found Value: a weak key, a new certificate
management bits [=] 1024. can be generated by
Tracking: 645204
executing "nas_config -ssl" in
the control station in order to
generate a new key with 2048
length.
Exists in version:
8.1.3.72
8.1.3.79
8.1.6.96
8.1.6.101
8.1.8.119
VNX File OE, Platforms: All An error posts during rescan Error during rescan after No workaround.
system Severity: Medium stating that root_disk(s) are setting Host I/O Limits Exists in version:
management unavailable when the limit (previously called Front-End
Tracking: 577681 8.1.3.72
on the SG is set that I/O Quota) on UVMAX SG
contains the control that contains the control 8.1.3.79
volumes. volumes. 8.1.6.96
8.1.6.101
8.1.8.119
VNX File OE, Platforms: All Deduplication LUN is left in Deduplication on a private Please contact your service
system Severity: Medium inconsistent state when LUN hangs at enabling for provider to recover the LUNs
management Storage Processor (SP) weeks. to normal state.
Tracking: 624401
reboots and Exists in versions:
enabling/disabling 8.1.3.72
operation on its way to
completion. 8.1.3.79
8.1.6.96
8.1.6.101
8.1.8.119
VNX File OE, Platforms: All The following error can The file Do not use naviseccli.bin.
system occur when using /usr/lib/libNonFipsUtilities. Use naviseccli instead.
management Severity: Low naviseccli.bin after a fresh so is missing from the
installation: Control Station after an Exists in versions:
Tracking: 532380
./naviseccli.bin: error while loading Express Install installation. All 8.1 releases.
shared libraries:
libNonFipsUtilities.so: cannot open
shared object file: No such file or
directory
VNX File OE, Platforms: All The battery properties in the Users are unable to obtain No workaround.
system inventory page do not detailed power information
management Severity: Medium display input power. when using the GUI or CLI. Exists in versions:
Tracking: 540001 All 8.1 releases.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
52
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE, Platforms: All Error 5007: Running nas_quotas If the error occurs, retry the
system server_5: /nas/sbin/repquota -u occasionally produces the operation.
management Severity: Medium /nas/server/server_4/quotas_fs_file following error:
/nas/server/server_4/quotas_uid_file Exists in versions:
Tracking: 546410 nas_quotas CMD failed:
.etc/rpt_file .etc/rpt_file.sids : : All 8.1 releases.
exec failed /nas/bin/nas_quotas -user -report -
fs pbrfs_0005 501 Error 5007:
server_5: /nas/sbin/repquota -u
/nas/server/server_4/quotas_fs_fil
e
/nas/server/server_4/quotas_uid_fi
le .etc/rpt_file .etc/rpt_file.sids : :
exec failed
VNX File OE, Platforms: All During an upgrade, a thin The out of space error may Limit or suspend write
system file system failed VJTREE occur during an upgrade operations during upgrades.
management Severity: Critical operations because of an when the system encounters
out of space message write operations on file Exists in versions:
Tracking: 558325
systems. The file system All 8.1 releases.
auto-extension cannot
complete because the NAS
service is down during the
upgrade.
VNX File OE, Platforms: All Failure to create a file Some LUNs were bound Avoid operations that lead to
system system from a NAS pool. from a RAID group. The user LUN migration when file
management Severity: Critical ran diskmark and then systems are built on them.
The following error message
Tracking: 563493 displays: created file systems on Verify that the disk type of all
File system cannot be built them. Some of these LUNs disk volumes under the file
because it would contain space were moved to another thin system are from the same
from multiple mapped pools or a pool via LUN compression or mapped pool or compatible
mix of both mapped pool and migration. The new file RAID group based pool(s). For
RAID group based pool. system could not be created file system extension, choose
on these LUNs and diskmark the matching pool that the
failed. current storage of the file
system is from.
Exists in versions:
All 8.1 releases.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
53
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE, Platforms: All SavVol auto extension does Currently, SnapSure SavVol Add more storage into the
system not use up all space left in auto-extend asks for a storage pool used by
management Severity: Low the pool if the pool is certain amount of storage SnapSure SavVol (make sure
smaller than 20 GB. (for example, 20 GB) which at least 20GB is free) and the
Tracking: 569073
is calculated from storage SavVol auto-extend will
pool properties (such as succeed on the next attempt.
HWM). If the storage pool
has less storage than that Exists in versions:
amount (such as 19GB), the All 8.1 releases.
SavVol auto-extend will fail
and some existing
checkpoints may be
inactive. The following alert
displays in Unisphere:
/nas/sbin/rootnas_fs -x
<ckpt_name> QOSsize=20G Error
12010: The requested space
20000 is not available from the
pool <pool_name>.
There will always be a small
amount of storage (for
example, 19GB) that cannot
be fully consumed by
SavVol auto-extend, but
which can be consumed by
other operations (such as
Production File System auto-
extend).
VNX File OE, Platforms: All Storage Pools for File is When running nas_diskmark Press the "Rescan Storage
system empty in the GUI even on a system with massive System" or manually run
management Severity: Low though multiple pools exist. LUNs, there is a very low nas_diskmark again.
possibility that diskmark
Tracking: 573536 Exists in versions:
succeeds; the GUI does not
receive data about its All 8.1 releases.
Storage Pool for File.
The Storage Pool for File
page has no change.
VNX File OE, Platforms: All RecoverPoint File: nas_rp - The primary system has not Wait for the Primary Control
Replication failback - Error completely rebooted, Station to complete its reboot
Severity: Critical 13421904947: resulting in the error. operation before running nas
Tracking: 558919 Unable to communicate with rp -failback.
Control Station on source site.
Exists in versions:
All 8.1 releases.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
54
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE, Platforms: All Replication switchover The replication session fails; Add disk space to the SavVol
Replication stops after the source Data no transfer will continue pool.
Severity: Critical Mover fails over. although the session status
shows fine. A message such Exists in versions:
Tracking: 568516
as the following appears in All 8.1 releases.
/nas/log/sys_log.txt:
CS_PLATFORM:SVFS:ERROR:2
1:::::Slot4:1372057453:
/nas/sbin/rootnas_fs -x
root_rep_ckpt_978_56827_1
QOSsize=20000M Error 3024:
There are not enough free disks
available to satisfy the request..
VNX File OE, Platforms: All RPA reboot regulation and Replication replica cluster Disable group will stabilize
Replication detach form cluster. will become unstable and RP system.
Severity: Critical rpa will reboot until affected
CG is expelled or Journal Exists in versions:
Tracking: 586433
Volume LUN configuration is All 8.1 releases.
fixed.
VNX File OE, Platforms: All RecoverPoint failback fails. When running RecoverPoint No workaround.
Recover Severity: Medium failback, the following error
Point FS appears, then the operation Exists in versions:
Tracking: 644251 8.1.3.72
fails:
13421849338: File system FS1 is 8.1.3.79
made up of disk volumes with 8.1.6.96
inconsistent disk types: d7 (dense 8.1.6.101
UNSET),d8 (dense UNSET),d9 8.1.8.119
(dense UNSET),d10 (dense
UNSET),d11 (dense
Mirrored_performance),d12 (dense
UNSET),d13 (dense
Mirrored_performance),d14 (dense
UNSET),d15 (dense UNSET),d16
(dense Mirrored_performance)

VNX File OE, Platforms: All The Recover Point init Running /nas/sbin/nas_rp This issue rarely occurs.
Recover command failed while -cabinetdr -init Rerun /nas/sbin/nas_rp -
Point FS Severity: Critical discovering storage on a <cel_name> failed with the cabinetdr -init <cel_name>.
source site. following error:
Tracking: 570980 Error 5008: Error discovering Exists in versions:
storage on src site. All 8.1 releases.
VNX File OE, Platforms: All nas_migrate -i Some warning messages These messages are only
Migration <migration name> printed relative to other migration warnings and will not impact
Severity: Low other migrations' warning sessions running on the the execution of the current
messages. same box could appear session.
Tracking: 565259
when information is
requested on a particular Exists in versions:
session. All 8.1 releases.
VNX File OE, Platforms: All Migration information does The UI provides inaccurate CLI and log files provide
Migration not accurately reflect the progress information on more accurate info.
Severity: Low task information and migration tasks.
percent complete on the Exists in versions:
Tracking: 565886
source system. All 8.1 releases.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
55
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE, Platforms: All Usermapper service was On global configuration Manually disable the
Migration enabled on destination migration, if usermapper is usermapper service on the
Severity: Critical while it was disabled on disabled on the source target.
source. cabinet, warning is reported
Tracking: 565968 Exists in versions:
but manual operation is
asked to the user to disable All 8.1 releases.
the target usermapper
service.
VNX File OE, Platforms: All Unisphere failed to access When attempting to connect Close or terminate the
ESRS (Control the Control Station. to the array by using existing session using the
Station) Severity: Critical Unisphere and the ESRS terminate button. Alternately,
Tracking: 557982 Service Link, a Certificate go to Service Link > View All >
Error may occur. End (for all existing sessions)
and start a new session.
Exists in versions:
All 8.1 releases.
VNX File OE, Platforms: All VNX CIFS server cannot be When a VNX CIFS server is Microsoft Windows 2012
CIFS managed by Windows 2012 added to a Windows 2012 Server Manager requires
Severity: Medium Server Manager. Server manager, the Microsoft Agent on the server;
following error is displayed: EMC does not support third
cannot manage the operating party installation on its
Tracking: 566436 system of the target computer server.
To access information on a
server managed by a VNX
storage system, you must use
'computer management'
instead of 'server manager'.
Exists in versions:
All 8.1 releases.
VNX File OE Platforms: All After disabling When attempting to enable Wait and try again later.
Severity: High deduplication on a LUN, it or disable the deduplication Exists in versions:
Tracking: 661800 can take longer than on a LUN while it is 8.1.6.96
expected to enable disengaging from its
deduplication on the same deduplication destination, 8.1.6.101
LUN again. the system returns the 8.1.8.119
following error:
Could not set
properties:(Deduplication: SP A:
Cannot enable/disable
Deduplication on the LUN %x
which is not ready. If problems
persist please gather SP Collects
and contact your service provider.
(0x716a841b)).

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
56
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX File OE Platforms: All When a VNX Storage Connecting the faulted SP Manually reset the faulted
Severity: Medium Processor (SP) reboot is with console server or Storage Processor.
Tracking: 661888 initiated, the SP can stop terminal server, displays a Exists in versions:
booting because of a POST message such as ErrorCode: 8.1.6.96
error. The SP will appear to 0x00000310.
be faulted by its peer 8.1.6.101
storage processor. 8.1.8.119
VNX File OE Platforms: All After a cache lost event, Storage pool resources are Manually fix the corruption
Severity: Medium running Storage Pool temporarily unavailable. and run Pool Recovery again.
Tracking: 701819 recovery failed, and the Exists in versions:
Storage Pool was 8.1.6.96
inaccessable.
8.1.6.101
8.1.8.119
VNX File OE Platforms: All The following error occurred The pool name on the Run the nas_diskmark -m –a
when the user renamed a Control Station (CS) is command on the CS after
Severity: Medium mapped pool in the different from the pool name performing any of the
Tracking: 564012 backend: on the backend. This error following operations related
com.emc.cs.symmpoller.Agen results when renaming a to the ~filestorage group:
tException: The specified mapped pool on the • Add/remove a LUN.
object does not exist. backend, but the
• Turn on, turn off, pause,
nas_diskmark command is
resume or modify
not run on the Control
Compression on a LUN.
Station to synchronize the
pool names. • Modify the Tiering Policy
or Initial Tier of a LUN.
• Create/destroy a mirror
(both sync and async)
on a LUN.
Exists in versions:
All 8.1 releases.
VNX Block Platforms: All LUN –destroy operation fails Snapshot destroy is an Wait for the snapshots to be
OE, VNX with snapshots exist error if asynchronous operation. If a destroyed or include the
Snapshots Severity: Medium a LUN is destroyed LUN is destroyed “destroySnapshots” switch
immediately after destroying immediately after destroying while destroying the LUN.
Frequency: Rarely snapshot(s) associated with its snapshots, there is a
under a rare set of the LUN. possibility of a snapshot Exists in versions:
circumstances being in the destroying state All 5.33 versions.
that prevents the LUN from
Tracking: 481887 being destroyed.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
57
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block Platforms: All Not enough free space in a If the total consumed size of Expand the pool or if the
OE, Virtual pool to recover LUNs. a LUN is greater than 512TB 512TB spans multiple LUNs.
Provision Severity: Critical and there is not enough free Then, only do one recovery at
space in the pool (up to a time where each LUN is at
Tracking: 569009 600GB), the recovery of that or below 512TB of consumed
LUN will require expanding space.
the pool to create the
required free space. This Exists in versions:
also means if there are All 5.33 versions.
multiple LUNs consuming a
sum of 512TB consumed
space, but each LUN
consumes less than 512TB,
recovery can be run
simultaneously on multiple
LUNs only as long as the
sum of their consumed size
is less than 512TB.
VNX Block Platforms: All A storage processor (SP) The SP may reboot if the Do not trespass destination
OE, SANCopy may reboot if many following occurs: LUNs or initiate an NDU when
Severity: Medium destination LUNs are • If a SAN Copy session is a copy session with 50 or
trespassed or an NDU is running with 50 or more more destinations is in
Frequency: Likely initiated. destinations located on progress.
under specific
the SAN Copy storage Exists in versions:
circumstances
system and 50 or more
of the destination LUNs All 5.33 versions.
Tracking: 293019
are trespassed.
• An NDU is initiated.
VNX Block Platforms: All A LUN shrink operation on a Compression has internal No workaround.
OE, LUN with compression logic to iterate many times
Compression Severity: Low enabled takes a long time. for the shrink operation to Exists in versions:
Frequency: properly clear the data. All 5.33 versions.

Infrequently under
specific
circumstances
Tracking: 543919
VNX Block Platforms: All A decompressing LUN Compression uses LUN Enable compression on the
OE, cannot be destroyed. Migrator technology for LUN before destroying it, or
Compression Severity: Low decompression and wait for decompression to
Frequency: destroying a LUN under this complete.
condition is not allowed.
Always under Exists in versions:
specific All 5.33 versions.
circumstances
Tracking: 549338

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
58
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE LUN remains in a destroying After attempting to destroy a Contact your service provider.
Platforms: All
Virtual state. LUN, the LUN remains in a
destroying state. The LUN – Exists in versions:
Provision Severity: Medium
list command returns: All 5.33 versions.
Frequency: Rarely Current State : Destroying (5)
during a rare set of
circumstances

Tracking: 577722

VNX Block OE Platforms: All Windows Server 2012 When the storage pool low This is a reporting issue with
Virtual storage pool low space space warning threshold is the Windows Server event
Provision Severity: Medium warning shows the incorrect crossed, the event logged log. The correct used and
used and available capacity on a Windows 2012 server available capacity are
Frequency: Always of the pool. does not show the correct displayed in the Unisphere
during a specific used and available capacity UI.
event of the pool.
Exists in versions:
Tracking: 539153 All 5.33 versions.

VNX Block OE Platforms: All In the case of single-fault On an idle array (where no If IOs are running on the
Virtual disk failures, the pool LUN IOs are running on the array, or even a single write is
Provision Severity: Medium state is reported as ready array), in the case of single- done to the LUN right after
when the LUNs are actually fault disk failures (RAID the disk fault occurred, the
Frequency: Always faulted. protection is still intact), the situation will correct itself
during a specific pool LUNs on the non- after two minutes and both
event. owning SP show as ready SPs will report pool LUNs as
when they should show as faulted.
Tracking: 556191 faulted like the LUNs on the
owning SP. Exists in versions:
All 5.33 versions.
Unisphere Platforms: All When changing the Use the VNX for Block CLI Exists in versions:
Recommended Ratio of hotsparepolicy -set 1.3.1.1.0033
Severity: Critical Keep Unused setting from command to overwrite the 1.3.2.1.0051
30 to 60, insufficient disk recommended value (for 1.3.3.1.0072-1
Frequency: space may be reserved for example, overwriting 60 with 1.3.6.1.0096
Occasionally hotspares and may increase 30) to the desired value. 1.3.8.1.0119
the risk of failure. For example:
Tracking: 606043 hotsparepolicy -set
<Policy ID> -
keep1unusedper 30 -o
VNX Block OE Platforms: VNX After removing a VNX Try to restart the management
Severity: Medium enclosure, Unisphere may server via the Unisphere
Tracking: 701406 still show the enclosure as Setup page. If the removed
present. enclosure still appears,
reboot the Storage Processor
(SP).
Exists in:
05.33.006.5.096
05.33.006.5.102
05.33.008.5.119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
59
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All In a VNX pool with An error message indicates Attempt to delete the pool at
Severity: Low deduplication enabled, that the pool is not empty a later time.
when all LUNs in the pool when it is empty. Exists in versions:
Frequency:
are deleted, the VNX system
Occasionaly under 05.33.006.5.096
indicates that the pool is not
certain conditions empty. 05.33.006.5.102
Tracking: 680639 05.33.008.5.119

VNX Block OE Platforms: All A single VNX Storage VNX Storage Processor (SP) Exists in versions:
Severity: High Processor (SP) bugcheck bugcheck occurs during a 05.33.006.5.096
Tracking: 686838 occurs when a migration migration process. 05.33.006.5.102
process attempts to start a
new session on storage pool 05.33.008.5.119
LUN.

VNX Block OE Platforms: All Attempting to delete a LUN SP bugcheck for both Avoid deleting LUNs while
Severity: High while specific operations are system Storage Processors. any of the specified
active results in a bugcheck operations are active
Tracking: 662213
(0x05900000) on both VNX Exists in versions:
Storage Processors (SPs) 05.33.006.5.096
These operations include: 05.33.006.5.102
• Clone - Sync 05.33.008.5.119
• CPM - Copy/Resume
• SanCopy -
Rollback/SnapLU
activate
• MLU - Attach/Rollback
snap
VNX Block OE Platforms: All After creating a VNX storage The system generates the Perform a full poll from
Severity: Medium pool performing the following error message: Unipshere Debug page or
following combination of C:\Program Files restart the k10governor
Tracking: 694090
actions creates a system (x86)\EMC\Navisphere service on both Storage
error: CLI\NaviSECCli.exe" -User Processors (SPs).
sysadmin -Password sysadmin -
1. Swapping out a disk in Scope 0 -h 10.244.212.80 Exists in versions:
the storage pool storagepool -create -disks 0_5_1 05.33.006.5.096
2. Deleting the storage pool 0_5_ 2 0_5_3 0_5_4 0_5_0 -rtype 05.33.006.5.102
r_5 Disk Pool number already in
3. Creating a new storage use (0x76008301) 05.33.008.5.119
pool

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
60
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All Encryption percentage does Look for the following
Severity: Medium not change. activities in the system:
Tracking: 649384 Faulted disk
Disk zeroing in progress
Disk rebuild in progress
Disk verify in progress
Exists in verion:
05.33.000.5.072
05.33.000.5.074
05.33.000.5.079
05.33.000.5.081
05.33.006.5.096
05.33.006.5.102
05.33.008.5.119

VNX Block OE Platforms: All A Link Control Card (LCC) or The peer LCC/ICM does not Exists in version:
Inter Connect Module (ICM) have this problem. Once in 05.33.000.5.081
Severity: Medium this state, the fault persists.
in a VNX DAE reports either 05.33.000.5.079
Frequency: Rarely a PSU fault or Fan fault 05.33.000.5.074
because it does not detect a 05.33.000.5.072
Tracking: 599765 replaced module (after a 05.33.000.5.051
FRU). 05.33.006.5.096
05.33.006.5.102
05.33.008.5.119

VNX Block OE Platforms: All When downloading firmware In this case, ODFU process Wait for the RAID group
to drives using The Online is not hung but is paused rebuild to complete and the
Severity: Medium waiting for the RAID group
Disk Firmware Upgrade ODFU process will
rebuild to complete.
Frequency: Rarely (ODFU) process, if a drive in automatically resume.
a RAID group is faulted
Tracking: 616702 Exists in version:
during the download
process it can take an 05.33.000.5.081
extended time (up toseveral 05.33.000.5.079
days) for the download 05.33.000.5.074
process to fully complete. 05.33.000.5.072
ODFU shows that it is in the 05.33.000.5.051
ACTIVATE state for the 05.33.006.5.096
remaining drives in the 05.33.006.5.102
degraded RAID group. 05.33.008.5.119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
61
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All After a non-disruptive In rare cases, a Broadcom Log in through the VNX
upgrade (NDU), the driver can cause issues system service port, then first
Severity: Low when bringing up VNX
management port for one of disable and then re-enable
system SP management
Frequency: Seldom the VNX system’s Storage the disconnected VNX SP
ports after a NDU.
Processors (SPs) may management port.
Tracking: 613348 transition to disconnected If disabling and then re-
status. anabling the SP port does not
work, try rebooting the SP.
Exists in version:
05.33.000.5.081
05.33.000.5.079
05.33.000.5.074
05.33.000.5.072
05.33.000.5.051
05.33.006.5.096
05.33.006.5.102
05.33.008.5.119

VNX Block OE Platforms: All When migrating LUNs within For more information, refer Avoid migrating LUNs within a
the same deduplication to KnowledgeBase article deduplication domain. If you
Severity: Medium 176653.
domain, deduplication need to move the current LUN
Frequency: savings are lower than to a larger one, use the LUN
Occasionally expected is complete. expansion functionality
instead.
Tracking: 611558
Exists in version:
05.33.000.5.081
05.33.000.5.079
05.33.000.5.074
05.33.000.5.072
05.33.000.5.051
05.33.006.5.096
05.33.006.5.102
05.33.008.5.119

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
62
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All The VNX Security The timeout value for Exists in versions:
Configuration Guide lists Unisphere on VNX Block-
Severity: Minor steps required to change the only systems cannot be 05.33.000.5.081
Frequency: Always Unisphere session timeout changed with VNX 05.33.000.5.079
period. These steps only Unisphere or the VNX for 05.33.000.5.074
Tracking: 617430 apply to VNX Unified and Block CLI. 05.33.000.5.072
VNX File-only systems. VNX 05.33.000.5.051
Block-only systems do not
05.33.006.5.096
provide a way to adjust the
Unisphere timeout session 05.33.006.5.102
period. 05.33.008.5.119

VNX Block OE Platforms: iSCSI ports are unitialized When copper twinaxial Replace copper twinaxial
VNX5400, VNX5600, after an upgrade to VNX OE cables that support iSCSI cables with optical small
VNX5800, VNX7600, for block version connections are in use, form-factor pluggable
iSCSI hosts experience data
VNX8000 05.33.000.5.034 upgrade. transceivers and cables from
unavailable (DU) after a
non-disruptive upgrade array ports to switch.
Severity: Critical
(NDU) to VNX Block OE Exists in versions:
Frequency: Always version 05.33.000.5.034.
The iSCSI hosts can no 05.33.000.5.034
under specific
circumstances longer log in. 05.33.000.5.051
05.33.000.5.072
Tracking: 05.33.000.5.074
58805510/ 05.33.000.5.079
599567 05.33.000.5.081
05.33.006.5.096
05.33.006.5.102
05.33.008.5.119

VNX Block OE Platforms: The Dirty Cache Pages Dirty Cache Pages (MB) No workaround.
VNX5200, VNX5400, (MB):, message displayed message displays an
by the Unisphere CLI after estimation that may be Exists in versions:
VNX5600, VNX5800,
VNX7600, VNX8000 issuing the command cache higher than the actual value All 5.33 versions.
-sp -info, may be inexact. for short time periods,
Severity: Low especially while the SP
Frequency: Cache is in the Disabling
Infrequently under state.
specific
circumstances

Tracking: 564282

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
63
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: A Background Verify A Background Verify Reissue the Background
VNX5200, VNX5400, operation may not complete operation may not complete Verify operation after the
VNX5600, VNX5800, while a RAID type 10 is as expected; it is not normal initialization is complete.
VNX7600, VNX8000 initializing after a bind to issue a Background Verify
Exists in versions:
operation. operation immediately after
Severity: Low All 5.33 versions.
a bind operation.
Frequency:
Frequently under
specific
circumstances

Tracking: 555603

VNX Block OE Platforms: All LUNs may fail to come After a storage pool that Contact your service provider.
online after a power failure went offline due to a
Severity: Medium Exists in versions:
or hardware failure. hardware failure comes
All 5.33 versions.
Frequency: Rarely back online, some LUNs in
under a rare set of that storage pool will stay
circumstances offline.
The LUN –list command will
Tracking: 579903 display:
Deduplication primary LUN
requires recovery. Please contact
your service
provider.(0x712d8d3b)

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
64
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All Drives that do not support When one or more drives in Contact your service provider.
Enhanced Queuing become a VNX array running OE for
Severity: Critical faulted on VNX Block OE Block 05.33 have a version Exists in versions:
05.33 systems. of firmware that does not All 5.33 versions.
Frequency: Rarely
under specific support Enhanced Queuing.
circumstances Running naviseccli –h
<SP IP addr> faults –
Tracking: 580959 list command returns:
Faulted Subsystem: <array serial #>
Bus <bus #> Enclosure <encl #>:
Faulted
Bus <bus #> Enclosure <encl #>
Disk <disk #> : Removed
Running naviseccli –h
<SP IP addr> getlog
returns the following (event
log ID):
(71678047)Bus <bus #> Enclosure
<encl #> Disk <disk #> failed
enhanced queuing check. SN: <disk
serial #> TLA:<disk tla #> Rev:<disk
firmware rev>
Ktrace logs on the array SP may
also contain:
std:WARN OBJ <disk obj #>
DSK:<bus #>_<encl #>_<slot #>:
Drive firmware upgrade
required. Enhanced queuing not
supported.
VNX Block OE Platforms: All SP B in peer set-up For SPs A and B in a peer Reboot the system after
experiences a fatal error set-up, SP A was idle manually entering the BIOS.
Severity: Critical while SP A is idle after (performing triage activities
rolling reboot. after a rolling reboot) when Exists in versions:
Frequency: Rarely
under specific SP B experiences a fatal All 5.33 versions.
circumstances error.

Tracking: 547980

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
65
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: On the battery back-up On the backup battery unit, No workaround.
VNX5200, VNX5400, (BBU) unit, the marker LED in certain Battery failure
VNX5600, VNX5800, does not get set for certain cases, the fault LED (located Exists in versions:
VNX7600 fault conditions. on the battery backup unit) All 5.33 versions.
will not assert. In most
Severity: Medium cases, the firmware will
Frequency: Rarely assert the LED. But if the
under specific BBU fails due to specific
circumstances self-test faults, or the
battery backup unit fails to
Tracking: 554516 charge fully after 16 hours,
the fault LED will not be set.
VNX Block OE Platforms: All When a module is removed It takes about 3 seconds for No workaround.
from an enclosure, the drive or the enclosure to
Severity: Medium approximately 3 seconds be reported as removed Exists in versions:
elapse before the removal after a drive pull or an All 5.33 versions.
Frequency: Rarely
under specific detection occurs. enclosure pull. In other
circumstances words, there is a 3-second
delay between the time the
Tracking: 558151 drive is rendered out of
service and the time the
drive is detected as
removed.
VNX Block OE Platforms: All A Windows 2012 server may Windows 2012 server No workaround.
unexpectedly reboot. reboots unexpectedly when
Severity: Low the specified threshold of Exists in versions:
70% is crossed on the All 5.33 versions.
Tracking: 561589
storage pool. This event only
happens with
NativeWindows MPIO and
when no Multi-pathing is
enabled on the server.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
66
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All Unexpected error is When using the ODFU Wait until the NDU operation
displayed during the online Wizard, if you cancel the that is part of the ODFU
Severity: Medium disk firmware upgrade operation after it has Wizard's activities is actually
(ODFU). already started, the non- completed before retrying the
Frequency: Rarely
disruptive upgrade (NDU) Wizard. This can be
under specific
installation that is part of determined by running
circumstances
the underlying “naviseccli ndu –status”
Tracking: 566151 implementation will command and confirming the
continue. The Wizard status is: “Status: Operation
confirms the cancellation completed successfully.” If
even though the NDU so, then retry the ODFU
operation is ongoing and Wizard.
cannot be interrupted.
Exists in versions:
If you retry the ODFU Wizard All 5.33 versions.
and it attempts to perform
the underlying NDU
operation again, it may
result in an error saying that
a package is already
installed. The error is an
accurate reflection of what
is happening on the array.
VNX Block OE Platforms: All The Service Processor This issue occurs when both No workaround.
Enclosure (SPE) fault LED the xPE SPA battery and the
Severity: Medium does not turn on after SPE DAE 0_0 SPB battery are Exists in versions:
battery removal. removed. In this case, the All 5.33 versions.
Frequency:
fault LED on DAE 0_0 will
Rarely under assert, but the fault LED on
specific the xPE will not. In this
circumstances specific case, the fault LED
should assert on the xPE
Tracking: 569147 because a second SPS on
both the xPE and DAE allows
cache to remain enabled.
VNX Block OE Platforms: All Online Drive Firmware This problem occurs when The workaround is to repair
Upgrade (ODFU) will wait for using USM to install the degraded RAID group, so
Severity: Medium a degraded RAID group to firmware on drives that are it is healthy again and the
Frequency: become healthy before it in a degraded RAID firmware upgrade can
will complete the firmware group. Some drives in the continue/complete, or cancel
Rarely under upgrade of all drives in that degraded RAID group may the outstanding ODFU from
specific degraded RAID group. be shown as ‘Non-qualified’, USM.
circumstances while other drives won’t be
listed by USM and won’t be Exists in versions:
Tracking: 568692 upgraded. The ODFU screen All 5.33 versions.
may show 100% in the
progress bar, although the
installation status will still
show ‘In progress.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
67
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

VNX Block OE Platforms: All Powerfail: SPa bug checked After an upgrade failure, an No user action is required to
for DLS.sys SP may time out while recover from this failure. The
Severity: Medium (DLS!DLSInitialize+1396d) waiting for recovery to timing of the locks that are
Frequency: in power fail test during complete and panic the SP used to synchronize these
NDU. prematurely. After the threads has been changed.
Rarely under panic, the SP will finish
specific recovery and come up Exists in versions:
circumstances normally. The symptoms are All 5.33 versions.
that recovery after a failure
Tracking: 568692 may take slightly longer
than expected, and a dump
file would be found on the
SP that was recovering. Not
every upgrade failure can hit
this timing window, and
there has to be other activity
(Deduplication, LUN
migration, etc.) for this
window to be triggered.
Virtualization Platforms: All VMware: Sync does not VASA information displays If you suspect that this
perform after a session is in vSphere may be out of information may be out of
Severity: Low re-established. sync with the current state date, perform a manual Sync
of the storage system due to via the Storage Providers
Tracking: 465905 errors in the Storage page and refresh/update the
Provider, vCenter Server, or appropriate pages in the
communication errors vSphere Client. If this does
between the two not fix the issue, remove and
components. re-add the Storage Provider(s)
in question.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
68
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Virtualization Platform: All VASA Unable to add Vendor To allow a LDAP user to login
LDAP users are not properly Provider in vSphere using through VASA, it is not
Frequency: Always mapped to correct VASA credentials of an LDAP user sufficient for the LDAP group
under specific privileges on VNX for File. on VNX for File. to be mapped to an
circumstances appropriate group.
1. Create an LDAP user
Severity: Low account, if it does not
Tracking: 496273 exist, by having the user
login through Unisphere
(through the Control
Station IP). This will auto-
create the account..
2. When the appropriate
mapped account exists
on the Control Station,
the administrator can add
the user to any of the
three groups 'VM
Administrator', 'Security
Administrator' or
'Administrator'.
Note: The account should be
mapped to the least
privileged account that allows
all the necessary operations
to take place.
Exists in versions:
All versions
Virtualization Platforms: All VASA Provider goes off-line To add a VNX Block storage Remove both VASA
and the certificate is system *twice* to the list of connections to the storage
Severity: Low missing. Information does Vendor Providers (once for system, then re-add a single
not update in Virtual Center. each Storage Processor) is VASA connection to either of
Tracking: 565093 not a valid configuration. the SPs.
This results in duplicate
data being returned to
vCenter Server. To remove
one of these duplicate
connections also de-
authorizes the vCenter
Server on the other
(remaining) connection, and
results in this connection
becoming offline.
Virtualization VAAI The copy offload operation No action necessary. After the
Platform: All
Copy offload between SPs generateds requests on the copy offload operation
Frequency: Always causes implicit trespasses. array that trigger load completes, normal host I/O to
under specific balancing. If the source and the destination LUN trigger
circumstances. destination devices are not the load balancing back to
owned by the same SP, the correct user-assigned SP.
Severity: Low the array moveds Exists in versions:
ownership of the
destination LUN to match All 1.3 versions.
the source.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
69
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

USM Platforms: All USM Online Disk Firmware The information about failed Exists in version:
Upgrade (ODFU) failed to disks presented to the user 1.3.3.1.0072-1
Severity: Medium report the information about is not accurate.
1.3.6.1.0096
failed disks. 1.3.8.1.0119
Tracking: 645113

USM Platforms: All After an NDU, one SP's UPGRADE_WITH_USM failed. Disable and then enable the
manangement port may be manangement port by logging
Severity: Medium in a disconnected status. in through the service port. If
this doesn’t work, try
Frequency: Seldom rebooting the SP.
occurs
Exists in versions:
Tracking: 613348 1.3.3.1.0072-1
1.3.6.1.0096
1.3.8.1.0119
USM Platforms: All The USM Online Disk While watching the status in No workaround.
Firmware Upgrade (ODFU) the USM ODFU wizard, some Exists in versions:
Severity: Medium wizard inaccurately reports reports are inaccurate. The All 1.3 versions.
the disk firmware upgrade completed disks number
Tracking: 572236 status and progress. increases, while the
Remaining disks and
Upgrading disks number
remains at 0; the progress
bar remains at 100%, while
the upgrade is still in
progress; once the overall
staus is complete, it's
possible that not all disks
have been reported.

USM Platforms: All Cannot log into USM when When one SP is down, USM None.
one SP is down. takes several minutes to log Exists in versions:
Severity: Medium into the system. All 1.3 versions.
Tracking: 558207

USM Platforms: CLARiiON An error is presented when The wizard returns an error Java 64 does not support
running the Storage System when run against a loading 32-bit DLL. Install 32-
Severity: Medium Verification wizard on a CLARiiON system. bit Java.
CLARiiON system.
Tracking: 550578

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
70
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

USM Platforms: All The software upgrade USM does not support No workaround.
process hangs after a file upgrades of VNX OE in a Exists in versions:
Severity: Medium transfer. proxy configuration. All 1.3 versions.
Tracking: 559742

USM Platforms: VNX An internal error appears An internal error is shown Verify network connectivity.
during a language pack after the File-side language Restart USM and log into the
Severity: Medium installation. pack is installed, and system. Start the Install
before starting the Block- Software wizard and choose
Tracking: side language pack the third option to install the
561544/ installation. Block language pack.
551522 Exists in versions:
All 1.3 versions.
USM Platforms: VNX The Install Software wizard The Install Software wizard Under Tools, click Software
fails to upgrade VNX Block fails to upgrade the VNX for Maintenance Status to view
Severity: Medium OE. Block OE. An error states the upgrade status. When the
that USM is unable to obtain upgrade finishes, commit the
Tracking: 578647 the software maintenance package and re-enable
status. statistics, if needed.
Exists in versions:
All 1.3 versions.
Unisphere, Platforms: All Unisphere sometimes loads Some Unisphere content, for Enable Java Cache to ensure
slowly or does not load example, wizard panels and that future load times are
completely. the support section, may not faster.
Severity: Medium
appear. The Language
Package does not take Exists in versions:
Tracking: 538390 effect and the UI appears All 1.3 versions.
only in English.

Unisphere Platforms: All In rare cases, Unisphere In rare conditions, if the Disable the failback policy
QoS Manager Quality of Service Manager fallback policy is enabled, and reconnect to the array
Severity: Critical may lose connection to the the Unisphere QoS Manager after three mintues.
array for two or three GUI/CLI will lose connection
Tracking: 562832 minutes. to the array for two or three Exists in versions:
minutes. All 1.3 versions.
Unisphere Platforms: All Naviseccli commands on Naviseccli commands fails The naviseccli string that
Host the control station that have authentication even with contains a "$" should be
software, CLI, Severity: Low a "$" in the username or password that is confirmed enclosed in single quotes
and Utilities password fail to work with Unisphere. (such as 'test$me'), so the
Frequency: Always authentication. entire string will be passed to
under specific naviseccli, passing
circumstances authentication.
Tracking: Exists in version:
62974296/ 1.3.3.1.0072-1
641084, 642898 1.3.6.1.0096
1.3.8.1.0119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
71
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: Server Utility update Unisphere Server Utility Add the hostname-ipaddress
Host command failed with error serverutilcli update mapping to /etc/hosts.
software, CLI, All Linux and Unix message: command fails with error
and Utilities message: Exists in versions:
platforms NAVLInetHostNotFound:
No such host... No such host. All 1.3 versions.
Severity: Critical

Tracking: 572417

Unisphere Platforms: VNX5400 Pool creation failed on a When attempting to create a No workaround. This is
Host VNX5400. storage pool, the following expected behavior when the
software, CLI, Severity: Low pool status message may be system limits are exceeded.
and Utilities received if the system LUN The storage pool can be
Tracking: 573776 limits have been reached: destroyed.
Current Operation: Creating
Current Operation State: Failed Exists in versions:
Current Operation Status: Illegal All 1.3 versions.
unit number Current Operation
Percent Completed: 24
This message indicates that
system configuration has
reached it maximum
configuration for FLU's and
the pool cannot be created.
Unisphere Platforms: Windows Removal of an iSNS target is Although the Server Utility No workaround. The Server
Host reported by the Server Utility cannot remove an iSNS Utility cannot be used to
software, CLI, Severity: Medium as successful when the target, the iSNS target still remove an iSNS target.
and Utilities operation was actually can be selected for removal.
Tracking: 573772 unsuccessful. The remove operation will Exists in versions:
then be reported as All 1.3 versions.
completing successfully,
even though it was
unsuccessful and the target
is still present.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
72
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: The virtual Fibre Channel This is an environmental Ensure that the management
Host port configured for the issue caused by the operating system and virtual
software, CLI, Windows Server Hyper-V virtual machine management operating machine are running on the
and Utilities 2012 (VM) cannot be recognized system and the virtual same version of integration
by the VM. machine being run on services. For more
Severity: Low different versions of information, refer to:
integration services. The Version compatibility of
Tracking: 521220 management operating Integration Service:
system (which runs the http://technet.microsoft.com/
Hyper-V role) and virtual en-
machines should run the us/library/ee207413%28v=W
same version of integration S.10%29.aspx
services. Otherwise, some How to upgrade the Integration
new features of the Service:
http://technet.microsoft.com/
management operating
en-
system might not be us/library/ee941103%28v=W
supported on the VM. S.10%29.aspx

Exists in versions:
All 1.3 versions.
Unisphere Platforms: Linux and Unisphere Host Agent Unisphere Host Agent The hostname-ipaddress
Host UNIX platforms cannot be started on an cannot be started on mapping should be added to
software, CLI, AsianUx host. AsianUx host. An error /etc/hosts. Host Agent
and Utilities Severity: Critical message such as the requires the hostname-
following appears in ipaddress mapping for a
Tracking: 547526 /var/log/agent.log: network connection.
mm/dd/yyyy 16:43:56 Agent
Main -- Net or File event. Err: Exists in versions:
Local hostname/address All 1.3 versions.
mapping unknown; see
installation notes.
Unisphere Platforms: Windows On a Windows 2012 server, On Windows Server 2012 Install Microsoft Windows 8
Host Server 2012 Windows STOP errors can without February 2013 and Windows Server 2012
software, CLI, occur when running Server cumulative updates February 2013 cumulative
and Utilities Severity: Low Utility 1.3 or Host Agent 1.3. installed, Windows STOP updates. Refer to Microsoft
Tracking: 519934 errors (blue or black screen Knowledgebase article
errors) can occur when 2795944 for more
running Server utility or Host information:
Agent 1.3. http://support.microsoft.com
/kb/2795944/EN-US
Exists in versions:
All 1.3 versions.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
73
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: Windows When configuring an iSCSI Server Utility may fail to If multiple network adapters
Host connection, the Server Utilty connect if the server has are configured on the server,
software, CLI, Severity: Critical may fail to connect if the serveral network adapters, EMC recommends that the
and Utilities wrong network adapter is not all of them are reachable default adapter is selected
Tracking: 537021 selected. to each other, and the wrong while using the Server Utility
network adapter is selected to create an iSCSI connection.
when configuring an iSCSI Alternatively, ensure that the
connection. The failure right network adapter is
message may also take a selected. Otherwise, the
while to appear. selected subnet may not be
able to access the target.
Make sure that the selected
network adapter can access
the target configured on
array.
Exists in versions:
All 1.3 versions.

Unisphere Platforms: All Unisphere may crash when For systems with large Increase Java memory by:
Analyzer using Analyzer on a system configurations, the 1. Go the Start menu in
Severity: Critical with a large configuration Unisphere UI may crash if Windows.
(hundreds of LUNs). there are hundreds of LUNs. 2. Select Settings > Control
Tracking: 572930
Panel.
3. Double-click the Java
Plugin icon.
4. Select the Advanced tab.
5. In the Java Runtime
Parameters, type
Xmx1024m.
Exists in versions:
All 1.3 versions.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
74
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All The deduplication feature- The deduplication feature No workaround
Analyzer level state of the array is state of the array is
Severity: Medium inaccurate in both the UI or inaccurate when opening Exists in versions:
CLI. the archive dump file in the All 1.3 versions.
Tracking: 562742 UI or CLI.
In the UI, the deduplication
tab of the specific mapped
LUN should display the
deduplication feature-level
state, but it actually
displays the state of the
pool in which the mapped
LUN is contained. In the CLI,
the deduplication feature
state is incorrect in the
dump for the LUNs
configuration. It shows the
states of the LUN instead of
the feature-level state.
Unisphere Platforms: All Analyzer does not work Unisphere Real-Time Close both sessions and start
Analyzer when there are two open Analyzer does not work only one Unisphere Analyzer
Severity: Low sessions for the same when there are two sessions UI session.
system. for the same host system.
Tracking: 559104 Exists in versions:
All 1.3 versions.
Unisphere Platforms: All When running VNX When Unisphere off-array Work arounds:
Unisphere in off-array mode, online help is invoked in
Severity: Medium • Use Internet Explorer or
the Unisphere online help Chrome, the browser
Tracking: 635311 Firefox to open Unisphere
will not load if Chrome is set displays a blank page
• Prior to accessing
as the default browser.
Unisphere, open Chrome
with the following
command: <Chrome-
path>" --allow-file-access-
from-files
Exists in versions:
1.3.6.1.0096
1.3.8.1.0119
Unisphere Platforms: All It can take multiple When a user launches Increase the amount of RAM
attempts to access the Unisphere, the applet may in the computer running
Control Station. hang. The user has to try Unisphere and disable on-
Severity: Low
multiple times before access scanning of anti-virus
launching Unisphere applications when launching
Tracking: 551081 successfully. Unisphere for the first time.
Exists in versions:
All 1.3 versions.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
75
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All With PowerPath installed, The host could not be found There are two workarounds
the user wants to when the user wants to for this issue:
disconnect the storage disconnect the storage 1) Set the DWORD registry
group from the host, but the group from the host. value AutoHostRegistration
Severity: Medium host cannot be found. located under
HKLM\System\CurrentControl
Set\Control\EmcPowerPath
Tracking: 641746 registry key to 0. Then, reboot
the host.
2) Uninstall PowerPath.
Then, install PowerPath using
the <Setup.exe>
/v"AUTO_HOST_REGISTRATIO
N=0" option.
Exists in version:
1.3.3.1.0072-1
1.3.6.1.0096
1.3.8.1.0119
Unisphere Platforms: All The Storage Capacity There is more free space The displayed free capacity
displayed in the Dashboard than what is displayed. of storage pool accounts for
section shows File free the File side only.
capacity as smaller than the The File free capacity
Severity: Medium Free capacity displayed on displayed on Dashboard is
Storage Pool table. from the point view of the
whole system including File
Tracking: 652886 and Block.
Exists in version:
1.3.3.1.0072-1
1.3.6.1.0096
Unisphere Platforms: All After BBU B is removed from Only the first line of the error Use naviseccli account to
the enclosure, navi faults - is reported, "Bus 0 Enclosure login <SP IP>/debug, click the
list fails to report the 0: Faulted". The complete Force A Full Poll.
message "Bus 0 Enclosure 0 message is not reported. Exists in version:
Severity: Medium BBU B: Removed, as 1.3.3.1.0072-1
expected. only reports the
first line of the error "Bus 0 1.3.6.1.0096
Enclosure 0: Faulted". It 1.3.8.1.0119
Tracking: 651009
does not report the
complete message.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
76
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All When a VNX system is Workaround: change the

assigned a hostname VNX system hostname so
Severity: Critical composed strictly of that the hostname contains
numeric characters, the one or more non-numeric
Frequency: system will not start and characters.
users cannot access the Exists in versions:
Always under a system through Unisphere. 1.3.1.1.0033
specific set of
1.3.2.1.0051
cirumstances
1.3.3.1.0072-1
Tracking: 611766 1.3.6.1.0096
1.3.8.1.0119
Unisphere Platforms: All When creating a storage Since I/O is running, the Try to create storage pool
pool of "MAX" size while I/O amount of available space again, or select a specific
Severity: Critical is running to other LUNs in can change from the time size for the storage pool.
that pool, Unisphere can the request to create the
Frequency: Exists in versions:
return error that states that pool is initiated until the
Occasionally the requested LUN size is time it is processed by the 1.3.2.1.0051
too large. system. 1.3.3.1.0072-1
Tracking: 616169 1.3.8.1.0119
Unisphere Platforms: All When managing background Users must have admin Ensure that anyone who
tasks in Unisphere, the privileges to abort or delete wants to delete or abort a
Severity: Critical Abort and Delete buttons background tasks. background task has admin
appear disabled in the privileges in Unisphere.
Frequency: Background Tasks tab.
Occasionally Exists in versions:
1.3.2.1.0051
Tracking: 612365 1.3.3.1.0072-1
1.3.6.1.0096
1.3.8.1.0119
Unisphere Platforms: All Clicking the Unisphere When selecting the To access the Symmetrix
Symmetrix LUN View button Unisphere Symmetrix LUN LUN view:
Severity: Medium for a VNX Gateway does not View button for a VNX 1. Open the Dashboard
open the Symmetrix LUN Gateway (located under page from Unisphere
Frequency: view. Storage > Storage Storage > Storage
Occasionally Configuration > File Systems page.
Systems), the following This launches the
Tracking: 615316 message appears: Unisphere for VMAX
Register the Unisphere dashboard
VMAX credentials 2. Select
INTEGRATED_NAS_IG
from Initiator group in
the Initiator section on
Unisphere for VMAX
dashboard.
Exists in versions:
1.3.2.1.0051
1.3.3.1.0072-1
1.3.6.1.0096
1.3.8.1.0119

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
77
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All When configuring user To register user credentials Mouse over the Edit and
privileges to launch the for launching the Unisphere Configuration buttons to
Severity: Low VMAX UI from Unisphere, VMAX view from a Unisphere enable these buttons and
configuration controls VNX gateway, make the associated
Frequency: occasionally appear administrators click Register functionality accessible.
Occasionally disabled. for Unisphere VMAX to open
Exists in versions:
a credentials configuration
Tracking: 615749 page. 1.3.2.1.0051
Occasionally the Edit and 1.3.3.1.0072-1
Configuration buttons in the 1.3.6.1.0096
credentials page appear 1.3.8.1.0119
disabled in this page.
Unisphere Platforms: All More LUNs cannot be In the Storage > LUNs table, In the case where pool LUNs
created in the Storage > more LUNs cannot be reach the limit, but RAID
Severity: Low LUNs table by clicking created by clicking Create group LUNs do not, create
Create when either the pool when either the pool LUNs RAID group LUNs in Storage >
Tracking: 574138 LUNs or RAID group LUNs or RAID group LUNs reach Storage Pools > RAID Groups.
have reached the limit. the limit. A popup warning In the case where RAID group
message appears and then LUNs reach the limit, but pool
the create LUN dialog LUNs do not, create pool
closes. LUNs in Storage > Storage
Pools > Pools.
Exists in versions:
All 1.3 versions.
Unisphere Platforms: All After issuing the getlog If there are many log entries There are two steps to this
command where there are in the event log, the getlog workaround:
Severity: Low many event log command may output a lot 1. Ensure the network
entries,CIMOM may restart of information, which can bandwidth between the
Tracking: 488940 and thus stop service take a long time. If getlog host which issued the
temporarily. command takes over half an getlog command and the
hour, a dump will be target array is found.
generated, and CIMOM will 2. Redirect the command
stop service for about two output to a file instead of
minutes due to CIMOM's outputting to the screen.
restarting. For example: naviseccli
-h xx.xx.xx.x getlog >
naviloginfo.txt

Exists in versions:
All 1.3 versions.
Unisphere Platforms: All LUN compression fails if the If the system is configured Delete another LUN, then
system is configured with with maximum LUNs, compress the target LUN.
Severity: Low the maximum number of enabling the LUN
LUNs. compression will fail. Exists in versions:
Tracking: 490729 All 1.3 versions.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
78
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All Error when pinging/tracing The following error message Do not ping/trace route SP
the route SP management IP will display when management IP from an iSCSI
Severity: Medium from an iSCSI data port pinging/tracing the route SP data port; it is not
inUnisphereI. management IP from an recommended.
Tracking: 522202 iSCSI data port in Unisphere
UI: Exists in versions:
Ping/traceroute to peer SP or All 1.3 versions.
management workstation from iSCSI
port disrupts management
communication and is not permitted.
Unisphere Platforms: All Host appears registered After attaching a cloned To create a host from a
with unexpected host to array, the host might cloned image, do not include
Severity: Medium information and may be be registered with a Host Agent in the image. Or
unavailable. unexpected information, alternatively, before attaching
Tracking: 559676 such as Host IP, host ID or the new host to array,
host name. This may be uninstall Host Agent with all
inherited from the image the configuration information
that was used to create the removed and install a new
host. Without the right host Host Agent from scratch.
information, the new host Refer to Knowledgebase
might be unavailable on the articles emc66921, and
array. emc63749 for details about
how to clean up the Host
Agent inherited from the
image.
Exists in versions:
All 1.3 versions.
Unisphere Platforms: All After a bus cable is moved If a bus cable is moved from This is a display issue only.
from one port to another, one port to another, there Restart the management
Severity: Medium faults may be seen on both will be faults from both the server from the setup page or
the original bus and the new original bus and the new reboot the SP.
Tracking: 563384 bus. bus.This will remain even
after moving the bus cable Exists in versions:
back to the first port. All 1.3 versions.
Unisphere Platforms: All A faulted LUN does not A faulted LUN will not be No workaround.
display in the output of the shown in the faults -list
faults –list command output unless it is Exists in versions:
Severity: Medium
unless it is associated with associated with a system All 1.3 versions.
Tracking: 564905 a system feature. feature such as a storage
group, mirror, snap, and so
on.
Unisphere Platforms: All There are missing columns There may be missing Delete the existing
in the UI table if the columns in a UI table after persistence file
Severity: Medium language setting has been recently switching the persistence.per from
recently changed. language setting. <userHome>\emc\Unisphere
Tracking: 472986 for Unisphere, or
<userHome>\emc\USM for
Unisphere Service Manager
(USM).
Exists in versions:
All 1.3 versions.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
79
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Unisphere Platforms: All A timeout error occurs when In rare cases, binding a No workaround. LUNs are
deleting LUNs at the same large number of LUNs to a deleted successfully, despite
Severity: Low time as binding a large RAID group using Naviseccli this timeout error.
number of LUNs to a RAID at nearly the same time as
Tracking: 532907 group. deleting LUNs in the UI will Exists in versions:
result in a timeout error, All 1.3 versions.
although the LUNs are
deleted sucessfully.
Unisphere Platforms: Two Windows 2008 iSCSI When running Unisphere, Log out of Unisphere and log
hosts connected at the after two Windows 2008 in again.
Windows Server same time do not display iSCSI hosts are connected to
under Host > Host List. an array and rebooted, Exists in versions:
2008
although they are shown as All 1.3 versions.
Severity: Medium logged in and registered
under Hosts > Initiators, the
Tracking: 526482 following warning is shown
on the status column.
The initiator is not
fully connected to the
Storage System. As a
result they do not show
under Hosts > Host List.
Unisphere Platforms: All In the Unisphere UI, an When an asynchronous There are two workarounds
asynchronous mirror with a mirror only has a fractured for this issue:
Severity: Medium fractured secondary image secondary image but no 1. Select the asynchronous
and no primary image primary image, the mirror and click
Tracking: 567075 cannot be deleted. secondary image cannot be properties to open the
deleted from the Unisphere Remote Mirror Properties
UI. After selecting the dialog. Go to the
secondary image and Secondary Image tab and
clicking on the Delete click Force Delete to force-
button, nothing will happen destroy this secondary
and there will be no failure image.
message.
2. Use the CLI to destroy this
secondary image by using
the -force switch.
Exists in versions:
All 1.3 versions.
Snapview Platform: All Activating a snap session on If an attempt is made to The session should be
snapshots a snapshot with an open activate a snap session on a activated on an unused
Severity: Low activated session may fail snapshot which already has snapshot.
without an error indication. an activated session, the
Frequency: Always operation will fail but no Exists in versions:
under specific error will be returned. All 5.33 versions.
circumstances

Tracking: 539292

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
80
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Snapview Platforms: All Unisphere command will fail Navisphere CLI and Reissue the protected restore
clones during a single SP reboot. Unisphere Manager return operation after both SPs have
Severity: Low an error message when completed booting.
starting a protected restore.
Frequency: Rarely If a clone’s protected restore Exists in versions:
under specific operation is initiated while All 5.33 versions.
circumstances one of the storage
processors is booting, the
Tracking: 294717 SP that owns the clone
source may not be able to
communicate with the peer
SP for a short period of time.
Snapview Platforms: All Synchronizing and reverse- SnapView clones will restart Fracture the clone after the SP
clones sychronizing will be started synchronizing/reverse recovers from the failure.
Severity: Low in automatic mode when synchronizing an
running with a single SP. unfractured clone after an Exists in versions:
Frequency: Always SP failure even if the All 5.33 versions.
under a rare set of recovery policy is set to
circumstances manual. This behavior
occurs only if the system is
Tracking: running with a single SP, or
247637, 248149, when the clone source is
251731 also a MirrorView
secondary.
SnapCLI Platforms: SnapCLI fails when the VNX Snapshots containing Dynamic disks must be
Windows operation is targeted for a a dynamic disk, which is imported using the Disk
dynamic disk. rolled back to the Administrator or the
Severity: Low production host, cannot be Microsoft Diskpart utility.
imported on the production
Frequency: Always host using SnapCLI. Exists in versions:
3.32.0.0.5 and previous
Tracking: 286529

SANCopy for Platforms: All SAN Copy does not verify When you use SAN Copy When you modify a copy
Block the selected LUN size when with Navisphere CLI, you are descriptor with Navisphere
Severity: Low the size of the LUN source able to change the source CLI, ensure any destination
changes. LUN to be incorrectly larger LUNs are always the same
Frequency: Always than the destination LUNs. size or larger than the source
The SAN Copy session LUN.
Tracking: 184420 eventually fails because the
destination LUNs are too Exists in versions:
small. SAN Copy does not All 5.33 versions.
verify that the selected LUN
size is valid.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
81
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

SANCopy for Platforms: All A SAN Copy modify If the only destination of a Modify the copy session to a
Block command fails if the only SAN Copy session fails and full session and then back to
Severity: Low destination of a SAN Copy this session is modified to an incremental session. Once
session fails. replace it with a new the modify is successful, add
Frequency: Always. destination, the modify your new destination to the
fails. This issue happens session. Once the addition of
Tracking: 215061 because the modify the destination is successful,
command checks for the remove the previously failed
new destination before session.
checking that the failed
destination is removed in Exists in versions:
the modified session. The All 5.33 versions.
modify fails as it thinks a
failed destination exists.
SANCopy for Platforms: All Remote devices in the SAN If SAN Copy sessions start Schedule the SAN Copy
Block Copy session may fail if between two storage sessions on both storage
Severity: Medium iSCSI ports are used as a systems connected over systems so that they do not
combination of initiator iSCSI and both storage run at the same time.
Frequency: Rarely, ports and target ports. systems act as SAN Copy Or configure the iSCSI
under specific systems for some SAN Copy connections between the
circumstances sessions and remote storage systems so that iSCSI
systems for other SAN Copy ports used for SAN Copy in
Tracking: 311047 sessions, remote devices in the I/O module are all used
the SAN Copy session may either as initiator ports or
fail with error: target ports but not in
Unable to locate the device. Check combination.
that the device with this WWN
exists. Exists in versions:
All 5.33 versions.
SANCopy for Platforms: All Start Time and Completion Session display on Start After starting the session, the
Block Time of session may be Time and Completion Time inconsistency is non-existent.
Severity: Low inconsistent on both SPs. may be inconsistent on both
SPs after adding a Exists in versions:
Frequency: Rarely, destination to Incremental All 5.33 versions.
under specific session.
circumstances

Tracking: 350153

SANCopy for Platforms: All If you change the max The max concurrent SAN New setting takes effect after
Block concurrent setting, and Copy setting does not take existing active sessions stop.
Severity: Low there are more active effect immediately when
sessions than the new there are already more Exists in versions:
Frequency: Under setting allows, the new active sessions than new All 5.33 versions.
specific setting does not take effect setting.
circumstances immediately.
Tracking: 475390

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
82
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

MirrorView Platforms: All MirrorView/S If a mirror is destroyed while Avoid destroying a mirror
Synch Storage processor can a trespass occurs, it is when a trespass is likely,
Severity: Medium reboot unexpectedly when a possible for internal data such as just after a storage
mirror is destroyed. structures to become processor boots, when hosts
Frequency: Rarely inconsistent and result in a with failover software may
under specific storage processor reboot. attempt to rebalance the
circumstances load.
Tracking: 237638 Exists in versions:
All 5.33 versions.

MirrorView Platforms: All MirrorView/A An uncleared deadlock When you promote a large
Asynch An attempt to promote a prevention flag (error group, reduce other loads on
Severity: Medium large consistency group 0x7152807) may prevent the storage system where
when the storage systems further promote or possible. If this issue is
Frequency: Likely are connected by iSCSI can administrator operations. found, destroy and recreate
under specific fail. This issue can occur during the affected group.
circumstances heavy I/O traffic and/or An SP restart of the primary
other mirror updates. and/or secondary storage
Tracking: 329924
system clears the deadlock
prevention flag.
Exists in versions:
All 5.33 versions.
MirrorView Platforms: All MirrorView/A Internal data structures can Issue a synchronize
Asynch Mirrors may become inconsistent, which command for the mirror. If
Severity: Low administratively fracture results in the mirrors being this fails the first time, retry
unexpectedly. administratively fractured. the command.
Frequency: Rarely
under specific Exists in versions:
circumstances All 5.33 versions.

Tracking: 333132

MirrorView Platforms: All MirrorView/A If a multi-LUN consistent Issue a synchronize

Asynch Mirrors may become (MLC) SnapView session command for the mirror. If
Severity: Low administratively fractured starts, a mirror may fracture this fails the first time, retry
unexpectedly. unexpectedly. the command.
Frequency: Likely
under specific Exists in versions:
circumstances All 5.33 versions.

Tracking: 335576

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
83
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

MirrorView Platforms: All MirrorView/S When Secure CLI processes Retry the mirror create
Asynch Secure CLI may time out a large number of system operation.
Severity: Low during a mirror creation actions, it may return the
following error: Exists in versions:
operation.
Frequency: Rarely Request failed. The force polling All 5.33 versions.
under specific failed, because of timeout - the
circumstances system may be busy, please try
again. (334575)
Tracking: 334575

MirrorView Platforms: All MirrorView/S If one storage processor Reissue the synchronize
Asynch A mirror may fracture shuts down at the same command.
Severity: Low unexpectedly. time the other storage
processor sends a Exists in versions:
Frequency: Rarely synchronize command, the All 5.33 versions.
under specific mirror may fracture.
circumstances

Tracking: 389452

Data at Rest Platforms: VNX Removing hardware If a drive or SP replacement If the VNX chassis and both
Encryption Severity: Medium improperly can cause data is required on a D@RE- Storage Processors (SPs)
to become inaccessible. enabled array, the standard need to be replaced - do not
Tracking: 700786
VNX2 replacement replace both SPs
procedure can be used. simultaneously. Instead,
If a 6Gb SAS UltraFlex I/O retain one SP until the array is
Module needs to be added back online before replacing
or replaced, the standard the second SP. Alternatively,
VNX2 procedure can be if the hardware was already
used. replaced, you can restore the
keystore from a backup with
the assistance of EMC
Support.
Exists in versions:
05.33.006.5.096
05.33.008.5.119
Admsnap Platforms: All An admsnap command may The admsnap command The actual state of the
incorrectly report a failure, may report a failure but the operation can be verified by
Severity: Low but the command succeeds operation succeeds if the using Navisphere®
if the target LUN is target LUN of the operation /Unisphere® software.
Frequency: Rarely trespassed during the is trespassed during the
under specific operation. admsnap operation. Exists in versions:
circumstances 2.32.0.0.5 and previous

Tracking: 286532

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
84
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Admsnap Platforms: AIX Admsnap activate The messages are generated To prevent these messages
commands executed in an because a deactivated from beign generated,
Severity: Low AIX PowerPath® snapshot is present in the activate the snapshot using
environment may generate storage group. Whenever Secure CLI, which will allow
Frequency: Likely SC_DISK_ERR2 messages in snapshots are in the storage execution of admsnap on the
under specific the system log file. group, running cfgmgr host.
circumstances causes ASC 2051 problems
in the errpt file. The Exists in versions:
Tracking: 215474 messages are harmless and 2.32.0.0.5 and previous
can be ignored.
Admsnap Platforms: Linux Admsnap sessions are not Admsnap cannot access The Linux kernel creates only
activated on a Linux system more than eight device eight SG devices (SCSI
Severity: Medium if more than eight device paths on the backup host. generic devices) by default.
paths are required to Additional SG devices must
Frequency: Always complete the operation. be created and then linked to
under specific the SD devices. (The internal
circumstances disk uses one of the SG
devices).
Tracking: 286533
Use the Linux utility
/dev/MAKEDEV to create
additional SCSI generic
devices.
Exists in versions:
2.32.0.0.6 and previous
Admsnap Platforms: Windows Admsnap fails when the An admsnap session Dynamic disks must be
operation is targeted for a containing a dynamic disk imported using the Disk
Severity: Low dynamic disk. that is rolled back to the Administrator or the Microsoft
production host cannot be Diskpart utility.
Frequency: Always imported on the production
host using admsnap. Exists in versions:
Tracking: 286529 2.32.0.0.5 and previous

Admsnap Platforms: Windows The admsnap start The admsnap start Trespass the volume to the
command fails if the volume command fails with Error: primary path or use
Severity: Low contains a Veritas volume 0x3E050011 (One or more Navisphere Secure CLI to start
and the LUNs for that devices need manual attention the SnapView session.
Frequency: Always volume are trespassed to by the operator),if the volume
the secondary path. contains a Veritas volume Exists in versions:
Tracking: 206345 and the LUNs for that 2.32.0.0.5 and previous
volume are trespassed to
the secondary path.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
85
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Admsnap Platform: Windows The admsnap activate The admsnap activate This usually occurs when the
command may inaccurately command generates a registry contains stale device
Severity: Low return a warning if the warning that one or more mapping information. Update
operating system maintains devices was not assigned a the registry by using a utility
Frequency: Always a drive letter mapping for drive letter when all from Microsoft called
under specific the volume being brought volumes were assigned “scrubber” to remove stale
circumstances. online. drive letters. entries. The stale device
mapping information
Tracking: 225937 generates a condition that
prevents admsnap from
determining if all volumes
activated were assigned drive
letters. Admsnap generates a
warning.
Exists in versions:
2.32.0.0.5 and previous
Admsnap Platform: Windows The admsnap command The admsnap command To resolve this issue,
fails to start or stop a fails to start or stop a trespass the volume to the
Severity: Low session in a DMP session in a DMP peer storage processor and
environment. environment. reissue the admsnap
Frequency: Always The failure is due to the command.
under specific trespassing of the LUN that
circumstances. Exists in versions:
is the target of admsnap
operation. The DMP/Volume 2.32.0.0.5 and previous
Tracking: 226043
Manager keeps track of the
current storage processor
owner, independently from
the operating system.
Admsnap Platform: Windows The admsnap list The admsnap list Use the –d option on the
command may list devices command may list devices command line to suppress
Severity: Low multiple times when multiple times when duplicate entries for a
executed in a DMP executed in a DMP particular device or volume.
Frequency: Always environment. environment.
under specific Exists in versions:
circumstances. 2.32.0.0.5 and previous

Tracking: 225832

Admsnap Platform: Solaris The admsnap activate The admsnap activate Use the –o <device> option for
command causes LUNs to command (when issued the admsnap activate
Severity: Low trespass on the host in a without the –o <device> command.
DMP environment. parameters) scans the SCSI
Frequency: Always. bus using the primary and Exists in versions:
secondary paths for the 2.32.0.0.5 and previous
Tracking: 207655 devices, causing the LUNs
to trespass.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
86
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Known problems and limitations

Category Details Description Symptom Workaround/Version

Admsnap Platform: SuSE Warning messges are The package fails to Use the yast2 command on
generated during the complete the operation SuSE Linux systems to install
Severity: Low installation or removal (installation or removal) or remove the admsnap
process if Admsnap is without generating warning package.
Frequency: Always installed or uninstalled messages.
under specific when rpm is used on SuSE Exists in versions:
circumstances. systems. 2.32.0.0.6 and previous

Tracking: 230902

Admsnap Platforms: All A snapcli command may A snapcli command may The actual state of the
report a failure, but the report a failure, but the operation can be verified
Severity: Low command succeeds if the command succeeds if the using Unisphere® software.
target LUN is trespassed target LUN was trespassed
Frequency: Rarely during the operation. during the operation. Exists in versions:
under specific 3.32.0.0.5 and previous
circumstances

Tracking: 286532

Admsnap Platforms: AIX The snapcli attach The error messages are Activate the VNX snapshots
command executed in an generated due to a mount point using
Severity: Low AIX PowerPath® presence of a detached Navisphere Secure CLI. Then
environment can generate VNX snapshots mount execute SnapCLI on the host
Frequency: SC_DISK_ERR2 messages point in the storage group. to prevent these messages
in the system log file. Whenever VNX snapshots from being generated.
Likely under mount points are in the
specific storage group, running Exists in versions:
circumstances cfgmgr causes ASC 2051 3.32.0.0.5 and previous
Tracking: 215474 problems in the errpt file.
The messages are
harmless and can be
ignored.
Admsnap Platforms: Linux VNX snapshots are not SnapCLI cannot access The Linux kernel creates only
attached on a Linux system more than eight device eight SG devices (SCSI
Severity: Medium if more than eight device paths on the backup host. generic devices) by default.
paths are required to Additional SG devices must
Frequency: complete the operation. be created and then linked
to the SD devices. (The
Always under internal disk uses one of the
specific SG devices).
circumstances
Use the Linux utility
Tracking: 286533 /dev/MAKEDEV to create
additional SCSI generic
devices.
Exists in versions:
3.32.0.0.6 and previous

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
87
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Known problems and limitations

Category Details Description Symptom Workaround/Version

Admsnap Platforms: The snapcli create The snapcli create Trespass the volume to the
Windows command fails if the command fails with the primary path or use
volume contains a Veritas following error message if Navisphere Secure CLI to
Severity: Low volume and the LUNs for the volume contains a create the VNX Snapshot.
that volume are trespassed Veritas volume and the
Frequency: Always to the secondary path. LUNs for that volume are Exists in versions:
trespassed to the 3.32.0.0.5 and previous
Tracking: 206345 secondary path:
Error: 0x3E050011 (One or
more devices need manual
attention by the operator).
Admsnap Platforms: The snapcli attach The snapcli attach This usually occurs when the
Windows command might return a command generates a registry contains stale
warning if the operating warning that one or more device mapping information.
Severity: Low system maintains a drive devices are not assigned Update the registry by using
letter mapping for the drive letters, when the the “scrubber” utility from
Frequency: Always volume being brought other volumes are Microsoft to remove stale
under specific online. assigned drive letters. entries. The stale device
circumstances. mapping information
generates a condition that
Tracking: 225937 prevents SnapCLI from
determining if all volumes
attached were assigned
drive letters. SnapCLI
generates a warning.
Exists in versions:
3.32.0.0.5 and previous
Admsnap Platforms: SnapCLI fails to create or SnapCLI fails to create or The LUN trespassing that is
Windows destroy a VNX Snapshot in destroy a VNX Snapshot in the target of the Snap CLI
a DMP environment. a DMP environment. causes failure. The
Severity: Low DMP/Volume Manager
keeps track of the current
Frequency: Always storage processor owner
under specific independently from the
circumstances operating system. To resolve
this issue, trespass the
Tracking: 226043 volume to the peer storage
processor and use the
snapcli command.
Exists in versions:
3.32.0.0.5 and previous

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
88
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Documentation

Category Details Description Symptom Workaround/Version

Admsnap Platforms: The snapcli list The snapcli list Use the –d option on the
Windows command might list command might list command line to suppress
devices multiple times devices multiple times duplicate entries for a
Severity: Low when executed in a DMP when executed in a DMP particular device or volume.
environment. environment.
Frequency: Always Exists in versions:
under specific 3.32.0.0.5 and previous
circumstances

Tracking: 225832

Admsnap Platforms: Solaris The snapcli attach The snapcli attach Use the –o <device> option
command causes LUNs to command (when issued for the snapcli attach
Severity: Low trespass on the host in a without the –o <device> command.
DMP environment. parameters) scans the SCSI
Frequency: Always. bus using the primary and Exists in versions:
secondary paths for the 3.32.0.0.5 and previous
Tracking: 207655 devices, causing the LUNs
to trespass.
Admsnap Platforms: SuSE If “rpm” is used on SuSE The package fails to Use the yast2 command on
systems during the complete the operation SuSE Linux systems to
Severity: Low installation or removal (installation or removal) or install or remove the
process, warning messages warning messages are SnapCLI package.
Frequency: Always are generated or there are generated.
under specific problems in installing or Exists in versions:
circumstances uninstalling SnapCLI. 3.32.0.0.6 and previous

Tracking: 230902

Admhost Platforms: Admhost does not support Admhost operations fail if The workaround is to import
Windows Dynamic Drives. you attempt them on a Dynamic Drives using the
Windows Dynamic Drive. Disk Administrator or the
Microsoft Diskpart utility.
Severity: Medium
Exists in versions:
Frequency: Always 1.32.0.0.5 and previous
Tracking: 203400

Documentation
EMC provides the ability to create step-by-step planning, installation, and maintenance
instructions tailored to your environment. To create VNX customized documentation, go to:
https://mydocuments.emc.com/VNX.
For the most up-to-date documentation and help go to EMC Online Support at
https://Support.EMC.com.

Configuring VNX Naming Sevices

This manual refers to iPlanet support rather than support for Oracle Directory Server
Enterprise Edition (ODSEE) in VNX . ODSEE is the new version formerly known as iPlanet or
Sun Java System Directory Server and Sun ONE Directory Server . Version 11.x is supported in

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
89
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
Documentation

by VNX. This manual will be updated in a subsequent release.

Using VNX Replicator

Please note the following for the manual, Using VNX Replicator (P/N 300-014-567 Rev 01):
The syntax for the Snapsure configuration has changed to: ckpt:10:200:20
When changing the Snapsure configuration, the updated process is as follows:
1. Locate this SnapSure configuration line in the file:
ckpt:10:200:20, where:
10 = Control Station polling interval rate in seconds
200 = maximum rate at which a file system is written in mb/second
20 = percentage of the entire system’s volume allotted to the creation and extension
of all the SavVols used by the VNX system.
Note: If this line does not exist, it means the SavVol-space-allotment parameter is currently
set to its default value of 20, which means 20 percent of the system space can be used for
SavVols. To change this setting, you must first add the line: ckpt:10:200:20.

EMC VNX Operating Environment for Block 05.33.008.5.119 EMC VNX Operating
90
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes
 Where to get help

Where to get help

EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or for information about EMC products,
licensing, and service, go to EMC Online Support (registration required) at:
http://Support.EMC.com.
Troubleshooting
Go to EMC Online Support. After logging in, locate the appropriate Support by Product page.
Technical support
For technical support and service requests, go to EMC Online Support. After logging in, locate
the appropriate Support by Product page and choose either Join Live Chat or Create Service
Request. To open a service request through EMC Online Support, you must have a valid
support agreement. Contact your EMC Sales Representative for details about obtaining a
valid support agreement or to answer any questions about your account.

Copyright © 2015 EMC Corporation. All Rights Reserved. Published in the USA.
Published August 2015
EMC believes the information in this publication is accurate as of its publication date. The information is subject to
change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and
other countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories
section on the EMC online support website.

EMC VNX Operating Environment for Block 05.33.008.5.119, EMC VNX Operating
91
Environment for File 8.1.8.119, EMC Unisphere 1.3.8.1.0119 Release Notes