While Creating the new TDEV device, Its giving me double the size

I used the same command for the other VMX box that is running the engunity 5875 and its giving me 16 GB device not the 32 GB devices .

create dev count=5
size=34960,
emulation=FBA,
config=tdev;

On Vmax -

GB = Cylinders * 15 * 128 * 512 / 1024 / 1024 / 1024

Hence

34960* 15 * 128 * 512 / 1024 / 1024 / 1024 = ~ 32.006

To create 16Gb size TDEV-

create dev count=5, size=17480, emulation=FBA, config=tdev;

Do you have the symapi logs .. If yes, please provide the extract by removing the symm sn information.

Also provide the symdev output of the device which was created to confirm if 16Gb was created.

Below is the example

I am was created 4 devices yday , 2*4 Gb device and 1*8 GB device and 1* 2Gb Devices , Below is the logs and my commands

***I removed the symm serial numbers everywhere***** .

A Configuration Change operation is in progress. Please wait...

    Establishing a configuration change session...............Established.

    {

      create dev count=2, size=9206 cyl, emulation=FBA, config=TDEV,

        mvs_ssid=0;

      create dev count=1, size=18414 cyl, emulation=FBA, config=TDEV,

        mvs_ssid=0;

      create dev count=1, size=4370 cyl, emulation=FBA, config=TDEV,

        mvs_ssid=0;

    }

    Performing Access checks..................................Allowed.

    Checking Device Reservations..............................Allowed.

    Initiating COMMIT of configuration changes................Queued.

    COMMIT requesting required resources......................Obtained.

    Step 004 of 054 steps.....................................Executing.

    Step 009 of 054 steps.....................................Executing.

    Step 009 of 054 steps.....................................Executing.

    Step 030 of 054 steps.....................................Executing.

    Step 030 of 054 steps.....................................Executing.

    Step 049 of 172 steps.....................................Executing.

    Step 049 of 172 steps.....................................Executing.

    Step 091 of 172 steps.....................................Executing.

    Step 093 of 172 steps.....................................Executing.

    Step 093 of 172 steps.....................................Executing.

    Step 093 of 172 steps.....................................Executing.

    Step 101 of 172 steps.....................................Executing.

    Step 107 of 172 steps.....................................Executing.

    Step 112 of 172 steps.....................................Executing.

    Step 116 of 172 steps.....................................Executing.

    Step 132 of 172 steps.....................................Executing.

    Step 132 of 172 steps.....................................Executing.

    Local:  COMMIT............................................Done.

      New symdevs: 7057:705A [TDEVs]

    Terminating the configuration change session..............Done.

The configuration change session has successfully completed.

================================================================================

        Device Name           Directors                  Device

--------------------------- ------------- -------------------------------------

                                                                           Cap

Sym  Physical               SA DA :IT  Config        Attribute    Sts   (MB)

--------------------------- ------------- -------------------------------------

7057 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      NR    4315

7058 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      NR    4315

7059 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      NR    8632

705A Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      NR    2048

Hi Avinash ,

I agree with you

but i tried creating  the same type of tdev from other VMax but its giving me 16 GB device not the 32 GB devices

Hi Avinash,

Here is another example for 16GB device . in the screenshot you can see the cylinder size is double the device size

I have seen this in Older Array(DMX-1 & 2) where default track size was 32 KB.

In DMX-3 and above track size is 64 KB

What is the Variable SYMAPI_TRACK_SIZE_32K_COMPATIBLE set to in options file (Located in /var/symapi/config)

What is the SE version ?

Hi,

What is the cylinder size in the Box?

I agree with Avinash, something is not right in your configuration. 34960 Cyl should be equal to 32 GB. In your api logs, I can see that you have created 2 *4 gb device by giving the device size of 9206 cyl? These two devices should have been bigger in the size.

Relook at the Avinash's suggestion for your answers.

regards,

saurabh

Sorry for delay in response

We are using the single management station thats having 6 to 7 VMAX boxes are connected . If below is the case then it has to be uniform across all the VMAX boxes right ? in my case its totally different

* /var/symapi/config/options **

#

# Parameter:            SYMAPI_TRACK_SIZE_32K_COMPATIBLE

#

# Allowed values:       ENABLE | DISABLE

#

# Default value:        DISABLE

#

# Description:          Specifies how to report device sizes. ENABLE reports

#                       device size in terms of 32 KB tracks. DISABLE reports

#                       device sizes in their native mode, depending on the

#                       Symmetrix array model.

#

#SYMAPI_TRACK_SIZE_32K_COMPATIBLE = DISABLE

Hi All,

Now I too agree with Avinash . Whatever avinash said in the earlier thread is correct.

In my environment , we have discovered the same box in 2 management stations. In one management station we have this option "  SYMAPI_TRACK_SIZE_32K_COMPATIBLE" enable and other one its disabled .

Wherever its enabled we have to give double the actual size and wherever its disabled there we have to give the exact device size .

Thanks Avinash for helping me on this and also thanks to rohilla too