Version 2.3.1.20364
Release Notes
P/N 300-012-191 REV 24 October 04, 2012
Product description ................................................................................... 2 New features and changes ........................................................................ 2 Fixed issues ................................................................................................. 3 Installation and upgrade considerations ................................................ 4 Technical notes ........................................................................................... 5 Troubleshooting and getting help ........................................................... 5
Check the VNXe Online Support website, at emc.com/vnxesupport, for updates to this document. Updates are made when a new version or patch is released, or when new information is discovered. Registration is required for the Online Support website.
Product description
Product description
The EMC VNXe is an entry-level, multiprotocol (Block and File) storage product that delivers enterprise-class reliability and data availability in a solution that is easy to install, manage, service, and support. Designed for the IT generalist, VNXe provides an applicationcentric view of storage that enables administrators with little or no storage expertise to easily deploy and manage storage resources to support their key business applications.
Fixed issues
Fixed issues
The following issues have been fixed in this release:
Priority P01 Symptom Description Rolling storage processor restarts occurred when users tried upgrading to VNXe Release 2.3.1.19462. This issue occurred when a storage processor already upgraded to VNXe Release 2.3.1.19462 restarted for some reason before the other storage processor was upgraded to the same release. Support for a new enclosure was introduced in VNXe Release 2.3.1.19462. The new enclosure requires new configuration management software that syncs up the storage processors. The rolling restart issue occurred because the operating environment did not understand the new messages before the upgrade. Both storage processors restarted frequently. This occurred because the netfilter module, which tracks all active connections, was also tracking internal and loopback traffic. This extra tracking caused the netfilter table to fill up and drop heartbeat packets. Users received the following alert message stating that the battery backup unit (BBU) may have faulted: 6012d : SP BBU 0 has faulted. This was an erroneous message that was generated when the system was unable to obtain the BBU status for a few seconds. When the solid state disk (SSD) became full, both storage processors were re-imaged and restarted. Fix The rolling restart condition will no longer occur when a storage processor with new software restarts before the other storage processor is upgraded with the new software. Tracking Number 501648
P01
Existing rules were fixed to prevent internal and loopback traffic from being tracked. Also, new rules were added to the firewall to prevent packets from being dropped. The application code used to monitor BBU status has been fixed to ensure that such false messages are not generated when the control bus is busy. A script was added that monitors the SSD usage and issues an alert message when the SSD usage is greater than 90% of the total capacity.
506880
P02
506882
P01
506885
Priority P01
Symptom Description When a shared folder server or iSCSI server service failed and became unavailable, a memory leak occurred in one of the VNXe services. This caused the storage processor to run out of available memory, which may have resulted in the storage processor restart. Keeping expired or completed tasks in memory for unnecessary period of time contributed to a high memory usage by the management service. This may have resulted in the storage processor restart. A memory leak in one of the management services led the storage processor to run low on memory. This resulted in performance issues. The memory leak led the storage processor to run out of available memory, which may have resulted in the storage processor restart. When a persistent database corruption was present, users noticed inconsistent information in Unisphere and often were unable to perform regular management operations. For example, datastore virtual disks were not visible in the user interface.
P02
Any expired or completed tasks are now cleaned up every minute to reduce the management service memory usage. The memory leak was fixed.
506894
P01
506895
P01
A lock has been added that prevents simultaneous write operations from multiple threads to the same persistent database file.
506896
Technical notes
Technical notes
Required update
EMC recommends that you keep your VNXe system up to date by upgrading to the latest software version at your earliest opportunity. Note that if you are running any version of VNXe that is older than 2.1.0, you must first upgrade your system to VNXe 2.1.0 and then upgrade to the current software version.
Copyright 2012 EMC Corporation. All rights reserved. Published in the USA. Published October 2012 EMC believes the information in this publication is accurate 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.