Anda di halaman 1dari 40
EMC é VNX ㍷ Series Release 7.0 Getting Started with VNX ㍷ Installation Assistant for
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
 

"∂∑¿π∞Æت â $," "∂π∑∂π®ª∞∂µ ≥≥ π∞Æت∫ π¨∫¨πΩ¨´

/º©≥∞∫ب´ %¨©πº®π¿

$," ©¨≥∞¨Ω¨∫ ªØ¨ ∞µ≠∂𥮪∞∂µ ∞µ ªØ∞∫ ∑º©≥∞™®ª∞∂µ ∞∫ ®™™ºπ®ª¨ ®∫ ∂≠ ∞ª∫ ∑º©≥∞™®ª∞∂µ ´®ª¨ 3ب ∞µ≠∂𥮪∞∂µ ∞∫ ∫º©±¨™ª ª∂ ™Ø®µÆ¨ æ∞ªØ∂ºª µ∂ª∞™¨

3'$ (-%.1, 3(.- (- 3'(2 /4!+(" 3(.- (2 /1.5(#$# 2 (2 $," ".1/.1 3(.-

,

*$2 -. 1$/1$2$-3 3(.-2 .1 6 11 -3($2 .% -8 *(-# 6(3' 1$2/$"3 3.

3'$ (-%.1, 3(.- (- 3'(2 /4!+(" 3(.- -# 2/$"(%(" ++8 #(2"+ (,2 (,/+($#

6

11 -3($2 .% ,$1"' -3 !(+(38 .1 %(3-$22 %.1 / 13("4+ 1 /41/.2$

4∫¨ ™∂∑¿∞µÆ ®µ´ ´∞∫ªπ∞©ºª∞∂µ ∂≠ ®µ¿ $," ∫∂≠ªæ®π¨ ´¨∫™π∞©¨´ ∞µ ªØ∞∫ ∑º©≥∞™®ª∞∂µ π¨∏º∞π¨∫ ®µ ®∑∑≥∞™®©≥¨ ∫∂≠ªæ®π¨ ≥∞™¨µ∫¨

%∂π ªØ¨ ¥∂∫ª º∑ ª∂ ´®ª¨ π¨Æº≥®ª∂π¿ ´∂™º¥¨µª ≠∂π ¿∂ºπ ∑π∂´º™ª ≥∞µ¨ Æ∂ ª∂ ªØ¨ 3¨™Øµ∞™®≥ #∂™º¥¨µª®ª∞∂µ ®µ´ ´Ω∞∫∂π∞¨∫ ∫¨™ª∞∂µ ∂µ $," /∂æ¨π≥∞µ≤

%∂π ªØ¨ ¥∂∫ª º∑ ª∂ ´®ª¨ ≥∞∫ª∞µÆ ∂≠ $," ∑π∂´º™ª µ®¥¨∫ ∫¨¨ $," "∂π∑∂π®ª∞∂µ 3π®´¨¥®π≤∫ ∂µ $," ™∂¥

≥≥ ∂ªØ¨π ªπ®´¨¥®π≤∫ º∫¨´ بπ¨∞µ ®π¨ ªØ¨ ∑π∂∑¨πª¿ ∂≠ ªØ¨∞π π¨∫∑¨™ª∞Ω¨ ∂浨π∫

"∂π∑∂𮪨 '¨®´∏º®πª¨π∫ '∂∑≤∞µª∂µ ,

Getting Started with VNX Installation Assistant for File/Unified 7.0

 

Contents

Preface

5

Chapter 1: Introduction

9

.Ω¨πΩ∞¨æ (µª¨π∂∑¨π®©∞≥∞ª¿ ¥®ªπ∞ø /π¨π¨∏º∞∫∞ª¨∫ (µ∫ª®≥≥ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ µ¨ªæ∂π≤ ™Ø¨™≤≥∞∫ª 1ºµ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ 6Ø®ª -¨øª

 

Chapter 2: Troubleshooting

17

$," $ +®© (µª¨π∂∑¨π®©∞≥∞ª¿ -®Ω∞Æ®ª∂π *µ∂æµ ∑π∂©≥¨¥∫ ®µ´ ≥∞¥∞ª®ª∞∂µ∫ ªª®™Ø∞µÆ ® "(%2 ∫Ø®π¨ ≠®∞≥∫ "®µµ∂ª π¨∫ª®πª ªØ¨ ∞µ∫ª®≥≥®ª∞∂µ ≠∂π 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ "(%2 ∫¨πΩ¨π ™π¨®ª∞∂µ ≠®∞≥∫ "(%2 ∫¨πΩ¨π ±∂∞µ ≠®∞≥∫ "(%2 6∞µ´∂æ∫ ∫¨πΩ¨π µ®¥¨ ≥¨µÆªØ π¨∫ªπ∞™ª∞∂µ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ≠®∞≥∫ ª∂ ™∂¥∑≥¨ª¨ ™∂µ≠∞ƺπ®ª∞∂µ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ Ω¨π∫∞∂µ ®µ´ 5-7 ∫∂≠ªæ®π¨ Ω¨π∫∞∂µ ®π¨ µ∂ª ™∂¥∑®ª∞©≥¨ #∂æµ≥∂®´ #(2*/ 13 ºª∞≥∞ª¿ ≠∂π 6∞µ´∂æ∫ 5∞∫ª® ∞2"2( +4- ªª®™Ø ≠®∞≥∫ ,/%2 ™≥∞¨µª ™∂µ≠∞ƺπ®ª∞∂µ ∂µ ∞2"2( Ø∂∫ª ≠®∞≥∫

 

Getting Started with VNX Installation Assistant for File/Unified 7.0

Contents

,/%2 ≠®∞≥∫ ª∂ ®´´ ªØ¨ +∞µºø Ø∂∫ª /π∂©≥¨¥ π¨∑∂πª∞µÆ /π∂Ω∞∫∞∂µ∞µÆ ≠®∞≥∫ 1¨∫º¥¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ 2¿∫ª¨¥ ´¨≠∞µ¨´ ∫ª∂π®Æ¨ ∑∂∂≥ µ∂ª ™π¨®ª¨´ 4µπ¨™∂Ω¨π®©≥¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ¨ππ∂π∫ "Ø®µÆ¨ ® Ω®≥º¨ ∫¨ª æ∞ªØ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ $," 3π®∞µ∞µÆ ®µ´ /π∂≠¨∫∫∞∂µ®≥ 2¨πΩ∞™¨∫

39

Index

Getting Started with VNX Installation Assistant for File/Unified 7.0

 

Preface

∫ ∑®πª ∂≠ ®µ ¨≠≠∂πª ª∂ ∞¥∑π∂Ω¨ ®µ´ ¨µØ®µ™¨ ªØ¨ ∑¨π≠∂π¥®µ™¨ ®µ´ ™®∑®©∞≥∞ª∞¨∫ ∂≠ ∞ª∫ ∑π∂´º™ª ≥∞µ¨∫ $," ∑¨π∞∂´∞™®≥≥¿ π¨≥¨®∫¨∫ π¨Ω∞∫∞∂µ∫ ∂≠ ∞ª∫ Ø®π´æ®π¨ ®µ´ ∫∂≠ªæ®π¨ 3بπ¨≠∂π¨ ∫∂¥¨ ≠ºµ™ª∞∂µ∫ ´¨∫™π∞©¨´ ∞µ ªØ∞∫ ´∂™º¥¨µª ¥®¿ µ∂ª ©¨ ∫º∑∑∂πª¨´ ©¿ ®≥≥ Ω¨π∫∞∂µ∫ ∂≠ ªØ¨ ∫∂≠ªæ®π¨ ∂π Ø®π´æ®π¨ ™ºπ𨵪≥¿ ∞µ º∫¨ %∂π ªØ¨ ¥∂∫ª º∑ ª∂ ´®ª¨ ∞µ≠∂𥮪∞∂µ ∂µ ∑π∂´º™ª ≠¨®ªºπ¨∫ π¨≠¨π ª∂ ¿∂ºπ ∑π∂´º™ª π¨≥¨®∫¨ µ∂ª¨∫

 

(≠ ® ∑π∂´º™ª ´∂¨∫ µ∂ª ≠ºµ™ª∞∂µ ∑π∂∑¨π≥¿ ∂π ´∂¨∫ µ∂ª ≠ºµ™ª∞∂µ ®∫ ´¨∫™π∞©¨´ ∞µ ªØ∞∫ ´∂™º¥¨µª ∑≥¨®∫¨ ™∂µª®™ª ¿∂ºπ $," π¨∑π¨∫¨µª®ª∞Ω¨

Getting Started with VNX Installation Assistant for File/Unified 7.0

5

Preface Special notice conventions $," º∫¨∫ ªØ¨ ≠∂≥≥∂æ∞µÆ ™∂µΩ¨µª∞∂µ∫
Preface
Special notice conventions
$," º∫¨∫ ªØ¨ ≠∂≥≥∂æ∞µÆ ™∂µΩ¨µª∞∂µ∫ ≠∂π ∫∑¨™∞®≥ µ∂ª∞™¨∫
CAUTION: ™®ºª∞∂µ ™∂µª®∞µ∫ ∞µ≠∂𥮪∞∂µ ¨∫∫¨µª∞®≥ ª∂ ®Ω∂∞´ ´®ª® ≥∂∫∫ ∂π ´®¥®Æ¨ ª∂ ªØ¨ ∫¿∫ª¨¥
∂π ¨∏º∞∑¥¨µª
Important: µ ∞¥∑∂𪮵ª µ∂ª¨ ™∂µª®∞µ∫ ∞µ≠∂𥮪∞∂µ ¨∫∫¨µª∞®≥ ª∂ ∂∑¨π®ª∞∂µ ∂≠ ªØ¨ ∫∂≠ªæ®π¨
Note: µ∂ª¨ ∑π¨∫¨µª∫ ∞µ≠∂𥮪∞∂µ ªØ®ª ∞∫ ∞¥∑∂𪮵ª ©ºª µ∂ª Ø®¡®π´ π¨≥®ª¨´
Hint: µ∂ª¨ ªØ®ª ∑π∂Ω∞´¨∫ ∫ºÆƨ∫ª¨´ ®´Ω∞™¨ ª∂ º∫¨π∫ ∂≠ª¨µ ∞µΩ∂≥Ω∞µÆ ≠∂≥≥∂æ ∂µ ®™ª∞Ω∞ª¿ ≠∂π ®
∑®πª∞™º≥®π ®™ª∞∂µ
Where to get help
$," ∫º∑∑∂πª ∑π∂´º™ª ®µ´ ≥∞™¨µ∫∞µÆ ∞µ≠∂𥮪∞∂µ ™®µ ©¨ ∂©ª®∞µ¨´ ®∫ ≠∂≥≥∂æ∫
/π∂´º™ª ∞µ≠∂𥮪∞∂µ %∂π ´∂™º¥¨µª®ª∞∂µ π¨≥¨®∫¨ µ∂ª¨∫ ∫∂≠ªæ®π¨ º∑´®ª¨∫ ∂π ≠∂π
∞µ≠∂𥮪∞∂µ ®©∂ºª $," ∑π∂´º™ª∫ ≥∞™¨µ∫∞µÆ ®µ´ ∫¨πΩ∞™¨ Æ∂ ª∂ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª
権∫∞ª¨ π¨Æ∞∫ªπ®ª∞∂µ π¨∏º∞π¨´ ®ª تª∑ 2º∑∑∂πª $," ™∂¥
3π∂º©≥¨∫Ø∂∂ª∞µÆ &∂ ª∂ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ≠ª¨π ≥∂ÆÆ∞µÆ ∞µ ≥∂™®ª¨
ªØ¨ ®∑∑≥∞™®©≥¨ 2º∑∑∂πª ©¿ /π∂´º™ª ∑®Æ¨
3¨™Øµ∞™®≥ ∫º∑∑∂πª %∂𠪨™Øµ∞™®≥ ∫º∑∑∂πª ®µ´ ∫¨πΩ∞™¨ π¨∏º¨∫ª∫ Æ∂ ª∂ $," "º∫ª∂¥¨π
2¨πΩ∞™¨ ∂µ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ≠ª¨π ≥∂ÆÆ∞µÆ ∞µ ≥∂™®ª¨ ªØ¨ ®∑∑≥∞™®©≥¨
2º∑∑∂πª ©¿ /π∂´º™ª ∑®Æ¨ ®µ´ ™Ø∂∂∫¨ ¨∞ªØ¨π Live Chat ∂π Create a service request 3∂
∂∑¨µ ® ∫¨πΩ∞™¨ π¨∏º¨∫ª ªØπ∂ºÆØ $," .µ≥∞µ¨ 2º∑∑∂πª ¿∂º ¥º∫ª Ø®Ω¨ ® Ω®≥∞´ ∫º∑∑∂πª
®Æ𨨥¨µª "∂µª®™ª ¿∂ºπ $," ∫®≥¨∫ π¨∑π¨∫¨µª®ª∞Ω¨ ≠∂π ´¨ª®∞≥∫ ®©∂ºª ∂©ª®∞µ∞µÆ ® Ω®≥∞´
∫º∑∑∂πª ®Æ𨨥¨µª ∂π æ∞ªØ ∏º¨∫ª∞∂µ∫ ®©∂ºª ¿∂ºπ ®™™∂ºµª
Note: #∂ µ∂ª π¨∏º¨∫ª ® ∫∑¨™∞≠∞™ ∫º∑∑∂πª π¨∑π¨∫¨µª®ª∞Ω¨ ºµ≥¨∫∫ ∂µ¨ Ø®∫ ®≥π¨®´¿ ©¨¨µ ®∫∫∞Ƶ¨´ ª∂
¿∂ºπ ∑®πª∞™º≥®π ∫¿∫ª¨¥ ∑π∂©≥¨¥
Your comments
8∂ºπ ∫ºÆƨ∫ª∞∂µ∫ æ∞≥≥ ب≥∑ º∫ ™∂µª∞µº¨ ª∂ ∞¥∑π∂Ω¨ ªØ¨ ®™™ºπ®™¿ ∂πÆ®µ∞¡®ª∞∂µ ®µ´ ∂Ω¨π®≥≥
∏º®≥∞ª¿ ∂≠ ªØ¨ º∫¨π ∑º©≥∞™®ª∞∂µ∫
/≥¨®∫¨ ∫¨µ´ ¿∂ºπ ∂∑∞µ∞∂µ ∂≠ ªØ∞∫ ´∂™º¥¨µª ª∂
6
Getting Started with VNX Installation Assistant for File/Unified 7.0

Preface

techpubcomments@EMC.com

Getting Started with VNX Installation Assistant for File/Unified 7.0

7

Preface

8

Getting Started with VNX Installation Assistant for File/Unified 7.0

   

1

Introduction

$," 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ∞∫ ® ∫ª®µ´ ®≥∂µ¨ æ∞¡®π´ ªØ®ª ™∂µ∫∂≥∞´®ª¨∫ ¥º≥ª∞∑≥¨ ≠ºµ™ª∞∂µ∫ π¨∏º∞π¨´ ≠∂π ∞µ∫ª®≥≥®ª∞∂µ

 

3Ø∞∫ ´∂™º¥¨µª ∞∫ ∑®πª ∂≠ ªØ¨ 5-7 ∞µ≠∂𥮪∞∂µ ∫¨ª ®µ´ ∞∫ ∞µª¨µ´¨´ ≠∂π º∫¨π∫ æØ∂ 段ª ª∂ ™∂µ≠∞Æºπ¨ ®µ´ ¥®µ®Æ¨ 5-7 º∫∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

3∂∑∞™∫ ∞µ™≥º´¨´ ®π¨

.Ω¨πΩ∞¨æ ∂µ ∑®Æ¨

(µª¨π∂∑¨π®©∞≥∞ª¿ ¥®ªπ∞ø ∂µ ∑®Æ¨

 

/π¨π¨∏º∞∫∞ª¨∫ ∂µ ∑®Æ¨

(µ∫ª®≥≥ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ∂µ ∑®Æ¨

 

5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ µ¨ªæ∂π≤ ™Ø¨™≤≥∞∫ª ∂µ ∑®Æ¨

1ºµ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ∂µ ∑®Æ¨

Getting Started with VNX Installation Assistant for File/Unified 7.0

9

Introduction Overview 3ب $," é 5-7㍷ (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨
Introduction
Overview
3ب $," é 5-7㍷ (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ∞∫ ® ∫ª®µ´ ®≥∂µ¨ æ∞¡®π´ ªØ®ª
™∂µ∫∂≥∞´®ª¨∫ ¥º≥ª∞∑≥¨ ≠ºµ™ª∞∂µ∫ π¨∏º∞π¨´ ≠∂π ∞µ∫ª®≥≥®ª∞∂µ ∫º™Ø ®∫ 5-7 ´∞∫™∂Ω¨π¿ ®µ´
∞µ∞ª∞®≥∞¡®ª∞∂µ ب®≥ªØ ™Ø¨™≤ ™∂µ≠∞ƺπ®ª∞∂µ ∂≠ "∂µªπ∂≥ 2ª®ª∞∂µ ®µ´ ©≥®´¨∫ ®µ´ ∑π∂´º™ª
π¨Æ∞∫ªπ®ª∞∂µ 3Ø∞∫ æ∞¡®π´ Ø®∫ ©¨¨µ ¨øª¨µ´¨´ ª∂ ∞µ™≥º´¨ ® ∫∞¥∑≥¨ ∞µª¨π≠®™¨ ≠∂π Ω®π∞∂º∫
™∂µ≠∞ƺπ®ª∞∂µ ª®∫≤∫ ª∂ ∫¨ª º∑ ªØ¨ 5-7 ≠∂π ∑π∂´º™ª∞∂µ 3ب 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π
%∞≥¨ 4µ∞≠∞¨´ ∞µ™≥º´¨∫ ® ∫∞¥∑≥¨ ∞µª¨π≠®™¨ ª∂ ∑π∂Ω∞∫∞∂µ ºµº∫¨´ ´∞∫≤∫ ™∂µ≠∞ƺπ¨ -%2 ®µ´ "(%2
®µ´ ∫¨ª º∑ ,/%2 ∫ª∂π®Æ¨ ≠∂π ,/%2 ∫º∑∑∂πª¨´ ∫¿∫ª¨¥∫ ∂µ≥¿
Note: (≠ ¿∂º 段ª ª∂ ™∂µ≠∞Æºπ¨ ªØ¨ (/Ω ®´´π¨∫∫¨∫ ≠∂π ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ "∂µªπ∂≥ 2ª®ª∞∂µ ®´´π¨∫∫
#-2 ∂π -3/ ∂π ≠∂π ªØ¨ #®ª® ,∂Ω¨π∫ #-2 ∂π -3/ º∫¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´
≠∂π ªØ¨ ∞µ∞ª∞®≥ ∞µ∫ª®≥≥®ª∞∂µ ®µ´ ªØ¨µ π¨≠¨π ª∂ "∂µ≠∞ƺπ∞µÆ ®µ´ ,®µ®Æ∞µÆ -¨ªæ∂π≤∞µÆ ∂µ 5-7 ª¨™Øµ∞™®≥
¥∂´º≥¨ ®µ´ $," 5-7 "∂¥¥®µ´ +∞µ¨ (µª¨π≠®™¨ 1¨≠¨π¨µ™¨ ≠∂π %∞≥¨ ª∂ ™∂¥∑≥¨ª¨ ªØ¨ (/Ω ®´´∞ª∞∂µ∫
"≥∞™≤ (µ∫ª®≥≥ ª∂ ∑¨π≠∂π¥ ©®∫∞™ ∫¿∫ª¨¥ ∫¨ªº∑ ∂≠ ® ≠®™ª∂π¿ ∞µ∫ª®≥≥¨´ ºµ™∂µ≠∞Æºπ¨´ 5-7
◆ 5-7 ´∞∫™∂Ω¨π¿ ®µ´ ∞µ∞ª∞®≥∞¡®ª∞∂µ
◆ '¨®≥ªØ ™Ø¨™≤
◆ "∂µ≠∞ƺπ®ª∞∂µ ∂≠ "∂µªπ∂≥ 2ª®ª∞∂µ ®µ´ ©≥®´¨∫
◆ "∂µ≠∞ƺπ¨ "∂µµ¨™ª'∂¥¨ ¨ ¥®∞≥ ∫º∑∑∂πª
"≥∞™≤ "∂µ≠∞Æºπ¨ ª∂
◆ /π∂Ω∞∫∞∂µ ∫ª∂π®Æ¨ º∫∞µÆ ¨ø∑π¨∫∫ ®µ´ ™º∫ª∂¥ ¥∂´¨
◆ "𨮪¨ ©®∫∞™ ®µ´ Ø∞ÆØ≥¿ ®Ω®∞≥®©≥¨ µ¨ªæ∂π≤ ´¨Ω∞™¨∫
◆ "𨮪¨ ®µ´ ®ªª®™Ø "(%2 ∫Ø®π¨∫
◆ "𨮪¨ -%2 ¨ø∑∂πª∫
◆ 2¨ª º∑ ,/%2
Note: 3Ø∞∫ ∂∑ª∞∂µ ∞∫ ®Ω®∞≥®©≥¨ ∂µ≥¿ ≠∂π ,/%2 ∫º∑∑∂πª¨´ ∫¿∫ª¨¥∫ 2¨≥¨™ª ªØ∞∫ ∂∑ª∞∂µ ∂µ≥¿ ∞≠ ¿∂º 段ª
ª∂ πºµ ,/%2 ®µ´ ªØ¨ ,/%2 ∞µ≠π®∫ªπº™ªºπ¨ ∞∫ ™∂µ≠∞Æºπ¨´ ∂µ ¿∂ºπ ∫¿∫ª¨¥ ∞µ ®´Ω®µ™¨ 1¨≠¨π ª∂ $,"
5-7 ,/%2 ∂Ω¨π %" ®µ´ ∞2"2( Ω +∞µºø "≥∞¨µª∫ /π∂´º™ª &º∞´¨ ª∂ ¥®µº®≥≥¿ ™∂µ≠∞ƺπ¨ ,/%2
Interoperability matrix
3®©≥¨ ∂µ ∑®Æ¨ ™∂ππ¨≥®ª¨∫ ªØ¨ 5-7 æ∞ªØ ªØ¨ π¨∫∑¨™ª∞Ω¨ 5-7 .$ ≠∂π %∞≥¨ Ω¨π∫∞∂µ∫ "≥∞¨µª
.2 ®µ´ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ Ω¨π∫∞∂µ∫
10
Getting Started with VNX Installation Assistant for File/Unified 7.0
Table 1. Interoperability matrix VNX hardware VNX5300 VNX5500 VNX5700 VNX7500 Prerequisites Wizard Storage
Table 1. Interoperability matrix VNX hardware VNX5300 VNX5500 VNX5700 VNX7500 Prerequisites Wizard Storage
Table 1. Interoperability matrix
VNX hardware
VNX5300
VNX5500
VNX5700
VNX7500
Prerequisites
Wizard
Storage Provisioning
Network Configuration
CIFS
NFS
Storage Provisioning Network Configuration CIFS NFS Client OS VNX Installation Assistant for File/Unified

Client OS

VNX Installation Assistant for File/Unified version

Windows XP, 2000, Vista

7.0.10.3 or later

Windows XP, 2000, Vista

7.0.10.3 or later

Windows XP, 2000, Vista

7.0.10.3 or later

Windows XP, 2000, Vista

7.0.10.3 or later

Prerequisites

Display settings must have a minimum of 256 colors (for Windows NT and Windows 2000).

Proper communication channel between the VNX, the interfaces, and the client must exist.

VNX must be provisioned to get the pool size.

Interfaces must be available to attach a share to the client.

Proper communication channel between the VNX, the interfaces, and the client must exist.

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.

VNX must be provisioned to get the pool size.

Interfaces must be available to attach a share to the client.

Proper communication channel between the VNX, the interfaces, and the client must exist.

between the VNX, the interfaces, and the client must exist. 11 Introduction VNX OE for File

11

Introduction

VNX OE for File

7.0.10.3 or later

7.0.10.3 or later

7.0.10.3 or later

7.0.10.3 or later

Note: 3ب 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ æ∞¡®π´ ´∂¨∫ µ∂ª πºµ ∂µ -3 ∫¨πΩ¨π∫

3®©≥¨ ∂µ ∑®Æ¨ ≥∞∫ª∫ ªØ¨ ∑π¨π¨∏º∞∫∞ª¨∫ ≠∂π ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

Table 2. Prerequisites for different wizards in VNX Installation Assistant

Operating system

Windows XP/2000/Vista

Windows XP/2000/Vista

Windows XP/2000/Vista

Windows XP/2000/Vista

Windows XP/2000/Vista Windows XP/2000/Vista Windows XP/2000/Vista Windows XP/2000/Vista Prerequisites

Prerequisites

12 Wizard Operating system MPFS Windows XP/2000/Vista ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆

12

12 Wizard Operating system MPFS Windows XP/2000/Vista ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ Getting
Wizard Operating system MPFS Windows XP/2000/Vista ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆
Wizard
Operating system
MPFS
Windows XP/2000/Vista

Getting Started with VNX Installation Assistant for File/Unified 7.0

Started with VNX Installation Assistant for File/Unified 7.0 VNX must be provisioned so that at least

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.

Interfaces must be available to attach a share to the client.

Proper communication channel between the VNX, the interfaces, the computer running VNX Instal- lation Assistant for File/Unified, and MPFS Linux hosts must exist.

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.

For iSCSI configuration, the iSCSI package must be installed on the client.

Introduction

Table 2. Prerequisites for different wizards in VNX Installation Assistant (continued)

Prerequisites
Prerequisites

Install the VNX Installation Assistant for File/Unified

!¨≠∂π¨ ∞µ∫ª®≥≥∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ Ω¨π∞≠¿ ªØ®ª

™™¨∫∫ ª∂ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ®ª تª∑ 2º∑∑∂πª $," ™∂¥ ∂π ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ 3∂∂≥©∂ø "# ∑π¨≠¨ππ¨´ ∞∫ ®Ω®∞≥®©≥¨

6∞µ´∂æ∫ ©®∫¨´ ™≥∞¨µª ™∂¥∑ºª¨π ∞∫ ∂µ ªØ¨ ∫®¥¨ ∫º©µ¨ª ™º∫ª∂¥¨π µ¨ªæ∂π≤ ®∫ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ

3ب ™∂¥∑ºª¨π ¥º∫ª Ø®Ω¨ ®ª ≥¨®∫ª ,! ∂≠ ≠𨨠∫∑®™¨ (µª¨πµ¨ª ™∂µµ¨™ª∞Ω∞ª¿ ∞∫ π¨™∂¥¥¨µ´¨´

3∂ ∂©ª®∞µ ®µ´ ∞µ∫ª®≥≥ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

Note: .µ ¿∂ºπ ™∂¥∑ºª¨π ´∞∫®©≥¨ ®µ¿ ≠∞π¨æ®≥≥ ∫∂≠ªæ®π¨ ∑∂∑ º∑ ©≥∂™≤¨π∫ Ω∞πªº®≥ ∑π∞Ω®ª¨ µ¨ªæ∂π≤ 5/- ∞µª¨π≠®™¨∫ ®µ´ 5,æ®π¨ µ¨ªæ∂π≤ ∞µª¨π≠®™¨∫ ©¨≠∂π¨ πºµµ∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

#∂æµ≥∂®´ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ≠π∂¥ ® ≥∞µ≤ ∂µ ªØ¨ Tools ∑®Æ¨ ∂≠ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ (≠ ¿∂º ´∂ µ∂ª Ø®Ω¨ ®™™¨∫∫ ª∂ ªØ¨ 権∫∞ª¨ ∞µ∫¨πª ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ 3∂∂≥©∂ø "# ∞µª∂ ¿∂ºπ ™∂¥∑ºª¨π

(µ ªØ¨ Getting Started with your EMC VNX Installation æ∞µ´∂æ ™≥∞™≤ VNX Installation

Assistant for File/Unified ª∂ ∞µ∫ª®≥≥ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ∂µ ¿∂ºπ ™∂¥∑ºª¨π %∞ƺπ¨ ∂µ ∑®Æ¨ ∫Ø∂æ∫ ªØ¨ ∞µ∫ª®≥≥®ª∞∂µ ∑π∂™¨∫∫ ≠∂π 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ≠π∂¥ 5-7 (µ∫ª®≥≥®ª∞∂µ 3∂∂≥©∂ø "#

≠∂π %∞≥¨ 4µ∞≠∞¨´ ≠π∂¥ 5-7 (µ∫ª®≥≥®ª∞∂µ 3∂∂≥©∂ø "#

Introduction

Network Load VNX Installation Toolbox CD in either a laptop or PC tower. VNX-000065 EMC®
Network
Load VNX Installation Toolbox CD in
either a laptop or PC tower.
VNX-000065
EMC®
Celerra®
NS40
System
Tutorial
CSA
Installation
P/N
nnn-nnn-nnn-A0n
CD EMC
Copyright©
2nnn
Corporation
All
Rights
Reserved
This
CD
contains
intellectual
property
of
EMC
Corporation
the or Use
licensed
EMC
Corporation
of of this
from
third
parties.
and the
intellectual
is herein
to the
property
contained
is CD
expressly
limited
to License
terms
and
conditions
the
Agreement.

Figure 1. Installing VNX Installation Assistant for File/Unified

3ب $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ®ª تª∑ 2º∑∑∂πª $," ™∂¥ ∑π∂Ω∞´¨∫ ¥∂π¨ ∞µ≠∂𥮪∞∂µ

VNX Installation Assistant for File/Unified network checklist

!¨≠∂π¨ ¿∂º πºµ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ¨µ∫ºπ¨ ªØ®ª

8∂ºπ 5-7 ∞∫ ∑∂æ¨π¨´ º∑ 3ب ∞µ∫ª®≥≥®ª∞∂µ ƺ∞´¨ ∑π∂Ω∞´¨∫ ®´´∞ª∞∂µ®≥ ∞µ≠∂𥮪∞∂µ

8∂ºπ 5-7 ∞∫ ™∂µµ¨™ª¨´ ª∂ ªØ¨ µ¨ªæ∂π≤ 3ب ∞µ∫ª®≥≥®ª∞∂µ ƺ∞´¨ ∑π∂Ω∞´¨∫ ®´´∞ª∞∂µ®≥ ∞µ≠∂𥮪∞∂µ

8∂ºπ 5-7 ®µ´ ¿∂ºπ 6∞µ´∂æ∫ ™≥∞¨µª ®π¨ ∂µ ªØ¨ ∫®¥¨ ∑Ø¿∫∞™®≥ + -

µ¿ ¨ø∞∫ª∞µÆ ≠∞π¨æ®≥≥ ∑∂∑ º∑ ©≥∂™≤¨π∫ ®µ´ 5/- ®π¨ ´∞∫®©≥¨´

"∞∫™∂ 2¨™ºπ∞ª¿ ®Æ¨µª ∞∫ ªºπµ¨´ ∂≠≠ ∂µ ªØ¨ ™≥∞¨µª /"

(≠ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ™®µµ∂ª ´¨ª¨™ª ªØ¨ , " ®´´π¨∫∫ ∂≠ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ¨µ∫ºπ¨ ªØ®ª ¿∂º ∫¨≥¨™ª ªØ¨ ™∂π𨙪 + - µ¨ªæ∂π≤ ∞µª¨π≠®™¨ ™®π´ ∂µ æØ∞™Ø ¿∂º 段ª ª∂ ∫¨®π™Ø ≠∂π ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ

(≠ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ™®µµ∂ª ´¨ª¨™ª ªØ¨ , " ®´´π¨∫∫ ∂≠ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ∑∂æ¨π ™¿™≥¨ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ®µ´ ™≥∞™≤ Retry Search

Note: (ª ª®≤¨∫ ∫¨Ω¨π®≥ ¥∞µºª¨∫ ª∂ π¨©∂∂ª ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ 8∂º ™®µ ∑∞µÆ ªØ¨ (/ ®´´π¨∫∫ ∂≠ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ª∂ ¥®≤¨ ∫ºπ¨ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ∞∫ π¨©∂∂ª¨´ ©¨≠∂π¨ ¿∂º ™∂µª∞µº¨

(≠ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ∫ª∞≥≥ ´∂¨∫ µ∂ª π¨∫∑∂µ´ º∫¨ ªØ¨ ∫º∑∑≥∞¨´ ™π∂∫∫ ∂Ω¨π ™®©≥¨ / - ®µ´ ≥®©¨≥¨´ 2¨πΩ∞™¨ + - "®©≥¨ ∫∫¨¥©≥¿ ª∂ ™∂µµ¨™ª ª∂ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ

VNX Installation Assistant for File/Unified network checklist

13

Introduction

   
 

´∞𨙪≥¿ ≠π∂¥ ªØ¨ ™≥∞¨µª /" πºµµ∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ®µ´ ∑¨π≠∂π¥ ªØ¨ ≠∂≥≥∂æ∞µÆ

® #∞∫™∂µµ¨™ª ªØ¨ ¨øª¨πµ®≥ µ¨ªæ∂π≤ ™®©≥¨ ª∂ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ 3Ø∞∫ ™®©≥¨ ∞∫ ≥®©¨≥¨´ ,&,3 ®∫ ∫Ø∂æµ ∞µ ªØ¨ ≠∂≥≥∂æ∞µÆ ≠∞ƺπ¨

 
 
 

© "∂µ≠∞Æºπ¨ ªØ¨ 6∞µ´∂æ∫ ™≥∞¨µª æ∞ªØ ® ∫ª®ª∞™ (/ ®´´π¨∫∫ ∂µ ªØ¨ ∫®¥¨ ≥∂Æ∞™®≥ µ¨ªæ∂π≤ ©¨∞µÆ º∫¨´ ©¿ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ º∫∞µÆ ® µ¨ª¥®∫≤ ∂≠ ®µ´ µ∂ ´¨≠®º≥ª Æ®ª¨æ®¿ ®´´π¨∫∫

4∫¨ ® ∫ªπ®∞Æت ªØπ∂ºÆØ ∂π ™π∂∫∫∂Ω¨π $ªØ¨πµ¨ª ™®©≥¨ ª∂ ™∂µµ¨™ª ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ™≥∞¨µª ´∞𨙪≥¿ ª∂ ªØ¨ ¨øª¨πµ®≥ ∑∂πª ∂µ ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ≥®©¨≥¨´ ®∫ ¨ªØ ®∫ ∫Ø∂æµ ∞µ ªØ¨ ≠∂≥≥∂æ∞µÆ ≠∞ƺπ¨

 
 
 

´

,®≤¨ ∫ºπ¨ ª∂ ´∞∫®©≥¨ æ∞π¨≥¨∫∫ ™∂¥¥ºµ∞™®ª∞∂µ ®µ¿ ≠∞π¨æ®≥≥ ∫∂≠ªæ®π¨ ∑∂∑ º∑ ©≥∂™≤¨π∫ 5/- ∞µª¨π≠®™¨∫ ®µ´ 5,æ®π¨ µ¨ªæ∂π≤ ∞µª¨π≠®™¨∫

¨

1¨©∂∂ª ªØ¨ "∂µªπ∂≥ 2ª®ª∞∂µ ®µ´ æ®∞ª ≠∂π ªØ¨ π¨©∂∂ª ª∂ ™∂¥∑≥¨ª¨

1¨∫ª®πª ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ æ∞¡®π´ ®µ´ ™≥∞™≤ Next ∂µ ªØ¨ Welcome ∑®Æ¨ ª∂ ∞µ∞ª∞®ª¨ ªØ¨ ©π∂®´™®∫ª ®µ´ ´∞∫™∂Ω¨π¿ ∑π∂™¨∫∫ ªØ¨µ ™∂µª∞µº¨ æ∞ªØ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ™∂µ≠∞ƺπ®ª∞∂µ

 

Run the VNX Installation Assistant for File/Unified

3∂ πºµ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

 

#∂º©≥¨ ™≥∞™≤ ªØ¨ VNX Installation Assistant for File/Unified ∫Ø∂πª™ºª ∂µ ªØ¨ ´¨∫≤ª∂∑ ∂π Æ∂ ª∂ " /π∂Æπ®¥%∞≥¨∫ $," 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ∫ª®πªº∑ ≥®ºµ™Ø ©®ª 3ب 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ƺ∞´¨∫ ¿∂º ªØπ∂ºÆØ ªØ¨ 𨥮∞µ∞µÆ ∫ª¨∑∫

"≥∞™≤ Install ª∂ ™∂µ≠∞Æºπ¨ ® ≠®™ª∂π¿ ∞µ∫ª®≥≥¨´ 5-7

 

$µ∫ºπ¨ ª∂ π¨Æ∞∫ª¨π ¿∂ºπ ∫¿∫ª¨¥ º∫∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ®≠ª¨π ªØ¨ ∞µ∞ª∞®≥ ∫¿∫ª¨¥ ∞µ∫ª®≥≥®ª∞∂µ ®µ´ ∑π¨™∂µ≠∞ƺπ®ª∞∂µ Ø®∫ ©¨¨µ ™∂¥∑≥¨ª¨´

"≥∞™≤ Configure ª∂ ∑π∂Ω∞∫∞∂µ ∫ª∂π®Æ¨ ®µ´ ∫¨ªº∑ ªØ¨ 5-7 ≠∂π ∑π∂´º™ª∞∂µ

14

Getting Started with VNX Installation Assistant for File/Unified 7.0

 

Introduction

&∂ ª∂ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ®ª تª∑ 2º∑∑∂πª $," ™∂¥ ≠∂π ¥∂π¨ ∞µ≠∂𥮪∞∂µ ª ªØ¨ ¨µ´ ∂≠ ¨®™Ø ™∂µ≠∞ƺπ®ª∞∂µ ¿∂ºπ ∫¿∫ª¨¥ æ∞≥≥ ©¨ º∫®©≥¨ ®µ´ π¨®´¿ ≠∂π ∑π∂´º™ª∞∂µ

≠ª¨π ¿∂º π¨Æ∞∫ª¨π ¿∂ºπ 5-7 ∫¿∫ª¨¥ ¿∂º ¥º∫ª ™∂µ≠∞Æºπ¨ ªØ¨ ∫¿∫ª¨¥ ≠∂π ∑π∂´º™ª∞∂µ 3Ø¨π¨ ®π¨ ∫¨Ω¨π®≥ ™∂¥¥∂µ ∞¥∑≥¨¥¨µª®ª∞∂µ∫ ®Ω®∞≥®©≥¨ ªØπ∂ºÆØ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ∂π

¿∂º ™®µ ™∂µ≠∞Æºπ¨ ¿∂ºπ ∫¿∫ª¨¥ ©¿ º∫∞µÆ ªØ¨ $," 4µ∞∫∑بπ¨∫∂≠ªæ®π¨

"∂¥¥∂µ ∞¥∑≥¨¥¨µª®ª∞∂µ∫

é

"𨮪¨ "(%2 ∫Ø®π¨∫

"𨮪¨ -%2 ¨ø∑∂πª∫

2¨ª º∑ ,/%2 ≠∂π ,/%2 ∫º∑∑∂πª¨´ ∫¿∫ª¨¥∫

/¨π≠∂π¥ ™∂¥¥∂µ ∑∂∫ª 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ª®∫≤∫

Note: .µ ® 6∞µ´∂æ∫ 5∞∫ª® ∫¿∫ª¨¥ ∞≠ ¿∂º µ¨¨´ ª∂ º∫¨ "(%2 æ∞¡®π´ ¿∂º ¥º∫ª ´∞∫®©≥¨ 4∫¨π ™™¨∫∫ "∂µªπ∂≥

3ب $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ®ª تª∑ 2º∑∑∂πª $," ™∂¥ ∑π∂Ω∞´¨∫ ¥∂π¨ ∞µ≠∂𥮪∞∂µ

What Next?

8∂º ®π¨ µ∂æ π¨®´¿ ª∂ ´∂ ªØ¨ ≠∂≥≥∂æ∞µÆ

(µ∫ª®≥≥ ®µ´ ™∂µ≠∞ƺπ¨ $," 2¨™ºπ¨ 1¨¥∂ª¨ 2º∑∑∂πª $212 (/ "≥∞¨µª 4∫¨ ªØ¨ Initialize and register VNX and configure ESRS ≥∞µ≤ ºµ´¨π 5-7 ª®∫≤∫ ®µ´ ©¨ ∫ºπ¨ ª∂ ∫¨≥¨™ª ªØ¨ $212 ∂∑ª∞∂µ æبµ ∑π∂¥∑ª¨´

ªª®™Ø ∂µ¨ ∂π ¥∂π¨ ∫¨πΩ¨π∫ ª∂ ¿∂ºπ 5-7 4∫¨ ªØ¨ Attach server ≥∞µ≤ ºµ´¨π 2¨π٨𠪮∫≤∫ ∂µ ªØ¨ ∫º∑∑∂πª 権∫∞ª¨ ª∂ ƨµ¨π®ª¨ ∫ª¨∑ ©¿ ∫ª¨∑ ∞µ∫ªπº™ª∞∂µ∫ ≠∂𠮪ª®™Ø∞µÆ ® ∫¨πΩ¨π

Run the VNX Installation Assistant for File/Unified

15

Introduction

16

Getting Started with VNX Installation Assistant for File/Unified 7.0

   

2

Troubleshooting

∫ ∑®πª ∂≠ ®µ ¨≠≠∂πª ª∂ ™∂µª∞µº∂º∫≥¿ ∞¥∑π∂Ω¨ ®µ´ ¨µØ®µ™¨ ªØ¨ ∑¨π≠∂π¥®µ™¨ ®µ´ ™®∑®©∞≥∞ª∞¨∫ ∂≠ ∞ª∫ ∑π∂´º™ª ≥∞µ¨∫ $," ∑¨π∞∂´∞™®≥≥¿ π¨≥¨®∫¨∫ µ¨æ Ω¨π∫∞∂µ∫ ∂≠ ∞ª∫ Ø®π´æ®π¨ ®µ´ ∫∂≠ªæ®π¨ 3بπ¨≠∂π¨ ∫∂¥¨ ≠ºµ™ª∞∂µ∫ ´¨∫™π∞©¨´ ∞µ ªØ∞∫ ´∂™º¥¨µª ¥®¿ µ∂ª ©¨ ∫º∑∑∂πª¨´ ©¿ ®≥≥ Ω¨π∫∞∂µ∫ ∂≠ ªØ¨ ∫∂≠ªæ®π¨ ∂π Ø®π´æ®π¨ ™ºπ𨵪≥¿ ∞µ º∫¨ %∂π ªØ¨ ¥∂∫ª º∑ ª∂ ´®ª¨ ∞µ≠∂𥮪∞∂µ ∂µ ∑π∂´º™ª ≠¨®ªºπ¨∫ π¨≠¨π ª∂ ¿∂ºπ ∑π∂´º™ª π¨≥¨®∫¨ µ∂ª¨∫

 

(≠ ® ∑π∂´º™ª ´∂¨∫ µ∂ª ≠ºµ™ª∞∂µ ∑π∂∑¨π≥¿ ∂π ´∂¨∫ µ∂ª ≠ºµ™ª∞∂µ ®∫ ´¨∫™π∞©¨´ ∞µ ªØ∞∫ ´∂™º¥¨µª ™∂µª®™ª ¿∂ºπ $," "º∫ª∂¥¨π 2º∑∑∂πª 1¨∑π¨∫¨µª®ª∞Ω¨

/π∂©≥¨¥ 1¨∫∂≥ºª∞∂µ 1∂®´¥®∑ ≠∂π 5-7 ™∂µª®∞µ∫ ®´´∞ª∞∂µ®≥ ∞µ≠∂𥮪∞∂µ ®©∂ºª º∫∞µÆ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ®µ´ π¨∫∂≥Ω∞µÆ ∑π∂©≥¨¥∫

3∂∑∞™∫ ∞µ™≥º´¨´ ®π¨

$," $ +®© (µª¨π∂∑¨π®©∞≥∞ª¿ -®Ω∞Æ®ª∂π ∂µ ∑®Æ¨

 

*µ∂æµ ∑π∂©≥¨¥∫ ®µ´ ≥∞¥∞ª®ª∞∂µ∫ ∂µ ∑®Æ¨

"Ø®µÆ¨ ® Ω®≥º¨ ∫¨ª æ∞ªØ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ∂µ ∑®Æ¨

$," 3π®∞µ∞µÆ ®µ´ /π∂≠¨∫∫∞∂µ®≥ 2¨πΩ∞™¨∫ ∂µ ∑®Æ¨

Getting Started with VNX Installation Assistant for File/Unified 7.0

17

18 EMC E-Lab Interoperability Navigator Known problems and limitations Attaching a CIFS share fails Symptom

18

18 EMC E-Lab Interoperability Navigator Known problems and limitations Attaching a CIFS share fails Symptom Cause

EMC E-Lab Interoperability Navigator

Known problems and limitations

Attaching a CIFS share fails

Symptom

Cause

Solution

Symptom

Cause

Solution

service nas start

Solution Symptom Cause Solution service nas start Troubleshooting 3ب $," $ +®© ㍷
Solution Symptom Cause Solution service nas start Troubleshooting 3ب $," $ +®© ㍷

Troubleshooting

3ب $," $ +®© (µª¨π∂∑¨π®©∞≥∞ª¿ -®Ω∞Æ®ª∂π ∞∫ ® ∫¨®π™Ø®©≥¨ 権 ©®∫¨´ ®∑∑≥∞™®ª∞∂µ ªØ®ª ∑π∂Ω∞´¨∫ ®™™¨∫∫ ª∂ $," ∞µª¨π∂∑¨π®©∞≥∞ª¿ ∫º∑∑∂πª ¥®ªπ∞™¨∫ (ª ∞∫ ®Ω®∞≥®©≥¨ ®ª تª∑ 2º∑∑∂πª $," ™∂¥ ≠ª¨π ≥∂ÆÆ∞µÆ ∞µ ª∂ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ≥∂™®ª¨ ªØ¨ ®∑∑≥∞™®©≥¨ 2º∑∑∂πª ©¿ /π∂´º™ª ∑®Æ¨ ≠∞µ´ Tools ®µ´ ™≥∞™≤ E-Lab Interoperability Navigator

3Ø∞∫ ∫¨™ª∞∂µ ≥∞∫ª∫ ªØ¨ ≤µ∂æµ ∑π∂©≥¨¥∫ ®µ´ ≥∞¥∞ª®ª∞∂µ∫ ≠∂π ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

Attaching a CIFS share may fail when not using the first primary blade.

VNX Installation Assistant for File/Unified only sets up the DNS for the first primary blade.

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.

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

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.

Log in as root on the Control Station and at the command line, type:

Getting Started with VNX Installation Assistant for File/Unified 7.0

on the Control Station and at the command line, type: Getting Started with VNX Installation Assistant
CIFS server creation fails Symptom Cause Solution 1. 2. where: $ where: $ CIFS server
CIFS server creation fails Symptom Cause Solution 1. 2. where: $ where: $ CIFS server
CIFS server creation fails
Symptom
Cause
Solution
1.
2.
where:
$
where:
$
CIFS server join fails
Symptom
Cause
where: $ where: $ CIFS server join fails Symptom Cause 19 Troubleshooting CIFS server creation fails
where: $ where: $ CIFS server join fails Symptom Cause 19 Troubleshooting CIFS server creation fails
where: $ where: $ CIFS server join fails Symptom Cause 19 Troubleshooting CIFS server creation fails

19

Troubleshooting

CIFS server creation fails because the CIFS server join with the domain fails.

One possible reason can be that the default gateway is not set up for a blade.

Set up a default gateway before using the CIFS server create and attach:

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.

When the interface is created, run the CLI command:

$ server_route server_2 -add default <gateway>

<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

1 = the gateway address.

To verify that the default gateway was added, type:

server_route server_2 -1

CIFS server join fails if there is clock skew between the Data Mover and the
CIFS server join fails if there is clock skew between the Data Mover and the domain controllers.
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.
for File/Unified does not provide an option to add an NTP server to the domain controller.

Known problems and limitations

20 Solution ◆ ◆ Symptom Cause Solution Troubleshooting Create an NTP server for the Data

20

20 Solution ◆ ◆ Symptom Cause Solution Troubleshooting Create an NTP server for the Data Mover

Solution

Symptom

Cause

Solution

20 Solution ◆ ◆ Symptom Cause Solution Troubleshooting Create an NTP server for the Data Mover
20 Solution ◆ ◆ Symptom Cause Solution Troubleshooting Create an NTP server for the Data Mover

Troubleshooting

Create an NTP server for the Data Mover from the Unisphere. This option is available
Create an NTP server for the Data Mover from the Unisphere. This option is available

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.

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.

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.

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.

Getting Started with VNX Installation Assistant for File/Unified 7.0

screen accepts server names up to 63 characters. Getting Started with VNX Installation Assistant for File/Unified
Symptom ◆ ◆ Cause 21 Troubleshooting VNX Installation Assistant for File/Unified fails to complete

Symptom

Cause

Symptom ◆ ◆ Cause 21 Troubleshooting VNX Installation Assistant for File/Unified fails to complete
Symptom ◆ ◆ Cause 21 Troubleshooting VNX Installation Assistant for File/Unified fails to complete
Symptom ◆ ◆ Cause 21 Troubleshooting VNX Installation Assistant for File/Unified fails to complete

21

Troubleshooting

VNX Installation Assistant for File/Unified fails to complete configuration

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.

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.

Assistant for File/Unified wizard because the default gateway IP address is 10.113.254.254. Known problems and limitations

Known problems and limitations

22 Solution 1. Preferred workaround: a.   # b.   # should be set to

22

22 Solution 1. Preferred workaround: a.   # b.   # should be set to a

Solution

1. Preferred workaround:

a.

 

#

b.

 

#

should be set to a new IP address.

#

c.

 

#

d.

 

#

#

e.

f.

g.

2. Alternative workaround:

a.

b.

c.

f. g. 2. Alternative workaround: a. b. c. Troubleshooting With the VNX Installation Assistant
f. g. 2. Alternative workaround: a. b. c. Troubleshooting With the VNX Installation Assistant

Troubleshooting

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

Verify that SPA's IP address was changed and not SPB:

/nas/sbin/navicli -h <spa> networkadmin -get

/nas/sbin/navicli -h <spb> networkadmin -get

should still be set with an internal IP address.

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

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

Edit /etc/hosts and /nas/site/sp_info files to reflect the correct internal IP address for SPA.

Verify network admin information on SPs once again.

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.

Connect the VNX Installation Assistant for File/Unified client directly to the Control Station by using a LAN cable.

Reconfigure the default gateway IP on the Windows client to something like 10.113.0.1.

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

Getting Started with VNX Installation Assistant for File/Unified 7.0

the Control Station back to a pre-VNX Installation Getting Started with VNX Installation Assistant for File/Unified
d. Symptom Cause Solution The CD use ◆ ◆ ◆ Be the but 23

d.

Symptom

Cause

Solution

The

CD

use

Be

the

but

CD use ◆ ◆ ◆ Be the but 23 Troubleshooting Assistant for File/Unified configured
CD use ◆ ◆ ◆ Be the but 23 Troubleshooting Assistant for File/Unified configured
CD use ◆ ◆ ◆ Be the but 23 Troubleshooting Assistant for File/Unified configured

23

Troubleshooting

Assistant for File/Unified configured state. Rerun the VNX Installation Assistant process.
Assistant for File/Unified configured state. Rerun the VNX Installation Assistant process.

Assistant for File/Unified configured state.

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.

The CSA version and the Celerra Software version are not compatible.

VNX Installation Assistant for File/Unified wizard is available on the VNX Installation Toolbox

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,

only the first three fields of the NAS version. Also, note:

The CSA cannot install multiple versions of the wizard on a given client.

You cannot upgrade from one version of the CSA to another.

To upgrade, uninstall the existing CSA application and then install the new CSA version.

aware that CSA versions 5.5.30 and 5.5.31 do not perform version-checking, which means that

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,

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.

Celerra model releases. The following compatibility statements can be made at this time. Known problems and

Known problems and limitations

24 Troubleshooting NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only,

24

24 Troubleshooting NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only, and
24 Troubleshooting NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only, and
24 Troubleshooting NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only, and
24 Troubleshooting NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only, and
24 Troubleshooting NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only, and

Troubleshooting

NAS 5.5 family: ◆ CSA 5.5.30 is compatible with NAS version 5.5.30 only, and not
NAS 5.5 family:
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).
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).
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).
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.
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:
CSA 5.6.36 is compatible with NAS versions 5.6.36 only, and not with any other NAS versions
(provides pop-up message).
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.
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.

Getting Started with VNX Installation Assistant for File/Unified 7.0

Check process that prevents successful configuration. Getting Started with VNX Installation Assistant for File/Unified 7.0
  ◆ ◆ ◆ ◆ Symptom Cause ◆ ◆ Solution 1. 2. 3. 4. link.
 

Symptom

Cause

Solution

1.

2.

3.

4.

link.

iSCSI LUN Attach fails

Symptom

Cause

3. 4. link. iSCSI LUN Attach fails Symptom Cause 25 Troubleshooting CSA 5.6.39 is compatible with
3. 4. link. iSCSI LUN Attach fails Symptom Cause 25 Troubleshooting CSA 5.6.39 is compatible with
3. 4. link. iSCSI LUN Attach fails Symptom Cause 25 Troubleshooting CSA 5.6.39 is compatible with

25

Troubleshooting

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

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

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

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.

The user account control is enabled on the Windows Vista computer.

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.

On Windows Vista, click Start and go to the Control Panel, then click User Accounts.

On the Make changes to your user account page, click the Turn User Account Control on or off

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.

Restart your computer and retry attaching an iSCSI LUN to the local computer from VNX In- stallation Assistant for File/Unified.

While creating a new iSCSI LUN and attaching it to a local host, the iSCSI attach fails with an error message :

Disk not found

The operating system of the host does not support dynamic search of iSCSI LUN and needs a reboot to detect the new iSCSI LUN.

Known problems and limitations

not support dynamic search of iSCSI LUN and needs a reboot to detect the new iSCSI
26 Solution   1. 2. 3. 4. 5. 6. 7. Symptom Cause Solution   1.

26

26 Solution   1. 2. 3. 4. 5. 6. 7. Symptom Cause Solution   1.

Solution

 

1.

2.

3.

4.

5.

6.

7.

Symptom

Cause

Solution

 

1.

2.

3.

4.

5.

MPFS client configuration on iSCSI host fails

Symptom

Cause

client configuration on iSCSI host fails Symptom Cause Troubleshooting Close all the applications and reboot the
client configuration on iSCSI host fails Symptom Cause Troubleshooting Close all the applications and reboot the

Troubleshooting

Close all the applications and reboot the host.

Launch the VNX Installation Assistant for File/Unified and log in to your VNX.

On the Configuration wizards page, select Create/Attach iSCSI LUN.

On the iSCSI Create and Attach page, select Attach a host to an existing iSCSI LUN.

On Attach an iSCSI LUN page, select Local Host.

Select the blade name for the iSCSI Target from the available list.

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

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.

Before working on the Windows 2008 client machine, go to command prompt, type diskpart, and then press Enter.

On the DISKPART prompt, type SAN and press Enter to see the current SAN policy on the machine.

If Online All is displayed then iSCSI LUN create and attach will work as desired on the VNX Installation Assistant for File/Unified.

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.

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 fails to complete the MPFS client configuration on iSCSI host. The iSCSI service is
MPFS fails to complete the MPFS client configuration on iSCSI host.
The iSCSI service is not running on the host, or the local mount directory to create is under
a read-only directory.

Getting Started with VNX Installation Assistant for File/Unified 7.0

directory to create is under a read-only directory. Getting Started with VNX Installation Assistant for File/Unified
Solution 1. 2. 3. Symptom Cause Solution Symptom Cause Solution 1. 2. 3. 27

Solution

1.

2.

3.

Symptom

Cause

Solution

Symptom

Cause

Solution

1.

2.

3.

Symptom Cause Solution 1. 2. 3. 27 Troubleshooting Run the iSCSI status command to check if
Symptom Cause Solution 1. 2. 3. 27 Troubleshooting Run the iSCSI status command to check if
Symptom Cause Solution 1. 2. 3. 27 Troubleshooting Run the iSCSI status command to check if

27

Troubleshooting

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.

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.

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.

MPFS fails to add the Linux host

MPFS fails to add the Linux host, an error appears:

MPFS does not support the kernel of this host

The MPFS client software does not support the kernel of this host.

The MPFS client support matrix is listed in the file host_support.properties, which is under <CSA installation directory>\startup\mpfs.

The format of the support host value is OSname-KernelVersion-CpuType. The user can get the host’s 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.

Username or password is not correct, or the default SSH server installations are config- ured to refuse the authentication password.

Type the correct username and password on the MPFS Add Hosts page, and add the hosts again.

If the login still fails, then the default SSH server installations may be configured to decline the authentication type password.

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

SSH daemon to re-read this configuration. For example, run: /etc/init.d/sshd restart Known problems and limitations

Known problems and limitations

28 Problem reporting Symptom CSA fails to complete successfully. Cause Unknown. Solution   From

28

28 Problem reporting Symptom CSA fails to complete successfully. Cause Unknown. Solution   From

Problem reporting

Symptom

CSA fails to complete successfully.

Cause

Unknown.

Solution

 

From the client PC:

Provisioning fails

Symptom

Provisioning fails with an error:

Cause

Solution

Symptom

On the Welcome screen, user is prompted:

Cause

On the Welcome screen, user is prompted: Cause Troubleshooting When reporting problems with CSA that
On the Welcome screen, user is prompted: Cause Troubleshooting When reporting problems with CSA that

Troubleshooting

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:

Log file from C:\Program Files\EMC\CSA\startup\startup_wiz.log file.

All the contents of directory C:\Program Files\EMC\CSA\startup\test.

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.

Unable to establish communication with <IP address>

The connectivity between the EMC VNX for Block system and the Control Station is lost.

Check the cable connection between VNX for Block system and Control Station.

Resume VNX Installation Assistant for File/Unified

Enter the password for this VNX If the user runs VNX Installation Assistant for File/Unified,
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.

Getting Started with VNX Installation Assistant for File/Unified 7.0

from the point where it was discontinued. Getting Started with VNX Installation Assistant for File/Unified 7.0
Solution Welcome Symptom Cause Solution clar_r10. Symptom 29 Troubleshooting When the VNX Installation

Solution

Welcome

Symptom

Cause

Solution

clar_r10.

Symptom

Welcome Symptom Cause Solution clar_r10. Symptom 29 Troubleshooting When the VNX Installation Assistant for
Welcome Symptom Cause Solution clar_r10. Symptom 29 Troubleshooting When the VNX Installation Assistant for
Welcome Symptom Cause Solution clar_r10. Symptom 29 Troubleshooting When the VNX Installation Assistant for

29

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

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:

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

MPFS needs to create MPFS storage pools from the system defined pools clar_r5_performance, clar_r6, or clar_r10 for the MPFS initialization.

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

Unrecoverable VNX Installation Assistant for File/Unified errors

Unrecoverable VNX Installation Assistant for File/Unified errors that prevent completion of VNX Installation Assistant for

Unrecoverable VNX Installation Assistant for File/Unified errors that prevent completion of VNX Installation Assistant for File/Unified configuration process.

Known problems and limitations

prevent completion of VNX Installation Assistant for File/Unified configuration process. Known problems and limitations
30 Cause Troubleshooting Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that

30

30 Cause Troubleshooting Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that

Cause

30 Cause Troubleshooting Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that
30 Cause Troubleshooting Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that

Troubleshooting

Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that need to be reversed.

Inadvertent mistakes made during VNX Installation Assistant for File/Unified configuration that need to be reversed.

Getting Started with VNX Installation Assistant for File/Unified 7.0

File/Unified configuration that need to be reversed. Getting Started with VNX Installation Assistant for File/Unified 7.0
Solution 1. 2. 3. 4. 5. folder. 31 Troubleshooting Perform the following steps to set

Solution

Solution 1. 2. 3. 4. 5.

1.

2.

3.

4.

5.

Solution 1. 2. 3. 4. 5. folder. 31 Troubleshooting Perform the following steps to set the
Solution 1. 2. 3. 4. 5. folder. 31 Troubleshooting Perform the following steps to set the

folder.

Solution 1. 2. 3. 4. 5. folder. 31 Troubleshooting Perform the following steps to set the

31

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.

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.

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 director y. If a copy cannot be downloaded, contact the EMC Support and reference the NAS version involved.

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.

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/

Remove any extra or unwanted entries for the Control Station hostname and external IP ad-

Known problems and limitations

32 6.   # # # 7. 8. 9. 10. Troubleshooting dress from the /etc/hosts

32

32 6.   # # # 7. 8. 9. 10. Troubleshooting dress from the /etc/hosts (by

6.

 

#

#

#

7.

8.

9.

10.

32 6.   # # # 7. 8. 9. 10. Troubleshooting dress from the /etc/hosts (by
32 6.   # # # 7. 8. 9. 10. Troubleshooting dress from the /etc/hosts (by

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.

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)

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.

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

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.

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.

Getting Started with VNX Installation Assistant for File/Unified 7.0

by using VNX Installation Assistant for File/Unified. Getting Started with VNX Installation Assistant for File/Unified 7.0
VNX Installation Assistant for File/Unified value Control Station hostname Control Station Static IP ad- dress

VNX Installation Assistant for File/Unified value

Control Station hostname

Control Station Static IP ad- dress

1.

2.

3.

1.

2.

3.

Control Station Netmask

1.

2.

3.

Control Station DNS Domain

1.

2.

3.

Control Station DNS Servers

1.

2.

3.

1. 2. 3. Control Station DNS Servers 1. 2. 3. 33 Troubleshooting Change a value set
1. 2. 3. Control Station DNS Servers 1. 2. 3. 33 Troubleshooting Change a value set
1. 2. 3. Control Station DNS Servers 1. 2. 3. 33 Troubleshooting Change a value set

33

Troubleshooting

Change a value set with the VNX Installation Assistant for File/Unified

≠ª¨π º∫∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ª∂ ∞µ∫ª®≥≥ ¿∂ºπ ∫¿∫ª¨¥ ¿∂º ¥®¿ 段ª ª∂ ™Ø®µÆ¨ ∂µ¨ ∂π ¥∂π¨ ∂≠ ªØ¨ Ω®≥º¨∫ ªØ®ª æ¨π¨ ™∂µ≠∞Æºπ¨´ 4∫¨ 3®©≥¨ ∂µ ∑®Æ¨ ª∂ ™Ø®µÆ¨ ®µ¿ ∂≠ ªØ¨ Ω®≥º¨ ∫¨ª∫ æØ∞≥¨ º∫∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´

4µ∞∫∑Ø¨π¨ ™®µ ©¨ º∫¨´ ª∂ ™Ø®µÆ¨ ªØ¨ Ω®≥º¨ ∫¨ª∫ ´ºπ∞µÆ ªØ¨ 5-7 (µ∫ª®≥≥®ª∞∂µ ∫∫∞∫ª®µª ≠∂π %∞≥¨ 4µ∞≠∞¨´ ¨ø™¨∑ª ªØ¨ ∑º©≥∞™ ∫ª∂π®Æ¨ ∑π∂™¨∫∫∂π (/ ®´´π¨∫∫¨∫ 8∂º ¥º∫ª º∫¨ ªØ¨ "+( ™∂¥¥®µ´∫ ª∂ ™Ø®µÆ¨ ªØ∂∫¨ Ω®≥º¨∫ 3∂ ¨µª¨π ® "+( ™∂¥¥®µ´ º∫¨ ªØ¨ CLI Commands ª®©

Note: 8∂º Ø®Ω¨ ª∂ ≥∂Æ ∞µ ª∂ 4µ∞∫∑Ø¨π¨ ®∫ π∂∂ª ª∂ ™Ø®µÆ¨ ªØ¨ Ω®≥º¨ ∫¨ª∫

Table 3. How to change the value set by using Unisphere

How to change it

Select your VNX system.

Go to System Manage Control Station.

Edit the Hostname.

Select your VNX system.

Go to System Manage Control Station.

Edit the IP Address.

Select your VNX system.

Go to System Manage Control Station.

Edit the Netmask.

Select your VNX system.

Go to System Manage Control Station.

Edit the DNS Domain Name.

Select your VNX system.

Go to System Manage Control Station.

Edit the DNS Servers.

➤ Manage Control Station . Edit the DNS Servers . Change a value set with the

Change a value set with the VNX Installation Assistant for File/Unified

Control Station . Edit the DNS Servers . Change a value set with the VNX Installation
34 VNX Installation Assistant for File/Unified value Control Station NTP servers Control Station time zone

34

34 VNX Installation Assistant for File/Unified value Control Station NTP servers Control Station time zone Root

VNX Installation Assistant for File/Unified value

Control Station NTP servers

Control Station time zone

Root password

NAS Administrator password

Blade DNS Domain

Primary Blade DNS Server

How to change it

1.

2.

3.

1.

2.

3.

1.

2.

3.

4.

1.

2.

3.

4.

1.

2.

3.

1.

2.

3.

4.

Select your VNX system.

Edit the NTP servers.

Select your VNX system.

Edit the Current Timezone.

Select your VNX system.

Go to Settings.

Edit the required root information.

Select your VNX system.

Go to Settings.

Edit the required nasadmin information.

Select your VNX system.

Go to System Network DNS.

Select your VNX system.

Go to System Network DNS.

and click Properties.

Edit the DNS server information.

and click Properties . Edit the DNS server information. Troubleshooting Table 3. How to change the
and click Properties . Edit the DNS server information. Troubleshooting Table 3. How to change the

Troubleshooting

Table 3. How to change the value set by using Unisphere (continued)

Go to System Manage Control Station.

Go to System Manage Control Station.

Select root from the Users list and click Properties.

Select nasadmin from the Users list and click Properties.

Delete the existing DNS domain and create a new one.

Select a DNS domain for the primary blade DNS server

Getting Started with VNX Installation Assistant for File/Unified 7.0

Select a DNS domain for the primary blade DNS server Getting Started with VNX Installation Assistant
VNX Installation Assistant for File/Unified value Secondary Blade DNS Server 1. 2. 3. 4. Blade
VNX Installation Assistant for File/Unified value Secondary Blade DNS Server 1. 2. 3. 4. Blade
VNX Installation Assistant
for File/Unified value
Secondary Blade DNS
Server
1.
2.
3.
4.
Blade NTP Server
1.
2.
3.
4.
Blade time zone
1.
2.
3.
4.
Storage Processor B IP Ad-
dress
Site ID
1.
2.
3.
4. Storage Processor B IP Ad- dress Site ID 1. 2. 3. 35 Troubleshooting Table 3.
4. Storage Processor B IP Ad- dress Site ID 1. 2. 3. 35 Troubleshooting Table 3.
4. Storage Processor B IP Ad- dress Site ID 1. 2. 3. 35 Troubleshooting Table 3.

35

Troubleshooting

Table 3. How to change the value set by using Unisphere (continued)

 

How to change it

 

Select your VNX system.

Go to System Network DNS.

Select a DNS domain for the secondary blade DNS server

and click Properties.

Edit the DNS server information.

 

Select your VNX system.

Go to System Data Movers.

Select a Data Mover and click Properties.

Edit the NTP server information.

 

Select your VNX system.

Go to System Data Movers.

Select a Data Mover and click Properties.

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>

Storage Processor A IP Ad- CLI: As root, run the following command:

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>

 

Select your VNX system.

Go to System ServiceTasks Manage Connect Home.

Edit the Site ID.

➤ Manage Connect Home . Edit the Site ID . Change a value set with the

Change a value set with the VNX Installation Assistant for File/Unified

➤ Manage Connect Home . Edit the Site ID . Change a value set with the
36 VNX Installation Assistant for File/Unified value Dial-in Modem Licenses NFS Export values iSCSI LUN

36

36 VNX Installation Assistant for File/Unified value Dial-in Modem Licenses NFS Export values iSCSI LUN values

VNX Installation Assistant for File/Unified value

Dial-in Modem

Licenses

NFS Export values

iSCSI LUN values

CIFS Share values

How to change it

1.

Select your VNX system.

2.

3.

Edit the Dial-in Modem information.

1.

Select your VNX system.

2.

Go to System Manage Licenses.

3.

Edit the information for the licenses.

1.

Select your VNX system.

2.

Go to Sharing NFS.

3.

 

click Properties.

4.

Edit the NFS export information.

1.

Select your VNX system.

2.

Go to Sharing iSCSI.

3.

 

Properties.

4.

Edit the iSCSI LUN information.

1.

Select your VNX system.

2.

Go to Sharing CIFS.

3.

 

Properties.

4.

Edit the CIFS share information.

EMC Training and Professional Services

information. EMC Training and Professional Services Troubleshooting Table 3. How to change the value set by
information. EMC Training and Professional Services Troubleshooting Table 3. How to change the value set by

Troubleshooting

Table 3. How to change the value set by using Unisphere (continued)

Go to System ServiceTasks Manage Connect Home.

Select an NFS export from the list of NFS Exports and

Select an iSCSI LUN from the list of LUNs and click

Select a CIFS share from the list of CIFS Shares and click

$," "º∫ª∂¥¨π $´º™®ª∞∂µ ™∂ºπ∫¨∫ ب≥∑ ¿∂º ≥¨®πµ Ø∂æ $," ∫ª∂π®Æ¨ ∑π∂´º™ª∫ æ∂π≤ ª∂ƨªØ¨π æ∞ªØ∞µ ¿∂ºπ ¨µΩ∞π∂µ¥¨µª ª∂ ¥®ø∞¥∞¡¨ ¿∂ºπ ¨µª∞π¨ ∞µ≠π®∫ªπº™ªºπ¨ ∞µΩ¨∫ª¥¨µª $," "º∫ª∂¥¨π $´º™®ª∞∂µ ≠¨®ªºπ¨∫ ∂µ≥∞µ¨ ®µ´ Ø®µ´∫ ∂µ ªπ®∞µ∞µÆ ∞µ ∫ª®ª¨ ∂≠ ªØ¨ ®πª ≥®©∫ ™∂µΩ¨µ∞¨µª≥¿ ≥∂™®ª¨´ ªØπ∂ºÆØ∂ºª ªØ¨ æ∂π≥´ $," ™º∫ª∂¥¨π ªπ®∞µ∞µÆ ™∂ºπ∫¨∫ ®π¨ ´¨Ω¨≥∂∑¨´ ®µ´ ´¨≥∞Ω¨π¨´ ©¿ $,"

Getting Started with VNX Installation Assistant for File/Unified 7.0

®µ´ ´¨≥∞Ω¨π¨´ ©¿ $," Getting Started with VNX Installation Assistant for File/Unified 7.0
 

Troubleshooting

¨ø∑¨πª∫ &∂ ª∂ ªØ¨ $," .µ≥∞µ¨ 2º∑∑∂πª 権∫∞ª¨ ®ª تª∑ 2º∑∑∂πª $," ™∂¥ ≠∂π ™∂ºπ∫¨ ®µ´ π¨Æ∞∫ªπ®ª∞∂µ ∞µ≠∂𥮪∞∂µ

 

$," /π∂≠¨∫∫∞∂µ®≥ 2¨πΩ∞™¨∫ ™®µ ب≥∑ ¿∂º ∞¥∑≥¨¥¨µª ¿∂ºπ 5-7 ∫¨π∞¨∫ ¨≠≠∞™∞¨µª≥¿ "∂µ∫º≥ª®µª∫ ¨Ω®≥º®ª¨ ¿∂ºπ ©º∫∞µ¨∫∫ (3 ∑π∂™¨∫∫¨∫ ®µ´ ª¨™Øµ∂≥∂Æ¿ ®µ´ π¨™∂¥¥¨µ´ 殿∫ ªØ®ª ¿∂º ™®µ ≥¨Ω¨π®Æ¨ ¿∂ºπ ∞µ≠∂𥮪∞∂µ ≠∂π ªØ¨ ¥∂∫ª ©¨µ¨≠∞ª %π∂¥ ©º∫∞µ¨∫∫ ∑≥®µ ª∂ ∞¥∑≥¨¥¨µª®ª∞∂µ ¿∂º ƨª ªØ¨ ¨ø∑¨π∞¨µ™¨ ®µ´ ¨ø∑¨πª∞∫¨ ªØ®ª ¿∂º µ¨¨´ æ∞ªØ∂ºª ∫ªπ®∞µ∞µÆ ¿∂ºπ (3 ∫ª®≠≠ ∂π Ø∞π∞µÆ ®µ´ ªπ®∞µ∞µÆ µ¨æ ∑¨π∫∂µµ¨≥ "∂µª®™ª ¿∂ºπ $," "º∫ª∂¥¨π 2º∑∑∂πª 1¨∑π¨∫¨µª®ª∞Ω¨ ≠∂π ¥∂π¨ ∞µ≠∂𥮪∞∂µ

 

EMC Training and Professional Services

37

Troubleshooting

38

Getting Started with VNX Installation Assistant for File/Unified 7.0

   

Index

C

- 2 ≠®¥∞≥¿

 

- 2 ∫¨πΩ∞™¨∫

"(%2 "∂µªπ∂≥ 2ª®ª∞∂µ

-¨ª¥®∫≤ -¨ªæ∂π≤ "∂µ≠∞ƺπ®ª∞∂µ -%2 -3/ ∫¨πΩ¨π∫

D

´¨≠®º≥ª Æ®ª¨æ®¿ #-2 #∂¥®∞µ #-2 2¨πΩ¨π∫

E

 

P

∑π¨ ™∂µ≠∞ƺπ®ª∞∂µ ∑π∞¥®π¿ ©≥®´¨ ∑π∂Ω∞∫∞∂µ∞µÆ /π∂ø¿ 1/

 

$," $ +®© -®Ω∞Æ®ª∂π ¨ø∑∂πª∞µÆ

 

S

G

2ª®ª∞™ (/ ®´´π¨∫∫ 2ª∂π®Æ¨ /π∂Ω∞∫∞∂µ∞µÆ

 

Æ®ª¨æ®¿ ®´´π¨∫∫

 
 

T

M

ªπ∂º©≥¨∫Ø∂∂ª∞µÆ

 

,

" ®´´π¨∫∫

,/%2 ¥º≥ª∞∑≥¨ ©≥®´¨ ∫º∑∑∂πª

 

V

N

5,æ®π¨ µ¨ªæ∂π≤ ∞µª¨π≠®™¨∫ 5/- ∞µª¨π≠®™¨∫

 

-

2 ≠®¥∞≥¿

Getting Started with VNX Installation Assistant for File/Unified 7.0

39

Index

40

Getting Started with VNX Installation Assistant for File/Unified 7.0