Release Notes: This release contains development-level support of SMI-S 1.1: It is not intended or claimed that this release has been certified by SNIA or the CTP with regards to SMI-S 1.1 support. ************************************************************************* 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) Adding a device for management 6) Tracing 7) Authentication 8) Uninstalling 9) Notes 10) Known Issues 11) End User License Agreement ************************************************************************* 1) Supported Features The 1.1 provider supports both the 1.1(Development-level) and the 1.02(certified) SMI-S, distinguished by namespace. The 1.02 is supported in the /root/lsissi namespace, the 1.1 in the /root/lsissi11. This provider is compliant with SMI-S 1.0.2/1.0.3. The 1.0.2 namespace is certified with SNIA CTP 1.0.2. No support for SMI-S 1.1 in a product environment is claimed nor should it be assumed. 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 Pool Manipulation, Capabilities and Settings LUN Creation Device Credentials LUN Mapping and Masking Backend Ports The following profiles and subprofiles (indented) are supported in the SMI-S 1.1 Provider: Server Array Access Points Disk Drive Lite Extent Composition Location Software Copy Services Job Control Device Credentials Masking and Mapping Multiple Computer System FC Target Ports FC Initiator Ports Block Server Performance Please refer to the document SMI-S Provider Functional Specification for details about the SMI-S provider specific implementation of these profiles. ************************************************************************* 2) Supported Firmware Versions The following firmware versions are supported in this release: 5.30, 5.33, 5.34, 5.40, 5.42, 6.10, 6.12 & 6.14 (SANtricity versions 8.3, 8.33, 8.34, 8.40, 8.42, 9.10, 9.12 & 9.14 respectively) ************************************************************************* 3) Upgrading from a previous Version of the Provider This Provider is a stand-alone replacement for any down-level SMI-S Provider. To correctly install the current version without an installer, all files from the down-level Provider must be moved/removed from the host computer. To do this properly follow these steps: 1. Stop the following services/daemons only if they are running Windows NT/2000/2003 UNIX-based Service Location Protocol slpd SMI-S Provider cimomd 2. Move the down-level files to a new location (this could be done using a compressed file, like .zip or .tgz, or simply renaming the parent directory). Deleting the previous version is not recommended. 3. Follow the directions in Section 4 to install the new SMI-S Provider. ************************************************************************* 4) Installing the SMI-S Provider *Note (for users of the .ZIP archive): Mininum JRE level is 1.4.1. If a JAVA_HOME variable is set on your installation machine, please ensure that the JRE it points to is at least 1.4.1. If installing from an installer package (setup_.exe AIX_Installer.tar, Solaris_Installer.tar, or Linux_Installer.tar) please refer to the InstallationInstructions.txt document for instructions. If working with a zip: 1. Unpack the release zipfile. 2. Set JAVA_HOME to the base directory of your java installation. (All that's really required is that the command "java" be in the directory $JAVA_HOME/bin.) 3. Starting the Provider To start the CIMOM with SLP support, go to release/SMI_SProvider/bin on windows, and run runservice.bat 4. To start the CIM client (cimworkshop) go to release/wbemservices/bin and on Unix, run sh cimworkshop.sh or, on Windows, run cimworkshop.bat A username and password are required; however, cimworkshop will accept any values for these strings: Note: The current interop namespace is "\root\". Namespace defines a scope within which object keys must be unique. ************************************************************************* 5) Adding a Device for management: a. 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. b. 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. That's it. You should now be able to use cimworkshop (or any CIM client) to view and modify the the array. ************************************************************************* 6) Tracing NOTE: Any changes to the tracing level will require a resart of the provider to take effect. The SMI-S provider's trace facility uses a properties file, providerTraceLog.properties, to control the trace. This file needs to be edited to enable/disable tracing. The file is located in SMI_SProvider\bin off of the installation directory. To enable tracing of the CIMOM - Provider Interface, locate the following line in the properties file: "#log4j.logger.cimprovider.OurCIMObject=WARN, Console" and change "WARN" to "DEBUG". Also, remove the "#" from the beginning of the line. To disable tracing, change "DEBUG" back to "WARN". To completely disable tracing (debug and error) put the "#" back in front of the line. To enable tracing of the Provider - SYMbol Interface, edit the file called symbolSDKTraceLog.properties and edit the file to locate the following line in the properties file: "#log4j.logger.symbolsdk.StorageArrayObject=WARN, Console" and change "WARN" to "DEBUG". To disable tracing, change "DEBUG" back to "WARN". The trace log information will be written out to the console and to a log file. The file’s name is Provider.log. If running as a service on windows, the log files can be found either in C:\WINNT\System32 or C:\WINDOWS\System32. In all other cases, this log file can be found in the SMI_SProvider\bin\ folder within the install directory. Please note that the trace log is implemented as a circular buffer that spans four files. Subsequent file names will have a number appended at the end of '.log'. ************************************************************************* 7) 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, that the Provider is installed into, must take care of authentication. In order to turn authentication on, you much 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. ************************************************************************* 8) Uninstalling If a zip was used, you may simply delete all the folders extracted from the zip after stopping the CIMOM. If an installer was used: If the provider and CIMOM were installed together, the entire installation including the CIMOM will be removed. Currently, if the Provider is installed into an existing CIMOM, only the Provider related files are removed from the system. The MOF's are not unregistered. To perform uninstallation, simply execute the ./deinstall script from the location the installer tar file was expanded. ************************************************************************* 9) Notes Currently, if the provider is installed in a WSI CIMOM, the CIMOM server must be restarted for it to recognize the new provider. ************************************************************************* 10) Known Issues If the provider was installed into a JWS CIMOM, there is no way currently to do a clean uninstall. Although provider files will be removed cleanly using the uninstall script / executable, 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. Some JWS Bugs that are affecting the Provider: 937982 Namespaces are replaced with interop n/s in associations Although the provider supports multiple namespaces (separate Interop and Array namespaces) this defect in the CIMOM will cause a problem traversing the ElementConformsToProfile association from the RegisteredProfile in the interop namespace to the StorageSystem in the array namespace. 529081 CIMOM returns duplicated objects This defect causes duplicate objects to be returned if roles are not specified in the references/referenceNames calls (can also occurr in the associators / associatorNames as noted in the sourceforge bug) 1017056 JWS CIMOM does not translate references correctly. 1109600 inParams on invokeMethods are lost When an extrinsic method is invoked, all parameters following a reference parameter are lost by the CIMOM when using the JWS client 1108616 CIMObjectPath in CIMInstance is invalid When the CIMOM passed CIMInstances to the provider, the CIMObjectPath is not fully formed 1102467 When a subscription is created, CIMOM does not cross namespace SSL Support is not yet available in JWS. A workaround has been added but should be considered temporary and experimental. ************************************************************************* 11) End User License Agreement License Agreement for Storage Management Software READ THIS LICENSE CAREFULLY BEFORE USING THE SOFTWARE EMBEDDED IN THE HARDWARE OR A NY 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 LSI LOGIC STORAGE SYSTEMS, INC. ("SSI") SALES REPRESENTATIVE FOR CREDIT. This Agreement governs your use of the SMI-S 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 SSI for use with the System (together the "Software"). These terms and conditions apply unless You entered into a separate written license agreement with SSI for the use of the Software, in which case that separate agreement shall govern. License. Subject to the terms of this Agreement, SSI grants You a limited and non-exclusive license to use and operate the Software on an SSI 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 SSI of such destruction or return the copies to SSI. 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 SSI 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. SSI 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. SSI 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, SSI 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 SSI or SSI'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 SSI'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, SSI 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, SSI 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 SSI 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, SSI AND THEIR AFFILIATES EXPRESSLY DISCLAIM AND ARE RELEASED FROM ANY RESPONSIBILITY OR LIABILITY