
Troubleshooting storage
• Increase 3PAR storage systems connection limit (page 166)
• Cinder block storage volume does not attach to virtual machine instance (page 167)
• Cinder block storage volume does not establish an SSH connection with the 3PAR storage
system (page 168)
• Specifying a device already in use causes an error when attaching a volume (page 168)
• Volume not associated with a volume type cannot be modified or deleted when the storage
driver is removed (page 169)
• Volume is in Error state when it is created without a block storage driver (page 169)
• Unable to associate block storage driver with 3PAR storage system (page 169)
• Unable to delete block storage driver (page 170)
• Unable to delete a volume type (page 170)
• Unable to edit a volume type (page 170)
• Volume created with a failed block storage driver cannot be deleted (page 170)
• Volume status is mismatched between CloudSystem Console and CloudSystem Portal (page 171)
• Renaming or changing the comment section in volumes with an “osv-” prefix in the 3PAR
storage system causes the volumes to become inoperable (page 171)
• Block storage volumes may indefinitely remain in undesired state (page 171)
• Last iSCSI initiator configured for an ESX host is used for attaching a volume (page 171)
• Attaching an iSCSI volume to an ESX instance slows if degraded LUNs exist in vCenter Server
(page 172)
• Volume state is not immediately updated when deleting a volume does not succeed (page 172)
• Block storage drivers Host CPG summary is not automatically updated (page 172)
TIP: For additional troubleshooting information, enable console access on your Foundation base
appliance using the CLI and then find the following log. To enable access, see “Enable console
access and set the password” (page 199).
• /var/log/cinder/volume.log
For more information, see the HP 3PAR StoreServ Storage Troubleshooting Guide available from
the HP Support Center at http://www.hp.com/go/support.
Increase 3PAR storage systems connection limit
Possible cause and recommendationSymptom
The default connection limit has been reached
The web service supports up to 15 connections, so there can be up to 15
OpenStack Block Storage servers enabled to access the 3PAR storage system.
However, the default number of allowed connections is lower. .
• Increase the connection limit to15 by opening an ssh connection to the
3PAR storage system and entering:
% setwsapi -sru high
% showwsapi -sru
The following will be displayed:
WSAPI server SRU is set to: high (15)
OpenStack Block Storage servers cannot
connect to the 3PAR storage system
166 Troubleshoot resource configuration
Comentários a estes Manuais