6.0.6_Fix_List (1)

8/14/2019 6.0.6_Fix_List (1)

1/9

Copyright 2012-2013

PS Series Firmware: FixList Version 6.0.6 (July 2013)Page 1 of 9

Dell EqualLogic PS Series Firmware Version 6.0.6 FixList

Note: Items that have the potential for significant impact on system availability or data integrity areidentified with the [CRITICAL]flag.

Issues Corrected in Version 6.0.6

PS Series Firmware version 6.0.6 includes all bug fixes that were incorporated into versions 6.0 or earlier.

Hardware After removing the array that previously was the group lead, the group could no longer send syslog

messages. [Tracking #: 562098]

Some PS41x0 and PS61x0 arrays incorrectly reported that the control module clock battery had a low

charge by issuing the following error message:Ti me- of - day cl ock batt er y vol t age i s l ow.[Tracking #s: 301264, 297744, 311890, 332643, 328593, 410414, and 412124]

While using EqualLogic PS-M4110 blade storage arrays, fans randomly may have revved up to a high

RPM rate and then went back down to normal. The getfanreqinfo section of the CMC logs showed normal

fan request percentages, but the airflow messages indicated one of the arrays requested 82 or 100 percent.

Volumes

When running SyncRep and doing a switch over between SyncActive and SyncAlternate pools, the

system sometimes became unresponsive for an undetermined amount of time. This condition waslinked to volume renames after a switchover and then a switchback. This issue also occurred withSyncRep switches with lower block size I/O.

Several fixes and improvements have been made in relation to conditions that might have determineda volume to become unavailable due to SyncRep after enabling/disabling SyncRep on a collection, or

after attempting switching to SyncAlternate pool. [Tracking #: 746454]

An issue was corrected in relation to an internal task pause that may have resulted in stuck pagemoveprocess while member free space was getting low.

An internal algorithm was improved to achieve more evenly distribution of connections across themembers in the same pool.



8/14/2019 6.0.6_Fix_List (1)

2/9

Copyright 2012-2013


Firmware Update Issues

During firmware upgrade to patched revisions of firmware (-Lx), the active controller may havefailed to load the specific patch, thus the update may have only been applied to the passive controller.[Tracking # 782219]

Hardware

In certain conditions, a fan failure warning event may have been displayed at various intervals with the

following message: Fan speed i s out si de operat i ng l i mi t s. Condition may then have cleared itselfseconds later.

On PS41x0 / PS61x0 platforms, controller modules may have reported invalid sensors reading as

sensor t emperat ur e bel ow t he operat i ng l i mi t . [Tracking #s: 420027 and 549161]

An issue that may have determined a passive controller to reboot spontaneously has been corrected toresolve the temporary effect on array redundancy. [Tracking #: 749774]

[CRITICAL] On very rare occasions, during controller bootup, new RAID labels may have beenwritten to the drives, resulting in data loss. [Tracking #s: 719252 and 725264]

In very rare circumstances, certain use of IP payload compression may have generated aninappropriate response at the targets which may have resulted in an unexpected controller failover.

[Tracking #: 706460]

In rare occasions when using OffloadDataTransfers (ODX) with Windows 2012 initiators, a specificWriteUsingToken command could have generated an inappropriate response at the target that may

have resulted in a controller failover. (see T10 specifications regarding Wr i t eUsi ngTokencommand)[Tracking #: 762035]

An improvement has been made when an array would be operating in high-altitude installations to

eliminate a cosmetic power supply fan speed error message in such circumstances. [Tracking #:687218]

Legacy platforms to include controller modules Type 2 and Type 5 may have experienced

unnecessary copy-to-spare of valid drives, if user was using SanAssist or ran diagnostics. [Tracking#: 758190]

CPU erratas have been reviewed for PS(M)41x0, PS61x0, PS65x0, and PS60x0 platforms to preventa watchdog reset that would have triggered an unexpected controller failover.

After a copy-to-spare process for a SMART tripped drive, a replacement drive may have beendisplayed as "history of failure" instead of becoming hot-spare. [Tracking #s: 796873 and 749774]

Replication

If SyncRep was in use but had been paused on a volume for a long time, it could have resulted in

either resource exhaustion on the controller or in an unexpected controller failover.

When using snap replication, the behavior of the unmanaged flag for the temporary promotion,

temporary promotion with failback and permanent promotion has been revised to fix issue when suchflag was inadvertently not removed. [Tracking #s: 424189, 619340, and 292232]

Volumes

A condition has been corrected that may have triggered unnecessary redistribution of the iSCSIsessions to the same array member when volume distribution had not changed. [Tracking #s: 634504,667173, 673207, 742967, and 777614]

8/14/2019 6.0.6_Fix_List (1)

3/9

Copyright 2012-2013


In certain scenarios, user actions of disable/enable, pause/resume of SyncRep-enabled volumes mayhave resulted in volume transition to an invalid internal state, requiring support intervention to restoreavailability of the volume to the initiators.

[CRITICAL] In very rare circumstances and after a failover in multiple RAID LUN arrays, aninternal log may have been inadequately committed, affecting volume page consistency. [Tracking#s: 694268 and 261429]

Other Issues

A PagedPool resource allocation method was revised to prevent resource exhaustion in certainscenarios. [Tracking #s: 797010, 700072, and 796918]

In very large Active Directory implementations with the EqualLogic FS7xx0 and one or more PS

Series arrays, repeated user / group list enumeration requests may have caused CIFS authenticationfailures and disconnects. A CLI support option was introduced to turn on/off the enumeration.[Tracking #s: 793483 and 814123]




During a firmware upgrade on a group using sync-rep which was out of sync, the restart causederrors, but did not generate a warning message.

Disk firmware updates from KD08 to KD0A started on controller types 1, 2, and 5 but failed. Codewas modified to no longer run firmware updates on these controller types. [Tracking #: 533460]

Following a firmware upgrade to version 6.0.1, when user converted from RAID 10 to RAID 50, thefollowing error was displayed: Warning health conditions currently exist. Correct these conditions

before they affect array operation. More spare drives are expected. [Tracking #: 552574]

Following a firmware upgrade, user was unable to restart the array (from the GUI nor the CLI) after

installing the Japanese language pack. [Tracking #: PSE006855] [CRITICAL]During a firmware update, while moving members into the maintenance pool, a

volume appeared to be deleted with no user action. [Tracking #s: 679493, 705682, 659222, 635094,

410289, 202488, and 630792]

Hardware

An issue occurred with Self-Encrypting Drives (SED) where the array incorrectly marked the spare

drive as failed and needing replacement. [Tracking #: 656506]

When using Host Integration Tools 4.5, after upgrading to firmware version 6.0.x, a controllerrestarted. [Tracking #s: 714079, 679484, 705740, 732366, 760900, 760896, and 764987]

On a PS6110 or PS4110 array, a vertical failover followed by a passive controller failure or rebootmay have caused the entire array to go offline.

[CRITICAL] While processing a preemptive drive removal request, RAID incorrectly attempted toprocess more than one drive failure request, and generated a failure event and possible outages.[Tracking #s: 606292, 650187, 689710, 689806, 724011, 695665, 720342, and 753459]

8/14/2019 6.0.6_Fix_List (1)

4/9

Copyright 2012-2013


Networking

A PS6110/PS4110 array with Data Center Bridging (DCB) enabled, in a correctly configured DCBnetwork, could take up to three or four minutes to fail over as a result of a network switch failure.

LDAP Active Directory user name and group name are now limited to 63 ASCII characters. Prior tothis release, ad-user/ad-group entries were limited to 26 characters.

When settings negotiated with a DCB switch that was incorrectly configured resulted in there beingno Ethernet flow control, the error message returned was not clear. Improved the GUI DCB flow

control warning message to provide better guidance on what switch changes are necessary.

Replication

Under certain conditions, a retry request involving the automatic balancing functionality and

replication resulted in an unexpected controller failover. [Tracking #: 738935]

User was unable to rerun replication. For current volumes, the process stopped with a status of in-

progress. For new volumes, the following error was displayed: Bad passwor d or part ner namespeci f i ed. Check t he spel l i ng and case of t he group name and password.

If user paused SyncRep for prolonged periods of time (more than 24 hours), even on a single volume,the array became unresponsive.

Under certain conditions, after promoting and demoting replicas, the following was displayed:Repl i ca set wi t h t he same name al r eady exi st s on t he par t ner . Remove i t on t he

par t ner. However, the phantom replica set could not be deleted. [Tracking #: 60746]

In certain conditions when using EqualLogic Storage Replication Adapter for VMware SiteRecovery Manager (SRM), a re-protect operation failed due to an orphan MIB entry.

When promoting a replica of a promoted replica, the volume ID of the second promoted replica didnot match the volume ID of the original volume. Instead it matched the actual volume ID of the first

promoted replica.

If user restarted MgmtExec on the source array while replication was in progress, a Kernel exceptionoccurred.

User Interface

The default value displayed in the web interface and Remote Setup Wizard was RAID 50, which isdifferent than the Dell-recommended RAID 6 policy.

The Add Pair operation was not permitted while a node was detached. The following message was

displayed: NAS cont r ol l er {0} i s det ached. You must att ach the cont r ol l er t o per f ormt hi s oper at i on.

Volumes

Intermittently, volume was getting stuck in "out of sync" state on switching to SyncAlternate pool

while one of the members of that pool was vacating. A snapshot of a volume with multihost access enabled displayed the following error if multiple hosts

attempted to simultaneously access the snapshot: I ni t i at or cannot access t hi s t ar getbecause an i SCSI sessi on f r omanother i ni t i ator al r eady exi st s and mul t i host access

i s not enabl ed f or t hi s t ar get . [Tracking #: 635738]

If sync-rep was enabled on template volumes that had "in use" pages, when user clicked on theFailover to SyncAlternate link, volume went out of sync.

8/14/2019 6.0.6_Fix_List (1)

5/9

Copyright 2012-2013


Other Issues

After enabling the EMhome functionality, the following INFO message was displayed in the event

log every two minutes: E- Mai l Home not i f i cat i on has been enabl ed. [Tracking #: 32985]

In arrays running versions 6.0.0 through 6.0.3 firmware, an unauthenticated user could havepotentially traversed the directory and accessed a file that contains encrypted password informationfor the Dell EqualLogic storage array. No user data was exposed by this vulnerability. A copy of theencrypted passwords does not offer a useful path to attacking the system. Users could not modify or

upload system files via this vulnerability. [Tracking #: 691433]

Issue Corrected in Version 6.0.2-H2

PS Series Firmware version 6.0.2-H2 includes all bug fixes that were incorporated into versions 6.0 orearlier.

An issue occurred with Self-Encrypting Drives (SED) where the array incorrectly marked the sparedrive as failed and needing replacement. [Tracking #: 656506]

A PS6110/PS4110 array with Data Center Bridging (DCB) enabled, in a correctly configured DCBnetwork, could take up to three or four minutes to fail over as a result of a network switch failure.

Issue Corrected in Version 6.0.2



After updating all members in a group to version 6.0.1 (from version 6.0.0), the GUI did not allow thelanguage packs to be installed on the members; the update wizard displayed the following: Member isnot compatible with selected language pack.

The firmware update script did not check suitability of all language kits before copying them. Thisresulted in missing language kits after the upgrade.

Hardware

Non-hardware drive errors on SATA drives led to preemptive drive removal. This issue impactedcontroller types 7, 8, and 10 only, which were shipped on PS4000E, PS6000E, PS6010E, PS6500Eand PS6510 arrays. [Tracking #s: 383341, 380686, 358418, 391004, 344726, 374075]

Under rare conditions on a PS-M4110 array, while the OS was booting or transitioning to active frompassive, a NULL pointer in the status page address caused a controller to restart out of sequence.

If an array with SED drives was not set up correctly, and a reboot was performed during the setupprocess, SED key sharing was disrupted with a failed health condition of sed_unresolved.

Replication

When synchronous replication was enabled, if user paused the synchronous replication for a long timewhile continuing to write to the volume, the secondary controller may have restarted.

When the following operation was performed, one or more volumes were changed to state

unavailable due to SyncRep. Once this state was reached, the volumes were stuck and could not bedeleted.

User added and removed volumes to an existing SyncRep collection, then a SyncRep switchoccurred.

8/14/2019 6.0.6_Fix_List (1)

6/9

Copyright 2012-2013


User then removed a volume from the SyncRep collection.

Other Issues

If a MAC address was not resolved, the packets were put in the ARP hold queue until a response tothe ARP request was generated.

An attempt to create a share directory with space in the name failed with the following error:" Char act er "" i s not al l owed.

Under rare circumstances, a drive mirror operation caused the array to become unresponsive.

If you were in the Replication section of the graphical user interface (GUI) and selected an individual

outbound replica container, the help button in the upper right corner of the screen did not contain thecorrect information.

An intra-group connection failure on a PS-M4110 in a DCB network caused volumes to go offline

and become inaccessible. After about 4 or 5 minutes, the connection resumed and volumes wereonline again.

Issue Corrected in Version 6.0.1-L1

Version 6.0.1-L1 contains some key diagnostic command enhancements that will provide supporttechnicians with additional data on the health of the drives in an array.

Issue Corrected in Version 6.0

PS Series Firmware version 6.0 includes all bug fixes that were incorporated into versions 5.2.5 or earlier.


The firmware update script did not trigger EMhome e-mails according to the email home policy.[Tracking #: 17940]

Users did not always pause in-progress replications during the firmware update process. Failure to

pause in-progress replications can lead to replications not being fully functional after the update.Code was modified to display a warning message, reminding users to pause all replications prior to afirmware update.

Users inadvertently initiated a restart before a CEMI firmware update completed. A restart during aCEMI firmware update can corrupt the flash card code on both controllers. The following warning isnow displayed informing users not to restart until the firmware update completes: A CEMI firmwareupdate is in progress. The array cannot be rebooted or halted in this state. Wait for the firmware update to complete, then

retry the operation. [Tracking #: 75210]

Under rare circumstances, a PS6x10 array would not restart after a disk drive replacement. [Tracking#s: 193506, 225473, 141950, 146411, 154775]

During a firmware upgrade, before users issued a restart command, I/O performance droppedsignificantly. [Tracking #: 23320]

Following a firmware update, the secondary controller in a PS61xx array erroneously reported apower supply fan failure every few hours. [Tracking #: 356374]

8/14/2019 6.0.6_Fix_List (1)

7/9

Copyright 2012-2013


Group Securi ty

The OpenSSH has been updated to OpenSSH_5.0 NetBSD_Secure_Shell-20080403+, OpenSSL0.9.9-dev 09 May 2008, sha2 fix (NetBSD-SA2009-012) applied in order to correct securityvulnerability issues. [Tracking #: 79575]

Initiator Connections

Disrupted iSCSI connections may not have been recovered immediately in groups with large numbers

of iSCSI initiator connections attempting to connect simultaneously.

Even though a dedicated management network port was defined, NTP traffic traveled over Ethernet

ports used for iSCSI traffic. [Tracking #: 122433]

Users were seeing excessive warnings for connection limits. [Tracking #: 121385]

Replication performance was degraded when using high-latency WAN links. [Tracking #: 334970]

In SAN environments using the Host Integration Tools, iSCSI connections to the group were droppedwhen an internal process unexpectedly restarted. [Tracking #s: 301700, 315785, 400833]

User Interface

The CLI commandaccount show act i ve

was corrected to display remote and local IP addresses. The GUI's Ethernet interface error status was not cleared until the member was rebooted. [Tracking

#s: 107065, 97610, 97465, 96996, 94501, 75048, 93895, 93517, 93135, 88161]

Users with read-only accounts could not change their own passwords. [Tracking #: 134062]

If a pool movement failed, the GUI continued to report the movement's status as "in-progress."

User was able to delete a member of a group that was offline, which caused a loss of data. Theprocess to delete an offline member of a group has been changed to require interaction with the DellEqualLogic customer support team in an effort to prevent data loss. [Tracking #: 151373]

In rare instances, after a firmware upgrade, grpadmin could not manage pools using the CLI. Thefollowing error was returned:Administrator grpadmin is not allowed access to pool defaults.[Tracking

#: 155201] In rare instances, a resource used by the network management process could be exhausted, causing

slow GUI response. [Tracking #s: 155970, 326406, 121237, 172614, 154843]

The Group Manager GUI allowed the "Thin Provisioned Volume" option to be set when cloning avolume that was not thin provisioned. The resulting clone was not thin provisioned, but was listed as

such in the GUI. This option is no longer available. You must first clone, and then thin provision avolume. [Tracking #s: 359992, 316424, 318855, 23490, 153934, 176714, 218976]

Using the GUI to perform a pool move and a change from normal to thin-provisioned volume at the

same time resulted in the volume having 0% volume reserve, and 0% for snap reserve. [Tracking#s: 176955, 298161, 191887]

The Group Manager GUI could not display information about a storage pool, and indefinitelydisplayed a Ret r i evi ng dat astatus message when merging pools or deleting them from the group.

In rare instances, the Group Manager GUI displayed snapshots associated with previous replication

operations that had been interrupted. [Tracking #s: 195934, 139176]

The Group Manger GUI erroneously displayed the following error message while running diagnostics

from the GUI while a CLI session was left open: Unknown er r or 13 r et urned by t he ser ver .[Tracking #s: 177329, 215508, 311220]

User could not log in to the Group Manager GUI. [Tracking #: 187466]

8/14/2019 6.0.6_Fix_List (1)

8/9

Copyright 2012-2013


The Group Manager GUI and CLI incorrectly indicated that the construction of a RAID set remainedat 0%, even after the operation had completed. [Tracking #: 332409]

Hardware

Under rare conditions, a read error on a disk caused it to go offline. [Tracking #s: 290764, 301337,433799, 263746]

Under rare conditions, the array panicked during a power cycle. When this occurred, the following

message was displayed: Pani c r ecover y f r omCPU0 wi t h reason ' added i nval i d SASaddress .[Tracking #: 336304]

The PS65xx arrays did not always reset the amber drive warning light after a bad disk drive wasreplaced. [Tracking #s: 271703, 270105, 271189, 267520, 290665, 300213, 307085, 323951]

Under certain conditions, a PS65x0 channel card failure did not fail over to the secondary channel

card. [Tracking #: 405829]

After a hardware fault, the PS6100 primary active controller sometimes hung and did not fail over.[Tracking #s: 429293, 391583, 411766, 483775]

Replication

If replication was paused and the size was changed on the primary group, a restart of the replicationfailed after a failback of the original volume from secondary to primary group. [Tracking #: 233412]

Volume description did not replicate with volume name. [Tracking #: 840561086]

If a VMware SRM volume was replicated and promoted, user could not connect to the replica.

Volumes

If a volume move operation failed due to a source pool space problem, it did not resume even whenthe free space issue was resolved. [Tracking #: 32356]

User could not cancel a volume move operation that was in-progress but not working correctly.[Tracking #: 327549]

Space balancing when free space was low was not always effective. I/O errors and/or volume

disconnects occurred when the pool approached 0 free space. [Tracking #: 150830, 162772, 150830,179068, 200269, 202159, 150830, 228707, 241119]

Volume replication became stuck in-progress while trying to replicate a volume containing lostblocks. [Tracking #: 401773]

If a reset command was invoked for an array, users were not provided with a warning of what data

was to be destroyed (the array name, the IP addresses, and any volumes on its member). Note that

Dell strongly recommends that users not reset a running array. Use the del et e member commandinstead, which moves data from the array to other arrays and automatically resets the array. [Tracking

#: 249528]

Using CLI, users could create a volume using 0% thin-growth-max, which is below the allowedminimum of 10%. [Tracking #: 268307]

When the array attempted to automatically balance a 30MB volume across two members, it failed.Volumes larger than 30MB were not affected. [Tracking #: 294635]

In rare circumstances, volumes went offline during a member update. When this occurred,notifications were generated, but not sent to the user. [Tracking #: 356009]

In rare circumstances, during inter-array network problems with multiple volume moves, the GUIbecame unresponsive and volume moves could not continue. [Tracking #: 375991]

8/14/2019 6.0.6_Fix_List (1)

9/9

Copyright 2012-2013


Under certain instances, volumes marked with lost blocks, but still online, did not allow new iSCSIinitiator logins after the lost blocks were cleared. [Tracking #: 378045]

Free space balancing sometimes did not occur after a firmware update. [Tracking #: 338059]

During firmware upgrade procedures, while migrating members into a maintenance pool,

acknowledgments on cancelling tasks were not requested from participating members. This resultedin overlapping page movement tasks and ultimately in unexpected controller failovers. [Tracking #:416721]

Other Issues

Under a rare condition, such as an extremely heavy workload on the group, or an extremely poornetwork environment, the iSCSI connection count could get out of sync. [Tracking #: 80616]

The UNIX Secure Copy (SCP) command failed to transfer large segments of diagnostics. [Tracking#: 86317]

Free space and provisioning warning messages were reported too often during normal arrayoperations. [Tracking #s: 160843, 78575, 295963, 348799]

When applying a config.cli (from the CLI save- conf i gcommand) to a fresh configuration, the

following error was generated: Er r or : Bad command.

When a volume was thin provisioned, then immediately moved to another pool, the volumessnapshot reserve showed 0%. [Tracking #: 176955]

A single-member group became unresponsive when communications with a RADIUS server weredisrupted. [Tracking #: 211274]

The crypto-legacy-protocols were being saved incorrectly with save- conf i g.

A network resource issue occurred during times of severe ARP flooding. [Tracking #: 191806]

When a dedicated management port was enabled, bringing down eth0 caused sessions to disconnecton the management network. [Tracking #: 347770]

In certain situations, volumes which had lost blocks cleared in the past were taken offline and

incorrectly marked as having lost blocks. [Tracking #s: 348142, 217145, 373054, 442742] A timing issue caused RADIUS authentication to fail when there was a large number of volumes on

the SAN. [Tracking #: 343065]

The Remote Setup Wizard displayed incorrect serial number for PS4100 and PS6100 arrays.

Documents

6.0.6_Fix_List (1)