VPLEX: GUI and CLI not showing new free space in expanded Storage Pool.
Summary: VPlex 5.4 using VIAS to integrate VNX storage is show incorrect storage pool size after a pool expansion was done on the connected VNX array. New free space added to the storage pool on the array is not reflected in the VPlex CLI or GUI storage-pools context. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Customer creating new VPlex virtual volumes from storage-pools but operation is failing due to not having not enough space in the selected storage-pool.
Sometime proceeding this virtual volume create VNX arrays connected to the same Array Service Provider server sustained major instability causing the array to disconnect from the VPlex . The time frame of these issues should correlate with the exception as seen in the bole.log.
Unable to create new VPlex virtual volumes from storage-pools.
When creating virtual-volumes using the provisioning storage from pools method it was seen that the VPlex cluster > pool was showing an incorrect value when compared to the VNX GUI (Unisphere for VNX) output seen under Storage > Pools looking at the problem Pool name. Compared to the VPlex CLI output:
VPlexcli: ll /clusters/cluster-x/storage-elements/array-providers/AMPServerName/managed-arrays/EMC-CLARiiON-Array/storage-pools
Example:
Name Total Free Space Total Used Space Total Space Pool Types
------ ---------------- ---------------- ----------- -----------
Pool 1 7T 81.1T 138T Thick, Thin
From the VPlex Cli Pool has 7TB free space but from the VNX GUI Pool1 actually had 54TB free space this mismatch is the issue causing VPlex to believe there is not enough free space to create new virtual volumes.
Sometime proceeding this virtual volume create VNX arrays connected to the same Array Service Provider server sustained major instability causing the array to disconnect from the VPlex . The time frame of these issues should correlate with the exception as seen in the bole.log.
Unable to create new VPlex virtual volumes from storage-pools.
When creating virtual-volumes using the provisioning storage from pools method it was seen that the VPlex cluster > pool was showing an incorrect value when compared to the VNX GUI (Unisphere for VNX) output seen under Storage > Pools looking at the problem Pool name. Compared to the VPlex CLI output:
VPlexcli: ll /clusters/cluster-x/storage-elements/array-providers/AMPServerName/managed-arrays/EMC-CLARiiON-Array/storage-pools
Example:
Name Total Free Space Total Used Space Total Space Pool Types
------ ---------------- ---------------- ----------- -----------
Pool 1 7T 81.1T 138T Thick, Thin
From the VPlex Cli Pool has 7TB free space but from the VNX GUI Pool1 actually had 54TB free space this mismatch is the issue causing VPlex to believe there is not enough free space to create new virtual volumes.
Cause
On the management server of the VPlex cluster where the problem array is connected refer to the following management server log file in the directory /var/log/VPlex/cli/ bole.log looking at the most recent log. Using the less cmd:
Example: service@cluster-1:/var/log/VPlex/cli> less bole.log_20161025105350
In the Collect-diagnostic logs file this is located in the directory mgmt_server/cluster-X/vias look into the bole.log files looking at the most recent.
Look for the following exception:
2016-10-14 23:32:46,507 ERROR [Timer-6] Bole: Failed to get storage-pools for managed-array 'EMC-CLARiiON-CKM0015xxxxx15'.
com.emc.vplex.via.orca.amp.AMPException: Failed to list storage pools for array 'EMC-CLARiiON-CKM0015xxxxx15' with provider 'nw-ut-01-031'. Cause: Unable to connect
at com.emc.vplex.via.orca.amp.types.smis.SMISManagementProvider.listAllStorageResourcePools(SMISManagementProvider.java:96)
truncated
[Tip] grep for ERROR as follows:
[vplexuser@RP_VPLEX_logserver vias]$ grep ERROR bole.log_20160909095747
2016-10-14 23:32:46,507 ERROR [Timer-6] Bole: Failed to get storage-pools for managed-array 'EMC-CLARiiON-CKM0015xxxxx15'.
2016-10-14 23:32:46,519 ERROR [Timer-6] PoolCache: GetPoolsForArray: Failed on array EMC-CLARiiON-CKM0015xxxxx15
[vplexuser@RP_VPLEX_logserver vias]$ grep 2016-10-14 via.log_20160909095747
2016-10-14 23:32:46,490 ERROR [Timer-6] ArrayManagementProvider: com.emc.vplex.via.orca.amp.AMPException: Failed to list storage pools for array 'EMC-CLARiiON-CKM0015xxxxx15' with provider 'nw-ut-01-031'. Cause: Unable to connect
Above exception shows that the SMI GetPoolsForArray command failed with cause unable to connect after this exception was meet there were no more successful GetPoolsForArray commands run to the problem array.
Looking to the VPlex firmware logs located in /var/log/VPlex/cli/ firmware.log at looking to the time stamp of the above exception in this case showed many events indicating the array sustained major instability disconnecting from VPlex and soon reconnecting causing a log rebuild of all DD with leg on this array at which time the exception logged and no later successful get pool commands were run.
Note: In this case the customer had a VNX array connected to VPlex cluster-1 and another VNX array collected VPlex cluster-2 with both VPlex clusters registering the same Array Service Provider server.
Example: service@cluster-1:/var/log/VPlex/cli> less bole.log_20161025105350
In the Collect-diagnostic logs file this is located in the directory mgmt_server/cluster-X/vias look into the bole.log files looking at the most recent.
Look for the following exception:
2016-10-14 23:32:46,507 ERROR [Timer-6] Bole: Failed to get storage-pools for managed-array 'EMC-CLARiiON-CKM0015xxxxx15'.
com.emc.vplex.via.orca.amp.AMPException: Failed to list storage pools for array 'EMC-CLARiiON-CKM0015xxxxx15' with provider 'nw-ut-01-031'. Cause: Unable to connect
at com.emc.vplex.via.orca.amp.types.smis.SMISManagementProvider.listAllStorageResourcePools(SMISManagementProvider.java:96)
truncated
[Tip] grep for ERROR as follows:
[vplexuser@RP_VPLEX_logserver vias]$ grep ERROR bole.log_20160909095747
2016-10-14 23:32:46,507 ERROR [Timer-6] Bole: Failed to get storage-pools for managed-array 'EMC-CLARiiON-CKM0015xxxxx15'.
2016-10-14 23:32:46,519 ERROR [Timer-6] PoolCache: GetPoolsForArray: Failed on array EMC-CLARiiON-CKM0015xxxxx15
[vplexuser@RP_VPLEX_logserver vias]$ grep 2016-10-14 via.log_20160909095747
2016-10-14 23:32:46,490 ERROR [Timer-6] ArrayManagementProvider: com.emc.vplex.via.orca.amp.AMPException: Failed to list storage pools for array 'EMC-CLARiiON-CKM0015xxxxx15' with provider 'nw-ut-01-031'. Cause: Unable to connect
Above exception shows that the SMI GetPoolsForArray command failed with cause unable to connect after this exception was meet there were no more successful GetPoolsForArray commands run to the problem array.
Looking to the VPlex firmware logs located in /var/log/VPlex/cli/ firmware.log at looking to the time stamp of the above exception in this case showed many events indicating the array sustained major instability disconnecting from VPlex and soon reconnecting causing a log rebuild of all DD with leg on this array at which time the exception logged and no later successful get pool commands were run.
Note: In this case the customer had a VNX array connected to VPlex cluster-1 and another VNX array collected VPlex cluster-2 with both VPlex clusters registering the same Array Service Provider server.
Resolution
- Have the customer identify the pool name and array where this pool lives
- Confirm the array is registered with VPlex under array server providers for the specific VPlex cluster.
To see array management provider server:
VPlexcli:/> cd clusters/PRA-VPLEXCL-2/storage-elements/array-providers/
VPlexcli:/clusters/cluster-2/storage-elements/array-providers> ll
Name Provider Type Connectivity Status
------------ ------------- -------------------
Server_name SMI-S connected
Checking AMP server status as seen from the VPlex:
VPlexcli:/clusters/cluster-2/storage-elements/array-providers/server_name> ll
Attributes:
Name Value
------------------- --------------
connectivity-status connected
ip-address 111.222.333.444
port 5988
provider-type SMI-S
use-ssl false
username admin
Checking the managed arrays at that VPlex cluster:
VPlexcli:/clusters/cluster-2/storage-elements/array-providers/server_name/managed-arrays> ll
Name
---------------------------
EMC-CLARiiON-ArraySerialNumber
This confirms the AMP server is in contact with VPlex and the array with the AMP server.
- Confirm array connectivity is ok for any array connected to this AMP server checking cluster-1 and 2.
- General health-check
- Check firmware logs for streaming scsi/133, stdf/17, disk/1004, apf/13
- If arrays and AMP server connection are ok, proceed to restart the management console of the management server with the management server command
service@cluster-2:~> sudo /etc/init.d/VPlexManagementConsole restart
From the VPlexcli; Recheck the pool free space:
VPlexcli: ll /clusters/cluster-x/storage-elements/array-providers/AMPServerName/managed-arrays/EMC-CLARiiON-Array/storage-pools
Total free space for the pool should match the pool free space as seen from the VNX GUI
Affected Products
VPLEX SeriesProducts
VPLEX Series, VPLEX VS1, VPLEX VS2, VPLEX VS6Article Properties
Article Number: 000171054
Article Type: Solution
Last Modified: 05 مايو 2026
Version: 6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.