Storage Center 6.7 Release Notes

Transcription

1 Document Number: Rev. O Storage Center 6.7 Release Notes This document describes the new features, enhancements, and known issues in Storage Center 6.7. Current Version: Release Date: Previous Version: Topics: Revision History Storage Center 6.7 Feature Availability and Licenses Storage Center 6.7 Scalability System Manager Requirements New in This Release Storage Center Fixed s Known s Storage Center Update Information Revision History Document Number: Revision Date A October 2015 Initial release B October 2015 Added the Import Volumes from PS Series Storage Arrays feature description C October 2015 Added information about the SC9000 controller D November 2015 Updated for Storage Center E December 2015 Updated for Storage Center F February 2016 Updated for Storage Center G February 2016 Removed information about SCv2000 series H June 2016 Updated for Storage Center I June 2016 Updated for Storage Center J August 2016 Updated for Storage Center K November 2016 Updated for Storage Center L December 2016 Updated for Storage Center M April 2017 Updated for Storage Center N May 2017 Added one Fixed and clarified Live Volume with Automatic Failover availability O March 2018 Updated for Storage Center Storage Center 6.7 Release Notes 1

2 Storage Center 6.7 Feature Availability and Licenses The core licenses and support for optional licensed features varies depending on the storage system. Table 1. Licensed Features Storage System SC9000 Licensed Features SC9000 storage systems provide a Core Software bundle and optional value-add bundles. Core Software Bundle Data Compression Data Instant Replay (Snapshots) Dynamic Capacity Dynamic Controllers Enterprise Manager Local Data Protection Multi-VLAN Tagging Virtual Ports SC9000 storage systems support these optional licenses: Replay Manager Data Progression Enterprise Manager Chargeback Live Volume Remote Instant Replay (Replication) SED FIPS Secure Data Storage Protection Bundle Replay Manager Live Volume Remote Instant Replay Storage Optimization Bundle Data Progression Fast Track Total Feature Bundle SED FIPS Secure Data Storage Optimization Bundle Storage Protection Bundle SC8000 SC8000 storage systems provide the following licensed features: Data Compression Data Instant Replay (Snapshots) Dynamic Capacity Dynamic Controllers Enterprise Manager Local Data Protection Multi-VLAN Tagging SC8000 storage systems support these optional licenses: 2 Storage Center 6.7 Release Notes

3 Storage System Licensed Features Replay Manager Data Progression Enterprise Manager Chargeback Fast Track Live Volume Remote Instant Replay (Replication) SED FIPS Secure Data Virtual Ports SC4020 SC4020 storage systems provide the following licensed features: Data Compression Data Instant Replay (Snapshots) Dynamic Capacity Dynamic Controllers Enterprise Manager Local Data Protection Multi-VLAN Tagging SC4020 storage systems support these optional licenses: Replay Manager Data Progression Enterprise Manager Chargeback Fast Track Live Volume Remote Instant Replay (Replication) SED FIPS Secure Data Virtual Ports Storage Center 6.7 Scalability The following scalability guidelines apply to Storage Center 6.7. Storage System Scalability Guidelines The following scalability guidelines apply to SC9000, SC8000, SC4020, and CT-SC040 storage systems running Storage Center 6.7. NOTE: Raw storage space is expressed in decimal units (for example, 1TB = bytes). Addressable storage space is expressed in base 2 units (for example, 1TB = 2 40 bytes). Therefore, a 1TB drive measured in decimal units is equal to 0.909TB base 2 units. Storage System SC9000 (Dual-Controller) with 128GB of memory per controller SC8000 (Dual-Controller) with 64GB of memory per controller Supported Maximum 3.1PB raw and 2.0PB addressable storage space using the standard 2MB page size 750TB raw and 500TB addressable storage space using a 512KB page size 3.1PB raw and 2.0PB addressable storage space using the standard 2MB page size 750TB raw and 500TB addressable storage space using a 512KB page size Storage Center 6.7 Release Notes 3

4 Storage System SC8000 (Dual-Controller) with 16GB of memory per controller SC4020 with 16GB of memory per controller CT-SC040 (Dual-Controller) with 12GB of memory per controller CT-SC040 (Dual-Controller) with 6GB of memory per controller Supported Maximum 750TB raw and 500TB addressable storage space using the standard 2MB page size 400TB raw and 300TB addressable storage space using a 512KB page size 1054TB raw and 700TB addressable storage space using the standard 2MB page size 500TB raw and 400TB addressable storage space using a 512KB page size 750TB raw and 500TB addressable storage space using the standard 2MB page size 400TB raw and 300TB addressable storage space using a 512KB page size 400TB raw and 300TB addressable storage space using the standard 2MB page size 400TB raw and 300TB addressable storage space using a 512KB page size Storage Center Scalability Guidelines The following scalability guidelines are the maximum recommended design guidelines for SC9000, SC8000, SC4020, and CT-SC040 controllers running Storage Center 6.7. Storage Center Object Disk Folder Server Volume Live Volume Thin Import Data Instant Replay NOTE: Data Instant Replay (Snapshots) is a licensed feature. Replication Supported Maximum 10 disk folders 500 servers (Total number of servers includes physical servers, virtual servers, and server clusters.) 500 server folders 1000 server HBA initiator ports (Total number of HBA initiator ports includes all physical and virtual ports that are visible to the SAN.) 500TB maximum volume size (or the maximum addressable storage space, whichever is less) 2000 volumes 500 volume folders 100 Live Volumes 10 volumes (maximum simultaneous imports) 16,000 Replays (4000 Replays for an SC4020) 1000 Replay profiles 100 Replay history profiles 40 volumes per consistency group 500 source replications (SC4020: 250 replications) 2000 target replications (SC4020: 1000 replications for FC and 230 replications for iscsi) 4 Storage Center 6.7 Release Notes

5 System Manager Requirements System Manager is a Java applet that requires the use of a Java plug-in to run. The following table provides the minimum software requirements for running System Manager. Component Web browser Requirements Windows Internet Explorer versions 7, 8, 9, and 11 Windows Internet Explorer Desktop version 10 (Internet Explorer Modern version 10 is not supported) Mozilla Firefox on Microsoft Windows NOTE: Other web browsers might work, but are not officially supported. Java Java version 7 and 8. When using Java, open the Java Control Panel and make sure that the Enable Java content in the browser option is selected. Enterprise Manager Compatibility Storage Center 6.7 is compatible with Enterprise Manager 2015 R2 or later. New in This Release Storage Center 6.7 supports new Dell EMC hardware and introduces software features. SC9000 Storage Controller Storage Center 6.7 introduces support for the SC9000 storage controller. SC8000 Storage Controller The SC8000 storage controller now supports the 4GB write cache card, support for Solid State Drives (SSDs) and Self-Encrypting Drives (SEDs), and Data Compression for all-flash arrays. SC4020 Storage System The SC4020 storage system now supports a maximum of 192 drives, 16Gb Fibre Channel IO cards, solid state drives (SSDs) and selfencrypting drives (SEDs), and Data Compression for all-flash arrays. SC400 and SC420 Expansion Enclosures Storage Center 6.7 introduces support for SC400 and SC420 expansion enclosures. Storage Center 6.7 Release Notes 5

6 Data Progression Improvements Storage Center includes changes to Data Progression that reduce the impact on Storage Center performance. Data Progression runs daily at specified time and continues until all tasks are completed. If all the tasks are not completed, those tasks are completed in the next Data Progression cycle. NOTE: Data Progression still follows the schedule set on the Storage Center. Live Volume Automatic Failover Storage Center version introduces support for automatic failover and recovery for Live Volumes. NOTE: Dell recommends that both Storage Centers are running the same version of Storage Center. NOTE: Live Volume with automatic failover is only supported with ESX 5.5 and 6.0. Also, this feature does not support using raw device mappings with ESX. Import Volumes From PS Series Storage Arrays Enterprise Manager version 2015 R2 and Storage Center version 6.7 support importing volumes from EqualLogic PS Series storage arrays. You can import volumes using the offline or online method. Offline import migrates a volume from the source to the destination. The volume must then be mapped to the server after the import. Online import creates a destination volume, maps it to the server, then migrates the data to the destination volume. NOTE: Online import supports only stand alone Windows Server 2008 R2 or later operating systems. Custom Profiles for Flash Optimized Storage Storage Center now supports Custom Profiles for Flash Optimized storage. User Interface Updates Storage Center 6.7 provides the following user interface enhancements to improve usability. Thin Import and External Device features are now managed using Storage Manager New volume Preallocate Storage configuration wizard Controller node indicator light added for SC8000 and SC9000 controllers Asset Tag configuration added for SC8000 and SC9000 controllers Additional dialog boxes and instructional messages that provide error recovery for anticipated issues 6 Storage Center 6.7 Release Notes

7 Storage Center Fixed s The following section summarizes the issues fixed in Storage Center 6.7. Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS SCOS SCOS SCOS SCOS SCOS SCOS An SSD with an endurance life that extends beyond February 2106 displays a premature end of endurance life. A storage system with SupportAssist enabled that is unable to successfully complete the sending of SupportAssist information might be unable to manage new drives or manually remove drives safely. Drives in the archived disk folder might count against the total number of managed drives in the storage system. After updating a storage system to Storage Center 6.7, the controllers might reset while processing the Link Configuration initialization step. Clickjacking vulnerability found on web server ports in Storage Center. On storage systems that only have spinning drives and have large volumes with a large number of new page writes, existing snapshots take a very long to expire. Updated the OpenSSL version on the Storage Center to OpenSSL 1.0.1u to address the following security vulnerabilities: CVE CVE CVE CVE CVE CVE CVE CVE CVE SCOS Addressed the following security vulnerabilities related to SSL 3.0 and TLS 1.0: CVE CVE SCOS SCOS SCOS SCOS SCOS-2658 Removing a port from a fault domain while a controller is down might result in storage system configuration issues. A single disk with failing I/Os might cause storage system-wide performance degradation. A controller might reset while setting up Live Volume protection. A controller might reset when the lock associated with a particular message type cannot be found. Due to variable timing conditions within the platform, messages can arrive out of order. A rare timing window in which rebalancing local ports at the same time as volume level operations (view volume creation, mapping/unmapping to a server, etc.) leads to the rebalance not completing. Storage Center 6.7 Release Notes 7

8 SCOS-2224 A storage system might fail to delete a replication when the QoS node is blocked and there is outstanding I/O. Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS In a dual-controller storage system, a license file conflict might cause the controllers to reboot. A Cisco UCS blade server running ESXi might fail to boot from SAN after updating the Storage Center software on a storage system. If a storage system is performing Data Progression on a large amount of data and fails to expire snapshots, a controller might reset and become stuck a in reset loop. Controllers might reset when creating multiple Live Volumes in parallel. A controller might reset during replication initialization. The Storage Center process might stop and fail to restart. This issue causes the Storage Center alert queue to fill up, which might cause a controller to reset. A storage system might enter emergency mode if it is unable to create page pool devices due to CA out of space errors. In a two controller storage system, the active controller might reset during failover after performing a Storage Center update on the peer controller. A controller might reset when removing an enclosure or reinserting a previously archived or deleted disk into the enclosure from which it was removed. When creating a Live Volume, choosing a destination volume that is mapped to a server might cause the Live Volume to go offline. This might cause other volumes that use Deduplication or Compression on the destination Storage Center to go offline. In rare instances, a storage system with Live Volumes might reset when multiple changes are made to the Fibre Channel switch configurations within a short time period. Fibre channel switch environment changes might generate fatal RISC pause errors on the front-end ports. A Fibre Channel port or controller might reset due to RISC pause errors on a QLogic 8 Gb Fibre Channel HBA. Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS Updating to Storage Center might cause an increase in BadRegionsPresent health code errors for drives. 8 Storage Center 6.7 Release Notes

9 Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS Data Progression might fail to move pages to tier 3 for volumes that are larger than 32 TB. If a specific history has multiple view volumes, Data Progression might fail to move pages for volumes that are smaller than 32 TB. Using Offloaded Data Transfer (ODX) in Hyper-V might result in degraded MPIO paths. A degraded extent that misses a write on an un-degraded spot may not move due to a healthcode. A storage system might incorrectly report snapshot bad pages when the system is low on memory. A controller might become stuck during the reboot process after rebooting the storage system to apply Storage Center software updates. A controller rebalance might take several minutes to complete while deactivating the history of a large volume (several TBs) if the storage system has space management snapshots. A storage system with compression running might experience incomplete cache flushes if the controllers reboot several times in a row. Chassis firmware updates might fail when updating an SC4020 storage system from Storage Center 6.6 to Storage Center 6.7. A 10 Gb iscsi I/O card is unable to receive data from an Oracle Linux server if the write command is 8,126,464 bytes or larger. A dual controller reset might occur due to a data overflow issue with a 10 Gb iscsi I/O card. A controller reset might occur because of high memory usage caused by login requests that take a long to time process during heavy I/O. SC8000 controllers with CHA3 cache cards might reset due to a reference to a no longer supported Storage Center subsystem. Creation of the first volume on a storage system with 7K drives might result in a false PagePool 7K Down alert condition. Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS SCOS Renewed the Java code signing certificate for Storage Center System Manager. Using Offloaded Data Transfer (ODX) in Hyper-V might result in degraded MPIO paths. Storage Center 6.7 Release Notes 9

10 Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS SCOS-7269 SCOS-3408 Storage Center memory might not be released properly when compression is enabled. On rare occasions during a RAID rebalance, a short timing window may occur where inaccurate pagepool information is read from the system resulting in volumes becoming inaccessible for a brief period. Incorrect SSD endurance tracker alerts might appear if duplicate endurance tracker entries are created. Unable to manage SED drives when running Gemalto SafeNet 8.4 and later. An SC4020 controller reset might occur because of a network broadcast loop. A dual controller reset might occur if a single volume is mapped to more than 10 local ports per controller. A dual controller reset might occur following the deletion of iscsi remote port configurations. A single controller storage system shows servers as partially connected when servers are connected using Fibre Channel. A controller reset might occur while modifying or deleting an iscsi fault domain. Storage Center UPS monitoring does not support newer UPS network cards. A controller reset might occur because of an issue with deduplication. VMotioning VMs to an SC4020 might cause the datastore to go offline. An error might occur in the Dell Storage Manager Client if the user preferences snapshot profile list is invalid. Deduplication and Compression might take volumes offline when responses to storage type status are incorrect. An CT-SC040 controller reset might occur due to an issue with the system profile size. Volume cleanup might not complete successfully when deleting all of the volumes on a Storage Center. Performing a RAID rebalance when attempting to remove an entire tier of disks might not complete properly. Setting the VLAN Priority to a value above 0 on a fault domain with a Chelsio T5 I/O card that is performing VLAN tagging will result in iscsi initiators that are unable to login. A controller reset might occur because of web server processes not end correctly over time. Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS Resolved an issue with the Secure Console command syntax. 10 Storage Center 6.7 Release Notes

11 Fixed s in Version The following table summarizes the issues fixed in Storage Center SCOS SCOS SCOS SCOS-9033 SCOS-8248 SCOS-7943 SCOS-7936 SCOS-7932 SCOS-7856 SCOS-7533 SCOS-3382 SCOS-2526 SCOS-2534 SCOS-2390 SCOS-1852 SCOS-1546 In rare cases, disabling compression a volume might cause the controllers to reboot. iscsi IO cards might report read errors for volumes that are mapped to an ESXi cluster. Enabling SNMP on a storage system might cause the SNMP agent to stop unexpectedly and the SNMP agent cannot be restarted. An SC4020 storage system might incorrectly create swap alerts. In a Windows 2012 R2 virtual machine running in ESXi 5.5 or Hyper-V on Windows Server 2012, an iscsi Offloaded Data Transfer (ODX) attempt is causing volume access to hang when the volumes are on different storage systems. A controller might reset if the iscsi initiator logs out from the target, but the initiator fails to terminate the connection. Security enhancement regarding Apache HTTPD and OpenSSL vulnerabilities. Adding a storage system to Enterprise Manager might fail if the storage system is licensed for SEDs, but it does not have any SED disks. Logging in to the Storage Center System Manager might time out when using Active Directory credentials. On a storage system with compression enabled, performance degradation might occur during the first few minutes of Data Progression because of table validation. A controller reset might occur when Secure Console is disabled from the Storage Center System Manager. After updating to Storage Center 6.6.5, a controller with iscsi IO cards might reset during a front-end rebalance, resulting in an outage. An iscsi IO card might send out an Address Resolution Protocol (ARP) request for IP on another network if it cannot find a gateway. In Storage Center or later, snapshot messages in system logs might contain an incorrect Position 3072 is past the expected bound error message. The Storage Center admin user does not receive an when a disk folder is close to being full. Fixed s in Version The following table summarizes the issues fixed in Storage Center CQ CQ CQ CQ CT-SC040 controllers may not display the correct memory allocation statistics and tracking levels or may provide inconsistent memory threshold data due to legacy memory allocation code. This issue may trigger event alerts for events that are not system critical. Storage Center 6.7 Release Notes 11

12 CQ CQ CQ CQ CQ CQ CQ CQ After updating to Storage Center version 6.7.4, Data Progression, Data Compression, and RAID Rebalance operations may stop working without warning. CT-SC040 controllers may issue event alerts and reset due to a system size memory allocation issue. Fixed s in Version The following table summarizes the issues fixed in Storage Center CQ Volumes utilizing the Data Compression feature may become inaccessible. Fixed s in Version The following table summarizes the issues fixed in Storage Center CQ CQ CQ CQ CQ CQ CQ CQ CQ For SC8000 and SC9000 controllers, Data Progression may experience latency due to compression threads utilizing a single socket instead of using both available sockets. After upgrading a controller, performing a Storage Center software update may cause performance issues due to improperly handled update file links. Phone Home may fail after updating from Storage Center versions 6.4 or 6.5 to Storage Center version 6.6 and later due to previous, pending requests that are unable to complete. A controller may reset and failover may be unsuccessful due to an iscsi IO cache card memory leak with iscsi attached Oracle and Linux servers. On rare occasions, Data Progression and subsequent rebalancing may fail due to snapshot full page memory limitations. A volume restripe operation with large amounts of compressed data may take an extended period of time to restripe due to Data Progression errors. For SC4020 controllers, an enclosure firmware update may fail due to missing electronically stored information (ESI) paths during installation. When performing a non-service affecting upgrade, upgrading from a CHA3 cache card to a 4GB Write cache card may cause the upgrade to fail due to card installation errors. On rare occasions, when performing a non-service affecting upgrade, a controller may reset due to duplicate or overlapping data writes. 12 Storage Center 6.7 Release Notes

13 Fixed s in Version The following summarizes the issues fixed in Storage Center CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ Web services under a sustained heavy workload may fail to restart resulting in a loss of access to the Storage Center management interface. Controllers may report increased memory usage due to improper release of sockets. A volume restripe operation with large amounts of compressed data may take an extended amount of time to restripe due to Data Progression errors. Security enhancement regarding the vulnerability CVE An SC4020 controller may reset if the incorrect version license file is applied. After a Storage Center software update, the SMTP service may not function properly due to ARP reply packet rejection. For SC9000 controllers, a controller reset may occur due to a failover error. A controller reset may occur due to a TCP connection LAST_ACK socket state error. For SC9000 controllers, an incorrect Storage Center Upgrade Required message displays during the login and on the About page. Disks may get a BadRegionsPresent health code during a rebuild, even when they are down, due to the multiple RIPExpired errors. Disks may get excessive health codes because RIPExpired issues codes on devices that are down. Deferred fabric events may lead to a controller reboot. On rare occasions, a controller may reset when referencing a NULL pointer on a JBOD lookup. Deleted iscsi remote replication connections may not be removed properly. Modifying data progression configurations may cause other Storage Profile changes. A controller reboot may occur when reconfiguring and/or deleting iscsi connections. A controller may reboot if an iscsi host sends a non-512 byte aligned first burst size when Immediate Data is enabled. A controller may reboot during data progression due to RAID 5 reporting the incorrect pointer during a disk failure. Disk drive status may be set to Unknown following an SC200/SC220 power event. A controller may reset during Live Volume migration and go into a read-only state due to a proxy error. An SC4020 BMC may hang when a serial cable is connected and an invalid character is used during the login process. Software upgrades may fail due to a watchdog timer timeout. During a software upgrade, a controller may fail due to a PreUpdateCheck ClearJobs call error. A local controller may reset, when creating and deleting portable volumes from a remote Storage Center, due to a double-queuing error if the request fails. Security vulnerability may occur because Secure Socket Layer (SSL) supports a weak cipher suite that uses an encryption algorithm with a short key length. For information, see support.microsoft.com/kb/ Storage Center 6.7 Release Notes 13

14 CQ CQ CQ CQ CQ Security vulnerability can occur due to a minor NTP vulnerability in processing remote configuration packets referenced in SA-15:07. Security: CVE , CVE , Security: CVE , CVE , Security: FreeBSD-SA-14:31.ntp. Enabling additional debug logging on iscsi IO cards may lead to server connectivity issues on other controller front-end ports. The Storage Center System Manager user interface does not allow Volume Manager privileged users to view volumes or replays on active volumes and issues an error message. On rare occasions, replacing a failed power supply in a dual-controller Storage Center causes both controllers to reboot. In rare cases, the CPU temperature monitor may cause a controller reboot. CQ Security vulnerabilities can occur on Apache servers due to implementing OpenSSL version 1.0. CQ CQ CQ CQ Data Progression may move active pages out of highest cost writable class. Upgrading from CT-SC040 controller to SC8000 controller may disable Phone Home and Secure Shell (SSH). A controller may fail to initialize after a software upgrade due to an SCUpdate API error. CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ CQ The Storage Center System Manager user interface does not provide a tier redundancy option and cannot be modified causing all tiers to default to dual-redundancy. An unplanned controller reboot may occur if one of the controller s system times is adjusted manually during the controller hardware upgrade process. After a nonservice affecting software upgrade, servers may not initialize because the wait time between upgrades on drives is too short, causing a backup of IOs and the server to abort IOs. A controller may reboot due to cache handling errors. SMTP service may become unresponsive. On rare occasions, replacing a failed power supply in a dual-controller Storage Center causes both controllers to reset. For SC4020 controllers, iscsi IO card drivers are hardcoded with an incorrect value. On rare occasions, the Storage Center System Manager user interface does not properly locate disks in the system and issues a warning. A controller may reset after a failover completes due to a port reset. Data Progression may not start when a volume creation operation does not complete properly. Replays may fail and volumes may become marked as secondary because of an API collision due to a server being deleted (or in the process of being deleted) and a UsageDesired configuration change. Asynchronous Replication may not resume after it is paused due to an incorrect variable attribute. Upgrading from CT-SC040 controller to SC8000 controller may cause a controller to fail because port objects set for cleanup are not deleted. IO latency issues could occur when a drive medium error is detected and the system incorrectly sets the current IO to a low recovery level. After a rebuild, drives may appear on a host controller and not appear on a peer controller until a reboot is performed. Intermittent IO latency may be present when Microsoft System Center Operations Manager polls Storage Center. In rare cases, a RAID device may not be degraded properly when a second write failure is reported for the same device. 14 Storage Center 6.7 Release Notes

15 Known s The following sections summarize the known issues that may affect Storage Center operations. Known Storage Center s The following table lists known issues in Storage Center 6.7. SCOS-6862 CQ SCOS-6821 CQ SCOS-6432 CQ CQ SCOS-6258 CQ CQ CQ SCOS-5446 CQ CQ In rare instances, the internal boot device on an SC9000 controller may become unusable following an unexpected power event and the controller will not boot. Workaround: Contact technical support. After performing an import from a PS Series storage array, Storage Center continues to attempt to log in to the target volume. These attempts cause multiple failure logs. Workaround: Delete the remote connection to the Storage Center. Then, configure another remote connection to the Storage Center. The status of a secondary Live Volume remains down after bringing the primary Storage Center back online. Workaround: The primary and secondary Storage Centers must be running the same version of Storage Center software. Bridgehead Software Integrated Serverless Backup (ISB), Integrated Disaster Recovery (IDR), and Healthcare Data Management (HDM) Solution for MEDITECH Scanning & Archiving (SCA) software products have a compatibility issue with Storage Center versions 6.6 and 6.7. Currently, Storage Center versions 6.6 and 6.7 will not work properly with these Bridgehead Software products. Workaround: Do not update to Storage Center versions 6.6 or 6.7 if the Bridgehead IDR/ISB applications are in use. For more information, see the Copilot Services Technical Alert: Bridgehead IDR/ISB for MEDITECH incompatibility with Storage Center Operating System version 6.6. In rare instances, SC4020 controllers may not initialize following a reset or controller power cycle. Workaround: The controller must be rebooted by performing a power cycle. After the controller is power cycled, the controller boots up successfully. In rare instances on SC4020 storage systems, failure LEDs may be illuminated for some drives in the chassis even though Storage Center reports the disks as up and healthy. Workaround: Verify the disk status in the Enterprise Manager or System Manager client. If the status is up and healthy, no action is required. If experiencing this issue, contact technical support. To clear this condition, a full system power cycle is required. A host server running Windows Server 2012 R2 that is connected to a Storage Center using iscsi may become partially connected to the Storage Center after a virtual port failover. Workaround: Configure the EnableNOPOut setting in the Windows Registry using the instructions in the Storage Center Microsoft Multipath I/O Best Practices guide on the Dell Tech Center website. If an isns server is defined incorrectly on the Storage Center or if the isns server is down, IO may be slightly degraded every 30 seconds. High traffic on a 1Gb PCIe iscsi IO card may cause connectivity issues. Storage Center 6.7 Release Notes 15

16 Known Vendor s The following table lists vendor issues found with Storage Center 6.7 CQ Storage Center servers running RedHat version 7.1 may experience resets. Workaround: Use the latest recommended version of RedHat. See the Dell Storage Compatibility Matrix. CQ Emulex OCx1410x iscsi adapters do not function correctly with Storage Center 6.7. Workaround: Do not use Emulex OCx1410x adapters until they are listed in the Dell Storage Compatibility Matrix. CQ CQ CQ CQ ESXi 5.x hosts with QxE82xx iscsi adapters using QLA4xxx driver version (ESXi 5.1) or (ESXi 5.5) might fail to log in to the Storage Center after a controller reset or failover. Workaround: Use the latest recommended driver version for the QLogic adapters. See the Dell Storage Compatibility Matrix. A Storage Center that is in virtual port mode and connected to a server running AIX version 6.1 or 7.1 may intermittently reset iscsi HBAs and cause the iscsi volumes to time out. Workaround: Do not configure Storage Center virtual port mode if AIX iscsi hosts will be connected. If a protected site is running Storage Center 6.x and the recovery site is running Storage Center 5.5 or earlier, ESX hosts at the recovery site fail to mount VMFS5 datastores and log the error: Host does not support ATS or ATS initialization has failed in the local vmkernel.log file. Workaround: Update the storage system running Storage Center 5.x to Storage Center 5.6 or 6.x. CQ CQ CQ Oracle Solaris 10 and 11 server iscsi connections fail during controller failover in Virtual Port mode. Workaround: Use Legacy Mode with Oracle 10 and 11 servers. On a storage system with iscsi front-end ports, if a controller or port is in a failover process when a Windows boot from SAN is requested, the boot might fail. Workaround: Subsequent boot from SAN requests succeed when the controller or port is up. Storage Center Update Information The following information must be considered before updating to Storage Center 6.7. NOTE: When performing an update of both the Storage Center and Enterprise Manager software, update Enterprise Manager before updating Storage Center. NOTE: When using Dell storage Software Suite for AIX, make sure you update to version or version before updating to Storage Center 6.7. Updating Software on Storage Center Controllers Storage Center 6.7 supports controller models SC9000, SC8000, SC4020, and CT-SC040. To update Storage Center: 16 Storage Center 6.7 Release Notes

17 The Storage Center must be running Storage Center or later to perform a Phone Home/SupportAssist update to Storage Center 6.7. This update may require network firewall changes to maintain the transition between Phone Home (Storage Center 6.5 and earlier) and SupportAssist (Storage Center 6.6 and later). See the Storage Center Pre-Deployment Tech Note for more information. When updating from Storage Center 6.0 or earlier to Storage Center 6.7, plan for a longer maintenance window and contact technical support if you need assistance. See the Storage Center Software Update Guide for more information. Contacting Dell Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services might not be available in your area. To contact Dell for sales, technical support, or customer service issues, go to For customized support, type your system service tag on the support page and click Submit. For general support, browse the product list on the support page and select your product Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Storage Center 6.7 Release Notes 17