We have discussed about Virtual Provisioning of Symmetrix in previous post. Now, we will discuss about Virtual Provisioning Configuration. You have to understand your storage environment before you run the below mentioned command.

Configuring and viewing data devices and pools:

Data Devices are devices with datadev attribute. Only Data Devices can be part of Thin Pool. Devices with different protection scheme can be supported for use in Thin Pools. It is depending on specific Enginuity level. All devices with the datadev attribute are used for exclusively for populating Thin Pools.

Create command file (Thin.txt) with following syntax:

create dev count=10, config=2-Way-Mir, attribute=datadev, emulation=FBA, size=4602;

# symconfigure -sid 44 -file thin.txt commit –v –nop

A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000190101244
{
create dev count=10, size=4602, emulation=FBA,
config=2-Way Mir, mvs_ssid=0000, attribute=datadev;
}
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Submitting configuration changes..........................Submitted
…..
…..
…..
Step 125 of 173 steps.....................................Executing.
Step 130 of 173 steps.....................................Executing.
Local: COMMIT............................................Done.
Terminating the configuration change session..............Done.

The configuration change session has successfully completed.

# symdev list -sid 44 -datadev

Symmetrix ID: 000190101244
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Sym Physical SA :P DA :IT Config Attribute Sts Cap(MB)
--------------------------- ------------- -------------------------------------
10C4 Not Visible ???:? 01A:C4 2-Way Mir N/A (DT) RW 4314
10C5 Not Visible ???:? 16C:D4 2-Way Mir N/A (DT) RW 4314
10C6 Not Visible ???:? 15B:D4 2-Way Mir N/A (DT) RW 4314
10C7 Not Visible ???:? 02D:C4 2-Way Mir N/A (DT) RW 4314
10C8 Not Visible ???:? 16A:D4 2-Way Mir N/A (DT) RW 4314
10C9 Not Visible ???:? 01C:C4 2-Way Mir N/A (DT) RW 4314
10CA Not Visible ???:? 16B:C4 2-Way Mir N/A (DT) RW 4314


Thin Pool can be created using symconfigure command and without adding data devices:

# symconfigure -sid 44 -cmd "create pool Storage type=thin;" commit –nop

Once pool is created, data devices can be added to the pool and enabled:

3 Comments:

  1. Anonymous Says:
  2. Great post with crisp and clear explanation! I have a question and was wodnering if you have any insight on this. I have a thin pool, added TDATs, bound the thin devs. Mapped the thin DEVS to the FAs as well. The Solaris 10 x86 hosts with leadville drivers don't see it though ("Not Visible").

    symdev show

    Symm ID: XXXXXXXX

    Device Physical Name: Not Visible
    ...

    ...

    ...
    Front Director Paths (1):
    {
    ----------------------------------------------------------------------
    POWERPATH DIRECTOR PORT LUN
    --------- ---------- ---- -------- ---------
    PdevName Type Type Num Sts VBUS TID SYMM Host
    ----------------------------------------------------------------------
    Not Visible N/A FA 07E:0 RW 000 00 060 N/A
    }
    ...

    ...

    ...

    Any thoughts on why this could happen? Your thoughts on this will be greatly appreciated. Thanks a bunch :)

  3. Sirajudeen Says:
  4. Reinitializing the link makes the host aware of this new device.

    Confirm the correct device node for the HBA. Run the following:

    luxadm -e dump_map /dev/fc/fp0 - HBA WWPN will be displayed in line with Type labeled as "Unknown Type, Host Bus Adapter" (as shown in emcgrab)

    Force the HBA to log out of the switch and log back in: ( Caution! This command will reset all ports on the loop. )

    luxadm -e forcelip /dev/fc/fp0

    Confirm that the device is seen now:

    luxadm probe
    At this point, format, inq and PowerPath will be able to see the device as well.

  5. Sirajudeen Says:
  6. Reinitializing the link makes the host aware of this new device.

    Confirm the correct device node for the HBA. Run the following:

    luxadm -e dump_map /dev/fc/fp0 - HBA WWPN will be displayed in line with Type labeled as "Unknown Type, Host Bus Adapter" (as shown in emcgrab)

    Force the HBA to log out of the switch and log back in: ( Caution! This command will reset all ports on the loop. )

    luxadm -e forcelip /dev/fc/fp0

    Confirm that the device is seen now:

    luxadm probe
    At this point, format, inq and PowerPath will be able to see the device as well.

Post a Comment