EMC Symmetrix: VCMDB and ACLX

VCMDB: Volume Control Manager Database

ACLX: Access Control Logix

VCM: Volume Control Manager device (where the database resides)

VCM Gatekeeper: Volume Control Manager Gatekeeper (database doesn’t reside on these devices)

SFS Volumes: Symmetrix File System Volumes

.
        If you work with EMC Symmetrix systems, you know the importance of VCMDB. Introduced with Symmetrix 4.0 and used in every generation after that, VCMDB stands for Volume Control Manager Database). Also in the latest generation of systems the VCM device is at times also referenced as VCM Gatekeeper.

      VCMDB is a relatively small device that is created on the Symmetrix system that allows for hosts access to various devices on the Symmetrix. VCMDB keeps an inventory of which devices have access to which host (HBA’s). Without a VCMDB in place, host systems will not be able to access the Symmetrix. The VCMDB should be backed up on regular intervals and would be helpful in a rainy day.

          The VCMDB device size grew along with new generations of Symmetrix systems that got introduced, primarily a means to keep a track of more supported devices (hypers / splits) on these platforms. With the introduction of Symmetrix V-Max, the VCMDB concept is now a bit changed to ACLX (Access Control Logix). Access Logix is being used on the Clariion systems for years now.

.

Here are a few things to consider with VCMDB

• On the older Symmetrix systems (4.0, 4.8, 5.0 and 5.5), the VCMDB (device) is mapped to all the channels, host
• In these systems the VCMDB access is typically restricted by Volume Logix or ACL (access control lists)
• With the Symmetrix DMX, DMX2 Systems – Enginuity Code 5670, 5671 the VCM device only requires to be mapped to the Management stations
• Management stations include SYMCLI Server / Ionix Control Center Server / Symmetrix Management Console
• At all given times on the DMX, DMX2 platforms, the VCMDB would need to be mapped to at least one station to perform online SDDR changes. Alternatively this problem of not having device mapped to at least one host can also be fixed by the PSE lab
• Mapping VCMDB to multiple hosts, channels may make the device venerable to crashes, potential tampering, device attributes and data change
• You can write disable VCMDB to avoid the potential of the above
• With these systems, the host can communicate to the VCMDB via Syscalls
• The VCM Edit Director Flag (fibrepath) needs to be enabled for management stations to see VCM device
• The database (device masking database) of the VCMDB resides on the SFS volumes. This feature was introduced with DMX-3 / DMX-4 (5772 version of microcode). A 6 cylinder VCM Gatekeeper device is okay to use with these versions of microcode.
• Starting Symmetrix V-Max systems, the concept of ACLX was introducted for Auto Provisioning etc.
• VCM volumes are required to be mirrored devices like SFS volumes

.

 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

.

Notes about various Types of VCMDB

• Type 3 of VCMDB can be converted to Type 4 VCMDB (code upgrade from 5669 to 5670 to 5671)
• Solutions enabler 5.2 and Solutions Enabler 5.3 can read/write Type 3 VCMDB
• Solutions enabler 5.3 can read/write Type 4 VCMDB
• VCMDB device is recommended to be a certain size, but it is okay to use a larger size device if no choices are available.

.

Converting various types of VCMDB using SymCLI

• If the device cylinder size is equal with a conversion you are attempting, the following will help you convert your VCMDB from type x to type y.
  • Backup the device
  • symmaskdb –sid <symmid> backup –file backup
  • Check the VCMDB type using
  • symmaskdb – sid <symmid> list database
  • Convert from type 4 to type 5
  • Symmaskdb – sid <symmid> convert –vcmdb_type 5 –file Covertfilename

.

To initialize VCMDB for the first time on a Symmetrix System

Within Ionix Control Center

• Click on the Symmetrix array you are trying to initialize the VCMDB
• Select Masking then VCMDB Management and then initialize
• Select a new backup and create a file name
• Create a file name with .sdm extenstion
• Click on Activate the VCMDB
• VCMDB backups are stored at \home\ecc_inf\data\hostname\data\backup\symmserial\
• Also it will be viewable within Ionix Control Center at Systems/Symmetrix/VCMDB Backups/

.

With SymCLI

• To query the VCMDB database
  • symmaskdb –sid <symmid> list database
  • To backup and init an existing VCMDB database
    • symmaskdb – sid <symmid> init –file backup

More technical deep dive coming soon on various other topics…including ACLX.
Cheers

SAN Switch Migration - How to plan and what need to consider?

       The Zoning Migration within SAN Fabric can import complete zone set information and aliases without any effect on existing SAN fabrics, simplifying SAN migration between different vendors. Such as Cisco, Brocade and McData.

         Import of zone set(h/w + s/w) actually save up a lot time for the migration work but there is some preparation need to be done before the migration. Prepare of the script of zone set, check the interopmode for future fabric expansion (In case other brand of switch will be add in the fabric is required)

     Before you begin, save the current Production Fabric from all SAN Switches.

           Example of Import Zone set. Export the zoning info from the Old switches and prepare the script and import to the new SAN. One important reminder, make sure you have configured the Interoperation mode “Interopmode” before you import the zone set. As the change of Interopmode setting will reset the zoning config.  Make sure all Switch that going to merge / ISL are in the same or Compatible Interop-Mode.

Before ISL / merge the switches,  you need to make sure all Switch in the fabric have a unique DID. You need to determine the principal switch in the fabric. This is to ensure that you have a proper fabric management  for future expansion.

Migration between Brocade Switches is very Simple and easy. Below is the script that I prepared before I import to the new Brocade switch.

Create Zone

switch>zonecreate "USUNIXSAN_HBA0_CX1234_SPA0","10:00:00:00:C9:2D:10:12;50:06:01:60:39:01:2D:xx"

switch>zonecreate "USUNIXSAN_HBA0_CX1234_SPB0","10:00:00:00:C9:23:11:13;50:06:01:68:39:01:2D:xx"

switch>zonecreate "SANDUEL_HBA0_CX1234_SPA0","10:00:00:00:C9:2A:10:17;50:06:01:60:39:01:2D:xx"

switch>zonecreate "SANDUEL_HBA0_CX1234_SPB0","10:00:00:00:C9:23:12:3D;50:06:01:68:39:01:2D:xx"

switch>zonecreate "WINAPPS2008_HBA0_CX1234_SPA0","10:00:00:00:C9:2D:10:12;50:06:01:60:39:01:2D:xx"

switch>zonecreate "WINAPPS2008_HBA0_CX1234_SPB0","10:00:00:00:C9:23:11:13;50:06:01:68:39:01:2D:xx"

---

Config Create

switch>cfgcreate "SANDUEL_FabricA", "USUNIXSAN_HBA0_CX1234_SPA0"

switch>cfgadd "SANDUEL_FabricA", "USUNIXSAN_HBA0_CX1234_SPB0"

switch>cfgadd "SANDUEL_FabricA", "SANDUEL_HBA0_CX1234_SPA0"

switch>cfgadd "SANDUEL_FabricA", "SANDUEL_HBA0_CX1234_SPB0"

switch>cfgadd "SANDUEL_FabricA", "WINAPPS2008_HBA0_CX1234_SPA0"

switch>cfgadd "SANDUEL_FabricA", "WINAPPS2008_HBA0_CX1234_SPB0"

---

switch>enable the configure.

switch>cfgenable “SANDUEL_FabricA”

EMC Symmetrix DMX-4: Supported Drive Types

In this blog post we will discuss the supported drive models for EMC Symmetrix DMX-4. Right before the release of Symmetrix V-Max systems, in early Feb 2009 we saw some added support for EFD’s (Enterprise Flash Disk) on the Symmetrix DMX-4 platform. The additions were denser 200GB and 400GB EFD’s.
The following size drives types are supported with Symmetrix DMX-4 Systems at the current microcode 5773: 73GB, 146GB, 200GB, 300GB, 400GB, 450GB, 500GB, 1000GB. Flavors of drives include 10K or 15K and interface varies 2GB or 4GB.
The drive has capabilities to auto negotiate to the backplane speed. If the drive LED is green the speed is 2GB, if its neon blue its 4GB interface.
To read a blog post on supported drive types on EMC Symmetrix V-Max System

The following are details on the drives for the Symmetrix DMX-4 Systems. You will find details around Drive Types, Rotational Speed, Interface, Device Cache, Access times, Raw Capacity, Open Systems Formatted Capacity and Mainframe Formatted Capacity.



73GB FC Drive
Drive Speed: 10K
Interface: 2GB / 4GB
Device Cache: 16MB
Access speed: 4.7 – 5.4 mS
Raw Capacity: 73.41 GB
Open Systems Formatted Cap: 68.30 GB
Mainframe Formatted Cap: 72.40 GB
73GB FC Drive
Drive Speed: 15K
Interface: 2GB / 4GB
Device Cache: 16MB
Access speed: 3.5 – 4.0 mS
Raw Capacity: 73.41 GB
Open Systems Formatted Cap: 68.30 GB
Mainframe Formatted Cap: 72.40 GB
146GB FC Drive
Drive Speed: 10K
Interface: 2GB / 4GB
Device Cache: 32MB
Access speed: 4.7 – 5.4 mS
Raw Capacity: 146.82 GB
Open Systems Formatted Cap: 136.62 GB
Mainframe Formatted Cap: 144.81 GB
146GB FC Drive
Drive Speed: 15K
Interface: 2GB / 4GB
Device Cache: 32MB
Access speed: 3.5 – 4.0 mS
Raw Capacity: 146.82 GB
Open Systems Formatted Cap: 136.62 GB
Mainframe Formatted Cap: 144.81 GB
300GB FC Drive
Drive Speed: 10K
Interface: 2GB / 4GB
Device Cache: 32MB
Access speed: 4.7 – 5.4 mS
Raw Capacity: 300.0 GB
Open Systems Formatted Cap: 279.17 GB
Mainframe Formatted Cap: 295.91 GB
300GB FC Drive
Drive Speed: 15K
Interface: 2GB / 4GB
Device Cache: 32MB
Access speed: 3.6 – 4.1 mS
Raw Capacity: 300.0 GB
Open Systems Formatted Cap: 279.17 GB
Mainframe Formatted Cap: 295.91 GB
400GB FC Drive
Drive Speed: 10K
Interface: 2GB / 4GB
Device Cache: 16MB
Access speed: 3.9 – 4.2 mS
Raw Capacity: 400.0 GB
Open Systems Formatted Cap: 372.23 GB
Mainframe Formatted Cap: 394.55 GB
450GB FC Drive
Drive Speed: 15K
Interface: 2GB / 4GB
Device Cache: 16MB
Access speed: 3.4 – 4.1 mS
Raw Capacity: 450.0 GB
Open Systems Formatted Cap: 418.76 GB
Mainframe Formatted Cap: 443.87 GB
500GB SATA II Drive
Drive Speed: 7.2K
Interface: 2GB / 4GB
Device Cache: 32MB
Access speed: 8.5 to 9.5 mS
Raw Capacity: 500.0 GB
Open Systems Formatted Cap: 465.29 GB
Mainframe Formatted Cap: 493.19 GB
1000GB SATA II Drive
Drive Speed: 7.2K
Interface: 2GB / 4GB
Device Cache: 32MB
Access speed: 8.2 – 9.2 mS
Raw Capacity: 1000.0 GB
Open Systems Formatted Cap: 930.78 GB
Mainframe Formatted Cap: 986.58 GB
73GB EFD
Drive Speed: Not Applicable
Interface: 2GB
Device Cache: Not Applicable
Access speed: 1mS
Raw Capacity: 73.0 GB
Open Systems Formatted Cap: 73.0 GB
Mainframe Formatted Cap: 73.0 GB
146GB EFD
Drive Speed: Not Applicable
Interface: 2GB
Device Cache: Not Applicable
Access speed: 1mS
Raw Capacity: 146.0 GB
Open Systems Formatted Cap: 146.0 GB
Mainframe Formatted Cap: 146.0 GB
200GB EFD
Drive Speed: Not Applicable
Interface: 2GB / 4GB
Device Cache: Not Applicable
Access speed: 1mS
Raw Capacity: 200 GB
Open Systems Formatted Cap: 196.97 GB
Mainframe Formatted Cap: 191.21 GB
400GB EFD
Drive Speed: Not Applicable
Interface: 2GB / 4GB
Device Cache: Not Applicable
Access speed: 1mS
Raw Capacity: 400.0 GB
Open Systems Formatted Cap: 393.84 GB
Mainframe Formatted Cap: 382.33 GB
Support for 73GB and 146GB EFD’s have been dropped with the Symmetrix V-Max Systems, they will still be supported with the Symmetrix DMX-4 Systems which in addition to 73 GB and 146GB also supports 200GB and 400GB EFD’s.

EMC Timefinder Commands

The following are the Timefinder Procedural Commands
It outlines everything that needs to be done from start to finish. Realize that for routine operations, some of these steps won’t be needed; however, for the sake of completeness.
Prepare EMC structures

1. Create a Symmetrix disk group

symdg -t [ Regular | RDF1 | RDF2 ] create ${group}

2. Add devices to the disk group

symld -g ${group} add pd /dev/dsk/c#t#d#

symld -g ${group} add dev 01a

3. Associate BCV devices to the disk group

symbcv -g ${group} associate pd ${bcv_ctd}

symbcv -g ${group} associate dev ${bcv_dev}


Establish BCV mirrors

1. ID the logical device names: Timefinder defaults to using the logical device names. You can id the logical device names by:

symmir -g ${group} query

2. First time establish, execute a full establish:

symmir -g ${group} -full establish ${std_log_dev} bcv ${bcv_log_dev}

3. Use symmir query to monitor progress.

symmir -g ${group} query


Break BCV mirrors

1. Types of splits:

1. Instant split: Split is performed in the background after the completion of the split I/O request.

2. Force split: Splits the pair during establish or restore operations; invalid tracks may exist.

3. Reverse split: Resyncs the BCV with the full data copy from its local or remote mirror.

4. Reverse differential split: Enables a copy of only out-of-sync tracks to the BCV from its mirror.

5. Differential split: Enables a copy of only the updated tracks to the BCV’s mirror.

2. Commands:

symmir -g ${group} split

symmir -g ${group} split -instant

symmir -g ${group} split -differential

symmir -g ${group} reverse split -differential


Reestablish or restore BCV mirrors

1. Restore copies data from BCV back to standard pair. >Reestablish, on the other hand, does a
differential update of the BCV from the standard device.

2. Commands:

symmir -g ${group} establish Differential reestablish from standard device to BCV

symmir -g ${group} -full restore Full restore of all tracks on BCV to standard device.

symmir -g ${group} restore Differential restore of BCV data to standard device.


The Timefinder Strategies are as follows

1. Maintain BCV mirrors with the standard device; break the mirrors when you want to backup, test,
or develop on a copy of the original.

This is probably the most common way of running Timefinder. The advantage is that the split operation will happen almost instantly as the mirrors are fully synced all the time. The disadvantage is that anything towards that happens to the standard device will be reflected in the BCV mirror.

2. Maintain the BCV as a split device to keep an online backup of the original data.

How to do Connection between standard to concorent BCVs

In order to use the control functions of Solutions Enabler, you must create device groups and add/associate Symmetrix devices with the group. The following example shows how to create a device group, add a standard device to it and associate two BCV devices to the group.
The following commands will create a device group using the default type (regular). Next we will add a device to the device group and assign it a logical name. Then we associate two BCV devices with the device group so we can switch back and forth with the BCV devices.

symdg create mygroupsymld -g mygroup add dev 000 STD000
symbcv -g mygroup associate dev 110 BCV000
symbcv -g mygroup associate dev 111 BCV001

NOTE: At this point you have only added/associated devices with a device group. These actions do not in any way describe which devices should actually be paired. This may be confusing as the documentation is not very explicit. The fact is that the symmetrix may already have BCV pair information about these devices depending on how they were used in the past.
Now issue the commands to define the STD/BCV pair and actually synchronize the pair with a full establish.

symmir -g mygroup -full establish STD000 BCV dev 110
or
symmir -g mygroup -full establish STD000 BCV ld BCV000

This explicit definition of the STD device and the particular BCV device will cause any existing pair information to be disregarded and will use this new information to create a pair. This is

comparable to the older TimeFinder Command Line Interface "bcv -f filename" where the file "filename" consisted on one line entries pairing STD devices with BCV devices. And finally, split this TimeFinder pair and synchronize the STD device with a different BCV device.

symmir -g mygroup split
symmir -g mygroup -full establish STD000 BCV dev 111

Another method to establish pairs, using the "-exact" option [Available in V3.2-73-06 and higher]The -full -exact options on the symmir command instructs SYMCLI to define the STD/BCV pairs in the same order they were entered into the device group.

symdg create mygroupsymld -g mygroup add dev 000 STD000
symld -g mygroup add dev 001 STD001
symbcv -g mygroup associate dev 110 BCV000
symbcv -g mygroup associate dev 111 BCV001
symmir -g mygroup -full -exact establish

This will pair the first STD device (STD000) with the first BCV (BCV000) entered into the device group, and pair the second STD device (STD001) with the second BCV (BCV001) entered into the device group.

EMC Symmetrix DMX Models by Cabinets Types :

The below is the true breakdown of the type of the EMC Symmetrix and EMC DMX machines to the type of cabinet properties it has. 

Starting with the Symm 3.0′s EMC introduced a 1/2 Hieght cabinets, Single Full Cabinet and a 3 Cabinet machine. The same ideas went into the Symm 4.0 and 4.8. 

Starting the Symm 5.0 and into Symm 5.5, EMC introduced the Badger cabinets, which where much slimmer and about 5 ft in height, it was a disaster with those cabinets. Really no one bought it. 

Starting the DMX800′s and DMX1000′s which are the single cabinet, EMC introduced the DMX2000′s in 2 cabinets and DMX3000 in 3 cabinet style. 

Also if you ever wondered where those Symm modell numbers came from

1st Digit: 3 = Open Systems. 5 = Mainframe. 8 = Mixed.

2nd Digit: Related to Cabinet size, dependant on Generation’

3rd Digit: 00 = 5¼” Drives. 30 = 3½” Drives              

The DMX uses 31/2″ Fiber Drives

EMC Symmetrix V-Max: Enginuity 5874

          
           EMC Symmetrix V-Max systems were introduced back in the month of April 2009. With this new generation of Symmetrix came a new name V-Max and a new Enginuity family of microcode 5874.

          With this family of microcode 5874: there are 7 major areas of enhancements as listed below.

Base enhancements

Management Interfaces enhancements

SRDF functionality changes

Timefinder Performance enhancements

Open Replicator Support and enhancements



Virtualization enhancements


    
         With Enginuity family 5874 you also need solutions enabler 7.0. The initial Enginuity was release 5874.121.102, a month into the release we saw a new emulation and SP release 5874.122.103 and the latest release as of 18^th of June 2009 is 5874.123.104. With these new emulation and SP releases, there aren’t any new features added to the microcode rather just some patches and fixes related to the maintenance, DU/DL and environmentals. Based on some initial list of enhancements by EMC and then a few we heard at EMC World 2009, to sum up, here are all of those.


   RVA: Raid Virtual Architecture:


        With Enginuity 5874 EMC introduced the concept of single mirror positions. Normally it has always been challenging to reduce the mirror positions since they cap out at 4. With enhancements to mirror positions related to SRDF environments and RAID 5 (3D + 1P, 7D +1P) / RAID 6  (6D+2P, 14D+2P) / RAID 1 devices, now it will open doors to some further migration and data movement opportunities related to SRDF and RAID devices.

Large Volume Support:

       With this version of Enginuity, we will see max volume size of 240GB for open systems and 223GB for mainframe systems with 512 hypers per drive. The maximum drive size supported on Symmetrix V-Max system is 1TB SATA II drives. The maximum drive size supported for EFD on a Symmetrix V-Max system is 400GB. 

Dynamic Provisioning:

        Enhancements related to SRDF and BCV device attributes will overall improve efficiency during configuration management. Will provide methods and means for faster provisioning.  

Concurrent Configuration Changes:

        Enhancements to concurrent configuration changes will allow the customer and customer engineer to perform through Service Processor and through Solutions enabler certain procedures and changes that can be all combined and executed through a single script rather than running them in a series of changes.

Service Processor IP Interface:

        All Service Processors attached to the Symmetrix V-Max systems will have Symmetrix Management Console 7.0 on it, that will allow customers to login and perform Symmetrix related management functions. Also the service processor will have capabilities to be managed through the customer’s current IP (network) environment. Symmetrix Management Console will have to be licensed and purchased from EMC for V-Max systems. The prior versions of SMC were free. SMC will now have capabilities to be opened through a web interface.

SRDF Enhancements:

       With introduction of RAID 5 and RAID 6 devices on the previous generation of Symmetrix (DMX-4), now the V-Max offers a 300% better performance with TImefinder and other SRDF layered apps to make the process very efficient and resilient.

Enhanced Virtual LUN Technology:

        Enhancements related to Virtual LUN Technology will allow customers to non-disruptively perform changes to the location of disk either physically or logically and further simplify the process of migration on various systems.

Virtual Provisioning:

        Virtual Provisioning can now be pushed to RAID 5 and RAID 6 devices that were restrictive in the previous versions of Symmetrix. 

Autoprovisioning Groups:

       Using Autoprovisiong groups, customers will now be able to perform device masking by creating host initiators, front-end ports and storage volumes. There was an EMC Challenge at EMC World 2009 Symmetrix corner for auto provisioning the symms with a minimum number of clicks. Autoprovisioning groups are supported through Symmetrix Management Console. So the above are the highlights of EMC Symmetrix V-Max Enginuity 5874. As new version of the microcode is released later in the year stay plugged in for more info.