Article Number: 000155626
| Issue ID | Functional Area | Description | Workaround/Resolution |
| MDT-144591 | Data Collection | In PowerStore Manager, when viewing the labels in the Dashboard > Performance tab, and Summary chart, the Latency, IOPs, and Bandwidth labels are not complete. The calculations that are presented are:
The "Latency" label should also be displayed as "Average Latency" when viewing the Bandwidth details, IOPs details, Latency Details, and I/O size in the Dashboard>Performance chart. The same issue occurs when exporting the data from the Dashboard>Performance tab, and Summary chart to a .csv format. |
None |
| MDT-143159 | Data Collection | The logical used metric for an appliance includes system internal volumes in the calculation, while the logical provisioned metric does not include system internal volumes in the calculation. | None |
| MDT-121809 | Data Collection | The system metrics display a steady state of activity even when there is no host I/O. This activity is background I/O used to maintain coherency in the NAS file system. | None |
| MDT-115320 | Data Collection | In the one-hour view of Performance metrics, the value at the top of the charts may not match the value that is shown in the chart below it. Also, the values may not update simultaneously. | None |
| MDT-81498 | Data Collection | Performance metrics for the front-end Ethernet ports are available through the PowerStore REST API, performance_metrics_by_fe_eth_port, and in the PowerStore Manager. These stats are reporting all I/O through that port, however, there is no distinction between different categories of I/O, such as iSCSI, replication I/O, internal I/O. | None |
| MDT-433662 | Data Protection | Pausing a volume replication on the destination system while an NDU is occurring on the source system may cause a mismatch of replication states and prevent the volume from replicating. | Pause the replication on the source system and then resume the replication. |
| MDT-429755 | Data Protection | Customers are not allowed to change the node affinity of replication destination volumes. | Change the node affinity of nonreplicated volumes to balance the workload across the nodes. |
| MDT-427983 | Data Protection | Replication performance may be impacted when extension switches are used in the storage environment. | Use the High network latency option when extension switches are used regardless of the latency or packet loss. |
| MDT-196359 | Data Protection | Not all days are displayed correctly when you view snapshot rules that are returned from the "show days_of_week" CLI command. | Use other display options such as "-o nvp" or "-o json." |
| MDT-126774 | Data Protection | Information about the source and parent of a thin clone is not easily accessible. | From the thin clone details page, click the pencil icon next to the thin clone name to view detailed information, including the source, the parent, and when the thin clone was created or refreshed. You can also add the optional column, Family ID to the volume or volume group table. Filtering by Family ID identifies all the thin clones and the base resource in the family, which can help identify the parent resource. |
| MDT-178690 | Hardware | An unplanned appliance reboot may occasionally result in a disk page leak (up to 512 per occurrence). These pages contain no user data or active metadata, and there is no data loss. | Contact your service provider. |
| MDT-447077 | Import | The REST API size attribute of the file system on a source NAS server may be displayed in MB instead of bytes. | None |
| MDT-436110 | Import | Unable to download the file import report when all NAS dockers are stopped. | Use the REST API command /file_import_session/{id}/report to download the file import report. |
| MDT-424389 | Import | When a VNX file system is imported, the Data Connection column on the Remote Systems tab may display "Status not available" for the VNX connection. | None |
| MDT-194635 | Import | When a NAS server is imported from a legacy Dell storage system, the "Importable Status" and "Non-Importable Reasons values" for the source NAS server may fail to update automatically. | Click Refresh NAS Server on the Select NAS Servers page to manually update the "Importable Status" and "Non-Importable Reasons" values. |
| MDT-147910 | Import | Importing a volume from a source system to PowerStore fails while switching path on host. This issue only impacts Linux operating systems. If any "blocklist" keyword appears in the multipath.conf file before the blocklist {} block, the host plug-in fails to blocklist the source volume, and the import fails. For imports to be successful, the keyword "blocklist" and curly brace should appear in the same line, for example, "blocklist { " in /etc/multipath.conf file. | Modify the multipath.conf file manually, if not present already, to "blocklist {" form. If multipath.conf has "blocklist" keyword, such as product_blacklist, before the blocklist section, move that section after the blocklist section for imports to work successfully. |
| MDT-139298 | Import | During import, if the active controller on the Dell EqualLogic storage array is restarted, it may cause some import sessions to fail and may stop host I/O to some target volumes. | Manual cleanup may be required and host I/O to the source array could need to be restarted. |
| MDT-419494 | PowerStore Manager | If PowerStore Manager is displayed in a language other than English and a performance chart is downloaded in PDF format, the performance chart may contain unreadable characters. | If PowerStore Manager is displayed in a language other than English, download the performance chart in a different format such as PNG, JPG, or CSV. If PowerStore Manager is displayed in English, you can download the performance chart in any format. |
| MDT-415295 | PowerStore Manager | An error might occur in PowerStore Manager if the appliance name on the Hardware > Appliances screen is changed to a name that is more than 64 characters in length. | Change the name of the appliance to be 64 characters or less. |
| MDT-153361 | PowerStore Manager | When there is little I/O to volumes, the average io_size and average latency that is reported might be inaccurate. When I/O is greater than 1 I/O per second, these metrics should be accurate. Metrics are accurate when I/O is greater than 1 I/O per second. | None |
| MDT-145343 | PowerStore Manager | On the Storage > Storage Containers tab in PowerStore Manager, you may see an error message when you try filtering the entries that are based on the UUID column. |
Try filtering and sorting entries using another column. |
| MDT-141238 | PowerStore Manager | The Object IDs for PowerStore resources are not available in the object tables. | If you require the Object IDs for scripting, see the object URL when you go to the details page for the object in PowerStore Manager. The object ID is a sub string of the object details page URL. For example, "40ffcb14" is the object ID of the volume in the URL: http://10.0.0.1/#/storage/volumes/40ffcb14/capacity |
| MDT-138826 | PowerStore Manager | When a proactive cache vault operation is in progress, the Capacity tab in PowerStore Manager may display internal erroneous messages. | Ignore such internal error messages that appear when a proactive cache vault operation is in progress. |
| MDT-121748 | PowerStore Manager | The Ports card on the appliance details page, which appears in between Alerts and Hardware cards, only lists Ethernet physical or virtual ports. | To view all front-end physical Ethernet and Fibre Channel ports for an appliance, on the Hardware page, click the Ports tab. |
| MDT-80757 | PowerStore Manager | In PowerStore Manager, under Monitoring > Alerts, the first event that is associated with a newly inserted hardware component may appear without a name. | Based on the information in the event description, identify the affected component on the Hardware card under Hardware > Appliance. |
| MDT-207994 | PowerStore REST API | An incorrectly formatted REST request may return more results than expected. This issue occurs because filters that are incorrectly provided are ignored. When specifying filters, ensure that you provide the filter elements correctly. | If the user supplies the request in the correct format, there is no issue. |
| MDT-425548 | Security | If an appliance with the KMIP feature enabled is removed while all configured KMIP servers are unreachable, the remove operation succeeds. However, any subsequent attempt to add the appliance back to the cluster fails. | None. When an appliance is removed from a cluster with the KMIP feature enabled. it must be reimaged to be used again. |
| MDT-146882 | Security | Attempting to change the LDAP authentication of a NAS server from simple to Kerberos in PowerStore Manager fails if an SMB server is not configured. | Use the REST API to create an SMB server before changing the LDAP authentication of a NAS server to Kerberos. |
| MDT-141947 | Security | An iSCSI login may fail when it is performed immediately after configuring CHAP credentials through the PowerStore Manager or the REST API. | Retry the iSCSI login. |
| MDT-135211 | Security | Job_id field in the audit_event REST API is not supported and contains an invalid value. | None |
| MDT-418618 | Storage - Block | The "Status" and "Metro Lag" values on the Metro Volume tab in PowerStore Manager may be truncated. | The full "Status" value is displayed in the graphic on the left side of the Metro Volume tab. The full "Metro Lag" value is not displayed elsewhere in PowerStore Manager. To calculate the "Metro Lag" value, subtract the "Last Synchronization" time from the current time. |
| MDT-238415 | Storage - Block | The restore and refresh operations overwrite the contents of the storage resource with the data from the selected snapshot or clone. Data not flushed from the host cache before the operation could cause data integrity issues after the restore or refresh. | To prevent data integrity issues, shut down the application using the volume and take the volume offline on the hosts before proceeding with snapshot restore or refresh operations. |
| MDT-440618 | Storage - File | The Import Connection ID is shown instead of the Remote System ID in the localized error message that is displayed when a file import session fails. | None |
| MDT-296205 | Storage - File | PowerStore Manager and CLI do not display unique space metrics per file system. | None. For more information, see Dell Knowledge Base Article 000201686: PowerStore: Space Metrics - Volume Family Unique Data. |
| MDT-242904 | Storage - File | After changing the appliance name, the names that are displayed on the NAS Servers page, in the Current Node, and the Preferred Node columns are not updated with the new appliance name. | To see the updated appliance name, go to the Settings>Network IPs>Management tab. |
| MDT-169031 | Storage - File | An alert is not presented when a file system reaches its soft quota. | See the Events to receive the information about the files system reaching its soft limit quota. |
| MDT-143070 | Storage - File | Unable to modify the LDAP settings from simple authentication to Kerberos when SMB protocol is not configured on the NAS server. | Use one of the following options to work around this issue: Add the SMB protocol before making the LDAP modifications on the NAS server. Use the PowerStore REST API to make the LDAP modifications on the NAS server. |
| MDT-148309 | Support Connectivity | If a data collection fails to upload the first time, a successful subsequent upload may not properly reflect the success. | Verify the success of the subsequent upload from the associated job details and log messages. |
| MDT-137707 | Support Connectivity | SupportAssist cannot reconnect to PowerStore after being manually disabled through the service script and then reenabled through PowerStore Manager. | First, try to clear the error condition by disabling and reenabling SupportAssist again through PowerStore Manager. If those actions do not work, use the PowerStore REST API to disable, and reenable SupportAssist to clear the error condition. |
| MDT-133955 | Support Connectivity | While gathering support materials for SupportAssist, the option to "Send materials to Support when finished" is enabled. Once the process is completed, a "Success," status indicates that both the collection of materials and the upload to SupportAssist was successful. | None |
| MDT-127298 | Support Connectivity | Do not attempt to enable SupportAssist while in the middle of converting your system from IPv4 to IPv6. The system may lose contact with SupportAssist. | If the system looses contact with SupportAssist while in the middle of converting your system from IPv4 to IPv6, use the svc_remote_support service script to force_disable SupportAssist. |
| MDT-114008 | Support Connectivity | Alerts sent to SupportAssist through the external SupportAssist gateway may have timestamps that are slightly earlier or later than the actual time. | If this shift in timestamp is unacceptable, use SupportAssist with Direct Connect instead of the Gateway Connect mode. |
| MDT-85409 | Support Connectivity | When a SupportAssist REST API request is made containing an invalid resource ID, the request fails, however, a technically incorrect error message may be returned. | None |
| MDT-148124 | Virtualization | Metrics data may be unavailable in PowerStore Manager if a PowerStore cluster cannot communicate with vCenter Server due to a vCenter Server failure or connection problem. This issue also affects metrics that do not directly depend on vCenter Server statistics, such as Capacity metrics. | Restore the vCenter Server connection to the PowerStore cluster. |
| MDT-125727 | Virtualization | Registering a VASA provider using the FQDN of the PowerStore cluster is not supported. | Use the cluster management IP address when registering a VASA provider. |
PowerStore, PowerStore 1000X, PowerStore 1000T, PowerStore Expansion Enclosure, PowerStore 3000X, PowerStore 3000T, PowerStore Rack, PowerStore 5000X, PowerStore 5000T, PowerStore 7000X, PowerStore 7000T, PowerStore 9000X, PowerStore 9000T
19 Jun 2023
11
Solution