S2A6620 User GuideV1.2

Silicon Storage Appliance S2A6620 (SFA OS Version 1.
2) User Guide
Rev C
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 purchasers personal use without the written permission of DataDirect Networks, Inc. 2009 DataDirect Networks, Inc. All rights reserved. DataDirect Networks, the DataDirect Networks logo, and Silicon Storage Appliance are trademarks of DataDirect Networks, Inc. All other brand and product names are trademarks of their respective holders. DataDirect Networks Licensor(s) makes no warranties, express or implied, including without limitation the implied warranties of merchantability and fitness for a particular purpose, regarding the software. DataDirect Networks Licensor(s) does not warrant, guarantee or make any representations regarding the use or the results of the use of the software in terms of its correctness, accuracy, reliability, currentness, or otherwise. The entire risk as to the results and performance of the software is assumed by you. The exclusion of implied warranties is not permitted by some jurisdictions. The above exclusion may not apply to you. In no event will DataDirect Networks Licensor(s), and their directors, officers, employees, or agents (collectively DataDirect Networks Licensors) be liable to you for any consequential, incidental, or indirect damages (including damages for loss of business profits, business interruption, loss of business information, and the like) arising out of the use or inability to use the software even if DataDirect Networks Licensor has been advised of the possibility of such damages. Because some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitations may not apply to you. DataDirect Networks Licensors liability to you for actual damages from any cause whatsoever, and regardless of the form of the action (whether in contract, tort (including negligence), product liability or otherwise), will be limited to $50.
Printed in the USA December 2009 Document Number 96-30040-001 Rev C
S2A6620 User Guide (Rev C)
ii
STANDARD WARRANTY Definitions: This two-year limited warranty applies to the following DataDirect Networks network infrastructure and individual SAN solution components that include: Silicon Storage Appliance Hardware, Drive Modules, RAID Hardware Components, Storage Hardware Components, and Disk Drive Docking Bays and Enclosures (hereinafter DataDirect Networks Products). Fibre Channel Interface Kits, SCSI Interface Kits, Host Adapters and Networking Products are limited to a 90-day warranty. Software bundled or included with DataDirect Networks solutions are furnished exclusively under the terms of the applicable license agreements. Warranty: DataDirect Networks warrants that the DataDirect Networks Products accompanied by this limited Warranty are free from defects in material and workmanship for a period of two years from the date of original purchase from DataDirect Networks or an authorized DataDirect Networks reseller. During the term of this Warranty, DataDirect Networks will, at its option, repair or replace any defective parts of the DataDirect Networks products purchased under this Warranty at no additional charge. Repair parts or replacement DataDirect Networks products will be furnished on an exchange basis, and will be either reconditioned or new. When returning the DataDirect Networks products, the Purchaser must prepay any shipping charges. In addition, the Purchaser is responsible for insuring the products returned and assumes the risk of loss during shipment. Warranty Claim Requirements: Purchaser claims made pursuant to this Warranty must conform to the following requirements: 1. The DataDirect Networks products must be returned to (a) an Authorized DataDirect Networks Servicing Reseller in the country of original purchase, or (b) a DataDirect Networks facility which performs Warranty service in the country of original purchase, or (c) an Authorized DataDirect Networks Third Party Service Provider in the country of original purchase. 2. The Purchaser must provide proof of purchase and date of purchase from DataDirect Networks or an Authorized DataDirect Networks Reseller. 3. The Purchaser may request information on how to obtain warranty service by contacting any Authorized DataDirect Networks Reseller, or by writing to the Warranty Service Department, DataDirect Networks, 9351 Deering Avenue, Chatsworth, CA 91311. Disclaimers: THIS LIMITED WARRANTY DOES NOT APPLY TO ANY DATADIRECT NETWORKS PRODUCTS WHICH HAVE BEEN DAMAGED OR RENDERED DEFECTIVE (a) AS A RESULT OF ACCIDENT, MISUSE, OR ABUSE; (b) BY THE USE OF PARTS NOT MANUFACTURED OR SOLD BY DATADIRECT NETWORKS; (c) BY MODIFICATION WITHOUT THE WRITTEN PERMISSION OF DATADIRECT NETWORKS, OR (d) AS A RESULT OF SERVICE BY ANYONE OTHER THAN DATADIRECT NETWORKS, AN AUTHORIZED DATADIRECT NETWORKS SERVICING RESELLER, OR AN AUTHORIZED DATADIRECT NETWORKS THIRD PARTY SERVICE PROVIDER. EXCEPT AS EXPRESSLY SET FORTH ABOVE, DATADIRECT NETWORKS MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR PURPOSE, AND DATADIRECT NETWORKS EXPRESSLY DISCLAIMS ALL WARRANTIES NOT STATED HEREIN. IN THE EVENT THE PRODUCTS ARE NOT FREE FROM DEFECTS AS WARRANTED ABOVE, THE PURCHASER'S SOLE REMEDY SHALL BE REPAIR OR REPLACEMENT AS PROVIDED ABOVE. UNDER NO CIRCUMSTANCES WILL DATADIRECT NETWORKS BE LIABLE TO THE PURCHASER, OR TO ANY USER, FOR ANY DAMAGES, EXPENSES, LOST PROFITS, LOST SAVINGS, DAMAGE TO OR REPLACEMENT OF EQUIPMENT AND PROPERTY, COSTS OF RECOVERING, REPROGRAMMING, OR REPRODUCING ANY PROGRAM OR DATA STORED IN OR USED WITH THE PRODUCTS, OR OTHER DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE DATADIRECT NETWORKS PRODUCTS. ANY IMPLIED WARRANTIES ARE LIMITED TO THE TERMS OF THIS EXPRESS LIMITED WARRANTY. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES FOR CONSUMER PRODUCTS, AND SOME STATES DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE.
iii
DataDirect Networks END-USER LICENSE AGREEMENT for SILICON STORAGE APPLIANCE SOFTWARE AND/OR FIRMWARE IMPORTANT - READ CAREFULLY
This End User Software License Agreement (this "EULA") is a legal agreement between you, the individual or entity that has agreed to pay for the rights granted herein ("Licensee"), and DataDirect Networks, Inc., a California corporation (DDN). This EULA governs Licensee's possession and use of the Software and the Documentation (each as defined below).
BY CHECKING AND/OR CLICKING I ACCEPT OR A SIMILAR BOX OR BUTTON ASSOCIATED WITH THIS EULA AT THE BEGINNING OF THE SOFTWARE DOWNLOAD, INSTALLATION, OR ACTIVATION PROCESS, BY INSTALLING ANY OF THE SOFTWARE, BY ACTIVATING ANY OF THE SOFTWARE WITH ANY ASSOCIATED LICENSE KEY, OR BY USING ANY OF THE SOFTWARE, LICENSEE AGREES TO ALL OF THE TERMS AND CONDITIONS IN THIS EULA. IF LICENSEE DOES NOT AGREE TO ALL OF THE TERMS AND CONDITIONS IN THIS EULA, LICENSEE MUST NOT INSTALL, ACTIVATE, OR USE ANY OF THE SOFTWARE, AND LICENSEE MUST NOT CHECK AND/OR CLICK I ACCEPT OR ANY SIMILAR BOX OR BUTTON ASSOCIATED WITH THIS EULA DURING THE SOFTWARE DOWNLOAD, INSTALLATION, OR ACTIVATION PROCESS. IF LICENSEE DOES NOT AGREE TO ALL OF THE TERMS AND CONDITIONS IN THIS EULA, LICENSEE MAY RETURN THE UNUSED SOFTWARE FOR A FULL REFUND, PROVIDED THAT LICENSEE'S RIGHT TO RETURN THE UNUSED SOFTWARE FOR A FULL REFUND EXPIRES THIRTY (30) DAYS AFTER THE PURCHASE OF THE SOFTWARE FROM DDN OR A DDN-AUTHORIZED RESELLER OR DISTRIBUTOR, AND APPLIES ONLY IF LICENSEE IS THE ORIGINAL END USER PURCHASER.
1.
DEFINITIONS. As used herein, the following terms shall have the following meanings:
1.1. Documentation means any and all end user documentation provided by DDN in connection with the Software, and all Updates thereto. 1.2. Factory Installed Software means Software that is installed by DDN on a DDN hardware product prior to delivery of that DDN hardware product to Licensee, and all Updates thereto. Factory Installed Software may include, without limitation, S2A firmware, DirectOS, DirectMon, and certain third party file server programs. 1.3. GPL Software refers to certain open source software that DDN may provide to Licensee in connection with a DDN hardware product, including but not limited to the Linux software provided by DDN in connection with the S2A6620. GPL Software is provided by DDN to Licensee solely under the terms of the GNU General Public License, Version 2, June 1991 (the GNU GPL), a copy of which accompanies this Agreement. Consistent with the requirements of the GNU GPL, DDN will provide a complete machine-readable copy of the source code for GPL Software for a charge of no more than DDN's cost of physically performing such distribution, provided that such copy is requested within three (3) years following Licensee's receipt of the corresponding GPL Software from DDN. 1.4. Remote Software means Software that is meant to be installed on Licensee's own hardware and that is not installed by DDN or a DDN reseller on a DDN hardware product prior to delivery of that DDN hardware product to Licensee, and all Updates thereto. Remote Software may include, without limitation, DDN's GUI program. 1.5. Software means all software and firmware that accompanies this EULA, all copies thereof, all media associated therewith, and all Updates thereto; provided that the term Software does mean any software or other materials for which a separate end user license agreement is provided (including but not limited to the GPL Software). 1.6. Updates means any and all updates, upgrades, new releases, modifications, and/or supplements that may be provided by DDN from time to time, whether through an online download process or otherwise. 1.7. Use means to install, store, load, execute, and display one copy of the Software on one device at a time for Licensee's internal business purposes.
2.
LICENSE GRANTS.
2.1. Software. Subject to all terms and conditions in this EULA, DDN hereby grants to Licensee a limited, revocable, non exclusive, non sublicenseable license to: (a) Use Factory Installed Software, only in object code form, and only on the DDN hardware products that are purchased by Licensee and that contain such software when first delivered to Licensee, provided that Licensee may not Use Factory Installed
iv
Software in connection with any storage media (e.g., disk drives) or storage media enclosures that were not purchased from DDN, and provided further that (i) S2A firmware may only be used with the number of S2A ports (if any) specified in the corresponding invoice;
(ii) S2A firmware may only be used with the amount of disk storage (if any) specified in the corresponding invoice; and (iii) the RAID 6, SATAssure, and/or Sleep Mode functionality contained in the S2A firmware may not be used unless specified in the corresponding invoice. (b) Use Remote Software, only in object code form, and only on the number of Licensee computers for which Licensee has purchased a license (as specified in the corresponding invoice); and (c) make one copy of the Software, only in object code form, and Use that copy only for backup and archival purposes. 2.2. Documentation. Subject to all terms and conditions in this EULA, DDN hereby grants to Licensee a limited, revocable, non-exclusive, non-sublicenseable license to copy and use the Documentation to the limited extent reasonably necessary to support Licensee's permissible Use of the Software. 3. OWNERSHIP. Licensee acknowledges and agrees that DDN, its suppliers, and/or its licensors, as applicable, own and shall retain all rights, title, and interest in and to the Software and the Documentation, including but not limited to all patents, trademarks, trade names, inventions, copyrights, know how, trade secrets, and other intellectual and industrial property rights (and any corresponding applications or registrations) related to the Software or the Documentation. DDN's suppliers and licensors are intended beneficiaries under this EULA and independently may protect their rights in the Software and the Documentation in the event of any infringement or breach of this EULA. 4. RESERVATION OF RIGHTS. Licensee acknowledges and agrees that the Software and the Documentation have been licensed to Licensee pursuant to the terms and conditions of this EULA, and that the Software and the Documentation have not been sold to Licensee. DDN and its suppliers and licensors reserve all rights not expressly granted herein. Licensee shall not use or copy the Software or the Documentation except as is expressly authorized in this EULA. Licensee acknowledges and agrees that the Software and the Documentation are protected by United States copyright laws and international treaty provisions. Except as otherwise expressly provided herein, Licensee must treat the Software and the Documentation like any other copyrighted material. Licensee shall not knowingly take any action that would cause the Software or the Documentation to be placed in the public domain. 5. RESTRICTIONS.
5.1. Usage Restrictions. Licensee shall not permit any person other than Licensee's employees and authorized agents to possess or use the Software or the Documentation, and Licensee shall cause all such employees and authorized agents to abide by all terms and conditions imposed upon Licensee herein. Licensee may not exceed the number of licenses, agents, tiers, nodes, seats, or other Use restrictions or authorizations agreed to and paid for by Licensee. Licensee shall not use the Software to operate nuclear facilities, life support, or any other mission critical application where human life or property may be at stake, and Licensee understands that the Software is not designed for such purposes and that its failure in such cases could lead to death, personal injury, or severe property or environmental damage for which DDN and its suppliers and licensors are not responsible. Some Software may require license keys or contain other technical protection measures. Licensee acknowledges that DDN may monitor Licensee's compliance with Use restrictions and authorizations, remotely or otherwise. If DDN makes a license management program available which records and reports Software usage information, Licensee agrees to appropriately install, configure, and execute such license management program beginning no later than one hundred and eighty (180) days from the date it is made available to Licensee and continuing for the period that the Software is used. 5.2. No Transfer. Licensee may not, and agrees that it will not, transfer, assign, rent, lease, lend, resell, or in any way distribute or transfer the Software or the Documentation (or any rights in this EULA, the Software, or the Documentation) to any third parties, including by operation of law, without DDN's prior written approval, payment to DDN of any applicable fees, and compliance with applicable third party terms. Upon any approved transfer of this EULA, Licensee's rights hereunder will terminate and Licensee will immediately deliver the Software, the Documentation, and all copies thereof to the transferee. The transferee must agree in writing to the terms of this EULA and, upon such agreement, the transferee will be considered the Licensee for purposes of this EULA. Licensee may transfer Factory Installed Software only upon transfer of the associated DDN hardware product. 5.3. No Reverse Engineering; No Modification. To the maximum extent permitted by applicable law, Licensee shall not reverse engineer, disassemble, decrypt, or decompile the Software, or otherwise attempt to discover, reconstruct, or identify the source code for the Software or any user interface techniques, algorithms, logic, protocols, or specifications included, incorporated, or implemented therein. Furthermore, to the maximum extent permitted by applicable law, Licensee shall not modify, port, or translate the Software or the Documentation. Where Licensee has other rights with respect to the Software or the Documentation mandated under statute, Licensee will provide DDN with reasonably detailed information regarding any intended modifications, porting, translations, reverse engineering, disassembly, decryption, or decompilation, and the purposes therefore. 5.4. Proprietary Notices and Legends. If Licensee makes any copies of the Software or the Documentation in accordance with this EULA, Licensee must reproduce in all such copies all proprietary notices and legends contained in the originals.
5.5. Updates. Upon Licensee's installation of any Update to Software, Licensee shall have no further rights, and DDN shall have no further obligations, with respect to those portions of the Software that such Update was intended to replace. If additional or different license terms or conditions accompany an Update, Licensee acknowledges and agrees that Licensee's Use of that Update will be subject to those additional or different terms and conditions. 5.6. Export Restrictions; Compliance with Laws. Licensee agrees that Licensee will not, directly or indirectly, export or transmit the Software or the Documentation to any country, entity, or person to which such export or transmission is restricted by any applicable government regulation or statute without the prior written consent, if required, of the governmental entity as may have jurisdiction over such export or transmission. Licensee agrees to comply with and conform to all applicable laws, regulations, and ordinances relating to Licensee's use of the Software and/or the Documentation. 6. RESPONSIBILITIES OF LICENSEE.
6.1. Payment. In consideration for the licenses and rights granted to Licensee herein, Licensee agrees to pay all amount(s) for such licenses and rights as set forth in the corresponding invoice, in accordance with the payment terms agreed upon by Licensee. 6.2. Indemnification. Licensee hereby agrees to indemnify, protect, defend, and hold DDN and its licensors harmless from and against any and all claims, losses, or damages (including but not limited to reasonable attorneys' and experts' fees) attributable to (a) Licensee's use or misuse of the Software or the Documentation, or (b) any failure by Licensee to comply with any term, condition, or restriction in this EULA. 7. COMPLIANCE AUDIT. DDN shall have the right, upon reasonable notice, to conduct and/or have an independent accounting firm conduct, during normal business hours on Licensee's premises under Licensee's reasonable supervision, an audit to verify Licensee's compliance with the terms of this EULA. If an audit reveals underpayments, then Licensee will immediately pay DDN such underpayments together with the costs reasonably incurred by DDN in connection with the audit and seeking compliance with this section. 8. USE OF LICENSEE INFORMATION. With respect to any information Licensee provides to DDN in connection with the Software or the Documentation, DDN may use such information for any purpose without restriction, including, without limitation, for product support and development purposes, provided that DDN will not use such information in a form that identifies Licensee. 9. TERM AND TERMINATION.
9.1. General. Except as provided below with respect to evaluation and limited term licenses, this EULA and the license(s) granted herein will remain effective until terminated. Licensee may terminate this EULA and the licenses granted herein by ceasing all use of the Software and the Documentation, and returning all copies of the Software and the Documentation to DDN. This EULA (including but not limited to the licenses granted to Licensee herein) will automatically terminate if Licensee fails to comply with any term or condition of this EULA. 9.2. Evaluation and Term Licenses. If the Software and the Documentation have been licensed to Licensee for evaluation purposes, this EULA will be effective only until the end of the designated evaluation period. If the Software and the Documentation have been licensed to Licensee for a limited term as specified in the applicable sales acknowledgement, invoice, or otherwise, then this EULA will be effective only until the end of such term. Software that is subject to any evaluation or limited term license may contain code that can disable most or all of the features of such software upon expiration of such evaluation or limited term license, and unless Licensee has paid the applicable license fee for any additional licenses, Licensee shall have no rights to use such Software or the corresponding Documentation upon expiration of any such license. 9.3. Obligations Upon Termination or Expiration. Licensee agrees, upon any termination or expiration of this EULA, to cease use of, and to destroy or return to DDN, all copies of the Software and the Documentation. At DDN's request, Licensee will certify in writing to DDN that Licensee has complied with these requirements. Notwithstanding anything in this EULA to the contrary, Sections 1, 3, 4, 5.3, 5.6, 6, 7, 8, 9, 10.2, 10.3, 11, 12, and 13 of this EULA shall survive any expiration or termination of this EULA and continue in perpetuity. 10. LIMITED WARRANTY; DISCLAIMER; LIMITATION OF LIABILITY.
10.1. Limited Warranty. DDN warrants only to the original Licensee that, for a period of ninety (90) days following DDN's initial shipment of Software (and not Updates thereto) to such Licensee, such Software, as delivered to such Licensee, will substantially conform to the corresponding Documentation. Licensee's sole and exclusive remedy, and DDN's entire liability, under this warranty is for DDN to use commercially reasonable efforts to cause the defective or malfunctioning Software to substantially conform to the corresponding Documentation. Notwithstanding the foregoing, DDN will have no liability for any defective or malfunctioning Software under this Section 10.1 if (a) Licensee fails to notify DDN of the defect or malfunction during the Warranty Period, or (b) the defect or malfunction is caused by (i) use of such Software in combination with any hardware or other software that has not been approved in writing by DDN, (ii) the negligence or fault of Licensee or a third party, (iii) Licensee's failure to follow the instructions set forth in the corresponding Documentation, or (iv) modifications to that Software made by any person other than DDN or an authorized representative of DDN.
vi
10.2. Disclaimer. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EXCEPT AS EXPRESSLY SET FORTH IN SECTION 10.1 ABOVE, THE SOFTWARE AND THE DOCUMENTATION ARE PROVIDED AS IS, AND DDN AND ITS SUPPLIERS AND LICENSORS DO NOT MAKE AND SPECIFICALLY DISCLAIM ALL EXPRESS AND IMPLIED WARRANTIES OF EVERY KIND RELATING TO THE SOFTWARE, THE DOCUMENTATION, AND/OR USE OF THE SOFTWARE OR THE DOCUMENTATION (INCLUDING, WITHOUT LIMITATION, ACTUAL AND IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT), AS WELL AS ANY WARRANTIES THAT THE SOFTWARE OR THE DOCUMENTATION (OR ANY ELEMENTS OF EITHER) WILL ACHIEVE A PARTICULAR RESULT, OR WILL BE UNINTERRUPTED OR ERROR FREE. 10.3. Limitation of Liability. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL DDN OR ITS SUPPLIERS OR LICENSORS BE LIABLE UNDER ANY THEORY OF LIABILITY FOR ANY CONSEQUENTIAL, INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, OR EXEMPLARY DAMAGES OF ANY KIND (INCLUDING, WITHOUT LIMITATION, DAMAGES ARISING FROM LOSS OF PROFITS, REVENUE, DATA, OR USE, OR FROM INTERRUPTED COMMUNICATIONS OR DAMAGED DATA, OR FROM ANY DEFECT OR ERROR, OR IN CONNECTION WITH LICENSEE'S ACQUISITION OF SUBSTITUTE GOODS OR SERVICES OR MALFUNCTION OF THE SOFTWARE, OR ANY SUCH DAMAGES ARISING FROM BREACH OF CONTRACT OR WARRANTY OR FROM NEGLIGENCE OR STRICT LIABILITY) IN CONNECTION WITH THIS EULA, THE SOFTWARE, THE DOCUMENTATION, AND/OR ANY USE OF THE SOFTWARE OR THE DOCUMENTATION, EVEN IF DDN OR ANY OF ITS SUPPLIERS OR LICENSORS OR ANY OTHER PERSON HAS BEEN ADVISED OR SHOULD KNOW OF THE POSSIBILITY OF SUCH DAMAGES, AND NOTWITHSTANDING THE FAILURE OF ANY REMEDY TO ACHIEVE ITS INTENDED PURPOSE. WITHOUT LIMITING THE FOREGOING, DDN'S MAXIMUM AGGREGATE LIABILITY IN CONNECTION WITH THIS EULA, THE SOFTWARE, THE DOCUMENTATION, AND/OR USE OF THE SOFTWARE OR THE DOCUMENTATION SHALL NOT EXCEED THE TOTAL AMOUNT OF ANY LICENSE FEES AND/OR MAINTENANCE FEES PAID BY LICENSEE IN CONNECTION WITH THE SOFTWARE. 11. U.S. GOVERNMENT RESTRICTED RIGHTS.
11.1. Commercial Software. The Software and the Documentation are deemed to be commercial computer software and commercial computer software documentation, respectively, for purposes of Federal Acquisition Regulations (FAR) 12.212 and the Defense FAR Supplement (DFARS) 227.7202-1, 227.7202-3, and 227.7202-4, and the restrictions set forth in such regulations, and this EULA shall be deemed to be the license described in such regulations. Any use, modification, reproduction, release, performance, display, or disclosure of the Software or the Documentation by any agency, department, or entity of the United States Government (the Government) shall be governed solely by the terms of this EULA and is prohibited except to the extent expressly permitted by the terms of this EULA. The Software and the Documentation are also deemed to be restricted computer software for purposes of FAR 52.227-14(g)(3) (Alternate III (June 1987)) and FAR 52.227-19, which clauses are incorporated herein by reference subject to the express restrictions and prohibitions set forth above. 11.2. Certain Technical Data. Any technical data provided by DDN in connection with the Software or the Documentation that is not covered by the above provisions is deemed to be technical information related to commercial computer software or commercial computer software documentation for purposes of FAR 12.212 and the restrictions set forth therein, and is deemed to be technical data or information related or pertaining to commercial items or processes developed at private expense for purposes of DFARS 227.7102-1 and 227.7102 2 and the restrictions set forth therein, and this EULA shall be deemed to be the license described in such regulations. Any use, modification, reproduction, release, performance, display, or disclosure of such technical data by the Government shall be governed solely by the terms of this EULA and is prohibited except to the extent expressly permitted by the terms of this EULA. Such technical data is also deemed to be limited rights data as defined in FAR 52.227-14(a) (Alternate I (June 1987)) and for purposes of FAR 52.227-14(g)(2) (Alternate II (June 1987)), which clauses are incorporated herein by reference subject to the express restrictions and prohibitions set forth above. Such technical data shall also be deemed to be technical data for purposes of DFARS 252.227-7015, which clause is incorporated herein by reference subject to the express restrictions and prohibitions set forth above. 11.3. Third Party Acceptance of Restrictions. Licensee shall not provide the Software, the Documentation, or the technical data described in Section 11.2 above to any party, including but not limited to the Government, unless such third party accepts the same restrictions as are set forth in this Section 11. Licensee is responsible for ensuring that the proper notice is given to all such third parties and that the Software, the Documentation, and such technical data is properly marked with the required legends. Nothing in this Section 11.3 shall be deemed to modify the restrictions on transfer or disclosure set forth elsewhere in this EULA. 12. GOVERNING LAW; ENFORCEMENT.
12.1. Governing Law. This EULA and the rights and obligations of the parties hereunder shall be governed by the laws of the State of California, without reference to conflicts of laws principles; provided, however, that if the Software and the Documentation is licensed outside the United States, then certain local laws may apply. The parties agree to the non exclusive jurisdiction of the state and federal courts in Los Angeles County, California in connection with the litigation of any dispute pertaining to this EULA and waive any objection to such jurisdiction based on venue or personal jurisdiction. IN ADDITION, THIS EULA WILL NOT BE GOVERNED OR INTERPRETED IN ANY WAY BY REFERRING TO ANY LAW BASED ON THE UNIFORM COMPUTER INFORMATION TRANSACTIONS ACT (UCITA), EVEN IF THAT LAW HAS BEEN ADOPTED IN CALIFORNIA, AND THE UNITED NATIONS CONVENTION ON CONTRACTS FOR THE INTERNATIONAL SALE OF GOODS IS HEREBY EXCLUDED. 12.2. Equitable Relief. Licensee acknowledges that any actual or threatened breach of the provisions of this EULA will constitute immediate, irreparable harm to DDN for which monetary damages would be an inadequate remedy; that injunctive relief is an
vii
appropriate remedy for any such breach or threatened breach; and that, in such event, DDN will be entitled to immediate injunctive relief without the requirement of posting bond. 13. MISCELLANEOUS. Except as otherwise expressly agreed in a written, signed agreement between DDN and Licensee, this EULA sets forth the entire agreement between DDN and Licensee with respect to the Software, the Documentation, and/or Licensee's use of the Software and the Documentation, and it is expressly agreed that the terms of this EULA will supersede the terms in any of Licensee's purchase orders or other ordering documents. There are no implied licenses with respect to the Software or the Documentation. No provision of this EULA may be waived, modified, or superseded except by a written instrument signed by each of DDN and Licensee. No failure or delay in exercising any right or remedy shall operate as a waiver of any such (or any other) right or remedy. The language of this EULA shall be construed as a whole, according to its fair meaning and intent, and not strictly for or against either party, regardless of who drafted or was principally responsible for drafting this EULA or any specific term or condition hereof. This EULA shall bind and inure to the benefit of the parties and their successors and permitted assigns. Both parties are acting as independent contractors with respect to the activities hereunder. In the event of any legal proceeding between the parties arising out of or related to this EULA, the prevailing party shall be entitled to recover, in addition to any other relief awarded or granted, its costs and expenses (including but not limited to reasonable attorneys' and expert witness' fees) incurred in any such proceeding. If any provision in this EULA is invalid or unenforceable, such provision shall be construed, limited, or altered, as reasonably necessary, to eliminate the invalidity or unenforceability and all other provisions of this EULA shall remain in effect.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Should Licensee have any questions concerning this EULA, or if Licensee desires to contact DDN for any reason, please write DDN at 9351 Deering Avenue, Chatsworth, CA 91311, or send an email to DDN at support@datadirectnet.com.
viii
GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
ix
To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
xi
"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination.
xii
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify
xiii
or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
xiv
END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>. Copyright (C) 1997 Massachusetts Institute of Technology This software is being provided by the copyright holders under the following license. By obtaining, using and/or copying this software, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose and without fee or royalty is hereby granted, provided that the full text of this NOTICE appears on ALL copies of the software and documentation or portions thereof, including modifications, that you make. THIS SOFTWARE IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL BEAR NO LIABILITY FOR ANY USE OF THIS SOFTWARE OR DOCUMENTATION. The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders. See the file AUTHORS which should have accompanied this software for a list of all copyright holders. This file may be derived from previously copyrighted software. This copyright applies only to those changes made by the copyright holders listed in the AUTHORS file. The rest of this file is covered by the copyright notices, if any, listed below. Copyright (c) 1992-1996 The Regents of the University of California. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without written agreement is hereby granted, provided that the above copyright notice and the following two paragraphs appear in all copies of this software. IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED
xv
HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. Copyright (C) 2004, 2005, 2006 Board of Trustees, Leland Stanford Jr. University. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
xvi
CGIC License Terms Basic License CGIC, copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 by Thomas Boutell and Boutell.Com, Inc. Permission is granted to use CGIC in any application, commercial or noncommercial, at no cost. HOWEVER, this copyright paragraph must appear on a "credits" page accessible in the public online and offline documentation of the program. Modified versions of the CGIC library should not be distributed without the attachment of a clear statement regarding the author of the modifications, and this notice may in no case be removed. Modifications may also be submitted to the author for inclusion in the main CGIC distribution. IF YOU WOULD PREFER NOT TO ATTACH THE ABOVE NOTICE to the public documentation of your application, consult the information which follows regarding the availability of a nonexclusive commercial license for CGIC. Commercial License The price of a nonexclusive commercial license is $200 U.S. To purchase the license: 1. Print and sign two copies of the document below. 2. Send both copies, along with Visa, Mastercard, Discover, or Amex card number, cardholder's name, and expiration date OR a check for $200 in U.S. funds drawn on a U.S. bank, to: Boutell.Com, Inc. PO Box 63767 Philadelphia, PA 19147 USA Credit card orders may alternatively be faxed to: Boutell.Com, Inc. (208) 445-0327 BE SURE TO INCLUDE AN EMAIL ADDRESS, as well as a postal address and phone number. 3. We will return one signed copy to you promptly. You will also receive swift notification of new versions of CGIC, in addition to ongoing email support. *** CGIC Nonexclusive Commercial License The licensee named below is granted the right to utilize CGIC, major version 1 or 2, any minor version thereof, in CGI applications without the need for a credit notice of any kind. CGI applications developed by the holder of this license may be distributed freely in source code or binary form without additional fees or royalties. This license does not grant the right to use CGIC to create a development tool which passes on substantially all of the capabilities of the CGIC library to the user of the tool, unless that tool is to be used internally by the license holder only in order to develop CGI applications. This license may not be resold, but applications developed in accordance with the terms of the license may be distributed freely subject to the limitations described above. Future minor (2.x) versions of CGIC will be covered by this license free of charge. If significant defects of workmanship are discovered in version 2.x, minor releases to correct them will be made available before or at the same time that those defects are addressed in any future major version. Future "major" (3.x) versions will be available to licensees at an upgrade price of $50. If, for any reason, any portion of this license is found to be invalid, that portion of the license only is invalidated and the remainder of the agreement remains in effect. If this license has not been signed by Thomas Boutell or M. L. Grant on behalf of Boutell. Com, Inc., it is invalid. Licensee: _____________________ _____________________
Complete Mailing Address:
_____________________ _____________________ Phone Number: Email Address: _____________________ _____________________
Signed for Boutell.Com, Inc.: _____________________ Date: _____________________
xvii
Preface
Preface
What is in this guide This user guide gives you step-by-step instructions on how to install, configure and connect the DataDirect Networks S2A6620 system to your host computer, and how to use and maintain the system.
Related Documentation
S2A6620 Command Line User Interface (CLUI) Command Reference S2A6620 Release Notes
International Standards
The S2A6620 complies with the requirements of the following agencies and standards: CE UL
Potential for Radio Frequency Interference

USA Federal Communications Commission (FCC) This equipment has been tested and found to comply with the limits for a class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. The supplier is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the users authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
European Regulations
This equipment complies with European Regulations EN 55022 Class A: Limits and Methods of Measurement of Radio Disturbance Characteristics of Information Technology Equipments and EN50082-1: Generic Immunity.
Safe Handling
Remove drives to minimize weight Do not try to lift the enclosure by yourself Do not lift the S2A6620 by the handles on the power cooling module (PCM); they are not designed to support the weight of the enclosure.
S2A6620 User Guide ( Rev C)
xviii
Preface
Safety
NOTE : If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.
Caution !
Safety goggles should be worn when maintaining the equipment.
WARNING: The S2A6620 MUST be grounded before applying power. Unplug the unit if you think that it has become damaged in any way and before you move it.
Caution ! To maintain proper airflow through the system, operate the system with the enclosure top covers closed. Plug-in modules are part of the enclosure and must only be removed when a replacement can be immediately installed. The system must not be run without all modules in place. In order to comply with applicable safety, emission, and thermal requirements, the top covers should remain closed while running. The S2A6620 system must only be operated from a power supply input voltage range of 200 VAC to 240 VAC. The equipment is intended to operate with two (2) working PCMs. Before removal/replacement of any module, disconnect all supply power for complete isolation. A faulty PCM must be replaced with a fully operational module within 24 hours.
WARNING: To minimize the risk of electric shock, disconnect the power from the power supply, either by turning off the switch or by physically removing the power cable, prior to removing the PCM from the enclosure. Do not remove a faulty PCM unless you have a replacement module of the correct type ready for insertion. The power connection must always be disconnected prior to removal of the PCM from the enclosure. A safe electrical earth connection must be provided to the power cord. Provide a suitable power source with electrical overload protection to meet the requirements given in the technical specifications.
WARNING: Do not remove covers from the PCM. Danger of electric shock inside. Return the PCM to your supplier for repair.
xix
Preface
WARNING: Operation of the S2A6620 with ANY modules missing will disrupt the airflow and the drives will not receive sufficient cooling. It is ESSENTIAL that all apertures are filled before operating the unit.
Recycling of Waste Electrical and Electronic Equipment (WEEE)

At the end of the products life, all scrap/ waste electrical and electronic equipment should be recycled in accordance with National regulations applicable to the handling of hazardous/ toxic electrical and electronic waste materials.
NOTE : Observe all applicable safety precautions, such as weight restrictions, handling batteries and lasers etc, detailed in the preceding paragraphs when dismantling and disposing of this equipment.
ESD Precautions
Caution ! It is recommended that you check and fit a suitable anti-static wrist or ankle strap and observe all conventional ESD precautions when handling the S2A6620 plug-in modules and components. Avoid contact with backplane components and module connectors.
Data Security
Power down your host computer and all attached peripheral devices before beginning installation. Each enclosure contains up to 60 removable disk drive modules. Disk units are fragile. Handle them with care, and keep them away from strong magnetic fields. ALL the supplied plug-in modules and blanking plates must be in place for the air to flow correctly around the enclosure and also to complete the internal circuitry. If the enclosure is used with modules or blanking plates missing for more than a few minutes, the enclosure can overheat, causing power failure and data loss. Such use may also invalidate the warranty. If you remove a drive module, replace it immediately. If it is faulty, replace it with a drive module of the same type and capacity. Ensure that all disk drives are removed from the enclosure before attempting to move the rack installation. Do not abandon your backup routines. No system is completely foolproof.
xx
Table of Contents
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.1 DataDirect Networks SAN Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.2 Features of the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 The S2A6620 System Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2.1 Enclosure Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2.2 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.3 Power Cooling Module (PCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.2.4 Drive Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.2.5 Drive Expander Module (DEM) Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.2.6 LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.2.6.1 Front Panel Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.2.6.2 Internal Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.2 Setting Up the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.2.1 Unpacking the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.2.2 Rack-Mounting the S2A6620 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.3 Connecting the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.2.3.1 Host Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.2.3.2 Expansion Enclosure Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.2.3.3 Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.2.4 Powering On the S2A6620 (and Expansion Enclosure). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.3 Configuring the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.3.1 Planning Your Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.3.2 Drive Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.3.3 Initial Configuration via RS-232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.3.3.1 Serial Interface Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.3.3.2 Configure Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.3.4 Setting System Time & Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.3.5 Checking Status of Physical Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.3.6 Creating Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.3.7 Creating Virtual Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.8 Creating Spare Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.3.9 Initializing the Host System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.9.1 Present Virtual Disk to External Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.3.10 Setup Email and SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.10.1 Setup Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.3.10.2 Setup SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.1 Managing the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.1.1 Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.1.2 User Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 3.1.3 Available Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 3.1.3.1 Basic Key Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 3.2 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2.1 Monitor Status of Storage Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2.1.1 Disk Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2.1.2 Storage Pool View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.2.1.3 Virtual Disk View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
S2A6620 User Guide (Re v C)
xxi
Table of Contents
3.2.1.4 3.2.1.5 3.2.2 3.2.2.1 3.2.2.2 3.2.2.3 3.2.2.4 3.2.2.5 3.2.2.6 3.2.2.7 3.2.2.8 3.2.3 3.2.3.1 3.2.3.2 3.2.3.3 3.2.4 3.2.4.1 3.2.4.2 3.2.4.3 3.2.5 3.2.6 3.2.7 3.2.8
Spare Pool View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Visual Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Storage Pool & Virtual Disk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Changing the Disks Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Creating a Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Storage Pool Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Naming a Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Deleting a Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Creating a Virtual Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Naming a Virtual Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Deleting a Virtual Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Spare Pool Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Creating a Spare Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Naming a Spare Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Deleting a Spare Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Drive Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Full and Partial Rebuilds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Sparing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Manual Drive Replace/Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 SATAssure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Cache Coherency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Setting the Systems Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Restarting the S2A6620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.3 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.3.1 Background Job Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.3.2 Rebuild Policy Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 3.4 Firmware Update Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.4.1 Displaying Current Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 3.4.2 Firmware Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.4.2.1 Linux Environment-Firmware Update from the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 3.4.2.2 Windows Environment-Firmware Update from the Network . . . . . . . . . . . . . . . . . . . . . . . . . . 63 3.4.3 Enclosure (Disk Shelf) Firmware Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 3.4.3.1 Linux Environment-Firmware Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 3.4.3.2 Windows Environment-Firmware Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 3.4.3.3 Disk Shelf Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 3.5 The System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 3.6 Remote Management of S2A6620. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 3.6.1 Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 3.6.2 Network Interface Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 3.6.3 Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 3.7 Presentations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 3.7.1 Application Discovered Initiator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 3.7.2 Application Host Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 3.7.3 Application Presentation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 3.7.4 Configuration of Presentations of Virtual Disks to Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 3.7.4.1 Host Object Creation Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.7.4.2 Identifying Host FC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 3.7.4.3 Presenting a VD to a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
xxii
Table of Contents
3.7.5
Additional Configuration Considerations For Macintosh Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.1 Status LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 4.1.1 Front Panel Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 4.1.2 Power Cooling Module (PCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 4.1.3 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 4.1.4 HDD (Hard Disk Drive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 4.1.5 DEM (Drive Expander Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 4.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 4.2.1 Initial Start-up Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 4.2.2 RAID[0]$ Prompt is not shown correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 4.2.3 System Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 4.2.4 Power Supply/Cooling Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 4.2.5 Thermal Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 4.3 Component Failure Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 4.3.1 Replacing a Power/Cooling Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 4.3.2 Replacing a Drive Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4.3.3 Replacing a DEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 4.3.4 Replacing an I/O Module on an expansion shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 4.3.5 Replacing a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 4.3.6 Automatic Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 4.3.7 Drive Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 4.3.8 When a Spare is not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 4.4 Manual Intervention Required (MIR) Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.1 The GUI Management Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.2 Starting the GUI Management Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.2.1 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.2.2 Initial Home Screen and Health Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.3 Physical Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.3.1 Physical Disks Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.3.2 Checking Status of Physical Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.4 Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 5.4.1 Storage Pool Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 5.5 Virtual Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.5.1 Virtual Disk Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.6 Spare Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 5.6.1 Spare Pool Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 5.7 Initializing the Host System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 5.8 Presentations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 5.8.1 Presentation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 5.9 Email and Critical Event Notification Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Appendix A. Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
xxiii
Table of Contents
Appendix B. Safety Requirements for Rack Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
xxiv
S ECTION 1
Introducing the S2A6620
Introduction
1.1
Introduction
Welcome to the DataDirect Networks S2A6620 User Guide.
1.1.1
DataDirect Networks SAN Solution

The DataDirect Networks Silicon Storage Appliance (S2A) is an intelligent network infrastructure device designed and optimized for the high bandwidth and capacity requirements of departmental, rich media and high performance workgroup applications. The S2A6620 is a compact version of DDNs network storage system. It is a unit that combines DDNs controller chassis and disk enclosure chassis into a single self-contained enclosure. The S2A6620 plugs seamlessly into existing network environments, thereby protecting and upgrading investments made in legacy storage and networking products to substantially improve their performance, availability and manageability. The S2A6620 is designed to support mixed workload environments with industry leading density, large number of small random IOPS and high sequential throughput making it a perfect shared storage for transactional, backup or rich media markets. It enables a multi-vendor environment comprised of standalone and clustered servers, workstations and PCs to access and back up data stored in centralized or distributed storage devices in an easy, cost effective and reliable manner. This modular architecture ensures high data availability and uptime along with application performance.
1.1.2
Features of the S2A6620

The S2A6620 incorporates the following features: Fibre Channel connectivity The S2A6620 provides up to 4 individual 8Gb/s Fibre Channel host port connections, including simultaneous access to the same data through multiple ports. Each FC host port supports point-to-point and switched fabric operation. Support for 256 storage pools, 16 spare pools, and 512 virtual disks Effectively, the 6620 is limited by the number of disks in the system 120 drives maximum configured into 60 2-disk RAID-1 storage pools it the maximum possible. The maximum number of virtual disks in the system is set to 512 with an upper limit of 64 virtual disks per pool. The maximum number of spare pools has been increased to 16. Active/Active operation with cache coherency and failover Both Controllers operate in active mode at all times meaning I/O requests can be serviced by either Controller from any host port and failover is transparent to the host. Automatic Storage Pool Failover When paths are lost to drives that affect pool redundancy, the pool will move automatically to the other side. RAID 5, RAID 6, RAID 1 The system is based on a high performance software RAID engine with default RAID5 support and a currently optional/licensed RAID6. Also, 2 member RAID 1with a fixed chunk size is supported.
Introduction
Configurable RAID group sizes (5 or 9 drives per RAID 5 group, 6 or 10 drives per RAID 6 group) This feature allows you to configure the system with the desired RAID and redundancy levels based on the importance of your data. Each RAID group is configured independently and any valid combination for the number of drives in the array is supported. 32 K chunk size support Addition of 32K chunk size for RAID- 5 & 6 storage pools. Stripe size of 32kb, 64KB, 128KB, 256KB Configurable stripe sizes aid in system tuning for the applications data pattern. Stripe sizes are uniquely configurable per RAID set. 2 MB maximum request size This is the maximum transfer size a host may request from the unit and covers nearly all commonly found use cases. SAS/SATA Storage Pool This feature allows in-box storage pooling, where high performance SAS drives are used for primary data and high capacity SATA drives are used for secondary data or active archiving. Flexible configurations along with intermixing of SATA and SAS drives within the same enclosure is supported. Although for performance and reliability reasons, there are best practice guidelines. Optional SATAssure data protection SATAssure technology is designed by DDN to improve the reliability of enterprise SATA drives and make sure that data integrity is always maintained for all IO operations. Partial rebuild This feature reduces rebuild times by updating only the data that has changed while the drive was down. Hot-swappable and redundant components Adhering to enterprise RAS standard, almost all hardware components (such as drives, Controllers, power cooling modules, and DEM cards) are redundant and hot-swappable. Hot spares The unit supports as many hot spares as desired and they can be allocated as global hot spares or assigned to a specific RAID set. Comprehensive, centralized management capability The S2A6620 provides a wide range of management capabilities either via a secured CLUI or the GUI Management Agent: Configuration Management, Performance Management, and Firmware Update Management. Management options via RS-232 and Ethernet (SSH) A RS-232 port and Ethernet port are included to provide local and remote management capabilities. Drive Fault LED When a drive has been failed, the drive fault LEDs will be lit. SNMP and Email notification Inquiry items and events will be trapped in the SMNP MIB and in the email agent.
Introduction
The S2A6620 System Hardware
1.2

The S2A6620 is a four-unit (4U), rack-mountable enclosure that houses two power cooling modules, two Controllers, and slots for up to 60 SAS or SATA drives (Figure 1). The Controllers provide system management and host connectivity interfaces. The S2A6620 design concept is based on a subsystem together with a set of plug-in modules and (as supplied) comprises: Enclosure Chassis with front panel drive status indicator Two (2) Power Cooling (PCM) plug-in modules Two plug-in Controllers Up to 60 top loadable hard disk drives in a 5x12 matrix SAS and SATA drive intermix allowed Eight (8) SAS Drive Expander Modules (DEM)
Figure 1. The S2A6620 - Front and Rear Views
1.2.1
Enclosure Chassis
The chassis assembly contains 60 drive bays at the top, each of which accommodates a plug-in drive module capable of holding a 3.5-inch SAS or SATA Hard Disk Drive (HDD) or Solid State Disk (SDD). The 60 drive bays are arranged in five rows of twelve drives (5x12) (Figure 2). At the rear, the chassis assembly contains two (2) power cooling modules and two (2) Controllers (Figure 3). The chassis is fitted with 19-inch rack mounting features which enables it to be installed into 19-inch wide racks and uses four (4) EIA units of rack space. A mid-plane separates the front and back of the chassis and provides the interconnect system between the power cooling modules, Controllers, and the baseboard.
Figure 2. S2A6620 Top View
30 Drive Bays
Front of S2A662
30 Drive Bays
Figure 3. S2A6620 Rear View
Controller 1
Controller 2
Power Cooling Module 1
Power Cooling Module 2
1.2.2
Controller
The two Controllers are redundant and hot-swappable modules which provide the intelligence and active/active data protection features of the S2A6620 (Figure 4). If a Controller fails, the remaining Controller will assume its functionality and continue to provide data access, at a reduced performance level.
Figure 4. A S2A6620 Controller

Firmware Status LED CLI Port Expansion Port (DO NOT USE)
EXPANSION CLI
Identify LED Power LED
RESE LINK
PORT 2 PORT 1
SPEED
Power Switch Ethernet Port
Host Port 2
Host Port 1
There are two 8Gb/s host ports for Fibre Channel host connections. You may connect your host systems directly to these ports or connect the ports to your Fibre Channel switches and hubs. When an FC signal is present on the port, the respective LED turns green. The EXPANSION port is used to connect to an expansion enclosure StorageScaler6000. The CLI connector provides local system monitoring and configuration capabilities. The Ethernet port provides remote monitoring and configuration capabilities. The LINK LED is off when there is no Ethernet link. The Firmware Status LED blinks green when the S2A6620 firmware is loading. It stays solid green when the S2A6620 is ready to be accessed. The Power LED turns green when there is power applied to the Controller. The Identify LED turns blue when an SES identify command is received.
1.2.3
Power Cooling Module (PCM)

Two (2) power cooling modules are supplied with the S2A6620, installed in the rear of the chassis (Figure 5).
Figure 5. Power Cooling Module
Power Cord Connector Power Switch Thumbscrew on lifting bar
The S2A6620 must always be operated with two PCM installed. Module replacement should only take a few minutes to perform but must be completed with 10 minutes from removal of the failed module. Four (4) LEDs mounted on the PCM indicate the status of the module and the fans (Figure 6). Figure 7 provides a description of the color and status of the LEDs.
Figure 6. Power Cooling Module LEDs
Normal Operation LEDs Faults LEDs
Figure 7. PCM LED Description LED Description PCM AC Color Green Status ON - AC input to PCM within tolerances OFF - PCM failed ON - DC output of PCM within tolerances OFF - PCM failed ON - PCM fault detected OFF - no detected PCM faults ON - receiving SES identify command OFF - NOT receiving SES identify command
PCM DC
Green
PCM Fault
Amber
PCM ID
Blue
1.2.4
Drive Modules
The drive module comprises a hard disk mounted in a carrier (Figure 8). Each drive bay can house a single low profile 1.0-inch high, 3.5-inch form factor disk drive in its carrier. A fully loaded enclosure contains 60 drive modules. The module handle provides the following functions: Camming of the module into and out of drive bays Positive spring loading of the drive/baseplane connector Drive Status LED incorporated in handle assembly
NOTE : The S2A6620 design allows for drive bays to be left empty without the need for fitting dummy drive modules.
The S2A6620 supports a SATA interposer card which allows simultaneous access to the SATA HDD from both Controllers installed in the enclosure. Note that a SATA interposer card, which is part of the drive carrier assembly, is required to run SATA HDDs.
Figure 8. Drive Module

Handle Open Drive Status LED
10
1.2.5
Drive Expander Module (DEM) Card

The S2A6620 contains eight (8) top-loadable, hot-swappable DEMs (Figure 9). The DEMs provide the SAS connectivity between the Controllers and the HDDs located with the enclosure. The DEMs are organized into four module pairs, with each module pair controlling a bank of 15 drives. If a DEM card fails, its sister card will provide continuous operation of the unit until a replacement is inserted bringing the unit back to full redundancy.
Figure 9. DEM Card Locations (Viewing from Top)
DEM Card x 8
Each DEM (Figure 10) connects to a single port of the HDD based on the location within the enclosure within which it is installed. Each card provides power control signals to each drive slot. It controls HDD identify/service LEDs and monitors the status from partner DEM. Each pair of DEMs supports 15 drives.
Figure 10. DEM Card
Locking Mechanism
11
1.2.6
LED Indicators
The S2A6620 has both FRU and status LEDs to indicate the state of various components within the enclosure. Each FRU has a visible blue identity LED. Each FRU, except the drive module, has a visible amber LED which indicates a fault.
1.2.6.1
Front Panel Indicators

The front panel indicators show the aggregated status of all the modules (Figure 11). The LEDs are defined in Figure 12. The Drive Activity LEDs indicate drive presence and flash during data I/O.
Figure 11. Front Panel LED Indicators
System Fault System Power Shelf Identify Cover Open DEM Fault Drive Fault
Drive Activity LEDs
Figure 12. Front Panel LED Description LED Definition Shelf Identify Color Blue Status ON - SES is sending an identify command OFF - SES is NOT sending an identify command ON - one or more components within enclosure have failed. A service action is required. Exact failed component has its own amber fault LED lit. OFF - no detectable faults ON - DC power is present OFF - DC power is not present LED does NOT flash under normal operating conditions OFF - both cover pieces securely closed and latched in place ON - either of the cover pieces is NOT securely closed and latched in place OFF - all DEMs operating correctly ON - at least one DEM has failed; service action required ON - one or more HDDs are failed; SES must determine exact HDD OFF - no detectable drive faults ON - when SAS HDD is present Blinks - indicates HDD activity OFF - no HDD activity
System Fault
Amber
System Power
Green
Cover Open
Amber
DEM Fault
Amber
Drive Fault
Amber
Individually numbered
HDDs
Green
12
1.2.6.2
Internal Indicators
For some components, the failure LED is internal to the enclosure and visible only when the cover is open. The various internal indicators are listed in Figure 13.
Figure 13. Internal LED Indicators Description DEM DC Location DEM internal to enclosure DEM internal to enclosure HDD internal to enclosure Color Green Status ON - 1.2VDC regulator circuit correctly functioning OFF - faulty 1.2VDC regulator circuit ON - receiving SES identify command OFF - NOT receiving SES identify command ON (blinking) - receiving SES identify command ON (steady) - drive/slot fault OFF - NOT receiving SES identify command
DEM ID
Blue
HDD ID
Blue
13
S ECTION 2
S2A6620 Installation
Installation Overview
2.1
Installation Overview
Here is an overview of all the steps needed to be taken to complete an installation and configuration of an S2A6620 system. Each step is explained in detail in Section 2.2 and Section 2.3 of this Guide. 1. Unpack the S2A6620 system. 2. Rackmount the S2A6620 (and expansion enclosure). (See Appendix A for physical dimensions and weight of the S2A6620) 3. Connect the S2A6620 to your Fibre Channel (FC) switch, host computer(s), and expansion enclosure. 4. Power up the system. 5. Configure the storage array (create storage pools, virtual disks, and spare pools) via RS-232 interface or SSH. 6. Initialize the Storage Pools for use with your server/client systems. Partition disk space and create filesystems as needed.
16
Setting Up the S2A6620
2.2

This section details the installation of the hardware components of the S2A6620 system. If your S2A controller and disk enclosure configuration is delivered already installed in the rack, it must be removed from the shipping pallet using a minimum of 4 people. The racked unit may not be tipped more than 10 degrees, either from a level surface or rolling down an incline (such as a ramp).
!
Warning
NOTE : Follow the safety guidelines for rack installation given in Appendix B Safety Requirements for Rack Installation .
2.2.1
Unpacking the S2A6620
!
Warning
Wear an ESD wrist strap or otherwise ground yourself when handling S2A6620 modules and components. Electrostatic discharge can damage the circuit boards.
Before you unpack your S2A6620, inspect the shipping container(s) for damage. If you detect damage, report it to your carrier immediately. Retain all boxes and packing materials in case you need to store or ship the system in the future. While removing the components from their boxes/containers, inspect the S2A6620 chassis and all components for signs of damage. If you detect any problems, contact DataDirect Networks Customer Service at 818-700-6052 or customerservice@datadirectnet.com immediately. Your S2A6620 ships with the following: S2A6620 controller chassis with integrated Controllers Two (2) power cables One (1) mini-jack serial cable for initial configuration One (1) enclosure faceplate Rack-mounting hardware S2A6620 User Guide S2A6620 Quick Start Guide Release Notes
17
2.2.2
Rack-Mounting the S2A6620 Chassis

The S2A6620 is designed to fit within a 4U rack space. Follow these steps to mount the system in your rack: 1. Using eight (8) 10-32 0.188" Phillips panhead screws for each slider, attach the four (4) inner sliders to the chassis as shown in Figure 14 below.
Figure 14. Attach 4 Inner Sliders to Chassis
2. For expansion enclosure, skip this step and proceed to the next step. Loosen the nine (9) screws on the rail kit and set the length to fit the depth of your rack (Figure 15). Tighten all the screws once the rail kit is set to the desired length. Repeat for the other rail kit.
Figure 15. Adjust Rail Kit Length
Loosen (9) Screws t o Adjust Rail Kit Length
18
3. Attach the two (2) rail kits to your rack as shown in Figure 16. Make sure you leave enough space for the unitbottom of screw plate aligns to bottom of S2A6620 chassis. At the front, use one (1) screw plate, one (1) shelf locking bracket (installed from behind), and six (6) #10 screws. For the rear end, use one (1) screw plate and four (4) #10 screws. 4. If the depth of your rack is more than 25.5 inches (647 mm), attach the two (2) Cable Management Arm (CMA) brackets to the rear end of the rail kits (Figure 16).
Figure 16. Attach Rail Kits to Rack
Shelf Locking Bracket Installed from Behind
Attach Screw Plate with (6) #10 Screws
Attach (2) CMA Brackets Attach Screw Plate with (4) #10 Screws
19
5. Using two (2) 10-32 0.50" (100d) Phillips flathead screws for each CMA, attach the CMA to the CMA brackets (Figure 17). If the depth of your rack is 25.5 inches (647 mm) or less, attach the CMA directly to the rack, above the rail kits. For square-hole rack, add 100d #10 shoulder washers. 6. With the help of a partner, hold the chassis close to the rail kits. Align the rear flanges on chassis with the rail kit flanges (Figure 17) and slide the chassis into rack until the sliders are engaged (slide in about 12 inches until stopped). Then slide the chassis out until locked. Depress the slider locks and proceed to slide the chassis all the way in. 7. Secure the two CMA to rear of chassis with two (2) 8-32 0.25" Phillips panhead screws.
Figure 17. Install Chassis to Rack

Rail Kit Flange (Rear Flange of Chassis must set on Rail Kit Flange) Attach CMA to Chassis with (2) 8-32x0.25" Phillips Panhead Screws
Attach CMA with (2) 10-32x0.50" (100d) Phillips Flathead Screws (Add 100d #10 Shoulder Washers for Square-Hole Rack)
Rear Flange on Chassis
20
2.2.3
2.2.3.1
Connecting the S2A6620

Host Connections
Each S2A6620 supports up to four Fibre Channel host connections, two per Controller. Each connection is auto-sensing and supports 2 Gb/s, 4 Gb/s or 8 Gb/s. You may connect more than four hosts to the unit using a Fibre Channel switch (not provided). The host ports are numbered as shown in Figure 18 below. Connect your switch or host system(s) to these ports.
Figure 18. A Controller
Expansion Port (DO NOT USE)
EXPANSION CLI
CLI Connector Firmware Status LED Power LED
LINK
PORT 2 PORT 1
SPEED
Host Port 2
Host Port 1
2.2.3.2
Expansion Enclosure Connections

The StorageScaler6000 Expansion Enclosure can be daisy-chained to the S2A6620 to increase storage capacity. Follow these steps to connect an expansion enclosure:
NOTE : Only the DDN StorageScaler6000 can be used with the S2A6620 for storage expansion.
1. Using the supplied mini-SAS connector, connect one end of the cable to the port labeled EXPANSION on the S2A6620 Controller (Figure 18). 2. Connect the other end of the cable to the port labeled EXP2 on the expansion enclosure (Figure 19).
Figure 19. I/O Module on Expansion Enclosure
EXP 2 Port
HOST1 EXP 1 HOST 2 EXP 2
3. Repeat for the second Controller (Figure 20).

Figure 20. Daisy-Chaining the S2A6620
S2A6620
Expansion Enclosure
21
2.2.3.3
Power Connections
Each S2A6620 (and expansion enclosure) ships with two fully redundant power supplies that require 220 V connections. Only the power cables supplied with the system should be used. The power supplies are accessible from the rear of the unit. 1. Verify that the power switch on both supplies is in the OFF position (Figure 21). 2. Then connect the power cables from the S2A6620 to the appropriate 220 V outlets. For maximum redundancy, connect the two power supplies to different AC circuits. 3. Similarly, connect the power cables to the expansion enclosure.
Power Cord Connector
Power Switch
22
2.2.4
Powering On the S2A6620 (and Expansion Enclosure)

1. If an expansion enclosure is connected, turn the switch on each power supply to the ON position. 2. On the S2A6620, turn the switch on each power supply to the ON position. 3. Verify that the Power LED on each Controller turns green within a few seconds (Figure 22), indicating a successful power application.
Figure 22. A Controller
Firmware Status LED Power LED
EXPANSION CLI
LINK
PORT 2 PORT 1
SPEED
4. Verify that the Firmware Status LED blinks green within one minute of power application (Figure 22), indicating that the S2A6620 firmware is currently loading. 5. Verify that the Firmware Status LED stays solid green within two minutes of power application, indicating that the S2A6620 is ready to be accessed. You may now configure the system as described in Sections 2.3 "Configuring the S2A6620" or 5.1 "The GUI Management Agent".
23
Configuring the S2A6620
2.3

This section provides information on configuring your S2A6620. NOTE : The configuration examples provided here represent only a general guideline. These examples should not be used directly to configure your particular S2A6620. The CLUI (Command Line User Interface) commands used in these examples are fully documented in Sections 3.1 through 3.5however, exact commands may change depending on your firmware version. To access the most up-to-date commands, use the CLUIs online HELP feature. You need not type a complete CLUI command; there is a short-hand. For example, SHOW CON LO ALL is adequate for SHOW CONTROLLER LOCAL ALL.
2.3.1
Planning Your Setup and Configuration

Before proceeding to configure the storage settings for the S2A6620, it is necessary to understand the basic organization of the system. The S2A6620 uses Storage Pools and Virtual Disks to configure drive storage for use by host systems. A Storage Pool (sometimes referred to as a RAID group) is a collection of 5 to 10 disk drives, ideally of the same capacity and type. In RAID5, the capacity of one drive is reserved for parity, allowing data recovery in the event of a single drive loss in the Storage Pool. In RAID6, the capacity of two drives is reserved for parity, allowing data recovery if either one or two drives are down in a Storage Pool. A single RAID5 Storage Pool can be configured using 5 or 9 drives. A single RAID6 Storage Pool can be configured using 6 or 10 drives. The S2A6620 supports up to 512 Storage Pools in a single system. A Storage Pool can be configured with drives of different capacity, in which case the S2A6620 will use the lowest capacity for all drives, but this is not recommended. A Virtual Disk is the storage unit presented to any attached host. Virtual disks allocate space in 8 GiB increments. For example, 16 GiB of storage space will be allocated when creating a Virtual Disk of 10 GiB. You can create up to 512 Virtual Disks per system; however, only 64 Virtual Disks per Storage Pool is permitted. NOTE : In this document, the terms "GB" and "GiB" are used interchangeably, and denote 1,073,741,824 bytes (230 bytes). The drives in the system are categorized into one of the following pools: Unassigned Pool - By default, all the drives or replacement drives are initially allocated to this pool. When a drive has failed or been released (from a spare pool, for example) it is also moved to this pool. Storage Pool (sometimes referred to as a RAID group) - A collection of 5 to 10 disk drives, ideally of the same capacity and type.
24
Spare Pool - This type of pool contains drive(s) that can be used as spare drives in one or more Storage Pools.
2.3.2
Drive Layout
Figure 23 shows the layout of drives in an S2A6620. Drives are always referenced by enclosure ID and slot number as illustrated. The drive layout may also be found inside the doors of the enclosure. The S2A6620 supports any mix of SAS and SATA drives. For most efficient airflow and reduced vibrations, SAS drives should be placed in the front of the enclosure (lower slot numbers) while SATA drives should be placed in the rear of the enclosure (higher slot numbers).
Figure 23. S2A6620 Drive Layout
DRIVE 1 DRIVE 2 DRIVE 3 DRIVE 4 DRIVE 5 DRIVE 13 DRIVE 14 DRIVE 15 DRIVE 16 DRIVE 17 DRIVE 18
DEM 2B DEM 4A
DRIVE 25 DRIVE 26 DRIVE 27 DRIVE 28 DRIVE 29 DRIVE 30

DEM 2A DEM 4B

DEM 1B DEM 3A

DEM 1A DEM 3B
Front of Chassis
DRIVE 6 AUX DRIVE DRIVE 7 DRIVE 8 DRIVE 9 DRIVE 10 DRIVE 11 DRIVE 12
2.3.3
Initial Configuration via RS-232

The S2A6620 can be configured and administered either via serial connection (using the supplied mini-jack cable) or via Ethernet connection using SSH. However, in order to use the SSH connection, it is first necessary to configure the network settings on each Controller. This can only be done using the serial interface as described below.
2.3.3.1
Serial Interface Configuration

1. Connect the supplied mini-jack cable to the port labeled CLI on Controller 1 (Figure 24). Connect the other end of the cable to a serial port on a standard PC.
Figure 24. CLI Port on Controller
CLI Connector
Serial EXPANSION CLI
LINK
PORT 2 PORT 1
SPEED
2. Load a serial console program (such as HyperTerminal, minicom, and screen) and use the following settings for the serial connection: Bits per second: 115,200 Data bits: Parity: 8 None
25
Stop bits: Flow control:
1 None
3. Once connected, press the <Enter> key to bring up the password prompt. Enter the password: user.
2.3.3.2
Configure Network Settings

To enable SSH access to each Controller, the network settings must be configured as follows: 1. Enter command: UI SET NETWORK_INTERFACE LOCAL 0 IP_ADDRESS=<ip_address> IP_MASK=<netmask> IP_GATEWAY=<gateway> where <ip_address> is an address appropriate to the local network. The netmask and gateway values can also be entered (Figure 25).
Figure 25. Set Network Interface Example
RAID[0]$ ui set network_interface local 0 ip_address=10.32.31.31 ip_mask=255.255.240.0 ip_gateway=10.32.16.2 NETWORK_INTERFACE 0 set with STATUS=Success (0x0)
2. To verify the new settings, enter command (Figure 26): UI SHOW NETWORK_INTERFACE LOCAL *
Figure 26. Show Network Interface Settings
RAID[0]$ ui show network_interface local * Network device id 0 address 10.32.31.31 netmask 255.255.240.0 gateway 10.32.16.2
3. Switch the serial cable to the CLI port on Controller 2 and repeat the above steps to enter a different IP address for Controller 2. 4. Enter command SHUTDOWN SUBSYSTEM RESTART to restart the Controllers and make the changes take effect.
2.3.4
Setting System Time & Date

The system time and date for the S2A6620 are factory-configured will be set in GMT time zone. Changing the time zone is not supported currently. You may need to change the settings so that the time stamps for all events are correct. To display the current system time (Figure 27), enter command SHOW SUBSYSTEM ALL_ATTRIBUTES
Figure 27. Show Current System Time
RAID[0]$ show subsystem RP Subsystem Name: UID: Subsystem Time: Locate Dweel Time: Enabled Licenses: Mirror Synch: all_attributes 0x0000000000000000 Fri Jan 30 16:48:55 121 seconds RAID6 SATASSURE NA
2009
26
To change the date and time to March 1, 2009 2:15:32 pm, for example, type: SET SUBSYSTEM DATE_AND_TIME=2009:3:1:14:15:32
27
2.3.5
Checking Status of Physical Disks

Before creating any storage pools, check the status of all the drives. 1. Enter command SHOW PHYSICAL_DISK * (Figure 28) .
Figure 28. Show Disk Information Screen
RAID[0]$ show physical_disk * |Member| Encl|Slot| Vendor | Product ID |Type|Cap GB |RPM|Revision| Serial Number |Pool|Status| Idx|Status| WWN | -------------------------------------------------------------------------------------------------------------------------------1 1 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZLKH UNAS GOOD 57 5000cca20def4516 1 2 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKNL79H UNAS GOOD 32 NORM 5000cca20df3a263 1 3 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKD8Y5F UNAS GOOD 42 NORM 5000cca20defdc87 1 4 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK72BLH UNAS GOOD 1 NORM 5000cca20ded7e05 1 5 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB269H UNAS GOOD 38 NORM 5000cca20def4edd 1 6 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB1LHH UNAS GOOD 23 NORM 5000cca20def4c96 1 7 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF200P8G6K2YF UNAS GOOD 40 NORM 5000cca215c2fa66 1 8 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKA6P9H UNAS GOOD 41 NORM 5000cca20deeeb53 1 9 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAGVYF UNAS GOOD 47 5000cca20def0a0a 1 10 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKA5SDH 2 GOOD 45 NORM 5000cca20deee7d3 1 11 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK8VH8F 2 GOOD 39 NORM 5000cca20dee4cee 1 12 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZ75H 1 GOOD 26 NORM 5000cca20def43b5 1 13 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTMNRF 4 GOOD 20 NORM 5000cca215cb32bd 1 14 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTLDJF 4 GOOD 33 NORM 5000cca215cb2dfe 1 15 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPR7F 3 GOOD 3 NORM 5000cca215cb3a6e 1 16 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPW9F 5 GOOD 50 NORM 5000cca215cb3b0b 1 17 Hitachi HUA721050KLA330 SATA 465 7K GK6OAB0A GTE402P6G94E8E 1 GOOD 27 NORM 5000cca214c427f6 1 18 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPNXF UNAS GOOD 58 5000cca215cb3a45 1 19 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPTBF 4 GOOD 18 NORM 5000cca215cb3ab0 1 20 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKSMX8D 0 GOOD 21 NORM 5000cca20df505cb 1 21 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKERMGF 0 GOOD 17 NORM 5000cca20df08447 1 22 Hitachi HUA721050KLA330 SATA 465 7K GK6OAB0A GTE402P6G9M0SE 1 GOOD 28 NORM 5000cca214c45ec1 1 23 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKNTM6D 1 GOOD 35 NORM 5000cca20df3ba5a 1 24 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKKVV3F 1 GOOD 30 NORM 5000cca20df26595 1 25 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN35ZAKE8HZH 0 GOOD 5 NORM 5000cca20df04f4d 1 26 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKDW9PH 0 GOOD 6 NORM 5000cca20df0217e 1 27 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKSNNDD 0 GOOD 8 NORM 5000cca20df50898 1 28 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZ4LH 0 GOOD 9 NORM 5000cca20def4365 1 29 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB2GEH 2 GOOD 37 NORM 5000cca20def4fd9 1 30 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKESH1F 1 GOOD 31 NORM 5000cca20df0877f 1 31 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN03ZAGMUMUD UNAS GOOD 49 5000cca20dc9034c 1 32 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN35ZAK6VLBF 1 GOOD 25 NORM 5000cca20ded6490 1 33 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKN0S7F 1 GOOD 36 NORM 5000cca20df360bf 1 34 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK9VNRH 2 GOOD 44 NORM 5000cca20deec1f6 1 35 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKL1MYH 0 GOOD 22 NORM 5000cca20df27b5c 1 36 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN03ZAGH9Y4D 2 GOOD 43 NORM 5000cca20dc6f6e1 1 37 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSLNF 3 GOOD 7 NORM 5000cca215cb4181 1 38 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRPVF 5 GOOD 54 NORM 5000cca215cb3e23 1 39 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSMGF 3 GOOD 14 NORM 5000cca215cb419a 1 40 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTK4HF 5 GOOD 56 NORM 5000cca215cb2944 1 41 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRPDF 5 GOOD 52 NORM 5000cca215cb3e15 1 42 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRLVF 4 GOOD 24 NORM 5000cca215cb3dc6 1 43 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTNPYF 3 GOOD 13 NORM 5000cca215cb36a4 1 44 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPWUF 5 GOOD 53 NORM 5000cca215cb3b1b 1 45 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPSHF 3 GOOD 12 NORM 5000cca215cb3a95 1 46 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPKNF 4 GOOD 29 NORM 5000cca215cb39e0 1 47 Hitachi HUA721050KLA330 SATA 465 7K GK6OAB0A GTE402P6G94EYE 2 GOOD 46 NORM 5000cca214c4280b 1 48 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRP6F 5 GOOD 51 NORM 5000cca215cb3e0f 1 49 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTV0KF 4 GOOD 15 NORM 5000cca215cb4a93 1 50 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTUYLF 3 GOOD 2 NORM 5000cca215cb4a56 1 51 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSJZF UNAS GOOD 59 5000cca215cb414d 1 52 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTNV9F 5 GOOD 55 NORM 5000cca215cb372b 1 53 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTTZ5F 4 GOOD 19 NORM 5000cca215cb46a7 1 54 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTR3ZF 4 GOOD 34 NORM 5000cca215cb3bf9 1 55 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTT3DF 3 GOOD 4 NORM 5000cca215cb4369 1 56 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPGWF 3 GOOD 10 NORM 5000cca215cb398a 1 57 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPH3F 3 GOOD 11 NORM 5000cca215cb3991 1 58 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSMLF 4 GOOD 16 NORM 5000cca215cb419e 1 59 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSK6F UNAS GOOD 60 5000cca215cb4154 1 60 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPATF 5 GOOD 48 NORM 5000cca215cb390b Total Physical Disks: 60 Total Assigned Disks: 54 Total Unassigned Disks: 6 Total SATA Disks: 60 Total Member State Normal:
54
2. Verify that all the drives are present and healthy. If the drives are not visible, type SHUTDOWN SUBSYSTEM RESTART at the CLUI prompt to reboot both Controllers. If there is a drive missing, enter command SHOW PHYSICAL_DISK * . Then search through the list to find out which slot is not reporting (Figure 29). Display list is sorted by slot number.
28
Figure 29. Physical Disk List Example Screen

RAID[0]$ show physical_disk * all_attributes OID: Pool OID: Capacity: Raw Capacity: Block Size: Enabled Disk Ch: Disk Slot: Vendor ID: Product ID: Product Revision: Serial Number: Health State: Rotation Speed: Device Type: Member State: Spare: Failed: UUID: ..... 0x20a7003f UNASSIGNED 704512 MBs (0x56000000 blocks) 715404 MBs (0x575466f0 blocks) 512 0x27 0x22 1:42 Hitachi Hitachi HUA721075KLA330 GK8OAB0A GTF200P8GBVPXF GOOD 7200 RPM SATA UNASSIGNED FALSE FALSE 0x5000cca215c564560
2.3.6
Creating Storage Pools

A Storage Pool on a S2A6620 has the following attributes: RAID Level Storage Pools can be configured to use RAID1, RAID5 or RAID6 parity scheme. In RAID5, the capacity of one drive is reserved for parity, allowing data recovery in the event of a single drive loss in the Storage Pool. In RAID6, the capacity of two drives is reserved for parity, allowing data recovery if either one or two drives are down in a Storage Pool. For maximum data protection, DataDirect Networks recommends the use of RAID6. Chunk Size The chunk size defines the amount of data written to a single disk before proceeding to the next disk in the Storage Pool. For optimal performance, the chunk size should be proportional to the expected host request size. For example, a large chunk size should be used when transferring large blocks of data while a small chunk size should be used when transferring multiple small blocks of data. RAID1 does not take a chunk size. Drive Count A RAID5 Storage Pool may consist of 5 or 9 drives. A RAID6 Storage Pool may consist of 6 or 10 drives. For maximum performance, Storage Pools should be created using drives with the same characteristics (such as SAS/SATA, capacity, and RPM). To create a Storage Pool, use the CREATE POOL command: 1. At the CLUI prompt, type: CREATE POOL RAID_LEVEL=<RAID level> CHUNK_SIZE=<chunk size> {ASSIGN_POLICY=[SAS|SATA] NUMBER=<number of disks> or PHYSICAL_DISK=<list of disks>} where <RAID level>= raid5 or raid6; <chunk_size>=64kb, 128kb, or 256kb; <number of disks>= 5 or 9 drives for RAID 5, 6 or 10 drives for RAID 6; <list of disks>=index name of disks. You may either explicitly select the disks for the pool by using PHYSICAL_DISK= or specify the number of disks in the pool by using NUMBER= in which case the next available disks will be selected (Figure 30).
29
Figure 30. CREATE POOL Example (1)

RAID[0]$ create pool raid_level=raid5 chunk_size=64kb physical_disk=0x003e 0x003f 0x0040 0x0041 0x0042 POOL 0 OID=0x19b60000 create STATUS='Success' (0x0) RAID[0]$ create pool raid_level=raid6 chunk_size=128kb number=6 POOL 1 OID=0x19b80001 create STATUS='Success' (0x0)
If you specify the ASSIGN_POLICY and NUMBER parameters together (Figure 31), only the selected type of drives will be used for the Storage Pool and you will not need to enter the individual disk name.
Figure 31. CREATE POOL Example (2)
RAID[0]$ create pool raid_level=raid6 chunk_size=128kb number=6 assign_policy=sas POOL 2 OID=0x19b80002 create STATUS='Success' (0x0)
2. Use the CREATE POOL command to add more Storage Pools as needed. If you need to delete a Storage Pool, use the DELETE POOL <pool-id> command. NOTE : Storage Pool initialization is a background process and multiple storage pools can be initialized simultaneously. However, Virtual Disks on a Storage Pool are NOT accessible until its initialization is complete. 3. To view the list of configured Storage Pools, enter command SHOW POOL * (Figure 32).
Figure 32. Show Pool Information Screen
|Total |Free |Max | |Disk| Global |Spare | Idx|Name |State |Chunk|Raid| Faults |cap GB|cap GB|VD GB | Settings | Jobs |T/O |spare pool|Policy| --------------------------------------------------------------------------------------------------------------------0 pool-0 NORMAL 128 5 4104 0 0 W R F I 10 UNASSIGNED AUTO 1 pool-1 NORMAL 128 5 4104 0 0 W R F I 10 UNASSIGNED AUTO 2 pool-2 NORMAL 128 5 4104 0 0 W R F I 10 UNASSIGNED AUTO 3 pool-3 NORMAL 128 5 6192 0 0 W R F I I 10 UNASSIGNED AUTO 4 pool-4 NORMAL 128 5 6192 0 0 W R F I 10 UNASSIGNED AUTO 5 pool-5 NORMAL 128 5 6192 0 0 W R F I I 10 UNASSIGNED AUTO Total Storage Pools: 6
SHOW POOL <id> Pool (Figure 33).
ALL_ATTRIBUTES will display detailed information of the Storage
30
Figure 33. SHOW POOL ALL_ATTRIBUTES Example Screen

RAID[0]$ show pool 0 all_attributes OID: 0x19b40000 Type: STORAGE Name: 0x19b40000 Chunk Size: 64KB (0x80 blocks) Block Size: 512 RAID Type: RAID5 Free Raid5 Capacity: 2801664 MBs Max VD Size: 2801664 MBs Total Capacity: 3522560 MBs UUID: 0x00 Global Spare Pool: UNASSIGNED DiskTimeout(FRT): 10 minutes Init Policy: NO IO permitted Init Priority: 50% Full Rebuild Priority: 80% Fractional Rebuild Priority: 90% Sparing Policy: AUTOMATIC Assign Policy: Device Type: NA Rotation Speed: NA Raw Capacity: NA SATAssure: FALSE IO ROUTING: TRUE WBC: TRUE MWBC: FALSE Initializing: TRUE Rebuilding: FALSE Paused: FALSE AutoWriteLock: FALSE Critical: FALSE Current Home: 0x0015b2a122b20000 Future Home: 0xffffffffffffffff Preferred Home: 0x0015b2a122b20000 BkgdJob OID: 0x28000003 Total Phy Disks 5 State: NORMAL Member Size: 704512 MB pID State UUID 0x003e NORM 0x5000cca215c56e47 0x003f NORM 0x5000cca215c56456 0x0040 NORM 0x5000cca215c54c71 0x0041 NORM 0x5000cca215c5675c 0x0042 NORM 0x5000cca215c56e55
0x00000000 0x00000000 0x00000000
2.3.7
Creating Virtual Disks

A Virtual Disk can be created on just a part of a Storage Pool or uses all of the capacity of a single Storage Pool. To create a Virtual Disk, use the CREATE VIRTUAL_DISK command: 1. At the CLUI prompt, type: CREATE VIRTUAL_DISK CAPACITY=<capacity> POOL=<pool-id> where <capacity> is the capacity of the Virtual Disk in GiB or type max to use all available capacity; <pool-id> is the Storage Pool to be used by this Virtual Disk (Figure 34). A message is displayed to indicate whether the Virtual Disk creation was successful.
Figure 34. CREATE VIRTUAL DISKS Example Screen
RAID[0]$ create virtual_disk capacity=16 pool=0 VIRTUAL_DISK 0 OID=0x89ba000 creation STATUS='Success' (0x0) RAID[0]$ create virtual_disk capacity=32 pool=0 VIRTUAL_DISK 1 OID=0x89bb001 creation STATUS='Success' (0x0)
2. Use the CREATE VIRTUAL_DISK command to add more Virtual Disks as needed. If you need to delete a Virtual Disk, use the DELETE VIRTUAL_DISK <virtual disk-id> command.
31
NOTE : Virtual Disk(s) on a Storage Pool are NOT accessible until its initialization is complete. 3. To view the list of configured Virtual Disks, type SHOW VIRTUAL_DISK * (Figure 35).
Figure 35. Show Virtual Disk Information Screen
RAID[0]$ show virtual_disk * | Home |Background| Idx|Name | State |Pool|Raid|Cap GB|Settings| Jobs |Current|Preferred|Future| Job | --------------------------------------------------------------------------------------------------0 vd-0_0 READY 0 5 3632 W I 0(L) 0 0(L) 0 None INACTIVE 1 vd-1_1 READY 1 5 3632 W I 0(L) 0 1(R) 0 1(R) 0 INACTIVE 2 vd-2_2 READY 2 5 3632 W I 0(L) 0 0(L) 0 None INACTIVE 3 vd-3_3 NOT RDY 3 5 5480 W I I 0(L) 0 1(R) 0 1(R) 0 0x28000003 4 vd-4_4 READY 4 5 5480 W I 0(L) 0 0(L) 0 None INACTIVE 5 vd-5_5 NOT RDY 5 5 5480 W I I 0(L) 0 1(R) 0 1(R) 0 0x28000005 Total Virtual Disks: 6
SHOW POOL <id> ALL_ATTRIBUTES will display detailed information of the Storage Pool POOL <id> ALL_ATTRIBUTES will display detailed information of the Storage PoolSHOW VIRTUAL_DISK <id> ALL_ATTRIBUTES will display detailed information of the Virtual Disk (Figure 36).
Figure 36. SHOW VIRTUAL_DISK ALL_ATTRIBUTES Example Screen
RAID[0]$ show virtual_disk 0 all_attributes OID: 0x89ba0000 Name: 89ba0000 POOL OID: 0x19b40000 Capacity: 16384 MBs Offset: 0x0 State: NOT RDY Raidlevel: RAID5 IO ROUTING: TRUE WBC: TRUE MWBC: FALSE Initializing: TRUE Paused: FALSE AutoWriteLock: FALSE Critical: FALSE Present Home Only:FALSE Current Home: 0x0015b2a122b20000 0x00000000 Future Home: 0xffffffffffffffff 0x00000000 Preferred Home: 0x0015b2a122b20000 0x00000000 BkgdJob OID: 0x28000000 UUID: 60001ff0722b20000000000089ba0000
2.3.8
Creating Spare Pools

The S2A6620 supports the concept of Spare Pool. A Spare Pool contains Physical Disks that can be used as spare disks in one or more Storage Pools. In the event of drive failure, a drive that is assigned to a spare pool is automatically swapped into the Storage Pool to replace the failed drive. A rebuild then occurs immediately, reducing the possibility of data loss due to additional drive failures. Spare pools can be shared by Storage Pools or dedicated to a particular Storage Pool in which case the spare disks will only be used by the designated Storage Pool. After a spare pool is created, you will need to select drive(s) from the Unassigned Pool and assign it to the spare pool. To create a spare pool: 1. At the CLUI prompt, type: CREATE SPARE_POOL (Figure 37)
32
A message is displayed to indicate whether the new spare pool creation was successful.
Figure 37. CREATE SPARE POOL Example Screen
RAID[0]$ create spare_pool SPARE POOL 6 OID=0x19bc0006 create STATUS=Success (0x0)
2. Assign disk(s) to the spare pool, enter command: ASSIGN PHYSICAL_DISK <disk-id> TO_POOL <pool-id> where <disk-id> is the index name of the disk to be added. To view the list of unassigned disks, enter command SHOW UNASSIGNED_POOL PHYSICAL_DISK A message is displayed to indicate whether the disk has been added to the spare pool (Figure 38).
Figure 38. Assign Physical Disk to Spare Pool Example Screen
RAID[0]$ assign physical_disk 0x004e to_pool 6 PHYSICAL_DISK 78 OID=0x20b6004e assigned to POOL 6 OID=0x19bc0006STATUS=Success (0x0)
3. Use the CREATE SPARE_POOL and ASSIGN PHYSICAL_DISK commands to create more spare pools as needed. If you need to delete a disk from the spare pool, enter command ASSIGN PHYSICAL_DISK <disk-id> TO_POOL 0x1800ffff To delete a spare pool, enter command DELETE SPARE_POOL <pool-id> 4. To view the list of configured spare pool(s), enter command SHOW SPARE_POOL * (Figure 39).
Figure 39. Show Spare Pool Information Screen
RAID[0]$ show spare * |Disk |Total |Total|Storage | Idx|Name |Blocks| T/O |Cap GB| PDs |Pool Idx| ------------------------------------------------------------6 spare_pool-6 512 10 0 0 7 spare_pool-7 512 10 0 0 Total Spare Pools: 2
SHOW SPARE_POOL <id> ALL_ATTRIBUTES will display detailed information of the spare pool (Figure 40). SHOW SPARE_POOL <id> PHYSICAL_DISKS will display the list of disks in the pool.
Figure 40. Show Spare Pool Example Screen (2)
RAID[0]$ show spare_pool 6 all_attributes OID: 0x19bc0006 Type: GLOBAL SPARE Name: 19bc0006 Block Size: 0x200 DiskTimeout(FRT): 10 minutes Total Capacity: 1409024 MBs UUID: 0x00 Total Phy Disks 2 RAID[0]$ show spare_pool 6 physical_disk OID: 0x20b6004e Index: 0x004e OID: 0x20b7004f Index: 0x004f
5. Assign spare pools to Storage Pools. Enter command: SET POOL <pool-id> SPARE_POOL <spare-pool-id>
33
where <pool-id> and <spare-pool-id> are the index names of the Storage Pool and spare pool respectively. NOTE : Each Storage Pool must have a spare pool assigned to it. If a Storage Pools attributes show Global Spare Pool: UNASSIGNED no spare pool will serve this Storage , Pool. A message is displayed to indicate whether the spare pool has been designated (Figure 41). Repeat this step for each Storage Pool in the system.
Figure 41. Set Storage Pool to Spare Pool Example Screen
RAID[0]$ set pool 0 spare_pool 6 POOL 0 OID=0x19b40000 attributes set with STATUS=Success (0x0)
6. Use the SHOW POOL command to view the new Storage Pool information (Figure 42).
Figure 42. Show Pool Example Screen
RAID[0]$ show pool 0 all_attributes OID: 0x19b40000 Type: STORAGE Name: 0x19b40000 Chunk Size: 64KB (0x80 blocks) Block Size: 0x200 RAID Type: RAID5 Free Raid5 Capacity: 2752512 MBs Total Capacity: 3522560 MBs UUID: 0x00 Global Spare Pool: 0x19bc0006 DiskTimeout(FRT): 10 minutes Init Policy: NO IO permitted ....
2.3.9
Initializing the Host System

When a Storage Pool is created, initialization begins automatically and will continue in the background until it is completed. Once the Storage Pool has completed its initialization, its Virtual Disk(s) can be accessed immediately. To monitor the progress of a job, use the SHOW JOB * ALL_ATTRIBUTES command. It will display the type of job and the percentage of completion (Figure 43).
Figure 43. Show Job Example Screen
RAID[0]$ show job * all_attributes OID: 0x28000000 Target: 0x19b40000 Type: INITIALIZE Status: RUNNING Priority: 50 Fraction Complete:71%
34
You may also check if a Virtual Disk is ready for access using the SHOW VIRTUAL_DISK <id> ALL_ATTRIBUTES command (Figure 44).
Figure 44. Show Virtual Disk Example Screen
RAID[0]$ show virtual_disk 0 all_attributes OID: 0x89ba0000 Name: 89ba0000 POOL OID: 0x19b40003 Capacity: 16384 MBs Offset: 0x0 State: READY Raidlevel: RAID5 IO ROUTING: TRUE WBC: TRUE MWBC: FALSE Initializing: FALSE Paused: FALSE AutoWriteLock: FALSE Data Lost: FALSE Present Home Only:FALSE ....
2.3.9.1
Present Virtual Disk to External Host

A Presentation on a S2A6620 has the following components: Discovered Initiators A Discovered Initiator is defined as a Fibre-channel initiator that has logged into the S2A6620. This is normally a single port on a Fibre-channel HBA in an external computer. Host A Host is an abstract client of a Virtual Disk that has all the access to all data within the Virtual Disk. This most commonly represents an external computer with one or more Fibre Channel initiators. Host attributes are OS (operating system) of which you can select GENERIC, WINDOWS, LINUX or MAC_OS. The OS attribute dictates the way the controller responds to certain Fibre-channel commands where appropriate. For example, Mac OS X expects a different response from an inquiry of LUN0 (the controller LUN) than a Windows host. Channel A Channel is one of the Fibre-channel ports on the controller. Channel attributes are MODE of which you can select either MAC_OS or STANDARD. When MAC_OS is selected, the ports node name will be set differently in order to be visible to a Macintosh system. Stack A Stack is the input side of the subsystem. In the case of the S2A6620, the stack is defined as the Fibre-channel interface. In future versions of the product, different interface stacks may exist. Presentation A Presentation is the relationship between a Host and a Virtual Disk. A presentation implies that the related Host has some sort of access to the Virtual Disk. Attributes of a Presentation are: PORT - from which the host will see the virtual disk READ_ONLY - controls read only access PRESENT_HOME_ONLY - presents the specified Virtual Disk from its designated home controller only LUN - user-specified the LUN number that the Virtual Disk will show to the host.
To create a host: Use the APPLICATION CREATE HOST [OSTYPE=GENERIC|LINUX|MAC_OS|WINDOWS] command where OSTYPE is the operating system. Generic is the default.
To delete a host:
35
Use the APPLICATION DELETE
HOST=<object-id>.
To display presentations associated with the specified application host: Use the APPLICATION SHOW HOST=<object-id> [PRESENTATIONS] command. To display the presentations associated with the specified application host: Use the APPLICATION SHOW HOST=<object-id> [INITIATORS] command. To create a presentation to a Virtual Disk for the specified host: Use the APPLICATION CREATE PRESENTATION VIRTUAL_DISK=<object-id> HOST=<object-id> |ALL command. To create an initiator object that is associated with the specified host: Use the APPLICATION IMPORT DISCOVERED_INITIATOR=<object-id> HOST=<object-id> command. To simply present the virtual disk to all controller ports for both controllers (promiscuous mode): Use the APPLICATION CREATE PREENTATION VIRTUAL_DISK=<object-id> HOST=ALL command.
2.3.10
Setup Email and SNMP

The tables below detail the additional inquiry items and events that will be trapped in the SMNP MIB and in the Email Agent.
Figure 45. SNMP and Email Notification Events SNMP EVENTS ERROR DESCRIPTION
LOG_ES_EXPANDER_ELEMENT_ERROR LOG_ES_POWER_SUPPLY_NORMAL LOG_ES_POWER_SUPPLY_REMOVED LOG_ES_POWER_SUPPLY_INSERTED LOG_ES_TEMPERATURE_SENSOR_NORMAL LOG_ES_TEMPERATURE_SENSOR_REMOVED LOG_ES_TEMPERATURE_SENSOR_INSERTED LOG_ES_COOLING_ELEMENT_NORMAL LOG_ES_COOLING_ELEMENT_REMOVED
A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has reported an error condition. The power supply has returned to a normal status. A power supply has been removed. A power supply has been inserted. A temperature sensor (located in the power supply) has returned to normal status. A temperature sensor (located in the power supply) has been removed. A temperature sensor (located in the power supply) has been inserted A fan (located in the power supply) has returned to normal status A fan (located in the power supply) has been removed.
36
Figure 45. SNMP and Email Notification Events SNMP EVENTS ERROR DESCRIPTION
LOG_ES_COOLING_ELEMENT_INSERTED LOG_ES_EXPANDER_ELEMENT_NORMAL LOG_ES_EXPANDER_ELEMENT_REMOVED LOG_ES_EXPANDER_ELEMENT_INSERTED LOG_ES_DISK_SLOT_ELEMENT_REMOVED LOG_ES_DISK_SLOT_ELEMENT_INSERTED
A fan (located in the power supply) has been inserted The DEM reports normal. A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has been removed. A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has been inserted. A device has been removed from a disk slot. A device has been inserted into a disk slot.
Email Notification Events A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has reported an error condition.
LOG_ES_EXPANDER_ELEMENT_ERROR
2.3.10.1
Setup Email
There is only one logical EMAIL_AGENT for the subsystem. While each controller has an EMAIL_AGENT, the two are ideally managed as a single, logical SNMP_AGENT in that all of their settable attribute values are shared. Wild-card object-IDs may be used in the SHOW command. Automatic emails will be sent as notification of a selected group of warning and error events that have occurred on the controller. To set email address, use the command, UI SET EMAIL IP_ADDRESS=<ip_address> IP_PORT=<port> FROM= <email> TO=<email> SUBJECT="text". EXAMPLE:
S2A 6620-9 RAID[1]$ UI SET EMAIL IP_ADDRESS=10.255.128.38 IP_PORT=30 FROM="6620@DDN.COM" TO="6620_USER@DDN.COM" SUBJECT="DDN S2A6620-9-2:EVENT NOTIFICATION" EMAIL AGENT SET WITH STATUS='SUCCESS' (0X0)
To show all email address attributes, use the command, UI SHOW EMAIL ALL.. EXAMPLE:
S2A 6620-9 RAID[1]$ UI SHOW EMAIL ALL E-MAIL AGENT ATTRIBUTES IP_ADDRESS=10.255.128.38 IP_PORT=30 FROM=6620@DDN.COM TO=6620_USER@DDN.COM SUBJECT=DDN S2A6620-9-2:EVENT NOTIFICATION
2.3.10.2
Setup SNMP
There is one logical SNMP_AGENT for the subsystem. While each controller has an SNMP_AGENT, the two are managed as a single, logical SNMP_AGNET in that all of their settable attribute values are shared. Wild-card object-IDs may be used in the SHOW command.
37
The Simple Network Management Protocol (SNMP) monitors network attached devices for conditions that warrant administrative attention. In Version 1.1, SNMP traps have been implemented to monitor critical and warning events. A management information base (MIB) has also been created to be used to provide inquiry objects and events to the users monitoring application. The provided SNMP traps expose management data on the managed system in the areas of temperature senor, fans, power supplies, pools, and physical disks as well as a variety of real-time critical and error events. To set email address, use the command, UI SET SNMP IP_ADDRESS=<ip_address> COMMUNITY=<name>. EXAMPLE:
RAID[1]$ UI SET SNMP IP_ADDRESS=101.243.23.10 COMMUNITY="DDN 6620" SNMP AGENT SET WITH STATUS='SUCCESS' (0X0)
To show all SNMP trap agent attributes, use the command, UI SHOW SNMP. EXAMPLE:
RAID[1]$ UI SHOW SNMP ALL SNMP TRAP AGENT ATTRIBUTES IP_ADDRESS=101.243.23.10 COMMUNITY=DDN 6620
38
S ECTION 3
S2A6620 Management
Managing the S2A6620
3.1

The S2A6620 provides a set of tools that enable administrators to centrally manage the network storage and resources that handle business-critical data. These include Configuration Management, Performance Management, and Firmware Update Management. NOTE : The command descriptions given in this User Guide only apply to Firmware Version 1.0.3.3.xxxx. To access the most up-to-date commands, use the CLUIs Online Help feature.
3.1.1
Management Interface
SAN management information for the S2A6620 can be accessed locally through a serial interface, or remotely through SSH. NOTE : An S2A6620 may only have one active login (serial or SSH) per Controller at any given time.
Locally via Serial Interface Any RS-232 terminal or terminal emulator (such as Hyperterminal) can be used to configure and monitor the S2A6620. 1. Connect the supplied mini-jack cable to the port labeled CLI on Controller 1 (Figure 46). Connect the other end of the cable to a serial port on a standard PC.
Figure 46. CLI Port on Controller
CLI Connector
EXPANSION CLI
LINK
PORT 2 PORT 1
SPEED
2. Load a serial console program (such as HyperTerminal, minicom, and screen) and use the following settings for the serial connection: Bits per second: 115,200 Data bits: Parity: Stop bits: Flow control: 8 None 1 None
3. Once connected, press the <Enter> key to bring up the password prompt. Enter the password: user. Remotely via SSH To configure and monitor the S2A6620 remotely, connect the S2A to your Ethernet network. Please refer to Section 3.6 for further information on how to set up the S2As network interface.
41
3.1.2
User Logins
RS-232 Login For a terminal session, press the <Enter> key to bring up the password prompt. Enter the password: user NOTE : If the system prompts you for a user name, enter the user name: user.
Login via SSH For a SSH session, enter the user name user and password user (Figure 47). Both are case sensitive.
Figure 47. SSH Login Screen
login as: user user@10.23.23.16s password: Linux (none) 2.6.25-ddn-016620-3 #2 SMP Wed Jan 14 10:38:28 MST 2009 x DataDirect Networks Storage Scalar 6620(tm) J
Logout To logout, enter command QUIT. For SSH connection, the current session will be disconnected.
3.1.3
Available Commands
Entering the ? character at the CLUI prompt will display the available commands within the S2A6620 CLUI (Figure 48). To get help information on a command, type the command followed by a question mark. For example, ASSIGN ?<Enter> will display help on assign options on the system.
Figure 48. Help Screen
RAID[0]$ ? Select one of the following subjects for additional commands: APPLICATION Selects the application processor as the subject RAID Selects the raid processor as the subject UI Selects the user interface as the subject Additional commands: HELP Provides information on how to use the user interface help QUIT Exits the Command Line User Interface Object class options available for default subject RAID: Available keywords: ASSIGN Assign raid object CLEAR Clear raid object states CREATE Create raid objects DELETE Delete raid objects LOCATE Locate raid objects MOVE_HOME Locate raid objects PAUSE Pause raid objects REPLACE Replace raid objects RESUME Resume raid objects SET Set raid objects SHOW Display raid objects SHUTDOWN Shutdown raid objects SYNCHRONIZE Synchronize raid objects UPDATE_FIRMWARE Update firmware on raid objects
42
3.1.3.1
Basic Key Operations

The command line editing and history features support ANSI and VT-100 terminal modes. The command history buffer can hold up to 64 commands. The full command line editing and history only work on main CLI and SSH sessions when entering new commands. Basic Key Assignments are listed in Figure 49. Simple, not full command, line editing only is supported when the: CLUI prompts the user for more information. alternate CLUI prompt is active. (The alternate CLUI is used on the RS-232 connection during an active SSH session.) NOTE : Not all SSH programs support all the keys listed in Figure 49.
Figure 49. Basic Key Assignments Key Backspace Delete Up Arrow Down Arrow Right Arrow Left Arrow Home End Insert PgUp PgDn Ctrl-U Ctrl-K Ctrl-A Ctrl-E ANSI CTRL or Escape Sequence Ctrl-H Del, or Esc [3~ Esc [A Esc [B Esc [C Esc [D Esc [H or Esc [1~ Esc [K or Esc [4~ Esc [2~ Esc [5~ Esc [6~ Ctrl-U Ctrl-K Ctrl-A Ctrl-E Description deletes preceding character deletes current character retrieves previous command in the history buffer retrieves next command in the history buffer moves cursor to the right by one character moves cursor to the left by one character get the oldest command in the history buffer get the latest command in the history buffer toggles between insert mode and overtype mode retrieves oldest command in the history buffer retrieves latest command in the history buffer delete to beginning of line delete to end of line move cursor to beginning of line move cursor to end of line
43
Configuration Management
3.2
The S2A6620 provides uniform configuration management across a heterogeneous SAN.
3.2.1
Monitor Status of Storage Assets

The drives in the system are categorized into one of the following pools: Unassigned Pool - By default, all the drives or replacement drives are initially allocated to this pool. When a drive has failed or been released (from a spare pool, for example) it is also moved to this pool. Storage Pool (sometimes referred to as a RAID group) - A collection of 5 to 10 disk drives, ideally of the same capacity and type. Spare Pool - This type of pool contains Physical Disks that can be used as spare disks in one or more Storage Pools.
3.2.1.1
Disk Information
SHOW PHYSICAL_DISK * displays a list of all the disks installed in the system (Figure 50). SHOW UNASSIGNED_POOL PHYSICAL_DISK displays the list of unassigned disks. SHOW PHYSICAL_DISK=<disk-id> ALL retrieves information about a specific disk
(Figure 51).
44
Figure 50. Show Physical Disk List Example Screen

RAID[0]$ show physical_disk * |Member| Encl|Slot| Vendor | Product ID |Type|Cap GB |RPM|Revision| Serial Number |Pool|Status| Idx|Status| WWN | -------------------------------------------------------------------------------------------------------------------------------1 1 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZLKH UNAS GOOD 57 5000cca20def4516 1 2 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKNL79H UNAS GOOD 32 NORM 5000cca20df3a263 1 3 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKD8Y5F UNAS GOOD 42 NORM 5000cca20defdc87 1 4 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK72BLH UNAS GOOD 1 NORM 5000cca20ded7e05 1 5 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB269H UNAS GOOD 38 NORM 5000cca20def4edd 1 6 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB1LHH UNAS GOOD 23 NORM 5000cca20def4c96 1 7 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF200P8G6K2YF UNAS GOOD 40 NORM 5000cca215c2fa66 1 8 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKA6P9H UNAS GOOD 41 NORM 5000cca20deeeb53 1 9 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAGVYF UNAS GOOD 47 5000cca20def0a0a 1 10 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKA5SDH 2 GOOD 45 NORM 5000cca20deee7d3 1 11 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK8VH8F 2 GOOD 39 NORM 5000cca20dee4cee 1 12 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZ75H 1 GOOD 26 NORM 5000cca20def43b5 1 13 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTMNRF 4 GOOD 20 NORM 5000cca215cb32bd 1 14 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTLDJF 4 GOOD 33 NORM 5000cca215cb2dfe 1 15 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPR7F 3 GOOD 3 NORM 5000cca215cb3a6e 1 16 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPW9F 5 GOOD 50 NORM 5000cca215cb3b0b 1 17 Hitachi HUA721050KLA330 SATA 465 7K GK6OAB0A GTE402P6G94E8E 1 GOOD 27 NORM 5000cca214c427f6 1 18 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPNXF UNAS GOOD 58 5000cca215cb3a45 1 19 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPTBF 4 GOOD 18 NORM 5000cca215cb3ab0 1 20 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKSMX8D 0 GOOD 21 NORM 5000cca20df505cb 1 21 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKERMGF 0 GOOD 17 NORM 5000cca20df08447 1 22 Hitachi HUA721050KLA330 SATA 465 7K GK6OAB0A GTE402P6G9M0SE 1 GOOD 28 NORM 5000cca214c45ec1 1 23 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKNTM6D 1 GOOD 35 NORM 5000cca20df3ba5a 1 24 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKKVV3F 1 GOOD 30 NORM 5000cca20df26595 1 25 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN35ZAKE8HZH 0 GOOD 5 NORM 5000cca20df04f4d 1 26 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKDW9PH 0 GOOD 6 NORM 5000cca20df0217e 1 27 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKSNNDD 0 GOOD 8 NORM 5000cca20df50898 1 28 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZ4LH 0 GOOD 9 NORM 5000cca20def4365 1 29 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB2GEH 2 GOOD 37 NORM 5000cca20def4fd9 1 30 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKESH1F 1 GOOD 31 NORM 5000cca20df0877f 1 31 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN03ZAGMUMUD UNAS GOOD 49 5000cca20dc9034c 1 32 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN35ZAK6VLBF 1 GOOD 25 NORM 5000cca20ded6490 1 33 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKN0S7F 1 GOOD 36 NORM 5000cca20df360bf 1 34 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK9VNRH 2 GOOD 44 NORM 5000cca20deec1f6 1 35 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKL1MYH 0 GOOD 22 NORM 5000cca20df27b5c 1 36 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN03ZAGH9Y4D 2 GOOD 43 NORM 5000cca20dc6f6e1 1 37 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSLNF 3 GOOD 7 NORM 5000cca215cb4181 1 38 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRPVF 5 GOOD 54 NORM 5000cca215cb3e23 1 39 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSMGF 3 GOOD 14 NORM 5000cca215cb419a 1 40 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTK4HF 5 GOOD 56 NORM 5000cca215cb2944 1 41 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRPDF 5 GOOD 52 NORM 5000cca215cb3e15 1 42 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRLVF 4 GOOD 24 NORM 5000cca215cb3dc6 1 43 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTNPYF 3 GOOD 13 NORM 5000cca215cb36a4 1 44 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPWUF 5 GOOD 53 NORM 5000cca215cb3b1b 1 45 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPSHF 3 GOOD 12 NORM 5000cca215cb3a95 1 46 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPKNF 4 GOOD 29 NORM 5000cca215cb39e0 1 47 Hitachi HUA721050KLA330 SATA 465 7K GK6OAB0A GTE402P6G94EYE 2 GOOD 46 NORM 5000cca214c4280b 1 48 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTRP6F 5 GOOD 51 NORM 5000cca215cb3e0f 1 49 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTV0KF 4 GOOD 15 NORM 5000cca215cb4a93 1 50 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTUYLF 3 GOOD 2 NORM 5000cca215cb4a56 1 51 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSJZF UNAS GOOD 59 5000cca215cb414d 1 52 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTNV9F 5 GOOD 55 NORM 5000cca215cb372b 1 53 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTTZ5F 4 GOOD 19 NORM 5000cca215cb46a7 1 54 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTR3ZF 4 GOOD 34 NORM 5000cca215cb3bf9 1 55 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTT3DF 3 GOOD 4 NORM 5000cca215cb4369 1 56 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPGWF 3 GOOD 10 NORM 5000cca215cb398a 1 57 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPH3F 3 GOOD 11 NORM 5000cca215cb3991 1 58 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSMLF 4 GOOD 16 NORM 5000cca215cb419e 1 59 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTSK6F UNAS GOOD 60 5000cca215cb4154 1 60 Hitachi HUA721075KLA330 SATA 698 7K GK8OA70M GTF202P8GTPATF 5 GOOD 48 NORM 5000cca215cb390b Total Physical Disks: 60 Total Assigned Disks: 54 Total Unassigned Disks: 6 Total SATA Disks: 60 Total Member State Normal:
54
Figure 51. Physical Disk Information Example Screen

RAID[0]$ show physical_disk 0x003f all_attributes OID: Pool OID: Capacity: Raw Capacity: Block Size: Enabled Disk Ch: Disk Slot: Vendor ID: Product ID: Product Revision: Serial Number: Health State: Rotation Speed: Device Type: Member State: Spare: Failed: UUID: 0x20a7003f UNASSIGNED 704512 MBs (0x56000000 blocks) 715404 MBs (0x575466f0 blocks) 512 0x27 0x22 1:42 Hitachi Hitachi HUA721075KLA330 GK8OAB0A GTF200P8GBVPXF GOOD 7200 RPM SATA UNASSIGNED FALSE FALSE 0x5000cca215c564560
45
If there is a failed drive, SHOW UNASSIGNED_POOL FAILED ALL will display the failed drives information (Figure 52).
Figure 52. Show Failed Drive Example Screen
RAID[0]$ show unassigned_pool failed all OID: 0x20a7003f Pool OID: UNASSIGNED Capacity: 704512 MBs (0x56000000 blocks) Raw Capacity: 715404 MBs (0x575466f0 blocks) Block Size: 512 Enabled Disk Ch: 0x27 0x22 Disk Slot: 1:42 Vendor ID: Hitachi Product ID: Hitachi HUA721075KLA330 Product Revision: GK8OAB0A Serial Number: GTF200P8GBVPXF Health State: FAILED Rotation Speed: 7200 RPM Device Type: SATA Member State: UNASSIGNED Spare: FALSE Failed: TRUE UUID: 0x5000cca215c564560
3.2.1.2
Storage Pool View

Storage pools are the basic building blocks of the S2A6620. SHOW POOL * displays the list of configured Storage Pools in the system (Figure 53).
Figure 53. Show Configured Storage Pool List Example Screen
RAID[0]$ show pool * |Total |Free |Max | |Disk| Global |Spare | Idx|Name |State |Chunk|Raid| Faults |cap GB|cap GB|VD GB | Settings | Jobs |T/O |spare pool|Policy| --------------------------------------------------------------------------------------------------------------------0 pool-0 NORMAL 128 5 4104 0 0 W R F I 10 UNASSIGNED AUTO 1 pool-1 NORMAL 128 5 4104 0 0 W R F I 10 UNASSIGNED AUTO 2 pool-2 NORMAL 128 5 4104 0 0 W R F I 10 UNASSIGNED AUTO 3 pool-3 NORMAL 128 5 6192 0 0 W R F I 10 UNASSIGNED AUTO 4 pool-4 NORMAL 128 5 6192 0 0 W R F I 10 UNASSIGNED AUTO 5 pool-5 NORMAL 128 5 6192 0 0 W R F I 10 UNASSIGNED AUTO Total Storage Pools: 6
NOTE : If you issue the command, SHOW POOLS * , and the pools indicate there is a fault, check the details of the pool. The pool will go into WR thru state on initial startup to allow the batteries the opportunity to charge. The WR Thru mode is necessary to allow for data integrity until battery redundancy on each controller is completed. If there is a battery issue, the system will indicate replacement is required and all VDs will remain in WR Thru mode until the issue is resolved. SHOW POOL <id> PHYSICAL_DISK displays the list of disks associated with the specified Storage Pool (Figure 54).
46
Figure 54. Show Storage Pools Physical Disks Example Screens

RAID[0]$ show pool 0 physical_disk |Member| Encl|Slot| Vendor | Product ID |Type|Cap GB |RPM|Revision| Serial Number |Pool|Status| Idx|Status| WWN | -------------------------------------------------------------------------------------------------------------------------------1 4 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAK72BLH 0 GOOD 1 NORM 5000cca20ded7e05 1 6 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKB1LHH 0 GOOD 23 NORM 5000cca20def4c96 1 20 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKSMX8D 0 GOOD 21 NORM 5000cca20df505cb 1 21 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKERMGF 0 GOOD 17 NORM 5000cca20df08447 1 25 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN35ZAKE8HZH 0 GOOD 5 NORM 5000cca20df04f4d 1 26 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVP65ZAKDW9PH 0 GOOD 6 NORM 5000cca20df0217e 1 27 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN63ZAKSNNDD 0 GOOD 8 NORM 5000cca20df50898 1 28 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKAZ4LH 0 GOOD 9 NORM 5000cca20def4365 1 35 HITACHI HDS725050KLA360 SATA 465 7K K2AOAD1A KRVN65ZAKL1MYH 0 GOOD 22 NORM 5000cca20df27b5c Total Physical Disks: 9 Total Assigned Disks: 9 Total Unassigned Disks: 0 Total SATA Disks: 9 Total Member State Normal:
SHOW POOL <id> VIRTUAL_DISK displays the list of Virtual Disks associated with the specified Storage Pool (Figure 55).
Figure 55. Show Storage Pools Virtual Disks Example Screens
RAID[0]$ show pool 0 virtual_disk | Home |Background| Idx|Name | State |Pool|Raid|Cap GB|Settings| Jobs |Current|Preferred|Future| Job | --------------------------------------------------------------------------------------------------0 vd-0_0 READY 0 5 3632 W I 0(L) 0 0(L) 0 None INACTIVE Total Virtual Disks: 1
SHOW POOL <id> ALL displays detailed information of the Storage Pool (Figure 56).
47
Figure 56. Show Storage Pool Details Example Screen

RAID[0]$ show pool 0 all_attributes OID: 0x19b40000 Type: STORAGE Name: 0x19b40000 Chunk Size: 64KB (0x80 blocks) Block Size: 0x200 RAID Type: RAID5 Free Raid5 Capacity: 2801664 MBs Max VD Size: 2801664 MBs Total Capacity: 3522560 MBs UUID: 0x00 Global Spare Pool: UNASSIGNED DiskTimeout(FRT): 10 minutes Init Policy: NO IO permitted Init Priority: 50% Full Rebuild Priority: 80% Fractional Rebuild Priority: 90% Sparing Policy: AUTOMATIC Assign Policy: Device Type: NA Rotation Speed: NA Raw Capacity: NA SATAssure: FALSE IO ROUTING: TRUE WBC: TRUE MWBC: FALSE Initializing: TRUE Rebuilding: FALSE Paused: FALSE AutoWriteLock: FALSE Critical: FALSE Current Home: 0x0015b2a122b20000 Future Home: 0xffffffffffffffff Preferred Home: 0x0015b2a122b20000 BkgdJob OID: 0x28000003 Total Phy Disks 5 State: NORMAL Member Size: 704512 MB pID State UUID 0x003e NORM 0x5000cca215c56e47 0x003f NORM 0x5000cca215c56456 0x0040 NORM 0x5000cca215c54c71 0x0041 NORM 0x5000cca215c5675c 0x0042 NORM 0x5000cca215c56e55
0x00000000 0x00000000 0x00000000
3.2.1.3
Virtual Disk View

SHOW VIRTUAL_DISK * displays the list of configured Virtual Disks in the system (Figure 57).
Figure 57. List of Virtual Disks Example Screens
RAID[0]$ show virtual_disk * | Home |Background| Idx|Name | State |Pool|Raid|Cap GB|Settings| Jobs |Current|Preferred|Future| Job | --------------------------------------------------------------------------------------------------0 vd-0_0 READY 0 5 3632 W I 0(L) 0 0(L) 0 None INACTIVE 1 vd-1_1 READY 1 5 3632 W I 0(L) 0 1(R) 0 1(R) 0 INACTIVE 2 vd-2_2 READY 2 5 3632 W I 0(L) 0 0(L) 0 None INACTIVE 3 vd-3_3 READY 3 5 5480 W I 0(L) 0 1(R) 0 1(R) 0 INACTIVE 4 vd-4_4 READY 4 5 5480 W I 0(L) 0 0(L) 0 None INACTIVE 6 vd-6_5 READY 5 5 5480 W I 0(L) 0 1(R) 0 1(R) 0 INACTIVE Total Virtual Disks: 6
SHOW VIRTUAL_DISK <id> ALL_ATTRIBUTES will display detailed information of the Virtual Disk (Figure 58).
48
Figure 58. Show Virtual Disk Details Example Screen

RAID[0]$ show virtual_disk 0 all_attributes OID: 0x89ba0000 Name: 89ba0000 POOL OID: 0x19b40000 Capacity: 16384 MBs Offset: 0x0 State: NOT RDY Raidlevel: RAID5 IO ROUTING: TRUE WBC: TRUE MWBC: FALSE Initializing: TRUE Paused: FALSE AutoWriteLock: FALSE Data Lost: FALSE Present Home Only:FALSE Current Home: 0x0015b2a122b20000 0x00000000 Future Home: 0xffffffffffffffff 0x00000000 Preferred Home: 0x0015b2a122b20000 0x00000000 BkgdJob OID: 0x28000000 UUID: 60001ff0722b20000000000089ba0000
3.2.1.4
Spare Pool View

SHOW SPARE_POOL * will display the list of configured spare pool(s) (Figure 59).
Figure 59. List of Spare Pools Example Screens
RAID[0]$ show spare_pool * |Disk |Total |Total|Storage | Idx|Name |Blocks| T/O |Cap GB| PDs |Pool Idx| ------------------------------------------------------------6 spare_pool-6 512 10 0 0 7 spare_pool-7 512 10 0 0 Total Spare Pools: 2
To display detailed information of the spare pool: Use the SHOW SPARE_POOL <id> ALL_ATTRIBUTES command (Figure 60). To display the list of disks in the pool: Use the SHOW SPARE_POOL <id> PHYSICAL_DISKS command.
Figure 60. Show Spare Pool Example Screen
RAID[0]$ show spare_pool 6 all_attributes OID: 0x19bc0006 Type: GLOBAL SPARE Name: 19bc0006 Block Size: 0x200 DiskTimeout(FRT): 10 minutes Total Capacity: 1409024 MBs UUID: 0x00 Total Phy Disks 2 RAID[0]$ show spare_pool 6 physical_disk OID: 0x20b6004e Index: 0x004e OID: 0x20b7004f Index: 0x004f
3.2.1.5
Visual Indication
Locate Physical Disk LOCATE PHYSICAL_DISK <id> provides a visual indication of the specified drive. The status LED of the drive will blink.
49
LOCATE UNASSIGNED_POOL provides a visual indication of the drives that are unassigned. The status LED of the drives will blink. LOCATE UNASSIGNED_POOL FAILED provides a visual indication of the drives that have failed. The status LED of the drives will blink. Locate Storage Pool LOCATE POOL <id> provides a visual indication of the specified Storage Pool. The status LED of the drives in the specified Storage Pool will blink. Locate Enclosure LOCATE ENCLOSURE <id> provides a visual indication of the specified enclosure. The Shelf Identify LED of the enclosure will blink.
50
3.2.2
Storage Pool & Virtual Disk Management

The S2A6620 creates centrally-managed and vendor-independent storage pooling. It enables different types of storage to be aggregated into a single logical storage resource from which virtual volumes (virtual disks) can be served up to multi-vendor host computers. The networked storage pools will provide the framework to manage the growth in storage demand from web-based applications, database growth, network data-intensive applications, and disaster tolerance capabilities. The storage array may consist of up to 24 Storage Pools. The Storage Pools can be used individually or split into multiple Virtual Disks. A Virtual Disk can be as small as part of a Storage Pool or uses all of the capacity of a single Storage Pool. Virtual disks allocate space in 8 GiB increments. For example, 16 GiB of storage space will be allocated when creating a Virtual Disk of 10 GiB. Up to 64 Virtual Disks are supported in total. NOTE : In this document, the terms "GB" and "GiB" are used interchangeably, and denote 1,073,741 bytes (230 bytes). You can add and remove Storage Pools without affecting system operations. Use the SHOW POOL * command to display the current list of Storage Pools (Figure 61).
Figure 61. Show Storage Pool List Example Screen
RAID[0]$ show pool * OID: 0x19b40000 Index: 0x0000 Name: 19b40000 OID: 0x19b60001 Index: 0x0001 Name: 19b60001
3.2.2.1
Changing the Disks Status

SET PHYSICAL_DISK <disk-id> FAILED instructs the system to fail the specified disk. When a non-SPARE disk is specified and it is failing, the disk will not cause a multi-channel failure. The disk is marked as failed. An attempt is made to replace it with a spare disk. When a SPARE disk is specified, it is released, but marked as unhealthy and unavailable. CLEAR PHYSICAL_DISK <disk-id> FAILED changes the specified disks Failed state to FALSE. After clearing a disk, use the ASSIGN PHYSICAL_DISK <disk-id> TO_POOL <pool-id> SET_SPARE command to add the disk back to the Storage Pool it was failed from. This command will also initiate a rebuild if a spare has not already been assigned to the Storage Pool.
3.2.2.2
Creating a Storage Pool

To create a Storage Pool, enter command: CREATE POOL RAID_LEVEL=<RAID level> CHUNK_SIZE=<chunk size> {ASSIGN_POLICY=[SAS|SATA] NUMBER=<number of disks> or PHYSICAL_DISK=<list of disks>} where: RAID level = raid5 or raid6 or raid1 chunk size = 32kb, 64 kb, 128 kb, or 256 kb number of disks = 5 or 9 drives for RAID 5, 6 or 10 drives for RAID 6 list of disks = index name of disks
51
You may either explicitly select the disks for the pool by using PHYSICAL_DISK= or specify the number of disks in the pool by using NUMBER= in which case the next available disks will be selected. If you specify the ASSIGN_POLICY and NUMBER parameters together, only the selected type of disks will be used for the Storage Pool and you will not need to enter the individual disk name. Examples: To use only the specified disks: CREATE POOL RAID_LEVEL=RAID5 CHUNK_SIZE=64KB PHYSICAL_DISK=0x003e 0x003f 0x0040 0x0041 0x0042 To use the next available disks: CREATE POOL RAID_LEVEL=RAID6 CHUNK_SIZE=128KB NUMBER=6 To use only the selected type of disks: CREATE POOL RAID_LEVEL=RAID6 CHUNK_SIZE=128KB NUMBER=6 ASSIGN_POLICY=SAS
3.2.2.3
Storage Pool Initialization

When a Storage Pool is created, initialization begins automatically and will continue in the background until it is completed. Once the Storage Pool has completed its initialization, its Virtual Disk(s) can be accessed immediately. You may use the SHOW POOL command to check if the Storage Pool is being initialized (see Section 3.2.1.2, "Storage Pool View" for more information). You may monitor the initialization progress using the SHOW JOB command (see Section 3.3.1, "Background Job Priority" for more information).
3.2.2.4
Naming a Storage Pool

SET POOL <pool-id> NAME=<name> lets you specify a name to identify the Storage Pool (Figure 62).
Figure 62. Set Pool Name Example Screen
RAID[0]$ set pool 0 name=RAID 5 Set POOL 0 OID: 0x19b40000 attributes set with STATUS=Success (0x0)
3.2.2.5
Deleting a Storage Pool

DELETE POOL=<id> deletes the specified Storage Pool from the system.
!
Warning
The DELETE POOL command erases all the data on the Storage Pool.
52
3.2.2.6
Creating a Virtual Disk

To create a Virtual Disk, enter command: CREATE VIRTUAL_DISK CAPACITY=<capacity> POOL=<pool-id> where <capacity> is the capacity of the Virtual Disk in GiB or type max to use all available capacity; <pool-id> is the Storage Pool to be used by this Virtual Disk (Figure 63). A message is displayed to indicate whether the Virtual Disk creation was successful.
Figure 63. Create Virtual Disks Example Screen
RAID[0]$ create virtual_disk capacity=16 pool=0 VIRTUAL_DISK 0 OID=0x89ba000 creation STATUS='Success' (0x0) RAID[0]$ create virtual_disk capacity=32 pool=0 VIRTUAL_DISK 1 OID=0x89bb001 creation STATUS='Success' (0x0)
3.2.2.7
Naming a Virtual Disk

SET VIRTUAL_DISK <id> NAME=<name> lets you specify a name to identify the Virtual Disk (Figure 64).
Figure 64. Set Virtual Disk Name Example Screen
RAID[0]$ set virtual_disk 0 name=LUN 0 VIRTUAL_DISK 0 OID=0x89ba000 attributes set with STATUS=Success (0x0)
3.2.2.8
Deleting a Virtual Disk

DELETE VIRTUAL_DISK=<id> deletes the specified Virtual Disk from the system.
!
Warning
When you delete a Virtual Disk, you lose access to all data that was stored on that Virtual Disk.
53
3.2.3
Spare Pool Management

The S2A6620 supports the concept of Spare Pool which contains Physical Disks that can be used as spare disks. Spare pools can be shared by Storage Pools or dedicated to a particular Storage Pool in which case the spare disks will only be used by the designated Storage Pool. After a spare pool is created, you will need to select drive(s) from the Unassigned Pool and assign it the spare pool. In the event of drive failure, a drive that is assigned to a spare pool is automatically swapped into the Storage Pool to replace the failed drive. A rebuild then occurs immediately, reducing the possibility of data loss due to additional drive failures. NOTE : Each Storage Pool must have a spare pool assigned to it. If a Storage Pools attributes show Global Spare Pool: UNASSIGNED no spare pool will serve this Storage , Pool.
3.2.3.1
Creating a Spare Pool

Use these commands to create a spare pool, add disk to the spare pool, and assign the spare pool to a Storage Pool: CREATE SPARE_POOL ASSIGN PHYSICAL_DISK <disk-id> TO_POOL <spare-pool-id> SET POOL <pool-id> SPARE_POOL <spare-pool-id> where <pool-id> and <spare-pool-id> are the index names of the Storage Pool and spare pool respectively.
3.2.3.2
Naming a Spare Pool

SET SPARE_POOL <pool-id> NAME=<name> lets you specify a name to identify the spare pool.
3.2.3.3
Deleting a Spare Pool

To delete a disk from the spare pool, enter command ASSIGN PHYSICAL_DISK <disk-id> TO_POOL 0x1800ffff To delete a spare pool, enter command DELETE SPARE_POOL <pool-id>
54
3.2.4
Drive Rebuild
The S2A6620s automatic drive failure recovery procedures ensure that absolute data integrity is maintained while operating in degraded mode.
3.2.4.1
Full and Partial Rebuilds

Both full and partial (fractional) rebuilds are supported in S2A6620. Rebuilds are done at the Storage Pool level, not the Virtual Disk level. Partial rebuilds will reduce the time to return the Storage Pool to full redundancy and can be controlled by adjustable time limit for each Storage Pool. Permitted time limits are 0 (in which case partial rebuild is off) to 240 minutes. The timer will begin when a disk in the Storage Pool is declared missing. If the disk reappears prior to the expiration of the timer, a fractional rebuild will be done. Otherwise, the disk will be declared failed, replaced by a spare and a full rebuild will begin to return the Storage Pool to full redundancy. The default partial rebuild timer (Disk Timeout) setting is 10 minutes. Under heavy write workloads, it is possible that the number of stripes that need to be rebuilt will exceed the systems internal limits prior to the timer expiration. When this happens, a full rebuild will be started automatically instead of waiting for the partial rebuild timeout. Use the SHOW POOL <id> ALL_ATTRIBUTES command to display the current Disk Timeout setting (Figure 65).
Figure 65. Show Pool All Attributes
RAID[0]$ show pool 3 all OID: 0x19b003 Type: STORAGE Name: RAID5set Chunk Size: 64KB (0x80 blocks) Block Size: 0x200 RAID Type: RAID5 Free Raid5 Capacity: 2752512 MBs Max VD Size: 2752512 MBs Total Capacity: 3522560 MBs UUID: 0x00 Global Spare Pool: 0x19bc0006 DiskTimeout(FRT): 10 minutes ....
To change the disk timeout setting, use this command: SET POOL <id> DISK_TIMEOUT=<timeout> where <timeout> is in the range of <0..240> minutes. The default setting is 10.
3.2.4.2
Sparing Policy
Each Storage Pool has a sparing policy that determines what happens when a Physical Disk within the pool fails (or becomes inaccessible). In the event of a drive failure, the S2A6620 will automatically initiate a drive rebuild if the sparing policy is set to automatic and a spare pool has been assigned to the Storage Pool. Use the SHOW POOL <id> ALL_ATTRIBUTES command to display the current settings
(Figure 66).
55
Figure 66. Show Pool All Attributes

RAID[0]$ show pool 3 all OID: 0x19b003 Type: STORAGE .... UUID: 0x00 Global Spare Pool: 0x19bc0006 DiskTimeout(FRT): 10 minutes Init Policy: NO IO permitted Init Priority: 50% Full Rebuild Priority: 80% Fractional Rebuild Priority: 90% Sparing Policy: AUTOMATIC ....
To change the sparing policy setting, use this command: SET POOL <id> SPARING_POLICY=[AUTOMATIC|MANUAL] The default setting is automatic which is recommended. A rebuild operation can take up to several hours to complete, depending on the size of the disk and rate of rebuild. Refer to Section 3.3, "Performance Management" on page 59 for information on how to adjust the rate of rebuild.
3.2.4.3
Manual Drive Replace/Rebuild

Should a spare pool not be assigned to a storage pool, it becomes necessary to manually add a drive to the pool to replace a failed drive. To add a drive to the pool to replace a failed drive, use this command: ASSIGN PD=<id of the disk to be added> STORAGE_POOL=<id of the storage pool> SET_SPARE The disk will be put into the storage pool as the spare drive and it will be used in the storage pool to replace the failed drive.
3.2.5
SATAssure
If you have purchased the optional SATAssure license, you may enable it for the Storage Pool. To display the current setting, enter command SHOW POOL <pool-id> ALL_ATTRIBUTES
Figure 67. Show Storage Pool Details Example Screen
RAID[0]$ show pool 0 all_attributes OID: Type: Name: ... 0x19b40000 STORAGE 0x19b40000
Assign Policy: Device Type: Rotation Speed: Raw Capacity: SATAssure: IO ROUTING: WBC: MWBC: Initializing: Rebuilding: ...
NA NA NA FALSE TRUE TRUE FALSE TRUE FALSE
To enable SATAssure, enter command SET POOL <pool-id> SATASSURE=TRUE
56
To disable SATAssure, enter command SET POOL <pool-id> SATASSURE=FALSE
3.2.6
Cache Coherency
By default, the S2A6620 runs in couplet mode, where both Controllers are running simultaneously, communicating through internal Ethernet connections. This means that the S2A6620 is always running with cache coherency enabled. The write back cache settings are configurable for each Storage Pool. To display the current settings, enter command SHOW POOL <id> ALL_ATTRIBUTES. To change the settings, use these commands: SET POOL <id> MIRRORED_WRITE_BACK_CACHE=[TRUE|FALSE] SET POOL <id> WRITE_BACK_CACHING=[TRUE|FALSE] NOTE : Turning off mirroring may result in data integrity issues.
3.2.7
Setting the Systems Date and Time

SHOW SUBSYSTEM ALL_ATTRIBUTES displays the current system date and time (Figure 68).
Figure 68. Show System Time
RAID[0]$ show subsystem RP Subsystem Name: UID: Subsystem Time: Time zone: DST offset: Locate Dwell Time: Mirror Synch: all_attributes 0x0000000000000000 Fri Jan 30 16:48:55 0 minutes 0 minutes 120 seconds NA
2009
The system time and date for the S2A6620 are factory-configured for the U.S. Pacific Standard Time (PST) zone. The system records time using the military method, which records hours from 00 to 24, not in a.m. and p.m. increments of 1 to 12.Valid date settings are between years 2000 and 2104. Settings are automatically adjusted for leap years. To change the system date and time to March 1, 2009 2:15:32 pm, for example, type: SET SUBSYSTEM DATE_AND_TIME=2009:3:1:14:15:32
57
3.2.8
Restarting the S2A6620

System Restart SHUTDOWN CONTROLLER [LOCAL|REMOTE|0|1] RESTART performs a restart on the specified Controller. SHUTDOWN SUBSYSTEM RESTART performs a restart on both Controllers. These commands will prepare the system to be restarted. The system will halt all I/O requests and save the data to the disks before restarting. The restart process may take several minutes to complete. System Shutdown SHUTDOWN CONTROLLER [LOCAL|REMOTE|0|1] shuts down the specified Controller. SHUTDOWN SUBSYSTEM shuts down both Controllers. If you need to power down the S2A6620, use SHUTDOWN prior to shutting off the power. This will cause the S2A6620 to immediately flush its cache, abort all initialization and rebuild operations, and proceed with an orderly shutdown. All hosts actively using the S2A6620 should be safely shutdown and all users logged out before using this command. The S2A6620 will halt all I/O requests and save the data to the disks. The unit can be safely turned off after using this command. Once shut down is complete, all power supplies must be switched off or unplugged. Power must be removed from the system for at least 10 seconds before it will start up again. NOTE : Use SHUTDOWN whenever you need to power down the S2A6620 for maintenance. SHUTDOWN flushes any data left in the cache and prepares the S2A6620 for an orderly shutdown.
58
Performance Management
3.3
Initialization and rebuild operations are background processes and their rates can be adjusted to minimize their impact on system performance.
3.3.1
Background Job Priority

To monitor all current jobs (Figure 69), enter command: SHOW JOB * ALL_ATTRIBUTES The type of job and percentage of completion are displayed.
Figure 69. Show Job Example Screen
RAID[0]$ show job * all OID: 0x2b010003 Target: 0x19b40003 Type: REBUILD Status: RUNNING Priority: 80 Fraction Complete:5% OID: 0x28000004 Target: 0x19b60004 Type: INITIALIZE Status: RUNNING Priority: 50 Fraction Complete:10%
You may specify the amount of system resources that should be devoted to a background job. The higher its priority value, the faster the background job will run and the more the background job will impact client IO performance. To set the job priority, enter command: SET JOB=<id> PRIORITY=<priority> where <priority> is a number between 1 and 99. Note that PRIORITY is not a percentage or a mathematical fraction of the available resources. For example, two background jobs with priority values of 50 will not use 100% of the system resources. The S2A6620 may or may not limit the number of background jobs to keep the total of their priorities below 100. Pause/Resume a Job You may pause a job at any time using the PAUSE JOB=<id> command (Figure 70). To resume the job, enter command RESUME JOB=<id>
Figure 70. Pause/Resume a Job
RAID[0]$ pause job 0x28000003 JOB 3 OID=0x28000003 paused with STATUS='Janus Success' (0x0) RAID[0]$ show job * all_attributes OID: 0x28000003 Target: 0x19b40003 Type: INITIALIZE Status: PAUSED Priority: 50 Fraction Complete:11% RAID[0]$ resume job 0x28000003 JOB 3 OID=0x28000003 resumed with STATUS='Janus Success' (0x0) RAID[0]$ show job * all_attributes OID: 0x28000003 Target: 0x19b40003 Type: INITIALIZE Status: RUNNING Priority: 50 Fraction Complete:11%
59
3.3.2
Rebuild Policy Priority

Each Storage Pool has its own rebuild policy settings. You may specify the priority values for full rebuild and partial (fractional) rebuild policies. To display the current settings, enter command SHOW POOL <id> ALL_ATTRIBUTES (Figure 71).
Figure 71. Show Pool Information
RAID[0]$ show pool 3 all_attributes OID: 0x19b40003 Type: STORAGE Name: raid 5 set Chunk Size: 64KB (0x80 blocks) Block Size: 0x200 RAID Type: RAID5 Free Raid5 Capacity: 2752512 MBs Total Capacity: 3522560 MBs UUID: 0x00 Global Spare Pool: 0x1a0f000a DiskTimeout(FRT): 10 minutes Init Policy: NO IO permitted Init Priority: 50% Full Rebuild Priority: 80% Fractional Rebuild Priority: 90% Sparing Policy: AUTOMATIC .....
Full Rebuild Priority To change the full rebuild priority value (Figure 72), enter command: SET POOL <id> REBUILD_FULL_POLICY=<priority> where <priority> is an integer in the range of 1 to 99. The default value specifies a priority of 80%.
Figure 72. Set Full Rebuild Priority
RAID[0]$ set pool 3 rebuild_full_policy=70 POOL 3 OID=0x19b40003 attributes set with STATUS=Success (0x0)
Partial Rebuild Priority To change the partial rebuild priority value (Figure 73), enter command: SET POOL <id> REBUILD_PARTIAL_POLICY=<priority> where <priority> is an integer in the range of 1 to 99. The default value specifies a priority of 90%.
Figure 73. Set Partial Rebuild Priority
RAID[0]$ set pool 3 rebuild_partial_policy=80 POOL 3 OID=0x19b40003 attributes set with STATUS=Success (0x0)
60
Firmware Update Management
3.4

DataDirect Networks periodically releases firmware updates to enhance features of the products. Please contact our Technical Support Department to obtain the latest firmware files. Before performing any updates, please note the following: 1. The UPDATE ENCLOSURE command starts a background operation so that the CLUI is free to do other operations during the UPDATE. The status that comes back from the UPDATE ENCLOSURE command only indicates whether the background operation was successfully started. SHOW ENCLOSURE <oidex> UPDATE_FIRMWARE_PROGRESS should be used immediately after the command and then subsequently periodically to check the status of the UPDATE.
2. When you SCP the Consolidated Download File (.DDN) to the firmware directory, it must be copied to the PRIMARY controller. Since the PRIMARY may change, it is probably best to copy it to BOTH controllers. If SHOW ENCLOSUER <oidex> UPDATE_FIRMWARE_PROGRESS reports status JS_ES_DL_UCODE_OPEN_FAILED, the most likely cause is that the file was not copied to the PRIMARY controller. 3. When the S2A6620 is busy rebuilding, initializing, or doing host IO, UPDATE ENCLOSURE operations may fail because the enclosure is too busy to service the UPDATE IOs in a timely fashion. Therefore, make sure that there are no rebuilds, initializations, or host IO operations being done during the UPDATE ENCLOSURE operation. 4. In order to cause the new enclosure firmware to start being used you must power cycle the enclosure. In the 6620, it is best to do this by doing a SHUTDOWN SUBSYSTEM followed by power-cycling the enclosure. This is also required to recover from an UPDATE ENCLOSURE failure. These power cycles are required.
3.4.1
Displaying Current Firmware Version

The SHOW CONTROLLER <id> ALL_ATTRIBUTES command displays version information of the S2A6620s hardware and firmware (Figure 74).
61
Figure 74. show Controller Information Screen

RAID[0]$ show controller local all_attributes OID: 0x38000001 Firmware Version: Release: 1.0.3.3 Source Version: 1877 Fully Checked In: Yes Private Build: Yes Build Type: Production Build Date and Time: 2009-03-02-09:49:EST Builder Username: compiler Builder Hostname: ereo-debian Build for CPU Type: AMD-64-bit Hardware Version: 0x0 State: RUNNING Local AP OID: 0x00000000 Memory Size: 0x0 Max Q of S ID: 0x0 Up Time (seconds): 0x7fe3 Last Event Sequence #: 0x27b Log Facility Mask: .... Crash Dump Enabled: Log Disk Enabled: RP Count: Restart Pending: Name: Controller: Controller ID: MIR Reason:
TRUE TRUE 0x1 FALSE B LOCAL (SECONDARY) 0x0015b2a1214a0000 None
3.4.2
Firmware Update Procedure

The firmware update procedure described here only applies to upgrades from firmware version 1.0.3.3.xxxx or later to a new version. Upgrades from an older version of firmware must be done by a trained technician. If you are upgrading from v1.0.3.3.xxxs or later, there are two methods that can be utilized: copy the new firmware image over to the controller via the network instead of using a USB flash drive for Linux copy the new firmware image over to the controller via the network for Windows users. NOTE : The S2A6620 now supports an upgrade of the firmware while the system is still online. However, you must correctly follow the upgrade instructions to perform a successful online upgrade.
NOTE : In the examples, the filename of the firmware image is ddn-flash-6620-1.1.0.0.3489-opt.tgz and the IP address of the controller is 10.32.31.240. Replace these parameters with the filename and IP address appropriate for your installation .
3.4.2.1
Linux Environment-Firmware Update from the Network

Follow these steps to update the firmware: 1. Copy the new firmware to both Controllers using an scp or sftp client. The username is firmware and the password is Firmware (Note that entries are case-sensitive). For example: scp ddn-flash-6620-1.2.0.0.3489-opt.tgz firmware@10.32.31.240:
62
2. At the CLUI prompt, enter command UPDATE_FIRMWARE CONTROLLER=<controller-id> FILE=<file-specification> For example: UPDATE_FIRMWARE CONTROLLER=LOCAL FILE="ddn-flash-6620-1.2.0.0.3489-opt.tgz" (Note that the file name must be enclosed with double quotation marks.) 3. Upon completion of reboot, login and enter command SHOW CONTROLLER LOCAL ALL. Verify that the firmware version is correct. For example: CLUI unable to get RAID SUBSYSTEM NAME. STATUS=MIR:Firmware Version Mismatch (0x30003f8) NOTE : The firmware will be in MIR, firmware version mismatch state for the first controller that is upgraded. You must ensure that you have a CLUI prompt from the newly upgraded controller before moving to Step 4. 4. Upgrade the second controller by repeating Steps 2-3 on the other controller.
3.4.2.2
Windows Environment-Firmware Update from the Network

This method requires a SFTP or SCP client, and involves two steps copying the firmware image to both controllers and launching the update. 1. Copy the new firmware to the Controller using an scp or sftp client. You must use an application that supports SFTP or SCP. WinSCP, a free SFTP and SCP client, is used in this example. 2. Launch WinSCP or other SFTP/SCP client. For hostname, use the IP address of your controller. User name is firmware and password is Firmware. Both user name and password are case-sensitive. 3. Select Login (Figure 75).
At the login screen, use the user name admin with the password password to log into the system. S2A6620. User name and passwords are care sensitive. Figure 75. Logon Screen
4. Find the image file and drag this to the destination window and select copy.
63
Copy operation commences. To launch the update, 1. Login to the controller via an SSH session with the username of user and password of user. 2. At the CLI prompt enter: update_firmware controller=<controller-id> FILE=<file-specification> For example: update_firmware controller=LOCAL FILE= ddn-flash-6620-1.2.0.0.3489-opt.tgz NOTE : The quotes around the filename of the firmware image are required. 3. Upon completion of reboot, login and enter command SHOW CONTROLLER LOCAL ALL.. Verify that the firmware version is correct. For example: CLUI unable to get RAID SUBSYSTEM NAME. STATUS=MIR:Firmware Version Mismatch (0x30003f8) NOTE : The firmware will be in MIR, firmware version mismatch state for the first controller that is upgraded. You must ensure that you have a CLUI prompt from the newly upgraded controller before moving to Step 4. 4. Upgrade the second controller by repeating Steps 2-3 on the other controller.
3.4.3
Enclosure (Disk Shelf) Firmware Update Procedure

WARNING: Before starting this procedure, verify that a power cycle or any perturbations to the system is NOT required for the next 2 hours.S2A6620. There are two (2) parts to update the enclosure firmware: 1. Upload the enclosure firmware to the 6620 using either Linux Environment or
Windows
2. Update Disk Shelf using CLUI commands.
3.4.3.1
Linux Environment-Firmware Upload

Obtain the firmware from DDN. Firmware must be running on the S2A6620 and must be connected to the enclosure to be upgraded. 1. Use the secured copy program (scp) to transfer the file to the expander with the command: scp <firmware file name> firmware@<ip_address_of_6620>:
64
NOTE : Ensure the colon (:) is at the end of the above command. 2. Enter the password: Firmware NOTE : (Note that entries are case-sensitive). The file will be copied to the S2A6620.
3.4.3.2
Windows Environment-Firmware Upload

Obtain the firmware from DDN. Firmware must be running on the S2A6620 and must be connected to the enclosure to be upgraded. 1. Use the putty secured copy program (pscp) to transfer the file to the expander with the command: pscp <firmware file name> firmware@<ip_address_of_6620>: NOTE : Ensure the colon (:) is at the end of the above command. 2. Enter the password: Firmware NOTE : (Note that entries are case-sensitive). The file will be copied to the S2A6620.
3.4.3.3
Disk Shelf Upgrade

Once the file is copied from either procedure above (Linux or Windows), follow the steps below to complete the upgrade: 1. Log onto the S2A6620. NOTE : User name is user Password is user . . 2. At the CLUI prompt, enter command UPDATE ENCLOSURE <enclosure num> FILE=<file name uploaded> The upgrade will take approximately 2 hours. 3. To monitor the upgrade progress, enter command SHOW ENCLOSURE 1 UPDATE_FIRMWARE_PROGRESS For example: RAID[0]$ show enclosure 1 update_firmware_progress ES download progress for enclosure 1. CDF file name /tmp/janus_update//S2A6620_D02_011.DDN CDF is for Vendor ID DDN CDF is for Product ID S2A6620 CDF package version D02.011 CDF release date 01-OCT-2008
65
Download is in progress and 15 percent complete. Download consists of 2 images. Image 2 is in progress and 13 percent complete. 4. When the download is completed, you must power-cycle the enclosure. 5. Verify the upgrade is completed, enter command SHOW ENCLOSURE 1 UPDATE_FIRMWARE_PROGRESS For example: RAID[0]$ show enclosure 1 update_firmware_progress ES download progress for enclosure 1. Download not in progress -- last download completed successfully.
6. Verify the upgrade was successful by using the command: SHOW EXPANDER NOTE : The expanders are Sub Index 3 thru 10. Ensure that the Firmware version and the Init String version are identical. For example: RAID[0]$ show expander 1 * all Sub Index: 1 Sub OID: 0x78000001 Enclosure Index: 1 Enclosure OID: 0x50000001 Position: 1 SES Status: OK Present: TRUE Predicted Failure Ind: OFF Locate Indicator: OFF Location: IOM 1 Firmware version: 0078 Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: 2 0x78000002 1 0x50000001 2 OK TRUE OFF OFF IOM 2 3 0x78000003 1 0x50000001 3 OK TRUE OFF
66
Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version:
OFF DEM 1 TCA-00300-01-A MXSCI00089HVD12B D02.011 D02.011 7 4 0x78000004 1 0x50000001 4 OK TRUE OFF OFF DEM 2 TCA-00300-01-A MXSCI00089HVD110 D02.011 D02.011 7 5 0x78000005 1 0x50000001 5 OK TRUE OFF OFF DEM 3 TCA-00300-01-A MXSCI00085QVD2CB D02.011 D02.011 7 6 0x78000006 1 0x50000001 6 OK TRUE OFF OFF DEM 4 TCA-00300-01-A MXSCI00086QVD109 D02.011 D02.011
67
FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID: Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version: Sub Index: Sub OID: Enclosure Index: Enclosure OID:
7 7 0x78000007 1 0x50000001 7 OK TRUE OFF OFF DEM 5 TCA-00300-01-A MXSCI000893VD19D D02.011 D02.011 7 8 0x78000008 1 0x50000001 8 OK TRUE OFF OFF DEM 6 TCA-00300-01-A MXSCI00085LVD0A5 D02.011 D02.011 7 9 0x78000009 1 0x50000001 9 OK TRUE OFF OFF DEM 7 TCA-00300-01-A MXSCI00089HVD11A D02.011 D02.011 7 10 0x7800000a 1 0x50000001
68
Position: SES Status: Present: Predicted Failure Ind: Locate Indicator: Location: Part number: Serial number: Firmware version: Init string version: FPGA version:
10 OK TRUE OFF OFF DEM 8 TCA-00300-01-A MXSCI00089HVD12C D02.011 D02.011 7
Total Expanders: 10
69
The System Logs
3.5
The System Logs

To display the event log starting at the start sequence number in ascending sequence number order (Figure 76), enter command: SHOW CONTROLLER <id> LOG ASCEND
Figure 76. Show Controller Log Example Screen (1)
RAID[0]$ show controller 0 log ascend 000001 2009-02-05 12:13:31:3387789 G=0 S=0 T=1 RP=0 VP=63 LOG_JOI_BUILD_INFO1 JOI FW VERSION ON PROCESSOR 0X40 = (1.0.3.1-0). 000002 2009-02-05 12:13:31:3387798 G=0 S=0 T=1 RP=0 VP=63 LOG_JOI_BUILD_INFO2 JOI FW WAS BUILT ON JJDEBIAN AT 2009-02-05-14:17:MST (PRODUCT). 000003 2009-02-05 12:13:52:8320854 G=3 S=1 T=1 RP=0 VP=1 LOG_LOGDISK_ENABLE_RECEIVED_FROM_STATE LOG RECEIVED FROM STATE
To display the event log starting at the start sequence number in descending sequence number order (Figure 77), enter command: SHOW CONTROLLER <id> LOG DESCEND
RAID[0]$ SHOW CONTROLLER 1 LOG DESCEND 000024 2009-02-11 05:08:48:7027390 G=0 S=0 T=1 RP=0 VP=1 LOG_JOI_TIME_SET JOI TIME WAS SET BY AN ADMINISTRATOR AT 2009-2-11 5:8:48; NEARBY LOG ENTRIES MAY APPEAR OUT OF TIME ORDER. OFFSET= 0X1C987C765CD3B2B. 000023 2009-02-06 04:49:20:5069068 G=3 S=1 T=1 RP=0 VP=1 LOG_LOGDISK_ENABLE_RECEIVED _FROM_STATE LOGRECEIVED FROM STATE 000022 2009-02-06 04:49:20:4952631 G=0 S=0 T=1 RP=0 VP=1 LOG_JOI_TIME_SET JOI TIME WAS SET BY AN ADMINISTRATOR AT 2009-2-6 4:49:20; NEARBY LOG ENTRIES MAY APPEAR OUT OF TIME ORDER. OFFSET= 0X1C987C7A302483D.
To display the event log starting at the specified start sequence number in ascending sequence number order (Figure 78), enter command: SHOW CONTROLLER <id> LOG ASCEND START_SEQUENCE <start-sequence-number>
RAID[0]$ SHOW CONTROLLER 1 LOG ASCEND START_SEQUENCE 20 000021 2009-02-06 04:49:20:4731906 G=4 S=2 T=1 RP=0 VP=1 LOG_ST_MIR_STATE STATE MIR STATE STATE:000A 000022 2009-02-06 04:49:20:4952631 G=0 S=0 T=1 RP=0 VP=1 LOG_JOI_TIME_SET JOI TIME WAS SET BY AN ADMINISTRATOR AT 2009-2-6 4:49:20; NEARBY LOG ENTRIES MAY APPEAR OUT OF TIME ORDER.OFFSET = 0X1C987C7A302483D. 000023 2009-02-06 04:49:20:5069068 G=3 S=1 T=1 RP=0 VP=1 LOG_LOGDISK_ENABLE_ RECEIVED_FROM_STATE LOG RECEIVED FROM STATE 000024 2009-02-11 05:08:48:7027390 G=0 S=0 T=1 RP=0 VP=1 LOG_JOI_TIME_SET JOI TIME WAS SET BY AN ADMINISTRATOR AT 2009-2-11 5:8:48; NEARBY LOG ENTRIES MAY APPEAR OUT OF TIME ORDER. OFFSET = 0X1C987C765CD3B2B.
70
Remote Management of S2A6620
3.6

The S2A6620 can be managed locally through the RS-232 interface, or remotely via SSH. The CLUI is the same regardless of the management interface (RS-232 or SSH).
3.6.1
Network Connection
Connect the Telnet port on the back of the Controllers to your Ethernet network (Figure 79). Then configure the network interface as described below.
Figure 79. Connectors on Controller
EXPANSION CLI
LINK
PORT 2 PORT 1
SPEED
Telnet Connector CLI Connector
NOTE : Currently, the S2A6620 does not support network configuration protocols such as DHCP or BOOTP.
3.6.2
Network Interface Set Up

UI SHOW NETWORK_INTERFACE [LOCAL] * displays the list of the network interfaces with their associated controller IDs and devices (Figure 80). LOCAL gives you information on the Controller that you are currently logged into. Controller.
Figure 80. Current Network Interface Settings Screen
RAID[0]$ ui show network_interface local * Network device id 0 address 10.32.31.31 netmask 255.255.240.0 gateway 10.32.16.2
To change the network interface settings on the Controller you are connected to, enter command: UI SET NETWORK_INTERFACE LOCAL 0 IP_ADDRESS=<ip_address> IP_MASK=<netmask> IP_GATEWAY=<gateway> where <ip_address> is an address appropriate to the local network. The netmask and gateway values can also be entered (Figure 81).
Figure 81. Set Network Interface Example
RAID[0]$ ui set network_interface local 0 ip_address=10.32.31.31 ip_mask=255.255.240.0 ip_gateway=10.32.16 NETWORK_INTERFACE 0 set with STATUS=Success (0x0)
Enter command SHUTDOWN SUBSYSTEM RESTART to restart the Controllers and make the changes take effect. NOTE : This network interface setup must be performed separately on each controller. Since you cannot use a remote command currently, you must plug the serial port into each controller to issue the commands to each controller.
71
3.6.3
Logins
By default, the login name is user and its password is user. Both are case sensitive. Only one SSH session is permitted at a time. Once a SSH session is initiated, the RS-232 console switches to a CLI sub-shell. The SSH client should be using port 22 with its local echoing function disabled.
72
Presentations
3.7
Presentations
A Presentation on a S2A6620 has the following components: Discovered Initiators A Discovered Initiator is defined as a Fibre-channel initiator that has logged into the S2A6620. This is normally a single port on a Fibre-channel HBA in an external computer. Host A Host is an abstract client of a Virtual Disk that has all the access to all data within the Virtual Disk. This most commonly represents an external computer with one or more Fibre Channel initiators. Host attributes are OS (operating system) of which you can select GENERIC, WINDOWS, LINUX or MAC_OS. The OS attribute dictates the way the controller responds to certain Fibre-channel commands where appropriate. For example, Mac OS X expects a different response from an inquiry of LUN0 (the controller LUN) than a Windows host.
OSTYPE: Standard uses current settings and Custom allows for requests for different adjustments from OEMs.
Channel A Channel is one of the Fibre-channel ports on the controller. Channel attributes are MODE of which you can select either MAC_OS or STANDARD. When MAC_OS is selected, the ports node name will be set differently in order to be visible to a Macintosh system. Stack A Stack is the input side of the subsystem. In the case of the S2A6620, the stack is defined as the Fibre-channel interface. In future versions of the product, different interface stacks may exist. Presentation A Presentation is the relationship between a Host and a Virtual Disk. A presentation implies that the related Host has some sort of access to the Virtual Disk. Attributes of a Presentation are: PORT - from which the host will see the virtual disk READ_ONLY - controls read only access PRESENT_HOME_ONLY - presents the specified Virtual Disk from its designated home controller only LUN - user-specified the LUN number that the Virtual Disk will show to the host.
3.7.1
Application Discovered Initiator Commands

To import a discovered initiator object that is associated with the specified host, use the APPLICATION IMPORT DISCOVERED_INITIATOR=<object-id> HOST=<object-id> command. To display the attributes of a specified initiator, use the APPLICATION SHOW DISCOVERED_INITIATOR=<object-id> [ALL_ATTRIBUTES] command. To create an application initiator for the specified host, use the APPLICATION CREATE INITIATOR HOST=<object-id> WWPN=<integer> command. To delete the specified initiator, use the APPLICATION DELETE INITIATOR=<object-id> command.
3.7.2
Application Host Commands

To create a host stack, use the APPLICATION CREATE HOST [OSTYPE=GENERIC|LINUX|MAC_OS|WINDOWS] command. In the case of a FCP target Application Stack, the ID string is not used. In the case of the Lustre OSS, the ID String is the name of a block device. The default operating system type is GENERIC.
73
Presentations
To delete the specified host, use the APPLICATION DELETE HOST =<object-id> command. To display the presentation associated with the specified application host, use the APPLICATION SHOW HOST=<object-id> [PRESENTATIONS] command. To display the initiators associated with the specified application host, use the APPLICATION SHOW HOST=<object-id> [INITIATORS] command.
3.7.3
Application Presentation Commands

To create a presentation to a virtual disk for the specified host, use the APPLICATION CREATE PRESENTATION VIRTUAL_DISK=<object-id> HOST=<object-id> command. To delete a presentation to a virtual disk for the specified host, use the APPLICATION DELETE PRESENTATION VIRTUAL_DISK=<object-id> HOST=<object-id> [FORCE] command. Note the optional parameter of FORCE deletes without asking questions. To delete the specified presentation, use the APPLICATION DELETE PRESENTATION=<object-id> [FORCE] command. Note the optional parameter of FORCE deletes without asking questions. The wildcard * deletes all presentations. To set the specified attribute to the specified value, use the APPLICATION SET PRESENTATION=<object-id> <attribute-name>=<value> [<attribute-name>=<value>] command. Attributes are: ENABLE=ALL|NONE|<channel-id> where the channel-id is the object-id of an EnabledClientChannel. LUN=<integer> where the integer is a Logical Unit Number (LUN) that will be used to present the associated Virtual Disk to the associated Host. NOTE: Each LUN integer entered for a presentation is cumulative and does not replace the previous entry. HOME_ONLY[=TRUE|FALSE] which enables/disables the home_only parameter. READ_ONLY[=TRUE|FALSE] which enables/disables read_only.
3.7.4
Configuration of Presentations of Virtual Disks to Hosts

NOTE : If you are configuring a storage subsystem with any MAC OSx presentations , it is absolutely required that you read and understand section 3.7.5 Additional Configuration considerations for Macintosh Hosts prior to actually doing your configuration. There are 3 objects/relationships that must be properly established in order to create a presentation of a LUN (virtual disk) to a host. Establish a host object for EACH host that wishes access to the S2A6620 storage subsystem virtual disk. NOTE : On the storage subsystem you ONLY need to create a single host object for any/all virtual disk presentations to that host!
74
Presentations
Import a discovered initiator into an established relationship with a host object. An association between a discovered initiators FC Port/Node WWN (World Wide Name) to a host object is established in this operation. This association of host/port WWN to host object is maintained persistently within the subsystems configuration information along with all other information. If the host to controller association is subsequently disrupted and then re-established, the controller is able to maintain this relationship until such time that the configuration in the storage controller is cleared or that relationship is deleted. TIP: Use of a host based HBA utility such as HBAnyware or SANsurfer will allow you to examine the FC Port/Node WWNs on the host in the easiest manner. Assign a virtual disk to a host object. NOTE : You may ONLY present a virtual disk ONCE to the same host object.
WARNING:You can present a virtual disk to the multiple hosts; however, this is dangerous. If doing so, presenting them as Read-only to the other hosts would be appropriate.
NOTE : You may present a virtual disk to ALL hosts. This may be appropriate in some limited system environments; however, it is best practice to not MIX the presentations, where some VDs are selectively presented while others are presented all. Managing at the host end may become confusing. To present a virtual disk to ALL hosts, use the CLUI command: APPLICATION CREATE PRESENTATION VD=<vd_index> HOST=ALL
3.7.4.1
Host Object Creation Example

The following example demonstrates presenting 6 Virtual Disks to 3 separate hosts (2 Windows host and a Linux host) from a single storage subsystem. Although this configuration will have a FC Switch, the steps necessary are identical. NOTE : In the example, below, the clui user interface is operating in the RAID subject mode. The ASM (Application Stack Management) commands must be preceded by the subject application. Example:
RAID[1]$ RAID[1]$ RAID[1]$ RAID[1]$
application create host name=co-ls1 ostype=Linux application create host name=co-test-d10 ostype=windows app cre host name=co-test-d08 os windows
HOST 301 OID=0x1d5e012d creation STATUS='Success' (0x0) HOST 302 OID=0x1d5f012e creation STATUS='Success' (0x0) HOST 303 OID=0x1d60012f creation STATUS='Success' (0x0)
75
Presentations
RAID[1]$
application show host *

| Stack | Host Mode Attributes | | | Index | OS Type | Characteristics 00000 00000 00000 LINUX WINDOWS WINDOWS 0x0000000000000001 0x0000000000000001 0x0000000000000001
Index | Host Name 00304 00305 00306 co-ls1 co-test-d10 co-test-d08
-------------------------------------------------------------------------------
Total Hosts: 3
Recommendations:
When creating host objects, always include a descriptive name for host objects that is easily recognizable. This benefits the storage administrator in managing storage connectivity issues. The OS_TYPE determines the FC flow control mechanism for host I/O. The Linux OS type is currently appropriate for all versions/implementations of Linux / UNIX. The Windows OS type is currently appropriate for all versions of the Windows operating systems. It is imperative the OSTYPE for Apple/MAC hosts be appropriately set to MAC. Please see section 3.7.5 Additional Configuration Considerations For Macintosh Hosts. The setup requirements involving MAC OSX hosts require additional steps and considerations.
3.7.4.2
Identifying Host FC Connections via Ports

The host ports of the controller dynamically acknowledges and logs in any FC Host/Port WWN connection that it can sync up with. When you query the storage subsystem for the discovered initiators, the listing you get will be the current set of connections that are logged in. If a connection is broken and then re-established, the re-discovered Port/Node WWN will be assigned a new host_index number. This is inconsequential after a specific Port/Node WWN is directly associated with a specific host that is done in a subsequent step. Example of discovered initiators:
RAID[1]$
application show discovered *

| World Wide Name (WWN) node name | port name | | | Ctrl 0 | Ctrl 1 |
Index | Type | port id |
-------------------------------------------------------------------------------00003 00005 00006 00007 00011 00012 FC FC FC FC FC FC 0x010600 0x010800 0x010900 0x010a00 0x010300 0x010200 0x20000000c9813cc9 0x10000000c9813cc9 0x20000000c9813cc8 0x10000000c9813cc8 0x20000000c9813a47 0x10000000c9813a47 0x20000000c9813a46 0x10000000c9813a46 0x2000001b32827e95 0x2100001b32827e95 0x2001001b32a27e95 0x2101001b32a27e95 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1
Total FC Initiators: 6 RAID[1]
76
Presentations
In order to provide an association between a host and a virtual disk you must identify the FC connection (its Node/Port WWN name to the host object). You may utilize the following techniques: Utilize the physical sticker tag information on the HBA. Connect a single host at a time (and all its FC connections to the subsystem) to the subsystem (direct connect or via a switch), identify their WWNs as a discovered initiator, then a proceed to plug in subsequent hosts, noting their WWNs. Utilized a host based FC Adapter utility such as HBAnywhere (for Emulex HBAs) (Figure 83) or SANsurfer (for Qlogic HBAs) (Figure 83).
Example for Linux system with driver loaded (example of Qlogic):

# cd # ls 1 2 #
/proc/scsi/qla2xxx
grep adapter-port 1
scsi-qla0-adapter-port=210000e08b9d6149;
bm-dell-09:/proc/scsi/qla2xxx #
grep adapter-port 2
scsi-qla1-adapter-port=210100e08bbd6149;
#
lsscsi -g | grep -i ddn

disk disk DDN DDN S2A 8500 S2A 8500 5.31 5.31 /dev/sdc /dev/sdg /dev/sg2 /dev/sg6
[1:0:0:1] [2:0:0:1]
Example for Linux system without Driver loaded:

cd /sys/class/fc_host # ls -la
# total 0 drwxr-xr-x 4 root root 0 Jul 15 11:47 .
drwxr-xr-x 43 root root 0 Jul 15 11:48 .. drwxr-xr-x drwxr-xr-x # # 3 root root 0 Jul 15 11:48 host3 3 root root 0 Jul 15 11:48 host4
cd host3 ls -la
0 Jul 15 11:48 . 0 Jul 15 11:47 ..
total 0 drwxr-xr-x 3 root root drwxr-xr-x 4 root root
lrwxrwxrwx 1 root root 0 Jul 15 11:47 device -> ../../../devices/pci0000:00/0000:00:04.0/0000:0a:00.0/host3 -r--r--r-- 1 root root 4096 Jul 17 15:31 fabric_name --w------- 1 root root 4096 Jul 17 15:31 issue_lip -r--r--r-- 1 root root 4096 Jul 17 15:31 node_name -r--r--r-- 1 root root 4096 Jul 17 15:31 port_id -r--r--r-- 1 root root 4096 Jul 17 15:31 port_name -r--r--r-- 1 root root 4096 Jul 17 15:31 port_state -r--r--r-- 1 root root 4096 Jul 17 15:31 port_type -r--r--r-- 1 root root 4096 Jul 17 15:31 speed
77
Presentations
drwxr-xr-x 2 root root lrwxrwxrwx 1 root root
0 Jul 15 11:47 statistics 0 Jul 15 11:48 subsystem -> ../../../class/fc_host
-r--r--r-- 1 root root 4096 Jul 17 15:31 supported_classes -r--r--r-- 1 root root 4096 Jul 17 15:31 symbolic_name -rw-r--r-- 1 root root 4096 Jul 17 15:31 system_hostname -rw-r--r-- 1 root root 4096 Jul 17 15:31 tgtid_bind_type --w------- 1 root root 4096 Jul 15 11:47 uevent #
cat port_name
0x2100001b3282dc50
NOTE : In switch environments you may disable/enable the ports on the switch to identify which physical connection you are dealing with.
Figure 82. HBAnyware Screen
78
Presentations
Figure 83. SANsurfer FC HBA Manager Screen
Utilizing one or more of the techniques above, you can document an association between the physical host and the discovered initiators on the storage.
Example of show discovered_initiator command all

co-6620-2 RAID[1]$
application show discovered_initiator *

| World Wide Name (WWN) node name Node WWN | port name Port WWN | |
| Host
Index | Type | Index | Index | Type | port id |
------------------------------------------------------------00004 00006 00007 00008 00011 00012 FC FC FC FC FC FC 0x010600 0x010900 0x010a00 0x010300 0x010200 0x010800 0x20000000c98107cb 0x10000000c98107cb 0x20000000c9813a47 0x10000000c9813a47 0x20000000c9813a46 0x10000000c9813a46 0x20000000c98107ca 0x10000000c98107ca 0x2000001b32827e95 0x2100001b32827e95 0x2001001b32a27e95 0x2101001b32a27e95
co-test-d08 co-test-d10 co-test-d10 co-test-d08 co-ls1 co-ls1
Now identify the WWN and the discovered initiator index number with the host and its index number and import the appropriate discovered initiator to an association with the appropriate host.
Example of importing discovered initiators

RAID[1]$ application import discovered 11 host 304 INITIATOR 12 OID=0x2d66000c imported from DISCOVERED_INITIATOR 11 OID=0x3000000b STATUS='Success' (0x0) RAID[1]$ application import discovered 12 host 304 INITIATOR 13 OID=0x2d67000d imported from DISCOVERED_INITIATOR 12 OID=0x3000000c STATUS='Success' (0x0)
79
Presentations
RAID[1]$
application import discovered 4 host 306
INITIATOR 14 OID=0x2d68000e imported from DISCOVERED_INITIATOR 4 OID=0x30000004 STATUS='Success' (0x0) RAID[1]$
application import discovered 8 host 306
INITIATOR 15 OID=0x2d69000f imported from DISCOVERED_INITIATOR 8 OID=0x30000008 STATUS='Success' (0x0) RAID[1]$
app import discovered=6 host=305
INITIATOR 16 OID=0x2d6a0010 imported from DISCOVERED_INITIATOR 6 OID=0x30000006 STATUS='Success' (0x0) RAID[1]$
app imp disc 7 host 305
INITIATOR 17 OID=0x2d6b0011 imported from DISCOVERED_INITIATOR 7 OID=0x30000007 STATUS='Success' (0x0) RAID[1]$
application show initiator *
| Host | World Wide Name (WWN) | Index | Type | Index | node name | port name | -----------------------------------------------------------00012 FC 00304 0x2000001b32827e95 0x2100001b32827e95 00013 FC 00304 0x2001001b32a27e95 0x2101001b32a27e95 00014 FC 00306 0x20000000c98107cb 0x10000000c98107cb 00015 FC 00306 0x20000000c98107ca 0x10000000c98107ca 00016 FC 00305 0x20000000c9813a47 0x10000000c9813a47 00017 FC 00305 0x20000000c9813a46 0x10000000c9813a46 Total FC Initiators: 6
3.7.4.3
Presenting a VD to a host
From your list of virtual disks that have been created, identify the host that you wish to present this lun to and create the presentation. Recommendations: Commands entered through the CLI may take a shortened form of the unique word as demonstrated in the above examples. Spaces may be used in place of = sign in command syntax
Example of List Of candidate Virtual Disks for presentation:

RAID[1]$
show vd *
| Home |Background| Job |
Idx|Name 49 vd-49_29 50 vd-50_30 51 vd-51_31 52 vd-52_32 53 vd-53_33 54 vd-54_34 55 vd-55_35 56 vd-56_36 57 vd-57_37 58 vd-58_38 59 vd-59_39
| State |Pool|Raid|Cap GB|Settings| Jobs |Current|Preferred| READY READY READY READY READY READY READY READY READY READY READY 29 30 31 32 33 34 35 36 37 38 39 6 6 1 1 5 5 6 6 5 5 1 1400 1400 344 344 1400 1400 3608 3608 3608 3608 344 W W W W W W W W W W W I I I I I I I I I I I 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0 0(R) 0 1(L) 0
---------------------------------------------------------------------------------INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE
80
Presentations
60 vd-60_41
READY
41
896
1(L) 0
1(L) 0
INACTIVE
Total Virtual Disks: 12
Example of Creating VD presentation to Linux Host co-ls1 specifying SCSI LUN_ID for the presented VD:
NOTE : This is the LUN number the host will see.
co-6620-2 RAID[1]$
application create presentation vd 49 host 304 lun 60 app create pres vd=50 host=304 lun 61 app show presentation *
Host | VD | | Home | Read | Channel Mask | |
PRESENTATION 2480 OID=0x256c09b0 creation STATUS='Success' (0x0) co-6620-2 RAID[1]$
PRESENTATION 2481 OID=0x256d09b1 creation STATUS='Success' (0x0) co-6620-2 RAID[1]$
Pres. | Host Index | Name
Index | Index | LUN | Only | Only |
---------------------------------------------------------------------------------02480 02481 co-ls1 co-ls1 00304 00304 00049 00050 060 061 OFF OFF R/W R/W 0xffffffffffffffff 0xffffffffffffffff
Total Presentations: 2
Example of Creating VD presentation to Windows Host co-test-d10 (not specifying SCSI LUN_ID):
NOTE : The next two VD are presented to a Windows host and the subsystem assigns the SCSI LUN_ID.
co-6620-2 RAID[1]$
application create presentation vd 51 host 305
PRESENTATION 2482 OID=0x256e09b2 creation STATUS='Success' (0x0)
co-6620-2 RAID[1]$
application create presentation vd 52 host 305
PRESENTATION 2483 OID=0x256f09b3 creation STATUS='Success' (0x0)
co-6620-2 RAID[1]$
application show presentation *

Host | VD | | Home | Read | Channel Mask | |
--------------------------------------------------------------------------------02480 02481 02482 02483 co-ls1 co-ls1 co-test-d10 co-test-d10 00304 00304 00305 00305 00049 00050 00051 00052 060 061 000 001 OFF OFF OFF OFF R/W R/W R/W R/W 0xffffffffffffffff 0xffffffffffffffff 0xffffffffffffffff 0xffffffffffffffff
81
Presentations
NOTE : For windows environments, you should let the subsystem specify the LUN_ID for a VD.
Example of Creating VD presentation to Windows Host co-test-d08 specifying SCSI LUN_ID 10 and 12):
NOTE : The next two VDs are presented to a Windows host and specify the SCSI_ID for the VDs as 10 & 12.
co-6620-2 RAID[1]$
application create presentation vd 58 host 306 lun 10
PRESENTATION 2484 OID=0x257009b4 creation STATUS='Success' (0x0)
co-6620-2 RAID[1]$
application create presentation vd 59 host 306 lun 12
PRESENTATION 2485 OID=0x257109b5 creation STATUS='Success' (0x0)
co-6620-2 RAID[1]$
app show pres *
Host | VD
| Home | Read |
Channel Mask
| |
--------------------------------------------------------------------------------02480 02481 02482 02483 02484 02485 co-ls1 co-ls1 co-test-d10 co-test-d10 co-test-d08 co-test-d08 00304 00304 00305 00305 00306 00306 00049 00050 00051 00052 00058 00059 060 061 000 001 010 012 OFF OFF OFF OFF OFF OFF R/W R/W R/W R/W R/W R/W 0xffffffffffffffff 0xffffffffffffffff 0xffffffffffffffff 0xffffffffffffffff 0xffffffffffffffff 0xffffffffffffffff
Recommendations: At times some hosts may have device discovery issues if there are gaps in the SCSI LUN_ID space. Letting the subsystem assign (as it will by default), the lowest SCSI_ID it can from this subsystem, may be considered a best practice. Use of a host based HBA utility such as HBAnyware or SANsurfer greatly enhances ability to determine perceived connectivity issues between the storage subsystem and the host. Your hosts multipath driver must be enabled correctly to recognize DDNs Device/Hardware ID. For Windows Server 2008 the Device/Hardware_ID information must be entered into the MPIO stack as an 8 bit / 16 character space padded field. For Linux OSs, the /etc/multipath.conf file must be edited, and the Device/Hardware_ID is NOT padded with the space character.
Device DDN Hardware_ID S2A 6620
82
Presentations
3.7.5
Additional Configuration Considerations For Macintosh Hosts

Apple/Mac Operating systems handles Fibre Channels Port/Node WWNs uniquely. Apple hosts expect node names to be unique across all subsystem ports. All other OSs expect the FC node names to be the same across all subsystem ports. Because of this uniqueness, VD presentations must be uniquely setup when an APPLE/Mac presentation is being made from a 6620 storage subsystem. NOTE : You MUST create the host object with OSTYPE=MAC for MAC hosts! You must identify at least one controller port (channel) (preferably one controller port for each 6620 controller) on the 6620 storage subsystem as operating in the MAC mode: APPLICATION SET CHANNEL [0|1|2|3] MODE MAC NOTE : Setting /changing the mode of a channel will require a shutdown/restart of the storage controller for the change to actually take place.
If a Mac presentation is being made from the subsystem, NO other VD from this subsystem should be presented to ALL hosts ! In a SAN and/or MIXED OS environment of MAC and other operating systems, create the presentations as follows:
APPLICATION CREATE PRESENTATION VD <vd_index> HOST <host_index> ENABLE=NONE
This will disable channels through which to make a presentation. Then you will next enable the specific channels through which you wish to make the presentation: APPLICATION SET PRESENTATION <index> ENABLE {0|1|2|3} To enable two channels, it is necessary to enter two separate commands. In the current implementation, you can disable all channels, enable all channels, or enable one channel at a time thru the clui. If you wish two channels enabled, use the following CLUI commands: APPLICATION SET PRESENTATION <index> ENABLE 0 APPLICATION SET PRESENTATION <index> ENABLE 2 Channel 0 is C0P0. Controller 0 is the LH controller as viewed from the rear of the unit. Channel 1 is C0P1. Channel 2 is C1P0. Controller 1 is the RH controller as viewed from the rear of the unit.Channel 3 is C1P1. If you have an existing storage configuration running Windows/Linux presentations and you wish to ADD a vd presentation for MAC: you will have to sustain a storage outage now so that you can disable all VD presentations thru any channel,
83
Presentations
and then re-enable the appropriate channels one at a time that will be serving VDs to the Windows/Linux hosts. You will then set up the appropriate channel(s) that will operate in MAC mode. At this point you can restart the storage subsystem, proceed in creating your MAC VD presentations and enable them thru their separate channels.
84
S ECTION 4
Supporting the S2A6620
Status LED Indicators
The S2A6620 system includes an Enclosure Services Processor and associated monitoring and control logic to enable it to diagnose problems within the enclosures power, cooling and drive systems. The sensors for power and cooling conditions are housed within the power supply/cooling modules. Each module is independently monitored.
4.1

Green LEDs are always used for good or positive indication. Amber LEDs indicate there is a critical fault present within the module.
4.1.1
Front Panel Indicators

The front panel indicators show the aggregated status of all the modules (Figure 84). The LEDs are defined in Figure 85.
Figure 84. Front Panel LED Indicators

System Fault System Power Shelf Identify Cover Open DEM Fault Drive Fault
Figure 85. Front Panel LED Description LED Definition Color Status ON - SES is sending an identify command OFF - SES is NOT sending an identify command ON - one or more components within enclosure have failed. A service action is required. Exact failed component has its own amber fault LED lit. OFF - no detectable faults ON - DC power is present OFF - DC power is not present LED does NOT flash under normal operating conditions OFF - both cover pieces securely closed and latched in place ON - either of the cover pieces is NOT securely closed and latched in place
Shelf Identify
Blue
System Fault
Amber
System Power
Green
Cover Open
Amber
86
Figure 85. Front Panel LED Description LED Definition Color Status OFF - all DEMs operating correctly ON - at least one DEM has failed; service action required ON - one or more HDDs are failed; SES must determine exact HDD OFF - no detectable drive faults ON - when SAS HDD is present Blinks - indicates HDD activity OFF - no HDD activity
DEM Fault
Amber
Drive Fault
Amber
Individually numbered
HDDs
Green
4.1.2
Power Cooling Module (PCM)

Figure 86 describes the PCM LED status. Under normal conditions, the LEDs should be illuminated constant GREEN. If a problem is detected, the color of the relevant LED will change to AMBER.
Figure 86. Power Cooling Module LEDs
Normal Operation LEDs
LED Enclosure front
Description Enclosure fault PCM AC
Color Amber
Status ON - AC input, DC output, fan or other PCM fault detected ON - AC input to PCM within tolerances OFF - PCM failed ON - DC output of PCM within tolerances OFF - PCM failed ON - AC input, DC output, fan or other PCM fault detected OFF - no fault detected ON - receiving SES identify command OFF - NOT receiving SES identify command
Green
PCM DC
Faults LEDs
Green
PCM Fault
Amber
PCM ID
Blue
87
4.1.3
Controller
Figure 88 describes the Controller LED (Figure 87) status. Under normal conditions, the LEDs should be illuminated constant GREEN. If a problem is detected, the color of the relevant LED will change to AMBER.
Figure 87. LEDs on Controller
Firmware Status LED Identify LED Power LED
EXPANSION CLI
RESE LINK
PORT 2 PORT 1
SPEED
Figure 88. Controller LED Indicators Identifier Enclosure fault Location Front enclosure Color Amber ON - IO fault detected ON - S2A6620 is ready to be accessed Blinks - firmware is loading OFF - S2A6620 is NOT ready to be accessed ON - power is applied to Controller OFF - power is NOT applied to Controller ON - SES identify command is received OFF - SES identify command is NOT received Status
Firmware status
Rear enclosure
Green
Power
Rear enclosure
Green
Identify
Rear enclosure
Blue
4.1.4
HDD (Hard Disk Drive)

Figure 89 describes the fault LED status when an HDD has failed. Under normal conditions, the LEDs should be illuminated constant GREEN. If a problem is detected, the color of the relevant LED will change to AMBER.
Figure 89. HDD LED Indicators Identifier Enclosure fault Drive fault Location Enclosure front Enclosure front Color Amber Amber Status ON - drive fault ON - drive fault
88
4.1.5
DEM (Drive Expander Module)

Figure 90 describes the DEM LED status. Under normal conditions, the LEDs should be illuminated constant GREEN. If a problem is detected, the color of the relevant LED will change to AMBER.
Figure 90. DEM LED Indicators Identifier Location Color Amber Amber Amber Status ON - DEM fault detected ON - DEM fault detected ON - DEM fault detected ON - DC voltage regulation is within limits OFF - DC output failure ON - expander internal processor is booted and operating correctly OFF - expander internal processor is NOT booted or ready
Enclosure fault Front enclosure DEM fault DEM fault Front enclosure Internal (DEM) enclosure Internal (DEM) enclosure
DC OK
Green
Expander MIPS Internal (DEM) ready enclosure
Green
89
Troubleshooting
4.2
Troubleshooting
This section describes common problems, with possible solutions, which can occur with the S2A6620 system.
4.2.1
Initial Start-up Problems

Faulty Cords
First check that you have wired up the enclosure correctly. Then, if: cords are missing or damaged plugs are incorrect cords are too short Call Customer Service for a replacement.
Computer Doesnt Recognize the S2A6620

1. Check that the host interface cables from the S2A6620 to the host computer are connected correctly. 2. Check that all drive modules have been correctly installed. 3. Check the Controller is setup as follows: Ensure the Controller has been correctly installed and all external links and cables are securely fitted. Ensure the maximum cable length has not been exceeded.
4.2.2
RAID[0]$ Prompt is not shown correctly

The default CLUI prompt is RAID[0]$. If CLUI$ is shown instead of RAID[0]$, one of the following problems may have occurred: The firmware on this Controller is in a MIR state and the MIR state needs to be resolved. Refer to Section 4.4, "Manual Intervention Required (MIR) Conditions" on page 105 for troubleshooting information. The CLUI has lost communication with the firmware or the firmware is not running. A restart of the system is needed. There are multiple CLUI connections to the firmware already and there are not enough resources to allow another connection. Only one CLUI connection is currently supported.
90
Troubleshooting
4.2.3
System Faults
Symptom
Cause
Action 1. Check for other AMBER LED indications on the Power Cooling modules. If there is a PSU error present there may be a communications problem with that Power Cooling module. Remove and then re-fit the module, if the problem persists then replace the module. 2. Check for other AMBER LED indications on the drive modules. If none are evident then there may either be an ESI processor problem or a backplane problem.
1. The System Fault LED The ESI processor has turns amber on front detected an internal fault panel. (e.g. failure of an internal communications path)
4.2.4
Power Supply/Cooling Faults
Symptom 1. System Fault LED is amber on front panel.
Cause 1. Any power fault.
Action 1. Check power On/Off switch on rear of Power Cooling module is turned ON. 2. Check AC Mains connections to Power Cooling module is live. 3. Disconnect the Power Cooling module from mains power and remove the module from the system, re-install module. If problem persists, replace Power Cooling Module. 4. Reduce the ambient temperature.
2. A fan failure. 2. An amber LED on one 3. A thermal condition or more Power Cooling which could cause PSU modules. overheating.
91
Troubleshooting
4.2.5
Thermal Alarm
Symptom
Cause
Action 1. Check local ambient environment temperature is below the upper 40C specification. 2. Check the installation for any airflow restrictions at the front and rear of the enclosure. A minimum gap of 1" (25mm) at the front and 2" (50mm) at the rear is recommended. 3. Check for restrictions due to dust build-up, clean as appropriate. 4. Check for excessive re-circulation of heated air from rear to the front, use in a fully enclosed rack installation is not recommended. 5. If possible shutdown the enclosure and investigate the problem before continuing.
1. Enclosure System If the internal FAULT LED is amber. temperature measured in the 2. An amber LED on airflow through the one or more Power enclosure exceeds a Cooling Modules. pre-set threshold a 3. Air temperature thermal alarm will exiting PSU is above sound. 55C.
!
Warning
An Enclosure will shut down when a critical temperature threshold is exceeded in order to prevent permanent damage to the disk drives.
92
Component Failure Recovery
4.3

The S2A6620 contains redundant and hot-swappable components: Power/Cooling Module Drive Module DEM I/O Module Controller . A single component failure, therefore, will not shut down the system. However, in the unlikely event of component failure, you can replace the failed component while the S2A is running. The replaced component will automatically be returned to service once the component has been installed and booted up.
!
Warning
If the S2A6620 is powered up and you remove any module, replace it immediately. If the system is used with modules missing for more than a few minutes, the system can overheat, causing power failure and data loss. Such use will invalidate the warranty.
!
Warning
Observe all conventional ESD precautions when handling S2A6620 modules and components. Avoid contact with backplane components and module connectors.
4.3.1
Replacing a Power/Cooling Module

If a power supply or fan fail, the PCM Fault LED on the power cooling module will turn amber. (Refer to Figure 91.) If a power supply unit or its fan is faulty, you must replace the whole PCM. You must not take any longer than 5 minutes to replace this module to prevent the enclosure from over-heating. NOTE : Obtain a replacement module of the same type before removing any faulty module. As there should always be two (2) power cooling modules installed, the system can continue running while you replace the faulty module. 1. Identify the failed PCM with an amber Fault LED. 2. Turn off the modules power switch and disconnect the power cord. 3. Loosen the modules thumbscrew on the lifting bar, lift the bar, and then slide the module out of the bay.
93
4. Ensure that the power switch on the new (replacement) module is OFF. 5. Slide the module into the bay making sure it is fully inserted by pressing on the lifting bar. Tighten the thumbscrew to secure it. 6. Connect the power cord. Turn on the power switch. Verify that the AC and DC LEDs are green, indicating that the module is operating normally.

Power Cord Connector Power Switch Thumbscrew on lifting bar
Lifting Bar
4.3.2
Replacing a Drive Module

If a drive module fails, the LED on the drive module will turn blue.
NOTE : When a drive is failed by the S2A6620, replace it promptly so that the operation and performance of the system are not affected.
Figure 92. Drive Module Removal
1. SLIDE LATCH BACKWARD 2. LIFT HANDLE AND PULL MODULE UP TO REMOVE
CAUTION : Drive spin down--Damage can occur to a drive if it is removed while still spinning. DDN recommends that you perform ALL steps of the following procedure to ensure that the drive has stopped prior to removal.
94
To remove a module:
1. The drive modules reside in an enclosure drawer. Pull out the drawer until the drawer locks securely in place. 2. Following the label instructions, release both front and rear cover locks.
3. Open the cover NOTE : Opening the cover affects the system cooling. Please limit service time to 5 minutes. Reminder beeps will occur occasionally. A continuous alarm will sound after 5 minutes. 4. Locate the carrier that has the blue LED. 5. On that carrier, slide the latch backward to release handle (Figure 92). 6. Lift handle and pull module up, just enough to disconnect the module from the backplane. 7. Wait for 30 seconds for the drive to completely spin down. 8. Pull the module gently out of the drive bay.
To insert a module:
9. Slide the latch backward to release handle. 10. Insert module into drive bay. Note orientation of module. 11. Cam the drive module home. The camming foot on the base of the module will engage into the slot in the enclosure. 12. When the module is fully inserted, close the handle. You should hear a click as the latch engages and holds the handle closed. 13. Close the enclosure covers.
95
14. Following the label instructions, secure both front and rear cover locks. NOTE : Both cover locks must be secure before shutting drawer into the rack. Otherwise, open cover alarm will sound. 15. Depress both shelf locks on both sides of drawer and push drawer back into rack.
96
4.3.3
Replacing a DEM
IMPORTANT: The DEM card should only be replaced by trained personnel. The handle rib will light up BLUE for service.
WARNING:
Observe all conventional ESD precautions. Avoid contact with backplane components and module connectors, etc.
NOTE :
Instructions are also clearly labeled on the inside cover of the enclosures (Figure 93).
Figure 93. DEM Removal Label
NOTE :
DDN recommends that this operation be performed with the file system unmounted and the S2A6620 offline.
To Replace the DEM

1. The DEMs reside in an enclosure drawer. Pull out the drawer until the drawer locks securely in place. 2. Following the label instructions, release both front and rear cover locks.
97
3. Open the cover. NOTE : Opening the cover affects the system cooling. Please limit service time to 5 minutes. Reminder beeps will occur occasionally. A continuous alarm will sound after 5 minutes.
4. Locate the DEM that needs to be replaced. 5. Grip the top latch, rotate it until you reach the limit of rotation, and then pull up to remove the DEM. 6. Insert the replacement DEM. 7. Press on the latch to rotate it down and lock it into place. 8. Close the enclosure covers. 9. Following the label instructions, secure both front and rear cover locks. NOTE : Both cover locks must be secure before shutting drawer into the rack. Otherwise, open cover alarm will sound.
10. Depress both shelf locks on both sides of drawer and push drawer back into rack.
4.3.4
Replacing an I/O Module on an expansion shelf

WARNING: Do not remove this module unless a replacement can be immediately added. The system must not be run without all units in place. If the controllers are running version 1.2 or later, you can replace an I/O module in an expansion shelf while the subsystem is running load.
98
However, if the controllers are running version 1.1, you must unmount all file systems using the 6620 storage and shutdown both controllers prior to replacing an I/O module in an expansion shelf.
Version 1.2-I/O Module Replacement:

1. Remove the SAS cable from the I/O module. If the I/O module was functioning, you will see the storage pools that had disks behind that I/O module fail over to the other controller load should continue. If the I/O module is not functioning, you should notice no changes in storage pool locations as they will have already failed over to the other controller. 2. Remove the I/O module from the chassis.
a) Release the two latches on the bottom of the unit by simply pulling each latch out and away from unit. b) Pull the latches forward to cam the module out of the enclosure. c) Grip the unit securely and withdraw the module.
3. Insert the new I/O module.
a) With the latches in the open position, slide the I/O module into the enclosure until the latches engage automatically. b) Cam the module home by manually closing the latches. A click should be heard as the latches engage.
4. Allow the I/O module to power up you should see the I/O LEDs turn on. 5. Insert the SAS cable into the new I/O module. You should now see some of the virtual disks move to their original home controllers as the path to the drives has been restored.
Version 1.1 - I/O Module Replacement:

1. Shutdown load from the host applications to the subsystem. 2. Shutdown both controllers by using the shutdown subsystem CLI command. WARNING: Wait until the controllers complete their shutdown before going to the next step. 3. Shutdown power to the 6620 base enclosure. 4. Shutdown power to the expansion shelf. 5. Remove the SAS cable from the I/O module. 6. Remove the I/O module from the chassis.
a) Release the two latches on the bottom of the unit by simply pulling each latch out and away from unit. b) Pull the latches forward to cam the module out of the enclosure. c) Grip the unit securely and withdraw the module.
99
7. Insert the new I/O module.
a) With the latches in the open position, slide the I/O module into the enclosure until the latches engage automatically. b) Cam the module home by manually closing the latches. A click should be heard as the latches engage.
8. Insert the SAS cable into the new I/O module. 9. Power up the expansion shelf. WARNING: Allow the expansion shelf to come up fully before proceeding to the next step. 10. Power on the base 6620 enclosure this should start the controllers. 11. Restart load from the host application.
100
4.3.5
Replacing a Controller
NOTE : A controller can be replaced while the subsystem in running load. If both controllers need to be replaced, replace each controller one at a time to ensure that the feature licensing is kept and to eliminate any chance of data loss.
To Replace the controller:

1. Using the CLUI command, ui show network *, get the IP address of the controller you want to replace. Record this IP Address as you will need to re-enter it on the new controller. 2. Shutdown the controller you want to replace using CLUI command, shutdown controller local force. All virtual disks on that controller will move to the surviving controller and load should continue. 3. Remove the cables from the controller. 4. Remove the controller from the chassis. 5. Insert the replacement controller into the chassis BUT DO NOT not plug in its cables yet. NOTE : The replacement controller should boot automatically. 6. Ping the old controllers IP address (as noted in step 1) to ensure there are no duplicate IP issues. 7. Login to the new controller. 8. Set the IP address using the CLUI command, ui set network local 0 <IP address from step 1>. 9. Verify the IP address is set by using the CLUI command, ui show network * . 10. Plug in the Ethernet cable BUT DO NOT PLUG IN the fibre channel cable yet. 11. Ping the replacement controller to ensure the network settings are working. NOTE : The replacement controller should be in a MIR_VERSION_MISMATCH state unless you are fortunate enough to receive a controller with the same firmware level on it. 12. To upgrade the firmware on the replacement controller to the correct level use the procedure outlined in this user manual. 13. After the upgrade, allow the replacement controller to reboot and join the other controller. 14. If the replacement controller has the correct level of firmware, it should be in a MIR_NOT_LAST_CONTROLLER state. This should clear on its own if it does not, you can use the clear subsystem MIR CLI command to force it to join the other controller
101
15. Verify the configuration (all virtual disks will still be on the surviving controller). 16. Verify that the feature licenses have been transferred by using the CLUI command, show controller local all. 17. Plug in the fibre channel cables. The virtual disks that were originally on the controller should begin to move back to the new controller.
102
4.3.6
Automatic Rebuild
A single drive failure in any Storage Pool does not result in data loss. The Virtual Disk(s) on that Storage Pool will continue to operate in degraded mode. If a spare drive is available and automatic rebuild is enabled, the S2A6620 will automatically rebuild the data to a spare drive. NOTE : System performance will be impacted while recovery is taking place. When a drive failure occurs, the failure is written to the event log. You may monitor the rebuild progress or adjust the rebuild rate to match the user load requirements. To display the event log (Figure 94), use the SHOW CONTROLLER LOCAL LOG command.
Figure 94. Display Event Log
RAID[0]$ show controller local log 000041 2009-02-04 15:03:17:7295774 G=4 S=0 T=1 RP=0 VP=1 LOG_ST_POOL_CHANGE STATE POOL CHANGE POOL:0003 STATE:0005 000042 2009-02-04 15:03:17:7295780 LOG_ST_MEMBER_CHANGE STATE MEMBER POOL:0003 INDEX:0000 STATE:0003 G=4 S=0 T=1 RP=0 VP=1 CHANGE ID:5000cca215c56e02 PDIDI:0145
State Change on Pool:0003 Drive Replacement Rebuild Initiated on Spare Drive
000043 2009-02-04 15:03:17:7295810 G=4 S=0 T=1 RP=0 VP=1 LOG_ST_REBUILD_START STATE REBUILD START ID:5000cca215c56e02 PDIDI:0145 POOL:0003 INDEX:0000 FENCE:0000000000000000
To look at the failed drive (Figure 95), enter command SHOW UNASSIGNED_POOL FAILED ALL
Figure 95. Display Failed Drive
RAID[0]$ show unassigned_pool failed all OID: 0x20a7003f Pool OID: UNASSIGNED Capacity: 704512 MBs (0x56000000 blocks) Raw Capacity: 715404 MBs (0x575466f0 blocks) Block Size: 512 Enabled Disk Ch: 0x27 0x22 Disk Slot: 1:42 Vendor ID: Hitachi Product ID: Hitachi HUA721075KLA330 Product Revision: GK8OAB0A Serial Number: GTF200P8GBVPXF Health State: FAILED Rotation Speed: 7200 RPM Device Type: SATA Member State: UNASSIGNED Spare: FALSE Failed: TRUE UUID: 0x5000cca215c564560
Physical Location Enclosure 1 Drive Slot 42
To monitor the rebuild progress (Figure 96), enter command SHOW JOB * ALL_ATTRIBUTES
Figure 96. Display Rebuild Progress
RAID[0]$ show job * all_attributes OID: 0x2b050003 Target: 0x19b40003 Type: REBUILD Status: RUNNING Priority: 80 Fraction Complete:12%
103
To show the Storage Pool information (Figure 97), enter command SHOW POOL <id> ALL_ATTRIBUTES. Once the rebuild is complete, the status of Storage Pool will return to NORMAL.
Figure 97. Display Storage Pool Information
RAID[0]$ show pool 3 all_attributes OID: 0x19b40003 Type: STORAGE Name: raid 5 set Chunk Size: 64KB (0x80 blocks) Block Size: 0x200 RAID Type: RAID5 Free Raid5 Capacity: 2752512 MBs Total Capacity: 3522560 MBs UUID: 0x00 Global Spare Pool: 0x1a0f000a Initializing: Rebuilding: Paused: AutoWriteLock: Data Lost: Current Home: Future Home: Preferred Home: BkgdJob OID: BkgdJob Priority: Total Phy Disks State: Member Size: pID State 0x0191 RBLD 0x004e NORM 0x0040 NORM 0x0041 NORM 0x0042 NORM ... FALSE TRUE FALSE FALSE FALSE 0x0015b2a122b20000 0xffffffffffffffff 0xffffffffffffffff 0x2b050003 80% 5 NOREDUNDANCY 704512 MB UUID 0x5000cca215c56e02 0x5000cca215c5709c 0x5000cca215c54c71 0x5000cca215c5675c 0x5000cca215c56e55
0x00000000 0x00000000 0x00000000
Spare Drive Rebuilding
4.3.7
Drive Replacement
Upon completion of a rebuild, the spare drive becomes a member of the Storage Pool, replacing the failed drive. After you have replaced the failed drive with a new drive, the new drive is added to the Unassigned Pool. It is recommended that you assign this new drive to the spare pool to replace the spare drive that has been used.
4.3.8
When a Spare is not available

When a drive is failed by the system and there is no spare drive available, you need to replace the failed drive immediately. After you have replaced the failed drive with a new drive, you can initiate a rebuild as described below: 1. Enter command SHOW UNASSIGNED_POOL * ALL to identify the new drives index name. 2. Enter command ASSIGN PHYSICAL_DISK <new-disk-id> TO_POOL <pool-id> SET_SPARE where <new-disk-id> is the index name of the replacement drive and <pool-id> is the OID of the Storage Pool that had the failed drive.
104
Manual Intervention Required (MIR) Conditions
4.4

Manual Intervention Required (MIR) represents a condition with the Controller that requires the user to provide a solution before proceeding with normal controller operations. This is to guard against the controller firmware executing operations that may not necessarily be the desired operation of the user. These conditions will most likely be seen in a new system installation environment. For example, when a system is booted and the backend physical disks have never been installed behind the Controllers, the controller firmware has never had a chance to write out configuration metadata. The Controller recognizes that there is no valid metadata and requires the user to provide input on whether to proceed or not. SHOW CONTROLLER LOCAL ALL_ATTRIBUTES will display the MIR condition of the Controller you are logged into (Figure 98).
Figure 98. Show Controller Information Screen
RAID[0]$ show controller local all_attributes OID: 0x38000001 Firmware Version: Release: 1.0.3.3 Source Version: 1877 Fully Checked In: Yes Private Build: Yes Build Type: Production Build Date and Time: 2009-03-02-09:49:EST Builder Username: compiler Builder Hostname: ereo-debian Build for CPU Type: AMD-64-bit Hardware Version: 0x0 State: RUNNING Local AP OID: 0x00000000 Memory Size: 0x0 Max Q of S ID: 0x0 Up Time (seconds): 0x7fe3 Last Event Sequence #: 0x27b Log Facility Mask: .... Crash Dump Enabled: Log Disk Enabled: RP Count: Restart Pending: Name: Controller: Controller ID: MIR Reason:
TRUE TRUE 0x1 FALSE B LOCAL (SECONDARY) 0x0015b2a1214a0000 None
Listed below are the possible MIR conditions and their required actions.
MIR_JIS_DISCOVERY_IN_PROG
Initialized Storage discovery is in progress. Please allow time for configuration discovery to complete. If this condition persists, please reboot the system. If this condition continues to persist after the reboot, please contact customer support.
MIR_OTHER_JIS_DISCOVERY_IN_PROG
Initialized Storage discovery is in progress on the other controller. Please allow time for configuration discovery to complete. If this condition persists, please reboot the system. If this condition continues to persist after the reboot, please contact customer support.
105
MIR_NO_BACKEND_DRIVES
This controller cannot find any disk drives on the backend. Install disk drives on the backend or fix the condition that prevents this controller from finding backend drives. Please refer to the installation guidelines for proper setup.
MIR_NO_CONFIG
A configuration could not be created on the backend drives. Fix the condition that prevents this controller from creating a configuration on the backend drives. Please refer to the installation guidelines for proper setup.
MIR_NO_QUORUM
No quorum drives could be found within the disk drives on the backend. Fix the condition that prevents the quorum drives from being seen. This may be caused by the drives never being in the storage array. This will normally happen on new system installations. Use the "CLEAR SUBSYSTEM MIR_STATE" command to create an empty configuration. *NOTE: This creates a new configuration and the old configuration will be deleted if existed.
MIR_NOT_LAST_CONTROLLER
This controller found a valid configuration, but was not present when another controller owned the configuration. Since the controller was not present, it does not know if another controller may have cached data for this configuration. This may happen when controllers are swapped out or if the controllers went down and restarted individually. In many cases, this MIR state will resolve itself by communicating with the other controller and obtaining permission to use the found configuration. If the MIR state does not resolve itself in 3 minutes, it is recommended to manually clear this state by telling the controller to use the found configuration. To use the found configuration on this controller, use the "CLEAR SUBSYSTEM MIR_STATE" command.
MIR_MULTIPLE_JIS
Multiple configurations were found on the quorum disks. This may happen if the drives from one system were installed in another system when the systems were powered down and then rebooted. If the drives were installed in the system while running, then this should not be an issue. A list of found configurations will be listed. Use the "CLEAR SUBSYSTEM MIR_STATE ID=<id>" command to use the specified ID's configuration.
MIR_DUAL_NO_AGREE
The two connected controllers do not agree on the id of the configuration. This may occur if one controller saw a subset of the drives and the other controller saw a different subset of drives. Please refer to the installation guidelines for proper setup.
MIR_CONFIG_MISMATCH
The configuration version of this firmware does not match the configuration version of that on media. To proceed, either reload the previous version of firmware and do a backup then upgrade, or delete your configuration to continue. Use "CLEAR SUBSYSTEM CONFIGURATION" to create an empty configuration. *NOTE: This creates a new configuration and the old configuration will be deleted if existed.
106
MIR_NO_LOAD_CONFIG
A configuration could not be loaded from the backend drives. Fix the condition that prevents this controller from loading a configuration from the backend drives, or use "CLEAR SUBSYSTEM MIR_STATE" to create an empty configuration. Please refer to the installation guidelines for proper setup. *NOTE: This creates a new configuration and the old configuration will be deleted if existed.
107
S ECTION 5
GUI Management Agent
The GUI Management Agent
5.1
The GUI Management Agent

This section provides information on configuring your S2A6620 using the GUI (Graphic User Interface) Management Agent. NOTE : The configuration examples provided here represent only a general guideline. These examples should not be used directly to configure your particular S2A6620.
110
Starting the GUI Management Agent
5.2
5.2.1
Login
Using a web browser, open a link to the IP address of the 6620. The S2A Management System supports Mozilla FireFox (version 3.0.11 and above) as well as Microsoft Internet Explorer (version 8.0 and above). At the login screen, use the user name admin with the password password to log into the system. S2A6620. User name and passwords are care sensitive. Figure 99. Logon Screen
5.2.2
Initial Home Screen and Health Indicators

The home screen shows the Health Indicator. Since this is a new unconfigured system, at this point, the Health Indicator should be orange. You should see an alert message below the Health Indicator which show that manual intervention is required for both controllers.
WARNING: For any future encounters with MIR state issues, please refer to the Service Manual for specific instructions on how to clear them.
1. Select the controller name. The system displays the Show Controller Screen. home screen shows the Health Indicator. 2. Select the underlined Manual Intervention Required. Details of the MIR state displays, STATUS=MIR: no quorum disks found.
111
3. Press the CLEAR MIR button to clear the MIR state. Your subsystem is now ready to be configured. Figure 100. Controllers-Show All Screen
112
Physical Disks
5.3
Physical Disks
5.3.1
Physical Disks Commands

Physical Disk Commands are located under the Physical Disk tab drop down menu: Show Physical Disks Show Failed Disks Locate Disks Set Failed Assign to Pool Clear Failed
NOTE : If asterisks appear in the PD column when you attempt to view the advanced drives or attempt to locate a drive, this shows that only 1 controller see the drive. Therefore a controller is down or another hardware issue exists somewhere.
5.3.2
Checking Status of Physical Disks

Before creating any storage pools, check the status of all the drives.
Under the Physical Disks tab, select SHOW ALL PHYSICAL DISKS to verify that all the drives are present and healthy. Figure 101. Physical Disk-Show All Screen
NOTE : If the drives are not visible, select SUBSYSTEM RESTART under the Subsystem tab to reboot
the system.
113
Storage Pools
5.4
Storage Pools
When creating a Storage Pool on a S2A6620, the following selectable attributes are available: RAID Level Storage Pools can be configured to use either a RAID1, RAID5 or RAID6 parity scheme. In RAID5, the capacity of one drive is reserved for parity, allowing data recovery in the event of a single drive loss in the Storage Pool. In RAID6, the capacity of two drives is reserved for parity, allowing data recovery if either one or two drives are down in a Storage Pool. For maximum data protection, DataDirect Networks recommends the use of RAID6. Chunk Size The chunk size defines the amount of data written to a single disk before proceeding to the next disk in the Storage Pool. For optimal performance, the chunk size should be proportional to the expected host request size. For example, a large chunk size should be used when transferring large blocks of data while a small chunk size should be used when transferring multiple small blocks of data. Drive Count A RAID5 Storage Pool may consist of 5 or 9 drives. A RAID6 Storage Pool may consist of 6 or 10 drives. For maximum performance, Storage Pools should be created using drives with the same characteristics (such as SAS/SATA, capacity, and RPM). Drive Type Drive types can be SAS or SATA. Drive Size Drive size is the capacity of the drive. Spindle Speed You may choose (RPM): 15000, 10000, 7200, 5400, 0 or SSD. SATAssure
SATAssure technology is designed by DDN to improve the reliability of enterprise SATA drives and make sure that data integrity is always mentioned for all IO operations. A license is required to run this feature.
5.4.1
Storage Pool Commands

Storage Pool Commands are located under the Pool tab drop down menu: Show Storage Pools Create Storage Pool Set Storage Pools Attributes Delete Storage Pool Locate Storage Pool
114
Storage Pools
To create a Storage Pool :

1. Under POOLS tab, select CREATE STORAGE POOL. displays. Figure 102. Create Storage Pool Screen 1 Storage Pools-Create Storage Pool screen
2. Select CHUNK_SIZE for pools of type RAID5(4d+1p), RAID5 (8d+1p), RIAD6 (4d+2p: 32kb, 64kb, 128kb, 256kb.
NOTE : RAID1 does not accept a chunk size and the selection field will be disabled when RAID1 is selected.
3. Enable or disable SATAssure 4. Select RAID Level: RAID1, RAID5(4d+1p), RAID5(8d+1p), RAID6(4d+2p), RAID6(8d+2p) 5. Select Drive Type from scroll list. 6. Select Spindle Speed from scroll list. 7. Select Drive Size from scroll list. 8. Select CREATE STORAGE POOL. Success or error message displays followed by list of created storage pools.
Figure 103. Storage Pool List
9. Repeat step 1 to add more Storage Pools as needed.
115
Storage Pools
10. Select Advanced Options. displays.

Figure 104. Create Storage Pool Screen 1
Storage Pools-Create Storage Pool Advanced screen
11. Select drives to add to the pool to be created. 12. Select Create Storage Pools. 13. To return to previous screen, select Back. 14. To cancel, select Cancel.
To show Storage Pools:

Under POOLS tab, select SHOW STORAGE POOLs.
To delete Storage Pool:

1. Under POOLS tab, select DELETE STORAGE POOL. Storage Pools-Delete Storage Pool screen displays. 2. Select the storage pool you want to delete. 3. Press the DELETE button or press CANCEL to cancel operation. Success or failure message displays.
To set storage pool attributes:

1. Under POOLS tab, select SET STORAGE POOL ATTRIBUTES. Storage Pools- Set Attributes screen displays. 2. Select the storage pool whose attributes you want to change. Set Attributes screen appears,
116
Storage Pools
Figure 105. Storage Pool Set Attributes
3. Make the changes desired. 4. Press the UPDATE button. Success or failure message displays.
To locate storage pools:

1. Under POOLS tab, select LOCATE STORAGE POOL. Storage Pools- Locate screen displays. 2. Select the storage pool you want to locate. Screen appropriately changes.
Figure 106. Storage Pool Locate
3. Press the LOCATE button. Success or failure message displays.
117
Virtual Disks
5.5
Virtual Disks
A Virtual Disk can span a portion Storage Pool or utilize then entire capacity of a single Storage Pool. VDs are created in increments of 8GB, that is, 6GB=8GB, 15GB=16GB, etc.
5.5.1
Virtual Disk Commands

Virtual Disk Commands are located under the Virtual Disk tab drop down menu:
Show Virtual Disks Create Virtual Disk Set Virtual Disks Attributes Delete Virtual Disk
To create a Virtual Disk:

1. Under the Virtual Disk tab, select CREATE Virtual Disk. Virtual Disk-Create screen displays.
Figure 107. Create Virtual Disk Screen 1
2. Select Pool. 3. Enter CAPACITY in GiB. 4. Press CREATE VIRTUAL DISK button. A message displays to indicate whether or not the Virtual Disk creation was successful.
118
Virtual Disks
Figure 108. Create Virtual Disk Screen 2
5. Repeat steps 1-4 to add more Virtual Disks as needed. 6. Under Virtual Disk tab, select SHOW VIRTUAL DISKS to view the list of configured Virtual Disk(s). Select the individual VD Name to display detailed information of the Virtual Disk selected.
Figure 109. Virtual Disk Detail Screen
To delete a Virtual Disk:

1. Under Virtual Disk tab, select DELETE Virtual Disk. Delete Virtual Disk screen displays. 2. Select the virtual disk you want to delete. 3. Press the DELETE button or press CANCEL to cancel operation. Success or failure message displays.
To view a list a Virtual Disks:

Under Virtual Disk tab, select Show Virtual Disk.
To set Virtual Disk Attributes:

1. Under Virtual Disk tab, select SET VIRTUAL DISK ATTRIBUTES. Virtual Disks- Set Attributes screen displays. 2. Select the virtual disk whose attributes you want to change. Set Attributes screen appears.
119
Virtual Disks
Figure 110. Virtual Disk Set Attributes
120
Spare Pools
5.6
Spare Pools
The S2A6620 supports the concept of Spare Pool. A Spare Pool contains Physical Disks that can be used as spare disks in one or more Storage Pools. In the event of a drive failure, a drive that is assigned to a spare pool is automatically swapped into the Storage Pool to replace the failed drive. A rebuild then occurs immediately, reducing the possibility of data loss due to additional drive failures. Spare pools can be shared by Storage Pools or dedicated to a particular Storage Pool in which case the spare disks will only be used by the designated Storage Pool.
5.6.1
Spare Pool Commands

Spare pool Commands are located under the Pool tab drop down menu:
Show Spare Pools Create Spare Pool Set Spare Pools Attributes Delete Spare Pool Locate Spare Pool
To create a Spare Pool:

1. Under POOLS tab, select CREATE SPARE POOL. Spare Pools-Create Spare Pool screen displays.
.
Figure 111. Create Storage Pool Screen 1
2. Select Drive Size. 3. Select Spindle Speed. 4. Select Drive Type.
121
Spare Pools
5. Press Next button. STORAGE POOLS-CREATE STORAGE POOLS-ADVANCED screen displays.
Figure 112. Create Storage Pools Advanced Screen
6.
Select PHYSICAL DISK by checking in the appropriate box.
7. Select CREATE SPARE POOL. A message is displayed to indicate whether the new spare pool creation was successful.
8. Repeat Steps 1 - 7 to add more spare pools as needed. NOTE : Each Storage Pool must have a spare pool assigned to it.
To display a list of unassigned Spare Pools:

1. Under POOLS tab, select SHOW UNASSIGNED POOL.
2. Under POOLS tab, select command SHOW SPARE POOL to view the list of configured spare pool(s). 3. To assign the spare pool to a storage pool, select SET POOL ATTRIBUTES under POOL tab. 4. Select the name of the pool that you will assign to the new Spare Pool.
WARNING: When assigning disk drives to a spare pool that is to be assigned to a given storage pool, be sure to select a disk that is as large or larger than any disks in the assigned storage pool.
122
Spare Pools
Figure 113. Set Spare Pool Attributes
5. In the drop down for Assign Spare Pool, select the name of the Spare Pool then press the Update button.
To show Spare Pools:

Under POOLS tab, select SHOW SPARE POOLs.
To delete Spare Pools:

1. Under POOLS tab, select DELETE SPARE POOL. Spare Pools-Delete Spare Pool screen displays. 2. Select the spare pool you want to delete. 3. Press the DELETE button or press CANCEL to cancel operation. Success or failure message displays.
To set spare pool attributes:

1. Under POOLS tab, select SET SPARE POOL ATTRIBUTES. Spare Pools- Set Attributes screen displays. 2. Select the storage pool whose attributes you want to change. Set Attributes screen appears,
123
Spare Pools
Figure 114. Storage Pool Set Attributes
To locate spare pools:

1. Under POOLS tab, select LOCATE SPARE POOL. SPARE Pools- Locate screen displays. 2. Select the storage pool you want to locate. Screen appropriately changes. 3. Press the LOCATE button. Success or failure message displays.
To display the list of available disks, under POOLS tab, select SHOW UNASSIGNED POOL 4. Under POOLS tab, select command SHOW SPARE POOL to view the list of configured spare pool(s).
NOTE : Each Storage Pool must have a spare pool assigned to it. If a Storage Pools attributes show
Global Spare Pool: UNASSIGNED no spare pool will serve this Storage Pool. , 5. To assign the spare pool to a storage pool, select SET POOL ATTRIBUTES under POOL tab. 6. Select the name of the pool that you will assign to the new Spare Pool. 7. In the drop down for Assign Spare Pool, select the name of the Spare Pool then press the Update button.
124
5.7

When a Storage Pool is created, initialization begins immediately as a background job and will continue until it is completed. Once the Storage Pool has completed its initialization, Virtual Disk(s) can be presented to host systems. However, you may immediately create the presentations. To monitor the progress of a job, under SUBSYSTEM tab, select the SHOW BACKGROUND JOBS. Figure 115. Subsystem Menu
It will display the type of job and the percentage of completion. Select Background Job to display all attributes. Figure 116.
You may also check if a Virtual Disk is ready for access by selecting under the Virtual Disk tab, SHOW VIRTUAL DISKS.
125
Figure 117.
126
Presentations
5.8
Presentations
A Presentation on a S2A6620 has the following components: Discovered Initiators A Discovered Initiator is defined as a Fibre-channel initiator that has logged into the S2A6620. This is normally a single port on a Fibre-channel HBA in an external computer. Host A Host is an abstract client of a Virtual Disk that has all the access to all data within the Virtual Disk. This most commonly represents an external computer with one or more Fibre Channel initiators. Host attributes are OS (operating system) of which you can select GENERIC, WINDOWS, LINUX or MAC_OS. The OS attribute dictates the way the controller responds to certain Fibre-channel commands where appropriate. For example, Mac OS X expects a different response from an inquiry of LUN0 (the controller LUN) than a Windows host. Channel A Channel is one of the Fibre-channel ports on the controller. Channel attributes are MODE of which you can select either MAC_OS or STANDARD. When MAC_OS is selected, the ports node name will be set differently in order to be visible to a Macintosh system. Stack A Stack is the input side of the subsystem. In the case of the S2A6620, the stack is defined as the Fibre-channel interface. In future versions of the product, different interface stacks may exist. Presentation A Presentation is the relationship between a Host and a Virtual Disk. A presentation implies that the related Host has some sort of access to the Virtual Disk. Attributes of a Presentation are: PORT - from which the host will see the virtual disk READ_ONLY - controls read only access PRESENT_HOME_ONLY - presents the specified Virtual Disk from its designated home controller only LUN - user-specified the LUN number that the Virtual Disk will show to the host.
5.8.1
Presentation Commands
Presentation commands are located under the Presentation tab drop down menu:
Show Presentation Create Presentation Delete Presentation Update Presentation

To present the Virtual Disk to an external host: 1. Under the Presentation tab, select Create Host.
127
Presentations
Figure 118. Presentation Menu
Presentation-Create Host screen displays.
Figure 119. Presentation-Create Host Screen 1
2. Specify the OS attribute using the pull down menu if necessary. 3. Press the Create Host button. Success or error message displays followed by list of created hosts.
Figure 120. Create Host Screen 2
4. Repeat steps 1-3 to create more hosts. To import one or more Discovered Initiators to your newly created Host: 1. Under the Presentation tab, select Import Initiators. Presentation-Create Host screen displays.
128
Presentations
Figure 121. Presentation-Import Initiator Screen 1
2. Select the Initiator. 3. Select the corresponding host, 4. Press the Import Initiator button. Success or error message displays. To create the Presentation: 1. Under the Presentation tab, select Create Presentation. Presentation-Create Presentation screen displays. Figure 122. Create Presentation Screen 1
2. Select a host and a virtual disk. 3. Press the Create Presentation button. Success or error message displays.
129
Presentations
NOTE : You can view the new Presentations by selecting the Show Presentation menu selection under
Presentation tab.
Figure 123. Show Presentation Screen
The external computer can access the Pool once it has completed its initialization. You may also check if a Virtual Disk is ready for access by selecting under the Virtual Disk tab, SHOW VIRTUAL DISKS. OPTIONAL: To present the virtual disks to all hosts on all ports,: 1. Under the Presentation tab, select Create Presentation. Presentation-Create Presentation screen displays. Figure 124. Presentation-Create Presentation Display Screen
2. Select ALL HOSTS option. 3. Select Virtual Disks. 4. Press the Create Presentation button.
130
Email and Critical Event Notification Setup
5.9

Notices that a critical event has occurred will be sent via email. This email address is user-entered. Only one is permitted per system. To set up or change the email address:
1. Under the SUBSYSTEM tab, select the UPDATE EMAIL SETTINGS.

Figure 125. Update Email Settings Screen.
The upper portion of the screen will display the current Email Agent Attributes, if any. You will access the lower portion of the screen to enter email information.
2. In the Update IP Address field, enter the IP address of the SMTP server to which the subsystem will send email notifications. 3. In the IP Port field, enter the IP Port of the SMTP server to which the subsystem will send email notifications. 4. In the Update From field (maximum field size 512), enter an identification string, such as the name of the controller. This is a string which will be included on the From line of the email notification message sent by the agent. 5. In the Update To field (maximum field size 512), enter an Internet Mail Format (RFC2822) email address to which the subsystem will send email notifications. 6. In the Update Subject field (maximum field size 512), enter a string to be included on the Subject line of the email notification sent by the email agent. 7. Press the UPDATE button. Success or failure message displays. The tables below detail the additional inquiry items and events that will be trapped in the SMNP MIB and in the Email Agent.
131
Figure 126. SNMP and Email Notification Events SNMP EVENTS ERROR LOG_ES_EXPANDER_ELEMENT_ERROR LOG_ES_POWER_SUPPLY_NORMAL LOG_ES_POWER_SUPPLY_REMOVED LOG_ES_POWER_SUPPLY_INSERTED LOG_ES_TEMPERATURE_SENSOR_NORMAL LOG_ES_TEMPERATURE_SENSOR_REMOVED LOG_ES_TEMPERATURE_SENSOR_INSERTED LOG_ES_COOLING_ELEMENT_NORMAL LOG_ES_COOLING_ELEMENT_REMOVED LOG_ES_COOLING_ELEMENT_INSERTED LOG_ES_EXPANDER_ELEMENT_NORMAL LOG_ES_EXPANDER_ELEMENT_REMOVED LOG_ES_EXPANDER_ELEMENT_INSERTED LOG_ES_DISK_SLOT_ELEMENT_REMOVED LOG_ES_DISK_SLOT_ELEMENT_INSERTED DESCRIPTION A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has reported an error condition. The power supply has returned to a normal status. A power supply has been removed. A power supply has been inserted. A temperature sensor (located in the power supply) has returned to normal status. A temperature sensor (located in the power supply) has been removed. A temperature sensor (located in the power supply) has been inserted A fan (located in the power supply) has returned to normal status A fan (located in the power supply) has been removed. A fan (located in the power supply) has been inserted The DEM reports normal. A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has been removed. A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has been inserted. A device has been removed from a disk slot. A device has been inserted into a disk slot.
Email Notification Events LOG_ES_EXPANDER_ELEMENT_ERROR A DEM (base shelf or expansion shelf) or an IO module (expansion shelf) has reported an error condition.
132
S ECTION 6
Appendices
A
Technical Specifications
Here are the technical specifications for the S2A6620.
NOTE : Specifications subject to change without notice.
Configuration, Performance, & Capacity Host interface Drive interface Management interface Cache memory Number of host ports Number of host connections Number of drives supported Number of Storage Pools supported Number of Virtual Disks supported Number of Spare Pools supported Hot spare capability Full duplex 10/100/1000 BaseT onboard Fibre channel 8Gb/s SAS / SATA /SDD RS-232 and Ethernet (SSH) 6 GB 4 Up to 512 Up to 60 with a single unit, 120 with expansion enclosure 256 512; 64 per pool 16 Yes Yes
Reliability SES (SCSI Enclosure Services) protocol support Temperature monitoring Redundant hot-swappable power & cooling modules Yes Yes 2
135
Physical, Power & Environmental S2A6620 chassis dimensions (HWD) S2A6620 chassis Weight 7.0" (18 cm) 17.56" (45 cm) 37" (94 cm) 120 lbs (54.5 kg) without drives, 240 lbs (109.1 kg) with drives 200-240 V @ 47-63 Hz 10.3A @ 230VAC 7.5A @ 230VAC 5 C to 35 C / 20% - 80%, non-condensing
Electrical/AC Power consumption (maximum current) Power consumption (average current) Operating environment (temperature / relative humidity) Non-operating environment (temperature/ relative humidity) Cooling (maximum, peak, average) Certification
-10 C to 35 C / 20% - 80%, non-condensing
13324 BTU/h, 6560 BTU/h, 5973 BTU/h UL, CE, CUL, FCC
NOTE : Specifications subject to change without notice.
136
B
Safety Requirements for Rack Installation
The following safety requirements must be considered when theS2A6620 is mounted in a rack. The rack when configured with the units must meet the safety requirements of UL 60950 and IEC 60950. Mechanical Loading The mounting of the system must conform to even and safe mechanical loading. Uneven mechanical loading could cause a rack to tip and fall. The rack construction must be capable of supporting the total weight of the installed enclosure(s) and the design should incorporate stabilizing features suitable to prevent the rack from tipping or being pushed over during installation or in normal use. When loading a rack with the units, fill the rack from the bottom up and empty from the top down. Always remove all modules and drives, to minimize weight, before loading the chassis into a rack.
WARNING : It is recommended that you do not slide more than one enclosure out of the rack at a time, to avoid danger of the rack tipping over.
When mounting in a rack, ensure that the enclosure is pushed fully back into the rack. The system must be operated with low pressure rear exhaust installation. (The back pressure created by rack doors and obstacles should not exceed 5 pascals [0.5mm water gauge].) Circuit Overloading The rack should have a safe electrical distribution system. It must provide over current protection for the unit and must not be overloaded by the total number of units installed in the rack. Consideration of the units nameplate rating should be used when addressing these concerns. Reliable Earthing The electrical distribution system must provide a reliable earth ground for each unit and the rack. Each power supply in each unit has an earth leakage current of 1.5mA. The design of the electrical distribution system must take into consideration the total earth leakage current from all the power supplies in all the units. The rack will require labelling with HIGH LEAKAGE CURRENT. Earth connection essential before connecting supply.
137
Elevated Operating Ambient Temperature If the S2A6620 system is installed in a closed or multi-unit rack assembly, the operating ambient temperature of the rack environment may be greater than room ambient. The rack design should take into consideration the maximum operating ambient temperature for the unit is 35C. Air Flow When installing the system, do not compromise on the amount of air flow required for safe operation of the system.
138
Contacting Technical Support & Shipping Instructions
You can contact DataDirect Networks Technical Support by: Telephone at 1 . 8 8 8 . 6 3 4 . 2 3 7 4 (North America) 1 . 8 1 8 . 7 1 8. 8 5 0 7 (International) Internet e-mail at support@datadirectnet.com Technical Support is available Monday through Friday. After hours support is available to those customers that have a Service Contract. Please contact our sales representatives for more information. You can find us on the World Wide Web at www.ddn.com You can contact our Customer Service by: Telephone at 1 . 8 1 8 . 7 0 0 . 6 0 5 2 Internet e-mail at customerservice@datadirectnet.com Our Corporate Headquarters is located at: 9351 Deering Avenue, Chatsworth, California 91311 1 . 8 1 8 . 7 0 0 . 76 0 0 , 1 . 8 1 8 . 7 0 0 . 7 60 1 (fax)
Product Shipping Instructions

If you are shipping the product to another location, always use the original packaging provided with your unit(s). If you are sending a product to DataDirect Networks for warranty or out of warranty repair, you must obtain a Return of Materials Authorization (RMA) number from DataDirect Networks Technical Support.
96-30040-001

S2A6620 User GuideV1.2

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

S2A6620 User GuideV1.2

Transféré par

Droits d'auteur :

Formats disponibles

Silicon Storage Appliance S2A6620 (SFA OS Version 1.

Printed in the USA December 2009 Document Number 96-30040-001 Rev C

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

S2A6620 User Guide (Rev C)

Complete Mailing Address:

_____________________ _____________________ Phone Number: Email Address: _____________________ _____________________

Signed for Boutell.Com, Inc.: _____________________ Date: _____________________

S2A6620 User Guide (Rev C)

Potential for Radio Frequency Interference

S2A6620 User Guide ( Rev C)

Safety goggles should be worn when maintaining the equipment.

S2A6620 User Guide ( Rev C)

Recycling of Waste Electrical and Electronic Equipment (WEEE)

S2A6620 User Guide ( Rev C)

Additional Configuration Considerations For Macintosh Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix B. Safety Requirements for Rack Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

S2A6620 User Guide (Re v C)

DataDirect Networks SAN Solution

Features of the S2A6620

S2A6620 User Guide (Re v C)

S2A6620 User Guide (Re v C)

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

The S2A6620 System Hardware

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

Figure 3. S2A6620 Rear View

Power Cooling Module 1

Power Cooling Module 2

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

Figure 4. A S2A6620 Controller

Identify LED Power LED

Power Switch Ethernet Port

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

Power Cooling Module (PCM)

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

Figure 8. Drive Module

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

Drive Expander Module (DEM) Card

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

Front Panel Indicators

Drive Activity LEDs

S2A6620 User Guide (Re v C)

The S2A6620 System Hardware

S2A6620 User Guide (Re v C)

___________ _ Phone Number: Email Address: _ ___________

Signed for Boutell.Com, Inc.: _ Date: _