IBM
TotalStorage
SAN
Volume
Controller
Configuration
Guide
Version
1.2.1
IBM
TotalStorage
SAN
Volume
Controller
Configuration
Guide
Version
1.2.1
FourthEdition(October2004)
Note:Beforeusingthisinformationandtheproductitsupports,readtheinformationin″Notices.″
Contents
Figures. . . ix
Tables . . . xi
About thisguide . . . xiii
Whoshouldusethis guide . . . xiii
Summaryof Changes . . . xiii
Summaryof ChangesforSC26-7543-03SANVolumeController ConfigurationGuide . . . xiii
Emphasis . . . xv
Numbering conventions . . . xvi
SANVolumeControllerlibraryandrelatedpublications . . . xvi
RelatedWebsites . . . xviii
Howto orderIBMpublications. . . xviii
Howto sendyourcomments. . . xix
Chapter1. Overview . . . 1
SANVolumeController . . . 1
Virtualization . . . 4
Asymmetric virtualization. . . 7
Symmetricvirtualization . . . 8
Object overview . . . 9
Nodes andclusters . . . 11
I/OgroupsandUninterruptiblePower Supply. . . 15
Storage subsystemsandmanageddisks . . . 20
Managed diskgroupsandvirtualdisks(VDisks). . . 24
Hosts andvirtual(VDisk)mappings . . . 29
CopyServices . . . 32
FlashCopy . . . 32
Remote Copy . . . 44
Configurationrules andrequirements. . . 49
Configurationrules . . . 51
Configurationrecommendationsfor largeSANs . . . 60
Configurationrequirements . . . 62
Maximumconfiguration . . . 64
Supportedfibre-channelextenders. . . 66
Performanceoffibre-channelextenders. . . 66
Chapter2. Preparingto configuretheSANVolumeController . . . 69
Createclusterfromthefrontpanel. . . 69
Overview ofpasswords. . . 71
Masterconsolesecurityoverview . . . 72
Masterconsole. . . 73
Validatingthetruststorecertificateexpiration . . . 74
Configuringthemasterconsole . . . 75
Configuringthenetwork . . . 76
Configuringthebrowser . . . 78
Secure Shell(SSH) . . . 78
ConfiguringtheSecureShell(SSH)clientsystem . . . 80
Configuringthemasterconsolehostname. . . 84
StartingtheTivoli SANManager . . . 85
SettingupRemoteSupport . . . 86
IBMDirector. . . 88 ||
ConfiguringIBMDirectorfortheSANVolumeControllerCall-Homeand
Event Notification . . . 89
Upgradingsoftwareonthemasterconsole. . . 94
Connectingto theRemote SupportCenter. . . 95
ClearingtheWindowseventlogs . . . 95
Troubleshootingmasterconsoleproblems . . . 96
Installingantivirussoftware . . . 98
Chapter3. SANVolumeControllerConsole . . . 101
Using theSANVolumeControllerConsole . . . 101
Accessing theSANVolumeControllerConsole . . . 102
SANVolumeControllerConsolelayout . . . 103
SANVolumeControllerConsolebannerarea . . . 103
SANVolumeControllerConsoletaskbar. . . 104
SANVolumeControllerConsoleportfolio. . . 104
SANVolumeControllerConsoleworkarea . . . 104
UpgradingtheSANVolumeControllerConsolesoftware . . . 104
Overview ofcreatinga clusterusingtheSANVolumeControllerConsole 105 Browserrequirements fortheSANVolumeController . . . 105
ConfiguringaclusterusingtheSANVolumeControllerConsole . . . 106
LaunchingtheSANVolumeControllerConsole . . . 114
Settingclustertime . . . 116
DisplayingclusterpropertiesusingtheSANVolumeControllerConsole 117 Scenario: typicalusagefortheSANVolumeControllerConsole . . . 118
Addingnodestoa cluster . . . 120
Displayingnode propertiesusingtheSANVolumeControllerConsole . . . 125
Creatingmanageddiskgroups . . . 125
Creatingvirtualdisks . . . 127
Using imagemode virtualdisks . . . 127
Creatinghosts. . . 131
Showing VDisksmappedto ahost . . . 132
Creatingconsistencygroups . . . 133
CreatingFlashCopymappings. . . 133
AdvancedfunctionFlashCopyoverview . . . 134
StartingFlashCopymappings . . . 135
StoppingFlashCopymappings . . . 135
DeletingFlashCopymappings . . . 135
StartingFlashCopyconsistency groups . . . 136
StoppingFlashCopyconsistencygroups . . . 136
DeletingFlashCopyconsistencygroups . . . 137
AdvancedfunctionsoverviewfortheSANVolumeControllerConsole . . . . 137
DeterminingtheWWPNsfor anodeusingtheSANVolumeController Console . . . 138
DeterminingtherelationshipbetweenVDisksandMDisksusingtheSAN VolumeControllerConsole . . . 138
DeterminingtherelationshipbetweenmanageddisksandRAIDarraysor LUNs usingtheSANVolumeControllerConsole . . . 139
IncreasingthesizeofyourclusterusingtheSANVolumeControllerConsole 139 Replacingafaultynodewithaspare nodeusingtheSANVolumeController Console . . . 142
RecoveringfromofflineVDisksafteranode oranI/Ogroupfailed . . . . 146
ReplacinganHBAinahost usingtheSANVolumeControllerConsole 148 Deletinghosts. . . 149
Shrinking virtualdisks . . . 149
Migratingvirtualdisks . . . 150
Creatingimage-modevirtualdisks . . . 151
AdvancedfunctionRemote Copyoverview . . . 152
Advancedfunctionclusteroverview . . . 152
Chapter4. Command-LineInterface . . . 169
Using theCommand-Line Interface(CLI) . . . 169
PreparingtheSSHclientsystemoverview . . . 170
PreparingtheSSHclientsystemto issuecommand-lineinterface commands . . . 171
PreparingtheSSHclientonanAIXhost . . . 172
Issuing CLIcommandsfromaPuTTYSSHClient system . . . 174
RunningthePuTTYandplinkutilities . . . 174
ConfiguringtheclusterusingtheCLI . . . 177
SettingtheclustertimeusingtheCLI . . . 178
ReviewingandsettingtheclusterfeaturesusingtheCLI . . . 178
DisplayingclusterpropertiesusingtheCLI . . . 179
MaintainingpasswordsusingtheCLI . . . 179
Scenario: typicalusageforthecommand-lineinterface. . . 179
Addingnodestoacluster usingtheCLI . . . 181
Displayingnode propertiesusingtheCLI. . . 186
Discovering MDisksusingtheCLI . . . 187
Creatingmanageddisk(MDisk)groupsusingtheCLI . . . 188
AddingMDiskstoMDiskgroupsusingtheCLI. . . 190
Createvirtualdisks(VDisks) . . . 191
Creatinghostobjects usingtheCLI . . . 194
CreateVDisk-to-hostmappingsusingtheCLI . . . 195
CreateFlashCopymappingsusingtheCLI . . . 195
CreatingaFlashCopyconsistencygroupandaddingmappingsusingthe CLI . . . 196
Preparingandtriggering aFlashCopymapping usingtheCLI . . . 197
Preparingandtriggering aFlashCopyConsistencyGroupusingtheCLI 198 AdvancedfunctionswiththeCLI . . . 200
DeterminingtheWWPNsof anodeusingtheCLI . . . 200
DeterminingtheVDisknamefromthevpathnumberonthehost . . . 201
DeterminingthehostthataVDiskismappedto . . . 202
DeterminingtherelationshipbetweenVDisksandMDisksusingtheCLI 202 DeterminingtherelationshipbetweenMDisksandRAIDarraysorLUNs usingtheCLI . . . 203
IncreasingthesizeofyourclusterusingtheCLI . . . 203
ReplacingafaultynodeintheclusterusingtheCLI. . . 206
RecoveringfromofflineVDisksafteranode oranI/Ogroupfailedusingthe CLI . . . 210
ReplacinganHBAinahost usingtheCLI . . . 213
ExpandingVDisks . . . 214
Shrinking aVDiskusingtheCLI . . . 217
MigratingextentsusingtheCLI . . . 217
MigratingVDisksbetweenMDiskgroupsusingtheCLI. . . 219
MigratingaVDiskbetweenI/OgroupsusingtheCLI . . . 220
Creatinganimagemode VDiskfromanunmanagedMDiskusingtheCLI 221 AdvancedfunctionclusteroverviewusingtheCLI . . . 222
Chapter5. Backingupandrestoringtheclusterconfiguration . . . 231
Backing uptheclusterconfiguration. . . 231
Restoringtheclusterconfiguration . . . 234
Deletinga backupconfigurationfile . . . 238
Disruptivesoftwareupgrade . . . 242
UpgradingtheSANVolumeControllerfirmwareusingtheSANVolume ControllerConsole . . . 243
Performing thenode rescue. . . 246
Automaticupgrade . . . 247
Automaticrecoveryfromupgradeproblems . . . 247
PuTTYscp . . . 248
Installing theupgradeusingtheCLI. . . 249
Installing thesoftware . . . 250
Manual recoveryfromsoftwareupgradeproblems . . . 251
Chapter7. Configuringother SANdevicesandSANswitches forusewith the SANVolumeController . . . 253
Configuringandservicingstoragesubsystems. . . 253
Identifying yourstoragesubsystem . . . 254
Configurationguidelines . . . 254
Configuringabalancedstoragesubsystem . . . 260
Expandingalogical unit . . . 263
Modifyinga logicalunitmapping . . . 264
Storage subsystemtasksusingtheSANVolumeControllerConsole. . . . 265
ControllertasksusingtheCLI . . . 269
Creatingaquorumdisk . . . 272
Manualdiscovery . . . 273
Servicingstoragesubsystems . . . 273
ConfiguringtheEMCCLARiiONsubsystem . . . 273
Access Logix . . . 274
ConfiguringtheEMCCLARiiONcontrollerwithAccessLogixinstalled . . . 274
ConfiguringtheEMCCLARiiONcontroller(Access Logixnotinstalled) 277 Supportedmodels oftheEMCCLARiiON . . . 277
Supportedfirmware levelsfortheEMC CLARiiON . . . 278
ConcurrentmaintenanceontheEMCCLARiiON . . . 278
UserinterfaceonCLARiiON . . . 278
SharingtheEMCCLARiiONbetweenahostandtheSANVolumeController 279 Switchzoning limitationsfor theEMC CLARiiON . . . 279
Quorumdisks ontheEMCCLARiiON . . . 280
AdvancedfunctionsfortheEMCCLARiiON. . . 280
Logical unitcreationanddeletionontheEMCCLARiiON. . . 281
Configuringsettingsfor theEMCCLARiiON. . . 281
ConfiguringtheEMCSymmetrixsubsystem. . . 285
Supportedmodels oftheEMCSymmetrixcontroller. . . 285
Supportedfirmware levelsfortheEMC Symmetrixcontroller . . . 286
ConcurrentmaintenanceontheEMCSymmetrix . . . 286
UserinterfaceonSymmetrix . . . 287
SharingtheEMCSymmetrixcontrollerbetweenahostandtheSANVolume Controller . . . 287
Switchzoning limitationsfor theEMC Symmetrix . . . 288
Quorumdisks onEMCSymmetrix . . . 288
AdvancedfunctionsforEMC Symmetrix . . . 289
Logical unitcreationanddeletiononEMCSymmetrix . . . 289
Configurationinterface fortheEMCSymmetrix . . . 290
Configuringsettingsfor theEMCSymmetrix . . . 290
ConfiguringtheEnterpriseStorageServer . . . 293
ConfiguringtheEnterpriseStorageServer(ESS) . . . 293
Supportedmodels oftheESS . . . 295
Supportedfirmware levelsfortheESS. . . 295
ConcurrentmaintenanceontheESS . . . 295
||
||
||
||
UserinterfaceonESS. . . 295
SharingtheESSbetweena hostandtheSANVolumeController. . . 296
Switchzoning limitationsfortheESS . . . 296
Quorumdisks ontheESS . . . 296
AdvancedfunctionsfortheESS . . . 297
Logical unitcreationanddeletionontheESS . . . 297
ConfiguringtheFAStTsubsystem . . . 298
ConfiguringFAStTdiskcontrollersforthestorageserver . . . 299
Support actionsfor theFAStTcontroller . . . 300
Supportedmodels oftheIBMFAStTcontroller. . . 302
Supportedfirmware levelsfortheFAStT . . . 302
ConcurrentmaintenanceontheIBMFAStT . . . 302
UserinterfaceonFAStT . . . 302
SharingtheIBMFAStTcontrollerbetweenahostandtheSANVolume Controller . . . 303
Quorumdisks ontheIBMFAStT . . . 303
AdvancedfunctionsfortheIBMFAStT. . . 303
Logical unitcreationanddeletionontheIBMFAStT. . . 305
Configurationinterface fortheIBMFAStT . . . 305
ControllersettingsfortheIBMFAStT . . . 306
ConfiguringtheHDSLightningsubsystem . . . 309
Supportedmodels oftheHDSLightning . . . 310
Supportedfirmware levelsforHDSLightning . . . 310
ConcurrentmaintenanceontheHDSLightning99xxV . . . 311
UserinterfaceonLightning . . . 311
SharingtheHDSLightning99xxVbetweenhostandtheSANVolume Controller. . . 311
Quorumdisks onHDSLightning99xxV . . . 312
AdvancedfunctionsforHDSLightning. . . 312
LUconfigurationfor Lightning . . . 313
Configuringsettingsfor Lightning. . . 315
ConfiguringtheHDSThundersubsystem. . . 317
Supportedmodels oftheHDSThunder . . . 317
Supportedfirmware levelsforHDSThunder. . . 318
ConcurrentmaintenanceontheHDSThunder . . . 318
UserinterfaceontheHDSThunder. . . 318
SharingtheHDSThunderbetweenhost andtheSANVolumeController 319 SettingupaThunderwithmorethanfourports . . . 320
Quorumdisks onHDSThunder . . . 320
AdvancedfunctionsforHDSThunder . . . 321
Logical unitcreationanddeletiononHDSThunder . . . 322
Configuringsettingsfor HDSThunder . . . 323
ConfiguringtheHPStorageWorkssubsystem . . . 328
HPStorageWorksdefinitions . . . 330
ConfiguringtheHPStorageWorkscontroller. . . 332
Supportedmodels oftheHPStorageWorkscontroller . . . 335
Supportedfirmware levelsfortheHPStorageWorkscontroller . . . 336
ConcurrentmaintenanceontheHPStorageWorks . . . 336
Configurationinterface fortheHPStorageWorks . . . 337
SharingtheHPStorageWorkscontrollerbetweenahostandtheSAN VolumeController . . . 337
Switchzoning limitationsfortheHPStorageWorkssubsystem . . . 338
Quorumdisks onHPStorageWorks. . . 338
Support forHPStorageWorksadvancedfunctions . . . 339
HPStorageWorksadvancedfunctions . . . 340
Logical unitcreationanddeletionontheHPStorageWorks . . . 340
|| || || || || ||
Configuringsettingsfor theHPStorageWorks . . . 341
ConfiguringtheHPQEnterpriseVirtualArray(EVA)subsystem. . . 346
Supportedmodels oftheHPQEVA . . . 346
Supportedfirmware levelsforHPQ EVA . . . 347
UserinterfaceonHPQEVA. . . 347
SharingtheHPQEVAcontrollerbetweena hostandtheSANVolume Controller . . . 347
Switchzoning limitationsfor theHPQ EVAsubsystem . . . 348
Quorumdisks onHPQ EVA. . . 348
Support forHPQ EVAadvancedfunctions . . . 348
Logical unitconfigurationontheHPQEVA . . . 348
Logical unitpresentation . . . 349
Configurationinterface fortheHPQEVA . . . 350
Configuringsettingsfor theHPQEVA . . . 350
Switch zoningfortheSANVolumeController . . . 351
Zoningconsiderations forRemoteCopy . . . 354
Switchoperationsoverlong distances . . . 355
Reference . . . 357
Installing orupgradingtheIBMTotalStorageSANVolumeControllerConsole for Windows . . . 357
InstallationoverviewfortheSANVolumeControllerConsole . . . 358
SANVolumeControllerConsolehardwareinstallationrequirements . . . . 359
SANVolumeControllerConsoleworkstationspacerequirements . . . 360
SANVolumeControllerConsolesoftwareinstallationrequirements . . . . 360
Installingor upgradingtheSANVolumeControllerConsoleingraphical mode . . . 361
Installingor upgradingtheSANVolumeControllerConsoleinunattended (silent)mode . . . 366
Verifying theWindowsservicesassociatedwiththeSANVolumeController Console . . . 371
Postinstallationtasks . . . 371
Removing theSANVolumeControllerConsole . . . 374
Valid combinationsofFlashCopyandRemoteCopyfunctions . . . 376
SettingupSNMPtraps . . . 376
ConfiguringIBMDirectoroverview . . . 377
Settingupaneventactionplan . . . 377
Settingupane-mail . . . 378
Settingupane-mailusernotification . . . 379
Object types . . . 380
Event codes . . . 381
Informationeventcodes . . . 381
Configurationeventcodes . . . 383
Accessibility . . . 386 Notices . . . 387 Trademarks. . . 389 Glossary. . . 389 Index . . . 399 || || || || | || || || || || || || ||
Figures
1. ASANVolumeControllernode . . . 2
2. Exampleofa SANVolumeControllerinafabric. . . 3
3. Levelsofvirtualization . . . 6
4. Asymmetricalvirtualization. . . 7
5. Symmetricalvirtualization . . . 8
6. Virtualization . . . 10
7. Cluster,nodes,andclusterstate. . . . 12
8. Configurationnode . . . 15
9. I/Ogroupanduninterruptiblepowersupply . . . 16
10. Uninterruptiblepowersupply . . . 17
11. I/Ogroupsanduninterruptiblepowersupplyrelationship . . . 19
12. ControllersandMDisks . . . 22
13. MDiskgroup . . . 26
14. ManageddiskgroupsandVDisks . . . 27
15. Hosts,WWPNs,andVDisks . . . 31
16. Hosts,WWPNs,VDisksandSCSImappings . . . 32
17. Diskcontrollersystem sharedbetweenSANVolumeControlleranda host . . . 53
18. ESSLUsaccesseddirectly witha SANVolumeController . . . 54
19. FAStTdirectconnectionwithaSANVolumeControllerononehost . . . 55
20. FabricwithInter-SwitchLinksbetweennodesinacluster. . . 59
21. FabricwithInter-SwitchLinksina redundantconfiguration . . . 59
22. Basicframe layout. . . 103
23. Bannerarea . . . 103
24. Taskbar . . . 104
25. Welcomepanel . . . 107
26. AddCluster panel . . . 108
27. AddCluster panel . . . 109
28. Securityalertpanel . . . 109
29. CertificateInformationpanel . . . 110
30. CreateNewClusterwizard. . . 111
31. ErrorNotificationSettingspanel . . . 112
32. FeaturizationSettingspanel . . . 113
33. AddSSHpublickeypanel . . . 114
34. Viewingclusterspanels . . . 115
35. Welcomepanel . . . 116
36. Clusterdateandtimesettingspanel . . . 117
37. ViewClusterpropertiespanel. . . 118
38. SANVolumeControllerConsoleNodespanel. . . 121
39. Nodespanel . . . 122
40. Addnode dropdownlist . . . 123
41. AddNodeto Clusterpanel. . . 124
42. Viewinggeneraldetailspanel. . . 125
43. SANVolumeControllerConsolenodespanel . . . 156
44. Featurizationsettings. . . 235
45. Softwareupgradepanel. . . 244
46. Softwareupgrade-fileuploadpanel . . . 244
47. Applyingsoftwareupgradepanel . . . 245
48. Node-rescue-requestdisplay . . . 246
49. DestinationDirectorypanel . . . 363
50. PuTTYConfigurationpanel . . . 364
51. UpdatingEmbeddedWASPortspanel . . . 365
Tables
1. Emphasisdescriptions . . . xv
2. PublicationsintheSANVolumeControllerlibrary . . . xvii
3. OtherIBMpublications . . . xviii
4. Websites . . . xviii
5. Nodestate . . . 14
6. Manageddiskstatus . . . 22
7. Manageddiskgroupstatus . . . 25
8. Capacitiesoftheclustergivenextentsize . . . 26
9. Virtualdiskstatus . . . 28
10. FlashCopymapping events . . . 37
11. Backgroundcopy. . . 43
12. SANVolumeControllermaximumconfigurationvalues . . . 64
13. Upgradingvendorsoftware . . . 94
14. ReasonstoupgradeIBMsoftware . . . 94
15. Extentsize . . . 189
16. Supportedplatformsandrequirements . . . 214
17. CalculatetheI/Orate. . . 261
18. CalculatetheimpactofFlashCopyrelationships . . . 262
19. Determineifthestoragesubsystemisoverloaded . . . 262
20. SupportedmodelsoftheEMCCLARiiON . . . 277
21. EMCCLARiiONglobalsettingssupportedbytheSANVolumeController . . . 282
22. EMCCLARiiONcontrollersettingssupportedbytheSANVolumeController . . . 282
23. EMCCLARiiONportsettingssupportedbytheSANVolumeController . . . 283
24. EMCCLARiiONLUsettingssupportedbytheSANVolumeController. . . 284
25. SupportedmodelsoftheEMCSymmetrix . . . 285
26. EMCSymmetrixglobalsettingssupportedbytheSANVolumeController . . . 291
27. EMCSymmetrixportsettingssupportedbytheSANVolumeController . . . 291
28. EMCSymmetrixLUsettingssupportedbytheSANVolumeController. . . 292
29. SupportedmodelsoftheEnterpriseStorage Server . . . 295
30. SupportedmodelsoftheIBMFAStTcontroller . . . 302
31. IBMFAStTcontrollerglobalsettingssupportedbytheSANVolumeController. . . 308
32. SupportedHDSLightningmodels . . . 310
33. LightningglobalsettingssupportedbytheSANVolumeController . . . 315
34. LightningcontrollersettingssupportedbytheSANVolumeController . . . 316
35. LightningportsettingssupportedbytheSANVolumeController . . . 316
36. LightningLU settingsfor theSANVolumeController . . . 316
37. SupportedThunder9200models . . . 317
38. SupportedThunder95xxVmodels . . . 318
39. ThunderglobalsettingssupportedbytheSANVolumeController . . . 324
40. ThunderportsettingssupportedbytheSANVolumeController . . . 325
41. ThunderLU settingsfor theSANVolumeController . . . 327
42. Determiningpartition usage . . . 334
43. SupportedmodelsoftheHPStorageWorksHSG80 . . . 336
44. HSG80containertypesforlogical unitconfiguration . . . 340
45. HSG80globalsettingssupportedbytheSANVolumeController. . . 341
46. HSG80controllersettingssupportedbytheSANVolumeController . . . 342
47. HSG80portsettingssupportedbythe . . . 343
48. HSG80LUsettingssupportedbytheSANVolumeController . . . 344
49. HSG80connectionoptionsandtheirrequiredsettingsforthe . . . 344
50. SupportedHPQEVAmodels . . . 347
51. HPQEVAglobalsettingssupportedbytheSANVolumeController . . . 350
52. HPQEVALUsettingssupportedbytheSANVolumeController . . . 351
53. HPQEVAhostsettingssupportedbytheSANVolumeController . . . 351
|| || || || || || || ||
54. Fourhostsandtheirports . . . 352
55. Sixhostsandtheirports . . . 353
56. Validcombinationsof FlashCopyandRemoteCopyinteractions . . . 376
57. Objecttypes . . . 380
58. Informationeventcodes. . . 382
59. Configurationeventcodes . . . 383
|| ||
About
this
guide
TheIBMTotalStorageSANVolumeControllerConfigurationguideprovides informationthathelpsyouconfigureandusetheIBM®TotalStorage®SANVolume Controller™.
TheIBMTotalStorageSANVolumeControllerConfigurationguidealsodescribes theconfigurationtools,bothcommand-lineandWebbased,thatyoucanuseto define,expand, andmaintainthestorageoftheIBMTotalStorageSANVolume Controller.
Who
should
use
this
guide
TheIBMTotalStorageSANVolumeControllerConfigurationguideisintended for system administratorsorotherswhoinstallandusetheSANVolumeController. BeforeusingtheIBMTotalStorageSANVolumeController,youshouldhave an understandingof storageareanetworks(SANs), thestoragerequirements ofyour enterprise,andthecapabilitiesofyourstorageunits.
Relatedreference “Aboutthisguide”
TheIBMTotalStorageSANVolumeControllerConfigurationguideprovides informationthathelpsyou configureandusetheIBM®TotalStorage®SAN VolumeController™.
Summary
of
Changes
This documentcontainsterminology,maintenance,andeditorial changes. Technical changesor additionstothetextandillustrationsareindicatedbya vertical lineto theleftof thechange.This summaryof changesdescribesnew functionsthathave beenaddedtothisrelease.
Relatedreference
“SummaryofChangesforSC26-7543-03 SANVolumeControllerConfiguration
Guide”
TheSummaryof Changesprovidesa listofnew,modified,andchanged informationsincethelast versionoftheguide.
Summary
of
Changes
for
SC26-7543-03
SAN
Volume
Controller
Configuration
Guide
TheSummaryof Changesprovidesalist ofnew,modified,andchangedinformation sincethelastversion oftheguide.
Newinformation
This topicdescribesthechangestothisguidesincethepreviousedition, SC26-7543-02. Thefollowing sectionssummarize thechangesthathavesince been implementedfromthepreviousversion.
This versionincludesthefollowingnewinformation: v Addedthefollowingnew topics:
– ConfigurationrecommendationsforlargeSANs
– Queuedepth
– Calculatingaqueuedepthlimit
– Homogeneousqueuedepthcalculation
– Non-Homogeneousqueuedepthcalculation
– Limitingthequeuedepth
– Validatingthetruststorecertificateexpiration
– Usingimagemodevirtualdisks
– Storingpreexistingdata ontotheSANVolumeController
– ExposingLUN‘sonyourexistingstorageto theclusterviaswitchzoning
– Imagemode VDiskmigration
– Migrationmethods
– ImportingdatabycreatinganimagemodeVDisk
– ReviewingandsettingtheclusterfeaturesusingtheSANVolumeController
Console
v UpdatedtheEMCCLARiiONsubsystemsectionwiththefollowingnewtopics:
– AccessLogix
– Userinterface onCLARiiON
v UpdatedtheEMCSymmetrixsubsystemsectionwiththefollowing newtopic:
– Userinterface onSymmetrix
v UpdatedtheESSsubsystemsectionwiththefollowing newtopics:
– Userinterface onESS
– TargetportgroupsfortheESS
v UpdatedtheFAStTsubsystemsectionwiththefollowingnewtopic:
– Userinterface onFAStT
v UpdatedtheHDSLightningsubsystemsectionwiththefollowingnewtopics:
– Userinterface onLightning
– LUconfigurationfor Lightning
– Logicalunitcreationanddeletion onHDSLightning
– ConfiguringsettingsforLightning
– Globalsettingsfor Lightning
– Controllersettingsfor Lightning
– PortsettingsforLightning
– LUsettingsfor Lightning
v UpdatedtheHDSThundersubsystemsectionwiththefollowingnewtopic:
– Userinterface ontheHDSThunder
v Addedsupportfor theHPQ EnterpriseVirtualArray(EVA)subsystem.This
sectionincludesthefollowingnew topics: – SupportedmodelsoftheHPQ EVA
– Supportedfirmwarelevelsfor HPQEVA
– Userinterface onHPQ EVA
– SharingtheHPQEVAcontrollerbetweenahostandtheSANVolume
Controller
– Switchzoninglimitationsfor theHPQEVAsubsystem
– Supportfor HPQEVAadvancedfunctions
– LogicalunitconfigurationontheHPQ EVA
– Logicalunitcreationanddeletion ontheHPQ EVA
– Logicalunitpresentation
– ConfigurationinterfacefortheHPQ EVA
– ConfiguringsettingsfortheHPQEVA
– Globalsettingsfor theHPQEVA
– LUsettingsfor theHPQEVA
– HostsettingsfortheHPQ EVA
Changedinformation
This sectionliststheupdatesthatweremade inthis document.
v Supportfor 4-nodeconfigurationshas beenupdatedtosupport8-node.
v Increasedthenumberof supportedVDisksperI/Ogroupto 1024.
v Increasedthenumberof supportedVDisksperclusterto 4096.
v Updatedsupportinformationfor splitcontrollerconfigurations.
v Updatedthenumberofuninterruptiblepowersuppliestosupportupto8 nodes.
v Updatedthemaximumconfigurations.
v Updatedconfigurationexamplesto includea8-nodeconfiguration.
v Modifiedthestep-by-step instructionsfor restoringaclusterconfiguration.
v UpdatedtheSwitchzoninglimitationsfortheEMCCLARiiONsubsystem.
v UpdatedtheGlobalsettingsfortheEMCSymmetrixsubsystem.
v UpdatedtheSupportedmodelsof theIBMFAStTcontroller.
Deletedinformation
No deletionswere madeinthisversionof theguide.
Relatedreference
“SummaryofChanges”onpagexiii
Thisdocumentcontainsterminology, maintenance,andeditorialchanges.
Emphasis
Different typefacesareused inthis guideto showemphasis. Thefollowingtypefacesareusedto showemphasis:
Table1.Emphasisdescriptions
Boldface Textinboldfacerepresentsmenuitemsand
commandnames.
Italics Textinitalicsisusedtoemphasizeaword.
Incommandsyntax,itisusedforvariables forwhichyousupplyactualvalues,suchas adefaultdirectoryorthenameofacluster.
Table1.Emphasisdescriptions (continued)
Monospace Textinmonospaceidentifiesthedataor commandsthatyoutype,samplesof commandoutput,examplesofprogramcode ormessagesfromthesystem,ornamesof commandflags,parameters,arguments,and name-valuepairs.
Numbering
conventions
Aspecificnumberingconvention isused inthis guideandproduct.
Thefollowingnumberingconventionsareusedinthisguideandintheproduct: v 1kilobyte(KB)isequalto 1024bytes
v 1megabyte(MB)isequalto1048576bytes
v 1gigabyte(GB)isequalto1073741824bytes
v 1terabyte(TB)isequalto1099511627776bytes
v 1petabyte (PB)isequalto1 125899906842624bytes Relatedreference
“Aboutthisguide”onpage xiii
TheIBMTotalStorageSANVolumeControllerConfigurationguideprovides informationthathelpsyou configureandusetheIBM®TotalStorage®SAN VolumeController™.
“Whoshould usethisguide”onpagexiii
TheIBMTotalStorageSANVolumeControllerConfigurationguideisintended forsystem administratorsorotherswho installandusetheSANVolume Controller.
SAN
Volume
Controller
library
and
related
publications
Alistofotherpublicationsthatarerelatedtothisproductareprovidedto youfor your reference.
Thetablesinthissectionlist anddescribethefollowingpublications:
v Thepublicationsthatmakeupthelibraryfor theIBMTotalStorageSANVolume
Controller
v OtherIBMpublicationsthatrelateto theSANVolumeController
SANVolumeControllerlibrary
Table2 onpage xviilistsanddescribesthepublicationsthatmakeuptheSAN VolumeControllerlibrary.Unlessotherwisenoted,thesepublicationsareavailable inAdobe portabledocumentformat (PDF)onacompactdisc(CD)thatcomeswith theSANVolumeController.Ifyou needadditionalcopiesof thisCD,theorder numberisSK2T-8811.ThesepublicationsarealsoavailableasPDFfilesfromthe following Website:
Table2.PublicationsintheSANVolumeControllerlibrary
Title Description Ordernumber
IBMTotalStorageSAN VolumeController:CIMAgent Developer’sReference
Thisreferenceguide describestheobjectsand classesinaCommon InformationModel(CIM) environment.
SC26-7590
IBMTotalStorageSAN VolumeController: Command-LineInterface User’sGuide
Thisguidedescribesthe commandsthatyoucanuse fromtheSANVolume Controllercommand-line interface(CLI).
SC26-7544
IBMTotalStorageSAN VolumeController: ConfigurationGuide
Thisguideprovides guidelinesforconfiguring yourSANVolumeController.
SC26-7543
IBMTotalStorageSAN VolumeController:Host AttachmentGuide
Thisguideprovides guidelinesforattachingthe SANVolumeControllerto yourhostsystem.
SC26-7575
IBMTotalStorageSAN VolumeController: InstallationGuide
Thisguideincludesthe instructionstheservice representativeusestoinstall theSANVolumeController.
SC26-7541
IBMTotalStorageSAN VolumeController:Planning Guide
Thisguideintroducesthe SANVolumeControllerand liststhefeaturesyoucan order.Italsoprovides guidelinesforplanningthe installationandconfiguration oftheSANVolume
Controller.
GA22-1052
IBMTotalStorageSAN VolumeController:Service Guide
Thisguideincludesthe instructionstheservice representativeusesto servicetheSANVolume Controller.
SC26-7542
IBMTotalStorageSAN VolumeController:Translated SafetyNotices
Thisguidecontainsthe dangerandcautionnotices fortheSANVolume Controller.Thenoticesare showninEnglishandin numerousotherlanguages.
SC26-7577
OtherIBM publications
Table3 onpage xviiilistsanddescribesotherIBMpublicationsthatcontain additionalinformationrelatedto theSANVolumeController.
Table3.OtherIBMpublications
Title Description Ordernumber
IBMTotalStorageEnterprise StorageServer,IBM TotalStorageSANVolume Controller,IBMTotalStorage SANVolumeControllerfor CiscoMDS9000,Subsystem DeviceDriver:User’sGuide
ThisguidedescribestheIBM SubsystemDeviceDriver Version1.5forTotalStorage Productsandhowtouseit withtheSANVolume Controller.Thispublicationis referredtoastheIBM TotalStorageSubsystem DeviceDriver:User’sGuide.
SC26-7608
Relatedreference
“HowtoorderIBMpublications”
Thepublicationscenterisaworldwidecentralrepositoryfor IBMproduct publicationsandmarketingmaterial.
Relatedinformation
“Howtosend yourcomments”onpage xix
Related
Web
sites
Table4 listsWebsitesthathaveinformationabout SANVolumeControlleror relatedproducts ortechnologies.
Table4.Websites
Typeofinformation Website
SANVolumeControllersupport
http://www-1.ibm.com/servers/storage/support/virtual/2145.html TechnicalsupportforIBMstorage
products
http://www.ibm.com/storage/support/
How
to
order
IBM
publications
ThepublicationscenterisaworldwidecentralrepositoryforIBMproduct publicationsandmarketingmaterial.
TheIBMpublications center
TheIBMpublicationscenteroffers customizedsearchfunctionstohelp youfindthe publicationsthatyou need.Somepublicationsareavailableforyouto viewor download freeof charge.You canalsoorderpublications.Thepublicationscenter displays pricesinyourlocalcurrency.YoucanaccesstheIBMpublicationscenter throughthefollowingWebsite:
www.ibm.com/shop/publications/order/
Publicationsnotificationsystem
TheIBMpublicationscenterWebsiteoffersyoua notificationsystem forIBM publications. Registerandyoucancreateyourown profileof publicationsthat interest you.Thepublicationsnotificationsystemsendsyoua dailye-mailthat containsinformationabout neworrevised publicationsthatarebasedonyour profile.
If youwantto subscribe,youcanaccessthepublicationsnotificationsystem from theIBMpublicationscenterat thefollowingWebsite:
www.ibm.com/shop/publications/order/
Relatedreference
“SANVolumeControllerlibraryandrelatedpublications”onpagexvi
Alistof otherpublicationsthatarerelatedtothis productareprovided toyoufor yourreference.
How
to
send
your
comments
Your feedbackisimportant tohelpusprovidethehighestqualityinformation. Ifyou have anycommentsaboutthis bookoranyother documentation,youcansubmit them inoneof thefollowingways:
v e-mail
Submityour commentselectronicallytothefollowinge-mailaddress: [email protected]
Besureto includethenameandordernumberofthebook and,ifapplicable,the specificlocationof thetextyouarecommentingon,suchasapage numberor tablenumber.
v Mail
FillouttheReaders’Comments form(RCF)at thebackof thisbook.IftheRCF hasbeenremoved, youcanaddressyourcommentsto:
International Business Machines Corporation RCF Processing Department
Department 61C 9032 South Rita Road Tucson, Arizona 85775-4401 U.S.A.
Relatedreference
“SANVolumeControllerlibraryandrelatedpublications”onpagexvi
Alistof otherpublicationsthatarerelatedtothis productareprovided toyoufor yourreference.
Chapter
1.
Overview
This partprovidesanoverviewoftheSANVolumeController.
Relatedconcepts “SANVolumeController”
TheSANVolumeControllerisaSANappliancethatattachesopen-systems storagedevicesto supportedopen-systemshosts.
Relatedreference
“Objectoverview”onpage9
TheSANVolumeControllerisbasedonanumberof virtualizationconcepts.
“CopyServices”onpage32
Therearetwo typesof CopyServicesupportedbytheSANVolumeController.
“Configurationrulesandrequirements”onpage49
Ensurethatyouunderstandtherulesandrequirementswhenconfiguringthe SANVolumeController.
SAN
Volume
Controller
TheSANVolumeControllerisa SANappliancethatattachesopen-systemsstorage devicesto supportedopen-systemshosts.
TheIBM®TotalStorage®SANVolumeControllerprovidessymmetricvirtualization bycreatinga poolofmanaged disksfromtheattachedstoragesubsystems,which arethenmappedto asetofvirtualdisksfor usebyattachedhostcomputer
systems.Systemadministratorscanviewandaccessacommonpool ofstorageon theSAN,whichenables themtouse storageresourcesmoreefficientlyand
providesacommon basefor advancedfunctions.
TheSANVolumeControllerisanalogous toalogical volumemanager(LVM)ona SAN.It performsthefollowing functionsfortheSANstoragethatit iscontrolling: v Createsa singlepoolofstorage
v Manageslogical volumes
v ProvidesadvancedfunctionsfortheSAN,suchas:
– Largescalablecache
– Copyservices
- Point-in-timeCopy
- FlashCopy
®
(point-in-timecopy) - RemoteCopy(synchronouscopy)
- Datamigration
– Spacemanagement
- Mappingthatisbasedondesiredperformancecharacteristics
- Qualityofservice metering
Anodeisasinglestorageengine.SeeFigure1onpage2 foravisual ofanode. Thestorageenginesarealwaysinstalledinpairs withoneto fourpairsofnodes constitutingacluster. Eachnodeinapairisconfiguredtobackuptheother.Each pairof nodesisknown asanI/Ogroup.AllI/Ooperationsthataremanagedbythe nodesinanI/Ogroup arecachedonbothnodesforresilience. Eachvirtualvolume |
| | | |
isdefinedto anI/Ogroup. Toavoidanysinglepoint offailure,thenodesofanI/O group areprotected byindependent uninterruptiblepowersupply units.
TheSANVolumeControllerI/Ogroupssee thestoragepresentedtotheSANby thebackendcontrollersasanumberofdisksknownasmanaged disks.The applicationservicesdonotseethesemanageddisks. Insteadtheyseeanumberof logical disks,knownasvirtualdisks,thatarepresentedto theSANbytheSAN VolumeController. Eachnodemustonly beinoneI/Ogroupandprovideaccessto thevirtualdisksintheI/Ogroup.
TheSANVolumeControllerhelpsto providecontinuousoperationsandcanalso optimizethedatapathto ensureperformancelevels aremaintained. Ensurethat you useIBMTotalStorageMultipleDeviceManagerperformancemanagerto analyzetheperformancestatistics.SeeIBMTotalStorageMultipleDeviceManager ConfigurationandInstallationGuideandIBMTotalStorage MultipleDeviceManager CLI Guideformoreinformation.
Thefabriccontainstwodistinctzones:a hostzoneanda diskzone.Inthehost zone,thehostsystemscanidentifyandaddress thenodes.Youcanhave more than onehostzone.Generally,you willcreateonehostzone peroperating system type. Inthediskzone,thenodescanidentifythediskdrives.Hostsystemscannot operateonthediskdrivesdirectly;alldatatransferoccursthroughthenodes.As shown inFigure2onpage3, severalhostsystemscanbeconnectedtoaSAN fabric.AclusterofSANVolumeControllersisconnectedtothesamefabricand presents virtualdiskstothehostsystems.Youconfigurethesevirtualdisksusing thediskslocated ontheRAIDcontrollers.
Note: Youcanhave morethanonehostzone.Generallyyoucreateonehost zone
peroperatingsystemtype becausesomeoperatingsystemswillnottolerate otheroperatingsystemsinthesamezone.
Figure1.ASANVolumeControllernode | | | | | | |
You canremoveonenodeineach I/Ogroupfromaclusterwhenhardware service or maintenanceisrequired.Afteryouremovethenode,youcanreplacethefield replaceable units(FRUs) inthenode.Alldiskdrivecommunicationand
communicationbetweennodesisperformedthroughtheSAN.AllSANVolume Controllerconfigurationandservicecommandsaresentto theclusterthroughan Ethernetnetwork.
Each nodecontainsitsown vitalproductdata(VPD).Eachcluster containsVPD thatiscommon toallthenodesonthecluster,andanysystem connectedtothe EthernetnetworkcanaccessthisVPD.
Cluster configurationinformationisstoredoneverynodethatisinthecluster to allow concurrentreplacement ofFRUs.Anexampleof thisinformationmightbe informationthatisdisplayedonthemenuscreenof theSANVolumeController. Whena newFRUisinstalledandwhenthenodeisaddedbackintothecluster, configurationinformationthatisrequiredbythatnode isreadfromothernodesin thecluster.
SANVolumeControlleroperating environment
v MinimumofonepairofSANVolumeControllernodes
v Minimumtwouninterruptiblepowersupplies
v OnemasterconsoleisrequiredperSANinstallationfor configuration
Features ofaSANVolumeControllernode
v 19-inchrackmountedenclosure
v 4fibrechannel ports
v 2fibrechannel adapters
Fibre Channel Fabric
Host Host Host Host
SAN Volume Controller
.
.
.
RAID RAID
. . .
RAID RAID Host zone Disk zone SAN Volume Controller SAN Volume ControllerFigure2.ExampleofaSANVolumeControllerinafabric
|
v 4GBcachememory
Supportedhosts
For alistof supportedoperating systems,seetheIBMTotalStorageSANVolume ControllerWebsiteat:
http://www-1.ibm.com/servers/storage/support/virtual/2145.html
Multipathingsoftware
v IBMSubsystemDeviceDriver(SDD)
v RedundantDualActiveController(RDAC)
Note: Directattachhostssharingabackendstoragecontrollerwitha SANVolume
ControllercanrunmultipathdriversSDDandRDAC.Thereisnosupportfor theco-existenceofnativemultipathdriverswithSDDonthesamehost. Check thefollowingWebsite forthelatestsupportandcoexistenceinformation: http://www-1.ibm.com/servers/storage/support/virtual/2145.html
User interfaces
TheSANVolumeControllerprovidesthefollowinguserinterfaces:
v IBMTotalStorageSANVolumeControllerConsole,aWeb-accessiblegraphical
userinterface(GUI)thatsupportsflexibleandrapidaccesstostorage managementinformation
v Acommand-lineinterface(CLI) usingSecure Shell(SSH)
Application programminginterfaces
TheSANVolumeControllerprovidesthefollowingapplicationprogramming interface:
v IBMTotalStorageCommonInformationModel(CIM)Agentfor theSANVolume
Controller,whichsupports theStorage ManagementInitiativeSpecificationofthe StorageNetworkIndustryAssociation.
Relatedconcepts “Virtualization”
Virtualizationisaconcept thatappliestomanyareasof theinformation technologyindustry.
“Asymmetricvirtualization”onpage7
Withasymmetricvirtualization,thevirtualizationengineisoutsidethedatapath andperformsametadatastyleservice.Themetadata servercontainsallthe mappingandthelockingtableswhilethestoragedevicescontainonlydata.
“Symmetricvirtualization” onpage8
TheSANVolumeControllerprovidessymmetricvirtualization.
Virtualization
Virtualization isaconceptthatapplies tomanyareasof theinformationtechnology industry.
Where datastorageisconcerned,virtualizationincludesthecreationof apoolof storagethatcontainsseveraldisksubsystems.Thesesubsystemscanbefrom |
| |
various vendors.Thepoolcanbesplitintovirtualdisksthatarevisibleto thehost systemsthatusethem.Therefore, virtualdiskscan usemixedback-endstorage andprovidea commonwaytomanagea storageareanetwork (SAN).
Historically, thetermvirtualstoragehasdescribedthevirtualmemorytechniques thathave beenusedinoperating systems.Thetermstoragevirtualization,however, describestheshift frommanagingphysicalvolumesofdata tologicalvolumesof data.This shiftcanbemadeonseverallevelsof thecomponentsof storage networks.Virtualization separatestherepresentationofstoragebetweenthe operating systemanditsusersfromtheactualphysicalstoragecomponents.This techniquehasbeen usedinmainframecomputersfor manyyearsthroughmethods suchassystem-managedstorageandproducts liketheIBMDataFacilityStorage Management Subsystem(DFSMS).Virtualization canbeapplied atfourmainlevels: v Virtualizationat theserverlevelisperformedbymanagingvolumesonthe
operatingsystemsservers.An increaseintheamountoflogicalstorageover physicalstorageissuitablefor environmentsthatdonothavestoragenetworks. v Virtualizationat thestoragedevice levelisincommonuse.Striping,mirroring,
andredundantarraysofindependent disks(RAIDs)areused byalmostalldisk subsystems.Thistypeof virtualizationcanrangefromsimpleRAIDcontrollersto advancedvolumemanagementsuchasthatprovidedbytheIBMTotalStorage EnterpriseStorageServer (ESS)or byLogStructuredArrays(LSA).TheVirtual TapeServer(VTS)isanotherexampleof virtualizationat thedevice level. v Virtualizationat thefabriclevelenablesstoragepoolstobeindependentof the
serversandthephysicalcomponentsthatmakeupthestoragepools.One managementinterface canbeused tomanagedifferentstoragesystemswithout affectingtheservers.TheSANVolumeControllerisusedto performvirtualization atthefabriclevel.
v Virtualizationat thefilesystemlevelprovidesthehighestbenefitbecausedatais
shared,allocated,andprotected,notvolumes.
Virtualization isaradicaldeparturefromtraditionalstoragemanagement.In
traditionalstoragemanagement,storageisattached directlyto ahostsystem,which controls storagemanagement.SANsintroducedtheprincipleofnetworksof
storage,butstorageisstillprimarilycreatedandmaintainedat theRAIDsubsystem level.MultipleRAIDcontrollersofdifferenttypesrequireknowledgeof,andsoftware thatisspecificto,thegivenhardware.Virtualizationbringsacentralpointof control for diskcreation andmaintenance.It bringsnew waysofhandlingstorage
maintenance.
Wherestorageisconcerned,oneproblematicareathatvirtualizationaddresses is thatof unusedcapacity.Ratherthanindividualstoragesystemsremainingislands unto themselves,allowingexcessstoragecapacitytobewastedwhenjobsdonot requireit,storageispooledsothatjobsneeding thehighest storagecapacitycan use itwhentheyneedit.Regulatingtheamountof storageavailable becomes easierto orchestratewithout computingresourceorstorageresourcehaving tobe turned offandon.
Types ofvirtualization
Virtualization canbeperformedeitherasymmetricallyorsymmetrically.SeeFigure3 onpage6 formoreinformation.
Asymmetric
Avirtualization engineisoutside thedatapath andperforms ametadata styleservice.
Symmetric
Avirtualization enginesitsinthedata path,presentingdiskstothehosts buthidingthephysicalstoragefromthehosts.Advancedfunctions,suchas cacheandCopyServices,canthereforebeimplementedintheengine itself.
Virtualization atanylevelprovidesbenefits.Whenseveral levelsarecombined, however,thebenefits ofthoselevelscanalsobecombined.Anexampleofhow you can gainthehighestbenefitsisif youattacha lowcost RAIDcontrollertoa
virtualization enginethatprovidesvirtualvolumesforusebyavirtualfilesystem.
Note: TheSANVolumeControllerimplementsfabric-levelvirtualization.Withinthe
contextof theSANVolumeControllerandthroughoutthis document,
virtualizationrefersto symmetricfabric-levelvirtualization.
Relatedconcepts
“Asymmetricvirtualization”onpage7
Withasymmetricvirtualization,thevirtualizationengineisoutsidethedatapath andperformsametadatastyleservice.Themetadata servercontainsallthe mappingandthelockingtableswhilethestoragedevicescontainonlydata.
“Symmetricvirtualization” onpage8
TheSANVolumeControllerprovidessymmetricvirtualization.
“Virtualdisks”onpage26
AVDiskisalogicaldiskthattheclusterpresentsto thestorageareanetwork (SAN).
Relatedreference
“Configuringandservicingstoragesubsystems”onpage253
Followtheguidelinesandproceduresoutlinedinthissection tomakethemost oftheperformanceavailablefromyourstoragesubsystemsandtoavoid potentialI/Oproblems.
SAN
IBM AIX SUN Solaris HP-UX Windows
Server level
Fabric level Meta data server
Storage device level
Asymmetric
virtualization
Withasymmetric virtualization,thevirtualizationengineisoutsidethedatapathand performsa metadatastyleservice.Themetadataservercontainsallthemapping andthelockingtableswhilethestoragedevicescontainonly data.
In asymmetricvirtualstoragenetworks,thedataflow,(2)inthefigurebelow, is separatedfromthecontrolflow,(1).Aseparatenetwork orSANlinkisused for controlpurposes.Themetadataservercontainsallthemappingandlockingtables while thestoragedevicescontainonly data.Becausetheflowof controlis
separatedfromtheflowof data,I/Ooperationscanusethefullbandwidthof the SAN.Aseparatenetworkor SANlink isusedforcontrolpurposes.Thereare disadvantages,however,toasymmetric virtualization.
Thedisadvantagestoasymmetric virtualizationinclude:
v Dataisat risktoincreasedsecurityexposuresandthecontrolnetwork mustbe
protectedwithafirewall.
v Metadatacanbecome verycomplicatedwhenfilesaredistributedacrossseveral
devices.
v Eachhostthataccesses theSANmustknowhow toaccessandinterpretthe
metadata.Specific devicedriversoragent softwaremust thereforeberunningon eachof thesehosts.
v Themetadataservercannotrunadvancedfunctionssuchascachingorcopy
servicesbecauseit onlyknows aboutthemetadataandnotaboutthedataitself. SeeFigure4
For one,dataisatrisk toincreasedsecurityexposuresandthecontrolnetwork must beprotected witha firewall.In addition,metadata canbecomevery
complicatedwhenfilesaredistributedacrossseveral devices.Moreover,eachhost thataccesses theSANmust knowhowtoaccessandinterpretthemetadata. Specific devicedriveror agentsoftwaremustthereforeberunningoneach ofthese hosts.Finally, themetadata servercannotrunadvancedfunctions,suchascaching or copyservicesbecauseitonly knowsaboutthemetadata andnotabout thedata itself.
Relatedconcepts
“Symmetricvirtualization”onpage8
TheSANVolumeControllerprovidessymmetricvirtualization.
Metadata server Storage pool Host Storage pool Host SAN fabric 1 2
Symmetric
virtualization
TheSANVolumeControllerprovidessymmetricvirtualization.
Virtualization splitsthephysicalstorageRedundantArrayofIndependentDisks (RAID)arraysintosmallerchunksof storagethatareknown asextents. These extents arethenconcatenatedtogether,usingvariouspolicies, tomakevirtual disks. Withsymmetricvirtualization,hostsystemscanbeisolatedfromthephysical storage.Advancedfunctions,suchasdatamigration,can runwithout theneed to re-configurethehost. Withsymmetric virtualization,thevirtualizationengineisthe centralconfigurationpointfor theSAN.
In symmetricvirtualstoragenetworks(seeFigure5), dataandcontrolbothflow over thesamepath.Becausetheseparationof thecontrolfromthedataoccursin thedatapath, thestoragecanbepooledunderthecontrolofthevirtualization engine.Thevirtualizationengineperformsthelogical-to-physicalmapping.
Thevirtualizationenginedirectly controlsaccesstothestorageandtothedatathat iswrittento thestorage.Asa result,lockingfunctionsthatprovidedataintegrityand advancedfunctions,suchascacheandcopyservices,canberuninthe
virtualization engineitself.Thevirtualizationengineis,therefore,acentralpoint of controlfor deviceandadvancedfunctionmanagement.Symmetricvirtualization also allowsyouto buildakind offirewallinthestoragenetwork.Onlythevirtualization enginecangive accessthroughthefirewall.Symmetricvirtualization does,however, causesomeproblems.
Themain problemthatisassociatedwithsymmetricvirtualizationisrelatedto poor performance, becauseallI/Omustflowthroughthevirtualizationengine.This problem isoneof scalability.You canuseann-wayclusterof virtualizationengines thathas failovercapacitytosolvethisproblem.Youcan scaletheadditional processorpower,cachememory,andadapterbandwidthto getthelevelof
performancethatyou want.Thememoryandprocessingpowercanbeusedtorun theadvancedfunctions,suchascopyservicesandcaching.
TheIBMTotalStorageSANVolumeControllerusessymmetricvirtualization.Single virtualization engines,whichareknownasnodes,arecombinedto createclusters. Each clustercancontainbetweentwoandeightnodes.
Relatedconcepts Virtualizer Storage pool Host Storage pool Host SAN fabric I/O I/O
Figure5.Symmetricalvirtualization
“Asymmetricvirtualization”onpage7
Withasymmetricvirtualization,thevirtualizationengineisoutsidethedatapath andperformsametadatastyleservice.Themetadata servercontainsallthe mappingandthelockingtableswhilethestoragedevicescontainonlydata.
“Virtualization”onpage4
Virtualizationisaconcept thatappliestomanyareasof theinformation technologyindustry.
Object
overview
TheSANVolumeControllerisbasedonanumberofvirtualizationconcepts.
ASANVolumeControllerconsistsof asinglenode.Nodesaredeployedinpairs to makeupacluster.Acluster canhave1to 4nodepairs init.Eachpairof nodesis known asanI/Ogroup.EachnodemustbeinonlyoneI/Ogroup.
Virtual disks(VDisks)arelogical disksthatarepresentedtotheSANbynodes. Virtual disksarealso associatedwithanI/Ogroup. ThenodesintheI/Ogroup provideaccessto thevirtualdisksintheI/Ogroup.Whenanapplicationserver performsI/Oto avirtualdisk,ithasthechoiceof accessingthevirtualdiskvia either ofthenodesintheI/Ogroup.Aseach I/Ogrouponlyhastwo nodes,the distributedcachetheSANVolumeControllerprovidesisonly2-way.
Each nodedoesnotcontainanyinternalbatterybackupunitsandthereforemust beconnectedto anUninterruptiblePowerSupply(UPS)toprovidedata integrity intheeventof acluster-widepowerfailure.Insuchsituations,theUPSwillmaintain powerto thenodeswhilethecontentsofthedistributedcachearedumpedto an internaldrive.
ThenodesinaclusterseethestoragepresentedbySAN-attachedstorage subsystemsasanumberofdisks,known asmanageddisks(MDisks).Because theSANVolumeControllerdoesnotattempttoproviderecovery fromphysicaldisk failures withinthebackenddiskcontrollers,amanaged diskisusually,butnot necessarily,a redundantarrayof independentdisks(RAID)array.
Each manageddiskisdivided intoanumberofextents (defaultsizeis16MB) which arenumbered from0,sequentially,fromthestarttotheendof themanaged disk.TheextentsizemustbespecifiedwhencreatinganMDiskgroup.
Managed disksarecollected intogroups,knownasmanageddiskgroups(MDisk groups).Virtualdisksarecreatedfromtheextentscontainedbyamanageddisk group. Themanaged disksthatconstituteaparticularvirtualdiskmust allcome fromthesamemanageddiskgroup.
At anyonetime,asinglenode intheclusterisusedto manageconfiguration activity.Thisconfigurationnodemanagesacacheof theinformationthat describestheclusterconfigurationandprovidesa focalpoint forconfiguration. TheSANVolumeControllerdetectstheFibreChannelportsthatareconnectedto theSAN.Thesecorrespondto theHostBusAdapter (HBA)FibreChannels worldwideportnames(WWPNs)thatarepresentintheapplicationservers.The SANVolumeControllerallowsyou tocreatelogicalhostobjects thatgrouptogether WWPNsbelongingtoa singleapplicationserverormultipleapplicationservers. Application serverscanonlyaccessvirtualdisksthathavebeenallocatedto them. Virtual diskscanbemappedto ahostobject.Theactofmapping avirtualdisktoa |
host objectmakesthevirtualdiskaccessibletotheWWPNsinthathostobject, and hencetheapplicationserveritself.
Relatedconcepts
“Nodesandclusters”onpage11
ASANVolumeControllernode isa singleprocessingunit,which provides virtualization,cache,andcopyservicesfortheSAN.
“I/OgroupsandUninterruptible PowerSupply”onpage 15
Nodesaredeployedinpairsto makeupacluster. Eachpairofnodesisknown asanI/Ogroup.EachnodemaybeinonlyoneI/Ogroup.
“Storagesubsystemsandmanageddisks”onpage20
ThenodesinaclusterseethestorageexportedbySAN-attachedstorage subsystemsasanumberofdisks,knownasmanaged disks.TheSANVolume Controllerdoesnotattempttoproviderecovery fromphysicaldiskfailureswithin thestoragesubsystem.Amanaged diskisusually,butnotnecessarily,a RAID array.
Mdisk 2 Mdisk 3 Mdisk 4 Mdisk 5 Mdisk 6 Mdisk 7 Mdisk 8
Mdisk 1 Mdisk 9
Vdisk 1 Vdisk 2 Vdisk 3 Vdisk 4 Vdisk 5
Cache Node 1 Cache Node 3 Cache Node 4 UPS 1 UPS 2 Cache Node 2 Config Node
I/O group 1 I/O group 2
Mdisk group 1 Mdisk group 2 Mdisk group 3
Storage subsystem 1 Storage subsystem 2 Storage subsystem 3
WWPN WWPN Host 1 Host 2 WWPN WWPN Host 3 WWPN WWPN Figure6.Virtualization
“Manageddiskgroupsandvirtualdisks(VDisks)”onpage 24
Manageddisksarecollectedintogroupsknownasmanageddiskgroups.Virtual disksarelogical disksthatarepresentedtotheSANbySANVolumeController nodes.ThemaximumnumberofsupportedVDisksperI/Ogroupis1024.The maximumnumberof supportedVDisksperclusteris4096. Virtualdisks,like nodes,areassociatedwithanI/Ogroup.
“Hostsandvirtual(VDisk)mappings”onpage 29
ApplicationserverscanonlyaccessVDisksthathavebeenmade accessibleto them.
Nodes
and
clusters
ASANVolumeControllernodeisasingle processingunit,whichprovides virtualization, cache,andcopyservicesfor theSAN.
Nodes aredeployedinpairscalledI/Ogroups.Onenodeintheclusteris
designated theconfigurationnodebuteach nodeintheclusterholdsacopyofthe clusterstate information.
Relatedconcepts “Clusters”
Allconfigurationandserviceisperformedat theclusterlevel.
Relatedreference “Nodes”onpage13
ASANVolumeControllernode isa singleprocessingunitwithina SANVolume Controllercluster.
Clusters
Allconfigurationandserviceisperformedattheclusterlevel.
Aclustercanconsistof twonodes,withamaximumofeight nodes.Therefore,you can assignupto eightSANVolumeControllernodestoonecluster.
Someservice actionscanbeperformedat nodelevel,butallconfigurationis replicatedacrossallnodesinthecluster. Becauseconfigurationisperformedatthe clusterlevel,anIPaddressisassignedtotheclusterinsteadof eachnode.
Allyourconfigurationandserviceactions areperformedat theclusterlevel. Therefore,afterconfiguring yourcluster,youcantake advantageof the virtualization andtheadvancedfeaturesof theSANVolumeController.
Clusterstateandthe configurationnode
Theclusterstate holdsallconfigurationandinternalclusterdatafor thecluster. This clusterstate informationisheldinnonvolatilememory.If themainlinepowerfails, thetwouninterruptiblepowersuppliesmaintaintheinternalpowerlongenoughfor theclusterstate informationtobestoredontheinternaldiskdrive ofeach node. Thereadandwritecacheinformationisalso heldinnonvolatilememory.Similarly,if thepowerfailstoanode, configurationandcachedatafor thatnodewillbelost andthepartner nodeattemptsto flushthecache.Theclusterstateisstill maintained bytheothernodesonthecluster.
Figure7onpage12showsanexampleclustercontaining fournodes.Thecluster state showninthegreyboxdoesnotactuallyexist,insteadeachnodeholdsa copy of theentireclusterstate.
| |
| |
Theclustercontainsasinglenode thatiselected astheconfigurationnode.The configurationnodecan bethoughtof asthenodethatcontrols theupdating of cluster state.For example,a userrequestismade (item1),thatresultsinachange beingmadeto theconfiguration.Theconfigurationnodecontrolsupdates tothe cluster (item2).Theconfigurationnode thenforwardsthechangetoallnodes (includingNode1), andtheyallmakethestate-changeatthesamepointintime (item 3).Usingthis state-drivenmodelofclusteringensuresthatallnodesinthe cluster knowtheexactclusterstateat anyonetime.
Clusterconfigurationbackup:
Configurationbackup istheprocess ofextractingconfigurationdatafromacluster andwriting itto disk.
Backing uptheclusterconfigurationenablesyouto restoreit intheeventthat configurationdataislost.Thedatathatisbackedupisthemetadata thatdescribes theclusterconfiguration,notthedatathatyourenterpriseusestorunitsbusiness. Thebackupconfigurationfilescanbesavedonthemasterconsoleorthe
configurationnode.
Objectsincludedinthe backup
Configurationdata isinformationabout aclusterandtheobjectsthataredefinedin it.Thefollowingobjectsarecopied:
v Storagesubsystem
v Hosts
v I/Ogroups
v Manageddisks(MDisks)
v MDiskgroups
v Nodes
v Virtualdisks(VDisks)
v VDisk-to-hostmappings
v SSHkey
v FlashCopymappings
v FlashCopyconsistency groups
v RemoteCopyrelationships
v RemoteCopyconsistencygroups
Cluster
Cluster state
Node 1 Node 2 Node 3
Copy of cluster state Copy of cluster state Copy of cluster state Copy of cluster state Node 4 1 2 3 3 3 3 Configuration node
Relatedconcepts
“Clusters”onpage11
Allconfigurationandserviceisperformedat theclusterlevel.
“Configurationrestore”
Configurationrestoreistheprocessof usinga backupconfigurationfile,orfiles, onthemasterconsoleor configurationnode torestoreaspecificcluster
configuration.
Configuration restore:
Configurationrestoreistheprocessofusingabackup configurationfile, orfiles,on themasterconsoleor configurationnode torestoreaspecificclusterconfiguration. Restoringyour clusterconfigurationinvolvesrestoring themetadata thatdescribes your clusterconfiguration,notthedatayourenterpriseusesto runitsbusiness. Restoringyour clusterconfigurationisanimportantpartofa completebackup and disaster recoverysolution.However,youmust makeprovisionfor your
non-configurationdatato berestoredaswell. This processconsistsof twophases:
v Preparing
v Executing
Restorephases
Beforeissuingthepreparationcommand,or phase,theclusteritselfmust bereset to adefaultstate withthecorrectclustername.Duringthepreparationphase,the backup dataandthenew clusterareanalyzedfor compatibility,anda sequenceof commands isprepared.
Duringtheexecutionphase,thecommandsequenceisrun.
Relatedconcepts “Clusters”onpage11
Allconfigurationandserviceisperformedat theclusterlevel.
Chapter5, “Backingupandrestoring theclusterconfiguration,”onpage231
Youcanbackupandrestoretheclusterconfiguration.
“Clusterconfigurationbackup”onpage12
Configurationbackupistheprocessofextractingconfigurationdatafroma clusterandwritingitto disk.
Nodes
ASANVolumeControllernodeisasingle processingunitwithinaSANVolume Controllercluster.
For redundancy,nodesaredeployedinpairsto makeupacluster.Aclustercan have onetofourpairsof nodesinit.EachpairofnodesisknownasanI/Ogroup. Each nodecanbeinonly oneI/Ogroup.Amaximumof fourI/Ogroupseach containing twonodesissupported.
At anyonetime,asinglenode intheclusterisusedto manageconfiguration activity.Thisconfigurationnodemanagesacacheoftheconfigurationinformation thatdescribestheclusterconfigurationandprovidesa focalpoint forconfiguration commands. Iftheconfigurationnodefails,anothernode intheclusterwilltakeover itsresponsibilities.
| | | |
Table5 describestheoperationalstatesof anode. Table5.Nodestate
State Description
Adding Thenodewasaddedtotheclusterbutisnotyet synchronizedwiththeclusterstate(seeNote).
Deleting Thenodeisintheprocessofbeingdeletedfrom thecluster.
Online Thenodeisoperational,assignedtoacluster,and hasaccesstothefibre-channelSANfabric.
Offline Thenodeisnotoperational.Thenodewas
assignedtoaclusterbutisnotavailableonthe fibre-channelSANfabric.RuntheDirected
MaintenanceProcedurestodeterminetheproblem.
Pending Thenodeistransitioningbetweenstatesand,ina fewseconds,willmovetooneoftheotherstates.
Note: ItispossiblethatanodecanstayintheAddingstateforalongtime.Ifthisisthe case,deletethenodeandthenre-addit.However,youshouldwaitforatleast30minutes beforedoingthis.Ifthenodethathasbeenaddedisatalowercodelevelthantherestof thecluster,thenodewillbeupgradedtotheclustercodelevel,whichcantakeupto20 minutes.Duringthistimethenodewillbeshownasadding.
Relatedconcepts “Configurationnode”
Atanygiventime,onenodemanagesconfigurationactivity.Thisnode isthe
configurationnode. Configuration node:
At anygiventime, onenodemanagesconfigurationactivity.Thisnodeisthe
configurationnode.
Theconfigurationnodeisafocalpointfor configurationcommands, anditmanages thedatathatdescribestheclusterconfiguration.
If theconfigurationnodefails,theclusterchoosesanew configurationnode.This actioniscalledconfigurationnodefailover.Theswitchthatcontainsthenew node takesovertheclusterIPaddress.Thusyoucan accesstheclusterthroughthe sameIPaddressalthough theoriginal configurationnodehas failed.During the failover,thereisashortperiodwhenyoucannotusethecommandline toolsor SANVolumeControllerConsole.
Thefigure belowshowsanexampleclustercontaining fournodes.Node1has been designatedtheconfigurationnode. Userrequests (1)aretargetedatNode1. This mayresultinrequests (2)beingtargetedat theothernodesinthecluster,and data beingreturnedtoNode1. SeeFigure8onpage15formoreinformation.
Relatedreference
“Nodes”onpage13
ASANVolumeControllernode isa singleprocessingunitwithina SANVolume Controllercluster.
I/O
groups
and
Uninterruptible
Power
Supply
Nodes aredeployedinpairstomakeupacluster.Eachpairof nodesisknown as anI/Ogroup.Eachnodemaybeinonly oneI/Ogroup.
Virtual disksarelogical disksthatarepresentedtotheSANbySANVolume Controllernodes.VirtualdisksarealsoassociatedwithanI/Ogroup.TheSAN VolumeControllerdoes notcontain anyinternalbatterybackupunitsandtherefore must beconnected toanuninterruptiblepowersupplyto providedataintegrityin theeventofa clusterwidepowerfailure.
Input/Output
(I/O)
groups
An I/Ogroupisagroupthatisdefinedduringtheclusterconfigurationprocess. It usuallycontainstwoSANVolumeControllernodesforavailabilitypurposes. However, dependingontheconfiguration,anI/Ogroup maybeemptyor just contain asinglenode.Each nodeisassociatedwithonlyoneI/Ogroup,andeach virtualdisk(VDisk)isassociatedwithonlyoneI/Ogroup.ThenodesintheI/O group provideaccessto theVDisksintheI/Ogroup.
WhenanapplicationserverperformsI/Oto avirtualdisk,ithasthechoiceof accessingthevirtualdiskviaeither ofthenodesintheI/Ogroup.Avirtualdiskcan specifyapreferrednode.Thisisspecifiedwhenthevirtualdiskiscreated.Thisis thenodethroughwhicha virtualdiskshouldnormallybeaccessed.Aseach I/O group onlyhastwonodes,thedistributedcacheintheSANVolumeControllerneed only be2-way.When I/Oisperformedto avirtualdisk,thenodethatprocessesthe I/Oduplicates thedataontothepartnernodethatisintheI/Ogroup.
I/Otraffic foraparticularvirtualdiskis,at anyonetime,handled exclusivelybythe nodesinasingleI/Ogroup.Thus, althoughaclustermay havemanynodeswithin it,thenodeshandleI/Oinindependentpairs.ThismeansthattheI/Ocapabilityof theSANVolumeControllerscaleswell,sinceadditionalthroughputcanbeobtained byaddingadditionalI/Ogroups.
Awriteoperation froma hostisshown(item1), thatistargetedfor virtualdiskA. This writeistargetedatthepreferrednode,Node1(item 2).Thewriteiscached anda copyof thedataismade inthepartner node,Node2’scache(item3).The writeisnowcomplete,sofarasthehostisconcerned.Atsomelatertime,thedata iswritten,or destaged,to storage(item4).Thefigurealso showstwo
Node 1 Node 2 Node 3 Node 4
2 Configuration Node IP Interface 1
uninterruptiblepowersupplies(1and2)correctlyconfiguredsothateachnodeisin a differentpowerdomain.
When anodefailswithinanI/Ogroup,theothernodeintheI/Ogroup willtake over theI/Oresponsibilitiesof thefailednode. Datalossduringanodefailureis preventedbymirroringtheI/Oread/writedatacachebetweenthetwonodesinan I/Ogroup.
If onlyonenodeisassignedto anI/Ogroup, oranodehas failedinanI/Ogroup, thecacheisflushedto thediskandthengoes intowrite-throughmode.Therefore, any writesforthevirtualdisksthatareassignedto thisI/Ogrouparenotcached;it issent directlytothestoragedevice.If bothnodesinanI/Ogroupgooffline,the virtualdisksthatareassignedtotheI/Ogroupcannotbeaccessed.
When avirtualdiskiscreated,theI/Ogroupthatwillprovideaccessto thevirtual diskmustbespecified.However, virtualdiskscanbecreatedandaddedtoI/O groupsthatcontainofflinenodes.I/Oaccesswillnotbepossibleuntil atleastone of thenodesintheI/Ogroupisonline.
Theclusteralso providesa recoveryI/Ogroup.Thisisused whenboth nodesin theI/Ogrouphave sufferedmultiplefailures.This allowsyouto movethevirtual disks totherecoveryI/Ogroupandtheninto aworkingI/Ogroup. I/Oaccessisnot possiblewhenvirtualdisksareassignedtotherecoveryI/Ogroup.
Relatedconcepts
“Input/Output(I/O)groups”onpage 15
AnI/Ogroupisagroup thatisdefinedduringtheclusterconfigurationprocess.
“Uninterruptiblepowersupplyoverview”onpage17
TheuninterruptiblepowersupplyprovidestheSANVolumeControllerwitha secondarypowersourceto beused ifyoulose powerfromyourprimarypower sourceduetopowerfailures,powersags,powersurges,or linenoise.
Power Cached data Node 1 Cached data Node 2 Vdisk A Vdisk B I/O Group UPS 1 UPS 2 2. Data 3. Data 4. Data 1. Data Prefered node path Alternative node paths Prefered node path Power
“I/OgroupsandUninterruptible PowerSupply”onpage 15
Nodesaredeployedinpairsto makeupacluster. Eachpairofnodesisknown asanI/Ogroup.Eachnodemaybeinonly oneI/Ogroup.
Uninterruptible
power
supply
overview
TheuninterruptiblepowersupplyprovidestheSANVolumeControllerwitha secondarypowersourceto beused ifyoulose powerfromyourprimarypower sourcedueto powerfailures, powersags,powersurges,orline noise.
If apoweroutageoccurs,theuninterruptiblepowersupplywillmaintainpowerlong enoughto saveany configurationandcachedatacontainedinthedynamicrandom accessmemory(DRAM).Thedatawillbesavedto theSANVolumeController internaldisk.Figure10providesavisual oftheuninterruptiblepowersupply.
Note: TheSANVolumeControlleruninterruptiblepowersupplyisanintegralpart
oftheSANVolumeControllersolution,andmaintainscontinuous SAN VolumeControllerspecificcommunicationswithitsattached SANVolume Controllernodes.TheSANVolumeControllerwillnotoperatewithout the uninterruptiblepowersupply.TheSANVolumeControlleruninterruptible powersupplymustbeusedinaccordancewithdocumentedguidelines and proceduresandmustnotpoweranyequipmentotherthanSANVolume Controllernodes.
Toprovidefullredundancy andconcurrentmaintenance,theSANVolumeController must beinstalledinpairs.EachSANVolumeControllerof apairmustbeconnected to adifferentuninterruptiblepowersupply.Eachuninterruptiblepowersupply can supportuptotwo SANVolumeControllernodes.Itisalso recommendedthatyou connect thetwouninterruptiblepowersupply unitsfor thepairto different
independent electricalpowersources.Thisreducesthechanceof aninput power failureat bothuninterruptiblepowersupply units.
Figure10.Uninterruptiblepowersupply
| |
