Professional Documents
Culture Documents
SolutionsEnabler With SMIS
SolutionsEnabler With SMIS
Version 3.2.2
Release Notes
P/N 300-005-588 Rev A01 August 24, 2007
These release notes contain supplemental information about EMC SMI-S Provider version 3.2.2 for SMI-S version 1.2. These release notes are organized as follows:
Product description.............................................................................. 2 New features and changes .................................................................. 3 Fixed problems ..................................................................................... 7 Environment and system requirements ............................................ 8 Known problems and limitations .................................................... 11 Technical notes .................................................................................... 13 Documentation ................................................................................... 15 Software media, organization, and files.......................................... 15 Installation ........................................................................................... 16 Troubleshooting and getting help .................................................... 35
Product description
Product description
EMC SMI-S Provider V3.2.2 supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management. This initiative has developed a standard management interface that has culminated in a comprehensive specification (SMI-Specification or SMI-S). The SMI-S defines the open storage management interface that enables the interoperability of multiple vendors storage management technologies. These technologies are used to monitor and control storage resources in multivendor SAN topologies. The SMI strives to ensure consistent data and eliminate inconsistencies between management tools by providing a unified interface to the many storage objects that must be managed in a storage environment. This enables application developers to focus on a single, standard interface for the development of management tools. The EMC SMI-S Provider has been paired with the Pegasus CIM Server to provide an SMI-compliant interface for EMC Symmetrix and CLARiiON arrays. These release notes identify new EMC SMI-S Provider V3.2.2 enhancements and any known functionality restrictions and performance issues that may exist with the current version of this product and your specific storage environment. Certain functionality restrictions in previous versions of EMC SMI-S Provider have also been corrected in this release. More recent versions of EMC SMI-S Provider may be available, refer to the EMC Powerlink website for updates:
http://Powerlink.EMC.com
SMI-S Provider: Support for Solutions Enabler ............................... 3 Stand-alone install kit .......................................................................... 3 Change to interop namespace............................................................. 4 Supported profiles ................................................................................ 4 Supported packages ............................................................................. 4 Supported subprofiles.......................................................................... 4
SMI-S Provider: Support for Solutions Enabler Solutions Enabler customers that choose to upgrade their environments to EMC SMI-S Provider V3.2.2 must uninstall their existing version of Solutions Enabler prior to the installation. The SMI-S Provider V3.2.2 installation is bundled with the required Solutions Enabler V6.4.2 libraries that have some additional functionality supported in SMI-S Provider V3.2.2. Stand-alone install kit Beginning with V3.0, the SMI-S Provider has been delivered as a stand-alone installation kit. Previously, the EMC SMI-S Provider was provided within the EMC Solutions Enabler installation kit, which required the user to select numerous optional parameters during the Solutions Enabler installation script to install the provider.
As a stand-alone product, the process has been streamlined so that the EMC SMI-S Provider can be installed with fewer installation screens. The compatible version of EMC Solutions Enabler is automatically installed, if not already present. For more details on installing the EMC SMI-S Provider, refer to Installation on page 16.
Note: Solutions Enabler provides the interface between the Storage Management Initiative (SMI) and the Symmetrix and CLARiiON storage arrays. As such, the Solutions Enabler components required for SMI-S Provider operations have been included as part of the EMC SMI-S Provider installation for those that may not already have the proper version of Solutions Enabler installed.
Change to interop namespace The interop namespace for the EMC SMI-S Provider has changed from root/PG_Interop to interop. Supported profiles The EMC SMI-S Provider V3.2.2 supports the following profiles:
Array Server
Supported packages SMI-S version 1.1 introduced a new component called Packages. Packages are collections of classes and associations that are used in multiple profiles or subprofiles. Rather than repeat the material in each of the Profile models, the information is packaged and referenced in the appropriate Profile and Subprofile models. The EMC SMI-S Provider supports the following Packages:
Supported subprofiles Table 1 lists the supported subprofiles and the version of the SMI-S that supports it:
SMI-S supported subprofiles Access Points a Location Software Job Control Cluster b Multiple Computer System Disk Drive b Disk Drive Lite LUN Mapping and Masking b Masking and Mapping Pool Manipulation Capabilities and Settings b LUN Creation b Block Server Performance Extent Mapping b Extent Composition FC Initiator Ports FC Target Ports iSCSI Target Ports SPI Target Ports c Indication Copy Services d Volume Composition e Block Storage Views e
Table 1
SMI-S supported subprofiles Storage Server Asymmetry e Health Physical Package Block Services
a. This subprofile is only supported for CLARiiON storage arrays. b. The following subprofiles have been deprecated in SMI-S V1.0.3 and replaced with new subprofiles or packages. While these subprofiles are still available in the SMI-S V1.1, it is recommended that you use the new subprofiles or packages described here. The following list identifies the deprecated V1.0.3 subprofiles to the new V1.1 subprofiles packages: Cluster --> Multiple Computer System Disk Drive --> Disk Drive Lite LUN Mapping and Masking --> Masking and Mapping Pool Manipulation Capabilities and Settings --> Block Services package LUN Creation --> Block Services package Extent Mapping --> Extent Composition c. This subprofile is supported only for Symmetrix storage arrays. d. This subprofile is considered experimental for SMI-S V1.1 and SMI-S 1.2 and will change in future releases. As a result, backward compatibility cannot be guaranteed with the next release. Please contact EMC for permission to use this subprofile. e. This subprofile is considered experimental for SMI-S V1.2 and will change in future releases. As a result, backward compatibility cannot be guaranteed with the next release. Please contact EMC for permission to use this subprofile.
Fixed problems
Fixed problems
A complete list of issues that have been fixed in SMI-S V3.2.2 and Solutions Enabler (and other EMC product releases) can be viewed, searched, and parsed online by using the EMC E-Lab Issue Tracker tool available from the EMC Powerlink website.
Note: EMC E-Lab Issue Tracker is the main source for details about all open and fixed SMI-S Provider issues. It is regularly updated to contain the most current information regarding all versions of the SMI-S Provider. Details from E-Lab Issue Tracker can be viewed on screen, exported to Microsoft Excel, and printed for your convenience.
EMC SMI-S Provider support for SMI-S Supported schemas and specifications Distributed Management Task Force Common Information Model (DMTF CIM) Schema V2.14 Storage Management Initiative Specification (SMI-S) V1.0.3, V1.1.0, V1.2.0 (preliminary) OpenPegasus V2.6.0 a
a. This is included as part of the EMC SMI-S Provider installation.
EMC hardware support for SMI-S Supported Symmetrix arrays (supported with EMC EnginuityTM 5x67 or later) Symmetrix DMXseries (DMX-3, DMX-2, DMX-1) Symmetrix 8000 Series Supported CLARiiON arrays (supported with EMC Navisphere Release 19, 22, 24, 26) CX3 Series, CX Series, and AX Series
Host operating system support Supported operating systema RHEL 3.0, RHEL 4.0 SLES9 SP3 Solaris 8, 9, 10 Microsoft Windows 2000 SP4 Microsoft Windows Server 2003
a. The SMI-S Provider is supported only on 32-bit platforms.
CLARiiON-specific requirements
Table 5 lists additional software that must be installed to manage CLARiiON arrays using the SMI-S Provider V3.2.2.
Table 5
CLARiiON-specific requirements Requirements CLARiiON Navisphere Release 19, 22, 24, or 26 EMC Solutions Enabler V6.4.2 a
a. Solutions Enabler V6.4.2 provides the interface between the Storage Management Interface (SMI) and the Symmetrix and CLARiiON storage arrays. As such, the Solutions Enabler components required for SMI-S Provider operations have been included as part of the EMC SMI-S Provider installation.
Symmetrix-specific requirements
Table 6 lists additional Enginuity requirements that must be installed to manage Symmetrix arrays using the SMI-S Provider V3.2.2.
Table 6
Symmetrix-specific requirements Requirements Enginuity version 5x67 or higher EMC Solutions Enabler V6.4.2 a
a. Solutions Enabler V6.4.2 provides the interface between the Storage Management Interface (SMI) and the Symmetrix and CLARiiON storage arrays. As such, the Solutions Enabler components required for SMI-S Provider operations have been included as part of the EMC SMI-S Provider installation.
Note: When using the SMI-S Provider to manage Symmetrix arrays, it is recommended that three or more gatekeepers be present for use by the provider.
10
11
Shared CIMOM restriction The CIMOM installed with the EMC SMI-S Provider does not support or allow any third-party SMI-S providers. Solutions Enabler Access Control limitation If Solutions Enabler Access Control is enabled on the Symmetrix array, then the host on which the SMI-S Provider is running must have sufficient privileges to perform the necessary operations. Network port contentions By default, EMC SMI-S Provider listens on network ports 5988 (for http) and 5989 (for https). If these ports are in use by some other process (such as WMIProvider), the EMC SMI-S Provider will not start. Examine the EMC SMI Provider log file EMCProvider-<date>.log (in the symapi\log directory) for messages indicating something like a socket busy, port in use, or bind failed. When this occurs, you can either move the other process to a different network port, or specify different port values for the EMC SMI-S Provider by changing the httpPort and httpsPort parameters of the cimserver_planned.conf file (located in the symcli directory) and restarting the provider. During installation, the scripts attempt to determine if the default ports, 5988 and 5989, are in use. If they are in use at install time, the installation will attempt to use other ports until free ports are found. Once a usable port value is found, the script will update the cimserver_planned.conf file with the ports that will be used after installation.
12
Technical notes
Technical notes
This section provides technical notes for advanced configuration of EMC SMI-S Provider V3.2.2.
CLARiiON arrays Supply additional LUNs to add to a Snap pool to increase the pool's capacity. You cannot specify the new size. Symmetrix arrays Supply the new size for the Snap pool. You can not supply additional LUNs to add to a Snap pool.
13
Technical notes
Any device that is marked Private. Currently, the following devices are marked Private: Vault Devices (Symmetrix) Symmetrix File System (SFS) Devices (Symmetrix) SAVE Devices (Symmetrix) SNAP/Mirror Cache Devices (CLARiiON)
14
Documentation
Documentation
These release notes provide the latest information for the EMC SMI-S Provider V3.2.2. Release notes as well as all EMC documentation can be found on the EMC Powerlink website:
http://Powerlink.EMC.com
EMC SMI-S Provider Pegasus CIM Server EMC Solutions Enabler V6.4.2 runtime libraries
15
Installation
Installation
The EMC SMI-S Provider installation and setup process installes the EMC SMI-S Provider, Pegasus CIM Server, and EMC Solutions Enabler V6.4.2 runtime libraries.
The EMC SMI-S Provider installation: Windows: Installing the EMC SMI-S Provider on page 17 Solaris: Installing the EMC SMI-S Provider on page 20 Linux: Installing the EMC SMI-S Provider on page 22
Note: If you have a previous version of the SMI-S Provider or Solutions Enabler installed, you must uninstall it before attempting this installation. It is recommended that you back up your data before uninstalling. The SMI-S Provider V3.2.2 installation is bundled with the required Solutions Enabler V6.4.2 libraries.
Post installation: Post-installation tasks on page 24 Starting and stopping the Pegasus CIM Server on page 25 Controlling the EMC SMI-S Provider at runtime on page 27 Optional SSL configuration on page 29 Optional SLP configuration on page 33
Uninstall: Windows: Uninstalling SMI-S Provider on page 19 Solaris: Uninstalling SMI-S Provider on page 21 Linux: Uninstalling SMI-S Provider on page 23
Note: Management of EMC Symmetrix and CLARiiON arrays using the EMC SMI-S Provider does not require license keys.
16
Installation
1. Download the EMC SMI-S Provider V3.2.2 software from the Powerlink website or insert the EMC SMI-S Provider V3.2.2 CD. 2. Save all files and exit all Windows applications. To install the EMC SMI-S Provider V3.2.2 software on a Windows platforms, launch the self-extracting executable, se6420-WINDOWS-x86-SMI.msi. 3. WinZip unzips the installation files and starts InstallShield. The EMC Solutions Enabler With SMI dialog box opens to the welcome page. 4. Click Next to begin the installation. The Destination Folder dialog box opens and prompts you to select an install directory for Solutions Enabler and EMC SMI-S Provider. It is recommended that you choose the default directory.
Figure 1
Destination Folder
17
Installation
5. Click Next to continue. The Ready to Install the Program dialog box opens.
Figure 2
6. Click Install to begin installing files to your selected folder. This may take several minutes. The Installation Wizard Completed dialog box open. 7. Click Finish to complete the setup. 8. When complete, update your environment variable for path to include the Solutions Enabler installation directory, which by default is C:\Program Files\EMC\SYMCLI\bin, in order to run the command line utilities from any directory.
18
Installation
19
Installation
The installation program will begin copying the files. When complete, the installation program will automatically start the storapid daemon and the cimserver, which may take a few minutes. When complete, the installation program will return the following confirmation message, which lists EMC Solutions Enabler with SMI-S Provider in the HAS BEEN INSTALLED list:
#----------------------------------------------------------------------------# The following HAS BEEN INSTALLED in /opt/emc via the pkgadd utility. #----------------------------------------------------------------------------ITEM PRODUCT VERSION 01 EMC Solutions Enabler V6.4.2.0 SMI KIT #-----------------------------------------------------------------------------
20
Installation
The installation program will begin removing the files. When complete, the installation program will return the following confirmation message:
Solutions Enabler sucessfully uninstalled from your system.
21
Installation
The installation program will begin copying the files. When complete, the installation program will automatically start the storapid daemon and the cimserver, which may take a few minutes. When complete, the installation program will return the following confirmation message, which lists EMC Solutions Enabler with SMI-S Provider in the HAS BEEN INSTALLED list:
#----------------------------------------------------------------------------# The following HAS BEEN INSTALLED in /opt/emc via the rpm utility. #----------------------------------------------------------------------------ITEM PRODUCT VERSION 01 EMC Solutions Enabler V6.4.2.0 SMI KIT #-----------------------------------------------------------------------------
22
Installation
The installation program will begin removing the files. When complete, the installation program will return the following confirmation message:
Solutions Enabler sucessfully uninstalled from your system.
23
Installation
Post-installation tasks
There are post-installation tasks for both CLARiiON and Symmetrix arrays:
Note: The EMC SMI-S Provider will discover all storage arrays available in your environment. However, if you choose to limit discovery of specific arrays using SystemRegistrationService, or other means as directed by EMC Customer Service, any established relationships, such as an RDF link, between discovered and avoided arrays will not be manageable by the SMI-S Provider. To prevent this situation, make sure that all arrays, including remotely connected storage arrays, are fully discoverable.
Symmetrix array: Post-installation tasks When using the SMI-S Provider to manage Symmetrix arrays, it is recommended that three or more gatekeepers be present for use by the provider. CLARiiON array: Post-installation tasks Managing CLARiiON arrays through the SMI-S Provider requires some additional post-installation setup. You must complete the following tasks to manage your CLARiiON arrays in any environment: CLARiiON discovery and authorization connectivity in Solutions Enabler For the SMI-S provider to automatically discover locally attached CLARiiON storage arrays, authorization information must be provided to properly communicate to the CLARiiON storage processors. A locally attached storage array is one in which at least one CLARiiON LUN is visible to the host on which the provider is running. If the provider is setup to automatically discover locally attached CLARiiON storage arrays with the emcprovider.conf setting OslProv/com.emc.se.osls.osl.StorApi.database.discover (see Table 7 on page 27), or the client appilcation is making use of the EMCDiscoverSystem method of the EMC_SystemRegistrationService, then the authorization information for each CLARiiON storage processor must be provided as shown next.
24
Installation
Use the SYMCLI symcfg command, as shown in the following syntax example:
symcfg authorization add -host HostName -username UserName -password PassWord
For example, to add authorization for CLARiiON storage processor A with IP address 172.23.193.86, username clariion and password clarpass, use the following command:
symcfg authorization add -host 172.23.193.86 -username clariion -password clarpass
You must list the information for Storage Processor A first, then Storage Processor B.
Note: If the client application is using the EMCDiscoverSystem method of the EMC_SystemRegistrationService then it is recommend that the emcprovider.conf setting OslProv/com.emc.se.osls.osl.StorApi.database.discover be set to false.
Note: You must add authorization for each CLARiiON storage processor. If you fail to complete this task prior to running the SMI-S Provider, you may receive an error message stating that you do not have NaviCLI installed. NaviCLI is not required for Navisphere Release 19 or later, however, you must supply the authorization connectivity information as described previously.
If all CLARiiON arrays are being discovered out-of-band, then it is typical to have the emcprovider.conf configuration file setting OslProv/com.emc.se.osls.osl.StorApi.database.discover set to false. See the EMC SMI-S Provider Programmers Guide for further information on discovering CLARiiON storage arrays out-of-band.
25
Installation
Windows
On Windows, the CIM Server runs as a service and can be controlled through the Windows Services control panel. The service will not restart at boot unless you modify its startup property in the Services control panel to start automatically. The service name is EMC_SMI_Provider and it displays as Pegasus CIM Object Manager - EMC_SMI_Provider in the Services control panel. The cimserver.exe file in the Solutions Enabler storbin directory implements the CIM Server. Use the following command to stop the CIM Server:
cimserver -stop EMC_SMI_Provider
26
Installation
UNIX
On UNIX, the CIM Server runs as a daemon in the background. Use the following command from the SYMCLI directory to stop the CIM Server:
./storbin/cimserver -s
Use the following command from the SYMCLI directory to restart the CIM Server:
./storbin/cimserver
EMC SMI-S Provider properties (1 of 2) = <OptValue | DefaultValue> [filename] | <empty> Description Specifies the Solution Enabler database filename. If empty, will use the default database file. Specifies whether a one time discover is done, upon a cimserver start, prior to processing the first request received by the CIM Server. Note when the CIM Server is started the EMC SMI-S Provider is not loaded until it is requested from the CIM Server.
OslProv/com.emc.se.osls.osl.StorApi.database.discover
true | false
27
Installation
Table 7
EMC SMI-S Provider properties (2 of 2) = <OptValue | DefaultValue> FATAL, ERROR, WARNING, NOTICE, INFO Description Severity can be set to one of the following. Each setting will cause messages of the set severity and more severe to be appended to the log. The list below shows most severe at the top, and the least severe at the bottom. FATAL Events leading to shutdown of the system ERROR Internal or client error conditions WARNING Potential errors NOTICE Very important information (default if not present) INFO Informational, non-error messages Specifies the log directory. If removed or empty, the EMC SMI-S Provider log file will go to the default location, which is the log directory of the EMC Solutions Enabler. The filename will take the format:
EMCProvider-yyyymmdd.log
OslProv/com.emc.se.ofl.log.Control.directory
[directory] | /var/symapi/log/
28
Installation
29
Installation
CIM Server configuration file On startup, the CIM Server accesses the cimserver_planned.conf file to obtain connectivity values. The following properties can be configured:
Table 8
CIM configuration file (1 of 2) = <OptValue | DefaultValue> TRUE | FALSE Description When set to TRUE, the CIM server will log active commands and configuration settings. Used in conjunction with enableRemotePrivilegedUserAccess parameter. When set to TRUE, a valid CIM username and password is required to perform any operation. CIM users can be created with the cimuser CLI utility. If set to TRUE, the CIM server will start on the non-secure port. If set to FALSE, no non-secure ports are available. If set to TRUE, the CIM server will start on the secure port using SSL. If set to FALSE, no secure ports are available. Refer to the enableAuthentication parameter. Identifies the non-secure port on which the server should start. Identifies the secure port on which the server should start. Specifies the location of the Pegasus log files. Specifies the location of the cimserver password file. When set to TRUE, the cimserver will register and activate the SLP Server Agent daemon.
Parameter enableAuditLog
enableAuthentication
TRUE | FALSE
enableHttpConnection
FALSE | TRUE
enableHttpsConnection
FALSE | TRUE
enableRemotePrivilegedUserAccess TRUE | FALSE httpPort httpsPort logdir passwordFilePath slp [valid port number] | 5988 [valid port number] | 5989 [any_valid_path] |
var/symapi/log a
[any_valid_path] |
var/symapi/config/cimserver.passwd a
TRUE | FALSE
30
Installation
Table 8
Description Identifies the path to the server.pem file. If not set, the private key is expected to be in the same file as the server certificate.
a. The path shown is a UNIX-specific default installation path. Your actual install path may differ.
31
Installation
The cimuser command is an optional utility to add, modify, remove, and list CIM users.
Note: It is only necessary to create CIM Users if the enableAuthentication and enableRemotePriviledgedUserAccess parameters are set to true in the cimserver_planned.conf file. In addition, only a valid system user that can log into the system can be added.
The cimuser command enables the management of CIM users. If the password is not specified at the command line, the user will be prompted for it. The following syntax applies:
cimuser cimuser cimuser cimuser -a -u username [ -w password ] -m -u username [ -w password ][ -n newpassword] -r -u username -l
Indicates a specific user name that must already exist on the system.
-w password
32
Installation
5. Verify that your SLP Client User Agent (which is not provided with Solutions Enabler) can query for a URL and attributes, and that the Server Agent responds. The following is an example of a command-line client User Agent request and Server Agent response. It does not reflect an exact syntax of requests and responses:
slptool findsrvs service:wbem service:wbem:https://172.23.193.44:5989,56706 service:wbem:http://172.23.193.44:5988,56706 slptool findattrs service:wbem:http://172.23.193.44:5988 (template-url-syntax=http://172.23.193.44:5988), (service-id=PG:7F9BF3F0-CF1A-4E4C-B8EE-C0FEA0BD4A23), (service-hi-name=Pegasus), (service-hi-description=Pegasus C IM Server Version 2.6.0), (template-type=wbem), (template-version=1.0), (template-d escription=This template describes the attributes used for advertising Pegasus CIM Servers.), (InteropSchemaNamespace=interop), (FunctionalProfilesSupported=Basic Read, Basic Write,Schema Manipulation, Instance Manipulation,Association Traversa l, Qualifier Declaration,Indications), (MultipleOperationsSupported=FALSE), (AuthenticationMechanismsSupported=Basic),
EMC SMI-S Provider Version 3.2.2 Release Notes
33
Installation
34
Technical support For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.
35
Legal notices
This section provides legal attribution for acknowledging open-source and third-party software copyright and licensing requirements. OpenSSL copyright information
EMC SMI-S Provider uses OpenSSL. Copyright (c) 1998-2001 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. 2. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/) 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, contact openssl-core@openssl.org. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. Redistributions of any form whatsoever must retain the following acknowledgment: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/) THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
3.
5.
6.
36
OpenPegasus
EMC SMI-S Provider uses software from OpenPegasus. License information can be found at: http://www.openpegasus.org The text of the license follows:The Pegasus code uses the MIT open source license. This license was used to provide a minimum encumbrance on the code and allow maximum usage. This license is as follows: Copyright (c) 2000, 2001, 2002 BMC Software; Hewlett-Packard Development Company, L. P.; IBM Corp.; The Open Group; Tivoli Systems.Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L. P.; IBM Corp.; EMC Corporation; The Open Group.Copyright (c) 2004 BMC Software; Hewlett-Packard Development Company, L. P.;IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group.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 CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
37
38
For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals: Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software.
End of Legal Notices for Open-Source & Third-Party Copyright and Licensing
____________
39
Copyright 2007 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.
40