Вы находитесь на странице: 1из 2

AMS/WMS

MICROCODE VERSION 0770/E


RELEASED 03/08/2007

Newly supported features and functions for Version 0770/E


NONE

Improvements for Version 0770/E


NONE

The change of contents for Version 0770/E

1 NAS subsystem down after changing IP address of user port


Contents NAS subsystem down occurs (1) minute after changing the IP address of the user port on
DF700. When this phenomenon occurs, both NNC fail and reboot with the following WEB
information message: IA2D0x NNC No Response to Heartbeat (NNC-x)
The microcode of the DF700 sends an invalid message to the NAS OS when the IP address of
the DF700 is changed by SNM, and detects the heartbeat failure because the NAS OS terminates
the processing by the receipt of the unrecognized message.
The problem may occur with all of the following conditions met:
A) NAS configuration
B) The microcode of DF700 is 0770/A or 0770/C
C) The IP address of the user port of DF700 is changed

2 Subsystem hung-up during write share job


Contents With all of the following conditions met, the problem may occur:
A) PAIR or COPY status on the True Copy Basic
B) A write command for LU of (A) is reset by the host because the command processing in the
Subsystem is delayed
C) The following actions occur at the same time:
• Write job reset by processing from the host
• Completion of write data transfer

3 All HDD in a unit cannot be accessed because of SENC obstacle


Contents HDD in a unit are inaccessible due to WWN discrepancies, with some HDD and controller
blocked. The host may also be unable to access subsystem due to PIN over condition. This
phenomenon may occur by SENC block that causes WWN discrepancy of all HDD in the unit.

4 Controller failure caused by FC HDD obstacle


Contents Controller failure may occur with the following message, caused by FC HDD obstacle. This is
due to a microcode bug in the online verifying processing in RAID6.
WEB Message: H20100 parity generation LA error[DRR]
The problem may occur when all of the following conditions are met:
A) RAID6 with FC HDD
B) An HDD in the RAID group is detached
C) No spare HDD is available to recover the detached HDD
D) Online Verify detects a media/medium error in the other HDD in the RAID group.

HDS Confidential 1 of 2
5 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 is
occupied by the Queue Full processing, and the other controller detects the controller timeout.
(*1) The controller responds with Queue Full status when more than 512 commands from a port
are received simultaneously.

HDS Confidential 2 of 2

Вам также может понравиться