Installation Assistant Getting Started

EMC
VNX Series
Release 7.0
Getting Started with VNX Installation Assistant for File/Unified
P/N 300-011-839
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Cyghl 2011 - IMC Caln. A ghl eeed.
Iubhed Iebuay 2011
IMC beee lhe nmaln n lh ubaln auale a l ubaln dale. The
nmaln ub|el l hange vlhul nle.
THI INIORMATION IN THIS IULICATION IS IROVIDID "AS IS." IMC CORIORATION
MAKIS NO RIIRISINTATIONS OR WARRANTIIS OI ANY KIND WITH RISIICT TO
THI INIORMATION IN THIS IULICATION, AND SIICIIICALLY DISCLAIMS IMILIID
WARRANTIIS OI MIRCHANTAILITY OR IITNISS IOR A IARTICULAR IURIOSI.
Ue, yng, and dlbuln any IMC lvae debed n lh ubaln eue an
aabe lvae ene.
I lhe ml u-l-dale egualy dumenl yu dul ne, g l lhe Tehna
Dumenlaln and Ade eln n IMC Iven.
I lhe ml u-l-dale lng IMC dul name, ee IMC Caln Tadema n
IMC.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.0
Contents
Preface.....................................................................................................5
Chapter 1: Introduction...........................................................................9
Oeev................................................................................................................10
Inleeably malx.........................................................................................10
Ieeule...........................................................................................................11
Inla lhe VNX Inlaaln Alanl Ie/Uned....................................12
VNX Inlaaln Alanl Ie/Uned nelv hel......................13
Run lhe VNX Inlaaln Alanl Ie/Uned........................................14
Whal Nexl`...................................................................................................15
Chapter 2: Troubleshooting..................................................................17
IMC I-Lab Inleeably Nagal..............................................................18
Knvn bem and mlaln.......................................................................18
Allahng a CIIS hae a.......................................................................18
Cannl elal lhe nlaaln VNXInlaaln Alanl
Ie/Uned.............................................................................................18
CIIS ee ealn a............................................................................19
CIIS ee |n a....................................................................................19
CIIS Wndv 2000 ee name englh elln..............................20
VNX Inlaaln Alanl Ie/Uned a l mele
ngualn..........................................................................................21
VNX Inlaaln Alanl Ie/Uned en and VNX
lvae en ae nl malbe...................................................23
Dvnad DISKIART ully Wndv Vla...................................25
SCSI LUN Allah a...............................................................................25
MIIS enl ngualn n SCSI hl a.........................................26
MIIS a l add lhe Lnux hl..............................................................27
Ibem elng.......................................................................................28
Inng a.........................................................................................28
Reume VNX Inlaaln Alanl Ie/Uned.............................28
Sylem dened lage nl ealed.................................................29
Uneeabe VNX Inlaaln Alanl Ie/Uned
e........................................................................................................29
Change a aue el vlh lhe VNX Inlaaln Alanl
Ie/Uned.......................................................................................................33
IMC Tanng and Iena See...........................................................36
Index.......................................................................................................39
Contents
Preface
A 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, cac
niai qu |MC cccniaic.
Getting Started with VNX Installation Assistant for File/Unified 7.0 5
Special notice conventions
IMC 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 a
alua aln.
Where to get help
IMC 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 Sul
veble (eglaln eued) al hll://Sul.IMC.m.
Tubehlng G l lhe IMC Onne Sul veble. Ale ggng n, ale
lhe aabe Sul by Idul age.
Tehna ul I lehna ul and ee euel, g l IMCCulme
See n lhe IMC Onne Sul veble. Ale ggng n, ale lhe aabe
Sul by Idul age, and he elhe Live Chat Create a service request. T
en a ee euel lhugh IMC Onne Sul, yu mul hae a ad ul
ageemenl. Cnlal yu IMCae eeenlale dela abul blanng a ad
ul ageemenl vlh ueln abul yu aunl.
Note: D nl euel a e ul eeenlale une ne ha aeady been agned l
yu alua ylem bem.
Your comments
Yu uggeln v he u nlnue l me lhe auay, ganzaln, and ea
ualy lhe ue ubaln.
Ieae end yu nn lh dumenl l:
6 Getting Started with VNX Installation Assistant for File/Unified 7.0
Preface
techpubcomments@EMC.com
Preface
Preface
1
Introduction
IMC VNX Inlaaln Alanl Ie/Uned a land-ane vzad
lhal ndale mule unln eued nlaaln.
Th dumenl al lhe VNXnmaln el and nlended ue
vh vanl l ngue and manage VNX ung lhe VNX Inlaaln
Alanl Ie/Uned.
T nuded ae:
x
Oeev n age 10
x
Inleeably malx n age 10
x
Ieeule n age 11
x
Inla lhe VNX Inlaaln Alanl Ie/Uned n age 12
x
VNXInlaaln Alanl Ie/Unednelv hel n age
13
x
Run lhe VNX Inlaaln Alanl Ie/Uned n age 14
Overview
The IMC
VNXInlaaln Alanl Ie/Uned a land-ane vzad lhal

ndale mule unln eued nlaaln, uh a VNX dey and
nlazaln, healh he, ngualn Cnl Slaln and bade, and dul
eglaln. Th vzad ha been exlended l nude a me nleae au
ngualn 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 lehna
mdue 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:
x
VNX dey and nlazaln
x
Healh he
x
Cngualn Cnl Slaln and bade
x
Cngue CnnelHme e-ma ul
C Cngue l:
x
In lage ung exe and ulm mde
x
Ceale ba and hghy aaabe nelv dee
x
Ceale and allah CIIS hae
x
Ceale NIS exl
x
Sel u MIIS
Note: Th ln aaabe ny MIIS-uled ylem. Seel lh ln ny yu vanl
l un MIIS and lhe MIIS nalulue ngued n yu ylem n adane. Ree l |MC
VNX MP|S c |C an! SCS| 6.0 Inux Ccni P!ui Gu!c l manuay ngue MIIS.
Interoperability matrix
Tabe 1 n age 11 eale lhe VNX vlh lhe eele VNX OI Ie en, Cenl
OS, and VNX Inlaaln Alanl Ie/Uned en.
Introduction
Table 1. Interoperability matrix
VNX Installation Assistant
for File/Unified version
Client OS VNX OE for File VNX hardware
7.0.10.3 or later Windows XP, 2000, Vista 7.0.10.3 or later VNX5300
Note: The VNX Inlaaln Alanl Ie/Uned vzad de nl un n NT4 ee.
Prerequisites
Tabe 2 n age 11 l lhe eeule lhe VNX Inlaaln Alanl Ie/Uned.
Table 2. Prerequisites for different wizards in VNX Installation Assistant
Prerequisites Operating system Wizard
x
Display settings must have a minimum of 256
colors (for Windows NT and Windows 2000).
Windows XP/2000/Vista Storage Provisioning
x
Proper communication channel between the VNX,
the interfaces, and the client must exist.
Windows XP/2000/Vista Network Configuration
x
VNX must be provisioned to get the pool size.
x
Interfaces must be available to attach a share to
the client.
x
x
Respective domain controllers and their creden-
tials must be available to create and join the CIFS
server, and to attach the CIFS share to the client.
Windows XP/2000/Vista CIFS
x
VNX must be provisioned to get the pool size.
x
the client.
x
Windows XP/2000/Vista NFS
Prerequisites 11
Introduction
Table 2. Prerequisites for different wizards in VNX Installation Assistant (continued)
Prerequisites Operating system Wizard
x
VNX must be provisioned so that at least four
LUNs with the same size to be in one of the sys-
tem defined pool: clar_r5_performance, clar_r6,
or clar_r10.
x
the client.
x
the interfaces, the computer running VNX Instal-
lation Assistant for File/Unified, and MPFS Linux
hosts must exist.
x
For Fibre Channel configuration, the HBA driver
must be installed on the client, and the HBA must
be configured to connect to the fabric-connected
VNX system.
x
For iSCSI configuration, the iSCSI package must
be installed on the client.
Windows XP/2000/Vista MPFS
Install the VNX Installation Assistant for File/Unified
ee nlang lhe VNX Inlaaln Alanl Ie/Uned, ey lhal:
x
Ae l lhe IMC Onne Sul veble al hll://Sul.IMC.m lhe VNX
Inlaaln Tbx CD (eeed) aaabe.
x
Wndv-baedenl mule n lhe ame ubnel (ulme nelv) a lhe Cnl
Slaln.
x
The 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 lhe
VNX Inlaaln Tbx CD nl yu mule.
2. In lhe Getting Started with your EMC VNX Installation vndv, VNX Installation
Assistant for File/Unified l nla lhe VNXInlaaln Alanl Ie/Uned n yu
mule. Igue 1 n age 13 hv lhe nlaaln e VNX Inlaaln
Alanl Ie/Uned m VNX Inlaaln Tbx CD.
Introduction
This CD contains the intellectual property of
EMC Corporation or is licensed to EMC Corporation
from third parties. Use of this CD and the intellectual
property contained herein is expressly limited to the
terms and conditions of the License Agreement.
EMC Cel erra NS40 System
Tutori al CD
CSA Instal l ati on
P/N nnn-nnn-nnn-A0n
Copyri ght 2nnn EMC Corporati on
Al l Ri ghts Reserved
Network
VNX-000065
Load VNX Installation Toolbox CD in
either a laptop or PC tower.
Figure 1. Installing VNX Installation Assistant for File/Unified
The IMC Onne Sul veble al hll://Sul.IMC.m de me nmaln.
VNX Installation Assistant for File/Unified network checklist
ee 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 addlna
nmaln.
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 lhe
Cnl Slaln, enue lhal yu eel lhe el LAN nelv nleae ad n vhh
yu vanl l eah lhe Cnl Slaln.
7. I lhe VNX Inlaaln Alanl Ie/Uned annl delel lhe MAC adde lhe
Cnl 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 lhe
Cnl 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/N
038-003-457 and abeed See LAN Cabe Aemby) l nnel l lhe Cnl Slaln
VNX Installation Assistant for File/Unified network checklist 13
Introduction
dely m lhe enl IC unnng lhe VNX Inlaaln Alanl Ie/Uned, and
em lhe vng:
a. Dnnel lhe exlena nelv abe l lhe Cnl Slaln. Th abe abeed
MGMT, a hvn n lhe vng gue.
b. Cngue lhe Wndv enl vlh a lal II adde n lhe ame ga nelv
beng ued by lhe Cnl Slaln, ung a nelma 255.255.255.0, and n deaul
galevay adde.
. Ue a laghl-lhugh ( e) Ilhenel abe l nnel lhe VNX Inlaaln
Alanl 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 lhe
Welcome age l nlale lhe badal and dey e, lhen nlnue vlh lhe
VNX Inlaaln Alanl Ie/Uned ngualn.
Run the VNX Installation Assistant for File/Unified
T un lhe VNX Inlaaln Alanl Ie/Uned:
1. Dube- lhe VNX Installation Assistant for File/Unified hlul n lhe del g
l C:(IgamIe(IMC(VNX Inlaaln Alanl(lalu(aunh.bal. The VNX
Inlaaln 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 ale
lhe nla ylem nlaaln and engualn ha been meled.
4. C Configure l n lage and elu lhe VNX duln.
Introduction
5. 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. Thee
ae eea mmn memenlaln aaabe lhugh lhe VNX Inlaaln Alanl,
yu an ngue yu ylem by ung lhe IMC
Unheelvae.
Cmmn memenlaln:
x
Ceale CIIS hae
x
Ceale NIS exl
x
Sel u MIIS ( MIIS-uled ylem)
x
Iem mmn l-VNX Inlaaln Alanl la
Note: On a Wndv Vla ylem, yu need l ue CIIS vzad, yu mul dabe Ue Ae
Cnl.
The IMC Onne Sul veble al hll://Sul.IMC.m de me nmaln.
What Next?
Yu ae nv eady l d lhe vng:
x
Inla and ngue IMCSeue Remle Sul (ISRS) II Cenl. Ue lhe Initialize and
register VNX and configure ESRS n unde VNX la and be ue l eel lhe ISRS
ln vhen mled.
x
Allah ne me ee l yu VNX. Ue lhe Attach server n unde See la
n lhe ul veble l geneale le-by-le nluln allahng a ee.
Run the VNX Installation Assistant for File/Unified 15
Introduction
Introduction
2
Troubleshooting
A al an el l nlnuuy me andenhane lhe emane
andaable l dul ne, IMCeday eeae neven
l hadvae and lvae. Theee, me unln debed n lh
dumenl may nl be uled by a en lhe lvae
hadvae uenly n ue. I lhe ml u-l-dale nmaln n dul
ealue, ee l yu dul eeae nle.
I a dul de nl unln ey de nl unln a debed
n lh dumenl, nlal yu IMC Culme Sul Reeenlale.
P|cn|cuin |a!na VNXnlan addlna nmaln abul
ung lhe IMC Onne Sul veble and eng bem.
T nuded ae:
x
IMC I-Lab Inleeably Nagal n age 18
x
Knvn bem and mlaln n age 18
x
Change a aue el vlh lhe VNX Inlaaln Alanl
Ie/Uned n age 33
x
IMC Tanng and Iena See n age 36
EMC E-Lab Interoperability Navigator
The IMC I-Lab
Inleeably Nagal a eahabe, veb-baed aaln lhal

de ae l IMC nleeably ul male. Il aaabe al
hll://Sul.IMC.m. Ale ggng n l lhe IMC Onne Sul veble, ale lhe
aabe Sul by Idul age, nd Tools, and E-Lab Interoperability Navigator.
Known problems and limitations
Th eln l lhe nvn bem and mlaln lhe VNX Inlaaln Alanl
Ie/Uned.
Attaching a CIFS share fails
Attaching a CIFS share may fail when not using the first primary blade. Symptom
VNX Installation Assistant for File/Unified only sets up the DNS for the first primary blade. Cause
Unisphere can be used to set up the DNS on the other primary blades for VNX Installation Assistant
for 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 and
later.
Solution
Cannot restart the installation for VNX Installation Assistant for File/Unified
Cannot restart the installation for VNX Installation Assistant after exiting, before the cable check
is passed. NAS services are unavailable and attempts to access Unisphere and the NAS CLI di-
rectly do not work. (Linux CLI is accessible.)
Symptom
The VNX Installation Assistant for File/Unified mode on the Control Station is disabled before the
cable check completed successfully and NAS services are not available. This condition can occur
if a Shift + L is executed before the cable check completes.
Cause
Log in as root on the Control Station and at the command line, type: Solution
service nas start
Troubleshooting
CIFS server creation fails
CIFS server creation fails because the CIFS server join with the domain fails. Symptom
One possible reason can be that the default gateway is not set up for a blade. Cause
Set up a default gateway before using the CIFS server create and attach: Solution
1. Check if the Data Mover has any interfaces. If not, create an interface on the network for which
you need to set up the default gateway.
2. When the interface is created, run the CLI command:
$ server_route server_2 -add default <gateway>
where:
<gateway> = 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 an
interface 10.26.125.99, then type:
$ server_route server_ 2 -add default 10.26.125.1
where:
1 = the gateway address.
To verify that the default gateway was added, type:
$ server_route server_2 -1
CIFS server join fails
CIFS server join fails if there is clock skew between the Data Mover and the domain controllers. Symptom
The 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 the
domain controller.
Cause
Known problems and limitations 19
Troubleshooting
Solution x Create an NTP server for the Data Mover from the Unisphere. This option is available on the
Data Mover properties screen. The NTP server field accepts comma separated multiple NTP
servers. When you click the Apply button, the NTP server with the given IP address points to
the Data Mover.
x Another option is available through the CLI command. Use the modify command on the Data
Mover object for property ntpServer.
CIFS Windows 2000 server name length restriction
CIFS Windows 2000 server name cannot be greater than 15 characters, even though Windows
2000 Active Directory accepts up to 63 characters.
Symptom
In the VNX Installation Assistant for File/Unified, the same field is used to define the CIFS server
name and the NetBIOS name (compname). Therefore, if the CIFS server name is greater than 15
characters, a failure occurs because the NetBIOS name (compname) cannot be greater than 15
characters.
Cause
Windows 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.
Solution
Troubleshooting
VNX Installation Assistant for File/Unified fails to complete configuration
Symptom x VNX Installation Assistant for File/Unified fails to complete the configuration of SP IP addresses
during 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 and
displays the error:
Backend IP setup | Could not change IP address of the SP
CSA startup_wiz.log: ERROR 2008-06-06 16:15:12,233
[com.emc.celerra.startup.configuration.BaseSetup]:Backend
ip config (start) failed with retcode : 30 and error
message
WARN 2008-06-06 16:15:12,233
[com.emc.celerra.startup.configuration.BaseSetup]: There
were warnings or errors while configuring backend :
severity :4 and
messages : Could not change IP address of the SP Network
Settings on CSA client:
10.113.0.190
255.255.255.0
10.113.254.254
The 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, the
gateway address should be changed to match the same network as that of the Control Station
and the VNX Installation Assistant for File/Unified client during the VNX Installation Assistant for
File/Unified configuration work [10.113.x gateway vs. 10.113.x.x gateway]. In this case, the VNX
Installation Assistant for File/Unified application fails during the pre-configuration apply phase
where the IP addresses are being configured by the VNX Installation Assistant for File/Unified
wizard because the default gateway IP address is 10.113.254.254.
Cause
Troubleshooting
Solution
1. Preferred workaround:
a. With the VNX Installation Assistant application open at the point of failure, log in to the
Control Station as root and set a new default gateway:
# /sbin/route add -net default gw 10.113.0.1
b. Verify that SPA's IP address was changed and not SPB:
# /nas/sbin/navicli -h <spa> networkadmin -get
should be set to a new IP address.
# /nas/sbin/navicli -h <spb> networkadmin -get
should still be set with an internal IP address.
c. Return SPA to the default Internal IP address and gateway:
# /nas/sbin/navicli -h <spa> networkadmin -set -address
128.221.252.200 -gateway 128.221.252.104
d. 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 x
e. 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 the
screen where the gateway address was shown. Edit the address to 10.113.0.1, then
continue by using the VNX Installation Assistant for File/Unified to complete the installation:
<gateway>10.113.0.1</gateway>
Note: If the VNX Installation Assistant application was closed, locate and edit the C:\Program
Files\EMC\CSA\startup\test\CSA_xxxx.xml file to reflect the new gateway address. Restart
the VNX Installation Assistant, select the MAC address of the current Control Station, provide
the login information, and continue using the VNX Installation Assistant for File/Unified to
complete the installation.
2. Alternative workaround:
a. Connect the VNX Installation Assistant for File/Unified client directly to the Control Station
by 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 emc
166265 provides more information) to get the Control Station back to a pre-VNX Installation
Troubleshooting
Assistant for File/Unified configured state.
d. Rerun the VNX Installation Assistant process.
VNX Installation Assistant for File/Unified version and VNX software version
are not compatible
CSA 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 the
Celerra Software version (5.x.xx-x) installed on the system
you are trying to initialize.
Symptom
The CSA version and the Celerra Software version are not compatible. Cause
The VNX Installation Assistant for File/Unified wizard is available on the VNX Installation Toolbox
CD for all new installations, while several versions are also available for downloading from the
EMC 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 that
the 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 require
technical support intervention to repair. CSA versions 5.5.32 and later are supposed to check the
NAS 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 older
NAS 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 Celerra
model releases. The following compatibility statements can be made at this time.
Solution
Troubleshooting
NAS 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 built
into the wizard (CSA 5.5.32 will indicate by using a pop-up when the Celerra version is not
compatible, 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 version
not 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 a
problem).
Note: Due to potential CSA hang issue during pre-configuration apply changes screen, use
CSA version 5.6.38 with NAS 5.6.37 installs. Primus article emc 193170 provides details of
the 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 currently
recommended 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.38
CSA, downloadable from the EMC Online Support website. The CSA version 5.6.38
on EMC Online Support has been modified to correct a problem found with the Cable
Check process that prevents successful configuration.
Troubleshooting
x CSA 5.6.39 is compatible with NAS version 5.6.39 only, and not with any other previous NAS
versions. (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 CSA
is 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 indicates
CSA 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 testing
indicates CSA is backwards compatible with 5.6.41, 5.6.40, and 5.6.39 NAS versions.)
Download DISKPART utility for Windows Vista
When attaching an iSCSI LUN to the local computer on Windows Vista, it prompts to download
the DISKPART utility even though the utility is already installed. When checked by using the
Windows command line, the directory for DISKPART exists and is installed.
Symptom
x 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 utility
status and the user will get a pop-up in iSCSI create and attach page regarding DISKPART
installation.
Cause
Solution
1. 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 off
link.
3. On the Turn on User Account Control (UAC) to make your computer more secure option, clear
the 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 fails
While creating a new iSCSI LUN and attaching it to a local host, the iSCSI attach fails with an
error message :
Disk not found
Symptom
The operating system of the host does not support dynamic search of iSCSI LUN and needs a
reboot to detect the new iSCSI LUN.
Cause
Troubleshooting
Solution
1. 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 write
protected
Symptom
The default SAN policy on the Windows 2008 client machine is not set to VDS_SP_ONLINE. The
SAN policy on the Windows 2008 restricts all the iSCSI LUNs to be read only.
Cause
Solution
1. 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 the
machine.
3. If Online All is displayed then iSCSI LUN create and attach will work as desired on the VNX
Installation 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 the
iSCSI LUNs online with read-write options.
5. You can launch the VNX Installation Assistant for File/Unified and select the Create/Attach
iSCSI LUN to create and attach iSCSI LUN on Windows 2008 successfully.
MPFS client configuration on iSCSI host fails
MPFS fails to complete the MPFS client configuration on iSCSI host. Symptom
The iSCSI service is not running on the host, or the local mount directory to create is under
a read-only directory.
Cause
Troubleshooting
1. Run the iSCSI status command to check if the iSCSI service is running. If the iSCSI
service 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 display
the 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.
Solution
MPFS fails to add the Linux host
MPFS fails to add the Linux host, an error appears: Symptom
MPFS does not support the kernel of this host
The MPFS client software does not support the kernel of this host. Cause
The MPFS client support matrix is listed in the file host_support.properties, which is under
<CSA installation directory>\startup\mpfs.
Solution
The format of the support host value is OSname-KernelVersion-CpuType. The user can
get the hosts operating system, kernel version, and CPU type information by running
the following command:
uname -m;uname -n;uname -r;uname -s
If the host kernel is not on the MPFS client support matrix, the user needs to install a
kernel which is supported by MPFS.
MPFS wizard fails to log in to the Linux hosts. Symptom
Username or password is not correct, or the default SSH server installations are config-
ured to refuse the authentication password.
Cause
Solution
1. Type the correct username and password on the MPFS Add Hosts page, and add
the hosts again.
2. If the login still fails, then the default SSH server installations may be configured to
decline the authentication type password.
3. Edit the /etc/ssh/sshd_config and change the value of PasswordAuthentication to
yes, then restart the SSH daemon to re-read this configuration. For example, run:
/etc/init.d/sshd restart
Troubleshooting
Problem reporting
CSA fails to complete successfully. Symptom
Unknown. Cause
When reporting problems with CSA that require escalation to the Engineering team, a
Remedy 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.
Solution
Provisioning fails
Provisioning fails with an error:
Unable to establish communication with <IP address>
Symptom
The connectivity between the EMC VNX for Block system and the Control Station is lost. Cause
Check the cable connection between VNX for Block system and Control Station. Solution
Resume VNX Installation Assistant for File/Unified
On the Welcome screen, user is prompted: Symptom
Enter the password for this VNX
If the user runs VNX Installation Assistant for File/Unified, but cancels the execution prior to
completing all the steps, a configuration file is created that allows the user to resume the VNX
Installation Assistant for File/Unified from the point where it was discontinued.
Cause
Troubleshooting
When the VNX Installation Assistant for File/Unified is run, it creates a VNX system specific
configuration file (C:\Program Files\EMC\CSA\startup\test\CSA_nnnnnnnnnnnn.xml).
Solution
To 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/Unified
screen, select the box in the lower-left side of the screen next to Select if you want to create a
new configuration profile.
Note: VNX Installation Assiatant for File/Unified was previously known as Celerra Startup
Assistant (CSA).
Beginning with CSA version 5.5.32, there is a new page during the welcome phase which allows
the user to select either a new configuration or the MAC address of an existing installation
from the following menu:
Welcome
Select configuration profile
Select a profile using this MAC address: New Configuration
<existing MAC address>
System defined storage pool not created
On the MPFS System and Configuration page, the user is prompted:
To create MPFS storage pool, at least four LUNs with the
same size are required to be in one of the system defined
pools:
clar_r5_performance, clar_r6, or clar_r10
Symptom
MPFS needs to create MPFS storage pools from the system defined pools clar_r5_performance,
clar_r6, or clar_r10 for the MPFS initialization.
Cause
Select Provision unused disks on the Configurations wizards page to create at least one system
defined storage pool that includes at least four LUNs in the pool: clar_r5_performance, clar_r6, or
clar_r10.
Solution
Unrecoverable VNX Installation Assistant for File/Unified errors
Unrecoverable VNX Installation Assistant for File/Unified errors that prevent completion of VNX
Installation Assistant for File/Unified configuration process.
Symptom
Troubleshooting
Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that
need to be reversed.
Cause
Troubleshooting
Perform 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 following
steps may not work and a more intensive manual cleanup would be required, as indicated
in the notes below.
Solution
1. Run the following command to stop the NAT or Proxy_ARP configuration:
# /nasmcd/sbin/clariion_mgmt stop
Use clariion_mgmt -info to determine if NAT or Proxy-ARP is configured. If the command returns
Error 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 completely
by the -stop switch. If so, use the clariion_mgmt -stop -skip_rules command, then manually
edit 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 the
Control Station.
Finally, you should check the actual IP addresses running on the SPs and change them back
to the default VNX values (128.221.252.200/128.221.253.201) by using navicli -h <sp> net-
workadmin -set -address xxx by the -stop switch. If so, use the clariion_mgmt -stop -skip_rules
command, then manually edit the /etc/hosts and /nas/site/sp_info to restore the default
192.168.x (or 128.221.x) IP addresses for the SPs, remove the /nas/site/clariion_mgmt.cfg
file (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 -gateway
xxx.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, provides
more information.
2. Copy the S95cable_check script to /etc/rc3.d and chmod the file to make it executable by
using the chmod 755 S95cable_check command.
Note: The challenge here is that the VNX Installation Assistant for File/Unified process deletes
the S95cable_check file. If a copy has not been previously saved, mount a similar version of
the 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 reference
the NAS version involved.
3. Remove the /tmp/.factory_check_successful file if it exists. Existence of the file prevents
proper completion of the VNX Installation Assistant for File/Unified configuration process and
deletes the S95cable_check file on bootup, if present. The S95cable_check file should start
the 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/nasadmin
and delete the existing file in the /etc/... folder.
5. Remove any extra or unwanted entries for the Control Station hostname and external IP ad-
Troubleshooting
dress from the /etc/hosts (by using the vi editor and the like) that may be present if the VNX
Installation Assistant for File/Unified process was run multiple times.
6. If desired, clean up the e-mail user configuration file and disable the ConnectHome transport
mechanisms:
# 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 (NAS
5.5.31, 5.6.36
and later)
7. Connect to the serial port on the front (or back on newer models) of the Control Station. Use
HyperTerminal 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 waiting
to be configured by Celerra Startup Assistant (CSA). Use
CSA to verify that the system has been cabled properly.
Once the check is complete, CSA will instruct the Cable
Check Utility to continue and NAS services will be
started and a login prompt provided. If you want to break
out from this and login to the Control Station (you must
really 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 welcome
phase of the VNX Installation Assistant for File/Unified, select New Configuration to ignore any
existing xml files that might reside on the client from previous VNX Installation Assistant for
File/Unified configurations.
10. Start up the VNX Installation Assistant for File/Unified from the Windows client. On the Welcome
page, click Next. You should then be able to read the MAC address broadcast and continue
with remaining configuration steps by using VNX Installation Assistant for File/Unified.
Troubleshooting
Change a value set with the VNX Installation Assistant for File/Unified
Ale ung lhe VNX Inlaaln Alanl Ie/Uned l nla yu ylem, yu may
vanl l hange ne me lhe aue lhal vee ngued. Ue Tabe 3 n age 33 l
hange 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 CLI
mmand 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 Unisphere
How to change it VNX Installation Assistant
for File/Unified value
Control Station hostname
1. Select your VNX system.
2. Go to System Manage Control Station.
3. Edit the Hostname.
Control Station Static IP ad-
dress
3. Edit the IP Address.
Control Station Netmask
3. Edit the Netmask.
Control Station DNS Domain
3. Edit the DNS Domain Name.
Control Station DNS Servers
3. Edit the DNS Servers.
Change a value set with the VNX Installation Assistant for File/Unified 33
Troubleshooting
Table 3. How to change the value set by using Unisphere (continued)
Control Station NTP servers
3. Edit the NTP servers.
Control Station time zone
3. Edit the Current Timezone.
Root password
2. Go to Settings.
3. Select root from the Users list and click Properties.
4. Edit the required root information.
NAS Administrator password
2. Go to Settings.
3. Select nasadmin from the Users list and click Properties.
4. Edit the required nasadmin information.
Blade DNS Domain
2. Go to System Network DNS.
3. Delete the existing DNS domain and create a new one.
Primary Blade DNS Server
3. Select a DNS domain for the primary blade DNS server
and click Properties.
4. Edit the DNS server information.
Troubleshooting
Secondary Blade DNS
Server
3. Select a DNS domain for the secondary blade DNS server
and click Properties.
4. Edit the DNS server information.
Blade NTP Server
2. Go to System Data Movers.
3. Select a Data Mover and click Properties.
4. Edit the NTP server information.
Blade time zone
2. Go to System Data Movers.
3. Select a Data Mover and click Properties.
4. Edit the blade timezone information. For VNX software
version prior to 5.6, CLI: As root, run the following CLI
command:
/nasmcd/sbin/server_date <data mover>
timezone <posix-string>
CLI: As root, run the following command: Storage Processor A IP Ad-
dress
/nasmcd/sbin/clariion_mgmt -modify -
spa_ip <new_IP_address_for_SP_A>
CLI: As root, run the following command:
/nasmcd/sbin/clariion_mgmt -modify -
spb_ip <new_IP_address_for_SP_B>
Storage Processor B IP Ad-
dress
Site ID
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 35
Troubleshooting
Dial-in Modem
2. Go to System Service Tasks Manage Connect Home.
3. Edit the Dial-in Modem information.
Licenses
2. Go to System Manage Licenses.
3. Edit the information for the licenses.
NFS Export values
2. Go to Sharing NFS.
3. Select an NFS export from the list of NFS Exports and
click Properties.
4. Edit the NFS export information.
iSCSI LUN values
2. Go to Sharing iSCSI.
3. Select an iSCSI LUN from the list of LUNs and click
Properties.
4. Edit the iSCSI LUN information.
CIFS Share values
2. Go to Sharing CIFS.
3. Select a CIFS share from the list of CIFS Shares and click
Properties.
4. Edit the CIFS share information.
EMC Training and Professional Services
IMCCulme Idualnue heyuean hvIMClage dul v lgelhe
vlhn yu ennmenl l maxmze yu enle nalulue nelmenl. IMCCulme
Idualn ealue nne and hand-n lanng n lale--lhe-al ab nenenly aled
lhughul lhe vd. IMCulme lanng ue ae deeed and deeed by IMC
Troubleshooting
exel. G l lhe IMC Onne Sul veble al hll://Sul.IMC.m ue and
eglaln nmaln.
IMCIena See an heyumemenl yu VNXee eenly. Cnulanl
eauale yu bune, IT ee, and lehngy, and emmend vay lhal yu an
eeage yu nmaln lhe ml benel. Im bune an l memenlaln, yu
gel lhe exeene and exele lhal yu need vlhul lanng yu IT la hng and
lanng nev enne. Cnlal yu IMC Culme Sul Reeenlale me
nmaln.
EMC Training and Professional Services 37
Troubleshooting
Troubleshooting
Index
C
CIIS 11
Cnl Slaln 18
D
deaul galevay 19
DNS Dman 33
DNS See 33
E
IMC I-Lab Nagal 18
exlng 10
G
galevay adde 19
M
MAC adde 13, 23
MIIS 12
mule bade ul 18
N
NAS 5.5 amy 24
NAS 5.6 amy 24
NAS ee 18
Nelma 33
Nelv Cngualn 11
NIS 11
NTI ee 34
P
e-ngualn 21
may bade 18
nng 10
Ixy_ARI 31
S
Slal II adde 33
Slage Inng 11
T
lubehlng 17
V
VMvae nelv nleae 14
VIN nleae 14
Index

Installation Assistant Getting Started

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Installation Assistant Getting Started

Caricato da

Copyright:

Formati disponibili

EMC

VNXInlaaln Alanl Ie/Uned a land-ane vzad lhal

Inleeably Nagal a eahabe, veb-baed aaln lhal

Potrebbero piacerti anche