Release Notes

Issue Description
SCOS-7943 A controller might reset if the iSCSI initiator logs out from the target, but the initiator fails to terminate
the connection.
SCOS-6420 An SCv2000 series controller reset might occur due to an incorrect front-end SAS I/O card critical
temperature alert.
SCOS-6338 Storage Center UPS monitoring does not support newer UPS network cards.
SCOS-3400 The embedded iSCSI ports on an SCv2080 series storage system might reset on configurations
where there is congestion at the initiator, causing flow control back to the storage system.
SCOS-2570 In rare instances, a RAID device might not be degraded properly when a second write failure is
reported for the same device.
SCOS-2548 An SC9000 controller might reset due to an issue during controller failover.
SCOS-2534 After updating to Storage Center 6.6.5 a controller with iSCSI I/O cards might reset during a front-
end rebalance, resulting in an outage.
SCOS-2390 An iSCSI I/O card might send out an Address Resolution Protocol (ARP) request for IP on another
network if it cannot find a gateway.
SCOS-2386 A controller might reset if an iSCSI host sends a non-512 byte aligned first burst size when Immediate
Data is enabled.
SCOS-2098 Performing a non-service affecting upgrade from a CHA3 cache card to a 4 GB Write cache card
might cause the upgrade to fail due to card installation errors.
SCOS-1476 A controller might reset and fail-over might be unsuccessful due to an iSCSI I/O cache card memory
leak with iSCSI attached Oracle and Linux servers.
SCOS-1408 If TCP RX fragmentation is enabled on iSCSI I/O cards, the card might enter and exit hibernation
mode, causing replications to fail.
SCOS-1380 In rare instances, a single-disk predictive failure might cause high latency because of long disk
recovery during I/O.
SCOS-684 A short duration AC line brownout on an SCv2000 series or SC4020 storage system might cause
unnecessary controller failover.
SCOS-208 Disks might get a BadRegionsPresent health code during a rebuild, even when they are down, due to
the multiple RIPExpired errors.
SCOS-206 Disks might get excessive health codes because of RIPExpired issues codes on devices that are down.
Fixed Issues Related to Replication and Live Volume
The following issues are fixed in Storage Center 7.1:
Table 13. Fixed Replication and Live Volume Issues in
Storage Center 7.1.20
Issue Description
SCOS-36665 A controller reset might occur while attempting to fail over a Windows cluster on an RDM volume
mapped to non-unified ESXi hosts when using Live Volume High Consistency.
SCOS-35656 Live Volume proxy disk space might be counted towards the total available system disk space.
SCOS-32134 Access to a volume might be lost if out of memory errors occur before the replication enters the
suspending state.
SCOS-7793 A storage system might fail to delete a replication when the QoS node is blocked and there is
outstanding I/O.
Table 14. Fixed Replication and Live Volume Issues in Storage Center 7.1.12
Issue Description
SCOS-22156 The VVols feature in ESXi 6.0 Update 2 fails to work properly with Storage Center 7.1.2.
SCOS-21399 A controller might reset during cross-platform replication initialization with a PS Series array.
14 Dell Storage Center 7.1 Release Notes