1、NetAppxV-SeriesSystemsInstallationRequirementsandReferenceGuideNetApp, Inc.495 East Java Drive Sunnyvale, CA 94089 U.S.Part number: 210-06053-A0April 2013Telephone:+1(408)822-60Fax:+1(408)822-4501Supporttelephone:+1(888)4-NETAPPWeb:Feedback:doccommentsContentsV-Seriestechnologyoverview7HowaV-Seriess
2、ystemusesdifferenttypesofstorage7SupportedmethodsforconnectingaV-Seriessystemtoastoragearray8NumberofstoragearrayssupportedbehindaV-Seriessystem8Sharingstoragearraysamonghosts9SupportforMetroClusterconfigurationswithV-Seriessystems9V-Seriesplanningoverview10WheretofindV-Seriesinteroperabilityandlimi
3、tsinformation10Limitsinformationforconfigurationswithstoragearrays10Interoperabilityinformationaboutsupportforstoragearrays1132xxsystemconfigurationrestrictions12StagesofimplementationforasystemusingarrayLUNs12PlanningsummaryforaV-Seriessystemusingnativedisks13PlanningsummaryforaV-Seriessystemusinga
4、rrayLUNs14PlanningforRAIDimplementation17RAIDprotectionforarrayLUNsI7ImplicationsofLUNsizeandnumberforDataONTAPRAIDgroups17PlanningforDataONTAPuseofarrayLUNs19HowarrayLUNsaremadeavailableforhostuse19HowarrayLUNsbecomeavailableforDataONTAPstorageuse20Considerationswhenplanningfordiskownership20ArrayL
5、UNassignmentchanges21ArrayLUNtypessupportedbyDataONTAP21FactorsthatimpactthenumberandsizeofarrayLUNsyouneed21FactorsimpactingthenumberofarrayLUNsneeded21MinimumnumberofarrayLUNsrequiredperV-Seriessystem22SparccorearrayLUNrequirementforcoredumps23MinimumandmaximumarrayLUNsizessupportedbyDataONTAP23Mi
6、nimumarrayLUNsizefortherootvolume24ElementsthatreducetheusablespaceinanarrayLUN24ConsideringchecksumtypewhenplanningarrayLUNsizeandnumber.251.ocationoftherootvolumeManningforLUNsecurityonthestoragearraysAvailableLUNsecuritymethods31PlanningforpathstoarrayLUNs33Requirementsforredundantsetupofcomponen
7、tsinapath33WhentocheckforredundantpathstoarrayLUNs34RequirednumberofpathstoanarrayLUN34AdvantagesoffourpathstoanarrayLUN(clusteredDataONTAP8.1andlater)35UsingLUNgroupstopartitiontheloadoverV-Seriesconnections35ImplementationrequirementsforamultipleLUNgroupconfiguration36Exampleofaconfigurationwithmu
8、ltipleLUNgroups37HowpathsarereflectedinarrayLLTNnames38ArrayLUNnameformat39HowthearrayLUNnamechangesinDataONTAPdisplays41Validpathing:stand-alonesystemwithasingle2-portarrayLUNgroup42Validpathing:asingle4-portarrayLUNgroupinafabric-attachedconfiguration43Planningaport-to-portconnectivityscheme45HowF
9、Cinitiatorportsarelabeled45RequirementsforV-SeriesFCinitiatorportusage46RulesforsharinganFCinitiatorportwithmultipletargetports47Exampleconfiguration:sharedFCinitiatorports48CheckingthenumberofarrayLUNsvisibleonanFCinitiatorport(clusteredDataONTAP)52Whattoincludeinaport-to-portplanforconnectingtosto
10、ragearrays53Whattoincludeinaport-to-portplanforconnectingtonativediskshelves54Zoningguidelines56Zoningrequirements56Zoningrecommendationforaconfigurationwithstoragearrays57Exampleofzoninginaconfigurationwithstoragearrays58DeterminingthearrayLUNsforspecificaggregates60Rulesformixingstorageinaggregate
11、sforV-Seriessystems60HowthechecksumtypeisdeterminedforaggregateswitharrayLUNs61CheckingthechecksumtypeofsparearrayLUNs62Aggregateruleswhenthestoragearraysarefromthesamefamily63Aggregateruleswhenthestoragearraysarefromdifferentvendorsorfamilies.64Determiningwhethertouseneighborhoods(7-Modein8.x)Whata
12、V-Seriesneighborhoodis67RequirementsforV-Seriesneighborhoods68PlanningthenumberofarrayLUNsanddisksinaneighborhood68Howtoestablishaneighborhood70CalculationofthevisiblelimitforbotharrayLUNsanddisks71ConnectingaV-Seriessystemtoastoragearray74Commandsforcheckingback-endconfiguration(clusteredDataONTAP8
13、1andlater)78Back-endconfigurationerrorsdetectedbythestorageerrorsshowcommand(clusteredDataONTAP8.1andlater)80Situationsnotidentifiedbythestorageerrorsshowcommand81Verifyinginstallationwithstoragearrays(clusteredDataONTAP8.1andlater)83Checkingforback-endconfigurationerrorspreventingsystemoperation(c
14、lusteredDataONTAP8.1andlater)85Thestorageerrorsshowmessagesandtheirresolution(clusteredDataONTAP8.1andlater)86ArrayLUNistoosmallortoolarge87LUNIDsforthesameLDEVdonotmatch88VolumeSetAddressingisinconsistent91DuplicateLUNIDsonatargetport93FewerthantwopathstoanarrayLUN96AnaccesscontrolLUNwaspresented99
15、AllpathstoanarrayLUNareonthesamestoragearraycontroller99ArrayLUNsareconfiguredwithconflictingfailovermodes(clusteredDataONTAP8.2andlater)102Checkingwhethertheconfigurationmatchesyourintentions(clusteredDataONTAP8.1andlater)104ReasonsforfewerarrayLUNgroupsthanexpected106ReasonsformorearrayLUNgroupsth
16、anexpected107ReasonsformorepathstoanarrayLUNthanexpected109ReasonsfortheincorrectnumberofLUNsinarrayLUNgroups110Reasonsstoragearraysaremissingfromcommandoutput111Verifyinganinstallationwithstoragearrays(7-Modein8.x)112112Checkingthenumberofpaths(7-Modein8.x)113,116 117 .117.118.120.120 .120 .122.126
17、127.128.128.129.130131133137Exampleoutputshowingcorrectandincorrectpathing(7-Modein8.x)Troubleshooting116GettingstartedwithtroubleshootingInvalidpathsetupexamplesInvalidpathsetup:toomanypathstoanarrayLUN(7-Mode)Invalidpathsetup:alternatepathsarenotconfiguredWhathappenswhenalinkfailureoccursRelation
18、shipbetweenzoningandhostgroupconfigurationDependencybetweenzoneandhostgroupdefinitionsExampleofcascadingzoningandhostgroupconfigurationerrors.Installationquickstart(7-Modeandstoragearraysonly)125Sampleconfigurationfortheinstallationquickstart(7-Modeandstoragearrays)125Performingpreinstallationtaskso
19、nthestoragearrayInstallingtheV-SeriessystemSettinguptheswitchesSettingupLUNsecurityAssigninganarrayLUNtoaV-Seriessystemandcreatingtherootvolume.InstallingDataONTAPandlicensesTestingyoursetupAdditionalsetupObtainingWWNsmanually134SettingsforconnectingtoanASCIIterminalconsole135Targetqueuedepthcustomi
20、zation137GuidelinesforspecifyingtheappropriatetargetqueuedepthSettingthetargetqueuedepth(clusteredDataONTAPpriorto8.2and7-Mode).138Settingthetargetqueuedepth(clusteredDataONTAP8.2)138Displayingtargetqueuedepthstatistics(clusteredDataONTAP8.2)139Terminologycomparisonbetweenstoragearrayvendors141Gloss
21、ary145CoPyrlghiInformat。n147Trademarkinformation148Howtosendyourcomments149Index150V-SeriestechnologyOVerVieWAV-Seriessystemisanopenstoragecontrollerthatvirtualizesstoragefromstoragearrayvendors,nativedisks,orbothintoasingleheterogeneousstoragepool.TheDataONTAPsoftwareprovidesaunifiedstoragesoftware
22、platformthatsimplifiesmanagingbothnativediskshelvesandLUNsonstoragearrays.Youcanaddstoragewhenandwhereyouneedit,withoutdisruption.HowaV-SeriessystemusesdifferenttypesofstorageAV-SeriessystemcanuseLUNsfromstoragearraysonly,nativedisksonly,orboth.AV-SeriessystemthatusesarrayLUNspoolstheLUNsfromstorage
23、arraysandservesdatatoWindowsandUNIXhostsandclients.Windows and UNIX HostsWindows and UNIX CIientsZHostsController Pooling and Virtualizing Heterogeneous StorageC=onRAIDStorageArraysAV-SeriessystempresentsstoragetoclientseitherintheformofDataONTAPfilesystemvolumes,whichyoumanageonthesystembyusingData
24、ONTPmanagementfeatures,orasaSCSItargetthatcreatesLUNsforusebyclients.Inbothcases(filesystemclientsandLUNclients),ontheV-SeriessystemyoucombinethearrayLUNsintooneormoreDataONTAPvolumesforpresentationtotheclientsasfilesorasLUNsservedbyDataONTAP.Likewise,youcancombinenativedisksintooneormoreDataONTAPvo
25、lumesftrpresentationtoclients.SupportedmethodsforconnectingaV-SeriessystemtoastoragearrayYoucanincorporateafabric-attachedconfigurationwithstoragearraysintoanexistingFCSANinfrastructure.Fabric-attachedconfigurationsaresupportedforbothstand-alonesystemsandHApairs.Direct-attachedconfigurationsarenotsu
26、pportedfornewdeployments.Forolderdeployments,direct-attachedconfigurationsarelimitedtosomestoragearraysandsomeDataONTAPreleases.TheInteroperabilityMcontainsinformationabouttheconnectionmethodssupportedforspecificstoragearraysandplatformsrunningDataONTAP.NumberofstoragearrayssupportedbehindaV-Seriess
27、ystemFormoststoragearrays,youcanconnectastand-aloneV-SeriessystemorthenodesinanHApairtomultiplestoragearrays.Forafewstoragearrays,youarelimitedtoonestoragearraybehindtheV-Seriessystem.TheInteroperabilityMatrixidentifiesthestoragearraysforwhichonlyonestoragearrayissupportedbehindtheV-Seriessystem.Ifm
28、ultiplestoragearraysbehindaV-Seriessystemaresupportedforyourstoragearray,therulesareasfollows: Thereisnolimittothenumberofstoragearraysyoucandeploybehindyoursystem.Thestoragearrayscanbefromthesamevendor,eitherallfromthesamefamilyorfromdifferentfamilies.Note:Storagearraysinthesamefamilysharethesamepe
29、rformanceandfailovercharacteristics.Forexample,membersofthesamefamilyallperformactive-activefailover,ortheyallperformactive-passivefailover.Morethanonefactormightbeusedtodeterminestoragearrayfamilies.Forexample,storagearrayswithdifferentarchitectureswouldbeindifferentfamilieseventhoughothercharacter
30、isticsmightbethesame.TheV-SeriesImplementationGuideforThird-PartyStoragecontainsinformationaboutthestoragearrayfamiliesforeachvendor. Thestoragearrayscanbefromdifferentvendors.RelatedconceptsRulesforsharinganFCinitiatorportwithmultipletargetportsonpage47RulesformixingstorageinaggregatesforV-Seriessy
31、stemsonpage60SharingstoragearraysamonghostsAtypicalstoragearrayprovidesstorageforhostsfromdifferentvendors.However,DataONTAPrequiressomestoragearraystobededicatedtoV-Seriessystems.TodeterminewhetheryourvendorsstoragearraymustbededicatedtoV-Seriessystems,seetheInteroperabilityMatrix.SupportforMetroCI
32、usterconfigurationswithV-SeriessystemsThetypeofsupportforMetroClusterconfigurationswithV-SeriessystemsdiffersaccordingtoDataONTAPrelease.InDataONTAPreleasespriorto8.2,supportforMetroClusterconfigurationswithV-Seriessystemsisasfollows: TheV-SeriessystemsmustuseonlyLUNsonstoragearrays(nonativedisks).T
33、heV-Seriessystemsmustbe7-Modesystems(notclusteredsystems).ThestoragearraysandV-SeriesmodelsmustbeidentifiedintheInteroperabilityMatrixasbeingsupportedinMetroClusterconfigurations.StartinginDataONTAP8.2,supportforMetroClusterconfigurationswithV-Seriessystemsisasfollows:AMetroClusterconfigurationwithV
34、Seriessystemscanincludenativedisksonly,LUNsonstoragearraysonly,orboth.SettingupaMetroClusterconfigurationwithV-SeriessystemsrequiresFibreBridge6500Nbridgesandthenativediskssupportedbythisbridge.Theserequirementsarethesameforfabric-attachedandstretchMetroClusterconfigurations.TheV-Seriessystemsmustb
35、e7-Modesystems(clusteredDataONTPisnotsupportedwithMetroClusterconfigurations).ThestoragearraysandV-SeriesmodelsmustbeidentifiedintheInteroperabilityMatrixasbeingsupportedinMetroClusterconfigurations.SeetheDataONTAPHighAvailabilityandMetroClusterConfigurationGuidefor7-Modeforinformationabouthowtoplan
36、forandsetupaMetroClusterconfigurationwithstoragearrays.IfyourMetroClusterconfigurationwithV-Seriessystemswillincludedisks,alsoseethedocumentConfiguringaMetroClustersystemwithSASdiskshelvesandFibreBridge65OONbridges.V-SeriesplanningoverviewSuccessfulimplementationofaV-Seriesdeploymentrequirescarefulp
37、lanningandverifyingproperinstallationandconfigurationofalldevicesinyourdeployment.RelatedconceptsPlanningforDataONTAPuseofarrayLUNsonpage19PlanningforLUNsecurityonthestoragearraysonpage31PlanningforpathstoarrayLUNsonpage33DetenniningthearrayLUNsforspecificaggregatesonpage60Planningaport-to-portconne
38、ctivityschemeonpage45WheretofindV-SeriesinteroperabilityandlimitsinformationWhenplanningyourconfiguration,youneedtochecksourcesinadditiontoproductdocumentationforinteroperabilitydetailsandlimitsinformation.ToolsavailableontheNetAppSupportSiteprovide,inacentrallocation,specificinformationaboutwhichfe
39、atures,configurations,andstoragearraymodelsaresupportedinparticularreleases.Relatedconcepts1.imitsinformationforconfigurationswithstoragearraysonpage10Interoperabilityinformationaboutsupportforstoragearraysonpage111.imitsinformationforconfigurationswithstoragearraysTheHardwareUniverse(formerlytheSys
40、temConfigurationGuide)TheHardwareUniverseincludesthefollowinglimitsthatdonotapplytonativedisks:MinimumandmaximumarrayLUNsizethatDataONTAPsupports,MinimumsizeforthearrayLUNfortherootvolumeSparecorearrayLUNminimumsize1.imitsforRAIDgroupswitharrayLUNsMinimumaggregatesizeforanaggregateofarrayLUNsMaximum
41、numberofarrayLUNsanddiskscombined,perplatformTheHardwareUniversealsocontainsstoragelimitsthatarethesamefornativedisksandarrayLUNs.Note:LimitsforV-SeriessystemswerepreviouslyprovidedintheV-SeriesLimitsReferenceforThird-PartyStorageandtheV-SeriesSupportMatrix.RelatedconceptsInteroperabilityinformation
42、aboutsupportforstoragearraysonpage11InteroperabilityinformationaboutsupportforstoragearraysNotallDataONTAPreleasessupportthesamefeatures,configurations,storagearraymodels,andV-Seriesmodels.Duringyourdeploymentplanning,youneedtocheckDataONTAPsupportinformationtoensurethatyourdeploymentconformstoDataO
43、NTAPhardwareandsoftwarerequirementsforallsystemsinthedeployment.PreviouslyallsupportinformationusedtosetupdeploymentswithstoragearrayswasincludedintheV-SeriesSupportMatrix.AsOfNovember2012,theinformationisdividedintotwodifferenttools,asshowninthefollowingtable:Forinformationabout.Youshouldlookhere.D
44、ataONTAPworkingwithdevices,includingInteroperabilityMthefollowing:Note:TheInteroperabilityMatrixshowsthe,SupportedstoragearraysandstoragearrayBrocadeandCiscoswitchesthatarefirmwaresupported.YoucanfindguidesforSupportedswitchesandswitchfirmwareconfiguringspecificvendorswitchesontheWhetheryourstoragea
45、rraysupportsnondisruptive(live)upgradeofthestoragearrayfirmwareWhetheraMetroClusterconfigurationissupportedwithyourstoragearrayNetAppSupportS.DataONTAPlimitsforreleasesandplatforms,HardwareUniverse(formerlytheSystemincludingthefollowing:ConfigurationGuide),MinimumandmaximumarrayLUNsizes,includingthe
46、minimumarrayLUNsizefortherootvolumeandsparecorearrayLUNsMinimumaggregatesizeforaggregateswitharrayLUNsSupportedblocksizeMinimumandmaximumcapacityNeighborhoodlimitsknowledgedocshardwareNetAppsyscfgindcx.shtmlForinformationabout.Youshouldlookhere.InformationaboutwhatissupportedforspecificV-SeriesImplementationGuideforThird-Partyarrays,includingsupportedcon
