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

VSP

MICROCODE VERSION 70-03-09-00/00-MO99


RELEASED 04/23/2012

New supported features and functions for Version 70-03-09-00/00-MO99


1. Mainframe & OPEN System
NONE

2. Mainframe System
NONE

3. OPEN System
NONE

The change of contents for Version 70-03-09-00/00-MO99


1 Blockage of multiple cache PCBs
Phenomena When a power outage that can be restored within several
tens of seconds occurs, the data is backed up in memory but
not saved in CM-SSD as per specification.
However, if such an instantaneous power outage occurred
frequently (*), battery charge gradually got low and
eventually ran out. In this case, though the data was
volatilized, the micro-program determined as non-volatile
and cache management information became invalid, leading
to blockage of multiple cache PCBs. (SIM=FFEExx,
SSB=1355, 13C0)

(*) An instantaneous power outage repeatedly occurs within


10 seconds for 40 minutes or longer.
Severity (High, Medium, Low) High
Conditions of Occurrence The problem occurs when all the following conditions are
met.
(1) Cache battery charge is 50% or higher.
(2) An instantaneous power outage occurs frequently. (*)

(*) An instantaneous power outage repeatedly occurs within


10 seconds for 40 minutes or longer.
Affected Products/Version CMBK: All
Fixed Product/Version CMBK: 70-74-55
Category Open or Mainframe
Changed Part CMBK

HDS Confidential 1 of 9
2 No SIM when response delay is detected in drive
Phenomena While there was a drive for which SSB=A4CE that was
output when response delay drive was detected had been
output, if SOM144 or SOM887 was set to ON and a
response delay was detected in the same drive again, SIM
by the SOM setting was not output.
Severity (High, Medium, Low) High
Conditions of Occurrence The problem occurs when all the following conditions are
met.
(1) There is a drive in which SSB=A4CE has been output.
(2) SOM144 or SOM887 is set to ON.
(3) A response delay of the above drive is detected.
Affected Products/Version DKCMAIN: 70-03-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

3 Failed to open Restore Keys window and


unchanged number of LDEVs after LDEV deletion
Phenomena Phenomenon 1:
When Restore Keys window was activated, Storage
Navigator message 10122-107001 appeared and the window
could not be opened.
Phenomenon 2:
When Select by Parity Groups window was opened from
Edit CU Monitor Mode window, a parity group was
selected, and then Parity Group Properties window was
displayed, the number of LDEVs did not change after
LDEV deletion.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when the following is performed from
Storage Navigator after an LDEV is deleted or added.
Phenomenon 1:
After an encryption setting is made for a parity group to
which the LDEV used to belong, Restore Keys window is
activated.

Phenomenon 2:
After Edit CU Monitor Mode and then Select by Parity
Groups windows are opened, a parity group to which the
LDEV used to belong is selected, and the Parity Group
Properties window is opened.
Affected Products/Version SVP: 70-02-53/00 and higher
Fixed Product/Version SVP: 70-03-07/00
Category Storage Navigator
Changed Part SVP

HDS Confidential 2 of 9
4 Volatile activation with non-volatile PS ON
Phenomena After an MPB was exchanged with another MPB installed
on another RAID700 during PS OFF, when non-volatile PS
ON was performed, SIM=FFE7-00 was output and the
storage was activated with volatilization.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Problem may occur with the following conditions are met.
(1) An MPB is exchanged with another MPB installed on
another RAID700 while PS is OFF.
(2) Non-volatile PS ON is performed.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

5 CM PCB blockage and high MP usage rate


Phenomena Phenomenon 1: After activation following a power outage,
the CM PCB was blocked on CL-1 side (SSB=1353,
SIM=FFEE).
Phenomenon 2: The MP usage rate remained high even
though the I/O was stopped.
Severity (High, Medium, Low) Low
Conditions of Occurrence Phenomenon 1: The problem may occur when the following
condition (1) or (2) is met.
Phenomenon 2: The problem may occur when the following
condition (2) is met.
(1) A two-module configuration storage system is activated
after a power outage.
(2) After a power outage occurs while memory backup from
a CM PCB to an SSD fails on both of CL-1 and CL-2, the
storage system is activated.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

6 Deleting volume failed without LUN path definition


Phenomena When a volume without LUN path definition was deleted,
Storage Navigator message 03205-006535 was output and
the operation was disabled.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when path addition or deletion is retired
after path addition or deletion fails.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open
Changed Part DKCMAIN

HDS Confidential 3 of 9
7 Failure of discovery operation for EVA
Phenomena When the firmware of EVA was updated to a version that
supported VMWare VAAI function, a discovery operation
for the storage system failed and Storage Navigator
messages 00622-109016 and 00622-105251 were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Problem occurs when all the following conditions are met.
(1) EVA P6500/6300 is used as an external storage.
(2) The firmware version of EVA P6500/P6300 is
10100000. (VAAI support version)
(3) A discovery operation is performed for the above
storage system.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Universal Volume Manager
Changed Part DKCMAIN

8 Failure of retried external/virtual VOL deletion


Phenomena The following phenomena occurred.
[If an operation was from Storage Navigator]
(1) UVM external VOL deletion failed with Storage
Navigator message 00605-008966 and SSB=1556, 3213,
and 13F1 output.
(2) DP/DPz or CoW Snapshot virtual VOL deletion failed
with Storage Navigator message 03205-008966 and
SSB=1556, 3213, and 13F1 output.
[If an operation was from CCI]
(1) UVM external VOL deletion (raidcom delete
external_grp) failed (SSB=1556, 3213, and 13F1), and if the
status was checked by raidcom get command_status,
SSB1=2EDA, SSB2=FFFF were output.
(2) DP/DPz or CoW Snapshot virtual VOL deletion
(raidcom delete ldev) failed (SSB=1556, 3213, and 13F1),
and if the status was checked by raidcom get
command_status, SSB1=2EE8, SSB2=FFFF were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Problem occurs with all the following conditions met.
(1) Deletion of UVM external VOL, or DP/DPz or CoW
Snapshot virtual VOL fails with SSB=1559 (*) output.
(2) The deletion is retried for the same VOL.
* SSB=1559 is output when virtual VOL deletion
processing conflicts with configuration change by Volume
Migration or Quick Restore and fails.
Affected Products/Version DKCMAIN for Open: 70-02-03-00/00 and higher
DKCMAIN for Mainframe: 70-02-03-00/00 and higher
(other than DPz), 70-02-54-00/00 and higher (DPz)
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Universal Volume Manager, Dynamic Provisioning,
Dynamic Provisioning for Mainframe, Copy-on-Write
Snapshot
Changed Part DKCMAIN

HDS Confidential 4 of 9
9 ABEND of cache maintenance after all MPs
blockage
Phenomena During automatic recovery processing executed if invalid
cache management information was detected, a power
outage occurred and non-volatile PS ON was performed.
After the system was activated, when the blocked cache was
replaced, all MPs were blocked immediately after blockage
processing and SVP message ONL0117 was output,
eventually the cache maintenance ended abnormally.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Problem may occur with the following conditions met.
(1) A power outage occurs during automatic recovery
processing executed if invalid cache management
information is detected.
(2) Non-volatile PS ON is performed.
(3) The blocked CM PCB is replaced.
Affected Products/Version DKCMAIN: 70-02-03-00/00 and higher
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

10 Failure of removal of LDEVs in LUSE


Phenomena Phenomenon1
When LDEV removal was performed for a LUSE volume
without SCSI logical path from CCI, only the top LDEV in
the LUSE volume was deleted.
Phenomenon2
When a CM PCB was replaced while the above top LDEV
was installed again, SVP message 2412E was output and the
operation failed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Phenomenon1 occurs when the following conditions (1) and
(2) are met.
Phenomenon2 occurs when all the following conditions are
met.
(1) LDEV removal is performed from CCI.
(2) The LDEVs removed in (1) are included in a LUSE
volume without SCSI logical path.
(3) The top LDEV of the above LUSE is installed again.
(4) A CM PCB is replaced.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

HDS Confidential 5 of 9
11 SVP error message 4092E
Phenomena When a spreadsheet on which a value other than multiples
of 4,096 was described was read by using Offline SVP tool,
an error occurred and SVP message 4092E was output.
(The value of CLPR cache can be described in unit of
2,048MB)
Severity (High, Medium, Low) Low
Conditions of Occurrence Problem occurs with the following conditions met.
(1) A CLPR cache value described on a spreadsheet is other
than multiples of 4,096.
(2) The spreadsheet is read by using Offline SVP tool.
Affected Products/Version SVP: 70-02-74/00 and higher
Fixed Product/Version SVP: 70-03-07/00
Category Open or Mainframe
Changed Part SVP

12 I/O time-out messages during code upgrade


Phenomena During micro-program upgrade from 70-02-72-00/00 to 70-
03-02-00/00, I/O time-out messages IOS078I and IOS071I
were output on Mainframe host side, and SSB=8BD8 and
8907 were frequently output on storage system side.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions
are met.
(1) 2 modules and full MPB configuration (32 MPs).
(2) HMO51 is set to ON in both TC/TCz MCU and TC/TCz
RCU.
(3) Online micro-program exchange is performed during I/O
processing.
Affected Products/Version DKCMAIN: 70-02-31-00/00 and higher
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category True Copy, True Copy for Mainframe
Changed Part DKCMAIN

13 Data volatilization due to failure of CM-SSD


Phenomena When the data was restored in CM-SSD at activation after
planed power OFF or power outage, due to an intermittent
failure of CM-SSD, the data might be volatilized.
(SIM=FFCExx or FFDFxx, SSB=35B5, 354D)
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs with intermittent failure in CM-SSD at
planned power OFF or power outage.
Affected Products/Version DKCMAIN: All
CMBK: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
CMBK: 70-74-55
Category Open or Mainframe
Changed Part DKCMAIN, CMBK

HDS Confidential 6 of 9
14 LA error and ECC group blockage
Phenomena When an ECC group where a pool VOL belonged was
blocked due to drive blockage that exceeded the redundancy
limit, and the ECC group was recovered by replacing the
blocked drives with new drives, an LA error (SSB=3289,
a443) occurred and the ECC group might be blocked again
due to drive blockage.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are
met.
(1) An I/O is issued to a DP/DPz or DT/DTz VOL.
(2) An ECC group, to which a pool VOL associated with the
DP/DPz or DT/DTz VOL belongs, is blocked due to drive
blockage.
(3) The above blocked drives are replaced with new drives.
(4) The blocked ECC group is recovered by format.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-02-54-00/00 and higher
(DPz), 70-03-01-00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Dynamic Provisioning, Dynamic Provisioning for
Mainframe, Dynamic Tiering, Dynamic Tiering for
Mainframe
Changed Part DKCMAIN

15 Internal LDEV exceeding the maximum capacity


Phenomena By the following operations, an internal LDEV (3.0TB)
exceeding the maximum capacity of internal LDEV
(2.99TB) could be created.
(1) Install CV from CCI
(2) Offline SVP tool
In this case, if the area of over 2.99TB was accessed, an LA
error occurred and the LDEV might be blocked.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are
met.
(1) An internal LDEV with the capacity of over 2.99TB is
created by an operation from CCI or Offline SVP tool.
(2) The area over 2.99TB is accessed. (Including LDEV
format).
Affected Products/Version DKCMAIN: All
SVP: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
SVP: 70-03-07/00
Category CCI
Changed Part DKCMAIN, SVP

HDS Confidential 7 of 9
16 Delay in host I/O response
Phenomena When there was a TC/TCz or UR/URz path without the pair
created, a response to host I/O was delayed due to health
check. (Delay of 500μsec per path)
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are
met.
(1) There is a TC/TCz or UR/URz path.
(3) The TC/TCz pair is not created or no I/O is issued
through the path of TC/TCz or UR/URz.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category True Copy, True Copy for Mainframe, Universal Replicator,
Universal Replicator for Mainframe
Changed Part DKCMAIN

17 Delay in host I/O response due to MP health check


Phenomena In a configuration with the maximum number of MPBs
mounted (8 MPBs (32 MPs)), MP health check that was
executed every 2 seconds took about 1.7 msec for
processing, which caused a delay for 1.7 msec in host I/O
response when a host I/O and the MP health check occurred
at the same time.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are
met.
(1) A configuration with the maximum number of MPs
mounted. (8 MPBs (32 MPs))
(2) A host I/O and MP health check are performed at the
same time.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

18 Application error on SN or SVP reboot


Phenomena The following phenomena occurred on SVP.
- An application error on Storage Navigator.
- SVP reboot.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when the Monitor Switch of Storage
Navigator is enabled.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Open or Mainframe
Changed Part DKCMAIN

HDS Confidential 8 of 9
19 WCHK1 in TCz-URz cascade configuration
Phenomena WCHK1 (SSB=1644) occurred in the I-site in TCz-URz
cascade configuration where volumes whose emulation type
was 3390-A were used as data volumes, when a TCz pair
resync operation was performed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions
are met.
(1) TCz-URz cascade configuration (include the cascade
configuration via multi target configuration)
(2) The volume emulation type of I-site (TCz S-VOL/URz
P-VOL) is 3390-A. (include DPz)
(3) The TCz pair is in Suspend status, and URz is in Duplex
or Duplex-pending status.
(4) A TCz pair resync is performed.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Fixed Product/Version DKCMAIN: 70-03-09-00/00
Category Universal Replicator for Mainframe, True Copy for
Mainframe
Changed Part DKCMAIN

HDS Confidential 9 of 9

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