|
|
·
Microsoft Windows Server
2012 (x64 and x86,
Standard and Datacenter editions, and Windows Server 2012 Essentials)
·
Microsoft Windows Server
2008 (IA32 and x64, Standard,
Enterprise, and Datacenter editions)
·
Microsoft Windows Server
2008 R2 (x64, Standard,
Enterprise, and Datacenter editions)
·
Microsoft Windows Server
2008 and 2008 R2 x64
Hyper-V
·
Red Hat Enterprise Linux
5.7, 5.8, 6.1, 6.2 (IA32, x64)
·
SuSE Linux Enterprise Server 10.4 and 11 SP2 (x64 and IA32)
·
VMware ESX 4.0, 4.1, and 5.0
·
Apple OS X (Snow Leopard
10.6 and 10.7)
When Microsoft MPIO is used with this release of
firmware for Pro 5000 series storage arrays, some setting changes are
advisable:
·
Apply the following
Microsoft Windows time-out values (refer to Microsoft documentation for
information about how to make registry changes):
·
Disk Timeout value = 30
·
Path verify enabled =
False
·
Path verify period = 60
·
Retry Count = 10
·
Retry Interval = 5
·
PDO Timeout = 120
·
UseCustomPathRecoveryInterval = 1
·
PathRecoveryInterval = 60
·
When MPIO
is running on Windows Server 2008 R2 SP1, apply the following Microsoft hot-fixes:
·
KB2460971 - MPIO failover fails on a computer that is
running Windows Server 2008 R2.
·
KB2670762 - MPIO does not log path failure events in the
event log on a Windows Server 2008 R2-based computer.
·
KB2614956 - Windows 7 or Windows Server 2008 R2 crashes
when you use Mpclaim.exe to claim a storage device.
This release of firmware for Pro 5000 series storage
arrays has the following limitations:
·
The IPv6
protocol is not supported on the management port for this release. Use IPv4 instead.
·
SMI-S is not supported in this release.
·
The documentation
indicates that a maximum of ten chassis is supported. For this release a
maximum of six chassis is supported.
The following fixes were
incorporated in CS100P012 firmware:
· Fixed a bug with reserving cache elements that could lead to a data corruption.
·
Fixed an issue
where the CLI clear cache command fails to execute when only one controller is up.
The following fixes were
incorporated in CS100P011 firmware:
·
Fixed the Broadcom (LSI) Backend SAS Chip freeze
issue.
The following fixes were
incorporated in CS100P010 firmware:
·
Fixed a corner-case data unavailability issue caused
by a snap pool going offline after failover.
·
Fixed an https webserver hang.
·
Fixed various security issues.
·
Fixed a data unavailability issue caused by a page
fault with ESX hosts.
·
Fixed a corner-case data unavailability issue caused
by not updating the port WWNs during replications.
·
Fixed a corner-case data loss issue when a disk
failed in a RAID-1 configuration with replications.
·
Fixed a corner-case data loss issue caused by
incorrect marking of a pool as faulted when the pool went offline.
·
Improved health reporting for unhealthy pools.
·
Fixed an issue where auto-negotiation for controller
Ethernet ports is disabled if the auto-negotiation parameter is not specified
in the set network-parameters command.
·
Fixed a corner case data unavailability issue caused
by a controller crash after failover.
·
Fixed a data unavailability issue caused by pages
being freed during a virtual disk-group drain operation.
·
Fixed a data unavailability issue after an unsafe trust
operation.
·
Fixed a crash after an unsafe trust operation.
·
Fixed a controller hang during shutdown with ESX hosts.
The following enhancements were incorporated in CS100P009 firmware:
·
Enabled auto-unkill for
failover reason "PCIE link fault”.
The following fixes were
incorporated in CS100P009 firmware:
·
Fixed an issue where failover did not succeed.
·
Fixed an issue where failback took longer than 60
seconds.
·
Upgraded to OpenSSL v1.0.2h
and added security fix.
·
Enabled users to install their own SSL certificates
even if OpenSSL verification fails.
·
Improved error handling when a custom OpenSSL
certificate is used.
·
Prevented auto-unkill when
the partner controller is not installed.
·
Fixed an issue where a controller could hang due to
a hard drive medium error.
·
Enabled disk-group background utilities to run after
attempting to remove a disk group from a pool failed due to lack of space to
drain data and drain was aborted.
·
Fixed an issue with VMware where ATS aborts were
incorrectly handled and resulted in a crash.
·
Fixed an issue that allowed reconstruction of a
quarantined RAID-6 disk group to succeed, causing a controller crash, when
instead the reconstruction utility should have aborted.
·
Dequarantine event 173 now indicates the
status (health) of the dequarantined disk group and
whether the dequarantine mode was automatic or
manual.
·
Fixed an issue where the Management Controller
became unresponsive while deleting storage when storage-pool components were
missing from a storage pool.
The following enhancements were incorporated in CS100P008 firmware:
·
Upgraded Fiber Channel
Patch Libs.
The following fixes were
incorporated in CS100P008 firmware:
·
Changed code to initiate
full reconstruction, instead of quick rebuild, of disk group when pool health is
in offline state.
·
Prevented hangs or
crashes due to linked list corruption in paged storage code when a Storage
Controller runs out of more than one resource at a time.
·
Fixed a failover issue where
the surviving controller would hang after losing the heartbeat of the partner
controller.
·
Prevented manual dequarantine of a virtual disk group, which can result in
data loss or corruption.
·
Fixed an issue where
trying to remove all storage pools failed with an insufficient-space error.
·
Eliminated some
erroneous error messages that could be stored in the controller debug log when
I/O is performed to pools larger than 12.5 TiB.
·
Fixed a resource leak in
the special case where an I/O straddled a 4 MiB page boundary and certain other specific internal
conditions occurred, which would gradually reduce I/O performance and
eventually cause the controller to appear to hang from the host's standpoint.
·
Updated OpenSSL and OpenSSH versions.
·
Security fixes and dynamic
SSL certificate feature.
·
Fixed cases where paged
storage metadata could get out of sync and result in corruption of pool
metadata.
·
Provided a way for
support personnel to resolve situations in which a virtual pool cannot be
deleted by normal means.
·
Prevented an internal
data-lock issue that occurred when performing tier migration of paged storage.
·
Improved internal
mechanism for updating the health of a storage pool, and prevented utilities
from running on a pool in an offline state.
The following fixes were
incorporated in CS100P007 firmware:
·
Fix xcopy
handling of DMA errors.
·
Fix POODLE
vulnerability.
·
Fixed buffer overflow
exception caused by CLI show snapshots
command.
·
Vdisk owned by JBOD
enclosure went to a quarantined state after an expansion cable pull when other
controller is already killed.
·
Fixed issues with xcopy abort handling.
·
Fixed an inability to
create SNMP V3 User by specifying only the privacy
type and not the authentication type.
·
If the network port for A controller A is down, traps will be sent from controller
B.
·
Fixed an issue where
media error recovery during a copyback operation
could result in a single or dual controller crash.
·
Changed the remote command capability from
"monitor" to "manage."
·
Added a check and error
message if the configuration contains a storage pool.
·
Fixed an issue with
intermittent replication failures.
The following
enhancements were incorporated in CS100P004 firmware:
·
Edited the RAIDar
"Managing users" help topic to remove text indicating that user names
could include a space.
·
Added Management Controller CLI support to set partner
controller Ethernet parameters link speed, duplex mode and auto-negotiation.
·
SMC should have
replication information tab on volume group.
·
Add Storage Controller support
for SSD component auto-drain enable/disable.
·
CLI help changes for
pinning a volume to a tier.
·
Added support for SCSI
Thin Provisioning threshold checking.
·
Added auto-drain to CLI
online help for set/show storage-pools.
·
Disk Group Draining is
now user-configurable.
The following fixes were
incorporated in CS100P004 firmware:
·
Heartbleed security fix and updated SSL certificates.
·
Reduce prints for I/O
path.
·
Fixed a data corruption
problem and modified paged storage resource queuing.
·
Prevented a system crash
while creating snapshots.
·
Corrected an issue
mapping new volumes using groups.
·
Fixed erroneous implicit
logout issues.
·
Fixed a controller hang
issue during deletion of a replication image or snapshot on a secondary volume.
·
Fixed a cache crash that
was due to an unhandled replication error.
·
Fixed clear controller
cache stats so that read/write histogram data is also reset.
·
The scheduler was not
honoring the Time Constraint and Date Constraint of the schedule policy.
·
Fixed restore users and
restore defaults.
·
Fixed a cache flush hang
during snapshot creation.
·
Now displays the correct
storage pool size.
·
10 Gb/s
iSCSI system dropped connections intermittently due to timeouts on the wire.
·
Needed the ability to
pin a volume to a tier using the CLI and WBI.
·
Created a setting to
disable mouse-over (hover help) popups.
·
Fixed a controller crash
caused by a locking issue while acquiring a volumedataset
lock.
·
Fixed an issue with PGR
where meta records could be zeroed for paged volumes.
·
Fixed an issue where
changing email notifications from controller A caused controller B's port0 link to go down and then up.
·
Upgraded LSI 6 Gb/s SAS Libs.
·
Fixed a page fault in
iSCSI probes.
·
Fixed a drive loss (105
sec timeout) when updating firmware.
·
Fixed a data corruption
issue when a controller shut down for a firmware upgrade while the remaining
controller had stale data.
·
Fixed an erroneous
implicit logout issue.
·
Fixed a PGR issue where meta records could be zeroed.
·
Fixed an issue where a
global spare drive went to left-over status when one drive was pulled from each
vdisk while I/O was running.
The following
enhancements were incorporated in CS100P003 firmware:
·
Increased boot flush
speed measurement from 32 MB to 320 MB.
The following fixes were
incorporated in CS100P003 firmware:
·
Raised the CacheEccCorrectableCountThreshold to 30.
·
Now uses the correct (T10 SBC-3) status values for the Get LBA status command.
·
Fixed a crash when
adding a component to a storage pool.
·
Fixed parity errors which
were detected after shutdown and power removal of an array while rebuilds were
in progress.
·
Improved rebalance
within a tier by speeding it up significantly.
·
Fixed an issue where SSD SAS drives were reported as mechanical SAS drives.
·
Prevented periodic CompactFlash
checks from accessing raw ATA registers without a device lock.
·
Prevented possible
unreadable BLPT (Bottom Level Page Table) /TLPT (Top Level Page Table) entries on disk due to stale vuSN information.
·
Prevented a page fault
in rebalance when components became full.
·
Moved the CLI show storage-pool-components command to
manage-level.
The following
enhancements were incorporated in CS100P002-03
firmware:
·
Added support for the
customization toolkit.
The following fixes were
incorporated in CS100P002-03 firmware:
·
ATS errors in logs due
to not initializing fields on I/O completions if ATS command aborts.
·
Missed partner portal
causes synchronization deadlock.
·
Page fault in link down
with timeout scenario.
·
Both controllers crash due
to page faults during moderate data move load.
·
Crash when changing host
channel configuration to enable or disable jumbo frames while running I/O.
·
Hot pages can't move to SSD because coldest SSD pages are
not cold enough.
·
Remote replication fails
when reversing the replication set because the replication set loses a volume
name.
·
ATS commands do not work
if forwarded.
·
CLI map command fails when changing the mappings of a LUN from
read-write to read-only.
·
IP address errors on
iSCSI controllers.
·
Controller crashes when
an ATS command is aborted.
·
Both controllers crash
due to aborting ATS commands.
·
Intermittent hang when
the CLI unmap
command attempt to free up storage space.
·
Tiering sometimes incorrectly halts moving
pages or moves pages too slowly.
·
Windows 2012 does not
issue unmap commands to paged storage volumes with
deleted files.
·
Controller A crashes
during remote replication set creation.
·
Resource leak in portal
connections.
·
When drive enclosures
are disconnected or power cycled, I/O is allowed to restart without an updated
page allocation map.
·
Controller B kills
controller A during Partner Firmware Update.
·
Storage Controller hangs after running I/O from VMware
with ATS disabled from host.
The following sections discuss installing the firmware:
·
Installation notes and best
practices
·
Installation
troubleshooting
·
Installation instructions using Storage Management Console
·
Updating expansion module firmware using Storage Management Console
|
WARNING!
Do
not power cycle or restart devices during a firmware update. If the update is
interrupted or there is a power failure, the module could become inoperative.
If this occurs, contact technical support. The module may need to be returned
to the factory for reprogramming. |
|
|
CAUTION:
Before
upgrading firmware, ensure that the system is stable and is not being reconfigured
or changed in any way. If changes are in progress, monitor them and wait
until they are completed before proceeding with the upgrade. |
|
|
NOTE: To install this
firmware, you must download the firmware package from the Cloud Systems Group support site, https://www.seagate.com/support/by-product/clustered-file-systems/
and
save the file to your local filesystem. Ensure that FTP and telnet are
enabled. |
|
·
As with any firmware
upgrade, it is a recommended best practice to ensure that you have a full
backup prior to the upgrade.
·
When planning for a
firmware upgrade, schedule an appropriate time to perform an online upgrade.
o For single domain systems, I/O must be halted.
o For dual domain systems, because the online firmware upgrade is performed while
host I/Os are being processed, I/O load can impact
the upgrade process. Select a period of low I/O activity to ensure the upgrade
completes as quickly as possible and avoid disruptions to hosts and
applications due to timeouts.
·
When planning for a firmware
upgrade, allow sufficient time for the update.
o In single-controller systems, it takes approximately 10 minutes for the
firmware to load and for the automatic controller restart to complete.
o In dual-controller systems, the second controller usually takes an
additional 20 minutes to update, but may take as long as one hour.
·
During the installation
process, monitor the system to determine update status and know when the update
is complete.
·
After the installation
process is complete and all controllers have automatically restarted, verify
system status in Storage Management Console or the CLI and confirm that the new
firmware version is displayed as running on all controllers.
·
Updating controller
firmware may result in new event messages that are not described in the
documentation. For current event descriptions and applicable recommended
actions, see event text displayed in the Storage Management Consoler or RAIDar
and in the CLI.
If you experience
issues during the installation process, do the following:
1. When viewing system version information in the Storage Management Console
System Overview panel, if an hour has elapsed and the components do not show
that they were updated to the new firmware version, refresh the web browser. If
version information is still incorrect, proceed to the next troubleshooting
step.
2. If version information does not show that the new firmware has been
installed, even after refreshing the browser, restart all system controllers.
For example, in the CLI, enter the restart mc both
command. After the controllers have restarted, one of three things will happen:
·
Updated system version
information is displayed and the new firmware version shows that it was installed.
·
The Partner Firmware
Update process will automatically begin and will install the firmware on the
second controller. When complete, the versions should be correct.
·
System version
information is still incorrect. If system version information is still incorrect,
proceed to the next troubleshooting step.
3. Verify that all system controllers are operating properly. For example, in
the CLI, enter the show disks command
and read the display to confirm that the information displayed is correct.
·
If the show
disks command fails to display the disks correctly,
communications within the controller have failed. To reestablish communication,
cycle power on the system and repeat the show disks
command. (Do not restart the controllers; cycle power on the controller enclosure.)
·
If the show
disks command from all controllers is successful, perform the
firmware update process again.
|
NOTE: It takes approximately 10 minutes for the firmware to
load and for the automatic restart to complete. Progress messages are
displayed in the FTP interface during that time. Wait for the progress
messages to specify that the firmware load has completed. If the system Partner Firmware Update
(PFU) option is enabled, allow an additional 20
minutes for the partner controller to be updated. No messages are displayed
in the FTP interface during Partner Firmware Update. |
|
A controller enclosure can contain one or two controller modules. In a
dual-controller system, both controllers should run the same firmware version.
Storage systems in a replication set must run the same firmware version. You
can update the firmware in each controller module by loading a firmware file
obtained from the enclosure vendor.
If you have a dual-controller system and the Partner Firmware Update option
is enabled, when you update ne controller the system automatically updates the
partner controller. If Partner Firmware Update is disabled, after updating
firmware on one controller you must log into the partner controller's IP
address and perform this firmware update on that controller also.
For best results, the storage system should be in a healthy state before
starting firmware update.
Firmware update is supported from any of the following versions: CS100R008, CS100P009, CS100P010, CS100P011.
To update controller-module firmware:
1. Obtain the appropriate firmware file and download it to your computer or
network.
2. If the storage system has a single controller, stop I/O to the system
before you start the firmware update.
3. Restart the Management Controller in the controller to be updated; or if Partner
Firmware Update is enabled, restart the MCs in both controllers.
·
In the banner click the
system panel and select Update Firmware.
·
In the System topic
select Action > Update Firmware.
The Update Firmware panel opens. The Update Controller Modules tab shows
versions of firmware components that are currently installed in each
controller.
5. Click Choose File and select the firmware file to install.
6. If you have a dual-controller system and want firmware to be automatically
updated in both controllers, under Partner Firmware Upgrade select the Enabled
check box and click Set. (Partner Firmware Update is enabled by default.)
Otherwise, if Partner Firmware Update is disabled, after updating firmware on
one controller you must log into the partner controller and perform this
firmware update on that controller also.
7. Click OK. A panel shows firmware-update progress.
The process starts by validating the firmware file:
·
If the file is invalid,
verify that you specified the correct firmware file. If you did, try
downloading it again from the source location.
·
If the file is valid,
the process continues.
Firmware update typically takes 10 minutes for a controller with current
CPLD firmware, or 20 minutes for a controller with downlevel
CPLD firmware. If the controller enclosure has connected enclosures, allow
additional time for each expansion module's enclosure management processor (EMP) to be updated. This typically takes 3 minutes for each
EMP in an expansion enclosure.
If the Storage Controller cannot be updated, the update operation is
cancelled. Verify that you specified the correct firmware file and repeat the
update. If this problem persists, contact technical support.
When firmware update on the local controller is complete, users are
automatically signed out and the Management Controller restarts.
Until the restart is complete, sign-in pages say that “the system is currently
unavailable”.
When this message is cleared, you may sign in again.
If Partner Firmware Update is enabled, allow 10 to 20 minutes for the
partner controller to be updated.
8. Clear your web browser cache, then sign in to
Storage Management Console. If Partner Firmware Update is running on the
controller you sign in to, a panel shows Partner Firmware Update progress and
prevents you from performing other tasks until Partner Firmware Update is
complete.
An expansion enclosure can contain one or two expansion modules. Each
expansion module contains an enclosure management processor (EMP). All modules of the same model should run the same
firmware version.
Expansion-module firmware is updated in either of two ways:
·
When you update
controller-module firmware, all expansion modules are automatically updated to
a compatible firmware version.
·
You can update the
firmware in each expansion module by loading a firmware file obtained from the
enclosure vendor.
To update expansion module firmware:
1. Obtain the appropriate firmware file and download it to your computer or
network.
2. If the storage system has a single controller, stop I/O to the system
before you start the firmware update.
3. Do one of the following:
·
In the banner click the
system panel and select Update Firmware.
·
In the System topic
select Action > Update Firmware.
The Update Firmware panel opens.
4. Select the Update Expansion Modules tab. This tab shows information about
each expansion module in the system.
5. Select the expansion modules to update.
6. Click Choose File and select the firmware file to install.
7. Click OK. Messages show firmware-update progress.
It typically takes 3 minutes to update each EMP
in an expansion enclosure. Wait for a message which indicates that “the code load has completed”.
Verify that each updated expansion module has the new firmware version.
|
NOTE: It takes
approximately 10 minutes for the firmware to load and for the automatic
restart to complete. Progress messages are displayed in the FTP interface
during that time. Wait for the progress messages to specify that the firmware
load has completed. If the system Partner Firmware Update
option is enabled, allow an additional 20 minutes for the partner controller
to be updated. No messages are displayed in the FTP interface during the Partner Firmware Update. |
|
A controller enclosure
can contain one or two controller modules. In a dual-controller system, both
controllers should run the same firmware version. Storage systems in a
replication set must run the same firmware version. You can update the firmware
in each controller module by loading a firmware file obtained from the
enclosure vendor.
If you have a
dual-controller system and the Partner Firmware Update option is enabled, when
you update one controller the system automatically updates the partner
controller. If Partner Firmware Update is disabled, after updating firmware on
one controller you must log into the partner controller's IP address and
perform this firmware update on that controller also.
For best results, the
storage system should be in a healthy state before starting firmware update.
Firmware update via FTP
is supported from any of the following versions: CS100R008,
CS100P009, CS100P010, CS100P011.
To update
controller-module firmware:
1. Obtain the appropriate firmware file and download it to your computer or
network.
2. Place the downloaded firmware package in a temporary directory.
3.
Locate the firmware file
in the extracted folder.
4. In Storage Management Console, prepare to use FTP:
a. Determine the network-port IP addresses of the system controllers.
b. Verify that the system FTP service is enabled.
c. Verify that the user you will log in as has permission to use the FTP
interface and has manage access rights.
5. In single-domain environments, halt I/O to vdisks before starting the
firmware update.
6.
Restart the Management
Controller in the controller to be updated; or if Partner Firmware Update is
enabled, then restart the Management Controllers in both controllers.
7. Open a command prompt (Windows) or a terminal window (UNIX), and navigate to
the directory containing the firmware file to load.
a. Enter a command using the following syntax: ftp
<controller-network-address>.
b. Log in as a FTP user (user = ftp, password = flash).
c. Enter a command using the following syntax: put
<firmware-file> flash.
8. If needed, repeat these steps to load the firmware on additional modules.
If the Storage Controller cannot be
updated, the update operation is cancelled. If the FTP prompt does not return,
quit the FTP session and log in again. Verify that you specified the correct
firmware file and repeat the update. If this problem
persists, contact technical support.
When firmware update on the local
controller is complete, the message “Operation Complete” is printed, the FTP session returns to the ftp> prompt, and the FTP
session to the local Management Controller is
closed.
10. Clear your web browser's cache and then sign in to Storage Management
Console. In the Storage Management Console display, verify that the proper
firmware version appears for each module. If Partner Firmware Update is running
on the controller you sign in to, a dialog box shows Partner Firmware Update progress
and prevents you from performing other tasks until Partner Firmware Update is
complete.
|
NOTE: If you attempt to
load an incompatible firmware version, the message “ |
|
|
NOTE: If you are using a
Windows FTP client, during firmware update a client-side FTP application
issue can cause the FTP session to be aborted. If this issue persists, try
using Storage Management Console to perform the update, use another client,
or use another FTP application. |
|
|
NOTE: After firmware
update has completed on both controllers, if the correct version does not
appear for a component or if the system health is Degraded and the health reason
indicates that the firmware version is incorrect, verify that you specified
the correct firmware file and repeat the update. If this problem persists,
contact technical support. |
|
..Supersedes history
|
|
Firmware version |
Release date |
|
CS100P011 |
October 2017 |
|
CS100P010 |
August 2017 |
|
CS100P009 |
September 2016 |
|
CS100P008 |
April 2016 |
|
CS100P007 |
January 2016 |
|
CS100P004 |
July 2014 |
|
CS100P003 |
December 2013 |
|
CS100P002-03 |
June 2013 |
|
CS100R004 |
March 2013 |
..Effective date
|
March 2018
|
|
Rev. A |
Part number: |