9500V

MICROCODE VERSION 065E & 165E

RELEASED 04/20/2007

Newly supported features and functions for Version 065E & 165E

1 SATA 500GB HDD support – Models 9570V, 9580V, 9585V only

Contents This microcode supports the following SATA 500GB HDD in the RKAJAT (*1)
DF-F700-ATE500R – 491.9GB
(*1) RKAAT/RKAATL/RKAJATL is NOT supported
Note: SNM V7.10 required for the 500GB HDD support.
• Microcode: 9570V: 065E or higher
9580V/9585V: 165E or higher
• Storage Navigator Modular: 7.10 or higher
The 500GB 7.2K SATA drive is supported with 9570V, 9580V, and 9585V Thunder 9500V
models only.
• For new upgrade sales, DF-F700-ATE500R is supported with 9570V, 9580V and 9585V
• For new upgrade sales, DF700-RKAJAT is supported with Thunder 9570V, 9580V and 9585V,
and will be the only SATA shelf shipped from the factory for new upgrade sales.
• For existing installations, DF600-RKAJAT supported with 500GB 7.2K on 9570V, 9580V, and
9585V models with upgrade to minimum microcode and Storage Navigator Modular levels.
• 500GB 7.2K not supported with older 9500V SATA shelves, 9520V, and 9530V models.
o [Older SATA shelf] DF600-RKAAT is not supported with the 500GB 7.2K drive
o [9520V ] DF600-RKAATL, DF600-RKAJATL are not supported with the 500GB 7.2K drive
o 9530V does not support SATA (FC only)
Note: If there is any, plan to add future Fibre Channel expansion trays behind the SATA drives.
SATA expansion trays MUST BE INSTALLED in PAIRS

Improvements for Version 065E & 165E

NONE

The change of contents for Version 065E & 165E

1 All HDD in a unit cannot be accessed by a SENC obstacle

Contents All HDD in a unit become inaccessible due to WWN discrepancies, along with some HDD and
controller become blocked. The host may not be able to access the subsystem by PIN over
condition

2 Controller failure caused by Queue Full

Contents In a heavy I/O environment, a controller block may occur when a host continues a quick
command retry for Queue full (*1) status from the controller. The CPU of the controller
occupied by the Queue Full processing, and the other control detects the controller timeout.
(*1) The controller responds with Queue Full status when more than 512 commands from a port
received simultaneously.

HDS Confidential 1 of 2
 3 Write command time-out during large write
Contents With sequential and random I/O received for an LU, write command time-out may occur.
When all of the following conditions are met, the problem may occur:
1. In the case of Hi-speed Sequential Write Mode = OFF (default)
A) LU are configured with FC HDD - RAID5 with 4D+1P or 8D+1P
B) Write command for the area starts at the 256KB(4D+1P) or 512KB(8D+1P) boundary of the
above LU is issued from the host with an I/O size of 1MB, 2MB, 3MB and 8MB.
C) LU of (b) receives random write commands
2. In the case of Hi-speed Sequential Write Mode = ON)
A) LU are configured with FC HDD - RAID5 with 4D+1P or 8D+1P
B) Write command for the above LU is issued from the host with an I/O size of 512KB or larger
C) LU of (b) receives random write commands

4 Host command time-out and PS OFF failure occur

Contents When CHK1 (*) occurs in a write processing to SATA HDD, host command time-out and PS
failure may occur due to a microcode bug in the exclusion processing between controllers in
SATA configurations.
(*) CHK1: internal reset in a controller caused by hardware error
When all of the following conditions are met, the problem may occur:
A) SATA HDD
B) HDD error occurs in HDD write processing
C) CHK1 occurs in a controller
D) (b) and (c) occur at the same time

5 Controller blocked by “HA060x Kernel monitoring check NG (CTL-x)”

Contents When the Subsystem receives random writes, a controller block may occur with the following
message.
Web message: HA060x Kernel monitoring check NG (CTL-x)
This problem may occur with duplicated write area in an LU; this is due to a microcode bug in
the search processing of a write area.

HDS Confidential 2 of 2