VSP Microcode Update Resolves Data and Performance Issues

VSP
MICROCODE VERSION 70-02-70-00/00

RELEASED 09/07/2011
Newly supported features and functions for Version 70-02-70-00/00

1. Mainframe & OPEN System
NONE
2. Mainframe System
NONE
3. OPEN System
NONE
The change of contents for Version 70-02-70-00/00

1 MP blockade during power supply failure
Phenomena When a part of power supply broke down, all X-path cables which
connected modules received disturbance and all MPs were blocked as
modules were determined as blocked.
SIM=3073 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) 2-module configuration.
(2) All X-path cables receive disturbance due to a failure such as power
supply.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-70-00/00
Category Open or Mainframe
Changed Part DKCMAIN
2 Resource unlock failure during CM maintenance

Phenomena During CM maintenance, if a failure occurred, resource unlock failed and
SSB=147F was output.
Severity (High, Medium, Low) Low
(1) Mainframe VOL
(2) A failure (such as a transfer error between CMs or a segment reserve
error) occurs during CM replacement.
Category Mainframe
HDS Confidential 1 of 11
3 Data inconsistency in DP/DT volume
Phenomena In DP or DT virtual volume, because a part of data in page (*1) can be
incorrectly read, file system error and application error are detected.
(*1) OPEN: 42MB, MF: 38MB
Severity (High, Medium, Low) High
Conditions of Occurrence The problem occurs when all the following conditions are met.
A. RAID700 all current versions.

B. External volume constituting DP/DT
C. OPEN/Mainframe environment (Open only in case of DP as DP
Mainframe is not supported)
D. Page migration is performed by any of the following operations.
D-1. DP/DT pool expansion
D-2. DP/DT pool shrinks
D-3. DP/DT virtual volume zero data page reclamation
E. Destaging processing is performed by any of the following operations.
E-1. Sequential write in Mainframe/OPEN environment
E-2. Write Pending is over 10% in Mainframe environment
E-3. Write Pending is over 60% in OPEN environment
However, if SOM735 is set to ON, Write Pending is 20 to 50% while it is
10% when SOM735 is OFF and SOM732 is ON.
E-4. P-VOL in initial copy processing by True Copy
E-5. S-VOL in copy processing by UR, Shadow Image, or Flash Copy
E-6. Migration target volume being migrated by Volume Migration
Causes and Updates When Destaging processing is executed for an external volume,
Destaging target is registered at the initiation of Destaging. For the
Destaging target, data consistency is checked at write request to the
external volume, and if the data is inconsistent, the Destaging processing
is retried from the beginning.
In the course of the above processing, if page migration is performed by
rebalance during the Destaging processing for DP or DT pool which uses
an external volume, inconsistency is supposed to be detected at the
consistency check in the Destaging processing and the processing should
be retried, however inconsistency could not be detected due to the timing.
As a result, Destaging is wrongly executed for the migration source
external volume. (Normally, Destaging is executed for the migration
target external volume and page migration is completed.)
The micro-program has been modified to fix the problem.

Category Hitachi Dynamic Provisioning, Hitachi Dynamic Tiering
4 S-VOL data inconsistency at backup from CoW Snapshot V-
VOL
Phenomena When the data in Copy-on-Write Snapshot (CoW) S-VOL is read after
pairsplit operation, the updated data can be read instead of the data
updated in P-VOL before pairsplit operation and file system error and
application error are detected. If the same part of S-VOL is read, the
correct data can be read.
Severity (High, Medium, Low) High
Conditions of Occurrence The phenomenon may occur when the following conditions A1 to A5 or
B1 to B6 are met.
A1. RAID700 All versions
A2. The CoW Snapshot pair is changed to PSUS status by pairsplit
operation
A3. A read I/O is issued to the CoW Snapshot S-VOL
A4. A write I/O is issued to the CoW Snapshot P-VOL
A5. The above read I/O (A3) and write I/O (A4) are received at the same
time, the area to be written contains the part to be read and the write I/O
(A4) is the first write I/O after the pairsplit operation.
B1. RAID700 All versions

B2. True Copy S-VOL and CoW P-VOL share a volume.
B3. The True Copy pair is in COPY or PAIR status, and the CoW pair is
PSUS status.
B4. CoW Snapshot S-VOL receives a read I/O.
B5. Update to the CoW P-VOL by True Copy initial copy or update copy
is received.
B6. The above read I/O (B4) and the update (B5) are received at the same
time, and the update area contains the part to be read, and the update (B5)
is the first update after pairsplit operation.
Causes and Updates When a P-VOL receives a write I/O after a CoW pair status is changed to
PSUS by pairsplit operation, the data before update in P-VOL is copied to
a pool VOL and then the P-VOL data is updated with the new data.
On the other hand, when an S-VOL receives a read I/O, in which VOL
the target data is stored, P-VOL or the pool VOL, is checked and the data
stored in the P-VOL or pool VOL is transferred to a host.
In the course of the above processing, if a write I/O is issued to P-VOL
during the processing of read I/O to S-VOL, the data is switched to the
data before update stored in the pool VOL and transferred to the host
under normal circumstances, however, the data cannot be switched in
some cases because the read I/O is in process, eventually the new data in
P-VOL is transferred to the host.
The micro-program has been modified to fix the problem.

Category Copy-on-Write Snapshot, True Copy
5 Wrongly enabled operations without appropriate permission
Phenomena When remote command device registration/deletion or EXCTG
registration/deletion was executed for an LDEV of external VOL that was
allocated to a journal while the user had no permission for a resource
group where the external VOL belonged to, the error was not detected
and the operation was wrongly enabled.
Causes and Updates The micro-program has been modified to fix the problem.
Affected Products/Version SVP: 70-02-03/00 and higher
Fixed Product/Version SVP: 70-02-70/00
Category Universal Replicator for Mainframe
Changed Part SVP
6 LDEVs wrongly created with the same LBA start point

Phenomena When the following were executed from CLI, LBA start points of LDEVs
created in (1) and (2) were the same.
(1) Install CV command was requested.
(2) CoW Snapshot VOL creation was requested for the LDEV# same as
that in (1), but the command was rejected with SSB=2E11 and 0053
output.
(1) Install CV command is received from CLI.
(2) CoW Snapshot VOL creation is requested with the same LDEV#
specified before the processing result is reflected to the actual
configuration.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
7 WCHK1 occurrence in an MP with SIM=3073 output

Phenomena When cache failure blockade (single side) occurred on UR RCU side,
WCHK1 occurred in an MP and SIM=0x3073 was output.
(1) UR Mainframe pair.
(2) Update I/O (FMTWR) is executed.
(3) Cache failure blockade (single side) occurs on RCU.
Category Universal Replicator for Mainframe
8 SSBs frequent output at MP PCB blockade with HMO51 ON
Phenomena If an MP PCB was blocked while HMO51 was set to ON, SSB=B5CB
and B6FB were frequently output.
(1) Host Mode Option51 is set to ON.
(2) An MP PCB is blocked.
Category Open
9 Duplicate display of task result

Phenomena When SVP was rebooted while a Storage Navigator task was executed,
the task result display was duplicated.
(1) SVP is rebooted during any of the following processing’s.
- Format LDEVs
- Shred LDEVs
- Shrink pools
- Relocate pool
(2) Storage Navigator activation takes 20 minutes or longer.
(In a dialog "Wait for Storage Navigator Start" on SVP, the status of
ModelMan is Initialize (start) for more than 20 minutes and then Storage
Navigator activates)
Affected Products/Version SVP: All
Category Storage Navigator
Changed Part SVP
10 LA error with SSBs output and possible drive blockade after

pool VOL format
Phenomena When format for a pool VOL was executed as a recovery for blockade of
a DP pool due to the blockade of 2 PDEVs, an LA error occurred with
SSB=3289, A443, and B2FF output and some drives might be blocked.
(1) DP pool VOL.
(2) Pool VOL is blocked due to a drive failure.
(3) Format for the pool VOL is executed.
11 Incomplete message activation job and possible MIH
occurrence
Phenomena Because time-out flag continued to remain at re-activation of message
activation job (replication copy job), the message activation job could not
be completed and MIH might occur in a host. MIH message: IOS071I
(IOS1071I)
(1) Mainframe connection.
(2) Message activation job (replication copy job) waits for 1 second or
longer.
Category Mainframe
12 Incorrect display of LIST COUNTS and RMF report result

Phenomena When LIST COUNTs was executed, "BACK END DATA
TRANSFERS" might not be displayed correctly.
When RMF report was collected:

- XTNT POOL of CACHE SUBSYSTEM DEVICE OVERVIEW might
not be displayed correctly, and
- RAID RANK ACTIVITY might not be displayed correctly only when
the DKC emulation type was 2105.
(2) DEV# in the same CU in an ECC group is 0xff only or DEV# of a
virtual VOL (DP VOL or UVM) is 0xff.
(3) LIST COUNTS or RMF report is collected.
Category Mainframe
13 SSB=59F0 output during FCv2 copy processing

Phenomena During FCv2 copy processing, SSB=59F0 was output.
(2) FCv2 copy is in process.
Category Compatible Flash Copy version2
14 MIH occurrence during FCv2 copy processing
Phenomena When the following was executed for an FCv2 relation, MIH might
occur.
- Update I/O to the copy source
- Update I/O or read data command to the copy target
SSB= 59F0 and 1602 were output.
(1) Mainframe
(2) An I/O is issued to an area where FCv2 relation copy is not yet
performed.
- Update I/O to the copy source
- Update I/O or read data command to the copy target
(3) During the copy processing, a failure which disables copy processing
is detected.
Category Mainframe
15 Failure of recovery maintenance after device removal

Phenomena After a device removal (PDEV removal/Volume To Space/Make
Volume) failed with SVP message [ONL0813E], the recovery failed with
the same message output again and the following recovery maintenance
was disabled.
(1) During device removal maintenance (PDEV removal/Volume To
Space/Make Volume), SVP message [ONL0813E] is output and the
maintenance fails. (*a)
(2) As a recovery maintenance for the above, a removal setting different
from the above is made on the window and maintenance is performed.
*a: Depending on the timing of the above message display, the problem
may not occur.
16 Wrong light up of LEDs for removal
Phenomena After the removal of all HDDs in a DKU failed, when the same operation
was executed as a recovery, SVP message, [ONL 4050i] appeared and the
LEDs of SSW, HDDPWR, HDDFAN, and DKUPS, which indicated that
removal was enabled, lit up.
(1) All HDDs in a DKU are removed. (Including DKU frame removal)
(2) The above removal fails.
(3) The removal is retried as a recovery. (Excluding DKU frame removal)
(4) Either (a) or (b) below is met.
(a) The DKU where HDDs are removed is the last one.
(b) A DKU next to the one where HDDs are removed has no HDDs
installed.
Affected Products/Version SVP: All
Changed Part SVP
17 ABEND of copy processing with SIMs and SSBs output due to

DP-VOL removal
Phenomena During correction copy or drive copy of an ECC group including pool
VOLs, if a DP-VOL associated with the pool was removed, the copy
processing ended abnormally and SIM=453X and 463X were output, and
then SSB=9B51, 9A17 and 1389 might be output.
(1) Correction copy or drive copy of an ECC group including DP pool
VOLs is executed.
(2) A DP-VOL is removed.
18 Not logged SSB when CHP is ON

Phenomena When CHP was ON, RST NOTICE SSB=5001 was not logged in SVP.
(Host report was done correctly)
(2) CHP is ON.
Category Mainframe
19 Failure of copy to spare drive between different FF types
Phenomena Flash drive copy to a spare drive in different FF types (SFF/LFF) was
disabled.
(1) Copy to a spare drive from SFF to LFF or LFF to SFF is performed.
(2) Flash drives (SDTxx-xxxxxx) are used.
Affected Products/Version CONFIG: 70-02-58/00 and higher
Fixed Product/Version CONFIG: 70-02-72/00
Category HDD
Changed Part CONFIG
20 Invalid licensed capacity of FCv2

Phenomena When a volume created using Dynamic Provisioning for Mainframe was
specified as Flash Copy version2 source volume (S-VOL) or target
volume (T-VOL), the licensed capacity of FCv2 became invalid value.
(1) Mainframe
(2) A VOL created using Dynamic Provisioning for Mainframe is
specified as FCv2 S-VOL or T-VOL.
(3) While the above VOL is used as FCv2 S-VOL or T-VOL, zero page
discarding and data creation are executed.
- Zero page discarding in the above case includes user operation and the
others.
- Data creation in the above case includes I/O and copy operations.
Category Mainframe
21 I/O error occurrence with SSBs output during rebalance

Phenomena During rebalance processing (pool expansion/pool shrink/tier relocation),
an I/O error occurred and SSB=DD88, 14DC, 14FF, D031 and D034
were output.
(1) Rebalance (pool expansion/pool shrink/tier relocation) is executed.
(2) I/O load is high.
Category Dynamic Provisioning
22 WCHK1 occurrence at CHG removal during I/O
Phenomena When a CHG PCB was removed during I/O processing, WCHK1
occurred and SSB=32FE was output.
Conditions of Occurrence The problem may occur when any of the following conditions is met.
(1) A CHG PCB is removed during I/O processing.
(2) A CHG PCB is blocked due to LR processor failure during I/O
processing.
(3) All ESWs are blocked during I/O processing.
Category Open
23 MIH occurs when issuing I/O to an area where format write

has never been executed
Phenomena When the top pool VOL in a pool where a DP-VOL belonged was
blocked, if an I/O was issued to an area in which format write had never
been executed in the DP-VOL, MIH might occur.
(1) Dynamic Provisioning for Mainframe
(2) The top pool VOL in a pool where a DP-VOL belongs is blocked.
(3) A read or write I/O is issued to an area where format write has never
been executed in the DP-VOL.
Category Dynamic Provisioning for Mainframe
24 XRC session suspend and side file remaining

Phenomena When a micro-program was exchanged while XRC was in use,
SSB=1339, 133C and 4732 were output and the XRC session might be
suspended. Besides, a side file remained after the completion of suspend
processing.
(1) An XRC session is registered and pair creation is executed in micro-
program of earlier than V02.
(2) The micro-program is exchanged with V02 or higher.
Category Compatible XRC
25 PIN occurrence after failure in cache PCB or cache MG
Phenomena Immediately after a failure occurred in a cache PCB or cache MG, PIN
occurred, and SIM=FF4X-XX and SSB=13AE, 9FA5 were output.
Conditions of Occurrence The problem may occur immediately after a failure occurs in a cache
PCB or cache MG.
26 SIz pair failure suspension with SSBs and SIM output

Phenomena When Quick Restore of a Shadow Image for Mainframe pair which used
3390-A was executed, failure suspension occurred and SSB=229C, 2115
and SIM=47DX-XX were output.
(1) There is a Shadow Image for Mainframe pair which uses 3390-A and
is in SPLIT status.
(2) There is no update to copy source and target VOLs for HAR0 before
the 116th cylinder of VOL used by the Shadow Image for Mainframe pair
in SPLIT status.
(3) There are updates to copy source and target VOLs for HAR0 after the
116th cylinder of VOL used by the Shadow Image for Mainframe pair in
SPLIT status.
(4) There is a Shadow Image for Mainframe pair which shares the copy
source VOL.
(5) Quick Restore is executed for the SPLIT status pair in (2) and (3).

Category Shadow Image for Mainframe

VSP Microcode Update Resolves Data and Performance Issues

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

VSP Microcode Update Resolves Data and Performance Issues

Hochgeladen von

Copyright:

Verfügbare Formate

VSP

MICROCODE VERSION 70-02-70-00/00

Newly supported features and functions for Version 70-02-70-00/00

The change of contents for Version 70-02-70-00/00

2 Resource unlock failure during CM maintenance

A. RAID700 all current versions.

The micro-program has been modified to fix the problem.

B1. RAID700 All versions

The micro-program has been modified to fix the problem.

6 LDEVs wrongly created with the same LBA start point

7 WCHK1 occurrence in an MP with SIM=3073 output

9 Duplicate display of task result

10 LA error with SSBs output and possible drive blockade after

12 Incorrect display of LIST COUNTS and RMF report result

When RMF report was collected:

13 SSB=59F0 output during FCv2 copy processing

15 Failure of recovery maintenance after device removal

17 ABEND of copy processing with SIMs and SSBs output due to

18 Not logged SSB when CHP is ON

20 Invalid licensed capacity of FCv2

21 I/O error occurrence with SSBs output during rebalance

23 MIH occurs when issuing I/O to an area where format write

24 XRC session suspend and side file remaining

26 SIz pair failure suspension with SSBs and SIM output

Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher

Das könnte Ihnen auch gefallen