Visitors

EMC UIM Service Adoption Utility (SAU): Unable to adopt a Shared Storage Service

I tried to adopt a Shared Storage Service but it failed with the following error message:

EMC UIM-P Service Adoption Utility - Discovery Validation Failed
Discovery Validation failed.
Reason: Storage Pools – %Pool_Name% need to be graded in UIM

I checked Storage Pool configuration and confirmed it has been graded correctly. In my environment there are two Vblocks that are managed by one UIM virtual appliance. As both Vblocks configured in almost identical way, the storage pool names and grades are the same. UIM engineering team looked at this problem and confirmed that in this configuration UIM SAU may not be able to adopt a SSS correctly and provided the following workaround:

  1. Re-discover Vblock to refresh storage configuration;
  2. Backup UIM database;
  3. Open Database utility:
    uim001:/opt/ionix-uim/tools # su - pgdba
    pgdba@uim001:~> psql voyencedb uim
    SET
    psql (8.4.14)
    Type "help" for help.
  4. List the storage pools, I only included Storage pools where the Shared Storage LUNs are provisioned from:
    voyencedb=# select name, rdn from storage_pool;
    name                        |         rdn
    ----------------------------+---------------------
    PROD-VMFS-FAST-R5           | /EMC_UIMThinPool/3 # DC1 Vblock
    PROD-VMFS-FAST-R5           | /EMC_UIMThinPool/0 # DC2 Vblock

    I added Vblock names i.e. ‘# DC1 Vblock’ to help to identify Vblocks in different datacentres

  5. Run the following command to change the ‘rdn’ value to something UIM will not recognise. As you can see, it will only change ‘rdn’ / Storage Pool names for a Vblock called DC1, therefore SAU will only be able to see Storage Pools for other Vblock, called DC2, where we need to adopt the Shared Storage Service.
    voyencedb=# update storage_pool SET rdn = REPLACE(rdn, '/' , '@') where storage_array_id = (select storage_array_id from vblock where name ='DC1');
    UPDATE 13

    Where ‘UPDATE 13’ – Number of Storage Pools configured in Vblock DC1, all of them have been changed. As I stated before, I am only showing the Storage Pools where Shared Storage LUNs are carved from.

    voyencedb=# select name, rdn from storage_pool;
    name                        |         rdn
    ----------------------------+---------------------
    PROD-VMFS-FAST-R5           | @EMC_UIMThinPool@3 # DC1 Vblock
    PROD-VMFS-FAST-R5           | /EMC_UIMThinPool/0 # DC2 Vblock
  6. Now, when SAU can only ‘see’ storage pools on Vblock DC2, we can follow these instructions and adopt Shared Storage Service
  7. During SSS adoption, the LUNs/datastores may get adopted in RAW format: EMC UIM-P Service Adoption Utility - Shared Storage Service Format type RAW
    Change them to VMFS in SAU: Edit Services / Edit Storage Format…
    EMC UIM-P Service Adoption Utility - Shared Storage Service Format type VMFS
  8. When it is done, let’s revert ‘rdn’ to the original names (changing ‘@‘ back to ‘/‘):
    voyencedb=# update storage_pool SET rdn = REPLACE(rdn, '@' , '/') where storage_array_id = (select storage_array_id from vblock where name ='DC1');
    UPDATE 13
    voyencedb=# select name, rdn from storage_pool;
    name                        |         rdn
    ----------------------------+---------------------
    PROD-VMFS-FAST-R5           | /EMC_UIMThinPool/3 # DC1 Vblock
    PROD-VMFS-FAST-R5           | /EMC_UIMThinPool/0 # DC2 Vblock
  9. Don’t forget to Synchronize all Standard Services attached to Shared Storage Services you have just adopted.

This issue will be fixed permanently in the new release.

I would like to thank Zbigniew ‘Ziggy’ Misiak for his help in resolving this issue! Excellent service, as always!

Disclaimer: Make sure you take UIM database backup prior to implementing this workaround and follow this procedure at your own risk.
This procedure must be performed by a qualified VCE or EMC engineer. Please contact support.vce.com

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>