SFA OS Release 1.4.1 SFA™ OS Version 1.5.3.
Important Information Information in this document is subject to change without notice and does not represent a commitment on the part of DataDirect Networks, Inc. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of DataDirect Networks, Inc. © 2012 DataDirect Networks, Inc. All rights reserved.
TABLE OF CONTENTS 1.0 OVERVIEW .................................................................................................................................................... 4 2.0 INSTALLATION ............................................................................................................................................. 4 2.1 Overview ...........................................................................................................................................................
1.0 Overview This document applies to the SFA OS version 1.5.3.0-12955 release for DataDirect Networks’ SFA12K-40, SFA12K-20, SFA12K-20E, SFA10K-X, and S2A6620 storage systems. It details upgrade procedures, enhancements, resolved issues, known issues with workarounds, and recommended practices associated with these SFA OS firmware updates: • SFA12Ks from version 1.5.2.1 to 1.5.3.0 • SFA10Ks from version 1.5.1.4 to 1.5.3.0 • S2A6620s from version 1.5.1.1 to 1.5.3.0 • SFA12K-20Es from version 1.5.1.
2.4 Pre-Firmware-Upgrade Procedure 2.4.1 SFA12K-40, SFA12K-20, and SFA12K-20E NOTE: Before upgrading SFA OS on an SFA12K system, please read this section carefully. SFA OS 1.5.3.0 has a feature that will upgrade the SFA12K Baseboard Management Controller (BMC) firmware version automatically as part of the SFA OS upgrade. The automatic update will only function with SFA12K BMC versions newer than 21.54. Prior to upgrading to 1.5.3.0, please identify your current BMC version and then check these notes: 1.
Issue 'SHOW ENCLOSURE ALL' to identify your current BMC version. For example, see Figure 2.
The highlighted entries from the example log in Figure 4 show the entries that indicate the progress of the battery hardware revision upgrade. . . . 441545 2012-12-13 17:55:46:2937039 G=56 S=0 T=1 RP=0 VP=00 LOG_ES_ENCL_UPS_INFO ES UPS for controller 0x15b2a1dc5c0000 changed state SES status = 2, disabled = 0, charge = 91%, hold-up time = 17 min.
2.5 Post-Firmware-Upgrade Procedure 2.5.1 SFA12K-40, SFA12K-20, SFA12K-20E, and SFA10K After upgrading the firmware, perform these steps to initialize the battery life remaining feature: 1. Issue the command, SHOW UPS * ALL_ATTRIBUTES. 2. If you see a date in “Battery Mfg. Date”, do nothing more. 3. If you see the message shown in Figure 5, then issue the command, CLEAR CONTROLLER x UPS_HISTORY, where “x” is either “local” or “remote” depending on which UPS needs to be cleared. Battery Mfg.
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. 4.0 • 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.
• On S2A6620s the Li-Ion battery bounced between state before it worked properly. DE5129 • The Li-Ion firmware upgrade on an S2A6620 would not attempt to upgrade the battery’s firmware if the battery pack is failed even if a firmware upgrade is required to return it to service. DE5205 • When the Li Ion battery on the S2A6620 was in ROM mode due to a failed firmware upgrade, the battery would be reported missing.
• If stack commands (CLI commands starting with 'app') are issued shortly after rebooting a controller, you may encounter communication errors displayed in the CLI, and failure of the attempted commands. Errors may include: o Long delays followed by: Communication connection failed for this command o Or this message: ASM initialization in progress Suggested Work Around o After the failed controller comes back up, do not immediately issue any CLI commands besides "show controller".
5.2 SFA12K-20E On SFA12K-20E systems, if you choose to use the enhanced VM network management (SR-IOV), there is a problem which prevents binding the app IOC associated with the second physical interface on the SFA controller. If you bind the second interface, the VM may fail to start properly.
• • In an InfiniBand switch environment running RHEL 5.7, if a cable is pulled from either an initiator or a target, a failover occurs as expected; however, once the connection is reestablished, it does not fail back to the original controller. o In order to resolve this issue, you must issue the command, # udevtrigger. o The Linux man pages state that the command will simply “request kernel devices events for coldplug”.
5.7 Red Hat 6.2 This section applies to the SFA12K-40, SFA12K-20, SFA10K-X, SFA10K-M, and S2A6620. • • • • Updating the kernel and multipath packages to the latest version is recommended. As of this release, DDN qualified versions include: o the kernel version - 2.6.32-279.2.1.el6.x86_64 o the multipath version - 0.4.9-56.el6_3.1.x86_64. The kernel modules that come with OFED 1.5.4 will cause I/O threads to hang when the data path between the controller and switch is lost.
6.0 Recommended Practices The recommended best practices for the SFA12K-40, SFA12K-20, SFA12K-20E, SFA10K-X, SFA10K-M, and S2A6620 with SFA OS version 1.5.3.0 include: • SS6000 DEM and I/O module replacement. For SS6000 DEM and I/O module replacement, see the SFA OS User Guide for the procedures. • Reduce host I/O load during background initializations. When a storage pool is in the process of being initialized, a significant internal I/O load is generated.
8.0 Support To submit debug information to DDN, use the diag tgz command. Diag is a captive account on SFA OS systems that is used for performing operations on a controller when there’s no CLI access or the CLI isn’t appropriate. Perform diag operations by using ssh to login to the diag account. The command syntax is: ssh diag@xxx.xxx.xxx.xxx diag-command (where xxx.xxx.xxx.xxx is the controller’s IP address and diag-commands are listed in Table 1.
World Headquarters 9351 Deering Avenue • Chatsworth, CA 91311 ddn.com Phone: +1.818.700.7600 Fax: +1.818.700.
