User guide

DataDirect Networks SFA™ OS 1.5.3.0 Release Notes Revision B | 9
3.0 Enhancements
SFA OS Version 1.5.3.0 adds no enhancements. For enhancements added by product, see
the release notes versions given below.
• For SFA12K-40 and SFA12K-20, see the 1.5.2.1 release notes.
• For SFA12K-20E, see the 1.5.1.3 and 1.5.2.2 release notes.
• For the SFA10K, see the 1.5.1.4 release notes.
• For the S2A6620, see the 1.5.1.1 release notes.
• Added support for SFA12K-20E configurations with 1-4 SS7000 enclosures and 1
SS8460 enclosure.
4.0 Resolved Issues
These issues have been resolved since the previous SFA OS release.
• SFA OS version 1.5.2.1 introduced a new performance modification used
exclusively by SFA12K-20E systems called Full Stripe Write optimization. An
issue has been corrected where a drive disappears and its internal partial rebuild
bitmap for the drive is not updated. This could lead to some stripes not being
rebuilt when the missing drive reappears.
• For SFA12Ks the automatic BMC upgrade would force the BMC to version 21.61
even if the BMC was running a later version. DE4628
• For SFA12Ks in certain situations, when starting the controller, the controller
may fail to start one or more virtual machines. The virtual machines that do start
may not come up properly. When you try to query the state of the stacks using
CLI, you may see messages like "Controller 1 has not received controller 1 CPLD
data".
• There was an issue that resulted in double free when a Qlogic command is
terminated because the port reset state was not cleared for odd ports on SFA10K
and S2A6620 systems. DE2962
• There was an issue that caused SFA12K controllers to reboot and report a lot of
temperature sensor errors by both controllers. DE4173
• A Li-Ion battery cell deterioration warning put the system into write-thru
mode.DE4185
• For disk channels that are not connected and not supposed to be connected
(such as in the SFA12K-20), the GUI would indicate these channels were faulted.
DE4502
• On E platforms, issuing a “start stack” to an already running VM would stop and
restart that stack. DE4510
• Imported initiator status was not being saved correctly and this caused the
display to be incorrect in SHOW INITIATORS and SHOW HOSTS. DE4869
• Upgrading to the latest Ethernet driver corrected a problem where hardware
detection didn’t always work on S2A6620s. DE4883
• On SFA10Ks, e-mails notifications received from SFA OS contained spurious
characters at the end of the event. DE4970
• The SNMP agent inside the SFA controller would leave connections open. This
would result in the CLI not being able to connect as the connections were not
freed correctly and could also result in a controller crash. DE4911
• On S2A6620s Li-Ion battery faults resulted in many unnecessary log entries.
DE5128