Release Notes

Resolved issues
The following high severity issues are resolved in this release:
Table 11. Issues resolved in Storage Center 7.5.1
Issue Functional area Description
SCOS-61427 Alerts, Logs, and
Reports
Storage Center might generate alerts about pagepools entering conservation
mode despite plenty of free space on the disks. This issue occurs when
the Threshold Allocation value is less than the Threshold Conservation value,
which prevents Add Space from running before the storage system enters
Conservation mode.
SCOS-61253 Alerts, Logs, and
Reports
If the rsyslogd process stops working on a controller, it does not restart until the
controller is rebooted, which can result in missing entries in the syslog.
SCOS-61116 Alerts, Logs, and
Reports
If a replication link goes down, an alert with the confusing message Disk xx
all paths to device are down might be displayed. The alert with the
message Disk xx all paths to device are down is an alert about
replication, not an alert about a disk being down.
SCOS-60431 Alerts, Logs, and
Reports
The LDAP logging functionality in Storage Center does not log enough
authentication activity information to troubleshoot LDAP authentication issues.
SCOS-55150 Alerts, Logs, and
Reports
Storage Center might generate invalid alerts and syslog entries for validation
failures due to short-term failures like IPC connectivity issues or out of memory
conditions.
SCOS-61819 Data Reduction An issue with data compression might cause volume I/O to stall on a storage
system.
SCOS-60541 Data Reduction The deduplication garbage collection process might miss pages on large storage
systems.
SCOS-60114 Data Reduction Reduced the data progression runtime for storage systems that are using
compression or deduplication.
SCOS-59577 Data Reduction In rare cases, a segmentation fault might occur during deduplication ingestion.
SCOS-58642 Data Reduction High latency on read I/O can be caused by deduplication metadata locks.
SCOS-62567 Front-End
Communication
ESXi hosts might lose access to datastores because of path failures between
ESXi hosts and storage systems with SAS front-end ports.
SCOS-61920 Front-End
Communication
When a storage system Fibre Channel (FC) port is connected to a fabric switch
that initiates login from its name server address, a port restart may occur during
a local port rebalance.
SCOS-61731 Front-End
Communication
Performing a Jumbo Frame ping to a Chelsio T3 port with VLAN tagging enabled
might fail
SCOS-61060 Front-End
Communication
A controller might reset because of an issue with the QRQCM driver.
SCOS-60715 Front-End
Communication
Storage Center does not allow the removal of Virtual Port entries that were
associated with a Preferred Physical Port entry that has been removed from the
fault domain.
SCOS-60710 Front-End
Communication
Storage Center does not allow the removal of all ports from a fault domain and
the removal of a fault domain without ports.
SCOS-61760 Hardware Some SC280 expansion enclosures do not support sending diagnostic messages
to SES vendor pages 0x91, 0x92, and 0x93.
SCOS-61130 Hardware A SCv3000 Series controller might reset because of a memory allocation issue
with a Chelsio driver.
SCOS-60200 Hardware Performing cluster validation on a Windows 2019 Hyper-V cluster might fail if the
server has two SAS HBAs, and a single port from each HBA is in a single fault
domain on the Storage Center.
6