HPE XP Intelligent Storage Manager 10.6.0-00 Release Notes for XP Intelligent Management Suite
Published: March 2021 Edition: 1 © Copyright 2019-2021 Hewlett Packard Enterprise Development LP
Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel®, Itanium®, Optane™, Pentium®, Xeon®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. Java® and Oracle® are registered trademarks of Oracle and/or its affiliates. UNIX® is a registered trademark of The Open Group. All third-party marks are property of their respective owners. Release Notes
Description This is release version 10.6.0 of Hewlett Packard Enterprise XP Intelligent Storage Manager (ISM). Update recommendation Recommended Superseded version 10.5.1
Product models HPE XP Intelligent Storage Manager
Devices supported HPE XP7 Storage HPE XP8 Storage
Supported microcode/firmware
• XP7 Storage with microcode version 80-06-6x or later • XP8 Storage with microcode version 90-01-4x or later
Operating systems VMware ESXi 6.0 or later
Languages English
Release Notes 3 Enhancements
• Case-insensitive search is available for Volumes, Server Details, Host Groups, Virtual Storage Machines inventories, and some related dialogs and wizards. • The Storage System Details screen now includes an in-context launch to the Remote Web Console License Information screen. • For security reasons, the Intelligent Storage Manager server supports a server certificate chain length of up to 10 for TLS handshakes.
Fixes The following issues are resolved:
• When migrating volumes, the job that deletes a migration pair child job no longer fails with a message that includes, An unexpected internal error occurred.
• Upgrades no longer fail with a message that includes, Failed to restore backup data. • Text-based filtering now functions for on the Select Secondary Servers page for Create, attach and protect volumes with HA and on the Select Servers page for Detach Volume. • Attaching a volume no longer fails to assign the correct virtual volume ID. • In the Edit LUN Paths dialog box, changing a LUN and removing a path can now be completed in a single operation with no job failure. • If Intelligent Storage Manager manages storage systems that exceed the installed server CPU cores, a job that changes the storage system configuration no longer fails with the following message:Resource
The following known issues are resolved or are no longer applicable:
• An unexpected time lag no longer occurs in Intelligent Storage Manager while loading resources. • If a server is added while a storage system is being added, accurate server volume information is included. • If the snapshot schedule is for day 31 of the month, the schedule now runs correctly. • When backup files that include changes to network settings are restored, storage system inventories can now be restored. • In some older browsers, the bottom of the Tier Capacity graph for platinum-tier storage is cut off in the Pool Details window. • When attaching or detaching 50 or more volumes at the same time, Elasticsearch remains available for use. • Snap volumes reported in Intelligent Storage Manager no longer report a capacity usage value of 0 GB because the storage array does not report capacity information for secondary volumes. • Intelligent Storage Manager can attach or protect a volume even when an array has a host group with spaces in the name.
Release Notes 4 • On the Pools and Volumes inventory windows, mainframe pools and volumes are shown. Pool auto-selection no longer selects mainframe pools for volume creation. • Replication groups can now be deleted when all P-Vols are unprotected. • The Attach Volume or the Create and Attach volume operation no longer fails if a port is not part of the VSM. • When snapshot creation fails, an external replication group is no longer created. • Access to Intelligent Storage Manager is now available after changing the Intelligent Storage Manager server network address. • Backups now restore appliance details, such as NTP settings, log settings, certificate settings, and user settings (password of service account). • Intelligent Storage Manager no longer times out when creating a Docker container when the RMI port is changed for the storage system. • When the host mode option is set to auto for HP-UX, SOLARIS, AIX, OVMS or TRU64, all values are no longer set to null.
Important considerations None
Issues and workarounds
Problem Workaround / Comments
The Intelligent Storage Manager user interface displays a The service is down, resulting in the alert indicating an spinning icon or a yellow triangle if a call fails with an internal server error. Internal Server Error (500). Contact Hewlett Packard Enterprise customer support.
Hardware alerts on the Monitoring tab are not updated Click another tab and click the Monitoring tab to display unless you navigate to another tab and back to the updated alerts. Monitoring tab.
Spaces are automatically deleted from the beginning and No workaround. end of fields when entering SNMP configuration information.
When a large number of objects is loaded in the UI, the Reload the page and use the filtering functionality, if window slows down and eventually becomes unusable. possible. An option is to use the API instead of the UI.
Hardware monitoring alerts display even though alerts for Alerts are only cleared when all components of a given type some components of a given type (for example, fans, pools, with errors in the storage system return to a normal state. batteries) have cleared. The exception is disks, each of which can have alerts cleared, even if other disks remain in error. Alerts for ports and processors are cleared together, so alerts are cleared only when all ports and all processors are normal.
If one volume is attached to multiple servers, Data No workaround. Intelligent Storage Manager displays only Protection Alerts does not launch the Server Inventory one Server Detail page. page to display all servers that are affected.
Table Continued
Release Notes 5 Problem Workaround / Comments
No error is reported when the Change IP Address Utility is When running the utility, verify that the specified default executed with a default gateway that is outside the subnet gateway is in the same subnet as the VM IP address. If you of the VM. configuring an invalid gateway, the VM is inaccessible from other subnets.
Refcode mapping to SNMP trap description is not Refcode mapping file is available in the product available. installation media.
When a volume is being restored (RCPY state), subsequent Once the restore is complete, scheduled snapshots resume scheduled snapshots may fail with the error message: without errors.
An unexpected internal error occurred. Contact System Administrator if this condition persists. Failure details: An order to the control/command device was rejected It was rejected.
While creating pools, the following error displays: Confirm if the pool was created. If it was created, check that it matches the creation parameters. If it does not match, the Unexpected Error: LDEV not blocked. pool can be deleted through Intelligent Storage Manager. Then create the pool again.
Onboarding a control processor results in the error: • Confirm the status of the control processor; if it is active, create the zoneset. Switch has no active zoneset. • If the control processor is not active, then the IP address given was for the standby control processor. To add a switch, onboard with the active control processor.
If you immediately unprotect a volume after it is protected A volume can only be unprotected when it is in the PSUS/ with Clone Now, the following error message appears: It SSUS state. If the state is COPY, wait and retry again. was rejected due to SKEY=0x05, ASC=0x26, ASCQ=0x00, SSB=0xB9A2,0x23EF on Serial#(410304).
If a replication group has been set up using Intelligent Intelligent Storage Manager is designed to restrict volume Storage Manager and any snapshot volumes are deleted deletion if that volume is part of a replication group. without removing the replication group first, an issue may However, if volumes are deleted directly through the SVP occur where Intelligent Storage Manager still displays the console, the issue may still occur. deleted volume as part of a pair. It is also possible in this scenario for a subsequent volume created in Intelligent It is not recommended to perform volume deletion Storage Manager to be mistakenly assigned a status as a operations outside of Intelligent Storage Manager, especially cloned volume. if they are part of a replication group. If issues result from such operations, contact Hewlett Packard Enterprise customer support.
If a server is added while a storage system is being added, Contact your system administrator. The system the server job may fail with a message that a WWN already administrator can log in to Intelligent Storage Manager and exists, such as: in to the database Docker container and delete the server details. WWN 100000053326df1a already exists.
Table Continued
Release Notes 6 Problem Workaround / Comments
Initialization of multiple parity groups on FMD DC2 disks Wait for formatting to complete. completes after formatting is completed and the parity groups are in AVAILABLE status.
PVol used capacity does not change to 0 GiB after a restore After the restore, confirm that the actual capacity on the from a fastsnap. server matches the volume capacity in RAID Manager.
Changing security settings in Intelligent Storage Manager Ignore the popup messages. occasionally creates false job started popup messages even though no job is created.
Updating the pool template API without both Update both utilizationThreshold1 and utilizationThreshold1 and utilizationThreshold2 values. utilizationThreshold2 values results in a job failure.
Onboarding of a storage system fails. Restart the service processor.
When a pool created on a compression-enabled parity group Deleting the compression-enabled pool deletes the pool, but is deleted, the parity group cannot be reinitialized. the parity-group goes into an uninitialized state.
Delete the parity groups in an UNINITIALIZED state associated with the pool.
Try to re-create the parity group.
The Intelligent Storage Manager web interface displays the Wait for the storage system to be onboarded successfully. spinner animation when the user attempts to click a Not Accessible pool resource tile while a storage system is being added.
When importing a file from a backup, internal IDs of This issue only affects API users. If API operations are resources may change. dependent on resource IDs, verify the resources after the restore operation has completed and then update the IDs accordingly.
Pool creation using the Basic workflow fails if the chosen tier Select only capacity expansion-enabled or encryption- capacity contains both encryption-enabled and capacity enabled parity groups for pool creation. expansion-enabled parity groups.
Initialize Parity Group fails because the maximum number Wait for the status of some parity groups to change from of parity groups are in the QUICK_FORMATTING state. QUICK_FORMATTING to AVAILABLE, and then retry the operation for uninitialized parity groups.
The Initialize Parity Group operation reports successful job Verify if the parity group has been initialized. If not, wait for completion, but the parity group initialization has failed. the status of other parity groups to change from QUICK_FORMATTING to AVAILABLE, and then retry the operation.
A user is able to start a job to initialize parity groups that are The job fails without data loss, so this issue can be ignored if already in use. parity groups that are in use are selected by mistake.
Table Continued
Release Notes 7 Problem Workaround / Comments
Onboarding of an XP7 storage system succeeds, but with For XP7, create a new user account in Remote Web Console the following error message: and use it when onboarding the storage system.
An unexpected error occurred during communication with storage system.
On some older browsers, the bottom of the tier capacity The information should still be visible despite the edge of graph for platinum-tier storage is cut off on the Pool Details the graph being cut off. If it is not visible, update your page. version of Chrome, Firefox, or Internet Explorer and try again.
The number of volumes on the Servers screen and the Refresh the storage system. Servers Details screen may not match.
When updating the storage system credentials, Intelligent When updating the storage system credentials, do the Storage Manager updates the credentials stored in its following: database, but keeps using the session opened before the job started to update the storage system. 1. Log in to Remote Web Console and create your new credentials. 2. Log in to Intelligent Storage Manager and access the Update Storage System window. 3. Update the storage system credentials. 4. Connect via SSH session to the deployment using the root credentials. 5. Issue the Docker command: docker restart cli_xxx_
The Delete Pool job fails on a compression-enabled parity To reuse the parity group for pool creation: group. As part of the job, the pool is deleted, but initialization of the parity group fails. 1. Use Remote Web Console to format the blocked LDEVs. 2. Wait approximately 20 minutes for Intelligent Storage Manager to resync with Remote Web Console. 3. Create a pool on a compression-enabled parity group.
Capacity usage is not reported for external parity groups. Verify the capacity of the external parity group in Remote Web Console.
Unable to delete an THP Pool with deduplication enabled. Prerequisite: Delete all DRD volumes associated with the THP Pool.
Then, delete the THP Pool from the SVP:
1. Disable deduplication in Remote Web Console. 2. Wait for the cache to refresh. 3. Delete the THP pool from Intelligent Storage Manager.
Table Continued
Release Notes 8 Problem Workaround / Comments
Cache refresh fails with the message: Contact Hewlett Packard Enterprise customer support. The disk ID is Invalid. Array cleanup results in HORCM shutdown error: 1. Log in to the deployment via SSH. Please check if HORC manager is 2. Execute the following command: running or if HORCMINST is set correctly docker exec –it cli_xxx_ContainerID horcmstart 0
3. Execute a raidcom command to verify that RAID Manager is responding, such as: raidcom get pool -IM0
After a snapshot copy group that is created in Intelligent Do not rename a snapshot copy group created in Intelligent Storage Manager is renamed in Remote Web Console or in Storage Manager. RAID Manager, the snapshot fails with the message: The Command ended.
Clone creation fails with the error: Incorrect Pool 1. Confirm if the primary volume is created on a pool with State. deduplication or compression enabled. 2. Create a second pool with the deduplication or compression characteristics of the primary volume to create the clone.
Tier breakdown for external tier shows incorrect used The used capacity for pools created on external parity capacity on the Dashboard, the Storage Systems window, groups can be found on the Pool Detail window under Tier and the Storage System detail window. Information.
Cannot attach or protect a volume if an array has a host Do not create host groups with spaces in the name for an group with spaces in the name. iSCSI port.
Attachment of a volume with path auto-selection fails if the 1. Log in to the switch to which the storage port is target storage has a disabled port. connected with administrator credentials. 2. Enable the port corresponding to the WWN of storage port. # portenable {portId}
3. Exit the switch. 4. Attach the volume with the Storage Port enabled.
Or:
Select the target port with ENABLED status.
Cisco fabric switch addition fails with An unexpected 1. Log in to the switch. error occurred: Unknown error from 2. Create a zoneset on the switch. dependent service. 3. Enable the zoneset.
Table Continued
Release Notes 9 Problem Workaround / Comments
Cannot migrate an external volume greater than 4 TiB that 1. Access the Create Pool page and use the Advanced is virtualized from Remote Web Console. option to create a DDM pool. 2. Virtualize the volume using ISM. 3. Migrate the volume.
Unable to virtualize a volume when the DDM pool volume is 1. Log in through SSH to XP Intelligent Storage Manager. in the Blocked state. 2. Search for the serial number of the storage system that is blocked. #docker ps -a | grep -i cli_xxx_serialId #docker exec -it RAID Manager_serialId /bin/bash 3. Issue the RAID Manager command for LDEVs with status= BLK from the DDM Pool. # raidcom get ldev -ldev_list pool - pool_id {poolId} -IM0
4. Identify the external parity group to which the external LUN belongs. 5. Issue the RAID Manager command to connect the paths. # raidcom check_ext_storage external_grp -external_grp_id {externalParityGrpId} -IM0| # raidcom check_ext_storage external_grp -ldev_id {ldevId} -IM0
During volume attachment to servers, the path suggestion Do not use the Attach Volume window to suggest paths. process takes excessive time (5 second for each switch), Trace the paths manually between server and storage port. causing the attachment operation to cancel. This can occur if ISM manages more than 5 switches simultaneously.
Disconnected external parity groups and mapped volumes 1. Review the failed job for external parity groups details. cannot be reconnected after a virtualization job fails. 2. Issue the RAID Manager command to connect the paths. # raidcom check_ext_storage external_grp -external_grp_id {externalParityGrpId} -IM0 # raidcom check_ext_storage external_grp -ldev_id {ldevId} -IM0 3. Issue the get path command to verify the status is NML for the external parity group. # raidcom get path -IM0
Table Continued
Release Notes 10 Problem Workaround / Comments
When the pool volume status is blocked for the DDM, 1. Issue the RAID Manager command for the LDEV with another available DDM Pool is not automatically selected. status = BLK. # raidcom get ldev -ldev_list pool - pool_id {poolId} -IM0
2. Identify which external parity group the external LUN belongs to. 3. Issue the RAID Manager command to connect the paths. # raidcom check_ext_storage external_grp -external_grp_id {externalParityGrpId} -IM0| # raidcom check_ext_storage external_grp -ldev_id {ldevId} -IM0 4. Issue the get path command to verify the status is NML for external parity group. # raidcom get path -IM0
5. Repeat for all blocked volumes.
Following a change of host IP address and a storage system After all containers have started, restart the rainier-proxy restore operation, the user interface displays the 502 Bad container. Gateway message.
Virtualization for external volume migration fails when the Do not select an external volume that is not in the Meta created external volumes are in a different resource group Resource group. than the pool volume.
Onboarding a storage system fails with the error message: Restart either the VM or the Docker daemon.
Cannot connect to storage system.
The number of unused disks on Storage Systems Detail Check the available disks on the Parity Groups page. page is only displayed up to 10.
When an external volume is registered in a VSM, you cannot 1. Use Remote Web Console or RAID Manager to manage delete the VSM. the external volume from the VSM. 2. Remove the external volume using Remote Web Console. 3. Delete the external volume using Remote Web Console. 4. Delete the VSM.
The Failed to delete resource group due to number of 1. Remove undefined volumes or the host-group from undefined volumes field is not updated. Remote Web Console. 2. Wait for the cache to update. 3. Try to delete the VSM.
Table Continued
Release Notes 11 Problem Workaround / Comments
The Auto-select function does not show the path for the Specify the Host Mode and the Host Mode Option manually correct Host Mode and Host Mode Options from the or close the wizard and try again. following workflows:
• Attach existing volumes • Create Attach and Protect Volumes with Local Replication • Create Attach and Protect Volumes with High Availability • Protect Volumes with High Availability
The Edit LUN Path job may fail due to the following error Try the operation again. message:
Cannot map virtual volume id to the volume, because the volume has lun path.
If containers are not accessible while restore is in progress, 1. Restart the Docker service. VAM displays an error message that the exception file systemctl restart docker format is not valid. 2. Wait for the UI service, and then log in to Intelligent Storage Manager. 3. From the terminal, Issue: docker ps -a | grep -i rainier {dockerId} {image} Up 42 minutes 0.0.0.0:161-162->161-162/tcp, 0.0.0.0:161-162->161-162/udp, 8080/tcp 86dc768c0b894c55a3898ecb5df4e008_rai nier_1 4. Issue: docker exec -it {dockerId} /bin/bash
5. Exit. 6. In VAM, restore data from the already taken backup.
Create Volume fails with the error: The virtual Retry the operation. storage machine ID No VSM Selected (Default Meta Resource) is invalid.
If the pool tier name is changed for the target pool or for the Select the target pool manually. auto-select pool, create volume fails with the error: Unable to find pool for provided pool type.
Table Continued
Release Notes 12 Problem Workaround / Comments
For local replication configured for multiple servers, deleting Wait 20 minutes for the cache to update. or creating Business Copy or Fast Snap copies takes some time to update the cache.
After creating a Business Copy or Fast Snap copy, attaching Wait 20 minutes and try the operation again. the SVOL to server fails.
While attaching volumes to servers, no more than four paths No workaround. can be suggested.
The Share host group by all servers option is not available No workaround. in the Create External Volumes wizard.
A warning dialog may be displayed inappropriately when No workaround. attempting to attach volumes to servers for which CHAP user is set.
A job targeting a VSM may fail if the target VSM contains a 1. Log in to the Remote Web Console window. resource group with resource group name which consists of a blank space. 2. Click Administration and access the Resource Groups. 3. Select the resource group. 4. Click Edit Resource Group. 5. Remove any spaces from the resource group name. 6. Retry the operation.
Detach Volume completes with the following warning: 1. Log in to the switch.
Failed to remove connection between 2. Remove the zone from the switch.
For volumes attached to a server with auto create zone Use the following procedure to remove host group and zone enabled, removing paths through Edit LUN Path and information: detaching volumes may result in an error due to which server WWN in the host group and zoning may not be 1. Log into Remote Web Console. removed. 2. In the Storage Systems menu, click Ports/Host Groups/ ISCSI targets. 3. Select the port. 4. Delete the WWN from the host group. 5. Log in to the switch. 6. Delete the zone associated with storage system WWN and the server WWN.
Table Continued
Release Notes 13 Problem Workaround / Comments
When a pool is created with multiple tiers specified (in Basic Update pool tier setting manually to configure the tiering mode or API) or with Tiered setting (in Advanced mode or policy setting. API), the job may fail with an error that an order to the control/command device was rejected. As a result, the pool is created, but the Tier-related setting may not be set appropriately.
Attach Volume fails while Intelligent Storage Manager is Wait until Intelligent Storage Manager completes storage onboarding at least one storage system with a VSM with the system onboarding and retry the operation. same the model and serial number as the VSM of the volume that is being attached.
A warning dialog with a message cannot begin 1. Log in to Remote Web Console. restore process is displayed when the restore 2. Navigate to Ports > Host Groups > ISCSI targets. operation is completed, although backed up information is restored successfully. 3. Select host group name > Edit host groups. 4. Change the host group name. 5. Click Finish. 6. Wait for the task to finish. 7. Wait for the cache to refresh in Intelligent Storage Manager.
The Action Failed dialog box with an internal error message No workaround. is displayed when attempting to change the server name on the virtual appliance manager. However, the server name change is applied successfully.
Attachment of volumes with a LUN specified cannot be Do one of the following: submitted. An error message that the LUN is already reserved appears, even though the LUN is available. • Specify a different LUN and retry operation. • To use the same LUN, restart either the VM or the Docker daemon. SSH to Intelligent Storage Manager. # systemctl restart docker • Reboot the VM.
An error message is displayed just after deployment and log None. Ignore the message and continue. in to Intelligent Storage Manager: Resource FabricResource is not available.
When HA creation/deletion job fails with an error, HA pair Refresh the primary storage system, then the secondary information may not be displayed appropriately. storage system and then the primary storage system again.
If a volume is attached to unregistered servers, it cannot be Register servers to which the volume is attached. protected with HA.
Table Continued
Release Notes 14 Problem Workaround / Comments
When there is replication created by DPM in the data flow Delete replication created by DPM in the DPM UI first, then which is originally created by Intelligent Storage Manager, retry HA unprovisioning in Intelligent Storage Manager. HA unprovisioning fails with an error.
After the restore operation completes in the virtual Reconfigure the service account credential in the virtual appliance manager, the service account credential is set to appliance manager after the restore operation. the default.
Creating pool by using FMD DC2 and FMD HDE parity group After the pool is created, manually configure the pool by partially fails. As a result, a pool is created, but the pool may updating it. not be configured appropriately
When an Intelligent Storage Manager job fails, a warning Restart Docker service and retry the operation. may be shown when you try to run a task on the resource which is directly or indirectly related to the failed job.
The HA pair status may become NONE after Intelligent Manually refresh the secondary storage system and when Storage Manager is started. the secondary storage system refresh completes, manually refresh the primary storage system.
The Capacity field of the volume in Create, Attach and Manually enter the volume capacity information. Protect wizard launched from Attach Like Volumes may become empty.
User cannot enable TLS if the account domain is already Remove the account domain and enable TLS before registered. registering again.
HA pairs created by Intelligent Storage Manager are treated Do not delete the replication group if the pair is treated as as External replication if the status is not PAIR or pairs are External replication due to this issue. swapped. Use DPM to change the pair status to PAIR and if the HA pair is swapped, configure HA replication to non-swapped state to show HA pairs as Internal replication on Intelligent Storage Manager.
Cannot log in to Intelligent Storage Manager when you Wait for a few minutes and retry. attempt to log in immediately after the overwrite upgrade installation and no error message is displayed.
Installation of Intelligent Storage Manager fails with the error Avoid running install.sh to install or upgrade message No such file or directory when a Intelligent Storage Manager in a directory that contains a package is copied into a directory has a space in its file path. space in its path.
When attempting to create volumes from a pool that is part Wait for all jobs for that pool to finish, then try again. If the of a current job running, the Create Volume button does not issue still occurs with no related jobs are running, restart the respond when clicked. Intelligent Storage Manager server.
Attempting to remove a storage system that is already part Log in to a machine or VM where the Intelligent Manager of another removal job will prevent additional onboarding server is running and restart the Docker service. jobs of that storage system may not succeed.
Table Continued
Release Notes 15 Problem Workaround / Comments
Adding a LUN path between a WWN that is registered in a Manually add a zone setting that contains the WWN server and an existing port can fail if another WWN of the information. server is already linked with that port. If this occurs, the first WWN is successfully registered in the target port but the related zone setting is not created.
A job to detach volumes and remove zones results in a Delete the remaining zone manually. partial failure if there is a zone that cannot be deleted and includes a target volume and a target server's WWN.
Unable to log in to Intelligent Storage Manager after an Restart the Docker service. upgrade, restore operation, or an elasticsearch-memory- setting command execution.
The storage system refresh may not complete after an Restart the Docker service. upgrade.
In rare cases, attaching a volume that has an automatic LUN Refresh the storage system of the volume. If the problem still assignment fails because the LUN has been already mapped occurs, manually specify the LUN on the attaching volumes. to another volume.
Single sign-on between XP Common Services and Intelligent Make your XP Common Services host name resolvable from Storage Manager fails even if the host name of XP Common Intelligent Storage Manager. Services is written in the hosts file.
Single sign-on between XP Common Services and Intelligent Turn the Internet Explorer Compatibility View setting off. Storage Manager fails if Internet Explorer Compatibility View setting is enabled.
Running the setupcommonservice command fails Unregister Intelligent Storage Manager from XP Common after upgrading the Intelligent Storage Manager to 10.1.1 if Services, and then register again. all following conditions are met:
• The version of Intelligent Storage Manager before the upgrade is 10.0.1 or 10.0.2. • Intelligent Storage Manager is registered to XP Common Services before an upgrade.
XP Intelligent Storage Manager does not show which parity Use Remote Web Console or RAID Manager to find which groups are interleaved. parity groups are interleaved.
Table Continued
Release Notes 16 Problem Workaround / Comments
After a certain period has elapsed since a storage system is Restart the Docker service. onboarded with an SVP IP address, the following symptoms may occur:
• The GUI is partially displayed. • A pop-up message "Failed to get data from API. Try again." is displayed frequently on the GUI. • Running jobs do not finish.
The period can be several hours or days, depending on the number of onboarded storage systems, models and frequency of configuration changes.
If you selected to register Intelligent Storage Manager to XP If you want to change XP Common Services port number to Common Services during installation, the installer communicate by Intelligent Storage Manager, register XP automatically uses a port number of XP Common Services Common Services with the setupcommonservice based on a specified URL scheme (for example, if you specify command after the installation completed. a XP Common Services URL with https, the installer uses 443).
After a tier name is changed at the Tier management Do not change a tier name. Default values are: window, user capacity and total capacity of the tier is not displayed. Platinum, Gold, Silver, Bronze, External
The Domain Setting window of Virtual appliance manager Use a supported web browser other than Internet Explorer. unexpectedly displays an Action Failed dialog and does not display registered domain names. This problem occurs when all the following conditions are met:
• The web browser is Internet Explorer • One or more domain settings are configured at Virtual appliance manager
A dialog box that indicates a job was successfully submitted The job was successfully submitted. To confirm, go to the may not appear when submitting the job from a dialog box Jobs window. or a wizard.
A running job may not complete even if the actual process Restart the Docker service. has finished.
In Virtual Appliance Manager, changing an IP address of an Restart the Docker service. AD server operation does not update the IP address and the system attempts to use the IP address which is entered previously until the service is restarted.
If the Intelligent Storage Manager domain name includes an Do not use an underscore in the Intelligent Storage Manager underscore (_), the Virtual Appliance Manager screen is not domain name. accessible.
Table Continued
Release Notes 17 Problem Workaround / Comments
After changing the IP address of an SNMP trap in Virtual Remove the remaining SNMP trap entry using Remote Web Appliance Manager, the previous SNMP trap entry in the Console. storage system will remain, if it exists.
Changing the Intelligent Storage Manager server IP address Verify the SNMP IP address setting on Virtual Appliance can occasionally and unexpectedly apply also to the SNMP Manager and change the value, if needed IP address on Virtual Appliance Manager.
When simultaneously migrating a large number of volumes, Reduce the number of volumes to be migrated at one time. If the Migrate Volumes job will stall for hours after displaying possible, reduce the number of external parity groups in the the message: Storage System [Serial storage system. number]. Starting a migration task with ID [ID]. An import HA job may complete without an error even if the After the job completes, verify that the target HA pairs exist connected Data Protection Manager server is not available. in the Replication Group inventory. If they do not exist, verify the connection between Intelligent Storage Manager and Data Protection Manager. An import HA job mistakenly imports HA pairs that use a No workaround is available. quorum disk ID with no external volume. You cannot use a High Availability secondary volume To assign the same volume ID as the primary volume when physical ID to be the same as the primary volume physical ID there are multiple resource groups with the same virtual when multiple resource groups with the same virtual storage storage machine information, move the ID to metadevice in machine information exist and the physical ID is added to advance. the virtual storage machine. Intelligent Storage Manager overwrites the SNMP setting No workaround is available. even if the SNMP setting of the storage system is disabled. An attempt to perform an upgrade fails, and a message is Perform the following steps. output that includes, Failed to restore backup data. NOTE: Performing these steps will delete the job history information.
1. Acquire the backup data that was created when the upgrade failed. Copy the backup data file that was created when the upgrade failed to the client machine of Intelligent Storage Manager. The backup data is stored in the folder /tmp and the format of the file name is rainier-backup-*.tar.gz (example: /tmp/ rainier- backup-20200909-032929.tar.gz). 2. Delete the job information included in the backup data. Extract the backup data file and delete the contents of extracted directory /infra/hid-grizzly/ jobs.json. Then compress the extracted files again in the tar.gz format. 3. Uninstall Intelligent Storage Manager.
Table Continued
Release Notes 18 Problem Workaround / Comments
In the Create Path screen in the Attach Volumes dialog Remove the duplicate path by another tool and then try box, if there are multiple host groups that have the same again. WWN in a single port, the screen displays the duplicated paths and reject submitting a job. A job that requires a storage system's lock occasionally fails Retry the operation. If the problem continues, contact due to the error codes SSB1=0x2EF2 and SSB2=0x0009. Hewlett Packard Enterprise technical support. In rare cases, attaching a volume fails to assign the correct Check the volume. If this problem happened, detach it once, virtual volume ID to it with no error. and then attach it again. The Attach Like Volume dialog box presets a wrong When using the dialog box, verify that the capacity of the capacity unit. volume displays a correct value. If not, modify it in the dialog box. An error may not appear if you try to create a volume from a No workaround. tiered pool with invalid parameters, Removing a storage system occasionally fails with the Restart the Docker service. following error message:
An unexpected internal error occurred. Contact System Administrator if this condition persists. Failure details: I/O error on DELETE request for "http://localhost:8085/monitoring/ provider/api/status/600003/clear": Connection refused [errno=111, syscall=connect]; nested exception is java.net.ConnectException: Connection refused [errno=111, syscall=connect]
Only the last-chosen filter condition is effective in the table No workaround of the Use Existing LUN Paths screen.
Adding a WWN or iSCSI name to a server with the Apply After adding a WWN or iSCSI name, use the Edit LUN Paths changes to attach volume check box enabled fails if dialog box from the server to apply path settings to the Intelligent Storage Manager manages a storage system with storage system. no Fibre target port.
After Intelligent Storage Manager is installed, Unknown is Perform the following steps: displayed as the status of Intelligent Storage Manager on the XP Intelligent Management Suite screen. 1. Log in to the Intelligent Storage Manager server by using the root user account.
2. Restart the si container. # docker restart $ (docker ps -a | grep 6000/si | awk '{print $1}')
When a user attempts to protect a volume, the operation No workaround fails because there is a path addition failure to the created secondary volume if the storage system implements only iSCSI ports.
Release Notes 19 Installation requirements Verify that the environment meets or exceeds the minimum requirements to maximize all of the features of Intelligent Storage Manager.
Server Description
Hypervisor operating system VMware ESXi 5.0 or later
Docker version for installation from tar file v18.09.8 (minimum supported: v18.09.6)
v19.03.x
Python version for installation from tar file Python 3
When installing or upgrading Intelligent Storage Manager with the application installer, Python 3 is required to register Intelligent Storage Manager to XP Common Services.
Operating system for installation from tar file Linux
Access for installation from tar file Root user
Available disk space 80 GiB
100 GiB for installation using the application installer. This is due to the additional capacity required for the installer file and Docker requirements for image installation. After installation is complete, the required space is reduced to 80 GiB.
Memory 16 GiB RAM
NOTE: 32 GiB RAM is highly recommended for an environment where ISM manages 20 or more storage systems. For details, see the HPE XP Intelligent Storage Manager Getting Started Guide.
CPU 4 vCPUs
A client computer that can run a supported browser At least one of the following:
• Internet Explorer v11 or later
NOTE: Verify that the Font download option is enabled.
• Firefox ESR 68.0 or later • Chrome: Latest version of the stable channel
Verify that Intelligent Storage Manager ports do not overlap with those used by other programs on the storage system.
Release Notes 20 Service Active Directory and Active Directory Protocol Type and Port Domain Service Usage
RAID Manager N/A 31001/UDP and 34001/UDP
HTTP N/A 80/TCP
HTTPS N/A 443/TCP
Reserved N/A 1099/TCP, 8080/TCP, 8082/TCP, 8083/TCP, 8084/TCP, 8085/TCP, 8090/TCP, 11099/TCP, 51099/TCP, 51100/TCP, 8888 and 8843
SNMP N/A 161/UDP and 162/TCP
LDAP Directory, Replication, User and 389/TCP and 389/UDP Computer authentication, Group Policy, Trusts
DNS Names Resolution 53/TCP and 53/UDP
Data Protection Manager N/A 443/TCP
Installation instructions There are two Intelligent Storage Manager installations available. Each is delivered as a separate ISO image on a separate installation media. See the HPE XP Intelligent Storage Manager Getting Started Guide for complete instructions.
• Choose the Installer ISO (HPE XP Intelligent Storage Manager Installation Media DVD) to enable maximum control of the environment. Use the installer to create an instance of HPE XP Intelligent Storage Manager on any Docker-compatible operating system. • Choose the Appliance ISO (HPE XP Intelligent Storage Manager Preconfigured Media DVD) to deploy an OVF on existing virtualization infrastructure. The OVF contains a full Linux-based operating system running the HPE XP Intelligent Storage Manager software.
NOTE: Preconfigured media includes a publicly available operating system such as Oracle Linux. Hewlett Packard Enterprise does not provide support for this operating system, so we recommend that you regularly update it to prevent security issues. Contact Oracle support for any additional support or questions.
Release Notes 21 Upgrading by overwriting a previous version of Intelligent Storage Manager
Prerequisites • The overwrite upgrade can only be done from v10.3.0 or later to v10.6.0. • There must be 10 GiB of available space and a temporary total of 40 GiB of available space. • Ensure the backup and restore operation is not running.
NOTE: If you also want to upgrade the Docker version, upgrade Intelligent Storage Manager first and then upgrade Docker.
During installation, the following files are output under the folder where install.sh is located. Delete them if they are no longer required:
• Application log • Audit log • Installation log • Backup file
Procedure
1. Either open an SSH connection to the VM or open the VMware console and press Alt+F2 to reach the console. 2. Log in as a root user. 3. Copy the tar file from the installation media to any folder in the Linux environment and extract it. Navigate to the extracted folder.
4. In the directory where the virtual appliance manager resides, run the sudo ./install.sh command. 5. Log in with the following default service account credentials (which may have changed) when prompted. Application installation:
• User name: system • Password: manager
Virtual appliance installation:
• User name: service • Password: Chang3Me!
6. Enter y at the Do you want to upgrade [y/n] prompt. The Intelligent Storage Manager upgrade starts.
Troubleshooting the overwrite upgrade installation If the installation fails, try the following:
Release Notes 22 • Review the error message and retry the installation. • Restart the Docker service, verify that the older version is running and then retry the installation. • Verify the Docker logs. See Docker documentation for more information. • Review journal entries, which may have additional information about the error. To view the journal log, connect to the host with as the root user and run the following commands:
◦ journalctl --no-pager
◦ journalctl --no-pager -u docker
• If the installation produces any warnings or errors, they may point to the cause of the problem. Correct any issues the installer identifies, delete any Intelligent Storage Manager containers and images and start the installation again. • If the problem persists even though issues are corrected, try a fresh installation. 1. Verify that the backup file of the current version exists in the folder where install.sh is located and download the backup file. If the backup file does not exist, access virtual appliance manager and download the backup file. ◦ For the environment where the application installer version is originally installed, remove the older version and start the fresh installation. ◦ For the environment where the virtual appliance installer version is originally installed, discard the current environment and perform a virtual appliance installation.
2. Once installation completes, apply the backup file.
Upgrading from an earlier version of Intelligent Storage Manager You can upgrade Intelligent Storage Manager from v10.3.0 or later.
Procedure
1. Choose one of the following from the installation media:
• Use the Appliance ISO to deploy an OVF. The OVF installation deploys a VM with an operating system, Docker and Intelligent Storage Manager. • Use the Installer ISO to enable maximum control of the environment. The installer must be deployed in a Docker- compatible environment and contains only the Intelligent Storage Manager application.
NOTE: If you use the json-file logging driver, set the maximum log size to 50 MiB and the maximum number of files to 5.
2. In the current installation of Intelligent Storage Manager, access the virtual appliance manager at: https://
Release Notes 23 • User name: service • Password: Chang3Me!
Application installation:
• User name: system • Password: manager
4. When the virtual appliance manager opens in the browser, click Backup to download a backup file of the Intelligent Storage Manager system. The file may take a few seconds to start downloading. 5. After the backup file has been downloaded, shut down the current instance of Intelligent Storage Manager.
• If you used the Intelligent Storage Manager Installer model, delete the Intelligent Storage Manager Docker containers and images on the system before running the new installer. • If you used the Appliance model, the VM containing Intelligent Storage Manager should be shut down at this time. You may want to set a maintenance window to do this as the Intelligent Storage Manager product will be unavailable until the upgrade is complete.
6. Deploy the new version (v10.6.0), using the method of your choice. Follow the instructions in the HPE Intelligent Storage Manager Getting Started Guide until the product is initialized and ready to use. 7. In the new instance of Intelligent Storage Manager, log in to the virtual appliance manager. The default credential for a virtual appliance installation are:
• User name: service • Password: Chang3Me!
The default credential for an application installation are:
• User name: system • Password: manager
8. When the virtual appliance manager opens in the browser, click Restore. You are prompted to upload the backup file that was previously downloaded. Choose the file and upload it to the new instance of Intelligent Storage Manager.
The Intelligent Storage Manager appliance restarts. It may take up to an hour to restore the configuration. After the appliance is up and running, the upgrade is complete and the maintenance window can be lifted. (Optional) If the upgrade has completed satisfactorily, you can delete the VM containing the previous version of Intelligent Storage Manager.
NOTE: Do not cancel the restore operation. Cancellation may corrupt the new Intelligent Storage Manager instance. The progress bar may indicate 100% completion even though the operation has not completed.
Release Notes 24 Registering Intelligent Storage Manager server with HPE XP Common Services You can register Intelligent Storage Manager with your HPE XP Common Services portal by running a script included with Intelligent Storage Manager. After running this script you can access the Intelligent Storage Manager application from the portal using the Intelligent Storage Manager credentials.
Prerequisites • The Intelligent Storage Manager server and HPE XP Common Services server must be up and running. • The Intelligent Storage Manager server is version 10.0.1 or later. • The HPE XP Common Services server is version 10.0.1 or later. • If Intelligent Storage Manager was installed with the application installer (not a virtual appliance), install Python3 to run the script. • A user account with HPE XP Common Services that has the Application Administrator role.
Procedure
1. Either open an SSH connection to the VM or open the VMware console and press Alt+F2 to reach the console. 2. Log in as a root user.
3. Run the /opt/rainier/bin/setupcommonservice script. Parameters:
Parameter Required Description
csUsername Yes The username of an account with HPE XP Common Services csPassword Yes The password to authenticate a user specified in csUsername parameter csUri Yes The URL of the HPE XP Common Services server applicationHostAddres Yes The host name or an IP address of the Intelligent Storage Manager s server applicationPort Yes The port number of Intelligent Storage Manager applicationName Yes The name of the Intelligent Storage Manager server to display at the Intelligent Management Suite portal applicationDescriptio No A description of the Intelligent Storage Manager server to display at n the Intelligent Management Suite portal
Example command /opt/rainier/bin/setupcommonservice –csUsername sysadmin –csPassword sysadmin –applicationPort 443 –csUri https://common-services.example.com/ portal –applicationHostAddress administrator1.example.com –applicationName MyAdministrator1 –applicationDescription foobar Registering with following values: Hostname: administrator1.example.com Application Port :443 Display Name :MyAdministrator1
Release Notes 25 Application Description : foobar Registration Successful
After the command ran successfully, Intelligent Storage Manager is displayed in the portal. The name and description of the registered Intelligent Storage Manager server can be changed in the portal. If you want to change other properties such as host name, port number, etc, first remove the Intelligent Storage Manager from the portal, and then run the script again with appropriate parameters. Restrictions:
• Single sign-on compatibility with HPE XP Common Services: The single sign-on capability from Intelligent Management Suite portal to Intelligent Storage Manager is not available in this version. You must manually log in to Intelligent Storage Manager when you launch from the portal. • Displaying registered Intelligent Storage Manager status: Intelligent Storage Management portal displays the status of the registered application. For registered Intelligent Storage Manager, the Ready status is always displayed regardless of the application state. If you cannot launch the Intelligent Storage Manager login screen from the portal, despite the Ready status, check if the Intelligent Storage Manager server is running normally and that there is network connectivity between the Intelligent Storage Manager server and the HPE XP Common Services server.
Compatibility/Interoperability None
Determining current version In the Intelligent Storage Manager user interface, click the question mark (?) to view the installed version.
Related information The latest documentation for HPE XP Intelligent Storage Manager software is available at: https://www.hpe.com/info/XP-IMS-docs
Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback ([email protected]). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Release Notes 26