Release Notes

SAN Headquarters (SAN HQ)
While running SAN HQ on a PS6210 array, user reported a large number of the following event:
fsmRequest.cc:245:DIAG::7.6.5:context missing in read callback.
User Interface
User could not open Group Manager nor use Dell Storage Update Manager with Java v10.x.
The CLI command pool select default show returned an incorrect value of unknown .
Users could delete members in the maintenance pool using the CLI, but could not delete members using Group Manager.
Volumes
A volume administrator that was created using radius server was erroneously given maintenance pool access.
Issues Corrected in Version 10.0
This version of PS Series firmware includes all bug fixes that were incorporated into earlier releases.
Hardware
The NMC batteries in PS4210, PS6210, and PS6610 arrays were programmed to learn capacity and a temperature threshold
at 40C. This value was too low for normal ambient conditions and was changed to 55C.
Installation, Configuration, and Updates
When users saved the group configuration to a file using the save-config CLI command, the volume schedules related to
snapshot and replication were not saved.
Networking
Initiators might erroneously fail to log in to a single volume with Local reset initiated due to network errors .
Replication
Cross-platform replication snapshots were deleted even if the volume had an on-going replication scheduled or online
activated DR snapshots.
The time in all of the arrays involved in a cross-platform replication was not synchronized, which led to unexpected
expiration of replicas.
Cross-platform replication could not be configured because a volume was not created properly which prevented the system
from making the proper connections from the SC to the PS array.
[Critical] In very rare conditions where snapshot compression was enabled, PS6210 or PS6610 controllers could have
rebooted continuously due to a misinterpretation in the internal metadata structures. Additional code enhancements have
also been added in relation to this fixed item.
User Interface
When an SSH client attempted to log in to an array, sshd presented keyboard-interactive and public-key as valid
authentication methods, when they are not. This led to false-positive results on vulnerability scanners.
14