Symmetrix Basic Handbook V1.

Legend Fan PSE Lab Shanghai Serviceprocessor.net

EMC Symmetrix, 20 Years in the making..........................................................................................3 EMC Symmetrix and DMX Serial Num ers....................................................................................13 EMC Symmetrix ! DMX M"dels y Ca inets #y$es......................................................................1% Symmetrix &ard'are C"m$"nents...................................................................................................1( DMX &ard'are C"m$"nents...........................................................................................................1( EMC Symmetrix DMX)*+ C"m$"nents...........................................................................................1, EMC Symmetrix DMX)*+ Su$$"rted Dri-e #y$es..........................................................................1. EMC Symmetrix DMX)* and Symmetrix /)Max+ 0asi1 Di22eren1es.............................................2% EMC Symmetrix /)Max+ Enginuity %3,*........................................................................................31 EMC Symmetrix /)Max+ Su$$"rted dri-e ty$es..............................................................................3* Symmetrix /)Max Systems+ S4D5 Enhan1ements and 6er2"rman1e.............................................3( EMC Symmetrix Enginuity 7$erating En-ir"nment.......................................................................3. EMC Symmetrix+ 08N 2ile................................................................................................................*2 EMC Symmetrix+ Cal1ulati"ns 2"r &eads, #ra1ks, Cylinders, 90..................................................*( EMC Symmetrix 5ile System :S5S;.................................................................................................*. EMC Symmetrix+ /CMD0 and <C=X............................................................................................%2 EMC Symmetrix+ Dynami1 &"t S$ares............................................................................................%% EMC Symmetrix+ 6ermanent S$aring...............................................................................................%3 EMC Symmetrix DMX de-i1e ty$e, C7/D+ Ca1he 7nly /irtual De-i1e......................................(0 EMC Symmetrix Management C"ns"le :SMC ! 5"r Symmetrix /)Max Systems;........................(1 Sym1li 0asi1 C"mmands..................................................................................................................(% EMC #ime2inder C"mmands............................................................................................................(( EMC S4D5 0asi1s............................................................................................................................(3 S4D5 C"mmands..............................................................................................................................(. EMC Symmetrix > DMX S4D5 Setu$..............................................................................................,1

EMC Symmetrix, 20 Years in the making

So next year will mark a history of Symmetrix Products within EMC, still classified as one of the most robust systems out there after 20 years of its inception. n this section, we will talk about some facts on Symmetrix products as it relates to its features, characteristics, En!inuity microcode "ersions, model numbers, year released, etc. So the #ourney of Symmetrix systems started with Moshe $anai %alon! with his team& #oinin! EMC in late '0(s. ) floatin! story says, the idea of a cache based disk array was initially pitched to both *M and +P and was shot down. EMC was predominately a mainframe memory sellin! company back in the late ,-'0(s. .he Symmetrix products completely chan!ed the direction of EMC in a decade. /oe .ucci comes in at the end of -0(s from 0nisys with a bi! "ision. 1anted to radically chan!e EMC. .hrou!h new ac2uisitions, new technolo!ies, "ision and foremost the inte!ration of all the technolo!ies created today(s EMC. Symmetrix has always been the #ewel of EMC. *ack in the Moshe days, the en!ineers were treated so royally %+a"e heard stories about helicopter rides and la"ish parties with a satellite bus waitin! outside for a support call&. .hen comes the 3ata 4eneral ac2uisition in late -0(s that completely chan!ed the !ame. Some people within EMC were a!ainst the 34 ac2uisition and didn(t see much "alue in it. 1hile the Clariion 34 backplane is what chan!ed the Symmetrix to a Symmetrix 3M5 6 7iber *ased 3ri"es. 8"er this past decade, EMC radically chan!es its position and focuses on ac2uisitions, support, products, 2uality, efficiency, usability and foremost chan!in! itself from a hardware company to an nformation Solutions company focusin! on software as its inte!ral !rowth factor. 9ew ac2uisitions like :e!ato, 3ocumentum, ;S), kept on chan!in! the culture and the !rowth focus within EMC. .hen came <Mware and it chan!ed the rules of the !ame, EMC(s strate!ic mo"e to in"est into <Mware paid off bi! time. .hen happens the =>way partnership between <Mware 6 EMC 6 Cisco, to inte!rate next !eneration products, <>Max %Symmetrix&, <>Sphere and 0CS are born.

+ere we are in 200-, almost at the end of 20 years since the inception of the Symmetrix, the name, the product, the En!inuity code, the robust characteristics, the in"estment from EMC all stays committed with chan!in! market demands. /umpin! back into the Symmetrix, here are a few articles you mi!ht find interestin!, o"erall talkin! about "arious models, serial numbers of the machines and importantly a post on En!inuity 8peratin! En"ironment.

Symmetrix Fami y 1.0 C3) 6 nte!rated Cache 3isk )rray ;eleased ,--0 and sold throu!h ,--= ) 2?4* total disk space introduced 1ow, was in elementary school or may be middle school when this first !eneration Symmetrix was released@. Symmetrix !"00 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y ".0 C3) 6 nte!rated Cache 3isk )rray ;eleased ,--, and sold throu!h ,--? ) =B4* total disk space Mirrorin! introduced Symmetrix !!00 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y ".#

C3) 6 nte!rated Cache 3isk )rray ;eleased ,--2 and sold throu!h ,--C ;S7 capabilities added % actually met a !uy about 2 years a!o, he was one of the en!ineers that had worked on de"elopin! the first ;S7 capabilities at EMC and was "ery instrumental in de"elopin! the +opkinton PSE lab& Symmetrix !$00% AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y &.0 a so ca ed Symmetrix &000 and #000 Series ;eleased ,--? and sold throu!h ,--D C3)E nte!rated Cache 3isk )rray ncludes Mainframe Support %*us F .a!& 4lobal Cache introduced ,4* total Cache 930 6 Microcode S;37 introduced Supports Mainframe and open systems both En!inuity microcode C0xx, C,xx Symmetrix &100% 8pen systems support, half hei!ht cabinet, C.2C inch dri"es Symmetrix #100% Mainframe support, half hei!ht cabinet, C.2C inch dri"es Symmetrix &"00% 8pen Systems support, sin!le cabinet, C.2C inch dri"es Symmetrix #"00% Mainframe support, sin!le cabinet, C.2C inch dri"es Symmetrix &#00% 8pen Systems support, triple cabinet, C.2C inch dri"es
%

Symmetrix ##00% Mainframe support, triple cabinet, C.2C inch dri"es AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y !.0 a so ca ed Symmetrix &000 and #000 Series ;eleased ,--D and sold throu!h 2000 ;) 3 5P introduced =.C nch dri"e siGe introduced 8n triple cabinet systems C.2C inch dri"es used Supports Mainframe and 8pen Systems both .imefinder, Powerpath, 0ltra SCS support En!inuity microcode C2BC.xx.xx, C2BB.xx.xx Symmetrix &&&0% 8pen Systems Support, half hei!ht cabinet, =2 dri"es, =.C inch dri"es Symmetrix #&&0% Mainframe Support, half hei!ht cabinet, =2 dri"es, =.C inch dri"es Symmetrix &!&0% 8pen Systems Support, sin!le frame, -B dri"es, =.C inch dri"es Symmetrix #!&0% Mainframe Support, sin!le frame, -B dri"es, =.C inch dri"es Symmetrix &'00% 8pen Systems Support, triple cabinet, ,2' dri"es, C.2C inch dri"es Symmetrix #'00% Mainframe Support, triple cabinet, ,2' dri"es, C.2C inch dri"es AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y !.$ a so ca ed Symmetrix &000 and #000 Series

;eleased ,--' and sold throu!h 200, Symmetrix 8ptimiGer ntroduced *est hardware so farE least outa!es, least problems and least failures %not sure if EMC will a!ree to it, most customers do& =.C inch dri"es used with all models En!inuity microcode C2BC.xx.xx, C2BB.xx.xx, C2BD.xx.xx Symmetrix &(&0% 8pen Systems support, half hei!ht cabinet, =2 dri"es Symmetrix #(&0% Mainframe support, half hei!ht cabinet, =2 dri"es Symmetrix &$&0% 8pen Systems support, sin!le cabinet, -B dri"es Symmetrix #$&0% Mainframe support, sin!le cabinet, -B dri"es Symmetrix &)&0% 8pen Systems support, triple cabinet, 2CB dri"es Symmetrix #)&0% Mainframe support, triple cabinet, 2CB dri"es Models sold as =B=0>,', =B=0>=B, =B=0>C0, CB=0>,', CB=0>=B, CB=0> C0,='=0>=B, ='=0>C0, ='=0>D=, C'=0>=B, C'=0>C0, C'=0>D=, =-=0>=B, =-=0> C0, =-=0>D=, C-=0>=B, C-=0>C0, C-=0>D= %the last two di!its indicate the dri"es installed in the frame& AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y #.0 a so ca ed Symmetrix $000 Series H =000 %open sytems& I C000 %mainframe& J '000 %support for both& K Supports 8pen Systems and Mainframe without *0S and .)4 throu!h ESC89 ;eleased 2000 and sold throu!h 200= ,',4* 3isk introduced En!inuity microcode CCBD.xx.xx, CCB'.xx.xx Symmetrix $1&0% Slim cabinet, ?' dri"es

Symmetrix $!&0% Sin!le cabinet, -B dri"es Symmetrix $'&0% .riple cabinet, ='? dri"es Some models sold as '?=0>=B, '?=0>D=, '?=0>,', or 'D=0>=B, 'D=0>D=, 'D=0>,', %the last two di!its indicate the dri"es installed in the frame& AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix Fami y #.# LV* a so ca ed Symmetrix $000 Series ;eleased 200, and sold throu!h 200? :<3E :ow <olta!e 3isk ntroduced ,?B4* :<3 dri"e introduced 0ltra SCS dri"es cannot be used with the :<3 frame Mainframe optimiGed machines introduced ? Slice directors introduced with ESC89 and 7 C89 7 C89 introduced En!inuity microcode CCBD.xx.xx, CCB'.xx.xx Symmetrix $"&0% Slim cabinet, ?' dri"es, %rebranded ',=0, non l"d frame& Symmetrix $#&0% Sin!le cabinet, -B dri"es, %rebranded '?=0, non l"d frame& Symmetrix $$&0% .riple cabinet, ='? dri"es, %rebranded 'D=0, non l"d frame& Symmetrix $"&0 LV*% :<3 frame, slim cabinet, ?' :<3 dri"es Symmetrix $#&0 LV*% :<3 frame, sin!le cabinet, -B :<3 dri"es Symmetrix $$&0 LV*% :<3 frame, triple cabinet, ='? :<3 dri"es Symmetrix +,$#&0% :<3 frame, Sin!le cabinet, -B dri"es, optimiGed for mainframes

Symmetrix +,$$&0% :<3 frame, .riple cabinet, ='? dri"es, optimiGed for mainframe Some models sold as 'C=0>=B, 'C=0>D=, 'C=0>,?B, 'C=0>,', or ''=0>=B, ''=0>D=, ''=0>,?B, ''=0>,', %the last two di!its indicate the dri"es installed in the frame& AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix *-. or a so ca ed Symmetrix Fami y (.0 ;eleased 7eb 200= and sold throu!h 200B 3irect Matrix )rchitecture %3ata 4eneral *ackplane& introduced 3M5'00 was the first 3M5 system introduced ? Slice directors introduced ;) 3 C introduced after bein! introduced on 3M5>= 7irst !eneration with common 3) L 7) hardware ntroduction of modular power En!inuity Microcode CBB-.xx.xx, CBD0.xx.xx, CBD,.xx.xx Symmetrix *-.$00% Sin!le cabinet, 3)E based concept for dri"es, -B dri"es % swear, a customer told me, they ha"e !host like issues with their 3M5'00& Symmetrix *-.1000% Sin!le cabinet, ,' dri"es per loop, ,?? dri"es total Symmetrix *-.1000,P% Sin!le cabinet, - dri"es per loop, ,?? dri"es total, PJ Performance System Symmetrix *-."000% 3ual cabinet, modular power, ,' dri"es per loop, 2'' dri"es Symmetrix *-."000,P% 3ual cabinet, modular power, - dri"es per loop, 2'' dri"es, PJPerformance System

Symmetrix *-.&000,&% .riple cabinet, modular power, ,' dri"es per loop, = phase power, CDB dri"es AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix *-." or a so ca ed Symmetrix Fami y (.# ;eleased 7eb 200? and sold throu!h 200D 3ouble the processin! usin! 3M52 3M5 and 3M52 frames are same, only directors from 3M5 must be chan!ed to up!rade to 3M52, reboot of entire systems re2uired with this up!rade ;) 3 C introduced after bein! introduced on 3M5>= B?4* memory introduced ? Slice 3irectors En!inuity Microcode CBB-.xx.xx, CBD0.xx.xx, CBD,.xx.xx Symmetrix *-.$01% 2nd !eneration 3M5, Sin!le cabinet, 3)E based concept for dri"es, -B dri"es, 7C SPE 2 % swear, a customer told me, they ha"e !host like issues with their 3M5'00& Symmetrix *-.1000,-"% 2nd !eneration 3M5, Sin!le cabinet, ,' dri"es per loop, ,?? dri"es Symmetrix *-.1000,P"% 2nd !eneration 3M5, Sin!le cabinet, - dri"es per loop, ,?? dri"es, PJPerformance System Symmetrix *-."000,-"% 2nd !eneration 3M5, 3ual cabinet, ,' dri"es per loop, 2'' dri"es Symmetrix *-."000,P"% 2nd !eneration 3M5, 3ual cabinet, - dri"es per loop, 2'' dri"es, PJPerformance System Symmetrix *-."000,-",&% 2nd !eneration 3M5, 3ual cabinet, ,' dri"es per loop, 2'' dri"es, = Phase power Symmetrix *-."000,P",&% 2nd !eneration 3M5, 3ual cabinet, - dri"es per loop, 2'' dri"es, PJPerformance System, = Phase power

10

Symmetrix *-.&000,-",&% 2nd !eneration 3M5, .riple cabinet, ,' dri"es per loop, CDB dri"es, = Phase power AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix *-.,& or a so ca ed Symmetrix '.0 ;eleased /uly 200C and still bein! sold ' Slice directors ,-20 disk %;PM Ned to 2?00 dri"es& 3)E based concept introduced Symmetrix Priority Controls ;) 3 C introduced and then implemented on older 3M5, 3M5>2 <irtual :09 technolo!y S;37 enhancements Concept of "aultin! introduced En!inuity microcode CDD,.xx.xx, CDD2.xx.xx Symmetrix *-.,& )#0% System Cabinet, Stora!e *ay x 2, =B0 dri"es max, Modular Power, = Phase power Symmetrix *-.,&% System Cabinet, Stora!e *ay x ' %Expandable&, ,-20 dri"es max, ;PM(ed to 2?00 dri"es, = Phase power AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix *-.,! or a so ca ed Symmetrix '.0 ;eleased /uly 200D and still bein! sold <irtual pro"isionin! 7lash 3ri"es
11

7C L S).) dri"es ;) 3 B introduced S;37 enhancements .otal CacheE C,2 4* .otal Stora!eE , P* :ar!est dri"e supported ,.* S).) dri"e 7lash dri"es D=4*, ,?B4* later now support for 2004* and ?004* released ,-20 dri"es max %;PM(ed to 2?00 dri"es& En!inuity microcode CDD2.xx.xx, CDD=.xx.xx Symmetrix *-.,! )#0% System Cabinet, Stora!e *ay x 2, =B0 dri"es max, Modular Power, = Phase power Symmetrix *-.,!% System Cabinet, Stora!e *ay x ' %Expandable&, ,-20 dri"es max, ;PM(ed to 2?00 dri"es, Modular power, = Phase Power Some models sold as 3M5>? ,C00, 3M5>? 2C00, 3M5>? =C00 and 3M5>? ?C00 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Symmetrix V,-ax %;eleased )pril 200-& En!inuity Microcode C'D?.xxx.xxx .otal number of dri"es supportedE 2?00 .otal CacheE , .* mirrored %C,24* usable& .otal Stora!eE 2 P* )ll features on the <>Max ha"e been discussed earlier on the blo! post linked below

12

Symmetrix V,-ax SE% Sin!le System *ay, SEJSin!le En!ine, Stora!e *ay x 2, =B0 dri"es max, cannot be expanded to a full blown ' en!ine system if purchased as a SE, = Phase power, Modular Power Symmetrix V,-ax% System Cabinet, Stora!e *ay x ,0, 2?00 dri"es max, modular power, = phase power

EMC Symmetrix and DMX Serial Numbers

$ou always wondered how EMC comes up with these serial numbers for your Symmetrix and 3M5 Machines. f your machine serial number starts with +O %it means it was manufactured in +opkinton, M)& and for most of the international customers if it starts with CO %it means it was manufactured in Cork, reland&. 1ith the 3M5 Series of machines, EMC has introduced two new manufacturin! centers %.9 and S)&. .here are still machines startin! with +O and CO that will be shipped internationally and "ice "ersa.

.he .he .he .he

serial serial serial serial

number number number number

+O would always ha"e a , followin! it. CO would always ha"e a 2 followin! it. .9 would always ha"e a 2 followin! it. S) would always ha"e a 2 followin! it.

+ere is the Symmetrix and 3M5 Serial 9umberin! Con"ention.

Symmetrix Symmetrix Symmetrix Symmetrix Symmetrix Symmetrix Symmetrix Symmetrix

=.0, =.0, =.0, ?.0, ?.0, ?.0, ?.', ?.',

,L2 cabinetE +O,',B0xxxx , cabinetE +O,',C0xxxx = cabinetE +O,',?0xxxx ,L2 CabinetE +O,'2B0xxxx , cabinetE +O,'2C0xxxx = cabinetE +O,'2?0xxxx ,L2 cabinetE +O,'=B0xxxx , cabinetE +O,'=C0xxxx
13

Symmetrix Symmetrix Symmetrix Symmetrix Symmetrix

?.', C.0, C.0, C.C, C.C,

= , = , =

cabinetE cabinetE cabinetE cabinetE cabinetE

+O,'=D0xxxx +O,'?C0xxxx +O,'?D0xxxx +O,'CC0xxxx +O,'CD0xxxx

.he 3M5 Serial numbers still need more research because its hard to find a trend with the numberin! con"ention on it.

3M5'00E +O,'D-0xxxx 3M5,000>SE +O,'D?0xxxx 3M5,000>PE +O,'D?Bxxxx 3M52000>SE +O,'DD0xxxx 3M52000>PE +O,'DDBxxxx 3M5=000E +O,'D''xxxx 3M5=000>M2E+O,'D'-xxxx 3M5=E +O,-0,0xxxx 3M5?E +O,-,,0xxxx

t is "ery important that you Ser"ice processor Serial 9umber is exactly similar to that of the Symmetrix L 3M5 Serial 9umber %)s defined in the * 9 7 :E&. f both these serial numbers are different, your basic symc/g discover commands will fail. $our actual hardware Symmetrix L 3M5 Serial 9umber can still be different than the Serial number defined in the * 9 file, since the * 9 file serial number takes precedence. .he find your Symmetrix L 3M5 Serial 9umber look at the front and back of the Symmetrix on the top, the number should be!in with H0 or 10 or 23 or S4. .o find your Symmetrix L 3M5 Serial 9umber from the ser"ice processor, run E'51F or you can also try to run symc/g discover or symin6 from the ser"ice processor "ia S$MC: located 1%7Program Fi es7E-17Symc ibin. 8ne option before runnin! this, you can delete the file located on the ser"ice processor called symapi8db.bin located 1%7Program Fi es7E-17Symapidb. 3urin! the symc/g discover process, this file will be recreated. .he lo!s if this operation fails can be found at 1%7Program Fi es7E-17Symapi og. t is "ery important you do not chan!e your Symmetrix L 3M5 Serial number since the 7) 119 are determined usin! the last two di!its of your actual Serial 9umber. f you chan!e this, all the 119(s will chan!e causin! your

1*

7)(s, 3isk 119 etc to all chan!e. )s far as my knowled!e, this can only be chan!ed throu!h a * 9 7 :E chan!e.

EMC Symmetrix DMX Models by Cabinets y!es

.he below is the true breakdown of the type of the EMC Symmetrix and EMC 3M5 machines to the type of cabinet properties it has. Startin! with the Symm =.0(s EMC introduced a ,L2 +ie!ht cabinets, Sin!le 7ull Cabinet and a = Cabinet machine. .he same ideas went into the Symm ?.0 and ?.'. Startin! the Symm C.0 and into Symm C.C, EMC introduced the *ad!er cabinets, which where much slimmer and about C ft in hei!ht, it was a disaster with those cabinets. ;eally no one bou!ht it. Startin! the 3M5'00(s and 3M5,000(s which are the sin!le cabinet, EMC introduced the 3M52000(s in 2 cabinets and 3M5=000 in = cabinet style. )lso if you e"er wondered where those Symm modell numbers came from ,st 3i!itE = J 8pen Systems. C J Mainframe. ' J Mixed. 2nd 3i!itE ;elated to Cabinet siGe, dependant on 4eneration( =rd 3i!itE 00 J CPQ 3ri"es. =0 J =RQ 3ri"es .he 3M5 uses =,L2S 7iber 3ri"es

1%

Symmetrix "ard#are Com!onents

.here are "arious Components in a EMC Symmetrix series of machines. .o name a few 3isk 3irectors Channel 3irectors %C), 7), E), 7 , 4 , 7)2& Memory Cards 3isk 3ri"es Power Supply 7or = *ay cabinets %)C>3C PS and 3C>3C PS& 7an *ack End 3isk )dapters *ack End Channel )dapters %C), 7), E), 7 , 4 , 7)2& Communication Card EP8 Module *attery Ser"ice Processor

DMX "ard#are Com!onents

Some of the important hardware components of a 3M5 Machine are 3isk 3irectors %3)& *ack End 3isk )dapters Channel 3irectors %C), E), 7), 7)2, 7 , 4 & *ack End Channel 3irectors Memory Cards Power Module 7)9 *attery ECM %En"ironmental Control Module&,
1(

CCM %Communication Control Module& 3isk 3ri"es Ser"ice Processor

EMC Symmetrix DMX$%& Com!onents

n my pre"ious posts on EMC Symmetrix =, C, ' Series and EMC Symmetrix 3M5, 3M5>2 Series we discussed some important components that comprise in systems, in this post we will discuss some of the important components of EMC Symmetrix 3M5>?. EMC Symmetrix 3M5>? consist of , System *ay and %, upto '&Scalable Stora!e *ay(s. Each Stora!e *ay can hold up to 2?0 3isk 3ri"es totalin! ,-20 dri"e in ' Stora!e bays or ,02? .* System. Systems with special re2uirements can be confi!ured to 2?00 dri"es instead of standard ,-20 dri"es. .he primary bay is the System *ay which includes all directors, ser"ice processor, adapters, etc, while the Stora!e *ay contains all the disk dri"es, etc.

System Bay 91 Bay: 1hanne directors% 7ront End 3irectors %7C, ESC89, 7 C89, 4i!E, iSCS &, these are the L8 3irectors. *isk directors% *ack End 3irectors %3)&, these control the dri"es in the System. ; oba memory directors% Mirrored Memory a"ailable with 3M5>?, Memory 3irector siGes ran!e from '4*, ,B4*, =24* or B?4* totalin! C,24* %2CB4* mirrored&.

1,

*isk adapters% *ack End )dapters, they pro"ide an interface to connect disk dri"es throu!h the stora!e bays. 1hanne adapters% 7ront End )dapters, they pro"ide an interface for host connection %7C, ESC89, 7 C89, 4i!E, iSCS &. Po<er s=pp ies% = Phase 3elta or 1$E confi!uration, Tone ) and Tone * based Power Supplies, maximum ' of them in the system bay. Po<er distrib=tion =nits 9P*>:% 8ne P30 per Gone, 2 in total. Po<er distrib=tion pane s 9P*P:% 8ne P3P per Gone, 2 in total, power onLoff, main power. Battery back=p >nit 9BB>:% 2 *attery backup modules, ' **0 units, between = to C mins of backup power in case of a catastrophic power failure. 1oo ing /an mod= es% = 7ans at the top of the bay to keep it cool. 1omm=nications and Environmenta 1ontro 9.1-: mod= es% 7abric and En"ironmental monitorin!, 2 5CM located at the rear of the system bay. .his is the messa!e fabric, that is the interface between directors, dri"es, cache, etc. En"ironmental monitorin! is used to monitor all the <P3 %<ital Product 3ata&. Service processor components% Oeyboard, <ideo, 3isplay and Mouse. 0sed for remote monitorin!, call home, dia!nostics and confi!uration purposes. >PS% 0PS for the Ser"ice Processor Si encers% Made of foam inside, different Silencers for System and Stora!e bay(s.

Storage bay 91 Bay -inim=m to $ Bay?s -axim=m: *isk drives% Combination of D=4*, ,?B4*, =004*, ?004*, ?C04*, C004*, ,.* and now E73(s D=4*, ,?B4* and 2004* a"ailable. SpeedE ,0O, ,CO, D.2O S).) are all compatible, each ;) 3 4roup and each dri"e enclosure should only ha"e similar speed dri"es, similar type dri"es. ,C dri"es per Enclosure, 2?0 per bay, ,-20 total in the system. f the color of the :E3 li!hts

13

on the dri"e is *lue its 24* speed, if the color of the :E3 is !reen, the speed is ?4*. *rive Enc os=re >nits% ,B per Stora!e *ay, ,C dri"es per enclosure Battery Back=p >nit 9BB>:% ' **0 modules per Stora!e bay, each **0 support ? 3ri"e enclosures Po<er S=pp y5 System 1oo ing -od= e% 2 per dri"e enclosure Link 1ontro 1ards% 2 per dri"e enclosure Po<er *istrib=tion >nit 9P*>:% , P30 per Gone, 2 in total Po<er *istrib=tion Pane s 9P*P:% , P3P per Gone, 2 in total

EMC Symmetrix DMX$%& Su!!orted Dri'e y!es

n this section we will discuss the supported dri"e models for EMC Symmetrix 3M5>?. ;i!ht before the release of Symmetrix <>Max systems, in early 7eb 200- we saw some added support for E73(s %Enterprise 7lash 3isk& on the Symmetrix 3M5>? platform. .he additions were denser 2004* and ?004* E73(s. .he followin! siGe dri"es types are supported with Symmetrix 3M5>? Systems at the current microcode CDD=E D=4*, ,?B4*, 2004*, =004*, ?004*, ?C04*, C004*, ,0004*. 7la"ors of dri"es include ,0O or ,CO and interface "aries 24* or ?4*. .he dri"e has capabilities to auto ne!otiate to the backplane speed. f the dri"e :E3 is !reen the speed is 24*, if its neon blue its ?4* interface. 2he /o o<ing are detai s on the drives /or the Symmetrix *-.,! Systems. @o= <i /ind detai s aro=nd *rive 2ypes5 Aotationa Speed5
1.

Bnter/ace5 *evice 1ache5 4ccess times5 Aa< 1apacity5 Cpen Systems Formatted 1apacity and -ain/rame Formatted 1apacity.

'&;B F1 *rive 3ri"e SpeedE ,0O nterfaceE 24* L ?4* 3e"ice CacheE ,BM* )ccess speedE ?.D 6 C.? mS ;aw CapacityE D=.?, 4* 8pen Systems 7ormatted CapE B'.=0 4* Mainframe 7ormatted CapE D2.?0 4* '&;B F1 *rive 3ri"e SpeedE ,CO nterfaceE 24* L ?4* 3e"ice CacheE ,BM* )ccess speedE =.C 6 ?.0 mS ;aw CapacityE D=.?, 4* 8pen Systems 7ormatted CapE B'.=0 4* Mainframe 7ormatted CapE D2.?0 4* 1!(;B F1 *rive 3ri"e SpeedE ,0O nterfaceE 24* L ?4* 3e"ice CacheE =2M* )ccess speedE ?.D 6 C.? mS
20

;aw CapacityE ,?B.'2 4* 8pen Systems 7ormatted CapE ,=B.B2 4* Mainframe 7ormatted CapE ,??.', 4* 1!(;B F1 *rive 3ri"e SpeedE ,CO nterfaceE 24* L ?4* 3e"ice CacheE =2M* )ccess speedE =.C 6 ?.0 mS ;aw CapacityE ,?B.'2 4* 8pen Systems 7ormatted CapE ,=B.B2 4* Mainframe 7ormatted CapE ,??.', 4* &00;B F1 *rive 3ri"e SpeedE ,0O nterfaceE 24* L ?4* 3e"ice CacheE =2M* )ccess speedE ?.D 6 C.? mS ;aw CapacityE =00.0 4* 8pen Systems 7ormatted CapE 2D-.,D 4* Mainframe 7ormatted CapE 2-C.-, 4* &00;B F1 *rive 3ri"e SpeedE ,CO nterfaceE 24* L ?4* 3e"ice CacheE =2M*

21

)ccess speedE =.B 6 ?., mS ;aw CapacityE =00.0 4* 8pen Systems 7ormatted CapE 2D-.,D 4* Mainframe 7ormatted CapE 2-C.-, 4* !00;B F1 *rive 3ri"e SpeedE ,0O nterfaceE 24* L ?4* 3e"ice CacheE ,BM* )ccess speedE =.- 6 ?.2 mS ;aw CapacityE ?00.0 4* 8pen Systems 7ormatted CapE =D2.2= 4* Mainframe 7ormatted CapE =-?.CC 4* !#0;B F1 *rive 3ri"e SpeedE ,CO nterfaceE 24* L ?4* 3e"ice CacheE ,BM* )ccess speedE =.? 6 ?., mS ;aw CapacityE ?C0.0 4* 8pen Systems 7ormatted CapE ?,'.DB 4* Mainframe 7ormatted CapE ??=.'D 4* #00;B S424 BB *rive 3ri"e SpeedE D.2O nterfaceE 24* L ?4*

22

3e"ice CacheE =2M* )ccess speedE '.C to -.C mS ;aw CapacityE C00.0 4* 8pen Systems 7ormatted CapE ?BC.2- 4* Mainframe 7ormatted CapE ?-=.,- 4* 1000;B S424 BB *rive 3ri"e SpeedE D.2O nterfaceE 24* L ?4* 3e"ice CacheE =2M* )ccess speedE '.2 6 -.2 mS ;aw CapacityE ,000.0 4* 8pen Systems 7ormatted CapE -=0.D' 4* Mainframe 7ormatted CapE -'B.C' 4* '&;B EF* 3ri"e SpeedE 9ot )pplicable nterfaceE 24* 3e"ice CacheE 9ot )pplicable )ccess speedE ,mS ;aw CapacityE D=.0 4* 8pen Systems 7ormatted CapE D=.0 4* Mainframe 7ormatted CapE D=.0 4* 1!(;B EF* 3ri"e SpeedE 9ot )pplicable

23

nterfaceE 24* 3e"ice CacheE 9ot )pplicable )ccess speedE ,mS ;aw CapacityE ,?B.0 4* 8pen Systems 7ormatted CapE ,?B.0 4* Mainframe 7ormatted CapE ,?B.0 4* "00;B EF* 3ri"e SpeedE 9ot )pplicable nterfaceE 24* L ?4* 3e"ice CacheE 9ot )pplicable )ccess speedE ,mS ;aw CapacityE 200 4* 8pen Systems 7ormatted CapE ,-B.-D 4* Mainframe 7ormatted CapE ,-,.2, 4* !00;B EF* 3ri"e SpeedE 9ot )pplicable nterfaceE 24* L ?4* 3e"ice CacheE 9ot )pplicable )ccess speedE ,mS ;aw CapacityE ?00.0 4* 8pen Systems 7ormatted CapE =-=.'? 4* Mainframe 7ormatted CapE ='2.== 4* Support for D=4* and ,?B4* E73(s ha"e been dropped with the Symmetrix <>Max Systems, they will still be supported with the Symmetrix 3M5>?
2*

Systems which in addition to D= 4* and ,?B4* also supports 2004* and ?004* E73(s.

EMC Symmetrix DMX$% and Symmetrix ($ Max& )asi* Di++eren*es

EMC Symmetrix 3M5>? and Symmetrix <>MaxE *asic 3ifferences n this post we will co"er some important aspects L properties L characteristics L differences between the EMC Symmetrix 3M5>? and EMC Symmetrix <>Max. t seems like a lot of users are searchin! on blo! posts about this information. 7rom a hi!h le"el, ha"e tried to co"er the differences in terms of performance and architecture related to the directors, en!ines, cache, dri"es, etc t mi!ht be a !ood idea to also run both the 3M5>? and <>max systems throu!h 8meter to collect some basic comparisons between the front end and coordinated backend L cache performance data. )nyways en#oy this post, and possibly look for some more related data in the future post. E-1 Symmetrix *-.,! Called EMC Symmetrix 3M5>? 3M5E 3irect Matrix )rchitecture Max CapacityE , P* ;aw Stora!e Max 3ri"esE ,-00. 8n ;PME 2?00 max E73(s Supported E-1 Symmetrix V,-ax Called EMC Symmetrix <>Max <>MaxE <irtual Matrix )rchitecture Max CapacityE 2 P* of 0sable Stora!e Max 3ri"esE 2?00 E73(s Supported

2%

Symmetrix Mana!ement Console B.0 Solutions Enabler B.0 E73E D=4*, ,?B4*, 2004*, ?004* 7C 3ri"esE D=4*, ,?B4*, =004*, ?004*, ?C04* S).) S).) E C004*, ,000 4* 3ri"e SpeedE D.2O 7C 3ri"e SpeedE ,0O or ,CO Predecessor of 3M5>? is 3M5>= 3M5>? mana!ement has !ot a bit easy compared to the pre"ious !eneration Symmetrix ? Ports per 3irector 9o En!ine based concept 2? slots , System bay, - Stora!e bays 9o en!ines B? 7iber Channel total ports on all directors for host connecti"ity =2 7 C89 ports for host connecti"ity =2 4bE iSCS ports .otal CacheE C,24* with 2CB 4* usable %mirrored& 3ri"e interface speed either 24* or ?4*, dri"es auto ne!otiate speed 4reen color dri"e :E3 means 24* loop speed, *lue color dri"e :E3 means ?4* loop speed C,2 byte style dri"e %format&

Symmetrix Mana!ement Console D.0 Solutions Enabler D.0 E73E 2004*, ?004* 7C 3ri"esE D=4*, ,?B4*, =004*, ?004* S).) S).) E ,000 4* 3ri"e SpeedE D.2O 7C 3ri"e SpeedE ,CO Predecessor of <>Max is 3M5>? Ease of 0se with Mana!ement 6 atleast with SMC D.0 or so called ECC lite ' Ports per 3irector En!ine based concept .he concept of slots is !one , System bay, ,0 Stora!e bays ' En!ines in one System %serial number& ,2' 7iber Channel total ports on directorsLen!ines for host connecti"ity B? 7 C89 ports for host connecti"ity B? 4bE iSCSC ports .otal CacheE ,02? 4* with C,2 4* usable %mirrored& 3ri"e interface speed ?4*

8nly ?4* dri"e speed supported.

C20>byte style dri"e %' bytes used for storin! data check info&. ;emember the clarion dri"e styles, well the data stored in both the cases is different. .he ' bytes used with the Symmetrix <>Max are the data inte!rity field

2(

based on the al!orithm 3,0>. 7 standard proposal 7)S.E 7ully )utomated Stora!e .ierin! may not be supported on 3M5>?(s %most likely since the support mi!ht come based on a microcode le"el rather than a hardware le"el& MicrocodeE CDD2 L CDD= runs 3M5>?(s ;eleased in /uly 200D Concepts of 3irectors and Cache on separate physical slots L cards 3M5>? .imefinder performance has been better compared to pre"ious !eneration 9o P Mana!ement interface into the Ser"ice Processor 7)S.E 7ully )utomated Stora!e .ierin! will be supported later this year on the <>Max systems

MicrocodeE C'D? runs <>Max ;eleased in )pril 200Concept of condensed 3irector and Cache on board =00U better . mefinder Performance compared to 3M5>? P Mana!ement interface to the Ser"ice Processor, can be mana!ed throu!h the customer(s 9etwork 6 P infrastructure Symmetrix Mana!ement Console to be licensed at a cost startin! the <>Max systems )rchitecture of <>Max is completely redesi!ned with this !eneration and is completely different from the predecessor 3M5>? Microcode C'D? has been build on base CDD= from pre"ious !eneration 3M5>? mplementation of ;<)E ;aid <irtual )rchitecture :ar!e <olume SupportE 2?04* per :09 %8pen Systems& and 22=4* per :09 %Mainframe Systems& C,2 hypers per 3ri"e %luns per dri"e& <>Max systems introduced the concept of concurrent confi!uration chan!e

Symmetrix Mana!ement Console is not char!ed for until %free& 3M5>? )rchitecture of 3M5>? has been similar to the architecture of its predecessor 3M5>= Microcode CDD2 and CDD= has be build on pre"ious !eneration of microcode CDD, and CDD2 respecti"ely 9o ;<)E ;aid <irtual )rchitecture :ar!est supported "olume is B?4* per :09 ,2' hypers per 3ri"e %luns per dri"e& Confi!uration chan!e not as robust as <>Max Systems

2,

allowin! customers to perform chan!e mana!ement on the <>Max systems combined to work throu!h sin!le set of scripts rather than a step based process. 3M5>? does present some challen!es with mirror positions 9o <irtual Pro"isionin! with ;) 3 C and ;) 3 B de"ices 9o )utopro"isionin! !roups Minimum siGe 3M5>?E ) sin!le stora!e cabinet system, supportin! 2?0 dri"es can be purchased with a system cabinet 9o concepts of En!ine, architecture based on slots ;educed mirror positions !i"in! customers !ood flexibility for mi!ration and other opportunities <irtual Pro"isionin! allowed now with ;) 3 C and ;) 3 B de"ices Concept of )utopro"isionin! !roups introduced with <>Max Systems Minimum siGe <>Max SE %sin!le en!ine& system can be purchased with , en!ine and =B0 dri"e max. Each En!ine consists of ? Muad Core ntel Chips with either =24*, B?4* or ,2'4* cache on each en!ine with ,B front>end ports with each en!ine. *ackend ports per en!ine is ? ports connectin! System bay to stora!e bay ntel Muad Core chips used on En!ines Powerpath <E supported for <sphere 6 <irtual machines for <>Max <>Max fits in the cate!ory of Modular Stora!e and eliminates the bottle neck of a backplane <>Max systems ha"e been sold with a bi! marketin! buGG around hundreds of en!ines, millions of 8Ps, .*(s of cache, <irtual Stora!e .he concept of 7ederation has been introduced with <>Max systems, but systems are not federated in production or customer en"ironments yet En!ines are connected throu!h copper ;)P 3 8 interconnect at 2.C4* speed

Power PC chips used on directors Powerpath <E support for <sphere 6 <irtual machines for 3M5>? Concept of *ackplane exists with this !eneration of stora!e 3M5>? was truly sold as a !eneration up!rade to 3M5>=

Systems cannot be federated

3irectors are connected to the system throu!h a le!acy backplane %3M5 6 3irect Matrix

23

)rchitecture&. 9o support for 7C8E or ,04* Ethernet 9o support for '4* loop interface speeds Stron! Marketin! with 3M5>? and !ood success 9o support for 7C8E or ,04* Ethernet 9o support for '4* loop interface speeds <irtual Marketin! for <irtual Matrix %<> Max& since the product was introduced with 7)S. as a sales strate!y with 7)S. not a"ailable for at least until the later part of the year. 1ould nfini*and be supported in the future to connect en!ines at a short or lon! distance %se"eral meters& 1ith 7ederation expected in the upcomin! "ersions of <>Max, how would the cache latency play a role if you had federation between systems that are ,0 to ,0 meters awayV 4lobal Cache on local en!ines chipsE a!ain as cache is shared between multiple en!ines, cache latency is expected as multiple en!ines re2uest this 8 .he <>Max buildin! blocks %en!ines& can create a much lar!er stora!e monster 2004* of "ault space per En!ine, with ' en!ines, we are lookin! at ,.B.* of "ault stora!e 8PS per P8;. of <>Max Systems ,2' M*Ls +its ='C ;ead ='C 1rite 8PS for 2 P8;. of <>Max Systems ,2'M*Ls +its B=C ;ead

9o support for nfini*and expected with 3M5>? 9o 7ederation

4lobal Cache on 4lobal Memory 3irectors

3M5>? is a monster stora!e system 2CB4* total "ault on 3M5>? systems Performance on 3M5>? has been !reat compared to its pre"ious !eneration 3M5, 3M52, 3M5>=

2.

B?0 1rite <>Max performs better compared to 3M5>? 7 C89 2.2 x Performance on 7 C89 compared to 3M5>? Systems. 2 Ports can ha"e as many as ,D000 8PS on 7 C89 ) reduction of C0 to DCU o"erhead with the <>Max related to metadata 9ew S;37LE3P %extended distant protection& 3iskless ;2, passthrou!h de"ice, no disk re2uired for this passthrou!h .emplates and 1iGards within the new SMC D.0 console .otal S;37 4roups supported 2C0 B? 4roups on Sin!le Port for S;37 25 Connecti"ity compared to the 3M5> ? =5 usability compared to the 3M5>? ;) 3 B is =.B times better than the 3M5>? ;) 3 B on <>Max %performance& is e2ui"alent to ;) 3 , on 3M5>? S).) dri"es do not support the C20> byte style. EMC takes those ' bytes %C20 6 C,2& of calculation for data inte!rity .,0>3 7 standard proposal and writes it in blocks or chunks of B?O throu!h out the entire dri"e causin! performance de!radation. .he performance of S).) dri"es on <>Max is bad the 3M5>? systems 7iber Channel performance compared to 3M5>? impro"ed by about =BU 7iber Channel performance C000 8PS per channel

:ar!e Metadata o"erhead with the amount of "olumes, de"ices, cache slots, etc, etc S;37 .echnolo!y Supported

Symmetrix Mana!ement Console B.0 supported, no templates and wiGards .otal S;37 4roups supported ,2' ,B 4roups on Sin!le Port for S;37 <>Max comparison on Connecti"ity <>Max comparison on 0sability %Stora!e& 3M5>? was the first "ersion of Symmetrix where ;) 3B support was rolled out ;) 3B support on 3M5>? is and was a little premature S).) performance on 3M5>? is better than <>Max

S).) performance on 3M5>? is better than <>Max 7iber Channel performance better compared to 3M5 and 3M5>2(s. 3M5>? start supportin! ?4* interface host connecti"ity

30

;<) not a"ailable on 3M5>? platforms

;<)E ;aid <irtual )rchitecture allows to ha"e one mirror position for ;) 3 "olumes allowin! customers to used the rest of the = positions for either *C<(s, S;37, Mi!ration, etc, etc. M *EE Matrix nterface *oard Enclosure connects the 8dd and the E"ens or %7abric ) and 7abric *& 3irectors to!ether. .he S * %System nterface *oard& connects these en!ines to!ether usin! ;apid 8 3irector count !oes from , on the bottom to ,B %7& on the top, based on each en!ine ha"in! 2 directors. ' En!ines, ,B 3irectors. Sin!le en!ine failure %2 3irectors& will not cause 3ata :oss L 3ata 0na"ailable and the system will not cause an outa!e. 7ailed components can be 3irectors, En!ines, M *E, PS(s, 7an, Cache in a sin!le En!ine or 2 directors. Sin!le loop outa!es will not cause 30

9o M *E and S * with 3M5>?. ;ather the 3M5>? directors are connected throu!h a common backplane.

3irector count !oes from 3irector , on the left to 3irector ,' %+ex& on the ri!ht 2 3irectors failures if not in the same fabric or bus, rather are not 3 (s %3ual nitiators& of each other will not cause a system outa!e or data loss L data una"ailable Sin!le loop outa!es will not cause 30

EMC Symmetrix ($Max& Enginuity ,-.%

EMC Symmetrix <>Max systems were introduced back in the month of )pril 200-. 1ith this new !eneration of Symmetrix came a new name <>Max and a new En!inuity family of microcode C'D?.

1ith this family of microcode C'D?E there are D ma#or areas of enhancements as listed below.
31

Base enhancements -anagement Bnter/aces enhancements SA*F /=nctiona ity changes 2ime/inder Per/ormance enhancements Cpen Aep icator S=pport and enhancements Virt=a i+ation enhancements )lso EMC introduced SMC D.0 %Symmetrix Mana!ement Console& for mana!in! this !eneration of Symmetrix. 1ith En!inuity family C'D? you also need solutions enabler D.0 .he initial En!inuity was release C'D?.,2,.,02, a month into the release we saw a new emulation and SP release C'D?.,22.,0= and the latest release as of ,'th of /une 200- is C'D?.,2=.,0?. 1ith these new emulation and SP releases, there aren(t any new features added to the microcode rather #ust some patches and fixes related to the maintenance, 30L3: and en"ironmentals. *ased on some initial list of enhancements by EMC and then a few we heard at EMC 1orld 200-, to sum up, here are all of those. AV4% Aaid Virt=a 4rchitect=re% 1ith En!inuity C'D? EMC introduced the concept of sin!le mirror positions. 9ormally it has always been challen!in! to reduce the mirror positions since they cap out at ?. 1ith enhancements to mirror positions related to S;37 en"ironments and ;) 3 C %=3 I ,P, D3 I,P& L ;) 3 B %B3I2P, ,?3I2P& L ;) 3 , de"ices, now it will open doors to some further mi!ration and data mo"ement opportunities related to S;37 and ;) 3 de"ices. Large Vo =me S=pport% 1ith this "ersion of En!inuity, we will see max "olume siGe of 2?04* for open systems and 22=4* for mainframe systems with C,2 hypers per dri"e. .he maximum dri"e siGe supported on Symmetrix <>Max system is ,.* S).) dri"es. .he maximum dri"e siGe supported for E73 on a Symmetrix <>Max system is ?004*. *ynamic Provisioning%

32

Enhancements related to S;37 and *C< de"ice attributes will o"erall impro"e efficiency durin! confi!uration mana!ement. 1ill pro"ide methods and means for faster pro"isionin!. 1onc=rrent 1on/ig=ration 1hanges% Enhancements to concurrent confi!uration chan!es will allow the customer and customer en!ineer to perform throu!h Ser"ice Processor and throu!h Solutions enabler certain procedures and chan!es that can be all combined and executed throu!h a sin!le script rather than runnin! them in a series of chan!es. Service Processor BP Bnter/ace% )ll Ser"ice Processors attached to the Symmetrix <>Max systems will ha"e Symmetrix Mana!ement Console D.0 on it, that will allow customers to lo!in and perform Symmetrix related mana!ement functions. )lso the ser"ice processor will ha"e capabilities to be mana!ed throu!h the customer(s current P %network& en"ironment. Symmetrix Mana!ement Console will ha"e to be licensed and purchased from EMC for <>Max systems. .he prior "ersions of SMC were free. SMC will now ha"e capabilities to be opened throu!h a web interface. SA*F Enhancements% 1ith introduction of ;) 3 C and ;) 3 B de"ices on the pre"ious !eneration of Symmetrix %3M5>?&, now the <>Max offers a =00U better performance with . mefinder and other S;37 layered apps to make the process "ery efficient and resilient. Enhanced Virt=a L>3 2echno ogy% Enhancements related to <irtual :09 .echnolo!y will allow customers to non> disrupti"ely perform chan!es to the location of disk either physically or lo!ically and further simplify the process of mi!ration on "arious systems. Virt=a Provisioning% <irtual Pro"isionin! can now be pushed to ;) 3 C and ;) 3 B de"ices that were restricti"e in the pre"ious "ersions of Symmetrix. 4=toprovisioning ;ro=ps% 0sin! )utopro"ision! !roups, customers will now be able to perform de"ice maskin! by creatin! host initiators, front>end ports and stora!e "olumes.
33

.here was an EMC Challen!e at EMC 1orld 200- Symmetrix corner for auto pro"isionin! the symms with a minimum number of clicks. )utopro"isionin! !roups are supported throu!h Symmetrix Mana!ement Console. So the abo"e are the hi!hli!hts of EMC Symmetrix <>Max En!inuity C'D?. )s new "ersion of the microcode is released later in the year stay plu!!ed in for more info.

EMC Symmetrix ($Max& Su!!orted dri'e ty!es

1ith the release of EMC Symmetrix <>Max systems, EMC introduced hi!her density E73(s %Enterprise 7lash 3isks& than bein! supported on its predecessor, the EMC Symmetrix 3M5>?. *elow are some stats related to the supported dri"e types on a Symmetrix <> Max system with C'D?.,2=.,0? microcode. Possibly with introduction of 7)S. %7ully )utomated Stora!e .ierin!& later in the year we will see an up!rade to the microcode family for the <>Max systems to C-DB, also with that expect a much denser E73 support. n the mean time we should atleast see some additional support for <Sphere ?.0 %<mware& in 200- with C'DC family of microcode. 1ith that we should see sort of a new concept of 7ederation with Symmetrix <>Max Systems where EMC mi!ht !i"e some clues on how the ' en!ine systems mi!ht be expanded into either ,B or =2 en!ine systems.

3*

.he followin! siGe dri"es types are supported with Symmetrix <>Max Systems at the current microcode C'D?E ,?B 4*, 200 4*, =00 4*, ?00 4*, ?C0 4*, ,000 4*.

*rive 2ypes5 Aotationa Speed and Formatted 1apacity

1!( ;B F1 *rive 3ri"e SpeedE ,CO 8pen Systems 7ormat CapE ,?=.C= 4* Mainframe 7ormat CapE ,=-.=? 4* &00 ;B F1 *rive 3ri"e SpeedE ,CO 8pen Systems 7ormat CapE 2''.,- 4* Mainframe 7ormat CapE 2D-.DD 4* !00 ;B F1 *rive 3ri"e SpeedE ,0O 8pen Systems 7ormat CapE =-=.'? 4* Mainframe 7ormat CapE ='2.=2 4* !#0 ;B F1 *rive 3ri"e SpeedE ,CO 8pen Systems 7ormat CapE ?=2.2- 4* Mainframe 7ormat CapE ?,-.B? 4* 1000 ;B S424 BB *rive 3ri"e SpeedE D.2O 8pen Systems 7ormat CapE -'?.', 4*

3%

Mainframe 7ormat CapE -CB.02 4* "00 ;B EF* 3ri"e SpeedE 9ot )pplicable 8pen Systems 7ormat CapE ,-B.-D 4* Mainframe 7ormat CapE ,-,.2, 4* !00 ;B EF* 3ri"e SpeedE 9ot )pplicable 8pen Systems 7ormat CapE =-=.'? 4* Mainframe 7ormat CapE ='2.== 4* Support for D=4* and ,?B4* E73(s ha"e been dropped with the Symmetrix <>Max Systems, they will still be supported with the Symmetrix 3M5>? Systems which in addition to D= 4* and ,?B4* also supports 2004* and ?004* E73(s.

Symmetrix

($Max

Systems&

S/D0

Enhan*ements and 1er+orman*e

So this was one of those posts that always wanted to write related to Symmetrix <>Max and S;37 enhancements that were incorporated with the C'D? microcode. $esterday mornin! had a chat with a friend and ended up talkin! about S;37 and then later in the day had another interestin! conference call on S;37 with a potential customer. So really thou!ht, today was the day should !o ahead and finish this post.
3(

Here are the high ights o/ SA*F /or V,-ax Systems SA*F ;ro=ps% ,. 2C0 S;37 4roups with Symmetrix <>Max %C'D?& Systems. n the prior !eneration Symmetrix 3M5>? %CDD=&, it had support for ,2' !roups. :o!ically e"en with 2P* of stora!e, "ery seldom do customers hit that mark of 2C0 !roups. 2. B? S;37 !roups per 7C L 4i!E channel. n the pre"ious !eneration Symmetrix 3M5>? %CDD=&, there was support for =2 !roups per channel. SA*F 1onsistency s=pport <ith " mirrors% ,. Each le! is placed in a separate consistency !roup so it can be chan!ed separately without affectin! the other. 4ctive SA*F Sessions and additionDremova o/ devices% ,. 9ow customers can add or remo"e de"ices from a !roup without in"alidin! the entire !roup, upon the de"ice becomin! fully synced it should be added to the consistency !roup %with pre"ious !eneration Symmetrix 3M5>?, one de"ice add or remo"e would cause the entire !roup to in"alidate re2uirin! the customers to run full establish a!ain&. SA*F Bnva id 2racks% ,. .he Wlon! tailQ 6 last few tracks search has been "astly impro"ed. .he search procedure and methods for the Wlon! tail( has been completely redesi!ned. t is a known fact with S;37, that the last in"alid tracks take a lot of time to sync as its !oin! throu!h the cache search. 2. .he S;37 establish operations speed is at least impro"ed by ,05X see the numbers below in the performance data. 2ime/inderD1 one E SA*F restores% ,. Customers can now restore Clones to ;2 and ;2(s to ;,(s simultaneously, initially with the 3M5>?(s this was a =>step process. SA*F DE*P 9Extended *istance Protection:% ,. =>way S;37 for lon! distance with secondary site as a pass throu!h site usin! Cascaded S;37. 2. 7or Primary to Secondary sites customers can use S;37LS, for Secondary to .ertiary sites customer can use S;37L)
3,

=. 3iskless ;2, pass>throu!h de"ice, where the data does not !et stored on the dri"es or consume disk. ;2, is really in cache so the host is not able to access it. 9eeds more cache based on the amount of data transferred. ?. ;, A S 6Y ;2, A ) 6Y ;2 %Production site Y Pass>thru Site Y 8ut>of> re!ion Site& C. Primary %;,& sites can ha"e 3M5>= or 3M5>? or <>Max systems, .ertiary %;2& sites can ha"e 3M5>= or 3M5>? or <>Max systems, while the Secondary %;2,& sites needs to ha"e a <>Max system. A"" F *=a Secondary *evices% ,. ;22 de"ices can act as tar!et de"ices for 2 x ;, de"ices 2. 8ne Source de"ice can perform ;ead write on ;22 de"ices =. ;.8 impro"ed with primary site !oin! down Cther Enhancements% ,. 2. =. ?. C. B. D. 3ynamic Cache Partitionin! enhancements MoS for S;37LS Concurrent writes :inear Scalin! of L8 ;esponse times e2ui"alent across !roups <irtual Pro"isionin! supported with S;37 S;37 supports linkin! <irtual Pro"isioned de"ice to another <irtual Pro"isioned de"ice. '. Much more faster dynamic S;37 operations -. Much more faster failo"er and failback operations ,0.Much more faster S;37 sync(s Some very imited V,-ax Per/ormance Stats re ated to SA*F% ,. 2. =. ?. C. B. D. =BU impro"ed 7C performance 7C L8 per channel up to C000 8PS 4i!E L8 per channel up to ?000 8PS 2B0 M*Lsec ;) channel L8 rate, with 3M5>? it was ,-0 M*Lseconds -0 M*Lsec 4i!E channel L8 rate, with 3M5>? it was almost the same =BU impro"ement on S;37 Copy o"er 7C 9ew S;37 pairs can be created in D secs compared to CC secs with pre"ious !enerations '. ncremental establishes after splits happen in = seconds compared to B secs with pre"ious !enerations -. 7ull S;37 establishes happen in ? seconds compared to CC seconds with pre"ious !enerations

33

,0.7ailback S;37 happen in ,- seconds compared to ?D seconds with pre"ious !enerations

EMC

Symmetrix

Enginuity

2!erating

En'ironment
.he Clariion En"ironment is !o"erned by 7lare Code and the Symmetrix L 3M5 by En!inuity Code. .he En!inuity Code was de"eloped internally at EMC and so far to my knowled!e not outsourced anywhere for de"elopment purposes. EMC En!ineerin! is the crown of EMC, in"entin! new technolo!y and pushin! the en"elope in terms of definin! future products, technolo!ies and markets. 0nlike the Clariion 7lare Code that is customer up!radeable, the code on EMC Symmetrix L 3M5 is up!raded throu!h EMC only. .his code sits on the Ser"ice Processor but also !ets loaded on all the 3irectors durin! installation and up!rades. 8n these 3irectors is also loaded the * 9 7 :E %Confi!uration of the Symmetrix& alon! with the Emulation code. .he initial En!inuity code load and * 9 7 :E setup is performed when the customer first purchases the machine and is customiGed based on their S)9 en"ironment. )s new En!inuity code releases hit market, customers can !et the up!rades from EMC. t is "ery normal for customers to !o throu!h multiple code up!rades durin! the = to C year life cycle of these machines. .he ser"ice processor houses the code, but the Symmetrix L 3M5 can be rebooted or can be fully functional without the Ser"ice processor present. .he Ser"ice processor will allow an EMC trained and 2ualified en!ineer to perform dia!nostics and enable the call home feature for proacti"e fixes and failures. 7or any host related confi!urations chan!es, the presence of this ser"ice processor includin! EMC(s Symmwin Software is absolutely necessary.

3.

1ithout the presence of abo"e it becomes impossible to obtain confi!uration locks on the machine throu!h ECC or Symcli, restrictin! customer * 9 7 :E Chan!es for reconfi!uration. En!inuity Code le"el break down are based on the 7amily of machines. .ypically #0.. versions are limited to Symm =.0 Models %=,00LC,00, =200LC200, =C00LCC00&. .he &'xx "ersions are limited to Symm 2.C Models %?200,??00, ?'00& .he code le"els #"(#5 #"((5 #"(' are limited to Symm ?.0 %===0LC=00, =?00LC?=0, =D00LCD00& and Symm ?.' family %=B=0LCB=0, ='=0LC'=0, =-=0LC-=0& of machines. 7or Symm C.0 and C.C the En!inuity code "ersions are ##(' and ##($. .he last code "ersion for the Symm C.0 and C.C is ##($.($."$. .here will be no code up!rades for the Symmetrix after this "ersion. 4oin! into the 3M5, F 3M52 %3M5'00, 3M5,000, 3M52000, 3M5=000&, code le"els #(()5 #('0 and #('1 are the ma#or family En!inuity Code le"els. 7or the 3M5= and 3M5? code le"els #''15 #''" and #''& are the ma#or releases. .he latest "ersion #('1.'#.'# is the last known "ersion for the 3M5, and 3M52 family of machines.

.he !uidelines for En!inuity Code le"el breakdowns is as follows. Examp e #('1.'#.'# 9P ease see the co or coded system be o<:

7irst .wo di!its C0JSymm =.0 C2JSymm ?.0, ?.' CCJSymm C.0, C.C CB J 3M5,L3M52

*0

CD J 3M5=L3M5?

.he next two di!its are BD, B' J Microcode 7amily, Ma#or Symmetrix ;eleases for Symm C.0LSymm C.C B-, D0, D, J Microcode 7amily, Ma#or Symmetrix>3M5 ;eleases for 3M5,L3M52 D,, D2, D= J Microcode 7amily, Ma#or Symmetrix>3M5 ;eleases for 3M5=L3M5?

.he next two di!its are Emulation 9umber desi!nated as EE

.he last two di!its are 7ield ;elease le"el Ser"ice Processor Code :e"el %Symmwin <ersion&

.he "ersion of the En!inuity code will define what functionality and features the Symmetrix L 3M5 will ha"e for that !eneration. )s the hardware !ets better and faster, the En!inuity Code has to impro"e and add features to perform alon! with it.

*1

EMC Symmetrix& )3N +ile

EMC Symmetrix * 9 file, lar!ely an unknown topic in the stora!e industry and practically there is no a"ailable information related to it. .his post is #ust an attempt to shed some li!ht as to what a * 9 file is, how it works, what(s in it and why is it essential with the En!inuity code. . Some EMC folks ha"e capitaliGed on the * 9 file as to the personality it brin!s to the Symmetrix, while the EMC competition always uses it a!ainst them as it introduces complexities in the stora!e en"ironment with mana!ement and chan!e control. . Personally feel a Symmetrix wouldn(t be a Symmetrix if the * 9 file weren(t there. .he personality, characteristics, robustness, compatibility, flexibility, inte!ration with 8S(s, etc wouldn(t be there if the * 9 file didn(t exist. . 1ith the total number of 8S(s, de"ice types, channel interfaces and fla!s it supports today, sort of makin! it one of the most compatible stora!e arrays in the market. .he confi!uration and compatibility on the Symmetrix can be "erified usin! the E>:ab na"i!ator a"ailable on Powerlink. . So here are some /acts abo=t the BB3 /i e

8nly used with Symmetrix systems %En!inuity Code& . * 9 file stands for * 9);$ file. . * 9 file holds all information about the Symmetrix confi!uration . 8ne * 9 file per system serial number is re2uired. . * 9 file was used with Symmetrix 4en , in ,--0 and is still used in 20,0 with Symmetrix <>Max systems. .

*2

* 9 file holds information on S;37 confi!urations, total memory, memory in slots, serial number of the unit, number of directors, type of directors, director fla!s, en!ines, en!ine ports, front end ports, back end ports, dri"es on the loop, dri"es on the SCS bus, number of dri"es per loop, dri"e types in the slots, dri"e speeds, "olume addresses, "olume types, meta(s, de"ice fla!s and many more settin!s. . .he setup for host connection if the 8S is 8pen Systems or Mainframe en"ironments usin! 7 C89, ESC89, 4bE, 7C, ;7, etc is all defined in the * 9 file. )lso director emulations, dri"e formats if 8S3 or CO3, format types, dri"e speeds, etc is all defined in the * 9 file. . * 9 file is re2uired to make a system acti"e. t is created based on customer specifications and installed by EMC durin! the initial setup. . )ny on!oin! chan!es in the en"ironment related to hardware up!rades, definin! de"ices, chan!in! fla!s, etc is all accomplished usin! * 9 file chan!es. . * 9 file chan!es can be accomplished = ways. . * 9 file chan!e for hardware up!rades is typically performed by EMC only. . * 9 file chan!e for other chan!es that are de"ice, director, fla!s, meta(s, S;37 confi!urations etc is either performed throu!h the S$M)P infrastructure usin! SymC: or ECC %9ow onix& or SMC %Symmetrix Mana!ement Console& by the customer. %Edited based on the commentsE 8nly some chan!es now re2uire traditional * 9 file chan!e, typically others are performed usin! sys calls in en!inuity en"ironment& . Solutions enabler is re2uired on the Symcli, ECC, SMC mana!ement stations to enable S$M)P infrastructure to operate. . <CM3* needs to be setup on the Symmetrix for SymC: , ECC, SMC related chan!es to work. . 4atekeeper de"ices need to be setup on the Symmetrix front end ports for SymC: , ECC, SMC chan!es to work . 7or Symmetrix 8ptimiGer to work in your en"ironment, you need 3;< de"ices setup on your Symmetrix.%E3 .E3 based on commentsE 8nly

*3

re2uired until 3M5 platform. 4oin! forward with 3M5=L? F <>Max platforms it uses sys calls to perform these 8ptimiGer chan!es&. . Back in the day )ll and any * 9 file chan!es on the Symmetrix =.0, Symmetrix ?.0 used to be performed by EMC from the Ser"ice Processor. 8"er the years with introduction of S$M)P and other layered software products, now seldom is EMC in"ol"ed in the up!rade process. . Hard<are =pgrades * 9 7ile chan!es typically ha"e to be initiated and performed by EMC, a!ain these are the hardware up!rades. f the customer is lookin! at addin! =24*(s of Cache to the existin! 3M5>? system or addin! new 7ront End connecti"ity or up!radin! ,200 dri"e system to ,-20 dri"es, all these re2uire * 9 file chan!es initiated and performed by EMC. .o my understandin! the turn around time is #ust a few days with these chan!es, as it re2uires chan!e control and other processes within EMC. . 1=stomer initiated changes Confi!uration chan!es around front end ports, creatin! "olumes, creatin! meta(s, "olume fla!s, host connecti"ity, confi!uration fla!s, S;37 "olume confi!urations, S;37 replication confi!urations, etc can all be accomplished throu!h the customer end usin! the S$M)P infrastructure %with SymC: or ECC or SMC&. . Engin=ity =pgrade 0p!radin! the microcode %En!inuity& on a 3M5 or a <>Max is not a * 9 file chan!e, but rather is a code up!rade. *ack in the days, many up!rades were performed offline, but in this day and a!e, all chan!es are online and accomplished with minimum pains. .

**

2oday So EMC has mo"ed 2uite ahead with the Symmetrix architecture o"er the past 20 years, but the underlyin! * 9 file chan!e re2uirements ha"en(t chan!ed o"er these ' !enerations of Symmetrix. )ny and all * 9 file chan!es are recommended to be done durin! 2uite times %less 8PS&, at schedule chan!e control times. )!ain these would include the ones that EMC is performin! from a hardware perspecti"e or the customer is performin! for de"iceLfla! chan!es. . 2he process 3urin! the process of a * 9 file chan!e, the confi!uration file typically endin! with the name Z.* 9 is loaded to all the frontend directors, backend directors, includin! the !lobal cache. )fter the upload, the system is refreshed with this new file in the !lobal cache and the process makes the new confi!uration chan!es acti"e. .his process of refresh is called M: % nitial Memory :oad& and the * 9 file is typically called MP: % nitial Memory Pro!ram :oad& file. ) customer initiated * 9 file works in a similar way, where the S$M)P infrastructure that resides on the ser"ice processor allows the customer to interface with the Symmetrix to perform these chan!es. 3urin! this process, the scripts "erify that the customer confi!urations are "alid and then perform the chan!es and make the new confi!uration acti"e. .o 2uery the Symmetrix system for confi!uration details, reference the SymC: !uide. Some standard commands to 2uery your system would include symcf!, symcli, symde", symdisk, symdr", syme"ent, symhost, sym!ate, symin2, symstat commands and will help you na"i!ate and find all the necessary details related to your Symmetrix. )lso similar information in a 40 can be obtained usin! ECC and SMC. *oth will allow the customer to initiate S$M)P chan!es. 0nless somethin! has chan!ed with the <>Max, typically to !et an excel based representation of your * 9 file, ask your EMC CE. . Bss=es $ou cannot run two * 9 files in a sin!le system, thou!h at times the system can end up in a state where you can ha"e multiple * 9 files on "arious
*%

directors. .his phenomenon typically doesn(t happen to often, but an automated script when not finished properly can put the system in this state. )t this point the Symmetrix will initiate a call home immediately and the PSE labs should typically be able to resol"e these issues. )dditional software like Symmetrix 8ptimiGer also uses the underlyin! * 9 file infrastructure to make chan!es to the stora!e array to mo"e hot and cold de"ices based on the re2uired defined criteria. .here ha"e been 2uite a few known cases of Symmetrix 8ptimiGer causin! the abo"e phenomenon of multiple * 9 files. , .hou!h many critics will disa!ree with that statement. %E3 .E3 based on commentsE 8nly re2uired until 3M5 platform. 4oin! forward with 3M5=L? F <>Max platforms it uses sys calls to perform these 8ptimiGer chan!es&. . 3C2E% 8ne piece of ad"ice, ne"er run S$MC: or ECC scripts for * 9 file chan!es throu!h a <P9 connected desktop or laptop. )lways run all necessary SymC: L SMC L ECC scripts for chan!es from a ser"er in your local en"ironment. <ery hi!hly recommend, ne"er attempt to administer your Symmetrix system with an iPhone or a *lackberry. +ope in your 2uest to !et more information on * 9 files, this ser"es as the startin! point.

EMC Symmetrix& Cal*ulations +or "eads, ra*ks, Cylinders, 4)

+ere is the 2uick and dirty math on EMC Symmetrix +eads, .racks, Cylinder siGes to actual usable 4*(s of space. *ased on different !enerations of Symmetrix systems, here is how the con"ersions work.

*(

*efore we #ump into each model type, let(s look at what the basics are, with the followin! calculations. . . .here are s number of splits %hyper& per physical de"ice. .here are n number of cylinders per split %hyper& .here are 1# tracks per cylinder %heads& .here are either (! or 1"$ blocks of C,2 bytes per track . )ll the calculations discussed here are for 8pen Systems %7*)& de"ice types. 3ifferent de"ice emulations like =='0O, ==-0>,, ==-0>2, ==-0>=, ==-0>?, ==-0>2D, ==-0>C? ha"e different bytesLtrack, different bytesLcylinder and cylindersL"olume. . Symmetrix $000D*-.D*-.," Series En!inuity CodeE CCBD, CCB', CBB-, CBD0, CBD, ncludes EMC Symmetrix ',=0, '2=0, '?=0, 'C=0, 'D=0, ''=0, 3M5,000, 3M52000, 3M5=000 and "arious different confi!urations within those models. GB = Cylinders * 15 * 64 * 512 / 1024 / 1024 / 1024 e!E B,?0 Cylinder de"ices e2uates to 2.', 4* of usable data 6140 * 15 * 64 * 512 / 1024 / 1024 / 1024 = 2.81 GB Cylinders = GB / 15 / 64 / 512 * 1024 * 1024 * 1024 1here ,C J tracks per cylinder B? J blocks per track C,2 J bytes per block
*,

,02? J con"ersions of bytes to kb to mb to !b. . Symmetrix *-.,&D*-.,! Series En!inuity CodeE CDD,, CDD2, CDD= ncludes EMC Symmetrix 3M5>=, 3M5>? and "arious different confi!urations within those models. GB = Cylinders * 15 * 128 * 512 / 1024 / 1024 / 1024 E!E BCC20 Cylinder de"ice e2uates to C-.-D 4* of usable data 65540 * 15 * 128 * 512 / 1024 / 1024 / 1024 = 59.97 GB Cylinders = GB / 15 / 128 / 512 * 1024 * 1024 * 1024 ,C J tracks per cylinder ,2' J blocks per track C,2 J bytes per block ,02? J con"ersions of bytes to kb to mb to !b . Symmetrix V,-ax En!inuity CodeE C'D? ncludes EMC Symmetrix <>Max and "arious different confi!urations within this model. GB = Cylinders * 15 * 128 * 512 / 1024 / 1024 / 1024 E!E 2B2BB' Cylinder de"ice e2uates to 2?0.?D 4* of usable data 262668 * 15 * 128 * 512 / 1024 / 1024 / 1024 = 240.47 GB Cylinders = GB / 15 / 128 / 512 * 1024 * 1024 * 1024 ,C J tracks per cylinder

*3

,2' J blocks per track C,2 J bytes per block ' bytes J C20>C,2 used for .,0>3 7 ,02? J con"ersions of bytes to kb to mb to !b 3ri"e format on a <>Max is C20 bytes, out of which ' bytes are used for .,0> 3 7 % ) post on 3M5>? and <>Max differences&.

EMC Symmetrix 0ile System 5S0S6

<ery little is known about the Symmetrix Fi e System lar!ely known as SFS. Symmetrix 7ile System is an EMC P and practically only used within the Symmetrix en"ironment for housekeepin!, security, access control, stats collection, performance data, al!orithm selection, etc. f there are any facts about S7S that are known to you, please feel free to lea"e a comment. .his post talks about the effects of S7S and not really the underlyin! file system architecture. Some facts about the Symmetrix Fi e System are hi!hli!hted below.

Symmetrix 7ile System %S7S& resides on "olumes that ha"e specially been created for this purpose on the Symmetrix S7S "olumes are created durin! the initial En!inuity 8peratin! En"ironment load % nitial install& ? <olumes %2 Mirrored Pairs& are created durin! this process S7S "olumes were introduced with Symmetrix Series '000, En!inuity CCBD and CCB'

1haracteristics

? S7S "olumes are spread across multiple 3isk 3irectors %*ackend Ports& for redundancy

*.

S7S "olumes are considered as reser"ed space and not a"ailable to use by the host Symmetrix '000 SeriesE ? S7S "olumes, =4* each %cylinder siGe B,?0&. ;eser"ed space is =4* x ? "ols J ,2 4* total Symmetrix 3M5L3M5>2E ? S7S "olumes, =4* each %cylinder siGe B,?0&. ;eser"ed space is =4* x ? "ols J ,2 4* total Symmetrix 3M5>=L3M5>?E ? S7S "olumes, B4* each %cylinder siGe B,?0&. ;eser"ed space is B4* x ? "ols J 2? 4* total, % t(s different how the 4* is calculated based on cylinder siGe on a 3M5L3M5>2 "s a 3M5>=L3M5>?& Symmetrix <>MaxE ? S7S "olumes, ,B4* each, ;eser"ed space is ,B4* x ? "ols J B?4* total S7S "olumes cannot reside on E73 %Enterprise 7lash 3ri"es& S7S "olumes cannot be mo"ed usin! 7)S. ", andLor 7)S. "2 S7S "olumes cannot be mo"ed usin! Symmetrix 8ptimiGer S7S "olumes cannot reside on <ault 3ri"es or Sa"e <olumes S7S "olumes are specific to a Symmetrix %Serial 9umber& and do not need mi!ration S7S "olumes are mana!ed throu!h 3isk 3irectors %*ackend Ports& only S7S "olumes cannot be mapped to 7iber 3irectors %now 7E 6 7rontend Ports&

E//ects

S7S "olumes are write enabled but can only be interfaced and mana!ed throu!h the 3isk directors %*ackend Ports&. S7S "olumes can !o write disabled, which could cause issues around <CM3*. <CM3* issues can cause host path %+*)& and disk access issues. S7S "olume corruption can cause hosts to lose access to disk "olumes. f S7S "olumes !et un>mounted on a 7iber 3irector %7rontend Port&, can result into 30 %3ata 0na"ailable& situations.

Fixes

Since the S7S "olumes are only interfaced throu!h the 3isk 3irectors %*ackend Ports&, the PSE lab will need to be in"ol"ed in fixin! any issues. S7S "olumes can be <.8C(ed %formatted& and some key information below will need to be restored upon completion. )!ain this function can only be performed by PSE lab. S7S "olumes can be formatted while the Symmetrix is runnin!, but in a SCS >= P4; reser"ation en"ironment it will cause a cluster outa!e andLor a split brain.
%0

9o Symmetrix software %.imefinder, S$MC: , ECC, etc& will be able to interface the system while the S7S "olumes are bein! formatted. .he security auditin! L access control feature is disabled durin! the format of S7S "olumes, causin! any Symmetrix internal or external software to stop functionin!. )ccess Control 3atabase and S;37 host components L !roup settin!s will need to be restored after the S7S format

4ccess D >se case

)ny * 9 file chan!es to map S7S "olumes to host will fail. S7S "olumes cannot be mana!ed throu!h S$MC: or the Ser"ice Processor without PSE help. S$M)P %infrastructure& works alon! with S$MM1 9 and S7S "olumes to obtain locks, etc durin! any S$MC: L S$MM1 9 L ECC acti"ity %e!. *in Chan!es&. Since 7)S. ", and 7)S. "2 reside as a policy en!ine outside the Symmetrix, it uses the underlyin! S7S "olumes for chan!es %locks, etc&. Performance data relatin! to 7)S. would be collected within the S7S "olumes, which 7)S. policy en!ine uses to !au!e performance. Performance data relatin! to Symmetrix 8ptimiGer would be collected within the S7S "olumes, which 8ptimiGer uses to !au!e performance. 8ther performance data collected for the 3MSP %3ynamic Mirror Ser"ice Policy&. )ll )udit lo!s, security lo!s, access control database, )C:(s etc is all stored within the S7S "olumes. )ll S$MC: , S$M)P , Solutions enabler, host, interface, de"ices, access control related data is !athered on the S7S "olumes. 1ith the 3M5>? and the <>Max, all ser"ice process access, ser"ice processor initiated actions, denied attemptsX ;S) lo!s, etc are all stored on S7S "olumes.

>nkno<ns

S7S S7S S7S S7S S7S

structure is unknown architecture is unknown !arba!e collection and discard policy is unknown records stored, indexin!, etc is unknown inode structures, function calls, security settin!s, etc is unknown

)s more information !ets a"ailable, will try to update this post. +ope this is useful with your research on S7S "olumes@

%1

EMC Symmetrix& (CMD) and 7C8X

V1-*B% <olume Control Mana!er 3atabase 41L.% )ccess Control :o!ix V1-% <olume Control Mana!er de"ice %where the database resides& V1- ;atekeeper% <olume Control Mana!er 4atekeeper %database doesn(t reside on these de"ices& SFS Vo =mes% Symmetrix 7ile System <olumes . f you work with EMC Symmetrix systems, you know the importance of <CM3*. ntroduced with Symmetrix ?.0 and used in e"ery !eneration after that, <CM3* stands for <olume Control Mana!er 3atabase&. )lso in the latest !eneration of systems the <CM de"ice is at times also referenced as <CM 4atekeeper. <CM3* is a relati"ely small de"ice that is created on the Symmetrix system that allows for hosts access to "arious de"ices on the Symmetrix. <CM3* keeps an in"entory of which de"ices ha"e access to which host %+*)(s&. 1ithout a <CM3* in place, host systems will not be able to access the Symmetrix. .he <CM3* should be backed up on re!ular inter"als and would be helpful in a rainy day. .he <CM3* de"ice siGe !rew alon! with new !enerations of Symmetrix systems that !ot introduced, primarily a means to keep a track of more supported de"ices %hypers L splits& on these platforms. 1ith the introduction of Symmetrix <>Max, the <CM3* concept is now a bit chan!ed to )C:5 %)ccess Control :o!ix&. )ccess :o!ix is bein! used on the Clariion systems for years now. .

%2

Here are a /e< things to consider <ith V1-*B

8n the older Symmetrix systems %?.0, ?.', C.0 and C.C&, the <CM3* %de"ice& is mapped to all the channels, host n these systems the <CM3* access is typically restricted by <olume :o!ix or )C: %access control lists& 1ith the Symmetrix 3M5, 3M52 Systems 6 En!inuity Code CBD0, CBD, the <CM de"ice only re2uires to be mapped to the Mana!ement stations Mana!ement stations include S$MC: Ser"er L onix Control Center Ser"er L Symmetrix Mana!ement Console )t all !i"en times on the 3M5, 3M52 platforms, the <CM3* would need to be mapped to at least one station to perform online S33; chan!es. )lternati"ely this problem of not ha"in! de"ice mapped to at least one host can also be fixed by the PSE lab Mappin! <CM3* to multiple hosts, channels may make the de"ice "enerable to crashes, potential tamperin!, de"ice attributes and data chan!e $ou can write disable <CM3* to a"oid the potential of the abo"e 1ith these systems, the host can communicate to the <CM3* "ia Syscalls .he <CM Edit 3irector 7la! %fibrepath& needs to be enabled for mana!ement stations to see <CM de"ice .he database %de"ice maskin! database& of the <CM3* resides on the S7S "olumes. .his feature was introduced with 3M5>= L 3M5>? %CDD2 "ersion of microcode&. ) B cylinder <CM 4atekeeper de"ice is okay to use with these "ersions of microcode. Startin! Symmetrix <>Max systems, the concept of )C:5 was introducted for )uto Pro"isionin! etc. <CM "olumes are re2uired to be mirrored de"ices like S7S "olumes

. Vario=s di//erent types o/ V1-*B 2ype 05 2ype 15 2ype "5 2ype &5 2ype !5 2ype #5 2ype (

2ype 0% Symmetrix ?.0, =2 3irector System, ,B cylinder de"ice siGe, <olume :o!ix 2.x 2ype 1% Symmetrix ?.', B? 3irector System, ,B cylinder de"ice siGe, ES9 Mana!er ,.x 2ype "% Symmetrix C.0LC.C, B? 3irector System, ,B cylinder de"ice siGe, ES9 Mana!er 2.x

%3

2ype &% Symmetrix 3M5, supports =2 fibreL =2 iSCS initiator records per port, 2? cylinder de"ice in siGe. En!inuity CCB-, Solutions Enabler C.2, Support '000 de"ices 2ype !% Symmetrix 3M5L3M5>2, supports B? fibreL ,2' iSCS initiator records per port, ?' cylinder de"ice in siGe. En!inuity CBD0, Solutions Enabler C.=, Supports '000 de"ices 2ype #% Symmetrix 3M5L3M5>2, supports B? fibre L ,2' iSCS initiator records per port, -B cylinder de"ice in siGe, En!inuity CBD,, Solutions Enabler B.0, Supports ,B000 de"ices 2ype (% Symmetrix 3M5>=, 3M5>?, supports 2CB fibre L C,2 iSCS initiator records per port, -B cylinder de"ice in siGe, En!inuity CDD,, CDD2 Solutions Enabler B.0, Supports B?000 de"ices

. 3otes abo=t vario=s 2ypes o/ V1-*B

.ype = of <CM3* can be con"erted to .ype ? <CM3* %code up!rade from CBB- to CBD0 to CBD,& Solutions enabler C.2 and Solutions Enabler C.= can readLwrite .ype = <CM3* Solutions enabler C.= can readLwrite .ype ? <CM3* <CM3* de"ice is recommended to be a certain siGe, but it is okay to use a lar!er siGe de"ice if no choices are a"ailable.

. 1onverting vario=s types o/ V1-*B =sing Sym1LB

f the de"ice cylinder siGe is e2ual with a con"ersion you are attemptin!, the followin! will help you con"ert your <CM3* from type x to type y. o *ackup the de"ice o symmaskdb sid <symmid ba!k"# $ile ba!k"# o Check the <CM3* type usin! o symmaskdb sid <symmid lis% da%abase o Con"ert from type ? to type C o &ymmaskdb sid <symmid !'n(er% (!mdb)%y#e 5 $ile C'(er%$ilename

. 2o initia i+e V1-*B /or the /irst time on a Symmetrix System

%*

1ithin onix Control Center

Click on the Symmetrix array you are tryin! to ini%iali*e %+e ,C-.B Select -askin/ then ,C-.B -ana/emen% and then initialiGe Select a new backup and create a file name Create a file name with .sdm extenstion Click on 0!%i(a%e %+e ,C-.B <CM3* backups are stored at 1+'me1e!!)in$1da%a1+'s%name1da%a1ba!k"#1symmserial1 )lso it will be "iewable within onix Control Center at &ys%ems/&ymme%ri2/,C-.B Ba!k"#s/

. 1ith SymC:

.o 2uery the <CM3* database o symmaskdb sid <symmid lis% da%abase o .o backup and init an existin! <CM3* database symmaskdb sid <symmid ini% $ile ba!k"#

EMC Symmetrix& Dynami* "ot S!ares

.here are two types of sparin! strate!ies a"ailable on EMC Symmetrix Series of machines. *ynamic Hot Sparing% Startin! the Symmetrix ?.0, EMC had introduced dynamic hot spares in its En!inuity code to support customers a!ainst failin! disk dri"es and reducin! the probability of a data loss. )"ailable there onwards on each "ersion of Symmetrix, customers ha"e been able to use this +ot Sparin! technolo!y. .oday the 3ynamic sparin! is a"ailable on Symmetrix ?.0, Symmetrix ?.', Symmetrix C.0, Symmetrix C.C, 3M5, 3M52, 3M5=, and 3M5? systems.

%%

Permanent Spares% 1as introduced startin! the Symmetrix 3M5= products, now a"ailable on 3M5?(s and <>Max systems. belie"e, En!inuity code CDD2 started supportin! Permanent Spares to !uard customers a!ainst failin! disk dri"es to further help reduce any performance, redundancy and processin! de!radation on the Symmetrix systems with features that were not a"ailable with the 3ynamic +ot Sparin!. High ights o/ Permanent Sparing 3ue to some desi!n, performance, redundancy limitations and Symmetrix mirror positions, dynamic hot spares were becomin! a bottleneck related to customer internal #ob processin!, exampleE a failed ,.* S).) dri"e sync to dynamic spare mi!ht take more than ' to ?' hours. 1hile a similar process to remo"e the dynamic spare and e2ualiGe the replaced dri"e mi!ht take the same. 3urin! this time the machine is more or less in a lock down %8perational but not confi!urable&. *=e to these imitations5 a concept o/ Permanent spares <as introd=ced on E-1 Symmetrix systems5 <hich <o= d he p /= /i some gaps the *ynamic hot spares techno ogy has. Fo o<ing are the criteria /or *ynamic Hot Spares.

Some important things to consider <ith *ynamic Hot Sparing ,. Supported throu!h microcode %En!inuity& "ersion startin! Symmetrix 7amily ?.0, support extended throu!h all later releases of En!inuity until 3M5>? %CDD=&. 2. 3ynamic +ot Spares confi!ured and enabled in the backend by an EMC CE. =. 9o * 9 file chan!e is performed as the 3ynamic +ot Spare !ets in"oked or remo"ed upon a disk dri"e failure. ?. 9o * 9 file chan!e is allowed until the 3ynamic +ot Spare is remo"ed from the acti"e used de"ices pool and inserted back into the Spares pool. C. )n EMC CE will need to attend site to replace the failed dri"e and put the dynamic hot spare back in the pool of de"ices a"ailable for sparin!. B. En!inuity does not check for performance and redundancy when the dynamic hot spare is in"oked. D. n the pre"ious !eneration of Symmetrix systems, an exact match %speed, siGe, block siGe& was re2uired with 3ynamic hot spares. Startin! belie"e the CDD2 %3M5= onwards& "ersion of microcode that re2uirement is not necessary. 9ow lar!er or smaller multiple dynamic spares can be spread across protectin! multiple de"ices not ready, the
%(

one to one relationship %failed dri"e to dynamic spare& is not true any more. '. ;elated to performance on 3M5= systems and abo"e, if correct dynamic spares are not confi!ured, customers can see issues around redundancy and performance. Example, ) ,0O dri"e can be in"oked automatically a!ainst a failed dri"e that is ,CO causin! performance issues. )lso a dri"e on the same loop as other raid !roup de"ices can be in"oked as a hot spare, potentially causin! issues if the entire loop was to !o down. -. 3ynamic spares will not take all the characteristics of failed dri"es. Example, mirror positions. ,0.1hile the Permanent Spare or 3ynamic +ot Spare is not in"oked and is sittin! in the machine waitin! for a failure, these de"ices are not accessible from the front end %customer&. .he folks back at the PSE labs, will still be able to interact with these de"ices and in"oke it for you incase of a failure or a proacti"e failure or for any reasons the automatic in"oke fails. ,,. f a Permanent Spare fails to in"oke, a 3ynamic +ot Spare is in"oked, if a 3ynamic +ot Spare fails to in"oke, the customer data stays unprotected. ,2.3ynamic +ot Spare is supported with ;) 3>,, ;) 3>,0, ;) 3>5P, ;) 3>C and "arious confi!urations within each ;aid type. 3ynamic hot sparin! does not work with ;) 3>B de"ices. ,=.)s far as know for the <>Max systems, 3ynamic hot sparin! is not supported.

Some important bene/its o/ *ynamic Hot Sparing ,. 3ynamic +ot Sparin! kicks in when Permanent Sparin! fails to in"oke 2. Pro"ides additional protection a!ainst data loss 9o * 9 file chan!e is performed with 3ynamic +ot Sparin! )s a re2uirement to all the new systems that are confi!ured now, sparin! is re2uired. +ope this pro"ides a "ision into confi!urin! your next EMC Symmetrix on the floor.

%,

EMC Symmetrix& 1ermanent S!aring

.here are two types of sparin! strate!ies a"ailable on EMC Symmetrix Series of machines. *ynamic Hot Sparing% Startin! the Symmetrix ?.0, EMC had introduced dynamic hot spares in its En!inuity code to support customers a!ainst failin! disk dri"es and reducin! the probability of a data loss. )"ailable there onwards on each "ersion of Symmetrix, customers ha"e been able to use this +ot Sparin! technolo!y. .oday the 3ynamic sparin! is a"ailable on Symmetrix ?.0, Symmetrix ?.', Symmetrix C.0, Symmetrix C.C, 3M5, 3M52, 3M5=, and 3M5? systems. Permanent Spares% 1as introduced startin! the Symmetrix 3M5= products, now a"ailable on 3M5?(s and <>Max systems. belie"e, En!inuity code CDD2 started supportin! Permanent Spares to !uard customers a!ainst failin! disk dri"es to further help reduce any performance, redundancy and processin! de!radation on the Symmetrix systems with features that were not a"ailable with the 3ynamic +ot Sparin!. High ights o/ Permanent Sparing 3ue to some desi!n, performance, redundancy limitations and Symmetrix mirror positions, dynamic hot spares were becomin! a bottleneck related to customer internal #ob processin!, exampleE a failed ,.* S).) dri"e sync to dynamic spare mi!ht take more than ' to ?' hours. 1hile a similar process to remo"e the dynamic spare and e2ualiGe the replaced dri"e mi!ht take the same. 3urin! this time the machine is more or less in a lock down %8perational but not confi!urable&. *=e to these imitations5 a concept o/ Permanent spares <as introd=ced on E-1 Symmetrix systems5 <hich <o= d he p /= /i some gaps the *ynamic hot spares techno ogy has. Fo o<ing are the criteria /or Permanent Spares. Some important things to consider <ith Permanent Spares ,. Permanent Spares are supported throu!h the microcode %En!inuity& "ersions startin! the 3M5>= %CDD2 onwards& into the latest !eneration Symmetrix <>Max Systems.

%3

2. .he customer needs to identify and setup the de"ices for Permanent Spares usin! Solutions enabler or an EMC CE should perform a * 9 file chan!e on the machine to enable Permanent Spares and the associated de"ices. =. 1hen the Permanent Spare kicks in upon a failin! L failed dri"e, a * 9 file chan!e locally within the machine is performed usin! the unattended S :. )ny confi!uration locks or un>functional Ser"ice Processors will kill the process before it(s initiated, in this instance the Permanent Spare will not be in"oked but rather will in"oke the 3ynamic +ot Spare. ?. )n EMC CE will not re2uire attendin! the site ri!ht away to replace the dri"e since the Permanent Spare has been in"oked and all the data is protected. )ll failed dri"es where Permanent spares ha"e been in"oked can be replaced in a batch. 1hen the failed dri"e is replaced, it will become a Permanent spare and will !o the Permanent spares pool. C. Confi!uration of Permanent Spares is initiated throu!h * 9 file chan!e, durin! this process, the CE or the customer will re2uired to consider Permanent Spares rules related to performance and redundancy. B. f a Permanent Spare cannot be in"oked due to any reasons related to performance and redundancy, a 3ynamic +ot Spare will be in"oked a!ainst the failin! L failed de"ice. D. .he Permanent Spare will take all the ori!inal characteristics of a failed disk %de"ice fla!s, meta confi!s, hyper siGes, mirror positions, etc& as it !ets in"oked. '. .he rule of thumb with permanent spares is to "erify that the machine has re2uired type L siGe L speed L capacity L block siGe of the related permanent spare dri"es confi!ured. -. $ou can ha"e a sin!le Symmetrix frame with Permanent Spares and 3ynamic +ot Spares both confi!ured. ,0.1hile the Permanent Spare or 3ynamic +ot Spare is not in"oked and is sittin! in the machine waitin! for a failure, these de"ices are not accessible from the front end %customer&. .he folks back at the PSE labs, will still be able to interact with these de"ices and in"oke it for you incase of a failure or a proacti"e measure or for any reasons the automatic in"oke fails. ,,.Permanent spares can be in"oked a!ainst <ault dri"es, if a permanent spare dri"e is a"ailable on the same 3) where the failure occurred. ,2.Permanent spares can be confi!ured with E73(s. belie"e for e"ery 2 3)E(s %=0I dri"es& you ha"e to confi!ure one hot spare E73 %permanent spares&. ,=.Permanent Spares supports ;) 3 type ;) 3 ,, ;) 3 ,0, ;) 3 C, ;) 3 B and all confi!urations within. Some important Bene/its o/ Permanent Sparing
%.

,. )dditional protection a!ainst data loss 2. Permanent sparin! reduces the number of times the data copy is re2uired %one time& instead of dynamic spares that needs to data copy %two times&. =. Permanent sparin! resol"es the problem of mirror positions. ?. Permanent spares %failed& dri"es can be replaced in batches, do not re2uire immediate replacement. C. Permanent spares do not put a confi!uration lock on the machine, while an in"oked dynamic spare will put a confi!uration lock until replaced. B. Permanent spares obey the rules of performance and redundancy while 3ynamic hot sparin! does not.

EMC Symmetrix DMX de'i*e ty!e, C2(D& Ca*he 2nly (irtual De'i*e
+ere is some information on Cache 8nly <irtual 3e"ices. do not ha"e a "ery clear picture on the o"erall operation of this de"ice type, but from a hi!h le"el it can be summed up as followin! based on it characteristics. Startin! with microcode CBD0 on EMC Symmetrix 3M5 Systems, EMC introduced C8<3 %de"ice types&. 1e ha"e seen instances of C8<3 on CBD,, CDD, and CDD2 microcodes, really unknown if they exist on EMC Symmetrix <>Max systems at this point. +ere are some hi!hli!hts on C8<3E

E"en thou!h C8<3(s were introduced on the CBD0 microcode, recommendation is to up!rade to CBD, on the ;2 side of S;37L) before implementin! C8<3(s. 0sed with S;37L) technolo!y for cachin! data on ;2 side.

(0

Symconfi!ure will not allow %block& you to chan!e S;37L) !roup on ;2 side for C8<3 de"ices. $ou will need a * 9 7ile chan!e for this process by the Customer En!ineer. C8<3 is a <irtual 3e"ice but does end up takin! two de"ice numbers within your list of Symmetrix de"ice numbers % belie"e ',-2 de"ice numbers are a"ailable on the early 3M5(s&. f you are usin! C8<3, your confi!ured capacity mi!ht show more than your ;aw Capacity in ECC and Stora!eScope. C8<3(s cannot be snapped usin! . mefinder C8<3(s can only be created and destroyed by * 9 7ile %not throu!h S$MC: & C8<3 is only found on ;2 side of S;37L) Cache is used as part of creatin! the C8<3 C8<3(s are used in pairs, one is used for acti"e S;37L) cycle and , is used for inacti"e S;37L) cycle 9o 3ata is stored on C8<3, used practically for cachin! Primarily introduction of C8<3 was to reduce the write pendin! limits with S;37L)

+a"en(t really seen a lot of customers usin! C8<3 %de"ice types&. *ut sometimes durin! stora!e analysis of customer meta data re"eals these de"ice types since it is assi!ned a de"ice number.

EMC Symmetrix Management Console 5SMC 0or Symmetrix ($Max Systems6

.he Symmetrix Mana!ement Console is a "ery important step towards allowin! customers take control of their Symmetrix <>Max Systems. 1ith the new Symmetrix <>Max comes a new "ersion of Symmetrix Mana!ement Console allowin! customers to mana!e their EMC Symmetrix <>Max Systems throu!h a 40 web browser interface with tons of new added features and wiGards for usability.

(1

.he Symmetrix Mana!ement Console was de"eloped back in the day as a 40 to "iew customers Symmetrix 3M5 en"ironment, o"er years it has e"ol"ed more to be a functional and operational tool to interface the machine for data !atherin! but also to perform chan!es. EMC Solutions Enabler Symcli is a C: based interface to the 3M5 and <>Max Systems, but the SMC complements the C: by allowin! customers to perform more or less similar functions throu!h a 40 . .he looks F feels of SMC also resemble ECC %EMC Control Center& and customers sometime refer it as a ECC>lite %SMC&.

E-1 Symmetrix -anagement 1onso e in action monitoring E-1 Symmetrix V,-ax Systems Some of the important features and benefits of the SMC for <>Max are listed belowE ,& )llows customers to mana!e multiple EMC Symmetrix <>Max Systems

2& ncrease customer mana!ement efficiency by usin! Symmetrix Mana!ement Console to automate or perform functions with a few set of clicks

(2

=& .he Symmetrix Mana!ement Console D.0 only works with Symmetrix <> Max systems ?& .he Symmetrix Mana!ement Console is installed on the Ser"ice Processor of the <>Max System and can also be installed on a host in the S)9 en"ironment. C& Customers can now do trendin!, performance reportin!, plannin! and consolidation usin! SMC B& SMC will help customers reduce their .C8 with <>Max Systems

D& t takes minutes to install. 1indows en"ironment runnin! a 1indows Ser"er 200= alon! with S would be the best choice. ' & .he interface the customers work on is a 40 . t has the looks and feels of ECC and the Console also inte!rates with ECC. -& 9ew Symmetrix <>Max systems are confi!ured and mana!ed throu!h the Symmetrix Mana!ement Console. ,0& SMC also mana!es user, host permissions and access controls ,,& )lert Mana!ement ,2& 7rom a free product, SMC now becomes a licensed product, which the customers will ha"e to pay for ,=& t allows customers to perform functions related to confi!uration chan!es like creatin! and mappin! maskin! de"ices, chan!in! de"ice attributes, fla! settin!s, etc ,?& Perform replication functions usin! SMC like Clone, Snap, 8pen ;eplicator, etc ,C& SMC enables <irtual Pro"isionin! with the Symmetrix <>Max arrays ,B& Enables <irtual :09 technolo!y for automated policies and tierin!. ,D& )uto Pro"isionin! 4roup technolo!y is offered throu!h wiGards in SMC ,'& 3ynamic Cache Partitionin!E )llocates and deallocates cache based on policies and utiliGation. ,-& Symmetrix Priority Controls

(3

20& 7rom the SMC, customers can now launch SP) %Symmetrix Performance )nalyGer&, this is more on the lines of 1orkload )nalyGer which is a standard component of ECC Suite. .his allows customers to "iew their stora!e F application performance F monitorin!. SP) will can be obtained as a )dd>on product from EMC based on licensin!.

Virt=a L>3 2echno ogy in <orks =sing a <i+ard 2,& .he SMC !i"es the customer capabilities for 3isco"ery, Confi!uration, Monitorin!, )dministration and ;eplication Mana!ement. 22& SMC can be obtained from EMC Powerlink or throu!h your account mana!er from EMC if you ha"e an acti"e contract in place with EMC for hardwareLsoftware maintenance or if your systems are under warranty. High y recommended management too /or S43 4dmins and yea it?s not /ree anymore /or V,-ax Systems.

(*

Sym*li )asi* Commands

7ollowin! are the Symcli Commands $ou can use the man pa!es for further info. $ou can also use the option symxxx >h and will help you na"i!ate around. Most of the commands come in fla"ors of three as followsE ;eference 3escription Example pd Physical de"ice name Lde"LdskLc=t?dC de" Symmetrix de"ice name 077 ld Symmetrix lo!ical de"ice name 3E<00, Examples are as followsE ,. symde" list 2. sympd list =. symld >! [\!roup] list Command 9ote symde" Performs operations on a de"ice !i"en the Symmetrix de"ice name. sympd Performs operations on de"ices !i"en the de"ices physical name %c2t0d0& sym!ate Performs operations on !atekeeper de"ices. symd! Performs operations on Symmetrix de"ice !roups symld Performs operations on de"ices within a de"ice !roup symbc" Performs support operations on *C< pairs symmir Performs control operations on *C< pairs symrdf Performs control operations on ;37 pairs symcf! disco"er Creates a local database of the attached symmetricies. symin2 Shows internal F external de"ices that the host sees.

(%

EMC ime+inder Commands

.he followin! are the .imefinder Procedural Commands t outlines e"erythin! that needs to be done from start to finish. ;ealiGe that for routine operations, some of these steps won(t be neededX howe"er, for the sake of completeness. Prepare EMC structures ,. Create a Symmetrix disk !roup symdg ,t G Aeg= ar H A*F1 H A*F" I create JKgro=pL 2. )dd de"ices to the disk !roup sym d ,g JKgro=pL add pd DdevDdskDcMtMdM sym d ,g JKgro=pL add dev 01a =. )ssociate *C< de"ices to the disk !roup symbcv ,g JKgro=pL associate pd JKbcv8ctdL symbcv ,g JKgro=pL associate dev JKbcv8devL Establish *C< mirrors ,. 3 the lo!ical de"ice namesE .imefinder defaults to usin! the lo!ical de"ice names. $ou can id the lo!ical de"ice names byE symmir ,g JKgro=pL 6=ery 2. 7irst time establish, execute a full establishE symmir ,g JKgro=pL ,/= Kbcv8 og8devL estab ish JKstd8 og8devL bcv J

=. 0se symmir 2uery to monitor pro!ress. symmir ,g JKgro=pL 6=ery *reak *C< mirrors ,. .ypes of splitsE
((

,. nstant splitE Split is performed in the back!round after the completion of the split L8 re2uest. 2. 7orce splitE Splits the pair durin! establish or restore operationsX in"alid tracks may exist. =. ;e"erse splitE ;esyncs the *C< with the full data copy from its local or remote mirror. ?. ;e"erse differential splitE Enables a copy of only out>of>sync tracks to the *C< from its mirror. C. 3ifferential splitE Enables a copy of only the updated tracks to the *C<(s mirror. 2. CommandsE symmir symmir symmir symmir ,g ,g ,g ,g JKgro=pL JKgro=pL JKgro=pL JKgro=pL sp it sp it ,instant sp it ,di//erentia reverse sp it ,di//erentia

;eestablish or restore *C< mirrors ,. ;estore copies data from *C< back to standard pair. Y;eestablish, on the other hand, does a differential update of the *C< from the standard de"ice. 2. CommandsE symmir ,g JKgro=pL estab ish 3ifferential reestablish from standard de"ice to *C< symmir ,g JKgro=pL ,/= restore 7ull restore of all tracks on *C< to standard de"ice. symmir ,g JKgro=pL restore 3ifferential restore of *C< data to standard de"ice. .he .imefinder Strate!ies are as follows ,. Maintain *C< mirrors with the standard de"iceX break the mirrors when you want to backup, test, or de"elop on a copy of the ori!inal. .his is probably the most common way of runnin! .imefinder. .he ad"anta!e is that the split operation will happen almost instantly as the mirrors are fully synced all the time. .he disad"anta!e is that anythin! towards that happens to the standard de"ice will be reflected in the *C< mirror. 2. Maintain the *C< as a split de"ice to keep an online backup of the ori!inal data.

(,

EMC S/D0 )asi*s

Conceptually and operationally, S;37 is desi!ned to work in a 1)9L nternetLCloudLS)9 en"ironment with multiple Symms in"ol"ed, while .imefinder is local to a Symm, but performs the same functions. .he difference, S;37 can be performed without 4eo!raphic boundaries, while .imefinder is local. .he followin! are "arious different forms of S;37 that can be used by a customer to perform S;37 operations. Synchrono=s mode 1ith Synchronous mode, the remote symm must ha"e L8 in cache before the application recei"es the acknowled!ement. 3ependin! on distance where these Symmetrix machines are located, this may ha"e a si!nificant impact on performance. .his form of S;37 is su!!ested to be implemented in a campus en"ironment. f you want to ensure that the data is replicated real time without dirty tracks from one symmetrix to the other, you mi!ht want to enable 3omino effect. 1ith 3omino effect, your ;, de"ices will become not ready if the ;2 de"ices cant be reached. Semi,synchrono=s mode 1ith Semi>synchronous mode, the L8 between the ;, and ;2 de"ices are always out of sync. .he application recei"es the acknowled!ement from the first write L8 to the local cache. .he second L8 isn(t acknowled!ed until the first is in the remote cache. .his form of S;37 is faster than the pre"ious mentioned Synchronous mode. 4daptive 1opy,Nrite Pending 1ith )dapti"e Copy>1rite Pendin!, all the ;2 "olumes are copied o"er without the delay of acknowled!ement from the application. 1ith this mode, we can setup a skew parameter that will allow max number of dirty tracks. 8nce that number is reached, the system switches to a preconfi!ured mode like the

(3

semi>synchronous mode until the remote data is all synced. 8nce this is hit, S;37 is switched back to )dapti"e Copy>1rite Pendin! mode.

S/D0 Commands
.he followin! are S;37 Commands and what they are used for. Composite S;37 commands ,. ,. ,. 2. =. 2. 7ailo"erE )ctionsE 1rite disables %13& ;, Sets link to 9ot ;eady %9;& 1rite enables ;2 CommandE

symrd/ ,g JKgro=pL /ai over 2. 0pdateE +elps to speed up the failback operation by copyin! in"alid tracks before write disablin! any disks. ,. )ctionsE ,. :ea"es ser"ice state as is. 2. Mer!es the tracks =. Copies in"alid tracks 2. CommandE symrd/ ,g JKgro=pL =pdate =. ,. ,. 2. =. ?. C. 7ailbackE )ctionsE 1rite disables ;2 Suspends ;37 link Mer!es the disk tracks. ;esumes the link 1rite enables ;,

(.

B. Copies the chan!ed data 2. CommandE symrd/ ,g JKgro=pL /ai back ?. ,. ,. 2. 2. SplitE :ea"es both ;, F ;2 in write enabled state. )ctionsE Suspends the rdf link. 1rite enables ;2 CommandE

symrd/ ,g JKgro=pL sp it C. ,. ,. 2. =. ?. 2. EstablishE )ctionsE 1rite disables ;2 Suspends the rdf link Copies data from ;, to ;2 ;esumes the rdf link. CommandE I estab ish

symrd/ ,g JKgro=pL G ,/= B. ,. ,. 2. =. ?. C. 2.

;estoreE Copies data from ;2 to ;, )ctionsE 1rite disables both ;, F ;2 Suspends the rdf link. Mer!es the track tables ;esumes the rdf link. 1rite enables ;, CommandE I restore

symrd/ ,g JKgro=pL G ,/=

Sin!ular S;37 commands ,. SuspendE symrd/ ,g JKgro=pL s=spend 2. ;esumeE symrd/ ,g JKgro=pL res=me =. Set modeE symrd/ ,g JKgro=pL set mode sync symrd/ ,g JKgro=pL set domino on symrd/ ,g JKgro=pL set acp8disk ske< 1000

,0

EMC Symmetrix 9 DMX S/D0 Setu!

.his section talks about settin! up basic S;37 related functionality on the Symmetrix L 3M5 machines usin! EMC Solutions Enabler Symcli. 7or this setup, let(s ha"e two different host, our local host will be ;, %Source& "olumes and our remote host will be ;2 %.ar!et& "olumes. ) mix of ;, and ;2 "olumes can reside on the same symmetrix, in short you can confi!ure S;37 between two Symmetrix machines to act as if one was local and other was remote and "ice "ersa.

Step 1 Create S$MC: 3e"ice 4roups. Each !roup can ha"e one or more Symmetrix de"ices specified in it. S$MC: de"ice !roup information %name of the !roup, type, members, and any associations& are maintained in the S$M)P database. n the followin! we will create a de"ice !roup that includes two S;37 "olumes. S;37 operations can be performed from the local host that has access to the source "olumes or the remote host that has access to the tar!et "olumes. .herefore, both hosts should ha"e de"ice !roups defined. Complete the followin! steps on both the local and remote hosts. a& dentify the S;37 source and tar!et "olumes a"ailable to your assi!ned hosts. Execute the followin! commands on both the local and remote hosts. M symrd/ ist pd %execute on both local and remote hosts& or M symin6 b& .o "iew all the ;37 "olumes confi!ured in the Symmetrix use the followin!

,1

M symrd/ ist dev c& 3isplay a synopsis of the symd! command and reference it in the followin! steps. M symdg Fh d& :ist all de"ice !roups that are currently defined. M symdg ist e& 8n the local host, create a de"ice !roup of the type of ;37,. 8n the remote host, create a de"ice !roup of the type ;372. M symdg Ftype A*F1 create ne<srcdg %on local host& M symdg Ftype A*F" create ne<tgtdg %on remote host& f& <erify that your de"ice !roup was added to the S$M)P database on both the local and remote hosts. M symdg ist !& )dd your two de"ices to your de"ice !roup usin! the symld command. )!ain use %6h& for a synopsis of the command syntax. 8n local hostE M sym d Fh M sym d Fg ne<srcdg add dev MMM or M sym d Fg ne<srcdg add pd Physica driveM 8n remote hostE M sym d Fg ne<tgtdg add dev MMM or M sym d Fg ne<tgtdg add pd Physica driveM

,2

h& 0sin! the symin2 command, identify the !atekeeper de"ices. 3etermine if it is currently defined in the S$M)P database, if not, define it, and associate it with your de"ice !roup. 8n local hostE M symin6 M symgate ist %Check S$M)P & M symgate de/ine pd Physica driveM %to define& M symgate ,g ne<srcdg associate pd Physica driveM %to associate& 8n remote hostE M symin6 M symgate ist %Check S$M)P & M symgate de/ine pd Physica driveM %to define& M symgate ,g ne<tgtdg associate pd Physica driveM %to associate& i& 3isplay your de"ice !roups. .he output is "erbose so pipe it to more. 8n local hostE M symdg sho< ne<srcdg Hmore 8n remote hostE M symdg sho< ne<tgtdg H more #& 3isplay a synopsis of the symld command. M sym d ,h k& ;ename 3E<00, to 9E1<8:, 8n local hostE M sym d Fg ne<srcdg rename *EV001 3ENVCL1 8n remote hostE

,3

M sym d Fg ne<tgtdg rename *EV001 3ENVCL1 l& 3isplay the de"ice !roup on both the local and remote hosts. 8n local hostE M symdg sho< ne<srcdg Hmore 8n remote hostE M symdg sho< ne<tgtdg H more Step " 0se the S$MC: to display the status of the S;37 "olumes in your de"ice !roup. a& f on the local host, check the status of your S;37 "olumes usin! the followin! commandE M symrd/ ,g ne<srcdg 6=ery Step & Set the default de"ice !roup. $ou can use the WEn"ironmental <ariablesQ option. M set S@-1LB8*;One<srcdg %on the local host& M set S@-1LB8*;One<tgtdg %on the remote host& a& Check the S$MC: en"ironment. M symc i Fde/ %on both the local and remote hosts& b& .est to see if the S$MC: ^34 en"ironment "ariable is workin! properly by performin! a W2ueryQ without specifyin! the de"ice !roup. M symrd/ 6=ery %on both the local and remote hosts& Step ! Chan!in! 8perational mode. .he operational mode for a de"ice or !roup of de"ices can be set dynamically with the symrdf set mode command.

,*

a& 8n the local host, chan!e the mode of operation for one of your S;37 "olumes to enable semi>synchronous operations. <erify results and chan!e back to synchronous mode. M symrd/ set mode semi 3ENVCL1 M symrd/ 6=ery M symrd/ set mode sync 3ENVCL1 M symrd/ 6=ery b& Chan!e mode of operation to enable adapti"e copy>disk mode for all de"ices in the de"ice !roup. <erify that the mode chan!e occurred and then disable adapti"e copy. M symrd/ set mode acp disk M symrd/ 6=ery M symrd/ set mode acp o// M symrd/ 6=ery

Step # Check the communications link between the local and remote Symmetrix. a& 7rom the local host, "erify that the remote Symmetrix is Wali"eQ. f the host is attached to multiple Symmetrix, you may ha"e to specify the Symmetrix Serial 9umber %SS9& throu!h the 6sid option. M symrd/ ping G ,sid xx I %xxJlast two di!its of the remote SS9& b& 7rom the local host, display the status of the ;emote :ink 3irectors. M symc/g FA4 a ist

c& 7rom the local host, display the acti"ity on the ;emote :ink 3irectors. M symstat ,A4 a Step ( Fi 10 Fc "

,%

Create a partition on each disk, format the partition and assi!n a filesystem to the partition. )dd data on the ;, "olumes defined in the newsrcd! de"ice !roup. Step ' Suspend ;37 :ink and add data to filesystem. n this step we will suspend the S;37 link, add data to the filesystem and check for in"alid tracks. a& Check that the ;, and ;2 "olumes are fully synchroniGed. M symrd/ 6=ery b& Suspend the link between the source and tar!et "olumes. M symrd/ s=spend c& Check link status. M symrd/ 6=ery d& )dd data to the filesystems. e& Check for in"alid tracks usin! the followin! commandE M symrd/ 6=ery f& n"alid tracks can also be displayed usin! the symde" show command. Execute the followin! command on one of the de"ices in your de"ice !roup. :ook at the Mirror set information. 8n the local hostE M symdev sho< MMM !& 7rom the local host, resume the link and monitor in"alid tracks. M symrd/ res=me M symrd/ 6=ery

,(