# Remote Storage

Table 1. Remote Storage

        | S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
| --- | --- | --- | --- | --- | --- |
| 1 | Failure to Integrate HPE Alletra MP Plugin | Issues during plugin loading or integration of the HPE Alletra MP plugin in the Morpheus Enterprise environment. | - Confirm that the plugin `.jar` file is properly loaded as per section 5.2 “Adding HPE BMaaS Integration”. - Check if the correct credentials and URL for the storage array are used. | - **Plugin Logs**: Look for errors during plugin loading. - **System Logs**: Check for authentication or configuration failures. | - Ensure compatibility between the plugin version and Morpheus Enterprise. - Network/firewall issues may prevent communication with the storage array. |
| 2 | Storage Server Creation Failure | Failure when adding a new storage server (URL, credentials, or type mismatch). | - Verify the URL and credentials for accessing the storage array. - Ensure the correct type (“HPE Alletra Block Storage HVM”) is selected. | - **Storage Server Logs**: Check for error messages related to server creation (authentication issues, network problems). | - An incorrect URL or credentials can prevent server creation. - Make sure the storage server is accessible and reachable from the Morpheus interface. |
| 3 | Datastore Creation Failure | Issues while creating a datastore, such as selecting an incorrect storage server, or specifying incompatible resource pools or protocols. | - Verify that the storage server was created successfully. - Ensure correct datastore type and resource pool selection. - Ensure "FC" is selected for protocol. | - **Datastore Logs**: Check for errors when trying to create the datastore (incorrect type, wrong resource pool). | - Mismatched storage configuration or resource pool selection can lead to datastore creation failures. - Confirm network configurations for FC protocol. |
| 4 | Volume Creation Issues | Errors when creating volumes, including failure to assign the correct size, volume type (replicated/unreplicated), or datastore. | - Ensure the storage server is selected correctly. - Verify the volume size and type are correct. - Confirm the datastore is properly associated. | - **Volume Logs**: Errors related to volume creation (incorrect parameters, missing datastore). | - Volume size can only be increased - check the requirements. - Ensure correct replication type (CPP/APP) based on the storage array setup. |
| 5 | Volume Deletion Failure | Unable to delete volumes due to them being attached to servers or due to incorrect permission settings. | - Confirm the volume is detached from all servers. - Ensure you have the necessary permissions to delete the volume. | - **Volume Deletion Logs**: Look for errors related to detachment or permission issues during deletion. | - Volumes can only be deleted once detached. - Ensure no active processes are using the volume. |
| 6 | Volume Resize Failure | Unable to resize a volume, typically due to a lack of rescan on the server OS or exceeding size limits. | - Confirm the server OS has rescanned the volume. - Ensure the new size does not exceed any system or storage limits. | - **Volume Resize Logs**: Look for errors when attempting to resize (e.g., "resize failed" messages). | - Resize operations are only allowed for volume increases, not reductions. - Ensure the OS is aware of the new size after the resize. |
| 7 | Volume Consumption Issues During Provisioning | Difficulty attaching volumes during instance provisioning (shared/unshared, existing/new, replicated/unreplicated). | - Ensure the correct volume type (shared/unshared) is specified. - Verify replication settings (CPP/APP) are correct. - Check if the volume exists and is accessible. | - **Provisioning Logs**: Check for errors related to volume attachment (invalid volume, replication mismatch). | - Volumes must be properly configured before provisioning. - Shared volumes should be attached to all servers within the instance. |
| 8 | FC Protocol Issues | Issues with FC protocol during volume creation or consumption (e.g., failed attachments or slow response). | - Check if the storage server and datastore are properly configured for FC. - Confirm FC switches and network paths are properly set up. | - **Fibre Channel Logs**: Look for errors indicating FC connectivity or protocol issues. | - FC issues may be related to network misconfigurations or cable/connectivity problems. |
