This post is more than 5 years old
45 Posts
0
1876
Unable to provision storage with Hitachi AMS2100
Hello All,
can anyone assist with this issue we are facing. We have checked & double checked the zoning and all looks good form the fabric side.
the array is added as a virtual asset and a ports / pool are also added as expected.
when we try and provision storage from the Black Virtual Pool [Using the Hitachi] we get a failure.
firmware on the AMS2100 is supported.
please note: there is only16GB free space on the HDS
here is the errors we experience: [fails at Execution Step 1]
any suggestion would be appreciated.
Error 1021 (http: 400): Unable to find a suitable placement to handle the request. No matching storage pool found using virtual pool urn:storageos:VirtualPool:0663be1d-a543-4344-ae6a-0b6f106f4019:vdc1 and virtual array urn:storageos:VirtualArray:5a3f83f5-5626-47d8-a7d5-f1cad967661d:vdc1 as virtual pool contains 1) Pools are over subscribed. 2) Pools are over utilized. 3) No free space. 4) Reached Pool/System maximum resources limit. 5) Connectivity issue with the storage system which is not reachable.
| Date | Level | Message |
|---|---|---|
| Nov 26th 2014, 12:48:33 pm | INFO | Logged into vCenter 'POD A Virtual Center' VMware vCenter Server 5.5.0 build-1378903 |
| Nov 26th 2014, 12:48:33 pm | INFO | Targeting Host 'spoc-intel07.vplex.spoc' |
| Nov 26th 2014, 12:48:34 pm | INFO | Host 'spoc-intel07.vplex.spoc' connection state: connected |
| Nov 26th 2014, 12:48:34 pm | ERROR | Error 1021 (http: 400): Unable to find a suitable placement to handle the request. No matching storage pool found using virtual pool urn:storageos:VirtualPool:0663be1d-a543-4344-ae6a-0b6f106f4019:vdc1 and virtual array urn:storageos:VirtualArray:5a3f83f5-5626-47d8-a7d5-f1cad967661d:vdc1 as virtual pool contains 1) Pools are over subscribed. 2) Pools are over utilized. 3) No free space. 4) Reached Pool/System maximum resources limit. 5) Connectivity issue with the storage system which is not reachable. |
| com.emc.vipr.client.exceptions.ServiceErrorException: Error 1021 (http: 400): Unable to find a suitable placement to handle the request. No matching storage pool found using virtual pool urn:storageos:VirtualPool:0663be1d-a543-4344-ae6a-0b6f106f4019:vdc1 and virtual array urn:storageos:VirtualArray:5a3f83f5-5626-47d8-a7d5-f1cad967661d:vdc1 as virtual pool contains 1) Pools are over subscribed. 2) Pools are over utilized. 3) No free space. 4) Reached Pool/System maximum resources limit. 5) Connectivity issue with the storage system which is not reachable. at com.emc.vipr.client.impl.jersey.ExceptionOnErrorFilter.handle(ExceptionOnErrorFilter.java:38) at com.emc.vipr.client.impl.jersey.ProxyTokenFilter.handle(ProxyTokenFilter.java:23) at com.emc.vipr.client.impl.jersey.AuthTokenFilter.handle(AuthTokenFilter.java:30) at com.sun.jersey.api.client.Client.handle(Client.java:648) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:680) at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) at com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:568) at com.emc.vipr.client.impl.RestClient.post(RestClient.java:138) at com.emc.vipr.client.core.AbstractResources.postTasks(AbstractResources.java:459) at com.emc.vipr.client.core.BlockVolumes.create(BlockVolumes.java:92) at com.emc.sa.service.vipr.block.tasks.CreateBlockVolume.doExecute(CreateBlockVolume.java:52) at com.emc.sa.service.vipr.tasks.WaitForTasks.executeTask(WaitForTasks.java:19) at com.emc.sa.service.vipr.tasks.WaitForTasks.executeTask(WaitForTasks.java:6) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:64) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:55) at com.emc.sa.service.vipr.ViPRExecutionUtils.execute(ViPRExecutionUtils.java:28) at com.emc.sa.service.vipr.block.BlockStorageUtils.createVolumes(BlockStorageUtils.java:171) at com.emc.sa.service.vipr.block.CreateBlockVolumeHelper.createAndExportVolumes(CreateBlockVolumeHelper.java:66) at com.emc.sa.service.vmware.block.CreateVolumeAndVmfsDatastoreService.execute(CreateVolumeAndVmfsDatastoreService.java:31) at com.emc.sa.engine.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:197) at com.emc.sa.engine.ExecutionEngineImpl.runService(ExecutionEngineImpl.java:127) at com.emc.sa.engine.ExecutionEngineImpl.executeOrder(ExecutionEngineImpl.java:68) at com.emc.sa.engine.ExecutionEngineDispatcher.processOrder(ExecutionEngineDispatcher.java:46) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:90) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:84) at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:83) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) | ||
| Nov 26th 2014, 12:48:34 pm | INFO | Releasing Lock urn:storageos:Host:4daf2c56-8a73-41f5-971a-6fc5446d167c:vdc1 |
Precheck Steps
| Summary | Detail | Elapsed |
|---|---|---|
| Get vCenter | vCenter: urn:storageos:Vcenter:f3ef5901-3017-4c92-8182-458c6845e30f:vdc1 | a second |
| Connect to vCenter | Login to vCenter 'POD A Virtual Center | a second |
| Get Datacenter | Datacenter: urn:storageos:VcenterDataCenter:b56c550b-5c4b-4190-ae2b-e4440538d18b:vdc1 | a second |
| Find ESX Host | Find ESX host 'spoc-intel07.vplex.spoc' in datacenter 'POC-DC01' | a second |
| Get Host | id: urn:storageos:Host:4daf2c56-8a73-41f5-971a-6fc5446d167c:vdc1 | a second |
| Acquire Host Lock | Acquiring exclusive lock for host spoc-intel07.vplex.spoc (ID: urn:storageos:Host:4daf2c56-8a73-41f5-971a-6fc5446d167c:vdc1) | a second |
| Verify Datastore Does Not Exist | Verify that a datastore named 'test' does not already exist on datacenter 'POC-DC01' | a second |
Execution Steps
| Summary | Detail | Elapsed |
|---|---|---|
| Create Block Volume | Name: test, Size: 2147483648, Virtual Pool: urn:storageos:VirtualPool:0663be1d-a543-4344-ae6a-0b6f106f4019:vdc1, Virtual Array: urn:storageos:VirtualArray:5a3f83f5-5626-47d8-a7d5-f1cad967661d:vdc1, Project: urn:storageos:Project:733ee615-2513-4dc0-b3be-540faa9e4cec:global | a second |
| com.emc.vipr.client.exceptions.ServiceErrorException: Error 1021 (http: 400): Unable to find a suitable placement to handle the request. No matching storage pool found using virtual pool urn:storageos:VirtualPool:0663be1d-a543-4344-ae6a-0b6f106f4019:vdc1 and virtual array urn:storageos:VirtualArray:5a3f83f5-5626-47d8-a7d5-f1cad967661d:vdc1 as virtual pool contains 1) Pools are over subscribed. 2) Pools are over utilized. 3) No free space. 4) Reached Pool/System maximum resources limit. 5) Connectivity issue with the storage system which is not reachable. at com.emc.vipr.client.impl.jersey.ExceptionOnErrorFilter.handle(ExceptionOnErrorFilter.java:38) at com.emc.vipr.client.impl.jersey.ProxyTokenFilter.handle(ProxyTokenFilter.java:23) at com.emc.vipr.client.impl.jersey.AuthTokenFilter.handle(AuthTokenFilter.java:30) at com.sun.jersey.api.client.Client.handle(Client.java:648) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:680) at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) at com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:568) at com.emc.vipr.client.impl.RestClient.post(RestClient.java:138) at com.emc.vipr.client.core.AbstractResources.postTasks(AbstractResources.java:459) at com.emc.vipr.client.core.BlockVolumes.create(BlockVolumes.java:92) at com.emc.sa.service.vipr.block.tasks.CreateBlockVolume.doExecute(CreateBlockVolume.java:52) at com.emc.sa.service.vipr.tasks.WaitForTasks.executeTask(WaitForTasks.java:19) at com.emc.sa.service.vipr.tasks.WaitForTasks.executeTask(WaitForTasks.java:6) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:64) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:55) at com.emc.sa.service.vipr.ViPRExecutionUtils.execute(ViPRExecutionUtils.java:28) at com.emc.sa.service.vipr.block.BlockStorageUtils.createVolumes(BlockStorageUtils.java:171) at com.emc.sa.service.vipr.block.CreateBlockVolumeHelper.createAndExportVolumes(CreateBlockVolumeHelper.java:66) at com.emc.sa.service.vmware.block.CreateVolumeAndVmfsDatastoreService.execute(CreateVolumeAndVmfsDatastoreService.java:31) at com.emc.sa.engine.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:197) at com.emc.sa.engine.ExecutionEngineImpl.runService(ExecutionEngineImpl.java:127) at com.emc.sa.engine.ExecutionEngineImpl.executeOrder(ExecutionEngineImpl.java:68) at com.emc.sa.engine.ExecutionEngineDispatcher.processOrder(ExecutionEngineDispatcher.java:46) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:90) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:84) at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:83) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) | ||
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
November 26th, 2014 07:00
Hi Dave,
Please follow the below instructions:
1. First check the status of storagesystem.
2. If storageSystem status is showing Green, then please look at the pool freeCapacity, oversubscription & over utilized capacity information.
oversubscription & overutilized capacity computation includes current (requested) volume size.
ViPR default utilization limits:
1. If a Thin pool is oversubscribed by 300% or overutilized by 75%, then such pools will not be considered to create volumes.
2. If a Thick pool is overutilized by 75%, then such pools will not be considered to create volumes.
3. Finally check whether any maximum resource size limit is set on the pools.
To change these limits, you should edit the page and save it.
4. If you are not seeing any of the above issues, kindly share us the apisvc.log file which is located in /opt/storageos/logs folder.
We will take a look at it and provide a solution.
Regards,
Ganga
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
November 26th, 2014 07:00
you are welcome. Let us know if you face any issues.
sullybags
45 Posts
0
November 26th, 2014 07:00
Thanks Ganga
as suspected looks like a free space issue.
Free = 16GB
Subscribed = 3648GB
Total = 3664GB
we will clear out some space and try again
thanks.