There can be a multitude of reasons for the configuration change failure.  The API log will only provide part of the answer, please open a Service Request with the Symmetrix Support Center for further investigation.

Regards,

Chris

I guess its a script which is stuck. PSE will need to recover it by dialing in to the box.

I know that command is ok, I run it few weeks ago, when I created some vdevs.

Is there some commands to see "system readynes" or something?

There is nothing wrong in the command, please review the symapi logs, and open a case with EMC.

I have tested your commands, and i got 5 new vdev's. There may be some scripts malfunctioning or something else... its better to check with PSE.

The prepare does't for you, it does verifies the array readiness. The commit does include the prepare and fails, if the array is not ready. Most of the time the preview will pass, but it will fail at commit.

symconfigure -sid xxxx -cmd "create dev count=5, size=29491 cyl,  emulation=fba, config=vdev;" -v prepare

no locks at all.

$ symcfg list -lock

               S Y M M E T R I X      L O C K S

                              Lock       Lock    Lock                Time

    SymmID       Attachment   Status     Number  Usage               Held (Sec)

    0002xxxxxxxxx Local        N/A        N/A     N/A                 N/A

$ symcfg list -lockn all

               S Y M M E T R I X      L O C K S

                              Lock       Lock    Lock                Time

    SymmID       Attachment   Status     Number  Usage               Held (Sec)

    000xxxxxxxx Local        N/A        N/A     N/A                 N/A

Is it possible that there is to less cache on sym box:

$ symcfg list

                                S Y M M E T R I X

                                       Mcode    Cache      Num Phys  Num Symm

    SymmID       Attachment  Model     Version  Size (MB)  Devices   Devices

    000xxxxxxxx Local       DMX4-24   5773       49152       224      2551

preview and prepare end successfully, but commit don't

You've tried a symcfg discover first, also you can see if you have any lock in symmetrix:

symcfg list -lock

symcfg list -lockn all

local emc partner was aweare of this, but this isn't our production storage any more and this is low priority.

could be a hot spare process running, until it finishes can't do any changes. I get that often on our DMX4.

$ symdev list -lock

Symmetrix ID: 000xxxxxxxxxx

No devices are locked

but ecc basicaly use solution enabler to "talk" with symm.

Maybe to remove /var/symapi/db/symapi_db.bin and do the symcfg disc again?

For the answer of dynamox, you can check:

symdisk -sid xxx list -failed -v

symdisk does not always show failed drives. I have seen many instances where ECC will report drive failure and hot spare kicking in, yet symdisk says everything is ok.