Here is Your Customized Document

Your Configuration is:

VNX Issues and Recommended Actions

storage-systype - VNX5300
Document ID - 1401815338856

Reporting Problems

To send comments or report errors regarding this document,

please email: mydocs@emc.com.
For Issues not related to this document, contact your service provider.
Refer to Document ID:
1401815338856
Content Creation Date June 3, 2014
Date: Oct. 31, 2013

Known VNX Installation and Upgrade Issues

The following tables (which can also be found in EMC Knowledgebase article emc271233) are lists of known VNX
installation or upgrade issues with workarounds or recommendations.

Important: The tables are titled VNX Block Installation Issues, VNX File/Unified Issues, VNX Block Upgrade Issues,
and VNX File/Unified Issues. Within each table, the EMC Knowledgebase article number and a short description is
provided. These lists were accurate at publication time but may have since been updated. Always check EMC
Knowledgebase article emc271233 and its referenced Knowledgebase articles for the latest information.

Note: To read a Knowledgebase article, go to EMC online support website at Support.emc.com, click the Search
tab, select Knowledgebase in the Scope by resource dropdown, enter the KB article number in the Search
Support line, and then click the query icon.

VNX Block Installation Issues

ETA/ KB Article Description

RecoverPoint, VNX: Storage Processor (SP) reboots may occur with VNX Operating Environment Release
ETA emc327099 32 P204 in a RecoverPoint environment.
ETA emc316719 RecoverPoint: Thin LUN Extender can cause data inconsistency.
RecoverPoint, VNX: Unexpected RPA reboot may cause Storage Processor (SP) reboot resulting in short
ETA emc315777 data unavailability.
ETA emc308914 Excessive trespassing causes I/O performance issues, which may adversely affect Virtual Provisioning
Using compression on Thin LUNs could result in data integrity issues when these LUNs are heavily
ETA emc294916 written to over an extended period of time.
VNX systems with iSCSI-attached hosts may have a single or dual storage processor (SP) reboot after 248
ETA emc291837 days of runtime.
emc286025 EFD drives require new firmware update for new systems at the time of installation.
emc278385 Adding and removing VNX systems to local domains using Unisphere.
VNX, VNXe: Unable to initialize a VNX/VNXe system using VNX Installation Assistant (VIA), Unisphere
ETA 170407 Storage System Initialization Wizard (InitTool), or VNXe Connection Utility (CU).

VNX File / Unified Installation Issues

ETA/ KB Article Description
ETA 170407 VNX, VNXe: Unable to initialize a VNX/VNXe system using VNX Installation Assistant (VIA), Unisphere
Storage System Initialization Wizard (InitTool), or VNXe Connection Utility (CU).

1
 VNX Installation and Upgrade Issues
VNX Block Upgrade Issues

ETA/ KB Article Description

ETA emc327099 RecoverPoint, VNX: Storage Processor (SP) reboots may occur with VNX Operating Environment Release
32 P204 in a RecoverPoint environment.
ETA emc308955 SMLink_check tool should be run to check condition of Virtual Provision (VP) Pools on VNX OE 05.31
prior to upgrade to VNX OE 05.32.
ETA emc299619 Non-disruptive upgrade (NDU) from VNX OE 05.31.000.5.XXX and later to VNX OE 5.32.000.5.006 or VNX
OE 05.32.000.5.008 could result in a reboot of a single storage processor (SP) and the inability of the
NDU operation to complete.
ETA emc298607 VNX, RecoverPoint: VNX Operating Environment (OE) for Block 05.32 is incompatible with RecoverPoint
Appliance software.
emc315886 Non-disruptive upgrade failed due to slow virtual port uninstallation.
emc315885 VNX: Upgrade to VNX Operating Environment (OE) for Block 05.31 and 05.32.
emc307623 SP panic 0x00000044 (HEMI_MAX_CLK_EVENTS_EXCEEDED) on a VNX Series array during NDU from
VNX OE 05.31 to VNX OE 05.32.
emc277689 Array Read and Write cache settings will change after NDU of certain VNX Block enablers, and Read
cache may become disabled.
emc262738 Failover mode changes from 4 (ALUA) to 1 for ESX 4.x hosts when SP is rebooted.
ETA emc315777 RecoverPoint, VNX: Unexpected RPA reboot may cause Storage Processor (SP) reboot resulting in data
unavailability.
ETA emc165367 VNX: Thin LUNs and Virtual Machine (VM) datastores supported by Thin LUNs inaccessible over FCoE
transport.

VNX File / Unified Upgrade Issues

ETA/ KB Article Description

emc277773 System does not call home for some critical Block system errors.
emc281631 Only one alert is visible in the alerts page in Unisphere/Celerra Manager.
emc297471 Celerra, VNX, and VNXe: ESA-2012-027: EMC Celerra/VNX/VNXe Improper Access Control Vulnerability.
emc299745 Repeated Data Mover reboots could be triggered by a >2 TB file system with checkpoints.
emc309210 Celerra and VNX: Data Mover reboots when Windows client uses a previous version of checkpoints to
access file system.
SalesForce 166203 VNX: Microsoft Internet Information Services (IIS) server may experience operating issues after VNX
Operating Environment File upgrade.

2
3
Copyright 2013, EMC Corporation. All rights reserved.

Published Oct. 31, 2013

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.