9500V

MICROCODE VERSION 065C/V & 165C/V

RELEASED 01/22/2007

Newly supported features and functions for Version 065C/V & 165C/V

NONE

Improvements for Version 065C/V & 165C/V

(1) Inquiry Page 83H Identifier=3 support (for Longhorn)

Item Description
Contents When SPC-2 Mode is set, the microcode supports Inquiry Page 83H Identifier=3.
Note: This mode is for Microsoft test use only

(2) Information enhancement of DDS failure on SATA HDD

Item Description
Contents When a DDS failure (0b/88/02) occurs on SATA HDD, the microcode gets more information for
the root cause by enhancement of SENC firmware.

The change of contents for Version 065C/V & 165C/V

(1) McData switch login issue after 9500V power cycle

Item Description
Contents McData switch may not recognize the port of 9500V after a power cycle. When the first Link up
after power-on, the 9500V issues Link Reset to reset and change the BB_Credit after the receipt
of ACC for FLOGI, and issue FLOGI again. Though McData switch responds with ACC for the
second FLOGI, it may NOT respond to the subsequent PLOGI from the 9500V and the port of
9500V cannot be recognized. The problem of McData switch seems to be induced by the second
FLOGI after Link Reset from the 9500V.

(2) Controller failure by Watch dog time-out

Item Description
Contents When an LA error in a controller occurs, the controller may fail by Watch dog time-out.
When all of the following conditions are met, the problem may occur:
A) Hardware error on a controller occurs. (LA , DMA or Cache parity error)
B) HDD command is retried by (A).
C) New HDD command is received before command (B) is finished

(3) SATA HDD failure by SENC LA error

Item Description
Contents SATA HDD belonging to a SENC may be blocked, though there is an LA factor in the SENC.
This may occur by a SENC failure that causes an LA error.

HDS Confidential 1 of 2
(4) Spare SATA HDD failure by LA error
Item Description
Contents When the subsystem starts HDD recovery to spare an HDD, the spare HDD may fail.
When all of the following conditions are met, the problem may occur:
A) Write command is issued to SATA LU
B) Write command executed with write through mode. Battery obstacle, PIN over, PIN Hit, etc
C) HDD recovery starts automatically after completion of writing data and before reading data
to compare.

(5) Performance issue “Multiple Stream Mode”

Item Description
Contents When “Multiple Stream Mode is set, write performance may deteriorate. This is due to a bug in
the cache de-stage processing.
When all of the following conditions are met, the problem may occur:
A) “Multiple Stream Mode” or “Multiple Stream Mode(Write)” is enabled
B) Subsystem receives incomplete sequential write commands

(6) Shadow Image copy does not complete

Item Description
Contents Shadow Image copy does not complete, in addition the following problems may occur.
This is due to a microcode bug in the control processing when two exclusion processes occur at
the same time.
1) HDD recovery does not finish
2) Writing of configuration information to HDD does not complete
3) Quick Shadow restore copy does not complete
4) SMART function to SATA HDD does not finish
5) Forced parity correction does not complete
When all of the following conditions are met, the problem may occur:
A) Shadow Image copy is in process
B) Persistent Reserve command is received just before Shadow Image copy process starts the
change of the status at the end of the copy operation

(7) Recovery failure in HDD insertion

Item Description
Contents When an HDD is pulled out and inserted, the HDD does not recover.
When all of the following conditions are met, the problem may occur:
A) Execution of “Delete all” of RAID group from DAMP/SNM
B) Create RAID Group/LU after (A)
C) Replace an HDD in the RAID Group of (B)
Note: When a subsystem shutdown is executed after (A), this issue does not occur.

HDS Confidential 2 of 2