AMS/WMS

MICROCODE VERSION 0732/A

RELEASED 02/17/2006

Newly supported features and functions for Version 0732/A

1) User LAN port online setting support

Item Description
Contents The following can be set on User LAN port without a reboot – IP address, subnet mask, and
default gateway.

Improvements for Version 0732/A

1) Cache Partition Manager (CPM) enhancement

Item Description
Contents a) Partition setting and LU setting of CPM can now be applied with a single reboot
b) Snapshot can be installed when CPM is already used
c) In this case CPM configuration will be initialized when Snapshot is installed

2) Clearing the port configuration on the change of Interface board

Item Description
Contents When the type of installed interface board is changed, all of the following configuration setting
for the port will be cleared to eliminate the influence of the previous configuration.
a) Host Group information / Target information
b) Host Group Option / Target Option
c) Mapping information
d) FC Port setting information / NAS connection information / ISCSI port setting information
e) CHAP security information (ISCSI)

3) Support for displaying NAS OS/BIOS version on Web browser

Item Description
Contents Support for displaying NAS OS/BIOS version on Web browser

4) Support of default button of LAN configuration / on Web browser

Item Description
Contents Microcode supports button in the “equip set” window of Web that can set default configuration
of LAN.

5) Checking the same IP address of NNC management port

Item Description
Contents Checking the same IP address of NNC management port

6) QLA4010 support
Item Description
Contents Support of the ISCSI HBA “QLA4010”

HDS Confidential 1 of 5
7) Support of 128 host/per port connection of ISCSI
Item Description
Contents Support of 128 host/per port connection of ISCSI

8) Support of connection one or more AMS/WMS ISCSI ports to one IP-SAN

Item Description
Contents Note: Please see ECN DF700-103 for more detail information.

9) Support of Red Hat Linux (IA32) and Windows 2003 (IA32) connection with ISCSI
Item Description
Contents Note: Please refer to ECN DF700-103 Appendix A. for detail information.

The change of contents for Version 0732/A

1) Subsystem Down for controller recovery during sequential write

Item Description
Contents Subsystem may go down with the following message for controller recovery during sequential
write.
A) Data transfer check error [WRNODTYBK]
B) Parity generation LA error[DRR]
Problem may occur when all the following conditions are met.
Conditions:
A) DF700M (AMS500)
B) Cache memory is more than 2GB/CTL
C) LU is on RAID group of FC drives
D) LU is using master partition (partition #0 or #1)
E) RAID level of this LU is RAID5 (4D+1P or 8D+1P) or RAID6 (4D+2P or 8D+2P)
F) The longer sequential write command(more than 512KB length)
G) The controller is recovered

2) SATA HDD block

Item Description
Contents SATA HDD was blocked by a conflict between online verify and host I/O. When the online
verify and host I/O access the same area, the microcode executes the online verify process by
priority. In this case, the drive access for host I/O may result in a timeout error and the SATA
HDD may be blocked.

3) LU Hang Up
Item Description
Contents LU may hang up because the controller fails to block when the obstacle occurs on the controller.
The phenomenon is caused by a bug in the microcode logic to block the controller when a
specific obstacle occurs on the controller.

4) Incorrect Web information messages for NNC DIMM failure

Item Description
Contents When a failure of a NNC DIMM occurs, the displayed information message references the
wrong DIMM slot number.

HDS Confidential 2 of 5
5) NNC failure after pulling out the SFP modules
Item Description
Contents NNC failure occurs with the message of “NNC Hardware failure detected [TEMP] (NNC-X)”
after removal of an SFP module.
Due to a microcode bug an improper reference is made to a hard register.
Problem may occur when all the following conditions are met.
Conditions:
A) NAS Configuration (DF700XS, DF700S, DF700M with NNC)
B) Microcode version is 0726/A or later
C) SFP on the NNC is removed

6) Controller/ENC recovery failure after hardware error

Item Description
Contents This was caused by a microcode bug on the sequence of hardware error during controller or
ENC recovery.

7) Improper ENC failure and Improper Unit # on the failure message after HDU replacement
Item Description
Contents Improper ENC failure and improper Unit # on the failure message occur after HDU replacement
which has some fibre channel port failure. Due to microcode bug on the sequence of HDU
recovery, microcode found the backend fibre channel failure improperly after HDU replacement.

8) SNM connection failure by LAN failure

Item Description
Contents Storage Navigator Modular connection failure may occur by LAN failure, Web connection and
host I/O are no problem. This phenomenon is caused by a bug in the microcode logic to connect
to SNM.
Problem may occur when all the following conditions are met:
A) SNM is used to connect and reference DF700
B) LAN failure occurs
C) Response error from SNM after (B)

9) No guard for creating the pair with S-VOL of True Copy in Read only or Protected LU of Data
Retention
Item Description
Contents The phenomenon is caused by a bug in the microcode logic to create True Copy pairs with Read
only and Protected LU.
Problem may occur when all the following conditions are met.
A) Read only or Protected LU of Data Retention
B) Pair is created as S-VOL of True Copy LU

10) Inappropriate drive failure for drive response diagnosis function

Item Description
Contents Microcode bug in the sequence of drive response diagnosis function.
Problem may occur when all the following conditions are met.
A) Drive Response Time Diagnosis is set to “Enable(Output Message and Dynamic Sparing)”
B) The host I/O is about 100 IO/minute for both controllers

HDS Confidential 3 of 5
11) Sequential read performance deterioration
Item Description
Contents Due to a microcode bug in interruption sequence of prefetch, the prefetch may hang up and the
sequential read performance may deteriorate.
Problem may occur when all the following conditions are met.
A) During sequential read
B) SNM setting or pair setting from CCI or LU ownership change by host I/O.

12) Controller failure during the PS ON sequence after cache data loss
Item Description
Contents After a cache data loss a controller failure may occur during the PS ON sequence when
Snapshot has been installed.

13) Incorrect DST time for NAS

Item Description
Contents The summer daylight savings time setting for NAS may start and end later than expected, or the
DST setting may not start.

14) Controller failure due to NNC DIMM failure during NNC reboot
Item Description
Contents Due to the microcode bug in sequence of NNC cache failure during NNC reboot.
Problem may occur when all the following conditions are met.
A) NNC reboot
B) Cache failure of NNC occurs

15) NNC boot timeout

Item Description
Contents NNC boot timeout may occur after the recovery of the failed controller.

16) Alarm LED (Fibre Channel interface board) error

Item Description
Contents The Alarm LED on the FC interface board was not illuminated after the controller was replaced
without the SFP module. Due to a microcode bug in the failure detection during controller
recovery sequence, LED on the FC interface was not illuminated.
Problem may occur when all the following conditions are met.
A) SFP bad or un-installed
B) Controller was replaced with SFP failed or un-installed

17) Improper IP address display for the NNC port after initial setup of NAS
Item Description
Contents . Improper IP address (0.0.0.0) was displayed for the NNC port after initial setup of NAS
without resetting the IP address/subnet mask.
Problem may occur when all the following conditions are met.
A) Microcode 0726/A or later
B) Initial setup without resetting IP address /subnet mask for NNC ports

HDS Confidential 4 of 5
18) Subsystem Down by Read data transfer deadlock
Item Description
Contents Subsystem down might occur with READ command from the host to LU that is using the cache
partition with segment size is 4K or 8K. When the DF700 executes a long READ command it
may be separated into smaller data transfer several times. In the case of 4KB or 8KB segment
size using CPM; it is possible that the DF700 tries to close the READ command before
completing the entire transfer. This is caused by a bug in the data transfer sequence, and the
subsystem may halt with internal deadlock.
Problem may occur when all the following conditions are met.
A) CPM is installed and enabled.
B) LU is using the cache partition with segment size of 4KB or 8KB.
C) RAID level is RAID0 /RAID5 /RAID6 and
1. In case of 4KB segment size: more than 8D / 8D+1P or 8D+2P
2. In case of 8KB segment size: more than 16D / 16D+1P / 16D+2P
D) Read command is separated into several internal smaller size data transfers. The
phenomenon occurs more readily with longer Read commands.
E) The entire Read data is in the same data stripe column and All-Cache MISS.

19) Controller failure during online microcode update

Item Description
Contents A) Controller 1 failure may occur during online microcode from 0730/B to another revision.
B) Controller 1 failure may occur during online CTL1 replacement when 0730/A or 0730/B.
Problem may occur when all the following conditions are met.
A) DF700S (AMS200) or DF700XS (WMS100)
B) Number of system disks is less than (5)
C) Microcode is 0730/A or 0730/B
D) Execution of the online microcode update or online controller replacement for CTL1

20) CCI command failure by ISCSI port when LUN Manager is used
Item Description
Contents Microcode bug was found in the mapping sequence of CCI command with ISCSI.
Problem may occur when all the following conditions are met.
A) DF700 using ISCSI I/F
B) LUN Manager is installed
C) The host is connected to Host Group #1 or higher (HG0 is not affected)

21) Controller failure when the system HDD write and the host I/O occur simultaneously
Item Description
Contents Microcode bug was found in the cache access sequence.
The system HDD write occur at the following operation from SNM.
A) Starting an LU format
B) LU format completion
C) LU create
D) LU ownership change etc.

HDS Confidential 5 of 5