docu53275 vnx operating environment for block 05.33.000.5.52 release notes

1

EMC® VNX® VNX Operating Environment for Block 05.33.000.5.52

Release Notes P/N 302-000-403

REV 07 April, 2014

The software described in this document is intended for the VNX5200, VN5400, VNX5600, VNX5800, VNX7600, and VNX8000 (VNX2) platforms

Topics in this document include:

Revision history ......................................................................................... 2 Software media, organization, and files ................................................. 3 Fixed problems ........................................................................................... 4

VNX Operating Environment for Block 05.33.000.5.52 ................. 4 Fixed in previous releases ......................................................................... 4 Known problems and limitations .......................................................... 12

VNX OE for Block related ................................................................ 12 VNX OE for File related ................................................................... 27 Unisphere related ............................................................................. 36 Virtual Provisioning ......................................................................... 49 FAST CACHE and FAST VP ........................................................... 53 EMC SnapView related .................................................................... 53 EMC SANCopy for VNX OE for Block .......................................... 58 EMC MirrorView™/Asynchronous and

MirrorView™/Synchronous for VNX OE for Block related 61 EMC Serviceability related .............................................................. 63 EMC Snapshots related .................................................................... 65 Virtualization .................................................................................... 69

Documentation ......................................................................................... 71 Security Configuration Guide for VNX ......................................... 71

Where to get help ..................................................................................... 71

2

Revision history

EMC VNX Operating Environment for Block 05.33.000.5.52 Release Notes

Revision history

Revision Date Description

07 April, 2014 Updated document for Block OE version 05.33.000.5.52 with changes pertinent to issue 632514.

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)

These release notes contain supplemental information about the following VNX features:

EMC VNX Operating Environment (OE) for Block, Block Compression, and Block Deduplication

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

3

Software media, organization, and files


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 05.33.000.5.52 software is available in the respective VNX for Block upgrade bundles.

To upgrade to the VNX OE for Block version 05.33.000.52, use the wizards in the System Software section of the Unisphere Service Manager. For the latest version of USM, go to EMC Online Support at http://Support.EMC.com/ and navigate to Support by Product > VNX Series > Downloads.

4

Fixed problems


Fixed problems

VNX Operating Environment for Block 05.33.000.5.52

Block Deduplication

Details Symptom Fix Version Info

Platforms: All

Severity: Critical

Frequency: Likely under a specific set of circumstances

Tracking: 632514

Using VNX Block deduplication in systems running in conjunction with VMware ESX servers or Microsoft Windows 2012 servers potentially disrupted access to deduplication enabled LUNs.

Fixed in code. Upgrading to version 05.33.000.5.052 resolves issue. See EMC Knowledge Base Article 186891.

Exists in version: 05.33.000.5.051

Fixed in version: 05.33.000.5.052

Fixed in previous releases

Category Description Tracking Fixed in version

Block Deduplication

In a system configured for large deduplication, a mismatched deduplication counter size/cast (64-bit/32-bit) can cause data loss.

605245 Block OE 05.33.000.5.038

Block Deduplication

When shrink was performed while deduplication was running and in the process of collecting data to be deduplicated, the deduplication job stuck in a loop and it did not make any progress.

577233 Block OE 05.33.000.5.034

Block Deduplication

When attempting to delete a deduplication LUN while there were some active copy requests in-progress, the deduplication LUN could get stuck in destroying state.

574723 Block OE 05.33.000.5.034

Block OE A VNX single Storage Processor (SP) reboots when a host performs a 1MB write operation to the system that is attached to a Recoverpoint Appliance (RPA) system for replication

594685 File OE 05.33.000.5.051

5



Category Description Tracking Fixed in version Block OE MirrorView Asynchronous connections are fractured

on a VNX 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

595166

File OE 05.33.000.5.051

Block OE When a drive is removed, no event is logged to indicate the 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.

593320 File OE 05.33.000.5.051

Block OE After a driver reset, an unexpected SP reboot occurs producing an alert/log message such as the following: CPD PANIC -FCOEDMQL 1 (FE5)…

593659 File OE 05.33.000.5.051

Block OE An inaccurate VNX call-home message is generated which 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

595715 File OE 05.33.000.5.051

Block OE Storage processor bugchecks (0x00000041) occurred due to excessive traffic on the management ports.

596197 File OE 05.33.000.5.051

Block OE The VNX generates warning messages (BMS found XXX entries) because the number of Background Media Scan (BMS) log entries recorded for vault drives quickly reaches defined thresholds.

597131 File OE 05.33.000.5.051

Block OE Coherency errors for RAID-1 and RAID-6 occasionally do not generate the proper XOR sector trace messages in debug operations (performed by EMC Support).

599355 File OE 05.33.000.5.051

Block OE A dial home event is generated even though no fault has occurred.

599721 File OE 05.33.000.5.051

Block OE SPA and SPB panic within minutes of each other, and their 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.

607962

Block OE 05.33.000.5.038

6




Block OE When the weekly BBU test time arrives, SPA and SPB can start 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.

601545 Block OE 05.33.000.5.038

Block OE After a reboot pool luns can go offline. The mount may fail due to an unexpected slice object state initialized from slice cache.

606436 608736

Block OE 05.33.000.5.038

Block OE When copper twinaxial cables that supported iSCSI connections were in use, iSCSI hosts experienced data unavailable (DU) after a non-disruptive upgrade (NDU) to VNX OE for Block version 05.33.000.5.034.

58805510 /599567

Block OE 05.33.000.5.035

Block OE Could not upgrade the drive firmware for Micron Buckhorn SAS drives which had a drive firmware size of over 2 MB.

573654

Block OE 05.33.000.5.034

Block OE Panic occurred while shutting system down. 574220 Block OE 05.33.000.5.034

Block OE SP B reported a panic and created a Dump file on SP B.

574235 Block OE 05.33.000.5.034

Block OE The SP Fault LED blink rates were half the expected rate during normal and degraded boot scenarios.

577670 Block OE 05.33.000.5.034

Block OE Physical power switches on the SPs were automatically turned OFF during a power down. Array did not power up after power glitch (or short term power loss).

578752

Block OE 05.33.000.5.034

Block OE Battery Backup Unit (BBU) A: Not Ready || Battery Backup Unit B: Not Ready was reported in Unisphere.

593666 Block OE 05.33.000.5.034

Block OE The BBU self test was in a cycle where the tests repeated continuously.

584042 Block OE 05.33.000.5.034

Block OE An on-array debug utility/process was inadvertently left enabled in the shipping version of the VNX OE for Block code.

504517 Block OE 05.33.000.5.034

Block OE Some disks remained in the Transitioning state for more than 1 day after being reenabled.

577106 Block OE 05.33.000.5.034

ESRS IP Client Unable to install ESRS IP Client version 1.3 when selecting proxy server connection option.

600457 Unisphere 1.3.2.1.0051

7




FAST Cache/FAST VP

In Fast Cache configurations, when a drive is removed from the 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

592310 Unisphere 1.3.2.1.0051

File OE When using Filemover (DHSM), files with a modification time earlier than 1970/01/01 could not be recalled.

53114380 /563271

File OE 8.1.1.33

File OE After changing the admin password for a CIFS client 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.

568365 File OE 8.1.2.51

File OE Windows XP (and earlier) clients cannot navigate directories created with newer clients (for example, Windows 8 or Windows 2012 server OS) that support the SMB3 protocol.

591553 File OE 8.1.2.51

File OE The Windows Event Viewer cannot open a VNX security audit log file that was previouslyopened in UNIX (NFS).

591565 File OE 8.1.2.51

File OE Unable to access CIFS shares from Windows 7/Windows 2008, 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.

592737 File OE 8.1.2.51

File OE In Windows, previous versions of deleted files cannot be 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.

593570 File OE 8.1.2.51

File OE When the VNX default server names (for example, server_2 ) are renamed (for example, to server_hr), the migrate_system_conf command generates the following error:

Error! Invalid source <movername> is provided

598131 File OE 8.1.2.51

File OE The VNX File OE reboot occurs after a failover with a message similar to the following:

GP exception. Virt ADDRESS: <addr>. Err code: 0

603272 File OE 8.1.2.51

8



Category Description Tracking Fixed in version File OE When the Windows audit auto-archive feature is

enabled for a 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

607285 File OE 8.1.2.51

File OE A VNX Data Mover (DM) exeriences a "couldn't get a free page" bug check.

602155 File OE 8.1.2.51

File OE The Data Mover experienced a "GP exception" bug check.

595437 File OE 8.1.2.51

File OE When permanently unmounting a split-log filesystem and all its checkpoints, a VNX Data Mover (DM) failover fails with the following error:

replace_ufslog: failed to complete command

52621636/ 597422

File OE 8.1.2.51

File OE When one or more Data Movers (DMs) are powered off or pulled out from the system, the nas_rdf -restore function finishes without returning an error code.

600826 File OE 8.1.2.51

File OE Windows 8 or 8.1 and W2012/R2 servers are occasionally not 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.

602082 File OE 8.1.2.51

File OE The Data Mover experienced a rolling panic when the nas_fs -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

602139 File OE 8.1.2.51

File OE Avamar backup fails, and server log is filled with alert messages.

602168 File OE 8.1.2.51

File OE NFS mounts did not complete successfully. NFS mount threads were hung. If all of the NFS mount

threads were hung the Data Mover could panic.

604117 File OE 8.1.2.51

9



Category Description Tracking Fixed in version File OE When a VNX Data Mover (DM) is associated with a

large number 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.

605740 File OE 8.1.2.51

File OE When a SavVol is unavailable at boot time, any relevant Production File Systems (PFS) are mounted, invalidating any associated checkpoints.

607082 File OE 8.1.2.51

File OE On a Data Mover (DM) with several concurrent backup sessions running for long time, it is possible for the DM to reboot.

605163 File OE 8.1.2.51

File OE/CIFS Windows Quotas View of a CIFs Share were not displayed from one VNX when the drive was mapped. The user quota information was missing (using Window MMC Quota management) when several CIFS users were mapped to the same Unix Id.

52223586 /554095

File OE 8.1.1.33

File OE/Security DART panicked while downloading a large file (more than a few GB) using SCP (secure copy over ssh).

55032486 /578783

File OE 8.1.1.33

File OE/System Management

Data Mover completely hung and was unresponsive. FileMover (DHSM) users using the partial recall policy could experience a hang if they were reading a file that was larger than 4GB.

56871206 /580075

File OE 8.1.1.33

File OE/System Management

Temporary Checkpoints flooded the Control Station. Users were unable to create their own checkpoints or file systems.

570984 File OE 8.1.1.33

Platforms A single SP panic can occur when multiple rollback processes are in simulatneously active.

583999

Block OE 05.33.000.5.051

Serviceability The USM registration wizard sometimes fails with the error:

The version of management software installed on the storage system does not suport the storage system registration ….

595816 Unisphere 1.3.1.1.0051

Serviceability USM application stops when at the VNX OE for File Installation Status stage of the Install Software wizard. It displays the following message: Retrieving data. Please wait ...

594553

Unisphere 1.3.1.1.0051

Serviceability/ ESRS IP Client

When uninstalling the ESRS IP Client, the ESRS IP Client would sometimes report that ConnectEMC, one of the ESRS IP Client components, could not be uninstalled.

577404 ESRS IP Client 1.3.1.1.0033

Serviceability/ USM

An unexpected error was received while running the Install DAE 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.

574069

USM 1.3.1.1.0033

10




Serviceability/ USM

Install Software wizard keept reporting Control Station reboot timeout, and waiting for the suggested 3 minutes did not solve the problem.

575966

USM 1.3.1.1.0033

Serviceability USM

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

577921 USM 1.3.1.1.0033

Snapshots Snap creation failed with the error message: “The operation cannot be performed because the LUN is ‘Preparing’. Wait for the LUN’s Current Operation to complete ‘Preparing’ and retry the operation.”

577314 Block OE 05.33.000.5.034

SnapView A single SP reboot can occur when multiple rollback processes are in simulatneously active.

583999 Block OE 05.33.000.5.051

System Management

The VNX System Management Daemon crashes with an OutOfMemoryException message recorded in the /nas/log/nas_log.al.mgmtd.crash file.

601412 File OE 8.1.2.51

Unisphere IPv6 addresses appeared in the domain list when IPv6 was configured on the CS and received any operation that involved setup_slot.

575343 Unisphere 1.3.1.1.0033

Unisphere The Unisphere SP Properties dialog box shows the speed of the 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.

593974 Unisphere 1.3.1.1.0051

Unisphere When using Unisphere version 1.3.0 to log in to a domain with a legacy Celerra system, the client reports that the Celerra system is “Not Logged in”.

598046 Unisphere 1.3.1.1.0051

Unisphere Unisphere off-array applications will not launch in Java 7 Update 45. This is caused by a known issue of Java 7 Update 45.

595857 Unisphere 1.3.1.1.0051

Unisphere When running VNX Unisphere, a Java warning appears saying that future Java versions will not work with the application

596623 Unisphere 1.3.1.1.0051

Unisphere Analyzer

When opening a Unisphere Analyzer (NAR) file obtained from a VNX system with no defined pools or LUNs the following error message is generated: An unknown error has occurred.

593280


Unisphere Analyzer

When VNX LUNs are connected to multiple hosts, searching Unisphere Analyzer (NAR) files based on a Host criteria does not show all connections.

579127


11



Category Description Tracking Fixed in version Unisphere Service Manager

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

603183 Unisphere 1.3.1.1.0051


A create LUN operation could result in an internal error if the operation happened when the peer SP was rebooting and the peer SP was also the preferred path to service IO for the LUN.

573637 Block OE 05.33.000.5.034


LUN expand failed with “Unrecognized Thin Provisioning Driver error code: 36365”. This could happen if an SP panicked when hitting a particular boundary condition during LUN shrink; the symptom was observed during a subsequent LUN expand.

575603 Block OE 05.33.000.5.034


A pool and all its LUNs went offline following an SP reboot.

576389 Block OE 05.33.000.5.034


Host IOs failed to a Pool LUN which was reporting ready after the system recovered from a dual SP reboot/panic.

576467 Block OE 05.33.000.5.034


After attempting to destroy a storage pool, the destroy operation would fail. The storagepool –list command displayed: Current Operation: Destroying Current Operation State: Failed Current Operation Status: Subroutine failure (0x4000803c)

578172 Block OE 05.33.000.5.034


A LUN shrink on a deduplication-enabled LUN failed to complete only when all the LUNs in the deduplication domain were empty (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.

578421 Block OE 05.33.000.5.034


A single SP panic occurred with BugCheck code 7E. 578490 Block OE 05.33.000.5.034


LUNs failed to come online following an SP reboot. 579050 Block OE 05.33.000.5.034

12

Known problems and limitations



VNX OE for Block related

Details Description Symptom Version info

Platforms: All

Severity: Medium

Frequency: Rarely

Tracking: 599765

A Link Control Card (LCC) or Inter Connect Module (ICM) in a VNX DAE reports either a PSU fault or Fan fault because it does not detect a replaced module (after a FRU).

The peer LCC/ICM does not have this problem. Once in this state, the fault persists.


Platforms: All

Severity: Medium

Frequency: Rarely

Tracking: 616702

When downloading firmware to drives using The Online Disk Firmware Upgrade (ODFU) process, if a drive in a RAID group is faulted during the download process it can take an extended time (up toseveral days) for the download process to fully complete. ODFU shows that it is in the ACTIVATE state for the remaining drives in the degraded RAID group.

In this case, ODFU process is not hung but is paused waiting for the RAID group rebuild to complete.

Wait for the RAID group rebuild to complete and the ODFU process will automatically resume.


13




Platforms: VNX5200, VNX5400

Severity: Medium

Frequency: Rarely

Tracking: 618635

When a VNX5200 or VNX5400 system is installed with the maximum number of I/O modules but at least one I/O module is uninitialized, occationally an alert message indicating that an uninitialized I/O module has exceeded the system limit. For example:

Bus 0 Enclosure 0 SP A I/O Module 1 : Faulted -- Devices maximum limitation exceeds…


Platforms: All

Severity: Medium

Frequency: Occasionally

Tracking: 616361

The VNX system returns the following error message:

The Virtual Provisioning feature is in a degraded state. Please contact your service provider. (0x712d8100)

The event log for either SP A or SP B includes the following error:

The Virtual Provisioning feature is in a degraded state. Please contact your service provider. 00 00 04 00 05 00 2c 00 d3 04 00 00 04 81 2d e1 04 81 2d e1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 71 2d 81 04 MLU 01/28/2014 04:03:13 N/A (712d8105)Internal information only. The driver is degraded.

Reboot SP A until it is fully initialized, and then reboot SP B. This clears the degraded mode on the MLU driver.


Platforms: All

Severity: Low

Frequency: Seldom

Tracking: 613348

After a non-disruptive upgrade (NDU), the management port for one of the VNX system’s Storage Processors (SPs) may transition to disconnected status.

In rare cases, a Broadcom driver can cause issues when bringing up VNX system SP management ports after a NDU.

Log in through the VNX system service port, then first disable and then re-enable the disconnected VNX SP management port.

If disabling and then re-anabling the SP port does not work, try rebooting the SP.

Exists in version:

05.33.000.5.051

14




Platforms: VNX5200, VNX5400, VNX5600, VNX5800, VNX7600

Severity Low

Frequency: Infrequently under a specific set of circumstances

Tracking: 612219

Scheduled Battery Backup Unit (BBU) self-tests show that a BBU is faulted, even though the component is operational.

In some cases the BBU Energy Requirements can be reset to their default maximum settings after a period of time, and the VNX system does not match these values. This can result in the BBU being reported as Faulted when there is no real issue.

Remove the faulted BBU, wait 20 seconds, and then re-insert the BBU. This causes the Energy Requirements to reset and clears the fault.

Exists in version:

05.33.000.5.051

Platforms: All

Severity: Low

Frequency: Always under a specific set of circumstances

Tracking: 612801

VNX amber iSCSI port LED appears lit whenever a cable is connected, even though no data is being transferred through the port.

VNX system iSCSI port LEDs should only appear lit when data is being actively transferred through it. Occasionally they appear lit when a cable is connected, but no data is being transferred through the port.

Exists in version:

05.33.000.5.051

Platforms: All

Severity: Low


Tracking: 613202

A software upgrade process fails and the system returns an error message indicating that the data area passed for the system call is not large enough.

The upgrade may fail because the Windows command bcdedit fails to run. In this case, the following error message appears in the c:\temp\ndu-bcdedit-log.out file: Status:Operation Failed: A check script contained in the associated package failed.Check the SP event logs on the primary SP and the package release notes (0x71518013).

Retry the upgrade process.

Exists in version:

05.33.000.5.051

15




Platforms: All

Severity: Medium


Tracking: 611558

When migrating LUNs within the same deduplication domain, deduplication savings are lower than expected is complete.

For more information, refer to KnowledgeBase article 176653.

Avoid migrating LUNs within a deduplication domain. If you need to move the current LUN to a larger one, use the LUN expansion functionality instead.

Exists in version:

05.33.000.5.051

Platforms: All

Severity: Medium


Tracking: 612574

For a VNX Storage Pool (SP), statistics are not updated after destroying LUNs associated with the SP.

Reboot the affected SP.

Exists in version:

05.33.000.5.051

Platforms: All

Severity: Minor

Frequency: Always

Tracking: 617430

The VNX Security Configuration Guide lists steps required to change the Unisphere session timeout period. These steps only apply to VNX Unified and VNX File-only systems. VNX Block-only systems do not provide a way to adjust the Unisphere timeout session period.

The timeout value for Unisphere on VNX Block-only systems cannot be changed with VNX Unisphere or the VNX for Block CLI.

Exists in versions:

05.33.000.5.051


Severity: Critical


Tracking: 58805510/599567

iSCSI ports are unitialized after an upgrade to VNX OE for block version 05.33.000.5.034 upgrade.

When copper twinaxial cables that support iSCSI connections are in use, iSCSI hosts experience data unavailable (DU) after a non-disruptive upgrade (NDU) to VNX OE for block version 05.33.000.5.034. The iSCSI hosts can no longer log in.

Replace copper twinaxial cables with optical small form-factor pluggable transceivers and cables from array ports to switch.

Exists in versions:

05.33.000.5.034

05.33.000.5.051

16




Platforms: VNX5200, VNX5400, VNX5600, VNX5800, VNX7600, VNX8000

Severity: Low


Tracking: 564282

The Dirty Cache

Pages (MB):, message displayed by the Unisphere CLI after issuing the command cache -sp -info, may be inexact.

Dirty Cache Pages

(MB): displays an estimation that could be higher than the actual value for short time periods, especially while the SP Cache is in the Disabling state.

No workaround.

Exists in versions:

05.33.000.5.015

05.33.000.5.034

05.33.000.5.035

05.33.000.5.038

05.33.000.5.051


Severity: Low

Frequency: Frequently under a specific set of circumstances

Tracking: 555603

A Background Verify operation may not complete while a RAID type 10 is initializing after a bind operation.

A Background Verify operation may not complete as expected; it is not normal to issue a Background Verify operation immediately after a bind operation.

Reissue the Background Verify operation after the initialization is complete.

Exists in versions:

05.33.000.5.015

05.33.000.5.034

05.33.000.5.035

05.33.000.5.038

05.33.000.5.051

17





Severity: Low


Tracking: 556166

An SP panic may occur during a software upgrade or installation operations.

An SP panic may occur during a software upgrade, during installation of Data Service applications or creation of the FAST Cache.

Reissue the operation that resulted in SP Failure.

Exists in versions:

05.33.000.5.015

05.33.000.5.034

05.33.000.5.035

05.33.000.5.038

05.33.000.5.051

Platforms: All

Severity: Medium

Frequency: Rarely under a rare set of circumstances

Tracking: 579903

LUNs may fail to come online after a power failure or hardware failure.

After a storage pool that went offline due to a hardware failure comes back online, some LUNs in that storage pool will stay offline. The LUN –list command will display:

Deduplication primary LUN requires recovery. Please contact your service provider.(0x712d8d3b)

Contact your service provider to bring the LUN online.

Exists in versions:

05.33.000.5.015

05.33.000.5.034

05.33.000.5.035

05.33.000.5.038

05.33.000.5.051

18




Platforms: All

Severity: Critical

Frequency: Rarely under a specific set of circumstances

Tracking: 580959

Drives that do not support Enhanced Queuing become faulted on VNX OE for Block 05.33 systems.

This problem occurs when one or more drives in a VNX array running OE for Block 05.33 have a version of firmware that does not support Enhanced Queuing. Issuing a naviseccli –h <SP IP addr> faults –

list command returns the following:

Faulted Subsystem: <array serial #> Bus <bus #> Enclosure <encl #>: Faulted Bus <bus #> Enclosure <encl #> Disk <disk #> : Removed

Issuing a naviseccli –h <SP IP addr> getlog command returns the following (event log ID) and message:

(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 the following message:

std:WARN OBJ <disk obj #> DSK:<bus #>_<encl #>_<slot #>: Drive firmware upgrade required. Enhanced queuing not supported

Contact your service provider.

Exists in versions:

05.33.000.5.015

05.33.000.5.034

05.33.000.5.035

05.33.000.5.038

05.33.000.5.051

19




Platforms: All

Severity: Critical


Tracking: 546173

Failure mode and effects analysis is improperly handling internal fault reporting for the battery backup unit.

Battery back-up unit can be faulty and require replacement, but it will not be reported as Faulted until a 16 hour timeout elapses (i.e., battery backup unit did not become BatteryReady).

No workaround.

Exists in versions: 05.33.000.5.015 05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

05.33.000.5.051

Platforms: All

Severity: Critical


Tracking: 547980

SP B in peer set-up experiences a fatal error while SP A is idle after rolling reboot.

For SPs A and B in a peer set-up, SP A was idle (performing triage activities after a rolling reboot) when SP B experiences a fatal error.

Reboot the system after manually entering the BIOS.


05.33.000.5.038

05.33.000.5.051


Severity: Medium


Tracking: 554516

On the battery back-up (BBU) unit, the marker LED does not get set for certain fault conditions.

On the backup battery unit, in certain Battery failure cases, the fault LED (located on the battery backup unit) will not assert. In most cases, the firmware will assert the LED. But if the BBU fails due to specific self-test faults, or the battery backup unit fails to charge fully after 16 hours, the fault LED will not be set.

No workaround.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

20




Platforms: All

Severity: Medium


Tracking: 558151

When a module is removed from an enclosure, approximately 3 seconds elapse before the removal detection occurs.

It takes about 3 seconds for the drive or the enclosure to be reported as removed after a drive pull or an enclosure pull. In other words, there is a 3-second delay between the time the drive is rendered out of service and the time the drive is detected as removed.

No workaround.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

Platforms: All

Severity: Low

Tracking: 561589

A Windows 2012 server may unexpectedly reboot.

Windows 2012 server reboots unexpectedly when the specified threshold of 70% is crossed on the storage pool. This event only happens with NativeWindows MPIO and when no Multi-pathing is enabled on the server.

No workaround.

Exists in versions: 05.33.000.5.015 05.33.000.5.034

05.33.000.5.035

05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

Platforms: All

Severity: Critical


Tracking: 565361

Any failure of the read for a RAID Group capacity results in an “insufficient capacity” error message, even if capacity is not the cause of the error.

When a RAID Group is in a busy state and unable to provide capacity information, a bind LUN command on that RAID Group will fail. In this case, the CLI will always display “Insufficient free space,” even if the RAID Group has adequate space. The RAID Group is busy, and the LUN bind command should be retried.

Try the LUN bind command again.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

21




Platforms: All

Severity: Medium


Tracking: 566151

Unexpected error during online disk firmware upgrade (ODFU).

When using the ODFU Wizard, if you cancel the operation after it has already started, the non-disruptive upgrade (NDU) installation that is part of the underlying implementation will continue. The Wizard confirms the cancellation even though the NDU operation is ongoing and cannot be interrupted.

If you retry the ODFU Wizard 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.

Wait until the NDU operation that is part of the ODFU Wizard's activities is actually completed before retrying the Wizard. This can be determined by running “naviseccli ndu –status” command and confirming the status is: “Status: Operation completed successfully.” If so, then retry the ODFU Wizard.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

Platforms: All

Severity: Medium


Tracking: 566542

The serial attached SCSI (SAS) status LED for Port 2 on Base Module is not ON.

When backend cables are connected to ports 0 and 1 of the Base Module, the blue link LEDs will not activate. For all other interface cards (SLICS), the LEDs correctly indicate connectivity.

No workaround.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

22




Platforms: All

Severity: Medium


Tracking: 567026

Running the naviseccli ndu –list command in engineering mode may show a default version.

When running naviseccli ndu –list in engineering mode or trying to list the hidden NDU packages installed on an array, the special LUN_2_REV and LUN_014_REV packages that indicate File OE software revisions installed on the File private LUs, can show a default revision string or a real revision string such as “8.1.xxxxx.yyyyy.” This issue can occur arise if there is substantial I/O load on the Block backend. Try running the listing again to view the actual revision. You can also check by using the Control Station using the following command: /nasmcd/bin/nas_version

Retry the NDU package engineering mode listing, especially at a time when the I/O load is lower. Or, if available, run /nasmcd/bin/nas_version on the NAS Control Station.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

Platforms: All

Severity: Medium

Frequency:

Rarely under a specific set of circumstances

Tracking: 569147

The Service Processor Enclosure (SPE) fault LED does not turn on after SPE battery removal.

This issue should be encountered only rarely. This issue occurs when both the xPE SPA battery and the DAE 0_0 SPB battery are removed. In this case, the fault LED on DAE 0_0 will assert, but the fault LED on the xPE will not. In this specific case, the fault LED should assert on the xPE because a second SPS on both the xPE and DAE allows cache to remain enabled.

No workaround.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

23




Platforms: All

Severity: Medium

Frequency:


Tracking: 568692

Online Drive Firmware Upgrade (ODFU) will wait for a degraded RAID group to become healthy before it will complete the firmware upgrade of all drives in that degraded RAID group.

This problem occurs when using USM to install firmware on drives that are in a degraded RAID group. Some drives in the degraded RAID group may be shown as ‘Non-qualified’, while other drives won’t be listed by USM and won’t be upgraded. The ODFU screen may show 100% in the progress bar, although the installation status will still show ‘In progress’

The workaround is to repair the degraded RAID group, so it is healthy again and the firmware upgrade can continue/complete, or cancel the outstanding ODFU from USM.

Exists in versions:

05.33.000.5.015

05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

24




Platforms: All

Severity: Medium

Frequency:


Tracking: 53114380/564310

Seagate drive write performance.

If a new drive is immediately bound or used as a spare before it has had a chance to finish the initial zeroing, significant performance degradation can occur with current generations of Seagate drives. This also effects drives that are unbound and rebound with new LUNs/RGs. The Seagate drives perform the write same operation used in drive zeroing as a low priority drive command that does not perform well and interferes with the performance of host IO in the LUN initialization use case. The drives will perform as much as 3-5 times better when not zeroing under heavy workloads. Normally, unbound drives (spares) perform zeroing in the background and the performance penalty will not be felt. Seagate drives that are allowed to finish this intitial zeroing do not see this penalty when bound in RGs or used as spares.

Workaround: Allow newly inserted or rebound Seagate drives to fully zero before putting them under heavy load. There is currently no easy/effective way for to determine if the drives are zeroed.

Exists in versions:

05.33.000.5.015 05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

25




Platforms: All

Severity: Medium

Frequency:


Tracking: 568692

Powerfail: SPa panicked for DLS.sys ( DLS!DLSInitialize+1396d ) in power fail test during NDU.

After an upgrade failure, an SP may time out while waiting for recovery to complete and panic the SP prematurely. After the panic, the SP will finish recovery and come up normally. The symptoms are that recovery after a failure 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.

No user action is required to recover from this failure. The timing of the locks that are used to synchronize these threads has been changed.

Exists in versions:

05.33.000.5.015

05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

Platforms: All

Severity: Medium

Frequency:


Tracking: 591576

Incorrect DC power supply current output reported.

Power consumption for the VNX 5400, 5600, 5800, 7600 systems is not reported properly. The power is reported by the naviseccli -h <IP address> environment -list -all -power This also impacts Unsphere's Storage System Properties' dialog. under the Monitoring->Environment tab.

Exists in versions:

05.33.000.5.015

05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

26



Block Compression

Details Description Symptom Solution/Workaround

Platforms: All

Severity: Low

Frequency:

Infrequently under a specific set of circumstances

Tracking: 543919

A LUN shrink operation on a LUN with compression enabled takes a long time.

Compression has internal logic to iterate many times for the shrink operation to properly clear the data.

No workaround.


05.33.000.5.038

05.33.000.5.039

05.33.000.5.051

Platforms: All

Severity: Low

Frequency:

Always under a specific set of circumstances

Tracking: 549338

A decompressing LUN cannot be destroyed.

Compression uses LUN Migrator technology for decompression and destroying a LUN under this condition is not allowed.

Enable compression on the LUN before destroying it, or wait for decompression to complete.


05.33.000.5.038

05.33.000.5.03

05.33.000.5.051

Block Deduplication

There are no known problems or limitations in this release.

27



VNX OE for File related

System Management


Platforms: All

Severity: Medium

Tracking: 608134

A diskmark (a scan of LUNS available for use in storage pools for file systems) performed on 1,500 disks or more can fail or take more than 12 hours to complete. An error such as following may be generated:

Error 5017: storage health check failed FNM00134200418 storage API db out of sync, last updated 2014/02/10-11:19:24

Instead of performing a single comprehensive diskmark of all disks (for example, by using the VNX for File nas_diskmark -m -a CLI command), perform a series of individual diskmarks on each server (for example, server_devconfig server_x -c -s –a).

Exists in versions: 8.1.2.51

Platforms: All

Severity: Low

Tracking: 532380

The following error can occur when using naviseccli.bin after a fresh installation:

./naviseccli.bin: error while loading shared libraries: libNonFipsUtilities.so: cannot open shared object file: No such file or directory

The file /usr/lib/libNonFipsUtilities.so is missing from the Control Station after an Express Install installation.

Do not use naviseccli.bin. Use naviseccli instead.

Exists in versions: 8.1.0.15 8.1.1.33 8.1.2.51

Platforms: All

Severity: Medium

Tracking: 540001

The battery properties in the inventory page do not display input power.

Users are unable to obtain detailed power information when using the GUI or CLI.

No workaround.


Platforms: All

Severity: Medium

Tracking: 541017

SECURITY: Oracle JRE/JDK Multiple Vulnerabilities (CPU-FEB-2013) - UNIX/Linux - JRE

Oracle JRE/JDK Multiple Vulnerabilities exist and may cause potential risks.

Upgrade JDK/JRE to the latest version.


28




Platforms: All

Severity: Medium

Tracking: 546410

Error 5007: server_5: /nas/sbin/repquota -u /nas/server/server_4/quotas_fs_file /nas/server/server_4/quotas_uid_file .etc/rpt_file .etc/rpt_file.sids : : exec failed

Running nas_quotas occasionally produces the following error: nas_quotas CMD 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_file /nas/server/server_4/quotas_uid_file .etc/rpt_file .etc/rpt_file.sids : : exec failed

If the error occurs, retry the operation.


Platforms: All

Severity: Critical

Tracking: 558325

During an upgrade, a thin file system failed VJTREE operations because of an out of space message

The out of space error may occur during an upgrade when the system encounters write operations on file systems. The file system auto-extension cannot complete because the NAS service is down during the upgrade.

Limit or suspend write operations during upgrades.


Platforms: All

Severity: Critical

Tracking: 563493

Failure to create a file system from a NAS pool. The following error message displays:

File system cannot be built because it would contain space from multiple mapped pools or a mix of both mapped pool and RAID group based pool.

Some LUNs were bound from a RAID group. The user ran diskmark and then created file systems on them. Some of these LUNs were moved to another thin pool via LUN compression or migration. The new file system could not be created on these LUNs and diskmark failed.

Avoid operations that lead to LUN migration when file systems are built on them. Verify that the disk type of all disk volumes under the file system are from the same mapped pool or compatible RAID group based pool(s). For file system extension, choose the matching pool that the current storage of the file system is from.


29




Platforms: All

Severity: Medium

Tracking: 564012

The following error occurred when the user renamed a mapped pool in the backend:

com.emc.cs.symmpoller.AgentException: The specified object does not exist.

The pool name on the Control Station (CS) is different from the pool name on the backend. This error results when renaming a mapped pool on the backend, but the nas_diskmark command is not run on the Control Station to synchronize the pool names.

Run the nas_diskmark -m –a command on the CS after performing any of the following operations related to the ~filestorage group:

Add/remove a LUN.

Turn on, turn off, pause, resume or modify Compression on a LUN.

Modify the Tiering Policy or Initial Tier of a LUN.

Create/destroy a mirror (both sync and async) on a LUN.


Platforms: All

Severity: Low

Tracking: 569073

SavVol auto extension does not use up all space left in the pool if the pool is smaller than 20 GB.

Currently, SnapSure SavVol auto-extend asks for a certain amount of storage (for example, 20 GB) which is calculated from storage pool properties (such as HWM). If the storage pool has less storage than that amount (such as 19GB), the 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).

Add more storage into the storage pool used by SnapSure SavVol (make sure at least 20GB is free) and the SavVol auto-extend will succeed on the next attempt.


30




Platforms: All

Severity: Low

Tracking: 573536

Storage Pools for File is empty in the GUI even though multiple pools exist.

When running nas_diskmark on a system with massive LUNs, there is a very low possibility that diskmark succeeds; the GUI does not receive data about its Storage Pool for File. The Storage Pool for File page has no change.

Press the "Rescan Storage System" or manually run nas_diskmark again.


Platforms: All

Severity: Critical

Tracking: 587501

FC port no longer functions after P2P to tape (DDR) attempted

If Fibre Channel Point-to-Point mode is attempted on a link, the Data Mover will not be able to log into devices on that link when Loop mode is retried. The Data Mover does not provide a mechanism for attempting Point-to-Point, so this can only occur if Point-to-Point mode is initiated by a connected device.

Set the link for Loop mode, and reboot the Data Mover.


Unisphere UI


Platforms: All

Severity: Medium

Tracking: 538390

Unisphere sometimes loads slowly or does not load completely.

Some Unisphere content, for example, wizard panels and the support section, may not appear. The Language Package does not take effect and the UI appears only in English.

Enable Java Cache to ensure that future load times are faster.


Platforms: All

Severity: Low

Tracking: 551081

It can take multiple attempts to access the Control Station.

When a user launches Unisphere, the applet may hang. The user has to try multiple times before launching Unisphere successfully.

Increase the amount of RAM in the computer running Unisphere and disable on-access scanning of anti-virus applications when launching Unisphere for the first time.


31




Platforms: All

Severity: Low

Tracking: 573444

After File install & VIA execution, the initial Unisphere login to a Unified system fails with a Connection Error. Subsequent login attempts succeed.

When connecting a VNX via a CS IP where the CS's certificate cannot be verified, a web browser generates a popup, “Do you wish to continue?” It also 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.

Check the checkbox "Always trust content from this publisher".


Platform


Platforms: All

Severity: Critical

Tracking: 558919

RecoverPoint File: nas_rp -failback - Error 13421904947:

Unable to communicate with Control Station on source site.

The primary system has not completely rebooted, resulting in the error.

Wait for the Primary Control Station to complete its reboot operation before running nas rp -failback.

Exists in versions: 8.1.0.15 8.1.1.33

Platforms: All

Severity: Medium

Tracking: 566413

Limitations for nas_halt

Nas_halt cannot be run from /nas or /nbsnas directory (or subdirectory). The shutdown procedure will kill all processes using these directories before the shutdown is fully complete.

Check the current working directory, and do not run nas_halt from /nas or /nbsnas (or subdirectories).


32



Replication

Details Description Symptom Solution (or workaround)

Platforms: All

Severity: Critical

Tracking: 568516

Replication switchover stops after the source Data Mover fails over.

The replication session fails; no transfer will continue although the session status shows fine. A message such as the following appears in /nas/log/sys_log.txt:

CS_PLATFORM:SVFS:ERROR:21:::::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..

Add disk space to the SavVol pool.


Platforms: All

Severity: Critical

Tracking: 586433

RPA reboot regulation and detach form cluster.

Replication replica cluster will become unstable and rpa will reboot until affected CG is expelled or Journal Volume LUN configuration is fixed.

Disable group will stabilize RP system.


CIFS

Details Description Symptom Solution (or workaround)

Platforms: All Severity: Medium Tracking: 566436

VNX CIFS server cannot be managed by Windows 2012 Server Manager.

When a VNX CIFS server is added to a Windows 2012 Server manager, the following error is displayed:

cannot manage the operating system of the target computer

Microsoft Windows 2012 Server Manager requires Microsoft Agent on the server; EMC does not support third party installation on its server. To access information on a server managed by a VNX storage system, you must use 'computer management' instead of 'server manager'.


33



ESRS (Control Station)

Details Description Symptom Solution/Workaround)

Platforms: All

Severity: Critical

Tracking: 557982

Unisphere failed to access the Control Station.

When attempting to connect to the array by using Unisphere and the ESRS Service Link, a Certificate Error may occur.

Close or terminate the existing session using the terminate button. Alternately, go to Service Link > View All > End (for all existing sessions) and start a new session.


RecoverPoint FS


Platforms: All

Severity: Critical

Tracking: 570980

The init command for Recover Point failed because an error occurred during discovering storage on source site. It reports that there is no storage API data available for the first six disks of source site.

When running the /nas/sbin/nas_rp -cabinetdr -init <cel_name>” command for Disaster Recovery site, the command fails because the following error occurs when discovering storage on source site.

Error 5008: Error discovering storage on src site.

This issue rarely occurs. Rerun "/nas/sbin/nas_rp -cabinetdr -init <cel_name> ".


34




Platforms: All

Severity: Critical

Tracking: 563551

RecoverPoint Failover Consistency Group fails in both directions

RecoverPoint Failover Consistency Group fails in both directions and the following error is displayed:

/nas/sbin/nas_rp -cabinetdr -failover" fails with error message: Error 13431865362: Consistency group error code=131073: Failed to failover consistency group name=***

Check the following preconditions before running 'nas_rp' failover to avoid failure: 1. Run verify_group

group=<CG_name> copy=<target_copy> target_image=distributing on the target RPA.

2. If Step 1 fails, run disable_image_access group=<CG_name> copy=<target_copy> on target RPA.

3. Wait until verify_group group=<CG_name> copy=<target_copy> target_image=distributing succeeds. If the journal lag size is still large, wait until it is lower than 10GB.

Workaround: 1. After ‘nas_rp’ failover

fails, wait until the DR copy state become ‘LOGGED ACCESS’. You can get estimated time from ‘estimatedTimeToPhysicalAccess’ (microsecond) in the result of ‘get_group_state -f _xml’. Do not fail back when failover fails.

2. Run disable_image_access on target copy; verify that its state becomes ‘NO ACCESS’ using ‘get_group_state -f _xml’.

3. Run ‘nas_rp’ failover again.


35



Migration

Details Description Symptom Solution/Workaround)

Platforms: All

Severity: Low

Tracking: 565259

nas_migrate -i <migration name> printed other migrations' warning messages.

Some warning messages relative to other migration sessions running on the same box could appear when information is requested on a particular session.

These messages are only warnings and will not impact the execution of the current session.


Platforms: All

Severity: Low

Tracking: 565886

Migration information does not accurately reflect the task information and percent complete on the source system.

The UI provides inaccurate progress information on migration tasks.

CLI and log files provide more accurate info.


Platforms: All

Severity: Critical

Tracking: 565968

Usermapper service was enabled on destination while it was disabled on source.

On global configuration migration, if usermapper is disabled on the source cabinet, warning is reported but manual operation is asked to the user to disable the target usermapper service.

Manually disable the usermapper service on the target.


36



Unisphere related


Platforms: All

Severity: Critical


Tracking: 606043

When changing the Recommended Ratio of Keep Unused setting from 30 to 60, insufficient disk space may be reserved for hotspares and may increase the risk of failure.

Use the VNX for Block CLI hotsparepolicy -set command to overwrite the recommended value (for example, overwriting 60 with 30) to the desired value. For example:

hotsparepolicy -set <Policy ID> -keep1unusedper 30 -o

Exists in versions: 1.3.1.1.0033 Fixed in versions: 1.3.2.1.0051

Platforms: All

Severity: Critical

Frequency:

Always under a specific set of cirumstances

Tracking: 611766

When a VNX system is assigned a hostname composed strictly of numeric characters, the system will not start and users cannot access the system through Unisphere.

Workaround: change the VNX system hostname so that the hostname contains one or more non-numeric characters. Exists in versions: 1.3.1.1.0033 1.3.2.1.0051

Platforms: All

Severity: Critical


Tracking: 616169

When creating a storage pool of "MAX" size while I/O is running to other LUNs in that pool, Unisphere can return error that states that the requested LUN size is too large.

Since I/O is running, the amount of available space can change from the time the request to create the pool is initiated until the time it is processed by the system.

Try to create storage pool again, or select a specific size for the storage pool.

Exists in versions: 1.3.2.1.0051

37




Platforms: All

Severity: Critical

Frequency: Infrequently

Tracking: 618360

When creating a storage pool, if a drive selected for inclusion in the new pool is removed while the pool is being created, the pool remains in an Initializing state.

If you run the run the following VNX for Block CLI command:

storagepool –list, the command provides the following information about the pool:

Current Operation State: Failed Current Operation Status: Bind FRU not ready

Run the following VNX for Block CLI command to delete the failed pool and then recreate the pool: storagepool -destroy -id poolid

Create the storage pool again. The removed disk will not appear as a drive that can be included in the pool.


Platforms: All

Severity: Critical


Tracking: 616360

When creating a RAID Group with automatic disk select mode, the creation process can fail with an error message indicating that the RAID Group cannot be created with the selected Drive types.

In Unisphere, manually select the disks when creating the RAID group.


Platforms: All

Severity: Critical


Tracking: 612365

When managing background tasks in Unisphere, the Abort and Delete buttons appear disabled in the Background Tasks tab.

Users must have admin privileges to abort or delete background tasks.

Ensure that anyone who wants to delete or abort a background task has admin privileges in Unisphere.


Platforms: All

Severity: Medium


Tracking: 612485

Unable to create a network device using Unisphere wizards or Unisphere management screens.

Use the VNX for File CLI to create the network device.


38




Platforms: All

Severity: Medium


Tracking: 615316

Clicking the Unisphere Symmetrix LUN View button for a VNX Gateway does not open the Symmetrix LUN view.

When selecting the Unisphere Symmetrix LUN View button for a VNX Gateway (located under Storage > Storage Configuration > File Systems), the following message appears:

Register the Unisphere VMAX credentials

To access the Symmetrix LUN view: 1. Open the Dashboard

page from Unisphere Storage > Storage Systems page. This launches the Unisphere for VMAX dashboard

2. Select INTEGRATED_NAS_IG from Initiator group in the Initiator section on Unisphere for VMAX dashboard.


Platforms: All

Severity: Low


Tracking: 615749

When configuring user privileges to launch the VMAX UI from Unisphere, configuration controls occasionally appear disabled.

To register user credentials for launching the Unisphere VMAX view from a Unisphere VNX gateway, administrators click Register for Unisphere VMAX to open a credentials configuration page. Occasionally the Edit and Configuration buttons in the credentials page appear disabled in this page.

Mouse over the Edit and Configuration buttons to enable these buttons and make the associated functionality accessible.


Platforms: All

Severity: Low

Tracking: 574138

More LUNs cannot be created in the Storage > LUNs table by clicking Create when either the pool LUNs or RAID group LUNs have reached the limit.

In the Storage > LUNs table, more LUNs cannot be created by clicking Create when either the pool LUNs or RAID group LUNs reach the limit. A popup warning message appears and then the create LUN dialog closes.

In the case where pool LUNs reach the limit, but RAID group LUNs do not, create RAID group LUNs in Storage > Storage Pools > RAID Groups. In the case where RAID group LUNs reach the limit, but pool LUNs do not, create pool LUNs in Storage > Storage Pools > Pools.


39




Platforms: All

Severity: Low

Tracking: 488940

After issuing the getlog command where there are many event log entries,CIMOM may restart and thus stop service temporarily.

If there are many log entries in the event log, the getlog command may output a lot of information, which can take a long time. If getlog command takes over half an hour, a dump will be generated, and CIMOM will stop service for about two minutes due to CIMOM's restarting.

There are two steps to this workaround:

1. Ensure the network bandwidth between the host which issued the getlog command and the target array is found.

2. Redirect the command output to a file instead of outputting to the screen. For example: naviseccli -h xx.xx.xx.x getlog > naviloginfo.txt


Platforms: All

Severity: Low

Tracking: 490729

LUN compression fails if the system is configured with the maximum number of LUNs.

if the system is configured with maximum LUNs, enabling the LUN compression will fail.

Delete another LUN, then compress the target LUN.


Platforms: All

Severity: Medium

Tracking: 522202

Error when pinging/tracing the route SP management IP from an iSCSI data port inUnisphereI.

The following error message will display when pinging/tracing the route SP management IP from an iSCSI data port in Unisphere UI: Ping/traceroute to peer SP or management workstation from iSCSI port disrupts management communication and is not permitted.

Do not ping/trace route SP management IP from an iSCSI data port; it is not recommended.


40




Platforms: All

Severity: Medium

Tracking: 559676

Host appears registered with unexpected information and may be unavailable.

After attaching a cloned host to array, the host might be registered with unexpected information, such as Host IP, host ID or host name. This may be inherited from the image that was used to create the host. Without the right host information, the new host might be unavailable on the array.

To create a host from a cloned image, do not include a Host Agent in the image. Or alternatively, before attaching the new host to array, uninstall Host Agent with all the configuration information removed and install a new Host Agent from scratch. Refer to Knowledgebase articles emc66921, and emc63749 for details about how to clean up the Host Agent inherited from the image.


41




Platforms: All

Severity: Medium

Tracking: 548376

Two hosts with the same name are displayed in the host list in the UI.

In the UI, two hosts with the same host name can be seen in the host list. In the CLI, the storagegroup -connecthost command cannot assign all the paths that belong to the same host to the target storage group.

There are two workarounds for this issue:

1. In order to connect back the logged-out paths: a. First, connect back

the down paths (those paths that are logged-out, but still registered on the array).

b. Restart the Host Agent service on the host.

2. If the down paths were removed as planned and will no longer be used, unregister the discarded down paths.


Platforms: VNX8000

Severity: Medium

Tracking: 563290

Unisphere and the CLI do not accurately display the 60-drive Disk Array Enclosure (DAE) information after replacing a 25-drive DAE with a 60-drive DAE.

The UI and CLI do not correctly display the 60-drive enclosure information when replacing a 25-drive DAE with a 60-drive DAE.The information displayed may be a mix of information from the two enclosures.

Perform a full poll.


Platforms: All

Severity: Medium

Tracking: 563384

After a bus cable is moved from one port to another, faults may be seen on both the original bus and the new bus.

If a bus cable is moved from one port to another, there will be faults from both the original bus and the new bus.This will remain even after moving the bus cable back to the first port.

This is a display issue only. Restart the management server from the setup page or reboot the SP.


Platforms: All

Severity: Medium

Tracking: 564905

A faulted LUN does not display in the output of the faults –list command unless it is associated with a system feature.

A faulted LUN will not be shown in the faults -list output unless it is associated with a system feature such as a storage group, mirror, snap, and so on.

No workaround.


42




Platforms: All

Severity: Critical

Tracking: 566078

After completing installation with VNX Installation Assistant (VIA), the system may be in an unfused state.

After completing installation with VIA, the system may be in an unfused state.This may be evident in one of several ways:

domain -list does not contain the Control Station node

Opening the UI against the Control Station IP will report a connect error

Opening the UI against the block IPs will show a Block-only screen (no File features)

The array will need to be fused manually. Refer to Knowledge base article emc264129 for more information.


Platforms: All

Severity: Medium

Tracking: 472986

There are missing columns in the UI table if the language setting has been recently changed.

There may be missing columns in a UI table after recently switching the language setting.

Delete the existing persistence file persistence.per from <userHome>\emc\Unisphere for Unisphere, or <userHome>\emc\USM for Unisphere Service Manager (USM).


Platforms: All

Severity: Medium

Tracking: 568652

Security message when closing Unisphere if using JRE 7u21 or later.

A security dialog appears when closing Unisphere under JRE 7u21 and later:

Java has discovered application components that could indicate a security concern. Contact the application vendor to ensure that it has not been tampered with. Block potentially unsafe components from being run?

with an option to choose Yes or No.

Make either selection. Unisphere will close as expected.


43




Platforms: All

Severity: Low

Tracking: 532907

A timeout error occurs when deleting LUNs at the same time as binding a large number of LUNs to a RAID group.

In rare cases, binding a large number of LUNs to a RAID group using Naviseccli at nearly the same time as deleting LUNs in the UI will result in a timeout error, although the LUNs are deleted sucessfully.

No workaround. LUNs are deleted successfully, despite this timeout error.


Platforms: All

Severity: Critical

Tracking: 561400

Creation of FAST Cache may fail if created at the same time as the storage pool.

When both the storage pool and FAST Cache are created simultaneously, FAST Cache may fail to be created.

Destroy the FAST Cache and recreate it.


Platforms:

Windows Server 2008

Severity: Medium

Tracking: 526482

Two Windows 2008 iSCSI hosts connected at the same time do not display under Host > Host List.

When running Unisphere, after two Windows 2008 iSCSI hosts are connected to an array and rebooted, although they are shown as logged in and registered under Hosts > Initiators, the 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.

Log out of Unisphere and log in again.


Platforms: All

Severity: Medium

Tracking: 563392

Unisphere may hang after connecting a newly-created LUN to the storage group when the creation of more than 100 LUNs is in process.

When the creation of over 100 LUNs is in process, after navigating to the Storage Group dialog and, successfully connecting a newly-created LUN to the storage group, Unisphere may hang after clicking OK.

Restart Unisphere.


44




Platforms: All

Severity: Medium

Tracking: 567075

In the Unisphere UI, an asynchronous mirror with a fractured secondary image and no primary image cannot be deleted.

When an asynchronous mirror only has a fractured secondary image but no primary image, the secondary image cannot be deleted from the Unisphere UI. After selecting the secondary image and clicking on the Delete button, nothing will happen and there will be no failure message.

There are two workarounds for this issue:

1. Select the asynchronous mirror and click properties to open the Remote Mirror Properties dialog. Go to the Secondary Image tab and click Force Delete to force-destroy this secondary image.

3. Use the CLI to destroy this secondary image by using the -force switch.


Platforms: VNX5800

Severity: Critical

Tracking: 574400

Unisphere hangs after attaching LUNs to a storage group on a VNX5800 with a large configuration.

When connected to a system with a large configuration (for example, with around1000 LUNs) that also has I/O running through the Unisphere UI, Unisphere may hang when attaching a LUN to a storage group. In this case, the attach LUN operation will actually succeed.

Workaround: 1. After adding the LUNs,

wait approximately 30 seconds before closing the confirmation dialog

2. Restart theUnisphere UI to proceed.


Platforms: All

Severity: Medium

Tracking: 592568

On a compression command, an unrecognized error code may be returned Output: Unrecognized Error Code: (0xe12d8110)

When running a compression command, the error, Unrecognized Error Code: (0xe12d8110), will be returned to the user if MLU is in the process of initializing the slices.

Workaround: Retrying the operation should succeed.


45



Unisphere Analyzer


Platforms: All

Severity: Critical

Tracking: 572930

Unisphere may crash when using Analyzer on a system with a large configuration (hundreds of LUNs).

For systems with large configurations, the Unisphere UI may crash if there are hundreds of LUNs.

Increase Java memory by: 1. Go the Start menu in

Windows. 2. Select Settings >

Control Panel. 3. Double-click the Java

Plugin icon. 4. Select the Advanced

tab. 5. In the Java Runtime

Parameters, type Xmx1024m.


Platforms: All

Severity: Medium

Tracking: 562742

The deduplication feature-level state of the array is inaccurate in both the UI or CLI.

The deduplication feature state of the array is inaccurate when opening the archive dump file in the 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.

No workaround


Platforms: All

Severity: Low

Tracking: 559104

Analyzer does not work when there are two open sessions for the same system.

Unisphere Real-Time Analyzer does not work when there are two sessions for the same host system.

Close both sessions and start only one Unisphere Analyzer UI session.


46




Platforms: All

Severity: Medium

Tracking: 560704

If Unisphere with Analyzer enabled and USM are running on the same host, Analyzer Real-Time statistics may fail to update.

When the Unisphere UI with Analyzer UI enabled is running and USM is later started on the same host, Analyzer real-time statistics are no longer updated.

Do not run Unisphere UI and USM on same host, or close USM and restart the Analyzer UI when this issue occurs.


Unisphere Host software, CLI, and Utilities

Details Description Symptom Solution/Workaround Platforms:

All Linux and Unix platforms

Severity: Critical

Tracking: 572417

Server Utility update command failed with error message:

NAVLInetHostNotFound: No such host...

Unisphere Server Utility serverutilcli update command fails with error message:

No such host.

Add the hostname-ipaddress mapping to /etc/hosts.


Platforms: VNX5400

Severity: Low

Tracking: 573776

Pool creation failed on a VNX5400.

When attempting to create a storage pool, the following pool status message may be received if the system LUN limits have been reached: Current Operation: Creating Current Operation State: Failed Current Operation Status: Illegal 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.

No workaround. This is expected behavior when the system limits are exceeded. The storage pool can be destroyed.


47



Details Description Symptom Solution/Workaround Platforms: Windows

Severity: Medium

Tracking: 573772

Removal of an iSNS target is reported by the Server Utility as successful when the operation was actually unsuccessful.

Although the Server Utility cannot remove an iSNS target, the iSNS target still can be selected for removal. The remove operation will then be reported as completing successfully, even though it was unsuccessful and the target is still present.

No workaround. The Server Utility cannot be used to remove an iSNS target.


Platforms:

Windows Server 2012

Severity: Low

Tracking: 521220

The virtual Fibre Channel port configured for the Hyper-V virtual machine (VM) cannot be recognized by the VM.

This is an environmental issue caused by the management operating system and the virtual machine being run on different versions of integration services. The management operating system (which runs the Hyper-V role) and virtual machines should run the same version of integration services. Otherwise, some new features of the management operating system might not be supported on the VM.

Ensure that the management operating system and virtual machine are running on the same version of integration services. For more information, refer to the following Mircrosoft articles: Version compatibility of Integration Service: http://technet.microsoft.com/en-us/library/ee207413%28v=WS.10%29.aspx How to upgrade the Integration Service: http://technet.microsoft.com/en-us/library/ee941103%28v=WS.10%29.aspx


Platforms: Linux and UNIX platforms

Severity: Critical

Tracking: 547526

Unisphere Host Agent cannot be started on an AsianUx host.

Unisphere Host Agent cannot be started on AsianUx host. An error message such as the following appears in /var/log/agent.log:

mm/dd/yyyy 16:43:56 Agent Main -- Net or File event. Err: Local hostname/address mapping unknown; see installation notes.

The hostname-ipaddress mapping should be added to /etc/hosts. Host Agent requires the hostname-ipaddress mapping for a network connection.


48



Details Description Symptom Solution/Workaround Platforms: Windows Server 2012

Severity: Low Tracking: 519934

On a Windows 2012 server, Windows STOP errors can occur when running Server Utility 1.3 or Host Agent 1.3.

On Windows Server 2012 without February 2013 cumulative updates installed, Windows STOP errors (blue or black screen errors) can occur when running Server utility or Host Agent 1.3.

Install Microsoft Windows 8 and Windows Server 2012 February 2013 cumulative updates. Refer to Microsoft Knowledgebase article 2795944 for more information:

http://support.microsoft.com/kb/2795944/EN-US


Platforms: Windows

Severity: Critical

Tracking: 537021

When configuring an iSCSI connection, the Server Utilty may fail to connect if the wrong network adapter is selected.

Server Utility may fail to connect if the server has serveral network adapters, not all of them are reachable to each other, and the wrong network adapter is selected when configuring an iSCSI connection. The failure message may also take a while to appear.

If multiple network adapters are configured on the server, EMC recommends that the default adapter is selected while using the Server Utility to create an iSCSI connection. Alternatively, ensure that the right network adapter is selected. Otherwise, the selected subnet may not be able to access the target. Make sure that the selected network adapter can access the target configured on array.


49



Details Description Symptom Solution/Workaround Platforms: VNX5400, VNX5600, VNX5800, VNX7600, VNX8000

Severity: Low


Tracking: 576807

CQECC00606857-CIMOM_PerfCounter_Exceeded.dmp.zip generated on DAE testing secondary array.

The cimom will start leaving the SP unmanaged during that time period. The cimom log will likely contain certificate errors. The issue is due to a malformed certificate which causes the certificate to be rejected.

To fix this issue: Confirm the certificates of attached hosts and fix. The issue may clear once the cimom restarts.


Unisphere QoS Manager


Platforms: All

Severity: Critical

Tracking: 562832

In rare cases, Unisphere Quality of Service Manager may lose connection to the array for two or three minutes.

In rare conditions, if the fallback policy is enabled, the Unisphere QoS Manager GUI/CLI will lose connection to the array for two or three minutes.

Disable the failback policy and reconnect to the array after three mintues.




Platforms: All

Severity: Medium

Frequency: Rarely during a rare set of circumstances

Tracking: 577722

LUN remains in a destroying state.

After attempting to destroy a LUN, the LUN remains in a destroying state. The LUN –list command returns:

Current State : Destroying (5)

Contact your service provider.

Exists in versions:

05.33.000.5.015 05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

50




Platforms: All

Severity: Medium


Tracking: 579483

LUNs may fail to come online after a power failure or after fixing the hardware failure that caused the offline condition.

After a storage pool that went offline due to a power failure or a hardware failure comes back online, some LUNs in that storage pool will stay offline. The LUN –list command returns the following:

Current State: Offline Status: Error occurred accessing the Storage Pool. Resolve any hardware problems and retry the operation. If the problem persists, please contact your service provider.(0x712d8407)


Exists in versions:

05.33.000.5.015 05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

Platforms: All

Severity: Critical

Frequency: Always under a rare set of circumstances

Tracking: 534327

After a LUN encounters an internal error during a trespass, it cannot be brought online.

A LUN can not be brought online using existing recovery procedure after it encounters an internal error during a trespass.



05.33.000.5.038

Platforms: All

Severity: Medium

Frequency: Always during a specific event

Tracking: 539153

Windows Server 2012 storage pool low space warning shows the incorrect used and available capacity of the pool.

When the storage pool low space warning threshold is crossed, the event logged on a Windows 2012 server does not show the correct used and available capacity of the pool.

This is a reporting issue with the Windows Server event log. The correct used and available capacity are displayed in the Unisphere UI.


05.33.000.5.038

51




Platforms: All

Severity:

Medium


Tracking: 542529

Some LUNs remain offline after a RAID5 double-faulted disk or RAID6 triple-faulted disk is removed and reinserted in under one minute.

A subset of LUNs in a storage pool remain offline if a RAID5 double-faulted disk or RAID6 triple-faulted disk is removed and immediately reinserted in a period of less than a minute.

Contact your service provider to bring the LUNs online.


05.33.000.5.038

Platforms: All

Severity: Medium


Tracking: 557018

Single SP panic occurs due to a CDCA (cache dirty/can’t assign) condition after dual SP reboots.

A single SP panic occurs due to a CDCA condition caused by dual SP reboots, with a pool with a large number of disks (hundreds) and where the pool storage consumption is above 70% (the default consumption threshold).

The SP will recover on its own after the panic; there is no user-visible impact or lost functionality.


05.33.000.5.038

Platforms: All

Severity: Medium

Frequency: Always during a specific event.

Tracking: 556191

In the case of single-fault disk failures, the pool LUN state is reported as ready when the LUNs are actually faulted.

On an idle array (where no IOs are running on the array), in the case of single-fault disk failures (RAID protection is still intact), the pool LUNs on the non-owning SP show as ready when they should show as faulted like the LUNs on the owning SP.

If IOs are running on the array, or even a single write is done to the LUN right after the disk fault occurred, the situation will correct itself after two minutes and both SPs will report pool LUNs as faulted.


05.33.000.5.038

52




Platforms: All

Severity: Medium


Tracking: 567511

A LUN destroy command completes succesfully, but the LUN still remains in the system.

When attempting to destroy a pool LUN while auto-tiering is running, the destroy command completes successfully and the destroy operation continues in the background, during which the relocation object will be placed in disabled state. When the Policy Engine detects the disabled relocation object, it will attempt to abort the relocation operation. If the Policy Engine's actions happen prior to completion of the destroy operation, the relocation object will enter an error state and cause the destroy operation to fail. As a result the LUN remains in the system. Status (0x712d8426) will appear when displaying the LUN.

Contact your service provider to remove the LUN.


05.33.000.5.038

Platforms: All

Severity: Critical

Tracking: 571738

Snap creation fails and the snap will be left in an error state when the source LUN is in the middle of a trespass.

When creating a snap where the source LUN is in the middle of a trespass, the create-snap command will fail and the snap will be left in an error state with status:

0x716D8070 (MLU_SNAPSHOT_CBFS_FILE_NOT_FOUND).

Destroy this faulted snap and re-issue the create-snap command to create the snap.


05.33.000.5.038

53




Platforms: All

Severity: Critical

Tracking: 569009

Not enough free space in a pool to recover LUNs.

If the total consumed size of a LUN is greater than 512TB and there is not enough free space in the pool (up to 600GB), the recovery of that LUN will require expanding the pool to create the required free space. This also means if there are 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.

Expand the pool or if the 512TB spans multiple LUNs. Then, only do one recovery at a time where each LUN is at or below 512TB of consumed space.


05.33.000.5.038

FAST CACHE and FAST VP

There are no known problems or limitations in this release.

EMC SnapView related

SnapView Clones


Platforms: All

Severity: Low


Tracking: 294717

Unisphere command will fail during a single SP reboot.

Navisphere CLI and Unisphere Manager return an error message when starting a protected restore. If a clone’s protected restore operation is initiated while one of the storage processors is booting, the SP that owns the clone source may not be able to communicate with the peer SP for a short period of time.

Reissue the protected restore operation after both SPs have completed booting. Exists in versions: 05.33.000.5.015 05.33.000.5.034 05.33.000.5.035

05.33.000.5.038

Platforms: All

Severity: Low

Frequency: Always under a rare set of circumstances

Tracking:

247637, 248149, 251731

Synchronizing and reverse-sychronizing will be started in automatic mode when running with a single SP.

SnapView clones will restart synchronizing/reverse synchronizing an unfractured clone after an SP failure even if the recovery policy is set to manual. This behavior occurs only if the system is running with a single SP, or when the clone source is also a MirrorView secondary.

Fracture the clone after the SP recovers from the failure.


05.33.000.5.038

54




Platforms: All

Severity: Low

Frequency: Rarely under a rare set of ciscumstances

Tracking: 469420

A protected restore operation will fail and an error message will display.

Restarting a protected restore after both SP fail may result in the following error message:

Any writes issued since the PR started are lost. Please retry the command and the source will be restored to the data in the clone.

This indicates that the system has detected an inconsistent state of the data.

Reissue the protected restore reverse-sync operation.


SnapView Snapshots

Details Brief description Symptom details Solution/Workaround

Platform: All

Severity: Low


Tracking: 539292

Activating a snap session on a snapshot with an open activated session may fail without an error indication.

If an attempt is made to activate a snap session on a snapshot which already has an activated session, the operation will fail but no error will be returned.

The session should be activated on an unused snapshot.


05.33.000.5.038

Admsnap


Platforms: All

Severity: Low


Tracking: 286532

An admsnap command may incorrectly report a failure, but the command succeeds if the target LUN is trespassed during the operation.

The admsnap command may report a failure but the operation succeeds if the target LUN of the operation is trespassed during the admsnap operation.

The actual state of the operation can be verified by using Navisphere® /Unisphere® software.

Exists in versions: 2.32.0.0.5 and previous

55




Platforms: AIX

Severity: Low


Tracking: 215474

Admsnap activate commands executed in an AIX PowerPath® environment may generate SC_DISK_ERR2 messages in the system log file.

The messages are generated because a deactivated snapshot is present in the storage group. Whenever snapshots are in the storage group, running cfgmgr causes ASC 2051 problems in the errpt file. The messages are harmless and can be ignored.

To prevent these messages from beign generated, activate the snapshot using Secure CLI, which will allow execution of admsnap on the host.


Platforms: Linux

Severity: Medium


Tracking: 286533

Admsnap sessions are not activated on a Linux system if more than eight device paths are required to complete the operation.

Admsnap cannot access more than eight device paths on the backup host.

The Linux kernel creates only eight SG devices (SCSI generic devices) by default. Additional SG devices must be created and then linked to the SD devices. (The internal disk uses one of the SG devices). Use the Linux utility /dev/MAKEDEV to create additional SCSI generic devices.


Platforms: Windows

Severity: Low

Frequency: Always

Tracking: 286529

Admsnap fails when the operation is targeted for a dynamic disk.

An admsnap session containing a dynamic disk that is rolled back to the production host cannot be imported on the production host using admsnap.

Dynamic disks must be imported using the Disk Administrator or the Microsoft Diskpart utility.


56




Platforms: Windows

Severity: Low

Frequency: Always

Tracking: 206345

The admsnap start command fails if the volume contains a Veritas volume and the LUNs for that volume are trespassed to the secondary path.

The admsnap start command fails with Error: 0x3E050011 (One or more devices need manual attention by the operator),if the volume contains a Veritas volume and the LUNs for that volume are trespassed to the secondary path.

Trespass the volume to the primary path or use Navisphere Secure CLI to start the SnapView session.


Platform: Windows

Severity: Low

Frequency: Always under a specific set of circumstances.

Tracking: 225937

The admsnap activate command may inaccurately return a warning if the operating system maintains a drive letter mapping for the volume being brought online.

The admsnap activate command generates a warning that one or more devices was not assigned a drive letter when all volumes were assigned drive letters.

This usually occurs when the registry contains stale device mapping information. Update the registry by using a utility from Microsoft called “scrubber” to remove stale entries. The stale device mapping information generates a condition that prevents admsnap from determining if all volumes activated were assigned drive letters. Admsnap generates a warning.


Platform: Windows

Severity: Low


Tracking: 226043

The admsnap command fails to start or stop a session in a DMP environment.

The admsnap command fails to start or stop a session in a DMP environment. The failure is due to the trespassing of the LUN that is the target of admsnap operation. The DMP/Volume Manager keeps track of the current storage processor owner, independently from the operating system.

To resolve this issue, trespass the volume to the peer storage processor and reissue the admsnap command.


57




Platform: Windows

Severity: Low


Tracking: 225832

The admsnap list command may list devices multiple times when executed in a DMP environment.

The admsnap list command may list devices multiple times when executed in a DMP environment.

Use the –d option on the command line to suppress duplicate entries for a particular device or volume.


Platform: Solaris

Severity: Low

Frequency: Always.

Tracking: 207655

The admsnap activate command causes LUNs to trespass on the host in a DMP environment.

The admsnap activate command (when issued without the –o <device> parameters) scans the SCSI bus using the primary and secondary paths for the devices, causing the LUNs to trespass.

Use the –o <device> option for the admsnap activate command.


Platform: SuSE

Severity: Low


Tracking: 230902

Warning messges are generated during the installation or removal process if Admsnap is installed or uninstalled when rpm is used on SuSE systems.

The package fails to complete the operation (installation or removal) without generating warning messages.

Use the yast2 command on SuSE Linux systems to install or remove the admsnap package.


58



Admhost


Platforms:

Windows

Severity: Medium

Frequency: Always

Tracking: 203400

Admhost does not support Windows Dynamic Drives.

Admhost operations fail if you attempt them on a Dynamic Drive.

The workaround is to import Dynamic Drives using the Disk Administrator or the Microsoft Diskpart utility.


EMC SANCopy for VNX OE for Block

Details Description Symptom Solution/WorkaroundPlatforms: All

Severity: Medium

Frequency:

Likely under a specific set of circumstances

Tracking: 293019

A storage processor (SP) may reboot if many destination LUNs are trespassed or an NDU is initiated.

The SP may reboot if the following occurs:

If a SAN Copy session is running with 50 or more destinations located on the SAN Copy storage system and 50 or more of the destination LUNs are trespassed.

An NDU is initiated.

Do not trespass destination LUNs or initiate an NDU when a copy session with 50 or more destinations is in progress.


05.33.000.5.038

Platforms: All

Severity: Low

Frequency: Always.

Tracking: 184420

SAN Copy does not verify the selected LUN size when the size of the LUN source changes.

When you use SAN Copy with Navisphere CLI, you are able to change the source LUN to be incorrectly larger than the destination LUNs. The SAN Copy session eventually fails because the destination LUNs are too small. SAN Copy does not verify that the selected LUN size is valid.

When you modify a copy descriptor with Navisphere CLI, ensure any destination LUNs are always the same size or larger than the source LUN.


05.33.000.5.038

59




Severity: Low

Frequency: Always.

Tracking: 215061

A SAN Copy modify command fails if the only destination of a SAN Copy session fails.

If the only destination of a SAN Copy session fails and this session is modified to replace it with a new destination, the modify fails. This issue happens because the modify command checks for the new destination before checking that the failed destination is removed in the modified session. The modify fails as it thinks a failed destination exists.

Modify the copy session to a full session and then back to an incremental session. Once the modify is successful, add your new destination to the session. Once the addition of the destination is successful, remove the previously failed session.


05.33.000.5.038

Platforms: All

Severity: Medium

Frequency: Rarely, under a specific set of circumstances

Tracking: 311047

Remote devices in the SAN Copy session may fail if iSCSI ports are used as a combination of initiator ports and target ports.

If SAN Copy sessions start between two storage systems connected over iSCSI and both storage systems act as SAN Copy systems for some SAN Copy sessions and remote systems for other SAN Copy sessions, remote devices in the SAN Copy session may fail with error:

Unable to locate the device. Check that the device with this WWN exists.

Schedule the SAN Copy sessions on both storage systems so that they do not run at the same time. or Configure the iSCSI connections between the storage systems so that iSCSI ports used for SAN Copy in the I/O module are all used either as initiator ports or target ports but not in combination.


05.33.000.5.038

60




Severity: Low


Tracking: 350153

Start Time and Completion Time of session may be inconsistent on both SPs.

Session display on Start Time and Completion Time may be inconsistent on both SPs after adding a destination to Incremental session.

After starting the session, the inconsistency is non-existent.


05.33.000.5.038

Platforms: All

Severity: Low

Frequency: Under a specific set of circumstances

Tracking: 475390

If you change the max concurrent setting, and there are more active sessions than the new setting allows, the new setting does not take

effect immediately.

The max concurrent SAN Copy setting does not take effect immediately when there are already more active sessions than new setting.

New setting takes effect after existing active sessions stop.


05.33.000.5.038

Platforms: All

Severity: Low


Tracking: 560498

An incremental SAN Copy session or MirrorView / A session may fail to be removed.

If the peer SP is in the process of initialization or shutdown, an incremental SAN Copy session or MirrorView / A session may fail to remove.

Retry the incremental SAN Copy session or MirrorView / A session. The peer must be up to successfully remove the session.


05.33.000.5.038

61



EMC MirrorView™/Asynchronous and MirrorView™/Synchronous for VNX OE for Block related

EMC MirrorView/A


Platforms: All

Severity: Medium


Tracking: 329924

MirrorView/A An attempt to promote a large consistency group when the storage systems are connected by iSCSI can fail.

An uncleared deadlock prevention flag (error 0x7152807) may prevent further promote or administrator operations. This issue can occur during heavy I/O traffic and/or other mirror updates.

When you promote a large group, reduce other loads on the storage system where possible. If this issue is found, destroy and recreate the affected group. An SP restart of the primary and/or secondary storage system clears the deadlock prevention flag.


05.33.000.5.038

Platforms: All

Severity: Low


Tracking: 333132

MirrorView/A Mirrors may administratively fracture unexpectedly.

Internal data structures can become inconsistent, which results in the mirrors being administratively fractured.

Issue a synchronize command for the mirror. If this fails the first time, retry the command.


05.33.000.5.038

Platforms: All

Severity: Low


Tracking: 335576

MirrorView/A Mirrors may become administratively fractured unexpectedly.

If a multi-LUN consistent (MLC) SnapView session starts, a mirror may fracture unexpectedly.

Issue a synchronize command for the mirror. If this fails the first time, retry the command.


05.33.000.5.038

62



EMC MirrorView/S


Platforms: All

Severity: Medium


Tracking: 237638

MirrorView/S Storage processor can reboot unexpectedly when a mirror is destroyed.

If a mirror is destroyed while a trespass occurs, it is possible for internal data structures to become inconsistent and result in a storage processor reboot.

Avoid destroying a mirror when a trespass is likely, such as just after a storage processor boots, when hosts with failover software may attempt to rebalance the load.


05.33.000.5.038

Platforms: All

Severity: Low


Tracking: 334575

MirrorView/S Secure CLI may time out during a mirror creation operation.

When Secure CLI processes a large number of system actions, it may return the following error:

Request failed. The force polling failed, because of timeout - the system may be busy, please try again. (334575)

Retry the mirror create operation.


05.33.000.5.038

Platforms: All

Severity: Low


Tracking: 389452

MirrorView/S A mirror may fracture unexpectedly.

If one storage processor shuts down at the same time the other storage processor sends a synchronize command, the mirror may fracture.

Reissue the synchronize command.


05.33.000.5.038

63



EMC Serviceability related

USM


Platforms: All

Severity: Medium

Tracking: 572236

The USM Online Disk Firmware Upgrade (ODFU) wizard inaccurately reports the disk firmware upgrade status and progress.

While watching the status in the USM ODFU wizard, some reports are inaccurate. The completed disks number 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.

No workaround.


Platforms: All

Severity: Medium

Tracking: 558207

Cannot log into USM when one SP is down.

When one SP is down, USM takes several minutes to log into the system.

None.


Platforms: CLARiiON

Severity: Medium

Tracking: 550578

An error is presented when running the Storage System Verification wizard on a CLARiiON system.

The wizard returns an error when run against a CLARiiON system.

Java 64 does not support loading 32-bit DLL. Install 32-bit Java.

Platforms: All

Severity: Medium

Tracking: 559742

The software upgrade process hangs after a file transfer.

USM does not support upgrades of VNX OE in a proxy configuration.

No workaround


Platforms: VNX

Severity: Medium

Tracking: 576837

The state of a replaced disk does not change.

When running the Disk Replacement wizard in USM, the state of a replaced disk remains unchanged.

Verify the disk has been replaced by running the getdisk command as described in the EMC VNX Command Line Reference for Block CLI manual.


64




Platforms: VNX

Severity: Medium

Tracking: 561544/551522

An internal error appears during a language pack installation.

An internal error is shown after the File-side language pack is installed, and before starting the Block-side language pack installation.

Verify network connectivity. Restart USM and log into the system. Start the Install Software wizard and choose the third option to install the Block language pack.


Platforms: VNX

Severity: Medium

Tracking: 578647

The Install Software wizard fails to upgrade VNX for Block OE.

The Install Software wizard fails to upgrade the VNX for Block OE. An error states that USM is unable to obtain the software maintenance status.

Under Tools, click Software Maintenance Status to view the upgrade status. When the upgrade finishes, commit the package and re-enable statistics, if needed.


VNX Installation Assistant (VIA)


Platforms: All

Severity: Medium

Tracking: 593647

The VIA window closes after clicking Next from Welcome screen.

Run the Windows ipconfig command to check if the system has more than six active connections. If so, disable the unused connections to reduce the number to six or less. Then retry the VIA operation. Exists in versions: 8.1.2.51

65




Platforms: All

Severity: Medium

Tracking:566667

VIA fails to change the sysadmin password on the Apply page

An error message displays continuously when trying to change the password on the storage system and the retry fails.

Repair any network connectivity issues on the storage system. Wait 10 minutes, then click Retry.


Platforms: All

Severity: Medium


Tracking: 593647

VIA window closes after clicking Next from Welcome screen.

After launching VIA, the Welcome screen appears. If Next is clicked, the VIA application closes.

Run Windows ipconfig command to determine if the system has more than six connections. If so, disable the unused connections to make the total number no more than six and retry the VIA operation.


ESRS IP Client

There are no known problems and limitations in this release.

EMC Snapshots related

VNX Snapshots version 05.33.000.5.035


Platforms: All

Severity: Critical

Tracking: 571738

Snap creation fails and the snap will be left in an error state when the source LUN is in the middle of a trespass.

When creating a snap where the source LUN is in the middle of a trespass, the create-snap command will fail and the snap will be left in an error state with status 0x716D8070 (MLU_SNAP_CBFS_FILE_NOT_FOUND).

Destroy this faulted snap and re-issue the create-snap command to create the snap.

Exists in versions: 05.33.000.5.015 05.33.000.5.034 05.33.000.5.035 05.33.000.5.038

66




Platforms: All

Severity: Medium


Tracking: 481887

LUN –destroy operation fails with snapshots exist error if a LUN is destroyed immediately after destroying snapshot(s) associated with the LUN.

Snapshot destroy is an asynchronous operation. If a LUN is destroyed immediately after destroying its snapshots, there is a possibility of a snapshot being in the destroying state that prevents the LUN from being destroyed.

Wait for the snapshots to be destroyed or include the “destroySnapshots” switch while destroying the LUN.

Exists in versions: 05.33.000.5.015 05.33.000.5.034 05.33.000.5.035 05.33.000.5.038

SnapCLI version 3.32.0.0.5 (and 3.32.0.0.6, Linux only)

Details Description Symptom Solution/Workaround Platforms: All

Severity: Low


Tracking: 286532

A snapcli command may report a failure, but the command succeeds if the target LUN is trespassed during the operation.

A snapcli command may report a failure, but the command succeeds if the target LUN was trespassed during the operation.

The actual state of the operation can be verified using Unisphere® software.


Platforms: AIX

Severity: Low

Frequency:

Likely under a specific set of circumstances

Tracking: 215474

The snapcli attach command executed in an AIX PowerPath® environment can generate SC_DISK_ERR2 messages in the system log file.

The error messages are generated due to a presence of a detached VNX snapshots mount point in the storage group. Whenever VNX snapshots mount points are in the storage group, running cfgmgr causes ASC 2051 problems in the errpt file. The messages are harmless and can be ignored.

Activate the VNX snapshots mount point using Navisphere Secure CLI. Then execute SnapCLI on the host to prevent these messages from being generated.


67



Details Description Symptom Solution/Workaround Platforms: Linux

Severity: Medium

Frequency:

Always under a specific set of circumstances

Tracking: 286533

VNX snapshots are not attached on a Linux system if more than eight device paths are required to complete the operation.

SnapCLI cannot access more than eight device paths on the backup host.

The Linux kernel creates only eight SG devices (SCSI generic devices) by default. Additional SG devices must be created and then linked to the SD devices. (The internal disk uses one of the SG devices). Use the Linux utility /dev/MAKEDEV to create additional SCSI generic devices.


Platforms: Windows

Severity: Low

Frequency: Always

Tracking: 286529

SnapCLI fails when the operation is targeted for a dynamic disk.

VNX Snapshots containing a dynamic disk, which is rolled back to the production host, cannot be imported on the production host using SnapCLI.

Dynamic disks must be imported using the Disk Administrator or the Microsoft Diskpart utility.


Platforms: Windows

Severity: Low

Frequency: Always

Tracking: 206345

The snapcli create command fails if the volume contains a Veritas volume and the LUNs for that volume are trespassed to the secondary path.

The snapcli create command fails with the following error message if the volume contains a Veritas volume and the LUNs for that volume are trespassed to the secondary path:

Error: 0x3E050011 (One or more devices need manual attention by the operator).

Trespass the volume to the primary path or use Navisphere Secure CLI to create the VNX Snapshot.


68



Details Description Symptom Solution/Workaround Platforms: Windows

Severity: Low


Tracking: 225937

The snapcli attach command might return a warning if the operating system maintains a drive letter mapping for the volume being brought online.

The snapcli attach command generates a warning that one or more devices are not assigned drive letters, when the other volumes are assigned drive letters.

This usually occurs when the registry contains stale device mapping information. Update the registry by using the “scrubber” utility from Microsoft to remove stale entries. The stale device mapping information generates a condition that prevents SnapCLI from determining if all volumes attached were assigned drive letters. SnapCLI generates a warning.


Platforms: Windows

Severity: Low


Tracking: 226043

SnapCLI fails to create or destroy a VNX Snapshot in a DMP environment.

SnapCLI fails to create or destroy a VNX Snapshot in a DMP environment.

The LUN trespassing that is the target of the Snap CLI causes failure. The DMP/Volume Manager keeps track of the current storage processor owner independently from the operating system. To resolve this issue, trespass the volume to the peer storage processor and use the snapcli command.


Platforms: Windows

Severity: Low


Tracking: 225832

The snapcli list command might list devices multiple times when executed in a DMP environment.

The snapcli list command might list devices multiple times when executed in a DMP environment.

Use the –d option on the command line to suppress duplicate entries for a particular device or volume.


69



Details Description Symptom Solution/Workaround Platforms: Solaris

Severity: Low

Frequency: Always.

Tracking: 207655

The snapcli attach command causes LUNs to trespass on the host in a DMP environment.

The snapcli attach command (when issued without the –o <device> parameters) scans the SCSI bus using the primary and secondary paths for the devices, causing the LUNs to trespass.

Use the –o <device> option for the snapcli attach command.


Platforms: SuSE

Severity: Low


Tracking: 230902

If “rpm” is used on SuSE systems during the installation or removal process, warning messages are generated or there are problems in installing or uninstalling SnapCLI.

The package fails to complete the operation (installation or removal) or warning messages are generated.

Use the yast2 command on SuSE Linux systems to install or remove the SnapCLI package.


Virtualization


Platforms: All

Severity: Low

Tracking: 465905

VMware: Sync does not perform after a session is re-established.

VASA information displays in vSphere may be out of sync with the current state of the storage system due to errors in the Storage Provider, vCenter Server, or communication errors between the two components.

If you suspect that this information may be out of date, perform a manual Sync via the Storage Providers page and refresh/update the appropriate pages in the vSphere Client. If this does not fix the issue, remove and re-add the Storage Provider(s) in question.

70




Platform: All


Severity: Low

Tracking: 496273

VASA LDAP users are not properly mapped to correct VASA privileges on VNX for File.

Unable to add Vendor Provider in vSphere using credentials of an LDAP user on VNX for File.

To allow a LDAP user to login through VASA, it is not sufficient for the LDAP group to be mapped to an appropriate group.

1. Create an LDAP user account, if it does not 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

Platforms: All

Severity: Low

Tracking: 565093

VASA Provider goes off-line and the certificate is missing. Information does not update in Virtual Center.

To add a VNX Block storage system *twice* to the list of Vendor Providers (once for each Storage Processor) is not a valid configuration. 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.

Remove both VASA connections to the storage system, then re-add a single VASA connection to either of the SPs.

71

Documentation



Platform: All


Severity: Low

VAAI Copy offload between SPs causes implicit trespasses.

The copy offload operation generateds requests on the array that trigger load balancing. If the source and destination devices are not owned by the same SP, the array moveds ownership of the destination LUN to match the source.

No action necessary. After the copy offload operation completes, normal host I/O to the destination LUN trigger the load balancing back to the correct user-assigned SP.

Exists in versions: All versions

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://mydocs.emc.com/VNX.

For the most up-to-date documentation and help go to EMC Online Support at https://Support.EMC.com.

Security Configuration Guide for VNX

The information about ports 5988 and 5989 is listed in the wrong location, Table 4, VNX for file Data Mover network ports. The information should be listed instead in Table 5, VNX for file Control Station network ports.

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.

72

Where to get help


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.

Note: Do not request a specific support representative unless one has been assigned to your particular system problem.

Copyright © 2014 EMC Corporation. All Rights Reserved. Published in the USA.

Published February 2014

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.

docu53275 vnx operating environment for block 05.33.000.5.52 release notes

Documents

emc vnx vnx

vnx oe

block deduplication

block compression

block oe version

revision history emc

environment oe

following vnx features