storage manager v2 - fujitsumanuals.ts.fujitsu.com/file/8618/storman.pdf · ... srdf™,...

Edition May 2009

© S

iem

ens

Nix

dor

f In

form

atio

nssy

ste

me

AG

19

95

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e\

stor

man

.vor

Storage Manager (StorMan) V2.0Provisioning and managing virtualized storage resources

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs.

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

Certified documentation according to DIN EN ISO 9001:2000To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2000.

cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

Copyright and Trademarks

This manual is printed on paper treated with chlorine-free bleach.

Copyright © Fujitsu Technology Solutions 2009.

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

EMC2®, Symmetrix®, CLARiiON CX, SRDF™, TimeFinder™, SnapView™, Enginuity™ and EMC ControlCenter™ are trademarks of EMC2 Corporation, Hopkinton/MA (USA).

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

mailto:[email protected]

http://www.cognitas.de

U41824-J-Z156-1-76

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ay 2

009

S

tand

18:

03.2

7P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.

ivz

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 Functional overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.3 Documentation guide for different scenarios . . . . . . . . . . . . . . . . . . . . 131.3.1 “Standalone usage” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.2 Integration in DDC solutions (e.g. FlexFrame) or projects . . . . . . . . . . . . . . . 141.3.3 Integration with server management software . . . . . . . . . . . . . . . . . . . . . 151.3.4 Integration in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.4 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Functions and Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.1 Functional structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1.1 Storage provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1.2 Storage information and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.3 Statistics and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1.4 Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.2 Logical structure for storage management . . . . . . . . . . . . . . . . . . . . . 232.2.1 Virtualization layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.2.2 Storage layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.3.2 Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.3 Communication und security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.4 Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3.5 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.3.6 High availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Contents

U41824-J-Z156-1-76

3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.1.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.1.1.1 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.1.1.2 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.1 General requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.2 Additional software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.2.2 SMI-S Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.2.3 StorMan Administration GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.2.3 Installation and start of EMC SMI-S Provider . . . . . . . . . . . . . . . . . . . . . . 353.2.3.1 Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.2.3.2 Special issues for FibreCAT CX / CLARiiON CX Systems . . . . . . . . . . . . . 363.2.3.3 Special issues for Symmetrix Systems . . . . . . . . . . . . . . . . . . . . . . . 373.2.3.4 CIM-OM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.3 Installing the StorMan Server on Linux . . . . . . . . . . . . . . . . . . . . . . . 403.3.1 Configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.3.2 Starting and stopping the StorMan service . . . . . . . . . . . . . . . . . . . . . . . 44

3.4 Installing the StorMan Server on Windows . . . . . . . . . . . . . . . . . . . . . 453.4.1 Port configuration and other parameters (smserver.ini) . . . . . . . . . . . . . . . . . 493.4.2 Starting and stopping the StorMan service . . . . . . . . . . . . . . . . . . . . . . . 49

3.5 Installing the StorMan Server on BS2000/OSD . . . . . . . . . . . . . . . . . . . 49

3.6 Installing the StorMan GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.6.1 Copying web documents (Apache Server) . . . . . . . . . . . . . . . . . . . . . . . 503.6.2 Setting JNLP MIME type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.7 Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.7.1 Deinstallation of StorMan on a Linux Server . . . . . . . . . . . . . . . . . . . . . . 523.7.2 Deinstallation of StorMan on a Windows Server . . . . . . . . . . . . . . . . . . . . 523.7.3 Deinstallation of StorMan Server on a BS2000/OSD Server . . . . . . . . . . . . . . 533.7.4 Deinstalling the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.8 Upgrade Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4 The graphical user interface – StorMan GUI . . . . . . . . . . . . . . . . . . . . . 55

4.1 Starting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.1.1 Starting Java Web Start repeatedly . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.1.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Contents

U41824-J-Z156-1-76

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ay 2

009

S

tand

18:

03.2

7P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.

ivz

4.2 Elements of StorMan GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.2.1 Navigation area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.2.2 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.2.3 Output area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.2.4 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.2.5 Calling a StorMan function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.2.6 Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5 Setting up StorMan configurations . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.2 Setting up StorMan configurations using the GUI . . . . . . . . . . . . . . . . . 68

5.3 Setting up StorMan configurations using the CLI . . . . . . . . . . . . . . . . . 695.3.1 Specify one or more CIM Servers / API Servers . . . . . . . . . . . . . . . . . . . . 695.3.2 Discover a storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.3.3 Create StorMan pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.3.4 Using existing storage volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.3.5 Creating new storage volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.3.6 Discover changes to a storage array . . . . . . . . . . . . . . . . . . . . . . . . . . 715.3.7 Remove a storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.4 Diagnostic aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.4.1 StorMan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.4.2 SMI-S Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6 Administration and Provisioning tasks . . . . . . . . . . . . . . . . . . . . . . . 75

6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6.2 Administration and Provisioning tasks using the GUI . . . . . . . . . . . . . . . 76

6.3 Administration and Provisioning tasks using the CLI . . . . . . . . . . . . . . . 776.3.1 Add a new host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.3.2 Attach a logical device to a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.3.3 View the attachments to a device . . . . . . . . . . . . . . . . . . . . . . . . . . . 786.3.4 Detach a logical device from a host . . . . . . . . . . . . . . . . . . . . . . . . . . 786.3.5 Release a storage volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Contents

U41824-J-Z156-1-76

7 Replication tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.1 Working with full local mirrors (clones) . . . . . . . . . . . . . . . . . . . . . . . 797.1.1 Creating clone pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.1.2 Activating clone volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.1.3 Recreating clone pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807.1.4 Restoring the source volume from the clone . . . . . . . . . . . . . . . . . . . . . . 807.1.5 Terminating a clone pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807.1.6 Information about clone pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.2 Working with pointer based local mirrors (snapshots) . . . . . . . . . . . . . . . 817.2.1 Creating snapshot pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.2.2 Activating snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.2.3 Restoring the snap volume from the clone . . . . . . . . . . . . . . . . . . . . . . . 817.2.4 Terminating a snap pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.2.5 Information about snap pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

8 Statistics and performance tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

8.1 Setting up StorMan configuration using the CLI . . . . . . . . . . . . . . . . . . 85

8.2 Getting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

9 Special properties of storage systems . . . . . . . . . . . . . . . . . . . . . . . . 87

9.1 Special properties of EMC storage systems . . . . . . . . . . . . . . . . . . . . . 879.1.1 Dynamic creation of storage volumes / logical devices . . . . . . . . . . . . . . . . . 879.1.2 LUN masking in FibreCAT CX / CLARiiON CX systems . . . . . . . . . . . . . . . . 899.1.3 LUN masking in Symmetrix systems . . . . . . . . . . . . . . . . . . . . . . . . . . 929.1.4 Host storage connections (SPCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

9.2 Special properties of NetApp storage systems . . . . . . . . . . . . . . . . . . . 969.2.1 Dynamic LUN creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969.2.2 LUN mapping and LUN masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

10 StorMan for programmers – CLI description . . . . . . . . . . . . . . . . . . . . 99

10.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9910.1.1 Common CLI aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9910.1.2 Common enumeration values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10110.1.3 Common supported value ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

10.2 storattach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

10.3 storcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Contents

U41824-J-Z156-1-76

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ay 2

009

S

tand

18:

03.2

7P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.

ivz

10.4 storcfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11010.4.1 storcfg host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11110.4.1.1 storcfg host –add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11210.4.1.2 storcfg host –mod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11310.4.1.3 storcfg host –rem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11610.4.1.4 storcfg host –show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.4.2 storcfg cimom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12010.4.2.1 storcfg cimom –add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12110.4.2.2 storcfg cimom –mod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12310.4.2.3 storcfg cimom –rem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12510.4.2.4 storcfg cimom –discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12710.4.2.5 storcfg cimom –show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12910.4.3 storcfg system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.4.3.1 storcfg system –rem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13310.4.3.2 storcfg system –discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.4.3.3 storcfg system –show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13510.4.4 storcfg pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14010.4.4.1 storcfg pool –add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14110.4.4.2 storcfg pool –mod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14310.4.4.3 storcfg pool –rem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14510.4.4.4 storcfg pool –show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14610.4.5 storcfg volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14910.4.5.1 storcfg volume –add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15010.4.5.2 storcfg volume –mod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15210.4.5.3 storcfg volume –rem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15410.4.5.4 storcfg volume –discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15610.4.5.5 storcfg volume –show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

10.5 storcreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

10.6 stordelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

10.7 stordetach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.8 storemc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17910.8.1 storemc –add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18010.8.2 storemc –rem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

10.9 storinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

10.10 stormandb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Contents

U41824-J-Z156-1-76

10.11 stormirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18710.11.1 stormirror –activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18810.11.2 stormirror –create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19110.11.3 stormirror –deactivate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19410.11.4 stormirror –recreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19610.11.5 stormirror –restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19810.11.6 stormirror –terminate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20010.11.7 stormirror –show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

10.12 storparam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

10.13 storstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21110.13.1 storstat volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21210.13.1.1 storstat volume –get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

11 StorMan for programmers – StorMan Client interface for information and monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

12 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Fujitsu Technology Solutions: Software License Agreement for End Users . . . . . 219

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

U41824-J-Z156-1-76 9

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

1

1 Introduction

1.1 Functional overview

The main scope of Storage Manager (further on referenced as 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.

Functional overview Introduction

10 U41824-J-Z156-1-76

StorMan provides a common virtualization layer offering:

● Common and stable interfaces for

– “standalone usage”

– integration in DDC solutions (e.g. FlexFrame) or projects

– integration with server management software such as ServerView, open SM2, etc

– integration in BS2000/OSD (with SHC-OSD V7.0)

● 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, EMC, NetApp) and

– storage connectivity types on the backend

Introduction Functional overview

U41824-J-Z156-1-76 11

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

1

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 the standard for storage management in the storage world. However, for specific functions or for vendors apart from SMI-S, there is the option of integrating vendor-specific APIs.

The functionality of StorMan covers the main functions needed for storage provisioning, namely:

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

● LUN creation and deletion

StorMan

Storage Management and Virtualization Layer

Application Layer

Storage Layer:

...

FibreCAT SXNetApp

FAS

EMC Symmetrix FibreCAT CX

...

SMI-S client

FlexFrame BS2000/OSDServerView

SuiteopenSM2

Documentation Introduction

12 U41824-J-Z156-1-76

● LUN masking (managing the hosts access to volumes)

● Replication service (local mirroring replication based on snap and clone technology)

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

● discovery

● information about logical and physical components

● status monitoring

● statistical and performance metrics

1.2 Documentation

With exception of the GUI functions you will find a complete description of StorMan (e.g. concept, architecture, installation, CLI functions) in the StorMan manual.

For users of the GUI the manual only contains a chapter describing the GUI startup and basic informations for using the GUI.

The complete reference of GUI functions you will find online in the StorMan help system which you can call context sensitive from the StorMan GUI (refer to section “Using Help” on page 65).

Additional product information

Current information, version and hardware dependencies and instructions for installing and using a product version are contained in the associated Release Notice. These Release Notices are available at http://manuals.ts.fujitsu.com.

See the Release Notices for special information on a new release.

http://manuals.ts.fujitsu.com

Introduction Documentation guide for different scenarios

U41824-J-Z156-1-76 13

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

1

1.3 Documentation guide for different scenarios

For general informations about StorMan refer to chapter “Functions and Architecture” on page 19.

For installation of StorMan refer to chapter “Installation” on page 31. In addition to system and software requirements use the installation section concerning your system platform.

Which other chapters are relevant for the user depends on the usage scenario.

I The StorMan's Client Interface (API) is reserved for internal usage in other products of Fujitsu. Refer to chapter “StorMan for programmers – StorMan Client interface for information and monitoring” on page 217.

1.3.1 “Standalone usage”

Description of the StorMan tasks:

● For configuration and administration of storage resources to be managed by StorMan refer to chapter “Setting up StorMan configurations” on page 67. The concerning functions are available on the CLI. Alternatively a subset of these functions are offered by the GUI.

● To provide host with resources managed by StorMan refer to chapter “Administration and Provisioning tasks” on page 75. The concerning functions are available on the CLI. Alternatively a subset of these functions are offered by the GUI.

● To replicate storage devices on FibreCat CX storage systems refer to chapter “Repli-cation tasks” on page 79. The concerning functions are available on the CLI.

● To get statistic and performance informations from storage systems and their storage devices refer to chapter “Statistics and performance tasks” on page 83. The concerning functions are available on the CLI.

Description of the StorMan interfaces:

● All CLI commands can be used. For the syntax description refer to chapter “StorMan for programmers – CLI description” on page 99.

● Alternatively to the use of CLI commands a subset of configuration and providing tasks can be done by using the StorMan GUI. For basic informations about startup and using the GUI refer to chapter “The graphical user interface – StorMan GUI” on page 55. Please notice that the complete GUI function reference is only contained in the online help system.

● General information for users of StorMan API are available in the chapter “StorMan for programmers – StorMan Client interface for information and monitoring” on page 217.

Documentation guide for different scenarios Introduction

14 U41824-J-Z156-1-76

Description of special issues depending on the used storage system:

● Depending on the used storage system some functions to configure storage resources may not be available with StorMan (e.g. create a logical device). Refer to chapter “Special properties of storage systems” on page 87.

1.3.2 Integration in DDC solutions (e.g. FlexFrame) or projects


● For configuration and administration of storage resources to be managed by StorMan refer to chapter “Setting up StorMan configurations” on page 67. The concerning functions are available on the CLI. Alternatively a subset of these functions are offered by the GUI.

● To provide hosts with resources managed by StorMan refer to chapter “Administration and Provisioning tasks” on page 75. The concerning functions are available on the CLI. Alternatively a subset of these functions are offered by the GUI.


● ALL CLI commands can be used in this scenario (however, not all may be applicable). For the syntax description refer to chapter “StorMan for programmers – CLI description” on page 99.

● Alternatively to the use of CLI commands a subset of configuration and providing tasks can be performed by using the StorMan GUI. For basic informations about startup and using the GUI refer to chapter “The graphical user interface – StorMan GUI” on page 55. Please notice that the complete GUI function reference is only contained in the online help system.



Introduction Documentation guide for different scenarios

U41824-J-Z156-1-76 15

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

1

1.3.3 Integration with server management software

For integration with server management software such as ServerView Operations Manager and performance monitoring software such as openSM2 only a subset of StorMan functions is available. This subset consists of the functions for information and monitoring and do not include active management of the storage resources.


● For configuration and discovery of storage resources to be managed by StorMan refer to chapter “Setting up StorMan configurations” on page 67.


● The following subset of CLI commands ist available:

– The CLI commands storcfg host and storcfg cimon can be used for configu-ration.

– The CLI command storcfg system -show can be used for gathering detailed configuration and status information of the storage systems.

– The CLI command storstat that provides statistical information and metrics can be used for monitoring the performance of the storage systems.

– Additionally the CLI commands stormandb, storcheck, storparam, storinfo und storemc can be used.

For the syntax description refer to chapter “StorMan for programmers – CLI description” on page 99.


Documentation guide for different scenarios Introduction

16 U41824-J-Z156-1-76

1.3.4 Integration in BS2000/OSD

For integration in BS2000/OSD with the BS2000 product SHC-OSD the complete integration of StorMan is done by SHC-OSD internally. Refer to the SHC-OSD manual [1] for further details. The configuration of storage resources (FibreCAT CX) to be managed by StorMan have to be set up by StorMan CLI in the POSIX shell of BS2000/OSD. Please refer to chapter “Setting up StorMan configurations” on page 67.

However the complete functionality of StorMan is available on CLI level in the BS2000/OSD POSIX shell.


● For configuration of storage resources to be managed by StorMan refer to chapter “Setting up StorMan configurations” on page 67.

● To provide host with resources managed by StorMan refer to chapter “Administration and Provisioning tasks” on page 75.

● To replicate storage devices on FibreCat CX storage systems refer to chapter “Repli-cation tasks” on page 79. The concerning functions are available on the CLI.


● All CLI commands can be used. For the syntax description refer to chapter “StorMan for programmers – CLI description” on page 99.




Introduction Notational conventions

U41824-J-Z156-1-76 17

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

1

1.4 Notational conventions

The following fonts and symbols are used in this manual to indicate different types of infor-mation:

The following fonts and symbols are used in the CLI syntax description:

Font/Symbol Indicates Example

AaBbCc123 System outputs are written in this typewriter font.

http port 5988

AaBbCc123 Commands entered by the user are written in typewriter font bold

Italic text Program interface functions and menus are written like this.

Select the menu Add new host

“ ” Manual, chapter and section titles are enclosed by double inverted commas.

See chapter 3, “Installation“

Ê The enter symbol indicates an action that the operator must perform (e.g. enter something on the keyboard).

Ê Click the Attach button.

Indicates warnings.

Indicates important information about product operation.

Font/Symbol Indicates Example

AaBbCc123 Syntax elements of function call are written in this typewriter font.

storcfg

Italic text Variables are written in this typewriter font

function or hostname

{ } Braces enclose alternatives; one of the possible values shown within the braces must be entered.

{ –name hostname | –ip ip }

| A bar serves to separate alternative parameters or values.

–name hostname | –ip ip

[ ] Square brackets enclose optional parameters, i.e parameters which may be omitted.

[ –interface type ]

[,...] This entry after a value signifies that a list of values can be specified.

–addip ip[,...]

!i

Notational conventions Introduction

18 U41824-J-Z156-1-76

U41824-J-Z156-1-76 19

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

2

2 Functions and Architecture

2.1 Functional structure

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

● Storage provisioning

● Storage information and monitoring

● Statistics and performance monitoring

● Replication functions

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

2.1.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 virtu-alization 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” on page 55) and as CLI for automation support in scripts (see the chapter “StorMan for programmers – CLI description” on page 99).

Functional structure Functions and Architecture

20 U41824-J-Z156-1-76

StorMan V2.0 supports the Storage Provisioning features for following storage systems:

2.1.2 Storage information and monitoring

The storage information and monitoring features supported are those required for infor-mation 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 the CLI (and StorMan's Client Interface (API)).

StorMan V2.0 supports the Information and Monitoring features for following storage systems:

Storage system Vendor Supported connectivity type

FibreCAT CX1

1 The FibreCAT CX disk storage systems correspond to the CLARiiON CX disk storage systems of EMC2 Corpo-ration.

Fujitsu FC

Symmetrix EMC Corporation FC

CLARiiON CX EMC Corporation FC

NetApp® FAS systems NetApp FC


FibreCAT CX Fujitsu FC / iSCSI

FibreCAT SX Fujitsu FC / iSCSI

CLARiiON CX EMC Corporation FC / iSCSI

Functions and Architecture Functional structure

U41824-J-Z156-1-76 21

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

2

2.1.3 Statistics and Performance

The statistic and performance features supported are required for monitoring storage arrays mainly as used in by openSM2 and suitable for Managed Storage Services implementa-tions.

The statistic and performance monitoring features are provided on volume (LUN) level, namely the following:

● reads per second

● writes per second

● KB read per second

● KB write per second

● Average IO times for reads and wirtes


StorMan V2.0 supports the Statistics and Performance features for following storage systems:


FibreCAT CX Fujitsu FC

Symmetrix EMC Corporation FC


Functional structure Functions and Architecture

22 U41824-J-Z156-1-76

2.1.4 Replication

The Replication Service features cover the information and management of local mirroring functions implemented in the storage systems based on snap and clone technologies used e.g. by SHC-OSD to integrate FibreCAT CX and CLARiiON CX storage systems in BS2000/OSD.

The Replication Service features support the management of the following local mirroring functions:

● local mirroring based on full volume copies (clones)

● local mirroring based on pointer based technologies (snaps)


StorMan V2.0 supports the replication features based on the local mirroring product SnapView for following storage systems:


FibreCAT CX Fujitsu FC


Functions and Architecture Logical structure for storage management

U41824-J-Z156-1-76 23

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

2

2.2 Logical structure for storage management

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

2.2.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 descrip-tions.

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 StorMan administrator defines the StorMan managed storage pools as the storage resources available for provisioning. Further on these storage pools administrated by StorMan are just called pools to differentiate them from the notion of storage pools used in the context of storage systems.

In its simplest form, each 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 pool description contains general pool attributes and storage system- and volume-related attributes. The StorMan Server administrates the pool layer.

Logical structure for storage management Functions and Architecture

24 U41824-J-Z156-1-76

● 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 pool, etc. The storage identifier is created the first time storage is assigned and optionally deleted after de-assignment. An option of config-uring 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 pool.

An administration interface (GUI) to configure and manage the Virtualization Layer's config-uration data offers basic management functions (e.g. adding, removing, modifying and displaying 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. StorMan managed 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.

2.2.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 corre-sponding 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 client will call the corresponding vendor-specific SMI-S Providers.

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

Functions and Architecture Logical structure for storage management

U41824-J-Z156-1-76 25

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

2

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 higher 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. StorMan uses this branch for storage systems of NetApp to support these systems by using ManageONTAP API.

Architecture Functions and Architecture

26 U41824-J-Z156-1-76

2.3 Architecture

2.3.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 imple-mented 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.

StorMan - Architecture

StorMan ServerPlatforms:

Windows, RHEL ESx,

SLES, BS2000/OSD

TCP/IP

Repository

storId‘s, Pools,

servers, HBAs

SMI-S provider

EMC

SMI-S client

CIM-OM

StorMan Client(s):Platforms:

Windows, RHEL ESx,

SLES, BS2000/OSD

ONTAP

NetApp

SMI-S provider

Fujitsu

…

BS2000 ...

FlexFrame

openSM2

ServerView ...

…

port#

4178/

4179

SMI-S provider(s)

others

GUI

TCP/IP

proxy

StorMan SMI-S Provider & Storage

CLI, API

Functions and Architecture Architecture

U41824-J-Z156-1-76 27

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

2

The StorMan Client part resides on the same server as the calling application and provides its caller with a stub presenting the management 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.

2.3.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 4178).

2.3.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 pools (pool IDs) 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.

2.3.4 Repository

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

The repository is located in the following directory:

● %PROGRAMFILES%\Fujitsu\StorMan\repository (Microsoft Windows)

● /var/opt/SMAWstor/StorMan/repository (Linux)

● /var/storman/repository (POSIX in BS2000/OSD)

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 “High availability” on page 28).


28 U41824-J-Z156-1-76

2.3.5 Error handling

Managment 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.

2.3.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.

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. This can be defined by configuring the DataDirectory parameter in the smserver.ini file.

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 alter-native StorMan Server in the LAN.

Functions and Architecture Architecture

U41824-J-Z156-1-76 29

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

01P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

2

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.

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.

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 NetApp in StorMan) 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 NetApp filer.


30 U41824-J-Z156-1-76

U41824-J-Z156-1-76 31

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3 Installation

3.1 System requirements

3.1.1 Hardware

3.1.1.1 Server

StorMan V2.0 supports following servers:

● all current PRIMERGY servers as StorMan Clients and StorMan Servers

● SQ- and SX-Servers in BS2000/OSD environments

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.

3.1.1.2 Storage

EMC Storage

StorMan V2.0 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.3.2 and Solutions Enabler V6.5.3.

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 available by the name FibreCAT CX

StorMan V2.0 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.3.2 and Solutions Enabler V6.5.3.

https://powerlink.emc.com/

System requirements Installation

32 U41824-J-Z156-1-76

StorMan V2.0 supports the replication service functions required primarily for integration with SHC-OSD V7.0 for the current FibreCAT CX / CLARiiON CX models as supported by SMI-S Provider V3.3.2 and Solutions Enabler V6.5.3 as of Flare Code Release 26.

StorMan V2.0 does not support the information and monitoring functions required e.g. for integration with ServerView for Symmetrix and Symmetrix DMX storage of EMC corpo-ration.

NetApp Storage

StorMan supports the provisioning functions for the full range of SAN connected storage of NetApp® FAS (FAS2xx, FAS9xx, FAS3xxx) as supported by ManageONTAP 7.2.5 of NetApp.

StorMan V2.0 does not support the information and monitoring functions required e.g. for integration with ServerView for storage of NetApp.

FibreCAT SX arrays

StorMan V2.0 does not support the provisioning functions for FibreCAT SX storage.

StorMan V2.0 supports the information and monitoring functions required primarily for integration with ServerView for the current FibreCAT SX models SX60, SX80, SX88 and SX100. This support is based on the embedded SMI-S Provider available as of microcode version J200P08 and K100P11.

Installation Software

U41824-J-Z156-1-76 33

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.2 Software

3.2.1 General requirements

The platforms supported are:

● Microsoft Windows Server 2003 SP2

● Microsoft Windows XP SP2 and SP3

● SuSe Linux Enterprise Server (SLES) 10 SPx

● SuSe Linux Enterprise Server (SLES) 9 SPx

● Red Hat Enterprise Linux (RHEL) ES 5

● Red Hat Enterprise Linux (RHEL) ES 4

● BS2000/OSD V8.0

3.2.2 Additional software requirements

The following software packages are necessary

3.2.2.1 General

Red Hat Enterprise Linux (RHEL) ES 5 platforms only:

The package compat-libstdc++.33-3.2.3-61 must be installed. It contains compatible standard C++ libraries.

The package is available from your distributor’s online upgrade support.

3.2.2.2 SMI-S Provider

EMC Storage

● SMI-S Provider V3.3.2 for SMI-S V1.1 and higher from EMC Corporation.

As SMI-S Provider V3.3.2 is based on EMC Solutions Enabler V6.5.3.

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.3.2. Release Notes available at https://powerlink.emc.com/.


Software Installation

34 U41824-J-Z156-1-76

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

– Microsoft Windows 2000 SP4

– Microsoft Windows Server 2003

– Solaris 8, 9, 10

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

– SuSe Linux Enterprise Server (SLES) 9 (SP3) and 10

● 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,

– as a download fromhttps://partners.ts.fujitsu.com/com/service/storage/online/fibrecat/fibrecatcedownload for FibreCAT CX systems accessible for FibreCAT CX certified engineers of Fujitsu.

– For BS2000/OSD platforms the BS2000/OSD StorMan delivery and the EMC SMI-S Provider are part of the product SHC-OSD V7.0 (pls.refer to “SHC-OSD” manual [1])

● A FC connection for the CIM Server (SMI-S Provider) is required to support EMC Symmetrix storage arrays and is not required for FibreCAT CX and CLARiiON storage arrays.

NetApp Storage

As for StorMan V2.0 the support of NetApp® FAS storage is based on ManageONTAP 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 J200 and K100 respective.

3.2.2.3 StorMan Administration GUI

The following libraries are required in addition:

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

It is recommended that you update these libraries.


https://partners.ts.fujitsu.com/com/service/storage/online/fibrecat/fibrecatcedownload

http://java.sun.com


U41824-J-Z156-1-76 35

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.2.3 Installation and start of EMC SMI-S Provider

3.2.3.1 Download

Windows and Linux platforms

● 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 Technology Solutions partner net: http://partners.ts.fujitsu.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 ES 4 and SuSe SLES 9/10).

BS2000/OSD platforms

The EMC SMI-S Provider for BS2000/OSD platforms is delivered with the BS2000/OSD StorMan delivery as part of the product SHC-OSD V7.0. For installation instructions please refer to “SHC-OSD” manual [1] and Symmetrix documentation.

By default for BS2000/OSD the SMI-S Provider is installed and running on the X2000 carrier system.

Additionally BS2000/OSD does support an external SMI-S provider. In this case the SMI-S provider has to be installed and set up as described in “SHC-OSD” manual [1].

http://powerlink.emc.com


36 U41824-J-Z156-1-76

3.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.

● The features for local replication (SnapView Snap and SnapView Clone) are supported only for Flare Code Release 26 or higher.

● 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 “storemc” on page 197.

● 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 Fibre-Channel. If “ArrayCommPath” is enabled for the FC path(s), this can be “LUN Z”.

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.


U41824-J-Z156-1-76 37

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.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).

With SMI-S Provider version as of 3.2 this parameter should be set to false (default value). See section “LUN masking in Symmetrix systems” on page 92 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.

● 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 includes one line per Symmetrix with the serial number of the Symmetrix. The file is contained in the directory:

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

http://powerlink.emc.com


38 U41824-J-Z156-1-76

3.2.3.4 CIM-OM Settings

The following chapters describes the setting of the SMI-S Provider recommended for usage in StorMan configurations. They are defined in the parameter file EMCProvider_user.conf in the ...\SYMCLI\storbin\ directory.

The SMI-S Provider has to be restarted to activate modified set tings.

Please refer to EMC Release Notes for further information.

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 directs the Provider to synchronize its database if necessary.

Deliver indications without subscription

To receive indications without specific subscription the following parameters are mandatory and have to be set:

OslProv/com.emc.se.osls.osl.ind.IndicationManager.enableOnSubscribe = true

OslProv/com.emc.se.osls.osl.ind.IndicationManager.enableWithoutSubscription = true

Synchronous processing of replication function

Synchronous processing of replication functions is required by StorMan. Therefore the following parameters have to be set:

OslProv/com.emc.se.osls.osl.ReplicationService.replica.creation.action.synchronous = true

OslProv/com.emc.se.osls.osl.ReplicationService.replica.modification.action.synchronous = true

Disable remote replication

As StorMan V2.0 does not support remote replication, the function is disabled in the SMI-S Provider:

OslProv/com.emc.se.osls.osl.ReplicationService.remote.enable = false


U41824-J-Z156-1-76 39

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

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 -stop EMC_SMI_Provider

– 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 provides no warranty for these tools. Refer to EMC's latest Release Notes for details.

Installing the StorMan Server on Linux Installation

40 U41824-J-Z156-1-76

3.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. It has 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 section “Deinstallation” on page 52 for information on deinstal-lation.

Installation Installing the StorMan Server on Linux

U41824-J-Z156-1-76 41

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.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 server initialisation file: smserver.ini #====================================================================## ----- StorMan parameters -----------------------------------------## -- set variable path name for the data directory# for subdirectories backup, log and repository:# default values: # - Windows: the installation home directory# - others: the installation home directory# or the environment variable STORMAN_HOME_DATA if set.# DataDirectory = /var/storman### -- support of replication functions:# values:# 1 replication functions and information enabled# 0 NO replication functions and information enabled# default value: 0WithMirrors = 0## -- port number for the StorMan server:# default value: 4178StormanServerPort = 4178### ----- Parmeters of the CIMOM (SMI-S Provider) ---------------## -- Timeout value for CIMOM calls:# value range: <0 - 6000># default value: 600CimTimeOut = 600#


42 U41824-J-Z156-1-76

# ----- Parameters for function storcreate## -- Timeout value for CIMOM calls of function storcreate:# value range: <0 - 6000># default value: 0CreateTimeout = 0## -- Type of target operating system for storcreate calls# considered only if required by storage systems and the client # has none specified# supported values: local, windows, linux, solaris# default value: localDefaultTargetOSType = local## ----- Trace Levels ----------------------------------------------## -- maximum level to trace# values:# <0 trace all# 0 trace severe errors only# 1 trace errors too# 2 trace even warnings# 3 trace information# 4 trace debug# 5 trace extended debug# default value: 4MaxTraceLevel = 4## -- trace communication:# only for enabled extended debugging (MaxTraceLevel > 4)# values:# 0 trace off# 1 trace tcp/ip# 2 trace messages# 4 trace cim tcp/ip# 8 trace cim messages# add the values to enable the traces# default value: 0DebugCom = 0## -- trace communication and debugging info of worker threads# values:# 0 trace off# 1 trace worker# 2 trace updater# add the values to enable the traces# default value: 0TraceWorker = 0

Installation Installing the StorMan Server on Linux

U41824-J-Z156-1-76 43

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

Some other parameters can be modified by editing smserver.ini or by using the storparam command as described in section “storparam” on page 209:

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 *.orig are default backup files.

● The parameter StatusRefreshTime is no longer supported and no longer required as of StorMan V2.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 “storcreate” on page 182.

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 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 “storcreate” on page 182. Other possible values are 'windows', 'linux' or 'solaris'.

DataDirectory Supports a variable path name setting for the data directory containing the subdirectories backup, log and repository.The default values are depending of the platform:– Windows: the installation home directory– others: the installation home directory or the environment

variable STORMAN_HOME_DATA if set.

WithMirrors Enables or disables replication functions and information. The default value is 1 (enabled). If no replication features are used it is recommended to disable (WithMirrors = 0) the setting to obtain best performance.


44 U41824-J-Z156-1-76

3.3.2 Starting and stopping the StorMan service

The StorMan service is configured by installation being started automatically by the rc 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 “storcheck” on page 193.

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

Installation Installing the StorMan Server on Windows

U41824-J-Z156-1-76 45

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.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 “Deinstallation” on page 52 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:

Installing the StorMan Server on Windows Installation

46 U41824-J-Z156-1-76

● Click Next in the Installation Welcome window:

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

Installation Installing the StorMan Server on Windows

U41824-J-Z156-1-76 47

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

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

● (See next page)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.

Installing the StorMan Server on Windows Installation

48 U41824-J-Z156-1-76

The following screen shows that installation has been successful completed.

Installation Installing the StorMan Server on BS2000/OSD

U41824-J-Z156-1-76 49

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.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\StorMan\config as the default) where you are able to change the StorMan port as well as other parameters.

Refer to section “Configuration file” on page 41 for further details (the file is the same on Linux and Microsoft Windows).

3.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 “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 “storcheck” on page 193.

3.5 Installing the StorMan Server on BS2000/OSD

As StorMan in BS2000/OSD is completely embedded into the product SHC-OSD V7.0 please refer to “SHC-OSD” manual [1] for setting up and maintaining StorMan in BS2000/OSD with IMON.

Installing the StorMan GUI Installation

50 U41824-J-Z156-1-76

3.6 Installing the StorMan GUI

A virtual Java machine (JRE 1.6+) 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).

3.6.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 rootln -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>

http://java.sun.com

Installation Installing the StorMan GUI

U41824-J-Z156-1-76 51

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

Ê For Help support please extract the files from StorManGUIHelp.zip into StorMan/WebHelp subdirectory of the the document root directory (e.g. /usr/local/apache2/htdocs/StorMan/WebHelp for Linux) or into /opt/SMAW/SMAWstor/StorMan/StorManGui/WebHelp.

3.6.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.

Deinstallation Installation

52 U41824-J-Z156-1-76

3.7 Deinstallation

3.7.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.

● In the directory /var/opt/SMAWstor/log/ the StorMan logging files are not removed.

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

3.7.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\StorMan\config\ the configuration file smserver.ini is not removed.

● In the directory %PROGRAMFILES%\Fujitsu\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\StorMan\repository\ the StorMan repos-itory containing the complete configuration managed by StorMan is not removed.

● In the directory %PROGRAMFILES%\Fujitsu\StorMan\log\ the StorMan logging files are not removed.

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

Installation Upgrade Installations

U41824-J-Z156-1-76 53

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

3

3.7.3 Deinstallation of StorMan Server on a BS2000/OSD Server

As StorMan in BS2000/OSD is completely embedded into the product SHC-OSD please refer to SHC-OSD documentation for setting up and maintaining StorMan in BS2000/OSD in IMON.

3.7.4 Deinstalling the GUI

Remove the files or the symbolic link described in section “Copying web documents (Apache Server)” on page 50 from the Web Server document root.

3.8 Upgrade Installations

During the start of StorMan V2.0 installation it is automatically checked if a StorMan version is already installed and the upgrade can be done automatically.

However, if a data in place upgrade is planned that should save existing StorMan managed configuration the migration steps should be done as described below.

Migration from previous versions to StorMan V2.0 is supported as described below.

Data in place upgrades for StorMan configurations from StorMan V1.3 to StorMan V2.0 is supported “on the fly”: During the upgrade process the StorMan repository is upgraded automatically.

I Please note that downgrading from StorMan V2.0 to a lower StorMan version is not supported. For this reason it is recommended to create a backup of the repository using stormandb -dump before starting the upgrade.

If your managed storage configuration requires the EMC SMI-S Provider, this requires an additional upgrade step.

The following migration scenario is supported to upgrade from StorMan V1.3.0.15 to StorMan V2.0. The steps have to be performed according to the specific platform:

1. Create a backup of your StorMan repository:

stormandb -dump

2. Make sure your application is not using StorMan during the upgrade.

3. Stop the StorMan Server:

storman -stop

Upgrade Installations Installation

54 U41824-J-Z156-1-76

4. Only if you are using EMC SMI-S Provider: Upgrade EMC SMI-S Provider to version V3.3.2 (according to the Release Notes)

5. Start StorMan upgrade installation for StorMan V2.0

6. Check if StorMan V2.0 was succesfully updated and is running:

storcheck

7. Check the correct settings in the smserver.ini file after successful upgrade.

If you are using EMC SMI-S Provider an additional step is necessary:

8. Check if SMI-S Provider V3.3.2 was succesfully updated and is running:

storcfg cimom -show

U41824-J-Z156-1-76 55

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

4

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

4.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.

Starting the GUI The graphical user interface – StorMan GUI

56 U41824-J-Z156-1-76

● Click here.

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 “Elements of StorMan GUI” on page 60).

The graphical user interface – StorMan GUI Starting the GUI

U41824-J-Z156-1-76 57

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

4

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

Starting the GUI The graphical user interface – StorMan GUI

58 U41824-J-Z156-1-76

4.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.

The graphical user interface – StorMan GUI Starting the GUI

U41824-J-Z156-1-76 59

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

4

4.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.

Elements of StorMan GUI The graphical user interface – StorMan GUI

60 U41824-J-Z156-1-76

4.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 “Starting Java Web Start repeatedly” on page 58). The title bar of the browser informs about the application and the current StorMan server.

The main window contains a header with product informations and below two tabs providing the main functions:

● Configure tab (selected by default)It subsumes functions for maintaining the storage configuration managed by StorMan: display, add and remove CIM Server and storage pools, display storage systems, display devices and move them into the storage pools.

● Manage tabIt subsumes functions for providing hosts with storage resources managed by StorMan. Currently it can be used to attach and detach storage devices to and from servers.

Header

Work area

Buttons

Navigation area

Output area

The graphical user interface – StorMan GUI Elements of StorMan GUI

U41824-J-Z156-1-76 61

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

4

Each tab comprises following elements:

● the navigation area on the left-hand side containing objects in a tree view,

● the work area on the right-hand side containing object tables,

● a message field at the buttom on the left-hand side,

● and buttons on the right-hand side.

4.2.1 Navigation area

The navigation area displays a tree view of objects which can be administrated by StorMan. The hierarchy of the objects in the tree depends on the selected tab.

Tree view on the Configure tab

The tree view displays following objects (sequence beginning from root):

● Cim Server as root contains all CIM hosts and their storage resources to be managed by StorMan.


62 U41824-J-Z156-1-76

● CIM hosts can be added to the Cim Server root. Object name is the specified host name. The object <no CIM host> exists by default on the Cim Server root.

● Storage systems managed by a CIM host are linked to the respective host. Object name is the storage system name containing its model name and the system ID. Storage systems without assignment to a CIM host are linked to the <no CIM host> object.

● Storage pools as a named collection of storage volumes (devices) of a storage system are linked to respective storage system. Object name is the specified pool name. The storage pool <no StorMan Pool> exists by default to contain devices without assigment to an explicit defined pool.

● Storage system devices to be managed by StorMan are linked to the assigned pool or to the <no StorMan Pool>.

See chapter “Setting up StorMan configurations” on page 67 for details.

Tree view on the Manage tab

The tree view displays following objects (sequence beginning from root):

● All Hosts as root contains all hosts to be provided with storage resources by StorMan.


U41824-J-Z156-1-76 63

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

4

● Hosts can be added to the All Hosts root. Object name is the specified host name (host name or IP address). If the automatic discover find device connections to a WWPN which is not assigned to a defined host a unknown host is added with this WWPN as host identifier to the All Hosts root.

● WWPNs can be added to a host.

See chapter “Administration and Provisioning tasks” on page 75 for details.

4.2.2 Work area

The work area displays object tables depending on the object selected in the tree view.

Object tables

The upper object table comprises the properties of the selected object.

Optionally one or more object tables can be displayed below to provide additional informa-tions about the selected objects and its subordinated objects.

Example: object tables of a selected CIM host in the Manage tab

Sub tabs

In some cases the work area displays different object tables in sub tabs:

● A device is selected in the Configure tab.

● A host is selected by host name or WWPN in the Manage tab.


64 U41824-J-Z156-1-76

4.2.3 Output area

The output area consists of a message field to display messages or warnings.

4.2.4 Buttons

The main window offers field three buttons behind the message field:

● Help branches context sensitiv to the online help.

● Refresh refreshes the displayed data again.

● Exit terminates the StorMan GUI.

Selecting the Manage tab additionally each sub tab in the output area contains a botton for function call:

● Attach detaches devices selected on the Attach sub tab

● Detach attaches devices selected on the Connected devices sub tab.

Dialog boxes to request confirmation contain following buttons:

● OK confirms the question or the specified input to continue the called function.

● Cancel aborts the called function.

4.2.5 Calling a StorMan function

To call a StorMan function perform following steps:

1. Select the tab which offers the function:

● Configure tab to configure storage resources

● Manage tab to provide hosts with storage resources

2. Select the object on the tree view:

● for functions creating a new object the upper object

● for all other functions the corresponding object

3. Select the function:

● To add, remove, rename or move an object right-click the object to open the context menu and select the function.

● To attach or detach devices select the corresponding sub tab in the work area, select the device in the displayed device list and click the Attach or Detach button.


U41824-J-Z156-1-76 65

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

4

● To modify object properties click the concerning cell in the object property table and modify the value editing or by selecting from a drop-down list.

4.2.6 Using Help

The StorMan help starts in a separate browser window when clicking the Help button or F1 key in the GUI window. If the help is aready started only the existing help window is activated.

The help window displays on the left-hand side the navigation area and on the right-hand side the help topic depending on the selected object in the GUI at calling time.

Icons on the top

Help navigation

Navigation by TOC is selected by default. The table of contents displays in a tree view the hierarchy of all help topics. Selecting a TOC entry displays the concerning topic. Topics which contain subordinate topics will appear as book.

Clicking such a topic

● “opens” the book and shows the contained topics on the tree

hides or shows the navigation area

displays the start topic ot the help

prints the displayed topic

adds the displayed topic to the favorite list (can be used to navigate by favorites)


66 U41824-J-Z156-1-76

● or “closes” the book and hides the contained topics.

To change to navigation by Index, Search, Glossary of Favorites select the concerning tab in the navigation area.

The top of each topic displays the topic hierarchy (path from main topic to displayed topic).

Clicking to an upper topic on this path displays the concerning topic.

U41824-J-Z156-1-76 67

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

5

5 Setting up StorMan configurations

5.1 Overview

Configuration features are supported by the StorMan GUI and CLI. The basic functions are available on both interfaces, but some functions are only available on the CLI. Functions for trouble-shooting are only available on the CLI (refer to section “Diagnostic aids” on page 72).

Setting up StorMan configurations using the GUI Setting up StorMan configurations

68 U41824-J-Z156-1-76

5.2 Setting up StorMan configurations using the GUI

Use the Configure tab of the GUI to set up StorMan. See chapter “The graphical user interface – StorMan GUI” on page 55 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.

Following functions are available:

● Add a new CIM host

● Remove CIM host

● Display/modify CIM host properties (implicit function)

● Add a new pool

● Delete a pool

● Rename a pool

● Display/modify pool properties (implicit function)

● Moving devices into pools

● Display/modify device properties (implicit function)

● Remove a storage system

The StorMan help system contains the complete GUI functions reference. Refer to section “Using Help” on page 65.

Setting up StorMan configurations Setting up StorMan configurations using the CLI

U41824-J-Z156-1-76 69

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

5

5.3 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, the StorMan help system contains the complete GUI functions reference. For a function overview refer to section “Setting up StorMan configurations using the GUI” on page 68.

For details about the CLI commands, refer to chapter “StorMan for programmers – CLI description” on page 99.

5.3.1 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 38), you have to specify it as part of this command as described in section “storcfg cimom” on page 127. A discovery of the storage systems by the CIM Server is started automatically.

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

For storage arrays from NetApp, 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.

5.3.2 Discover a storage system

Execute the command

storcfg cimom -discover -name myCimHost

This starts a discovery of the storage systems by the CIM Server. A complete discovery of the storage systems and its configuration by the CIM Server is required to update the configuration data of the CIM Server, e.g. in case a new storage system has been connected. 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).

Setting up StorMan configurations using the CLI Setting up StorMan configurations

70 U41824-J-Z156-1-76

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 section “storemc” on page 197 to make the FibreCAT CX / CLARiiON CX visible for the SMI-S Provider before executing the storcfg cimom –discover command.

5.3.3 Create StorMan 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 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 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 pool, use the parameter -restype dynamic.

Pools can be shown using

storcfg pool -show

5.3.4 Using existing storage volumes

To add devices to your 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.

Setting up StorMan configurations Setting up StorMan configurations using the CLI

U41824-J-Z156-1-76 71

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

5

5.3.5 Creating new storage volumes

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

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

It is also possible to specify no pool, but an array, or just a model, or just a size, or just a RAID type. In these cases StorMan looks for an appropriate 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.

5.3.6 Discover changes to a storage array

StorMan is able to detect configuration changes in the storage system automatically by means of the CIM-OM. However a discover process can be triggered by StorMan, e.g.:

● For one storage system use

storcfg system -discover -system serial-number

● For storage systems are visible to the CIM Server use

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

5.3.7 Remove a storage system

A storage array that is no longer managed by StorMan should be removed from StorMan configuration.

● To remove one storage system use:

storcfg system -rem –system sysname

● In case a CLARiiON CX / FibreCAT CX storage system is concerned you should also remove it from the EMC SMI-S Provider's repository:

storemc -rem ... –system system

● In case the removed storage system is the only visible to a specific CIM Server you should also remove the CIM server to avoid automatic re-discovery of the storage system:

storcfg cimom -rem -name hostname-of-the-cim-server

Diagnostic aids Setting up StorMan configurations

72 U41824-J-Z156-1-76

5.4 Diagnostic aids

5.4.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 recre-ation process using the StorMan CLI:

storparam –debug 5

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

stormandb –dump

Afterwards, collect the following files 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 saved StorMan database files AddData.sql and AddTables.sql (created by stormandb –dump) in the ./backup directory.

These files are located in the /var/opt/SMAWstor/StorMan directory for Linux environments and in the C:\Programme\Fujitsu\StorMan directory for Windows environments. In BS2000/OSD environments first the files have to be transmitted by ftp directly from POSIX to a Windows or Linux system.

Setting up StorMan configurations Diagnostic aids

U41824-J-Z156-1-76 73

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

02P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

5

5.4.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.

Diagnostic aids Setting up StorMan configurations

74 U41824-J-Z156-1-76

U41824-J-Z156-1-76 75

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

7

6 Administration and Provisioning tasks

6.1 Overview

Using the provisioning features of StorMan hosts can be provided with necessary storage resources managed by StorMan. All hosts which are allowed to request storage resources are managed in the StorMan database (repository). With the provisioning features a host can be added to the StorMan repository and storage resources be attached to or detached from this host. The provisioning of a host will be ended by removing it from the repository.

Provisioning features are supported by the StorMan GUI and CLI. The basic functions are available on both interfaces, but some functions are only available on the CLI.

Administration and Provisioning tasks using the GUI Administration and Provisioning tasks

76 U41824-J-Z156-1-76

6.2 Administration and Provisioning tasks using the GUI

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.

Following functions are available:

● Add a new host

● Remove a host

● Add a new WWPN

● Remove a WWPN

● Display devices available for provisioning (implicit function)

● Attach a device or a selection of devices

● Detach a device or a selection of devices

● Display attached devices (implicit function)

The StorMan help system contains the complete GUI functions reference. Refer to section “Using Help” on page 65.

Administration and Provisioning tasks Administration and Provisioning tasks using the CLI

U41824-J-Z156-1-76 77

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

7

6.3 Administration and Provisioning tasks using the CLI

This section is a description based on the StorMan CLI. If you prefer to use the GUI for configuration, see section “Administration and Provisioning tasks using the GUI” on page 76. For details about the CLI commands, refer to chapter “StorMan for programmers – CLI description” on page 99.

6.3.1 Add a new 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,ip-adr2,... -wwpn wwpn1,wwpn2,...

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

WWPNs are usally specified as 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 “storcfg host” on page 119 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.

6.3.2 Attach a logical device to a host

The devices contained in the 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

Administration and Provisioning tasks using the CLI Administration and Provisioning tasks

78 U41824-J-Z156-1-76

6.3.3 View the attachments to a device

Use the command

storcfg volume -show -storid myStorID -showconnections

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.

6.3.4 Detach a logical device from a host

Use the command

stordetach -storid myStorID -hostname myApplicationHost

6.3.5 Release a storage volume

Use the command

stordelete -storID myStorID

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

U41824-J-Z156-1-76 79

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

27.

Mai

200

9 S

tand

11

:19.

20P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

8

7 Replication tasks The Replication Service features support the management of local mirroring functions:

● local mirroring based on full volume copies (clones)

● local mirroring based on pointer based technologies (snaps)

This section is a description based on the StorMan CLI. Information function of the Repli-cation Service are supported by CLI and GUI. However, active management is supported by CLI only. An API is available for internal use only in particular for SHC-OSD.

I Please verify that you have set the parameter WithMirrors=1 in the smserver.ini file before using replication functions.

The following selection shows some typical actions to administrate volume level replications from the original to a snap or clone replication.

7.1 Working with full local mirrors (clones)

7.1.1 Creating clone pairs

To start a clone session for local mirroring or for migration purpose a clone pair is created. After starting the session the synchronization from source volume to target volume is started. The clone volume is no longer accessible to host.

stormirror -create -mirrortype full -source storid -target storid -waitforsync

7.1.2 Activating clone volumes

To use a clone volume by a second host or application independent to the source volume the clone unit has to be activated.

stormirror -activate -source storid -target storid

The consistency of data at the point in time of activation must be assured by the application:

Working with full local mirrors (clones) Replication tasks

80 U41824-J-Z156-1-76

7.1.3 Recreating clone pairs

After finishing independent processing of the target volume the clone pair can be recreated. By recreating all modifications done on the target volume are discarded and the changes on the source volume are resynchronized to the target volume. The target volume is no longer accessible by host.

stormirror -recreate -source storid -target storid

7.1.4 Restoring the source volume from the clone

In case that all changes on the source volume should be discarded, the clone volume can be restored to the source volume to restore the data from the point of activation of the clone pair. The target volume is no longer accessible by host.

stormirror -restore -source storid -target storid

7.1.5 Terminating a clone pair

A clone pair can be terminated to stop the mirroring relationship between source volume and target volume. Both volumes can be used independently further on.

stormirror -terminate -source storid -target storid

7.1.6 Information about clone pairs

The command

stormirror -show [ -storid storid ]

shows the information about a specific volume specified by its storid and all its mirroring related information.

Replication tasks Working with pointer based local mirrors (snapshots)

U41824-J-Z156-1-76 81

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

27.

Mai

200

9 S

tand

11

:19.

20P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

8

7.2 Working with pointer based local mirrors (snapshots)

7.2.1 Creating snapshot pairs

To start a snap session a snap pair is created by assigning a snap volume to a source volume.

stormirror -create -mirrortype snap -source storid -target snapstorid

7.2.2 Activating snapshots

To use a snapshot of the data on the source volume the snapshot must be activated and made accessible to the host. Afterwards a host or application may use the snap volume independent to the source volume.

stormirror -activate -source storid -target snapstorid

To make the activated snaphot accessible to a host it must be attached:

storattach -storid storid [ -hostname hostname ]

The consistency of data at the point in time of activation must be assured by the application:

7.2.3 Restoring the snap volume from the clone

In case that all changes on the source volume should be discarded, the snap volume can be restored to the source volume. The snap volume remains accessible by host.

stormirror -restore -source storid -target storid

7.2.4 Terminating a snap pair

A clone pair can be terminated to stop the mirroring relationship between source volume and target volume. Both volumes can be used independently further on.

stormirror -terminate -source storid -target storid

Working with pointer based local mirrors (snapshots) Replication tasks

82 U41824-J-Z156-1-76

7.2.5 Information about snap pairs

The command

stormirror -show [ -storid storid ]

shows the information about a specific volume specified by its storid and all its mirroring related information.

U41824-J-Z156-1-76 83

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

9

8 Statistics and performance tasks The statistic and performance features supported are suitable for monitoring of storage arrays mainly as used by openSM2 or in Managed Storage Service scenarios.

The statistic and performance monitoring features are provided on volume (LUN) level (without access to the StorMan repository), namely the following:

● reads per second

● writes per second

● KB read per second

● KB write per second

● Average IO times for reads and writes

These features are implemented by StorMan's Client Interface (API) and CLI. They provide XML-based output information as described in chapter “StorMan for programmers – StorMan Client interface for information and monitoring” on page 217. Currently the API is available only for internal use (in particular openSM2). The CLI is available for general use.

Evaluation

As StorMan’s storstat interface is providing counters and sampled metrics in conjunction with time stamp representing the absolute collection time for the statistics. The calling appli-cation has to calculate and normalize the values to obtain the metrics per second. This can be achieved by periodical calls in time intervals (tn, tm) calculating the rates for the delta = tm - tn.

1. To calculate the IO and KB values per second please use the following method:

ReadIOs per second delta ReadIOs( )delta statisticTime( ) s[ ]----------------------------------------------------------=

Statistics and performance tasks

84 U41824-J-Z156-1-76

2. To calculate the average read (or write) times for Symmetrix please use the following method:

3. To calculate the time values for FibreCAT CX / CLARiiON CX please consider the following:

– Time metrics for FibreCAT CX / CLARiiON CX storage systems do not distinguish between Reads and Writes. On FibreCAT CX / CLARiiON CX level the IOSer-viceTime is defined as the average time for IOs elapsed in the storage system (in msec). This value does not differentiate reads and writes as not supported by Storage Array. It does not include any waiting time (which would correspond to a Response Time).

– A volume IOServiceTime is pretty much the time that the system is actively working on a single volume (LUN) request. This is an average number over all requests within a sampling interval and it does exclude the waiting time in any queues.

Therefor IOServiceTime for a volume is expressed as:

This value can be calculated based on the metrics delivered by StorMan using:

with: delta(ReadIOs + WriteIOs) are the cumulated reads and writes during one sample period

Note An evaluation tool has to assure to get statistical data at least once during one sample interval (default value: 5 min).

AverageReadTime μs[ ] delta SampledReadsTime( )delta SampledReadsCounter( )-------------------------------------------------------------------------------=

AverageWriteTime μs[ ] delta SampledWriteTime( )delta SampledWriteCounter( )----------------------------------------------------------------------------=

IOService Time UtilizationThroughput------------------------------=

Utilization delta IOTimeCounter( )delta IOTimeCounter IdleTimeCounter+( ) delta StatisticTime( )×----------------------------------------------------------------------------------------------------------------------------------------------------------------------=

Throughput delta ReadIOs WriteIOs+( )=

Statistics and performance tasks Setting up StorMan configuration using the CLI

U41824-J-Z156-1-76 85

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k0

9

8.1 Setting up StorMan configuration using the CLI

The following steps are necessarey to set up and enable a new installed StorMan to deliver statistical data based on the existing StorMan CLI. For a detailed CLI description please refer to chapter “StorMan for programmers – CLI description” on page 99.

Specify the CIM Servers

The CIM Servers hosting the SMI-S Provider from EMC Corp. must be contained in StorMan’s configuration to allow the communication between StorMan and SMI-S Provider.

Ê Execute the command

storcfg cimom -add -name myCimHost

to configure the name of the host(s) running the CIM Server in StorMan. A process to discover the storage systems visible by the SMI-S Provider starts automatically.

If your CIM Server is user + password protected, you have to specify these as part of this command.

Ê Verify the results with

storcfg cimom -show

and


(Re-)Discover storage systems


storcfg cimom -discover -name myCimHost

This starts a discovery of the storage systems by the CIM Server and enables StorMan to find the relations between the CIM Server and the connected storage systems. This command is helpful in case a new storage system was connected to an existing SMI-S provider or to rediscover a temporary not available storage system.

Ê Verify the results with


If FibreCAT CX / CLARiiON CX systems without FC connection are administrated, use the stormanemc command to make the FibreCAT CX / CLARiiON CX visible for the SMI-S Provider before executing the storcfg cimom –discover command.

Getting statistics Statistics and performance tasks

86 U41824-J-Z156-1-76

Example

storemc -add -name myCimHost -sp CXSPA,CXSPB -cxuser CXADMIN -cxpwd CXADMIN

Discover the storage system (storcfg cimom –discover …) is also required after executing the storemc command.

8.2 Getting statistics

The storstat command delivers statistical data (refer to “storstat” on page 211).

Statistical data for volumes


storstat volume -get -system *308

to get the statistic data for all volumes of the storage system with serial number *308 (wildcard specification).

U41824-J-Z156-1-76 87

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

0

9 Special properties of storage systems

9.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 volume configuration management (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.

9.1.1 Dynamic creation of storage volumes / logical devices

If required by the storcreate function, StorMan checks existing storage pools (RAID groups) with the desired RAID type in the storage system. If one with the requested available size is found, a new volume is created in that RAID group. If no RAID Group with the requested size and RAID Type is found, StorMan / SMI-S-Provider tries to create a new one. Keep in mind, that the number of unallocated disks required for that is depending on the RAID type.

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 recom-mended to configure the amount of required volumes before they are required by any appli-cations using StorMan or the storage system specific administration tools in order to keep the time for provisioning short.

https://powerlink.emc.com

Special properties of EMC storage systems Special properties of storage systems

88 U41824-J-Z156-1-76

Especially on Symmetrix systems, it is recommendable to use the Symmetrix-specific tools to create volumes because Storman V2.0 can only create one volume per StorMan request and each request causes a time-consuming reconfiguration.

A Symmetrix volume created dynamically by StorMan V2.0 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 V2.0 with SMI-S 1.2 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 6 NO YES Starting with FibreCAT CX 3-xx models.RAID 6 feature has to be activated onSymmetrix systems

RAID 1-0 YES NO

RAID 3 YES NO

RAID-S NO YES

Unprotected (Disk) YES YES

Special properties of storage systems Special properties of EMC storage systems

U41824-J-Z156-1-76 89

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

0

9.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 volumes from a server with StorMan, the specified volumes are 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,


90 U41824-J-Z156-1-76

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 “Host storage connections (SPCs)” on page 95 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.

V 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.

V 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.

Volumes property hostaccess: If AccessLogix is disabled or not activated on a FibreCAT CX/ CLARiiON, all volumes can be accessed by all connected hosts. In that case the property hostaccess of the volumes has the value allconnected, otherwise the hostaccess (refer to storcfg volume –show command) is controlled by lun masking and the property has the value restricted.


U41824-J-Z156-1-76 91

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

0

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 naviseccli command naviseccli -h sp-name port -list –all. Regis-tration 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 and 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 and failovermode for your FibreCAT CX / CLARiiON CX using

naviseccli -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).

Attach with unconnected FC-HBAs on a FibreCAT CX / CLARiiON CX system

The Masking functionality on FibreCAT CX systems is based on WWPNs and WWNNs.

Therefore, if volumes should be attached to a server who's HBA's haven't been connected to the FibreCAT CX / CLARiiON CX so far, the WWPNs for this server have to be specified together with their WWNN (“world wide node name”) in the format <wwpnwwnn> by using the CLI command storcfg host -add or storcfg host -mod as described in section “storcfg host” on page 119.



92 U41824-J-Z156-1-76

9.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 V2.0 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”). On Symmetrix systems, entries in the ”Login History Table” (LHT) are also represented by SPCs. So if an active HBA is connected to the Symmetrix, this is an SPC that defines a FC connection that is used by StorMan for ”attach/detach” requests.



U41824-J-Z156-1-76 93

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

0

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 volumes are added to them, and become visible for that HBAs via the related Symmetrix target ports. The attach function is refused if the complete amount of volumes is not mapped to those ports! No new SPCs (VCM records) are created in this case.

You cannot specify target ports for an attach request with StorMan 2.0. If no VCM records (SPC) exist for HBAs which are to be attached, StorMan first checks the mapping of the specified volumes. If all volumes are mapped to the same amount of target ports, StorMan will create one VCM record for each initiator and each of those target ports. StorMan does not modify the Mapping in Symmetrix systems. Once VCM records exist for a HBA, StorMan


94 U41824-J-Z156-1-76

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.

V 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.

Volumes property hostaccess: If a volume is mapped to FC ports on which LUN masking is not enabled, it's property hostaccess will have the value allconnected. In this case it is accessible by all connected hosts via these ports. Otherwise it has the value restricted and the hostaccess is controlled by lun masking.

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.


U41824-J-Z156-1-76 95

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

0

9.1.4 Host storage connections (SPCs)

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

● The first attach 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 also removes the related LHT entries on Symmetrix systems (if Enginuity version = 5671 or higher) and the related entries in the "Initiatorlist" on FibreCAT CX systems (only if the HBA is not FC logged in). Setting destroyconnection is recommended 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.

– Single HBAs have been connected to another target port on a Symmetrix system and the old connection can be removed.

In all other cases the parameter should not be set (default value).

Special properties of NetApp storage systems Special properties of storage systems

96 U41824-J-Z156-1-76

9.2 Special properties of NetApp storage systems

9.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 appli-cation 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.

9.2.2 LUN mapping and LUN masking

LUN masking in NetApp systems is performed by “igroups” (initiator groups). Different initi-ators, 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 V2.0 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 NetApp UI or detach the LUNs already attached for the single WWPNs of the host using destroyconnection.

Special properties of storage systems Special properties of NetApp storage systems

U41824-J-Z156-1-76 97

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

03P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

0

Figure 5: iGroups in a NetApp Architecture

Although a NetApp 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 NetApp 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 NetApp systems

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

luns

Server_1 Server_2

Port 1

HBA1 HBA2 HBA1 HBA2

Stdby-Port

igroup1 igroup1

Fabric

WWPN1

WWPN2WWPN3

WWPN4

Special properties of NetApp storage systems Special properties of storage systems

98 U41824-J-Z156-1-76

U41824-J-Z156-1-76 99

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

15:0

6.53

Pfa

d: O

:\al

f\sto

rma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\c

li_in

tro.

doc

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

10.1 General

10.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.

General StorMan for programmers – CLI description

100 U41824-J-Z156-1-76

Connection parameters

All commands need a connection to the StorMan Server. The necessary connection param-eters 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 substitutes 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.

I Up to StorMan V2.0 some output values/ structures and xml / xmlp format have been changed to improve the xml support.

StorMan for programmers – CLI description General

U41824-J-Z156-1-76 101

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

15:0

6.53

Pfa

d: O

:\al

f\sto

rma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\c

li_in

tro.

doc

10.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 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 pool for storage unit creation as well as when attaching (accessing) a storage unit which has already been created for a host.

StorMan resource types

The enumeration STORMAN_RESOURCE_TYPE defines the resource type property which desig-nates a pool resource (to be) reserved.

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

Value Meaning

STORMAN_RESOURCE_TYPE_ANY Indicates that the storage unit requested for reser-vation 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


102 U41824-J-Z156-1-76

StorMan connection types

The enumeration STORMAN_CONNECTION_TYPE represents possible connection type values. Connection type SAN is supported only with StorMan V1.3. In version V2.0 and higher this connection type is replaced (incompatible) by connection type FC.

StorMan storage models

The enumeration STORMAN_STORAGE_MODEL represents a list of supported storage system models.

Storman volume status

The enumeration STORMAN_VOLUME_STATUS represents a list of supported of volume status.

Value Meaning

STORMAN_CONNECTION_TYPE_ANY No specific storage type requested

STORMAN_CONNECTION_TYPE_FC SAN connected by FC

STORMAN_CONNECTION_TYPE_ISCSI SAN connected by iSCSI

STORMAN_CONNECTION_TYPE_SAS SAN connected by SAS (serial attached SCSI)

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 / CLARiiON CX storage system

STORMAN_STORAGE_MODEL_NETAPPFILER NetApp Filer from NetApp

STORMAN_STORAGE_MODEL_FIBRECAT_SX FibreCAT SX storage system

Value Meaning

STORMAN_VOLUME_STATUS_ANY No specific status requested

STORMAN_VOLUME_STATUS_UNKNOWN State of volume is not known

STORMAN_VOLUME_STATUS_READY Storage volume is in status READY

STORMAN_VOLUME_STATUS_NOT_READY Storage volume is in status NOT_READY

STORMAN_VOLUME_STATUS_READ_ONLY Storage volume is in status READ_ONLY

STORMAN_VOLUME_STATUS_ERROR Storage volume is in status ERROR


U41824-J-Z156-1-76 103

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

15:0

6.53

Pfa

d: O

:\al

f\sto

rma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\c

li_in

tro.

doc

Storman RAID levels

The enumeration STORMAN_RAID_LEVEL represents a list of supported raid levels.

Storman mirror volume usage

The enumeration STORMAN_MIRROR_VOLUME represents a list of supported values for the usage of a volume in mirroring relationships.

Storman mirror type usage

The enumeration STORMAN_MIRROR TYPE represents a list of supported values for the mirroring mode.

Value Meaning

STORMAN_RAID_LEVEL_ANY No specific RAID requested

STORMAN_RAID_LEVEL_UNKNOWN Unknown RAID level

STORMAN_RAID_LEVEL_DISK No RAID level

STORMAN_RAID_LEVEL_0 Striped

STORMAN_RAID_LEVEL_1 mirrored disk

STORMAN_RAID_LEVEL_10 mirrored disk with striping

STORMAN_RAID_LEVEL_3 striping with parity

STORMAN_RAID_LEVEL_5 striping with distributed parity

STORMAN_RAID_LEVEL_6 striping with 2 distributed parities

Value Meaning

STORMAN_MIRROR_VOLUME_NONE Not used for mirroring

STORMAN_MIRROR_VOLUME_ORIG_LOCAL Used as original in local mirroring relationship

STORMAN_MIRROR_VOLUME_MIRROR_LOCAL Used as local mirror

STORMAN_MIRROR_VOLUME_UNKNOWN Unknown mirroring relationship

STORMAN_MIRROR_VOLUME_ANY No specific mirroring requested

Value Meaning

STORMAN_MIRROR_TYPE_NONE No mirror type

STORMAN_MIRROR_TYPE SNAP Used as snap

STORMAN_MIRROR_TYPE FULL Used as full mirror

STORMAN_MIRROR_TYPE_UNKNOWN Unknown mirror information


104 U41824-J-Z156-1-76

Storman mirror pair status

The enumeration STORMAN_MIRROR_PAIR_STATUS represents a list of supported of volume status.

Value Meaning

STORMAN_MIRROR_PAIR_STATUS_INITIALIZING Mirror pair is in initialization

STORMAN_MIRROR_PAIR_STATUS_INITIALIZED Mirror pair is initialized

STORMAN_MIRROR_PAIR_STATUS_INACTIVE Mirror pair is inactive (Snaps only)

STORMAN_MIRROR_PAIR_STATUS_FAILED Mirror pair is broken after a failure

STORMAN_MIRROR_PAIR_STATUS_TERMINATING Mirror pair is in termination

STORMAN_MIRROR_PAIR_STATUS_RESTORING Mirror pair is restoring to original

STORMAN_MIRROR_PAIR_STATUS_RESYNCING Mirror pair is resyncing to mirror

STORMAN_MIRROR_PAIR_STATUS_SPLIT Mirror pair is split but out of synch, the mirror is accessible from host

STORMAN_MIRROR_PAIR_STATUS_SPLIT_AND_SYNC Mirror pair is split and synchronized, the mirror is accessible from host

STORMAN_MIRROR_PAIR_STATUS_SUSPENDED Mirror pair is suspended, the mirror is not accessible from host

STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZING Mirror pair is synchronizing

STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZED Mirror pair is synchronized, the mirror is not accessible from host

STORMAN_MIRROR_PAIR_STATUS_NOT_APPLICABLE pair status is not applicable to the pair


U41824-J-Z156-1-76 105

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

15:0

6.53

Pfa

d: O

:\al

f\sto

rma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\c

li_in

tro.

doc

10.1.3 Common supported value ranges

All StorMan commands have some common parameters with a defined range of supported values specified below:

The wildcard '*' is supported for alphabetic character strings as specified in the CLI description. Generally it can be used at any place of the string. Please note that for BS2000/OSD platforms the wildcard '*' is interpreted as the last character of a string i.e. any character(s) following the wildcard '*' are ignored.

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 253 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 253 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 or 32 hexadecimal numbers delimited by ':', '-' or without delimiter

U41824-J-Z156-1-76 106

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.04

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

ora

ttac

h.do

c

10.2 storattach

Makes one or multiple storage volumes visible for a host using the LUN masking capabilities of the storage system.

Syntax

Parameters

–storid storid[,...]

Specifies the previously assigned storID(s) of one or a list of source volumes as unique identifier(s). This parameter is mandatory.

–hostname hostname

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 one or a list for the device number(s) that can be seen by the host.Possible values: 0..255; e.g. –hostlun 128. If this parameter is not specified, they are 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 is 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

Refer to the description of the “Connection parameters” on page 100.

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

storattach

U41824-J-Z156-1-76 107

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.04

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

ora

ttac

h.do

c

Notes

● -storid must be specified to specify the storage unit(s).

● 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 infor-mation 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.

storattach

108 U41824-J-Z156-1-76

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 and 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_AVAILABLE

CIM Server or database not available

23 STORMAN_BAD_CONFIG Illegal LUN masking configuration found in a ClariiON system or mapping and masking do not fit in a Symmetrix (see section “LUN masking in FibreCAT CX / CLARiiON CX systems” on page 89 for details)

25 STORMAN_CIMOM_AUTH_FAILED

User / password for CIM Server not valid

U41824-J-Z156-1-76 109

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

04P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101

_bhb

\pro

d_e

\sto

rma

n.v1

1\st

orc

heck

.do

c

10.3 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 accessible.

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

Syntax

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

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


0 STORMAN_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


U41824-J-Z156-1-76 110

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4 storcfg

The storcfg command is used to configure the StorMan repository.

The first parameter specifies the object group of the repository that is configured:

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

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

storcfg object –function –functionparam ... –connectparam ...

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

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)

storcfg

U41824-J-Z156-1-76 111

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.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.

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

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

storcfg

112 U41824-J-Z156-1-76

10.4.1.1 storcfg host –add

Adds a new host to the StorMan repository.

Syntax

Parameters

–name hostname

Specifies the name of the host.

Refer to the common description of “hostname” on page 105.

–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.

–iqn iqn[,...]

Specifies a list of IQNs for iSCSI connected storage delimited by comma.

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

–connectparam


Return codes

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





13 STORMAN_COMMUNIC_ERROR Error in StorMan communication between client and server


20 STORMAN_ALREADY_EXISTS Object already exists in repository

storcfg

U41824-J-Z156-1-76 113

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.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

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.

–iqn iqn

Identifies the host by a IQN belonging to the host.

Exactly one of the parameters –name, –ip, -wwpn or -iqn 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.




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


storcfg

114 U41824-J-Z156-1-76

–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.

–newiqn iqn[,…]

A list of IQN's delimited by comma to assign to the host.

–addiqn iqn

Assign a single IQN to the host.

–remiqn iqn

Deassign a single IQN 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.

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

storcfg

U41824-J-Z156-1-76 115

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

Return codes







18 STORMAN_NOT_FOUND Specified host could not be found




storcfg

116 U41824-J-Z156-1-76

10.4.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

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.

–iqn iqn

Identifies the host by a IQN belonging to the host.

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

–connectparam


Return codes

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







18 STORMAN_NOT_FOUND Specified host could not be found

22 STORMAN_RESOURCE_NOT_ AVAILABLE


storcfg

U41824-J-Z156-1-76 117

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.1.4 storcfg host –show

Displays information related to the specified hosts.

Syntax

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

–iqn iqn

Selection by the IQN 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


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

storcfg

118 U41824-J-Z156-1-76

Return codes

Examples

1. Output for hosts with –format std (default)

storcfg host –show –name d*

hostID type STORMAN_HOSTID_TYPE_NAMEhostID ducksoup hostname ducksoup no IPs found WWPNs: 210000C09F956746 210000C09F956747 no IQNs found

2. Output for hosts with –format xmlp

storcfg host –show –name d* -format xmlp

<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <Text>Successful</Text> <SubCode>0</SubCode> <SubCodeText>STORMAN_SUB_NONE</SubCodeText> </ReturnCode> <Result> <Host> <HostIDType>STORMAN_HOSTID_TYPE_NAME</HostIDType> <HostID>ducksoup</HostID> <HostName>ducksoup</HostName> <IPs> </IPs>









storcfg

U41824-J-Z156-1-76 119

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

<WWPNs> <WWPN>210000C09F956746</WWPN> <WWPN>210000C09F956747</WWPN> </WWPNs> <IQNs> </IQNs> </Host> </Result></Response>

storcfg

120 U41824-J-Z156-1-76

10.4.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.

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 repos-itory

–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

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

storcfg

U41824-J-Z156-1-76 121

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.2.1 storcfg cimom –add

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

Syntax

Parameters

–name hostname

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


–ip ip

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

–http port

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

–interface type

Specifies the interface type for the hostname:

-interface smis (default) for CIM-OMs.

-interface netappapi for API Server of NetApp filers.

–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).

–discover discover

Specifies if any discover should be done for the new CIM-OM:

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

storcfg

122 U41824-J-Z156-1-76

-discover no starts no discover for the CIM-OM.

-discover query (default) starts the discover for known storage systems.

-discover deep starts a discover operation on the CIM-OM to update the CIM-OMs view on storage systems (may last some minutes depending on configuration).

By specifying this operand an additional call of storcfg cimom -discover … can be omitted.

At least 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 NetApp 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










CIM server or database not available

storcfg

U41824-J-Z156-1-76 123

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.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

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.

–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.

–interface type

Specifies the interface type for the hostname.

-interface smis (default) for CIM-OMs.

-interface netappapi for API Server (NetApp filers).

–newinterface type

Specifies the new interface type for the hostname:

-newinterface smis for CIM-OMs.

-newinterface netappapi for API Server (NetApp filers)

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

storcfg

124 U41824-J-Z156-1-76

–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.

–discover discover

Specifies if any discover should be done for the CIM-OM:

-discover no starts no discover for the CIM-OM.

-discover query (default) starts the discover for known storage systems.

-discover deep starts a discover operation on the CIM-OM to update the CIM-OMs view on storage systems (may last some minutes depending on configuration).

By specifying this operand an additional call of storcfg cimom -discover … can be omitted.

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

–connectparam


Return codes








18 STORMAN_NOT_FOUND Specified host was not found



storcfg

U41824-J-Z156-1-76 125

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.2.3 storcfg cimom –rem

Removes the CIM-OM or the API Server from the StorMan repository. The Storage Arrays and their corresponding 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

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


–http port

Specifies the port the CIM-OM is listening on .

–interface type


-interface smis for CIM-OMs.


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

–connectparam


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

storcfg

126 U41824-J-Z156-1-76

Return codes










storcfg

U41824-J-Z156-1-76 127

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.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.

I When adding a new CIM-OM or modifying a CIM-OM’s attributes with storcfg cimom –add or storcfg cimom –mod a discover parameter can directly be used to request the CIM-OM to discover all available storage systems.

Syntax

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


–http port

Specifies the port the CIM-OM is listening on.

–interface type


-interface smis for CIM-OMs.


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

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

storcfg

128 U41824-J-Z156-1-76

–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











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

storcfg

U41824-J-Z156-1-76 129

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.2.5 storcfg cimom –show

Displays information related to hosts hosting CIM-OMs.

Syntax

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


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

storcfg

130 U41824-J-Z156-1-76

Return codes

Examples

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

storcfg cimom –show

hostID type STORMAN_HOSTID_TYPE_NAMEhostID localhost hostname localhost IP interop interop http port 5988 user running true interface STORMAN_INTERFACE_TYPE_SMIS version V3.3.2.0










storcfg

U41824-J-Z156-1-76 131

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

2. Output for CIM-OMs with –format=xmlp

storcfg cimom –show -format

<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <Text>Successful</Text> <SubCode>0</SubCode> <SubCodeText>STORMAN_SUB_NONE</SubCodeText> </ReturnCode> <Result> <CIMOM> <HostIDType>STORMAN_HOSTID_TYPE_NAME</HostIDType> <HostID>localhost</HostID> <Name>localhost</Name> <IP/> <PortHttp>5988</PortHttp> <User/> <Password/> <InteropNamespace>interop</InteropNamespace> <IsRunning>true</IsRunning> <InterfaceType>STORMAN_INTERFACE_TYPE_SMIS</InterfaceType> <VersionString>V3.3.2.0</VersionString> </CIMOM> </Result></Response>

storcfg

132 U41824-J-Z156-1-76

10.4.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 automati-cally added to the StorMan repository only as a result of a storcfg cimom –discover call.

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

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

storcfg

U41824-J-Z156-1-76 133

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.3.1 storcfg system –rem

Removes the storage system from the StorMan repository.

If 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 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

Parameters

–system sysname

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

–connectparam


Return codes

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









storcfg

134 U41824-J-Z156-1-76

10.4.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

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

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







18 STORMAN_NOT_FOUND Matching object could not be provided





storcfg

U41824-J-Z156-1-76 135

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.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.

Syntax

Parameters

–system sysname

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

–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.

–showstoragepools

Displays also the storage pools of the storage systems with –format std. The xml output always contains these informations.

–showports

Displays also the storage port information of the storage systems with –format std. The xml output always contains these informations.

–showraidtypes

Displays also the RAID types supported by the storage systems with –format std. The xml output always contains these informations.

storcfg system –show [ –system sysname ] [ –model model ] [ –unmanaged ] [ –showstoragepools ] [ –showports ] [ –showraidtypes ] [ –extended ][ –format format ] –connectparam ...

storcfg

136 U41824-J-Z156-1-76

–extended

Displays extended logical and physical information about the storage system including FRU (Field Replaceable Unit) information. Two input modes are supported:

– If only the extended parameter is specified: Displays an information overview about all storage systems with available extended information.

– If the extended parameter and -system sysname are specified: Displays the complete and detailed information for the specified storage system.

All other parameters are rejected if the extended parameter is specified.

This option is currently supported for CLARiiON CX, FibreCAT CX and FibreCAT SX storage systems.

–format format






–connectparam


Return codes










storcfg

U41824-J-Z156-1-76 137

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

Examples

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

storcfg system -show –model clariion -showports -showstoragepools -showraidtypes

storage system name = CLARiiON+CK200041600121 serial number = CK200041600121 storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION storage model name = Rack Mounted CX500 OS = Flare OS version = 2.26.500.5.014 cache size = 4GB physical disks = 29 logical volumes = 191 masking enabled = yes configuration state = Ok storage port(s) = 500601601020F77C/FC/SP_A:0 500601611020F77C/FC/SP_A:1 500601681020F77C/FC/SP_B:0 500601691020F77C/FC/SP_B:1 storage pool(s) = P+Primordial usage = DMTF_STORAGE_POOL_USAGE_UNRESTRICRED status = STORMAN_STORAGE_POOL_STATUS_OK enabled size = 1730GB free size = 32756MB percent full = 98 S+GLOBAL usage = DMTF_STORAGE_POOL_USAGE_LOCAL_REPLICA status = STORMAN_STORAGE_POOL_STATUS_OK enabled size = 31GB free size = 31GB percent full = 0 . . . supp. raid type(s) = RAID0 RAID1-0 RAID1 RAID5 RAID6 UNPROTECTED

storcfg

138 U41824-J-Z156-1-76

2. Output for storage systems –format=xmlp

storcfg system -show –model clariion -showports -showstoragepools -showraidtypes

<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <Text>Successful</Text> <SubCode>0</SubCode> <SubCodeText>STORMAN_SUB_NONE</SubCodeText> </ReturnCode> <Result> <StorageSystem> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <StorageSerialNumber>CK200041600121</StorageSerialNumber> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <StorageModel>STORMAN_STORAGE_MODEL_CLARIION</StorageModel> <StorageModelName>Rack Mounted CX500</StorageModelName> <OSName>Flare</OSName> <OSVersion>2.26.500.5.014</OSVersion> <CacheSize>4294967296</CacheSize> <NumOfPhysDisks>29</NumOfPhysDisks> <NumOfVolumes>191</NumOfVolumes> <MaskingEnabled>STORMAN_BOOL_TRUE</MaskingEnabled> <PrimaryHostAccessController/> <ConfigID>20081119070338.000000+000+9</ConfigID> <LastChecked>1227078256282000</LastChecked> <ConfigState>0</ConfigState> <StoragePorts> <StoragePort> <PortID>500601601020F77C</PortID> <PortName>SP_A:0</PortName> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </StoragePort> <StoragePort> <PortID>500601611020F77C</PortID> <PortName>SP_A:1</PortName> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </StoragePort> <StoragePort> <PortID>500601681020F77C</PortID> <PortName>SP_B:0</PortName> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </StoragePort> <StoragePort> <PortID>500601691020F77C</PortID>

storcfg

U41824-J-Z156-1-76 139

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

<PortName>SP_B:1</PortName> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </StoragePort> </StoragePorts> <StoragePools> <StoragePool> <PoolName>P+Primordial</PoolName> <Status>STORMAN_STORAGE_POOL_STATUS_OK</Status> <EnabledSize>1858057797632</EnabledSize> <FreeSize>34348102656</FreeSize> <PercentFull>98</PercentFull> <PoolUsage>DMTF_STORAGE_POOL_USAGE_UNRESTRICRED</PoolUsage> <StatusString>OK</StatusString> <OwningController/> <RaidType>RAID0</RaidType> <NumDisks>29</NumDisks> <NumSpares>0</NumSpares> </StoragePool> <StoragePool> <PoolName>S+GLOBAL</PoolName> <Status>STORMAN_STORAGE_POOL_STATUS_OK</Status> <EnabledSize>33285996544</EnabledSize> <FreeSize>33285996544</FreeSize> <PercentFull>0</PercentFull> <PoolUsage>DMTF_STORAGE_POOL_USAGE_LOCAL_REPLICA</PoolUsage> <StatusString>OK</StatusString> <OwningController/> <RaidType>Unknown</RaidType> <NumDisks>1</NumDisks> <NumSpares>0</NumSpares> </StoragePool> . . . </StoragePools> <SupportedRaidTypes> <SupportedRaidType>RAID0</SupportedRaidType> <SupportedRaidType>RAID1-0</SupportedRaidType> <SupportedRaidType>RAID1</SupportedRaidType> <SupportedRaidType>RAID5</SupportedRaidType> <SupportedRaidType>RAID6</SupportedRaidType> <SupportedRaidType>UNPROTECTED</SupportedRaidType> </SupportedRaidTypes> </StorageSystem> </Result></Response>

storcfg

140 U41824-J-Z156-1-76

10.4.4 storcfg pool

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

Functions


–add

adds a new pool to the StorMan repository

–mod

modifies the attributes of an existing pool or renames the pool

–rem

removes a pool from the StorMan repository

–show

displays information related to pools

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

storcfg

U41824-J-Z156-1-76 141

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.4.1 storcfg pool –add

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

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

Syntax

Parameters

–poolid poolid

Specifies the ID of the pool. This parameter is mandatory.Refer to the common description of “poolid” on page 105.

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 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 pool, i.e. if dynamic creation of new logical volumes in the storage system is allowed for this pool

-restype predefined (default value) allows no dynamic creation

-restype dynamic allows dynamic creation

–access access

Specifies whether volumes in this 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


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

storcfg

142 U41824-J-Z156-1-76

Return codes








19 STORMAN_POOLID_IN_USE Pool ID is in use

20 STORMAN_ALREADY_EXISTS Object already exists in the repository



storcfg

U41824-J-Z156-1-76 143

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.4.2 storcfg pool –mod

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

Syntax

Parameters

–poolid poolid

Specifies the ID of the pool. This parameter is mandatory.Refer to the common description of “poolid” on page 105.

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

–newpoolid poolid

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

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

–newrestype restype

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

-newrestype predefined allows no dynamic creation.

-newrestype dynamic allows dynamic creation.

–newaccess access

Specifies whether volumes in this 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


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

storcfg

144 U41824-J-Z156-1-76

Return codes







18 STORMAN_NOT_FOUND Specified pool was not found

19 STORMAN_POOLID_IN_USE Pool ID already used otherwise



storcfg

U41824-J-Z156-1-76 145

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.4.3 storcfg pool –rem

Removes a pool from the StorMan repository.

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

Therefore the contents of the 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

Parameters

–poolid poolid

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

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

Return codes

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







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



storcfg

146 U41824-J-Z156-1-76

10.4.4.4 storcfg pool –show

Displays information related to pools.

Syntax

Parameters

–poolid poolid

Specifies the ID of the 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 pool, i.e. if dynamic creation of new logical volumes in the storage system is allowed for the pools. Supported values: predefined | dynamic | any (default)

–model model

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

––access access

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

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

storcfg

U41824-J-Z156-1-76 147

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

–format format

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





–connectparam


Return codes

Examples

1. Output for pools with –format std (default)

storcfg pool –show –poolid ralf*

pool ID = Ralf1-0 storage system name = CLARiiON+CK200041600121 storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION resource type = STORMAN_RESOURCE_TYPE_PREDEFINED allowed access = STORMAN_ACCESS_MODE_SHARED









storcfg

148 U41824-J-Z156-1-76

2. Output for pools with –format xmlp

storcfg pool –show –poolid ralf* -format xmlp

<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <Text>Successful</Text> <SubCode>0</SubCode> <SubCodeText>STORMAN_SUB_NONE</SubCodeText> </ReturnCode> <Result> <PoolDescription> <PoolID>Ralf1-0</PoolID> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <StorageModel>STORMAN_STORAGE_MODEL_CLARIION</StorageModel> <ResourceType>STORMAN_RESOURCE_TYPE_PREDEFINED</ResourceType> <AllowedAccess>STORMAN_ACCESS_MODE_SHARED</AllowedAccess> </PoolDescription> </Result></Response>

storcfg

U41824-J-Z156-1-76 149

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

10.4.5 storcfg volume

storcfg volume is used to manage the logical volumes in the pools of the StorMan repos-itory.

Functions


–add

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

–mod

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

–rem

removes a logical volume from the pool of StorMan repository

–discover

requests to discover a logical volume on a storage system, i.e. to update the configu-ration data of the specified logical volume

–show

displays information related to logical volumes

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

storcfg

150 U41824-J-Z156-1-76

10.4.5.1 storcfg volume –add

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

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

Syntax

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 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” on page 105.

– 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.

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

storcfg

U41824-J-Z156-1-76 151

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

–poolid poolid

Specifies the ID of the 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





9 STORMAN_STORID_IN_USE StorID already used otherwise


14 STORMAN_STORAGE_LOCKED Storage unit to be modified currently locked








storcfg

152 U41824-J-Z156-1-76

10.4.5.2 storcfg volume –mod

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


Syntax

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 pool to which the logical volume should be moved by its pool ID. The current pool is implicitly specified by the storID or the device ID of the logical volume.Both 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 105.

–connectparam


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

storcfg

U41824-J-Z156-1-76 153

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

Return codes









18 STORMAN_NOT_FOUND Matching object (Storage Volume) could not be provided






storcfg

154 U41824-J-Z156-1-76

10.4.5.3 storcfg volume –rem

Removes a logical volume from a pool of StorMan repository.

Syntax

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


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

–system sysname


–connectparam


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

storcfg

U41824-J-Z156-1-76 155

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

Return codes













storcfg

156 U41824-J-Z156-1-76

10.4.5.4 storcfg volume –discover

Starts a discovery call to the storage system for a specific logical volume to update its configuration and attributes. The specified volume can be contained in a pool or not.

Syntax

Parameters

–storid storid

This parameter is used 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.

–system sysname


–deviceid devid


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.

–connectparam


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

storcfg

U41824-J-Z156-1-76 157

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

Return codes


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

14 STORMAN_STORAGE_LOCKED Storage unit to be discovered currently locked.

16 STORMAN_FAULT Unexpected error in function.

18 STORMAN_NOT_FOUND Matching object (Storage Volume) could not be provided.





User / password for CIM Server not valid.

storcfg

158 U41824-J-Z156-1-76

10.4.5.5 storcfg volume –show

Displays information related to logical volumes.

Selection criteria can be specified using the function parameters.

Syntax

Parameters

–storid storid

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

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

–poolid poolid

Specifies the ID of a 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.

–deviceid devid

Specifies the device ID of the logical volume. (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).

storcfg volume –show [ –storid storid ] [ –poolid poolid ] [ –system sysname ] [ –deviceid devid ] [ –restype restype ] [ –minsize minsize ][ –maxsize maxsize ] [ –model model ] [ –hostname hostname ] [ –hostip ip ] [ –hostwwpn wwpn ][ –hostiqn iqn ] [ –hostlun lun ] [ –access access ] [ –hostaccess hostaccess ] [ –withunmanaged] [ –showconnections] [ –showmirrors] [ –mirrortype mirrortype] [ –mirrorusage mirrorusage] [ –targetostype ostype ] [ –raidtype raidtype] [ –format format ] –connectparam ...

storcfg

U41824-J-Z156-1-76 159

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

–maxsize maxsize

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

–model model

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


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.

–hostiqn iqn

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

–hostlun lun

Selects by the device number of the host the storID of is attached to. If –showconnections is specified only this connection is displayed.

–access access

Selects by the storman setting for multiple host access to the storage volume. Supported values: exclusive | shared | any (default).

–hostaccess hostaccess

Selects storage volumes according to their visibility to hosts (defined by lun mapping/ masking). Supported Values: restricted | allconnected | any (default). See also section “LUN masking in FibreCAT CX / CLARiiON CX systems” on page 90 and section “LUN masking in Symmetrix systems” on page 94.

storcfg

160 U41824-J-Z156-1-76

–withunmanaged

Displays also volumes which are not managed by StorMan (i.e. volumes which are not contained in the repository).

–showconnections

Displays also the host connections of the volumes (with output format std).

–showmirrors

Displays also assigned mirror volumes (with output format std).

–mirrorusage mirrorusage

Selects by the usage of the volume for mirroring (replication) functions (default: any).

Supported values: origlocal | mirrorlocal | any (default)

any selects the pairs regardless of their mirror usage.

origlocal selects original volumes of local mirror pair(s).

mirrorlocal selects mirror volumes of local mirror pair(s).

–mirrortype mirrortype

Specifies the mirror type of the volume for mirroring (replication) functions.

Supported values: snap | full | any (default)

any selects the mirroring feature defined by the specified mirror pair(s).

snap selects snapshot (pointer based) mirror pair(s).

full selects full copy mirror pairs.

–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)

–raidtype raidtype

Selects by the RAID type of the volume (default: any).

any selects the volumes regardless of the RAID type. The supported RAID types on a storage system can be shown by using storcfg system -show -showraidtypes.

–format format



storcfg

U41824-J-Z156-1-76 161

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c




–connectparam


Return codes

Examples

1. Output for logical volumes with –format std (default)

storcfg volume –show –poolid ralf* -showconnections -showmirrors

storage ID = FinanceServer_root pool ID = Ralf1-0 storage system name = CLARiiON+CK200041600121 storage serial nr. = CK200041600121 device ID = 1078 GUID = 60060160CDD21A00703ED3246564DD11 storage size = 2147483648 resource type = STORMAN_RESOURCE_TYPE_PREDEFINED storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION allowed access = STORMAN_ACCESS_MODE_SHARED current access = STORMAN_ACCESS_MODE_EXCLUSIVE target OS = STORMAN_OS_ANY status = STORMAN_VOLUME_STATUS_READY











storcfg

162 U41824-J-Z156-1-76

raid level = STORMAN_RAID_LEVEL_10 raid type = RAID1-0 owner controller = SP_A storage pool = C+0006 host access = STORMAN_HOST_ACCESS_RESTRICTED host connections host ID type = STORMAN_HOSTID_TYPE_NAME host ID = ducksoup initiators initiator ID = 210000C09F956746 connection type = STORMAN_CONNECTION_TYPE_FC storage connections host device number = 0 target ID = 500601601020F77C connection type = STORMAN_CONNECTION_TYPE_FC host device number = 0 target ID = 500601611020F77C connection type = STORMAN_CONNECTION_TYPE_FC host device number = 0 target ID = 500601681020F77C connection type = STORMAN_CONNECTION_TYPE_FC host device number = 0 target ID = 500601691020F77C connection type = STORMAN_CONNECTION_TYPE_FC initiator ID = 210000C09F956747 connection type = STORMAN_CONNECTION_TYPE_FC storage connections host device number = 0 target ID = 500601601020F77C connection type = STORMAN_CONNECTION_TYPE_FC host device number = 0 target ID = 500601611020F77C connection type = STORMAN_CONNECTION_TYPE_FC host device number = 0 target ID = 500601681020F77C connection type = STORMAN_CONNECTION_TYPE_FC host device number = 0 target ID = 500601691020F77C connection type = STORMAN_CONNECTION_TYPE_FC mirror targets storage ID = FinanceServer_root-mirror storage system name = CLARiiON+CK200041600121 pool ID = Raid1-0 device ID = 1079 GUID = 60060160CDD21A00713ED3246564DD11 mirror type = STORMAN_MIRROR_TYPE_FULL replication mode = STORMAN_MIRROR_REPLICA_LOCAL status = STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZING

storcfg

U41824-J-Z156-1-76 163

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

isSynch = false percentSynced = 24 pointInTime = storage ID = FinanceServer_root-snap storage system name = CLARiiON+CK200041600121 pool ID = Raid1-0 device ID = UID+600601600fa71000763f780b09b6dd11 GUID = 600601600FA71000763F780B09B6DD11 mirror type = STORMAN_MIRROR_TYPE_SNAP replication mode = STORMAN_MIRROR_REPLICA_LOCAL status = STORMAN_MIRROR_PAIR_STATUS_INACTIVE isSynch = false percentSynced = pointInTime = no mirror sources found no unassigned point in times foundstorage ID = FinanceServer_root-mirror pool ID = Raid1-0 storage system name = CLARiiON+CK200041600121 storage serial nr. = CK200041600121 device ID = 1079 GUID = 60060160CDD21A00713ED3246564DD11 storage size = 2147483648 resource type = STORMAN_RESOURCE_TYPE_PREDEFINED storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION allowed access = STORMAN_ACCESS_MODE_SHARED current access = STORMAN_ACCESS_MODE_NONE target OS = STORMAN_OS_ANY status = STORMAN_VOLUME_STATUS_NOT_READY raid level = STORMAN_RAID_LEVEL_10 raid type = RAID1-0 owner controller = SP_A storage pool = C+0006 host access = STORMAN_HOST_ACCESS_RESTRICTED no host connections found no mirror targets found mirror sources storage ID = FinanceServer_root storage system name = CLARiiON+CK200041600121 pool ID = Raid1-0 device ID = 1078 GUID = 60060160CDD21A00703ED3246564DD11 mirror type = STORMAN_MIRROR_TYPE_FULL replication mode = STORMAN_MIRROR_REPLICA_LOCAL status = STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZING percentSynced = 24 pointInTime =

storcfg

164 U41824-J-Z156-1-76

no unassigned point in times foundstorage ID = FinanceServer_root-snap pool ID = Raid1-0 storage system name = CLARiiON+CK200041600121 storage serial nr. = CK200041600121 device ID = UID+600601600fa71000763f780b09b6dd11 GUID = 600601600FA71000763F780B09B6DD11 storage size = 2147483648 resource type = STORMAN_RESOURCE_TYPE_NOT_APPLICABLE storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION allowed access = STORMAN_ACCESS_MODE_SHARED current access = STORMAN_ACCESS_MODE_NONE target OS = STORMAN_OS_ANY status = STORMAN_VOLUME_STATUS_NOT_READY raid level = STORMAN_RAID_LEVEL_UNKNOWN raid type = Unknown owner controller = SP_A storage pool = S+GLOBAL host access = STORMAN_HOST_ACCESS_ALL_CONNECTED no host connections found no mirror targets found mirror sources storage ID = FinanceServer_root storage system name = CLARiiON+CK200041600121 pool ID = Raid1-0 device ID = 1078 GUID = 60060160CDD21A00703ED3246564DD11 mirror type = STORMAN_MIRROR_TYPE_SNAP replication mode = STORMAN_MIRROR_REPLICA_LOCAL status = STORMAN_MIRROR_PAIR_STATUS_INACTIVE percentSynced = pointInTime = no unassigned point in times found

2. Output for logical volumes with –format xmlp

storcfg volume –show –poolid ralf* -format xmlp

<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <Text>Successful</Text> <SubCode>0</SubCode> <SubCodeText>STORMAN_SUB_NONE</SubCodeText> </ReturnCode> <Result>

storcfg

U41824-J-Z156-1-76 165

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

<VolumeDescription> <StorID>FinanceServer_root</StorID> <PoolID>Ralf1-0</PoolID> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <StorageSerialNumber>CK200041600121</StorageSerialNumber> <GUID>60060160CDD21A00703ED3246564DD11</GUID> <LastChecked>1227078622042000</LastChecked> <DeviceID>1078</DeviceID> <Size>2147483648</Size> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <StorageModel>STORMAN_STORAGE_MODEL_CLARIION</StorageModel> <ResourceType>STORMAN_RESOURCE_TYPE_PREDEFINED</ResourceType> <AllowedAccess>STORMAN_ACCESS_MODE_SHARED</AllowedAccess> <CurrentAccess>STORMAN_ACCESS_MODE_EXCLUSIVE</CurrentAccess> <TargetOS>STORMAN_OS_ANY</TargetOS> <Status>STORMAN_VOLUME_STATUS_READY</Status> <HostAccess>STORMAN_HOST_ACCESS_RESTRICTED</HostAccess> <RaidLevel>STORMAN_RAID_LEVEL_10</RaidLevel> <RaidType>RAID1-0</RaidType> <CurrOwnerController>SP_A</CurrOwnerController> <StoragePoolName>C+0006</StoragePoolName> <HostConnections> <HostConnection> <HostIDType>STORMAN_HOSTID_TYPE_NAME</HostIDType> <HostID>ducksoup</HostID> <DeviceConnections> <DeviceConnection> <InitiatorPort> <PortID>210000C09F956746</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </InitiatorPort> <StorageConnections> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601601020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601611020F77C</PortID> <PortName/>

storcfg

166 U41824-J-Z156-1-76

<ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601681020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601691020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> </StorageConnections> </DeviceConnection> <DeviceConnection> <InitiatorPort> <PortID>210000C09F956747</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </InitiatorPort> <StorageConnections> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601601020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601611020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType>

storcfg

U41824-J-Z156-1-76 167

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

</TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601681020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>0</HostDeviceNumber> <TargetPort> <PortID>500601691020F77C</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> </StorageConnections> </DeviceConnection> </DeviceConnections> </HostConnection> </HostConnections> <MirroringTargets> <MirroringTarget> <StorID>FinanceServer_root-mirror</StorID> <DeviceID>1079</DeviceID> <GUID>60060160CDD21A00713ED3246564DD11</GUID> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <PoolID>Raid1-0</PoolID> <MirrorType>STORMAN_MIRROR_TYPE_FULL</MirrorType> <ReplicationMode>STORMAN_MIRROR_REPLICA_LOCAL</ReplicationMode> <Status>STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZING</Status> <CopyMode>STORMAN_REMOTE_COPY_MODE_NONE</CopyMode> <IsSynch>false</IsSynch> <PercentSynced>24</PercentSynced> <PointInTime> <TimeStamp/> </PointInTime> </MirroringTarget> <MirroringTarget> <StorID>FinanceServer_root-snap</StorID> <DeviceID>UID+600601600fa71000763f780b09b6dd11</DeviceID> <GUID>600601600FA71000763F780B09B6DD11</GUID> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <PoolID>Raid1-0</PoolID>

storcfg

168 U41824-J-Z156-1-76

<MirrorType>STORMAN_MIRROR_TYPE_SNAP</MirrorType> <ReplicationMode>STORMAN_MIRROR_REPLICA_LOCAL</ReplicationMode> <Status>STORMAN_MIRROR_PAIR_STATUS_INACTIVE</Status> <CopyMode>STORMAN_REMOTE_COPY_MODE_NONE</CopyMode> <IsSynch>false</IsSynch> <PercentSynced/> <PointInTime> <TimeStamp/> </PointInTime> </MirroringTarget> </MirroringTargets> <MirroringSources> </MirroringSources> <UnassignedPointInTimes> </UnassignedPointInTimes> <TargetPorts> </TargetPorts> </VolumeDescription> <VolumeDescription> <StorID>FinanceServer_root-mirror</StorID> <PoolID>Raid1-0</PoolID> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <StorageSerialNumber>CK200041600121</StorageSerialNumber> <GUID>60060160CDD21A00713ED3246564DD11</GUID> <LastChecked>1227078384905000</LastChecked> <DeviceID>1079</DeviceID> <Size>2147483648</Size> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <StorageModel>STORMAN_STORAGE_MODEL_CLARIION</StorageModel> <ResourceType>STORMAN_RESOURCE_TYPE_PREDEFINED</ResourceType> <AllowedAccess>STORMAN_ACCESS_MODE_SHARED</AllowedAccess> <CurrentAccess>STORMAN_ACCESS_MODE_NONE</CurrentAccess> <TargetOS>STORMAN_OS_ANY</TargetOS> <Status>STORMAN_VOLUME_STATUS_NOT_READY</Status> <HostAccess>STORMAN_HOST_ACCESS_RESTRICTED</HostAccess> <RaidLevel>STORMAN_RAID_LEVEL_10</RaidLevel> <RaidType>RAID1-0</RaidType> <CurrOwnerController>SP_A</CurrOwnerController> <StoragePoolName>C+0006</StoragePoolName> <HostConnections> </HostConnections> <MirroringTargets> </MirroringTargets> <MirroringSources> <MirroringSource> <StorID>FinanceServer_root</StorID> <DeviceID>1078</DeviceID> <GUID>60060160CDD21A00703ED3246564DD11</GUID>

storcfg

U41824-J-Z156-1-76 169

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:05

.55

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e

\sto

rman

.v11

\sto

rcfg

.do

c

<StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <PoolID>Raid1-0</PoolID> <MirrorType>STORMAN_MIRROR_TYPE_FULL</MirrorType> <ReplicationMode>STORMAN_MIRROR_REPLICA_LOCAL</ReplicationMode> <Status>STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZING</Status> <CopyMode>STORMAN_REMOTE_COPY_MODE_NONE</CopyMode> <IsSynch>false</IsSynch> <PercentSynced>24</PercentSynced> <PointInTime> <TimeStamp/> </PointInTime> </MirroringSource> </MirroringSources> <UnassignedPointInTimes> </UnassignedPointInTimes> <TargetPorts> </TargetPorts> </VolumeDescription> <VolumeDescription> <StorID>FinanceServer_root-snap</StorID> <PoolID>Raid1-0</PoolID> <StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <StorageSerialNumber>CK200041600121</StorageSerialNumber> <GUID>600601600FA71000763F780B09B6DD11</GUID> <LastChecked>1227078622042000</LastChecked> <DeviceID>UID+600601600fa71000763f780b09b6dd11</DeviceID> <Size>2147483648</Size> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <StorageModel>STORMAN_STORAGE_MODEL_CLARIION</StorageModel> <ResourceType>STORMAN_RESOURCE_TYPE_NOT_APPLICABLE</ResourceType> <AllowedAccess>STORMAN_ACCESS_MODE_SHARED</AllowedAccess> <CurrentAccess>STORMAN_ACCESS_MODE_NONE</CurrentAccess> <TargetOS>STORMAN_OS_ANY</TargetOS> <Status>STORMAN_VOLUME_STATUS_NOT_READY</Status> <HostAccess>STORMAN_HOST_ACCESS_ALL_CONNECTED</HostAccess> <RaidLevel>STORMAN_RAID_LEVEL_UNKNOWN</RaidLevel> <RaidType>Unknown</RaidType> <CurrOwnerController>SP_A</CurrOwnerController> <StoragePoolName>S+GLOBAL</StoragePoolName> <HostConnections> </HostConnections> <MirroringTargets> </MirroringTargets> <MirroringSources> <MirroringSource> <StorID>FinanceServer_root</StorID> <DeviceID>1078</DeviceID> <GUID>60060160CDD21A00703ED3246564DD11</GUID>

storcfg

170 U41824-J-Z156-1-76

<StorageSystemName>CLARiiON+CK200041600121</StorageSystemName> <PoolID>Raid1-0</PoolID> <MirrorType>STORMAN_MIRROR_TYPE_SNAP</MirrorType> <ReplicationMode>STORMAN_MIRROR_REPLICA_LOCAL</ReplicationMode> <Status>STORMAN_MIRROR_PAIR_STATUS_INACTIVE</Status> <CopyMode>STORMAN_REMOTE_COPY_MODE_NONE</CopyMode> <IsSynch>false</IsSynch> <PercentSynced/> <PointInTime> <TimeStamp/> </PointInTime> </MirroringSource> </MirroringSources> <UnassignedPointInTimes> </UnassignedPointInTimes> <TargetPorts> </TargetPorts> </VolumeDescription> </Result></Response>

U41824-J-Z156-1-76 171

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

18:0

5.55

Pfa

d: O

:\alf\

sto

rma

n_0

710

100\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\s

torc

reat

e.do

c

10.5 storcreate

Reserves a new storage volume from a 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

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 105.

–poolid poolid

Specifies the ID of a 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 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.

–raidtype raidtype

Specifies the RAID type of the logical volume that should be reserved or created as a string that is supported by the specified storage system (default: #any).

This parameter should be used only in conjunction with a pool ID or a storage system. The supported RAID types on a storage system can be shown by using storcfg system -show -showraidtypes.

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

storcreate

172 U41824-J-Z156-1-76

–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 NetApp 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


storcreate

U41824-J-Z156-1-76 173

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

18:0

5.55

Pfa

d: O

:\alf\

sto

rma

n_0

710

100\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\s

torc

reat

e.do

c

Return codes





8 STORMAN_INVALID_STORID Specified storID not allowed

9 STORMAN_STORID_IN_USE StorID 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





21 STORMAN_FCT_NOT_POSSIBLE

Function could not be performed



24 STORMAN_CFG_CHANGE_FAILED

Volume creation was initialized but rejected by the storage system



U41824-J-Z156-1-76 174

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09 S

tand

18:

01.0

4P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.v

11\s

tord

elet

e.do

c

10.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 repos-itory. 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 a

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 pool and in the storage system. The value destroy destroys the device in the storage system and in the pool.

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

The deletion of the volume happens asynchronous and StorMan does not wait for completion. If the volume has host connections or is part of a mirror pair, it cannot be destroyed. In this case the storid is cleared but STORMAN_NOT_COMPLETE is returned.

–connectparam


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

stordelete

U41824-J-Z156-1-76 175

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09 S

tand

18:

01.0

4P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.v

11\s

tord

elet

e.do

c

Return codes










15 STORMAN_STORAGE_ATTACHED

No release because storage unit still attached



Function not supported





U41824-J-Z156-1-76 176

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.04

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

ord

etac

h.do

c

10.7 stordetach

Disconnects one or multiple storage volume(s) from a host using the LUN masking / unmasking capabilities of the storage system. Disconnected storage volumes are no longer visible to the host.

Syntax

Parameters

–storid storid[,...]

Specifies the assigned storID(s) of one or a list of volumes, separated by commas as unique identifier. This parameter is mandatory.


Specifies name of the server the storage volumes should be detached from.

–hostip ip

Specifies the IP address of the server.

–hostwwpn wwpn

Specifies the WWPN of the server's HBA the storage volumes should be detached from.

–system system

Specifies a storage system and can be specified instead of –storid. If specified StorMan will disconnect all volumes of this storage system from the specified server that are managed by StorMan i.e. that are contained in a pool. If –storid parameter is specified, this parameter is ignored.

–destroyconnection

Setting this parameter causes the connection between a server / HBA and the storage system / storage ports to be removed, in the case that no more volumes than the specified are attached to the host.

Default: Parameter is not set. Setting this parameter is useful if the host will no longer use the connection to the storage array. Normally the parameter should be set to false (not set). See section section “Host storage connections (SPCs)” on page 95 for more details.

stordetach –storid storid[,...] [ –hostname hostname ] [ –hostip ip ] [ –hostwwpn wwpn ] [ –system system] [ –destroyconnection ] –connectparam ...

stordetach

U41824-J-Z156-1-76 177

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.04

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

ord

etac

h.do

c

If specified together with –system connections between a server/ hba and a storage system/ storage ports can be removed even if no volumes of the system are attached to the server any more. Only if unmanged volumes (not contained in a StorMan pool) are connected to the host, the connections are not removed in this case and the command is refused.

–connectparam


stordetach

178 U41824-J-Z156-1-76

Notes

● -storid must be specified to specify the storage unit(s).

● 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



1 STORMAN_NO_ACTION Nothing to do











23 STORMAN_BAD_CONFIG Illegal masking configuration found (Clariion). See section “LUN masking in FibreCAT CX / CLARiiON CX systems” on page 89 for details.



31 STORMAN_REFUSED Error Type –destroyconnection required but other unmanaged volumes attached

U41824-J-Z156-1-76 179

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

04P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101

_bhb

\pro

d_e

\sto

rma

n.v1

1\st

ore

mc.

doc

10.8 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.

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 SMI-S Provider's repository

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

storemc

180 U41824-J-Z156-1-76

10.8.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 section “storcfg cimom –add” on page 121.).

The processing of this functions automatically starts a discover process on the specified CIM-OM to create or update the information about the specified CLARiiON CX or FibreCAT CX storage system. Additionally further storage systems visible to the CIM-OM may be discovered and added to the repository of StorMan.

Note If the authorization (userid and/or password) of the storage system has been changed or removed, you have to call storemc –rem (see page 182) for this system and call storemc –add again with the new authorization.

Syntax

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.

storemc –add [ –hostname hostname ] [ –hostip ip ] [ –http port ] [ –cimuser user ] [ –cimpwd pwd ] –sp spa,spb –cxuser user –cxpwd pwd –connectparam ...

storemc

U41824-J-Z156-1-76 181

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

04P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101

_bhb

\pro

d_e

\sto

rma

n.v1

1\st

ore

mc.

doc

–sp spa,spb

Specifies a list of two netnames or IP addresses of both storage processors (SPs) of the CLARiiON CX / FibreCAT CX array delimited by comma. Make sure that the SPs are specified in the correct order: The first name / address must be spa and the second spb, 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

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.







Function refused by SMI-S Provider





storemc

182 U41824-J-Z156-1-76

10.8.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 system name as delivered by the storcfg system –show command (e.g. CLARiiON+ck200024200100).

Syntax

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 system

Specifies the system name 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


storemc –rem [ –hostname hostname ] [ –hostip ip ] [ –http port ] –system system [ –cimuser user ] [ –cimpwd pwd ] –connectparam ...

storemc

U41824-J-Z156-1-76 183

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:01.

04P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101

_bhb

\pro

d_e

\sto

rma

n.v1

1\st

ore

mc.

doc

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 “storcfg system –rem” on page 133.

Return codes



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.





Function refused by SMI-S Provider





U41824-J-Z156-1-76 184

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd 1

8:01

.04

Pfa

d: O

:\alf\

sto

rman

_07

1010

0\0

7101

01_

bhb

\pro

d_e\

stor

man

.v11

\sto

rinf

o.do

c

10.9 storinfo

Provides information about StorMan.

Syntax

Parameters

–connectparam


Return codes

storinfo –connectparam ...






U41824-J-Z156-1-76 185

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tan

d 18

:01.

05P

fad

: O:\

alf\s

torm

an_

071

0100

\07

1010

1_b

hb\p

rod

_e\s

torm

an.

v11\

stor

man

db.d

oc

10.10 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

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 sure there is really no server working with the repository and no concurrent stormandb command is running because else the repository may be corrupted. This parameter is not supported in BS2000/OSD environment.

–connectparam


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

stormandb

186 U41824-J-Z156-1-76

Return codes






U41824-J-Z156-1-76 187

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

10.11 stormirror

Manages volume based replication functions. Local replication functions are supported as full copy mirrors or snapshots (pointer based) local mirrors of a source volume.

I Verify that you have set WithMirrors = 1 in the smserver.ini file before using stormirror functions.

Functions


–activate

activates mirror volume(s) of mirror pair(s) for direct usage

–create

creates new mirror pair(s) for logical volume(s) by establishing a mirroring relationship between source volume(s) and mirror volume(s)

–deactivate

deactivates mirror pair(s) to the point in time of activation

–recreate

recreate mirroring function for mirror pair(s)

–restore

restores mirror volume(s) of mirror pair(s) to source volume(s)

–terminate

terminates mirroring relationship for mirror pair(s)

–show

displays information related to mirror pair(s)

stormirror –function –functionparam ... –connectparam ...

stormirror

188 U41824-J-Z156-1-76

10.11.1 stormirror –activate

Activates one or more mirror pairs. This function defines the point in time on the mirror volumes and makes the mirror volumes available for a server and/or application.

Alternatively an existing point in time of the source volume can be activated by specifying the parameter pointintime, if supported by the mirroring function and the storage array. Currently this is only supported for snap pairs on FibreCAT CX systems.

The mirror pairs specified by the source and mirror volumes must be homogenous, i.e. they must have the same mirror type and must be specified in the correct order.

The activation of multiple mirror volumes is not supported consistent by means of IO sequence. Therefore consistency must be assured by caller.

Depending on mirror type and supported storage array, a storattach command is required before accessing the activated mirror (e.g. for snaps on FibreCAT CX/CLARiiON CX storage arrays).

Syntax

Parameters


Specifies the type of mirror pair(s). Supported values: snap | full | any (default) snap selects snapshot (pointer based) mirror pair(s). full selects full copy mirror pairs.any selects the mirroring feature defined by the specified mirror pair(s). The mirrortype must be the same for all specified mirror pairs.

–source storid[,...]

Specifies the storID(s) of one ore a list of source volumes for the mirror pair(s).

The number of specified storIDs for the source volumes must be equal to the number of specified storIDs for the target volumes.

–target storid[,...]

Specifies the storID(s) of one ore a list of target volumes for the mirror pair(s).


stormirror –activate [ –mirrortype mirrortype ] –source storid[,...] –target storid[,...] [ –pointintime timestamp[,...] ] [ –force ] –connectparam ...

stormirror

U41824-J-Z156-1-76 189

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

–pointintime timestamp[,...]

Only for snap volumes (mirror type snap): Specifies the point in time(s) of the source volumes to be activated on the target volumes for the mirror pair(s).

– The value #new is required to create a new point in time.

– timestamp specifies a deactivated snapsession no longer assigned to a target volume by the timestamp reflecting the point in time of activation. This parameter may be specified multiple times.


The specified target volumes and source volumes must be deactivated mirror pairs.

–force

Disables the status check of the mirrors before activation. The function is performed as supported by underlaying functions of the storage system.

–connectparam


stormirror

190 U41824-J-Z156-1-76

Return codes



1 STORMAN_NO_ACTION Nothing to do.

2 STORMAN_NOT_COMPLETE Function only partly completed.




storID does not yet exist.


14 STORMAN_STORAGE_LOCKED Storage unit currently locked.


18 STORMAN_NOT_FOUND No wwpn for the specified host was found in the repository.





29 STORMAN_MIRR_ALREADY_USED

Specified mirror(s) already in use

30 STORMAN_MIRR_ALREADY_ACTIVATED

Specified mirror(s) already activated

31 STORMAN_MIRR_NOT_PAIRED Number of originals and mirrors not equal

32 STORMAN_MIRR_NOT_SUPP Specified mirroring feature not supported

33 STORMAN_MIRR_MAX_NUM Maximum number of supported mirrors for the original exceeded

34 STORMAN_MIRR_NOT_FIT Specified mirror(s) not usable for the specified function

36 STORMAN_MIRR_INV_STATE Specified mirror(s) state invalid for this operation

38 STORMAN_MIRR_MIXED Specfiied storID(s) in different storage systems

stormirror

U41824-J-Z156-1-76 191

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

10.11.2 stormirror –create

Creates one or multiple mirroring pairs by assigning one or multiple mirror volumes to one or multiple source volumes. The mirror volumes can be specified as full mirror copies or pointer based logical copies (snapshots). For full mirror copies after establishing the mirroring relationship the synchronization process is started. According to the currently supported local replication, the source volumes and mirror volumes must all be part of the same storage system.

Syntax

Parameters


Specifies the type of mirror pair(s) to be created. Supported values: snap | full snap creates snapshot (pointer based) mirror pair(s). full creates full copy mirror pairs.




stormirror –create –mirrortype mirrortype –source storid[,...] –target storid[,...] [ –waitforsync ] –connectparam ...

stormirror

192 U41824-J-Z156-1-76


Specifies the storID(s) of one or a list of target volumes for the mirror pair(s).


The capacity and type of the specified target volumes must match to the prerequisites of the specified mirroring feature of the storage system.

If the value #auto is specified, StorMan automatically assigns appropriate target volumes to create the mirror pair(s). This function can be supported for –mirrortype snap only.

–waitforsync

Option to wait for the completion of the synchronization process of the newely created mirror pair(s). This function can be supported for –mirrortype full only.

–connectparam


Return codes

















stormirror

U41824-J-Z156-1-76 193

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c








37 STORMAN_MIRR_NO_AUTOASSIGN

Auto assign feature not supported



stormirror

194 U41824-J-Z156-1-76

10.11.3 stormirror –deactivate

Deactivates one or more mirror pairs. The data on the mirror pairs is reset to the point in time of the stormirror –activate processing, i.e. all changes made in the meantime on source volumes and on target volumes are discarded (lost). The mirror volumes are no longer accessible to the server and/or application.

The function is only supported for snapshot mirror pairs.

Syntax

Parameters


Specifies the type of mirror pair(s). Supported values: snap | any (default) snap selects snapshot (pointer based) mirror pair(s). any selects the mirroring feature defined by the specified mirror pair(s). Only snapshot mirror pair(s) are supported.







–connectparam


stormirror –deactivate [ –mirrortype mirrortype ] –source storid[,...] –target storid[,...] –connectparam ...

stormirror

U41824-J-Z156-1-76 195

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

Return codes

























stormirror

196 U41824-J-Z156-1-76

10.11.4 stormirror –recreate

Recreates one or more mirrors pairs. The function restarts the mirroring for the specified mirror pair(s). The mirror volumes are no longer accessible to the server and/or application and all changes done on the mirror volumes are discarded. A further stormirror -activate may activate the mirror volumes again for a new point in time.

The function is only supported for full mirror pairs (clones).

Syntax

Parameters


Specifies the type of mirror pair(s) to be recreated. Supported values: full | any (default) full selects full copy mirror pairs.any selects the mirroring feature defined by the specified mirror pair(s).







–waitforsync

Option to wait for the completion of the re-synchronization process of the mirror pair(s).

–connectparam


stormirror –recreate [ –mirrortype mirrortype ] –source storid[,...] –target storid[,...] [ –waitforsync ] –connectparam ...

stormirror

U41824-J-Z156-1-76 197

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

Return codes

























stormirror

198 U41824-J-Z156-1-76

10.11.5 stormirror –restore

Restores one or more mirror pairs. This function restores the contents of the mirror volumes back to the original volumes of the mirrored pairs. All changes on the original volumes are discarded. The mirror volumes of mirror type snap remain accessible to the server and/or application. The mirror volumes of mirror type full are no longer accessible to the server and/or appli-cation. The status of mirror volumes after processing a restore operation depends on the specific storage system.

Syntax

Parameters


Specifies the type of mirror pair(s) to be restored. Supported values: snap | full | any (default) snap selects snapshot (pointer based) mirror pair(s). full selects full copy mirror pairs.any selects the mirroring feature defined by the specified mirror pair(s).


Specifies the storID(s) of one or a list of source volumes for the mirror pair(s).



Specifies the storID(s) of one or a list of target volumes for the mirror pair(s).


–connectparam


stormirror –restore [ –mirrortype mirrortype ] –source storid[,...] –target storid[,...] –connectparam ...

stormirror

U41824-J-Z156-1-76 199

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

Return codes

























stormirror

200 U41824-J-Z156-1-76

10.11.6 stormirror –terminate

Terminates one or more mirror pairs. This function removes the relationship between the original volumes and the mirror volumes.

Syntax

Parameters


Specifies the type of mirror pair(s) to be terminated. Supported values: snap | full | any (default) snap selects snapshot (pointer based) mirror pair(s). full selects full copy mirror pairs.any selects the mirroring feature defined by the specified mirror pair(s).






The number of specified storIDs for the source volumes must be equal to the number of specified storIDs for the target volumes. If target is specified the pointintime parameter cannot be specified.

–pointintime timestamp[,...]

Only for snap volumes (mirror type snap): Specifies the point in time(s) of the source volume to be terminated.

– This parameter can be specified only instead of -target parameter. For a single source volumes a list of points in time can be specified for termination. A list of source volumes is not supported in this combination

stormirror –terminate [ –mirrortype mirrortype ] –source storid[,...] { –target storid [,...] |

–pointintime timestamp[,...] } [ –detach ] [ –force ] –connectparam ...

stormirror

U41824-J-Z156-1-76 201

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

– timestamp specifies a deactivated snapsession no longer assigned to a target volume by the timestamp reflecting the point in time of activation. This parameter may be specified multiple times.

The specified target volumes and source volumes must be deactivated mirror pairs.

–detach

The parameter is only considered if –mirrortype snap is specified.

Terminates mirror pair(s) regardless if they are attached to any server.

Not specifying this parameter only detached mirror pair(s) will be terminated.

–force

Terminates the mirror pair(s) regardless of their status. The function is performed as supported by underlaying functions of the storage system.

–connectparam


stormirror

202 U41824-J-Z156-1-76

Return codes























stormirror

U41824-J-Z156-1-76 203

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

10.11.7 stormirror –show

Displays information about the relationship and status of mirrored pairs. The selection is controlled by the specified parameters. The same selection parameters as for storcfg volume -show are supported.

Syntax

Parameters

–storid storid

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

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

–poolid poolid

Specifies the ID of a 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.


Specifies the mirror type of the volume for mirroring (replication) functions. Supported values: snap | full | any (default) snap selects snapshot (pointer based) mirror pair(s). full selects full copy mirror pairs.any selects the mirroring feature defined by the specified mirror pair(s).

–mirrorusage mirrorusage

Selects by the usage of the volume for mirroring (replication) functions (default: any).

Supported values: origlocal | mirrorlocal | any (default)

any selects the pairs regardless of their mirror usage.

origlocal selects original volumes of local mirror pair(s).

mirrorlocal selects mirror volumes of local mirror pair(s).

stormirror –show [ –storid storid ] [ –poolid poolid ] [ –system sysname ] [ –mirrortype mirrortype ] [ –mirrorusage mirrorusage ] [ –format format ] –connectparam ...

stormirror

204 U41824-J-Z156-1-76

–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.

I Additionally all selection parameters offered by storcfg volume -show are supported.

Return codes







18 STORMAN_NOT_FOUND Matching object could not be provided.



stormirror

U41824-J-Z156-1-76 205

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

Examples


stormirror -show -storid MN_4170

storage ID = MN_4170 pool ID = SHC-OSD-CX-FNM00082700019 storage system name = CLARiiON+FNM00082700019 storage serial nr. = FNM00082700019 device ID = 984 GUID = 600601603E402100D2D9255CB9BBDD11 storage size = 21474836480 resource type = STORMAN_RESOURCE_TYPE_PREDEFINED storage vendor = STORMAN_STORAGE_VENDOR_EMC storage model = STORMAN_STORAGE_MODEL_CLARIION allowed access = STORMAN_ACCESS_MODE_ANY current access = STORMAN_ACCESS_MODE_SHARED target OS = STORMAN_OS_ANY status = STORMAN_VOLUME_STATUS_READY raid level = STORMAN_RAID_LEVEL_5 raid type = RAID5 owner controller = SP_A storage pool = C+0001 host access = STORMAN_HOST_ACCESS_RESTRICTED mirror targets storage ID = MN_4176 storage system name = CLARiiON+FNM00082700019 pool ID = SHC-OSD-CX-FNM00082700019 device ID = 990 GUID = 600601603E402100BAEAC15FB7BBDD11 mirror type = STORMAN_MIRROR_TYPE_FULL replication mode = STORMAN_MIRROR_REPLICA_LOCAL status = STORMAN_MIRROR_PAIR_STATUS_SPLIT isSynch = false percentSynced = pointInTime = storage ID = MN_4178 storage system name = CLARiiON+FNM00082700019 pool ID = SHC-OSD-CX-FNM00082700019 device ID = 992 GUID = 600601603E402100BCEAC15FB7BBDD11 mirror type = STORMAN_MIRROR_TYPE_FULL replication mode = STORMAN_MIRROR_REPLICA_LOCAL status = STORMAN_MIRROR_PAIR_STATUS_SYNCHRONIZED isSynch = true percentSynced = 100 pointInTime =

stormirror

206 U41824-J-Z156-1-76

no mirror sources found no unassigned point in times found


stormirror -show -storid MN_4170 -format xmlp

<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <Text>Successful</Text> <SubCode>0</SubCode> <SubCodeText>STORMAN_SUB_NONE</SubCodeText> </ReturnCode> <Result> <VolumeDescription> <StorID>MN_4170</StorID> <PoolID>SHC-OSD-CX-FNM00082700019</PoolID> <StorageSystemName>CLARiiON+FNM00082700019</StorageSystemName> <StorageSerialNumber>FNM00082700019</StorageSerialNumber> <GUID>600601603E402100D2D9255CB9BBDD11</GUID> <LastChecked>1239976912547327</LastChecked> <DeviceID>984</DeviceID> <Size>21474836480</Size> <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_SHARED</CurrentAccess> <TargetOS>STORMAN_OS_ANY</TargetOS> <Status>STORMAN_VOLUME_STATUS_READY</Status> <HostAccess>STORMAN_HOST_ACCESS_RESTRICTED</HostAccess> <RaidLevel>STORMAN_RAID_LEVEL_5</RaidLevel> <RaidType>RAID5</RaidType> <CurrOwnerController>SP_A</CurrOwnerController> <StoragePoolName>C+0001</StoragePoolName> <HostConnections> <HostConnection> <HostIDType>STORMAN_HOSTID_TYPE_WWPN</HostIDType> <HostID>10000000C93EA2EF</HostID> <DeviceConnections> <DeviceConnection> <InitiatorPort> <PortID>10000000C93EA2EF</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType>

stormirror

U41824-J-Z156-1-76 207

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09

Sta

nd 1

8:01

.05

Pfa

d: O

:\alf\

stor

man

_07

101

00\0

7101

01_

bhb

\pro

d_e

\sto

rma

n.v1

1\st

orm

irror

.do

c

</InitiatorPort> <StorageConnections> <StorageConnection> <HostDeviceNumber>112</HostDeviceNumber> <TargetPort> <PortID>500601603CE004C7</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>112</HostDeviceNumber> <TargetPort> <PortID>500601683CE004C7</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> </StorageConnections> </DeviceConnection> </DeviceConnections> </HostConnection> <HostConnection> <HostIDType>STORMAN_HOSTID_TYPE_WWPN</HostIDType> <HostID>10000000C93EA376</HostID> <DeviceConnections> <DeviceConnection> <InitiatorPort> <PortID>10000000C93EA376</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </InitiatorPort> <StorageConnections> <StorageConnection> <HostDeviceNumber>112</HostDeviceNumber> <TargetPort> <PortID>500601603CE004C7</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>112</HostDeviceNumber> <TargetPort>

stormirror

208 U41824-J-Z156-1-76

<PortID>500601683CE004C7</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> </StorageConnections> </DeviceConnection> </DeviceConnections> </HostConnection> <HostConnection> <HostIDType>STORMAN_HOSTID_TYPE_WWPN</HostIDType> <HostID>20B400000EA085C1</HostID> <DeviceConnections> <DeviceConnection> <InitiatorPort> <PortID>20B400000EA085C1</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </InitiatorPort> <StorageConnections> <StorageConnection> <HostDeviceNumber>112</HostDeviceNumber> <TargetPort> <PortID>500601603CE004C7</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</ConnectionType> </TargetPort> </StorageConnection> <StorageConnection> <HostDeviceNumber>112</HostDeviceNumber> <TargetPort> <PortID>500601683CE004C7</PortID> <PortName/> <ConnectionType>STORMAN_CONNECTION_TYPE_FC</C

U41824-J-Z156-1-76 209

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Ma

i 200

9 S

tan

d 18

:01.

05P

fad:

O:\

alf\s

torm

an_

071

010

0\07

1010

1_b

hb\

prod

_e\s

torm

an.v

11\

stor

para

m.d

oc

10.12 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

Parameters

–show

Shows the settings of the StorMan Server.

–debug level

Sets the debug level of the server. Supported values:

0 Trace severe errors only1 Trace errors too2 Trace even warnings3 Trace information4 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:

1 Trace tcp / ip calls of clients 2 Trace messages of clients 4 Trace tcp / ip calls of CIM communication 8 Trace messages of CIM communication

Adding the values enables multiple traces.

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

storparam

210 U41824-J-Z156-1-76

–traceworker level

Enables the tracing of background threads with debug trace level (not higher than the level set by debug) to the trace file. Supported values:

0 Trace off (default) 1 Trace worker thread 2 Trace updater threads

Adding the values enables multiple levels.

–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.

–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 NetApp.

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






U41824-J-Z156-1-76 211

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

18:0

1.05

Pfa

d: O

:\alf\

stor

ma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\s

tors

tat.

doc

10.13 storstat

The storstat command is used to manage the collection of performance and statistical informations.

The first parameter specifies the object group of the repository that is configured:

The second parameter specifies the function:

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

For FibreCAT CX/CLARiiON CX storage systems the collection of statistical data must be activated to support any statistical data information function, currently possible by NaviCLI (setstat –on|off) or Navisphere Manager.

storstat object –function –functionparam ... –connectparam ...

First parameter object Object

volume logical volumes of storage systems visible by StorMan

Second parameter function Meaning

–get get statistic information

storstat

212 U41824-J-Z156-1-76

10.13.1 storstat volume

storstat volume is used to get statistical and performance data for storage volumes by StorMan.

Functions

The –function parameter supplies the following functions:

–get

Gets the statistical data for volumes of a storage system.

10.13.1.1 storstat volume –get

Gets the statistical and performance data related to storage volumes of a storage system. Selection criteria for the –get function can be specified using the parameters described below.

Syntax

Parameters

–system sysname

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

–format format






–connectparam


storstat volume –function –functionparam ... –connectparam ...

storstat volume –get –system sysname [ –format format ] –connectparam ...

storstat

U41824-J-Z156-1-76 213

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

18:0

1.05

Pfa

d: O

:\alf\

stor

ma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\s

tors

tat.

doc

Return codes

Output

The following volume specific metrics are provided:







18 STORMAN_NOT_FOUND Matching object could not be provided.


Function rejected by SMI-S Provider.


CIM Server or database not available.

Name Description Comments

StatisticsTime Absolute point in time of collecting statistical data. Format: CIM_DATETIME

Example: 20080319063103.781250+000yyyymmddHHMMSS.mmmmmmsUUU

SampleInterval Period of time the statistical data are collected from the storage array. Format: Interval Format (WMI)

Default setting: 5 min.Example:00000000000500.000000:000ddddddddHHMMSS.mmmmmm:000

ReadIOs Number of read IOs (Counter) Available for Symmetrix, FibreCAT CX and CLARiiON CX.

WriteIOs Number of write IOs (Counter) Available for Symmetrix, FibreCAT CX and CLARiiON CX.

KBytesRead Amount of KB read (Counter) Available for Symmetrix, FibreCAT CX and CLARiiON CX.

KBytesWritten Amount of KB written (Counter) Available for Symmetrix, FibreCAT CX and CLARiiON CX.

SampledReadsCounter Number of read IOs sampled to obtain the sampledReadsTime

Available for Symmetrix only. FibreCAT CX / CLARiiON CX storage systems do not provide this metric.

storstat

214 U41824-J-Z156-1-76

● All Counters are defined as UINT64 (the maximum value being 18446744073709551615). However overflow is handled by the provider.

● All time values are provided in micro seconds (µsec).

Examples


storstat volume -get -system 6ARA100505 (FibreCAT CX) storage system name = CLARiiON+6ARA100505 ... time last sampled = 20080318151708.687000+000 sample interval = 00000000000500.000000:000 storage StatisticsVolume(s)...

DeviceID = 1016

SampledReadsTime Cumulated time value in µsec elapsed for the sampled read IOs


SampledWritesCounter Number of write IOs sampled to obtain the sampledWritesTime


SampledWritesTime Cumulated time value in µsec elapsed for the sampled write IOs


IOTimeCounter Absolute counter representing all samples representing the cumulated IO service times of the components engaged in a IO for the respective volume

Provided for FibreCAT CX / CLARiiON CX storage systems instead of read /write specific metrics. Notes: – CLARiiON does not distinguish

reads from writes. – The sum of IOTimeCounter +

IdleTimeCounter is constant representing the sampling interval.

IdleTimeCounter Absolute counter representing all samples finding the IO processing idleing for the respective volume

refer to IOTimeCounter

Name Description Comments

storstat

U41824-J-Z156-1-76 215

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ai 2

009

Sta

nd

18:0

1.05

Pfa

d: O

:\alf\

stor

ma

n_0

7101

00\

0710

101

_bh

b\pr

od_

e\st

orm

an.v

11\s

tors

tat.

doc

StatisticTime = 20080318151652.484375+000 ReadIOs = 19446368 WriteIOs = 7036210 KBytesRead = 77701347 KBytesWritten = 28144910 IOTimeCounter = 93492 IdleTimeCounter = 28479267...

storstat volume -get -system *405 (Symmetriy) storage system name = SYMMETRIX+000287400405 ... time last sampled = 20080319063107.906000+000 sample interval = 00000000000500.000000:000 storage StatisticsVolume(s) DeviceID = 0000 StatisticTime = 20080319063103.781250+000 ReadIOs = 18234 WriteIOs = 0 KBytesRead = 9120 KBytesWritten = 0 SampledReadsCounter = 4535 SampledReadsTime = 845888 SampledWritesCounter = 0 SampledWritesTime = 0


storstat volume -get -system *405 -format xmlp (FibreCAT CX) <Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <SubCode>STORMAN_SUB_NONE</SubCode> <Text>Successful</Text> </ReturnCode> <Result> <StorageSystem> <StorageSystemName>CLARiiON+6ARA100505</StorageSystemName> <StorageModel>STORMAN_STORAGE_MODEL_CLARIION</StorageModel> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <Status>succesful</Status> <TimeLastSampled>20080319134136.234000+000</TimeLastSampled> <SampleInterval>00000000000500.000000:000</SampleInterval> <StatisticsVolumes> <StatisticsVolume> <DeviceID>0000</DeviceID> <StatisticTime>20080319134128.859375+000</StatisticTime> <ReadIOs>16695</ReadIOs>

storstat

216 U41824-J-Z156-1-76

<WriteIOs>520</WriteIOs> <KBytesRead>15327</KBytesRead> <KBytesWritten>2009</KBytesWritten> <IOTimeCounter>92</IOTimeCounter> <IdleTimeCounter>29379520</IdleTimeCounter> </StatisticsVolume>

... </StatisticsVolumes> </StorageSystem> </Result></Response>

storstat volume -get -system *405 -format xmlp (Symmetrix)<Response> <ReturnCode> <Code>STORMAN_OK</Code> <CodeNumber>0</CodeNumber> <SubCode>STORMAN_SUB_NONE</SubCode> <Text>Successful</Text> </ReturnCode> <Result> <StorageSystem> <StorageSystemName>SYMMETRIX+000287400405</StorageSystemName> <StorageModel>STORMAN_STORAGE_MODEL_SYMMETRIX</StorageModel> <StorageVendor>STORMAN_STORAGE_VENDOR_EMC</StorageVendor> <Status>succesful</Status> <TimeLastSampled>20080319134128.875000+000</TimeLastSampled> <SampleInterval>00000000000500.000000:000</SampleInterval> <StatisticsVolumes> <StatisticsVolume> <DeviceID>0000</DeviceID> <StatisticTime>20080319134112.656250+000</StatisticTime> <ReadIOs>18618</ReadIOs> <WriteIOs>0</WriteIOs> <KBytesRead>9312</KBytesRead> <KBytesWritten>0</KBytesWritten> <SampledReadsCounter>4620</SampledReadsCounter> <SampledReadsTime>861600</SampledReadsTime> <SampledWritesCounter>0</SampledWritesCounter> <SampledWritesTime>0</SampledWritesTime> </StatisticsVolume>

... </StatisticsVolumes> </StorageSystem> </Result></Response>

U41824-J-Z156-1-76 217

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

200

9 S

tand

18

:00.

55P

fad

: O:\

alf\

stor

man

_07

101

00\0

710

101_

bhb

\pro

d_e

\sto

rma

n.k1

2

11 StorMan for programmers – StorMan Client interface for information and monitoringThis 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 (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 / CLARiiON CX storage arrays 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 repos-itory; 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.

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

StorMan Client interface for information and monitoring

218 U41824-J-Z156-1-76

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.

U41824-J-Z156-1-76 219

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09 S

tand

18:

00.5

5P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.a

nh

12 Appendix

Fujitsu Technology Solutions: 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 Technology Solutions.

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 Technology Solutions 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 Technology Solutions 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 Technology Solutions upon request.

Appendix

220 U41824-J-Z156-1-76

2. End User License

2.1 Fujitsu Technology Solutions 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 Technology Solutions, 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 Technology Solutions directly or from authorized software resellers.

3. Downloading

For Software supplied by Fujitsu Technology Solutions over a network or a similar distribution path, the following additional conditions shall apply:

All products supplied for downloading by Fujitsu Technology Solutions 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

Appendix

U41824-J-Z156-1-76 221

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09 S

tand

18:

00.5

5P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.a

nh

own risk. Fujitsu Technology Solutions 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 Technology Solutions is operated and administered only for those countries in which Fujitsu Technology Solutions has one or more offices. Fujitsu Technology Solutions accepts no responsibility that Software and/or documentation can or may be downloaded from a Fujitsu Technology Solutions website also in locations other than the countries mentioned above. If you access a website of Fujitsu Technology Solutions from abroad, you are fully responsible for complying with any local regulations. Fujitsu Technology Solutions expressly prohibits the downloading of Software and/or documentation from a Fujitsu Technology Solutions 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 Technology Solutions and/or its third-party licensors.

The license terms do not authorize you to use the brands, logos or trademarks of Fujitsu Technology Solutions 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 Technology Solutions. Each and any use of brands, logos or trademarks with respect to the Software or Fujitsu Technology Solutions requires the express consent of Fujitsu Technology Solutions.

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 Technology Solutions 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

Appendix

222 U41824-J-Z156-1-76

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 Technology Solutions disclaims all warranties for the Software in this agreement. For the same reason, Fujitsu Technology Solutions 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 Technology Solutions.

In this End User License Agreement, Fujitsu Technology Solutions 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 Technology Solutions received from a third party. Fujitsu Technology Solutions 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 Technology Solutions 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 abovementioned GPL terms or by the conditions which are otherwise included with the open source software components. Fujitsu Technology Solutions receives neither license fees nor any other compensation for the delivered open source software components. As far as Fujitsu Technology Solutions 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.

http://www.gnu.org/copyleft/gpl.html

Appendix

U41824-J-Z156-1-76 223

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09 S

tand

18:

00.5

5P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.a

nh

Because of the special nature of the development and distribution of open source software components, Fujitsu Technology Solutions 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 Technology Solutions 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 Technology Solutions 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 Technology Solutions for direct damage caused as a result of a contract violation and/or other action or lapse on the part of Fujitsu Technology Solutions 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 Technology Solutions 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 Technology Solutions 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

Appendix

224 U41824-J-Z156-1-76

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 Technology Solutions 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 Technology Solutions 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 Technology Solutions 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.

Appendix

U41824-J-Z156-1-76 225

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Mai

20

09 S

tand

18:

00.5

5P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.a

nh

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, the Czech Republic, Georgia, Hungary, 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.

Appendix

226 U41824-J-Z156-1-76

U41824-J-Z156-1-76 227

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Ma

i 200

9 S

tan

d 18

:00.

55P

fad

: O:\

alf\s

torm

an_

071

010

0\07

1010

1_b

hb\p

rod

_e\s

torm

an.m

ix

GlossaryCIM / 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.

HostA computer that is connected to the storage array through a fibre-channel interface.

Initiator PortPort (FC connection) of an HBA. A port that initiates IOs to or from a logical device. Opposite to target port.

IP addressThe 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.

IQNiSCSI Qualified Name.

JNLPJava Network Launching Protocol.

LUNLogical Unit Number.

LUN maskingSelected visibility of specified LUNs of a FC connected storage array for an HBA.

Glossary

228 U41824-J-Z156-1-76

Pool A storage pool administrated by StorMan. It is a named collection of logical devices in the StorMan repository.

ServerIn 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-SStorage Management Initiative Specification.

SNIAStorage Networking Industry Association.

Storage Pool A named collection of logical devices in the storage system. In the manual storage pools administrated by StorMan are just called pools to differentiate them from the notion of storage pools used in the context of storage systems.

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.

StorManCentral and uniform storage management service for automatic storage provi-sioning.

Target PortFC 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.

URLUniform Resource Locator.

VCM Volume Configuration Management.

VCM databaseDatabase that contains all LUN masking information in the form of VCM records on a Symmetrix System. The database is located on a VCM device.

Glossary

U41824-J-Z156-1-76 229

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Ma

i 200

9 S

tan

d 18

:00.

55P

fad

: O:\

alf\s

torm

an_

071

010

0\07

1010

1_b

hb\p

rod

_e\s

torm

an.m

ix

VCM deviceSpecial device on a Symmetrix System that contains the VCM database.

VCM recordA 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 ServerFull-service web servers act as HTTP servers. In addition, they have many other capabilities, such as running CGI scripts.

WWPNWorld Wide Port Number.

Glossary

230 U41824-J-Z156-1-76

U41824-J-Z156-1-76 231

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28.

Ma

i 200

9 S

tan

d 18

:00.

56

Pfa

d: O

:\al

f\sto

rma

n_07

101

00\0

710

101

_bhb

\pro

d_e

\sto

rman

.lit

Related publicationsThe manuals are available as online manuals, see http://manuals.ts.fujitsu.com, or in printed form which must be paid and ordered separately at http://manualshop.ts.fujitsu.com.

[1] SHC-OSD Storage Management for BS2000/OSDUser Guide

[2] IMON (BS2000/OSD)Installation MonitorUser Guide

Related publications

232 U41824-J-Z156-1-76

U41824-J-Z156-1-76 233

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ay 2

009

S

tand

18:

04.1

3P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.

six

Index

AAccessLogix 87Apache Server 50API Server

specify 69authorization 27

CCIM Server

specify 69CLARiiON CX 20, 21, 22, 31, 87CLI 99

common aspects 99connection parameters 100enumeration values 101help function 100parameter file 99

common parametersvalues range 105

configuration data 23configuration file 41configuration layer 23Configure tab 68connection parameters

CLI 100connectivity type 20, 21, 22

Ddeinstallation 52device

attach 77detach 78release 78

disaster recovery 9discovery 69

document root 50Dynamic Data Center 9dynamic layer 24

Eenumeration values

CLI 101

FFibreCAT CX 20, 21, 22, 31, 87FibreCAT SX 20, 32full copy mirror 187

GGUI 55

main window 60start 55

Hhigh availability 28host

add 77hostname

common parameter 105

Iinformation and monitoring

API 217installation

EMC SMI-S Provider 35StorMan GUI 50StorMan Server (Linux) 40StorMan Server (Windows) 45

ipcommon parameter 105

Index

234 U41824-J-Z156-1-76

Llocal replication 187LUN masking

FibreCAT CX / CLARiiON CX 89NetApp FAS 96Symmetrix 92

MManage tab 76mirror pair

activate 188deactivate 194restore 198terminate 200

mirroringrestart 196

mirroring paircreate 191

mirrors pairrecreate 196

NNetApp FAS systems 20NetApp® FAS 32

Oobject group 211

Ppool 23

create 70poolid

common parameter 105provisioning 9

Rreplication 22, 79repository 23, 27

add a new host 112configure 110modify attributes of a host 113

SSMI-S 25SMI-S Provider 29smserver.ini 41snapshot 187software requirements 33SPC 95statistic 21, 83statistic and performance 21, 83storage array

discover 71storage information and monitoring 20storage layer 24storage pool 23storage provisioning 9, 19storage system

discovery 134storage volume

create 71discovery 156use 70

storattach 106storcfg 110storcfg cimom 120

-add 121-discover 127-mod 123-rem 125-show 129

storcfg host 111-add 112-mod 113-rem 116

storcfg host_-show 117storcfg pool 140

-add 141-mod 143-rem 145-show 146

storcfg system 132-discover 134-rem 133-show 135

Index

U41824-J-Z156-1-76 235

Dok

usch

ablo

nen

19x

24 V

ers

ion

7.3

2us

für

Fra

me

Mak

er

V7.

xvo

m 2

8.0

3.20

07©

cog

nita

s G

mbH

200

1-2

007

28. M

ay 2

009

S

tand

18:

04.1

3P

fad:

O:\a

lf\st

orm

an_0

710

100

\071

010

1_bh

b\p

rod_

e\s

torm

an.

six

storcfg volume 149-add 150, 188-discover 156-mod 152-rem 154-show 158

storcheck 109storcreate 171stordelete 174stordetach 176storemc 179

-add 180-rem 182

storIDcommon parameter 105

storinfo 184StorMan

architecture 26Client 26Server 26

StorMan configurationCLI 68, 69, 77

StorMan GUI -> GUI 55StorMan service

start and stop (Linux) 44start and stop (Windows) 49

STORMAN_ACCESS_MODE 101STORMAN_CONNECTION_TYPE 102STORMAN_RESOURCE_TYPE 101STORMAN_STORAGE_MODEL 102stormandb 185stormirror

activate 188create 191deactivate 194recreate 196restore 198terminate 200

storparam 209Symmetrix 20, 21, 87system requirements 31

Vvirtualization layer 23VolumeLogix 87

WWWPN

common parameter 105

Index

236 U41824-J-Z156-1-76

storage manager v2 - fujitsumanuals.ts.fujitsu.com/file/8618/storman.pdf · ... srdf™,...

Documents