Questions and Answers: 1) What is a hyper? Hyper is slice of a hard disk , we can have the size 8.

.16, or 32Gb upto 240 GB in V-max and ,64 GB DMX. 2)How do u check freespace? Symconfigure sid 5552 freespace unit mb list 3) How do u check locks? symcfg sid 5552 list lockn all symcfg sid 5552 release -lock XX force 4) What is the process to create metalun? Howmany types & can we expand the metalun, if so what is the process? Form meta from xx config=striped add dev yy:zz to meta xx We can expand a meta . bcv should be the same size of the meta. add dev 18:22 to meta 000, protect_data=TRUE, bcv_meta_head=030; 5)What is a gatekeeper?how do u check & assign them in dmx? Gatekeeper is communication device which will allow To send SCSI commands to the Symmetrix, Gatekeepers are typically 6 cylinders or 2888 KB in Size # symgate -sid 5552 define dev 588d

6) What is vaulting and where exactly the vault drives reside in clariion? When ever there is power failure or some reason array stops the data in the cache will destage to the first five disk in first DAE in the clarion. This process is called vaulting. 7) What is PSM Lun? Persitent storage manager is 2 GB lun which contain the information about the host other configuration iformation of the lun and array. 8) About powerpath How do you clear the dead paths and reconfigure the new path The command Powermt check will identify the dead paths end evently remove the dead path. 9)Polices of powerpath ,How are they different in symmetrix and clarion Symm_opt/CLAR_opt (default) I/O requests are balanced across multiple paths based on composition of reads, writes, and user-assigned device/application priorities Round_Robin I/O requests are distributed to each available path in turn Least_I/Os I/O requests are assigned to the path with the fewest number of requests in the queue Least_Blocks I/O requests are assigned to the path with the fewest total blocks in the queue Request Path failover only No Redirect Disable path failover and load balancing (same as Transparent=on) Default for Symmetrix when there is no license key; not supported on CLARiiON Basic Failover CDE-type functionality (SPASPB failover) Default for CLARiiON when there is no license key; not supported on Symmetrix

10) steps to be taken when the lun is not visible to host from storage? First of all we have to check port login to confirm that the server hba is loged in to symetrix FA or not, we can use the command symcfg sid list logins dir 7c p 0 If its not loged in we have to check the zoning in the switch. Or else we have to check the masking we can use the comman symmaskdbsid xx wwn list devs.

11)Command to be used to check all the devices using powerpath? Powermt display dev=all 12)Difference between hard zoning and soft zoning? In hard zoning we use domain ID and switch port. Advantage security is high HBA spoofing(Taking the identity) is not possible in hard zoning, disadvantage is when there is change in port we have reconfigure zoning. Soft zoning we use wwpn nos to do the zoning. When there is HBA change then we have to reconfigure zoning. 13)What is the significance of 17th rule?why cant it bee 15th and 16th? In DMX , backend directors connected redundant to each disk for this redundant pairing we use rule of 17 its emc recommended, not mandatory for FAs

14)When the PER bit is set on a device, that device is not automatically reserved or locked with a Persistent Reservation. It only means that device is now *able* to be reserved or locked with a Persistent Reservation. The device won't actually be reserved or locked until a host sends SCSI commands to establish a reservation on it. For a Persistent Reservation to be established on a device, the host (initiator) has to send the SCSI Persistent Reservation commands, and the Symm (target) has to support/accept the SCSI PR commands. When the PER bit is not set, the Symm device will not support/accept any SCSI PR commands. The general recommendation is to not set the PER bit on devices if the cluster host will not be using Persistent Reservations. This precaution ensures that a device will never be reserved or locked even if a mistake is made in configuration.

15)How to asssign a lun to the cluster.? When we allocate lun to a cluster we have to allocate a small lun of size gb for quarum drive. Which contain the all the disk information which is used by cluster software. We have to enable the scsi 3 persistence attribute. 16)How many device we can map to FA? We can map upto 4096 devices but it is shared between the ports in a director. A Symmetrix FA port is capable of supporting 4096 mapped devices. It assigns LUN numbers to mapped devices starting at 0 and counting up in 3 hexadecimal digits. For some host environments this is a problem, because some host HBAs are limited in the highest LUN that they can support. In other instances, applications might rely on a certain LUN such as LUN 0. Dynamic

Dynamic LUN addressing allows specific LUN values to be assigned, either manually or automatically, to each Symmetrix device that is being masked to an HBA, regardless of what LUN was assigned when the device was mapped to the FA. This eliminates the potential impact of the 256 LUNs per target limit of many HBAs by allowing LUN addresses between 0 and 255 to be specified on a per HBA World Wide Name basis. It also allows any device to be addressed as LUN 0 if a host requires that a device be assigned that LUN value. 17) DMX-3 Raid -5 Vaulting DMX-4 Raid - 6 flash drives SATA deives storage cap: 1PB Largest drive :1TB "symdisk -sid 432 list -by_diskgroup2 to see the pyhsicals in which disk groups, then use: "symdev -sid 432 list -disk_group <nn>" to see the devices in each disk group.

C- Bit settings in symmetrix. C = Common serial no, it changes the numbers after the volume id to zero's (when you do a inq), otherwise multipathed devices would appear with multiple numbers.

18) SYMAPI Database Symmetrix configuration and status info resides in SYMAPI database on the management host To reduce the number of inquiries from the host to the storage arrays, configuration and status information is maintained in a Symmetrix host database file called the Symmetrix configuration database (default file name: symapi_db.bin). 19) VCMDB The Volume Logix Database persistently maintains the device masking information. Originally the database was located directly on a Symmetrix Logical Volume. On DMX-3 it is maintained in the Symmetrix File System (SFS). Rather than create the actual VCMDB device, today we create a VCM Gatekeeper device which is used by the Solutions Enabler to access the database on the SFS, as the SFS volumes are not host addressable. The VCM Gatekeeper is a 6-cyl device.

Connection

Records

Maintained

in

VCMDBWWN

> Entries in the VCMDB define relationship between masked connections and devices

FA1

Various different types of VCMDB Type 0, Type 1, Type 2, Type 3, Type 4, Type 5, Type 6 Type 0: Symmetrix 4.0, 32 Director System, 16 cylinder device size, Volume Logix 2.x Type 1: Symmetrix 4.8, 64 Director System, 16 cylinder device size, ESN Manager 1.x Type 2: Symmetrix 5.0/5.5, 64 Director System, 16 cylinder device size, ESN Manager 2.x Type 3: Symmetrix DMX, supports 32 fibre/ 32 iSCSI initiator records per port, 24 cylinder device in size. Enginuity 5569, Solutions Enabler 5.2, Support 8000 devices Type 4: Symmetrix DMX/DMX-2, supports 64 fibre/ 128 iSCSI initiator records per port, 48 cylinder device in size. Enginuity 5670, Solutions Enabler 5.3, Supports 8000 devices Type 5: Symmetrix DMX/DMX-2, supports 64 fibre / 128 iSCSI initiator records per port, 96 cylinder device in size, Enginuity 5671, Solutions Enabler 6.0, Supports 16000 devices Type 6: Symmetrix DMX-3, DMX-4, supports 256 fibre / 512 iSCSI initiator records per port, 96 cylinder device in size, Enginuity 5771, 5772 Solutions Enabler 6.0, Supports 64000 devices

o o o o

Backup the device symmaskdb sid <symmid> backup file backup Check the VCMDB type using symmaskdb sid <symmid> list database

On director 2c port0 a) Create a command file Sun1# vi vcmport Set port 2c:0 VCM_STATE = enable; Wq b) Offline the port Sun1# symcfg sid 277 offline dir 2c p 0 c) Run the configuration Sun1# symconfigure sid 277 v f vcmport commit nop d) Online the port Sun1# symcfg sid 277 0nline dir 2c p 0

e) Refresh the database Sun1#symmask refresh f) Update symapi_db.bin Sun1#symcfg discover

20)SUN1#symcfg discover Solution enabler in host sends an API call through HBA to sym Gate keeper devices receives the API call Downloads the configuration of sym in IMPL.bin file to host This configuration is stored in /var/sym_api/db directory ofhost

21)Lists the HBAs assigned to the specified devices symmaskdb -sid SymmID [-v] list assignment [-v] -dev SymDevStart:SymDevEnd | SymDevName | SymDevName,SymDevName... 22) How to identify free mapped devices. symmaskdb -sid SymmID [-v] list no_assignment [-dir all [-p all] | -dir # [-p <# | all>]] list capacity -host Hostname Displays the capacity of the devices assigned to a particular host. 23)LUN OFFSET For sanboot host side it require lun 0 If suppose lun5 is there we have to change the lunoffset fron 5 to 0 from the storage end Upto 15 lunoffset is 0 for 16 1 and for 17 2 and so on symmask -sid SymmID -wwn wwn set lunoffset on -dir # -p # 24)preview prepare comitt Verify : to verify the current symmetrix configuration Preview: to validate the changes in the context of current symmetirx configuration The preview argument verifies the syntax and correctness of each individual change defined and then terminates the session without change execution Prepare:to validate if symmwin can execute the change script Commit: to actually execute the change script 25.How to revert the configuration changes on brocade switch Import the Config backup 26.Explain about the step by step process that you will do after replacing the failed HBA.

First u have to do zoning Next Replace hba symmask -sid xxx -wwn 10000000C937166D replace 10000000C959BA78

27)While allocating storage to a host if there are no free ports available in FA what you will do Casll to emc to install new fa ports

28.How to allocate storage to AIX host is there any difference between allocation to windows and AIX. same

29. Explain the storage allocation to cluster server. Same process Cluster For windows 2003 servers and Sun solaris u have to enable SCSI3 persistent binding parameter 30. for HP UX max deivices are 512 and for other os it is 256

. View the fibre connectivity statuses of the FAs symcfg sid xxxx FA/SA ALL port list if u run this cmd then u can identify VBUS info 31 Convert standard devices to dynamic devices (R1, R2). Local (R1) sid 277: Create a command file Sun1# vi dynamic Set dev 0001 attribute=dyn_rdf; wq! Run Configuration Sun1# symconfigure sid 277 v f dynamic commit -nop Update symapi_db.bin Sun1# symcfg discover To check the dynamic device Sun1# symdev list dynamic

32. command to find either any physical disks has failed or not ? Ans: 1.If the out put shows no devices were found means there is no physical disk failure.

tamadst:/root->symdisk -sid 2808 list -failed Symmetrix ID : 000290102808

No devices were found or else in case of any disk failure your going to get the folowwing output. tamadst:/root->symdisk -sid 2811 list -failed Symmetrix ID Disks Selected : 000290102811 :1

Capacity(MB) Ident Symb Int TID Vendor Type Hypers Total Free Actual ------ ---- --- --- ---------- ---------- ------ -------- -------- -------DF-15D 15D D 2 SEAGATE T146155 50 140014 1617 140014 33. How to see either hotspare has kicked in or not? Ans: in Row no.3 you can see hypers count means failed disk 15d:d2 has replaced with 15a:ca tamadst:/root->symdisk -sid 2811 list -hotspare Symmetrix ID Disks Selected : 000290102811 : 17

Capacity(MB) Ident Symb Int TID Vendor Type Hypers Total Free Actual ------ ---- --- --- ---------- ---------- ------ -------- -------- -------DF-1A 01A C 1C SEAGATE T146155 0 0 0 140014 DF-1A 01A D 11 SEAGATE T300155 0 0 0 286102 DF-15A 15A C A SEAGATE C146X15 19 0 0 140014 DF-16A 16A D 18 SEAGATE T146155 0 0 0 140014 DF-1B 01B D A SEAGATE C146X15 0 0 0 140014 DF-2B 02B C A SEAGATE T300155 0 0 0 286102 DF-2B 02B D 15 SEAGATE T300155 0 0 0 286102 34.how to see what are the devices or hypers effected on the faulty disk? Ans: use the following cmd to get full details of all hotspare here you can see rows like failed director,interface,target id is N/A means disk is spare only or else if you find some degits means the same disk has been replaced with the faulty disk tamadst:/root->symdisk -sid 2811 list -spare_info -V |more 16 Symmetrix ID Disks Selected : 000290102811 : 17

Director : DF-1A Interface :C Target ID : 1C Disk Group Number :5 Vendor ID Product ID : SEAGATE : SXT14685FC

Product Revision : T146155 Serial ID : 3LN5PEXH Disk Blocks :0 Block Size : 512 Actual Disk Blocks : 286749475 Total Disk Capacity (MB) : 0 Free Disk Capacity (MB) : 0 Actual Disk Capacity (MB) : 140014 Hypers :0 Hot Spare : True

Failed Director : N/A Failed Interface : N/A Failed Target ID : N/A SDR- symmetrix disk reallocation LUN and VBUS Mapping for HP-UX Here are the set of commands needed for mapping LUNS and VBUS on a HP-UX system. Your command file should look like. map dev XXX to dir FA:P, vbus=X, target=Y, lun=Z; Parameters: XXX is the Symmetrix device being mapped FA is the director the device is being mapped to P is the port on the FA X is the virtual bus value (valid values 0-F) Y is the target id (valid values 0-F) Z is the lun address (valid values 0-7) The symcfg sid xxx list available address will display LUNS above 7, but these are not valid and usable by HP-UX. You will have to find the next available LUN 0-7. If there are no more available addresses on any VBUS you can map a device and specify the next VBUS. This will create a new VBUS and adds the available LUNS to it. In the case where the HP-UX host is shared on the FA with another host type and heterogeneous port sharing is being used, it is only necessary to specify a LUN address. You will need to enable the Volume Set Address (V) flag on the FA or it will end up in error. The LUN address specified should be 3 digits, containing the required VBUS, target and LUN values. This LUN address will be interpreted as VBUS, target and LUN when the HP-UX host logs into the Symmetrix.

1) Allocation Steps. DMX 1) 2) 3) 4) First of all we have get the wwpn no: What kind of device STD,BCV What is the size If its new host do the zoning.

5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18)

To check the zoning is proper we can check the ports the hba is loged in to the FA >symmask -sid 5552 list logins -dir 7c -p 0 Check the devices which is not mapped. Symdev sid 5552 list noport or create the devices Create a txt file Create dev count=10 size=cyl,config=2way-mirror, emulation=FBA, Execute the file symconfigure sid 5552 f a.txt preview, prepare , commit Create meta volume Form meta from dev 0030, config=striped; add dev 0010:00200 to meta 0030. Find the available LUN id Symcfg sid 5552 address available list dir 7c p 0 map dev 0030 to dir 7c:0, lun=02f mask the device to wwpns symmask sid 5552 wwn 100010001010 dir 7c p 0 add devs 0030

19) refresh the symmask db 20) symaskdb sid 5552 refresh

Allocation V-Max 1) Create storage group #Symaccess create sid 5552 name xxx -type storage devs yy:zz 2)Create port group #symaccess create sid 5552 name xxx type port dirport 7E:0,10E:0 3)create initiator group #symaccess create sid 5552 name xxx type initiator wwn 10101001010 4) create view #symaccess create view sid 458 name MV_1 sg SG_1 pg PG_1-ig IG_1 5) display view symaccess show view MV_1 sid 458 Deallocation:

In the command file, you can delete one or more Symmetrix devices from the specified Symmetrix array. Deleting a device frees the space that it once occupied for future use Syntax: delete dev 0010:0020

Dissolving a Metavolume dissolve meta dev 107; Meta has to be unmapped before it can be dissolved Removes the meta head Frees up the meta members Data on the meta volume is lost

Unmapping Devices Devices must be write disabled (WD) or Not Ready before unmapping To make devices not ready use: symdev not_ready <SymDev> Unmapping causes hosts to lose access to the device unmap dev 13B:13F from dir 16A:0;

symmask -sid SymmID -wwn wwn add devs SymDevStart:SymDevEnd symmask -sid SymmID -wwn wwn remove devs SymDevStart:SymDevEnd symmask -sid SymmID -wwn wwn | -awwn awwn | -iscsi iscsi | -aiscsi aiscsi list logins [-dir all [-p all] | -dir # [-p <# | all>]] [-pdev PdevName] [-v] set heterogeneous <on host | off> -dir # -p # set hba_flags <on <flag,flag,flag...> <-enable | -disable> | off [flag,flag,flag...] > -dir # -p # set lunoffset <on <offset> <base> | off> -dir # -p # set visibility <on | off> -dir # -p # replace <wwn | iscsi> [-noprompt] delete [-dir # -p # | -dir all -p all] [-login] KEYWORDS authenticationIndicates iSCSI authentication data is being managed. Devs Indicates the devices to be added or removed. Hba Specifies the WWN or iSCSI name of the HBAs on the host. hba_flags Sets the record in the database to hold information on the HBA port setting that may differ than the current setting on the FA. Heterogeneous Sets the record in the database to hold connection protocol information on the host type that may differ from the current setting on the FA. Lockdown Sets the FCID value in the database to correlate that entry with a specific path. Logins Specifies to list the entries in the login history table. Lunoffset Sets the record in the database to hold base and offset information about a skip hole in the host-visible sequence of LUN addresses. Visibility Sets information in the database to note that the host should find all devices even if they are not contiguous.

Setting Front end port Flags:

Setting front end port flags allows the FA port to be compatible with different types of hosts and fibretopologies. The Common Serial Number, SCSI3 and SPC2 Protocol version are used across a variety of platforms. Volume set addressing is used by HP-UX hosts. Front end port flags can be overridden by the setting of HBA flags by using the symaccess command.To use auto provisioning groups on Symmetrix V-Max the ACLX flag must be enabled on the port

Setting the device attribute set dev SymDevName[:SymDevName] attribute=[NO]device_attr;

flag Setting ************ Originator Port wwn : 50060b00008617fe Type : Fibre User-generated Name : woodside/hba0 Visibility : No FCID Lockdown : No Lun Offset : No Heterogeneous Host : No Port Flag Overrides : Yes

: Common_Serial_Number(C) Volume_Set_Addressing(V) SCSI_3(SC3) SPC2_Protocol_Version(SPC2) Disabled : N/A Dynamic Addressing : N/A Authentication State : N/A Devices : 0459:045B 045F 0465 047A:047B 047E

Enabled

symmask -sid 780 set hba_flags on C,D,SC3,SPC2 -enable -wwn 50060b00008617fe -dir 10 -p 1 symmask -sid 780 -wwn 50060b00008617fe -dir 10a -p 1 set heterogeneous on symmask -sid <sym no.> -wwn <hba port wwn> -dir <FA> -p <port> set heterogeneous HPUX

Symmetrix arrays running Solutions Enabler V7.0 and Enginuity 5874, only allow you to set the HBA port flags on a per initiator basis. This feature allows specific host flags to be enabled and disabled on the director port. Setting HBA port flags replaces setting the heterogeneous host configuration flags. Volume Size Metrics A Symmetrix Logical Volume is an emulation of a Physical Disk and uses similar terminology Sector (16) 512 byte Block = 8 KB Track (R/W Head) (8) Sectors = 64 KB Cylinders (15) Tracks = 960 KB Volume sizes are typically specifiedin Cylinders 9000 Cyl Device = 8.8GB (9000 X 15 X 8 X 16 X 512 = 8,847,360,000) Largest Volume w. Enginuity 5874 = 262668 cylinders = 245760 MB = 240GB

Outputs:

These are some consolidated commands used for administration of EMC Symmetrix.

1. Display the properties and details of a particular volume symdev sid xxxx show [SymDevName]

2. List of available devices that are created but not assigned to the front end FAs symdev sid xxxx list noport nobcv

3. List of presented devices to a particular FA. symcfg sid xxxx list available address dir xx p x 4. View the fibre connectivity statuses of the FAs symcfg sid xxxx FA ALL port list 5. View the fibre connectivity statuses of the RAs and the RAGroups symcfg sid xxxx RA ALL port list 6. View the HBAs zoned into the FA symmask sid xxxx list logins dir xx p x 7. Adding LUN Masking (assigning LUNs to host HBAs) symmask -sid xxxx -wwn 10000000cxxxxxxx -dir xx -p x add devs xxx,xxx,xxx 8. Aliasing/Renaming the Host HBA wwns in the LUN Masking Database symmask sid xxxx wwn 10000000cxxxxxxx rename [NodeName]/[PortName] symmask sid 1200 wwn 10000000c9408060 rename kopeqdrac01/a1 9. Removing LUN Masking (unassigning LUNs from host HBAs) symmask -sid xxxx -wwn 10000000cxxxxxxx -dir xx -p x remove devs xxx,xxx

10. Refreshing the LUN Masking DB (This MUST be done every time a change is made) symmask -sid xxxx refresh -noprompt 11. List the LUN Masking DB by FA port symmaskdb sid xxxx list database dir xx p x 12 .List the LUN Masking DB by a Hosts wwn symmaskdb sid xxxx list database wwn 10000000cxxxxxxx/symmaskdb list devs -wwn XXXXXX 13. List the LUN Masking DB by an Alias symmaskdb sid xxxx list database awwn [NodeName]/[PortName] 14. List the wwns/alias for a particular LUN symmaskdb sid xxxx list assignment dev [SymDevName]

15. List a capacity report for an Alias (Host)

symmaskdb -sid xxxx list capacity -host [NodeName]

16. List all the Device Groups on that server

symdg list

17 .List details and properities of a particular device group symdg show [device group]

18 .Create a new device group for BCV ONLY relationships symdg -type REGULAR create [new dg name] symld g [device group] sid xxxx add dev [SymDevName] symbcv g [device group] sid xxxx add dev [SymDevName] symmir (BCV) commands symmir g [device group] query symmir g [device group] establish symmir g [device group] split 19. Create a new device group from the RDF1 (Source) location symdg -type RDF1 create [new dg name] symld g [device group] sid xxxx add dev [SymDevName] Commands for splitting the SRDF symrdf -g [device group] set mode sync symrdf -g [device group] query (keep checking until all synchronized) symrdf -g [device group] split symrdf -g [device group] query (make sure split) symrdf -g [device group] set mode acp_disk Putting SRDF back in place not saving any changes made in DR symrdf -g [device group] que (make sure mode is C.D) symrdf -g [device group] est symrdf -g [device group] query (query until less than 1GB left to synchronize) symrdf -g [device group] set mode acp_wp symrdf -g [device group] query (query until synchronized and make sure mode is C.W) 20. Create a new device group from the RDF2 (Target) location symdg -type RDF2 create [new dg name] symld g [device group] sid xxxx add dev [SymDevName] 21. View the statistics of the RA adapters symstat sid xxxx ra all i x c x

22. View the UNCONFIGURED space on the symm(DMX) symconfigure -sid xxxx list -freespace -units MB

23. This will check if you can run a symconfigure script symconfigure sid xxxx verify

24. This will check to see if there are any symconfigure scripts currently running symconfigure sid xxxx query

The 3 steps needed for running symconfigure scripts. symconfigure sid xxxx v f [command_file name and path] preview symconfigure sid xxxx v f [command_file name and path] prepare symconfigure sid xxxx v f [command_file name and path] commit 25. To view if there are any symconfigure locks symcfg -sid xxxx -lockn all list -sid 814 -lockn xx release) 26. To view if there are any devices that are locked symdev -sid xxxx -lock list xx release) (symdev -sid xxxx -lock (symcfg

27. This will write disable a particular Symm device (LUN) symdev sid xxxx write_disable [SymDevName] 28. This will read/write enable a particular Symm device (LUN) symdev sid xxxx rw_enable [SymDevName]

29. To view all the RDF groups symcfg -sid xxxx -rdfg all list

30. To view all the devices assigned to a particular RDF Group symrdf -sid 1200 -rdfg xx list

31. formmeta_[sid]_req[EMC request DB #].txt form meta from dev xxx config=striped, stripe_size=1920; add dev yyy:zzz to meta xxx;

32.dissolve_[sid]_req[EMC request DB #].txt dissolve meta dev xxx; 33. mapdev_[sid]_req[EMC request DB #].txt map dev xxx to dir xx:0 target=0, lun=xxx; map dev xxx to dir xx:0 target=0, lun=xxx; 34. unmapdev_[sid]_req[EMC request DB #].txt unmap dev xxx from dir all:all; 35.SRDF_EST_[sid]_req[EMC request DB #].txt convert dev xxx to RDF1+Mir, ra_group=x, remote_dev=xxx, invalidate=R2, start_copy=no; 36.convert-2-way_[sid]_req[EMC request DB #].txt convert dev xxx to 2-way-mir; 37. dyn_con2_[sid]_req[EMC request DB #].txt set dev xxx attribute=dyn_rdf; 38. set-dev-scsi3_[sid]_req[EMC request DB #].txt (Used for Oracle RAC) set dev xxx attribute=scsi3_persist_reserv; 39. Delete_dev_[sid]_req[EMC request DB #].txt delete dev xxx; 40. setportflag_[sid]_req[EMC request DB #].txt set port xxx:x unique_wwn=enable; 41. Create_2-way_[sid]_req[EMC request DB #].txt create dev count=xx, size=17480, emulation=FBA, config=2-way-mir, disk_group=x; 42. Create_BCV_[sid]_req[EMC request DB #].txt create dev count=xx, size=17480, emulation=FBA, config=BCV, disk_group=x; 43. Create_R5_[sid]_req[EMC request DB #].txt (Used in the DR site) create dev count=xx, size=17480, emulation=FBA, config=RAID-5, disk_group=x;

size=17480 = 8GB LUN size=8740 = 4GB LUN size=4369 = 2GB LUN size=2186 = 1GB LUN size=548 = 250MB LUN 44. List all RA groups Symcfg sid XXX list rdfg all 45. Set RDF qos to 5 symqos -g disk group set RDF pace 5 46. Check RDF qos symqos -g disk group que 47. Force split symrdf -g xxx split -symforce force 48. Suspend Single Device in Group symrdf -g xxx suspend DEVXXX 49. see various info including hetergenous port settings symmaskdb -sid xxx list database -v |more symmaskdb -sid xxx -host xxx list capacity 50. Replace hba symmask -sid xxx -wwn 10000000C937166D replace 10000000C959BA78

51. create pair symrdf createpair -sid 01346 -file 5040pairing.txt -type rdf1 -rdfg 1 -establish -noprompt SYMAPI logs /var/symapi/log 52. Symstat commands symstat -sid xxx -type PORT -dir xx -port x -i x -c x symstat -REQUESTS -g xxx -RepType rdf -i x c X

symstat -g xxx all -i 10 -c 3 53. See servers with EMC software talking to frame symcfg -sid xxx list connections 54. see locks on gatekeepers symcfg -semafores list 55. see locks on array devices symdev -sid xxx -lock list 56.remove locks on array devices symdev -sid xxx -lock 9 release -force -nop

57.see device reservations symdev -sid xxxxx -resv list

58. list logged events symevent -sid xxx list

59. list failed drives symdisk -sid xxx -failed list

UNIX: /usr/emc/API/symapi/config/symapi_licenses.dat Windows: C:\ Program Files\EMC\symapi\config (CHECK)