RIVERBED PRODUCT RELEASE NOTES

PRODUCT: STEELFUSION EDGE

RELEASE DATE: 28-JUNE-2018
VERSION: 5.1.2

CONTENTS
1) About SteelFusion edge
2) Fixed Problems
3) Known Issues
4) SteelCentral Controller for SteelHead Compatibility
5) Upgrading Version 5.1.2
6) Hardware and Software Requirements
7) Contacting Riverbed Support

1) ABOUT STEELFUSION EDGE

This release of SteelFusion Edge 5.1.2 software contains RiOS 9.6.2 (Release Notes),
BlockStream 5.1.2(Release Notes ), and ESXi 5.5p9 bundled (Release Notes).
This supports ESXi 5.5 U3a ( Release Notes), 6.0 Express Patch 4 and 6.0 Patch 3
(6.0.02.43.4192238) (Release Note).

2) FIXED PROBLEMS
Problems fixed in version 5.1.2
• 290956 An enhancement has been added to SteelFusion Core to periodically reset data
connections to the Edges. In the event that a SteelHead restart is performed, and the
data connections become unoptimized, this periodic reset will ensure that optimization
automatically resumes within 24 hours.
• 293051 With Release 4.6.2; SteelFusion Core enables the iSCSI Serial writes by default
for the following specific iSCSI Targets (Storage Arrays)
 Microsoft StorSimple: "Untagged" Serial writes
 Amazon Storage Gateway (ASG): "Untagged" Serial writes
 HPE 3PAR: "Simple" Serial writes
 This update ensures the SteelFusion Core iSCSI initiator serializes the writes to the said
iSCSI targets and hence the write order fidelity is preserved.
This update is applicable for both Fresh installations and Upgrades of 4.6.2 release.
• 293215 In rare cases, if a VMFS volume attached to a SteelFusion Core contains
corrupted metadata, the SteelFusion Core storage service may crash when the prefetch
module tries to read that metadata.
The SteelFusion Core storage service will not crash if the prefetch module reads VMFS
metadata that was corrupted in such a way as to cause VMDK metadata to go missing or
to be referenced multiple times. Instead, it will log one or both of the following warning
messages:
"More than one set of meta blocks for resident file: " <file name>
"Could not read metadata(from fdc.sf) for file:" <file name>
• 293487 iSCSI write serialization has been enabled on the SteelFusion Core by default for
all storage arrays mentioned in the SteelFusion 5.5 Interoperability Guide.
Problems fixed in version 5.1.1
• 287522 Incorrect usage of the NetApp API that helps iterate over the LUNs when given a
search criteria is leading to backup failure. If more than 20 LUNs match this criteria, the
API should be invoked multiple times. NetApp uses two storage array modes: C-mode
and 7mode. For C-mode, the fix is to properly use the NetApp API lun-get-iter to find the
required LUN. For 7-mode, there is an equivalent API (lun-list-info) to find the LUN;
however, a fix is pending in that code path. 7-mode customers can expect that fix in a
future release of SteelFusion. To work around this issue, create only one LUN per
flexible volume in the NetApp backend.
Problems fixed in version 5.1.0
• 206651 The Turbo Boot and Branch Recovery plugins are incompatible with each other
and cannot be used at the same time.
• 233005 Fixed an issue where ESXi upgrade and downgrade messages were not visible at
default logging level. ESXi upgrade/downgrade messages are now displayed at NOTICE
(default) level.
• 270951 Fixed an issue where Window server data-protection no longer fails in a
SteelFusion Edge HA setup after a fail-over event.
• 271015 Fixed an issue where the framework for scheduling a snapshot operation script
for an unsupported backend storage array fails to schedule a snapshot deletion with the
correct time. This failure is because of a 32-bit integer overflow, causing the Edge to
repeatedly request the snapshot deletion. With this fix, the framework for scheduling a
snapshot operation script has been extended to store the timestamp in a 64-bit integer,
preventing integer overflow in the near future. Currently, with the 32-bit integer, this
issue occurs every 49th day, at which point you must restart the 'dc' process in Core
using the "pm process dc restart" CLI command. Restarting the 'dc' process will reset the
timestamp and schedule snapshot operations using the correct time for the next 49
days.
2
• 272320 Switching from the FusionSync primary site to the secondary site may fail with a
"Core-HA is forming" error. Restart the core process on the secondary site, wait for
HAforming process to complete, and then retry.
• 278538 Fixed an issue to add validation for Windows usernames, which accepts a
username with the format 'Domain\username'. ESXi username validation has been
added as well.
• 278955 Cores in a high-availability configuration can be connected to storage arrays that
present LUNs as new iSCSI targets (such as Dell EqualLogic, Nutanix, and Nimble). In this
type of configuration, when you create a new LUN on the array and add it to a Core,
upon failover, the LUN on the failed Core will appear as "Degraded" on the active peer
Core. To work around this issue, choose Configure > Storage Array: iSCSI Initiator/MPIO
in the SteelFusion Core Management Console of the peer Core. Expand the iSCSI portal
and click Update iSCSI Portal.
• 278993 Fixed an issue to support the backup for a VM that has virtual hard disks created
from Edge local/non-Riverbed LUNs/Exports with these conditions:
If a VM has Edge local/non-Riverbed LUNs/Exports, all virtual hard disks created from
those LUNs/Exports should be marked as ‘Independent.’ Steps to do so using vSphere
client are as follows:
While creating a new virtual hard disk, check the Independent flag under Advanced
Options.
For an existing virtual hard disk:
Right-click the VM name, and go to Edit Settings
Under the Hardware tab, select the virtual hard disk created from Edge
local/nonRiverbed LUN/Export.
Check the Independent flag.
The virtual hard disk hosting the OS/VMX should not be created from an Edge
local/nonRiverbed LUN/Export.
• 279969 Fixed a problem in SteelFusion Core HA configurations, where performing a
rolling upgrade to 5.0, there is a temporary disruption in service to the core running a
pre-5.0 release. This issue only occurs during rolling upgrades when the cores in the HA
configuration are running 5.0 or earlier. After both the core HA nodes are upgraded to
5.0, the core will no longer crash.
• 280105 Fixed an issue where backup operations were failing while issuing requests to
NetApp storage due to timeout or connection errors. In case of timeout or transmission
errors, the storage operation is retried three times with a delay of 30 seconds.
• 280259 Fixed an issue where the Core might restart when it receives an Edge write
while the initialization is delayed. This issue was caused by slow access to the Journal
LUN. When FusionSync is configured and the Core process on the primary site is starting
up in a “fractured” state, slow access to the Journal LUN can delay initialization. On rare
3
 occasions, a Core in this situation may restart when it receives an Edge write. Now the
system does not write to the Journal LUN until it is ready.

• 283308 Fixed an issue in the client code to handle the failure scenario during reconnect
to a Windows server. Some services, such as Windows proxy operation, were disrupted
on a client that communicates to a Windows server on SteelFusion Edge or Core
appliances.
• 283350 The CLI command “show stats storage” returns an internal error on the standby
edge in Edge HA: "Command is not permitted on standby edge."
• 283493 Fixed an issue where crashes were observed due to prefetch thread timeouts.
The prefetch thread will now stack trace if the read hits the delay of 1 minute.
• 285079 Fixed an issue where the core 'dc' process crashed when three events (online,
resize/repartition, offline) on a LUN take place quickly. The root cause of the crash, a
sanitychecking assert condition, is fixed.
• 285213 Fixed an issue so that the system now displays the actual reason for why the
LUN resize failed.
• 285719 Fixed an issue where email notification for alarms were sent even though the
alarm was disabled.

3) KNOWN ISSUES
• 288095 The CLI and UI show “Unknown― in certain fields if TLS1.0 is disabled in
ESXi on the EX appliance. We recommend not disabling TLS1.0 in ESXi on EX appliance.
We also recommend that customers do not disable TLS1.0 in vCenter if ESXi is managed
by vCenter. Please use steps mentioned in
https://docs.vmware.com/en/VMwarevSphere/6.0/com.vmware.vsphere.security.doc/
GUI D-82028A21-8AB5-4E2E-90B8A01D1FAD77B1.html to re-enable TLS1.0.
• 288242 Backup and snapshot operations may fail if the customer disables TLS1.0 on the
proxy ESXi host. We recommend not disabling TLS1.0 in Proxy ESXi host. Please use
steps mentioned in
https://docs.vmware.com/en/VMwarevSphere/6.0/com.vmware.vsphere.security.doc/
GUI D-82028A21-8AB5-4E2E-90B8A01D1FAD77B1.html to re-enable TLS1.0.
• 288245 Some of the VSP operations will fail when TLS1.0 is disabled in ESXi on the EX
appliance. We recommend not disabling TLS1.0 in ESXi on EX appliance. We also
recommend that customers do not disable TLS1.0 in vCenter if ESXi is managed by
vCenter. Please use steps mentioned in
https://docs.vmware.com/en/VMwarevSphere/6.0/com.vmware.vsphere.security.doc/
GUI D-82028A21-8AB5-4E2E-90B8A01D1FAD77B1.html to re-enable TLS1.0.

4
4) STEELCENTRAL CONTROLLER FOR STEELHEAD
COMPATIBILITY
If you use SteelCentral Controller for SteelHead (SCC) to manage your appliances, you must
upgrade SCC to a specific version before you upgrade your appliances to this software
version. Failure to do so will prevent communication between SCC and your appliances.

For information on SCC compatibility with SteelHead, SteelHead CX, SteelHead EX,
Interceptor, Mobile Controller, and SteelFusion appliances, see the SteelCentral Controller
for SteelHead Installation Guide and Knowledge Base Article S15464 for complete details.

5) UPGRADING VERSION 5.1.2

Please review the SteelFusion Edge Installation and Configuration Guide for information on
upgrading SteelFusion Edge software version on SteelFusion Edge appliances.

6) HARWARDE AND SOFTWARE REQUIREMENTS

Please review the SteelFusion Edge Installation and Configuration Guide for information on
upgrading SteelFusion Edge software version on SteelFusion Edge appliances.

7) CONTACTING RIVERBED SUPPORT

Visit the Riverbed Support site to download software updates and documentation, browse
our library of Knowledge Base articles and manage your account. To open a support case,
choose one of the options below.

Phone
Riverbed provides phone support at 1-888-RVBD-TAC (1-888-782-3822). Outside the U.S.
dial +1 415 247 7381.

Online
You can also submit a support case online

Email
Send email to support@riverbed.com. A member of the support team will reply as quickly
as possible.

©2018 Riverbed Technology. All rights reserved. Riverbed and any Riverbed product or service name or logo used herein are
trademarks of Riverbed Technology. All other trademarks used herein belong to their respective owners. The trademarks and
logos displayed herein may not be used without the prior written consent of Riverbed Technology or their respective owners.