Rate this:

Virtually provisioned Thin device data can be migrated between high-performance drives and high-capacity drives. Data can be moved between storage pools configured on different drive technologies, and with different RAID protection types.

Virtual LUN VP migrations are session-based – each session may contain multiple devices to be migrated at the same time. There may also be multiple concurrent migration sessions. At the time of submission a migration session name is specified. This session name is subsequently used for the monitoring and management of the migration.

While an entire Thin device will be specified to be migrated, only Thin device extents that are allocated will be moved. Thin device extents that have been allocated, but not written to (for example, pre-allocated tracks), will be remapped to the target pool but will not cause any actual data to be copied.

New extent allocations that occur as a result of a host write to the thin device during the migration will come from the target pool.

During the migration, no changes occur to the front-end configuration of the thin device. The Symmetrix device number of the thin device remains the same, as does all mapping and masking information, and metadevice configuration. All local and remote replication relationships will also remain intact, and may actually be active during the migration.

For details and restrictions please refer to Feature document for “Symmetrix Virtual LUN VP Mobility”.

Example of how to do the migration:

In order to migrate a group of thin devices contained in the VP_ProdApp1 storage group, currently bound to a RAID 6 14+2 on SATA thin pool, to a RAID 1 on FC thin pool, the following steps would be performed:

1. Validate the migration:
symmigrate –sid 1849 –sg VP_ProdApp1 –tgt_pool –pool FC_R1_VP –name VP_migration validate

2. Establish the migration:
symmigrate –sid 1849 –sg VP_ProdApp1 –tgt_pool –pool FC_R1_VP –name VP_migration establish

3. Monitor the migration progress:
symmigrate –sid 1849 –name VP_migration query

4. Verify the migration has completed:
symmigrate –name VP_migration verify –migrated

5. Terminate the migration:
symmigrate –name VP_migration terminate

Rate this:

The following command can be used to view the device locks:

 

symdev -lock list  (Check for -L / P next to the lock)

 

L = Long lock, typically associated with SymReplicate and indicates that a long lock is normal. Before releasing lock the customer should check with replicate manager to see if they can stop the process holding the lock.

P = Persistent, cluster-type lock (ex: AIX)

 

To release the device external lock use:

 

symdev -lock # release

Rate this:

1.    symrdf -g dgname disable (Disables consistency protection for SRDF/A pairs in device group)

2.    symrdf -g dgname set mode acp_disk (This will turn on the adaptive copy write pending mode for the device group)

3.    symrdf -g dgname est (This initiates an establish for all the SRDF pairs in the device group)

4.    symrdf -g dgname query (To query a device Group)

 

Wait until the invalid track count is under 30,000 tracks

 

5.    symrdf -g dgname set mode async (Change the Copy mode to Asyncronous)

6.   symrdf -g dgname enable (Enables consistency protection for SRDF/A pairs in device group)

Rate this:

Rate this:

documentation…
san -> emc -> celerra – collect supoort data – – edit

description:
Run this for support and put in on the ftp server with nar files.
directions:
[nasadmin@seadcnsx1cs0 nar]$ /nas/tools/collect_support_materials
collect_support_materials[29843]: The collection script revision 2.8.4 has started.

Collecting /nas/log/*, /nas/log/webui/*, /nas/ConnectHome/*
and /nas/jserver/logs
Collecting output from server_log
Collecting output from internal commands
Collecting event log configuration files
Collecting files from .etc dir of each DM
Collecting Mirrorview DR logs
Collecting /var logs
Collecting upgrade logs
Collecting /etc files
Collecting /http/logs and /tomcat/logs
Collecting Celerra Manager tasks
Collecting cron files
Collecting Control Station process information and versions
Collecting /nas/jserver/debug_of_core* files
Now running material collection script for longer running commands.
Collecting complete nas dir listing
Collecting output from nas commands
Collecting RDF information
Collecting DHSM information
Collecting output from other CS commands
Collecting other files from /nas, /nas/site, /nas/sys,
/nas/rdf, and /nas/dos
Material Collection File:
/nas/var/log/support_materials_APM00070802955.091216_0908.zip has been generated.

**********************************************************************
Please include file /nas/var/log/support_materials_APM00070802955.091216_0908.zip
with materials submitted to EMC for problem investigation.
**********************************************************************

collect_support_materials[29843]: The collection script has finished successfully.
[nasadmin@seadcnsx1cs0 nar]$

Rate this:

VMAX doesn’t have VCMDB for masking. Insted, its using Autoprovisioning Groups.

Autoprovisioning Groups allow storage administrators to create
groups of host initiators, front-end ports, and logical devices. These groups are then
associated to form a masking view, from which all controls are managed.

A new command, symaccess, provides all the storage provisioning requirements for
Symmetrix V-Max arrays running Enginuity 5874.

The masking views, including storage groups, port groups, and initiator groups can
be backed up to a file, and restored from the backup file.

Use the following syntax to backup the masking views for a Symmetrix array to a file:

symaccess -sid SymmID -f BackupFilename [-noprompt] backup

Rate this:

Symmetrix V-Max Approach to Storage Reclamation

Follow the Below Steps for Storage Reclamation from the Vmax.

Step 1: Verify the Masking View Information. The Masking would give us the information about the
current Storage Group(SG), Initiator Group(IG) and Port Group(PG)
# Symaccess -sid 155 list view
The above syntax will list all the Masking View and identify the one you are working it on.
Step 2: View the Details of the Specific Masking
# Symaccess –sid 155 show view d1oraclust_MV
Step 3: Unmask and unmap the Devices. With Autoprovisioing Groups, this is simply matter of deleting the Masking View and the Devices will be unmapped and unmasked automatically. The following is an example if the command.
Caution
#symaccess –sid 155 delete view d1oraclust_MV
Step 3: Delete the Storage Group
#symaccess –sid 155 delete –name d1oraclust_SG -type storage -force
Step4: Delete the Initiator Group
#symaccess –sid 155 delete –name d1oraclust_IG -type initiator -force
Step5: Delete the Port Group
#symaccess –sid 155 delete –name d1oraclust_PG -type port -force

Step 6: Unbind the Devices from the thin Pool.
This step will make sure that we unbind the devices those are reclaimed from the host.

#symconfigure –f unbinddevice.cmd –preview
#symconfigure –f unbinddevice.cmd –prepare
#symconfigure –f unbinddevice.cmd –commit

Step6: Dissolve the Meta Devices
It is advised and to follow to delete the met devices once these freed up. The Intention behind is to have no discrepancy in the data of one server to be presented to other host by reusing the Devices in any form.
# symconfigure –f metadissolve.cmd preview
# symconfigure –f metadissolve.cmd prepare
# symconfigure –f metadissolve.cmd commit

Rate this:

To create from EMC ControlCenter:

1. Right-click on the Symmetrix in question. Select the Configure menu and then select Logical Device Creation.
2. Enter the amount of gatekeepers you want to create.
3. Fill out the form as follows:

Emulation: FBA
Type/Host: Open System
Size: 6
Unit: Cylinders
Configuration: Mirrored-2

4. Commit the changes and mask the devices to your servers.

From the command line:

1. Create a text file and input the following:

create dev count=x, config=2-way-mir, emulation=FBA, size=6;

2. Save the file and run the following:

symconfigure -sid xxx -f filename.txt -v preview
symconfigure -sid xxx -f filename.txt -v prepare
symconfigure -sid xxx -f filename.txt -v commit

3. Once the change is commited, mask the devices to your servers. Syminq commands will automatically pick up these devices as gatekeepers as shown in the output below:

/dev/rdsk/c1t1d87s2 GK EMC SYMMETRIX 5567 13195000

Rate this:

 

Info

uptime                             – Same as unix uptime
date                                 – Same as unix date
version                         – Gives versions of firmwares & OS

Hardware State

faultshow                     – Show switch faults
fanshow                         – Show switch FAN faults
psshow                          – Show switch POWER SUPPLY faults
tempshow                      – Show switch TEMPERATURE values
switchstatusshow        – Overall status of switch

Config

agtcfgshow                     – Show SNMP config
configshow                  – Show switch config
gbicshow                         – Show GBIC slots and serial numbers
licenseshow                 – Show license data
supportshow                 – Like Sun’s explorer – gets many configs at once
switchshow                     – Show switch ports and connections
zoneshow                         – Show zone and switch aliases

IP

bcastshow                     – Show broadcast routing
ifmodeshow                     – show interface mode (duplex)
ifshow                             – Like unix netstat -s
ipaddrshow                     – Like unix netstat -i
interfaceshow             – Like unix ndd

Performance

ifshow                             – Like unix netstat -s
portperfshow                 – Show interface mode (duplex)
portshow #                     – Show stats on a port
portrouteshow #         – Show routes on a port
portstatsshow #         – Show stats (netstat -s) on a port

Misc Show

diagshow                         – Show diagnostics – paged output
errdump                         – Show diagnostics – no paged output
fabricshow                     – Show fabric
fspfshow                         – Show FSPF protocol info
mqshow                             – Show queues
nbrstateshow                 – Show FSPF neighbor states
nsshow                             – Show name servers
nsallshow                     – Show all name servers
porterrshow                 – Like mpstat – shows port info
switchstatuspolicyshow – Show config at when errors are flagged

Rate this:

Problem:	Open Replicator session stuck in a CreateInProg state
Problem:	symrcopy -sid 3944 list -detailSymmetrix ID: 000290103944 Control Device            Remote Device                       Flags Status         Done Pace Name ————————- ———————————– —– ————– —- —- —————–       Protected Modified Sym   Tracks    Tracks    Identification                   RI CDSHU CTL <=> REM (%) —– ——— ——— ——————————– — —– ————– —- —- —————– 1A6D  0         0         CK200051700734:0037              CD X..XX CreateInProg   N/A  5    ldnpsm05868_3944 1F86  3276800   0         CK200055100555:0156              CD X..XX Created        N/A  5    ldnpsm055609_3944
Fix:	Terminate the session using the following command – Please be certain that you want to terminate the session before running this command: symrcopy terminate -file device_file -symforce Please be certain that you want to terminate the session before running this command. If this does not terminate the session, intervention from EMC technical support personnel is required.  Support personnel must access your storage system to terminate the session.  Contact the EMC Customer Support Center or your service representative for technical assistance and quote this solution ID.
Notes:	Example command operation and output: symrcopy terminate -file dev_file_1 -symforce Execute ‘Terminate’ operation for the 1 specified devices in device file  (y/[n]) ? y ‘Terminate’ operation execution is in progress for the device list in device file  Please wait… ‘Terminate’ operation successfully executed for the device list in device file