StorMan V1.3 Provisioning and managing virtualized …manuals.ts.fujitsu.com/file/7249/storman13.pdf · 7.1.1 Common CLI aspects ... With the scope of uniform integration of storage

StorMan V1.3 June 2007

Administrator & User Guide

StorMan V1.3 Provisioning and managing virtualized storage resources

Contents 1 Introduction .................................................................................................................5 1.1 Functional overview ......................................................................................................5 1.2 Functional structure.......................................................................................................7 1.2.1 Storage provisioning .....................................................................................................7 1.2.2 Storage information and monitoring ..............................................................................7 1.3 Logical structure for storage provisioning .....................................................................7 1.3.1 Virtualization layer.........................................................................................................7 1.3.2 Storage layer.................................................................................................................8 1.4 Architecture ...................................................................................................................9 1.4.1 General .........................................................................................................................9 1.4.2 Authorization ...............................................................................................................10 1.4.3 Communication und security.......................................................................................10 1.4.4 Repository ...................................................................................................................10 1.4.5 Error handling..............................................................................................................10 1.4.6 High availability ...........................................................................................................11

2 Installation .................................................................................................................12 2.1 System requirements ..................................................................................................12 2.1.1 Hardware.....................................................................................................................12 2.1.1.1 Server .....................................................................................................................12 2.1.1.2 Storage...................................................................................................................12 2.2 Software ......................................................................................................................13 2.2.1 General requirements .................................................................................................13 2.2.2 Additional software requirements................................................................................13 2.2.2.1 General...................................................................................................................13 2.2.2.2 SMI-S Provider .......................................................................................................13 2.2.2.3 StorMan Administration GUI...................................................................................14 2.2.3 Installation and start of EMC SMI-S Provider..............................................................14 2.2.3.1 Download................................................................................................................14 2.2.3.2 Special issues for FibreCAT CX / CLARiiON CX Systems.....................................15 2.2.3.3 Special issues for Symmetrix Systems...................................................................15 2.3 Installing the StorMan Server on Linux .......................................................................17 2.3.1 Configuration file .........................................................................................................17 2.3.2 Starting and stopping the StorMan service .................................................................19

StorMan V1.3 June 2007 2

2.4 Installing the StorMan Server on Windows .................................................................19 2.4.1 Port configuration and other parameters (smserver.ini)..............................................22 2.4.2 Starting and stopping the StorMan service .................................................................22 2.5 Installing the StorMan GUI ..........................................................................................23 2.5.1 Copying web documents (Apache Server)..................................................................23 2.5.2 Setting JNLP MIME type .............................................................................................23 2.6 Deinstallation...............................................................................................................24 2.6.1 Deinstallation of StorMan on a Linux Server...............................................................24 2.6.2 Deinstallation of StorMan on a Windows Server.........................................................24 2.6.3 Deinstalling the GUI ....................................................................................................24

3 The graphical user interface – StorMan GUI ..........................................................25 3.1 Starting the GUI ..........................................................................................................25 3.1.1 Starting Java Web Start repeatedly ............................................................................26 3.1.2 Troubleshooting ..........................................................................................................27 3.2 Elements of StorMan GUI ...........................................................................................28 3.2.1 Hierarchical browser ...................................................................................................29 3.2.2 Object tables ...............................................................................................................30 3.2.3 Buttons and the message field....................................................................................31

4 Setting up StorMan configurations .........................................................................32 4.1 Setting up StorMan configurations using the CLI........................................................32 4.1.1 Set or deactivate the Information and Monitoring Function.........................................32 4.1.2 Add host ......................................................................................................................32 4.1.3 Specify one or more CIM Servers / API Servers.........................................................33 4.1.4 Discover a storage system..........................................................................................33 4.1.5 Create StorMan storage pools ....................................................................................33 4.1.6 Using existing storage volumes ..................................................................................34 4.1.7 Creating new storage volumes....................................................................................34 4.1.8 Attach a logical device to a host..................................................................................34 4.1.9 View the attachments to a device ...............................................................................34 4.1.10 Detach a logical device from a host ............................................................................34 4.1.11 Release a storage volume ..........................................................................................35 4.1.12 Discover changes to a storage array ..........................................................................35 4.2 Setting up StorMan configurations using the GUI .......................................................35 4.2.1 Add a new CIM Host ...................................................................................................35 4.2.2 Remove Host ..............................................................................................................37 4.2.3 Add a new storage pool ..............................................................................................37 4.2.4 Delete a storage pool ..................................................................................................39 4.2.5 Rename a storage pool...............................................................................................40 4.2.6 Moving devices into storage pools ..............................................................................40 4.3 Diagnostic aids............................................................................................................42 4.3.1 StorMan.......................................................................................................................42 4.3.2 SMI-S Provider............................................................................................................42

5 Special properties of storage systems ...................................................................43 5.1 Special properties of EMC storage systems ...............................................................43 5.1.1 Dynamic creation of storage volumes / logical devices...............................................43 5.1.2 LUN masking in FibreCAT CX / CLARiiON CX systems.............................................44 5.1.3 LUN masking in Symmetrix systems...........................................................................46 5.1.4 Host storage connections (SPCs) ...............................................................................47 5.2 Special properties of Network Appliance storage systems .........................................47 5.2.1 Dynamic LUN creation ................................................................................................47 5.2.2 LUN mapping and LUN masking.................................................................................48

6 GUI: Administration and Provisioning tasks..........................................................49 6.1 Add a new host ...........................................................................................................49 6.2 Remove a host ............................................................................................................51 6.3 Add a new WWPN ......................................................................................................51 6.4 Remove a WWPN.......................................................................................................52


6.5 Attach a device............................................................................................................52 6.6 Detach a device ..........................................................................................................54

7 StorMan for programmers – CLI description..........................................................56 7.1 General .......................................................................................................................56 7.1.1 Common CLI aspects..................................................................................................56 7.1.2 Common enumeration values .....................................................................................57 7.1.3 Common supported value ranges ...............................................................................59 7.2 storcfg .........................................................................................................................60 7.2.1 storcfg host..................................................................................................................60 7.2.1.1 storcfg host –add....................................................................................................61 7.2.1.2 storcfg host –mod...................................................................................................61 7.2.1.3 storcfg host –rem....................................................................................................63 7.2.1.4 storcfg host –show..................................................................................................64 7.2.2 storcfg cimom..............................................................................................................66 7.2.2.1 storcfg cimom –add ................................................................................................66 7.2.2.2 storcfg cimom –mod ...............................................................................................68 7.2.2.3 storcfg cimom –rem................................................................................................69 7.2.2.4 storcfg cimom –discover.........................................................................................70 7.2.2.5 storcfg cimom –show..............................................................................................71 7.2.3 storcfg system.............................................................................................................73 7.2.3.1 storcfg system –rem ...............................................................................................73 7.2.3.2 storcfg system –discover ........................................................................................74 7.2.3.3 storcfg system –show.............................................................................................74 7.2.4 storcfg pool..................................................................................................................76 7.2.4.1 storcfg pool –add....................................................................................................76 7.2.4.2 storcfg pool –mod...................................................................................................77 7.2.4.3 storcfg pool –rem....................................................................................................78 7.2.4.4 storcfg pool –show..................................................................................................79 7.2.5 storcfg volume.............................................................................................................81 7.2.5.1 storcfg volume –add ...............................................................................................81 7.2.5.2 storcfg volume –mod ..............................................................................................83 7.2.5.3 storcfg volume –rem...............................................................................................84 7.2.5.4 storcfg volume –show.............................................................................................85 7.3 storcreate ....................................................................................................................89 7.4 storattach ....................................................................................................................91 7.5 stordetach ...................................................................................................................93 7.6 stordelete ....................................................................................................................95 7.7 stormandb ...................................................................................................................96 7.8 storcheck.....................................................................................................................97 7.9 storparam....................................................................................................................98 7.10 storinfo ......................................................................................................................100 7.11 storemc .....................................................................................................................101 7.11.1 storemc –add ............................................................................................................101 7.11.2 storemc –rem ............................................................................................................103

8 StorMan for programmers – StorMan Client interface for information and monitoring ........................................................................................................105

9 Appendix..................................................................................................................106 9.1 Fujitsu Siemens Computers: Software License Agreement for End Users..............106 9.2 OpenSource licenses ................................................................................................109 9.2.1 OpenPegasus ...........................................................................................................109

Glossary ..................................................................................................................................110

Index ..................................................................................................................................112

Copyright © Fujitsu Siemens Computers GmbH 2007.

EMC2® and Symmetrix® are trademarks or registered trademarks of EMC2 Corporation, Hopkinton/MA (USA).

NetApp® is a trademark or registered trademark of Network Appliance, Inc., Sunnyvale (USA)

All rights reserved. Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

See the Appendix for additional information on licenses.

Feel free to send us your comments on this manual by e-mail: [email protected]

Created by: cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de

mailto:[email protected]

www.cognitas.de


1 Introduction

1.1 Functional overview

The main scope of StorMan is the virtualization and dynamic management of storage resources and their dynamic assignment to servers in the following cases:

• Storage provisioning tasks

Example: An application requires additional storage capacity according to a specific policy that should be assigned quickly and automatically.

• Repurposing scenarios

Example: An application is migrated to a new server requiring access to the same storage resources as before.

• Dynamic Data Center (DDC) scenarios

Example: An application expands dynamically to an additional server requiring access to the same storage resources as before.

• Disaster recovery scenarios

Example: An application is subject to dynamic failover after failure of a server requiring access to the same storage resources.

• Storage consolidation scenarios

Example: The storage resources of an application are consolidated.

• Storage information and monitoring scenarios

Example: With the scope of uniform integration of storage arrays into server management software (e.g. ServerView).

A uniform management service for automatic storage provisioning, information and monitoring is provided by StorMan. The storage provisioning can be stateful or stateless.

StorMan provides a common virtualization layer offering:

• Common and stable interfaces for

− ‘standalone’ usage

− integration in DDC solutions (e.g. FlexFrame for Oracle, FlexFrame for SAP) or projects with components such as ASNB, ASCC, etc

− integration with server management software such as ServerView, etc

• Management options for

− administrators who use the StorMan GUI directly

− automation with prescheduled or event-triggered scripts based on StorMan’s CLIs

• A stable generic API for integration tasks providing

− detailed information about the logical and physical attributes of a storage array

− tooling for monitoring the status of storage arrays


• Encapsulation of the backend complexity of

− storage-vendor-specific interfaces (Fujitsu Siemens Computers, EMC, NetworkAppliance) and

− storage connectivity types: SAN (supported today), iSCSI and further types (in future) on the backend

The following figure provides an overview of the architectural layers:

Figure 1: Overview

The base technology of StorMan is a standard called SMI-S (Storage Management Initiative Specification), which is defined and supported by the SNIA (Storage Networking Industry Association). SMI-S is a widespread standard in the storage world. However, for specific functions or for vendors who do not yet support SMI-S, there is the option of integrating vendor-specific APIs.

The functionality of StorMan covers the high-priority functions needed for the area of storage provisioning, namely:

• managing and administrating storage resources (storage volumes and pools)

• LUN creation and deletion

• LUN masking (managing the hosts access to volumes)

Additionally, StorMan provides the functionality required for information and for monitoring storage arrays, namely:

• discovery

• information about logical and physical components

• status monitoring


1.2 Functional structure

From the structural point of view, StorMan consists of two functional components:

• Storage provisioning

• Storage information and monitoring

These two components can be used separated or combined depending on the needs of the configuration.

1.2.1 Storage provisioning

The storage provisioning functionality of StorMan covers the high-priority functions required for storage virtualization and dynamic storage provisioning, namely:

• managing and administrating storage resources (storage volumes and pools) in a virtualization layer

• LUN creation and deletion

• LUN masking (managing the hosts’ access to volumes)

These features are provided by StorMan’s GUI (see the chapter “The graphical user interface – StorMan GUI”) and as CLI for automation support in scripts (see the chapter “StorMan for programmers – CLI description”).

StorMan V1.3 supports the Storage Provisioning features for storage systems from Fujitsu-Siemens Computers (FibreCAT CX), EMC Corporation (Symmetrix and CLARiiON CX) and Network Appliances Inc (NetApp® FAS systems).

1.2.2 Storage information and monitoring

The storage information and monitoring features supported are those required for information and for monitoring storage arrays mainly for integration purposes, namely:

• discovery

• information about logical and physical components

• monitoring of status

These features are implemented by StorMan’s Client Interface (API) and provide XML-based output information as described in chapter 8. Currently this interface is only used by other products of Fujitsu Siemens Computers (in particular ServerView). It is not released for general use.

StorMan V1.3 supports the Information and Monitoring features for storage systems from Fujitsu Siemens Computers (FibreCAT SX, FibreCAT CX) and EMC Corporation (CLARiiON CX).

1.3 Logical structure for storage provisioning

The main requirement for storage provisioning is met by an abstract and narrow interface with a simple set of functions that can be invoked on behalf of the StorMan Client. The StorMan Client has to specify an object of storage provisioning, e.g. the storage resource (identified by its storID) and a server that needs to be provisioned with the storage resource.

1.3.1 Virtualization layer

The virtualization layer is a core part of StorMan. It administers the storage resource descriptions (configuration data). These descriptions are specific for each storage product. Therefore virtualization means providing a single interface for different kinds of descriptions.


Repository

A repository is required for consistent administration of the mapped resource descriptions. StorMan uses its own internal repository implemented as an internal database. While the database software is embedded into StorMan, its data can optionally be kept internally, or externally in SAN or NAS environment by means of configuration.

Configuration data

Administration is divided into 2 layers:

• Configuration layer

This layer referred to as the storage pool layer below handles storage configuration. The administrator of StorMan defines the storage pools as the storage resources available for provisioning. In its simplest form, each storage pool identified by its unique pool ID describes one storage system of the entire storage configuration known by StorMan (e.g. a Symmetrix array identified by its serial number and a subset of volumes configured in this array). Each storage pool description contains general storage pool attributes and storage system- and volume-related attributes. The StorMan Server administrates the storage pool layer.

• Dynamic layer

The existing storage assignments represented by a unique storage identifier (storID) can be managed using this layer. The current attribute and status of the provisioning functions are held in the dynamic layer for each storage identifier. Attributes of the storage identifier include the LUN of the storage volume, its current size, currently connected servers, its harboring storage pool, etc. The storage identifier is created the first time storage is assigned and optionally deleted after de-assignment. An option of configuring a storage identifier statically is also provided for provisioning cases where a predefined storage (LUN) is required and was already configured.

This data is kept in the StorMan repository with the same options for administration as described for the configuration layer.

In provisioning tasks that contain new assignments of storage such as creating a volume, the caller has to specify a storage resource and/or attributes of the storage that should be provided for the request. This description of the requested storage attributes is called storage policy below. Storage policy descriptions have a specific, extendable format containing information such as a specific storage pool.

An administration interface (GUI) to configure and manage the Virtualization Layer’s configuration data offers basic management functions (e.g. adding, removing, modifying and displaying storage pools and storage identifiers). Storage provisioning functions are also available on the GUI.

Initialization of the configuration data when setting up a StorMan configuration in an existing storage environment is supported. Storage pools can be configured based on the results of a discovery function. Existing assignments between server and storage are represented by internally generated storIDs in the configuration data.

Beside these mapping and administration tasks, the virtualization layer provides the necessary parameters for the storage layer.

1.3.2 Storage layer

The storage layer incorporates the implementation of the SMI-S client for the provisioning functions.

According to the SMI-S approach, the provisioning functions are transformed into the corresponding SMI-S calls. Distribution to the specific products is performed on the object manager level. According to the registered object managers of the vendor-specific SMI-S Providers, StorMan’s object manager client will call the corresponding vendor-specific SMI-S Providers.

Propietary API functions of the vendors may be incorporated for special functions or if support is not yet provided by SMI-S.


Standardization: SMI-S

SMI-S as SNIA’s evolving standard is considered increasingly important in the domain of storage management. The main functions for storage provisioning (e.g. device creation, device masking) used by StorMan are defined in SMI-S V1.1 and implemented by storage vendors (such as EMC corporation).

Storage–vendor-specific interfaces (APIs)

StorMan is ready to incorporate storage-vendor-specific APIs in its storage layer. In V1.3 StorMan uses this branch for storage systems of Network Appliance Inc. to support these systems by using ManageONTAP API.

1.4 Architecture

1.4.1 General

The following chapter covers the main lines of StorMan’s architecture. The core part, i.e. the StorMan Server incorporating the virtualization layer and the storage specific layer is implemented as a portable server.

Figure 2: Architecture

The provisioning functions supported on the StorMan Client side are provided as CLIs (Command language interfaces). An API that provides the information and monitoring functions is available for internal purpose.

The StorMan Server is installed and run as a service. It may be placed on any server of the configuration depending on the caller’s needs and storage application requirements.


The StorMan Client part resides on the same server as the calling application (e.g. ASNB, etc.) and provides its caller with a stub presenting the provisioning functions implemented by the StorMan Server. The calling application is not aware of the communication between the StorMan Client and StorMan Server. Therefore the StorMan Client and StorMan Server can be installed on the same server or on different servers of the same LAN.

1.4.2 Authorization

The StorMan Server runs on its hosting server as a service with administrator rights. Protection for this user identification can be set depending on the server and the platform.

The administration GUI connects to the server that hosts the StorMan Server by specifying the configurable port number (default value).

1.4.3 Communication und security

The core communication with the StorMan Server consists in sending the functions invoked on the StorMan Client to the StorMan Server and in receiving the respective results and return codes. Using the CLI functions the communication handling is encapsulated in the CLI call, i.e. a session is established for each call.

The communication between StorMan Client and StorMan Server as well as between StorMan GUI and StorMan Server is based on a Socket implementation.

The GUI provides administration and configuration functionalities, such as managing of storage pools and StorIDs on the StorMan Server as well as management functions for storage provisioning. The GUI applications can be called from any workstation within the LAN.

1.4.4 Repository

Configuration data is contained in an internally consistent repository. The GUI or the CLI can be used for the administration function of storage pools and storage identifiers in the repository. The repository is located in the following directory:

• %PROGRAMFILES%\Fujitsu Siemens\StorMan (Microsoft Windows)

• /var/opt/SMAWstor/StorMan/Repository (Linux).

There is no need for the user to view or modify the repository file directly, but it may be necessary to change its location, e.g. when a high availability solution is configured (see section 1.4.6).

1.4.5 Error handling

Provisioning tasks are critical for the calling application. A stable reaction and detailed return information are guaranteed for the caller of StorMan for functions terminated with errors or for which the response from called storage system is missing.

An internal logging function that logs all activities of the StorMan Server in a specific log file is available. The log file is primarily used for diagnostic purposes for StorMan.


1.4.6 High availability

High availability has to be provided by all components of a storage configuration: StorMan Server, StorMan Client and SMI-S Providers.

StorMan Server

The StorMan Server is designed as a single server and can therefore be considered as a single point of failure for Storage Management.

To provide high availability, a second redundant StorMan Server can be set up to take over requests from the StorMan Clients. These redundant StorMan Servers are optionally integrated with clustering software such as PRIMECLUSTER or ASCC.

To support integration into clustering software, StorMan provides functions to start and stop the StorMan Server and a check function to check the status of the StorMan Server.

The most critical part in a takeover scenario from a StorMan Server to a standby StorMan Server is the consistency of data in the internal repository. This can be achieved by:

1. Keeping the repository data of the internal database and the configuration data of both StorMan Servers externally in the SAN or NAS accessible from both servers.

2. Ensuring that the StorMan Servers have read and write access to the database files on both hosts, e.g. by using a user group that is identically on both hosts.

3. Assuring that the 2 StorMan Servers are not running concurrently.

4. Supporting a ‘rolling upgrade’ of the 2 StorMan Servers from one release n to release n+1 in this configuration.

StorMan Client

The StorMan Client is not critical from the HA perspective as it can easily access an alternative StorMan Server in the LAN.

SMI-S Provider

SMI-S Providers are implemented as proxy or embedded providers.

For SMI-S Providers running in proxy mode (e.g. SMI-S Provider of EMC Corporation), high availability can be achieved by configuring a redundant provider and integration with clustering software such as PRIMECLUSTER or ASCC.

In high-availability configurations where the SMI-S Provider resides on the same host(s) as the StorMan Server, it should be part of the same cluster (PRIMECLUSTER or ASCC).

Multiple SMI-S Providers can be configured in StorMan to manage the same storage system. The StorMan Server will automatically select an available SMI-S Provider to control the storage system, thus assuring a consistent view of the configuration when changing the SMI-S Provider usage.

Embedded SMI-S Providers (e.g. for FibreCAT SX arrays) run directly on the storage array and are therefore available as long as the storage array.

Storage-vendor-specific interfaces (APIs)

The storage-vendor-specific interfaces supported (ManageONTAP of Network Appliance in StorMan V1.3) are bundled with the StorMan Server. High availability is therefore assured by HA of the StorMan Server. The communication is performed directly with the Data ONTAP® Software on the Network Appliance filer. We consequently have the same conditions as we have in the case of an embedded SMI-S Providers.


2 Installation

2.1 System requirements

2.1.1 Hardware

2.1.1.1 Server

StorMan V1.3 supports all current PRIMERGY servers as StorMan Clients and StorMan Servers.

i

• For EMC Symmetrix, a server with FC connectivity to the managed storage arrays is required to host the CIM Server (SMI-S Provider).

• StorMan can manage any server connected to external storage via FC, as the server and its HBAs are part of the StorMan configuration and the storage array is supported.

2.1.1.2 Storage

EMC Storage

StorMan V1.3 supports the provisioning functions for the full range of SAN connected storage of EMC Corporation, namely the Symmetrix, Symmetrix DMX and CLARiiON CX products as supported by SMI-S Provider V3.2.1 and Solutions Enabler V6.4.1.

i

• For further details of supported Symmetrix and CLARiiON CX models, please refer to the EMC Support Matrix (ESM) available at https://powerlink.emc.com/

• CLARiiON CX models are also provided by Fujitsu Siemens Computers and named FibreCAT CX

StorMan V1.3 supports the information and monitoring functions required primarily for integration with ServerView for the current FibreCAT CX / CLARiiON CX models as supported by SMI-S Provider V3.2.1 and Solutions Enabler V6.4.1.

StorMan V1.3 does not support the information and monitoring functions required e.g. for integration with ServerView for Symmetrix and Symmetrix DMX storage of EMC corporation.

Network Appliance Storage

StorMan supports the provisioning functions for the full range of SAN connected storage of NetApp® FAS (FAS2xx, FAS9xx, FAS30xx) as supported by ManageONTAP API V1.6 of Network Appliance Inc.

StorMan V1.3 does not support the information and monitoring functions required e.g. for integration with ServerView for storage of Network Appliance Inc.

FibreCAT SX arrays

StorMan V1.3 does not support the provisioning functions for FibreCAT SX storage.

StorMan V1.3 supports the information and monitoring functions required primarily for integration with ServerView for the current FibreCAT SX models SX60 and SX80. This support is based on the embedded SMI-S Provider available as of microcode version J110P05.

https://powerlink.emc.com/


2.2 Software

2.2.1 General requirements

The platforms supported are:

• Microsoft Windows Server 2003 SP2

• Microsoft Windows XP SP2

• SuSe Linux Enterprise Server (SLES) 10

• SuSe Linux Enterprise Server (SLES) 9

• Red Hat Enterprise Linux (RHEL) ES 4

• Red Hat Enterprise Linux (RHEL) ES 3

2.2.2 Additional software requirements

The following software packages are necessary

2.2.2.1 General

The following Pegasus libraries are required and used by StorMan. They are also available as downloads from the Internet:

• Pegasus Common library V2.5.2 (http://www.openpegasus.org)

• Pegasus Client library V2.5.2 (http://www.openpegasus.org)

i

Fujitsu Siemens Computers does not cover any maintenance issues for these libraries.

2.2.2.2 SMI-S Provider

EMC Storage

• SMI-S Provider V3.2.1 for SMI-S V1.1 from EMC Corporation.

As SMI-S Provider V3.2.1 is based on EMC Solutions Enabler V6.4.1, it contains the compatible EMC Solutions Enabler Version 6.4.1

For further details of supported Symmetrix and CLARiiON CX / FibreCAT CX models, please refer to the EMC Support Matrix (ESM) and to EMC SMI-S Provider Version 3.2.1 Release Notes available at https://powerlink.emc.com/.

The following operating systems are supported (as of EMC Support Matrix):

− Microsoft Windows 2000 SP4

− Microsoft Windows Server 2003

− Red Hat Enterprise Linux (RHEL) ES 3.0 and 4.0

− SuSe Linux Enterprise Server (SLES) 9 SP3

http://www.openpegasus.org/




• The EMC SMI-S Provider is not part of the StorMan package. The EMC SMI-S Provider is available

− as a download from https://powerlink.emc.com/ for CLARiiON CX Systems,

− from http://extranet.fujitsu-siemens.com/service/storage/online/fibrecat/storagedownload.html for FibreCAT CX systems accessible for FibreCAT CX certified engineers of Fujitsu Siemens Computers.

• An FC connection for the CIM Server (SMI-S Provider) is required to support EMC Symmetrix storage arrays and is no longer required for FibreCAT CX and CLARiiON storage arrays.

Network Appliance Storage

As for StorMan V1.3 the support of NetApp® FAS storage from Network Appliance Inc. is based on MangeONTAP API; no SMI-S Provider is required.

FibreCAT SX Storage

As the SMI-S Provider for FibreCAT SX Storage is ‘embedded’, it is delivered by default with the storage array as part of the microcode and enabled by default. This support is available as of version J110.

2.2.2.3 StorMan Administration GUI

The following libraries are required in addition:

JRE V1.5.0.4 or higher (http://java.sun.com).

It is recommended that you update these libraries.

2.2.3 Installation and start of EMC SMI-S Provider

2.2.3.1 Download

• For CLARiiON CX systems download the EMC SMI-S Provider and the Release Notes from http://powerlink.emc.com

i

A Powerlink-userID is needed.

− Provider-Kit: Home -> Support -> Downloads & Patches -> Downloads S-Z

− Release Notes: Home -> Support -> Documentation Library -> Software S -> SMI-S Provider

• For FibreCAT CX systems download the EMC SMI-S Provider from the Fujitsu Siemens Computers extranet (http://extranet.fujitsu-siemens.com/service/storage/online/fibrecat/storagedownload.html).

i

A certified engineer (CE) userID is needed for FibreCAT CX systems.

Installation instructions for Windows and Linux are contained in the EMC Release Notes and not described in full here. Kits are currently available for Microsoft Windows and Linux (Red Hat RHEL ES3 and SuSe SLES 9).


http://extranet.fujitsu-siemens.com/service/storage/online/fibrecat/storagedownload.html

http://www.java.com/de/download

http://powerlink.emc.com/

http://extranet.fujitsu-siemens.com/service/storage/online/fibrecat/storagedownload.html


2.2.3.2 Special issues for FibreCAT CX / CLARiiON CX Systems

If you are working with FibreCAT CX / CLARiiON CX Systems, check or carry out the following on the server on which the EMC SMI-S Provider is installed:

• Flare Code Release 19 or higher including AccessLogix is installed on the FibreCAT CX / CLARiiON CX System.

• If a FibreCAT CX / CLARiiON CX without a FibreChannel connection to the host on which the EMC SMI-S Provider ist running shall be administrated by StorMan, follow the instructions in section 7.11 storemc.

• If a FibreCAT CX / CLARiiON CX with a FibreChannel connection to the host on which the EMC SMI-S Provider is running shall be administrated by StorMan, check the following:

− At least one volume of the system must be visible to the CIM Server via FibreChannel.

i

See also the chapter "Discovery of CLARiiON Arrays" in the "EMC SMI-S Provider Release Notes".

− Specify a userID and a password for each of the two storage processors (SP) of the FibreCAT CX / CLARiiON CX that has to be managed by the SMI-S Provider:

symcfg authorization add -host <sp-netname> -username <UserName> -password <PassWord>

This must be a valid CLARiiON userID with administrator role or management role that was defined during the FibreCAT CX / CLARiiON CX setup or in the Navisphere GUI. Check your entries using the symcfg auth list command.

• The feature Device (LUN) Masking delivered by "EMC AccessLogix" has to be active on the FibreCAT CX / CLARiiON CX.

• The SMI-S Provider can be prevented from discovering single FibreCAT CX / CLARiiON CX Systems with the claravoid file. This file is contained in the directory

%PROGRAMFILES%\EMC\SYMAPI\config (Microsoft Windows) /var/symapi/config (Unix/Linux)

and includes one line per FibreCAT CX / CLARiiON CX with the serial number of the FibreCAT CX / CLARiiON CX.

2.2.3.3 Special issues for Symmetrix Systems

• The SMI-S Provider Host has to be connected to the Symmetrix by FibreChannel.

• The feature Device (LUN) Masking delivered by "EMC VolumeLogix" has to be enabled on the Symmetrix and on every FC director port on which the application hosts are connected (VCM-enabled).

The following parameter should be defined in the ...\SYMCLI\storbin\EMCProvider.conf file only if an SMI-S Provider with version < 3.2 is used:

OslProv/com.emc.se.osls.osl.LunMask.loginhistory.enable = true

With SMI-S Provider version as of 3.2 this parameter should be set to false (default value). See section 5.1.3 for details. You are recommended to create an additional file EMCProvider_user.conf in the same directory for non default parameters, because this file will not be overwritten during the installation of an SMI-S Provider.

• A VCM device has to be configured in the Symmetrix system and the VCM database has to be initialized. Please refer to the "EMC Solutions Enabler Symmetrix Device Masking CLI Product Guide", available at http://powerlink.emc.com, for information on how to do this.

• The VCM device should be mapped to the SMI-S Provider Host to permit the SMI-S Provider to use it as a gatekeeper device before performing any device masking actions.

http://powerlink.emc.com/


• After the VCM device is created and mapped, execute symcfg discover and sympd list on the SMI-S Provider host to make sure that the VCM device is visible to the host.

To avoid conflicts with gatekeeper devices, you are recommended to set the following parameter in the .../symapi/config/options file:

SYMAPI_WAIT_ON_LOCKED_GK = ENABLE

• If the VCM device is visible to the host, StorMan via SMI-S Provider can attach additional gatekeeper devices itself. You are strongly recommended to attach at least 3 additional gatekeeper devices, because a "storapi” demon and a "storevnt" demon are also running on the SMI-S Provider host (see also the Release Notes for EMC SMI-S Provider). If only the VCM device is visible for the host (no additional gatekeepers), the SMI-S Provider may receive IO Errors because this device (used as a gatekeeper) is in use.

• Note: If additional gatekeeper devices are removed for the host later on, the SMI-S Provider has to perform a Symmetrix discovery again before it can continue working with the VCM device only (by calling storcfg cimom -discover).

• The SMI-S Provider can also be prevented from discovering single Symmetrix systems with the symavoid file. This file is contained in the directory

%PROGRAMFILES%\EMC\SYMAPI\config (Microsoft Windows) /var/symapi/config (Unix/Linux)

and includes one line per Symmetrix with the serial number of the Symmetrix.

Access to CIM-OM

If you want to restrict access to the CIM-OM, use the cimuser command as described in the EMC Release Notes. Before starting the SMI-S Provider, set the following parameter in the EMCProvider_user.conf file in the ...\SYMCLI\storbin\ directory.

OslProv/com.emc.se.osls.osl.StorApi.database.discover = false

This prevents the SMI-S Provider from synchronizing its database automatically after a restart. StorMan 1.3 directs the Provider to synchronize its database if necessary.

Start the Provider

After these items have been clarified, restart the SMI-S Provider.

• On Linux / Unix systems, perform the following steps:

− Stop the CIM Server:

/opt/emc/SYMCLI/V6.X.X/storbin/cimserver -s

− Start the CIM Server:

/opt/emc/SYMCLI/V6.X.X/storbin/cimserver –D /opt/emc/SYMCLI/V6.X.X

− Check the CIM Server / SMI-S Provider (optional):

/opt/emc/SYMCLI/V6.X.X/storbin/provider –l

If it is not running, a return code > 0 is delivered.

• On Windows Systems, this can be performed by:

− stopping the CIM Server:

\...\SYMCLI\storbin\cimserver -s

− starting the CIM Server:

\...\SYMCLI\storbin\cimserver -start EMC_SMI_Provider

− the CIM Server / SMI-S Provider can be checked using:

\...\SYMCLI\storbin\cimprovider –l


i

Fujitsu Siemens Computers provides no warranty for these tools. Refer to EMC’s latest Release Notes for details.

2.3 Installing the StorMan Server on Linux

You have to be logged in as root. Enter the following command to install StorMan:

rpm -i StorMan-<version>.rpm

i

• See the readme file for the correct version.

• Use -iv or -ivv for extended information.

• A StorMan userid is created during installation. This userid is normally called storman. Ithas the same password as root. Only if a userid storman already exists a user storman1 is created. If necessary, storman2, storman3 , etc. are created accordingly.

• If an earlier version of StorMan is already installed, it must be deinstalled first. Please refer to chapter 2.6 for information on deinstallation.

2.3.1 Configuration file

smserver.ini is the basic configuration file.

Most importantly, it defines the port number of the StorMan Server (StormanServerPort parameter). Note that StorMan uses one port with the number 4178 as the default. This port was assigned to StorMan by the Internet Assigned Numbers Authority (IANA). If necessary, you can edit the file to change the port number. All StorMan clients must specify the port number (4178 is used as default) to communicate with StorMan server.

smserver.ini is stored in the following directory: /var/opt/SMAWstor/StorMan/config.

# # ----- Storman ----- # # maximum level to trace # 0 trace severe errors only # 1 trace errors too # 2 trace even warnings # 3 trace information # 4 trace debug # 5 trace extended debug MaxTraceLevel = 4 # # trace communication if MaxTraceLevel = 5 # 0 trace off # 1 trace tcp/ip # 2 trace messages # 3 trace all DebugCom = 0 # # port for the storman server # default port: 4178 StormanServerPort = 4178 #


# # ----- CIM-Server ----- # CimTimeOut = 600 CreateTimeout = 0 # if Length of WWPNs should be more than 32 hex-digits, set the Parameter as shown below # WWPNLENGTH = 32 # # # ----- Sundry ----- # # refresh time for status in seconds # negative value: no refresh StatusRefreshTime = 60 # # targetOSType for create-lun if client has none specified # supported values: local, windows, linux, solaris # default: local DefaultTargetOSType = local

Some other parameters can be modified by editing smserver.ini or by using the storparam command as described in chapter 0: CimTimeOut Represents the timeout value in seconds for requests to the CIM-OM. A

request to the CIM Server is cancelled if there is no response. The default setting is 600 seconds.

CreateTimeout Timeout in seconds for dynamic volume creation (if a new volume is created during a storcreate request). The default setting is unlimited. The value is ignored if the timeout parameter is specified with the storcreate command, see section 7.3.

StatusRefreshTime Sets the time interval between two status refresh calls of the StorMan Server. This function is required to support the information and monitoring features only (e.g. for ServerView integration). The default value is 60 seconds. A negative value switches the refresh function off.

i

You are strongly recommended to switch off this function in configurations which do not use the information and monitoring features (ServerView integration)

DefaultTargetOSType

Target operating system type to be provisioned for dynamic volume creation (if a new volume is created during a storcreate request). This parameter is only but mandatory required and only supported for filers of Network Appliance Inc. The default setting is local, i.e. the operating system type of the server hosting the StorMan Server is used. The value is ignored if the -targetostype parameter is specified with the storcreate command, see section 7.3. Other possible values are ‘windows’, ‘linux’ or ‘solaris’.

i

• All entries in the configuration file are optimized for StorMan and care should be taken if they are changed. In particular, entries not mentioned here should not be changed.

• Files signed with *.fsc are default backup files.


2.3.2 Starting and stopping the StorMan service

The StorMan service is configured by installation being started automatically by the init.rd scripts. It can also be started manually as root.

Upon startup, storman reads its configuration file. The server is configured to listen on the default port 4178 (or any other user-defined port).

Once the server has started and performed some initialization activities, it will do the work of listening for and answering requests from clients.

To start or stop StorMan on Linux systems, enter:

/etc/init.d/storman start | stop

To check if StorMan is running, enter:

storcheck

This function is useful for high-availability configurations where applications are monitored by HA tools. For details about this command, please refer to the CLI description in section 7.8.

For high-availability configurations, starting and stopping the StorMan feature can be integrated into /rcinit script processing.

2.4 Installing the StorMan Server on Windows

i

If an earlier version of StorMan is already installed, it must be deinstalled first. Please refer to section 2.6 for information on deinstallation.

Perform the following steps to install StorMan:

• Log in with “administrator” rights.

• Execute

StorMan_Setup-<version>.exe

• Select the installation language and click OK:


• Click Next in the Installation Welcome window:

• Select I agree to these terms and conditions in the License Agreement window and click Next:


• Select your installation options. You have the choice of installing any combination of the Server, the Client or the GUI. Then click Next.

• Specify the installation folder and the StorMan Server port for StorMan communication if you need to change the default values. Afterwards click Install.

− Port number 4178 (default value) is a registered port at IANA which is reserved for StorMan. However, a different port number may be used, but it must be specified by StorMan Clients for each connection.

− If only the StorMan Client and / or the GUI have been selected for installation, only the installation folder is offered for optional specification.


The following screen shows that installation has been successful completed.

2.4.1 Port configuration and other parameters (smserver.ini)

Configuration settings for the StorMan Server are contained in the smserver.ini file. It is the basic configuration file and is located in the StorMan installation directory (%PROGRAMFILES%\Fujitsu Siemens\StorMan\config as the default) where you are able to change the StorMan port as well as other parameters.

Refer to section 2.3.1 for further details (the file is the same on Linux and Microsoft Windows.)

2.4.2 Starting and stopping the StorMan service

Upon startup, storman reads its configuration file. The server is configured to listen on the default port 4178 (or any other user-defined port).

It is configured to start automatically as a Windows service.

Once the server has started and performed some initialization activities, it will do the work of listening for and answering requests from client browsers.

To start or stop StorMan on Windows systems use the service manager.

To check if StorMan is running, check Windows services for “FSC StorMan Service” or enter

storcheck

in a DOS shell. This function is useful for high-availability configurations where applications are monitored by HA tools. For details about this command, please refer to the CLI description in section 7.8.


2.5 Installing the StorMan GUI

A virtual Java machine (JRE 1.5+) is required on the client side. If such a machine is not available, a new version can be downloaded from http://java.sun.com. The virtual Java machine is active once the browser has been restarted.

A Web Server must already be installed on the server.

Your document root will vary depending on how you have configured your web server.

• In case of Apache, the default document root is (example for Linux, Apache version 2.0+):

/usr/local/apache2/htdocs

• The path for IIS documents is c:\...\wwwroot (Windows only).

2.5.1 Copying web documents (Apache Server)

Perform the following steps to copy StorMan web documents into the document directory of your web server (document root) (example for Linux):

• Create a StorMan directory:

mkdir –p /usr/local/apache2/htdocs/StorMan

• Copy all files and subdirectories from /opt/SMAW/SMAWstor/StorMan/StorManGui into the StorMan directory under your web server document root:

cp –r /opt/SMAW/SMAWstor/StorMan/StorManGui/* /usr/local/apache2/htdocs/StorMan

• You may also use symbolic links and aliases to set the document root.

cd /usr/local/apache2/htdocs (for Apache) or cd /var/www/html (RedHat Web-Server) or other document root ln -s /opt/SMAW/SMAWstor/StorMan/StorManGui StorMan

To set the document root to point to other locations edit, the file

/etc/apache2/default-server.conf

as follows:

Alias StorMan "/opt/SMAW/SMAWstor/StorMan/StorManGu" <Directory> "/opt/SMAW/SMAWstor/StorMan/StorManGui"> Allow from all </Directory>

2.5.2 Setting JNLP MIME type

Before you can deploy an application with Java Web Start over the Web, you must ensure that the Web server you are using can handle JNLP files.

Configure the Web server so that files with the .jnlp extension are set to the application/x-java-jnlp-file MIME type. How you set the JNLP MIME type depends on the Web server you are using. For the Apache Web server on Linux, you simply add the line

application/x-java-jnlp-file JNLP

to the mime.types file. (/usr/local/apache2/conf/httpd.conf )

Restart Apache once you have added the above entry.

For other Web servers, check the respective documentation for instructions on setting MIME types.

http://www.java.com/


2.6 Deinstallation

2.6.1 Deinstallation of StorMan on a Linux Server

To uninstall StorMan enter:

rpm -e StorMan

There are backup files and configuration files which are not removed as part of the uninstall process:

• In the directory /var/opt/SMAWstor/StorMan/config/ the configuration file smserver.ini is not removed.

• In the directory /var/opt/SMAWstor/StorMan/backup/ all backup files are not removed to make sure that your data is not lost with the deinstallation.

• In the directory /var/opt/SMAWstor/repository/ the StorMan repository containing the complete configuration managed by StorMan is not removed.

If you are sure that you do not need these files any longer, delete the directory /var/opt/SMAWstor/StorMan/ manually.

2.6.2 Deinstallation of StorMan on a Windows Server

To uninstall StorMan, use the Windows software deinstallation utility.

There are backup files and configuration files which are not removed as part of the uninstall process (default paths below):

• In the directory %PROGRAMFILES%\Fujitsu Siemens\StorMan\config\ the configuration file smserver.ini is not removed.

• In the directory %PROGRAMFILES%\Fujitsu Siemens\StorMan\backup\ all backup files are not removed to make sure that your data is not lost with the deinstallation.

• In the directory %PROGRAMFILES%\Fujitsu Siemens\StorMan\repository\ the StorMan repository containing the complete configuration managed by StorMan is not removed.

If you are sure that you do not need these files any longer, delete the directory %PROGRAMFILES%\Fujitsu Siemens\StorMan\ manually.

2.6.3 Deinstalling the GUI

Remove the files or the symbolic link described in chapter 2.5.1 from the Web Server document root.


3 The graphical user interface – StorMan GUI This chapter describes how to start and work with the java-based graphical user interface (GUI).

3.1 Starting the GUI

The GUI can be started using Java Web Start:

• Start your browser.

• Enter the following URL:

http://<hostname>/StorMan/storman_en.html

i

If your URL is other than hostname and the standard http port, you need to change the code base in the stormanstart.jnlp file in the document root directory to reference the Web server. (e.g. if host name is host1, StorMan generates codebase=http://host1/StorMan)

The welcome screen appears on your monitor as soon as you start the GUI.

• Click here.

A splash screen is started first which shows that Java Web Start has been invoked:


When the download is complete, a window opens with a security warning:

• Now click Execute in order to start the GUI.

• In the next window enter or confirm a server name and a port number hosting the StorMan Server. The port number is defaulted with 4178.

Server Name is a host system running StorMan. The port name and server are saved in the file smConf.ini in the USERPROFILE directory.

Click OK to confirm the settings. Then the GUI main window appears next (see section 3.2).

Some of the advantages of using Java Web Start

• Java Web Start caches the application on the client's machine. This allows multiple reruns without setting up a remote connection to Server every time the application needs to be launched.

• It automatically updates the application files that are cached on the client's machine whenever the application is modified on the application server.

• It launches applications independently of a browser. Like normal applications, web-deployed applications can also be launched through desktop shortcuts.

Java Web Start itself offers two other options for starting the GUI:

• Via a browser

• Via a link that may have been created beforehand in Web Start

3.1.1 Starting Java Web Start repeatedly

• Open the control panel: Start menu -> Settings -> Control Panel

You should see the Java Coffee Cup logo icon in the Control Panel.

• Double-click the icon to open the Java Control Panel.


• In the Java Control Panel, click the Advanced tab.

• Click the + in front of shortcut creation.

This provides options for Java Web Start for creating shortcuts on the desktop. The options are:

− Always allow

− Always allow if hinted

− Prompt user

− Prompt user if hinted

− Never allow

Once you have created a link in the Start menu or on the desktop, you can use this shortcut in future to start the GUI.

If possible, Java Web Start always loads the application from the cache and at the same time performs a background check on the server for updates. If updates are present, the user is informed in a window and the update is loaded automatically at next the startup.

3.1.2 Troubleshooting

If Java Web Start cannot download an application from the server, the following window opens:


• Click Details for further information:

This error message can be understood as follows. During installation of StorMan GUI, the codebase URL is usually replaced by hostname (e.g. codebase="http://localhost/StorMan/").You have to replace the localhost parameter for the IP address or name of the local host in the stormanstart.jnlp file on the server side.

This file is in document root, e.g. (when you use Linux and Apache) in:

/usr/local/apache2/htdocs/StorMan/stormanstart.jnlp

Java Web Start will be able to function properly once you have performed this configuration.

3.2 Elements of StorMan GUI

The main window of the GUI appears after you have started the GUI and entered the server name and port number (see section 3.1.1).


The GUI provides two components, each in its own tab: Configure tab and Manage tab:

• Configure tab provides all functions for maintaining the storage configuration managed by StorMan:

− display, add and remove CIM Server and storage pools

− move devices into the storage pools

See section 4.2 for details of the Configure tab.

• The Manage tab is designed to provide functions to manage the storage configuration and its relations to servers. Currently it can be used to attach and detach storage devices to and from servers.

See chapter 6 for details of the Manage tab.

Both tabs comprise the following elements:

• The left area of the window contains a hierarchy browser and the right one object tables.

• Refresh and close buttons and a message field are at the bottom of the window.

3.2.1 Hierarchical browser

The hierarchical browser serves as a navigation aid which you can use to select CIM Servers, their storage systems, storage pools and devices. Depending on what you select, the object list will show the appropriate objects on the right-hand side of the window.

All storage systems currently not managed by any CIM Server are displayed in the <No CIM host> container.


3.2.2 Object tables

• The object table on the right-hand side of the window of the Configure tab comprises the following areas:

− The upper area comprises the property table of the selected object in the hierarchical browser.

− The object list appears below the property table. The type and number of objects displayed depend on the selections made in the hierarchical browser.

• The object table area of the Manage tab contains a sub-tab bar:

− The Connected Devices tab contains a property table of the selected host object in the hierarchical browser in its upper part and a list of the connected storage devices under it. Additionally, there is a Detach button in the lower part to detach the selected devices. When you detach a device you can also release it by activating the Release option. You can only execute actions if you have selected a device. The Release option is only checkable if the selected device does not have any connections to WWPNs other than the selected host.


− In the Attach tab you can choose a storage system and a Pool ID, and the devices are displayed in the table on the right-hand side. When you select a device, click Attach to attach the selected device to this host.

3.2.3 Buttons and the message field

There are two buttons and a message field in the lower part of the main window of the GUI:

• Close button to close the GUI.

• Refresh button to refresh the displayed data again.

• The message field displays messages or warnings.


4 Setting up StorMan configurations

4.1 Setting up StorMan configurations using the CLI

This section is a description based on the StorMan CLI. If you prefer to use the GUI for configuration, see section 4.2. For details about the CLI commands, refer to chapter 7.

4.1.1 Set or deactivate the Information and Monitoring Function

The Information and Monitoring function (required e.g. for ServerView integration) is activated by default. Execute the command

storparam –statusrefreshtime xx –save

to set your preferred time interval (default: 60 seconds) for the current and subsequent sessions as described in section 7.9.

To deactivate the Information and Monitoring function specify a negative value.

The time interval can also be modified by setting the StatusRefreshTime parameter in the configuration file smserver.ini. (see section 2.3.1).

i

To save resources in configurations not requiring the Information and Monitoring functions, you are strongly recommended to deactivate the function using this command

4.1.2 Add host

Add the hosts that are to be provided with storage units (LUNs) via StorMan using the storcfg host command, e.g.:

storcfg host -add -name myApplicationHost -ip ip-adr1,ipadr2,... -wwpn wwpn1,wwpn2,...

StorMan needs the Host WWPNs to attach / detach logical devices (LUNS) using the LUN masking functions.

WWPNs must be specified without the WWN(ode)N(ame) (210000C09F9568F8 or 21:00:00:C0:9F:95:68:F8).

The new entries can be checked using the storcfg host -show command.

A host can be removed from the StorMan repository using storcfg host -rem -name myApplicationHost.

Hosts can also be specified just by a WWPN (see section 7.2.1 for details). However, if the hosts have more than one HBA, you are recommended to specify a name and / or IP address for each host to provide a better general overview.

i

HBA WWPNs can be determined using the software for administering the FC switch or software supplied by the HBA vendor. They also should be printed on the HBA board.


4.1.3 Specify one or more CIM Servers / API Servers

Execute the command

storcfg cimom -add -name myCimHost

to specify the name of the host running the CIM Server. If you have specified a CIM User (see page 16), you have to specify it as part of this command as described in section 7.2.2.

For FibreCAT SX storage arrays, the CIM Server corresponds with the storage system because of the embedded SMI-S Provider.

For storage arrays from Network Appliance, the name of the NetApp FAS system is specified as API Server, because the used ManageONTAP functions reside on the filer. Execute the command

storcfg cimom -add -name myNetApp –interface netappapi

to specify the name of the NetApp FAS filer and the interface type as netappapi instead of a CIM Server.

4.1.4 Discover a storage system

Execute the command

storcfg cimom -discover -name myCimHost

This starts a discovery of the storage systems by the CIM Server and is needed by StorMan to find the relations between the CIM Server and the connected storage systems. This command can take some minutes depending on how many storage systems are connected and how large they are (from 15 to 60 seconds per storage system). The storage systems found by StorMan can be viewed using

storcfg system -show

If FibreCAT CX / CLARiiON CX systems without an FC connection are administrated, use the storemc command as described in chapter 7.11 to make the FibreCAT CX / CLARiiON CX visible for the SMI-S Provider before executing the storcfg cimom –discover command.

4.1.5 Create StorMan storage pools

If the storage volumes you want to provide for your servers are already created (bound) in the storage system, you have to ascertain the logical device numbers of the volumes to be used. If not, you can create new devices by using a StorMan storage pool which allows dynamic creation of new devices in the storage system. To ascertain appropriate devices that are already created, you can use the StorMan GUI or the storage system’s administration software or ask your storage system administrator. A storage pool is created using:

storcfg pool -add -poolid myPool -system sysname [-restype dynamic]

If you want to create new devices in the storage system for that storage pool, use the parameter -restype dynamic.

Storage pools can be shown using

storcfg pool -show


4.1.6 Using existing storage volumes

To add devices to your storage pool, ask the administrator of the storage system for unused logical devices (LUNs). Then use

storcfg volume -add -poolid myPool -system sysname -deviceid 0075 [-storid myStorID]

(assuming that 0075 is the device number / device ID of one of your logical volumes).

Repeat this command for each volume. If a storID is specified, this is assigned to the volume and can be used for further attach / detach commands. If no storID is specified, you have to use storcreate to reserve this (or another) device and assign a storID to it before it can be attached.

If this device has LUN masking connections to one or more hosts when it is added to the pool, StorMan automatically assigns a storID to the volume because it is already in-use. In this case it will not be used for automatic storage reservation by storcreate.

4.1.7 Creating new storage volumes

If the storage pool has the property -restype dynamic, the storcreate function creates a new volume in the array if no free volume with the requested size is already contained in the pool.

storcreate -storID myStorID -poolid myPool -size size-in-MB

It is also possible to specify no storage pool, but an array, or just a model, or just a size. In these cases StorMan looks for an appropriate storage pool. See the CLI Reference for details. Do not create new volumes without permission from the administrator of the array. RAID groups with enough space left have to be available when new devices are created.

4.1.8 Attach a logical device to a host

The devices contained in the storage pool(s) can be attached to any server that has been assigned to the StorMan repository.

• If all HBAs of that host are to have access to the device, use

storattach -storid myStorID –hostname myApplicationHost

• If only one HBA is to have access to the device, use

storattach -storid myStorID -hostwwpn WWPN-of-one-HBA

4.1.9 View the attachments to a device

Use

storcfg volume -show -storid myStorID

All host-side WWPNs connected to the device, the WWPNs of the storage system and the SCSI host device numbers (LUNs) visible to the host are displayed.

4.1.10 Detach a logical device from a host

Use the command

Stordetach -storid myStorID -hostname myApplicationHost


4.1.11 Release a storage volume

Use

stordelete -storID myStorID

The device is released and can be used by the storcreate function for new reservations. If the storage pool has the property STORMAN_RESOURCE_TYPE_DYNAMIC and the device was dynamically created by StorMan, it will also be removed (unbound) in the Storage System also.

4.1.12 Discover changes to a storage array

If the LUN masking setting or the devices or RAID groups are changed by tools other than StorMan, it is necessary that the CIM Object Manager / SMI-S Provider's database is updated before you continue provisioning with StorMan.

• If just one storage system was modified, use

storcfg system -discover -system serial-number

• If new storage systems are visible to the CIM Server or more than one system has been modified, use

storcfg cimom –discover -name hostname-of-the-cim-server

4.2 Setting up StorMan configurations using the GUI

Use the Configure tab of the GUI to set up StorMan. See chapter 3 on basic information on the GUI.

The Configure tab reflects the view of the storage configuration rooted by the CIM Hosts. The tree view linked to a CIM Host reflects all storage arrays that can be managed by the respective CIM Host.

4.2.1 Add a new CIM Host

Perform the following steps to add a CIM Host to a CIM Server root:

• Right-click Cim Server.

A menu appears:

• Click the Add a new CIM Host command to open a dialog box.

• Type in the name of the CIM Host and click OK.


The new CIM Server is created on the CIM Server root:

The right area of the main window contains two tables. The top one is an editable property table of the selected CIM Host. The bottom one lists the corresponding storage systems and their properties.

• Select one cell to type data. Press ENTER or TAB when you have finished typing.

The fields have the following meaning:

− Hostname You can modify the name of the CIM Host.

− IP You can enter a new IP address for this CIM Host.

− Port You can modify the default port number (default: 5988).

− Interop Namespace You can modify the interop namespace of the CIM-OM (default: interop).

− User You can enter a new user name.

− Password You can enter a password. For security reasons, the password field does not show the characters. Instead, asterisks ‘*’ are displayed.

− Interface You can use the drop down list to select the interface type.


Once you have created a host (e.g. marc), you will see the result both in the hierarchical browser and in the object list. In the example below, a property table and a table for storage systems can be found on the right-hand side.

4.2.2 Remove Host

Perform the following steps to remove a CIM Host from a CIM Server root:

• Right-click the host name (marc).

A menu appears:

• Click the Remove Host command.

• Click OK to confirm removal.

4.2.3 Add a new storage pool

A storage pool is a collection of storage volumes. You can establish a hierarchy of storage pools. The hierarchy may be based on the capacity of the devices associated with the storage pools (e.g. large, medium, small).

Perform the following steps to add a new storage pool:

• Right-click a storage system.


A menu appears:

• Click the Add a new storage pool command to open a dialog box.

• Type the name of the storage pool (e.g. MyDevices_100)

The name or identifier of the storage pool must start with an alphabetic character (‘A’, ‘B’, …, ‘Z’, ‘a’,’b’, …, ‘z’) followed by up to 254 characters, numbers, or the signs ‘+’, ‘-‘, ‘_’, ‘.’. The name must be unique. Internally it is not case-sensitive.

• Click OK.

The new storage pool is created in the StorMan repository.

In the window below you can see the newly created storage pool: MyDevices_100. The top table in the right area is the property table of the storage pool and the bottom area contains a table listing its devices. The property table is editable.

The name of the storage pool can be changed: Select the appropriate cell in the Pool ID column to edit the name. Press ENTER when you have finished typing.


The other settings are changed via drop-down lists:

• Dynamic creation allowed: specifies whether the dynamic creation of storage devices is allowed for this storage pool.

• Access mode: specifies the access mode for hosts accessing storage devices of the storage pool.

4.2.4 Delete a storage pool

Perform the following steps to delete a storage pool:

• Right-click a storage pool.

A menu appears:

• Click the Delete storage pool command.

• Click OK to confirm the deletion.

The storage pool and the storage devices it contains will be removed from the StorMan repository. They are no longer administrated by StorMan, but they will remain unchanged in the storage system with their connections to servers.


4.2.5 Rename a storage pool

Perform the following steps to rename a storage pool:

• Right-click a storage pool.

A menu appears:

• Click the Rename command to open a dialog box.

• Type the new name (pool ID) and click OK.

4.2.6 Moving devices into storage pools

Storage pool volumes are the logical devices that are assigned to a storage pool.

You can move devices from one storage pool to another storage pool. The <no StorMan pool> storage pool provides a collection of storage volumes not managed by StorMan.

The logical volumes must be part of the same storage system as the storage pool.

You can add volumes from the <no StorMan pool> to your storage pool. You can click on a device to ensure that the device has LUN masking connections to one or more servers.

Perform the following steps to move a device from the <no StorMan pool> to another storage pool.

• Select the <no StorMan pool> and right-click a device.

A menu appears:

• Click the Move to storage pool command to open a dialog box:

• Select the storage pool from the drop-down list and click OK.


The device will be moved into the selected storage pool.

i

• You can also move devices from one storage pool to another by a simple drag-and-drop operation.

• You can also move devices from a storage pool into the <no StorMan pool>.

Device property table and its connections

The upper area comprises the device property table and the connected host list appears below this. You can enter or modify the storage ID in the property table:

• Select the cell in the Storage ID column to type or modify the storage ID. Press ENTER when you have finished typing.

Assignments of storage IDs when moving storage devices into storage pools:

− A storage ID is assigned automatically by StorMan if the device is already attached to a server.

− No storage ID is assigned if the device is currently not attached to any server.

− A storage ID is specified / modified by the user as described above.

The storage ID must begin with an alphabetic character (‘A’, ‘B’, …, ‘Z’, ‘a’,’b’, …, ‘z’) followed by up to 254 characters, numbers, ‘+’, ‘-‘, ‘_’, ‘.’.

It should not start with the prefix ‘SM_’. This is reserved for automatic generation of a storage ID by StorMan.


4.3 Diagnostic aids

4.3.1 StorMan

StorMan provides a number of files containing important information for troubleshooting and for diagnosing errors.

To ensure the best possible support when problems are encountered while StorMan is being used, you are recommended to recreate the problem which occured if this is possible after you have set the highest debug level on the StorMan server for the duration of recreation process using the StorMan CLI:

storparam –debug 5

Please use the StorMan CLI to provide the current configuration data:

stormandb –dump

Afterwards, collect the files specified below which are located in the /var/opt/SMAWstor/StorMan directory for Linux environments and in the C:\Programme\Fujitsu Siemens\StorMan directory for the Windows environment and transmit them to your support organization:

1. The StorMan logging files stormanTraceyyyy-mm-dd.txt in the./log directory for the day(s) concerned.

2. The configuration file of the StorMan server smserver.ini in the./config directory.

3. The StorMan database StorMan.db in the ./repository directory. This can be linked to another directory or file (e.g. in the case of FlexFrameforOracle solutions to filer -> /filer/StorMan/repository/StorMan.db).

4. The saved StorMan database files AddData.sql and AddTables.sql (created by stormandb –dump) in the ./backup directory.

4.3.2 SMI-S Provider

Please refer to the Release Notes of the specific vendor for general diagnostic information regarding the support of SMI-S Providers.

In some cases the SMI-S Provider might not be aware of configuration changes on the storage array initiated by other management tools or instances (e.g. if an unexpected error STORMAN_FAULT is returned as result of a storattach or storcreate function).

In this situation you are recommended to initiate an update of the internal SMI-S Provider repository (only in the case of Proxy configurations) using

storcfg system –discover or

storcfg cimom -discover

and retry the failed function.


5 Special properties of storage systems

5.1 Special properties of EMC storage systems In order to use LUN masking functions, the masking software has to be installed and activated in the storage system. For Symmetrix systems this is “VolumeLogix”, for FibreCAT CX / CLARiiON CX systems “AccessLogix”.

Details about the storage system-specific LUN masking functionality can be found in the manuals for these products that are available at https://powerlink.emc.com.

On Symmetrix systems a VCM database device has to be configured and 3 gatekeeper devices must be visible to the host on which the SMI-S Provider is running. The VCM database contains the device (LUN) masking records. These records describe the amount of devices each FC initiator can access via one or more storage ports (in other words the “view” for any initiator to the storage system). Furthermore, LUN masking functionality has to be enabled for the FC target ports in the Symmetrix system to which the application hosts are connected.

Further information about installation and preparation of the SMI-S Provider can be found in the release notes for the SMI-S Provider.

5.1.1 Dynamic creation of storage volumes / logical devices

If required by the storcreate function, StorMan checks existing storage pools (RAID groups) in the storage system. If one with the requested available size is found, a new volume is created in that RAID group. In StorManV1.3 the RAID type cannot be selected, therefore the desired RAID type / RAID groups have to be configured in advance in the storage system before StorMan can create new LUNs.

Creation of storage volumes in a storage system is an asynchronous process that can take a few minutes. Thus, if StorMan is used for automated storage provisioning, you are recommended to configure the amount of required volumes before they are required by any applications using StorMan or the storage system specific administration tools in order to keep the time for provisioning short. Especially on Symmetrix systems, it is recommendable to use the Symmetrix-specific tools to create volumes because Storman V1.3 can only create one volume per StorMan request and each request causes a time-consuming reconfiguration.

A Symmetrix volume created dynamically by StorMan V1.3 is automatically mapped to all FC target ports (LUN mapping) of the Symmetrix. With future releases of StorMan it will be possible to specify the storage ports to which a newly created volume is mapped.

On the other hand, each volume in a FibreCAT CX / CLARiiON CX system is generally visible on all FC target ports.

StorMan V1.3 with SMI-S 1.1 supports the following RAID types for EMC storage systems: RAID Level FibreCAT CX /

CLARiiON CX Symmetrix Comments

RAID 0 YES NO RAID 1 YES YES RAID 5 YES YES RAID 5 feature has to be

activated on Symmetrix systems

RAID 1-0 YES NO RAID 3 YES NO RAID-S NO YES Unprotected (Disk) YES YES



5.1.2 LUN masking in FibreCAT CX / CLARiiON CX systems

LUN masking in FibreCAT CX / CLARiiON CX systems is controlled by storage groups (called ”SCSIProtocolController” in SMI-S terms). The storage groups represent the view of a part of the storage system for a special host:

Figure 3: LUN masking on FibreCAT CX / CLARiiON CX

LUN masking on a FibreCAT CX / CLARiiON CX system contains the following functions:

1. Creating and deleting storage groups

2. Connecting and disconnecting HBAs (WWPNs) to / from storage groups

3. Adding / removing volumes to / from storage groups.

Thus, attaching storage groups to a server with StorMan can include operations 1 – 3, or just operation 3 if a Storage group already exists that is connected to this host or the HBAs represented by their WWPNs.

If you detach storage groups from a server with StorMan, the specified volume is removed from the FibreCAT CX / CLARiiON CX storage group and the storage group is deleted if it was the last volume and the destroyConnection parameter was set. Therefore, the storage group will be recreated and connected to the hosts WWPNs when a following attach is called for the same host. destroyconnection should be used only if a host or its HBAs are removed from the configuration, or if a host’s HBAs are replaced or new HBAs are added. See section 5.1.4 for more details.

StorMan creates one storage group for each host if it does not find one for this host (HBA). Therefore volumes are added to more than one storage group if they are to be attached to more than one host.

! If LUN masking is already configured without using StorMan, the Storage groups should not be shared between different hosts. That would mean that a storattach command via StorMan would automatically attach the volume for all hosts which are connected to the storage group. As well it would be invisible for all the hosts if stordetach is called. Therefore, shared storage groups should be deleted or replaced by host-specific storage groups before StorMan is used.


On FibreCAT CX / CLARiiON CX systems the view of a storage group is the same on each FC target port. Unlike on Symmetrix systems, an HBA cannot access different groups of LUNs via different target ports. However, bear in mind that a volume is accessible only via one FibreCAT CX / CLARiiON CX storage processor at any one time. This is the “owner” of the volume. Using StorMan to attach / detach FibreCAT CX / CLARiiON CX volumes requires FC accessibility to the FibreCAT CX / CLARiiON CX system from the hosts to be provided with storage volumes (FC zoning).

! Unallowed Masking Configurations: The concept of FibreCAT CX / CLARiiON CX does not allow connections from one server to more than one storage group, nor from one HBA to more than one storage group. If Navisphere Host Agent is running on a server (and the FibreCAT CX / CLARiiON CX is aware of the server-HBA relations), these kinds of multi-connections are rejected. However, customer have the ability to connect a server (or HBA) to multiple storage groups (if no Host Agent is installed). StorMan also rejects storattach commands if this kind of configuration is detected (RC STORMAN_BAD_CONFIG). stordetach commands are also rejected if called with the hostname (or hostip) parameter. Nevertheless, detach can be performed by delivering a single WWPN only. To clear up these kinds of configuration, use stordetach and specify the single WWPNs and the destroyConnection parameter so that these storage groups are removed after the last volume is detached.

Prerequisites for LUN Masking in FibreCAT CX / CLARiiON CX systems for an application server

Check if the application server is already registered by the FibreCAT CX / CLARiiON CX system e.g. by using navicli command navicli -h sp-name port -list –all. Registration takes place automatically if the Navisphere agent or Navisphere server utility has been installed on the server and the server has been booted at least one time with an FC connection to the FibreCAT CX / CLARIION CX.

If an application server is registered by the agent or server utility, the system is aware of the operating system of the server and will use the correct values for unitserialnumber/arraycommpath/failovermode when volumes are attached to the server.

If an application server is not already registered by the FibreCAT CX / CLARiiON CX and volumes should be attached with StorMan, check the default values for unitserialnumber/arraycommpath/failovermode for your FibreCAT CX / CLARiiON CX using

navicli -h sp-name failovermode|arraycommpath|unitserialnumber

These values can differ for different operating systems. For Linux distributions and Windows Systems they should be

unitserialnumber - "array" arraycommpath 1 (enabled) failovermode 1

In the case of application servers, which are not registered, the system will use these values if volumes are attached to the servers.

If these parameters are not set correctly for an operating system, the FC devices may be inaccessible or path failover software may not work correctly.

For more details, refer to the vendor’s documentation, e.g. “EMC Host Connectivity Guide for Linux” (available at https://powerlink.emc.com and the documentation referenced there, such as HBA vendor-specific documents).



5.1.3 LUN masking in Symmetrix systems

In Symmetrix systems, the Volume Logix software provides LUN masking features. Details about it can be found at https://powerlink.emc.com. Records in the VCM database control the LUN masking. Each of these records defines a relationship between one HBA (represented by its WWPN), one Symmetrix FC Port and a number of logical devices (storage volumes / LUNs). In contrast to LUN masking on FibreCAT CX / CLARiiON CX, one HBA may have access to a different number of LUNs via different FC target ports (anyhow, StorMan V1.3 does not provide support for attaching / detaching a device via a specific target port). Like the storage groups in a FibreCAT CX / CLARiiON CX, the entries in the VCM database are called ”SCSIProtocolController” in SMI-S terms (abbreviated as “SPC”).

Setting of the host device number during an attach operation is not yet supported for Symmetrix systems.

Figure 4: LUN masking in EMC Symmetrix

If a storattach function is received, StorMan checks if SPCs already exist for this HBA-WWPN(s). If one or more are found, the volume is added to them, and becomes visible for that HBA via the related Symmetrix target port. No new SPCs (VCM records) are created in this case. If no VCM record (SPC) exists for an HBA, StorMan creates one new VCM record per HBA and target port to which the device is mapped and adds the device to it. For Symmetrix systems, SPCs are also generated if an HBA (represented by its WWPN) is already connected via FibreChannnel and the creation of new VCM entries is based on the LHT. If the special parameter LunMask.loginhistory.enable (see section 2.2.3.3) is set to true, the creation of new VCM entries is based on the LHT even if the HBAs are not connected any more, i.e. the attach function works more efficiently if a Symmetrix system is already connected to a host and FC zoning has been set. StorMan does not modify the Mapping in Symmetrix systems. Once VCM records exist for a HBA, StorMan will use these and only these records for further attaches, i.e. it is not possible to attach a group of volumes for a WWPN via different groups of Symmetrix ports. Check if the volumes are mapped to the same target ports the host is connected to.

Note that on an FC target port without LUN masking enabled, each connected host can access all devices mapped to this FC port. StorMan modifies the LUN masking only and does not modify the device



mapping. Therefore devices to be provided by StorMan must already be mapped to the required ports and LUN masking has to be enabled on these ports.

Before using StorMan for LUN masking with Symmetrix, consider the following:

• If VCM entries for the hosts (to be provided by StorMan) already exist, the HBAs affected and the target ports have to be physically connected and connected by FC zoning.

• Volumes that are not dynamically created by StorMan must already be mapped to the storage target ports that are accessible from the hosts.

• FC zoning for the hosts and storage systems is already configured and active.

Prerequisites for LUN Masking in Symmetrix systems

The FC director port-specific settings on the Symmetrix systems have to be checked or modified by EMC service personnel. These settings can differ for different operating systems.

5.1.4 Host storage connections (SPCs)

Please note the following issues for the various types of storage systems :

• The first attach (of a volume) for a host in one storage system may take some time (up to 2 minutes) if new SPCs have to be created. It also depends on the number of FibreChannel paths between host and storage system.

• With a detach call the destroyConnection parameter can be set (default value is “not set”). If set it causes the deletion of the affected SPC (FibreCAT CX / CLARiiON CX storage group or Symmetrix VCM database record) in the storage system if the last volume of the SPC has been detached. Setting destroyConnection is necessary only in the following cases:

− A host has been removed from the FC configuration or is no longer used.

− Single HBAs have been removed from a host

− New HBAs have been installed on a host

− The number of FibreCAT CX / CLARiiON CX storage groups or Symmetrix VCM records has reached a maximum.

In all other cases the parameter should not be set (default value). If an SPC is deleted during a detach operation, this also takes more time than when the default value is used.

5.2 Special properties of Network Appliance storage systems

5.2.1 Dynamic LUN creation

When creation of a new FC LUN is requested by storcreate, an existing volume is selected to create the new LUN. Currently you cannot specify an existing volume to host the new LUN.

Therefore, only existing volumes with a volume name starting with the string “StorMan” are selected for creation. This process ensures that no volumes potentially used by other application are affected by dynamic LUN creation by StorMan. So make sure that a volume named “StorManxxx” is available on a NetApp FAS aggregate with enough remaining space before using the dynamic LUN creation feature.

NetApp FAS filers integrate the support of RAID levels into its filers (e.g. RAID-DP, DP = double parity, a RAID6 implementation) on the level of aggregates. New volumes and new LUN s are automatically created with the RAID level of the aggregate.

For dynamic LUN creation on NetApp FAS filers it is essential to specify the type of target operating system that will deploy the LUN after creation. For this purpose the targetostype operand is supported for the storcreate command.


5.2.2 LUN mapping and LUN masking

LUN masking in Network Appliance systems is performed by “igroups” (initiator groups). Different initiators, referenced by their WWPNs, can be added to igroups, and LUNs can be mapped to one or more igroups to make them visible for the initiators. StorMan V1.3 supports a single igroup affected by a storattach / stordetach call. The attachment of the first LUN for a host will result in creation of one igroup for all of the host’s WWPNs.

If igroups are already configured before StorMan is used for LUN masking of the system and a host’s WWPNs are already connected to different igroups, a storattach call for the same host will result in STORMAN_ BAD_CONFIG. Therefore you should not mix attaches / detaches by WWPN with attaches / detaches by host for the same host.

If igroups are already configured by single WWPNs, you can only attach / detach by single WWPNs. If igroups are configured by host, you can only attach / detach by hosts.

If the igroups are configured by WWPN and you want to attach / detach by host, remove existing igroups using the Network Appliance UI or detach the LUNs already attached for the single WWPNs of the host using destroyConnection.

luns

Server_1 Server_2

Port 1

HBA1 HBA2 HBA1 HBA2

Stdby-Port

igroup1 igroup1

Fabric

WWPN1WWPN2

WWPN3WWPN4

Figure 5: iGroups in a Network Appliance Architecture

Although a Network Appliance filer allows a host WWPN connected to more than one igroup, this kind of configuration is not compliant to the use of storattach and stordetach, because in this case the storattach / stordetach command will affect all hosts that are connected to the igroup.

i

A detach with the destroyConnection parameter issued for a Network Appliance LUN removes the connection between host and igroup and deletes the igroup itself if no other LUNs are still mapped to the igroup.

Prerequisites before provisioning storage on Network Appliance systems

The FCP service must be licensed and activated. See the Network Appliance “Block Access Management Guide for FCP” for details.


6 GUI: Administration and Provisioning tasks The Manage tab in the main window provides the provisioning features of StorMan on the GUI.

Hosts that should be provisioned by StorMan have to be added to the StorMan database using the Manage tab.

6.1 Add a new host

Perform the following steps to add a host to the All Hosts folder.

• Right-click All Hosts.

A menu appears:

• Click the Add a new host command to open a dialog box:

• Type the name of the host and click OK.

The new host is created on the All Hosts root:


The main window shows the host names in the hierarchical browser on the left and a table of the hosts’ properties on the right.

• Click on a host name (e.g. groucho) to view the properties of a single host in the object table.

The object table area then contains a sub tab bar providing the Connected Devices tab and the Attach tab. When the Connected Devices tab is selected, the object table shows the host’s properties in the upper table and the device connections in the lower table.

When the Attach tab is selected, the object table shows two drop-down lists for storage systems and storage pools in the left-hand column. The list of attachable devices is shown in the right-hand column.


6.2 Remove a host

Perform the following steps to remove a host from the All Hosts root:

• Right-click the host name.

A menu appears:

• Click the Remove Host command.

• Click OK to confirm removal.

6.3 Add a new WWPN

Perform the following steps to add a new WWPN to a host:


A menu appears:

• Click the Add a new WWPN command to open a dialog box:

• Type a valid WWPN (omit hyphens) for this host and click OK.

After that the new WWPN appears in the left-hand property table. You can repeat this procedure to enter several WWPNs.

The host (HBA) WWPNs have to be added to the StorMan repository before you attach a device to a host.


6.4 Remove a WWPN

Perform the following steps to remove a WWPN from a host:


A menu appears:

• Click the Remove WWPN command to open a dialog box:

• Select a WWPN from the drop-down list and click OK.

After that the WWPN number disappears in the left-hand property table. You can repeat this procedure to remove several WWPNs.

6.5 Attach a device

When you attach a device, this storage volume becomes visible for a host. Perform the following steps to attach a device:

• Click on a host name in the hierarchy browser

• Select the Attach tab in the object table.

• Select a storage system from the Storage Systems drop-down list.


• Then select a corresponding pool ID from the Pool IDs drop-down list.

A list of attachable devices is shown on the right-hand side of the device list.

• Select a device in the device list and click Attach.

It may take some seconds until this function is executed. The first time a device for a specific host is attached to this storage system, it may take up to 1 minute.

If the storage ID has not already been specified, you will be prompted to enter a storage ID:

• Type in the storage ID and click OK.

A dialog box prompts you for a host LUN (Not for EMC Symmetrix storage):


• Type in a host LUN and click OK.

Make sure this LUN number is not already used for this host in this storage system. You may enter a number in the range 0 – 255. Note: This feature is not yet supported for EMC Symmetrix systems. In a Symmetrix system (up to Enginuity 5671), the host LUN number can only be defined by the mapping of the volume at configuration time.

The selected device will disappear from the list of attachable devices (after a few seconds) and will be displayed in the object table of the Connected Devices tab.

6.6 Detach a device

When you detach a device, this storage volume will be disconnected from a host. Perform the following steps to detach a device:

• Click on a host name in the hierarchy browser

• Select the Connected Devices tab in the object table.

• Select a device to detach.

This will activate the Detach button and the Destroy Connection check box. If the selected device has no other connections, the Release check box is also activated.


• If you want to remove the storage ID, select the Release check box and click Detach. (If you do not select the check box, the storage ID will be retained.)

• If you select the Destroy Connection check box and this is the last storage volume in the related storage system attached to the selected host, the connection between the HBA / host and a storage port / storage system will be destroyed when you click Detach (e.g. the storage group in a CLARiiON system will be removed when it is empty). This is recommended if the host will no longer use this connection to the storage array. See section 5.1.4 for more details.

It may take some seconds until this function is executed.


7 StorMan for programmers – CLI description This chapter covers all the StorMan features related to StorMan administration and storage provisioning provided on CLI level.

The StorMan CLI is not required for the Information and Monitoring features delivered for server management integration except the function storcfg cimom to set up the SMI-S Provider configuration.

7.1 General

7.1.1 Common CLI aspects

Some aspects are valid for all commands of the StorMan CLI. These are specified here and not repeated for each command.

Parameter file

The CLI can read additional command parameters from a file. This can be useful especially for connection parameters that do not change, or if the command line is too short to specify all required parameters. This file must be specified as

–file file

The file will be interpreted as a list of specified parameters prior to all other parameters in the command line.

The -file option is not designed to contain multiple commands; only additional parameters for a single command can be specified.

Lines beginning with ‘#’ in such a file are interpreted as comments and therefore ignored.

The –file option is not mentioned in the syntax diagrams of the individual commands.

Connection parameters

All commands need a connection to the StorMan Server. The necessary connection parameters are:

–server stormanserver

Specifies the IP address or name of the StorMan Server (default: localhost).

–port port

Specifies the port the server is listening on (default: 4178).

–user user

Specifies the user for validation on the server (default: not specified).

–pwd pwd

Specifies the password for validation on the server (default: not specified).

–connectparam stands for these parameters in the syntax diagrams of the individual commands.

Help function

An internal help function is supported for every command by the –help option.


Additional common aspects

• If a parameter is specified more than once, the last value will be used.

• Parameters are not case-sensitive. Parameter values are case-sensitive except when specified otherwise. StorIDs and Pool IDs are stored as input with case (for display) but treated without case in all internal search functions.

• If a specified parameter is not supported, the command is rejected.

7.1.2 Common enumeration values

All StorMan commands use a common set of enumerations for input parameters and output values. These are described below:

StorMan size types

The enumeration STORMAN_SIZE_TYPE defines the possible measuring units to be used when handling storage sizes. Value Meaning STORMAN_SIZE_TYPE_B Measure unit = 1

Byte 1 STORMAN_SIZE_TYPE_KB Measure unit = 1,000

Bytes 1,024 STORMAN_SIZE_TYPE_MB Measure unit = 1,000,000

Bytes 1,048,576 STORMAN_SIZE_TYPE_GB Measure unit = 1,000,000,000

Bytes 1,073,741,824 STORMAN_SIZE_TYPE_TB Measure unit = 1,000,000,000,000

Bytes 1,099,511,627,776

StorMan access mode types

The enumeration STORMAN_ACCESS_MODE defines how storage units may be accessed on a certain host: for exclusive or shared use. This property is used when selecting a storage pool for storage unit creation as well as when attaching (accessing) a storage unit which has already been created for a host. Value Meaning STORMAN_ACCESS_MODE_ANY Arbitrary access mode (only applicable with request) STORMAN_ACCESS_MODE_NONE Current state of storage unit: not yet attached to any host

(only available as information value) STORMAN_ACCESS_MODE_EXCLUSIVE The host will be attached (by request) or is shown as

attached exclusively. There is no further attach to another host allowed.

STORMAN_ACCESS_MODE_SHARED The host can be attached together with other hosts which are already attached with shared access mode


StorMan resource types

The enumeration STORMAN_RESOURCE_TYPE defines the resource type property which designates a storage pool resource (to be) reserved. Value Meaning STORMAN_RESOURCE_TYPE_ANY Indicates that the storage unit requested for reservation

may be predefined as well as dynamic STORMAN_RESOURCE_TYPE_PREDEFINED Indicates a certain storage unit as statically predefined STORMAN_RESOURCE_TYPE_DYNAMIC Indicates a certain storage unit as (to be) dynamically

created.

StorMan connection types

The enumeration STORMAN_CONNECTION_TYPE represents possible connection type values. Connection type SAN is supported with StorMan V1.3. Value Meaning STORMAN_CONNECTION_TYPE_ANY No specific storage type requested STORMAN_CONNECTION_TYPE_SAN Storage area network (SAN)

Storman storage vendors

The enumeration STORMAN_STORAGE_VENDOR represents a list of supported of storage vendors. StorMan V1.3 supports storage systems from EMC Corporation, Fujitsu Siemens Computers and Network Appliance Inc. Value Meaning STORMAN_STORAGE_VENDOR_ANY No specific vendor requested STORMAN_STORAGE_VENDOR_EMC EMC Corporation, providing Symmetrix and CLARiiON

CX storage systems STORMAN_STORAGE_VENDOR_NETAPP Network Appliance Inc., providing Network Appliance

Filer STORMAN_STORAGE_VENDOR_FSC Fujitsu Siemens Computers, providing FibreCAT SX and

FibreCAT CX storage systems

StorMan storage models

The enumeration STORMAN_STORAGE_MODEL represents a list of supported storage system models. The storage models Symmetrix and CLARiiON CX from EMC Corporation, Network Appliance Filer (NetApp FAS) from Network Appliance Inc. and FibreCAT SX and FibreCAT CX from Fujitsu Siemens Computers are supported with StorMan V1.3. Value Meaning STORMAN_STORAGE_MODEL_ANY No specific model requested STORMAN_STORAGE_MODEL_SYMMETRIX Symmetrix storage system from EMC STORMAN_STORAGE_MODEL_CLARIION FibreCAT CX storage system from Fujitsu Siemens

Computers / CLARiiON CX storage system from EMC Corporation

STORMAN_STORAGE_MODEL_NETAPPFILER Network Appliance Filer from Network Appliance Inc. STORMAN_STORAGE_MODEL_FIBRECAT_SX FibreCAT SX storage systems from Fujitsu Siemens

Computers


7.1.3 Common supported value ranges

All StorMan commands have some common parameters with a defined range of supported values specified below: Value Meaning and supported values ip | hostip IP address: a string of 4 decimal numbers delimited by '.' each in the range from 0 to

255 hostname host name: a string containing alphabetic characters ('A', 'B',... 'Z', 'a', 'b',... 'z',

numbers and other signs except: '\', '/', '*', '? ', '"', '<', '>', '|', ' '. Internally it is not case-sensitive.

poolid pool ID: a string starting with an alphabetic character ('A', 'B',... 'Z', 'a', 'b',... 'z' followed by up to 254 alphabetic characters, numbers, '+', '-', '_' or '.'. The pool ID must be unique. Internally it is not case-sensitive.

storid storage ID (storID): a string starting with an alphabetic character (‘A’, ‘B’, ..., ‘Z’, ‘a’, ‘b’, ..., ‘z’) followed by up to 254 characters, numbers, ‘+’, ‘-‘, ‘_’ or ‘.’ It should not start with prefix ‘SM_’ (regardless of case) as this is reserved for internal use. Internally it is not case-sensitive.

wwpn WWPN: a string of 16 hexadecimal numbers delimited by ':', ‘-‘ or without delimiter


7.2 storcfg The storcfg command is used to configure the StorMan repository.

storcfg object –function –functionparam ... –connectparam ... The first parameter specifies the object group of the repository that is configured: First parameter object Object cimom CIM Object Manager host hosts for provisioning or hosting a CIM-OM system storage systems managed by StorMan pool pools to organize logical volumes volume logical volumes managed by StorMan

The second parameter specifies the function. Most commands support at least the following functions:

Second parameter function Meaning –add adds an object to the repository –mod modifies the properties of an object –rem removes an object from the repository –show shows the attributes of one or more object(s)

If the –show function is specified, the output format can be selected by specifying the –format parameter.

7.2.1 storcfg host

storcfg host is used to manage host information in a StorMan configuration. The host information is necessary to attach a device to all FC ports of a host in one step and to display a storage volume with all its connection information related to a host.

storcfg host –function –functionparam ... –connectparam ...

Functions

The –function parameter supplies one of the following functions:

–add

adds a new host to the StorMan repository

–mod

modifies the attributes of a host already contained in StorMan repository

–rem

removes a host from the StorMan repository

–show

displays information related to hosts


7.2.1.1 storcfg host –add

Adds a new host to the StorMan repository.

Syntax

storcfg host –add { –name hostname | –ip ip[,...] } [ –wwpn wwpn[,...] ] –connectparam ...

Parameters

–name hostname

Specifies the name of the host.

Refer to the common description of hostname on page 59.

–ip ip[,...]

Specifies a list of IP addresses delimited by comma. If no hostname is specified, one of the IP addresses is used as hostid.

–wwpn wwpn[,...]

Specifies a list of WWPNs delimited by comma.

At least one of the parameters –name or –ip must be specified and have a non-empty value.

–connectparam

Refer to the description of the connection parameters on page 56.

Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server 16 STORMAN_FAULT Unexpected error in function. 20 STORMAN_ALREADY_EXISTS Object already exists in repository 22 STORMAN_RESOURCE_NOT_

AVAILABLE CIM Server or database not available

7.2.1.2 storcfg host –mod

Modifies the attributes of a host already contained in the StorMan repository.

If a parameter is not specified, the corresponding attribute is not changed.

Syntax

storcfg host –mod { –name hostname | –ip ip | –wwpn wwpn } [ –newname hostname ] { –newip ip[,...] | –addip ip | –remip ip } { –newwwpn wwpn[,…] | –addwwpn wwpn | –remwwpn wwpn } –connectparam ...

Parameters

–name hostname

Identifies the host by its name.


–ip ip

Identifies the host by an IP address belonging to the host.

–wwpn wwpn

Identifies the host by a WWPN belonging to the host.

Exactly one of the parameters –name, –ip or -wwpn must be specified to identify the host.

–newname hostname

Specifies the new name of the host. If the –newname is specified without a value, the name is removed.


–newip ip[,...]

Specifies a list of IP addresses delimited by comma. If no hostname is specified, one of the IP addresses is used as hostid.

–addip ip[,...]

Assign a single IP address to the host.

–remip ip

Deassign a single IP address from the host.

–newwwpn wwpn[,…]

A list of WWPNs delimited by comma to assign to the host.

–addwwpn wwpn

Assign a single WWPN to the host.

–remwwpn wwpn

Deassign a single WWPN from the host.

–connectparam


Only one of the paramters -newip, -addip or -remip can be specified to modify the IP address assignment to the host. Combined input of these parameters is rejected with STORMAN_INV_PARAMETERS. If a specified IP address is already assigned to a different host, the (re)assignment of this IP address is rejected with return code STORMAN_ALREADY_EXISTS.

Only one of the parameters –newwwpn, -addwwpn or -remwwpn can be specified to modify the WWPN assignment to the host. Combined input of these parameters is rejected with STORMAN_INV_PARAMETERS. If a specified WWPN is already assigned to a different host, the (re)assignment of this WWPN is rejected with return code STORMAN_ALREADY_EXISTS.

Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Specified host could not be found. 20 STORMAN_ALREADY_EXISTS Object already exists in repository 22 STORMAN_RESOURCE_NOT_



7.2.1.3 storcfg host –rem

Removes a host from the StorMan repository. If this host is also acting as one or more CIM-OMs, these are also removed from repository.

Syntax

storcfg host –rem { –name hostname | –ip ip | –wwpn wwpn } –connectparam ...

Parameters

–name hostname

Identifies the host by its name. This parameter supports wildcards (*).

–ip ip

Identifies the host by an IP address belonging to the host.

–wwpn wwpn

Identifies the host by a WWPN belonging to the host.

Exactly one of the parameters –name, –ip or -wwpn must be specified with a non-empty value to identify the host.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Specified host could not be found.

22 STORMAN_RESOURCE_NOT_ AVAILABLE

CIM Server or database not available


7.2.1.4 storcfg host –show

Displays information related to the specified hosts.

Syntax

storcfg host { –name hostname | –ip ip | –wwpn wwpn } [ –format format ] –connectparam ...

Parameters

–name hostname

Selection by the name of the host.

–ip ip

Selection by the IP address of the host.

–wwpn wwpn

Selection by the WWPN of a host

All parameters above can be specified partially using ‘*’ as wildcard.

–format format

Specifies the output format. Permitted values: std (default) | short | xml | xmlp.

std selects a multi-line output: Each attribute of an object is displayed on a separate line. This is also the default output format.

short displays only the id / name of an object on a separate line.

xml writes the output in xml format in a single line.

xmlp writes the output in xml format, but in a multi-line format for better human readability (pretty print).

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 22 STORMAN_RESOURCE_NOT_



Examples

a) Output for hosts with –format std (default)

storcfg host –show –name d*

hostID type STORMAN_HOSTID_TYPE_NAME hostID demeter hostname demeter IPs: 172.25.75.31 WWPNs: 10000000C93EA433 10000000C93EA514

b) Output for hosts with –format xmlp

storcfg host –show –name d* -format xmlp

<Hosts> <hostIDType>STORMAN-HOSTID-TYPE-NAME</hostIDType> <hostID>demeter</hostID> <hostName>demeter</hostName> <IPs>172.25.75.31</IPs> <WWPNs>10000000C93EA433</WWPNs> <WWPNs>10000000C93EA514</WWPNs> </Hosts>


7.2.2 storcfg cimom

storcfg cimom is used to manage CIM Object Manager information for SMI-S controlled storage systems and storage array information (API Server) for API controlled storage arrays in the StorMan repository. Please note that all following references to CIM-OMs are valid for the storage array information for API controlled storage arrays respective.

storcfg cimom –function –functionparam ... –connectparam ...

Functions


–add

adds a new CIM-OM information or the new API Server to the StorMan repository

–mod

modifies the attributes of an existing CIM-OM or the API Server in the StorMan repository

–rem

removes CIM-OM information or the API Server from the StorMan repository

–discover

requests to discover the CIM-OM all available storage systems

–show

displays information related to hosts hosting CIM-OMs or API Servers

7.2.2.1 storcfg cimom –add

Adds the new CIM-OM information or the new API Server to the StorMan repository.

Syntax

storcfg cimom –add { –name hostname | –ip ip } [ –interface type ] [–interop interop] –http port [ –cimuser user ] [ –cimpwd pwd ] –connectparam ...

Parameters

–name hostname

Specifies the name of the host the CIM-OM is running on or the name of the API Server (Network Appliance filer).


–ip ip

Specifies the IP address of the host the CIM-OM is running on or the IP address of the API Server (Network Appliance filer).


–interface type

Specifies the interface type for the hostname:

-interface smis (default) for CIM-OMs.

-interface netappapi for API Server of Network Appliance filers.–http port

Specifies the port the CIM-OM is listening on (default: 5988 for interface type smis, 80 for interface type netappapi).

–interop interop

Specifies the interop namespace of the CIM-OM. Supported for –interface smis only.

–cimuser user

Specifies the user for the CIM-OM connection (default: none).

–cimpwd pwd

Specifies the password for the CIM-OM connection (default: none).

At least -http and one of the parameters –name or –ip must be specified. If no host with the specified name or ip exists in the StorMan repository, a new host is added. For EMC’s SMI-S Provider, “cimuser” is a user name that is configured for the specified CIM Server (see the vendor-specific Installation Guides for information on how to add a cimuser). If a cimuser is specified, it must be provided for the StorMan repository with the function storcfg cimom –add.

For API Server of Network Appliance filers cimuser / cimpwd are used to logon to the filer.

–connectparam


i

It is recommendable to add the host to the repository first using storcfg host –add. You can add wwpn information and a couple of IP addresses in this step. If the CIM-OM is added before the host, you have to use storcfg host –mod to provide additional information for the host.

Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 20 STORMAN_ALREADY_EXISTS Object already exists in repository 22 STORMAN_RESOURCE_NOT_

AVAILABLE CIM server or database not available


7.2.2.2 storcfg cimom –mod

Modifies the attributes of an existing CIM-OM or an API Server.


Any combination of the parameters name, ip, interface and http which uniquely identifies the CIM-OM may be used to specify the CIM-OM to be modified.

To change the name or IP address of the CIM-OM or of the API Server, please use the function storcfg host –mod.

Syntax

storcfg cimom –mod { –name hostname | –ip ip } [ –interface type ] –http port [ –newinterface type ] [ –newhttp port ] [ –newinterop interop ] [ –newuser user ] [ –newpwd pwd ] –connectparam ...

Parameters

–name hostname

Specifies the name of the host the CIM-OM is running on or the name of the API Server.

–ip ip

Specifies the IP address of the host the CIM-OM is running on or the IP address of the API Server.

–interface type

Specifies the interface type for the hostname.

-interface smis (default) for CIM-OMs.

-interface netappapi for API Server (Network Appliance filers).

–http port

Specifies the port the CIM-OM is listening on. If the CIM-OM and StorMan are located on the same host, no port is used for communication and this parameter can be omitted.

–newinterface type

Specifies the new interface type for the hostname:

-newinterface smis for CIM-OMs.

-newinterface netappapi for API Server (Network Appliance filers)

–newinterop interop

Specifies the interop namespace of the CIM-OM. Supported for –interface smis only.

–newhttp port

Specifies the new port the CIM-OM is listening on

–newuser user

Specifies the new user for the CIM-OM connection.

–newpwd pwd

Specifies the new password for the CIM-OM connection.

At least one of the parameters –name or –ip must be specified to select the CIM-OM.

–connectparam



Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Specified host was not found. 22 STORMAN_RESOURCE_NOT_


7.2.2.3 storcfg cimom –rem

Removes the CIM-OM or the API Server from the StorMan repository. The Storage Arrays and their corresponding storage pools managed by the removed CIM-OM are not removed from the repository as a further CIM-OM may be or may become available for management. The host information remains in the StorMan repository; only the description of the CIM-OM is removed.

Any combination of the parameters name, ip, interface and http which uniquely identifies the CIM-OM may be used to specify the CIM-OM to be removed.

Syntax

storcfg cimom –rem { –name hostname | –ip ip } [ –interface type ] –http port –connectparam ...

Parameters

–name hostname

Specifies the name of the host, the name of the host the CIM-OM is running on or the name of the API Server. This parameter supports wildcards (*).

–ip ip


–interface type


-interface smis for CIM-OMs.


–http port

Specifies the port the CIM-OM is listening on .

At least one of the parameters –name or –ip must be specified.

–connectparam



Return codes



7.2.2.4 storcfg cimom –discover

Requests the CIM-OM to discover all available storage systems, i.e. to get or update all the configuration data of all storage systems which can be accessed by the respective CIM-OM. This function may take some time depending on the number of connected storage systems and their complexity.

Any combination of the parameters name, ip, interface and http which uniquely identifies the CIM-OM may be used to specify that the CIM-OM should discover storage systems.

In general, a storage system should not be managed using CIM Servers on different hosts concurrently if the CIM-OMs have repositories of their own. If more than one CIM Host have connections to one storage system, they should not run at the same time.

Syntax

storcfg cimom –discover { –name hostname | –ip ip } [ –interface type ] –http port –connectparam ...

Parameters

–name hostname

Specifies the name of the host, the CIM-OM is running on or the name of the API Server. This parameter supports wildcards (*).

–ip ip


–interface type


-interface smis for CIM-OMs.


–http port

Specifies the port the CIM-OM is listening on.

At least one of the parameters –name or –ip must be specified.

–connectparam



i

If the CIM-OM or the API Server are specified by their name, the name must be valid in the local network otherwise STORMAN_RESOURCE_NOT_AVAILABLE is returned. If the name is modified or removed from the network, the name can be removed or modified in the StorMan repository using storcfg host –mod .

Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Specified host could not be found. 22 STORMAN_RESOURCE_NOT_


25 STORMAN_CIMOM_AUTH_ FAILED

User / password for CIM Server not valid. If the CIM Server supports authentication.

7.2.2.5 storcfg cimom –show

Displays information related to hosts hosting CIM-OMs.

Syntax

storcfg cimom –show [ –system sysname ] –format format –connectparam ...

Parameters

-system sysname

Specifies the storage system name and selects all CIM-OMs or API Servers managing the respective storage system(s). This parameter supports wildcards (*). If the parameter is not specified, all CIM-OMs and API Servers in StorMan repository are displayed.

–format format



short displays only the id/name of an object on a separate line.



–connectparam



Return codes



Examples

a) Output for CIM-OMs with –format std (default)

storcfg cimom –show

hostID type STORMAN_HOSTID_TYPE_NAME hostID ducksoup hostname ducksoup IP 172.25.75.100 interop interop http port 5988 user administrator running true interface STORMAN_INTERFACE_TYPE_SMIS hostID type STORMAN_HOSTID_TYPE_NAME hostID mynetapp hostname mynetapp IP 172.25.75.101 interop http port 80 user root running false interface STORMAN_INTERFACE_TYPE_NETAPP_API

b) Output for CIM-OMs with –format=xmlp

storcfg cimom –show -format

<CIMOMs> <hostIDType>STORMAN-HOSTID-TYPE-NAME</hostIDType> <hostID>ducksoup</hostID> <hostName>ducksoup</hostName> <IP>172.25.75.100</IP> <interop>interop</interop> <PortHttp>5988</PortHttp> <User>administrator</User> <Running>true</Running> <interface>STORMAN_INTERFACE_TYPE_SMIS</interface> </CIMOMs>


7.2.3 storcfg system

storcfg system is used to manage the storage systems in the StorMan repository.

The –add and –mod functions are not supported because storage systems are automatically added to the StorMan repository only as a result of a storcfg cimom –discover call.

storcfg system –function –functionparam ... –connectparam ...

Functions


–rem

removes the storage system from the StorMan repository

–discover

requests to rediscover the storage system, i.e. to completely update the configuration data of the specified storage system

–show

displays information related to the storage systems

7.2.3.1 storcfg system –rem

Removes the storage system from the StorMan repository.

If storage pools are defined for the storage system concerned, they are also completely removed from the StorMan repository together with their logical volumes. Therefore the contents of the storage pools (logical volumes and their assigned storIDs) can no longer be managed by StorMan.

The configuration of the storage system and its assignment to servers is not touched by this function.

Syntax

storcfg system –rem –system sysname –connectparam ...

Parameters

–system sysname

Specifies the system name of the storage system to be removed. This parameter is mandatory and supports wildcards (*).

–connectparam


Return codes




7.2.3.2 storcfg system –discover

Storman starts a discovery of the storage system ( i.e. the complete configuration data of the specified storage system is updated). The discovery is processed by the appropriate CIM-OM or API-Server in StorMan’s configuration. This function may take some time depending on the complexity of the storage system

Syntax

storcfg system –discover –system sysname –connectparam ...

Parameters

–system sysname

Specifies the system name of the storage system to discover. This parameter is mandatory and does not support wildcards (*).

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 22 STORMAN_RESOURCE_NOT_



User / password for CIM Server not valid.

7.2.3.3 storcfg system –show

Displays information related to the storage systems.

Selection criteria for the –show function can be specified using the parameters described below.

The following parameters are supported:

Syntax

storcfg system –show [ –system sysname ] [ –conntype conntype ] [ –vendor vendor ] [ –model model ] [ –unmanaged ] [ –format format ] –connectparam ...

Parameters

–system sysname

Specifies the system name of the storage system (default: *). Wildcards (*) are supported.

–conntype conntype

Specifies the vendor of the storage system. Supported values: san | any (default)


–vendor vendor

Specifies the connection type of the storage system. Supported values: emc | fsc | netapp | any (default).

–model model

Specifies the model of the storage system. Supported values: symmetrix | clariion | fibrecatsx | netappfiler | any (default).

–unmanaged

Displays only storage systems without a managing CIM-OM.

–format format






–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 22 STORMAN_RESOURCE_NOT_




Examples

a) Output for storage systems with –format=std (default)

storcfg system –show –model clariion

storage system name = CLARiiON+CK200041600124 connection type = STORMAN_STORAGE_TYPE_SAN storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION

b) Output for storage systems –format=xmlp

storcfg system –show –model clariion –format xmlp

<StorageSystems> <storageSystemName>CLARiiON+CK200041600124</storageSystemName> <connectionType>STORMAN-STORAGE-TYPE-SAN</connectionType> <storageVendor>STORMAN-STORAGE-VENDOR-EMC</storageVendor> <storageModel>STORMAN-STORAGE-MODEL-CLARIION</storageModel> </StorageSystems>


7.2.4 storcfg pool

storcfg pool is used to manage the storage pools in the StorMan repository.

storcfg pool –function –functionparam ... –connectparam ...

Functions


–add

adds a new storage pool to the StorMan repository

–mod

modifies the attributes of an existing storage pool or renames the storage pool

–rem

removes a storage pool from the StorMan repository

–show

displays information related to storage pools

7.2.4.1 storcfg pool –add

Adds a new storage pool to the StorMan repository. The storage pool is defined for a specific storage system already contained in the repository.

After completing the –add function, the new storage pool is created and empty; it contains no logical volumes.

Syntax

storcfg pool –add –poolid poolid –system sysname [ –restype restype ] [ –access access ] –connectparam ...

Parameters

–poolid poolid

Specifies the ID of the storage pool. This parameter is mandatory. Refer to the common description of poolid on page 59.

The pool ID must be unique and is internally not case-sensitive. If the pool ID already exists in the repository, the command is rejected.

–system sysname

Specifies the system name of the storage system that contains the storage pool. If the specified storage system is not contained in the repository, the command is rejected.

This parameter is mandatory.

–restype restype

Specifies the type of resources in this storage pool, i.e. if dynamic creation of new logical volumes in the storage system is allowed for this storage pool

-restype predefined (default value) allows no dynamic creation

-restype dynamic allows dynamic creation


–access access

Specifies whether volumes in this storage pool can be attached to one host only at a point in time (-access exclusive) or may be attached to multiple hosts (default: -access shared).

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 19 STORMAN_POOLID_IN_USE Pool ID is in use 20 STORMAN_ALREADY_EXISTS Object already exists in the repository 22 STORMAN_RESOURCE_NOT_


7.2.4.2 storcfg pool –mod

Modifies the attributes of a specified existing storage pool or renames the storage pool. If a parameter is not specified, the corresponding attribute is not changed.

Syntax

storcfg pool –mod –poolid poolid [ –newpoolid poolid ] [ –newrestype restype ] [ –newaccess access ] –connectparam ...

Parameters

–poolid poolid

Specifies the ID of the storage pool. This parameter is mandatory. Refer to the common description of poolid on page 59.

The pool ID must be unique and is internally not case-sensitive.

–newpoolid poolid

Specifies the new ID of the storage pool in the case of renaming.

For restrictions in naming the pool ID, refer to the common description of poolid on page 59.

–newrestype restype

Specifies if dynamic creation of logical volumes is allowed for this storage pool:

-newrestype predefined allows no dynamic creation.

-newrestype dynamic allows dynamic creation.

–newaccess access

Specifies whether volumes in this storage pool can be attached to one host only at a point in time (-newaccess exclusive) or may be attached to multiple hosts (default: -newaccess shared).

–connectparam



Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Specified pool was not found. 19 STORMAN_POOLID_IN_USE Pool ID already used otherwise 22 STORMAN_RESOURCE_NOT_


7.2.4.3 storcfg pool –rem

Removes a storage pool from the StorMan repository.

If the storage pool contains logical volumes, these are also removed from the StorMan repository.

Therefore the contents of the storage pool (logical volumes with their assigned StorIDs) can no longer be managed by StorMan.

The configuration of the storage system and its assignment to servers is not touched by this function.

Syntax

storcfg pool –rem –poolid poolid –connectparam ...

Parameters

–poolid poolid

Specifies the ID of the storage pool to be removed. This parameter is mandatory.

Refer to the common description of poolid on page 59. Wildcards (*) are supported.

Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided, i.e. pool ID not

found 19 STORMAN_POOLID_IN_USE pool ID already used otherwise 22 STORMAN_RESOURCE_NOT_



7.2.4.4 storcfg pool –show

Displays information related to storage pools.

Syntax

storcfg pool –show [ –poolid poolid ] [ –system sysname ] [ –restype restype ] [ –vendor vendor ] [ –model model ] [ –conntype conntype ] [ –access access ] [ –format format ] –connectparam ...

Parameters

–poolid poolid

Specifies the ID of the storage pool (default: *). Wildcards (*) are supported.

–system sysname

Specifies the system name of the storage system (default: *). Wildcards (*) are supported.

–restype restype

Selects by the type of resources in a storage pool, i.e. if dynamic creation of new logical volumes in the storage system is allowed for the storage pools. Supported values: predefined | dynamic | any (default)

–vendor vendor

Selects by the vendor of the storage system. Supported values: emc | fsc | netapp | any (default).

–model model

Selects by the model of the storage system. Supported values: symmetrix | clariion | fibrecatsx | netappfiler | any (default).


Selects by the connection type of the storage system. Supported values: san | any (default)

–access access

Selects by the host access to the storage system. Supported values: exclusive | shared | any (default).

–format format






–connectparam



Return codes



Examples

a) Output for storage pools with –format std (default)

storcfg pool –show –poolid ralf*

pool ID = Ralf100 storage system name = CLARiiON+ck200024200100 storage type = STORMAN_STORAGE_TYPE_SAN storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION resource type = STORMAN_RESOURCE_TYPE_DYNAMIC allowed access = STORMAN_ACCESS_MODE_ANY

b) Output for storage pools with –format xmlp

storcfg pool –show –poolid ralf* -format xmlp

<PoolDescriptions> <poolID>Ralf100</poolID> <storageSystemName>CLARiiON+ck200024200100</storageSystemName> <connectionType>STORMAN-STORAGE-TYPE-SAN</connectionType> <storageVendor>STORMAN-STORAGE-VENDOR-EMC</storageVendor> <storageModel>STORMAN-STORAGE-MODEL-CLARIION</storageModel> <dynamicAllowed>false</dynamicAllowed> </PoolDescriptions> <PoolDescriptions> <poolID>Ralf_121</poolID> <storageSystemName>CLARiiON+CK200041600121</storageSystemName> <connectionType>STORMAN-STORAGE-TYPE-SAN</connectionType> <storageVendor>STORMAN-STORAGE-VENDOR-EMC</storageVendor> <storageModel>STORMAN-STORAGE-MODEL-CLARIION</storageModel> <dynamicAllowed>true</dynamicAllowed> </PoolDescriptions>


7.2.5 storcfg volume

storcfg volume is used to manage the logical volumes in the storage pools of the StorMan repository.

storcfg volume –function –functionparam ... –connectparam ...

Functions


–add

adds new logical volumes to a specified storage pool of the StorMan repository

–mod

changes the attributes of logical volumes of the storage pool or moves a logical volume into another storage pool

–rem

Removes a logical volume from the storage pool of StorMan repository

–show

Displays information related to logical volumes

7.2.5.1 storcfg volume –add

Adds one or more new logical volumes to a specified storage pool of the StorMan repository. The storage pool must already exist in the repository. The logical volumes must be part of the same storage system as the storage pool.

The function supports the addition of single logical volumes to a storage pool or a mass operation adding all logical volumes of a storage system not yet contained in the StorMan repository.

Syntax

storcfg volume –add [ –storid storid ] –poolid poolid –system sysname –deviceid devid –connectparam ...

Parameters

–storid storid

If the parameter is not specified (or no value is specified), there are two cases:

− A storID is assigned automatically by StorMan if the logical volume is already attached to a server.

− No storID is assigned if the logical volume is currently not attached to any server. It is considered as a free volume in the storage pool. This volume can be requested by a subsequent storcreate command.

If the parameter is specified with a storID, the value storid specifies the unique identifier to be assigned to the logical volume for further management by StorMan which is selectable by the caller.

− For naming conventions related to storIDs, refer to the common description of storid.

− If the storID already exists, the command is rejected.

− If specified by caller, the storID is assigned regardless of the attachment of the logical volume to a server.


If the value #auto is specified, StorMan automatically generates a storID for all logical volumes regardless of any attachment to a server. This value is supported only in combination with parameter -deviceid #all.

Default: Parameter not specified.

–poolid poolid

Specifies the ID of the storage pool the logical volume should be added to. This parameter is mandatory. If the pool ID does not exist in the repository, the command is rejected.

–system sysname

Specifies the name of the storage system. This parameter is mandatory to uniquely specify the volume in combination with –deviceid devid.

–deviceid devid

Specifies the device ID of the logical volume. This parameter is mandatory. Possible values:

− The value is a string (not an integer value) and must be equal to the value shown by StorMan via storcfg volume –show –system sysname –storid. Otherwise STORMAN_NOT_FOUND is returned.

− If the value #all is specified, all logical volumes of the storage system not yet contained in the StorMan repository are added. In this case the –storid #auto parameter must be specified to automatically assign storIDs to the volumes.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server14 STORMAN_STORAGE_LOCKED Storage unit to be modified currently locked. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 19 STORMAN_STORID_IN_USE StorID already used otherwise 20 STORMAN_ALREADY_EXISTS Object already exists in the repository 22 STORMAN_RESOURCE_NOT_





7.2.5.2 storcfg volume –mod

Changes attributes of logical volumes in a storage pool (e.g. rename) or moves a logical volume from a storage pool to another storage pool.


Syntax

storcfg volume –mod { [ –storid storid ] [ –deviceid devid ] } [ –system sysname ] [ –newpoolid poolid ] [ –newstorid storid ] –connectparam ...

Parameters

–storid storid

This parameter is mandatory for logical volumes with an assigned storID.

For logical volume without assigned storID, the parameter must be omitted and the parameter -deviceid must be specified instead.

–deviceid devid

Specifies the device ID of the logical volume. This parameter is mandatory if the logical volume does not have an assigned storID.

It may be specified additionally for logical volumes with an assigned storID. If both storID and device ID are specified, the input must be consistent.

–system sysname

Specifies the name of the storage system. This parameter must be specified if the -deviceid parameter is used to specify the volume.

–newpoolid poolid

Specifies the target storage pool to which the logical volume should be moved by its pool ID. The current storage pool is implicitly specified by the storID or the device ID of the logical volume. Both storage pools must belong to the same storage system.

–newstorid storid

If specified, renames the storID of the logical volume to the specified value. Refer to the common description of storid on page 59.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server14 STORMAN_STORAGE_LOCKED Storage unit to be modified currently locked. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object (Storage Volume) could not be provided.19 STORMAN_STORID_IN_USE StorID already used otherwise 20 STORMAN_ALREADY_EXISTS Object already exists in the repository 22 STORMAN_RESOURCE_NOT_





7.2.5.3 storcfg volume –rem

Removes a logical volume from a storage pool of StorMan repository.

Syntax

storcfg volume –rem [ –storid storid ] { [ –deviceid devid ] } [ –system sysname ] –connectparam ...

Parameters

–storid storid

This parameter is mandatory for logical volumes with an assigned storID. Wildcards (*) are supported.

For logical volume without assigned storID, the parameter must be omitted and the -deviceid parameter must be specified instead.

–deviceid devid

Specifies the device ID of the logical volume. This parameter is mandatory if the logical volume does not have an assigned storID.

The logical volume specified by its device ID must already be contained in a storage pool.

–system sysname

Specifies the name of the storage system. This parameter must be specified if the -deviceid parameter is used to specify the volume.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server14 STORMAN_STORAGE_LOCKED Storage unit to be modified currently locked. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 19 STORMAN_STORID_IN_USE StorID already used otherwise 20 STORMAN_ALREADY_EXISTS Object already exists in the repository 22 STORMAN_RESOURCE_NOT_



7.2.5.4 storcfg volume –show

Displays information related to logical volumes.

Selection criteria can be specified using the function parameters.

Syntax

storcfg volume –show [ –storid storid ] [ –poolid poolid ] [ –system sysname ] [ –restype restype ] [ –minsize minsize ] [ –maxsize maxsize ] [ –vendor vendor ] [ –model model ] [ –hostname hostname ] [ –hostip ip ] [ –hostwwpn wwpn ] [ –conntype conntype ] [ –access access ] [ –targetostype ostype ] [ –format format ] –connectparam ...

Parameters

–storid storid

Specifies the storID for the logical volume (default: *). Wildcards (*) are supported.

–poolid poolid

Specifies the ID of a storage pool the logical volume belongs to (default: *). Wildcards (*) are supported.

–system sysname

Specifies the system name of the storage system the logical volume belongs to (default: *). Wildcards (*) are supported.

–restype restype

Selects by the type of logical volume. Supported values: predefined | dynamic | any (default)

–minsize minsize

Selects by the minimum size of the logical volume in MB (default: no restriction).

–maxsize maxsize

Selects by the maximum size of the logical volume in MB (default: no restriction).

–vendor vendor

Selects by the vendor of the storage system. Supported values: emc | fsc | netapp | any (default).

–model model

Selects by the model of the storage system. Supported values: symmetrix | clariion | fibrecatsx | netappfiler | any (default).

–hostname hostname

Selects by the name of the host the storID of is attached to (default: *). Wildcards (*) are supported.

–hostip ip

Selects by the IP adress of the host the storID of is attached to (default: *). Wildcards (*) are supported.

–hostwwpn wwpn

Selects by the WWPN of the host port the storID of is attached to (default: *). Wildcards (*) are supported.


Selects by the connection type of the storage system. Supported values: san | any (default)


–access access

Selects by the host access to the storage system. Supported values: exclusive | shared | any (default).

–targetostype ostype

Selects by the operating system type of the provisioned host, for NetApp FAS storage systems only. Supported values: local | windows | linux | solaris | any (default)

–format format






–connectparam


To display all logical volumes (even if they are not managed by StorMan) of a storage system you have to specify exactly one system using the –system parameter and specify –storid without a value. All other parameters are ignored in this case.

Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server14 STORMAN_STORAGE_LOCKED Storage unit to be modified currently locked. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 22 STORMAN_RESOURCE_NOT_


Examples

a) Output for logical volumes with –format std (default)

storcfg volume –show –poolid ralf*

storID = SM_803 poolID = Ralf_368 storage system name = Symmetrix+000287400368 device ID = 10FD GUID = 600604800002874003684D4158303033 storage size = 3264000KB resource type = STORMAN_RESOURCE_TYPE_PREDEFINED storage type = STORMAN_STORAGE_TYPE_SAN storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_SYMMETRIX allowed access = STORMAN_ACCESS_MODE_ANY current access = STORMAN_ACCESS_MODE_EXCLUSIVE target OS = STORMAN_OS_ANY


host connections host ID type = STORMAN_HOSTID_TYPE_NAME host ID = storman1 WWPN connections host WWPN = 210000C09F9DF5C0 storage connections host device number = 0 storage WWPN = 5006048448586C03 host WWPN = 210000C09F9DF5C1 storage connections host device number = 0 storage WWPN = 5006048448586C03 host ID type = STORMAN_HOSTID_TYPE_WWPN host ID = 200000C09F9DF5F6 WWPN connections host WWPN = 200000C09F9DF5F6 storage connections host device number = 0 storage WWPN = 5006048448586C03 storID = SM_864 poolID = Ralf124 storage system name = CLARiiON+CK200041600124 device ID = 0004 GUID = 6006016049910A00BABE92EE90E1D911 storage size = 6144B resource type = STORMAN_RESOURCE_TYPE_PREDEFINED connection type = STORMAN_STORAGE_TYPE_SAN storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION allowed access = STORMAN_ACCESS_MODE_EXCLUSIVE current access = STORMAN_ACCESS_MODE_NONE target OS = STORMAN_OS_ANY no host connections found storID = poolID = Ralf124 storage system name = CLARiiON+CK200041600124 device ID = 0031 GUID = 6006016038A00A00D904E75F6BE2D911 storage size = 292969B resource type = STORMAN_RESOURCE_TYPE_PREDEFINED connection type = STORMAN_STORAGE_TYPE_SAN storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION allowed access = STORMAN_ACCESS_MODE_ANY current access = STORMAN_ACCESS_MODE_NONE target OS = STORMAN_OS_ANY no host connections found

b) Output for logical volumes with –format xmlp

storcfg volume –show –poolid ralf* -format xmlp <StorageDescriptions> <storID>SM_803</storID> <poolID>Ralf_368</poolID> <storageSystemName>Symmetrix+000287400368</storageSystemName> <GUID>600604800002874003684D4158303033</GUID> <deviceID>10FD</deviceID> <size>3264000</size> <sizeType>STORMAN-SIZE-TYPE-KB</sizeType> <connectionType>STORMAN-STORAGE-TYPE-SAN</connectionType> <storageVendor>STORMAN-STORAGE-VENDOR-EMC</storageVendor> <storageModel>STORMAN-STORAGE-MODEL-SYMMETRIX</storageModel> <resourceType>STORMAN-RESOURCE-TYPE-PREDEFINED</resourceType> <allowedAccess>STORMAN-ACCESS-MODE-ANY</allowedAccess> <currentAccess>STORMAN-ACCESS-MODE-EXCLUSIVE</currentAccess> <targetOS>STORMAN-OS-ANY</targetOS>


<hostConnections> <hostIDType>STORMAN-HOSTID-TYPE-NAME</hostIDType> <hostID>storman1</hostID> <deviceConnections> <hostWWPN>210000C09F9DF5C0</hostWWPN> <storageConnections> <hostDeviceNumber>0</hostDeviceNumber> <storageWWPN>5006048448586C03</storageWWPN> </storageConnections> </deviceConnections> <deviceConnections> <hostWWPN>210000C09F9DF5C1</hostWWPN> <storageConnections> <hostDeviceNumber>0</hostDeviceNumber> <storageWWPN>5006048448586C03</storageWWPN> </storageConnections> </deviceConnections> </hostConnections> <hostConnections> <hostIDType>STORMAN-HOSTID-TYPE-WWPN</hostIDType> <hostID>200000C09F9DF5F6</hostID> <deviceConnections> <hostWWPN>200000C09F9DF5F6</hostWWPN> <storageConnections> <hostDeviceNumber>0</hostDeviceNumber> <storageWWPN>5006048448586C03</storageWWPN> </storageConnections> </deviceConnections> </hostConnections> </StorageDescriptions> <StorageDescriptions> <storID>SM_864</storID> <poolID>Ralf124</poolID> <storageSystemName>CLARiiON+CK200041600124</storageSystemName> <GUID>6006016049910A00BABE92EE90E1D911</GUID> <deviceID>0004</deviceID> <size>6144</size> <sizeType>STORMAN-SIZE-TYPE-B</sizeType> <connectionType>STORMAN-STORAGE-TYPE-SAN</connectionType> <storageVendor>STORMAN-STORAGE-VENDOR-EMC</storageVendor> <storageModel>STORMAN-STORAGE-MODEL-CLARIION</storageModel> <resourceType>STORMAN-RESOURCE-TYPE-PREDEFINED</resourceType> <allowedAccess>STORMAN-ACCESS-MODE-EXCLUSIVE </allowedAccess> <currentAccess>STORMAN-ACCESS-MODE-NONE</currentAccess> <targetOS>STORMAN-OS-ANY</targetOS> </StorageDescriptions> <StorageDescriptions> <storID></storID> <poolID>Ralf124</poolID> <storageSystemName>CLARiiON+CK200041600124</storageSystemName> <GUID>6006016038A00A00D904E75F6BE2D911</GUID> <deviceID>0031</deviceID> <size>292969</size> <sizeType>STORMAN-SIZE-TYPE-B</sizeType> <connectionType>STORMAN-STORAGE-TYPE-SAN</connectionType> <storageVendor>STORMAN-STORAGE-VENDOR-EMC</storageVendor> <storageModel>STORMAN-STORAGE-MODEL-CLARIION</storageModel> <resourceType>STORMAN-RESOURCE-TYPE-PREDEFINED</resourceType> <allowedAccess>STORMAN-ACCESS-MODE-ANY</allowedAccess> <currentAccess>STORMAN-ACCESS-MODE-NONE</currentAccess> <targetOS>STORMAN-OS-ANY</targetOS> </StorageDescriptions>


7.3 storcreate Reserves a new storage volume from a storage pool or creates a new volume in the storage systems as specified by the caller or defined by the attributes of the specified storage pool.

Syntax

storcreate –storid storid [ –poolid poolid ] [ –system sysname ] –size size [ –restype restype ] [ –access access ] [ –vendor vendor ] [ –model model ] [ –targetostype ostype ] [ –timeout timeout ] –connectparam ...

Parameters

–storid storid

Specifies the storID as the unique identifier to be assigned to the new logical volume for further management by StorMan. This parameter is mandatory.

Refer to the common description of storid on page 59.

–poolid poolid

Specifies the ID of a storage pool the logical volume should be reserved or created for (default: *). Wildcards (*) are supported.

If the specified pool ID does not exist in the repository, the command is rejected.

–system sysname

Specifies the system name of the storage system the logical volume should be reserved or created for (default: *). Wildcards (*) are supported.

If both –poolid and –system are specified, the information must be consistent (the specified storage pool(s) must be part of the specified storage systems), otherwise the command is rejected.

–size size

Specifies by the minimal size of the logical volume in MB. This parameter is mandatory.

–restype restype

Specifies the type of logical volume. Supported values: predefined | dynamic | any (default)

–access access

Specifies the required type of access mode for the requested volume. Supported values: exclusive | shared | any (default). If the value any is specified, the access type of the pools from which a volume could be reserved is ignored.

–vendor vendor

Specifies the vendor of the storage system. Supported values: emc | netapp | any (default).

–model model

Specifies the model of the storage system. Supported values: symmetrix | clariion | netappfiler | any (default).


–targetostype ostype

Specifies the required target operating system type for the requested volume. This value is currently a special option for Network Appliance filers and therefore interpreted only if -vendor netapp is specified. Permitted values: local | windows | linux | solaris | any (default).

The value local sets up the local operating system type performing the storcreate function (i.e. the StorMan Client).

The value any sets up the value of DefaultTargetOSType specified in the smserver.ini file.

–timeout timeout

Specifies the timeout in seconds if a volume is created dynamically. The default value is specified in the smserver.ini file. If the value 0 is specified, no timeout will be used.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 8 STORMAN_INVALID_STORID Specified store ID not allowed. 9 STORMAN_STORID_IN_USE Store ID already use otherwise. 11 STORMAN_NO_STORAGE_FOUND Matching storage could not be provided, i.e.

if –restype dynamic: not enough space left in the storage system, if –restype predefined: no volume with the requested properties (size) available

13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.14 STORMAN_STORAGE_LOCKED Storage unit currently locked. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND Matching object could not be provided. 21 STORMAN_FCT_NOT_POSSIBLE Function could not be performed. 22 STORMAN_RESOURCE_NOT_


24 STORMAN_CFG_CHANGE_ FAILED

Volume creation was initialized but rejected by the storage system




7.4 storattach Makes a storage volume visible for a host using the LUN masking capabilities of the storage system.

Syntax

storattach –storid storid [ –hostname hostname ] [ –hostip ip ] [ –hostwwpn wwpn ] [ –hostlun lun ] –connectparam ...

Parameters

–storid storid

Specifies the previously assigned storID as unique identifier. This parameter is mandatory.


Specifies name of the server to be provisioned with storage (attached).

–hostip ip

Specifies the IP address of the server to be provisioned with storage (attached).

–hostwwpn wwpn

Specifies the server’s HBA WWPN which the device should be attached to.

–hostlun lun

Specifies the device number that can be seen by the host. Possible values: 0..255; e.g. –hostlun 128. If this parameter is not specified, one is assigned by the storage system.

This parameter is not yet supported by all storage systems. If a SCSI host LUN is specified, make sure that this number is not already used for another device on the same host via the same storage ports – otherwise STORMAN_INV_PARAMETERS will be returned.

This parameter not yet supported for Symmetrix systems (and rejected with STORMAN_FCT_NOT_POSSIBLE). In a Symmetrix system (up to Enginuity 5771), the host LUN number is only defined by the mapping of the volume.

–connectparam


Note

• -storid must be specified to specify the storage unit.

• One of the parameters hostname, hostip or hostwwpn must be specified to specify the host exactly. If hostname or hostip is specified, StorMan must have the necessary information to determine the WWPNs of the host (e.g. supplied with storcfg host in its internal repository) and the storage is attached to all known host ports.

• If the host specification is redundant, i.e. as a result of –hostname and / or –hostip and / or -hostwwpn, the specified parameters must be consistent.


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 1 STORMAN_NO_ACTION Nothing to do. 2 STORMAN_NOT_COMPLETE Function only partly completed. 3 STORMAN_VER_NOT_SUPP Version not supported 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 10 STORMAN_STORID_NOT_FOUND StorID does not yet exist. 12 STORMAN_INV_ACCESS_MODE Specified access mode not allowed or incompatible. E.g.

a volume from a pool with access-mode=shared should be attached to more than one host.

13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.14 STORMAN_STORAGE_LOCKED Storage unit currently locked. 16 STORMAN_FAULT Unexpected error in function. 18 STORMAN_NOT_FOUND No wwpn for the specified host was found in the

repository. 22 STORMAN_RESOURCE_NOT_


23 STORMAN_BAD_CONFIG Illegal LUN masking configuration found in a ClariiON system or mapping and masking do not fit in a Symmetrix (see 5.1.2 for details).




7.5 stordetach Disconnects a storage volume from a host using the LUN masking / unmasking capabilities of the storage system. The storage volume is no longer visible to the host.

Syntax

stordetach –storid storid [ –hostname hostname ] [ –hostip ip ] [ –hostwwpn wwpn ] [ –destroyConnection ] –connectparam ...

Parameters

–storid storid

Specifies the assigned storID as unique identifier. This parameter is mandatory.


Specifies name of the server to be detached from storage.

–hostip ip

Specifies the IP address of the server.

–hostwwpn wwpn

Specifies the WWPN of the server’s HBA which the device should be detached from.

–destroyConnection

Setting this parameter causes the connection between a HBA and a storage port to be destroyed after detaching the last storage volume from this specific host or HBA. Default: Parameter not set.

Setting this parameter is useful if the host will no longer use this connection to the storage array. Normally the parameter should be set to false (not set). See section 5.1.4 for more details.

–connectparam


Note

• -storid must be specified to specify the storage unit.

• Exactly one of the parameters -hostname, –hostip or –hostwwpn must be specified to specify the host . If –hostname or –hostip is specified, StorMan must have the necessary information to determine the WWPNs of the host (e.g. supplied with storcfg host in its internal repository) and the storage is attached to all known host ports.

• If the host specification is redundant, i.e. as a result of –hostname and / or –hostip and / or -hostwwpn, the specified parameters must be consistent.


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 1 STORMAN_NO_ACTION Nothing to do. 2 STORMAN_NOT_COMPLETE Function only partly completed. 3 STORMAN_VER_NOT_SUPP Version not supported 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 10 STORMAN_STORID_NOT_FOUND StorID does not yet exist. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.14 STORMAN_STORAGE_LOCKED Storage unit currently locked. 16 STORMAN_FAULT Unexpected error in function. 22 STORMAN_RESOURCE_NOT_


23 STORMAN_BAD_CONFIG Illegal masking configuration found (Clariion). See section5.1.2 for details.




7.6 stordelete

Releases a reserved device (i.e. one with a storID). If the storage volume is still attached to a host, the command will be rejected.

For a predefined device, normally only the storID will be removed from the StorMan repository. The storage volume may be reserved again by a subsequent storcreate command. A dynamically created device will normally be removed from the StorMan repository and destroyed in the storage system. This standard behavior can be changed with the mode parameter.

Syntax

stordelete –storid storid [ –mode mode ] –connectparam ...

Parameters

–storid storid

Specifies the assigned storID as unique identifier. This parameter is mandatory.

–mode mode

Sets up the behavior of the function. Supported values: std (default) | keep | destroy

The default value std sets up normal behavior as described above. If keep is specified, the storID is cleared and the device remains in the storage pool and in the storage system. The value destroy destroys the device in the storage system and in the storage pool.

i

If –mode destroy is set, the volume (logical device) is completely removed and all data stored on that volume is lost.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 2 STORMAN_NOT_COMPLETE Function only partly completed. 3 STORMAN_VER_NOT_SUPP Version not supported. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 10 STORMAN_STORID_NOT_FOUND StorID does not yet exist. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.14 STORMAN_STORAGE_LOCKED Storage unit currently locked. 15 STORMAN_STORAGE_ATTACHED No release because storage unit still attached. 16 STORMAN_FAULT Unexpected error in function. 21 STORMAN_FCT_NOT_POSSIBLE Function not supported. 22 STORMAN_RESOURCE_NOT_





7.7 stormandb Saves or restores the StorMan repository. This command is only supported on the StorMan Server.

i

stormandb is not a StorMan Client command. It is an administrative command only available on the StorMan Server.

For Linux systems it is only available when you are logged in on the StorMan Server with the storman userID. This userID (usually storman) can be found in the /opt/SMAW/SMAWstor/StorMan/userInfo file.

Syntax

stormandb { –dump | –load } [–noserver] –connectparam

Parameters

–dump

Selects the backup function. The StorMan repository will be saved to the folder backup of the StorMan directory.

–load

Selects the restore function. The StorMan repository will be restored from the backup folder of the StorMan directory.

If this parameter is used to restore the StorMan repository after installing a new version of StorMan, StorMan has to be restarted because the format of the database may have changed.

–noserver

Setting this parameter the command will work directly on the repository. Make shure there is really no server working with the repository and no concurrent stormandb command is running because else the repository may be corrupted.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.16 STORMAN_FAULT Unexpected error in function.


7.8 storcheck Checks the availability of the StorMan Server. The check covers the availability of the StorMan Server itself, its database, and optionally if at least one of the configured CIM-OMs is reachable.

The result message of the check is directed to stdout and the exit code is set (see return codes below).

Syntax

storcheck [ –timeout timeout ] [ –ignorecimom ] –connectparam ...

Parameters

– timeout timeout

Specifies a timeout value in seconds the command waits for a response of the checked CIM-OM. Default: 60 seconds.

– ignorecimom

Specifies whether the availability of the configured CIM-OM’s is checked.

Omitting this parameter (default) causes the command to check the availability of the configured CIM-OM.

Setting this parameter causes the command to skip the checks for the availability of the configured CIM-OM’s This is useful in configurations where the availability of CIM-OM can be checked separately.

–connectparam


Return codes

Exit code Message Meaning 0 Ok Everything OK 1 StorMan not reachable The StorMan Server is not reachable 2 No Database The StorMan Server is running but the database has

failed 3 No CIM-OM The StorMan Server is running and the database is up

but no CIM-OM is reachable 7 Invalid parameters Specified parameters invalid


7.9 storparam Modifies the settings for the StorMan Server without restarting it. All settings are valid for the current StorMan Server session. They can optionally be maintained persistent for further sessions.

Syntax

storparam { –show | [ –debug level ] [ –debugcom comopt ] [ –cimtimeout timeout ] [ –createtimeout timeout ] [ –statusrefreshtime refreshtime ] [ –defaulttargetostype ] [ –save ] } –connectparam ...

Parameters

–show

Shows the settings of the StorMan Server.

–debug level

Sets the debug level of the server. Supported values: 0 Trace severe errors only 1 Trace errors too 2 Trace even warnings 3 Trace information 4 Trace debug (default) 5 Trace extended debug

–debugcom comopt

Sets the debug option for communication (only active if the overall debug level is 5). Supported values: 0 Trace off (default) 1 Trace tcp / ip calls 2 Trace messages 3 Trace all

–cimtimeout timeout

Specifies the timeout for the CIM-OM connection (in seconds). Default: 600 seconds.

–createtimeout timeout

Specifies the timeout for the creation of a volume. Default: unlimited. Any value lower than or equal to 0 is interpreted as unlimited.

–statusrefreshtime refreshtime

Sets the time interval between two status refresh function cycles. Default: 60 seconds. Any negative value switches the refresh function off.

This function is only required to support the Information and Monitoring features (e.g. for ServerView integration).

You are strongly recommended to set a negative value (e.g. -1) in configurations without ServerView.

–defaulttargetostype

Sets the default value for the target operating system type for dynamic LUN creation using the storcreate function. This value is only interpreted for filers of Network Appliance Inc.

Supported values: local | windows | linux | solaris

The value local sets up the local operating system type of the StorMan Server.


–save

Saves the currently specified parameter values to the file smserver.ini to be preserved for subsequent sessions (restart of StorMan Server).

–connectparam


Return codes

Error Code Message Meaning 0 STORMAN_OK Function successful. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.16 STORMAN_FAULT Unexpected error in function.


7.10 storinfo Provides information about StorMan.

Syntax

storinfo –version –connectparam ...

Parameters

–version

Displays the version and build of the local system and (if one is specified) of a server.

–connectparam


Return codes

Error Code Message Meaning 0 STORMAN_OK Function successful. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server.16 STORMAN_FAULT Unexpected error in function.


7.11 storemc Provides vendor-specific functions to add / remove EMC storage systems to / from the EMC SMI-S Provider’s database. This function can be used to handle FibreCAT CX or CLARiiON CX systems with no FibreChannel connection to the host running the SMI-S Provider (CIM-OM). These so-called “out-of-band” storage systems are not discovered automatically using storcfg cimom –discover but have to be added manually using storemc.

storemc –function –functionparam ... –connectparam ...

Functions


–add

adds a CLARiiON CX or FibreCAT CX storage system to the StorMan repository and the SMI-S Provider’s repository

–rem

removes a CLARiiON CX or FibreCAT CX storage system from an MI-S Provider’s repository

7.11.1 storemc –add

Adds a CLARiiON CX or FibreCAT CX storage system to the StorMan repository and the SMI-S Provider’s repository. The system is specified by the -sp parameter as described below. The specified CIM-OM must be contained in the repository of StorMan and clearly defined by its hostname / ip address and the port (see “storcfg cimom –add” in section 7.2.2.1.).

Syntax

storemc –add [ –hostname hostname ] [ –hostip ip ] [ –http port ] [ –cimuser user ] [ –cimpwd pwd ] –sp sp[,...] –cxuser user –cxpwd pwd –connectparam ...

Parameters


Specifies the name of the host the CIM-OM is running on which will be directed to discover the specified storage system.

–hostip ip

Specifies the IP address of the host the CIM-OM is running on.

–http port

Specifies the port the CIM-OM is listening on (default: 5988).

–cimuser user

Specifies the user for the CIM-OM connection (default: none). Mandatory if the CIM user requires authentication.

–cimpwd pwd

Specifies the password for the CIM-OM connection (default: none). Mandatory if the CIM user requires authentication.


–sp sp[,...]

Specifies a list of netnames or IP addresses of both storage processors (SPs) of the CLARiiON CX / FibreCAT CX array delimited by comma. Make sure that SPs are specified in the correct order: The first name / address must be SP-A and the second SP-B, otherwise the function does not work.

–cxuser user

Specifies a valid userID on the CLARiiON CX / FibreCAT CX (or the CLARiiON CX / FibreCAT CX domain) with administrator or manager privilege.

–cxpwd pwd

Specifies the password for the userID on CLARiiON CX / FibreCAT CX.

–connectparam


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 22 STORMAN_RESOURCE_NOT_


21 STORMAN_FCT_NOT_POSSIBLE Function refused by SMI-S Provider. 25 STORMAN_CIMOM_AUTH_

FAILED User / password for CIM Server not valid.

i

In High availability configurations i.e. if more than one CIM Server / SMI-S Provider can manage the same storage system, it is necessary to run this command for each CIM Server.


7.11.2 storemc –rem

Removes an CLARiiON CX / FibreCAT CX storage system from an EMC SMI-S Provider’s repository. The system is specified by its serial number as delivered by the storcfg system –show command (e.g. “CLARiiON+ck200024200100”).

Syntax

storemc –rem [ –hostname hostname ] [ –hostip ip ] [ –http port ] –system serialnum [ –cimuser user ] [ –cimpwd pwd ] –connectparam ...

Parameters


Specifies the name of the host the CIM-OM is running on which the storage system is removed from the SMI-S Provider’s repository.

–hostip ip

Specifies the IP address of the host the CIM-OM is running on.

–http port

Specifies the port the CIM-OM is listening on (default: 5988).

–system serialnum

Specifies the serial number of the storage system that is contained in the StorMan repository.

–cimuser user

Specifies the user for the CIM-OM connection (default: none). Mandatory if the CIM user requires authentication.

–cimpwd pwd

Specifies the password for the CIM-OM connection (default: none). Mandatory if the CIM user requires authentication.

–connectparam


If a CIM Server is specified by its hostname as described above, the system will be removed from the repository of this CIM Server only.

If no CIM Server is specified, the storage system will be removed from the repositories of all CIM Servers that actually have access to this system. This command is useful if a storage system is physically removed or if a storage system should be managed by another CIM Server.

If no CIM Server is specified, it is necessary that all CIM Servers related to the system are contained in the StorMan database with matching user and password for die CIM-OM connection (–cimuser and -cimpwd). If a system should be removed completely from StorMan’s repository, use storcfg system –rem as described in section 7.2.3.1.


Return codes

Error Code Name Error Type 0 STORMAN_OK Function successful. 1 STORMAN_NO_ACTION No CIM Server for this system was found. 2 STORMAN_NOT_COMPLETE If no CIM Host was specified, the remove function could

not be performed for all CIM Hosts, e.g. because not all are running.

7 STORMAN_INV_PARAMETERS Specified parameters invalid. 13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client & server16 STORMAN_FAULT Unexpected error in function. 22 STORMAN_RESOURCE_NOT_


21 STORMAN_FCT_NOT_POSSIBLE Function refused by SMI-S Provider. 25 STORMAN_CIMOM_AUTH_

FAILED User / password for CIM Server not valid.


8 StorMan for programmers – StorMan Client interface for information and monitoring

This chapter is an introduction to the StorMan features related to StorMan information and monitoring functions that are all provided on a C++ interface level and are required for integration with server management software. Currently this interface is only used by other products of Fujitsu Siemens Computers (in particular ServerView). It is not released for general use.

General

The interfaces consist of a class (C++) with methods to connect to StorMan Server and to retrieve information about storage systems and to describe the retrieved information.

As of StorMan V1.3, these interfaces are supported for FibreCAT SX and FibreCAT CX storage arrays of Fujitsu Siemens Computers and for CLARiiON CX storage arrays of EMC Corporation only.

To provide these features, the StorMan Server addresses the SMI-S Provider directly to retrieve the information. The retrieved information is not maintained in the StorMan repository; it is passed directly to the caller of the client interface.

The StorMan repository is required to maintain the information related to the SMI-S Providers and CIM Servers only.

Addtionally and to improve the integration support the StorMan repository can be used to maintain the information about the relationship between hosts and their HBA and WWPN information.

The StorMan Client Interface allows another process to connect to a StorMan Server process and to get information about accessible storage systems. The information delivered is structured in XML syntax. The Interface is a C++ class. A header file has to be added to caller’s C++ program code to use this interface.

Example

A CGI process may use the StorMan Client Interface:

CGI process StorMan Server storage systems

The interface provides:

• methods to connect to a StorMan Server.

• methods to get overall and specific information about storage systems.

In detail, the public methods are Connect, GetSystems, Get, GetAll and GetLastErrorMsg. The retrieval of information starts after a successful call of Connect with a GetSystem call that delivers references for calls of Get or GetAll in an XML document.


9 Appendix

9.1 Fujitsu Siemens Computers: Software License Agreement for End Users

1. Subject of this Agreement 1.1 For the purposes of this agreement “Software” shall mean the software with the object code, the version and the specification indicated in the software product data sheet of Fujitsu Siemens Computers.

The Software consists of machine-readable instructions and/or printed documentation and related licensed materials.

1.2 Please read this agreement carefully before you use the Software. If you do not agree with the license terms in this agreement, you are not permitted to use the Software and must immediately return all copies of the Software and all accompanying items to the Licensor/Sublicensor (either Fujitsu Siemens Computers or the reseller who supplied you with the Software) with proof of purchase for a full refund.

1.3 Any use of the Software requires the proper payment of the applicable license fees. By using the Software you agree to be bound by the terms of this agreement.

1.4 Fujitsu Siemens Computers reserves the right to implement at any time in the future an additional software license key and/or license certificates as countermeasures against software piracy.

1.5 Software components from third-party software suppliers which are part of the scope of the delivery are subject to separate license agreements that are included with the Software or that are transmitted by Fujitsu Siemens Computers upon request.

2. End User License 2.1 Fujitsu Siemens Computers grants you a non-exclusive and non-transferable license to use the Software on the number of workstations for which you have purchased licenses. Unless you purchase additional licenses, you are not permitted to operate the Software on more than the maximum number of licensed workstations or on hardware that exceeds the specified type.

You are permitted to make a backup copy of the Software for archiving purposes, provided you properly mark the copy or partial copy of the Software with the copyright notice and any other ownership information.

2.2 You are not permitted to copy, modify or distribute the Software. Furthermore, you are not permitted to re-compile, re-engineer, convert, revise, compile or modify the Software. You may not sub-license, without selling the related hardware, assign, rent, lease or transfer the Software except as expressly permitted by this agreement or due to mandatory legal regulations.

2.3 If you acquired the Software as a program upgrade, your license for the use of the old software version ends automatically with the installation of the upgrade version of the Software. If parts of the old software version are not replaced by the upgrade version, the license for the old version continues to be effective until the remnants of the old software version are also replaced or deactivated or shut down in any other way.

2.4 Unless specified otherwise in the respective software data sheet of Fujitsu Siemens Computers, the license for a software version or release does not give you any rights to new releases (updates), new versions (upgrades) or technical support services for the Software. Supplemental software support contracts and maintenance services, including or excluding new releases and new versions and additional technical support services, can be purchased separately either from Fujitsu Siemens Computers directly or from authorized software resellers.

3. Downloading For Software supplied by Fujitsu Siemens Computers over a network or a similar distribution path, the following additional conditions shall apply: All products supplied for downloading by Fujitsu Siemens Computers are selected, made available and —


if supplied by third parties — provided without modification. However, you are fully responsible for ensuring the most current version and usability of downloadable material for your own purposes and on your own system. You download Software at your own risk. Fujitsu Siemens Computers will not accept any liability, particularly not for transmission errors or problems that arise during the downloading process (line failures, connection interruptions, server failures, data corruption, etc.).

The website of Fujitsu Siemens Computers is operated and administered only for those countries in which Fujitsu Siemens Computers has one or more offices. Fujitsu Siemens Computers accepts no responsibility that Software and/or documentation can or may be downloaded from a Fujitsu Siemens Computers website also in locations other than the countries mentioned above. If you access an FSC website from abroad, you are fully responsible for complying with any local regulations. Fujitsu Siemens Computers expressly prohibits the downloading of Software and/or documentation from a Fujitsu Siemens Computers website in countries where such downloading is considered illegal.

4. Copyright All rights and licenses, unless they are expressly granted to you in this license terms, as well as all property and usage rights related to the Software (including parts of the Software) remain fully with Fujitsu Siemens Computers and/or its third-party licensors.

The license terms do not authorize you to use the brands, logos or trademarks of Fujitsu Siemens Computers or its third-party licensors, nor are you permitted to use any other brands which are deceptively similar to the brands, logos or trademarks of Fujitsu Siemens Computers. Each and any use of brands, logos or trademarks with respect to the Software or Fujitsu Siemens Computers requires the express consent of Fujitsu Siemens Computers

5. Licensor’s warranty and liability disclaimer, if Software is sold and delivered by Reseller If you acquire the Software directly from an authorized reseller (called “Reseller”), the right to install and use the Software may be subject to additional software license conditions agreed upon between you as the licensee and the respective reseller.

In all cases of an authorized software resale, the software is sublicensed and made available to the licensee directly by the Reseller. In such cases, Fujitsu Siemens Computers is not a contractual party of the software license agreement between you, as licensee and the Reseller, as far as the procurement of the software licenses are concerned. Legal claims in connection with the software licensing can therefore be asserted only on the basis of the agreements with the Reseller. Under no circumstances, however, will the respective scope of the license for the licensee exceed the scope of the license agreements as specified in sections 1, 2, 3 and 4 of this agreement.

Subject to mandatory legal regulations, particularly those governing liability and/or warranties, which cannot be excluded in connection with end user license agreement regulations and with reference to the licensee’s claims against the Reseller, Fujitsu Siemens Computers disclaims all warranties for the Software in this agreement. For the same reason, Fujitsu Siemens Computers disclaims any and all liability/claims for any violations of third parties’ rights as well as any implied warranties for the software’s marketability and its suitability for a particular purpose. This disclaimer of liability does not apply in cases of willful or malicious behavior by Fujitsu Siemens Computers.

In this End User License Agreement, Fujitsu Siemens Computers grants no warranties of any kind, either express or implied.

6. Disclaimer of liability with respect to shareware, freeware and/or open source software components 6.1 The Software may contain freeware or shareware which Fujitsu Siemens Computers received from a third party. Fujitsu Siemens Computers paid no license fees for the use of this freeware or shareware. Accordingly, the licensee is not charged any license fees for the use of the freeware or shareware. You recognize and accept that Fujitsu Siemens Computers therefore grants no warranties with respect to such freeware or shareware components and does not assume any liability in connection with the ownership, the distribution and/or the use of the respective freeware or shareware.

6.2 The Software may also contain open source software components that were developed according to the “open source model” and which are distributed exclusively on the basis of the GPL (General Public License: http://www.gnu.org/copyleft/gpl.html) terms and conditions or other standard open source standard license terms and conditions applicable to the respective open source components at the time of their dissemination. You recognize and accept that the licensing of such open source software components is governed exclusively by the above-mentioned GPL terms or by the conditions which are otherwise included with the open source software components. Fujitsu Siemens Computers receives neither license fees nor any other compensation for the delivered open source software components. As

http://www.gnu.org/copyleft/gpl.html


far as Fujitsu Siemens Computers or a third party receives any compensation in connection with open source software components, it is received exclusively for additional delivery items and/or services.

Because of the special nature of the development and distribution of open source software components, Fujitsu Siemens Computers assumes no express or implied liability for such components and excludes any kind of warranty for such open source software components, particularly in connection with missing specifications, lack of functionality, programming errors or any other malfunctions.

7. General limitations of liability 7.1 Neither Fujitsu Siemens Computers nor its suppliers are liable for any consequential or indirect damages, including damages arising as a result of or in connection with an operational interruption, lost profits or sales, lost data, or costs of capital. Fujitsu Siemens Computers and its suppliers will not be liable for additional ancillary or consequential costs or for any other losses, costs or expenses of any kind which arise as a result of the holding, sale, use or impossibility of use of the Software, independent of whether such claims are asserted due to warranty rights, contracts, tort or any other legal theory.

7.2 The liability of Fujitsu Siemens Computers for direct damage caused as a result of a contract violation and/or other action or lapse on the part of Fujitsu Siemens Computers which have not been excluded or cannot be completely excluded due to mandatory law are limited to no more than €250,000.00. Any and all other liabilities for direct damage are excluded. Damage caused by Fujitsu Siemens Computers as a result of slight negligence are excluded to the extent permitted by applicable legal regulations.

7.3 Limitations and exclusions of liability resulting from this agreement do not apply to damage where Fujitsu Siemens Computers carries compulsory liability according to applicable laws and where such liability cannot be limited to a maximum amount (for example, liability for bodily damage; product liability or fraudulently incorrect information).

8. Export controls Due to its components as well as the nature or purpose of these components, the export of the Software and/or its accompanying documents may be subject to official or regulatory approval. In cases where the Software is intended for export, you are obliged to get all approvals and authorizations required to comply with all relevant export regulations.

The Software may not be exported if there is reason to assume that the Software will be used in connection with nuclear, chemical or biological weapons or for missile technology. Furthermore, you may not deliver the Software — or have it delivered indirectly — to such companies or persons who are listed in the applicable U.S. export regulations (particularly the Table of Denial Orders/U.S. Denied Persons Lists (DPL) or in the E.U. export regulations (particularly the EU Terrorist List) or in the applicable warnings issued by the German export authorities or any other competent authorities in any country.

Under no circumstances is Fujitsu Siemens Computers obligated to deliver software, patches, updates or upgrades, to provide software for download or to fulfill any other contractual commitments if this would be a violation of the applicable export regulations of the Federal Republic of Germany, the European Union, the United States of America or of any other countries.

If you export or re-export the Software or a copy of it, this may be a violation of applicable export laws and a severe violation of the terms of this agreement.

9. Miscellaneous 9.1 If any term or condition in this agreement or any other contract that is subject to the terms and conditions of this agreement turns out to be invalid or unenforceable (partly or in full), the validity of all other terms and conditions remains unaffected, unless complying with the remaining terms and conditions would represent an unreasonable hardship for either contract party, even with the application of applicable legal regulations to close the legal gap.

9.2 If you/ the licensee do not pay the license fees due and/or if the licensee does not comply with essential terms and conditions of this license agreement, Fujitsu Siemens Computers reserves the right to cancel the license. In case of such cancellation, you must immediately return any and all copies of the software in your possession and confirm the complete return [of the software copies] or the destruction of these copies in writing.

9.3 Neither you nor Fujitsu Siemens Computers is responsible or liable for the respective party’s non-compliance with its obligations if the reason for such non-compliance is outside the party’s control due to force majeure.


9.4 Any and all modifications and/or amendments to these license terms and conditions are only valid if they are made in writing.

10. Applicable law 10.1 These license terms and conditions are governed by the laws of the Federal Republic of Germany.

10.2 In the event that provisions of clause 10.1 are unenforceable, these license terms and conditions shall be governed by the laws of the country in which you acquire the Software, with the following exceptions: 1) In Australia, the terms and conditions of this license are governed by the laws of the state or sovereign territory in which the business contract is being concluded; 2) in Albania, Armenia, Belarus, Bosnia-Herzegovina, Bulgaria, Croatia, Kazakhstan, Kirgizia, the former Yugoslavian Republic of Macedonia (FYROM), Moldavia, Poland, Romania, Russia, Slovakia, Slovenia, the Ukraine and the Federal Republic of Yugoslavia, the terms and conditions of this license are governed by the laws of the Federal Republic of Germany; 3) in the United Kingdom [Great Britain], all disputes with respect to these license terms and conditions are governed by English law, and English courts have exclusive jurisdiction; 4) in Canada, the terms and conditions of this license are governed by the laws of the Province of Ontario; 5) in the United States of America and in Puerto Rico as well as in the People’s Republic of China the terms and conditions of this license are governed by the laws of the U.S. State of New York.

9.2 OpenSource licenses

9.2.1 OpenPegasus

See also: http://www.openpegasus.org

OpenPegasus Licensing

The Pegasus project uses the MIT open source license. This license was used to provide a minimum encumbrance on the code and allow maximum usage. This license applies to OpenPegasus code, OpenPegasus website content, and contributions to the OpenPegasus wiki.

The 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. Copyright (c) 2005 Hewlett-Packard Development Company, L.P.; IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group. Copyright (c) 2006 Hewlett-Packard Development Company, L.P.; IBM Corp.; EMC Corporation; Symantec 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 CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.



Glossary CIM / CIM-OM Common Information Model / Common Information Model Object Manager.

Client A computer system or process that requests a service of another computer system or process that is typically referred to as a server. Multiple clients can share access to a common server.

HBA Host Bus Adapter

Host A computer that is connected to the storage array through a fibre-channel interface.

Initiator Port Port (FC connection) of an HBA. A port that initiates IOs to or from a logical device. Opposite to target port.

IP address The unique 32-bit address that specifies the location of each device or workstation in the Internet. For example, 127.25.97.103 is an IP address.

JNLP Java Network Launching Protocol.

LUN Logical Unit Number.

LUN masking Selected visibility of specified LUNs of a FC connected storage array for an HBA.

Server In a network, the hardware or software that provides facilities to other stations; for example, a file server, a printer server, a mail server. The station making the request of the server is usually called the client.

SMI-S Storage Management Initiative Specification.

SNIA Storage Networking Industry Association.

Storage Pools A named collection of logical devices in the StorMan repository.

Storage volumes (devices) A volume is a fixed amount of storage on a disk. It is possible for a single disk to contain more than one volume or for a volume to span more than one disk.

StorMan Central and uniform storage management service for automatic storage provisioning.

Target Port FC term. Describes an FC port belonging to a storage system. FC logical devices (LUNs) can be targeted via one or more target ports. Opposite to initiator port.

URL Uniform Resource Locator.

VCM database Database that contains all LUN masking information in the form of VCM records on a Symmetrix System. The database is located on a VCM device.

VCM device Special device on a Symmetrix System that contains the VCM database.

VCM record A record of the VCM database that specifies the relationship between one initiator port, one target port and an amount of devices. Reflects the LUN masking settings in a Symmetrix system.


Web Server Full-service web servers act as HTTP servers. In addition, they have many other capabilities, such as running CGI scripts.

WWPN World Wide Port Number


Index AccessLogix 43 Apache Server 23 API Server

specify 33 authorization 10 CIM host

add 35 remove 37

CIM Server specify 33

CLARiiON CX 7, 12, 43 CLI 56

common aspects 56 connection parameters 56 enumeration values 57 help function 56 parameter file 56

common parameters values range 59

configuration data 8 configuration file 17 configuration layer 8 Configure tab 29, 35 connection parameters

CLI 56 deinstallation 24 device

assign to a storage pool 40 attach 34, 52 detach 34, 54 release 35

disaster recovery 5 discovery 33 document root 23 Dynamic Data Center 5 dynamic layer 8 enumeration values

CLI 57 FibreCAT CX 7, 12, 43 FibreCAT SX 12 GUI 25

main window 28 start 25

hierarchical browser 29 high availability 11 host

add 32, 49 remove 51

hostname common parameter 59

information and monitoring API 105

Information and Monitoring set up 32

installation EMC SMI-S Provider 14 StorMan GUI 23

StorMan Server (Linux) 17 StorMan Server (Windows) 19

ip common parameter 59

LUN masking FibreCAT CX / CLARiiON CX 44 NetApp FAS 48 Symmetrix 46

Manage tab 29, 49 NetApp FAS systems 7 NetApp® FAS 12 object table 30, 50, 52, 54 poolid

common parameter 59 provisioning 5 repository 8, 10

add a new host 61 configure 60 modify attributes of a host 61

SMI-S 9 SMI-S Provider 11 smserver.ini 17 software requirements 13 SPC 47 storage array

discover 35 storage information and monitoring 7 storage layer 8 storage pool 8

add 37 create 33 delete 39 rename 40

storage provisioning 5, 7 storage system

discovery 74 storage volume

create 34 use 34

storattach 91 storcfg 60 storcfg cimom 66

-add 66 -discover 70 -mod 68 -rem 69 -show 71

storcfg host 60 -add 61 -mod 61 -rem 63

storcfg host_-show 64 storcfg pool 76

-add 76 -mod 77 -rem 78 -show 79


storcfg system 73 -discover 74 -rem 73 -show 74

storcfg volume 81 -add 81 -mod 83 -rem 84 -show 85

storcheck 97 storcreate 89 stordelete 95 stordetach 93 storemc 101

-add 101 -rem 103

storID common parameter 59

storinfo 100 StorMan

architecture 9 Client 9 Server 9

StorMan configuration CLI 32, 35

StorMan GUI -> GUI 25 StorMan service

start and stop (Linux) 19 start and stop (Windows) 22

STORMAN_ACCESS_MODE 57 STORMAN_CONNECTION_TYPE 58 STORMAN_RESOURCE_TYPE 58 STORMAN_SIZE_TYPE 57 STORMAN_STORAGE_MODEL 58 STORMAN_STORAGE_VENDOR 58 stormandb 96 storparam 98 Symmetrix 7, 43 system requirements 12 virtualization layer 7 VolumeLogix 43 WWPN

add 51 common parameter 59 remove 52

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.

Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.

Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.

Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.

Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.

Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009

Documents

StorMan V1.3 Provisioning and managing virtualized …manuals.ts.fujitsu.com/file/7249/storman13.pdf · 7.1.1 Common CLI aspects ... With the scope of uniform integration of storage