HPE XP Intelligent Storage Manager 10.0.1-00 Release Notes for XP Intelligent Management Suite
Part Number: P14272-003 Published: November 2019 Edition: 1 © Copyright 2019 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. Description This is release version 10.0.1 of Hewlett Packard Enterprise XP Intelligent Storage Manager (ISM). Update recommendation Recommended Superseded version 3.4.1
Product models HPE XP Intelligent Storage Manager
Devices supported HPE XP7 Storage HPE XP8 Storage
Supported microcode/firmware Intelligent Storage Manager 10.0.0-00 and 10.0.1-00 supports:
• XP7 Storage with microcode version 80-06-6x or later. • XP8 Storage with firmware 90-01-4x or later.
Operating systems VMware ESXi 5.0 or later
Languages English
Important considerations None
Enhancements Intelligent Storage Manager provides support for:
3 Version 10.0.1 includes:
Ability to register Intelligent Storage Manager with HPE XP Common Services
Version 10.0.0 includes:
• HPE XP8 Storage • HA Setup page • HA unprovisioning • Manual storage system refresh • Ability to upgrade in place • CU:LDEV setting during resource addition to VSM • CU:LDEV setting during migration task creation and update • Capacity saving setting during migration task creation and update • Automatic job screen refresh • Attach volumes by selecting server group • Maintenance information collection from CLI, as a part of this item, changed application log collection method from virtual appliance manager to CLI • Support for startTLS for LDAP directory server and the management server communication • Intelligent Storage Manager now operates in several additional locales (German, French, Spanish, Italian, Simplified Chinese, Traditional Chinese, Korean, Japanese) • During HA provisioning or protect with HA operation, the system attempts to use the physical volume ID which is the same as the primary volume physical ID as the HA secondary volume physical ID • Recommended ports are displayed for the volume attach operation of XP8 storage systems • Ability to use existing resource group for VSM resource addition if matching resource group exists • List view is now the default view • The OVF now has a full Linux-based operating system • Support for Docker v18.09.x
Fixes
• Cannot unvirtualize an external volume which is over 4TiB under DDM pool. • Cannot migrate DDM volume. • Users that are part of the user group with ForeignSecurityPrincipal members are unable to log in to Ops Center Administrator. These group members are included with AD migration and in the “cn=ForeignSecurityPrincipals” OU container.
Issues and workarounds The following table lists known issues in the current release of Intelligent Storage Manager.
4 Problem Workaround / Comments
The Intelligent Storage Manager user interface may display The service is down, resulting in the alert indicating an only a 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 loading large numbers of objects in the UI, the page Reload the page and use the filtering functionality, if 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.
No error is reported when the Change IP Address Utility is When running the utility, make sure that the specified executed with a default gateway that is outside the subnet default gateway is in the same subnet as the desired VM IP. of the VM. Configuring an invalid gateway will result in your VM being inaccessible from another subnet.
An unexpected time lag is noticed in Intelligent Storage There is a lag when resources are created outside of Manager when resources are loading. Intelligent Storage Manager.
Wait for Intelligent Storage Manager to process the resources.
Refcode mapping to SNMP trap description is not Refcode mapping file is available in the product available. installation media.
When a volume is in the process of being restored (RCPY Once the restore is complete, scheduled snapshots resume state), subsequent scheduled snapshots may fail with the without errors. error message:
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.
Table Continued
5 Problem Workaround / Comments
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 CP. To add a switch, onboard with the active control processor.
Immediately unprotecting a volume after it is protected with A volume can only be unprotected when it is in the PSUS/ Clone Now results in the error message: It was SSUS state. If the state is COPY, wait and retry again. 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 disallow 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. It is not recommended to deleted volume as part of a pair. It is also possible in this perform volume deletion operations outside of Intelligent scenario for a subsequent volume created in Intelligent Storage Manager, especially if they are part of a replication Storage Manager to be mistakenly assigned a status as a group. If issues result from such operations, contact Hewlett cloned volume. Packard Enterprise customer support.
If a server is added while a storage system is being added, Wait for the internal cache to refresh. the server will not have accurate attached volume information for the server.
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 into Intelligent Storage Manager and exists, such as: into the db Docker container and delete the server details.
WWN 100000053326df1a already exists.
Initialization of multiple parity groups on FMD DC2 disks Wait for the formatting to complete. jobs 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 on the server that the actual from a fastsnap. capacity matches the volume capacity in RAID Manager.
Changing security settings in Intelligent Storage Manager Ignore the popups. occasionally creates false job started popups 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.
If the snapshot schedule is for day 31 of the month, the Set the scheduler for any day from 1 to 28. schedule will not run in months with fewer than 31 days.
Onboarding of a storage system fails. Restart the service processor.
Table Continued
6 Problem Workaround / Comments
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 create the parity group again.
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 is completed and update the IDs accordingly.
Pool creation using the Basic workflow fails if the chosen tier Select only compressed or encryption-enabled parity groups capacity contains both encryption-enabled and compressed for pool creation. 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 will fail without data loss, so this issue can be in use. ignored if parity groups that are in use are selected by mistake.
When backup files that include changes to network settings If the appliance comes back online after a restore operation are restored, storage system inventories may fail to be with its inventories missing, wait ten minutes for the restored. inventory to refresh. If the elements are still missing, return to virtual appliance manager (VAM) and restore the backup file again.
Onboarding of an XP7 storage system succeeds with errors: For XP7, create a new user account in Remote Web Console and use it when on-boarding 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.
When attaching or detaching 50 or more volumes at once, When updating the storage system credentials, do the Elasticsearch may become unavailable. Restrict bulk attach/ following: detach operations to no more than 25 volumes at one time. Restart either the VM or the Elasticsearch container.
Table Continued
7 Problem Workaround / Comments
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 page. 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_
Delete pool job fails on a compression-enabled parity group. To reuse the parity group for pool creation: 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.
Snap volumes reported in Intelligent Storage Manager will Use the pool summary to retrieve information about the pool always report a capacity usage value of 0 GB, because the capacity usage. storage array does not report capacity information for secondary volumes.
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.
Cache refresh fails with message: Contact Hewlett Packard Enterprise customer support. The disk ID is Invalid.
Table Continued
8 Problem Workaround / Comments
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 created in Intelligent Storage Do not rename a snapshot copy group created in Intelligent Manager is renamed in Remote Web Console or in RAID Storage Manager. 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 page, and groups can be found on the Pool Detail page under Tier the Storage System detail page. 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.
On the Pools inventory page and Volumes inventory page, Do not perform any update or delete operations on the the mainframe pools and volumes are displayed. mainframe pool.
Pool auto-selection selects mainframe pools for volume Mainframe volumes cannot be attached or protected in ISM. creation. Do not select mainframe pools to create volumes.
Replication groups cannot be deleted when all PVols are On the Replication Groups inventory page, manually delete unprotected. the partially deleted replication groups.
The Attach Volume operation or the Create and Attach Select a port that is enabled for the VSM. volume operation fails if a port is not part of the VSM.
Table Continued
9 Problem Workaround / Comments
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.
Unable to attach a volume to a server with a name longer Rename the server name to a name that has fewer than 61 than 60 characters. characters. Then retry to attach the volume.
Attach, Protect volume, Delete server, or List path 1. Remove the host mode option from the iSCSI target operations fail when iSCSI ports on the array are configured (Host Group of iSCSI) on the storage system. using Remote Web Console. 2. Recreate the iSCSI target on the storage system so that the iSCSI target ID will be changed.
When the snapshot creation fails, an external replication 1. Log in to Remote Web Console. group is created. 2. Go to Replication. 3. Select the Local Replication tab. 4. Select Snapshot Groups. 5. Delete Replication/Snapshot Group Name.
When creating multiple parity groups, a child job fails with Wait for some time and try again. null pointer exception.
Cannot access ISM after changing the network address of Do one of the following: the ISM server. • Rename ifcfg-eth0_bkup to bkup_ifcfg- eth0, and then reboot the ISM server from the root account.
• Remove ifcfg-eth0_bkup, and then reboot the ISM server from the root account.
• Issue the ip-change command with the same settings from the service account.
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
10 Problem Workaround / Comments
Backup does not restore appliance details (NTP settings/Log Set NTP/Log/Certificates/user credentials after the restore settings/Certificate Settings/user settings - Password of using the virtual appliance manager. service account)
When creating a volume from the Pools inventory, the pool Create the volume from the Volumes inventory page and is deselected in the Create Volumes page. select the required pool.
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. SSH to ISM. 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 which external parity group the external LUN belongs to. 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 page to suggest paths. Trace process takes excessive time (5 second for each switch), the paths manually between server and storage port. causing the attachment operation to cancel. This can occur if ISM manages more than 5 switches.
Table Continued
11 Problem Workaround / Comments
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
When the pool volume status is blocked for DDM, another 1. Issue the RAID Manager command for the LDEV with 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.
Unable to add an LDAP account domain if the ISM server is No workaround. in a different domain.
Table Continued
12 Problem Workaround / Comments
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.
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.
Table Continued
13 Problem Workaround / Comments
If containers are not accessible while restore is in progress, 1. Restart 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 error "The virtual storage machine Retry the operation. 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 error. Unable to find pool for provided pool type.
When the host mode option is set to auto for HP-UX, Select the host mode option corresponding to the operating SOLARIS, AIX, OVMS or TRU64, all values are always set to system. null.
For local replication configured for multiple servers, deleting Wait 20 minutes for the cache to update. or creating Clone / Snap On Snap takes some time to update cache.
After creation of Business Copy or Fast Snap, attaching the Wait 20 minutes and try the operation again. 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.
Warning dialog may be displayed inappropriately when None. attempting to attach volumes to servers for which CHAP user is set.
Table Continued
14 Problem Workaround / Comments
A job targeting a VSM may fail if the target VSM contains a 1. Log into Remote Web Console page. 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.
When Pool is created with multiple tiers specified (in Basic Update pool tier setting manually to set tiering policy mode or API) or with Tiered setting (in Advanced mode or setting. API), job may fail with an error that an order to the control/ command device was rejected. As a result, the pool is created, but Tier-related setting may not be set appropriately.
Attach volume fails while is onboarding at least one storage Wait until Intelligent Storage Manager completes storage system with a VSM with the same the model and serial system onboarding and retry the operation. number as the VSM of the volume that is being attached.
Table Continued
15 Problem Workaround / Comments
Warning dialog with a message cannot begin 1. Log in to Remote Web Console. restore process is displayed when restore operation 2. Navigate to Ports / Host Groups/ ISCSI targets. 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 cache refresh in Intelligent Storage Manager.
Action-failed dialog with an internal error message is No workaround. displayed when attempting to change server name on VAM. However, the server name change is applied successfully.
Attachment of volumes with 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.
Error message is displayed just after deployment and log in None. Ignore the message and continue. to Intelligent Storage Manager with message: Resource FabricResource is not available.
When HA creation/deletion job fails with an error, HA pair Refresh the primary storage system, then secondary storage information may not be displayed appropriately. 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.
When there is replication created by DPM in the data flow Delete replication created by DPM in DPM UI first, then retry which is originally created by Intelligent Storage Manager, HA unprovisioning in Intelligent Storage Manager. HA unprovisioning fails with an error.
After restore operation in virtual appliance manager, service Re-configure service account credential in virtual appliance account credential is set to default. manager after restore operation.
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 Intelligent Storage Manager job fails, warning may be Restart docker service and retry operation. shown when you try to run a task on the resource which is directly/indirectly related to the failed job.
Table Continued
16 Problem Workaround / Comments
HA pair status may become NONE after Intelligent Storage Manually refresh the secondary storage system and when Manager is started. the secondary storage system refresh completes, manually refresh the primary storage system.
Capacity field of the volume in Create, Attach and Protect Manually enter volume capacity information. 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 replication group if the pair is treated as as External replication if status is not PAIR or pairs are External replication due to this issue. swapped. Use DPM to change pair status to PAIR and if 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 right after overwrite upgrade installation and no error message is displayed.
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)
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, refer to the getting started guide.
Table Continued
17 Server Description
CPU 4 vCPUs
A client computer that can run a supported browser At least one of the following:
• Internet Explorer v11 (and only certain minor versions of IE: 18537, 163841S) or later • Firefox v31.3.0 ESR, v34.0.5 or later • Chrome v38.0.2125.122 or later
Verify that Intelligent Storage Manager ports do not overlap with those used by other programs on the storage system.
Service Active Directory and Active Directory Protocol Type and Port Domain Service Usage
RAID Manager N/A 31001/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 Installer 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 Appliance Software 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.
18 Upgrading by overwriting a previous version of Intelligent Storage Manager
Prerequisites • Overwrite upgrade can only be done from v3.4, v3.4.1 or v10.0.0 to v10.0.1. • 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 root account. 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 service account credentials when prompted. The default credential for an application installation are:
• User name: system • Password: manager
The default credential for a virtual appliance installation are:
• User name: service • Password: Chang3Me!
6. Enter y at the Do you want to upgrade [y/n] prompt. Intelligent Storage Manager upgrade starts.
Troubleshooting the overwrite upgrade installation If the installation fails, try the following:
19 • Check the error message and retry the installation. • Restart the Docker service, check that the older version is running and then retry the installation. • Check the Docker logs. See Docker documentation for more information. • Journal entries may have additional information about the error. To view the journal log, connect to the host with the root account and run these 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 application installer version is originally installed, remove the older version and start the fresh installation. ◦ For the environment where 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 To upgrade from Intelligent Storage Manager v3.4.x or v10.0.0 to v10.0.1, do the following:
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 v3.4 or v10.0.0 installation of Intelligent Storage Manager, access the virtual appliance manager at: https://
20 • User name: service • Password: Chang3Me!
The default credentials for an application installation are:
• User name: system • Password: manager
4. When the virtual appliance manager opens in the browser, click Backup to download a backup file of 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 v3.4 or v10.0.0 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 wish to declare a maintenance window to do this as the Intelligent Storage Manager product will be unavailable until the upgrade is complete.
6. Deploy version v10.0.1, using the method of your choice. Follow the instructions in the 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 into 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 virtual appliance manager opens in the browser, click Restore. You will be prompted to upload the backup file that was downloaded earlier. 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 Intelligent Storage Manager v10.0.1 instance. The progress bar may indicate 100% completion even though the operation has not completed.
21 Registering Intelligent Storage Manager server with HPE XP Common Services With v10.0.1, you can register the Intelligent Storage Manager v10.0.1 with your HPE XP Common Services portal by running a script included with Intelligent Storage Manager 10.0.1. After running this script you can access the Intelligent Storage Manager application from the portal using the Intelligent Storage Manager credentials. To register Intelligent Storage Manager, run the script using the procedure described in this section.
Prerequisites • The Intelligent Storage Manager server and HPE XP Common Services server must be up and running. • The Intelligent Storage Manager server is 10.0.1 or later. • The HPE XP Common Services server is 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 root account.
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
22 Display Name :MyAdministrator1 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 http://www.hpe.com/info/ storage/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.
23