Release Notes: This release contains SNIA CTP-certified support for SMI-S 1.1. SMI-S 1.0.2/1.0.3 is also supported, but CTP re-certification was not funded since CTP 1.0.2 was previously certified. The SMI provider in this release is intended for use with storage systems developed by Engenio Storage Group, LSI Logic Corporation. SMI Provider Version: 9.16.G0.34 July 2006 SMI-S support: 1.1, 1.0.2/1.0.3 FOR USE WITH IBM TotalStorage Productivity Center 3.1.1 and above. ************************************************************************* Table of Contents 1) Supported Features 2) Supported Firmware Versions 3) Upgrading from a previous Version of the Provider 4) Installing the SMI-S Provider 5) Starting, Stopping, Restarting the provider service 6) Adding a device for management 7) Tracing 8) Authentication 9) Multi-homed servers 10) Uninstalling 11) Notes 12) Known Issues 13) End User License Agreement ************************************************************************* 1) Supported Features The 1.1 provider supports both the 1.1 and the 1.0.2 SMI-S interfaces, distinguished by namespace. SMI-S 1.1 is supported in the /root/lsissi11 namespace. SMI-S 1.0.2 is supported in the /root/lsissi namespace. 1.1--------------------- The following profiles and subprofiles (indented) are supported in the SMI-S 1.1 Provider: Server Array Access Points (non-CTP experimental support) Disk Drive Lite LUN Creation Extent Composition Location Software Copy Services (Snapshot, Volume Copy, Remote Volume Mirror) Job Control Device Credentials Masking and Mapping Multiple Computer System Block Server Performance 1.0.2/1.0.3------------- The following profiles and subprofiles (indented) are supported in the SMI-S 1.02 Provider: Server Array Disk Drive Cluster Extent Mapping Software Copy Services (Snapshot, Volume Copy) Pool Manipulation, Capabilities and Settings LUN Creation Device Credentials LUN Mapping and Masking Backend Ports Please refer to the document SMI Provider Functional Specification for details about the SMI provider specific implementation of these profiles. ************************************************************************* 2) Supported Firmware Versions The following RAID controller firmware versions are supported in this release: 5.30, 5.33, 5.34, 5.40, 5.42, 6.10, 6.12, 6.14, 6.15, 6.16 (SANtricity Storage Manager versions 8.3, 8.33, 8.34, 8.40, 8.42, 9.10, 9.12, 9.14, 9.15, 9.16 respectively) Note that this provider supports Engenio storage products and does not include support for LSI MegaRAID products. ************************************************************************* 3) Upgrading from a previous Version of the Provider This Provider is a stand-alone replacement for any down-level SMI Provider. To correctly install the provider accompanying this readme: 1. Follow the directions that accompanied your currently installed provider, to uninstall and completely remove that version of the provider. 2. Follow the directions in section 4 below to install the new provider. ************************************************************************* 4) Installing the SMI Provider The provider is packaged as an archive file for UNIX servers and as an install executable for Windows. 1. Move the provider install archive/executable into the file system on the server where it is to be installed. 2. For Windows: Double click the install executable icon and follow the directions provided on screen. This completes the Windows installation. None of the remaining steps pertain to Windows. At this point you can delete the install executable if you so desire. 3. For all UNIX platforms: unpack the archive file using the command: tar -xvf {archive file name} 4. For all UNIX platforms: run the install script using the command: ./install. Follow the directions provided on screen. This completes the Unix install. You should retain the UNIX install files because they are used to deinstall. You can delete the original archive file if you so desire. ************************************************************************* 5) Starting, Stopping And Restarting the Provider Service 1. For Windows: Use the MMC services panel, start, stop or restart service "Engenio SMI-S Provider Server". 2. For Solaris: cd /opt/engenio/SMI_SProvider/bin. Use the following commands: ./launch start - to start ./launch stop - to stop ./launch restart - to restart 3. For Linux: cd /usr/engenio/SMI_SProvider/bin. Use the following commands: ./launch start - to start ./launch stop - to stop ./launch restart - to restart 4. For AIX: cd /opt/engenio/SMI_SProvider/bin. Use the following commands: ./launch start - to start ./launch stop - to stop ./launch restart - to restart ************************************************************************* 6) Adding a Device for management: 1. From Cimworkshop, locate the class "_DeviceDiscoveryService", invoke the "addDevice" method on an instance of that class and add your host name or IP address in the "HostNameOrIPAddr" property. If you wish to make any changes to the array's configuration, you will need to create an instance of _SharedSecret as described in the SMI-S with the following properties specified: SystemCreationClassName "_StorageSystem" SystemName _StorageSystem.Name (Insert the Storage Identifier you obtain by enumerating instances of_ProviderConfig) ServiceCreationClassName "_SharedSecretService" ServiceName "SharedSecretService" RemoteID any user name Secret client-defined password - the array password. 2. Instead of step 1 above you can execute the ProviderUtil bat file/script in release/SMI_SProvider/bin, on Unix-based system, execute sh ProviderUtil For Windows, execute ProviderUtil.bat. Follow the prompts, the default CIMOM port is 5988. When the script is finished after an addDevice, the array will be added and the SharedSecret instance will be present. Note: the client can also modify the secret which in turn changes the password on the array. Please do not modify the secret on the arrays in the SNIA lab. ************************************************************************* 7) Debug Tracing NOTE: Any changes to the tracing level will require a restart of the provider to take effect. NOTE: Turn on tracing only under the direction of your customer support representative. 1. Go to directory {install location}/SMI_SProvider/bin 2. Edit file providerTraceLog.properties in a text file editor such as notepad or vi. 3. Scroll down to the last line in the file and remove # at the begining of the line. 4. Save the file and exit the editor. 5. Restart the provider using the directions in the above section. 6. On Windows: the trace log will be in either C:\WINNT\System32 or C:\WINDOWS\System32. 7. On UNIX: the trace log is in the {install location}/SMI_SProvider/bin director. 8. The trace file name is: SMI_SProvider.log. ************************************************************************* 8) Authentication The provider is shipped with authentication turned off by default. It is only available to be turned on if the Provider / CIMOM package is installed together. If you choose to install the Provider into an existing CIMOM, the CIMOM into which the Provider is installed must take care of authentication. In order to turn authentication on, you must stop the Provider service and edit the cimom.properties file in the wbemservices/cimom/bin folder. Do the following: From the list of available authentication providers (listed below), choose the one you want and make sure it does not have the "#" in front of it. Only ONE must be selected (not have the "#" in front). The list below is the default: ======================================================================================================== org.wbemservices.wbem.cimom.pswdprov=org.wbemservices.wbem.cimom.security.UnsecureUserPasswordProvider #org.wbemservices.wbem.cimom.pswdprov=cimprovider.security.BasicUserPasswordProvider #org.wbemservices.wbem.cimom.pswdprov=cimprovider.security.CredentialsBasedPasswordProvider ======================================================================================================== When BasicUserPasswordProvider authentication is enabled, domain and local users are allowed to authenticate on Windows machines. If operating over VPN, domain authentication does not function. Only local users are allowed to authenticate on Unix machines. When CredentialsBasedPasswordProvider authentication is enabled, initially, all users are allowed. To secure the system, you must create an instance of _CIMOMSharedSecret in the "/interop" namespace. The following keys must be populated as such: SystemCreationClassName = "_StorageManagementSystem" CreationClassName = "_CIMOMSharedSecretService" ServiceName = "CIMOMSharedSecretService" SystemName = CIMOM_IP RemoteId = USER_CHOICE If you wish to have an actual password, you must also populate the "Secret" property with a password of your choosing. With this authentication enabled, only user/password combinations created as _CIMOMSharedSecret instances will be allowed access to the CIMOM. To remove a user, simply delete the appropriate instance. ************************************************************************* 9) Multi-homed hosts In order for SLP to work correctly on machines with multiple IP addresses, create a file named "systemIPs.txt". It should be created in the ..\SMI_SProvider\bin directory where the product was installed. This differs by operating system. Edit this file and list one or more of the known IP addresses of the server, each one on a separate line, in order of precedence (most preferred address on top). When the CIMOM is started it tries to use each address in the file in the order they are listed. It stops when it finds one it can use and will use that address from then on. If the CIMOM is run on a server with multiple IP addresses and this process is not followed, it will randomly and inconsistently select one of addresses. ************************************************************************* 10) Uninstalling 1. For Windows: Use add/remove programs in the control panel to remove the provider. The uninstall may leave behind files that were created by the provider after the install is complete. This may include trace files, repository files, and other administrative files. These files will need to be manually deleted to completely remove the provider. 2. For UNIX: cd to the directory where you unpacked the original archive file. There is a deinstall script which should be executed as follows: ./deinstall. The deinstall process may leave behind files that were not part of the original install. These files will need to be deleted manually. ************************************************************************** 11) Notes Currently, if the provider is installed in a WSI CIMOM, the CIMOM server must be restarted for it to recognize the new provider. ************************************************************************* 12) Known Issues - If the provider was installed into a pre-existing JWS CIMOM, there is no way currently to do a clean uninstall. Although provider files will be removed cleanly using the deinstall script, the MOF's compiled into the CIMOM will remain. Uninstalling and reinstalling the JWS CIMOM would be required to clean out the CIMOM's repository. - If the Engenio proprietary managment software (SANtricity) is used in conjunction with the provider, there can be issues when invoking the ExposePath method. In some situations, the provider can not work with hosts and/or host groups created by SANtricity management software. The workaround is to delete hosts/host groups created by SANtricity and recreate them using an SMI based management client. - The provider sometimes encounters error situations which keep it from being able to generate subsystem level performance statistics. There is currently no workaround for this problem. - The JWS CIMOM and Engenio provider do not consistently use the same IP address on a dual/multi ported server. Disable or unplug all but one Ethernet connection to use the CIMOM/Provider on a dual ported server. ************************************************************************* 13) End User License Agreement License Agreement for Storage Management Software READ THIS LICENSE CAREFULLY BEFORE USING THE SOFTWARE EMBEDDED IN THE HARDWARE OR ANY OTHER SOFTWARE ORDERED OR OTHERWISE ACQUIRED FROM SSI FOR USE WITH THE SYSTEM. YOUR USE OF THE SOFTWARE CONSTITUTES YOUR ASSENT TO THE TERMS OF THIS AGREEMENT. SIMILARLY, THE ACTIVATION OF A SOFTWARE KEY TO ENABLE ADDITIONAL FUNCTIONALITY CONTAINED IN THE HARDWARE CONSTITUTES YOUR ASSENT TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT WANT TO ENTER INTO THIS LICENSE AGREEMENT, DO NOT REQUEST A SOFTWARE KEY, AND RETURN THE UNOPENED PACKAGE TO YOUR ENGENIO INFORMATION TECHNOLOGIES ("ENGENIO") SALES REPRESENTATIVE FOR CREDIT. This Agreement governs your use of the SMI Provider storage management software, any additional functionality embedded in the firmware which You may cause to be activated and any additional software or firmware you order or otherwise acquire from ENGENIO for use with the System (together the "Software"). These terms and conditions apply unless You entered into a separate written license agreement with ENGENIO for the use of the Software, in which case that separate agreement shall govern. License. Subject to the terms of this Agreement, ENGENIO grants You a limited and non-exclusive license to use and operate the Software on an ENGENIO storage system (the "System"). Nothing in this Agreement provides You with any right in the Software except for the license granted herein. You may make a reasonable number of copies of the Software for backup and archival purposes only. Except as expressly permitted under this Agreement or by applicable law without the possibility of contractual waiver, You may not copy, merge, transmit, modify, reverse engineer, decompile or disassemble the Software, or sublicense, rent, lease, assign or otherwise transfer the Software to anyone. Termination. Your license shall automatically terminate when You are no longer in possession of the System or You violate the terms of this Agreement. Upon termination of the license You shall immediately stop using the Software, and purge and destroy any and all copies of the Software with notice to ENGENIO of such destruction or return the copies to ENGENIO. Limited Warranty and Disclaimer. Any pre-production versions of the Software (e.g. alpha or beta versions) distributed to You are delivered "as-is," without any express or implied warranties ENGENIO warrants for 90 days following delivery of the Software to You that: (i) the media on which the Software is contained will be free of defects in material and workmanship; and (ii) the Software will perform in accordance with published specifications for the Software. THE FOREGOING WARRANTY IS IN LIEU OF ALL OTHER WARRANTIES WITH RESPECT TO THE SOFTWARE. ENGENIO DISCLAIMS, AND YOU HEREBY WAIVE, ANY AND ALL OTHER EXPRESS OR IMPLIED WARRANTIES INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE OR MERCHANTABILITY AND THE STATUTORY WARRANTY OF NON-INFRINGEMENT. ENGENIO DOES NOT WARRANT THAT THE SOFTWARE WILL OPERATE UNINTERRUPTED OR ERROR-FREE, OR THAT USE OF THE SOFTWARE WILL MEET YOUR REQUIREMENTS. In case of breach of the warranty, ENGENIO at its option will: (i) replace the defective Software; (ii) repair or correct the defective Software so they will operate in substantial conformance with published specifications for the Software; or (iii) refund the license fee paid by You for the defective Software. Any claim based on this warranty must be submitted in writing within the applicable warranty period. The warranty will apply only if: (a) the Software has been properly installed and used at all times and in accordance with the instructions for use; (b) no modification, alteration or addition has been made to the Software by persons other than ENGENIO or ENGENIO's authorized representative; and (c) Customer has not requested modifications, alterations or additions to the Software that cause it to deviate from the documentation. The foregoing states Your sole and exclusive remedy and ENGENIO's sole and exclusive liability with respect to any breach of the warranty. Limitation of Liability. Regardless of the basis for any claim, whether in contract, tort, or otherwise, ENGENIO will be liable to You only for the amount of Your actual direct loss or damage relating to the Software, up to the license fee paid by You for the Software. Irrespective of the basis of the claim, ENGENIO and its resellers, licensors and developers of the Software will not be liable for any special, indirect, punitive, incidental or consequential damages of any kind (including, without limitation lost profits, loss of or damage to Your records or data, or the cost of cover), nor will ENGENIO be liable for any third party claims unless specifically provided in this Agreement. Neither party may bring a legal action under this Agreement more than two years after the cause of action arose. Export Policy. You agree that You shall not directly or indirectly, export, re-export or transship the Software in violation of any applicable export control laws or regulations promulgated and administered by the governments of the countries claiming jurisdiction over the parties or transactions. You acknowledge that U.S. laws, regulations and requirements regulate the export of U.S. origin products/technology and prohibit use, sale or re-export if You know, or have reason to know, that such products/technology are for use in connection with the design, development, production, stockpiling or use of nuclear, chemical or biological weapons or missiles. Restricted Rights. With respect to any acquisition of the Software by or for any unit or agency of the U.S. Government, the Software shall be classified as "commercial computer software" as defined in the applicable provisions of the Federal Acquisition Regulation ("FAR") 12.212 dated October 1988. The Software was developed entirely at private expense and no part of it was first produced in the performance of a U.S. Government Contract. If the Software is supplied for use by the Department of Defense ("DOD"), it is delivered subject to the terms of this Agreement and in accordance with DOD FAR Supplement ("DFARS") 227.7202-1(a). If the Software is supplied for use by a Federal agency other than DOD, it is restricted computer software delivered subject to the terms of this Agreement and (i) FAR 12.212(a); (ii) FAR 52.227-19; or (iii) FAR 52.227-14 (ALT III), as applicable. High Risk Activities. THE SOFTWARE AND HARDWARE PRODUCTS ARE NOT DESIGNED, MANUFACTURED, OR INTENDED FOR USE OR RESALE AS ON-LINE CONTROL PRODUCTS REQUIRING FAIL-SAFE CONTROLS, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATIONS SYSTEMS, AIR TRAFFIC CONTROL, LIFE SUPPORT, OR WEAPONS SYSTEMS WHERE FAILURE OF THE SOFTWARE AND HARDWARE PRODUCTS COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY AND/OR SUBSTANTIAL PROPERTY DAMAGE. YOU AGREE NOT TO USE THE SOFTWARE AND HARDWARE PRODUCTS FOR ANY SUCH PURPOSES, AND LSI, ENGENIO AND THEIR AFFILIATES EXPRESSLY DISCLAIM AND ARE RELEASED FROM ANY RESPONSIBILITY OR LIABILITY FOR ANY AND ALL DAMAGES THAT MAY BE INCURRED DUE TO THE USE OF THE SOFTWARE AND HARDWARE PRODUCTS IN SUCH APPLICATIONS. Governing Law. This Agreement is governed by the laws of the State of California. Additional Notice: This software makes use of the Sun WBEM Services CIM Object Manager, source code for which is available under the terms of the Sun Industry Standards Source License Version 1.2.