HP 4400 HP StorageWorks Enterprise Virtual Array release notes (XCS 09534000) - Page 4

Fixes (XCS 09534000), Controller termination

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 4 highlights

• HP SCSI FC Compliant Data Replication Protocol-This protocol supports Fibre Channel exchangebased routing in which all frames within a given exchange use the same path, but other exchanges can use other paths. This allows for improved performance. This protocol supports fabric switches that are configured for either exchange-based routing or inorder delivery. For optimum performance, HP recommends using exchange-based routing. For feature details and best practices, see the HP Continuous Access EVA Implementation Guide. NOTE: HP strongly recommends that you review these release notes and the HP StorageWorks Enterprise Virtual Array Updating Product Software Guide (XCS 09534000) before upgrading the controller software and using this feature. • VMware for HP Command View EVA support-The controller software supports HP Command View EVA on a Windows guest operating system (running on a VMware server). This is supported on VMware ESX Server 3.5 and 4.0. See the HP Command View EVA Installation Guide for installation and configuration details. NOTE: When presenting EVA LUNs to a VMware server (where HP Command View EVA is installed), presentation is only supported on VMware ESX Server 3.5. Fixes (XCS 09534000) The following issues have been fixed in XCS 09534000: Controller termination This section describes issues that can result in termination of controller operation. A single controller termination will result in a reduction of redundancy. A dual controller termination indicates a possibility of a data unavailable condition. A recursive termination will require manual intervention to address. • Implemented a resource management scheme that monitors the use of volatile buffers during a heavy sequential workload or parity rebuild, which previously could result in a controller termination (termination code 0x02160102). This applies to the EVA4400 only. • Improved diagnostic capability to help define root cause in rare instances of the Logical Disk Capacity being set to zero (termination code 0x0442011f). • Address an issue where diagnostic inquiry commands sent to a controller after a restart could lead to a termination, indicating Unit Stalled Too Long as the cause (termination code 0x4238011f). • Fixed a recursive termination (termination code 0x04d3011f) that could occur during a resynchronization if a disk drive is removed while reconstruction processes are running. • Fixed a recursive termination (termination code 0x04D3011f) that occurred during snapshot creation when the source virtual disk on the secondary controller. • Fixed a controller termination that occurred when persistent reservation commands caused a DSI exception (termination code 0x04d3011f). • Fixed a possible recursive termination (termination code 0x0402011f) that could occur after a controller software upgrade if the active storage system metadata volume fails. 4

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
•
HP SCSI FC Compliant Data Replication Protocol
—
This protocol supports Fibre Channel
exchange-
based
routing in which all frames within a given exchange use the same path, but other exchanges
can use other paths. This allows for improved performance.
This protocol supports fabric switches that are configured for either exchange-based routing or in-
order delivery. For optimum performance, HP recommends using exchange-based routing. For
feature details and best practices, see the
HP Continuous Access EVA Implementation Guide
.
NOTE:
HP strongly recommends that you review these release notes and the
HP StorageWorks Enterprise
Virtual Array Updating Product Software Guide (XCS 09534000)
before upgrading the controller
software and using this feature.
•
VMware for HP Command View EVA support
—
The controller software supports HP Command
View EVA on a Windows guest operating system (running on a VMware server). This is supported
on VMware ESX Server 3.5 and 4.0. See the
HP Command View EVA Installation Guide
for in-
stallation and configuration details.
NOTE:
When presenting EVA LUNs to a VMware server (where HP Command View EVA is installed),
presentation is only supported on VMware ESX Server 3.5.
Fixes (XCS 09534000)
The following issues have been fixed in XCS 09534000:
Controller termination
This section describes issues that can result in termination of controller operation. A single controller
termination will result in a reduction of redundancy. A dual controller termination indicates a possibility
of a data unavailable condition. A recursive termination will require manual intervention to address.
•
Implemented a resource management scheme that monitors the use of volatile buffers during a
heavy sequential workload or parity rebuild, which previously could result in a controller termination
(termination code
0x02160102
). This applies to the EVA4400 only.
•
Improved diagnostic capability to help define root cause in rare instances of the Logical Disk Ca-
pacity being set to zero (termination code
0x0442011f
).
•
Address an issue where diagnostic inquiry commands sent to a controller after a restart could lead
to a termination, indicating Unit Stalled Too Long as the cause (termination code
0x4238011f
).
•
Fixed a recursive termination (termination code
0x04d3011f
) that could occur during a resyn-
chronization if a disk drive is removed while reconstruction processes are running.
•
Fixed a recursive termination (termination code
0x04D3011f
) that occurred during snapshot
creation when the source virtual disk on the secondary controller.
•
Fixed a controller termination that occurred when persistent reservation commands caused a DSI
exception (termination code
0x04d3011f
).
•
Fixed a possible recursive termination (termination code
0x0402011f
) that could occur after a
controller software upgrade if the active storage system metadata volume fails.
4