EMCVNX SeriesRelease 7.0Getting Started with VNX Installation Assistant for File/UnifiedP/N 300-011-839REV A01EMC CorporationCorporate Headquarters:Hopkinton, MA 01748-91031-508-435-1000www.EMC.comCyghl 2011 - IMC Caln. A ghl eeed.Iubhed Iebuay 2011IMC beee lhe nmaln n lh ubaln auale a l ubaln dale. Thenmaln ub|el l hange vlhul nle.THI INIORMATION IN THIS IULICATION IS IROVIDID "AS IS." IMC CORIORATIONMAKIS NO RIIRISINTATIONS OR WARRANTIIS OI ANY KIND WITH RISIICT TOTHI INIORMATION IN THIS IULICATION, AND SIICIIICALLY DISCLAIMS IMILIIDWARRANTIIS OI MIRCHANTAILITY OR IITNISS IOR A IARTICULAR IURIOSI.Ue, yng, and dlbuln any IMC lvae debed n lh ubaln eue anaabe lvae ene.I lhe ml u-l-dale egualy dumenl yu dul ne, g l lhe TehnaDumenlaln and Ade eln n IMC Iven.I lhe ml u-l-dale lng IMC dul name, ee IMC Caln Tadema nIMC.m.A lhe ladema ued heen ae lhe ely lhe eele vne.Cale Headuale: Hnln, MA 01748-9103 Getting Started with VNX Installation Assistant for File/Unified 7.0ContentsPreface.....................................................................................................5Chapter 1: Introduction...........................................................................9Oeev................................................................................................................10Inleeablymalx.........................................................................................10Ieeule...........................................................................................................11Inla lhe VNX Inlaaln Alanl Ie/Uned....................................12VNX Inlaaln Alanl Ie/Uned nelv hel......................13Run lhe VNX Inlaaln Alanl Ie/Uned........................................14Whal Nexl`...................................................................................................15Chapter2:Troubleshooting..................................................................17IMC I-Lab Inleeably Nagal..............................................................18Knvn bem and mlaln.......................................................................18Allahng a CIIS hae a.......................................................................18Cannl elal lhe nlaaln VNXInlaaln Alanl Ie/Uned.............................................................................................18CIIS ee ealn a............................................................................19CIIS ee |n a....................................................................................19CIIS Wndv 2000 ee name englh elln..............................20VNX Inlaaln Alanl Ie/Uned a l melengualn..........................................................................................21VNX Inlaaln Alanl Ie/Uned en and VNXlvae en ae nl malbe...................................................23Dvnad DISKIART ully Wndv Vla...................................25SCSI LUN Allah a...............................................................................25MIIS enl ngualn n SCSI hl a.........................................26Getting Started with VNX Installation Assistant for File/Unified 7.0 MIIS a l add lhe Lnux hl..............................................................27Ibemelng.......................................................................................28Inng a.........................................................................................28Reume VNX Inlaaln Alanl Ie/Uned.............................28Sylem dened lage nl ealed.................................................29Uneeabe VNX Inlaaln Alanl Ie/Unede........................................................................................................29Change a aue el vlh lhe VNX Inlaaln Alanl Ie/Uned.......................................................................................................33IMC Tanng and Iena See...........................................................36Index.......................................................................................................39 Getting Started with VNX Installation Assistant for File/Unified 7.0ContentsPrefaceA ai an ci i nc an! cnnanc inc cnanc an! aa|ic i !ui nc,|MCc!aq ccac cn i na!uac an! iuac. Tnccc, nc unin !c|c!n in !uncni naq ni |c uic! |q a cn inc iuac na!uac ucniq n uc.| inc ni u-i-!aic nnain n !ui caiuc, cc i qu !ui ccac nic.| a !ui !c ni unin cq !c ni unin a !c|c! n in !uncni, cacniai qu |MC cccniaic.Getting Started with VNX Installation Assistant for File/Unified 7.0 5Special notice conventionsIMC ue lhe vng nenln ea nle:CAUTION: Aauln nlan nmaln eenla l addala damage l lhe ylem eumenl.Important: An mlanl nle nlan nmaln eenla l ealn lhe lvae.Note: A nle eenl nmaln lhal mlanl, bul nl hazad-ealed.Hint: A nle lhal de uggeled ade l ue, len nng v-n ally aalua aln.Where to get helpIMC ul, dul, and enng nmaln an be blaned a v:Idul nmaln I dumenlaln, eeae nle, lvae udale, nmalnabul IMCdul, enng, andee, g l lhe IMCOnne Sulveble (eglaln eued) al hll://Sul.IMC.m.Tubehlng G l lhe IMC Onne Sul veble. Ale ggng n, alelhe aabe Sul by Idul age.Tehna ul I lehna ul and ee euel, g l IMCCulmeSee n lhe IMC Onne Sul veble. Ale ggng n, ale lhe aabeSul by Idul age, and he elhe Live Chat Create a service request. Ten a ee euel lhugh IMC Onne Sul, yu mul hae a ad ulageemenl. Cnlal yu IMCae eeenlale dela abul blanng a adul ageemenl vlh ueln abul yu aunl.Note: D nl euel a e ul eeenlale une ne ha aeady been agned lyu alua ylem bem.Your commentsYu uggeln v he u nlnue l me lhe auay, ganzaln, and eaualy lhe ue ubaln.Ieae end yu nn lh dumenl l:6 Getting Started with VNX Installation Assistant for File/Unified 7.0Prefacetechpubcomments@EMC.comGetting Started with VNX Installation Assistant for File/Unified 7.0 7Preface8 Getting Started with VNX Installation Assistant for File/Unified 7.0Preface1IntroductionIMC VNX Inlaaln Alanl Ie/Uned a land-ane vzadlhal ndale mule unln eued nlaaln.Th dumenl al lhe VNXnmaln el and nlended uevh vanl l ngue and manage VNX ung lhe VNX InlaalnAlanl Ie/Uned.T nuded ae:xOeev n age 10xInleeably malx n age 10xIeeule n age 11xInla lhe VNX Inlaaln Alanl Ie/Uned n age 12xVNXInlaaln Alanl Ie/Unednelv hel n age13xRun lhe VNX Inlaaln Alanl Ie/Uned n age 14Getting Started with VNX Installation Assistant for File/Unified 7.0 9OverviewThe IMC VNXInlaaln Alanl Ie/Uned a land-ane vzad lhalndale mule unln eued nlaaln, uh a VNX dey andnlazaln, healh he, ngualn Cnl Slaln and bade, and duleglaln. Th vzad ha been exlended l nude a me nleae aungualn la l el u lhe VNX duln. The VNX Inlaaln Alanl Ie/Unednude a me nleae l nunuedd, ngue NIS, andCIIS,and el u MIIS lage ( MIIS-uled ylem ny).Note: I yu vanl l ngue lhe II6 addee lhe Cnl Slaln (Cnl Slaln adde,DNS, NTI) lhe Dala Me (DNS NTI) ue VNX Inlaaln Alanl Ie/Uned lhe nla nlaaln and lhen ee l Cngung an! Managng Nciung n VNX lehnamdue and |MC VNX Cnnan! Inc |nicac |cccnc |c l mele lhe II6 addln.C Inla l em ba ylem elu a aly nlaed (unngued) VNX:xVNX dey and nlazalnxHealh hexCngualn Cnl Slaln and badexCngue CnnelHme e-ma ulC Cngue l:xIn lage ung exe and ulm mdexCeale ba and hghy aaabe nelv deexCeale and allah CIIS haexCeale NIS exlxSel u MIISNote: Th ln aaabe ny MIIS-uled ylem. Seel lh ln ny yu vanll un MIIS and lhe MIIS nalulue ngued n yu ylem n adane. Ree l |MCVNX MP|S c |C an! SCS| 6.0 Inux Ccni P!ui Gu!c l manuay ngue MIIS.Interoperability matrixTabe 1 n age 11 eale lhe VNX vlh lhe eele VNX OI Ie en, CenlOS, and VNX Inlaaln Alanl Ie/Uned en.10 Getting Started with VNX Installation Assistant for File/Unified 7.0IntroductionTable 1. Interoperability matrixVNX Installation Assistantfor File/Unified versionClient OS VNX OE for File VNX hardware7.0.10.3 or later Windows XP, 2000, Vista 7.0.10.3 or later VNX53007.0.10.3 or later Windows XP, 2000, Vista 7.0.10.3 or later VNX55007.0.10.3 or later Windows XP, 2000, Vista 7.0.10.3 or later VNX57007.0.10.3 or later Windows XP, 2000, Vista 7.0.10.3 or later VNX7500Note: The VNX Inlaaln Alanl Ie/Uned vzad de nl un n NT4 ee.PrerequisitesTabe 2 n age 11 l lhe eeule lhe VNX Inlaaln Alanl Ie/Uned.Table 2. Prerequisites for different wizards in VNX Installation AssistantPrerequisites Operating system WizardxDisplay settings must have a minimum of 256colors (for Windows NT and Windows 2000).Windows XP/2000/Vista Storage ProvisioningxProper communication channel between the VNX,the interfaces, and the client must exist.Windows XP/2000/Vista Network ConfigurationxVNX must be provisioned to get the pool size.xInterfaces must be available to attach a share tothe client.xProper communication channel between the VNX,the interfaces, and the client must exist.xRespective domain controllers and their creden-tials must be available to create and join the CIFSserver, and to attach the CIFS share to the client.Windows XP/2000/Vista CIFSxVNX must be provisioned to get the pool size.xInterfaces must be available to attach a share tothe client.xProper communication channel between the VNX,the interfaces, and the client must exist.Windows XP/2000/Vista NFSPrerequisites 11IntroductionTable 2. Prerequisites for different wizards in VNX Installation Assistant (continued)Prerequisites Operating system WizardxVNX must be provisioned so that at least fourLUNs with the same size to be in one of the sys-tem defined pool: clar_r5_performance, clar_r6,or clar_r10.xInterfaces must be available to attach a share tothe client.xProper communication channel between the VNX,the interfaces, the computer running VNX Instal-lation Assistant for File/Unified, and MPFS Linuxhosts must exist.xFor Fibre Channel configuration, the HBA drivermust be installed on the client, and the HBA mustbe configured to connect to the fabric-connectedVNX system.xFor iSCSI configuration, the iSCSI package mustbe installed on the client.Windows XP/2000/Vista MPFSInstall the VNX Installation Assistant for File/Unifiedee nlang lhe VNX Inlaaln Alanl Ie/Uned, ey lhal:xAe l lhe IMC Onne Sul veble al hll://Sul.IMC.m lhe VNXInlaaln Tbx CD (eeed) aaabe.xWndv-baedenl mule n lhe ame ubnel (ulme nelv) a lhe CnlSlaln.xThe mule mul hae al eal 150 M ee ae. Inlenel nnelly emmended.T blan and nla lhe VNX Inlaaln Alanl Ie/Uned:Note: On yu mule, dabe any eva lvae, -u be, lua ale nelv(VIN) nleae, and VMvae nelv nleae bee unnng lhe VNX Inlaaln Alanl Ie/Uned.1. Dvnad lhe VNX Inlaaln Alanl Ie/Uned m a n n lhe Tools age lhe IMC Onne Sul veble. I yu d nl hae ae l lhe veble, nel lheVNX Inlaaln Tbx CD nl yu mule.2. In lhe Getting Started with your EMC VNX Installation vndv, VNX InstallationAssistant for File/Unified l nla lhe VNXInlaaln Alanl Ie/Uned n yumule. Igue 1 n age 13 hv lhe nlaaln e VNX InlaalnAlanl Ie/Uned m VNX Inlaaln Tbx CD.12 Getting Started with VNX Installation Assistant for File/Unified 7.0IntroductionThis CD contains the intellectual property ofEMC Corporation or is licensed to EMC Corporationfrom third parties. Use of this CD and the intellectualproperty contained herein is expressly limited to theterms and conditions of the License Agreement.EMC Cel erra NS40 SystemTutori alCDCSA Instal l ati onP/N nnn-nnn-nnn-A0nCopyri ght 2nnn EMC Corporati onAl lRi ghts ReservedNetworkVNX-000065Load VNX Installation Toolbox CD in either a laptop or PC tower.Figure 1. Installing VNX Installation Assistant for File/UnifiedThe IMC Onne Sul veble al hll://Sul.IMC.m de me nmaln.VNX Installation Assistant for File/Unified network checklistee yu un lhe VNX Inlaaln Alanl Ie/Uned, enue lhal:1. Yu VNX veed u. The nlaaln gude de addlna nmaln.2. Yu VNX nneled l lhe nelv. The nlaaln gude de addlnanmaln.3. Yu VNX and yu Wndv enl ae n lhe ame hya LAN.4. Any exlng eva, -u be, and VIN ae dabed.5. C Seuly agenl luned n lhe enl IC.6. I lhe VNX Inlaaln Alanl Ie/Uned annl delel lhe MAC adde lheCnl Slaln, enue lhal yu eel lhe el LAN nelv nleae ad n vhhyu vanl l eah lhe Cnl Slaln.7. I lhe VNX Inlaaln Alanl Ie/Uned annl delel lhe MAC adde lheCnl Slaln, ve ye lhe Cnl Slaln and Retry Search.Note: Il lae eea mnule l ebl lhe Cnl Slaln. Yu an ng lhe II adde lheCnl Slaln l mae ue lhe Cnl Slaln ebled bee yu nlnue.8. I lhe Cnl Slaln l de nl end, ue lhe ued -e abe (I/N038-003-457 and abeed See LAN Cabe Aemby) l nnel l lhe Cnl SlalnVNX Installation Assistant for File/Unified network checklist 13Introductiondely m lhe enl IC unnng lhe VNX Inlaaln Alanl Ie/Uned, andem lhe vng:a. Dnnel lhe exlena nelv abe l lhe Cnl Slaln. Th abe abeedMGMT, a hvn n lhe vng gue.b. Cngue lhe Wndv enl vlh a lal II adde n lhe ame ga nelvbeng ued by lhe Cnl Slaln, ung a nelma 255.255.255.0, and n deaulgalevay adde.. Ue a laghl-lhugh ( e) Ilhenel abe l nnel lhe VNX InlaalnAlanl Ie/Uned enl dely l lhe exlena l n lhe Cnl Slaln(abeed a "elh3"), a hvn n lhe vng gue.d. Mae ue l dabe vee mmunaln, any eva lvae, -u be,VIN nleae, and VMvae nelv nleae.e. Rebl lhe Cnl Slaln and val lhe ebl l mele.. Relal lhe VNX Inlaaln Alanl Ie/Uned vzad and Next n lheWelcome age l nlale lhe badal and dey e, lhen nlnue vlh lheVNX Inlaaln Alanl Ie/Uned ngualn.Run the VNX Installation Assistant for File/UnifiedT un lhe VNX Inlaaln Alanl Ie/Uned:1. Dube- lhe VNX Installation Assistant for File/Unified hlul n lhe del gl C:(IgamIe(IMC(VNX Inlaaln Alanl(lalu(aunh.bal. The VNXInlaaln Alanl Ie/Uned gude yu lhugh lhe emanng le.2. C Install l ngue a aly nlaed VNX.3. Inue l egle yu ylemung lhe VNXInlaaln Alanl Ie/Uned alelhe nla ylem nlaaln and engualn ha been meled.4. C Configure l n lage and elu lhe VNX duln.14 Getting Started with VNX Installation Assistant for File/Unified 7.0Introduction5. G l IMC Onne Sul veble al hll://Sul.IMC.m me nmaln.Al lhe end eah ngualn, yu ylem v be uabe and eady duln.Ale yu egle yu VNX ylem, yu mul ngue lhe ylem duln. Theeae eea mmn memenlaln aaabe lhugh lhe VNX Inlaaln Alanl, yu an ngue yu ylem by ung lhe IMC Unheelvae.Cmmn memenlaln:xCeale CIIS haexCeale NIS exlxSel u MIIS ( MIIS-uled ylem)xIem mmn l-VNX Inlaaln Alanl laNote: On a Wndv Vla ylem, yu need l ue CIIS vzad, yu mul dabe Ue AeCnl.The IMC Onne Sul veble al hll://Sul.IMC.m de me nmaln.What Next?Yu ae nv eady l d lhe vng:xInla and ngue IMCSeue Remle Sul (ISRS) II Cenl. Ue lhe Initialize andregister VNX and configure ESRS n unde VNX la and be ue l eel lhe ISRSln vhen mled.xAllah ne me ee l yu VNX. Ue lhe Attach server n unde See lan lhe ul veble l geneale le-by-le nluln allahng a ee.Run the VNX Installation Assistant for File/Unified 15Introduction16 Getting Started with VNX Installation Assistant for File/Unified 7.0Introduction2TroubleshootingA al an el l nlnuuy me andenhane lhe emaneandaable l dul ne, IMCeday eeae neven l hadvae and lvae. Theee, me unln debed n lhdumenl may nl be uled by a en lhe lvae hadvae uenly n ue. I lhe ml u-l-dale nmaln n dulealue, ee l yu dul eeae nle.I a dul de nl unln ey de nl unln a debedn lh dumenl, nlal yu IMC Culme Sul Reeenlale.P|cn|cuin |a!na VNXnlan addlna nmaln abulung lhe IMC Onne Sul veble and eng bem.T nuded ae:xIMC I-Lab Inleeably Nagal n age 18xKnvn bem and mlaln n age 18xChange a aue el vlh lhe VNX Inlaaln Alanl Ie/Uned n age 33xIMC Tanng and Iena See n age 36Getting Started with VNX Installation Assistant for File/Unified 7.0 17EMC E-Lab Interoperability NavigatorThe IMC I-Lab Inleeably Nagal a eahabe, veb-baed aaln lhalde ae l IMC nleeably ul male. Il aaabe alhll://Sul.IMC.m. Ale ggng n l lhe IMC Onne Sul veble, ale lheaabe Sul by Idul age, nd Tools, and E-Lab Interoperability Navigator.Known problems and limitationsTh eln l lhe nvn bem and mlaln lhe VNX Inlaaln Alanl Ie/Uned.Attaching a CIFS share failsAttaching a CIFS share may fail when not using the first primary blade. SymptomVNX Installation Assistant for File/Unified only sets up the DNS for the first primary blade. CauseUnisphere can be used to set up the DNS on the other primary blades for VNX Installation Assistantfor File/Unified previously known as Celerra Startup Assistant (CSA) versions 5.6.39 to 5.6.46.VNX Installation Assistant for File/Unified extends multiple blade support for version 5.6.47 andlater.SolutionCannot restart the installation for VNX Installation Assistant for File/UnifiedCannot restart the installation for VNX Installation Assistant after exiting, before the cable checkis passed. NAS services are unavailable and attempts to access Unisphere and the NAS CLI di-rectly do not work. (Linux CLI is accessible.)SymptomThe VNX Installation Assistant for File/Unified mode on the Control Station is disabled before thecable check completed successfully and NAS services are not available. This condition can occurif a Shift + L is executed before the cable check completes.CauseLog in as root on the Control Station and at the command line, type: Solutionservice nas start18 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingCIFS server creation failsCIFS server creation fails because the CIFS server join with the domain fails. SymptomOne possible reason can be that the default gateway is not set up for a blade. CauseSet up a default gateway before using the CIFS server create and attach: Solution1. Check if the Data Mover has any interfaces. If not, create an interface on the network for whichyou need to set up the default gateway.2. When the interface is created, run the CLI command:$ server_route server_2 -add default where: = name of the default gateway address.Note:Contact your network administrator to get the default gateway address to use in the serv-er_route command.For example, if you are setting up a default gateway for network range 10.26.125.xxx, create aninterface 10.26.125.99, then type:$ server_route server_ 2 -add default 10.26.125.1where:1 = the gateway address.To verify that the default gateway was added, type:$ server_route server_2 -1CIFS server join failsCIFS server join fails if there is clock skew between the Data Mover and the domain controllers. SymptomThe NTP server synchronizes the timestamp between the Data Mover and the domain controllers.VNX Installation Assistant for File/Unified does not provide an option to add an NTP server to thedomain controller.CauseKnown problems and limitations 19TroubleshootingSolution x Create an NTP server for the Data Mover from the Unisphere. This option is available on theData Mover properties screen. The NTP server field accepts comma separated multiple NTPservers. When you click the Apply button, the NTP server with the given IP address points tothe Data Mover.x Another option is available through the CLI command. Use the modify command on the DataMover object for property ntpServer.CIFS Windows 2000 server name length restrictionCIFS Windows 2000 server name cannot be greater than 15 characters, even though Windows2000 Active Directory accepts up to 63 characters.SymptomIn the VNX Installation Assistant for File/Unified, the same field is used to define the CIFS servername and the NetBIOS name (compname). Therefore, if the CIFS server name is greater than 15characters, a failure occurs because the NetBIOS name (compname) cannot be greater than 15characters.CauseWindows 2000 servers with names greater than 15 characters can be created by using Unisphere.In Unisphere, go to the CIFS share option. This screen accepts server names up to 63 characters.Solution20 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingVNX Installation Assistant for File/Unified fails to complete configurationSymptom x VNX Installation Assistant for File/Unified fails to complete the configuration of SP IP addressesduring pre-configuration and displays the error message:Could not change IP address of the SP.x VNX Installation Assistant for File/Unified fails to apply the pre-configuration changes anddisplays the error:Backend IP setup | Could not change IP address of the SPCSA startup_wiz.log: ERROR 2008-06-06 16:15:12,233[com.emc.celerra.startup.configuration.BaseSetup]:Backendip config (start) failed with retcode : 30 and errormessageWARN 2008-06-06 16:15:12,233[com.emc.celerra.startup.configuration.BaseSetup]: Therewere warnings or errors while configuring backend :severity :4 andmessages : Could not change IP address of the SP NetworkSettings on CSA client:10.113.0.190255.255.255.010.113.254.254The gateway address that was entered during pre-configuration is invalid for communication be-tween the VNX Installation Assistant for File/Unified client and the Control Station. Instead, thegateway address should be changed to match the same network as that of the Control Stationand the VNX Installation Assistant for File/Unified client during the VNX Installation Assistant forFile/Unified configuration work [10.113.x gateway vs. 10.113.x.x gateway]. In this case, the VNXInstallation Assistant for File/Unified application fails during the pre-configuration apply phasewhere the IP addresses are being configured by the VNX Installation Assistant for File/Unifiedwizard because the default gateway IP address is 10.113.254.254.CauseKnown problems and limitations 21TroubleshootingSolution1. Preferred workaround:a. With the VNX Installation Assistant application open at the point of failure, log in to theControl Station as root and set a new default gateway:# /sbin/route add -net default gw 10.113.0.1b. Verify that SPA's IP address was changed and not SPB:# /nas/sbin/navicli -h networkadmin -getshould be set to a new IP address.# /nas/sbin/navicli -h networkadmin -getshould still be set with an internal IP address.c. Return SPA to the default Internal IP address and gateway:# /nas/sbin/navicli -h networkadmin -set -address128.221.252.200 -gateway 128.221.252.104d. After SPA reboots, check and restore any tresspassed LUNs:# /nas/sbin/navicli -h 128.221.252.200 getlun -trespass# /nas/sbin/navicli -h 128.221.252.200 trespass lun xe. Edit /etc/hosts and /nas/site/sp_info files to reflect the correct internal IP address for SPA.f. Verify network admin information on SPs once again.g. Click the Back button in the VNX Installation Assistant for File/Unified to return to thescreen where the gateway address was shown. Edit the address to 10.113.0.1, thencontinue by using the VNX Installation Assistant for File/Unified to complete the installation:10.113.0.1Note:If the VNX Installation Assistant application was closed, locate and edit the C:\ProgramFiles\EMC\CSA\startup\test\CSA_xxxx.xml file to reflect the new gateway address. Restartthe VNX Installation Assistant, select the MAC address of the current Control Station, providethe login information, and continue using the VNX Installation Assistant for File/Unified tocomplete the installation.2. Alternative workaround:a. Connect the VNX Installation Assistant for File/Unified client directly to the Control Stationby using a LAN cable.b. Reconfigure the default gateway IP on the Windows client to something like 10.113.0.1.c. Remove the VNX Installation Assistant for File/Unified configuration (Primus article emc166265 provides more information) to get the Control Station back to a pre-VNX Installation22 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingAssistant for File/Unified configured state.d. Rerun the VNX Installation Assistant process.VNX Installation Assistant for File/Unified version and VNX software versionare not compatibleCSA dislays a pop-up after you select the MAC address:Note: VNX Installation Assistant for File/Unified was formerly known as Celerra Startup Assistant(CSA).This version of CSA (5.x.xx) is not compatible with theCelerra Software version (5.x.xx-x) installed on the systemyou are trying to initialize.SymptomThe CSA version and the Celerra Software version are not compatible. CauseThe VNX Installation Assistant for File/Unified wizard is available on the VNX Installation ToolboxCD for all new installations, while several versions are also available for downloading from theEMC Online Support website. When determining compatibility between CSA and NAS versions,use only the first three fields of the NAS version. Also, note:x The CSA cannot install multiple versions of the wizard on a given client.x You cannot upgrade from one version of the CSA to another.x To upgrade, uninstall the existing CSA application and then install the new CSA version.Be aware that CSA versions 5.5.30 and 5.5.31 do not perform version-checking, which means thatthe wizard would attempt to configure the system during installation. If an incompatible CSA-to-NAS version is used, the Celerra configuration may not complete successfully and may requiretechnical support intervention to repair. CSA versions 5.5.32 and later are supposed to check theNAS version for compatibility before allowing the user to continue with the configuration process,but due to various changes, later released versions of CSA will not always be able to support olderNAS versions for configuration purposes. Review the following compatibility information.The CSA wizard when introduced supported factory pre-configured NS20 and NS40 installations.CSA now supports the NX4 Celerra model, and this support will be expanded to future Celerramodel releases. The following compatibility statements can be made at this time.SolutionKnown problems and limitations 23TroubleshootingNAS 5.5 family:x CSA 5.5.30 is compatible with NAS version 5.5.30 only, and not with any other NAS versions(CSA implements the NAT solution as the default).x CSA 5.5.31 is compatible with NAS version 5.5.31 only, and not with any other NAS versions(CSA implements the proxy ARP solution as the new default).x CSA 5.5.32 is compatible with NAS versions 5.5.31 and 5.5.32, and has version-checking builtinto the wizard (CSA 5.5.32 will indicate by using a pop-up when the Celerra version is notcompatible, such as with any NAS version prior to 5.5.31 or after 5.5.32).x CSA 5.5.33 is compatible with NAS versions 5.5.33, 5.5.32, and 5.5.31, and fails with a versionnot compatible message if used on NAS versions greater than 5.5.33.Note: There is no CSA version for NAS versions 5.5.34, 5.5.35, or 5.5.36.x CSA 5.5.37 is compatible with NAS versions 5.5.37, 5.5.36, 5.5.35, and 5.5.34.NAS 5.6 family:x CSA 5.6.36 is compatible with NAS versions 5.6.36 only, and not with any other NAS versions(provides pop-up message).x CSA 5.6.37 is compatible with NAS versions 5.6.37 only, and not with any other NAS versions(no compatibility pop-up when used on NAS 5.6.36 configuration, but does not work due to aproblem).Note:Due to potential CSA hang issue during pre-configuration apply changes screen, useCSA version 5.6.38 with NAS 5.6.37 installs. Primus article emc 193170 provides details ofthe 5.6.37 CSA issue.x CSA 5.6.38 is compatible with NAS versions 5.6.38, 5.6.37, and 5.6.36, and is the currentlyrecommended CSA version to use with these NAS versions.CAUTION: Do not use the 5.6.38 CSA from the CD. Use only the "revised" 5.6.38CSA, downloadable from the EMC Online Support website. The CSA version 5.6.38on EMC Online Support has been modified to correct a problem found with the CableCheck process that prevents successful configuration.24 Getting Started with VNX Installation Assistant for File/Unified 7.0Troubleshootingx CSA 5.6.39 is compatible with NAS version 5.6.39 only, and not with any other previous NASversions. (CSA implements ConnectHome and email User configuration screen option.)x CSA 5.6.40 is compatible with NAS versions 5.6.40 and 5.6.39. (Partial testing indicates CSAis backwards compatible with 5.6.39 NAS version.)x CSA 5.6.41 is compatible with NAS versions 5.6.41, 5.6.40, and 5.6.39. (Partial testing indicatesCSA is backwards compatible with 5.6.40 and 5.6.39 NAS versions.)x CSA 5.6.42 is compatible with NAS versions 5.6.42, 5.6.41, 5.6.40, and 5.6.39. (Partial testingindicates CSA is backwards compatible with 5.6.41, 5.6.40, and 5.6.39 NAS versions.)Download DISKPART utility for Windows VistaWhen attaching an iSCSI LUN to the local computer on Windows Vista, it prompts to downloadthe DISKPART utility even though the utility is already installed. When checked by using theWindows command line, the directory for DISKPART exists and is installed.Symptomx The user account control is enabled on the Windows Vista computer.x The VNX Installation Assistant for File/Unified will not be able to find the DISKPART utilitystatus and the user will get a pop-up in iSCSI create and attach page regarding DISKPARTinstallation.CauseSolution1. On Windows Vista, click Start and go to the Control Panel, then click User Accounts.2. On the Make changes to your user account page, click the Turn User Account Control on or offlink.3. On the Turn on User Account Control (UAC) to make your computer more secure option, clearthe Use User Account Control (UAC) to help protect your computer checkbox and click OK.4. Restart your computer and retry attaching an iSCSI LUN to the local computer from VNX In-stallation Assistant for File/Unified.iSCSI LUN Attach failsWhile creating a new iSCSI LUN and attaching it to a local host, the iSCSI attach fails with anerror message :Disk not foundSymptomThe operating system of the host does not support dynamic search of iSCSI LUN and needs areboot to detect the new iSCSI LUN.CauseKnown problems and limitations 25TroubleshootingSolution1. Close all the applications and reboot the host.2. Launch the VNX Installation Assistant for File/Unified and log in to your VNX.3. On the Configuration wizards page, select Create/Attach iSCSI LUN.4. On the iSCSI Create and Attach page, select Attach a host to an existing iSCSI LUN.5. On Attach an iSCSI LUN page, select Local Host.6. Select the blade name for the iSCSI Target from the available list.7. Select all other fields appropriately and click Next to attach the iSCSI LUN successfully.iSCSI LUN attach fails on the Windows 2008 client machine with an error message:DiskPart has encountered an error: The Media is writeprotectedSymptomThe default SAN policy on the Windows 2008 client machine is not set to VDS_SP_ONLINE. TheSAN policy on the Windows 2008 restricts all the iSCSI LUNs to be read only.CauseSolution1. Before working on the Windows 2008 client machine, go to command prompt, type diskpart,and then press Enter.2. On the DISKPART prompt, type SAN and press Enter to see the current SAN policy on themachine.3. If Online All is displayed then iSCSI LUN create and attach will work as desired on the VNXInstallation Assistant for File/Unified.4. If Offline Shared is displayed then type the following command in the command prompt to ac-tivate the VDS_SP_ONLINE policy: SAN POLICY = OnlineAll. This policy will make all theiSCSI LUNs online with read-write options.5. You can launch the VNX Installation Assistant for File/Unified and select the Create/AttachiSCSI LUN to create and attach iSCSI LUN on Windows 2008 successfully.MPFS client configuration on iSCSI host failsMPFS fails to complete the MPFS client configuration on iSCSI host. SymptomThe iSCSI service is not running on the host, or the local mount directory to create is undera read-only directory.Cause26 Getting Started with VNX Installation Assistant for File/Unified 7.0Troubleshooting1. Run the iSCSI status command to check if the iSCSI service is running. If the iSCSIservice is not running, start the iSCSI service by running iSCSI start command.2. If MPFS cannot create the local mount directory, then the user can go back to the MPFS-enabled NFS Mount screen and select the host from the host navigation tree to displaythe mount selection on the Export to the Mount field.3. Remove the export from the specified local mount directory, if it is under a read-only di-rectory and specify a different local mount directory for the MPFS export to mount.SolutionMPFS fails to add the Linux hostMPFS fails to add the Linux host, an error appears: SymptomMPFS does not support the kernel of this hostThe MPFS client software does not support the kernel of this host. CauseThe MPFS client support matrix is listed in the file host_support.properties, which is under\startup\mpfs.SolutionThe format of the support host value is OSname-KernelVersion-CpuType. The user canget the hosts operating system, kernel version, and CPU type information by runningthe following command:uname -m;uname -n;uname -r;uname -sIf the host kernel is not on the MPFS client support matrix, the user needs to install akernel which is supported by MPFS.MPFS wizard fails to log in to the Linux hosts. SymptomUsername or password is not correct, or the default SSH server installations are config-ured to refuse the authentication password.CauseSolution1. Type the correct username and password on the MPFS Add Hosts page, and addthe hosts again.2. If the login still fails, then the default SSH server installations may be configured todecline the authentication type password.3. Edit the /etc/ssh/sshd_config and change the value of PasswordAuthentication toyes, then restart the SSH daemon to re-read this configuration. For example, run:/etc/init.d/sshd restartKnown problems and limitations 27TroubleshootingProblem reportingCSA fails to complete successfully. SymptomUnknown. CauseWhen reporting problems with CSA that require escalation to the Engineering team, aRemedy AR should be opened and the following data should be collected:From the client PC:x Log file from C:\Program Files\EMC\CSA\startup\startup_wiz.log file.x All the contents of directory C:\Program Files\EMC\CSA\startup\test.x Run the command ipconfig/all for IP issues.From the Celerra Control Station, collect all the information retrieved by the collect_sup-port_materials script.SolutionProvisioning failsProvisioning fails with an error:Unable to establish communication with SymptomThe connectivity between the EMC VNX for Block system and the Control Station is lost. CauseCheck the cable connection between VNX for Block system and Control Station. SolutionResume VNX Installation Assistant for File/UnifiedOn the Welcome screen, user is prompted: SymptomEnter the password for this VNXIf the user runs VNX Installation Assistant for File/Unified, but cancels the execution prior tocompleting all the steps, a configuration file is created that allows the user to resume the VNXInstallation Assistant for File/Unified from the point where it was discontinued.Cause28 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingWhen the VNX Installation Assistant for File/Unified is run, it creates a VNX system specificconfiguration file (C:\Program Files\EMC\CSA\startup\test\CSA_nnnnnnnnnnnn.xml).SolutionTo run VNX Installation Assistant for File/Unified again from the same Windows workstation,but to set up a different VNX system on the Welcome to VNX Installation Assistant for File/Unifiedscreen, select the box in the lower-left side of the screen next to Select if you want to create anew configuration profile.Note: VNX Installation Assiatant for File/Unified was previously known as Celerra StartupAssistant (CSA).Beginning with CSA version 5.5.32, there is a new page during the welcome phase which allowsthe user to select either a new configuration or the MAC address of an existing installationfrom the following menu:WelcomeSelect configuration profileSelect a profile using this MAC address: New Configuration

System defined storage pool not createdOn the MPFS System and Configuration page, the user is prompted:To create MPFS storage pool, at least four LUNs with thesame size are required to be in one of the system definedpools:clar_r5_performance, clar_r6, or clar_r10SymptomMPFS needs to create MPFS storage pools from the system defined pools clar_r5_performance,clar_r6, or clar_r10 for the MPFS initialization.CauseSelect Provision unused disks on the Configurations wizards page to create at least one systemdefined storage pool that includes at least four LUNs in the pool: clar_r5_performance, clar_r6, orclar_r10.SolutionUnrecoverable VNX Installation Assistant for File/Unified errorsUnrecoverable VNX Installation Assistant for File/Unified errors that prevent completion of VNXInstallation Assistant for File/Unified configuration process.SymptomKnown problems and limitations 29TroubleshootingInadvertent mistakes made during VNX Installation Assistant for File/Unified configuration thatneed to be reversed.Cause30 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingPerform the following steps to set the VNX system and Control Station back to a pre-VNX Instal-lation Assistant for File/Unified state.CAUTION: If the system is in a misconfigured or partially configured state, the followingsteps may not work and a more intensive manual cleanup would be required, as indicatedin the notes below.Solution1. Run the following command to stop the NAT or Proxy_ARP configuration:# /nasmcd/sbin/clariion_mgmt stopUse clariion_mgmt -info to determine if NAT or Proxy-ARP is configured. If the command returnsError 12: Not configured, then the clariion_mgmt -stop command does not need to be run.In some situations, the NAT or Proxy-ARP configuration may fail to be torn down completelyby the -stop switch. If so, use the clariion_mgmt -stop -skip_rules command, then manuallyedit the /etc/hosts and /nas/site/sp_info to restore the default 192.168.x (or 128.221.x) IP ad-dresses for the SPs, remove the /nas/site/clariion_mgmt.cfg file (if it exists), then reboot theControl Station.Finally, you should check the actual IP addresses running on the SPs and change them backto the default VNX values (128.221.252.200/128.221.253.201) by using navicli -h net-workadmin -set -address xxx by the -stop switch. If so, use the clariion_mgmt -stop -skip_rulescommand, then manually edit the /etc/hosts and /nas/site/sp_info to restore the default192.168.x (or 128.221.x) IP addresses for the SPs, remove the /nas/site/clariion_mgmt.cfgfile (if it exists), then reboot the Control Station. Finally, you should check the actual IP ad-dresses running on the SPs and change them back to the default VNX values xxxx -gatewayxxx.xxx or if necessary by using direct connection to the SP LAN port and /setup program.The Primus article, emc176667 - Troubleshooting failed Proxy-ARP conversions, providesmore information.2. Copy the S95cable_check script to /etc/rc3.d and chmod the file to make it executable byusing the chmod 755 S95cable_check command.Note: The challenge here is that the VNX Installation Assistant for File/Unified process deletesthe S95cable_check file. If a copy has not been previously saved, mount a similar version ofthe NAS CD-ROM and copy the S95cable_check script from the /EMC/nas directory to the/etc/rc3.d directory. If a copy cannot be downloaded, contact the EMC Support and referencethe NAS version involved.3. Remove the /tmp/.factory_check_successful file if it exists. Existence of the file preventsproper completion of the VNX Installation Assistant for File/Unified configuration process anddeletes the S95cable_check file on bootup, if present. The S95cable_check file should startthe VNX Installation Assistant for File/Unified discovery and configuration process.4. Save a copy of the /etc/sysconfig/network-scripts/ifcfg-eth3 file to the folder /home/nasadminand delete the existing file in the /etc/... folder.5. Remove any extra or unwanted entries for the Control Station hostname and external IP ad-Known problems and limitations 31Troubleshootingdress from the /etc/hosts (by using the vi editor and the like) that may be present if the VNXInstallation Assistant for File/Unified process was run multiple times.6. If desired, clean up the e-mail user configuration file and disable the ConnectHome transportmechanisms:# rm /nas/sys/.email_user.config (NAS 5.6.39 and higher)# /nas/bin/nas_emailuser -init# /nas/sbin/nas_connecthome -modify -modem_priority Dis-abled-ftp_priority Disabled -email_priority Disabled (NAS5.5.31, 5.6.36and later)7. Connect to the serial port on the front (or back on newer models) of the Control Station. UseHyperTerminal and configure as follows:COM1 or COM2; Bits per second: 19200; Data bits: 8; Parity: None; Stop bits: 1; Flow Control:None; verify that Autodetect and ANSI are selected for terminal emulation.8. Reboot the Control Station and wait for the following console screen message before contin-uing with the next step:Starting cable_check: This is an NS40FC system waitingto be configured by Celerra Startup Assistant (CSA). UseCSA to verify that the system has been cabled properly.Once the check is complete, CSA will instruct the CableCheck Utility to continue and NAS services will bestarted and a login prompt provided. If you want to breakout from this and login to the Control Station (you mustreally know what you are doing) press "L".Waiting for Celerra Startup Assistant (CSA), to contin-ue...............Note: VNX Installation Assistant for File/Unified was formerly known as Celerra Startup As-sistant (CSA).9. On the Windows client running the VNX Installation Assistant for File/Unified, remove the ex-isting CSA.xml file from the location C:\Program Files\EMC\CSA\start-up\test\CSA_000e0ccfc72a.xml (example of filename). Alternatively, during the welcomephase of the VNX Installation Assistant for File/Unified, select New Configuration to ignore anyexisting xml files that might reside on the client from previous VNX Installation Assistant forFile/Unified configurations.10. Start up the VNX Installation Assistant for File/Unified from the Windows client. On the Welcomepage, click Next. You should then be able to read the MAC address broadcast and continuewith remaining configuration steps by using VNX Installation Assistant for File/Unified.32 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingChange a value set with the VNX Installation Assistant for File/UnifiedAle ung lhe VNX Inlaaln Alanl Ie/Uned l nla yu ylem, yu mayvanl l hange ne me lhe aue lhal vee ngued. Ue Tabe 3 n age 33 lhange any lhe aue el vhe ung lhe VNX Inlaaln Alanl Ie/Uned.Unhee an be ued l hange lhe aue el dung lhe VNX Inlaaln Alanl Ie/Uned, exel lhe ub lage e II addee. Yu mul ue lhe CLImmand l hange lhe aue. T enle a CLI mmand, ue lhe CLI Commands lab.Note: Yu hae l g n l Unhee a l l hange lhe aue el.Table 3. How to change the value set by using UnisphereHow to change it VNX Installation Assistantfor File/Unified valueControl Station hostname1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the Hostname.Control Station Static IP ad-dress1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the IP Address.Control Station Netmask1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the Netmask.Control Station DNS Domain1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the DNS Domain Name.Control Station DNS Servers1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the DNS Servers.Change a value set with the VNX Installation Assistant for File/Unified 33TroubleshootingTable 3. How to change the value set by using Unisphere (continued)How to change it VNX Installation Assistantfor File/Unified valueControl Station NTP servers1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the NTP servers.Control Station time zone1. Select your VNX system.2. Go to System Manage Control Station.3. Edit the Current Timezone.Root password1. Select your VNX system.2. Go to Settings.3. Select root from the Users list and click Properties.4. Edit the required root information.NAS Administrator password1. Select your VNX system.2. Go to Settings.3. Select nasadmin from the Users list and click Properties.4. Edit the required nasadmin information.Blade DNS Domain1. Select your VNX system.2. Go to System Network DNS.3. Delete the existing DNS domain and create a new one.Primary Blade DNS Server1. Select your VNX system.2. Go to System Network DNS.3. Select a DNS domain for the primary blade DNS serverand click Properties.4. Edit the DNS server information.34 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingTable 3. How to change the value set by using Unisphere (continued)How to change it VNX Installation Assistantfor File/Unified valueSecondary Blade DNSServer1. Select your VNX system.2. Go to System Network DNS.3. Select a DNS domain for the secondary blade DNS serverand click Properties.4. Edit the DNS server information.Blade NTP Server1. Select your VNX system.2. Go to System Data Movers.3. Select a Data Mover and click Properties.4. Edit the NTP server information.Blade time zone1. Select your VNX system.2. Go to System Data Movers.3. Select a Data Mover and click Properties.4. Edit the blade timezone information. For VNX softwareversion prior to 5.6, CLI: As root, run the following CLIcommand:/nasmcd/sbin/server_date timezone CLI: As root, run the following command: Storage Processor A IP Ad-dress/nasmcd/sbin/clariion_mgmt -modify -spa_ip CLI: As root, run the following command:/nasmcd/sbin/clariion_mgmt -modify -spb_ip Storage Processor B IP Ad-dressSite ID1. Select your VNX system.2. Go to System Service Tasks Manage Connect Home.3. Edit the Site ID.Change a value set with the VNX Installation Assistant for File/Unified 35TroubleshootingTable 3. How to change the value set by using Unisphere (continued)How to change it VNX Installation Assistantfor File/Unified valueDial-in Modem1. Select your VNX system.2. Go to System Service Tasks Manage Connect Home.3. Edit the Dial-in Modem information.Licenses1. Select your VNX system.2. Go to System Manage Licenses.3. Edit the information for the licenses.NFS Export values1. Select your VNX system.2. Go to Sharing NFS.3. Select an NFS export from the list of NFS Exports andclick Properties.4. Edit the NFS export information.iSCSI LUN values1. Select your VNX system.2. Go to Sharing iSCSI.3. Select an iSCSI LUN from the list of LUNs and clickProperties.4. Edit the iSCSI LUN information.CIFS Share values1. Select your VNX system.2. Go to Sharing CIFS.3. Select a CIFS share from the list of CIFS Shares and clickProperties.4. Edit the CIFS share information.EMC Training and Professional ServicesIMCCulme Idualnue heyuean hvIMClage dul v lgelhevlhn yu ennmenl l maxmze yu enle nalulue nelmenl. IMCCulmeIdualn ealue nne and hand-n lanng n lale--lhe-al ab nenenly aledlhughul lhe vd. IMCulme lanng ue ae deeed and deeed by IMC36 Getting Started with VNX Installation Assistant for File/Unified 7.0Troubleshootingexel. G l lhe IMC Onne Sul veble al hll://Sul.IMC.m ue andeglaln nmaln.IMCIena See an heyumemenl yu VNXee eenly. Cnulanleauale yu bune, IT ee, and lehngy, and emmend vay lhal yu aneeage yu nmaln lhe ml benel. Im bune an l memenlaln, yugel lhe exeene and exele lhal yu need vlhul lanng yu IT la hng andlanng nev enne. Cnlal yu IMC Culme Sul Reeenlale menmaln.EMC Training and Professional Services 37Troubleshooting38 Getting Started with VNX Installation Assistant for File/Unified 7.0TroubleshootingIndexCCIIS 11Cnl Slaln 18Ddeaul galevay 19DNS Dman 33DNS See 33EIMC I-Lab Nagal 18exlng 10Ggalevay adde 19MMAC adde 13, 23MIIS 12mule bade ul 18NNAS 5.5 amy 24NAS 5.6 amy 24NAS ee 18Nelma 33Nelv Cngualn 11NIS 11NTI ee 34Pe-ngualn 21may bade 18nng 10Ixy_ARI 31SSlal II adde 33Slage Inng 11Tlubehlng 17VVMvae nelv nleae 14VIN nleae 14Getting Started with VNX Installation Assistant for File/Unified 7.0 3940 Getting Started with VNX Installation Assistant for File/Unified 7.0Index