VMAX Device Creation

1. Operational prerequisites:
Below are the requirements to complete the device creation through solution enabler:
• Verify configuration changes can be made safely:
symconfigure verify –sid <sym id>
• Check for free disk space for creating new volumes.
symconfigure list –freespace [-units CYLINDERS|MB] -sid <sym id>
• Compact on I/O. Make device not ready use:
symdev not_ready <symdev>

2. Basic steps for device creation:

Below are the basic steps to create the devices.
• Create the device.
• Device Nos# 2, Device size=1GB/1024MB, Protection: RAID-5 [3+1]

Case 1:
Creating Data Devices with protection RAID.
Create Thin Pool.
Put Data Devices in Thin Pool.
Create TDEV
Create Meta if manual.
Bind TDEV to Thin Pool.

Case 2:
Data Devices, Thin Pool is already available.
Create TDEVs.
Create Meta if manual.
Bind TDEV to Thin Pool.
Add to FAST.

3. Create Device – RAID 1/5/6

Create Device: RAID 5

symconfigure -sid <sym id> -cmd "create dev count=2, size=1024 MB, emulation=FBA,
config=RAID-5, data_member_count=3;” –preview –nop;

symconfigure -sid <sym id> -cmd "create dev count=2, size=1024 MB, emulation=FBA,
config=RAID-5, data_member_count=3;” –prepare –nop;

symconfigure -sid <sym id> -cmd "create dev count=2, size=1024 MB, emulation=FBA,
config=RAID-5, data_member_count=3;” –commit –nop;

Display created device

4. Create Data Device – RAID 1/5/6

Create 8 DT/RAID 5/50 GB = 400 GB

symconfigure -sid <sym id> -cmd "create dev count=8, size=50 GB, emulation=FBA,
config=RAID-5, data_member_count=3, attribute=datadev;” –preview –nop;

symconfigure -sid <sym id> -cmd "create dev count=8, size=50 GB, emulation=FBA,
config=RAID-5, data_member_count=3, attribute=datadev;” –prepare –nop;

symconfigure -sid <sym id> -cmd "create dev count=8, size=50 GB, emulation=FBA,
config=RAID-5, data_member_count=3, attribute=datadev;” –commit –nop;

Display DT:
symdev list -datadev

5. Create Device – TDEV

Below are the basic steps to create the devices.
• Create the device.
• Device Nos: 1, Tdev size=240 GB
• Device Nos: 4, Tdev size=400 GB

Create Device: 240 GB TDEV

symconfigure -sid <sym id> -cmd "create dev count=1, size=240 GB, emulation=FBA,
config=tdev;” –preview –nop;

symconfigure -sid <sym id> -cmd "create dev count=1, size=240 GB, emulation=FBA,
config=tdev;” –prepare –nop;

symconfigure -sid <sym id> -cmd "create dev count=1, size=240 GB, emulation=FBA,
config=tdev;” –commit –nop;

Display TDEV: Not bound

Symdev list –sid <symid> -tdev –unbound
symcfg list –sid <symid> -tdev

Create Device: 400 GB TDEV, we have to create meta

• Create the devices for meta.

symconfigure -sid <sym id> -cmd "create dev count=4, size=100 GB, emulation=FBA,
config=tdev;” –preview –nop;

symconfigure -sid <sym id> -cmd "create dev count=4, size=100 GB emulation=FBA,
config=tdev;” –prepare –nop;

symconfigure -sid <sym id> -cmd "create dev count=4, size=100 GB, emulation=FBA,
config=tdev;” –commit –nop;

SITA / Orange Business Services 1/11 Highly Confidential

6. Create Device – META DEVICES for 4. 400GB TDEV
Below are the basic steps to create the meta devices.
• We have already created 8 Data Devices.
• We are creating Meta dev# 107. So device 107 becomes the Meta Head
• Adding devices <> to Meta# 107, so all devices added to it becomes meta members.
• Config: Concatenation or Striped
• Data Members reasonable Sizes recommendation: 4, 8, 16, 32
• Max Data Members: 255
• Two Data members can’t be on same disk. In case of EFD, it can be at times but in
SATA/FC, they have to be on different disks.
• Ex: add dev <108> or add dev 108:115 [adding all desired devices in single command.]

Display TDEVs before bounding to the pool

symdev list –tdev -unbound

Create Meta
symconfigure -sid <sym id> -cmd "form meta from dev <107>, config=concatenated; add dev
<> to meta 107;” –preview –nop;

symconfigure -sid <sym id> -cmd "form meta from dev <107>, config=concatenated; add dev
<> to meta 107;” –prepare –nop;

symconfigure -sid <sym id> -cmd "form meta from dev <107>, config=concatenated; add dev
<> to meta 107;” –commit –nop;

Display created device

symcfg list –sid <symid>–v

Below are the basic steps to view the meta items:

• Auto Meta : Disabled
• Minimum Auto Meta Size : < size in MB >
• Auto Meta Member Size : <0 - default>
• Auto Meta Configuration : N/A

7. Create Thin Pool

symconfigure -sid <sym id> -cmd "create pool P1 type=thin;” –preview –nop;
symconfigure -sid <sym id> -cmd "create pool P1 type=thin;” –prepare –nop;
symconfigure -sid <sym id> -cmd "create pool P1 type=thin;” –commit –nop;

Display Thin Pool

symcfg list –sid <symid> -pool –thin
symcfg show –sid <symid> -pool P1 –thin –detail [-detail includes listing of Thin devices.]
symcfg show –sid <symid> -pool P1 –thin –all [-all shows information on En & Dsb. DTs.]

SITA / Orange Business Services 2/11 Highly Confidential

8. Adding Data Devices to Thin Pool

• Data Devices in Thin Pool when added (By Default) : Disabled

• Use member_state=Enabled, to enable the data devices.

symconfigure -sid <sym id> -cmd "add dev <>:<> to pool P1 type=thin,
member_state=Enable;” –preview –nop;

symconfigure -sid <sym id> -cmd "add dev <>:<> to pool P1 type=thin,
member_state=Enable;” –prepare –nop;

symconfigure -sid <sym id> -cmd "add dev <>:<> to pool P1 type=thin,
member_state=Enable;” –commit –nop;

Display created device

symcfg list –sid <symid> -pool –thin

9. Binding Thin Device to Thin Pool

• Binding allocates one extent (12 tracks) to each Tdev.

• After binding, status of thin device will change to Bound.

symconfigure -sid <sym id> -cmd "bind tdev 107 to pool P1;” –preview –nop;

Display Thin Pool after adding DT, Tdevs.

symcfg show –sid <symid> -pool P1 –thin –detail

SITA / Orange Business Services 3/11 Highly Confidential

10. Pre-allocation of space in Thin Device.

• We are pre allocating space of 50 GB to TDEV.

• Pre allocation can be done at the time of binding or creation of devices.

symconfigure -sid <sym id> -cmd "start allocate on tdev <>:<> start_cyl=0 size=50GB;” –
preview –nop;

Pre allocation at time of creation or binding of device.

symconfigure -sid <sym id> -cmd "create dev count=4, size=100 GB, emulation=FBA,
config=tdev, preallocate size=50GB;” –commit –nop;
or
symconfigure -sid <sym id> -cmd "add dev <>:<> to pool P1 type=thin,
member_state=Enable, preallocate size=50GB;” –commit –nop;
or
symconfigure -sid <sym id> -cmd "create dev count=4, size=100 GB, emulation=FBA,
config=tdev, binding to pool P1, preallocate size=50GB;” –commit –nop;

Display Thin Device after pre allocated space

• You will see the pre allocated space in Total Allocated Tracks.
symcfg list –sid <symid> -tdev

Display Thin Pool after pre allocated space

• You will see the pre allocated space in Allocated Tracks.
symcfg show –sid <symid> -pool P1 –thin –detail

SITA / Orange Business Services 4/11 Highly Confidential

Action on Thin Devices TDEV: Binding, Unbinding, Rebinding, Migrate, Relocate.
Action on Thin Pools: Disable, Drain, Rebalance, Reclaim, Pre-allocation, Rename, Expand

11. Add Data Devices that are not currently pooled.

• Non-pooled devices will come under Disabled Devices with 0 Tracks allocation.
• Device State = Disabled
• Once added to Thin Pool and enabled, DT is ready to use.
• Device State = Enabled
• Enabling makes DT ready to receive data.

Check list of nonpooled data devices

symdev list -sid <sym id> -datadev –nonpooled

Add Data Devices from the list of non-pooled & Enable them.
symconfigure -sid <sym id> -cmd "add dev <>:<> to pool P1 type=thin,
member_state=Enable;” –preview –nop;

12. Pool Rebalancing

• Rebalancing causes redistribution of data across all enabled Data Devices.

• Pool Status: Enabled to Balancing
• After rebalancing, in Enabled Devices>Free Tracks & Full(%), data is equally spread
over all the Data Devices.

Before starting Rebalance

symcfg show –sid <sym id> -pool P1 –thin –all

Pool Rebalancing
symconfigure -sid <sym id> -cmd "start balancing on pool P1 type=thin;” –commit –nop;

During starting Rebalance: Pool Status: Balancing

symcfg show –sid <sym id> -pool P1 –thin –all

After Rebalance: Pool Status: Enabled

symcfg show –sid <sym id> -pool P1 –thin –all

SITA / Orange Business Services 5/11 Highly Confidential

13. Space Reclamation

• Reclamation recovers zero filled spaces from TDEVs and returns it to pool.
• Runs as a Background process.
• Pool Bound Thin Devices==> Status: Bound.
• During rebalancing, in Pool Bound Thin Devices==> Status: Reclaiming.
• Reclamation can run on SG, DG, and ranges of devices.

Before starting Reclamation

symcfg show –sid <sym id> -pool P1 –thin –detail

TDEV Reclamation
symconfigure -sid <sym id> -cmd "start free on tdev <> start_cyl=0 end_cyl=last_cyl
type=reclaim;” –commit –nop;

During Reclamation: Pool Status: Reclaiming

symcfg show –sid <sym id> -pool P1 –thin –detail

After Rebalance: Pool Status: Bound

symcfg show –sid <sym id> -pool P1 –thin –detail

14. Draining

• Draining allows non-disruptive removal of Data Devices.

• Before removing Data Device from a pool, Device must be Disabled.
• Device State = Enabled
• Disabling a Data Device.
• Device State = Draining.
• When Device enters Draining state: -
a. used tracks are being copied on remaining enabled devices in the pool.
b. Device moves from Enabled Devices to Disabled Devices.

Before starting Draining

symcfg show –sid <sym id> -pool P1 –thin –all

DT Draining
symconfigure -sid <sym id> -cmd "disable dev 107 in pool P1, type=thin;” –commit –nop;

During Draining: Device Status: Draining

symcfg show –sid <sym id> -pool P1 –thin –all

After Draining: Device Status: Disabled

symcfg show –sid <sym id> -pool P1 –thin –all

SITA / Orange Business Services 6/11 Highly Confidential

15. Unbinding TDEV

• For unbinding, TDEV must be unmapped or Not Ready(NR) state.

• Before removing Data Device from a pool, Device must be Disabled.

Before starting Unbinding

symdev list –sid <sym id> -tdev -bound

Tdev Not Ready

symdev –sid <sym id> not_ready –range <>:<> -nop

Tdev Unbinding:
symconfigure –sid <sym id> -cmd “unbind tdev <>:<> from pool P1;” –commit –nop;

After Unbinding:
symcfg show –sid <sym id> -pool P1 –thin –detail

16. Set Subscription Limit

• It is set to prevent over-subscription from going beyond a specified level.

• It can be set during Thin Pool creation. Specify max_subs_percent and after the thin
pool creation.

Set Subscription Limit: 120%

symconfigure –sid <sym id> -cmd “set pool P1, type=thin, max_subs_percent=120;” –
commit –nop;

After Setting Subscription Limit:

symcfg show –sid <sym id> -pool P1 –thin –detail

SITA / Orange Business Services 7/11 Highly Confidential

 VMAX Device Deletion

1. Operational prerequisites:
Below are the requirements to complete the device reclaiming through solution enabler:
• Name of the device.
• Size of the device.
• Storage group of the device.
• Admin rights on SE.
• Device wwn number and device LUN ID

To get all the device detail, open the change ticket and have a look at the attached excel file
to confirm the correct device name, and their size.

2. Basic steps for device creation:

Below are the basic steps to create the devices.
• Remove the device from the cluster storage group using –unmap command
• Unbind the device from thin pool.
• If device is a meta then dissolve the meta device.
• Delete all the meta members.

3. Unbind the device from thin pool:

When we unbind the devices from pool, below points should be considered.
• All the thin devices must be NR or unmapped before unbinding.
• All data on the devices will be lost.
• Allocated extents on the data devices will be free.

4. Dissolve meta device:

All data on the meta device will be lost when the meta is dissolved.

5. Delete the device:

• A device must be free of BCV or Snap sessions.
• If the device is data device, it must be disabled and have no used tracks.

SITA / Orange Business Services 8/11 Highly Confidential

Check which Thin pool our device is bound: Let’s say Dev name: 0385
symcfg list –tdev –bound | find “0385”

Check and ensure no device is in unbound pool right now

symdev list –tdev –unbound

Remove from SG and unmap the device

symaccess –sid <sym id> -name SG_1 –type storage dev 0385 remove –unmap

Remove Device Identifier

symconfigure –sid <sym id> -cmd “set dev 0385 No device_name;” –nop commit

Tdev Not Ready

symdev –sid <sym id> not_ready dev 0385 -nop

Tdev Unbinding:
symconfigure –sid <sym id> -cmd “unbind tdev 0385 from pool P1;” –commit –nop;

After Unbinding:
symcfg show –sid <sym id> -pool P1 –thin –detail

Check the unbound device: You will see TDEV 0385

symdev list –tdev –unbound

<Dissolve META now if dev is META>

Delete the device

symconfigure –sid <sym id> -cmd “delete dev 0385;” preview –nop;
symconfigure –sid <sym id> -cmd “delete dev 0385;” commit –nop;

Check the delete device: You will not see TDEV 0385 anymore
symdev list –tdev –unbound

SITA / Orange Business Services 9/11 Highly Confidential

6. If TDEV is META:
Below are the requirements to complete the device reclaiming through solution enabler:
• META should be unmapped before dissolving.
• Dissolve the meta. Range: dev <>:<> or Device: dev <>.
• Dissolving:

removes the meta head,

frees up the meta members,

meta members appear as individual device.

data on meta volume is lost.

Remove from SG and unmap the device

symconfigure –sid <sym id> -cmd “dissolve meta dev 0385;” –nop preview;
symconfigure –sid <sym id> -cmd “dissolve meta dev 0385;” –nop commit;

-----END----

SITA / Orange Business Services 10/11 Highly Confidential